NEW changes in stable-new

Processing changes file: linux_4.9.144-3.1_armhf.changes ACCEPT

NEW changes in stable-new

Processing changes file: linux_4.9.144-3.1_amd64.changes ACCEPT Processing changes file: linux_4.9.144-3.1_armel.changes ACCEPT Processing changes file: linux_4.9.144-3.1_i386.changes ACCEPT

NEW changes in stable-new

Processing changes file: linux_4.9.144-3.1_arm64.changes ACCEPT

NEW changes in stable-new

Processing changes file: linux_4.9.144-3.1_s390x.changes ACCEPT

NEW changes in stable-new

Processing changes file: linux_4.9.144-3.1_all.changes ACCEPT Processing changes file: linux_4.9.144-3.1_ppc64el.changes ACCEPT

Bug#922715: debbugs: b.d.o/release-critical/britney/testing-nr wrongly reports RC bugs when reported against two packages

Package: debbugs Version: 2.6.0 Severity: normal X-Debbugs-CC: debian-release@lists.debian.org Hi Don, You may have noticed that I file a lot of bugs nowadays against two source packages due to autopkgtest failures in testing with one or more packages from unstable. Typically, I file them

Re: debian squeeze repository

On Tue, Feb 19, 2019 at 06:11:27PM +, miel...@t-online.de wrote: > > Ladies and gentlemen, > > I tried to update a debian squeeze OS, with a > /etc/apt/sources.list Debian 6 "Squeeze" stopped receiving security and errata updates in 2014. You should upgrade to a supported release as soon as

debian squeeze repository

Ladies and gentlemen, I tried to update a debian squeeze OS, with a /etc/apt/sources.list deb http://archive.debian.org/debian/ squeeze contrib main non-free I got GPG error: http://archive.debian.org squeeze Release: The following signatures were invalid: KEYEXPIRED 1520281423 KEYEXPIRED

NEW changes in stable-new

Processing changes file: linux_4.9.144-3.1_source.changes ACCEPT

Re: toulbar2: What will happen if testing migration takes longer than removal from testing

> Hi Thomas, >> Dear Andreas, >> >> Thanks for taking care of toulbar2. I did spend some time to try to go >> around this #920459 bug but even a postprocessing of the LaTeX output of >> doxygen (removing inclusion of the xcolor package that generates the >> LaTeX compilation issue) did not work

Re: toulbar2: What will happen if testing migration takes longer than removal from testing

Sorry, missed the Reply-All as Andreas pointed out. See attached mail. Thomas --- Begin Message --- Hi Thomas, On Tue, Feb 19, 2019 at 11:15:13AM +0100, Thomas Schiex wrote: > Dear Andreas, > > Thanks for taking care of toulbar2. I did spend some time to try to go > around this #920459 bug

Re: toulbar2: What will happen if testing migration takes longer than removal from testing

On Tue, Feb 19, 2019 at 11:13:29AM +0100, Andreas Tille wrote: > On Tue, Feb 19, 2019 at 09:07:24AM +0100, Ondřej Surý wrote: > > I believe that it was the case before that if the autoremoval was due a > > specific RC bug, any activity on that specific bug would reset the timer > > for

Re: toulbar2: What will happen if testing migration takes longer than removal from testing

On Tue, Feb 19, 2019 at 09:07:24AM +0100, Ondřej Surý wrote: > I believe that it was the case before that if the autoremoval was due a > specific RC bug, any activity on that specific bug would reset the timer for > autoremoval. I've thought the same but despite the activity it is not reset (at

NEW changes in stable-new

Processing changes file: postgresql-9.6_9.6.12-0+deb9u1_amd64.changes ACCEPT

Subvenciones a fondo perdido para empresas

Subvenciones para Pymes Subvenciones Subvenciones a fondo perdido para pymes. Saber msSubvenciones europeas, nacionales y de las comunidades autnomas. Buscador de subvenciones de toda clase para todo el territorio nacional. Alertas programables. Gestin includa. Quiero saber ms Si lo

Re: toulbar2: What will happen if testing migration takes longer than removal from testing

Hi, I believe that it was the case before that if the autoremoval was due a specific RC bug, any activity on that specific bug would reset the timer for autoremoval. But it might have changed since… or my memory is failing me. Cheers, Ondrej > On 19 Feb 2019, at 08:46, Andreas Tille wrote: