Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #11208
| From | Scott Kitterman <debian@kitterman.com> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Numpy migration? |
| Date | 2019-01-05 21:00 +0100 |
| Message-ID | <xd0gW-18d-11@gated-at.bofh.it> (permalink) |
| References | <xcUXT-6rf-5@gated-at.bofh.it> <xcWdj-78E-1@gated-at.bofh.it> <xd07g-14F-17@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Saturday, January 05, 2019 08:30:28 PM Ole Streicher wrote: > Mattia Rizzolo <mattia@debian.org> writes: > > 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. > > I agree (with the explanation in your other mail) here; it just states > the fact that they really don't go together very well (at least in > situation similar to the specific CI test). For what it's worth, I hit (AIUI) the same situation when I updated python- bleach. It broke python-readme-renderer. I reuploaded python-bleach with the breaks and a new version of python-readme-renderer (which worked with the new bleach) and both migrated two days later (since they both had autopkgtests). Scott K
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Numpy migration? Ole Streicher <olebole@debian.org> - 2019-01-05 15:20 +0100
Re: Numpy migration? Mattia Rizzolo <mattia@debian.org> - 2019-01-05 15:40 +0100
Re: Numpy migration? Ole Streicher <olebole@debian.org> - 2019-01-05 16:20 +0100
Re: Numpy migration? Mattia Rizzolo <mattia@debian.org> - 2019-01-05 16:40 +0100
Re: Numpy migration? Ole Streicher <olebole@debian.org> - 2019-01-05 20:50 +0100
Re: Numpy migration? Scott Kitterman <debian@kitterman.com> - 2019-01-05 21:00 +0100
Re: Numpy migration? Mattia Rizzolo <mattia@debian.org> - 2019-01-06 01:40 +0100
Re: Numpy migration? Ole Streicher <olebole@debian.org> - 2019-01-06 17:30 +0100
Re: Numpy migration? Steffen Möller <steffen_moeller@gmx.de> - 2019-01-06 18:20 +0100
Re: Numpy migration? Mattia Rizzolo <mattia@debian.org> - 2019-01-06 18:50 +0100
Re: Numpy migration? Mattia Rizzolo <mattia@debian.org> - 2019-01-06 19:00 +0100
Re: Numpy migration? Ole Streicher <olebole@debian.org> - 2019-01-07 09:30 +0100
Re: Numpy migration? Mattia Rizzolo <mattia@debian.org> - 2019-01-07 17:30 +0100
Re: Numpy migration? Ole Streicher <olebole@debian.org> - 2019-01-07 18:10 +0100
Re: Numpy migration? Paul Gevers <elbrus@debian.org> - 2019-01-07 21:10 +0100
Re: Numpy migration? Ole Streicher <olebole@debian.org> - 2019-01-05 16:40 +0100
Re: Numpy migration? Mattia Rizzolo <mattia@debian.org> - 2019-01-05 16:50 +0100
csiph-web