Bug#840127: jessie-pu: package libio-socket-ssl-perl/2.002-2+deb8u2

[Salvatore Bonaccorso]

Hi Adam,

On Sat, Oct 08, 2016 at 09:10:33PM +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Sat, 2016-10-08 at 17:37 +0200, Salvatore Bonaccorso wrote:
> > We were asked if #839576 can be fixed in stable as well, it is already
> > addressed in unstable back with the 2.017-1 upload, which caused
> > problems for the user with ACL's set on the SSL_key_file.
> > 
> > Attached is the proposed debdiff. Would it be acceptable for an
> > upcoming jessie point release?
> 
> Please go ahead.

Thanks! Uploaded.

Regards,
Salvatore


signature.asc
Description: PGP signature

Bug#839814: jessie-pu: package sympa/6.1.23~dfsg-2+deb8u1

[Salvatore Bonaccorso]

Hi Adam,

On Sat, Oct 08, 2016 at 09:18:50PM +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Wed, 2016-10-05 at 12:56 +0200, Salvatore Bonaccorso wrote:
> > Sympa is affected by a nasty bug when used under systemd, that after
> > logrotation with the original logrotate setup in jessie, sympa is in a
> > confused state. This is tracked as #804066 and was fixed in unstable
> > already with 6.2.16~dfsg-1.
> > 
> > I would like to propose that this is fixed as well for stable,
> > attached is the proposed debidff, where I needed to use
> > reload-or-try-reload (try-reload-or-restart in unstable).
> > 
> > Does this look acceptable for the upcoming jessie point release?
> 
> Please go ahead.

Thanks a lot, just uploaded.

> I realise it's not part of the modified section of the file, but this:
> 
> invoke-rc.d --quiet rsyslog rotate > /dev/null || true
> 
> does look a little odd.

Yes you are right. I checked, and this seems still the case as well
for the unstable version.

Regards,
Salvatore


signature.asc
Description: PGP signature

Bug#836795: jessie-pu: package samba/2:4.1.17+dfsg-2+deb8u2

[Jelmer Vernooij]

On Sat, Sep 24, 2016 at 08:14:38PM +0100, Adam D. Barratt wrote:
> Control: tags -1 -moreinfo +confirmed
> 
> On Mon, 2016-09-05 at 20:50 +, Jelmer Vernooij wrote:
> > I'd like to update Samba in jessie to 4.2.14+dfsg. Debdiff is attached.
> > 
> > The 4 Samba releases since 4.2.10 (currently in jessie) only fix
> > important bugs, in particular a CVE (CVE-2016-2119) and various
> > regressions introduced by the security fixes from 4.2.10.
> 
> Please go ahead, with the changelog distribution set to "jessie".
> 
> I'll hopefully be able to find a suitable machine on my work network to
> test with, and I assume at least Lars Maes would also be happy to test.

Can I also upload a new minor version of tevent that's required by
this version of Samba?


signature.asc
Description: PGP signature

Re: Stretch freeze and the possible future upload of MATE 1.18

[Mike Gabriel]

Hi Vlad,

thanks for taking this initiative of communication. Much appreciated.

I try to give some answers, Niels may jump in and correct me, if necessary.

On  Fr 07 Okt 2016 14:51:47 CEST, Vlad Orlov wrote:


Hi,


It depends on what the MATE release includes. If it involves a
transition (e.g. ABI / API bumps), then you are looking at 5th of
November as deadline.


Hmm... does it mean changes in soname of some library from MATE
that will cause package name change? E.g. libmate-desktop-2.so ->
libmate-desktop-3.so, then package libmate-desktop-2-17 would have
its name changed too.


Yes. And all packages build-depending on libmate-desktop-dev would  
require to be rebuilt.


In MATE this is non-criticial as long as only MATE packages B-D on  
libmate-desktop-dev. But if there is any package outside of the Debian  
MATE team's scope, then this gets nasty so close to the freeze.



Or does something else count as transition? E.g. if some of MATE
packages would change dependency from libmateweather to libgweather.


No. This should be fine.


