Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Paul Gevers Newsgroups: linux.debian.maint.python Subject: Re: Numpy migration? Date: Mon, 07 Jan 2019 21:10:02 +0100 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Jan 7 20:04:24 2019 Old-Return-Path: X-Amavis-Spam-Status: No, score=-12.3 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DIGITS_LETTERS=1, LDO_WHITELIST=-5, MD5_SHA1_SUM=-1, MEDS2=2, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no Openpgp: preference=signencrypt Autocrypt: addr=elbrus@debian.org; prefer-encrypt=mutual; keydata= mQENBE2LmVYBCADS6vA01KutEM74dDGrsmT2q6Mh5C3TAyNhLigBEWNGnfbFr6AHX1EvdkC/ 7g5QcFGqiiOjTdHncRNtvUbistfbF1ynE6evD3p5tpkn6ymmVwSIjx9np7GWJgZgBo0zkpij M1iimHTs1BcZhL7WQlvVJO3Xm8jr7NpgjkRRkkPaj0Kd/HYuPGqN74pwXB7nR5Uw2ypYS0eT iCHUUTUrvgP3fqOWc2bgbCIsuoXpp/QLT5ehC+M01UKMHVUkr97cwT4wg03XqE2cL7r6szry GZMpL3CU4IsPNghfeZhRrZlk6A73OtpLxTXibydt8Og91eC2ALer28bJnn+haIaTNwc3ABEB AAG0H1BhdWwgR2V2ZXJzIDxlbGJydXNAZGViaWFuLm9yZz6JAUAEEwEIACoCGyMFCQ8JnAAF CwkIBwMFFQoJCAsFFgIDAQACHgECF4AFAlTDaZECGQEACgkQnFyZ6wW9dQoAOwf/RXvt0Qs7 x8TY0oaf8CnUdtsO9a5J7P+AEIPTUrB00uxWnSW2oE/qmWMIPgH95X3VvOZkXNLNcc74N1TV jz5Q15LbUBU2x39jJEdPPv0lUXzzJ6z0vR1Am+sXOVyG9JIS4OP2vkgL3M2kd3FLIstA13Kx Ri3GsXliLVNrZ4gmuYKRh3TUYCBQsm1WY9mQBTIkjtqMRSSImsp95rLFU+ypr7JeGRqY0vc9 xOghcCo4rtHe8DlWsfI0mRSC0yIj4Ckith6DND7BWv5rvyB9Q0EOL86ZjAIGoxSappdo5+Dp k74LP3pzTh2Y6ZH1OPdUnBWmncOgJhhOBebtAuRhl4yrw7kBDQRNi5lWAQgAumUcESLidpdh WC3ef1EUoJE0n8ADZ11gaTTlWIbhq773gNHvSq06CKamQkY6wIrmluGmkKvHcGGaQjCYat1c 1VtAtAQO0AEa3jxEHyV5DYh8mBKCa5rdtc0DvCj9Zndd07V9Y4/0qrdmOHn2yimdlXlsJ4LI FzsAk1co+7bYen8J/uWz6bcaf1MeAlw+RuF7xkxn0aRGutbH74ejRGU23v+4BhRDgUmre3rF QI9e9DVXOFfB1/vzbZSa5RHHugTGwr7oObxeIhpDGDcG3cxbtvqwfsPQ5qNutpZ1rVGEKV9Z 55m1kvJ1O8oAnCnf8XNPMWArtYLevWB6e8jqitja9wARAQABiQElBBgBCAAPBQJNi5lWAhsM BQkPCZwAAAoJEJxcmesFvXUK9RUH/2TVjz5SiUAGe8G9BiGFVmKm0/XdLbpzvJYA1Rj4P9tn J90WhvfZgEsFqDge+PasjeLzzuTUebFkt6oI4YaZ/KA22DQ4DCSJmdUploZ+N2x88Kls1GJW CVsODIIvoRDviTCOmoqQv5zjCkSdm/TJcIBQzZ4Y4eUWMiFu7Hd7MJxI8fMtvZolqZAtguym tqJRtC0eFX8qn+jVIfUboue1cel+MHSWwwimZ0kmQWrujT//fP/i7BXBuYBiltTINiJ8oj1T 4xG+Fzs7OWHVImeuNDoi8gIROi1Ov59ASI0TXTtjC8ge9OTAw2Ka1Cxk7sOCNsymv03ji7Fe UpMdtYrHduSZAQ0ETYuZVgEIANLq8DTUq60Qzvh0MauyZParoyHkLdMDI2EuKAERY0ad9sWv oAdfUS92QL/uDlBwUaqKI6NN0edxE229RuKy19sXXKcTp68Penm2mSfrKaZXBIiPH2ensZYm BmAGjTOSmKMzWKKYdOzUFxmEvtZCW9Uk7debyOvs2mCORFGSQ9qPQp38di48ao3vinBcHudH lTDbKlhLR5OIIdRRNSu+A/d+o5ZzZuBsIiy6hemn9AtPl6EL4zTVQowdVSSv3tzBPjCDTdeo TZwvuvqzOvIZkykvcJTgiw82CF95mFGtmWToDvc62kvFNeJvJ23w6D3V4LYAt6vbxsmef6Fo hpM3BzcAEQEAAbQfUGF1bCBHZXZlcnMgPGVsYnJ1c0BkZWJpYW4ub3JnPokBQAQTAQgAKgIb IwUJDwmcAAULCQgHAwUVCgkICwUWAgMBAAIeAQIXgAUCVMNpkQIZAQAKCRCcXJnrBb11CgA7 B/9Fe+3RCzvHxNjShp/wKdR22w71rkns/4AQg9NSsHTS7FadJbagT+qZYwg+Af3lfdW85mRc 0s1xzvg3VNWPPlDXkttQFTbHf2MkR08+/SVRfPMnrPS9HUCb6xc5XIb0khLg4/a+SAvczaR3 cUsiy0DXcrFGLcaxeWItU2tniCa5gpGHdNRgIFCybVZj2ZAFMiSO2oxFJIiayn3mssVT7Kmv sl4ZGpjS9z3E6CFwKjiu0d7wOVax8jSZFILTIiPgKSK2HoM0PsFa/mu/IH1DQQ4vzpmMAgaj FJqml2jn4OmTvgs/enNOHZjpkfU491ScFaadw6AmGE4F5u0C5GGXjKvDuQENBE2LmVYBCAC6 ZRwRIuJ2l2FYLd5/URSgkTSfwANnXWBpNOVYhuGrvveA0e9KrToIpqZCRjrAiuaW4aaQq8dw YZpCMJhq3VzVW0C0BA7QARrePEQfJXkNiHyYEoJrmt21zQO8KP1md13TtX1jj/Sqt2Y4efbK KZ2VeWwngsgXOwCTVyj7tth6fwn+5bPptxp/Ux4CXD5G4XvGTGfRpEa61sfvh6NEZTbe/7gG FEOBSat7esVAj170NVc4V8HX+/NtlJrlEce6BMbCvug5vF4iGkMYNwbdzFu2+rB+w9Dmo262 lnWtUYQpX1nnmbWS8nU7ygCcKd/xc08xYCu1gt69YHp7yOqK2Nr3ABEBAAGJASUEGAEIAA8F Ak2LmVYCGwwFCQ8JnAAACgkQnFyZ6wW9dQr1FQf/ZNWPPlKJQAZ7wb0GIYVWYqbT9d0tunO8 lgDVGPg/22cn3RaG99mASwWoOB749qyN4vPO5NR5sWS3qgjhhpn8oDbYNDgMJImZ1SmWhn43 bHzwqWzUYlYJWw4Mgi+hEO+JMI6aipC/nOMKRJ2b9MlwgFDNnhjh5RYyIW7sd3swnEjx8y29 miWpkC2C7Ka2olG0LR4Vfyqf6NUh9Rui57Vx6X4wdJbDCKZnSSZBau6NP/98/+LsFcG5gGKW 1Mg2InyiPVPjEb4XOzs5YdUiZ640OiLyAhE6LU6/n0BIjRNdO2MLyB705MDDYprULGTuw4I2 zKa/TeOLsV5Skx21isd25A== User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.1 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="1avso6O1ECKp8mwTQFgJRfY2d42qOeonv" X-Mailing-List: archive/latest/16669 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/52b0308c-ae05-a627-1ca1-babc47c93a2f@debian.org Approved: robomod@news.nic.it Lines: 145 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: Niels Thykier X-Original-Date: Mon, 7 Jan 2019 21:03:59 +0100 X-Original-Message-ID: <52b0308c-ae05-a627-1ca1-babc47c93a2f@debian.org> X-Original-References: <87a7kfqk65.fsf@orrococo> <8736q7qh9w.fsf@orrococo> <20190105153545.GB26988@mapreri.org> <87tvimq4vf.fsf@orrococo> <20190105221009.GA23578@mapreri.org> <87h8elpy5u.fsf@orrococo> <20190106175829.GH23578@mapreri.org> <87d0p8q4hs.fsf@orrococo> <20190107162036.GU23578@mapreri.org> Xref: csiph.com linux.debian.maint.python:11218 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --1avso6O1ECKp8mwTQFgJRfY2d42qOeonv Content-Type: multipart/mixed; boundary="QXReNKNabMVIz3AIyFjW3pYrNb3ZhSnf6"; protected-headers="v1" From: Paul Gevers To: debian-python@lists.debian.org Cc: Niels Thykier Message-ID: <52b0308c-ae05-a627-1ca1-babc47c93a2f@debian.org> Subject: Re: Numpy migration? References: <87a7kfqk65.fsf@orrococo> <8736q7qh9w.fsf@orrococo> <20190105153545.GB26988@mapreri.org> <87tvimq4vf.fsf@orrococo> <20190105221009.GA23578@mapreri.org> <87h8elpy5u.fsf@orrococo> <20190106175829.GH23578@mapreri.org> <87d0p8q4hs.fsf@orrococo> <20190107162036.GU23578@mapreri.org> In-Reply-To: <20190107162036.GU23578@mapreri.org> --QXReNKNabMVIz3AIyFjW3pYrNb3ZhSnf6 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Hi Mattia, all, On 07-01-2019 17:20, Mattia Rizzolo wrote: > On Mon, Jan 07, 2019 at 09:03:11AM +0100, Ole Streicher wrote: >> Mattia Rizzolo writes: >>> On Sun, Jan 06, 2019 at 05:07:41PM +0100, Ole Streicher wrote: >>>> Now it turns out that there is a new migration problem, which is apl= py: >>>> Current aplpy (2.0~rc2-2) CI test works well >>> >>> You probably mean aplpy 1.1.1-4. >> >> No, I meant the one above (although the unstable test was not done on >> ci.d.n when I wrote my last mail). >=20 > Right, that explains why I didn't see it. > It seems now britney is triggering aplpy test with a big set of > triggers (I suppose the result of the several Breaks that have been > added in the meantime), so it's indeed trying to move everything > together. Indeed. >> The problem is that aplpy uses matplotlib, and the old matplotlib uses= >> the deprecated numpy function np.asscalar(), which leads to a >> DeprecationWarning, which is (on purpose, by upstream) thrown as error= =2E >> >> https://ci.debian.net/data/autopkgtest/testing/amd64/a/aplpy/1658948/l= og.gz >> >> This does only happen in the combination "new numpy + old matplotlib",= >> but this is the one that is tested for the CI test. >=20 > mhh=E2=80=A6 for this, indeed a breaks numpy -> matplotlib could be use= d, but it > feels a bit too strong to me, as nothing was really broken since it's > just deprecations. >=20 > elbrus; this is a case where I think I could use your input (tl;dr: new= > numpy causes deprecations in testing's version of matplotlib (fixed in > unstable), which in turn causes failures in new aplpy, how to make the > stack happy?). The commit, with lots of comments [1], that implemented most of the related logic is here: https://salsa.debian.org/release-team/britney2/commit/18633e275c34973379f= 1426542047bf30c7829c3 With the current code your options are: - *versioned* depends on one of the binary packages from the source you want from unstable in any of the binary packages that is going to be taken from unstable - *versioned* breaks or conflicts on the binary packages from the source you want from unstable in any of the binary packages that is going to be taken from unstable - *versioned* test dependency in the package that is used for autopkgtest (only helps if the version that is tested is already taken from unstable). The version of the test dependency will NOT be added to the triggers (maybe, I have to think about it, that could be an britney improvement), but if the version of the autopktest is going to be taken from unstable already due to other considerations, with the current settings of ci.d.n and autopkgtest the required version will be installed= =2E Personally I don't think it is an issue to add the breaks, but I can see why people find it heavy in cases like this one. As discussed in the med-fichier bug, britney may want to grow knowledge from a X-breaks-autopkgtest-of-source header, but that doesn't exist now and I am not extremely keen about adding it because I fear people may too easily add it when a normal breaks is in order. Paul [1] + # Here we figure out what is required from the source suite + # for the test to install successfully. + # + # Loop over all binary packages from trigger and + # recursively look up which *versioned* dependencies are + # only satisfied in the source suite. + # + # For all binaries found, look up which packages they + # break/conflict with in the target suite, but not in the + # source suite. The main reason to do this is to cover test + # dependencies, so we will check Testsuite-Triggers as + # well. + # + # OI: do we need to do the first check in a smart way + # (i.e. only for the packages that are actully going to be + # installed) for the breaks/conflicts set as well, i.e. do + # we need to check if any of the packages that we now + # enforce being from the source suite, actually have new + # versioned depends and new breaks/conflicts. + # + # For all binaries found, add the set of unique source + # packages to the list of triggers. --QXReNKNabMVIz3AIyFjW3pYrNb3ZhSnf6-- --1avso6O1ECKp8mwTQFgJRfY2d42qOeonv Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAlwzsLAACgkQnFyZ6wW9 dQpMOgf+Iyld3qsSYUQq+vEISgPyNnuUxI8iv6DcE+oieH2H49+A73xx2A0oqcTf lX6akdybzEqsNDUhM03KV4dRtEwF6zfwMDcYXntlfDVkZq2yRn6rQrZPu9JFSORo mpiCeObJwg04HAseCwl39PpWXCW6IOUXs7WLuvonn1W4EYP/mmu2p+NOr9MVtKVY AHgsIDUq6sJ3XHaeXk6DdlumGzqsIapOY7rHDNBVkf7EfpZiXUZ1EqYx31X/z7lc SIyMlBTraZz9nf/L3orgTDE5zqJIUvK9OleAqqPXKwvdSb65uuoPhOkHBlk386sj EEnTYDQbBYw/0dxt8vLVtBv8F2IEXQ== =0vaM -----END PGP SIGNATURE----- --1avso6O1ECKp8mwTQFgJRfY2d42qOeonv--