Re: Please block kdevplatform/5.1.1-1

[Pino Toscano]

In data lunedì 10 luglio 2017 09:18:11 CEST, Julien Cristau ha scritto:
> On 07/10/2017 08:29 AM, Pino Toscano wrote:
> > Hi,
> > 
> > can you please block kdevplatform/5.1.1-1 from entering testing
> > tonight?
> > kdevelop is affected by #866354 on armel, and I'd like the whole
> > kdevelop stack (kdevplatform, kdevelop, kdevelop-python, and
> > kdevelop-php) to migrate to testing at the same time.
> > 
> Block hint added (not version specific, so you'll need to prod again to
> get it lifted).

It looks like the kdevelop stack is built on all the release archs now,
can you please remove the block hint to let the packages migrate?

Thanks,
-- 
Pino Toscano

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

Bug#874477: stretch-pu: package ruby-gnome2/3.1.0-1+deb9u1

[dai]

On Sat, Sep 09, 2017 at 05:19:42PM +0200, Julien Cristau wrote:
> Assuming this is tested in stretch to actually be the right
> dependencies, feel free to upload :)

Uploaded. Thanks.
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: PGP signature

Re: KSK-2017 SUAs

[Adam D. Barratt]

On Sat, 2017-09-09 at 19:32 +0100, Adam D. Barratt wrote:
> On Sat, 2017-09-09 at 14:19 -0400, Robert Edmonds wrote:
> > Thanks for writing these! The text mostly looks good to me. The
> > only
> > nit I have is that I would write "The keys used to authenticate the
> > root DNS zone" instead of "The keys used to [sign] the root DNS
> > zone[s]".
> > Technically, there is a chain of signatures and the KSKs do not
> > directly sign the root zone, and there is only a singular root
> > zone.
> 
> Thanks for the review.
> 
> All of the packages are built now and I was hoping to get the SUAs
> released tonight, but we're having a couple of issues with getting
> the
> -updates suites updated so it depends if an ftp-master happens to be
> around in time.

For the record, those have just been released as SUAs 123-126.

Regards,

Adam

Bug#873771: stretch-pu: package evolution/3.22.6-1+deb9u1

[Michael Biebl]

Am 09.09.2017 um 16:45 schrieb Phil Wyett:
> This was originally an NMU after discussion and approval to do it as one with
> Jeremy Bicha and others in #debian-gnome on IRC. It would have gone into
> unstable and moved forward but did not get a sponsor. At this point 3.24 went
> into unstable and Jeremy advised to now make it a stretch-pu, Which it now is.
> 


Thanks for your persistence Phil. I've committed your debdiff to the
evolution SVN and uploaded your changes. I've only dropped the
Non-maintainer upload line.

Regards,
Michael

-- 
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#860966: marked as done (jessie-pu: package eom/1.8.0+dfsg1-4+deb8u1)

[Debian Bug Tracking System]

Your message dated Sat, 9 Sep 2017 21:39:30 +0200
with message-id <20170909193930.cfevxed74ho4f...@betterave.cristau.org>
and subject line Re: Bug#860966: jessie-pu: package eom/1.8.0+dfsg1-4+deb8u1
has caused the Debian Bug report #860966,
regarding jessie-pu: package eom/1.8.0+dfsg1-4+deb8u1
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.)


-- 
860966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu

Please apply this update:

- Add the dependency libgl1-mesa-glx

- Fix new windows don't get focus.

- Don't change file permissions when saving the modified image

All fixed in testing, and this is the fix for jessie

Best Regards
Pablo Barciela

Debian MATE team member.



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
diff -Nru eom-1.8.0+dfsg1/debian/changelog eom-1.8.0+dfsg1/debian/changelog
--- eom-1.8.0+dfsg1/debian/changelog2014-07-01 19:40:50.0 +0200
+++ eom-1.8.0+dfsg1/debian/changelog2017-04-22 02:57:43.0 +0200
@@ -1,3 +1,17 @@
+eom (1.8.0+dfsg1-4+deb8u1) jessie-proposed-updates; urgency=medium
+
+  * debian/control:
++ Add D (eom): libgl1-mesa-glx. (Closes: #844844).
+
+  * debian/patches:
++ Add 0001_fix-new-windows-dont-get-focus.patch. Fix new windows
+  don't get focus. (Closes: #813323).
++ Add 0002_fix-permissions-when-saving-the-modified-image.patch.
+  don't change file permissions when saving the modified image
+  (Closes: #769792).
+
+ -- Pablo Barciela   Sat, 22 Apr 2017 02:57:43 +0200
+
 eom (1.8.0+dfsg1-4) unstable; urgency=medium
 
   * Add librsvg features to Eye of MATE. (Closes: #752282).
diff -Nru eom-1.8.0+dfsg1/debian/control eom-1.8.0+dfsg1/debian/control
--- eom-1.8.0+dfsg1/debian/control  2014-07-01 19:40:30.0 +0200
+++ eom-1.8.0+dfsg1/debian/control  2017-04-22 02:53:57.0 +0200
@@ -47,6 +47,7 @@
  mate-desktop-common,
  mate-icon-theme,
  shared-mime-info,
+ libgl1-mesa-glx,
 Recommends: librsvg2-common
 Breaks: mate-image-viewer (<= 1.0.0-1)
 Replaces: mate-image-viewer (<= 1.0.0-1)
diff -Nru 
eom-1.8.0+dfsg1/debian/patches/0001_fix-new-windows-dont-get-focus.patch 
eom-1.8.0+dfsg1/debian/patches/0001_fix-new-windows-dont-get-focus.patch
--- eom-1.8.0+dfsg1/debian/patches/0001_fix-new-windows-dont-get-focus.patch
1970-01-01 01:00:00.0 +0100
+++ eom-1.8.0+dfsg1/debian/patches/0001_fix-new-windows-dont-get-focus.patch
2017-04-22 02:53:57.0 +0200
@@ -0,0 +1,32 @@
+Description: Fix new windows don't get focus
+Author: vfscanf
+Upstream commit: 
https://github.com/mate-desktop/eom/commit/1b65a062fc01e15c4a461463a055b90d8cb3235e
+--- a/src/eom-application.c
 b/src/eom-application.c
+@@ -279,8 +279,24 @@ eom_application_get_file_window (EomApplication 
*application, GFile *file)
+ static void
+ eom_application_show_window (EomWindow *window, gpointer user_data)
+ {
+-  gtk_window_present_with_time (GTK_WINDOW (window),
+-GPOINTER_TO_UINT (user_data));
++  guint32 timestamp = GPOINTER_TO_UINT (user_data);
++  
++  /* set the proper interaction time on the window.
++   * Fall back to roundtripping to the X server when we
++   * don't have the timestamp, e.g. when launched from
++   * terminal. We also need to make sure that the window
++   * has been realized otherwise it will not work. lame.
++   */
++  if (!gtk_widget_get_realized (GTK_WIDGET (window)))
++  gtk_widget_realize (GTK_WIDGET (window));
++  
++  if (timestamp <= 0)
++  timestamp = gdk_x11_get_server_time (gtk_widget_get_window 
(GTK_WIDGET (window)));
++  
++  gdk_x11_window_set_user_time (gtk_widget_get_window (GTK_WIDGET 
(window)),
++timestamp);
++
++  gtk_window_present (GTK_WINDOW (window));
+ }
+ 
+ /**
diff -Nru 
eom-1.8.0+dfsg1/debian/patches/0002_fix-permissions-when-saving-the-modified-image.patch
 
eom-1.8.0+dfsg1/debian/patches/0002_fix-permissions-when-saving-the-modified-image.patch
--- 

Processed: tagging 872441

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 872441 - moreinfo
Bug #872441 [release.debian.org] stretch-pu: package gsoap/2.8.35-4+deb9u1
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
872441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: KSK-2017 SUAs

[Ondřej Surý]

Adam, thanks for writing these. The texts look good to me with (or even 
without) Robert's changes.



On 9 September 2017 20:19:13 Robert Edmonds  wrote:


Adam D. Barratt wrote:

Hi,

It's not clear whether there will have been a stretch point release
before the KSK rollover in October, but there definitely won't have
been a jessie point release, and in any case we need to update unbound
in the next couple of days (to avoid new installs on stretch having
broken DNSSEC validation for the next month).

Assuming I've not missed any packages that have been updated, we need
four SUAs. I've included draft text for each below - review, comments
and suggestions welcome.


Hi, Adam:

Thanks for writing these! The text mostly looks good to me. The only nit
I have is that I would write "The keys used to authenticate the root DNS
zone" instead of "The keys used to [sign] the root DNS zone[s]".
Technically, there is a chain of signatures and the KSKs do not directly
sign the root zone, and there is only a singular root zone.

--
Robert Edmonds
edmo...@debian.org

Re: KSK-2017 SUAs

[Adam D. Barratt]

On Sat, 2017-09-09 at 14:19 -0400, Robert Edmonds wrote:
> Thanks for writing these! The text mostly looks good to me. The only
> nit I have is that I would write "The keys used to authenticate the
> root DNS zone" instead of "The keys used to [sign] the root DNS
> zone[s]".
> Technically, there is a chain of signatures and the KSKs do not
> directly sign the root zone, and there is only a singular root zone.

Thanks for the review.

All of the packages are built now and I was hoping to get the SUAs
released tonight, but we're having a couple of issues with getting the
-updates suites updated so it depends if an ftp-master happens to be
around in time.

Regards,

Adam

Re: KSK-2017 SUAs

[Robert Edmonds]

Adam D. Barratt wrote:
> Hi,
> 
> It's not clear whether there will have been a stretch point release
> before the KSK rollover in October, but there definitely won't have
> been a jessie point release, and in any case we need to update unbound
> in the next couple of days (to avoid new installs on stretch having
> broken DNSSEC validation for the next month).
> 
> Assuming I've not missed any packages that have been updated, we need
> four SUAs. I've included draft text for each below - review, comments
> and suggestions welcome.

Hi, Adam:

Thanks for writing these! The text mostly looks good to me. The only nit
I have is that I would write "The keys used to authenticate the root DNS
zone" instead of "The keys used to [sign] the root DNS zone[s]".
Technically, there is a chain of signatures and the KSKs do not directly
sign the root zone, and there is only a singular root zone.

-- 
Robert Edmonds
edmo...@debian.org

Bug#868558: All affected packages are manually uloaded

[Andreas Tille]

Hi Dirk,

On Sat, Sep 09, 2017 at 08:56:28AM -0500, Dirk Eddelbuettel wrote:
> I really, really appreciate that.
> 
> In your view, can we / shall we also close the underlying
> 
> https://bugs.debian.org/861333
> 
> which started this?   As I understand you correctly, all identified packages
> should by now have been rebuilt, so R should be free to migrate to testing.

I would have waitet 4 days to enable the rebuild packages getting
permission to enter testing but since you have closed the other bug
now I think there is no real harm done if these will follow the main
R packages some days later.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#872910: transition: scalapack

[Drew Parsons]

On Sat, 2017-09-09 at 13:20 +0200, Emilio Pozuelo Monfort wrote:
> 
> > scalapack 2.0 has been stabilised in experimental, I think it is
> > now
> > ready for release in unstable. I have tested various client
> > packages.
> > The API has not changed, the transition should be no more
> > complicated
> > than updating any configurations with -lblacs-${mpi} to -scalapack-
> > ${mpi} 
> > and any -L references to multiarch if needed. 
> 
> Do you mean source code changes are needed in the build systems to do
> those
> changes? Or are rebuilds enough?

The ones using -lblacs will need source changes. Some scalapack clients
may need source changes to update to multiarch lib paths. I've been in
touch with the Debichem maintainers to let them know the upgrade is
coming.

> > 
> libgfortran4 is in testing, so that's not a blocker indeed. Please go
> ahead.

Thanks Emilio.

Drew

Processed: Bug#874742: stretch-pu: kscreenlocker/5.8.7-1+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 confirmed
Bug #874742 [release.debian.org] stretch-pu: kscreenlocker/5.8.7-1+deb9u1
Added tag(s) confirmed.

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

Bug#874742: stretch-pu: kscreenlocker/5.8.7-1+deb9u1

[Julien Cristau]

Control: tag -1 confirmed

On Mon, Jun 19, 2017 at 11:49:10 +0200, Maximiliano Curia wrote:

> kscreenlocker 5.8.6-2 currently in stretch to 5.8.7-1+deb9u1
> #
> 
> kscreenlocker (5.8.7-1+deb9u1) stretch; urgency=medium
> 
>   * Upload to stretch
> 
>  -- Maximiliano Curia   Mon, 19 Jun 2017 09:27:23 +0200
> 
> kscreenlocker (5.8.7-1) unstable; urgency=medium
> 
>   * New upstream release (5.8.7)
>  + Implement manual focus on click
>Currently only the first created screenlock window gets focus.
>On clicks, no focus events are sent, which makes it impossible to input
>passwords. This patch now makes it possible to focus to a different
>screenlock window (on a different monitor, for example) using a mouse
>button press.
>This should also fix newly created screenlock windows stealing the 
> focus
>of already displayed ones as only the first window gains automatic 
> focus.
>Fixes KDE#348789, KDE#374289
> 
>  -- Maximiliano Curia   Thu, 08 Jun 2017 17:14:31 +0200
> 
> The full debdiff is available in 
> https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/kscreenlocker_5.8.6-2_5.8.7-1+deb9u1.debdiff
> The full upstream gitlog and the diff for the debian packaging are:
> https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/kscreenlocker_5.8.6_5.8.7.upstream.gitlog
> https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/kscreenlocker_5.8.6-2_5.8.7-1+deb9u1.debian.diff
> 
One new German string and entire Basque translation on top of the focus
fix.  I guess that should be ok, assuming the fix is actually needed and
tested in stretch.

Cheers,
Julien

Bug#874741: Bug#865537: stretch-pu: plasma 5.8.7 LTS pre-approval

[Julien Cristau]

Control: tag -1 moreinfo

On Mon, Jun 19, 2017 at 11:49:10 +0200, Maximiliano Curia wrote:

> kde-cli-tools 4:5.8.4-2 currently in stretch to 4:5.8.7-1+deb9u1
> #
> 
> kde-cli-tools (4:5.8.7-1+deb9u1) stretch; urgency=medium
> 
>   * Upload to stretch
> 
>  -- Maximiliano Curia   Mon, 19 Jun 2017 09:11:58 +0200
> 
> kde-cli-tools (4:5.8.7-1) unstable; urgency=medium
> 
>   * New upstream release (5.8.7)
>  + Fix query for available modules
>The old query was bad because two reasons:
> * it didn't use the same query systemsettings uses
> * it didn't use exist so if the first property did not exist the
>   second one was not evaluated since the parser bailed out
>Test Plan: Ran kcmshell5 --list, it's better now
>This fixes KDE#378548
> 
>  -- Maximiliano Curia   Thu, 08 Jun 2017 16:15:10 +0200
> 
> kde-cli-tools (4:5.8.5-1) experimental; urgency=medium
> 
>   * New upstream release (5.8.5).
> 
>  -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:13 +0100
> 
> The full debdiff is available in 
> https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/kde-cli-tools_4:5.8.4-2_4:5.8.7-1+deb9u1.debdiff
> The full upstream gitlog and the diff for the debian packaging are:
> https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/kde-cli-tools_5.8.4_5.8.7.upstream.gitlog
> https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/kde-cli-tools_4:5.8.4-2_4:5.8.7-1+deb9u1.debian.diff
> 
Once again one code fix comes with lots of noisy changes to po files,
and the one I can understand looks wrong:

 #: keditfiletype.cpp:133
-#, fuzzy, kde-format
-#| msgid "File type %1"
+#, kde-format
 msgid "File Type Editor"
-msgstr "Type de fichier « %1 »"
+msgstr "Erreur de type de fichier"

"File Type Editor" doesn't mean the same as "File Type Error".

(also ca@valencia was updated without changing PO-Revision-Date :( )

Cheers,
Julien

Processed: Re: Bug#865537: stretch-pu: plasma 5.8.7 LTS pre-approval

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #874741 [release.debian.org] stretch-pu: kde-cli-tools/4:5.8.7-1+deb9u1
Added tag(s) moreinfo.

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

Processed: Re: Bug#874580: stretch-pu: package waagent/2.2.14-1~deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #874580 [release.debian.org] stretch-pu: package waagent/2.2.14-1~deb9u1
Added tag(s) moreinfo.

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

Bug#874580: stretch-pu: package waagent/2.2.14-1~deb9u1

[Julien Cristau]

Control: tag -1 moreinfo

On Thu, Sep  7, 2017 at 16:10:48 +0200, Bastian Blank wrote:

> The Azure agent provides the provisioning part of the Microsoft Azure 
> platform.
> It is necessary to tell the platform about the state of the systems.  Therefor
> it is part of the "hardware" support for the Azure platform.
> 
> Recent versions of the agent add support for a new revision of the platform
> called Azure Stack.  In a nutshell, Azure Stack is Azure in a box for your 
> home
> (Azure on Premise).  Without this update, Debian can't be used on this new
> platform.  The package itself is only useful on images within the Azure
> plattform and thus this upload will only affect users within Azure. 
> 
Do any of the changes affect the pre-existing Azure platforms?  What's
the regression potential for those users?

(Also, we prefer if the full diff is included in pu bugs directly.)

Cheers,
Julien

Bug#874477: stretch-pu: package ruby-gnome2/3.1.0-1+deb9u1

[Julien Cristau]

Control: tag -1 confirmed

On Wed, Sep  6, 2017 at 20:15:49 +0900, HIGUCHI Daisuke (VDR dai) wrote:

> ruby-gnome2 is GNOME-related bindings for the Ruby language.
> This provides many GNOME-related bindings with many dependencies.
> 
> But some of bindings do not have proper dependencies by packaging problem,
> so users Ruby scripts requiring them are unusable (bug 874365).
> This bug has been already fixed in unstable.
> Attached git-diff fixes this issue for stretch.
> 
Assuming this is tested in stretch to actually be the right
dependencies, feel free to upload :)

Thanks,
Julien

Processed: Re: Bug#874477: stretch-pu: package ruby-gnome2/3.1.0-1+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 confirmed
Bug #874477 [release.debian.org] stretch-pu: package ruby-gnome2/3.1.0-1+deb9u1
Added tag(s) confirmed.

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

Processed: Re: Bug#874389: stretch-pu: package topal/75-2.1+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 confirmed
Bug #874389 [release.debian.org] stretch-pu: package topal/75-2.1+deb9u1
Added tag(s) confirmed.

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

Bug#874389: stretch-pu: package topal/75-2.1+deb9u1

[Julien Cristau]

Control: tag -1 confirmed

On Tue, Sep  5, 2017 at 18:43:07 +0100, Phil Brooke wrote:

> Package: release.debian.org
> Severity: normal
> Tags: stretch
> User: release.debian@packages.debian.org
> Usertags: pu
> 
> Topal was calling sed using only single [ ... ] for the character
> class syntax (bug 870825).  The version of sed in stretch does not
> allow this and topal crashes as a result for some use cases.  A patch
> has been tested with some users directly and a patched version has
> been uploaded to unstable (topal/75.3).
> 
> The debdiff below fixes this problem (and only this problem) for stretch.
> 
Looks sane, feel free to upload.

Cheers,
Julien

Bug#874350: stretch-pu: package mate-power-manager/1.16.2-1+deb9u1

[Julien Cristau]

Control: tag -1 confirmed

On Tue, Sep  5, 2017 at 11:48:55 +0200, Mike Gabriel wrote:

> Package: release.debian.org
> Severity: normal
> Tags: stretch
> User: release.debian@packages.debian.org
> Usertags: pu
> 
> We received notice that mate-power-manager crashes on startup when run on
> top of upower 0.99.5 on notebooks with a backlit keyboard. See #870121 for
> details.
> 
> Knowing that stretch only has upower 0.99.4, the attached simple .debdiff
> resolves this problem, in case people start backporting upower.
> 
With the changelog fixed, feel free to go ahead.

Cheers,
Julien

Processed: Re: Bug#874350: stretch-pu: package mate-power-manager/1.16.2-1+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 confirmed
Bug #874350 [release.debian.org] stretch-pu: package 
mate-power-manager/1.16.2-1+deb9u1
Added tag(s) confirmed.

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

Bug#874254: stretch-pu: package tdbcodbc/1.0.4-2+deb9u1 preapproval

[Julien Cristau]

Control: tag -1 moreinfo

On Mon, Sep  4, 2017 at 15:26:54 +0300, Sergei Golovan wrote:

> Appears that the tdbcodbc package currently in stretch hav a bug introduced by
> the Debian maintainer and me the uploader, which leads to immediate segfault
> on its loading. So the package is unusable at the moment.
> 
> We'd like to propose an update 1.0.4-2+deb9u1 with a fix. The difference
> between 1.0.4-2 and 1.0.4-2+deb9u1 is attached.
> 
The changes to debian/compat and debian/control are neither documented
in the changelog nor appropriate in a stable update.

Is there a bug number for that error?  It looks like this may or may not
be fixed in sid now, but definitely wasn't yesterday.

Cheers,
Julien

Processed: Re: Bug#874254: stretch-pu: package tdbcodbc/1.0.4-2+deb9u1 preapproval

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #874254 [release.debian.org] stretch-pu: package tdbcodbc/1.0.4-2+deb9u1 
preapproval
Added tag(s) moreinfo.

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

Bug#873771: stretch-pu: package evolution/3.22.6-1+deb9u1

[Phil Wyett]

On Sat, 2017-09-09 at 16:30 +0200, Julien Cristau wrote:
> Control: tag -1 confirmed
> 
> On Wed, Aug 30, 2017 at 22:47:06 +0100, Phil Wyett wrote:
> 
> > Please consider for stretch pu. debdiff attached.
> > 
> > A functionality update that fixes severe application hangs when you mouse
> > right
> > click in the email composer window for spell checking or other available
> > task.
> > 
> > Original bug report upstream:
> > 
> > https://bugzilla.gnome.org/show_bug.cgi?id=777086
> > 
> > Debian BTS bug, now closed:
> > 
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871626
> > 
> > Debian RFS, superseded by upload into unstable after 17 day wait and nobody
> > stepped forward to sponsor:
> > 
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872022
> > 
> 
> Sounds fine to me, assuming this is tested in a stretch environment.  Is
> this a NMU or going through the evolution maintainers?
> 
> Cheers,
> Julien


Hi Julien,

This was originally an NMU after discussion and approval to do it as one with
Jeremy Bicha and others in #debian-gnome on IRC. It would have gone into
unstable and moved forward but did not get a sponsor. At this point 3.24 went
into unstable and Jeremy advised to now make it a stretch-pu, Which it now is.

This has been built and tested all versions of debian. I have been running it on
 (and built with) stretch since the fix became available.

Note: I am the original upstream bug reporter and intimate with this bug and
Milan Cha of Red Hat was the dev who helped in reproduction, debug and was the
dev who committed the fix.

Regards

Phil

-- 
*** If this is a mailing list, I am subscribed, no need to CC me.***

Playing the game for the games sake.

Web: https://kathenas.org

Github: https://github.com/kathenas

Twitter: kathenasorg

Instagram: kathenasorg

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

Bug#874198: stretch-pu: package opendkim/2.11.0~alpha-10+deb9u1

[Julien Cristau]

Control: tag -1 moreinfo

On Sun, Sep  3, 2017 at 20:43:55 -0400, Scott Kitterman wrote:

> Thanks to me not understanding some things about systemd service files and
> how they interacted with opendkim (and incomplete testing on my part), the
> package, as released for stretch, is pretty non-functional.
> 
Is there a risk of setups where things currently work in stretch but
won't after these changes?  Or where the update ends up with opendkim
running as root, say because the service file gets updated but
opendkim.conf doesn't?  This might be worth a note in NEWS.Debian to
give people a chance to double check?

Cheers,
Julien

Processed: Re: Bug#874198: stretch-pu: package opendkim/2.11.0~alpha-10+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #874198 [release.debian.org] stretch-pu: package 
opendkim/2.11.0~alpha-10+deb9u1
Added tag(s) moreinfo.

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

Bug#868558: nmu: multiple r-* packages

[Sébastien Villemot]

On Sat, Sep 09, 2017 at 09:39:37AM -0500, Dirk Eddelbuettel wrote:
> 
> On 9 September 2017 at 16:18, Sébastien Villemot wrote:
> | But since I do not want to waste my time, I first need to be sure that you 
> would
> | accept such a patch.
> 
> Re-read
> 
>  http://eddelbuettel.github.io/rcppapt/binnmuAfterR340.html
> 
> and construct (using R and my RcppAPT packages) the set of packages that
> 
>  - are reverse depends of r-base-core in Debian (just over 500+ iirc)
>  - have a src/ directory, ie are Archicture: any 
>  - have .C or .Fortran calls below R/
>  - use dynamic symbol registration 
>  - but ignore whether they have been rebuilt
> 
> so it would differ from my analysis.  I reckon that you would end up with
> maybe 100 to 150 (a guess) packages for which you would need a Breaks:
> declaration.

Thanks for the pointers and for the explanation. Indeed the list will be quite
long, keeping in mind that some packages may appear several times with
architecture qualifiers if version numbers differ across architectures (due for
example to different binNMU version suffixes).

> Now I, as maintainer of r-base, feel that I would not serve my users with the
> added fragility of 100+ breaks statements.
> 
> But you are of course free to create a locally patched package for local
> tests and users.  We know how quickly a local apt repo can be created.  As
> having this functionality seems rather important to you (while I remain more
> than sceptical) I suggest you work on that in such a local package.

Well, I am interested in having this fixed in Debian, not in a local package or
repository. So I understand from your message that I cannot help.

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Bug#868558: nmu: multiple r-* packages

[Dirk Eddelbuettel]

On 9 September 2017 at 16:18, Sébastien Villemot wrote:
| But since I do not want to waste my time, I first need to be sure that you 
would
| accept such a patch.

Re-read

 http://eddelbuettel.github.io/rcppapt/binnmuAfterR340.html

and construct (using R and my RcppAPT packages) the set of packages that

 - are reverse depends of r-base-core in Debian (just over 500+ iirc)
 - have a src/ directory, ie are Archicture: any 
 - have .C or .Fortran calls below R/
 - use dynamic symbol registration 
 - but ignore whether they have been rebuilt

so it would differ from my analysis.  I reckon that you would end up with
maybe 100 to 150 (a guess) packages for which you would need a Breaks:
declaration.

Now I, as maintainer of r-base, feel that I would not serve my users with the
added fragility of 100+ breaks statements.

But you are of course free to create a locally patched package for local
tests and users.  We know how quickly a local apt repo can be created.  As
having this functionality seems rather important to you (while I remain more
than sceptical) I suggest you work on that in such a local package.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Processed: Re: Bug#873771: stretch-pu: package evolution/3.22.6-1+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 confirmed
Bug #873771 [release.debian.org] stretch-pu: package evolution/3.22.6-1+deb9u1
Added tag(s) confirmed.

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

Bug#873771: stretch-pu: package evolution/3.22.6-1+deb9u1

[Julien Cristau]

Control: tag -1 confirmed

On Wed, Aug 30, 2017 at 22:47:06 +0100, Phil Wyett wrote:

> Please consider for stretch pu. debdiff attached.
> 
> A functionality update that fixes severe application hangs when you mouse 
> right
> click in the email composer window for spell checking or other available task.
> 
> Original bug report upstream:
> 
> https://bugzilla.gnome.org/show_bug.cgi?id=777086
> 
> Debian BTS bug, now closed:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871626
> 
> Debian RFS, superseded by upload into unstable after 17 day wait and nobody
> stepped forward to sponsor:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872022
> 
Sounds fine to me, assuming this is tested in a stretch environment.  Is
this a NMU or going through the evolution maintainers?

Cheers,
Julien

Processed: Bug#874740: stretch-pu: breeze-gtk/5.8.7-1+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 confirmed
Bug #874740 [release.debian.org] stretch-pu: breeze-gtk/5.8.7-1+deb9u1
Added tag(s) confirmed.

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

Bug#874740: stretch-pu: breeze-gtk/5.8.7-1+deb9u1

[Julien Cristau]

Control: tag -1 confirmed

Next up, breeze-gtk.

On Mon, Jun 19, 2017 at 11:49:10 +0200, Maximiliano Curia wrote:

> breeze-gtk 5.8.4-1 currently in stretch to 5.8.7-1+deb9u1
> ##
> 
> breeze-gtk (5.8.7-1+deb9u1) stretch; urgency=medium
> 
>   * Upload to stretch
> 
>  -- Maximiliano Curia   Mon, 19 Jun 2017 08:55:23 +0200
> 
> breeze-gtk (5.8.7-1) unstable; urgency=medium
> 
>   * New upstream release (5.8.7)
>  + Set no stepper button for GTK3 scrollbars on gtk >=3.20
>This is a workaround to mitigate broken (huge wide) scrollbars in
>mozilla/Gecko based applications for GTK3 >= 3.20 in versions 52
>onwards.
>Ref: https://bugs.kde.org/show_bug.cgi?id=377008 and
> https://bugzilla.mozilla.org/show_bug.cgi?id=1343802
>The mozilla bug is now 'fixed' and landing in nightlies v55, but may
>continue to affect earlier releases if not brought forward upstream.
>Regardless of any other concern, applying this brings the appearance
>of newer breeze and breeze-gtk scrollars into closer accord.
>KDE#377008
> 
>  -- Maximiliano Curia   Tue, 06 Jun 2017 17:14:40 +0200
> 
> breeze-gtk (5.8.5-1) experimental; urgency=medium
> 
>   * New upstream release (5.8.5).
> 
>  -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:12 +0100
> 
> The full debdiff is available in 
> https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debdiff
> The full upstream gitlog and the diff for the debian packaging are:
> https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4_5.8.7.upstream.gitlog
> https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/breeze-gtk_5.8.4-1_5.8.7-1+deb9u1.debian.diff
> 
Looks fine, feel free to upload this one.

Cheers,
Julien

Bug#874740: stretch-pu: breeze-gtk/5.8.7-1+deb9u1

[Julien Cristau]

On Sat, Sep  9, 2017 at 16:15:39 +0200, Julien Cristau wrote:

> Control: tag -1 confirmed
> 
> Next up, breeze-gtk.
> 
> On Mon, Jun 19, 2017 at 11:49:10 +0200, Maximiliano Curia wrote:
> 
> > breeze-gtk (5.8.7-1+deb9u1) stretch; urgency=medium
> > 
[...]
> Looks fine, feel free to upload this one.
> 
Actually no.  Unstable has 5.8.7-1, so this needs to be a lower version.
Please change to 5.8.7-1~deb9u1 before upload.

Cheers,
Julien

Bug#874739: stretch-pu: bluedevil/4:5.8.7-1+deb9u1

[Julien Cristau]

Control: tag -1 moreinfo

Hi Maxy,

I split this request up into individual per-package bugs.  Let's start
with bluedevil.

On Mon, Jun 19, 2017 at 11:49:10 +0200, Maximiliano Curia wrote:

> bluedevil 4:5.8.4-1 currently in stretch to 4:5.8.7-1+deb9u1
> #
> 
> bluedevil (4:5.8.7-1+deb9u1) stretch; urgency=medium
> 
>   * Upload to stretch.
>   * Document how to run bluedevil in in other DEs (Closes: 781012)
> 
>  -- Maximiliano Curia   Sat, 17 Jun 2017 12:23:14 +0200
> 
> bluedevil (4:5.8.7-1) unstable; urgency=medium
> 
>   * New upstream release (5.8.7).
> + ReceiveFileJob: Don't cancel the request right after accepting it
> 
>   KNotification::closed is emitted also when one of the notification
>   actions was triggered.
> 
>   KDE#376773
> 
>  -- Maximiliano Curia   Sun, 28 May 2017 18:35:52 +0200
> 
> bluedevil (4:5.8.5-1) experimental; urgency=medium
> 
>   * New upstream release (5.8.5).
> 
>  -- Maximiliano Curia   Fri, 30 Dec 2016 18:46:11 +0100
> 
> The full debdiff is available in 
> https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4-1_5.8.7-1+deb9u1.debdiff
> The full upstream gitlog and the diff for the debian packaging are:
> https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_5.8.4_5.8.7.upstream.gitlog
> https://gnuservers.com.ar/~maxy/debian/plasma_5.8.7_stretch-pu/bluedevil_4:5.8.4-1_4:5.8.7-1+deb9u1.debian.diff
> 
A couple of comments:

* Typo in debian/README.Debian, "This is service is provided by the
  bluez-obexd package" has an "is" too many.
* The noise from po files getting regenerated is difficult to handle.
  I see one fix to the german plasma_applet_org.kde.plasma.bluetooth.po,
  addition of a Basque bluedevil.po, a change to the French bluedevil.po
  that I'm not sure is accurate, more changes to the French
  plasma_applet_org.kde.plasma.bluetooth.po, a change to the Brazilian
  bluedevil.po
* The change to src/kded/bluedevil.json is also unreadable :(

One thing I'd like to see is a description of the user impact of the bug
being fixed here.  We're talking an awful lot of diff churn for a single
fix here, so it'd be nice to have some actual justification.

Thanks,
Julien

Processed: Re: stretch-pu: bluedevil/4:5.8.7-1+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #874739 [release.debian.org] stretch-pu: bluedevil/4:5.8.7-1+deb9u1
Added tag(s) moreinfo.

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

Bug#868558: nmu: multiple r-* packages

[Sébastien Villemot]

On Sat, Sep 09, 2017 at 08:53:49AM -0500, Dirk Eddelbuettel wrote:
> On 9 September 2017 at 14:12, Sébastien Villemot wrote:
> | On Sat, Sep 09, 2017 at 06:48:12AM -0500, Dirk Eddelbuettel wrote:
> | > 
> | > On 9 September 2017 at 06:44, Niels Thykier wrote:
> | > | Thanks to Sébastien and Andreas for explaining the issue.
> | > 
> | > Well, was it "explained" ?  They both raised and stressed a hypothetical
> | > issue: That "there might be siutations where a partial upgrade breaks"
> | > 
> | > We don't actually know whether this holds.  This R 3.4.* change was not a
> | > full-fledged ABI change.
> | 
> | I made the following experiment:
> | 
> | - started from a minimal stretch chroot
> | - installed r-base and r-cran-spatial
> | - upgraded r-base to the version from sid (but not r-cran-spatial)
> 
> Come one. That's the situation of EVERY known bug in testing fixed in
> unstable.

No it’s not the same. In the present case, (partially-)upgrading to unstable
*introduces* a bug.

> I am done. This way too dogmatic for my taste. I feel sorry about the users
> who will not get access to current, updated and bug free version of R because
> of this.  A wrong decision.

I don’t want to argue about the soundness of this technical requirement. I am
just interested in having this issue sorted out, since I am a R user and
package maintainer.

As already stated in <20170906144810.f663j3gykjcxo...@villemot.name>, I am
willing to help by generating the correct list of Breaks that, if incorporated
in the debian/control of r-base, would solve the issue.

But since I do not want to waste my time, I first need to be sure that you would
accept such a patch.

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Bug#867814: stretch-pu: package ncurses/6.0+20161126-1+deb9u1

[Sven Joachim]

On 2017-09-09 15:08 +0200, Julien Cristau wrote:

> Do you know what the reverse dependencies of the tic program or library
> are in Debian,

Short answer: I don't know.

Long answer:

The tic library is used by tack and a few programs in ncurses-bin (tic
and its aliases infotocap/captoinfo, infocmp and toe).  I am not aware
of any others, but there might be one or two.

For the programs, infocmp is commonly used by Perl's Term::Cap module
which in turn is used by other Perl modules, so by quite a few
packages.  It only runs infocmp on the terminfo description pointed to
by the TERM variable.  There are 40+ other hits for infocmp on
codesearch.debian.net, I have not really checked them.

Apparently captoinfo and infotocap have no reverse dependencies.  For
tic and toe, it is impossible to check due to their short names. :-(

If you run tic with common arguments as a normal user, it will write to
the ~/.terminfo directory, creating it if necessary.  I don't have this
directory which indicates that third parties don't run tic behind my
back, but then again I have only a fraction of all packages installed.

> and whether any of them commonly process untrusted
> terminfo data (though I know that's not an easy thing to paint as
> black/white)?

If I had known such a program, I would have asked for a DSA after all.
So I don't know, but my knowledge is limited and Debian is large.

Cheers,
   Sven

Processed: Re: Bug#873624: stretch-pu: package yadm/1.06-1+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 confirmed
Bug #873624 [release.debian.org] stretch-pu: package yadm/1.06-1+deb9u1
Added tag(s) confirmed.

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

Bug#873624: stretch-pu: package yadm/1.06-1+deb9u1

[Julien Cristau]

Control: tag -1 confirmed

On Tue, Aug 29, 2017 at 23:50:19 +0800, ChangZhuo Chen wrote:

> Package: release.debian.org
> Severity: normal
> Tags: stretch
> User: release.debian@packages.debian.org
> Usertags: pu
> 
> 
> This pu fix the no-dsa security vulnerability CVE-2017-11353 [0]. The
> diff is attached.
> 
> [0] https://security-tracker.debian.org/tracker/CVE-2017-11353
> 
Assuming this has been tested in a stretch environment, feel free to
upload.

Cheers,
Julien

Bug#868558: All affected packages are manually uloaded

[Dirk Eddelbuettel]

On 9 September 2017 at 15:38, Andreas Tille wrote:
| I hereby closing this bug since all affected packages were
| manually uploaded.

I really, really appreciate that.

In your view, can we / shall we also close the underlying

https://bugs.debian.org/861333

which started this?   As I understand you correctly, all identified packages
should by now have been rebuilt, so R should be free to migrate to testing.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#868558: nmu: multiple r-* packages

[Dirk Eddelbuettel]

On 9 September 2017 at 14:12, Sébastien Villemot wrote:
| On Sat, Sep 09, 2017 at 06:48:12AM -0500, Dirk Eddelbuettel wrote:
| > 
| > On 9 September 2017 at 06:44, Niels Thykier wrote:
| > | Thanks to Sébastien and Andreas for explaining the issue.
| > 
| > Well, was it "explained" ?  They both raised and stressed a hypothetical
| > issue: That "there might be siutations where a partial upgrade breaks"
| > 
| > We don't actually know whether this holds.  This R 3.4.* change was not a
| > full-fledged ABI change.
| 
| I made the following experiment:
| 
| - started from a minimal stretch chroot
| - installed r-base and r-cran-spatial
| - upgraded r-base to the version from sid (but not r-cran-spatial)

Come one. That's the situation of EVERY known bug in testing fixed in unstable.
You explicitly chose to NOT get the fix, to then state it wasn't fixed.

I am waiting for you to also enforce use of 'rm -i' over 'rm'.

I am done. This way too dogmatic for my taste. I feel sorry about the users
who will not get access to current, updated and bug free version of R because
of this.  A wrong decision.

Dirk

| - ran the example described in #861333:
| 
|   $ R -e "library(spatial); example(surf.gls)"
| 
| then I get a crash with the error message "object 'VR_frset' not found".
| 
| So this confirms that partial upgrades are indeed broken.
| 
| Best,
| 
| -- 
| ⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
| ⣾⠁⢠⠒⠀⣿⡁  Debian Developer
| ⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
| ⠈⠳⣄  http://www.debian.org
| [DELETED ATTACHMENT signature.asc, application/pgp-signature]

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#873332: stretch-pu: package pyosmium/2.11.3-1

[Julien Cristau]

Control: tag -1 moreinfo

On Sat, Aug 26, 2017 at 17:43:26 +0200, Bas Couwenberg wrote:

> Upstream has released a new stable release of pyosmium fixing important
> bugs which I'd like to propose for inclusion in the next stable update.
> 
> Kind Regards,
> 
> Bas

> diff -Nru pyosmium-2.11.1/debian/changelog pyosmium-2.11.3/debian/changelog
> --- pyosmium-2.11.1/debian/changelog  2017-05-05 09:51:21.0 +0200
> +++ pyosmium-2.11.3/debian/changelog  2017-08-26 15:10:04.0 +0200
> @@ -1,3 +1,11 @@
> +pyosmium (2.11.3-1) stretch; urgency=medium
> +
> +  * New upstream bugfix release.
> +- handler functions not called when using replication service (#38)
> +- handler functions not called when using Reader instead of file
> +
> + -- Bas Couwenberg   Sat, 26 Aug 2017 15:10:04 +0200
> +
>  pyosmium (2.11.1-1) unstable; urgency=medium
>  
>* New upstream bugfix release.

Can you elaborate on the user or reverse-dependency impact of those
bugs, and what are the risks and mitigations for the changes you're
proposing?  Are there any related automated or manual tests?

Cheers,
Julien

Processed: Re: Bug#873332: stretch-pu: package pyosmium/2.11.3-1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #873332 [release.debian.org] stretch-pu: package pyosmium/2.11.3-1
Added tag(s) moreinfo.

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

Processed: Re: Bug#872991: stretch-pu: package lava-tool/0.21-1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 confirmed
Bug #872991 [release.debian.org] stretch-pu: package lava-tool/0.21-1
Added tag(s) confirmed.

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

Bug#872991: stretch-pu: package lava-tool/0.21-1

[Julien Cristau]

Control: tag -1 confirmed

On Wed, Aug 23, 2017 at 14:37:44 +0100, Neil Williams wrote:

> diff -Nru lava-tool-0.21/debian/changelog lava-tool-0.21/debian/changelog
> --- lava-tool-0.21/debian/changelog   2017-01-19 15:46:04.0 +
> +++ lava-tool-0.21/debian/changelog   2017-08-23 11:55:21.0 +0100
> @@ -1,3 +1,9 @@
> +lava-tool (0.21-1+deb9u1) stretch; urgency=medium
> +
> +  * Add missing dependency: python-simplejson. (Closes: #872782)
> +
> + -- Neil Williams   Wed, 23 Aug 2017 11:55:21 +0100
> +
>  lava-tool (0.21-1) unstable; urgency=medium
>  
>* New upstream release
> diff -Nru lava-tool-0.21/debian/control lava-tool-0.21/debian/control
> --- lava-tool-0.21/debian/control 2017-01-19 15:46:04.0 +
> +++ lava-tool-0.21/debian/control 2017-08-23 11:55:21.0 +0100
> @@ -22,7 +22,7 @@
>  
>  Package: lava-tool
>  Architecture: all
> -Depends: python-setuptools,
> +Depends: python-setuptools, python-simplejson,
>   ${python:Depends}, ${misc:Depends}
>  Recommends: ca-certificates
>  Breaks: lava-dashboard-tool (<< 0.8), lava-scheduler-tool (<< 0.6)
> 
Feel free to upload.

Cheers,
Julien

Bug#872953: stretch-pu: package at-spi2-core/2.22.0-6

[Cyril Brulebois]

Control: tag -1 confirmed

Julien Cristau  (2017-09-09):
> Control: tag -1 d-i
> 
> On Tue, Aug 22, 2017 at 22:43:25 +0200, Samuel Thibault wrote:
> 
> > Blind users have reported that their screen reader, Orca, would
> > sometimes crash when switching from window to window (Bug#872912),
> > affecting both stable and testing.  Upstream released a fix, which was
> > confirmed by Bug#872912 tester to completely fix the issue in sid.  I
> > would thus like to upload the fix to stable, as attached diff shows.
> > 
> Looks fine to me, though should get a kibi-ack due to building a udeb.
> 
> Cyril, please tag this either confirmed or moreinfo when you have a
> chance.

Memory and debtree -R --rdeps-depth=99 seem to agree: dependencies of
the gtk3 udeb, which we don't use yet, so no objections.


KiBi.


signature.asc
Description: PGP signature

Processed: Re: Bug#872953: stretch-pu: package at-spi2-core/2.22.0-6

[Debian Bug Tracking System]

Processing control commands:

> tag -1 confirmed
Bug #872953 [release.debian.org] stretch-pu: package at-spi2-core/2.22.0-6
Added tag(s) confirmed.

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

Processed: Re: Bug#872953: stretch-pu: package at-spi2-core/2.22.0-6

[Debian Bug Tracking System]

Processing control commands:

> tag -1 d-i
Bug #872953 [release.debian.org] stretch-pu: package at-spi2-core/2.22.0-6
Added tag(s) d-i.

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

Bug#872953: stretch-pu: package at-spi2-core/2.22.0-6

[Julien Cristau]

Control: tag -1 d-i

On Tue, Aug 22, 2017 at 22:43:25 +0200, Samuel Thibault wrote:

> Blind users have reported that their screen reader, Orca, would
> sometimes crash when switching from window to window (Bug#872912),
> affecting both stable and testing.  Upstream released a fix, which was
> confirmed by Bug#872912 tester to completely fix the issue in sid.  I
> would thus like to upload the fix to stable, as attached diff shows.
> 
Looks fine to me, though should get a kibi-ack due to building a udeb.

Cyril, please tag this either confirmed or moreinfo when you have a
chance.

Cheers,
Julien

> commit acbc35d8089e0ad597fd4f22b8c745d87ebe33e8
> Author: Samuel Thibault 
> Date:   Tue Aug 22 21:07:39 2017 +0200
> 
> Upstream fix for crash on switching between windows
> 
> patches/accessible_get_parent.diff (Closes: Bug#872912).
> 
> diff --git a/debian/changelog b/debian/changelog
> index 5e0b720..0252734 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,3 +1,10 @@
> +at-spi2-core (2.22.0-6+deb9u1) stretch; urgency=medium
> +
> +  * patches/accessible_get_parent.diff: Upstream fix for crash on switching
> +between windows (Closes: Bug#872912).
> +
> + -- Samuel Thibault   Thu, 10 Aug 2017 21:20:02 +0200
> +
>  at-spi2-core (2.22.0-6) unstable; urgency=medium
>  
>* patches/git-329ef2c4ebcb3aec6dcfcac15357fd583a60c969:
> diff --git a/debian/patches/accessible_get_parent.diff 
> b/debian/patches/accessible_get_parent.diff
> new file mode 100644
> index 000..5c1d035
> --- /dev/null
> +++ b/debian/patches/accessible_get_parent.diff
> @@ -0,0 +1,30 @@
> +commit 2347dad97cd903f6b7fed5a56b738e9ecdf80cac
> +Author: Mike Gorse 
> +Date:   Mon May 8 18:59:40 2017 -0500
> +
> +atspi_accessible_get_parent: move check for NULL AtspiApplication object
> +
> +Now, if we don't have a cached parent, then we always either return NULL
> +or make a D-Bus call. This might make the code more robust, and hoping
> +that it will fix https://bugzilla.gnome.org/show_bug.cgi?id=767074,
> +though in theory it should make no difference there.
> +
> +diff --git a/atspi/atspi-accessible.c b/atspi/atspi-accessible.c
> +index 4547ef7..b84317f 100644
> +--- a/atspi/atspi-accessible.c
>  b/atspi/atspi-accessible.c
> +@@ -268,11 +268,12 @@ atspi_accessible_get_parent (AtspiAccessible *obj, 
> GError **error)
> + {
> +   g_return_val_if_fail (obj != NULL, NULL);
> + 
> +-  if (obj->parent.app &&
> +-  !_atspi_accessible_test_cache (obj, ATSPI_CACHE_PARENT))
> ++  if (!_atspi_accessible_test_cache (obj, ATSPI_CACHE_PARENT))
> +   {
> + DBusMessage *message, *reply;
> + DBusMessageIter iter, iter_variant;
> ++if (!obj->parent.app)
> ++  return NULL;
> + message = dbus_message_new_method_call (obj->parent.app->bus_name,
> + obj->parent.path,
> + DBUS_INTERFACE_PROPERTIES, 
> "Get");
> diff --git a/debian/patches/series b/debian/patches/series
> index 266c41a..eb8e71a 100644
> --- a/debian/patches/series
> +++ b/debian/patches/series
> @@ -3,3 +3,4 @@ revert-register-late
>  register-client-not-too-early
>  git-329ef2c4ebcb3aec6dcfcac15357fd583a60c969
>  git-eba079f3e72e61e6b55d81727ab50c85d505d296
> +accessible_get_parent.diff

Bug#868558: marked as done (nmu: multiple r-* packages)

[Debian Bug Tracking System]

Your message dated Sat, 9 Sep 2017 15:38:01 +0200
with message-id <20170909133801.m6pwpdteiex6g...@an3as.eu>
and subject line All affected packages are manually uloaded
has caused the Debian Bug report #868558,
regarding nmu: multiple r-* packages
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.)


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

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: binnmu
Severity: normal

R 3.4.0, which was released in April, made one subtle breaking change
affecting how (optional) compiled code in contributed package is loaded,
affecting the older two of the three (plus one internal) available
mechanisms:  .C() and .Fortran().  Packages still load and run parts of
their code, they just can no longer access this compiled code---unless
rebuilt. 

This has been discussed in #86133 at https://bugs.debian.org/861333

I have now prepared a fine-grained set of packages requiring a NMU, narrowing
the actual set of required rebuilds down from an unconditional 514 packages
(all reverse depends of r-base-core) to 92 packages meeting all requirements.

  nmu r-bioc-makecdfenv_1.50.0-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
  nmu r-bioc-multtest_2.30.0-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-bioc-edger_3.14.0+dfsg-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
  nmu r-cran-boolnet_2.1.3-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-cran-tikzdevice_0.10-1-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
  nmu r-cran-logspline_2.1.9-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-cran-genabel_1.8-0-1+b1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
  nmu r-cran-lhs_0.14-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-bioc-limma_3.30.8+dfsg-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
  nmu r-cran-coin_1.1-3-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-other-iwrlars_0.9-5-2 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-cran-mnp_2.6-4-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-cran-msm_1.6.4-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-cran-fields_8.10-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-cran-desolve_1.14-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-cran-adephylo_1.1-10-2 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-cran-dosefinding_0.9-15-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
  nmu r-cran-deldir_0.1-12-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-cran-rniftilib_0.0-35.r79-2 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
  nmu r-cran-data.table_1.10.0-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
  nmu r-cran-qtl_1.40-8-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-bioc-preprocesscore_1.36.0-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
  nmu r-cran-contfrac_1.1-10-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-cran-glmnet_2.0-5-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-cran-bitops_1.0-6-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-cran-sp_1:1.2-4-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-cran-spc_1:0.5.3-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-bioc-snpstats_1.24.0+dfsg-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
  nmu r-cran-tgp_2.4-14-2 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-cran-brglm_0.5-9-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-cran-cmprsk_2.2-7-2 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-bioc-affy_1.52.0-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-cran-ncdf4_1.15-1+b2 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-cran-treescape_1.10.18-6 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
  nmu r-bioc-rbgl_1.50.0+dfsg1-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
  nmu r-bioc-rtracklayer_1.34.1-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
  nmu r-cran-hexbin_1.27.1-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-cran-princurve_1.1-12-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
  nmu r-cran-mapproj_1.2-4-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-cran-blockmodeling_0.1.8-1 . ANY . -m 'Rebuild against R 3.4.*, see 
#861333'
  nmu r-cran-hdf5_1.6.10-4+b1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu r-cran-pscl_1.4.9-1 . ANY . -m 'Rebuild against R 3.4.*, see #861333'
  nmu 

Bug#871937: stretch-pu: package monkeysign/2.2.3

[Julien Cristau]

Control: tag -1 moreinfo

On Sat, Aug 12, 2017 at 14:21:11 -0400, Antoine Beaupre wrote:

> Package: release.debian.org
> Severity: normal
> Tags: stretch
> User: release.debian@packages.debian.org
> Usertags: pu
> 
> Hi,
> 
> I am working on a new release of Monkeysign, which I'd like to upload
> in Debian. If it would be just me, I would tag the current HEAD with
> 2.2.4, considering the changes are mostly minor and non-disruptive:
> 
> angela:monkeysign$ git diff 2.2.3 --stat
>  CONTRIBUTING.rst|   9 +-
>  debian/gbp.conf |   2 +-
>  doc/usage.rst   |   4 +
>  monkeysign/cli.py   |  11 +-
>  monkeysign/gpg.py   |  35 ++--
>  monkeysign/gtkui.py |  81 ++---
>  monkeysign/tests/files/7B75921E.asc | 331 
> -
>  monkeysign/tests/test_gpg.py|  21 +--
>  monkeysign/tests/test_ui.py | 147 -
>  monkeysign/ui.py| 168 ---
>  po/nl.po| 725 
> 
>  11 files changed, 1225 insertions(+), 309 deletions(-)
> 
> as you can see, more than half of the diff (725 lines) is just a
> translation file update. The rest is fixes for tests and critical
> bugfixes (although the bugfixes have not been reported directly in the
> Debian BTS, but discovered through my own testing).
> 
> Attached is the actual diff. Should I upload this as 2.2.4 to unstable
> and stable-pu? Or should i minimize this diff to a bare minimum and
> release a more targeted 2.2.4 to stable and a 2.3.0 to unstable?
> 
There's no such thing as uploading the same package version to unstable
and proposed-updates.  Please first get the changes in unstable, with
whatever version number.  Let them sit for a while, and then come back
with a request for stable, with a description and justification of the
changes (which I couldn't see here).

Cheers,
Julien

Processed: Re: Bug#871937: stretch-pu: package monkeysign/2.2.3

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #871937 [release.debian.org] stretch-pu: package monkeysign/2.2.3
Added tag(s) moreinfo.

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

Bug#870513: stretch-pu: package cloud-init/0.7.9-2

[Julien Cristau]

Control: tag -1 moreinfo

On Sat, Aug 26, 2017 at 10:56:16 +0200, Thomas Goirand wrote:

> On 08/06/2017 07:12 PM, Jonathan Wiltshire wrote:
> > Control: tag -1 moreinfo
> > 
> > On Wed, Aug 02, 2017 at 08:45:57PM +0200, Thomas Goirand wrote:
> >> diff -Nru cloud-init-0.7.9/debian/cloud-init.NEWS 
> >> cloud-init-0.7.9/debian/cloud-init.NEWS
> >> --- cloud-init-0.7.9/debian/cloud-init.NEWS1970-01-01 
> >> 01:00:00.0 +0100
> >> +++ cloud-init-0.7.9/debian/cloud-init.NEWS2017-08-02 
> >> 20:28:11.0 +0200
> >> @@ -0,0 +1,8 @@
> >> +cloud-init default behavior from upstream is to manage sources.list for 
> >> Debian,
> >> +adding contrib and non-free by default. This is clearly a bug which we 
> >> have
> >> +fixed. If you need contrib and non-free on your computer running 
> >> cloud-init,
> >> +then please use /etc/apt/sources.list.d facility, instead of the general 
> >> file
> >> +in /etc/apt/sources.list, as we changed the behavior. Our appologies for 
> >> this
> >> +change.
> >> +
> >> + -- Thomas Goirand   Wed, 02 Aug 2017 20:28:11 +0200
> > 
> > Is NEWS the appropriate place for this, or would README or the changelog be
> > better? As it will only be shown when upgrading existing systems, this will
> > simply be noise (those systems will already have a sources.list).
> > 
> > 
> > Thanks,
> 
> Hi,
> 
> I have removed the README.Debian file, and re-uploaded to:

Why?  The contents of that README seem harmless, and Jonathan's question
was about the change in this specific update, and the NEWS file, not
README.Debian.

TBH I'm not sure a behaviour change like this is appropriate for stable,
although it can be argued that people won't deploy it without testing
first.  Is the behaviour configurable somehow?

Cheers,
Julien

Processed: Re: Bug#870513: stretch-pu: package cloud-init/0.7.9-2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #870513 [release.debian.org] stretch-pu: package cloud-init/0.7.9-2
Added tag(s) moreinfo.

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

Processed: Re: Bug#868756: stretch-pu: package ntp/1:4.2.8p10+dfsg-3+deb9u1 (pre-pre-approval)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 confirmed
Bug #868756 [release.debian.org] stretch-pu: package 
ntp/1:4.2.8p10+dfsg-3+deb9u1 (pre-pre-approval)
Added tag(s) confirmed.

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

Bug#868756: stretch-pu: package ntp/1:4.2.8p10+dfsg-3+deb9u1 (pre-pre-approval)

[Julien Cristau]

Control: tag -1 confirmed

On Tue, Aug 15, 2017 at 22:47:23 +0200, Bernhard Schmidt wrote:

> debdiff attached, I tested all the upgrade paths I could think of.
> 
> The debdiff of the resulting binary is
> 
> Files in second .deb but not in first
> -
> -rwxr-xr-x  root/root   /usr/bin/sntp
> 
> Control files: lines which differ (wdiff format)
> 
> Installed-Size: [-1650-] {+1804+}
> Version: [-1:4.2.8p10+dfsg-3-] {+1:4.2.8p10+dfsg-3+deb9u1+}
> 
> Best Regards,
> Bernhard

> diff -Nru ntp-4.2.8p10+dfsg/debian/changelog 
> ntp-4.2.8p10+dfsg/debian/changelog
> --- ntp-4.2.8p10+dfsg/debian/changelog2017-05-07 23:04:52.0 
> +0200
> +++ ntp-4.2.8p10+dfsg/debian/changelog2017-08-08 22:44:37.0 
> +0200
> @@ -1,3 +1,13 @@
> +ntp (1:4.2.8p10+dfsg-3+deb9u1) stretch; urgency=medium
> +
> +  * Build and install /usr/bin/sntp (Closes: #793837)
> +sntp (the successor of ntpdate as general purpose NTP client) has
> +been accidentally included in Jessie, dropped after Jessie,
> +reintroduced too late for Stretch and is now included in Buster.
> +Fix regression by building sntp and shipping it in ntp:any
> +
> + -- Bernhard Schmidt   Tue, 08 Aug 2017 22:44:37 +0200
> +
>  ntp (1:4.2.8p10+dfsg-3) unstable; urgency=medium
>  
>* No-change upload to supersede accidental upload of experimental

Seems ok, feel free to upload.

Cheers,
Julien

Bug#867814: stretch-pu: package ncurses/6.0+20161126-1+deb9u1

[Julien Cristau]

Control: tag -1 moreinfo

On Sun, Jul  9, 2017 at 19:30:55 +0200, Sven Joachim wrote:

> Package: release.debian.org
> Severity: normal
> Tags: stretch
> User: release.debian@packages.debian.org
> Usertags: pu
> 
> Recently a few flaws in the tic program and the tic library have been
> detected: null pointer dereference, buffer overflow, stack smashing, you
> name it.  Six bugs have been reported in the Red Hat bugtracker and four
> CVEs assigned.  Fortunately there are rather few users who would run
> affected programs at all, so it was decided that no DSA would be
> necessary.
> 
Hi Sven,

Do you know what the reverse dependencies of the tic program or library
are in Debian, and whether any of them commonly process untrusted
terminfo data (though I know that's not an easy thing to paint as
black/white)?

Thanks,
Julien

Processed: Re: Bug#867814: stretch-pu: package ncurses/6.0+20161126-1+deb9u1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #867814 [release.debian.org] stretch-pu: package 
ncurses/6.0+20161126-1+deb9u1
Added tag(s) moreinfo.

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

Bug#866753: marked as done (stretch-pu: package gcc-6/6.3.0-18+deb9u1)

[Debian Bug Tracking System]

Your message dated Sat, 9 Sep 2017 15:00:49 +0200
with message-id <20170909130049.7nzyxnsb4cgpn...@betterave.cristau.org>
and subject line Re: Bug#866753: stretch-pu: package gcc-6/6.3.0-18+deb9u1
has caused the Debian Bug report #866753,
regarding stretch-pu: package gcc-6/6.3.0-18+deb9u1
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.)


-- 
866753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Hi,

I'd like to revisit #864597 (upgrade-reports: jessie -> stretch: gnome
fails to upgrade: cycle found while processing triggers) again ...

As I had noted there, adding a Breaks: tzdata-java to gcc-6-base would
have fixed this faulty upgrade path as well.
The fix of reverting the dependency change in ca-certificates-java made
the trigger cycle go away, but reintroduced some upgrade issues where
openjdk-7 was kept installed instead of being upgraded to openjdk-8.

The attached patch adds this Breaks (not yet fixed in sid) as well as a
few libstdc++6 v5 related Breaks (already fixed in sid). I don't know if
doko has more changes that should go to stretch, I "only" care for the
upgrade path issues. (And I won't upload gcc-6 without his explicit Ack,
but preferably he should to the upload).

If this is acceptable for stretch r1, we should get it into s-p-u asap,
s.t. I can test the affected upgrade paths in piuparts to be sure we
don't introduce regressions (but fix the upgrade paths that kept
openjdk-7 installed instead of upgrading to openjdk-8).
Doing upgrade tests from jessie(+pu) to stretch+pu can be done easily
with piuparts.


Andreas
diff -u gcc-6-6.3.0/debian/changelog gcc-6-6.3.0/debian/changelog
--- gcc-6-6.3.0/debian/changelog
+++ gcc-6-6.3.0/debian/changelog
@@ -1,3 +1,13 @@
+gcc-6 (6.3.0-18+deb9u1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * libstdc++6: Add more Breaks to smoothen upgrades from jessie to stretch.
+Closes: #863845, #863745.
+  * gcc-6-base: Add Breaks: tzdata-java to smoothen the openjdk 7 -> 8 upgrade
+path from jessie to stretch. Closes: #863820.
+
+ -- Andreas Beckmann   Sat, 01 Jul 2017 15:00:25 +0200
+
 gcc-6 (6.3.0-18) unstable; urgency=medium
 
   * Update to SVN 20170516 (r248076) from the gcc-6-branch.
diff -u gcc-6-6.3.0/debian/control gcc-6-6.3.0/debian/control
--- gcc-6-6.3.0/debian/control
+++ gcc-6-6.3.0/debian/control
@@ -33,7 +33,7 @@
 Priority: required
 Depends: ${misc:Depends}
 Replaces: ${base:Replaces}
-Breaks: ${base:Breaks}
+Breaks: ${base:Breaks}, tzdata-java
 Description: GCC, the GNU Compiler Collection (base package)
  This package contains files common to all languages and libraries
  contained in the GNU Compiler Collection (GCC).
@@ -1952,7 +1952,7 @@
 Provides: libstdc++6-armel [armel], libstdc++6-armhf [armhf]
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
-Breaks: ${multiarch:breaks}, libantlr-dev (<= 2.7.7+dfsg-6), libaqsis1 (<= 1.8.2-1), libassimp3 (<= 3.0~dfsg-4), blockattack (<= 1.4.1+ds1-2.1+b2), boo (<= 0.9.5~git20110729.r1.202a430-2), libboost-date-time1.54.0, libboost-date-time1.55.0, libcpprest2.4 (<= 2.4.0-2), printer-driver-brlaser (<= 3-3), c++-annotations (<= 10.2.0-1), clustalx (<= 2.1+lgpl-3), libdavix0 (<= 0.4.0-1+b1), libdballe6 (<= 6.8-1), dff (<= 1.3.0+dfsg.1-4.1+b3), libdiet-sed2.8 (<= 2.8.0-1+b3), libdiet-client2.8 (<= 2.8.0-1+b3), libdiet-admin2.8 (<= 2.8.0-1+b3), digikam-private-libs (<= 4:4.4.0-1.1+b2), emscripten (<= 1.22.1-1), ergo (<= 3.4.0-1), fceux (<= 2.2.2+dfsg0-1), flush (<= 0.9.12-3.1), libfreefem++ (<= 3.37.1-1), freeorion (<= 0.4.4+git20150327-2), fslview (<= 4.0.1-4), fwbuilder (<= 5.1.0-4), libgazebo5 (<= 5.0.1+dfsg-2.1), libgetfem4++ (<= 4.2.1~beta1~svn4635~dfsg-3+b1), libgmsh2 (<= 2.9.3+dfsg1-1), gnote (<= 3.16.2-1), gnudatalanguage (<= 0.9.5-2+b2), python-healpy (<= 1.8.1-1+b1), innoextract (<= 
 1.4-1+b1), libinsighttoolkit4.7 (<= 4.7.2-2), libdap17 (<= 3.14.0-2), libdapclient6 (<= 3.14.0-2), libdapserver7 (<= 3.14.0-2), libkolabxml1 (<= 1.1.0-3), libpqxx-4.0 (<= 4.0.1+dfsg-3), libreoffice-core (<= 1:4.4.5-2), librime1 (<= 1.2+dfsg-2), libwibble-dev (<= 1.1-1), lightspark (<= 0.7.2+git20150512-2+b1), libmarisa0 (<= 0.2.4-8), mira-assembler (<= 4.9.5-1), mongodb (<= 1:2.4.14-2), mongodb-server (<= 1:2.4.14-2), ncbi-blast+ (<= 2.2.30-4), libogre-1.8.0 (<= 1.8.0+dfsg1-7+b1), libogre-1.9.0 (<= 1.9.0+dfsg1-4), openscad (<= 2014.03+dfsg-1+b1), libopenwalnut1 (<= 

Bug#866604: marked as done (stretch-pu: package uwsgi-plugin-php)

[Debian Bug Tracking System]

Your message dated Sat, 9 Sep 2017 14:58:03 +0200
with message-id <20170909125803.3zkkl4vceko43...@betterave.cristau.org>
and subject line Re: Bug#866604: stretch-pu: package uwsgi-plugin-php
has caused the Debian Bug report #866604,
regarding stretch-pu: package uwsgi-plugin-php
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.)


-- 
866604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866604
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Dear release team,

I'm hereby asking, if the fix [1] for #853891 [2] would be accepted into
stretch?

Thanks for your work,
Georg


[1] 
https://anonscm.debian.org/cgit/pkg-uwsgi/uwsgi.git/commit/?id=cf89be69ac134ebeb14f453f7d915142d276472d
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864743


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Control: tag -1 wontfix

On Tue, Jul  4, 2017 at 12:18:55 +0200, Georg Faerber wrote:

> Hi KiBi,
> 
> On 17-07-01 02:27:41, Cyril Brulebois wrote:
> > I see a bug number mismatch here.
> 
> You're right, copy/paste error on my side..
> 
> > Anyway, you didn't really tell us what works and what doesn't with the
> > package currently in stretch. It's hard to tell whether it's currently
> > totally broken or whether you just need to install some php package
> > alongside it to satisfy other packages's dependencies.
> > 
> > I'd tend to think this pu request is about the latter, but you really
> > should be explaining why you want a change in stable in the first
> > place…
> 
> Sorry for not doing this upfront: 
> 
> - The package in stretch isn't totally broken, actually it works as
>   expected and does a great job.
> 
> - There is just a (minor) annoyance, so your assumption is correct: I
>   would like to serve IcingaWeb2 via uwsgi, that's why I've created
>   #853891 initially: Currently, in a Nginx powered stack, one has to
>   install packages like php7.0-fpm or the (deprecated) fcgiwrap to
>   satisfy the inter-package dependencies. 
>   
> - Adding 'Provides: php', like the patch [1] does, would solve this
>   issue and wouldn't force people into installing software, which they
>   don't need, in this case at least.
> 
> - I think taking this route is much more clean and "the Debian way" than
>   fiddling around via self-made packages, using equivs or something
>   similar.
> 
> - I've rebuilt the package for myself with the patch attached: It does
>   solve the initial problem and works as expected.
> 
> - I think the risk of regression(s) is quite low, given that the patch
>   only touches two lines of Debian code.
> 
Thanks for the extra explanation, this is much helpful.  Unfortunately I
don't think this meets the bar for updates to stable; I wouldn't mind
seeing this lumped in with a fix for a more severe issue in the future,
but on its own I think the bug is minor enough to not bother.  Sorry.

Cheers,
Julien--- End Message ---

Processed: cloning 865537, block 865537 with -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> clone 865537 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11
Bug #865537 [release.debian.org] stretch-pu: plasma 5.8.7 LTS pre-approval
Bug 865537 cloned as bugs 874739-874749
> block 865537 with -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11
Bug #865537 [release.debian.org] stretch-pu: plasma 5.8.7 LTS pre-approval
865537 was not blocked by any bugs.
865537 was not blocking any bugs.
Added blocking bug(s) of 865537: 874739, 874743, 874748, 874749, 874741, 
874745, 874746, 874742, 874740, 874744, and 874747
> retitle -1 stretch-pu: bluedevil/4:5.8.7-1+deb9u1
Bug #874739 [release.debian.org] stretch-pu: plasma 5.8.7 LTS pre-approval
Changed Bug title to 'stretch-pu: bluedevil/4:5.8.7-1+deb9u1' from 'stretch-pu: 
plasma 5.8.7 LTS pre-approval'.
> retitle -2 stretch-pu: breeze-gtk/5.8.7-1+deb9u1
Bug #874740 [release.debian.org] stretch-pu: plasma 5.8.7 LTS pre-approval
Changed Bug title to 'stretch-pu: breeze-gtk/5.8.7-1+deb9u1' from 'stretch-pu: 
plasma 5.8.7 LTS pre-approval'.
> retitle -3 stretch-pu: kde-cli-tools/4:5.8.7-1+deb9u1
Bug #874741 [release.debian.org] stretch-pu: plasma 5.8.7 LTS pre-approval
Changed Bug title to 'stretch-pu: kde-cli-tools/4:5.8.7-1+deb9u1' from 
'stretch-pu: plasma 5.8.7 LTS pre-approval'.
> retitle -4 stretch-pu: kscreenlocker/5.8.7-1+deb9u1
Bug #874742 [release.debian.org] stretch-pu: plasma 5.8.7 LTS pre-approval
Changed Bug title to 'stretch-pu: kscreenlocker/5.8.7-1+deb9u1' from 
'stretch-pu: plasma 5.8.7 LTS pre-approval'.
> retitle -5 stretch-pu: libksysguard/4:5.8.7-1+deb9u1
Bug #874743 [release.debian.org] stretch-pu: plasma 5.8.7 LTS pre-approval
Changed Bug title to 'stretch-pu: libksysguard/4:5.8.7-1+deb9u1' from 
'stretch-pu: plasma 5.8.7 LTS pre-approval'.
> retitle -6 stretch-pu: plasma-pa/4:5.8.7-1+deb9u1
Bug #874744 [release.debian.org] stretch-pu: plasma 5.8.7 LTS pre-approval
Changed Bug title to 'stretch-pu: plasma-pa/4:5.8.7-1+deb9u1' from 'stretch-pu: 
plasma 5.8.7 LTS pre-approval'.
> retitle -7 stretch-pu: systemsettings/4:5.8.7-1+deb9u1
Bug #874745 [release.debian.org] stretch-pu: plasma 5.8.7 LTS pre-approval
Changed Bug title to 'stretch-pu: systemsettings/4:5.8.7-1+deb9u1' from 
'stretch-pu: plasma 5.8.7 LTS pre-approval'.
> retitle -8 stretch-pu: user-manager/4:5.8.7-1+deb9u1
Bug #874746 [release.debian.org] stretch-pu: plasma 5.8.7 LTS pre-approval
Changed Bug title to 'stretch-pu: user-manager/4:5.8.7-1+deb9u1' from 
'stretch-pu: plasma 5.8.7 LTS pre-approval'.
> retitle -9 stretch-pu: kwin/4:5.8.7-1+deb9u1
Bug #874747 [release.debian.org] stretch-pu: plasma 5.8.7 LTS pre-approval
Changed Bug title to 'stretch-pu: kwin/4:5.8.7-1+deb9u1' from 'stretch-pu: 
plasma 5.8.7 LTS pre-approval'.
> retitle -10 stretch-pu: plasma-workspace/4:5.8.7-1+deb9u1
Bug #874748 [release.debian.org] stretch-pu: plasma 5.8.7 LTS pre-approval
Changed Bug title to 'stretch-pu: plasma-workspace/4:5.8.7-1+deb9u1' from 
'stretch-pu: plasma 5.8.7 LTS pre-approval'.
> retitle -11 stretch-pu: plasma-desktop/4:5.8.7.1-1+deb9u1
Bug #874749 [release.debian.org] stretch-pu: plasma 5.8.7 LTS pre-approval
Changed Bug title to 'stretch-pu: plasma-desktop/4:5.8.7.1-1+deb9u1' from 
'stretch-pu: plasma 5.8.7 LTS pre-approval'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
865537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865537
874739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874739
874740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874740
874741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874741
874742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874742
874743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874743
874744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874744
874745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874745
874746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874746
874747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874747
874748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874748
874749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874749
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#852954: jessie-pu: package libxrender/1:0.9.8-1+deb8u1

[Julien Cristau]

On Sat, Jan 28, 2017 at 15:30:54 +0100, Julien Cristau wrote:

> Package: release.debian.org
> Severity: normal
> Tags: jessie
> User: release.debian@packages.debian.org
> Usertags: pu
> 
> One more.
> 
For the record this is blocked on getting resolution upstream on
https://lists.x.org/pipermail/xorg-devel/2017-January/052247.html
Poked again today, 
https://lists.x.org/pipermail/xorg-devel/2017-September/054604.html

Cheers,
Julien

Bug#869667: stretch-pu: package xkeyboard-config/2.19-1

[Julien Cristau]

Control: tags -1 = stretch d-i confirmed

On Sat, Sep  9, 2017 at 14:12:38 +0200, Cyril Brulebois wrote:

> Adam D. Barratt  (2017-07-30):
> > Control: tags -1 + moreinfo d-i
> > 
> > On Tue, 2017-07-25 at 19:20 +0530, Pirate Praveen wrote:
> > > This fixes serious bug #865316 (all Indic language users were unable to
> > > select their keyboard layouts in stretch introducing a regression. This
> > > was caused by an earlier commit upstream which blacklisted Indic
> > > keyboard layouts, upstream was convinced it was a mistake and reverted
> > > the blacklist. This update applies that patch to debian package so
> > > stretch users can type using Indic language keyboards again).
> > 
> > This looks okay to me, other than this noise in the diff:
> > 
> > --- xkeyboard-config-2.19.orig/debian/files
> > +++ xkeyboard-config-2.19/debian/files
> > @@ -0,0 +1 @@
> > +xkeyboard-config_2.19-1.1_source.buildinfo x11 extra
> > 
> > As the package produces a udeb, this will need an ack from the d-i RM as
> > well; CCing appropriately.
> 
> No objections, thanks.
> 
Feel free to upload with the debian/files issue fixed.

Cheers,
Julien

Processed: Re: Bug#869667: stretch-pu: package xkeyboard-config/2.19-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 = stretch d-i confirmed
Bug #869667 [release.debian.org] stretch-pu: package xkeyboard-config/2.19-1
Added tag(s) confirmed; removed tag(s) moreinfo.

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

Bug#874732: nmu: vdr-plugin-xine_0.9.4-14

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

nmu vdr-plugin-xine_0.9.4-14 . ANY . unstable . -m "Rebuild against vdr 2.3.8."

Transitioning from (virtual) vdr-abi-2.2.0-debian to vdr-abi-2.3.8-debian

This seems to be the only package (still) affected.


Andreas

Bug#869667: stretch-pu: package xkeyboard-config/2.19-1

[Cyril Brulebois]

Adam D. Barratt  (2017-07-30):
> Control: tags -1 + moreinfo d-i
> 
> On Tue, 2017-07-25 at 19:20 +0530, Pirate Praveen wrote:
> > This fixes serious bug #865316 (all Indic language users were unable to
> > select their keyboard layouts in stretch introducing a regression. This
> > was caused by an earlier commit upstream which blacklisted Indic
> > keyboard layouts, upstream was convinced it was a mistake and reverted
> > the blacklist. This update applies that patch to debian package so
> > stretch users can type using Indic language keyboards again).
> 
> This looks okay to me, other than this noise in the diff:
> 
> --- xkeyboard-config-2.19.orig/debian/files
> +++ xkeyboard-config-2.19/debian/files
> @@ -0,0 +1 @@
> +xkeyboard-config_2.19-1.1_source.buildinfo x11 extra
> 
> As the package produces a udeb, this will need an ack from the d-i RM as
> well; CCing appropriately.

No objections, thanks.


KiBi.


signature.asc
Description: PGP signature

Bug#868558: nmu: multiple r-* packages

[Sébastien Villemot]

On Sat, Sep 09, 2017 at 06:48:12AM -0500, Dirk Eddelbuettel wrote:
> 
> On 9 September 2017 at 06:44, Niels Thykier wrote:
> | Thanks to Sébastien and Andreas for explaining the issue.
> 
> Well, was it "explained" ?  They both raised and stressed a hypothetical
> issue: That "there might be siutations where a partial upgrade breaks"
> 
> We don't actually know whether this holds.  This R 3.4.* change was not a
> full-fledged ABI change.

I made the following experiment:

- started from a minimal stretch chroot
- installed r-base and r-cran-spatial
- upgraded r-base to the version from sid (but not r-cran-spatial)
- ran the example described in #861333:

  $ R -e "library(spatial); example(surf.gls)"

then I get a crash with the error message "object 'VR_frset' not found".

So this confirms that partial upgrades are indeed broken.

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Bug#852952: jessie-pu: package libxrandr/2:1.4.2-1+deb8u1

[Julien Cristau]

Control: tag -1 - moreinfo

On Sat, Jan 28, 2017 at 15:10:24 +0100, Julien Cristau wrote:

> Package: release.debian.org
> Severity: normal
> Tags: jessie
> User: release.debian@packages.debian.org
> Usertags: pu
> 
New patch, now with less memory leak.  I've also attached the diff from
the previous one.

Cheers,
Julien
diff --git a/debian/changelog b/debian/changelog
index 0f83cd4..e804fe2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+libxrandr (2:1.4.2-1+deb8u1) jessie; urgency=medium
+
+  * Avoid out of boundary accesses on illegal responses.  Addresses
+CVE-2016-7947 and CVE-2016-7948.
+
+ -- Julien Cristau   Sat, 09 Sep 2017 13:45:59 +0200
+
 libxrandr (2:1.4.2-1) sid; urgency=medium
 
   * New upstream release.
diff --git a/src/XrrConfig.c b/src/XrrConfig.c
index 2f0282b..e68c45a 100644
--- a/src/XrrConfig.c
+++ b/src/XrrConfig.c
@@ -29,6 +29,7 @@
 #include 
 #endif
 
+#include 
 #include 
 #include 
 /* we need to be able to manipulate the Display structure on events */
@@ -272,23 +273,30 @@ static XRRScreenConfiguration *_XRRGetScreenInfo (Display *dpy,
 	rep.rate = 0;
 	rep.nrateEnts = 0;
 }
+if (rep.length < INT_MAX >> 2) {
+	nbytes = (long) rep.length << 2;
 
-nbytes = (long) rep.length << 2;
+	nbytesRead = (long) (rep.nSizes * SIZEOF (xScreenSizes) +
+			((rep.nrateEnts + 1)& ~1) * 2 /* SIZEOF(CARD16) */);
 
-nbytesRead = (long) (rep.nSizes * SIZEOF (xScreenSizes) +
-			 ((rep.nrateEnts + 1)& ~1) * 2 /* SIZEOF (CARD16) */);
+	/*
+	 * first we must compute how much space to allocate for
+	 * randr library's use; we'll allocate the structures in a single
+	 * allocation, on cleanlyness grounds.
+	 */
 
-/*
- * first we must compute how much space to allocate for
- * randr library's use; we'll allocate the structures in a single
- * allocation, on cleanlyness grounds.
- */
+	rbytes = sizeof (XRRScreenConfiguration) +
+	  (rep.nSizes * sizeof (XRRScreenSize) +
+	   rep.nrateEnts * sizeof (int));
 
-rbytes = sizeof (XRRScreenConfiguration) +
-  (rep.nSizes * sizeof (XRRScreenSize) +
-   rep.nrateEnts * sizeof (int));
+	scp = (struct _XRRScreenConfiguration *) Xmalloc(rbytes);
+} else {
+	nbytes = 0;
+	nbytesRead = 0;
+	rbytes = 0;
+	scp = NULL;
+}
 
-scp = (struct _XRRScreenConfiguration *) Xmalloc(rbytes);
 if (scp == NULL) {
 	_XEatData (dpy, (unsigned long) nbytes);
 	return NULL;
diff --git a/src/XrrCrtc.c b/src/XrrCrtc.c
index a704a52..b10bad4 100644
--- a/src/XrrCrtc.c
+++ b/src/XrrCrtc.c
@@ -24,6 +24,7 @@
 #include 
 #endif
 
+#include 
 #include 
 #include 
 /* we need to be able to manipulate the Display structure on events */
@@ -57,22 +58,33 @@ XRRGetCrtcInfo (Display *dpy, XRRScreenResources *resources, RRCrtc crtc)
 	return NULL;
 }
 
-nbytes = (long) rep.length << 2;
+if (rep.length < INT_MAX >> 2)
+{
+	nbytes = (long) rep.length << 2;
 
-nbytesRead = (long) (rep.nOutput * 4 +
-			 rep.nPossibleOutput * 4);
+	nbytesRead = (long) (rep.nOutput * 4 +
+			 rep.nPossibleOutput * 4);
 
-/*
- * first we must compute how much space to allocate for
- * randr library's use; we'll allocate the structures in a single
- * allocation, on cleanlyness grounds.
- */
+	/*
+	 * first we must compute how much space to allocate for
+	 * randr library's use; we'll allocate the structures in a single
+	 * allocation, on cleanlyness grounds.
+	 */
 
-rbytes = (sizeof (XRRCrtcInfo) +
-	  rep.nOutput * sizeof (RROutput) +
-	  rep.nPossibleOutput * sizeof (RROutput));
+	rbytes = (sizeof (XRRCrtcInfo) +
+		  rep.nOutput * sizeof (RROutput) +
+		  rep.nPossibleOutput * sizeof (RROutput));
+
+	xci = (XRRCrtcInfo *) Xmalloc(rbytes);
+}
+else
+{
+	nbytes = 0;
+	nbytesRead = 0;
+	rbytes = 0;
+	xci = NULL;
+}
 
-xci = (XRRCrtcInfo *) Xmalloc(rbytes);
 if (xci == NULL) {
 	_XEatDataWords (dpy, rep.length);
 	UnlockDisplay (dpy);
@@ -194,12 +206,21 @@ XRRGetCrtcGamma (Display *dpy, RRCrtc crtc)
 if (!_XReply (dpy, (xReply *) , 0, xFalse))
 	goto out;
 
-nbytes = (long) rep.length << 2;
+if (rep.length < INT_MAX >> 2)
+{
+	nbytes = (long) rep.length << 2;
 
-/* three channels of CARD16 data */
-nbytesRead = (rep.size * 2 * 3);
+	/* three channels of CARD16 data */
+	nbytesRead = (rep.size * 2 * 3);
 
-crtc_gamma = XRRAllocGamma (rep.size);
+	crtc_gamma = XRRAllocGamma (rep.size);
+}
+else
+{
+	nbytes = 0;
+	nbytesRead = 0;
+	crtc_gamma = NULL;
+}
 
 if (!crtc_gamma)
 {
@@ -357,7 +378,7 @@ XRRGetCrtcTransform (Display	*dpy,
 xRRGetCrtcTransformReq	*req;
 intmajor_version, minor_version;
 XRRCrtcTransformAttributes	*attr;
-char			*extra = NULL, *e;
+char			*extra = NULL, *end = NULL, *e;
 intp;
 
 *attributes = NULL;
@@ -395,9 +416,17 @@ XRRGetCrtcTransform (Display	*dpy,
 	else
 	{
 	int extraBytes = rep.length * 4 - 

Processed: Re: Bug#852952: jessie-pu: package libxrandr/2:1.4.2-1+deb8u1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - moreinfo
Bug #852952 [release.debian.org] jessie-pu: package libxrandr/2:1.4.2-1+deb8u1
Removed tag(s) moreinfo.

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

Bug#868558: nmu: multiple r-* packages

[Dirk Eddelbuettel]

On 9 September 2017 at 06:44, Niels Thykier wrote:
| Thanks to Sébastien and Andreas for explaining the issue.

Well, was it "explained" ?  They both raised and stressed a hypothetical
issue: That "there might be siutations where a partial upgrade breaks"

We don't actually know whether this holds.  This R 3.4.* change was not a
full-fledged ABI change.

| That is fine.  Then (to my knowledge) your only option is an "ABI bump".

I still disagree, for this case.

We will likely need one for anticipated internal R changes by R 3.5.0.

|  Until one of these solutions is applied, this bug is "wontfix" and
| r-base is blocked from migrating to testing.

I think this is a dissservice to our users.

Consider another data point.  It so happens that we have informal backports
for both Debian and Ubuntu at all the CRAN mirrors:

   https://cloud.r-project.org/bin/linux/debian/
   https://cloud.r-project.org/bin/linux/ubuntu/README.html

I am not aware of anything breaking there either.

So I think this is blown out of proportion regarding the _potential_ partial
upgrade issue.  We just don't know if it really applies.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#874570: nmu: php-facedetect_1.1.0+git20160406-3

[Andreas Beckmann]

Control: reopen -1

On 2017-09-09 13:14, Emilio Pozuelo Monfort wrote:
> On 07/09/17 13:13, Andreas Beckmann wrote:

>> nmu php-facedetect_1.1.0+git20160406-3 . ANY . experimental . -m "Rebuild 
>> against opencv 3.2"
> 
> That transition hasn't started in sid yet, so this will be a no-op unless we 
> add
> some --extra-depends on the new opencv in experimental - something we don't
> normally do. So I'm just closing this, and we'll deal with these once the 
> opencv
> transition starts.

php-facedetect/experimental was built against opencv 3.1 which is now
cruft in experimental ...
Since it already B-D libopencv-dev (>= 3), no --extra-depends is needed
and it will switch to 3.2, so please nmu it in experimental.
(I tested the rebuild before filing the bug, since I was not sure what
would happen.)

Thanks

Andreas

Processed: Re: Bug#874570: nmu: php-facedetect_1.1.0+git20160406-3

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #874570 {Done: Emilio Pozuelo Monfort } 
[release.debian.org] nmu: php-facedetect_1.1.0+git20160406-3
Bug reopened
Ignoring request to alter fixed versions of bug #874570 to the same values 
previously set

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

Processed: Re: Bug#872910: transition: scalapack

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#872910: transition: scalapack

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 22/08/17 13:11, Drew Parsons wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> scalapack 2.0 has been stabilised in experimental, I think it is now
> ready for release in unstable. I have tested various client packages.
> The API has not changed, the transition should be no more complicated
> than updating any configurations with -lblacs-${mpi} to -scalapack-${mpi} 
> and any -L references to multiarch if needed. 

Do you mean source code changes are needed in the build systems to do those
changes? Or are rebuilds enough?

> 
> I've marked the Ben file using openmpi, but it would be mpich (default
> mpi) on m68k and sh4. scalapack now provides both openmpi and mpich
> versions on all arches (except sh4 where openmpi does not build). 
> 
> The libgfortran4 transition is currently taking place. I think the
> collision is innocuous but tell me if you think it might be obstructive.

libgfortran4 is in testing, so that's not a blocker indeed. Please go ahead.

Cheers,
Emilio

Bug#874626: marked as done (nmu: gnuradio_3.7.11-1 gr-osmosdr_0.1.4-12)

[Debian Bug Tracking System]

Your message dated Sat, 9 Sep 2017 13:12:33 +0200
with message-id 
and subject line Re: Bug#874626: nmu: gnuradio_3.7.11-1 gr-osmosdr_0.1.4-12
has caused the Debian Bug report #874626,
regarding nmu: gnuradio_3.7.11-1 gr-osmosdr_0.1.4-12
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.)


-- 
874626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874626
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 gnuradio_3.7.11-1 . ANY . unstable . -m "Rebuild for codecs2 transition"
nmu gr-osmosdr_0.1.4-12 . ANY . unstable . -m "Rebuild for soapysdr transition"

(note gr-osmosdr is already at +b1)

Both packages need to be rebuilt against newer libraries to be able to migrate
to testing.

-- System Information:
Debian Release: buster/sid
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable'), (500, 'unstable'), (500, 'testing'), (500, 
'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On 08/09/17 10:25, Raphaël Hertzog wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> nmu gnuradio_3.7.11-1 . ANY . unstable . -m "Rebuild for codecs2 transition"

Scheduled on amd64 only, looks like the maintainer uploaded the binaries built
in a (slightly) outdated chroot.

> nmu gr-osmosdr_0.1.4-12 . ANY . unstable . -m "Rebuild for soapysdr 
> transition"

That's no longer needed afaics.

Cheers,
Emilio--- End Message ---

Bug#874570: marked as done (nmu: php-facedetect_1.1.0+git20160406-3)

[Debian Bug Tracking System]

Your message dated Sat, 9 Sep 2017 13:14:20 +0200
with message-id <25754ffa-ffb3-43d1-28dc-55bf2eb8a...@debian.org>
and subject line Re: Bug#874570: nmu: php-facedetect_1.1.0+git20160406-3
has caused the Debian Bug report #874570,
regarding nmu: php-facedetect_1.1.0+git20160406-3
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.)


-- 
874570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874570
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 php-facedetect_1.1.0+git20160406-3 . ANY . experimental . -m "Rebuild 
against opencv 3.2"

transition in experimental.


Andreas
--- End Message ---
--- Begin Message ---
On 07/09/17 13:13, Andreas Beckmann wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> nmu php-facedetect_1.1.0+git20160406-3 . ANY . experimental . -m "Rebuild 
> against opencv 3.2"

That transition hasn't started in sid yet, so this will be a no-op unless we add
some --extra-depends on the new opencv in experimental - something we don't
normally do. So I'm just closing this, and we'll deal with these once the opencv
transition starts.

Cheers,
Emilio--- End Message ---

Bug#874594: marked as done (nmu: ants_2.2.0-1)

[Debian Bug Tracking System]

Your message dated Sat, 9 Sep 2017 13:04:28 +0200
with message-id <7797ab3f-35e1-3f9b-7ae9-7aeda3156...@debian.org>
and subject line Re: Bug#874594: nmu: ants_2.2.0-1
has caused the Debian Bug report #874594,
regarding nmu: ants_2.2.0-1
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.)


-- 
874594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874594
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 ants_2.2.0-1 . ANY . experimental . -m "Rebuild against 
libinsighttoolkit4.12."

Let's finish that transition in experimental, too.


Andreas
--- End Message ---
--- Begin Message ---
On 07/09/17 20:02, Andreas Beckmann wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> nmu ants_2.2.0-1 . ANY . experimental . -m "Rebuild against 
> libinsighttoolkit4.12."
> 
> Let's finish that transition in experimental, too.

Scheduled.

Emilio--- End Message ---

Bug#874559: marked as done (nmu: pyqt5_5.9+dfsg-1)

[Debian Bug Tracking System]

Your message dated Sat, 9 Sep 2017 13:03:29 +0200
with message-id <730dada1-8de0-26e3-cc05-963c44770...@gmail.com>
and subject line Re: Bug#874559: nmu: pyqt5_5.9+dfsg-1
has caused the Debian Bug report #874559,
regarding nmu: pyqt5_5.9+dfsg-1
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.)


-- 
874559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874559
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 pyqt5_5.9+dfsg-1 . ANY . experimental . -m "Rebuild against 
qtdeclarative-abi-5-9-1."

Let's finish that transition in experimental, too.


Andreas
--- End Message ---
--- Begin Message ---
On 07/09/17 12:11, Andreas Beckmann wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> nmu pyqt5_5.9+dfsg-1 . ANY . experimental . -m "Rebuild against 
> qtdeclarative-abi-5-9-1."
> 
> Let's finish that transition in experimental, too.

Scheduled.

Emilio--- End Message ---

Bug#874564: marked as done (nmu: grok_1.20110708.1-4.2)

[Debian Bug Tracking System]

Your message dated Sat, 9 Sep 2017 13:03:54 +0200
with message-id <58c509ea-3fc1-e3c4-587b-4a7fc2a0f...@debian.org>
and subject line Re: Bug#874564: nmu: grok_1.20110708.1-4.2
has caused the Debian Bug report #874564,
regarding nmu: grok_1.20110708.1-4.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.)


-- 
874564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874564
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 grok_1.20110708.1-4.2 . amd64 . unstable . -m "Rebuild against 
libevent-2.1-6"

NMU uploaded binaries were built against libevent-2.0-5


Andreas
--- End Message ---
--- Begin Message ---
On 07/09/17 12:33, Andreas Beckmann wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> nmu grok_1.20110708.1-4.2 . amd64 . unstable . -m "Rebuild against 
> libevent-2.1-6"
> 
> NMU uploaded binaries were built against libevent-2.0-5

Scheduled.

Emilio--- End Message ---

Bug#874551: marked as done (nmu: biosig4c++_1.4.1-1.1)

[Debian Bug Tracking System]

Your message dated Sat, 9 Sep 2017 12:59:56 +0200
with message-id <371efd25-c639-d505-f7b6-25203dbb8...@debian.org>
and subject line Re: Bug#874551: nmu: biosig4c++_1.4.1-1.1
has caused the Debian Bug report #874551,
regarding nmu: biosig4c++_1.4.1-1.1
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.)


-- 
874551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874551
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 biosig4c++_1.4.1-1.1 . ANY . experimental . -m "Rebuild against liboctave4."

Let's finish another transition in experimental.


Andreas
--- End Message ---
--- Begin Message ---
On 07/09/17 10:57, Andreas Beckmann wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> nmu biosig4c++_1.4.1-1.1 . ANY . experimental . -m "Rebuild against 
> liboctave4."
> 
> Let's finish another transition in experimental.

Done.

Emilio--- End Message ---

Bug#874532: marked as done (nmu: amanda_1:3.4.3-1 openbabel_2.4.1-1)

[Debian Bug Tracking System]

Your message dated Sat, 9 Sep 2017 12:59:06 +0200
with message-id 
and subject line Re: Bug#874532: nmu: amanda_1:3.4.3-1 openbabel_2.4.1-1
has caused the Debian Bug report #874532,
regarding nmu: amanda_1:3.4.3-1 openbabel_2.4.1-1
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.)