Otherwise, I strongly recommend using early/mid-December as the latest
deadline upstream.  That way the MATE packaging has 2-3 weeks to get it
uploaded plus another 2-3 to fix any bugs without any extra hassle.  I
assume here that there is no need for new packages (based on your input
below).


Yes, there's no plan to add new packages into MATE.


Ok. Good.


So December means we need to meet soft freeze date (2017-01-05)?
That is, if we already handled the transitions.


By this date, packages have to be landed in testing. So, they have to  
be uploaded to unstable "a couple of days" earlier. With the last  
freeze for jessie, there was 10 days delay for the migration of  
packages from unstable to testing. IIRC.



Are new upstream versions allowed into Testing between soft freeze
and full freeze (provided that these are only new versions, not new
packages)?


IIRC, this was possible with review by someone from the release team.  
As the MATE upstream team is really careful and minimal with the  
changes in point release, I'd say all potential upstream releases of  
MATE within one release series (i.e. within 1.16 or 1.18) would be  
good candidates for receiving permission to be uploaded.



Please remember to coordinate with the MATE packaging team so they have
time to upload it to unstable and let it migrate.


Yes, sure. I just wanted to gather all the necessary info first,
mostly to understand it myself. :)


Personally, I'd prefer to start consolidating MATE 1.16 now and I  
would love to see it long term supported by upstream. I know that some  
MATE packages will face some major changes for 1.18 (e.g. Caja being  
ported to GtkApplication class). For Debian stretch, would it be an  
option (asking upstream here) to only include some MATE packages from  
1.18 and leave the rest at 1.16? Or another approach, would it make  
sense to have 1.16 micro releases with bigger patchsets than usual?


light+love
Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpQdqvXcGPbr.pgp
Description: Digitale PGP-Signatur

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: asused_3.72-11+deb8u1_amd64.changes
  ACCEPT
Processing changes file: icedove_45.3.0-1~deb8u1_amd64.changes
  ACCEPT
Processing changes file: icedove_45.3.0-1~deb8u1_arm64.changes
  ACCEPT
Processing changes file: icedove_45.3.0-1~deb8u1_armel.changes
  ACCEPT
Processing changes file: icedove_45.3.0-1~deb8u1_armhf.changes
  ACCEPT
Processing changes file: icedove_45.3.0-1~deb8u1_i386.changes
  ACCEPT
Processing changes file: icedove_45.3.0-1~deb8u1_mips.changes
  ACCEPT
Processing changes file: icedove_45.3.0-1~deb8u1_mipsel.changes
  ACCEPT
Processing changes file: icedove_45.3.0-1~deb8u1_powerpc.changes
  ACCEPT
Processing changes file: icedove_45.3.0-1~deb8u1_ppc64el.changes
  ACCEPT
Processing changes file: icedove_45.3.0-1~deb8u1_s390x.changes
  ACCEPT
Processing changes file: libav_11.8-1~deb8u1_amd64.changes
  ACCEPT
Processing changes file: libav_11.8-1~deb8u1_arm64.changes
  ACCEPT
Processing changes file: libav_11.8-1~deb8u1_armel.changes
  ACCEPT
Processing changes file: libav_11.8-1~deb8u1_armhf.changes
  ACCEPT
Processing changes file: libav_11.8-1~deb8u1_i386.changes
  ACCEPT
Processing changes file: libav_11.8-1~deb8u1_mips.changes
  ACCEPT
Processing changes file: libav_11.8-1~deb8u1_mipsel.changes
  ACCEPT
Processing changes file: libav_11.8-1~deb8u1_powerpc.changes
  ACCEPT
Processing changes file: libav_11.8-1~deb8u1_ppc64el.changes
  ACCEPT
Processing changes file: libav_11.8-1~deb8u1_s390x.changes
  ACCEPT
Processing changes file: libdbd-mysql-perl_4.028-2+deb8u2_amd64.changes
  ACCEPT
Processing changes file: libdbd-mysql-perl_4.028-2+deb8u2_arm64.changes
  ACCEPT
Processing changes file: libdbd-mysql-perl_4.028-2+deb8u2_armel.changes
  ACCEPT
