Bug#827061: Please commit to OpenSSL 1.0.2 in stretch now not constantly re-evaluateing

Sam Hartman: > > My understanding of the current plan is that we're adding openssl 1.1.0 > to unstable, but will make a decision about whether to drop libssl1.0.2 > later. > > That's really frustrating for the rest of the ecosystem--our users and > our upstreams, and I'd ask the release team to

NEW changes in stable-new

Processing changes file: monotone_1.1-4+deb8u2_armel.changes ACCEPT

NEW changes in stable-new

Processing changes file: monotone_1.1-4+deb8u2_armhf.changes ACCEPT

NEW changes in stable-new

Processing changes file: monotone_1.1-4+deb8u2_mips.changes ACCEPT

NEW changes in stable-new

Processing changes file: mdadm_3.3.2-5+deb8u2_armel.changes ACCEPT Processing changes file: monotone_1.1-4+deb8u2_mipsel.changes ACCEPT

Bug#843999: jessie-pu: package wot/20131118-2

Updated patch attached. diff --git a/debian/NEWS b/debian/NEWS new file mode 100644 index 000..dc8c4bc --- /dev/null +++ b/debian/NEWS @@ -0,0 +1,14 @@ +wot (20151208-3) jessie; urgency=high + + * WOT has been identified as malware or spyware. +At least since 2015-04, it passes all

Processed: jessie-pu: package wot/20131118-2

Processing commands for cont...@bugs.debian.org: > retitle 843999 jessie-pu: package wot/20131118-2 Bug #843999 [release.debian.org] jessie-pu: package wot/20151208-3 Changed Bug title to 'jessie-pu: package wot/20131118-2' from 'jessie-pu: package wot/20151208-3'. > thanks Stopping processing

NEW changes in stable-new

Processing changes file: mdadm_3.3.2-5+deb8u2_armhf.changes ACCEPT

NEW changes in stable-new

Processing changes file: monotone_1.1-4+deb8u2_arm64.changes ACCEPT Processing changes file: monotone_1.1-4+deb8u2_s390x.changes ACCEPT

NEW changes in stable-new

Processing changes file: monotone_1.1-4+deb8u2_i386.changes ACCEPT Processing changes file: monotone_1.1-4+deb8u2_powerpc.changes ACCEPT Processing changes file: monotone_1.1-4+deb8u2_ppc64el.changes ACCEPT

Bug#845443: jessie-pu: package nss-pam-ldapd/0.9.4-3+deb8u2

Hi, On Thu, Nov 24, 2016 at 07:59:26PM +0100, Julien Cristau wrote: > On Wed, Nov 23, 2016 at 14:19:24 +0100, Salvatore Bonaccorso wrote: > > > +nss-pam-ldapd (0.9.4-3+deb8u2) stable; urgency=medium > > + > > + * Non-maintainer upload. > > + * have init script stop action only return when

NEW changes in stable-new

Processing changes file: mdadm_3.3.2-5+deb8u2_amd64.changes ACCEPT Processing changes file: mdadm_3.3.2-5+deb8u2_i386.changes ACCEPT Processing changes file: mdadm_3.3.2-5+deb8u2_mips.changes ACCEPT Processing changes file: mdadm_3.3.2-5+deb8u2_mipsel.changes ACCEPT Processing changes

NEW changes in stable-new

Processing changes file: mdadm_3.3.2-5+deb8u2_arm64.changes ACCEPT

Re: Bug#844625: e2fsprogs: dumpe2fs segfaults in jessie

On Sat, Nov 19, 2016 at 10:12:36 -0500, Theodore Ts'o wrote: > On Sat, Nov 19, 2016 at 01:34:56PM +0100, Santiago Vila wrote: > > On Sat, Nov 19, 2016 at 07:14:39AM -0500, Theodore Ts'o wrote: > > > > > Why do you care? It's an extremely minor bug, and it's really not > > > worth the effort to

Bug#845443: jessie-pu: package nss-pam-ldapd/0.9.4-3+deb8u2