-- 
874532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874532
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 amanda_1:3.4.3-1 . ANY . experimental . -m "Rebuild against perl 5.26."
nmu openbabel_2.4.1-1 . ANY . experimental . -m "Rebuild against perl 5.26."

Some more bits for the finished perl transition.


Andreas
--- End Message ---
--- Begin Message ---
On 07/09/17 03:44, Andreas Beckmann wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> nmu amanda_1:3.4.3-1 . ANY . experimental . -m "Rebuild against perl 5.26."
> nmu openbabel_2.4.1-1 . ANY . experimental . -m "Rebuild against perl 5.26."
> 
> Some more bits for the finished perl transition.

Done.

Emilio--- End Message ---

Processed: Re: Bug#849505: transition: nodejs

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 849505 = confirmed
Bug #849505 [release.debian.org] transition: nodejs
Bug #872023 [release.debian.org] transition: nodejs
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
849505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849505
872023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872023
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

KSK-2017 SUAs

[Adam D. Barratt]

Hi,

It's not clear whether there will have been a stretch point release
before the KSK rollover in October, but there definitely won't have
been a jessie point release, and in any case we need to update unbound
in the next couple of days (to avoid new installs on stretch having
broken DNSSEC validation for the next month).

Assuming I've not missed any packages that have been updated, we need
four SUAs. I've included draft text for each below - review, comments
and suggestions welcome.

