Re: 8.4 and 7.10 planning
-boot? On 2016-02-21 12:24, Adam D. Barratt wrote: Hi, We're due both Jessie and Wheezy point releases, and are proposing doing both on the same weekend again, as we did for 8.2 and 7.9, as the CD team seem happy to try it again. Some suggested dates: March 12th / 13th March 19th / 20th
NEW changes in stable-new
Processing changes file: linux_3.16.7-ckt25-1_mips.changes ACCEPT
Bug#816243: jessie-pu: package subversion/1.8.10-6+deb8u3
On Sun, Feb 28, 2016 at 09:38:23PM -0500, James McCoy wrote: > I'd like to propose the following update (+ s/UNRELEASED/jessie/) to fix a > crash when running svn and using kwallet to store credentials. Ping. > $ debdiff subversion_1.8.10-6+deb8u{2,3}.dsc > diffstat for
NEW changes in stable-new
Processing changes file: linux_3.16.7-ckt25-1_mipsel.changes ACCEPT
Bug#817003: transition: glibc
Emilio Pozuelo Monfort wrote: > On 08/03/16 13:46, Steven Chamberlain wrote: > > Many architectures will be binNMUd against libc6 2.22, but please on > > kfreebsd-* could you binNMU these packages against libc0.1 2.22 instead: > > > > * p11-kit (breaks sid at the moment) > > * libnss-db > >
Bug#816891: jessie-pu: package espeakup/1:0.71-19
Hello, It is now uploaded. Samuel
NEW changes in oldstable-new
Processing changes file: linux_3.2.78-1_mips.changes ACCEPT
Re: Britney migration/removal emails not sent and removals not processed?
On 03/09/2016 08:14 PM, Adam D. Barratt wrote: > The footer of every mail should say exactly that. Yes, unfortunately I read that only after I sent my mail - I had previously thought Britney would run only once a day. Had the package migrated only today and the email had been immediate, I
Re: Britney migration/removal emails not sent and removals not processed?
On Wed, 2016-03-09 at 18:24 +, Niels Thykier wrote: > Christian Seiler: > > Hi again, > > > >> - I didn't get notified that open-iscsi migrated to testing yesterday. > > > > Great, I have the worst luck w.r.t. timing, just as a I sent the email I > > got the notification. :/ > > > >> sorry
Bug#815919: marked as done (nmu: gimagereader_3.1.2+git368fa8f-2 sikuli_1.0~x~rc3.tesseract3-dfsg1-12)
Your message dated Wed, 9 Mar 2016 20:04:13 +0100 with message-id <56e073ad.40...@debian.org> and subject line Re: Bug#815919: nmu: tesseract_3.04.01-3 openalpr_2.2.3-1 gimagereader_3.1.2+git368fa8f-1 sikuli_1.0~x~rc3.tesseract3-dfsg1-12 has caused the Debian Bug report #815919, regarding nmu:
Processed: Re: nmu: tesseract_3.04.01-3 openalpr_2.2.3-1 gimagereader_3.1.2+git368fa8f-1 sikuli_1.0~x~rc3.tesseract3-dfsg1-12
Processing control commands: > retitle -1 nmu: gimagereader_3.1.2+git368fa8f-2 > sikuli_1.0~x~rc3.tesseract3-dfsg1-12 Bug #815919 [release.debian.org] nmu: tesseract_3.04.01-4 openalpr_2.2.3-1 Changed Bug title to 'nmu: gimagereader_3.1.2+git368fa8f-2 sikuli_1.0~x~rc3.tesseract3-dfsg1-12' from
Bug#815919: nmu: tesseract_3.04.01-3 openalpr_2.2.3-1 gimagereader_3.1.2+git368fa8f-1 sikuli_1.0~x~rc3.tesseract3-dfsg1-12
Control: retitle -1 nmu: gimagereader_3.1.2+git368fa8f-2 sikuli_1.0~x~rc3.tesseract3-dfsg1-12 On Thu, 25 Feb 2016 18:50:49 +0100 Andreas Beckmannwrote: > The ABI change has been reverted and the transition to > libtesseract4 has to be undone (#815056). tesseract and openalpr
Bug#815919: nmu: tesseract_3.04.01-3 openalpr_2.2.3-1 gimagereader_3.1.2+git368fa8f-1 sikuli_1.0~x~rc3.tesseract3-dfsg1-12
retitle 815919 nmu: tesseract_3.04.01-4 openalpr_2.2.3-1 gimagereader_3.1.2+git368fa8f-2 sikuli_1.0~x~rc3.tesseract3-dfsg1-12 thanks There are some good reasons to do this sooner rather than later.
Processed (with 1 error): Re: Bug#815919: nmu: tesseract_3.04.01-3 openalpr_2.2.3-1 gimagereader_3.1.2+git368fa8f-1 sikuli_1.0~x~rc3.tesseract3-dfsg1-12
Processing commands for cont...@bugs.debian.org: > retitle 815919 nmu: tesseract_3.04.01-4 openalpr_2.2.3-1 Bug #815919 [release.debian.org] nmu: tesseract_3.04.01-3 openalpr_2.2.3-1 gimagereader_3.1.2+git368fa8f-2 sikuli_1.0~x~rc3.tesseract3-dfsg1-12 Changed Bug title to 'nmu:
Re: Britney migration/removal emails not sent and removals not processed?
Christian Seiler: > Hi again, > >> - I didn't get notified that open-iscsi migrated to testing yesterday. > > Great, I have the worst luck w.r.t. timing, just as a I sent the email I > got the notification. :/ > >> sorry for the noise. > > Regards, > Christian > Indeed :) Britney runs
NEW changes in oldstable-new
Processing changes file: linux_3.2.78-1_mipsel.changes ACCEPT
Re: Britney migration/removal emails not sent and removals not processed?
Hi again, > - I didn't get notified that open-iscsi migrated to testing yesterday. Great, I have the worst luck w.r.t. timing, just as a I sent the email I got the notification. :/ > sorry for the noise. Regards, Christian signature.asc Description: OpenPGP digital signature
Britney migration/removal emails not sent and removals not processed?
Dear release team, Britney seems to have stopped in sending notifications about testing migrations to package maintainers: - I didn't get notified that open-iscsi migrated to testing yesterday. - The package tracker [1] doesn't have an entry for that either. I also checked that if I look at
Bug#817258: wheezy-pu: package privoxy/3.0.19-2+deb7u4
Just after sending this out I noticed, that I wrote "stable" instead of "oldstable" to the changelog. Here's a fixed patch. Tscho Rolanddiff -Nru privoxy-3.0.19/debian/changelog privoxy-3.0.19/debian/changelog --- privoxy-3.0.19/debian/changelog 2016-01-22
Bug#817258: wheezy-pu: package privoxy/3.0.19-2+deb7u4
Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu I prepared a patch against privoxy 3.0.19-2+deb7u3, which closes the CVE-2013-2503, see
Re: [Reproducible-builds] [Reproducible] On making Stretch self-contained IRT to reproducibility
On Wed, Mar 9, 2016 at 5:24 PM, Holger Levsen wrote: > I dont think doing thousands of sourceful uploads is realistic nor useful Now that we have source-only uploads, it should be fairly easy to do on a fast network. Just a for loop around apt-get source, dch, debuild -S, debsign, dupload. --
NEW changes in stable-new
Processing changes file: linux_3.16.7-ckt25-1_armel.changes ACCEPT
Bug#817184: transition: sndio
Hi >Please go ahead. done a few seconds ago. thanks for the quick answer! Please hold on libsdl2, the fix is already on deferred/2 (for the RC bug), and I would like if possible to avoid an useless binNMU :) cheers, Gianfranco
Re: [Reproducible-builds] [Reproducible] On making Stretch self-contained IRT to reproducibility
Hi! On Wed, 2016-03-09 at 10:32:08 +0100, Holger Levsen wrote: > On Mittwoch, 24. Februar 2016, Emilio Pozuelo Monfort wrote: > > On 24/02/16 22:16, Niels Thykier wrote: > > >- Possible lack of buildd resources to do the rebuild. Notably, due > > > to Multi-Arch:same we would generally
NEW changes in oldstable-new
Processing changes file: linux_3.2.78-1_armel.changes ACCEPT Processing changes file: linux_3.2.78-1_powerpc.changes ACCEPT
NEW changes in stable-new
Processing changes file: linux_3.16.7-ckt25-1_armhf.changes ACCEPT
Re: [Reproducible-builds] [Reproducible] On making Stretch self-contained IRT to reproducibility
On Wed, Mar 9, 2016 at 11:10:38 +0100, Holger Levsen wrote: > Hi, > > On Mittwoch, 9. März 2016, Julien Cristau wrote: > > Most source packages that build both arch:all and arch-dependent > > packages will be affected, I believe. Enough that for all practical > > purposes, an arch:all binNMU
Re: [Reproducible-builds] [Reproducible] On making Stretch self-contained IRT to reproducibility
Hi, On Mittwoch, 9. März 2016, Julien Cristau wrote: > Most source packages that build both arch:all and arch-dependent > packages will be affected, I believe. Enough that for all practical > purposes, an arch:all binNMU means making things uninstallable, so is a > big no-no. IOW: if a source
Re: [Reproducible-builds] [Reproducible] On making Stretch self-contained IRT to reproducibility
On Wed, Mar 9, 2016 at 10:24:44 +0100, Holger Levsen wrote: > > On the arch:all rebuild-ability > > === > > > > Rebuilding arch:all packages currently requires manual uploads of all > > packages. While we have "arch:all" buildds, we do *not* have support > > for
Bug#817184: transition: sndio
Control: tags -1 confirmed On 08/03/16 20:19, Peter Piwowarski wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > libsndio has undergone a minor SONAME bump in the latest release; there is > however no consequential
Processed: Re: Bug#817184: transition: sndio
Processing control commands: > tags -1 confirmed Bug #817184 [release.debian.org] transition: sndio Added tag(s) confirmed. -- 817184: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: [Reproducible-builds] [Reproducible] On making Stretch self-contained IRT to reproducibility
Hi, On Mittwoch, 24. Februar 2016, Emilio Pozuelo Monfort wrote: > On 24/02/16 22:16, Niels Thykier wrote: > >- Possible lack of buildd resources to do the rebuild. Notably, due > > to Multi-Arch:same we would generally need to do the rebuild on all > > architectures. > FWIW, that
Re: [Reproducible-builds] [Reproducible] On making Stretch self-contained IRT to reproducibility
Hi, On Mittwoch, 24. Februar 2016, Niels Thykier wrote: > The topic of rebuilding all of Stretch to make it self-contained (IRT to > reproducibility) was brought up on the release IRC meeting today (topic > originally proposed in [1]). The highlights: > * To my knowledge, only people from the
NEW changes in oldstable-new
Processing changes file: linux_3.2.78-1_i386.changes ACCEPT