Processed: Re: Bug#867231: stretch-pu: package openstack-debian-images/1.19

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #867231 [release.debian.org] stretch-pu: package 
openstack-debian-images/1.19
Added tag(s) confirmed.

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

Bug#867231: stretch-pu: package openstack-debian-images/1.19

[Adam D. Barratt]

Control: tags -1 + confirmed

On Wed, 2017-07-05 at 10:41 +0200, Thomas Goirand wrote:
> On 07/05/2017 07:42 AM, Cyril Brulebois wrote:
> >> As usual, please provide a debdiff of the proposed source package,
> >> built and tested on stable, so that it can be confirmed.
> > 
> > Yeah, following the usual procedure, that has existed for years, *will*
> > save everyone time. Please do that.
> 
> Sorry for this, my bad. Debdiff attached for version 1.20~deb9u1 built
> on a stretch sbuild chroot. The built package is available here:
> 
> http://sid.gplhost.com/stretch-proposed-updates/openstack-debian-images/

Thanks.

+openstack-debian-images (1.20~deb9u1) stretch-proposed-updates; urgency=medium

Simply "stretch" is generally preferred there.

Please go ahead, bearing in mind that the upload window for 9.1 closes
over this weekend.

Regards,

Adam

Bug#864650: transition: mumps

[Drew Parsons]

On Tue, 2017-06-27 at 18:51 +0100, Jonathan Wiltshire wrote:
> On Mon, Jun 26, 2017 at 09:10:17PM +0800, Drew Parsons wrote:
> > 
> > That's right.  But it makes it simpler for stable users to just
> > grab
> > dolfin 2016.2.0-4 from snapshot archives if it hasn't been built
> > against new libraries like mumps 5.1.  Minimises the number of
> > codependent packages they'd have to pull in.
> 
> In that case, please come back when you're ready to proceed, in case
> there
> is by then a collision with another transition.

I'm happy with the state of dolfin in testing now.  I'd like to proceed
with the MUMPS 5.1 transition now.

Since petsc and slepc will be rebuilt as part of the mumps transition
anyway, I'll also upgrade petsc 3.7.6 and slepc 3.7.4. These are not a
true transition since their soname does not change.

Drew

Bug#868102: stretch-pu: package devscripts/2.17.6+deb9u1

[James McCoy]

On Thu, Jul 13, 2017 at 10:09:46AM +0100, Adam D. Barratt wrote:
> On 2017-07-12 3:27, James McCoy wrote:
> > * debchange:
> >   + Target stretch-backports with --bpo.  Closes: #867662
> >   + Support $codename{,-{proposed-updates,security}} as well.
> 
> I think there's a bug (or two?) that could be closed there?

Indeed.  Add the bug reference to the changelog.

> > * bts:
> >   + Add support for the new 'a11y' tag.  Closes: #867416
> 
> Please go ahead.

Done.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#867190: stretch-pu: package apt/1.4.7

[Julian Andres Klode]

On Thu, Jul 13, 2017 at 09:00:06PM +0100, Adam D. Barratt wrote:
> Control: tags -1 -moreinfo +confirmed
> 
> On Sun, 2017-07-09 at 17:08 +0200, Julian Andres Klode wrote:
> > The first one by David, the second by me, so this would end up
> > something like the following (order may be different, it's auto-generated
> > from git commits):
> > 
> > apt (1.4.7) stretch; urgency=medium
> > 
> >   [ Robert Luberda ]
> >   * fix a "critical" typo in old changelog entry (Closes: 866358)
> > 
> >   [ David Kalnischkies ]
> >   * use port from SRV record instead of initial port
> >   * travis: ignore profiling warning in progress lines  
> >
> > 
> >   [ Julian Andres Klode ]
> >   * Reset failure reason when connection was successful
> 
> maybe "... ensuring errors are correctly reported" or something similar?
> 
> >   * debian/gbp.conf: Set debian-branch to 1.4.y
> >   * http: Do not try reading content if Content-Length is 0
> >   * travis: Migrate to Docker
> >   * Release 1.4.7 (LP: #1702326)
> 
> Having the release item at the end looks slightly odd, imho. :-)
> 
> Please feel free to upload something like the above (bearing in mind
> that the window for 9.1 closes this weekend).

Uploaded with:

 apt (1.4.7) stretch; urgency=medium
 .
   * New release with important fixes up to 1.5~beta1; also see LP: #1702326
 .
   [ Robert Luberda ]
   * fix a "critical" typo in old changelog entry (Closes: 866358)
 .
   [ David Kalnischkies ]
   * test suite/travis CI: ignore profiling warning in progress lines
   * use port from SRV record instead of initial port
 .
   [ Julian Andres Klode ]
   * Reset failure reason when connection was successful, so later errors are
 reported as such and not as "connection failure" warnings.
   * debian/gbp.conf: Set debian-branch to 1.4.y
   * http: A response with Content-Length: 0 has no content, so don't try to
 read it - it will either timeout or the server closes the connection.
   * travis CI: Migrate to Docker



-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
  |  Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline').  Thank you.

Bug#867989: stretch-pu: package intel-microcode/3.20170707.1~deb9u1

[Henrique de Moraes Holschuh]

On Thu, 13 Jul 2017, Adam D. Barratt wrote:
> Please go ahead.

Uploaded, thank you very much!

-- 
  Henrique Holschuh

Bug#863682: superseeding with new version

[Henrique de Moraes Holschuh]

On Thu, 13 Jul 2017, Adam D. Barratt wrote:
> > Intel released the fixes for Kaby Lake as well, so I am updating this
> > s-p-u bug for the newer version of the intel-microcode package.
> 
> Please go ahead.

I've just uploaded it.  Thank you very much!

-- 
  Henrique Holschuh

Processed: Re: Bug#863682: superseeding with new version

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #863682 [release.debian.org] jessie-pu: package 
intel-microcode/3.20170707.1~deb8u1
Added tag(s) confirmed.

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

Bug#863682: superseeding with new version

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2017-07-10 at 18:19 -0300, Henrique de Moraes Holschuh wrote:
> retitle 863682 jessie-pu: package intel-microcode/3.20170707.1~deb8u1
> thanks
> 
> Intel released the fixes for Kaby Lake as well, so I am updating this
> s-p-u bug for the newer version of the intel-microcode package.

Please go ahead.

Regards,

Adam

Bug#867989: stretch-pu: package intel-microcode/3.20170707.1~deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2017-07-10 at 18:30 -0300, Henrique de Moraes Holschuh wrote:

> I'd like to update the intel-microcode package in Debian stretch.
> 
> This s-p-u request is related to the os-p-u request at:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863682
> 
> This package update is related to:
> https://lists.debian.org/debian-devel/2017/06/msg00308.html
> 
> This microcode update fixes the SKL150 and KBL095 errata
> (hyper-threading bug) on every Skylake and Kaby Lake processor affected
> by the issue.
> 
> It also fixes other undisclosed errata on Kaby Lake processors.

Please go ahead.

Regards,

Adam

Processed: Re: Bug#867989: stretch-pu: package intel-microcode/3.20170707.1~deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #867989 [release.debian.org] stretch-pu: package 
intel-microcode/3.20170707.1~deb9u1
Added tag(s) confirmed.

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

Processed: Re: Bug#867335: stretch-pu: package systemd/232-25

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed d-i
Bug #867335 [release.debian.org] stretch-pu: package systemd/232-25
Added tag(s) confirmed and d-i.

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

Bug#867335: stretch-pu: package systemd/232-25

[Adam D. Barratt]

Control: tags -1 + confirmed d-i