Package  : dns-root-data
Version  : 2017072601~deb9u1 [stretch]
   2017072601~deb8u1 [jessie]
Importance   : medium

The keys used to sign the root DNS zones for DNSSEC are in the process
of being updated.  Currently two such keys are in use, but from October
11th only the newer key will be in use.

The dns-root-data package includes information about such keys,
allowing other packages to use them for validation. This update ensures
that the newer key is marked as valid, ensuring that records will still
be able to be validated using DNSSEC after the older key is no longer
being used.

If you use dns-root-data then we strongly recommend that you install
this update.

Package  : bind9
Version  : 1:9.10.3.dfsg.P4-12.3+deb9u3 [stretch]
   1:9.9.5.dfsg-9+deb8u14 [jessie]
Importance   : medium

The keys used to sign the root DNS zones for DNSSEC are in the process
of being updated.  Currently two such keys are in use, but from October
11th only the newer key will be in use.

bind9 is a DNS resolver which can use DNSSEC in order to validation the
integrity of responses to DNS queries. This update adds support for the
newer key to bind9, ensuring that DNSSEC validation of the root zones
will continue to operate as expected after the key rollover.

If you use bind9 with DNSSEC validation, we strongly recommend that you
install this update.

Package  : unbound
Version  : 1.6.0-3+deb9u1 [stretch]
   1.4.22-3+deb8u3 [jessie]