Processing changes file: libdbd-mysql-perl_4.028-2+deb8u2_armhf.changes
  ACCEPT
Processing changes file: libdbd-mysql-perl_4.028-2+deb8u2_i386.changes
  ACCEPT
Processing changes file: libdbd-mysql-perl_4.028-2+deb8u2_mips.changes
  ACCEPT
Processing changes file: libdbd-mysql-perl_4.028-2+deb8u2_mipsel.changes
  ACCEPT
Processing changes file: libdbd-mysql-perl_4.028-2+deb8u2_powerpc.changes
  ACCEPT
Processing changes file: libdbd-mysql-perl_4.028-2+deb8u2_ppc64el.changes
  ACCEPT
Processing changes file: libdbd-mysql-perl_4.028-2+deb8u2_s390x.changes
  ACCEPT
Processing changes file: nspr_4.12-1+debu8u1_amd64.changes
  ACCEPT
Processing changes file: nspr_4.12-1+debu8u1_arm64.changes
  ACCEPT
Processing changes file: nspr_4.12-1+debu8u1_armel.changes
  ACCEPT
Processing changes file: nspr_4.12-1+debu8u1_armhf.changes
  ACCEPT
Processing changes file: nspr_4.12-1+debu8u1_i386.changes
  ACCEPT
Processing changes file: nspr_4.12-1+debu8u1_mips.changes
  ACCEPT
Processing changes file: nspr_4.12-1+debu8u1_mipsel.changes
  ACCEPT
Processing changes file: nspr_4.12-1+debu8u1_powerpc.changes
  ACCEPT
Processing changes file: nspr_4.12-1+debu8u1_ppc64el.changes
  ACCEPT
Processing changes file: nspr_4.12-1+debu8u1_s390x.changes
  ACCEPT

Processed: Re: Bug#839731: jessie-pu: package mpg123/1.20.1-2+deb8u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #839731 [release.debian.org] jessie-pu: package mpg123/1.20.1-2+deb8u1
Added tag(s) confirmed.