On Wed, 2016-11-23 at 14:19 +0100, Salvatore Bonaccorso wrote: > nss-pam-ldapd's nslcd under the conditions as described in #814881 > might fail to restart. nslcd restart which is stop+start with > systemd, is racy, and might lead to nslcd not running after a > restart. Ferenc has posted his

Bug#833865: jessie-pu: package youtube-dl/2014.08.05-1+deb8u1

On 2016-11-24 13:04:21, Julien Cristau wrote: > On Tue, Aug 9, 2016 at 11:50:27 -0400, Antoine Beaupré wrote: > >> This is a tentative of opening the discussion regarding a more regular >> update of the youtube-dl package in Debian stable. >> > TBH I think this should never have reached stable

Re: nspr transition to testing

On Sat, Nov 19, 2016 at 07:46:58 +0900, Mike Hommey wrote: > On Tue, Nov 15, 2016 at 07:24:00AM +, Niels Thykier wrote: > > Mike Hommey: > > > Hi, > > > > > > Why has nspr been a valid candidate for testing migration for several > > > weeks or months without it happening? > > > > > > Mike >

Bug#843999: jessie-pu: package wot/20131118-2

On Wed, Nov 23, 2016 at 23:28:18 +0100, W. Martin Borgert wrote: > On 2016-11-20 18:02, Jonathan Wiltshire wrote: > > In principle 'yes'; please prepare the diff and attach to this bug for > > review. > > Attached. > diff --git a/debian/NEWS b/debian/NEWS > new file mode 100644 > index

Re: dbgsym packages and stretch-as-stable

On Tue, Nov 8, 2016 at 00:18:21 +0100, Ansgar Burchardt wrote: > Hi, > > "Adam D. Barratt" writes: > > Apologies if I missed something in earlier discussions, but how are > > automagic debug packages and uploads to stable expected to interact? > > > > Will there need to be stable-new-dbgsym and

Processed: Re: Bug#845387: jessie-pu: package glibc/2.19-18+deb8u7

Processing control commands: > tag -1 confirmed Bug #845387 [release.debian.org] jessie-pu: package glibc/2.19-18+deb8u7 Added tag(s) confirmed. -- 845387: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#845387: jessie-pu: package glibc/2.19-18+deb8u7

Control: tag -1 confirmed On Wed, Nov 23, 2016 at 00:07:31 +0100, Aurelien Jarno wrote: > I would like to upload a new glibc package for the next jessie release. Thanks for the detailed explanation. Looks fine to me. Cheers, Julien

Bug#845443: jessie-pu: package nss-pam-ldapd/0.9.4-3+deb8u2

