Request to update the gnukhata-core new version

Hola , I have updated the Gnukhata-core version to 5.50 and it has passed lintian and sbuild and is ready to be uploaded. I would request mentors to please look into this and test it and update as needed. Thank you so much Manas Kashyap

Re: Numpy migration?

Mattia Rizzolo writes: > The way forward in cases like these is for the package that originally > cuased the breakage (i.e. numpy) to declare a versioned Breaks on the > borken and now fixed package (i.e. astropy (<< 3.1-1)). This way > britney and debci will know they have to test numpy and

Re: Numpy migration?

Mattia Rizzolo 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

Re: Numpy migration?

On Saturday, January 05, 2019 08:30:28 PM Ole Streicher wrote: > Mattia Rizzolo 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

About to upload pelican

Control: tag +pending On Fri, Jan 04, 2019 at 11:50:57PM +0100, Geert Stappers wrote: > On Sat, Jan 05, 2019 at 12:58:49AM +0300, Dmitry Shachnev wrote: > > On Fri, Jan 04, 2019 at 10:16:20PM +0100, Geert Stappers wrote: > > > > > > I would like to create > > >

Numpy migration?

Hi all, Since a few days, a new RC is stalled in unstable: testing: 1:1.15.4-2 unstable: 1:1.16.0~rc1-3 The reason that it can't migrate is that it breaks the CI tests of several packages in testing. For example astropy (where I am the uploader), and its dependencies. The CI test failures were

Re: Numpy migration?

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

Re: Numpy migration?

On Sat, Jan 05, 2019 at 04:15:04PM +0100, Ole Streicher wrote: > There is one more problem, which are transitional dependencies: > > The new python3-numpy version breaks (f.e.) python3-pyregion because of > the problem in python3-astropy. The new upload of python3-astropy fixes > this, so in

Re: Numpy migration?

)On Sat, Jan 5, 2019 at 3:18 PM Ole Streicher wrote: > However, astropy cannot migrate now, to testing, since it depends on the > new numpy version (and therefore can only migrate after numpy). And > numpy is blocked by the CI failure of astropy ... > > Looks like a deadlock. Which will be

Re: Numpy migration?

Mattia Rizzolo writes: > The way forward in cases like these is for the package that originally > cuased the breakage (i.e. numpy) to declare a versioned Breaks on the > borken and now fixed package (i.e. astropy (<< 3.1-1)). This way > britney and debci will know they have to test numpy and

Re: Numpy migration?

On Sat, Jan 05, 2019 at 08:30:28PM +0100, Ole Streicher wrote: > >> 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