-- 
839731: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#839731: jessie-pu: package mpg123/1.20.1-2+deb8u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Tue, 2016-10-04 at 12:01 +0100, James Cowgill wrote:
> A security issue was reported against mpg123 in bug #838960. Since it
> was marked no-DSA by the security team, it needs a normal jessie-pu
> update to fix it in jessie.
> 
> The debdiff is attached. I've tested it on jessie against the testcase
> provided in the upstream bug report (https://mpg123.org/bugs/240).

Please go ahead.

Regards,

Adam

Bug#839814: jessie-pu: package sympa/6.1.23~dfsg-2+deb8u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Wed, 2016-10-05 at 12:56 +0200, Salvatore Bonaccorso wrote:
> Sympa is affected by a nasty bug when used under systemd, that after
> logrotation with the original logrotate setup in jessie, sympa is in a
> confused state. This is tracked as #804066 and was fixed in unstable
> already with 6.2.16~dfsg-1.
> 
> I would like to propose that this is fixed as well for stable,
> attached is the proposed debidff, where I needed to use
> reload-or-try-reload (try-reload-or-restart in unstable).
> 
> Does this look acceptable for the upcoming jessie point release?

Please go ahead.

I realise it's not part of the modified section of the file, but this:

invoke-rc.d --quiet rsyslog rotate > /dev/null || true

does look a little odd.

Regards,

Adam

Processed: Re: Bug#839814: jessie-pu: package sympa/6.1.23~dfsg-2+deb8u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #839814 [release.debian.org] jessie-pu: package sympa/6.1.23~dfsg-2+deb8u1
Added tag(s) confirmed.

-- 
839814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#840127: jessie-pu: package libio-socket-ssl-perl/2.002-2+deb8u2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #840127 [release.debian.org] jessie-pu: package 
libio-socket-ssl-perl/2.002-2+deb8u2
Added tag(s) confirmed.

-- 
840127: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840127
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#839927: jessie-pu: package rawtherapee/4.2-1+deb8u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #839927 [release.debian.org] jessie-pu: package rawtherapee/4.2-1+deb8u1
Added tag(s) confirmed.

-- 
839927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#840127: jessie-pu: package libio-socket-ssl-perl/2.002-2+deb8u2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sat, 2016-10-08 at 17:37 +0200, Salvatore Bonaccorso wrote:
> We were asked if #839576 can be fixed in stable as well, it is already
> addressed in unstable back with the 2.017-1 upload, which caused
> problems for the user with ACL's set on the SSL_key_file.
> 
> Attached is the proposed debdiff. Would it be acceptable for an
> upcoming jessie point release?

Please go ahead.

Regards,

Adam

Bug#839927: jessie-pu: package rawtherapee/4.2-1+deb8u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Fri, 2016-10-07 at 00:26 +0200, Philip Rinn wrote:
> Sorry, I didn't attach the debdiff, it was only a 'git diff ...' Now I 
> attached
> the real debdiff.

Please go ahead.

Regards,

Adam

Processed: Re: Bug#839531: jessie-pu: package asused/3.72-11

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #839531 [release.debian.org] jessie-pu: package asused/3.72-11
Added tag(s) pending.

-- 
839531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#839531: jessie-pu: package asused/3.72-11

[Adam D. Barratt]

Control: tags -1 + pending

On Sun, 2016-10-02 at 12:25 +0100, Adam D. Barratt wrote:
> Control: tags -1 -moreinfo +confirmed
> 
> On Sun, 2016-10-02 at 02:05 +0200, Sebastien Badia wrote:
> > Pff really sorry for the waste time… I was too fast on this one…
> 
> No problem.
> 
> > Just fixed the version number, and re-builded/uploaded to mentors.d.n
> > https://mentors.debian.net/debian/pool/main/a/asused/asused_3.72-11+deb8u1.dsc
> > (build and tested in a clean env on Debian jessie).
> > 
> > The debdiff against 3.72-11 version in jessie is now attached.
> 
> Thanks; please feel free to upload that (or get it uploaded via a
> sponsor, if needed).

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#839869: transition: poppler 0.48.0

[Pino Toscano]

In data giovedì 6 ottobre 2016 10:25:57 CEST, Rene Engelhard ha scritto:
> Hi,
> 
> On Wed, Oct 05, 2016 at 10:13:14PM +0200, Pino Toscano wrote:
> > This transition impacts the existing poppler libraries in the following 
> > ways:
> > - libpoppler61 → libpoppler64
> [...]
> >   boomaga
> >   calligra
> >   cups-filters
> >   emacs-pdf-tools
> >   gambas3
> >   gdal
> >   gdcm
> >   inkscape
> >   ipe-tools
> >   pdf2djvu
> >   pdf2htmlex
> >   popplerkit.framework
> >   texlive-bin
> >   texworks
> >   xpdf
> 
> I believe there's stuff missing there for whatever reason. E.g. libreoffice
> (via libreoffice-pdfimport, 
> https://packages.debian.org/sid/libreoffice-pdfimport).
> 
> Was in your last transition bugs afaicr, so I wonder what went wrong this 
> time ;)

Oh right, sorry, it was indeed missing.  In the above list there is also:

  libreoffice
  openscenegraph
  openscenegraph-3.4

Thanks,
-- 
Pino Toscano

signature.asc
Description: This is a digitally signed message part.

Bug#840127: jessie-pu: package libio-socket-ssl-perl/2.002-2+deb8u2

[Salvatore Bonaccorso]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

Hi Stable Release Managers,

We were asked if #839576 can be fixed in stable as well, it is already
addressed in unstable back with the 2.017-1 upload, which caused
problems for the user with ACL's set on the SSL_key_file.

Attached is the proposed debdiff. Would it be acceptable for an
upcoming jessie point release?

Regards,
Salvatore
diff -Nru libio-socket-ssl-perl-2.002/debian/changelog libio-socket-ssl-perl-2.002/debian/changelog
--- libio-socket-ssl-perl-2.002/debian/changelog	2015-06-20 22:10:17.0 +0200
+++ libio-socket-ssl-perl-2.002/debian/changelog	2016-10-08 17:26:51.0 +0200
@@ -1,3 +1,13 @@
+libio-socket-ssl-perl (2.002-2+deb8u2) jessie; urgency=medium
+
+  * Add 0001-remove-r-for-checking-SSL_-cert-key-_file-since-this.patch.
+Removes the -r check for for checking SSL_{cert,key}_file since this
+will an usable error later anyway. Addresses "Cannot use SSL_key_file
+with ACL permissions".
+Thanks to Michael Braun and Steffen Ullrich. (Closes: #839576)
+
+ -- Salvatore Bonaccorso   Sat, 08 Oct 2016 17:26:51 +0200
+
 libio-socket-ssl-perl (2.002-2+deb8u1) jessie; urgency=medium
 
   * Add 0001-make-PublicSuffix-_default_data-thread-safe-by-stori.patch.
diff -Nru libio-socket-ssl-perl-2.002/debian/patches/0001-remove-r-for-checking-SSL_-cert-key-_file-since-this.patch libio-socket-ssl-perl-2.002/debian/patches/0001-remove-r-for-checking-SSL_-cert-key-_file-since-this.patch
--- libio-socket-ssl-perl-2.002/debian/patches/0001-remove-r-for-checking-SSL_-cert-key-_file-since-this.patch	1970-01-01 01:00:00.0 +0100
+++ libio-socket-ssl-perl-2.002/debian/patches/0001-remove-r-for-checking-SSL_-cert-key-_file-since-this.patch	2016-10-08 17:26:51.0 +0200
@@ -0,0 +1,26 @@
+From 7432b34d5bf6f63f4b422e2fc411ee3fc7750c9e Mon Sep 17 00:00:00 2001
+From: Steffen Ullrich 
+Date: Sun, 23 Aug 2015 21:17:06 +0200
+Subject: [PATCH] remove -r for checking SSL_{cert,key}_file since this will
+ cause a usable error later anywy if file does not exist. This fixes some part
+ of #106295
+
+---
+ lib/IO/Socket/SSL.pm | 1 -
+ 1 file changed, 1 deletion(-)
+
+diff --git a/lib/IO/Socket/SSL.pm b/lib/IO/Socket/SSL.pm
+index b000a6b..4fea291 100644
+--- a/lib/IO/Socket/SSL.pm
 b/lib/IO/Socket/SSL.pm
+@@ -2082,7 +2082,6 @@ sub new {
+ 	 defined( my $file = $arg_hash->{$_} ) or next;
+ 	for my $f (ref($file) eq 'HASH' ? values(%$file):$file ) {
+ 	die "$_ $f does not exist" if ! -f $f;
+-	die "$_ $f is not accessible" if ! -r _;
+ 	}
+ }
+ 
+-- 
+2.9.3
+
diff -Nru libio-socket-ssl-perl-2.002/debian/patches/series libio-socket-ssl-perl-2.002/debian/patches/series
--- libio-socket-ssl-perl-2.002/debian/patches/series	2015-06-20 22:10:17.0 +0200
+++ libio-socket-ssl-perl-2.002/debian/patches/series	2016-10-08 17:26:51.0 +0200
@@ -1,2 +1,3 @@
 0001-use-only-ICANN-part-in-public-suffix-list.patch
 0001-make-PublicSuffix-_default_data-thread-safe-by-stori.patch
+0001-remove-r-for-checking-SSL_-cert-key-_file-since-this.patch

Re: Architecture qualification meeting, scheduling

[Niels Thykier]

Adrian Bunk:
> [ fullquote adding -ports, for people not following -release or -devel ]
> 
> [...]
> 
> Is https://release.debian.org/stretch/arch_qualify.html the up-to-date 
> information available to you, and the "candidate" line how a decision
> would look like based on the current information?
> 
> cu
> Adrian
> 

It reflects all the issues we are aware of at the present time (except
for archive-{coverage,uptodate}, which can be seen from
https://buildd.debian.org/stats/).

If you believe we have overlooked an issue or an update, please do not
hesitate to let us know. :)

Thanks,
~Niels

Bug#839916: marked as done (nmu: bmusb_0.5.2-2)

[Debian Bug Tracking System]

Your message dated Sat, 8 Oct 2016 12:51:06 +0200
with message-id 
and subject line Re: Bug#839916: nmu: bmusb_0.5.2-2
has caused the Debian Bug report #839916,
regarding nmu: bmusb_0.5.2-2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
839916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

nmu bmusb_0.5.2-2 . amd64 . unstable . -m "Rebuild in a clean sid environment."

Maintainer uploaded binaries were built against libusb from
experimental.


Andreas
--- End Message ---
--- Begin Message ---
On 06/10/16 12:14, Andreas Beckmann wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> nmu bmusb_0.5.2-2 . amd64 . unstable . -m "Rebuild in a clean sid 
> environment."
> 
> Maintainer uploaded binaries were built against libusb from
> experimental.

Scheduled.

Emilio--- End Message ---

Bug#838242: transition: imagemagick

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 07/10/16 17:15, roucaries bastien wrote:
> I have tried and it seems so.
> 
> Due to perl transition I get some transient problem but it seems ok,
> except package only available under unstable

Alright. This is small enough that should be fine in any case.

You can go ahead.

I wonder why you called the new package libmagick++-6.q16-6v6 rather than just
libmagick++-6.q16-6. That seems like a mistake, though I guess just leave it
like that now, no need to go through NEW and add conflicts/replaces etc just for
a cosmetic change.

Cheers,
Emilio

Processed: Re: Bug#838242: transition: imagemagick

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #838242 [release.debian.org] transition: imagemagick
Added tag(s) confirmed.

-- 
838242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#834955: transition: x265

[Emilio Pozuelo Monfort]

On 07/10/16 23:04, Andreas Beckmann wrote:
> That needs a binNMU in experimental, too:
> 
> nmu gst-plugins-bad1.0_1.9.90-1 . ANY . experimental . -m "Rebuild against 
> libx265-95."

Scheduled.

Emilio

Re: Architecture qualification meeting, scheduling

[Adrian Bunk]

[ fullquote adding -ports, for people not following -release or -devel ]

On Fri, Oct 07, 2016 at 06:35:07PM +0100, Jonathan Wiltshire wrote:
> Hi,
> 
> I am arranging the final architecture qualification meeting for Stretch.
> This is primarily of interest to the release team, but I will also take
> input from porters.
> 
> As the schedule is currently wide open, please express your availability in
> the linked Doodle poll. There are 56 slots available, mostly in the European
> evening but a handful are daytime coinciding with the Cambridge
> mini-Debconf.
> 
> Porters, please note your architecture in your response ("name (arch)").
> 
> About the format of the meeting:
> Much like the Jessie meeting, it will be held via IRC in
> oftc.net/#debian-release and will be primarily a discussion amongst the
> release team. We will evaluate each port on the most up-to-date information
> available to us, and determine if it will be a release architecture for
> Stretch. We may ask for clarification from porters who are present if there
> are points at issue, but we ask that you are read-only otherwise.
> 
> http://doodle.com/poll/362qvb89cvu43d4z

Is https://release.debian.org/stretch/arch_qualify.html the up-to-date 
information available to you, and the "candidate" line how a decision
would look like based on the current information?

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Re: Bug#833574: monotone: FTBFS on powerpc (test suite failure)

[Adam D. Barratt]

On Sat, 2016-10-08 at 00:29 +0300, Adrian Bunk wrote:
> I would suggest to upload 1.1-4+deb8u2 (created on top of 1.1-4+deb8u1) 
> with 51-sigpipe-test.diff added to jessie, but Julien (or any other SRM) 
> should confirm that.

Please open a p-u bug with the proposed fix (as a source debdiff)
attached to discuss that; random mails to debian-release@ are awkward to
track and tend to get lost.

Regards,

Adam

Re: jessie-ignore for "maintainer address bounces" bugs?

[Andreas Beckmann]

On 2016-09-10 10:37, Andreas Beckmann wrote:
> Hi,
> 
> would it be OK to tag "maintainer address bounces" bugs as jessie-ignore?

This would affect about 10 bugs in jessie and a few less in wheezy.


Andreas