Importance   : medium

The keys used to sign the root DNS zones for DNSSEC are in the process
of being updated.  Currently two such keys are in use, but from October
11th only the newer key will be in use.

unbound is a DNS resolver which can use DNSSEC in order to validation
the integrity of responses to DNS queries. This update fixes an issue
which meant that new installs of unbound performed between September
11th and October 11th would not be able to validate the root zones.

The update also forces an upgrade of the dns-root-data package to that
included in SUA--1, ensuring that DNSSEC validation of the root
zones will continue to operate as expected after the key rollover.

If you use unbound with DNSSEC validation, we strongly recommend that
you install this update.

Package  : dnsviz
Version  : 0.6.4-1+deb9u1
Importance   : medium

The keys used to sign the root DNS zones for DNSSEC are in the process
of being updated.  Currently two such keys are in use, but from October
11th only the newer key will be in use.

dnsviz is a set of tools for analysing DNS and DNSSEC behaviour. This
update adds support for the new root key, ensuring that DNSSEC
validation of the root zones will continue to operate as expected after
the key rollover.

The update also includes updates to the DNS root hints file and some
other bug fixes.

If you use the DNSSEC-related features of dnsviz, we strongly recommend
that you install this update.

Regards,

Adam

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: unbound_1.6.0-3+deb9u1_armel.changes
  ACCEPT

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: bind9_9.10.3.dfsg.P4-12.3+deb9u3_armel.changes
  ACCEPT
Processing changes file: erlang-p1-tls_1.0.7-2+deb9u1_armel.changes
  ACCEPT
Processing changes file: 
freerdp_1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2_armel.changes
  ACCEPT

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: unbound_1.6.0-3+deb9u1_armhf.changes
  ACCEPT

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: bind9_9.10.3.dfsg.P4-12.3+deb9u3_armhf.changes
  ACCEPT

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: erlang-p1-tls_1.0.7-2+deb9u1_armhf.changes
  ACCEPT

Bug#868558: nmu: multiple r-* packages

[Niels Thykier]

Control: tags -1 wontfix

Dirk Eddelbuettel:
> 
> On 9 September 2017 at 01:31, Andreas Beckmann wrote:
> | On 2017-09-08 22:49, Dirk Eddelbuettel wrote:
> | > I still maintain that this is a useless "academic" consideration.  If 
> users
> | > want to corrupt their systems by only upgrading one package I will not 
> stop
> | > them.  They can simply fix them by also upgrading the package left behind.
> | 
> | If the package dependencies are not strict enough and allow known broken 
> | package combinations to be installed (without any --force switch), it's 
> | our fault, not the user.
> | 
> | > I aim for 'apt-get dist-upgrade' doing the right thing for them. It will
> | > automate this.
> | 
> | Users running testing or sid are much more likely to perform partial
> | upgrades.
> | Or imagine someone backporting r-base 3.4.1 to stretch ... Breaks will
> | really help here.
> | 
> | But let's get back on the topic.
> | 
> | I think a similar example to what you want to achive is #874413 + 
> | #873791. This is a ABI break in python (some internal module was 
> | removed), which requires a bunch of binNMUs. In addition to this, there 
> | were Breaks added in some core python packages (e.g. libpython2.7-
> | stdlib) against all the packages that used the removed ABI.
> | 
> | [...]
> 

Hi,

Thanks to Sébastien and Andreas for explaining the issue.

> That is madness, and AFAIUI also wrong (as you miss the package which might
> have been in the list, but aren't as they may have gotten upgraded by now).
> 

I appreciate that the Breaks-list is fragile; even more so at this scale
plus it needs to filter on binNMU versions (which can differ between
architectures).  However, we will need a solution for the "partial
upgrades" issue before r-base can migrate.

You may not like the "partial upgrades must work" principle or how it is
implemented, but please keep in mind that we (as a distribution and our
users) rely on it in many areas to ensure that every thing works as
intended.

> I do not plan to add this to r-base-core.  We already waited five month since
> April, what are another seven til the next release of R.
> 
> Dirk
>  
> [...]

That is fine.  Then (to my knowledge) your only option is an "ABI bump".
 Until one of these solutions is applied, this bug is "wontfix" and
r-base is blocked from migrating to testing.

Thanks,
~Niels





signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#868558: nmu: multiple r-* packages

[Debian Bug Tracking System]

Processing control commands:

> tags -1 wontfix
Bug #868558 [release.debian.org] nmu: multiple r-* packages
Added tag(s) wontfix.

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

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: 
freerdp_1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2_armhf.changes
  ACCEPT

NEW changes in oldstable-new

[Debian FTP Masters]

Processing changes file: krb5_1.12.1+dfsg-19+deb8u4_armel.changes
  ACCEPT
Processing changes file: unbound_1.4.22-3+deb8u3_armel.changes
  ACCEPT

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: bind9_9.10.3.dfsg.P4-12.3+deb9u3_mips64el.changes
  ACCEPT
Processing changes file: unbound_1.6.0-3+deb9u1_mipsel.changes
  ACCEPT

NEW changes in oldstable-new

[Debian FTP Masters]

Processing changes file: bind9_9.9.5.dfsg-9+deb8u14_armel.changes
  ACCEPT

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: bind9_9.10.3.dfsg.P4-12.3+deb9u3_mipsel.changes
  ACCEPT
Processing changes file: unbound_1.6.0-3+deb9u1_mips64el.changes
  ACCEPT

NEW changes in oldstable-new

[Debian FTP Masters]

Processing changes file: sudo_1.8.10p3-1+deb8u5_armel.changes
  ACCEPT

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: 
freerdp_1.1.0~git20140921.1.440916e+dfsg1-13+deb9u2_mipsel.changes
  ACCEPT

NEW changes in oldstable-new

[Debian FTP Masters]

Processing changes file: krb5_1.12.1+dfsg-19+deb8u4_armhf.changes
  ACCEPT
Processing changes file: sudo_1.8.10p3-1+deb8u5_armhf.changes
  ACCEPT
Processing changes file: unbound_1.4.22-3+deb8u3_armhf.changes
  ACCEPT