On Wed, Nov 23, 2016 at 14:19:24 +0100, Salvatore Bonaccorso wrote: > +nss-pam-ldapd (0.9.4-3+deb8u2) stable; urgency=medium > + > + * Non-maintainer upload. > + * have init script stop action only return when nslcd has actually stopped > +(Closes: #814881) > + > + -- Salvatore Bonaccorso

NEW changes in stable-new

Processing changes file: isenkram_0.18+deb8u1_amd64.changes ACCEPT Processing changes file: mdadm_3.3.2-5+deb8u2_source.changes ACCEPT Processing changes file: monotone_1.1-4+deb8u2_amd64.changes ACCEPT

Bug#845570: jessie-pu: package libdatetime-timezone-perl/1:1.75-2+2016j

On Thu, 24 Nov 2016 18:48:04 +, Adam D. Barratt wrote: > On Thu, 2016-11-24 at 19:31 +0100, gregor herrmann wrote: > > I've prepared an update of libdatetime-timezone-perl for jessie. > > The new version (manually stripped down debdiff attached) contains > > the update to the Olson DB 2016j,

Processed: Re: Bug#845570: jessie-pu: package libdatetime-timezone-perl/1:1.75-2+2016j

Processing control commands: > tags -1 + confirmed Bug #845570 [release.debian.org] jessie-pu: package libdatetime-timezone-perl/1:1.75-2+2016j Added tag(s) confirmed. -- 845570: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845570 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#845570: jessie-pu: package libdatetime-timezone-perl/1:1.75-2+2016j

Control: tags -1 + confirmed On Thu, 2016-11-24 at 19:31 +0100, gregor herrmann wrote: > I've prepared an update of libdatetime-timezone-perl for jessie. > The new version (manually stripped down debdiff attached) contains > the update to the Olson DB 2016j, as a quilt patch which only changes >

Processed: Re: Bug#843775: jessie-pu: package mdadm/3.3.2-5+deb8u2

Processing control commands: > tags 843775 + pending Bug #843775 [release.debian.org] jessie-pu: package mdadm/3.3.2-5+deb8u2 Ignoring request to alter tags of bug #843775 to the same tags previously set -- 843775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843775 845311:

Bug#845156: jessie-pu: package monotone/1.1-4+deb8u2

Control: tags -1 + pending On Tue, 2016-11-22 at 09:50 +0100, Markus Wanner wrote: > On 11/21/2016 06:42 PM, Adam D. Barratt wrote: > > +monotone (1.1-4+deb8u2) jessie-security; urgency=high > > > > With the distribution updated to "jessie", please go ahead. > > Thanks. With that change, I

Processed: Re: Bug#845156: jessie-pu: package monotone/1.1-4+deb8u2

Processing control commands: > tags -1 + pending Bug #845156 [release.debian.org] jessie-pu: package monotone/1.1-4+deb8u2 Added tag(s) pending. -- 845156: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#840942: jessie-pu: package isenkram/0.18+deb8u1

Processing control commands: > tags -1 + pending Bug #840942 [release.debian.org] jessie-pu: package isenkram/0.18+deb8u1 Added tag(s) pending. -- 840942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840942 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#843775: jessie-pu: package mdadm/3.3.2-5+deb8u2

Control: tags 843775 + pending On Tue, 2016-11-22 at 12:43 +0100, Cyril Brulebois wrote: > (dropping debian-boot@, adding 845311@) > > Hi Jens, > > Jens Sauer (2016-11-22): > > Thank you for reviewing this package. It was my first time doing this, > > I hope everything is

Bug#840942: jessie-pu: package isenkram/0.18+deb8u1

Control: tags -1 + pending On Tue, 2016-11-22 at 12:58 +, Adam D. Barratt wrote: > On 2016-11-22 12:45, Petter Reinholdtsen wrote: > > [Adam D. Barratt] > >> Yes, please. I've flagged the current upload for rejection. Once you > >> receive the confirmation from dak that the rejection has been

Processed: Re: Bug#843775: jessie-pu: package mdadm/3.3.2-5+deb8u2

Processing control commands: > tags 843775 + pending Bug #843775 [release.debian.org] jessie-pu: package mdadm/3.3.2-5+deb8u2 Added tag(s) pending. -- 843775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#842929: jessie-pu: package modsecurity-crs/2.2.9-1

On Thu, Nov 10, 2016 at 16:54:41 +0100, Alberto Gonzalez Iniesta wrote: > On Thu, Nov 10, 2016 at 03:38:12PM +, Adam D. Barratt wrote: > > > > On Wed, 2016-11-02 at 12:51 +0100, Alberto Gonzalez Iniesta wrote: > > > I was asked to update modsecurity-crs in Jessie in order to fix #838009. > >

Bug#842929: jessie-pu: package modsecurity-crs/2.2.9-1

On Thu, Nov 17, 2016 at 11:30:22 +0100, Alberto Gonzalez Iniesta wrote: > On Thu, Nov 10, 2016 at 03:38:12PM +, Adam D. Barratt wrote: > > Control: tags -1 + moreinfo > > > > On Wed, 2016-11-02 at 12:51 +0100, Alberto Gonzalez Iniesta wrote: > > > I was asked to update modsecurity-crs in

Bug#845570: jessie-pu: package libdatetime-timezone-perl/1:1.75-2+2016j

Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I've prepared an update of libdatetime-timezone-perl for jessie. The new version (manually stripped down debdiff attached) contains

Bug#833865: jessie-pu: package youtube-dl/2014.08.05-1+deb8u1

On Tue, Aug 9, 2016 at 11:50:27 -0400, Antoine Beaupré wrote: > This is a tentative of opening the discussion regarding a more regular > update of the youtube-dl package in Debian stable. > TBH I think this should never have reached stable in the first place... Cheers, Julien

Bug#845304: transition: libxtables12

On Tue, Nov 22, 2016 at 10:39:13 +0100, Emilio Pozuelo Monfort wrote: > On 22/11/16 10:29, Simon McVittie wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: transition > > X-Debbugs-Cc: iptab...@packages.debian.org > >

Bug#845564: jessie-pu: package lxc/1:1.0.6-6+deb8u5

Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Ohai, even if lxc/1:1.0.6-6+deb8u4 did not reach stable yet (see #844150), we would like to fix another bug in stable: #845465 aka CVE-2016-8649: attach: do not send procfd to

Re: Bug#845348: What is going on with gtkdatabox?

On 2016-11-24 08:24, Andreas Tille wrote: I'll checkout gtkdataboxmm myself since I was once sponsering this - no idea whether Daniele remains active on this package. I haven't used gtkdataboxmm for a long time now, and I'm no longer developing it upstream. I think that, unless someone wants

Re: What is going on with gtkdatabox?

On 24/11/16 09:04, Andreas Tille wrote: The other problem is that libgtkdatabox-0.9.2-0-dev should not be any more in the pool at all and I have no idea why this is the case. Binary packages that are no longer built by a source package are not removed instantly, they will be cleaned up by

Bug#845263: jessie-pu: package w3m/0.5.3-19+deb8u1

s://security-tracker.debian.org/tracker/source-package/w3m http://www.openwall.com/lists/oss-security/2016/11/24/1 See this changelog and the attached diffs. (w3m-20161122-20161124.diff is diff against the previous one, w3m-20161124.debdiff is full debdiff) w3m (0.5.3-19+deb8u1) jessie; urgency=medium

Processed: gridengine: staying with libssl1.0

Processing control commands: > severity -1 important Bug #828329 [src:gridengine] gridengine: FTBFS with openssl 1.1.0 Bug #827076 [src:gridengine] src:gridengine: FTBFS with openssl 1.1.0 Severity set to 'important' from 'serious' Severity set to 'important' from 'serious' > unblock 827061 by -1

Re: What is going on with gtkdatabox?

On 2016-11-24 9:04, Andreas Tille wrote: The other problem is that libgtkdatabox-0.9.2-0-dev should not be any more in the pool at all and I have no idea why this is the case. As with almost every other transition, it's still in the archive because other packages in the archive still

Re: What is going on with gtkdatabox?

Hi Adrian, On Thu, Nov 24, 2016 at 10:27:18AM +0200, Adrian Bunk wrote: > > > > I'm now realising that the first option has installable candidates which > > is astonishing since I assumed that with a new source package upload the > > binaries created by the previous version would vanish from the

Re: What is going on with gtkdatabox?

On Thu, Nov 24, 2016 at 08:40:43AM +0100, Andreas Tille wrote: > Hi again, > > On Thu, Nov 24, 2016 at 02:49:56AM +, peter green wrote: > > > > brp-pacu: has a build-dependency on libgtkdatabox-0.9.2-0-dev | > > libgtkdatabox-dev . Unfortunately buildds only look at the first option > > I'm

Processed: Re: Bug#828312 closed by Andrew Ayer <a...@andrewayer.name> (Bug#828312: fixed in git-crypt 0.5.0-2)

Processing control commands: > reopen -1 Bug #828312 {Done: Andrew Ayer } [src:git-crypt] git-crypt: FTBFS with openssl 1.1.0 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug