Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Mattia Rizzolo Newsgroups: linux.debian.maint.python Subject: Re: Numpy migration? Date: Sat, 05 Jan 2019 16:40:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Sat Jan 5 15:36:00 2019 Old-Return-Path: X-Amavis-Spam-Status: No, score=-11.9 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -3.5 Mail-Followup-To: debian-python@lists.debian.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="bCsyhTFzCvuiizWE" Content-Disposition: inline X-Info: Keep It Simple, Stupid. X-Operating-System: Linux, kernel 4.19.0-1-amd64, inside Debian GNU/Linux buster/sid sid. X-Message-Flag: WARNING!! Outlook sucks. A lot. User-Agent: Every email client sucks, this one just sucks less. X-Mailing-List: archive/latest/16656 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20190105153545.GB26988@mapreri.org Approved: robomod@news.nic.it Lines: 90 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Sat, 5 Jan 2019 16:35:46 +0100 X-Original-Message-ID: <20190105153545.GB26988@mapreri.org> X-Original-References: <87a7kfqk65.fsf@orrococo> <8736q7qh9w.fsf@orrococo> Xref: csiph.com linux.debian.maint.python:11205 --bCsyhTFzCvuiizWE Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 05, 2019 at 04:02:35PM +0100, Ole Streicher wrote: > I'll do tonight. It however looks a bit suboptimal: when the CI test > with a new version fails for an old reverse dependency, then the new > version obviously breaks that old package. So, the breakage could be > detected (and taken into account) automatically. Why do we need a manual > action then? Let me try to suggest you see from another side: the goal of the Breaks field is to prevent a given combination of known broken packages to be installed. Currently autopkgtest blocks the migration of numpy, but if there wasn't that block a Breaks should still be added, as the astropy in testing is not compatible with the new numpy. The fact that it hints britney to trigger the right tests is just a "side effects", the Breaks should be added nonetheless, theoretically; in practice, we rarely did it before autopkgtest started blocking the testing migration. > >> Another CI problem is python-astropy, which is the Python 2 version of > >> Astropy. python-astropy is going to be removed as soon as there are no > >> backward dependencies left; however there is still some cruft in > >> unstable that depends on python-astropy. But this should not hinder > >> numpy to migrate. > > > > I don't understand this, I don't see any python2-related issue right > > now. Could you please expand? >=20 > The new python-numpy breaks python-astropy in testing. Oh, sorry. I didn't realize python-astropy is a different source package=E2=80=A6 > Python-astropy is > however going to be removed completely; it has however some cruft rdeps > left in unstable. So, it cannot removed from unstable now, and therefore > still remains in testing and (unnecessarily) blocks the numpy migration. > Python-astropy already has an RC bug, but its autoremoval from testing > is still not even announced yet. Maybe you could ask the release team to hasten the removal of python-astropy and rdeps from testing? If the plan is to not relase it in buster I don't see a reason to keep it further. > The migration blocking CI tests seem to cause much more headaches than > just "fix your bugs"... Well, from what I see, it has helped a lot in this half a year detect a ton of regressions that would have otherwise bothered several people in a later moment=E2=80=A6 For sure it's not just "fix your bugs" but more like "fix your bugs AND all your rdeps", in fact you'd expect the maintainer of the package breaking everything to be a tad more proactive, but in many cases like this, it's not. --=20 regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=3Dmattia `- --bCsyhTFzCvuiizWE Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlwwzs4ACgkQCBa54Yx2 K63ZZg/8C1D7i5/4TfFpiv8C6iN+HM2Rn5eG3e5Al7GfiWOSBBD7TW+F4kL7HZRr y2NnS97cigMvdxcus3EXpyMw4pAOdodFXhh1N0gu0pydo0+QIDUNXtEWrB8dBOfr fbDjMJ/feWqPQOyJCGqSOKle+b5h8n7L5PNFlbkA/BnNWkqNnMbOb8IxP07Qgjx7 vSxezilmS/H1v6Uz4dfgGC4Q78vV+JcI7jbDL8c5NRdrvpz0IS8Afh8b6Npdl0/j qKFfkAHWSFfCrI7XLnoN9zceJFpuoqr2ECa7iEhRuMQPRWEQgDbUmN8PD8WQ6YYA nTlAsK+UKnb6SKOMkeyuIs0RePhxnitaN2n3x5TwfNskE1kXqxD+O49QpDoIFURT J+4SdrJB8/uvUuIPAtxTMkmtk+ZVARCt9ozqBD3a43BFdGsFDb8ZnVkxQTsT9d2y 2z9EnkaALwd8e21+vgdHs0ThSJMpwaVmgI6PUeYqnnKZxobYBO7GnvWfZJhmlGBe sv7mJu9JASX8MZpuFibyb710JY+w1flLzEmrhSQj3nF8E7GbEdWImgVUqHfEOv4h LawVnlJzvW0PyF2mVmT2a2yX32cOSwZ4gvpe7kdJPmx3saGUAOob4fm1q112cDTv LFoME0UYPSwNwgwJkgR7YqY46VU9RtV41SiEO+NbPqXtLJuU13Q= =Lvd/ -----END PGP SIGNATURE----- --bCsyhTFzCvuiizWE--