On Wed, 2017-07-05 at 23:25 +0200, Michael Biebl wrote:
> systemd (232-25+deb9u1) stretch; urgency=medium
> 
>   [ Dimitri John Ledkov ]
>   * Fix out-of-bounds write in systemd-resolved.
> CVE-2017-9445 (Closes: #866147, LP: #1695546)
[...]
>   [ Michael Biebl ]
>   * Be truly quiet in systemctl -q is-enabled (Closes: #866579)
[...]
>   * Improve RLIMIT_NOFILE handling.
> Use /proc/sys/fs/nr_open to find the current limit of open files
> compiled into the kernel instead of using a hard-coded value of 65536
> for RLIMIT_NOFILE. (Closes: #865449)
[...]
>   [ Nicolas Braud-Santoni ]
>   * debian/extra/rules: Use updated U2F ruleset.
> This ruleset comes from Yubico's libu2f-host. (Closes: #824532)

I'm okay with the diff, but as mentioned:

> The changes shouldn't affect the installer. CCed debian-boot nonetheless for
> a KiBi ack.

Regards,

Adam

Processed: Re: Bug#867190: stretch-pu: package apt/1.4.7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -moreinfo +confirmed
Bug #867190 [release.debian.org] stretch-pu: package apt/1.4.7
Ignoring request to alter tags of bug #867190 to the same tags previously set
Bug #867190 [release.debian.org] stretch-pu: package apt/1.4.7
Added tag(s) confirmed.

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

Bug#867190: stretch-pu: package apt/1.4.7

[Adam D. Barratt]

Control: tags -1 -moreinfo +confirmed

On Sun, 2017-07-09 at 17:08 +0200, Julian Andres Klode wrote:
> The first one by David, the second by me, so this would end up
> something like the following (order may be different, it's auto-generated
> from git commits):
> 
> apt (1.4.7) stretch; urgency=medium
> 
>   [ Robert Luberda ]
>   * fix a "critical" typo in old changelog entry (Closes: 866358)
> 
>   [ David Kalnischkies ]
>   * use port from SRV record instead of initial port
>   * travis: ignore profiling warning in progress lines
>  
> 
>   [ Julian Andres Klode ]
>   * Reset failure reason when connection was successful

maybe "... ensuring errors are correctly reported" or something similar?

>   * debian/gbp.conf: Set debian-branch to 1.4.y
>   * http: Do not try reading content if Content-Length is 0
>   * travis: Migrate to Docker
>   * Release 1.4.7 (LP: #1702326)

Having the release item at the end looks slightly odd, imho. :-)

Please feel free to upload something like the above (bearing in mind
that the window for 9.1 closes this weekend).

Regards,

Adam

Bug#863734: unblock: gnupg2/2.1.18-8

[Adam D. Barratt]

On Tue, 2017-07-11 at 11:16 -0400, Daniel Kahn Gillmor wrote:
> On Sun 2017-06-25 18:39:34 -0400, Daniel Kahn Gillmor wrote:
> > On Sat 2017-06-17 17:36:39 +0100, Adam D. Barratt wrote:
> >> Unfortunately we ran out of time to handle this before the release, so
> >> converting it to a proto-p-u request.
> >
> > Thanks for this conversion, Adam.  Please let me know if you need any
> > feedback from on it from me or anyone else on the pkg-gnupg-maint team.
> 
> ping on https://bugs.debian.org/863734 (sending gnupg2/2.1.18-8 to
> stretch proposed-updates) -- please let me know if you need anything
> else.

To be entirely honest, the size of the diff and the number of patches
still worries me, as it makes it very difficult to review. I'm assuming
that there haven't been any relevant regressions or follow-up fixes
since the -8 upload?

In any case, we can't simply transplant -8 to p-u, so would need to see
a debdiff for either a -6+deb9u1 or -8~deb9u1 upload (depending on how
you structure the changelog), built against and tested on stretch,
before confirming an upload.

Finally, unless I missed one when checking back through the thread, we
also need a d-i ack.

Regards,

Adam

Bug#868243: jessie-pu: package partman-ext3/84+deb8u1

[Cyril Brulebois]

Adam D. Barratt  (2017-07-13):
> Please go ahead.

Thanks, uploaded.


KiBi.


signature.asc
Description: Digital signature

Bug#868241: jessie-pu: package netcfg/1.131+deb8u2

[Cyril Brulebois]

Adam D. Barratt  (2017-07-13):
> s/prevents/prevent/, fwiw.

Oopsie, missed it before building & uploading.

> Please go ahead.

Done, thanks.


KiBi.


signature.asc
Description: Digital signature

Bug#868230: jessie-pu: package os-prober/1.65+deb8u1

[Cyril Brulebois]

Adam D. Barratt  (2017-07-13):
> Not as much as I feared from that comment. :-)

It made me unhappy anyway. :)

> Please go ahead.

Thanks, uploaded.


KiBi.


signature.asc
Description: Digital signature

Bug#868228: stretch-pu: package os-prober/1.76~deb9u1

[Cyril Brulebois]

Adam D. Barratt  (2017-07-13):
> Please go ahead.

Thanks, uploaded.


KiBi.


signature.asc
Description: Digital signature

Processed: Re: Bug#868243: jessie-pu: package partman-ext3/84+deb8u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #868243 [release.debian.org] jessie-pu: package partman-ext3/84+deb8u1
Added tag(s) confirmed.

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

Bug#868243: jessie-pu: package partman-ext3/84+deb8u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2017-07-13 at 17:40 +0200, Cyril Brulebois wrote:
> | partman-ext3 (84+deb8u1) jessie; urgency=low
> | 
> |   [ Christian Perrier ]
> |   * Force ext3|ext4 filesystem creation with "-F" so that D-I doesn't
> | "hang" when re-using an existing partition in some situations.
> | Closes: #767682

Please go ahead.

Regards,

Adam

Bug#868241: jessie-pu: package netcfg/1.131+deb8u2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2017-07-13 at 17:33 +0200, Cyril Brulebois wrote:
> | netcfg (1.131+deb8u2) jessie; urgency=medium
> | 
> |   * IPv6 autoconfiguration: fix NTP server name handling, which would be
> | stored as the DHCP-provided hostname, with many thanks to Malcolm
> | Scott for the bug report and the patch (Closes: #862745).
> |   * Stop queueing rdnssd's installation with IPv6 setups. This component
> | conflicts with network-manager and installing it from the network
> | configuration step might prevents large parts of desktop environments
> | from being installed. This isn't a perfect solution but this should be
> | way better than the current status quo (Closes: #854801).

s/prevents/prevent/, fwiw.

Please go ahead.

Regards,

Adam

Processed: Re: Bug#868241: jessie-pu: package netcfg/1.131+deb8u2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #868241 [release.debian.org] jessie-pu: package netcfg/1.131+deb8u2
Added tag(s) confirmed.

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

Bug#868230: jessie-pu: package os-prober/1.65+deb8u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2017-07-13 at 13:29 +0200, Cyril Brulebois wrote:
> I'd like to fix a few things in os-prober in jessie:
>  - dos vs. msdos check, leading to misdetections with EFI systems
>  - improve robustness with Windows detection by adding the -a flag
>to grep (this generates much diff noise, sorry)

Not as much as I feared from that comment. :-)

>  - add support for Windows 10 (at the top of said noise)

Please go ahead.

Regards,

Adam

Bug#868228: stretch-pu: package os-prober/1.76~deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2017-07-13 at 13:17 +0200, Cyril Brulebois wrote:
> | os-prober (1.76~deb9u1) stretch; urgency=medium
> | 
> |   * Rebuild for stretch.
> | 
> |  -- Cyril Brulebois   Thu, 13 Jul 2017 13:12:22 +0200
> | 
> | os-prober (1.76) unstable; urgency=medium
> | 
> |   [ Cyril Brulebois ]
> |   * os-probes/mounted/x86/05efi: Fix check on ID_PART_ENTRY_SCHEME, to
> | look for "dos" instead of "msdos" (Closes: #817023).
> | 
> |  -- Christian Perrier   Wed, 28 Jun 2017 07:08:36 +0200

Please go ahead.

Regards,

Adam

Processed: Re: Bug#868230: jessie-pu: package os-prober/1.65+deb8u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #868230 [release.debian.org] jessie-pu: package os-prober/1.65+deb8u1
Added tag(s) confirmed.

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

Processed: Re: Bug#868228: stretch-pu: package os-prober/1.76~deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #868228 [release.debian.org] stretch-pu: package os-prober/1.76~deb9u1
Added tag(s) confirmed.

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

Bug#863682: more information

[Henrique de Moraes Holschuh]

I have been taking a daily look for any reports of issues with intel
microcode updates over the last 30 days, and so far there are no reports
of issues caused by these updates.

Due to the HT errata issue, these microcode updates had a lot more
adoption than usual by users across most Linux distros, so they had a
lot of extra exposure already.

Version 20170511 shipped with stretch non-free, and we had no regression
reports about it.  It was also backported to jessie-backports, and even
with everyone that installed it both in stretch and jessie due to the
hyper-threading errata (about 2000 additional new installs according to
popcon), there were no regression reports.  It was widely installed on
other distros, and I could not find any regression reports on Gentoo,
Arch, Mint or Fedora, nor through Google searches.

Version 20170707 only added new microcode for newer processors (Kaby
Lake, and very recently launched Skylake server and Skylake-X), leaving
all other microcodes unchanged from 20170511.  Since the motherboards
that support such processors were launched relatively recently, and Kaby
Lake is quite close to Skylake firmware-wise as far as microcode and
closely related platform modules, the chances of regressions due to
outdated firmware are lower.  Again, I can't find any regression reports
at all related to this microcode update.

There are several reports from Ubuntu users about sucessfull installs of
both 20170511 and 20170707, since they're also evaluating it for SRUs as
well.  No regressions were reported so far:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1700373

Thanks!

-- 
  Henrique Holschuh

PTC Users List

[madison . harris]

Hello there,class="MsoNormal"> Might want to know whether you  
are keen on obtaining PTC Leads for your marketing effort?class="MsoNormal"> Data Fields: Name, Title,  
Email, Phone Numbers, Company Name, and Company Details like Physical  
Address, Web Address, Revenue Size, Employee Size and industry.class="MsoNormal">Please help me understand  
more about your requirements:class="MsoNormal">•         Job Titles…?•          
Industry…..? •         Geography….?class="MsoNormal">•         Special Instructions …?class="MsoNormal"> Please review and let me know  
your thoughts I will get back to you with more information and Price  
List. Regards,class="MsoNormal">Madison Harris Sales  
Executive class="MsoNormal">To opt-out response Remove in the subject  
line


























 
powered by GSM. Free mail merge and  
email marketing software for Gmail.

Bug#868243: jessie-pu: package partman-ext3/84+deb8u1

[Cyril Brulebois]

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

Hi,

It's high time we fix this issue in jessie: failing to pass the “force”
flag when using mkfs leads to hangs in d-i. It's been fixed in stretch
but not backported to jessie yet. Relevant bug reports according to my
notes: #767682, #778922, #774525, #767682.

Changelog entry:
| partman-ext3 (84+deb8u1) jessie; urgency=low
| 
|   [ Christian Perrier ]
|   * Force ext3|ext4 filesystem creation with "-F" so that D-I doesn't
| "hang" when re-using an existing partition in some situations.
| Closes: #767682
| 
|  -- Cyril Brulebois   Thu, 13 Jul 2017 17:36:02 +0200

Thanks for considering.


KiBi.
diff -Nru partman-ext3-84/commit.d/format_ext3 partman-ext3-84+deb8u1/commit.d/format_ext3
--- partman-ext3-84/commit.d/format_ext3	2014-07-08 07:09:38.0 +0200
+++ partman-ext3-84+deb8u1/commit.d/format_ext3	2017-07-13 17:35:45.0 +0200
@@ -56,7 +56,7 @@
 usage=''
 			fi
 			if log-output -t partman --pass-stdout \
-			   mkfs.$filesystem $device $usage >/dev/null; then
+			   mkfs.$filesystem -F $device $usage >/dev/null; then
 sync
 status=OK
 			else
diff -Nru partman-ext3-84/debian/changelog partman-ext3-84+deb8u1/debian/changelog
--- partman-ext3-84/debian/changelog	2014-11-15 08:07:34.0 +0100
+++ partman-ext3-84+deb8u1/debian/changelog	2017-07-13 17:36:07.0 +0200
@@ -1,3 +1,12 @@
+partman-ext3 (84+deb8u1) jessie; urgency=low
+
+  [ Christian Perrier ]
+  * Force ext3|ext4 filesystem creation with "-F" so that D-I doesn't
+"hang" when re-using an existing partition in some situations.
+Closes: #767682
+
+ -- Cyril Brulebois   Thu, 13 Jul 2017 17:36:02 +0200
+
 partman-ext3 (84) unstable; urgency=low
 
   [ Updated translations ]

Bug#868241: jessie-pu: package netcfg/1.131+deb8u2

[Cyril Brulebois]

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

Hi,

I'd like to fix two issues in netcfg: memory corruption with NTP server
name handling, and rdnssd's getting installed, which conflicts with
network-manager and prevents some desktops from being correctly installed.

Changelog entry:
| netcfg (1.131+deb8u2) jessie; urgency=medium
| 
|   * IPv6 autoconfiguration: fix NTP server name handling, which would be
| stored as the DHCP-provided hostname, with many thanks to Malcolm
| Scott for the bug report and the patch (Closes: #862745).
|   * Stop queueing rdnssd's installation with IPv6 setups. This component
| conflicts with network-manager and installing it from the network
| configuration step might prevents large parts of desktop environments
| from being installed. This isn't a perfect solution but this should be
| way better than the current status quo (Closes: #854801).
| 
|  -- Cyril Brulebois   Thu, 13 Jul 2017 17:28:42 +0200

Fixes are in stretch already.

Thanks for considering.


KiBi.
diff -Nru netcfg-1.131+deb8u1/autoconfig.c netcfg-1.131+deb8u2/autoconfig.c
--- netcfg-1.131+deb8u1/autoconfig.c	2013-01-13 14:23:24.0 +0100
+++ netcfg-1.131+deb8u2/autoconfig.c	2017-07-13 17:27:47.0 +0200
@@ -347,7 +347,7 @@
 			ns_idx++;
 		} else if (!strncmp("NTP server[", l, 11) && ntp_idx < NETCFG_NTPSERVERS_MAX) {
 			p = strstr(l, "] ") + 2;
-			strncpy(interface->ntp_servers[ns_idx++], p, sizeof(interface->ntp_servers[ntp_idx]));
+			strncpy(interface->ntp_servers[ntp_idx], p, sizeof(interface->ntp_servers[ntp_idx]));
 			ntp_idx++;
 		} else if (!strncmp("Domain search list[0] ", l, 21)) {
 			p = strstr(l, "] ") + 2;
@@ -470,7 +470,7 @@
 	if (ipv6) {
 		read_rdnssd_nameservers(interface);
 		if (nameserver_count(interface) > 0) {
-			di_exec_shell_log("apt-install rdnssd");
+			di_debug("Not queueing rdnssd installation to make sure not to interfere with network-manager");
 		}
 	}
 	
diff -Nru netcfg-1.131+deb8u1/debian/changelog netcfg-1.131+deb8u2/debian/changelog
--- netcfg-1.131+deb8u1/debian/changelog	2015-10-03 20:53:48.0 +0200
+++ netcfg-1.131+deb8u2/debian/changelog	2017-07-13 17:28:49.0 +0200
@@ -1,3 +1,16 @@
+netcfg (1.131+deb8u2) jessie; urgency=medium
+
+  * IPv6 autoconfiguration: fix NTP server name handling, which would be
+stored as the DHCP-provided hostname, with many thanks to Malcolm
+Scott for the bug report and the patch (Closes: #862745).
+  * Stop queueing rdnssd's installation with IPv6 setups. This component
+conflicts with network-manager and installing it from the network
+configuration step might prevents large parts of desktop environments
+from being installed. This isn't a perfect solution but this should be
+way better than the current status quo (Closes: #854801).
+
+ -- Cyril Brulebois   Thu, 13 Jul 2017 17:28:42 +0200
+
 netcfg (1.131+deb8u1) stable; urgency=medium
 
   * Fix is_layer3_qeth on s390x to avoid bailing out if the network

Bug#868230: jessie-pu: package os-prober/1.65+deb8u1

[Cyril Brulebois]

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

Hi,

I'd like to fix a few things in os-prober in jessie:
 - dos vs. msdos check, leading to misdetections with EFI systems
 - improve robustness with Windows detection by adding the -a flag
   to grep (this generates much diff noise, sorry)
 - add support for Windows 10 (at the top of said noise)

Cherry-picked from fixes available in stretch (or on the way to
stretch-pu for the first one).

Thanks for considering.


KiBi.
diff -Nru os-prober-1.65/debian/changelog os-prober-1.65+deb8u1/debian/changelog
--- os-prober-1.65/debian/changelog	2014-11-25 18:41:48.0 +0100
+++ os-prober-1.65+deb8u1/debian/changelog	2017-07-13 13:25:15.0 +0200
@@ -1,3 +1,16 @@
+os-prober (1.65+deb8u1) jessie; urgency=medium
+
+  * os-probes/mounted/x86/05efi: Fix check on ID_PART_ENTRY_SCHEME, to
+look for "dos" instead of "msdos" (Closes: #817023).
+  * Add -a flag to grep -qs for Windows Vista detection. It appears the
+file isn't always considered as a text file, so this should be more
+robust. Thanks to Gianluigi Tiesi for the report and the suggestion
+(Closes: #791383).
+  * Add support for Windows 10 (otherwise reported as Windows Recovery
+Environment). Thanks, Philipp Wolfer! (Closes: #801278).
+
+ -- Cyril Brulebois   Thu, 13 Jul 2017 13:25:12 +0200
+
 os-prober (1.65) unstable; urgency=medium
 
   [ Steve McIntyre ]
diff -Nru os-prober-1.65/os-probes/mounted/x86/05efi os-prober-1.65+deb8u1/os-probes/mounted/x86/05efi
--- os-prober-1.65/os-probes/mounted/x86/05efi	2014-11-12 16:19:18.0 +0100
+++ os-prober-1.65+deb8u1/os-probes/mounted/x86/05efi	2017-07-13 13:17:46.0 +0200
@@ -39,9 +39,9 @@
 	debug "$partition partition type is $ID_PART_ENTRY_TYPE"
 
 	if [ -z "$ID_PART_ENTRY_TYPE" -o -z "$ID_PART_ENTRY_SCHEME" -o \
-		\( "$ID_PART_ENTRY_SCHEME" != gpt -a "$ID_PART_ENTRY_SCHEME" != msdos \) -o \
+		\( "$ID_PART_ENTRY_SCHEME" != gpt -a "$ID_PART_ENTRY_SCHEME" != dos \) -o \
 		\( "$ID_PART_ENTRY_SCHEME" = gpt -a "$ID_PART_ENTRY_TYPE" != c12a7328-f81f-11d2-ba4b-00a0c93ec93b \) -o \
-		\( "$ID_PART_ENTRY_SCHEME" = msdos -a "$ID_PART_ENTRY_TYPE" != 0xef \) ]; then
+		\( "$ID_PART_ENTRY_SCHEME" = dos -a "$ID_PART_ENTRY_TYPE" != 0xef \) ]; then
 		debug "$partition is not a ESP partition: exiting"
 		exit 1
 	fi
diff -Nru os-prober-1.65/os-probes/mounted/x86/20microsoft os-prober-1.65+deb8u1/os-probes/mounted/x86/20microsoft
--- os-prober-1.65/os-probes/mounted/x86/20microsoft	2014-11-12 16:19:18.0 +0100
+++ os-prober-1.65+deb8u1/os-probes/mounted/x86/20microsoft	2017-07-13 13:22:21.0 +0200
@@ -31,19 +31,21 @@
 	for boot in $(item_in_dir boot "$2"); do
 		bcd=$(item_in_dir bcd "$2/$boot")
 		if [ -n "$bcd" ]; then
-			if grep -qs "W.i.n.d.o.w.s. .8" "$2/$boot/$bcd"; then
+			if   grep -aqs "W.i.n.d.o.w.s. .1.0" "$2/$boot/$bcd"; then
+long="Windows 10 (loader)"
+			elif grep -aqs "W.i.n.d.o.w.s. .8" "$2/$boot/$bcd"; then
 long="Windows 8 (loader)"
-			elif grep -qs "W.i.n.d.o.w.s. .7" "$2/$boot/$bcd"; then
+			elif grep -aqs "W.i.n.d.o.w.s. .7" "$2/$boot/$bcd"; then
 long="Windows 7 (loader)"
-			elif grep -qs "W.i.n.d.o.w.s. .V.i.s.t.a" "$2/$boot/$bcd"; then
+			elif grep -aqs "W.i.n.d.o.w.s. .V.i.s.t.a" "$2/$boot/$bcd"; then
 long="Windows Vista (loader)"
-			elif grep -qs "W.i.n.d.o.w.s. .S.e.r.v.e.r. .2.0.0.8. .R.2." "$2/$boot/$bcd"; then
+			elif grep -aqs "W.i.n.d.o.w.s. .S.e.r.v.e.r. .2.0.0.8. .R.2." "$2/$boot/$bcd"; then
 long="Windows Server 2008 R2 (loader)"
-			elif grep -qs "W.i.n.d.o.w.s. .S.e.r.v.e.r. .2.0.0.8." "$2/$boot/$bcd"; then
+			elif grep -aqs "W.i.n.d.o.w.s. .S.e.r.v.e.r. .2.0.0.8." "$2/$boot/$bcd"; then
 long="Windows Server 2008 (loader)"
-			elif grep -qs "W.i.n.d.o.w.s. .R.e.c.o.v.e.r.y. .E.n.v.i.r.o.n.m.e.n.t" "$2/$boot/$bcd"; then
+			elif grep -aqs "W.i.n.d.o.w.s. .R.e.c.o.v.e.r.y. .E.n.v.i.r.o.n.m.e.n.t" "$2/$boot/$bcd"; then
 long="Windows Recovery Environment (loader)"
-			elif grep -qs "W.i.n.d.o.w.s. .S.e.t.u.p" "$2/$boot/$bcd"; then
+			elif grep -aqs "W.i.n.d.o.w.s. .S.e.t.u.p" "$2/$boot/$bcd"; then
 long="Windows Recovery Environment (loader)"
 			else
 long="Windows Vista (loader)"

Bug#868228: stretch-pu: package os-prober/1.76~deb9u1

[Cyril Brulebois]

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

Hi,

I'd like to fix EFI-related misdetection in os-prober, due to an
appropriate check (dos vs. msdos).

Changelog excerpt (no unrelated changes in the meanwhile):
| os-prober (1.76~deb9u1) stretch; urgency=medium
| 
|   * Rebuild for stretch.
| 
|  -- Cyril Brulebois   Thu, 13 Jul 2017 13:12:22 +0200
| 
| os-prober (1.76) unstable; urgency=medium
| 
|   [ Cyril Brulebois ]
|   * os-probes/mounted/x86/05efi: Fix check on ID_PART_ENTRY_SCHEME, to
| look for "dos" instead of "msdos" (Closes: #817023).
| 
|  -- Christian Perrier   Wed, 28 Jun 2017 07:08:36 +0200

Thanks for considering.


KiBi.
diff -Nru os-prober-1.75/debian/changelog os-prober-1.76~deb9u1/debian/changelog
--- os-prober-1.75/debian/changelog	2017-05-01 09:55:33.0 +0200
+++ os-prober-1.76~deb9u1/debian/changelog	2017-07-13 13:13:03.0 +0200
@@ -1,3 +1,17 @@
+os-prober (1.76~deb9u1) stretch; urgency=medium
+
+  * Rebuild for stretch.
+
+ -- Cyril Brulebois   Thu, 13 Jul 2017 13:12:22 +0200
+
+os-prober (1.76) unstable; urgency=medium
+
+  [ Cyril Brulebois ]
+  * os-probes/mounted/x86/05efi: Fix check on ID_PART_ENTRY_SCHEME, to
+look for "dos" instead of "msdos" (Closes: #817023).
+
+ -- Christian Perrier   Wed, 28 Jun 2017 07:08:36 +0200
+
 os-prober (1.75) unstable; urgency=medium
 
   * Remove code using device mapper (Closes: #860833, #853927, #853163).
diff -Nru os-prober-1.75/os-probes/mounted/x86/05efi os-prober-1.76~deb9u1/os-probes/mounted/x86/05efi
--- os-prober-1.75/os-probes/mounted/x86/05efi	2017-05-01 09:55:33.0 +0200
+++ os-prober-1.76~deb9u1/os-probes/mounted/x86/05efi	2017-06-24 19:38:43.0 +0200
@@ -39,9 +39,9 @@
 	debug "$partition partition type is $ID_PART_ENTRY_TYPE"
 
 	if [ -z "$ID_PART_ENTRY_TYPE" -o -z "$ID_PART_ENTRY_SCHEME" -o \
-		\( "$ID_PART_ENTRY_SCHEME" != gpt -a "$ID_PART_ENTRY_SCHEME" != msdos \) -o \
+		\( "$ID_PART_ENTRY_SCHEME" != gpt -a "$ID_PART_ENTRY_SCHEME" != dos \) -o \
 		\( "$ID_PART_ENTRY_SCHEME" = gpt -a "$ID_PART_ENTRY_TYPE" != c12a7328-f81f-11d2-ba4b-00a0c93ec93b \) -o \
-		\( "$ID_PART_ENTRY_SCHEME" = msdos -a "$ID_PART_ENTRY_TYPE" != 0xef \) ]; then
+		\( "$ID_PART_ENTRY_SCHEME" = dos -a "$ID_PART_ENTRY_TYPE" != 0xef \) ]; then
 		debug "$partition is not a ESP partition: exiting"
 		exit 1
 	fi

Bug#867335: stretch-pu: package systemd/232-25

[Michael Biebl]

Am 06.07.2017 um 20:35 schrieb Michael Biebl:
> Am 06.07.2017 um 20:10 schrieb Cyril Brulebois:
>> Hi,
>>
>> Michael Biebl  (2017-07-05):
>>> I'd like to make a stable upload for systemd.
>>>
>>> All changes are already in unstable.
>>> An annotated changelog follows:
>>
>> Just had a quick glance at git, and it feels like there's a booboo…
>>
>>> systemd (232-25+deb9u1) stretch; urgency=medium
>>>
>>>   [ Dimitri John Ledkov ]
>>>   * Fix out-of-bounds write in systemd-resolved.
>>> CVE-2017-9445 (Closes: #866147, LP: #1695546)
>>>
>>> https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=stretch-proposed=986c0be9809e6234680c001b731c5b3099f41c1c
>>>
>>> That's probably the most important one to get into stretch.
>>> The security team wanted us to fix this issue via a stable upload.
>>
>> What's up with this extra patch, which seems entirely unrelated?
>>   debian/patches/debian/fsckd-daemon-for-inter-fsckd-communication.patch
>>
>> I'll have a closer look at the rest when time permits.
> 
> That's a bit of patch noise generated by gbp pq export. You can simply
> ignore that bit.

Ping, are there any more questions which I'd be happy to answer.
I'd really like to get the CVE fix into 9.1 if possible.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#862961: jessie-pu: package libembperl-perl/2.5.0-4+deb8u1

[Axel Beckert]

Hi,

Cyril Brulebois wrote:
> gregor herrmann  (2017-06-28):
> > So the only remaining code change is actually:
> > 
> > #v+
> > --- a/debian/zembperl.load.in
> > +++ b/debian/zembperl.load.in
> > @@ -1,6 +1,6 @@
> >  # The sucky "zembperl" name is so we load after perl
> > 
> > -# Depends: perl
> > +# Recommends: perl
> > 
> >  
> >LoadModule embperl_module @ARCHLIB@/auto/Embperl/Embperl.so
> > #v-
> > 
> > 
> > I've now tentatively changed d/changelog to say
> > 
> > #v+
> >   * Change hard dependency on mod_perl in zembperl.load to Recommends.
> > mod_perl is not required, and is enabled by default anyway if it is
> > installed.
> > This change matches the package dependencies and fixes an installation
> > failure when libapache2-mod-perl2 is not installed.
> > (Closes: #810655)
> > #v-
> > 
> > 
> > Does this make sense?
> 
> I think the situation is clearer with your explanations above, and the
> changes+changelog look in sync and reasonable.

*nod* Looks fine to me, too.

> > I'm attaching the full new debdiff, and I'm looping in Axel for a sanity
> > check.
> 
> I won't be tagging this bug report with +confirmed right away, since we're
> awaiting for some more feedback, but the proposed changes look good to me.

No objections from my side. I only vaguely remember the case back
then, but I do remember that there were issues if mod_perl wasn't
installed despite Embperl can be used without, e.g. as CGI.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


signature.asc
Description: Digital signature

Bug#866692: stretch-pu: package linux-latest/80+deb9u1

[Adam D. Barratt]

On 2017-07-13 11:56, Ben Hutchings wrote:

On Thu, 2017-07-13 at 07:42 +0100, Adam D. Barratt wrote:

[...]

If this is going to make it into 9.1, it needs to be uploaded _and
through NEW_ by the weekend.


I can upload straight away if you're satisfied by the answers I just
sent.


Yes, thanks.

Regards,

Adam

Bug#866692: stretch-pu: package linux-latest/80+deb9u1

[Ben Hutchings]

On Sat, 2017-07-01 at 16:10 +0100, Adam D. Barratt wrote:
[...]
> Overall the changes look okay to me, with the note below on unstable
> taken into account.
> 
> I was curious about this change though:
> 
> -Section: debug
> -Priority: extra
> 
> Should the -dbg packages not still be in the "debug" section?

Or metapackages?  I just reverted to the previous metadata.

> Is it intentional that there are still some dbgsym packages built by
> src:linux? Specifically:
> 
> hyperv-daemons-dbgsym  | 4.9.30-2+deb9u2 | stable-new | amd64, i386
> libcpupower1-dbgsym| 4.9.30-2+deb9u2 | stable-new | amd64, arm64, 
> armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> linux-cpupower-dbgsym  | 4.9.30-2+deb9u2 | stable-new | amd64, i386
> linux-kbuild-4.9-dbgsym| 4.9.30-2+deb9u2 | stable-new | amd64, arm64, 
> armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> linux-perf-4.9-dbgsym  | 4.9.30-2+deb9u2 | stable-new | amd64, arm64, 
> armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> usbip-dbgsym   | 2.0+4.9.30-2+deb9u2 | stable-new | amd64, arm64, 
> armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x

Yes, it is intentional that userland packages get automatic debug
symbol packages.

> > (We'll need a higher version in unstable, too, but I see 82 was uploaded
> > and reached NEW already, so hopefully that'll be sorted out by the time
> > the point release happens.)
> 
> Well, it'll need to be. :-) To be entirely honest, I'd prefer to get the
> unstable situation sorted before we fix stable. Looking at the NEW page
> for the unstable upload, I can't imagine that there'll be any issues
> getting it sorted quickly.

That's now done.

Ben.

-- 
Ben Hutchings
Design a system any fool can use, and only a fool will want to use it.



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

Bug#866692: stretch-pu: package linux-latest/80+deb9u1

[Ben Hutchings]

On Thu, 2017-07-13 at 07:42 +0100, Adam D. Barratt wrote:
> On Sat, 2017-07-01 at 16:10 +0100, Adam D. Barratt wrote:
> > Control: tags -1 + confirmed
> > 
> > Hi,
> > 
> > On Sat, 2017-07-01 at 06:07 +0200, Cyril Brulebois wrote:
> > > Hi Ben,
> > > 
> > > > > > Ben Hutchings  (2017-07-01):
> > > > src:linux-latest builds meta-packages depending on debug info packages
> > > > built from src:linux.  During the stretch release cycle, these were
> > > > changed to new-style dbgsym packages and then this change was reverted
> > > > to src:linux.  However, the change in src:linux-latest was *not*
> > > > reverted, leaving these meta-packages uninstallable.
> 
> [...]
> > -Section: debug
> > -Priority: extra
> > 
> > Should the -dbg packages not still be in the "debug" section?
> > 
> > Is it intentional that there are still some dbgsym packages built by
> > src:linux? Specifically:
> > 
> > hyperv-daemons-dbgsym  | 4.9.30-2+deb9u2 | stable-new | amd64, i386
> > libcpupower1-dbgsym| 4.9.30-2+deb9u2 | stable-new | amd64, 
> > arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> > linux-cpupower-dbgsym  | 4.9.30-2+deb9u2 | stable-new | amd64, i386
> > linux-kbuild-4.9-dbgsym| 4.9.30-2+deb9u2 | stable-new | amd64, 
> > arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> > linux-perf-4.9-dbgsym  | 4.9.30-2+deb9u2 | stable-new | amd64, 
> > arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> > usbip-dbgsym   | 2.0+4.9.30-2+deb9u2 | stable-new | amd64, 
> > arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> 
> Ping, both on the above questions and the upload.
> 
> If this is going to make it into 9.1, it needs to be uploaded _and
> through NEW_ by the weekend.

I can upload straight away if you're satisfied by the answers I just
sent.

Ben.

-- 
Ben Hutchings
Design a system any fool can use, and only a fool will want to use it.



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

Bug#866797: Uncoordinated libdap transition

[Bas Couwenberg]

Alastair,

Why do you keep uploading new upstream releases which trigger transition 
due to bumped SONAMEs to unstable, and thereby triggering uncoordinated 
transitions?


When SONAMEs are bumped and library packages renamed the package should 
be uploaded to experimental and the transition coordinated with the 
Release Team.


Please read the documentation and stick to that process: 
https://wiki.debian.org/Teams/ReleaseTeam/Transitions


I'm very disappointed that you still haven't learned to coordinate 
transition with the Release Team, especially since your uncoordinated 
libdap transition conflicts with the ongoing gdal-2.2.1 transition.


You need to contact the Release Team by filing the transition bugreport 
for libdap to coordinate the transition.


Kind Regards,

Bas

Bug#868222: stretch-pu: package partman-base/191+deb9u1

[Cyril Brulebois]

Adam D. Barratt  (2017-07-13):
> Control: tags -1 + confirmed
> 
> On 2017-07-13 8:56, Cyril Brulebois wrote:
> >| partman-base (191+deb9u1) stretch; urgency=medium
> >|
> >|   [ Karsten Merker ]
> >|   * For systems that are known to have their boot firmware on an mmcblk
> >| device, protect the firmware area on all mmcblk devices (and not
> >| only on mmcblk0) from being clobbered during guided partitioning
> >| and add missing whitespace to the corresponding log output.
> >| (Closes: #854822)
> 
> Please go ahead.

Thanks, uploaded.


KiBi.


signature.asc
Description: Digital signature

Bug#868102: stretch-pu: package devscripts/2.17.6+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2017-07-12 3:27, James McCoy wrote:

* debchange:
  + Target stretch-backports with --bpo.  Closes: #867662
  + Support $codename{,-{proposed-updates,security}} as well.


I think there's a bug (or two?) that could be closed there?


* bts:
  + Add support for the new 'a11y' tag.  Closes: #867416


Please go ahead.

Regards,

Adam

Processed: Re: Bug#868102: stretch-pu: package devscripts/2.17.6+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #868102 [release.debian.org] stretch-pu: package devscripts/2.17.6+deb9u1
Added tag(s) confirmed.

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

Processed: Re: Bug#868223: stretch-pu: package avogadro/1.2.0-2+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #868223 [release.debian.org] stretch-pu: package avogadro/1.2.0-2+deb9u1
Added tag(s) confirmed.

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

Processed: Re: Bug#868130: stretch-pu: package geolinks/0.2.0-1+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #868130 [release.debian.org] stretch-pu: package geolinks/0.2.0-1+deb9u1
Added tag(s) confirmed.

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

Bug#868223: stretch-pu: package avogadro/1.2.0-2+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2017-07-13 9:18, Michael Banck wrote:

Version 1.2.0-2 (now in testing) fixes an RC bug in stretch where atoms
are not displayed at all, rendering avogadro useless.

The debdiff is attached, it replaces the old eigen3.patch with the
upstream versions here:

https://github.com/cryos/avogadro/commit/2d4be7ede177a8df7340fe3b209698d591ee8a04
https://github.com/cryos/avogadro/commit/43af3c117b0b3220b15c2fe2895b94bbd83d3a60

Changelog entry:

|avogadro (1.2.0-2+deb9u1) stretch; urgency=medium


As mentioned on IRC, that wants to be 1.2.0-1+deb9u1, please, so as not 
to have a higher version than unstable and testing. ;-)


With that change, please go ahead.

Regards,

Adam

Bug#868130: stretch-pu: package geolinks/0.2.0-1+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2017-07-12 10:35, Bas Couwenberg wrote:

The incorrect dependencies for the python3-geolinks binary package
reported in #867405 also affect the package in stretch.

geolinks (0.2.0-2) has fixed the issue in testing & unstable, and the
same fix is included in this proposed update for stretch.


Please go ahead.

Regards,

Adam

Bug#868210: jessie-pu: package python3-colorlog/2.4.0-1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2017-07-13 6:25, Philipp Huebner wrote:

I would like to fix #867422 in Jessie.
debdiff attached.


+python-colorlog (2.4.0-1+deb8u1) oldstable; urgency=medium

"jessie", not "oldstable", please.

With that change, please go ahead.

Regards,

Adam

Processed: Re: Bug#867970: stretch-pu: package python3-plumbum/1.6.2-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #867970 [release.debian.org] stretch-pu: package python3-plumbum/1.6.2-1
Added tag(s) confirmed.

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

Processed: Re: Bug#868210: jessie-pu: package python3-colorlog/2.4.0-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #868210 [release.debian.org] jessie-pu: package python3-colorlog/2.4.0-1
Added tag(s) confirmed.

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

Bug#867966: stretch-pu: package python3-colorlog/2.10.0-1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2017-07-10 21:14, Philipp Huebner wrote:

debdiff attached


+python-colorlog (2.10.0-1+deb9u1) stable; urgency=medium

Please target "stretch", rather than "stable".

With that change, please go ahead.

Regards,

Adam

Processed: Re: Bug#867966: stretch-pu: package python3-colorlog/2.10.0-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #867966 [release.debian.org] stretch-pu: package python3-colorlog/2.10.0-1
Added tag(s) confirmed.

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

Bug#867970: stretch-pu: package python3-plumbum/1.6.2-1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2017-07-10 21:14, Philipp Huebner wrote:

debdiff attached


+python-plumbum (1.6.2-1+deb9u1) stable; urgency=medium

"stretch", not "stable", please.

With that change, please go ahead.

Regards,

Adam

Bug#868211: jessie-pu: package python3-plumbum/1.4.2-1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2017-07-13 6:26, Philipp Huebner wrote:

I would like to fix #867449 in Jessie.


+python-plumbum (1.4.2-1+deb8u1) oldstable; urgency=medium

That wants to target "jessie", not "oldstable", please.

With that change, please go ahead.

Regards,

Adam

Processed: Re: Bug#868222: stretch-pu: package partman-base/191+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #868222 [release.debian.org] stretch-pu: package partman-base/191+deb9u1
Added tag(s) confirmed.

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

Processed: Re: Bug#868211: jessie-pu: package python3-plumbum/1.4.2-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #868211 [release.debian.org] jessie-pu: package python3-plumbum/1.4.2-1
Added tag(s) confirmed.

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

Bug#868222: stretch-pu: package partman-base/191+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2017-07-13 8:56, Cyril Brulebois wrote:

| partman-base (191+deb9u1) stretch; urgency=medium
|
|   [ Karsten Merker ]
|   * For systems that are known to have their boot firmware on an 
mmcblk

| device, protect the firmware area on all mmcblk devices (and not
| only on mmcblk0) from being clobbered during guided partitioning
| and add missing whitespace to the corresponding log output.
| (Closes: #854822)


Please go ahead.

Regards,

Adam

Bug#868128: stretch-pu: package python-imaplib2/2.55-1

[Cyril Brulebois]

Hi,

Ilias Tsitsimpis  (2017-07-12):
> Due to cut'n'paste error, the python3-imaplib2 package in stretch
> declares no dependencies (#867437). Do you believe this is something
> worth fixing in stretch? Attached is the proposed diff.

This would look good to me.

> diff -Nru python-imaplib2-2.55/debian/changelog 
> python-imaplib2-2.55/debian/changelog
> --- python-imaplib2-2.55/debian/changelog 2016-09-09 20:11:08.0 
> +0300
> +++ python-imaplib2-2.55/debian/changelog 2017-07-12 11:37:15.0 
> +0300
> @@ -1,3 +1,10 @@
> +python-imaplib2 (2.55-1+deb9u1) stable-proposed-updates; urgency=medium

Please target “stretch” instead.

> +  * Fix typo that resulted in missing dependencies for python3-imaplib2.
> +Thanks to Adrian Bunk for reporting this (Closes: #867437)
> +
> + -- Ilias Tsitsimpis   Wed, 12 Jul 2017 11:37:15 +0300
> +
>  python-imaplib2 (2.55-1) unstable; urgency=medium
>  
>* New upstream release.
> diff -Nru python-imaplib2-2.55/debian/control 
> python-imaplib2-2.55/debian/control
> --- python-imaplib2-2.55/debian/control   2016-09-09 20:11:08.0 
> +0300
> +++ python-imaplib2-2.55/debian/control   2017-07-12 11:36:39.0 
> +0300
> @@ -20,7 +20,7 @@
>  
>  Package: python3-imaplib2
>  Architecture: all
> -Depends: ${python:Depends}, ${misc:Depends}
> +Depends: ${python3:Depends}, ${misc:Depends}
>  Description: Threaded Python IMAP4 client (Python 3)
>   Python IMAP4 rev1 mail protocol client class using threads for parallel
>   operation, allowing full use of the IMAP4 concurrency features and to

This might need to wait until 9.2 since 9.1 freeze is coming up shortly,
and the fixed version hasn't reached testing yet.


KiBi.


signature.asc
Description: Digital signature

Bug#868223: stretch-pu: package avogadro/1.2.0-2+deb9u1

[Michael Banck]

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

Version 1.2.0-2 (now in testing) fixes an RC bug in stretch where atoms
are not displayed at all, rendering avogadro useless.

The debdiff is attached, it replaces the old eigen3.patch with the
upstream versions here:

https://github.com/cryos/avogadro/commit/2d4be7ede177a8df7340fe3b209698d591ee8a04
https://github.com/cryos/avogadro/commit/43af3c117b0b3220b15c2fe2895b94bbd83d3a60

Changelog entry:

|avogadro (1.2.0-2+deb9u1) stretch; urgency=medium
|
|  [ Anton Gladky ]
|  * Update eigen3 patches, pull them from upstream. (Closes: #865085)
|
| -- Michael Banck   Thu, 13 Jul 2017 10:15:00 +0200

Thanks for considering. 

   

Michael

-- System Information:
Debian Release: 8.7
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru avogadro-1.2.0/debian/changelog avogadro-1.2.0/debian/changelog
--- avogadro-1.2.0/debian/changelog 2016-10-02 10:13:51.0 +0200
+++ avogadro-1.2.0/debian/changelog 2017-07-13 10:15:00.0 +0200
@@ -1,3 +1,10 @@
+avogadro (1.2.0-2+deb9u1) stretch; urgency=medium
+
+  [ Anton Gladky ]
+  * Update eigen3 patches, pull them from upstream. (Closes: #865085)
+
+ -- Michael Banck   Thu, 13 Jul 2017 10:15:00 +0200
+
 avogadro (1.2.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru avogadro-1.2.0/debian/control avogadro-1.2.0/debian/control
--- avogadro-1.2.0/debian/control   2015-09-26 21:19:33.0 +0200
+++ avogadro-1.2.0/debian/control   2017-07-13 10:15:00.0 +0200
@@ -7,7 +7,7 @@
 Build-Depends: cmake (>> 2.6.0),
debhelper (>> 7.0.50~),
libboost-python-dev,
-   libeigen3-dev,
+   libeigen3-dev (>> 3.3),
libgl2ps-dev,
libglew-dev,
libopenbabel-dev (>> 2.2.0),
diff -Nru avogadro-1.2.0/debian/patches/eigen3_lib.patch 
avogadro-1.2.0/debian/patches/eigen3_lib.patch
--- avogadro-1.2.0/debian/patches/eigen3_lib.patch  1970-01-01 
01:00:00.0 +0100
+++ avogadro-1.2.0/debian/patches/eigen3_lib.patch  2016-10-02 
10:13:37.0 +0200
@@ -0,0 +1,162 @@
+From 2d4be7ede177a8df7340fe3b209698d591ee8a04 Mon Sep 17 00:00:00 2001
+From: Claudio Fernandes 
+Date: Mon, 16 Jan 2017 19:48:23 -0200
+Subject: [PATCH] Adapt libavogadro/python to Eigen 3.3
+
+---
+ libavogadro/src/python/camera.cpp |  2 +-
+ libavogadro/src/python/eigen.cpp  | 60 +++
+ 2 files changed, 31 insertions(+), 31 deletions(-)
+
+diff --git a/libavogadro/src/python/camera.cpp 
b/libavogadro/src/python/camera.cpp
+index 69ca87bf8..30b32af7d 100644
+--- a/libavogadro/src/python/camera.cpp
 b/libavogadro/src/python/camera.cpp
+@@ -10,7 +10,7 @@ using namespace Avogadro;
+ void export_Camera()
+ {
+ 
+-  const Eigen::Transform3d& (Camera::*modelview_ptr)() const = 
::modelview;
++  const Eigen::Projective3d& (Camera::*modelview_ptr)() const = 
::modelview;
+   Eigen::Vector3d (Camera::*unProject_ptr1)(const Eigen::Vector3d&) const = 
::unProject;
+   Eigen::Vector3d (Camera::*unProject_ptr2)(const QPoint&, const 
Eigen::Vector3d&) const = ::unProject;
+   Eigen::Vector3d (Camera::*unProject_ptr3)(const QPoint&) const = 
::unProject;
+diff --git a/libavogadro/src/python/eigen.cpp 
b/libavogadro/src/python/eigen.cpp
+index c1faedbcc..20b4e719d 100644
+--- a/libavogadro/src/python/eigen.cpp
 b/libavogadro/src/python/eigen.cpp
+@@ -305,9 +305,9 @@ template <> struct ScalarTraits
+ struct innerclass
+ {
+   //
+-  //  Eigen::Transform3d --> python array (4x4)
++  //  Eigen::Projective3d --> python array (4x4)
+   //
+-  static PyObject* convert(Eigen::Transform3d const )
++  static PyObject* convert(Eigen::Projective3d const )
+   {
+ npy_intp dims[2] = { 4, 4 };
+ PyObject *result = PyArray_SimpleNew(2, dims, PyArray_DOUBLE);
+@@ -321,9 +321,9 @@ template <> struct ScalarTraits
+ return incref(result);
+   }
+   //
+-  //  Eigen::Transform3d* --> python array (4x4)
++  //  Eigen::Projective3d* --> python array (4x4)
+   //
+-  static PyObject* convert(Eigen::Transform3d *trans)
++  static PyObject* convert(Eigen::Projective3d *trans)
+   {
+ npy_intp dims[2] = { 4, 4 };
+ PyObject *result = PyArray_SimpleNew(2, dims, PyArray_DOUBLE);
+@@ -337,9 +337,9 @@ template <> struct ScalarTraits
+ return incref(result);
+   

Bug#868222: stretch-pu: package partman-base/191+deb9u1

[Cyril Brulebois]

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

Hi,

I'd like to fix an installation issue where some devices get their boot
firmware area clobbered. We guard against mmcblk0 only, and this fix
extends the guard to any mmcblk device. Tiny fix for the relevant log
included along in the same commit.

Changelog entry:
| partman-base (191+deb9u1) stretch; urgency=medium
| 
|   [ Karsten Merker ]
|   * For systems that are known to have their boot firmware on an mmcblk
| device, protect the firmware area on all mmcblk devices (and not
| only on mmcblk0) from being clobbered during guided partitioning
| and add missing whitespace to the corresponding log output.
| (Closes: #854822)
| 
|  -- Cyril Brulebois   Thu, 13 Jul 2017 09:45:14 +0200

Thanks for considering.


KiBi.
diff -Nru partman-base-191/debian/changelog partman-base-191+deb9u1/debian/changelog
--- partman-base-191/debian/changelog	2017-02-10 19:24:30.0 +0100
+++ partman-base-191+deb9u1/debian/changelog	2017-07-13 09:45:15.0 +0200
@@ -1,3 +1,14 @@
+partman-base (191+deb9u1) stretch; urgency=medium
+
+  [ Karsten Merker ]
+  * For systems that are known to have their boot firmware on an mmcblk
+device, protect the firmware area on all mmcblk devices (and not
+only on mmcblk0) from being clobbered during guided partitioning
+and add missing whitespace to the corresponding log output.
+(Closes: #854822)
+
+ -- Cyril Brulebois   Thu, 13 Jul 2017 09:45:14 +0200
+
 partman-base (191) unstable; urgency=medium
 
   [ Mathieu Trudel-Lapierre ]
diff -Nru partman-base-191/parted_server.c partman-base-191+deb9u1/parted_server.c
--- partman-base-191/parted_server.c	2017-02-03 18:56:10.0 +0100
+++ partman-base-191+deb9u1/parted_server.c	2017-07-13 09:44:49.0 +0200
@@ -1374,9 +1374,9 @@
  * the firmware area, resulting in an unbootable system (see
  * bug #751704).
  */
-if (is_system_with_firmware_on_disk() && !strcmp(disk->dev->path, "/dev/mmcblk0")) {
+if (is_system_with_firmware_on_disk() && !strncmp(disk->dev->path, "/dev/mmcblk", 11)) {
 disk->needs_clobber = 0;
-log("Sunxi/Freescale/AM33XX detected. Disabling ped_disk_clobber" \
+log("Sunxi/Freescale/AM33XX detected. Disabling ped_disk_clobber " \
 "for the boot device %s to protect the firmware " \
 "area.", disk->dev->path);
 }

Processed: Re: Bug#868214: stretch-pu: package grub-installer/1.140+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 confirmed
Bug #868214 [release.debian.org] stretch-pu: package grub-installer/1.140+deb9u1
Added tag(s) confirmed.

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

Bug#868214: stretch-pu: package grub-installer/1.140+deb9u1

[Cyril Brulebois]

Control: tag -1 confirmed

Adam D. Barratt  (2017-07-13):
> Control: tags -1 + confimred
> 
> On 2017-07-13 8:03, Cyril Brulebois wrote:
> >| grub-installer (1.140+deb9u1) stretch; urgency=medium
> >|
> >|   * Apply another patch by Hideki Yamane to fix support for systems with
> >a
> >| large number of disks, since the regression fix in the previous
> >upload
> >| was incomplete (Closes: #839894).
> 
> Please go ahead.

Thanks, on its way.


KiBi.


signature.asc
Description: Digital signature

Processed (with 1 error): Re: Bug#868214: stretch-pu: package grub-installer/1.140+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confimred
Unknown tag/s: confimred.
Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid 
help security upstream pending sarge sarge-ignore experimental d-i confirmed 
ipv6 lfs fixed-in-experimental fixed-upstream l10n newcomer a11y etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore.

Bug #868214 [release.debian.org] stretch-pu: package grub-installer/1.140+deb9u1
Requested to add no tags; doing nothing.

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

Bug#868214: stretch-pu: package grub-installer/1.140+deb9u1

[Adam D. Barratt]

Control: tags -1 + confimred

On 2017-07-13 8:03, Cyril Brulebois wrote:

| grub-installer (1.140+deb9u1) stretch; urgency=medium
|
|   * Apply another patch by Hideki Yamane to fix support for systems 
with a
| large number of disks, since the regression fix in the previous 
upload

| was incomplete (Closes: #839894).


Please go ahead.

Regards,

Adam

Bug#868214: stretch-pu: package grub-installer/1.140+deb9u1

[Cyril Brulebois]

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

Hi,

I'd like to fix a grub-installer issue: support for systems with a large
number of disks was added late in the stretch release cycle, broke a
more general use case, but my regression fix broke the many-discs JBOD
feature we tried to add. Despite long lines, this patch is just fixing a
missing /dev prefix.

Changelog entry:
| grub-installer (1.140+deb9u1) stretch; urgency=medium
| 
|   * Apply another patch by Hideki Yamane to fix support for systems with a
| large number of disks, since the regression fix in the previous upload
| was incomplete (Closes: #839894).
| 
|  -- Cyril Brulebois   Thu, 13 Jul 2017 08:56:40 +0200

(Not applicable for jessie.)

Thanks for considering.


KiBi.
diff -Nru grub-installer-1.140/debian/changelog grub-installer-1.140+deb9u1/debian/changelog
--- grub-installer-1.140/debian/changelog	2017-06-04 02:44:05.0 +0200
+++ grub-installer-1.140+deb9u1/debian/changelog	2017-07-13 08:56:49.0 +0200
@@ -1,3 +1,11 @@
+grub-installer (1.140+deb9u1) stretch; urgency=medium
+
+  * Apply another patch by Hideki Yamane to fix support for systems with a
+large number of disks, since the regression fix in the previous upload
+was incomplete (Closes: #839894).
+
+ -- Cyril Brulebois   Thu, 13 Jul 2017 08:56:40 +0200
+
 grub-installer (1.140) unstable; urgency=medium
 
   * Fix regression in the last upload, which should have added an extra
diff -Nru grub-installer-1.140/grub-installer grub-installer-1.140+deb9u1/grub-installer
--- grub-installer-1.140/grub-installer	2017-06-03 22:49:14.0 +0200
+++ grub-installer-1.140+deb9u1/grub-installer	2017-07-13 08:55:38.0 +0200
@@ -254,7 +254,7 @@
 /dev/mapper)
 	disc_offered_devfs="$bootfs"
 	;;
-/dev/[hsv]d[a-z0-9]|[hsv]d[a-z0-9][a-z]*|/dev/xvd[a-z]|/dev/cciss/c[0-9]d[0-9]*|/dev/ida/c[0-9]d[0-9]*|/dev/rs/c[0-9]d[0-9]*|/dev/mmcblk[0-9]|/dev/nvme[0-9]*n[0-9]*|/dev/ad[0-9]*|/dev/da[0-9]*)
+/dev/[hsv]d[a-z0-9]|/dev/[hsv]d[a-z0-9][a-z]*|/dev/xvd[a-z]|/dev/cciss/c[0-9]d[0-9]*|/dev/ida/c[0-9]d[0-9]*|/dev/rs/c[0-9]d[0-9]*|/dev/mmcblk[0-9]|/dev/nvme[0-9]*n[0-9]*|/dev/ad[0-9]*|/dev/da[0-9]*)
 	disc_offered_devfs="$prefix"
 	;;
 *)

Bug#866692: stretch-pu: package linux-latest/80+deb9u1

[Adam D. Barratt]

On Sat, 2017-07-01 at 16:10 +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> Hi,
> 
> On Sat, 2017-07-01 at 06:07 +0200, Cyril Brulebois wrote:
> > Hi Ben,
> > 
> > Ben Hutchings  (2017-07-01):
> > > src:linux-latest builds meta-packages depending on debug info packages
> > > built from src:linux.  During the stretch release cycle, these were
> > > changed to new-style dbgsym packages and then this change was reverted
> > > to src:linux.  However, the change in src:linux-latest was *not*
> > > reverted, leaving these meta-packages uninstallable.
[...]
> -Section: debug
> -Priority: extra
> 
> Should the -dbg packages not still be in the "debug" section?
> 
> Is it intentional that there are still some dbgsym packages built by
> src:linux? Specifically:
> 
> hyperv-daemons-dbgsym  | 4.9.30-2+deb9u2 | stable-new | amd64, i386
> libcpupower1-dbgsym| 4.9.30-2+deb9u2 | stable-new | amd64, arm64, 
> armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> linux-cpupower-dbgsym  | 4.9.30-2+deb9u2 | stable-new | amd64, i386
> linux-kbuild-4.9-dbgsym| 4.9.30-2+deb9u2 | stable-new | amd64, arm64, 
> armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> linux-perf-4.9-dbgsym  | 4.9.30-2+deb9u2 | stable-new | amd64, arm64, 
> armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> usbip-dbgsym   | 2.0+4.9.30-2+deb9u2 | stable-new | amd64, arm64, 
> armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x

Ping, both on the above questions and the upload.

If this is going to make it into 9.1, it needs to be uploaded _and
through NEW_ by the weekend.

Regards,

Adam