Bug#926299: unblock: busybox/1:1.30.1-4

[Niels Thykier]

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

(X-CC'ed kibi + debian-boot).

Hi kibi/d-i,

The recent upload of busybox fixes the bug #925979 in busybox-udeb.

Should we (RT) unblock it now or do you prefer waiting (as I
understand it there is d-i release coming up).

unblock busybox/1:1.30.1-4

Thanks,
~Niels

Re: gpac_0.7.1+dfsg1-1_amd64.changes is NEW

[Reinhard Tartler]

On 4/2/19 3:08 PM, Niels Thykier wrote:
> Thorsten Alteholz:
>> Hi Reinhard,
>>
>> On Tue, 2 Apr 2019, Reinhard Tartler wrote:
>>> Now about 6 weeks have passed since I've been uploading this package, and
>>> I do have a question: Is there anything wrong with this package?
>>
>> yes, you did an upload to unstable. At this time of the freeze and
>> without a notice from the maintainer/release team this is usually wrong.

I did the upload on 2/15. At the time of the upload, I missed the deadline
for the soft freeze by three days. I don't consider this a large or disruptive
change so I uploaded the package hoping it to get accepted anyways.

Admittedly, I then lost track of this package and realized only earlier today
that it still hadn't made it to unstable. My bad, sorry!

>>> I'm CC'ing the release team to inform them about this upload.
>>
>> Ok, so is this version suitable for buster?
>>
>>   Thorsten
>>
> 
> Note that gpac/0.5.2-426-gc5ad4e4+dfsg5-4.1 is currently in sid,
> recorded as fixing #892526, #902782 and #921969.  Therefore, please hold
> gpac/0.7.1+dfsg1-1 in NEW for now until the sid version can migrate to
> testing.

Ah, that's great news. I didn't realize that Moritz backported the
security fixes to an earlier upstream version. I managed to locate the
git commits but wasn't comfortable with backporting them to version 0.5.2,
not all of them applied cleanly and I lacked the confidence to resolve
the conflicts.

Thanks Moritz for taking care of this!

> 
> As for gpac/0.7.1+dfsg1-1, I cannot find a debdiff for it on the mailing
> list nor the BTS.  Therefore, I have no clue whether it is suitable for
> buster.

The debdiff is unreasonably large (several MiB), there are a *lot* of
unrelated upstream changes included.

I'll spare you to review it.

Given we do have those RC bugs fixed with more targeted patches, I
no longer see the urgency to get 0.7.1 into unstable. Would you agree
with having 0.7.1 in experimental instead? If so, I'd upload it as
0.7.1-2 to experimental.

Let me know if you have any thoughts or concerns on that.

Best,
-rt

Bug#926286: Debdiff

[Scott Talbert]

 diff -Nru wxpython4.0-4.0.4+dfsg/debian/changelog 
wxpython4.0-4.0.4+dfsg/debian/changelog
--- wxpython4.0-4.0.4+dfsg/debian/changelog 2019-01-25 18:19:15.0 
-0500
+++ wxpython4.0-4.0.4+dfsg/debian/changelog 2019-04-01 22:41:28.0 
-0400
@@ -1,3 +1,9 @@
+wxpython4.0 (4.0.4+dfsg-2) unstable; urgency=medium
+
+  * d/patches: Fix FTBFS with SIP 4.19.14 (Closes: #924856)
+
+ -- Scott Talbert   Mon, 01 Apr 2019 22:41:28 -0400
+
 wxpython4.0 (4.0.4+dfsg-1) unstable; urgency=medium
 
   * Update d/copyright and d/watch to use uscan repack mechanism vs. repack.sh
diff -Nru wxpython4.0-4.0.4+dfsg/debian/patches/fix-build-sip-4.19.14-1.patch 
wxpython4.0-4.0.4+dfsg/debian/patches/fix-build-sip-4.19.14-1.patch
--- wxpython4.0-4.0.4+dfsg/debian/patches/fix-build-sip-4.19.14-1.patch 
1969-12-31 19:00:00.0 -0500
+++ wxpython4.0-4.0.4+dfsg/debian/patches/fix-build-sip-4.19.14-1.patch 
2019-03-23 12:14:47.0 -0400
@@ -0,0 +1,132 @@
+From 3636ba3e606e3080942427beb68528f11cfb408e Mon Sep 17 00:00:00 2001
+From: Scott Talbert 
+Date: Fri, 22 Mar 2019 23:17:31 -0400
+Subject: [PATCH 1/2] Fix building with SIP 4.19.14
+
+This commit fixes building Phoenix with SIP 4.19.14.  One of the main changes
+in this release was to add SIP_OVERRIDE, which adds the C++ override keyword
+to method declarations that are intended to override the C++ class that SIP
+is wrapping.  Unfortunately, this exposed a few bugs which caused compile
+errors.  Most of the fixes are to the interface headers.  The two trickier
+fixes were to wxFileConfig and wxRendererNative.
+
+For wxFileConfig, the Save method's second parameter, 'conv', had been ignored.
+This caused the override check to fail.  This was resolved by ignoring the
+auto-generated Save() and adding a manually generated one without the second
+parameter.
+
+For wxRendererNative, the DrawTitleBarBitmap method is actually pure virtual
+in the subclass, so the fix was to ignore it there.  In the subclass
+wxDelegateRendererNative, it is concrete, but only on certain platforms.  This
+was fixed in a similar way by adding a manually generated method that will
+do the right thing on the platforms that support it.
+
+There is one other fix required for SIP 4.19.14: SIP has now added its own
+wrapper for size_t, so it required removing the one in wacky_ints.  This change
+was omitted for now because it should probably wait until Phoenix officially
+moves to 4.19.14.
+---
+ etg/config.py   | 10 +-
+ etg/printfw.py  |  1 -
+ etg/renderer.py | 18 +++---
+ etg/statbox.py  |  2 +-
+ ext/wxWidgets   |  2 +-
+ 5 files changed, 22 insertions(+), 11 deletions(-)
+
+diff --git a/etg/config.py b/etg/config.py
+index 8675e751..299f63b2 100644
+--- a/etg/config.py
 b/etg/config.py
+@@ -179,7 +179,7 @@ def run():
+ c.find('wxFileConfig').findOverload('wxInputStream').find('conv').ignore()
+ ctor = 
c.find('wxFileConfig').findOverload('wxString').find('conv').ignore()
+ #ctor.items.remove(ctor.find('conv'))
+-ctor = c.find('Save').find('conv').ignore()
++c.find('Save').ignore()
+ c.find('GetGlobalFile').ignore()
+ c.find('GetLocalFile').ignore()
+ 
+@@ -188,6 +188,14 @@ def run():
+ c.find('GetFirstEntry').ignore()
+ c.find('GetNextEntry').ignore()
+ 
++c.addCppMethod('bool', 'Save', '(wxOutputStream& os)', 
doc=c.find('Save').briefDoc, body="""\
++#if wxUSE_STREAMS
++return self->Save(*os);
++#else
++wxPyRaiseNotImplemented();
++#endif
++""")
++
+ 
+ 
+ #-
+diff --git a/etg/printfw.py b/etg/printfw.py
+index 0d0500ff..90f5f75a 100644
+--- a/etg/printfw.py
 b/etg/printfw.py
+@@ -61,7 +61,6 @@ def run():
+ c.find('CreateCanvas').isVirtual = True
+ c.find('CreateControlBar').isVirtual = True
+ c.find('Initialize').isVirtual = True
+-c.find('InitializeWithModality').isVirtual = True
+ 
+ 
+ 
+diff --git a/etg/renderer.py b/etg/renderer.py
+index 2319b62d..eea14676 100644
+--- a/etg/renderer.py
 b/etg/renderer.py
+@@ -43,25 +43,29 @@ def run():
+ c.find('GetGeneric').mustHaveApp()
+ c.find('GetDefault').mustHaveApp()
+ c.find('Set').mustHaveApp()
++c.find('DrawTitleBarBitmap').ignore()
++draw_tb_bmp_doc = c.find('DrawTitleBarBitmap').briefDoc
++
++
++c = module.find('wxDelegateRendererNative')
++c.mustHaveApp()
++c.addPrivateCopyCtor()
+ 
+ 
+ #virtual void DrawTitleBarBitmap(wxWindow *win,
+ #wxDC& dc,
+ #const wxRect& rect,
+ #wxTitleBarButton button,
+-#int flags = 0) = 0;
+-c.find('DrawTitleBarBitmap').setCppCode("""\
++#int flags = 0);
++c.addCppMethod('void', 'DrawTitleBarBitmap', '(wxWindow* win, wxDC& dc, 
const wxRect& rect, wxTitleBarButton 

Bug#926288: unblock: open-infrastructure-compute-tools/20190301-lts1-2

[Andreas Beckmann]

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

Please unblock package open-infrastructure-compute-tools

Properly cleanup all alternatives after package removal.

unblock open-infrastructure-compute-tools/20190301-lts1-2

Andreas
diff -Nru open-infrastructure-compute-tools-20190301-lts1/debian/changelog 
open-infrastructure-compute-tools-20190301-lts1/debian/changelog
--- open-infrastructure-compute-tools-20190301-lts1/debian/changelog
2019-03-02 11:51:51.0 +0100
+++ open-infrastructure-compute-tools-20190301-lts1/debian/changelog
2019-03-19 21:24:38.0 +0100
@@ -1,3 +1,12 @@
+open-infrastructure-compute-tools (20190301-lts1-2) unstable; urgency=medium
+
+  * Uploading to sid.
+  * Adding removal of previously forgotten mmdebstrap alternative to not
+leave cruft behind after package removal, thanks to Andreas Beckmann
+ (Closes: #924092).
+
+ -- Daniel Baumann   Tue, 19 Mar 2019 
21:24:38 +0100
+
 open-infrastructure-compute-tools (20190301-lts1-1) unstable; urgency=medium
 
   * Uploading to sid.
diff -Nru 
open-infrastructure-compute-tools-20190301-lts1/debian/open-infrastructure-container-tools.prerm
 
open-infrastructure-compute-tools-20190301-lts1/debian/open-infrastructure-container-tools.prerm
--- 
open-infrastructure-compute-tools-20190301-lts1/debian/open-infrastructure-container-tools.prerm
2019-03-02 11:51:43.0 +0100
+++ 
open-infrastructure-compute-tools-20190301-lts1/debian/open-infrastructure-container-tools.prerm
2019-03-19 21:24:31.0 +0100
@@ -4,6 +4,7 @@
 
 case "${1}" in
remove|upgrade|deconfigure)
+   update-alternatives --quiet --remove container_script 
/usr/share/open-infrastructure/container/scripts/mmdebstrap
update-alternatives --quiet --remove container_script 
/usr/share/open-infrastructure/container/scripts/debootstrap
update-alternatives --quiet --remove container_script 
/usr/share/open-infrastructure/container/scripts/progress-linux
update-alternatives --quiet --remove container_script 
/usr/share/open-infrastructure/container/scripts/debian

Bug#926286: unblock: wxpython4.0/4.0.4+dfsg-2

[Scott Talbert]

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

Please unblock package wxpython4.0

This fixes a wxpython4.0 FTBFS bug (#924856) with SIP 4.19.14 which was 
uploaded in late February.

unblock wxpython4.0/4.0.4+dfsg-2

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-4-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#925576: unblock: python-trustme/0.4.0-2

[Robie Basak]

Hi Paul,

On Sun, Mar 31, 2019 at 10:40:38AM +0200, Paul Gevers wrote:
> The fix doesn't prevent the package from FTBFS. Please check
> https://buildd.debian.org/status/fetch.php?pkg=python-trustme=all=0.4.0-2=1553646768=0

Thanks. I only spotted that after you approved the unblock request. It
did build in sbuild for me locally (after fixing the Build-Depends as
changed in -2), so it must be some difference wrt. the buildds. I will
investigate.


signature.asc
Description: PGP signature

Bug#926283: unblock: thunderbird/1:60.6.1-1

[Carsten Schoenert]

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

Please unblock package thunderbird

The package Thunderbird got the usual update to a new ESR version with
an update to 60.6.1.
This update fixes some known CVEs.

The changes to the packaging can be seen within the following diff output:

diff -puNr thunderbird-60.5.1/debian/changelog 
thunderbird-60.6.1/debian/changelog
--- thunderbird-60.5.1/debian/changelog 2019-02-14 20:01:03.0 +0100
+++ thunderbird-60.6.1/debian/changelog 2019-03-27 18:22:51.0 +0100
@@ -1,3 +1,32 @@
+thunderbird (1:60.6.1-1) unstable; urgency=medium
+
+  [ intrigeri ]
+  * [2013645] d/rules: drop useless usage of dpkg-parsechangelog
+
+  [ Carsten Schoenert ]
+  * [daf1252] New upstream version 60.6.1
+Fixed CVE issues in upstream version 60.6.0 (MFSA 2019-11)
+CVE-2019-9790: Use-after-free when removing in-use DOM elements
+CVE-2019-9791: Type inference is incorrect for constructors entered 
+   through on-stack replacement with IonMonkey
+CVE-2019-9792: IonMonkey leaks JS_OPTIMIZED_OUT magic value to script
+CVE-2019-9793: Improper bounds checks when Spectre mitigations are disabled
+CVE-2019-9794: Command line arguments not discarded during execution
+CVE-2019-9795: Type-confusion in IonMonkey JIT compiler
+CVE-2019-9796: Use-after-free with SMIL animation controller
+CVE-2018-18506: Proxy Auto-Configuration file can define localhost access
+to be proxied
+CVE-2019-9788: Memory safety bugs fixed in Firefox 66, Firefox ESR 60.6,
+   and Thunderbird 60.6
+Fixed CVE issues in upstream version 60.6.1 (MFSA 2019-12)
+CVE-2019-9810: IonMonkey MArraySlice has incorrect alias information
+CVE-2019-9813: Ionmonkey type confusion with __proto__ mutations
+  * [f88a505] rebuild patch queue from patch-queue branch
+added patch:
+fixes/Bug-1526744-find-dupes.py-Calculate-md5-by-chunk.patch
+
+ -- Carsten Schoenert   Wed, 27 Mar 2019 18:22:51 
+0100
+
 thunderbird (1:60.5.1-1) unstable; urgency=medium
 
   [ Alexander Nitsch ]
diff -puNr 
thunderbird-60.5.1/debian/patches/debian-hacks/stop-configure-if-with-system-bz2-was-passed-but-no-.patch
 
thunderbird-60.6.1/debian/patches/debian-hacks/stop-configure-if-with-system-bz2-was-passed-but-no-.patch
--- 
thunderbird-60.5.1/debian/patches/debian-hacks/stop-configure-if-with-system-bz2-was-passed-but-no-.patch
   2019-02-14 19:46:50.0 +0100
+++ 
thunderbird-60.6.1/debian/patches/debian-hacks/stop-configure-if-with-system-bz2-was-passed-but-no-.patch
   2019-03-26 21:53:39.0 +0100
@@ -8,10 +8,10 @@ Subject: stop configure if '--with-syste
  1 file changed, 1 insertion(+), 1 deletion(-)
 
 diff --git a/old-configure.in b/old-configure.in
-index f78c54d..506c08e 100644
+index 8ac71d1..5769ef6 100644
 --- a/old-configure.in
 +++ b/old-configure.in
-@@ -1825,7 +1825,7 @@ if test -z "$BZ2_DIR" -o "$BZ2_DIR" = no; then
+@@ -1826,7 +1826,7 @@ if test -z "$BZ2_DIR" -o "$BZ2_DIR" = no; then
  MOZ_SYSTEM_BZ2=
  else
  AC_CHECK_LIB(bz2, BZ2_bzread, [MOZ_SYSTEM_BZ2=1 MOZ_BZ2_LIBS="-lbz2"],
diff -puNr 
thunderbird-60.5.1/debian/patches/fixes/Bug-1526744-find-dupes.py-Calculate-md5-by-chunk.patch
 
thunderbird-60.6.1/debian/patches/fixes/Bug-1526744-find-dupes.py-Calculate-md5-by-chunk.patch
--- 
thunderbird-60.5.1/debian/patches/fixes/Bug-1526744-find-dupes.py-Calculate-md5-by-chunk.patch
  1970-01-01 01:00:00.0 +0100
+++ 
thunderbird-60.6.1/debian/patches/fixes/Bug-1526744-find-dupes.py-Calculate-md5-by-chunk.patch
  2019-03-26 21:53:39.0 +0100
@@ -0,0 +1,49 @@
+From: Rob Lemley 
+Date: Thu, 21 Feb 2019 15:14:17 -0500
+Subject: Bug 1526744 - find-dupes.py: Calculate md5 by chunk.
+
+Read the file in chunks and use md5.update() rather than reading the entire
+file into RAM and calculating the hash all at once. This prevents out of memory
+errors on build systems with low RAM.
+---
+ toolkit/mozapps/installer/find-dupes.py | 18 ++
+ 1 file changed, 14 insertions(+), 4 deletions(-)
+
+diff --git a/toolkit/mozapps/installer/find-dupes.py 
b/toolkit/mozapps/installer/find-dupes.py
+index 3935b79..0ff7efc 100644
+--- a/toolkit/mozapps/installer/find-dupes.py
 b/toolkit/mozapps/installer/find-dupes.py
+@@ -39,19 +39,29 @@ def is_l10n_file(path):
+ def normalize_path(p):
+ return normalize_osx_path(p)
+ 
++def md5hash_size(fp, chunk_size=1024*10):
++md5 = hashlib.md5()
++size = 0
++while True:
++data = fp.read(chunk_size)
++if not data:
++break
++md5.update(data)
++size += len(data)
++
++return md5.digest(), size
+ 
+ def find_dupes(source, allowed_dupes, bail=True):
+ allowed_dupes = set(allowed_dupes)
+ md5s = OrderedDict()
+ for p, f in UnpackFinder(source):
+-content = f.open().read()
+-m = hashlib.md5(content).digest()
++  

Bug#925321: RM: openjdk-8/8u171-b11-2

[Rene Engelhard]

clone 925321 -1
reassign -1 src:libreoffice
severity -1 important
retitle -1 obsolete openjdk-8 dependency
block 925321 by -1
thanks

Hi,

On Tue, Apr 02, 2019 at 09:08:19PM +0200, Paul Gevers wrote:
> Just for info, from IRC #debian-release today:
> 
> [21:03:39] <_rene_> elbrus: I think you are right (ENOSPC on my rpi
> handling the mail, need to fix it later), looks like remains of hackery
> working around Java broken with stack clash fix on i386
> 
> [21:04:48] <_rene_>   ifeq "$(DEB_HOST_ARCH)" "i386"
> [21:04:48] <_rene_> JAVA_RUNTIME_DEPENDS := openjdk-8-jre (>=
> 8u151-b12-2~) | openjdk-9-jre (>= 9.0.1+11-1~)
> [21:04:51] <_rene_>   else
> [21:04:51] <_rene_> [...]

Jup, will remove.

Regards,

Rene

Processed: Re: Bug#925321: RM: openjdk-8/8u171-b11-2

[Debian Bug Tracking System]

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

> clone 925321 -1
Bug #925321 [release.debian.org] RM: openjdk-8/8u171-b11-2
Bug 925321 cloned as bug 926281
> reassign -1 src:libreoffice
Bug #926281 [release.debian.org] RM: openjdk-8/8u171-b11-2
Bug reassigned from package 'release.debian.org' to 'src:libreoffice'.
Ignoring request to alter found versions of bug #926281 to the same values 
previously set
Ignoring request to alter fixed versions of bug #926281 to the same values 
previously set
> severity -1 important
Bug #926281 [src:libreoffice] RM: openjdk-8/8u171-b11-2
Severity set to 'important' from 'normal'
> retitle -1 obsolete openjdk-8 dependency
Bug #926281 [src:libreoffice] RM: openjdk-8/8u171-b11-2
Changed Bug title to 'obsolete openjdk-8 dependency' from 'RM: 
openjdk-8/8u171-b11-2'.
> block 925321 by -1
Bug #925321 [release.debian.org] RM: openjdk-8/8u171-b11-2
925321 was not blocked by any bugs.
925321 was not blocking any bugs.
Added blocking bug(s) of 925321: 926281
> thanks
Stopping processing here.

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

Apache 2.4.39 in Buster ?

[Xavier]

Hi all,

New Apache 2.4.39 fixes many bugs (including 5 CVEs [1]) with only 2
minor new features. Do you think it is a good idea to upgrade Apache
version in Buster or do you prefer a 2.4.38 with 2.4.39 fixes (means
2.4.39 without ~2 commits) or only CVEs fixes ? I'll wait for your
response before uploading to unstable.

Cheers,
Xavier

[1]: http://www.apache.org/dist/httpd/CHANGES_2.4.39

Bug#926274: nmu: znc-backlog_0.20180824-1

[Andreas Beckmann]

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

nmu znc-backlog_0.20180824-1 . ANY . unstable . -m "Rebuild against znc 
1.7.2-2."

znc-backlog has an extremely tight dependency on znc.


Andreas

Bug#926222: unblock: pbgenomicconsensus/2.3.2-2

[Andreas Tille]

Control: tags -1 - moreinfo

Hi Niels,

I think I addressed your very helpful remarks in the latest upload which
also has a shorter diff to the version in testing (see attachment),

Kind regards and thanks for your work as release manager

   Andreas.

-- 
http://fam-tille.de
diff -Nru pbgenomicconsensus-2.3.2/debian/changelog pbgenomicconsensus-2.3.2/debian/changelog
--- pbgenomicconsensus-2.3.2/debian/changelog	2019-01-11 21:19:28.0 +0100
+++ pbgenomicconsensus-2.3.2/debian/changelog	2019-04-02 21:29:59.0 +0200
@@ -1,3 +1,26 @@
+pbgenomicconsensus (2.3.2-3) unstable; urgency=medium
+
+  * Really fix autopkgtest
+
+ -- Andreas Tille   Tue, 02 Apr 2019 21:29:59 +0200
+
+pbgenomicconsensus (2.3.2-2) unstable; urgency=medium
+
+  [ Afif Elghraoui ]
+  * Remove myself from Uploaders
+
+  [ Andreas Tille ]
+  * Add myself to Uploaders
+  * python-pbgenomicconsensus Depends: python-pbconsensuscore
+  * Test Depends: poa
+  * Ignore some warnings which are breaking test results, remove
+tests that are based on non-existing input data
+  * Move exclusion of tests to upstream Makefile via patch rather than
+in d/rules.  This is needed to run autopkgtest successfully
+Closes: #925909
+
+ -- Andreas Tille   Tue, 02 Apr 2019 11:02:18 +0200
+
 pbgenomicconsensus (2.3.2-1) unstable; urgency=medium
 
   * Team upload
diff -Nru pbgenomicconsensus-2.3.2/debian/control pbgenomicconsensus-2.3.2/debian/control
--- pbgenomicconsensus-2.3.2/debian/control	2019-01-11 21:19:28.0 +0100
+++ pbgenomicconsensus-2.3.2/debian/control	2019-04-02 21:29:59.0 +0200
@@ -1,6 +1,6 @@
 Source: pbgenomicconsensus
 Maintainer: Debian Med Packaging Team 
-Uploaders: Afif Elghraoui 
+Uploaders: Andreas Tille 
 Section: science
 Priority: optional
 Build-Depends: debhelper (>= 12~),
@@ -49,7 +49,8 @@
 Architecture: all
 Section: python
 Depends: ${misc:Depends},
- ${python:Depends}
+ ${python:Depends},
+ python-pbconsensuscore
 Suggests: python-consensuscore2
 Description: Pacific Biosciences variant and consensus caller (Python 2)
  The GenomicConsensus package provides Quiver, Pacific Biosciences'
diff -Nru pbgenomicconsensus-2.3.2/debian/patches/ignore_test_requiring_pbtestdata.patch pbgenomicconsensus-2.3.2/debian/patches/ignore_test_requiring_pbtestdata.patch
--- pbgenomicconsensus-2.3.2/debian/patches/ignore_test_requiring_pbtestdata.patch	1970-01-01 01:00:00.0 +0100
+++ pbgenomicconsensus-2.3.2/debian/patches/ignore_test_requiring_pbtestdata.patch	2019-04-02 21:29:59.0 +0200
@@ -0,0 +1,23 @@
+Description: Test requires https://github.com/PacificBiosciences/PacBioTestData which is not packaged
+Bug-Debian: https://bugs.debian.org/925909
+Author: Andreas Tille 
+Last-Update: Thu, 28 Mar 2019 13:40:21 +0100
+
+--- a/Makefile
 b/Makefile
+@@ -8,7 +8,14 @@ tests: unit-tests basic-tests
+ 
+ unit-tests:
+ 	# Unit tests
+-	py.test --junit-xml=nosetests.xml tests/unit
++	# ignore tests requiring https://github.com/PacificBiosciences/PacBioTestData which is not packaged
++	set -e ; \
++	TMPDIR=$$(mktemp -d /tmp/test_ignore_XX) ; \
++	mv tests/unit/test_tool_contract.py $${TMPDIR} ; \
++	py.test --junit-xml=nosetests.xml tests/unit ; \
++	rm -rf tests/unit/__pycache__ ; \
++	mv $${TMPDIR}/* tests/unit ; \
++	rmdir $${TMPDIR}
+ 
+ # Note: We need at least cram/0.7 for '--xunit-file'
+ # Note: The cram tests often need h5py.
diff -Nru pbgenomicconsensus-2.3.2/debian/patches/ignore_test_using_local_data.patch pbgenomicconsensus-2.3.2/debian/patches/ignore_test_using_local_data.patch
--- pbgenomicconsensus-2.3.2/debian/patches/ignore_test_using_local_data.patch	1970-01-01 01:00:00.0 +0100
+++ pbgenomicconsensus-2.3.2/debian/patches/ignore_test_using_local_data.patch	2019-04-02 21:29:59.0 +0200
@@ -0,0 +1,29 @@
+Description: Ignore tests that are based on non-existing input data that probably reside on upstreams local host
+Bug-Debian: https://bugs.debian.org/925909
+Author: Andreas Tille 
+Last-Update: Thu, 28 Mar 2019 13:40:21 +0100
+
+--- a/Makefile
 b/Makefile
+@@ -22,8 +22,19 @@ unit-tests:
+ 
+ basic-tests:
+ 	# End-to-end tests
+-	# One of these now needs mummer and exonerate.
+-	PATH=`pwd`:$(PATH) cram --verbose --xunit-file=gc-cram.xml `ls tests/cram/*.t | grep -v -e arrow -e bad_input`
++	# some tests require a input files on a local mount of upstream
++	# The test poa-all4mer.t contains a wrong syntax in calling poa - no idea how to fix this thus ignoring the test
++	set -e ; \
++	TMPDIR=$$(mktemp -d /tmp/test_ignore_XX) ; \
++	for nt in $$(grep -Rl /mnt/secondary/Share/Quiver/ tests/*) ; do \
++	mkdir -p $${TMPDIR}/$$(dirname $${nt}) ; \
++	mv $${nt} $${TMPDIR}/$$(dirname $${nt}) ; \
++	done ; \
++	mkdir -p $${TMPDIR}/tests/cram ; \
++	mv tests/cram/poa-all4mer.t $${TMPDIR}/tests/cram ; \
++	PATH=`pwd`:$(PATH) cram --verbose --xunit-file=gc-cram.xml `ls tests/cram/*.t | grep -v -e arrow -e bad_input` ; \
++	cp -a -v 

Processed: Re: Bug#926222: unblock: pbgenomicconsensus/2.3.2-2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - moreinfo
Bug #926222 [release.debian.org] unblock: pbgenomicconsensus/2.3.2-2
Removed tag(s) moreinfo.

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

Bug#926271: unblock: perl/5.28.1-6

[Niko Tyni]

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

Please unblock package perl.

The version in sid fixes autopkgtest failures on arm64, ppc64 and s390x
(which were due to faulty tests) and has no runtime changes.

Changes:
 perl (5.28.1-6) unstable; urgency=medium
 .
   * Fix NDBM autopkgtests by recreating necessary hardlinks at test time
 (Closes: #925179)
   * Update patch metadata for the POSIX::mblen() fix.

The binary changes in the debdiff are just removals of the now unnecessary
test files (NDBM *.dir, replaced by hardlinks generated at test time.)

unblock perl/5.28.1-6

Many thanks for your work on the release, much appreciated!

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru perl-5.28.1/debian/changelog perl-5.28.1/debian/changelog
--- perl-5.28.1/debian/changelog2019-03-16 16:02:28.0 +0200
+++ perl-5.28.1/debian/changelog2019-03-31 14:51:22.0 +0300
@@ -1,3 +1,11 @@
+perl (5.28.1-6) unstable; urgency=medium
+
+  * Fix NDBM autopkgtests by recreating necessary hardlinks at test time
+(Closes: #925179)
+  * Update patch metadata for the POSIX::mblen() fix.
+
+ -- Niko Tyni   Sun, 31 Mar 2019 14:51:22 +0300
+
 perl (5.28.1-5) unstable; urgency=medium
 
   * Patch perlbug to use "editor" as the default editor. (Closes: #922609)
diff -Nru perl-5.28.1/debian/patches/fixes/posix-mbrlen.diff 
perl-5.28.1/debian/patches/fixes/posix-mbrlen.diff
--- perl-5.28.1/debian/patches/fixes/posix-mbrlen.diff  2019-03-16 
16:02:28.0 +0200
+++ perl-5.28.1/debian/patches/fixes/posix-mbrlen.diff  2019-03-31 
14:42:43.0 +0300
@@ -1,4 +1,4 @@
-From 90d15e4f19daccb9ae8e917cd79d27c7bf368c86 Mon Sep 17 00:00:00 2001
+From c13d09cc35d629482559ef95109cb92e09f6a8e8 Mon Sep 17 00:00:00 2001
 From: Niko Tyni 
 Date: Sun, 10 Mar 2019 19:40:42 +0200
 Subject: Fix POSIX::mblen mbstate_t initialization on threaded perls with
@@ -44,6 +44,7 @@
 Bug-Ubuntu: https://bugs.launchpad.net/bugs/1818953
 Bug-Debian: https://bugs.debian.org/924517
 Patch-Name: fixes/posix-mbrlen.diff
+Origin: backport, 
https://perl5.git.perl.org/perl.git/commit/25d7b7aa379d33ce2e8fe3e2bef4206b35739bc5
 ---
  MANIFEST   |  1 +
  ext/POSIX/POSIX.xs |  2 +-
diff -Nru perl-5.28.1/debian/source/include-binaries 
perl-5.28.1/debian/source/include-binaries
--- perl-5.28.1/debian/source/include-binaries  2019-03-16 16:02:28.0 
+0200
+++ perl-5.28.1/debian/source/include-binaries  2019-03-31 14:42:57.0 
+0300
@@ -3,14 +3,12 @@
 debian/tests/data/jessie.db
 debian/tests/data/amd64/jessie.gdbm
 debian/tests/data/jessie.gz
-debian/tests/data/amd64/jessie-ndbm.dir
 debian/tests/data/amd64/jessie-ndbm.pag
 debian/tests/data/jessie.storable
 debian/tests/data/stretch.bz2
 debian/tests/data/stretch.db
 debian/tests/data/amd64/stretch.gdbm
 debian/tests/data/stretch.gz
-debian/tests/data/amd64/stretch-ndbm.dir
 debian/tests/data/amd64/stretch-ndbm.pag
 debian/tests/data/stretch.storable
 debian/tests/data/buster.bz2
@@ -27,7 +25,6 @@
 debian/tests/data/arm64/buster-ndbm.dir
 debian/tests/data/arm64/buster-ndbm.pag
 debian/tests/data/arm64/stretch.gdbm
-debian/tests/data/arm64/stretch-ndbm.dir
 debian/tests/data/arm64/stretch-ndbm.pag
 debian/tests/data/armhf/buster.gdbm
 debian/tests/data/armhf/buster-ndbm.dir
@@ -36,11 +33,9 @@
 debian/tests/data/ppc64el/buster-ndbm.dir
 debian/tests/data/ppc64el/buster-ndbm.pag
 debian/tests/data/ppc64el/stretch.gdbm
-debian/tests/data/ppc64el/stretch-ndbm.dir
 debian/tests/data/ppc64el/stretch-ndbm.pag
 debian/tests/data/s390x/buster.gdbm
 debian/tests/data/s390x/buster-ndbm.dir
 debian/tests/data/s390x/buster-ndbm.pag
 debian/tests/data/s390x/stretch.gdbm
-debian/tests/data/s390x/stretch-ndbm.dir
 debian/tests/data/s390x/stretch-ndbm.pag
Binary files 
/tmp/gywYCdxNpu/perl-5.28.1/debian/tests/data/amd64/jessie-ndbm.dir and 
/tmp/SK1ctzlX4m/perl-5.28.1/debian/tests/data/amd64/jessie-ndbm.dir differ
Binary files 
/tmp/gywYCdxNpu/perl-5.28.1/debian/tests/data/amd64/stretch-ndbm.dir and 
/tmp/SK1ctzlX4m/perl-5.28.1/debian/tests/data/amd64/stretch-ndbm.dir differ
Binary files 
/tmp/gywYCdxNpu/perl-5.28.1/debian/tests/data/arm64/stretch-ndbm.dir and 
/tmp/SK1ctzlX4m/perl-5.28.1/debian/tests/data/arm64/stretch-ndbm.dir differ
Binary files 
/tmp/gywYCdxNpu/perl-5.28.1/debian/tests/data/ppc64el/stretch-ndbm.dir and 
/tmp/SK1ctzlX4m/perl-5.28.1/debian/tests/data/ppc64el/stretch-ndbm.dir differ
Binary files 
/tmp/gywYCdxNpu/perl-5.28.1/debian/tests/data/s390x/stretch-ndbm.dir and 
/tmp/SK1ctzlX4m/perl-5.28.1/debian/tests/data/s390x/stretch-ndbm.dir differ
diff -Nru 

Bug#926270: unblock: nvidia-graphics-drivers/410.104-3

[Andreas Beckmann]

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

Please unblock package nvidia-graphics-drivers

Hi,

I recently realized that I can improve the nvidia-graphics-drivers
upgrade path from stretch to buster on the no longer supported
32-bit architectures (i386, armhf) by reintroducing some (meta-)packages
as transitional packages depending on the corresponding packages from
the (still 32-bit supporting) 390xx legacy driver.

This request is for nvidia-graphics-drivers.

The diff looks a bit large since several files had to be renamed to
include the '.amd64' arch limitation in their name and the README and
NEWS needed to get a basename that is independent of a package name.
The NEWS and README diff seems to be repeated due to symlinks being used
in the package.
The effective changes are only on debian/{control,rules,rules.defs}.

 changelog|   17 ++
 control  |   77 ++-
 control.in   |   77 ++-
 control.md5sum   |8 -
 control.no-driver|4 
 nvidia-driver.NEWS   |  112 
 nvidia-driver.NEWS.amd64 |  112 
 nvidia-driver.README.Debian.amd64.in |  154 +++
 nvidia-driver.README.Debian.in   |  154 ---
 nvidia-driver.docs   |3 
 nvidia-driver.docs.amd64 |3 
 nvidia-driver.lintian-overrides  |3 
 nvidia-smi.install.amd64.in  |2 
 nvidia-smi.install.in|2 
 nvidia-smi.lintian-overrides.in  |   16 +-
 nvidia.NEWS  |  112 
 nvidia.README.Debian.in  |  154 +++
 rules|   13 +
 rules.defs   |2 
 xserver-xorg-video-nvidia.NEWS   |  112 
 xserver-xorg-video-nvidia.NEWS.amd64 |  112 
 xserver-xorg-video-nvidia.README.Debian.amd64.in |  154 +++
 xserver-xorg-video-nvidia.README.Debian.in   |  154 ---
 xserver-xorg-video-nvidia.docs   |2 
 xserver-xorg-video-nvidia.docs.amd64 |2 
 xserver-xorg-video-nvidia.install.amd64.in   |4 
 xserver-xorg-video-nvidia.install.in |4 
 xserver-xorg-video-nvidia.links.amd64.in |1 
 xserver-xorg-video-nvidia.links.in   |1 
 xserver-xorg-video-nvidia.lintian-overrides.in   |   12 +
 xserver-xorg-video-nvidia.postinst.amd64.in  |   22 +++
 xserver-xorg-video-nvidia.postinst.in|   22 ---
 xserver-xorg-video-nvidia.postrm |   29 
 xserver-xorg-video-nvidia.postrm.amd64   |   29 
 34 files changed, 1000 insertions(+), 685 deletions(-)


unblock nvidia-graphics-drivers/410.104-3

Andreas


nvidia-graphics-drivers_410.104-3.dsc.diff.gz
Description: application/gzip

Bug#925321: RM: openjdk-8/8u171-b11-2

[Paul Gevers]

Just for info, from IRC #debian-release today:

[21:03:39] <_rene_> elbrus: I think you are right (ENOSPC on my rpi
handling the mail, need to fix it later), looks like remains of hackery
working around Java broken with stack clash fix on i386

[21:04:48] <_rene_>   ifeq "$(DEB_HOST_ARCH)" "i386"
[21:04:48] <_rene_> JAVA_RUNTIME_DEPENDS := openjdk-8-jre (>=
8u151-b12-2~) | openjdk-9-jre (>= 9.0.1+11-1~)
[21:04:51] <_rene_>   else
[21:04:51] <_rene_> [...]

Paul



signature.asc
Description: OpenPGP digital signature

Re: gpac_0.7.1+dfsg1-1_amd64.changes is NEW

[Niels Thykier]

Thorsten Alteholz:
> Hi Reinhard,
> 
> On Tue, 2 Apr 2019, Reinhard Tartler wrote:
>> Now about 6 weeks have passed since I've been uploading this package, and
>> I do have a question: Is there anything wrong with this package?
> 
> yes, you did an upload to unstable. At this time of the freeze and
> without a notice from the maintainer/release team this is usually wrong.
> 
>> I'm CC'ing the release team to inform them about this upload.
> 
> Ok, so is this version suitable for buster?
> 
>   Thorsten
> 

Note that gpac/0.5.2-426-gc5ad4e4+dfsg5-4.1 is currently in sid,
recorded as fixing #892526, #902782 and #921969.  Therefore, please hold
gpac/0.7.1+dfsg1-1 in NEW for now until the sid version can migrate to
testing.

As for gpac/0.7.1+dfsg1-1, I cannot find a debdiff for it on the mailing
list nor the BTS.  Therefore, I have no clue whether it is suitable for
buster.

Thanks,
~Niels

Bug#926052: marked as done (unblock: python-pip/18.1-5)

[Debian Bug Tracking System]

Your message dated Tue, 2 Apr 2019 21:02:26 +0200
with message-id <4054e863-9f78-40c8-e837-ed60c19d0...@debian.org>
and subject line Re: Bug#926052: unblock: python-pip/18.1-5
has caused the Debian Bug report #926052,
regarding unblock: python-pip/18.1-5
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.)


-- 
926052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926052
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: unblock

Please unblock package python-pip

The version 18.1-5 includes a fix so that using the --extra-index-url option
of pip doesn't result in a "HTTPError: 404 Client Error: NOT FOUND".

Note that the bug is Debian specific, and is due to the way upstream calls
the requests module, which fails if the requests module is de-vendored /
de-embedded from pip, which is what has been done in Debian.

Bellow, inline in the body of this mail (sorry, I should have made it an
attachment, maybe?) is the debdiff for the package. Note that the changes to
the "hands-off-system-packages.patch" may be ignore, it's just produced by a
"quilt refresh" of the patch. Reading it, you'll notice that the only thing
that changes is the way "except HTTPError as exc:" is done, using the
imported "HTTPError" from pip._vendor.requests.exceptions rather than from
requests.HTTPError which fails.

Note that this bug deeply impacts the OpenStack CI/CD system which deeply
relies on pip and the --extra-index-url, which is why I care a lot for this
patch to go through.

Please unblock python-pip/18.1-5.

Cheers,

Thomas Goirand (zigo)

diff -Nru python-pip-18.1/debian/changelog python-pip-18.1/debian/changelog
--- python-pip-18.1/debian/changelog2019-01-03 17:38:22.0 +0100
+++ python-pip-18.1/debian/changelog2019-03-30 21:10:13.0 +0100
@@ -1,3 +1,15 @@
+python-pip (18.1-5) unstable; urgency=medium
+
+  * Team upload.
+  * Refresh hands-off-system-packages.patch.
+  * Add Properly_catch_requests_HTTPError_in_index.py.patch: this fixes 404
+when using --extra-index-url due to the way we de-bundle python-requests
+from pip. Thanks to Fabio Natali  for the bug report,
+Clark Boylan for the patch, and all of the OpenStack infra team for their
+help and involving me for this fix (Closes: #837764).
+
+ -- Thomas Goirand   Sat, 30 Mar 2019 21:10:13 +0100
+
 python-pip (18.1-4) unstable; urgency=medium
 
   * Generate Built-Using at the build time (Closes: #831271).
diff -Nru python-pip-18.1/debian/patches/hands-off-system-packages.patch 
python-pip-18.1/debian/patches/hands-off-system-packages.patch
--- python-pip-18.1/debian/patches/hands-off-system-packages.patch  
2019-01-03 17:38:22.0 +0100
+++ python-pip-18.1/debian/patches/hands-off-system-packages.patch  
2019-03-30 21:10:13.0 +0100
@@ -17,17 +17,18 @@
 Patch-Name: hands-off-system-packages.patch
 ---
 
 a/src/pip/_internal/utils/misc.py
-+++ b/src/pip/_internal/utils/misc.py
-@@ -285,22 +285,40 @@
+Index: python-pip/src/pip/_internal/utils/misc.py
+===
+--- python-pip.orig/src/pip/_internal/utils/misc.py
 python-pip/src/pip/_internal/utils/misc.py
+@@ -289,22 +289,40 @@ def renames(old, new):
  
  def is_local(path):
  """
 -Return True if path is within sys.prefix, if we're running in a 
virtualenv.
--
--If we're not in a virtualenv, all paths are considered "local."
 +Return True if this is a path pip is allowed to modify.
-+
+ 
+-If we're not in a virtualenv, all paths are considered "local."
 +If we're in a virtualenv, sys.prefix points to the virtualenv's
 +prefix; only sys.prefix is considered local.
 +
diff -Nru 
python-pip-18.1/debian/patches/Properly_catch_requests_HTTPError_in_index.py.patch
 
python-pip-18.1/debian/patches/Properly_catch_requests_HTTPError_in_index.py.patch
--- 
python-pip-18.1/debian/patches/Properly_catch_requests_HTTPError_in_index.py.patch
  1970-01-01 01:00:00.0 +0100
+++ 
python-pip-18.1/debian/patches/Properly_catch_requests_HTTPError_in_index.py.patch
  2019-03-30 21:10:13.0 +0100
@@ -0,0 +1,47 @@
+Description: Properly catch requests' HTTPError in index.py
+ This resolves issue #4195.
+ .
+ In index.py's index retrieval routine we were catching
+ requests.HTTPError to log and ignore 404s and other similar HTTP server
+ errors when pulling from (extra-)index-urls. Unfortunately, the actual
+ path to that exception is requests.exceptions.HTTPError 

Bug#926269: unblock: debian-edu-config/2.10.64

[Wolfgang Schweer]

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

Please unblock package debian-edu-config

It fixes three important bugs¹ that were detected while testing recent 
officially built Debian Edu ISO images. The bug logs contain detailed 
information. Holger Levsen has already uploaded the package.

Full source debdiff against the package in testing attached.

¹
#926183: fails to install LTSP chroot if BD iso image is used
-> https://bugs.debian.org/926183

#926184: don't prompt users to set up the initial LXQt session manually
-> https://bugs.debian.org/926184

#926186: should invalidate the nscd netgroup cache in case of changes
-> https://bugs.debian.org/926186

unblock debian-edu-config/2.10.64

Regards,
Wolfgang

No differences were encountered between the control files

diff -Nru debian-edu-config-2.10.63/cf3/cf.finalize 
debian-edu-config-2.10.64/cf3/cf.finalize
--- debian-edu-config-2.10.63/cf3/cf.finalize   2019-02-22 15:57:45.0 
+0100
+++ debian-edu-config-2.10.64/cf3/cf.finalize   2019-04-02 01:32:22.0 
+0200
@@ -14,13 +14,44 @@
 link_from => ln_s("/usr/share/debian-edu-config/lightdm-gtk-greeter.conf"),
 move_obstructions => "true";
 
-  # Make sure menu overrides are enabled in each case.
+  # Make sure desktop-profiles are disabled, use XDG instead for all DEs. This
+  # more general approach is needed because otherwise the user is prompted to
+  # set up the LXQt session manually (x-window-manager, panel config) now that
+  # lxqt depends on the 'lxqt-branding-debian' package.
 
   debian.installation::
 
 "/etc/default/desktop-profiles"
 edit_line => profile;
 
+"/etc/xdg/menus/applications-merged"
+link_from => ln_s("/usr/share/debian-edu/menu/menus/applications-merged"),
+move_obstructions => "true";
+
+"/etc/xdg/menus/gnome-applications.menu"
+link_from => 
ln_s("/usr/share/debian-edu/menu/menus/gnome-applications.menu"),
+move_obstructions => "true";
+
+"/etc/xdg/menus/kf5-applications.menu"
+link_from => 
ln_s("/usr/share/debian-edu/menu/menus/kf5-applications.menu"),
+move_obstructions => "true";
+
+"/etc/xdg/menus/lxde-applications.menu"
+link_from => 
ln_s("/usr/share/debian-edu/menu/menus/lxde-applications.menu"),
+move_obstructions => "true";
+
+"/etc/xdg/menus/lxqt-applications.menu"
+link_from => 
ln_s("/usr/share/debian-edu/menu/menus/lxqt-applications.menu"),
+move_obstructions => "true";
+
+"/etc/xdg/menus/mate-applications.menu"
+link_from => 
ln_s("/usr/share/debian-edu/menu/menus/mate-applications.menu"),
+move_obstructions => "true";
+
+"/etc/xdg/menus/xfce-applications.menu"
+link_from => 
ln_s("/usr/share/debian-edu/menu/menus/xfce-applications.menu"),
+move_obstructions => "true";
+
 commands:
 
   debian.server.installation::
@@ -73,7 +104,9 @@
 
 replace_patterns:
 
-  "PERSONALITY=polite" replace_with => value("PERSONALITY=rude");
+  "PERSONALITY=polite" replace_with => value("PERSONALITY=sheep");
+  # Needed if upgrading from 10+edu~a0
+  "PERSONALITY=rude" replace_with => value("PERSONALITY=sheep");
 }
 
 bundle agent editline_finalize
diff -Nru debian-edu-config-2.10.63/debian/changelog 
debian-edu-config-2.10.64/debian/changelog
--- debian-edu-config-2.10.63/debian/changelog  2019-03-18 15:21:39.0 
+0100
+++ debian-edu-config-2.10.64/debian/changelog  2019-04-02 10:54:26.0 
+0200
@@ -1,9 +1,23 @@
-debian-edu-config (2.10.63) UNRELEASED; urgency=medium
+debian-edu-config (2.10.64) unstable; urgency=medium
 
+  [ Wolfgang Schweer ]
+  * etc/ltsp/ltsp-build-client.conf: Add DIST="buster". (Closes: #926183)
+- Make sure the LTSP chroot installation works for all possible scenarios.
+  * cf3/cf.finalize: Use XDG instead of desktop-profiles. (Closes: #926184)
+- Make sure desktop-profiles are disabled and use XDG as a more general
+  approach. This is needed for LXQt to work without user interaction.
+  * tools/gosa-sync-dns-nfs: Make tool more robust. (Closes: #926186)
+- Invalidate the nscd netgroup cache to make NFS homedir mount more robust.
+
+ -- Holger Levsen   Tue, 02 Apr 2019 10:54:26 +0200
+
+debian-edu-config (2.10.63) unstable; urgency=medium
+
+  [ Wolfgang Schweer ]
   * Adjust sbin/debian-edu-pxeinstall. (Closes: #924927)
 - Set d-i version to 10, now that debian-installer-10-netboot is in Buster.
 
- -- Wolfgang Schweer   Mon, 18 Mar 2019 15:21:39 +0100
+ -- Holger Levsen   Thu, 21 Mar 2019 11:57:41 +
 
 debian-edu-config (2.10.62) unstable; urgency=medium
 
diff -Nru debian-edu-config-2.10.63/etc/ltsp/ltsp-build-client.conf 
debian-edu-config-2.10.64/etc/ltsp/ltsp-build-client.conf
--- debian-edu-config-2.10.63/etc/ltsp/ltsp-build-client.conf   2019-02-22 
15:57:45.0 +0100
+++ debian-edu-config-2.10.64/etc/ltsp/ltsp-build-client.conf   2019-03-22 
15:50:19.0 +0100
@@ -15,3 +15,5 @@
 # Set the next entry if the sources.list file 

Re: gpac_0.7.1+dfsg1-1_amd64.changes is NEW

[Thorsten Alteholz]

Hi Reinhard,

On Tue, 2 Apr 2019, Reinhard Tartler wrote:

Now about 6 weeks have passed since I've been uploading this package, and
I do have a question: Is there anything wrong with this package?


yes, you did an upload to unstable. At this time of the freeze and 
without a notice from the maintainer/release team this is usually wrong.



I'm CC'ing the release team to inform them about this upload.


Ok, so is this version suitable for buster?

  Thorsten

Bug#926267: unblock: nvidia-persistenced/410.104-1

[Andreas Beckmann]

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

Please unblock package nvidia-persistenced

Hi,

I recently realized that I can improve the nvidia-graphics-drivers
upgrade path from stretch to buster on the no longer supported
32-bit architectures (i386, armhf) by reintroducing some (meta-)packages
as transitional packages depending on the corresponding packages from
the (still 32-bit supporting) 390xx legacy driver.

This request is for nvidia-persistenced.

unblock nvidia-persistenced/410.104-1

Andreas
diff -Nru nvidia-persistenced-410.93/debian/changelog 
nvidia-persistenced-410.104/debian/changelog
--- nvidia-persistenced-410.93/debian/changelog 2019-02-11 18:23:51.0 
+0100
+++ nvidia-persistenced-410.104/debian/changelog2019-03-25 
18:07:00.0 +0100
@@ -1,3 +1,11 @@
+nvidia-persistenced (410.104-1) unstable; urgency=medium
+
+  * New upstream release.
+  * Adjust libnvidia-cfg1 dependencies to automatically switch to the legacy
+package on upgrades from stretch to buster on [!amd64].
+
+ -- Andreas Beckmann   Mon, 25 Mar 2019 18:07:00 +0100
+
 nvidia-persistenced (410.93-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru nvidia-persistenced-410.93/debian/control 
nvidia-persistenced-410.104/debian/control
--- nvidia-persistenced-410.93/debian/control   2019-02-11 18:23:51.0 
+0100
+++ nvidia-persistenced-410.104/debian/control  2019-03-25 18:07:00.0 
+0100
@@ -20,7 +20,10 @@
 Pre-Depends:
  ${misc:Pre-Depends}
 Depends:
- libnvidia-cfg1 | libnvidia-cfg1-any,
+ libnvidia-cfg1 [amd64]
+ | libnvidia-legacy-390xx-cfg1
+ | libnvidia-legacy-340xx-cfg1
+ | libnvidia-cfg1-any [amd64],
  adduser,
  ${shlibs:Depends},
  ${misc:Depends}
diff -Nru nvidia-persistenced-410.93/version.mk 
nvidia-persistenced-410.104/version.mk
--- nvidia-persistenced-410.93/version.mk   2018-12-21 00:18:10.0 
+0100
+++ nvidia-persistenced-410.104/version.mk  2019-02-06 06:15:59.0 
+0100
@@ -1 +1 @@
-NVIDIA_VERSION = 410.93
+NVIDIA_VERSION = 410.104

Bug#926264: unblock: nvidia-settings/410.104-2

[Andreas Beckmann]

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

Please unblock package nvidia-settings

Hi,

I recently realized that I can improve the nvidia-graphics-drivers
upgrade path from stretch to buster on the no longer supported
32-bit architectures (i386, armhf) by reintroducing some (meta-)packages
as transitional packages depending on the corresponding packages from
the (still 32-bit supporting) 390xx legacy driver.

This request is for nvidia-settings.

Andreas

unblock nvidia-settings/410.104-2
diff -Nru nvidia-settings-410.104/debian/changelog 
nvidia-settings-410.104/debian/changelog
--- nvidia-settings-410.104/debian/changelog2019-03-13 01:01:46.0 
+0100
+++ nvidia-settings-410.104/debian/changelog2019-03-30 09:38:32.0 
+0100
@@ -1,3 +1,10 @@
+nvidia-settings (410.104-2) unstable; urgency=medium
+
+  * [i386 armhf]: Reinstate nvidia-settings as a transitional package
+depending on nvidia-settings-legacy-390xx.
+
+ -- Andreas Beckmann   Sat, 30 Mar 2019 09:38:32 +0100
+
 nvidia-settings (410.104-1) unstable; urgency=medium
 
   * New upstream release 410.104.
diff -Nru nvidia-settings-410.104/debian/control 
nvidia-settings-410.104/debian/control
--- nvidia-settings-410.104/debian/control  2019-03-13 01:01:46.0 
+0100
+++ nvidia-settings-410.104/debian/control  2019-03-30 09:38:32.0 
+0100
@@ -30,21 +30,22 @@
 
 Package: nvidia-settings
 Section: contrib/x11
-Architecture: amd64
+Architecture: amd64 i386 armhf
 Pre-Depends:
  nvidia-installer-cleanup,
 Depends:
- ${nvidia-alternative},
- libxnvctrl0 (= ${binary:Version}),
+ nvidia-settings-legacy-390xx [!amd64],
+ ${nvidia-alternative} [amd64],
+ libxnvctrl0 (= ${binary:Version}) [amd64],
  ${shlibs:Depends}, ${misc:Depends}
 Recommends:
- libgl1-nvidia${nvidia:Legacy}-glvnd-glx | libgl1-nvidia${nvidia:Legacy}-glx,
- nvidia${nvidia:Legacy}-vdpau-driver,
- libnvidia${nvidia:Legacy}-ml1,
+ libgl1-nvidia${nvidia:Legacy}-glvnd-glx [amd64] | 
libgl1-nvidia${nvidia:Legacy}-glx [amd64],
+ nvidia${nvidia:Legacy}-vdpau-driver [amd64],
+ libnvidia${nvidia:Legacy}-ml1 [amd64],
 Provides:
- nvidia-settings-gtk-${nvidia:Version},
+ nvidia-settings-gtk-${nvidia:Version} [amd64],
 Conflicts:
- nvidia-settings-gtk-${nvidia:Version},
+ nvidia-settings-gtk-${nvidia:Version} [amd64],
 Description: tool for configuring the NVIDIA graphics 
driver${nvidia:LegacyDesc}
  The nvidia-settings utility is a tool for configuring the NVIDIA
  Linux graphics driver.  It operates by communicating with the NVIDIA
diff -Nru nvidia-settings-410.104/debian/nvidia-settings.install.amd64.in 
nvidia-settings-410.104/debian/nvidia-settings.install.amd64.in
--- nvidia-settings-410.104/debian/nvidia-settings.install.amd64.in 
1970-01-01 01:00:00.0 +0100
+++ nvidia-settings-410.104/debian/nvidia-settings.install.amd64.in 
2019-03-30 09:38:32.0 +0100
@@ -0,0 +1,6 @@
+usr/bin/nvidia-settingsusr/lib/#PRIVATE#/
+debian/nvidia-settings.desktop usr/lib/#PRIVATE#/
+nvidia-settings#LEGACY#.pngusr/share/pixmaps/
+usr/bin/nv-control-dpy usr/lib/#PRIVATE#/
+usr/share/man/man1/nvidia-settings.1.gzusr/lib/#PRIVATE#/
+usr/lib/libnvidia-gtk?.so.*
diff -Nru nvidia-settings-410.104/debian/nvidia-settings.install.in 
nvidia-settings-410.104/debian/nvidia-settings.install.in
--- nvidia-settings-410.104/debian/nvidia-settings.install.in   2019-03-13 
01:01:46.0 +0100
+++ nvidia-settings-410.104/debian/nvidia-settings.install.in   1970-01-01 
01:00:00.0 +0100
@@ -1,6 +0,0 @@
-usr/bin/nvidia-settingsusr/lib/#PRIVATE#/
-debian/nvidia-settings.desktop usr/lib/#PRIVATE#/
-nvidia-settings#LEGACY#.pngusr/share/pixmaps/
-usr/bin/nv-control-dpy usr/lib/#PRIVATE#/
-usr/share/man/man1/nvidia-settings.1.gzusr/lib/#PRIVATE#/
-usr/lib/libnvidia-gtk?.so.*
diff -Nru nvidia-settings-410.104/debian/nvidia-settings.lintian-overrides 
nvidia-settings-410.104/debian/nvidia-settings.lintian-overrides
--- nvidia-settings-410.104/debian/nvidia-settings.lintian-overrides
2019-03-13 01:01:46.0 +0100
+++ nvidia-settings-410.104/debian/nvidia-settings.lintian-overrides
2019-03-30 09:38:32.0 +0100
@@ -1,6 +1,11 @@
 no-upstream-changelog
 
 # the shared libraries are actually version-specific plugins
-package-name-doesnt-match-sonames
-shlib-calls-exit
-no-symbols-control-file
+[amd64]: package-name-doesnt-match-sonames
+[amd64]: shlib-calls-exit
+[amd64]: no-symbols-control-file
+
+# On architectures no longer supported by the current driver,
+# this is a dummy package depending on the 390xx legacy driver.
+[!amd64]: empty-binary-package
+[!amd64]: package-contains-no-arch-dependent-files
diff -Nru nvidia-settings-410.104/debian/rules 

Processed: Re: Bug#925321: RM: openjdk-8/8u171-b11-2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #925321 [release.debian.org] RM: openjdk-8/8u171-b11-2
Added tag(s) moreinfo.

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

Bug#925321: RM: openjdk-8/8u171-b11-2

[Paul Gevers]

Control: tags -1 moreinfo

Hi Andreas,

On 02-04-2019 16:36, Andreas Beckmann wrote:
> trying: -openjdk-8
> skipped: -openjdk-8 (0, 1, 6)
> got: 34+0: a-1:a-0:a-0:a-0:i-32:m-0:m-0:m-0:p-0:s-1
> * i386: libreoffice-officebean, libreoffice-sdbc-hsqldb

https://packages.debian.org/buster/libreoffice-officebean and
https://packages.debian.org/buster/libreoffice-sdbc-hsqldb
also show:
dep: openjdk-8-jre (>= 8u151-b12-2~) [i386]
OpenJDK Java runtime, using Hotspot JIT
or openjdk-9-jre (>= 9.0.1+11-1~)
Package not available

Which would explain why britney doesn't want to remove openjdk-8, but it
would also suggest that libreoffice-officebean and
libreoffice-sdbc-hsqldb are currently broken in unstable on i386.

I am not sure if I am interpreting this correctly.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#924399: marked as done (release.debian.org: ros-catkin has a bug and needs to rebuild one package)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2019 18:31:00 +
with message-id <83cfd460-9f6e-7e60-97e5-91e51066b...@thykier.net>
and subject line Re: Bug#924399: release.debian.org: ros-catkin has a bug and 
needs to rebuild one package
has caused the Debian Bug report #924399,
regarding release.debian.org: ros-catkin has a bug and needs to rebuild one 
package
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.)


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

I have detected an ugly bug in ros-catkin (#924395). It _only_ affects to
software that uses catkin and generates pkgconfig files (.pc) that uses
Boost.

In our case we have ros-rosconsole. The pkgconfig file is wrong. So, I would
like to push a new version of ros-catking and ask a rebuild of
ros-rosconsole.

Can it be possible for Buster?

Best regards,

Leopold



-- System Information:
Debian Release: 9.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.14.0-0.bpo.3-amd64 (SMP w/8 CPU cores)
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On Mon, 18 Mar 2019 16:47:19 +0100 Leopold Palomo-Avellaneda
 wrote:
> [...]
> 
> Hi Niels,
> 
> ros-catkin is uploaded and accepted. I wait some hours to ask for NMU. 
> However,
> I would like to add that I found another bug related with the cmake boost 
> thread
> library issue.
> 
> https://github.com/ros-visualization/python_qt_binding/commit/0a4893791039d5c3f851ee7bc2de832209d52f6d
> 
> It's not so critical like the other one because I have only found one package
> that this one makes an error, but the package in the archive is wrong. So, if
> you agree, I file a bug, and I can prepare a patch for the version in testing
> and pushed. I hope not to find more errors in the ros testing packages ...
> 
> 
> Leopold
> 
> 
> 
> 

Unblocked, thanks.
~Niels--- End Message ---

Bug#925185: unblock pre-approval: sysstat/12.0.3-1 (actually 12.0.3-2)

[Niels Thykier]

Control: tags -1 confirmed moreinfo


Robert Luberda:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please approve sysstat 12.0.3, which is upstream bugfix release,
> for uploading to unstable and migrating to testing.
> 
> [...]
> 
> I uploaded systat 12.0.3-1 to experimental a few days ago with the
> following changelog:
> 
>   sysstat (12.0.3-1) experimental; urgency=medium
>   
> * New upstream stable version:
>   + sadf: Fix out of bound reads security issues (CVE-2018-19416 and
> CVE-2018-19517, closes: #914384, #914553);
>   + sadf: Fix possible infinite loop;
>   + sar: Fortify remap_struct() function to prevent possible crashes on
> reading binary datafiles generated by older versions of sysstat.
> * systat.init.d: revert a change introduced in 11.5.5-1, as it caused
>   the start script to fail to execute the command that adds "Linux 
> Restart"
>   marker into statistics file on systems on which systemd is not used.
>   Thanks to Georgios Zarkadas for noticing this (closes: #924864).
> * debian/rules: replace deprecated dh_systemd_start by dh_installsystemd,
>   as suggested by lintian; the former command wass ignored by debhelper 
> v11,


Typo

>   what in turn resulted in the `--no-start' option being ignored, and the
>   restart markers were incorrectly added during package upgrades.
>   
>-- Robert Luberda   Sun, 17 Mar 2019 23:09:46 +0100
> 
> The debdiff against buster is attached. 
> 
> If you think this version would be OK for buster, then I can upload -2
> to unstable, with no other changes, except for Debian changelog entry.
> 
> Otherwise please let me know what would you approve, and what I should do:
>  - backport patch [3] only (but I don't think this would be safer);
>  - backport both patches, i.e. [3], and [4] (but those are the biggest ones);
>  - something else.
> 
> Regards,
> robert
> 
> 
> [...]
Please go ahead with 12.0.3-1 for buster and remove the moreinfo tag
when it is ready for unblocks.

Thanks,
~Niels

Processed: Re: Bug#925185: unblock pre-approval: sysstat/12.0.3-1 (actually 12.0.3-2)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed moreinfo
Bug #925185 [release.debian.org] unblock pre-approval: sysstat/12.0.3-1 
(actually 12.0.3-2)
Added tag(s) moreinfo and confirmed.

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

Bug#925219: marked as done (unblock: sigil/0.9.13-1)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2019 18:12:00 +
with message-id 
and subject line Re: Bug#925219: unblock: sigil/0.9.13-1
has caused the Debian Bug report #925219,
regarding unblock: sigil/0.9.13-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.)


-- 
925219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock

Dear RT,

I've just uploaded a sigil/0.9.13-1, with the latest upstream release.

It's a mostly bugfix release, that once stripped of the doc changes and
translation updates boils down to
 57 files changed, 643 insertions(+), 883 deletions(-)

According to upstream, 0.9.12 (released in February) is "very buggy"
(https://github.com/Sigil-Ebook/Sigil/wiki#versions-0911-and-0912-of-sigil-are-very-buggy)
and are not quite fit for usage.

Also, there is finally built-in support for system-wide mathjs, so we
are not patch-free, which is a great thing by itself for me :)

Please find attached the stripped down debdiff created with
/usr/bin/debdiff sigil_0.9.12+dfsg-1.dsc sigil_0.9.13+dfsg-1.dsc | 
filterdiff -x '*/ts/*' | filterdiff -x '*/docs/*'

Thanks for considering.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
diffstat for sigil-0.9.12+dfsg sigil-0.9.13+dfsg

 CMakeLists.txt |2 
 ChangeLog.txt  |   23 
 README.md  |2 
 appveyor.yml   |   13 
 debian/changelog   |   11 
 debian/control |2 
 debian/copyright   |8 
 debian/patches/mathajx |   50 -
 debian/patches/series  |1 
 debian/rules   |3 
 debian/sigil-data.install  |1 
 internal/gumbo/tokenizer.c |6 
 src/CMakeLists.txt |   40 
 src/Dialogs/ClipEditor.cpp |   22 
 src/Dialogs/ClipboardHistorySelector.cpp   |3 
 src/Dialogs/Reports.cpp|1 
 src/Dialogs/ReportsWidgets/AllFilesWidget.cpp  |7 
 src/Dialogs/ReportsWidgets/AllFilesWidget.h|2 
 src/Dialogs/ReportsWidgets/CSSFilesWidget.cpp  |7 
 src/Dialogs/ReportsWidgets/CSSFilesWidget.h|2 
 src/Dialogs/ReportsWidgets/CharactersInHTMLFilesWidget.cpp |6 
 src/Dialogs/ReportsWidgets/CharactersInHTMLFilesWidget.h   |2 
 src/Dialogs/ReportsWidgets/ClassesInHTMLFilesWidget.cpp|6 
 src/Dialogs/ReportsWidgets/ClassesInHTMLFilesWidget.h  |2 
 src/Dialogs/ReportsWidgets/HTMLFilesWidget.cpp |7 
 src/Dialogs/ReportsWidgets/HTMLFilesWidget.h   |2 
 src/Dialogs/ReportsWidgets/ImageFilesWidget.cpp|7 
 src/Dialogs/ReportsWidgets/ImageFilesWidget.h  |2 
 src/Dialogs/ReportsWidgets/LinksWidget.cpp |6 
 src/Dialogs/ReportsWidgets/LinksWidget.h   |2 
 src/Dialogs/ReportsWidgets/StylesInCSSFilesWidget.cpp  |6 
 src/Dialogs/ReportsWidgets/StylesInCSSFilesWidget.h|2 
 src/Dialogs/SearchEditor.cpp   |   15 
 src/MainUI/FindReplace.cpp |5 
 src/MainUI/FindReplace.h   |1 
 src/MainUI/MainWindow.cpp  |   60 +
 src/MainUI/MainWindow.h|1 
 src/MainUI/PreviewWindow.cpp   |   22 
 src/Misc/CSSInfo.cpp   |   24 
 src/Misc/CSSInfo.h |3 
 src/Misc/EmbeddedPythonPkg.cpp |  617 -
 src/Misc/FilenameDelegate.cpp  |   13 
 src/Misc/SettingsStore.cpp |   10 
 

Bug#926256: marked as done (unblock: gwenview/4:18.04.0-1.1)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2019 17:52:00 +
with message-id 
and subject line Re: Bug#926256: unblock: gwenview/4:18.04.0-1.1
has caused the Debian Bug report #926256,
regarding unblock: gwenview/4:18.04.0-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.)


-- 
926256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926256
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: unblock

Please unblock package gwenview

This update fixes a file overwrite issue if the obsolete gwenview-i18n
from lenny is still installed (#911638).

unblock gwenview/4:18.04.0-1.1

Andreas
diff -Nru gwenview-18.04.0/debian/changelog gwenview-18.04.0/debian/changelog
--- gwenview-18.04.0/debian/changelog   2018-04-23 06:56:17.0 +0200
+++ gwenview-18.04.0/debian/changelog   2019-03-24 16:07:37.0 +0100
@@ -1,3 +1,10 @@
+gwenview (4:18.04.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add Breaks+Replaces against gwenview-i18n from lenny.  (Closes: #911638)
+
+ -- Andreas Beckmann   Sun, 24 Mar 2019 16:07:37 +0100
+
 gwenview (4:18.04.0-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru gwenview-18.04.0/debian/control gwenview-18.04.0/debian/control
--- gwenview-18.04.0/debian/control 2018-04-23 06:34:28.0 +0200
+++ gwenview-18.04.0/debian/control 2019-03-24 14:11:58.0 +0100
@@ -43,8 +43,8 @@
 Architecture: any
 Depends: kinit, ${misc:Depends}, ${shlibs:Depends}
 Recommends: kamera, kio-extras, qt5-image-formats-plugins
-Breaks: ${kde-l10n:all}
-Replaces: ${kde-l10n:all}
+Breaks: ${kde-l10n:all}, gwenview-i18n
+Replaces: ${kde-l10n:all}, gwenview-i18n
 Description: image viewer
  Gwenview is an image viewer, ideal for browsing and displaying a collection of
  images.  It is capable of showing images in a full-screen slideshow view and
--- End Message ---
--- Begin Message ---
Andreas Beckmann:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package gwenview
> 
> This update fixes a file overwrite issue if the obsolete gwenview-i18n
> from lenny is still installed (#911638).
> 
> unblock gwenview/4:18.04.0-1.1
> 
> Andreas
> 

Unblocked, thanks.
~Niels--- End Message ---

Bug#926255: marked as done (unblock: filelight/4:18.04.1-1.1)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2019 17:53:00 +
with message-id <82fd5f0b-a3ae-f04e-ff9a-fb6f2246a...@thykier.net>
and subject line Re: Bug#926255: unblock: filelight/4:18.04.1-1.1
has caused the Debian Bug report #926255,
regarding unblock: filelight/4:18.04.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.)


-- 
926255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926255
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: unblock

Please unblock package filelight

This update fixes a file overwrite issue in case the obsolete
filelight-l10n from squeeze is still installed.  (Closes: #911783)

unblock filelight/4:18.04.1-1.1

Andreas
diff -Nru filelight-18.04.1/debian/changelog filelight-18.04.1/debian/changelog
--- filelight-18.04.1/debian/changelog  2018-05-23 01:11:17.0 +0200
+++ filelight-18.04.1/debian/changelog  2019-03-24 01:54:15.0 +0100
@@ -1,3 +1,10 @@
+filelight (4:18.04.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add Breaks+Replaces against filelight-l10n from squeeze. (Closes: #911783)
+
+ -- Andreas Beckmann   Sun, 24 Mar 2019 01:54:15 +0100
+
 filelight (4:18.04.1-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru filelight-18.04.1/debian/control filelight-18.04.1/debian/control
--- filelight-18.04.1/debian/control2018-05-22 23:51:51.0 +0200
+++ filelight-18.04.1/debian/control2019-03-24 00:59:56.0 +0100
@@ -27,8 +27,8 @@
 Package: filelight
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends}
-Breaks: ${kde-l10n:all}
-Replaces: ${kde-l10n:all}
+Breaks: ${kde-l10n:all}, filelight-l10n
+Replaces: ${kde-l10n:all}, filelight-l10n
 Description: show where your diskspace is being used
  Filelight allows you to understand your disk usage by graphically
  representing your filesystem as a set of concentric, segmented rings.
--- End Message ---
--- Begin Message ---
Andreas Beckmann:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package filelight
> 
> This update fixes a file overwrite issue in case the obsolete
> filelight-l10n from squeeze is still installed.  (Closes: #911783)
> 
> unblock filelight/4:18.04.1-1.1
> 
> Andreas
> 

Unblocked, thanks.
~Niels--- End Message ---

Bug#926137: marked as done (RM: coq-doc/8.6-1)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2019 17:54:00 +
with message-id <39b2fc43-374b-1e7f-8d63-8d8ddc5e0...@thykier.net>
and subject line Re: Bug#926137: RM: coq-doc/8.6-1
has caused the Debian Bug report #926137,
regarding RM: coq-doc/8.6-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.)


-- 
926137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926137
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: rm

buster currently carries coq/8.9.0-1, but coq-doc still documents
Coq 8.6. Building the reference manual for 8.9.0 requires the ANTLR 4
runtime for Python 3, which is not in buster
(https://bugs.debian.org/926134). With the freeze in effect, it’s
looking pretty unlikely that coq-doc for Coq 8.9.0 is going to make it
into buster/non-free before the buster release gets finalized. Please
remove coq-doc and its binary packages (coq-doc, coq-doc-html, and
coq-doc-pdf) from buster/non-free.
--- End Message ---
--- Begin Message ---
Benjamin Barenblat:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: rm
> 
> buster currently carries coq/8.9.0-1, but coq-doc still documents
> Coq 8.6. Building the reference manual for 8.9.0 requires the ANTLR 4
> runtime for Python 3, which is not in buster
> (https://bugs.debian.org/926134). With the freeze in effect, it’s
> looking pretty unlikely that coq-doc for Coq 8.9.0 is going to make it
> into buster/non-free before the buster release gets finalized. Please
> remove coq-doc and its binary packages (coq-doc, coq-doc-html, and
> coq-doc-pdf) from buster/non-free.
> 

Removal hint added, thanks.
~Niels--- End Message ---

Bug#926257: marked as done (unblock: okular/4:17.12.2-2.2)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2019 17:51:00 +
with message-id 
and subject line Re: Bug#926257: unblock: okular/4:17.12.2-2.2
has caused the Debian Bug report #926257,
regarding unblock: okular/4:17.12.2-2.2
to be marked as done.

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

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


-- 
926257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926257
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: unblock

Please unblock package okular

This update fixes a file overwrite issue in buster if the obsolete
okular-l10n from lenny is still installed (#911641).

unblock okular/4:17.12.2-2.2

Andreas
diff -Nru okular-17.12.2/debian/changelog okular-17.12.2/debian/changelog
--- okular-17.12.2/debian/changelog 2018-12-02 12:27:39.0 +0100
+++ okular-17.12.2/debian/changelog 2019-03-24 13:05:50.0 +0100
@@ -1,3 +1,10 @@
+okular (4:17.12.2-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add Breaks+Replaces against okular-l10n from lenny. (Closes: #911641)
+
+ -- Andreas Beckmann   Sun, 24 Mar 2019 13:05:50 +0100
+
 okular (4:17.12.2-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru okular-17.12.2/debian/control okular-17.12.2/debian/control
--- okular-17.12.2/debian/control   2018-12-02 12:24:09.0 +0100
+++ okular-17.12.2/debian/control   2019-03-24 03:40:28.0 +0100
@@ -76,9 +76,11 @@
 Breaks: kdegraphics-mobipocket (<< 4:4.12),
 okular-extra-backends (<< 4:16.12.0),
 okular-mobile (<< 4:17.04.1-0),
+okular-l10n,
 ${kde-l10n:all},
 Replaces: okular-extra-backends (<< 4:16.12.0),
   okular-mobile (<< 4:17.04.1-0),
+  okular-l10n,
   ${kde-l10n:all},
 Description: universal document viewer
  Okular is a universal document viewer with support for advanced document
--- End Message ---
--- Begin Message ---
Andreas Beckmann:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package okular
> 
> This update fixes a file overwrite issue in buster if the obsolete
> okular-l10n from lenny is still installed (#911641).
> 
> unblock okular/4:17.12.2-2.2
> 
> Andreas
> 

Unblocked, thanks.
~Niels--- End Message ---

Bug#926230: marked as done (unblock: openstack-cluster-installer/21)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2019 17:48:00 +
with message-id <5efd76ba-d48a-c547-c384-dc43fab56...@thykier.net>
and subject line Re: Bug#926230: unblock: openstack-cluster-installer/21
has caused the Debian Bug report #926230,
regarding unblock: openstack-cluster-installer/21
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.)


-- 
926230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926230
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: unblock

Dear release team,
Please unblock package openstack-cluster-installer

While continuing the development, I've found a number of issues which I
corrected and backported. This release 21 of openstack-cluster-installer
contains these bugfixes (no new feature).

I have attached the debdiff for the changes, though it may be hard to
read, so I would recommend reading individual commits from Salsa over
here:

https://salsa.debian.org/openstack-team/debian/openstack-cluster-installer/commits/debian/buster

The 8 commits are from 5th of March up to now.

Please unblock openstack-cluster-installer/21.

Cheers,

Thomas Goirand (zigo)
diff -Nru openstack-cluster-installer-20/debian/changelog 
openstack-cluster-installer-21/debian/changelog
--- openstack-cluster-installer-20/debian/changelog 2019-02-20 
14:12:23.0 +0100
+++ openstack-cluster-installer-21/debian/changelog 2019-03-05 
13:46:39.0 +0100
@@ -1,3 +1,18 @@
+openstack-cluster-installer (21) unstable; urgency=medium
+
+  * Bugfix release for Buster which includes:
+- Fixed reserve_ip_to_all_slaves_of_network() call in network_add API call.
+- Correctly check for $mgmt_net["iface2"] and not $onenet when calculating
+  --static-iface.
+- Fix block device list for swiftstore (statsd hostname was breaking it,
+ordering was broken).
+- Correctly set the erlang_cookie for rabbitmq as a random value.
+- Correctly use a a real random key for heat's encryption key.
+- Correct swift pipeline order when using encryption.
+- Correctly set unix rights of drives in /srv/node.
+
+ -- Thomas Goirand   Tue, 05 Mar 2019 13:46:39 +0100
+
 openstack-cluster-installer (20) unstable; urgency=medium
 
   * Set allow_resize_to_same_host to True on all nova nodes.
diff -Nru openstack-cluster-installer-20/puppet/manifests/controller.pp 
openstack-cluster-installer-21/puppet/manifests/controller.pp
--- openstack-cluster-installer-20/puppet/manifests/controller.pp   
2019-02-20 14:12:23.0 +0100
+++ openstack-cluster-installer-21/puppet/manifests/controller.pp   
2019-03-05 13:46:39.0 +0100
@@ -73,6 +73,7 @@
   $all_swiftproxy   = undef,
   $all_swiftproxy_ip= undef,
   $pass_mysql_rootuser  = undef,
+  $pass_rabbitmq_cookie = undef,
   $pass_keystone_db = undef,
   $pass_keystone_messaging  = undef,
   $pass_keystone_adminuser  = undef,
@@ -96,6 +97,7 @@
   $pass_neutron_db  = undef,
   $pass_neutron_messaging   = undef,
   $pass_neutron_authtoken   = undef,
+  $pass_heat_encryptkey = undef,
   $pass_heat_db = undef,
   $pass_heat_messaging  = undef,
   $pass_heat_authtoken  = undef,
@@ -1281,7 +1283,7 @@
   config_cluster   => true,
   cluster_nodes=> $all_masters,
   cluster_node_type=> 'ram',
-  erlang_cookie=> 'XAFSRAFNNFJOFSHLEUFT',
+  erlang_cookie=> $pass_rabbitmq_cookie,
   wipe_db_on_cookie_change => true,
 }->
 rabbitmq_vhost { '/':
@@ -1937,7 +1939,7 @@
   service_name => 'heat-api',
 }
 class { '::heat::engine':
-  auth_encryption_key   => '1234567890AZERTYUIOPMLKJHGFDSQ12',
+  auth_encryption_key   => $pass_heat_encryptkey[0,32],
 #  heat_metadata_server_url  => "${base_url}:8000/orchestration-cfn",
 #  heat_waitcondition_server_url => 
"${base_url}:8000/orchestration-cfn/v1/waitcondition",
 }
diff -Nru openstack-cluster-installer-20/puppet/manifests/swiftproxy.pp 
openstack-cluster-installer-21/puppet/manifests/swiftproxy.pp
--- openstack-cluster-installer-20/puppet/manifests/swiftproxy.pp   
2019-02-20 14:12:23.0 +0100
+++ openstack-cluster-installer-21/puppet/manifests/swiftproxy.pp   
2019-03-05 13:46:39.0 +0100
@@ -156,7 +156,7 @@
   # Because there's no ca_file option in castellan, we must
   # allow swiftproxy to run without encryption  in case we're
   # running on a PoC without a real certificate for 

Processed: Re: Bug#926222: unblock: pbgenomicconsensus/2.3.2-2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #926222 [release.debian.org] unblock: pbgenomicconsensus/2.3.2-2
Added tag(s) moreinfo.

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

Bug#926257: unblock: okular/4:17.12.2-2.2

[Andreas Beckmann]

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

Please unblock package okular

This update fixes a file overwrite issue in buster if the obsolete
okular-l10n from lenny is still installed (#911641).

unblock okular/4:17.12.2-2.2

Andreas
diff -Nru okular-17.12.2/debian/changelog okular-17.12.2/debian/changelog
--- okular-17.12.2/debian/changelog 2018-12-02 12:27:39.0 +0100
+++ okular-17.12.2/debian/changelog 2019-03-24 13:05:50.0 +0100
@@ -1,3 +1,10 @@
+okular (4:17.12.2-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add Breaks+Replaces against okular-l10n from lenny. (Closes: #911641)
+
+ -- Andreas Beckmann   Sun, 24 Mar 2019 13:05:50 +0100
+
 okular (4:17.12.2-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru okular-17.12.2/debian/control okular-17.12.2/debian/control
--- okular-17.12.2/debian/control   2018-12-02 12:24:09.0 +0100
+++ okular-17.12.2/debian/control   2019-03-24 03:40:28.0 +0100
@@ -76,9 +76,11 @@
 Breaks: kdegraphics-mobipocket (<< 4:4.12),
 okular-extra-backends (<< 4:16.12.0),
 okular-mobile (<< 4:17.04.1-0),
+okular-l10n,
 ${kde-l10n:all},
 Replaces: okular-extra-backends (<< 4:16.12.0),
   okular-mobile (<< 4:17.04.1-0),
+  okular-l10n,
   ${kde-l10n:all},
 Description: universal document viewer
  Okular is a universal document viewer with support for advanced document

Bug#926222: unblock: pbgenomicconsensus/2.3.2-2

[Niels Thykier]

Control: tags -1 moreinfo

Andreas Tille:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package pbgenomicconsensus
> 
> 
> I admit the changes are more complex than I would have prefered them to
> be.  The usage of the upstream Makefile inside the tests would have
> required to re-do the workaround for missing data for some tests as they
> were just done in debian/rules.  Instead I moved the code from d/rules
> right into upstream makefile to keep the test consistent at package
> build time and in autopkgtest.
> 
> Unfortunately further patches of the test suite are necessary to deal
> with several warnings bloating the output.
> 
> Kind regards, Andreas.
> 
> 
> unblock pbgenomicconsensus/2.3.2-2
> 
> [...]
> 

Hi,

A possible reoccurring issue is that the changes to the Makefile
involves long shell sequences with ";" (i.e. "Ignore errors") without
use of "set -e".  As an example is this:

> +--- a/Makefile
>  b/Makefile
> +@@ -8,7 +8,12 @@ tests: unit-tests basic-tests
> + 
> + unit-tests:
> +   # Unit tests
> +-  py.test --junit-xml=nosetests.xml tests/unit
> ++  # ignore tests requiring 
> https://github.com/PacificBiosciences/PacBioTestData which is not packaged
> ++  TMPDIR=$$(mktemp -d /tmp/test_ignore_XX) ; \
> ++  mv tests/unit/test_tool_contract.py $${TMPDIR} ; \
> ++  py.test --junit-xml=nosetests.xml tests/unit ; \
> ++  mv $${TMPDIR}/* tests/unit ; \
> ++  rmdir $${TMPDIR}
> + 
> + # Note: We need at least cram/0.7 for '--xunit-file'
> + # Note: The cram tests often need h5py.

AFAICT, if the py.test command fails the target might still succeed as
long as the final "rmdir" succeeds due to "; without set -e". Obviously,
it is not going to be any easier to correctly clean up *in case of* errors.


Similar issue appears here:

> +--- a/tests/cram/extra/plurality-fluidigm.t
>  b/tests/cram/extra/plurality-fluidigm.t
> +@@ -7,7 +7,8 @@ Some tests of a "fluidigm amplicons" dat
> + 
> + Set the QV threshold to 10.
> + 
> +-  $ variantCaller --algorithm=plurality -r $REFERENCE -q 10 -o variants.gff 
> -o consensus.csv -o consensus.fastq $INPUT
> ++  $ variantCaller --algorithm=plurality -r $REFERENCE -q 10 -o variants.gff 
> -o consensus.csv -o consensus.fastq $INPUT 2>&1 | tee | grep -v 
> H5pyDeprecationWarning
> ++  [1]
> + 
> + There are two true SNVs (and one diploid SNV that we miss right now).
> + 

(ASSUMPTION: It is a command and run under "normal shell rules" and the
test actually checks the exit code rather than the out).

If the above assumption holds, this patch will hide the exit code of
variantCaller and replace it by the exit code of grep (a normal pipeline
*without* the "set -o pipefail"-bashism will have the exit code of the
last command in the pipeline).

If it is just code examples, then you can (mostly) disregard this remark.


Final remark:

>  Test-Command:
> -   cp -r Makefile tests $AUTOPKGTEST_TMP
> -   && cd $AUTOPKGTEST_TMP
> -   && make tests
> +   make unit-tests || true # due to warnings caused by python-pbcore 
> some non-zero value is returned despite all tests are passing - thus adding 
> '|| true'
>  Depends:
> @,
> python-nose,
> python-cram,
> make,
> +   poa
>  Restrictions: allow-stderr

If the autopktest cannot "fail" (both stderr and exit code is ignored),
then it should either not be run or at least be tagged as "superficial"
as a(n unconditional) "Success" is not really saying anything about
whether it worked or exploded in fire and flames.

Thanks,
~Niels

Bug#926256: unblock: gwenview/4:18.04.0-1.1

[Andreas Beckmann]

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

Please unblock package gwenview

This update fixes a file overwrite issue if the obsolete gwenview-i18n
from lenny is still installed (#911638).

unblock gwenview/4:18.04.0-1.1

Andreas
diff -Nru gwenview-18.04.0/debian/changelog gwenview-18.04.0/debian/changelog
--- gwenview-18.04.0/debian/changelog   2018-04-23 06:56:17.0 +0200
+++ gwenview-18.04.0/debian/changelog   2019-03-24 16:07:37.0 +0100
@@ -1,3 +1,10 @@
+gwenview (4:18.04.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add Breaks+Replaces against gwenview-i18n from lenny.  (Closes: #911638)
+
+ -- Andreas Beckmann   Sun, 24 Mar 2019 16:07:37 +0100
+
 gwenview (4:18.04.0-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru gwenview-18.04.0/debian/control gwenview-18.04.0/debian/control
--- gwenview-18.04.0/debian/control 2018-04-23 06:34:28.0 +0200
+++ gwenview-18.04.0/debian/control 2019-03-24 14:11:58.0 +0100
@@ -43,8 +43,8 @@
 Architecture: any
 Depends: kinit, ${misc:Depends}, ${shlibs:Depends}
 Recommends: kamera, kio-extras, qt5-image-formats-plugins
-Breaks: ${kde-l10n:all}
-Replaces: ${kde-l10n:all}
+Breaks: ${kde-l10n:all}, gwenview-i18n
+Replaces: ${kde-l10n:all}, gwenview-i18n
 Description: image viewer
  Gwenview is an image viewer, ideal for browsing and displaying a collection of
  images.  It is capable of showing images in a full-screen slideshow view and

Bug#926255: unblock: filelight/4:18.04.1-1.1

[Andreas Beckmann]

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

Please unblock package filelight

This update fixes a file overwrite issue in case the obsolete
filelight-l10n from squeeze is still installed.  (Closes: #911783)

unblock filelight/4:18.04.1-1.1

Andreas
diff -Nru filelight-18.04.1/debian/changelog filelight-18.04.1/debian/changelog
--- filelight-18.04.1/debian/changelog  2018-05-23 01:11:17.0 +0200
+++ filelight-18.04.1/debian/changelog  2019-03-24 01:54:15.0 +0100
@@ -1,3 +1,10 @@
+filelight (4:18.04.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add Breaks+Replaces against filelight-l10n from squeeze. (Closes: #911783)
+
+ -- Andreas Beckmann   Sun, 24 Mar 2019 01:54:15 +0100
+
 filelight (4:18.04.1-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru filelight-18.04.1/debian/control filelight-18.04.1/debian/control
--- filelight-18.04.1/debian/control2018-05-22 23:51:51.0 +0200
+++ filelight-18.04.1/debian/control2019-03-24 00:59:56.0 +0100
@@ -27,8 +27,8 @@
 Package: filelight
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends}
-Breaks: ${kde-l10n:all}
-Replaces: ${kde-l10n:all}
+Breaks: ${kde-l10n:all}, filelight-l10n
+Replaces: ${kde-l10n:all}, filelight-l10n
 Description: show where your diskspace is being used
  Filelight allows you to understand your disk usage by graphically
  representing your filesystem as a set of concentric, segmented rings.

Bug#926217: marked as done (unblock: libmysofa/0.6~dfsg0-3)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2019 17:30:00 +
with message-id <544a6a69-e4af-328d-5b16-504f9468c...@thykier.net>
and subject line Re: Bug#926217: unblock: libmysofa/0.6~dfsg0-3
has caused the Debian Bug report #926217,
regarding unblock: libmysofa/0.6~dfsg0-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.)


-- 
926217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926217
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: unblock

Please unblock package libmysofa

A vulnerability was discovered in libmysofa which has been
reported as CVE-2019-10672, resp. Debian bug #926125.
While upstream has released a new version of libmysofa to fix the issue, I just
backported the fixes to the version currently in testing.
The debdiff also includes updates to Vcs-* stanzas and maintainer address
(migrating away from the alioth addresses), which i consider non-invasive enough
to be included.

Since the bug is security related and RC, please unblock it in time for buster.

unblock libmysofa/0.6~dfsg0-3

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

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru libmysofa-0.6~dfsg0/debian/changelog 
libmysofa-0.6~dfsg0/debian/changelog
--- libmysofa-0.6~dfsg0/debian/changelog2017-11-20 15:43:42.0 
+0100
+++ libmysofa-0.6~dfsg0/debian/changelog2019-04-01 23:25:15.0 
+0200
@@ -1,3 +1,16 @@
+libmysofa (0.6~dfsg0-3) unstable; urgency=medium
+
+  [ IOhannes m zmölnig ]
+  * Backport fix for CVE-2019-10672 (Closes: #926125)
+
+  [ Ondřej Nový ]
+  * d/control: Set Vcs-* to salsa.debian.org
+
+  [ Felipe Sateler ]
+  * Change maintainer address to debian-multime...@lists.debian.org
+
+ -- IOhannes m zmölnig (Debian/GNU)   Mon, 01 Apr 2019 
23:25:15 +0200
+
 libmysofa (0.6~dfsg0-2) unstable; urgency=medium
 
   * Set Multi-Arch:same (Closes: #882230)
diff -Nru libmysofa-0.6~dfsg0/debian/control libmysofa-0.6~dfsg0/debian/control
--- libmysofa-0.6~dfsg0/debian/control  2017-11-20 15:43:42.0 +0100
+++ libmysofa-0.6~dfsg0/debian/control  2019-04-01 23:25:15.0 +0200
@@ -1,6 +1,6 @@
 Source: libmysofa
 Priority: optional
-Maintainer: Debian Multimedia Maintainers 

+Maintainer: Debian Multimedia Maintainers 
 Uploaders:
  IOhannes m zmölnig (Debian/GNU) ,
 Build-Depends:
@@ -12,8 +12,8 @@
 Standards-Version: 4.1.1
 Section: devel
 Homepage: https://github.com/hoene/libmysofa
-Vcs-Git: https://anonscm.debian.org/git/pkg-multimedia/libmysofa.git
-Vcs-Browser: https://anonscm.debian.org/git/pkg-multimedia/libmysofa.git
+Vcs-Git: https://salsa.debian.org/multimedia-team/libmysofa.git
+Vcs-Browser: https://salsa.debian.org/multimedia-team/libmysofa
 
 Package: libmysofa-dev
 Section: libdevel
diff -Nru libmysofa-0.6~dfsg0/debian/patches/CVE-2019-10672.patch 
libmysofa-0.6~dfsg0/debian/patches/CVE-2019-10672.patch
--- libmysofa-0.6~dfsg0/debian/patches/CVE-2019-10672.patch 1970-01-01 
01:00:00.0 +0100
+++ libmysofa-0.6~dfsg0/debian/patches/CVE-2019-10672.patch 2019-04-01 
23:25:15.0 +0200
@@ -0,0 +1,77 @@
+Description: backported fixes for CVE-2019-10672
+Author: Christian Höne/IOhannes m zmölnig
+Origin: upstream
+Applied-Upstream: d39a171e9c6a1c44dbdf43f9db6c3fbd887e38c1, 
83d21e38f4ed65c2e3d76fc792bdf4abde6ec148, 
05ff8a6903c8a357c6d6fd921276732767741670, 
2ed84bbcf261629adf16c56a5b4532670084842e
+Last-Update: 2019-04-01
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- libmysofa.orig/src/hdf/btree.c
 libmysofa/src/hdf/btree.c
+@@ -308,8 +308,11 @@
+   b = i / elements;
+   x = i % elements + start[0];
+   if (x < sx) {
++
+   j = x * size + b;
+-  ((char*)data->data)[j] = 
output[i];
++  if (j >= 0 && j < 
data->data_len) {
++

Bug#926224: marked as done (unblock pbuilder/0.230.4)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2019 17:27:00 +
with message-id <88f5b363-1fae-ceb7-201b-b8d007ff5...@thykier.net>
and subject line Re: Bug#926224: unblock pbuilder/0.230.4
has caused the Debian Bug report #926224,
regarding unblock pbuilder/0.230.4
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.)


-- 
926224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock

Hi,

it seems we accidentally introduced a serious bug in the last upload.
Luckily the fix is trivial, but it was reported privately to me too late
to block the migration to testing.

anyway, here is the diff:


diffstat for pbuilder-0.230.3 pbuilder-0.230.4

 debian/changelog|8 
 pbuilder-createbuildenv |   12 
 2 files changed, 16 insertions(+), 4 deletions(-)

diff -Nru pbuilder-0.230.3/debian/changelog pbuilder-0.230.4/debian/changelog
--- pbuilder-0.230.3/debian/changelog   2019-03-26 15:44:52.0 +0100
+++ pbuilder-0.230.4/debian/changelog   2019-04-02 11:32:38.0 +0200
@@ -1,3 +1,11 @@
+pbuilder (0.230.4) unstable; urgency=medium
+
+  * createbuildenv:
++ Only try to print debootstrap.log if the file really exists.
++ Properly handle the case of a disabled internal cache.  Closes: #926115
+
+ -- Mattia Rizzolo   Tue, 02 Apr 2019 11:32:38 +0200
+
 pbuilder (0.230.3) unstable; urgency=medium

   [ Marcin Sulikowski ]
diff -Nru pbuilder-0.230.3/pbuilder-createbuildenv 
pbuilder-0.230.4/pbuilder-createbuildenv
--- pbuilder-0.230.3/pbuilder-createbuildenv2019-03-15 15:33:18.0 
+0100
+++ pbuilder-0.230.4/pbuilder-createbuildenv2019-04-02 11:25:17.0 
+0200
@@ -75,16 +75,20 @@
 if ! ( "${DEBOOTSTRAP}" \
 ${ARCHITECTURE:+--arch=$ARCHITECTURE} \
 --include=apt \
-"$USE_CACHE" \
+${USE_CACHE:+"$USE_CACHE"} \
 "${DEBOOTSTRAPOPTS[@]}" \
 "$DISTRIBUTION" \
 "$BUILDPLACE" \
 "$MIRRORSITE" \
 $DEBOOTSTRAPSCRIPT ) ; then
 log.e "$DEBOOTSTRAP failed"
-log.e "Tail of debootstrap.log:"
-tail -n 50 "$BUILDPLACE/debootstrap/debootstrap.log"
-log.e "End of debootstrap.log"
+if [ -f "$BUILDPLACE/debootstrap/debootstrap.log" ]; then
+log.e "Tail of debootstrap.log:"
+tail -n 50 "$BUILDPLACE/debootstrap/debootstrap.log"
+log.e "End of debootstrap.log"
+else
+log.e "debootstrap.log not present"
+fi
 exit 1
 fi



-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Mattia Rizzolo:
> Package: release.debian.org
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Hi,
> 
> it seems we accidentally introduced a serious bug in the last upload.
> Luckily the fix is trivial, but it was reported privately to me too late
> to block the migration to testing.
> 
> anyway, here is the diff:
> 
> 
> [...]
> 

Unblocked, thanks.
~Niels--- End Message ---

Bug#926239: marked as done (unblock: facter/3.11.0-2)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2019 17:26:00 +
with message-id <5c8c02a9-1853-c236-64a6-5dd3d700a...@thykier.net>
and subject line Re: Bug#926239: unblock: facter/3.11.0-2
has caused the Debian Bug report #926239,
regarding unblock: facter/3.11.0-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.)


-- 
926239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926239
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: unblock

Please unblock package facter

3.11.0-2, uploaded today in unstable, adds a missing build-dependency 
and fixes a regression since the facter 2.x series.

The facter package was lacking an explicit B-D on ruby, which has been 
transitively satisfied via rake so far. However, since the source 
directly uses /usr/bin/ruby, it should really B-D on ruby itself (see 
#897556).

Additionally, the version in Buster introduces a small regression 
compared to the 2.x series, by allowing custom facts to completely 
override built-in facts, even when this should not happen. This issue 
was discovered by the DSA and has been fixed upstream, so I 
cherry-picked the relevant commit. See #926197 for details.

Other than that, the package in unstable acknowledges the previous NMU, 
and bumps Standards-Version to 4.3.0.

Full source debdiff since 3.11.0-1.1 attached.

unblock facter/3.11.0-2
--- End Message ---
--- Begin Message ---
Apollon Oikonomopoulos:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package facter
> 
> 3.11.0-2, uploaded today in unstable, adds a missing build-dependency 
> and fixes a regression since the facter 2.x series.
> 
> The facter package was lacking an explicit B-D on ruby, which has been 
> transitively satisfied via rake so far. However, since the source 
> directly uses /usr/bin/ruby, it should really B-D on ruby itself (see 
> #897556).
> 
> Additionally, the version in Buster introduces a small regression 
> compared to the 2.x series, by allowing custom facts to completely 
> override built-in facts, even when this should not happen. This issue 
> was discovered by the DSA and has been fixed upstream, so I 
> cherry-picked the relevant commit. See #926197 for details.
> 
> Other than that, the package in unstable acknowledges the previous NMU, 
> and bumps Standards-Version to 4.3.0.
> 
> Full source debdiff since 3.11.0-1.1 attached.
> 
> unblock facter/3.11.0-2
> 

Unblocked, thanks.
~Niels--- End Message ---

Bug#926162: marked as done (unblock: opensaml/3.0.1-1)

[Debian Bug Tracking System]

Your message dated Tue, 02 Apr 2019 17:28:00 +
with message-id <03607093-bf4b-8049-3a10-42ac49d40...@thykier.net>
and subject line Re: Bug#926162: unblock: opensaml/3.0.1-1
has caused the Debian Bug report #926162,
regarding unblock: opensaml/3.0.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.)


-- 
926162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926162
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: unblock

Please unblock package opensaml

Dear Release Team,

To fix their latest security bug, Shibboleth upstream made a coordinated
patch release of the full stack, as usual.  You already unblocked the
critical part of this (xmltooling and shibboleth-sp) and they even
reached testing, so we're good.  OpenSAML, the middle component also
gained a small patch, and I'm asking you about that now.  It isn't
critical at all, just a tuning down of a handful or error messages to
warn level.  As upstream put it: "The goal of those changes was to reach
a state in which any ERROR in the log requires a necessary operational
response." I think eliminating this deviation would improve the
administration experience and the upstream support opportunities for the
users of buster, thus I ask you to consider accepting it.

The debdiff below does not convey properly how small this change really
is, because the current 3.0.0-2 package carries a forward ported
upstream patch CPPOST-110-Rebenchmark-tests-with-SHA256-disgest.patch,
which was released with 3.0.1 and thus removed from the Debian patch
queue.  So the biggest part of this diff does not appear if you compare
the patched trees.

The result of dh_auto_test was ignored in 3.0.0-1 waiting for the above
patch, and that should have already been reverted in 3.0.0-2, because
all tests succeed again with the patch (I checked the buildd logs
manually now).  So they're safe to reenable and have no effect on the
binary packages.

Finally, the path change in HTTPMetadataProvider.xml fixes a unit test
which requires network access and is skipped during the package build
anyway.  (But also succeeds after the necessary URL configuration now.)

If you're fine with this, I'm ready to upload opensaml/3.0.1-1 to
unstable.

Thanks,
Feri.

diff -Nru opensaml-3.0.0/configure opensaml-3.0.1/configure
--- opensaml-3.0.0/configure2018-07-10 03:09:31.0 +0200
+++ opensaml-3.0.1/configure2019-03-08 16:01:45.0 +0100
@@ -1,6 +1,6 @@
 #! /bin/sh
 # Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.69 for opensaml 3.0.0.
+# Generated by GNU Autoconf 2.69 for opensaml 3.0.1.
 #
 # Report bugs to .
 #
@@ -590,8 +590,8 @@
 # Identity of this package.
 PACKAGE_NAME='opensaml'
 PACKAGE_TARNAME='opensaml'
-PACKAGE_VERSION='3.0.0'
-PACKAGE_STRING='opensaml 3.0.0'
+PACKAGE_VERSION='3.0.1'
+PACKAGE_STRING='opensaml 3.0.1'
 PACKAGE_BUGREPORT='https://issues.shibboleth.net/'
 PACKAGE_URL=''
 
@@ -1430,7 +1430,7 @@
   # Omit some internal or obsolete options to make the list less imposing.
   # This message is too long to be a string in the A/UX 3.1 sh.
   cat <<_ACEOF
-\`configure' configures opensaml 3.0.0 to adapt to many kinds of systems.
+\`configure' configures opensaml 3.0.1 to adapt to many kinds of systems.
 
 Usage: $0 [OPTION]... [VAR=VALUE]...
 
@@ -1500,7 +1500,7 @@
 
 if test -n "$ac_init_help"; then
   case $ac_init_help in
- short | recursive ) echo "Configuration of opensaml 3.0.0:";;
+ short | recursive ) echo "Configuration of opensaml 3.0.1:";;
esac
   cat <<\_ACEOF
 
@@ -1658,7 +1658,7 @@
 test -n "$ac_init_help" && exit $ac_status
 if $ac_init_version; then
   cat <<\_ACEOF
-opensaml configure 3.0.0
+opensaml configure 3.0.1
 generated by GNU Autoconf 2.69
 
 Copyright (C) 2012 Free Software Foundation, Inc.
@@ -2202,7 +2202,7 @@
 This file contains any messages produced by compilers while
 running configure, to aid debugging if configure makes a mistake.
 
-It was created by opensaml $as_me 3.0.0, which was
+It was created by opensaml $as_me 3.0.1, which was
 generated by GNU Autoconf 2.69.  Invocation command line was
 
   $ $0 $@
@@ -3067,7 +3067,7 @@
 
 # Define the identity of the package.
  PACKAGE='opensaml'
- VERSION='3.0.0'
+ VERSION='3.0.1'
 
 
 cat >>confdefs.h <<_ACEOF
@@ -21436,7 +21436,7 @@
 # report actual input values of CONFIG_FILES etc. instead of their
 # values after options handling.
 ac_log="
-This file was extended by 

Processed: Re: Bug#926246: unblock: kronosnet/1.8-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed moreinfo
Bug #926246 [release.debian.org] unblock: kronosnet/1.8-1
Added tag(s) moreinfo and confirmed.

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

Bug#926246: unblock: kronosnet/1.8-1

[Niels Thykier]

Control: tags -1 confirmed moreinfo


Ferenc Wágner:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package kronosnet
> 
> Dear Release Team,
> 
> The latest upstream release of kronosnet fixes a use-after-free and a
> configuration error causing 100% CPU usage, both of which would be very
> good to have in buster.  Besides this, there's a flow change required by
> FreeBSD (which returns EINVAL if the destination address is filled in
> while sending over connected sockets) and some minor logging, test and
> documentation fixes.  Most of the latter does not affect the binary
> packages, because the unit tests and the doxyxml tool is not shipped.
> I'm the only user of this library (via corosync), so the change is also
> very narrow-scoped.  Unfortunately, the debdiff is hard to read due to
> the copyright year updates across the board.  Please consider digging
> through it. :)  I'm ready to upload kronosnet_1.8-1 if you agree.
> 
> Thanks,
> Feri.
> 
> [...]
> 
> unblock kronosnet/1.8-1
> 

Please go ahead and remove the moreinfo tag when it is ready to be
unblocked.

Thanks,
~Niels

Processed: Re: Bug#926021: unblock: lam/7.1.4-6

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - moreinfo
Bug #926021 [release.debian.org] unblock: lam/7.1.4-6
Removed tag(s) moreinfo.

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

Bug#926021: unblock: lam/7.1.4-6

[Andreas Beckmann]

Control: tag -1 - moreinfo

On Sun, 31 Mar 2019 21:15:03 +0100 Jonathan Wiltshire 
wrote:
> I'm afraid this is not "minimal changes". In particular the multi-arch and
> debhelper compat level changes are not appropriate at this stage.

The debhelper compat bump was already reverted, just not documented in
the changelog.

The multiarchification is the only way to properly synchronize the
alternatives handling with openmpi and mpich, all three implementations
need to be co-installable. There are "normal" alternatives for the
binaries and multiarch-alternatives for the libraries, while in stretch
there was only a single alternative for both binaries and libraries. It
would be a horrible mess to support both schemes at the same time.
Unfortunately these issues have been neglected for too long.

> I also have concerns about this package being abandoned upstream since
> 2015, as described in #922633.

I'll let the maintainer comment on this.


Andreas

Processed: Re: Bug#925321: RM: openjdk-8/8u171-b11-2

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #925321 {Done: Paul Gevers } [release.debian.org] RM: 
openjdk-8/8u171-b11-2
Bug reopened
Ignoring request to alter fixed versions of bug #925321 to the same values 
previously set

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

Bug#925321: RM: openjdk-8/8u171-b11-2

[Andreas Beckmann]

Control: reopen -1

On 2019-03-23 07:30, Paul Gevers wrote:
> On 23-03-2019 02:37, Andreas Beckmann wrote:
>> please kick openjdk-8 out of testing, finally it has no rdepends left.
>>
>> The version skew w.r.t. stable, i.e. stretch has a newer version than
>> buster, blocks a lot of piuparts stretch->buster upgrade tests.
> 
> This should be handled in unstable. I have updated bug 915620 for this.

The removal from unstable does not propagate to testing ...

trying: -openjdk-8
skipped: -openjdk-8 (0, 1, 6)
got: 34+0: a-1:a-0:a-0:a-0:i-32:m-0:m-0:m-0:p-0:s-1
* i386: libreoffice-officebean, libreoffice-sdbc-hsqldb

anbe@coccia:~$ dak rm -Rn -s testing openjdk-8
Will remove the following packages from testing:

 openjdk-8 | 8u212-b01-1 | source
openjdk-8-dbg | 8u212-b01-1 | amd64, arm64, armel, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
openjdk-8-demo | 8u212-b01-1 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
openjdk-8-doc | 8u212-b01-1 | all
openjdk-8-jdk | 8u212-b01-1 | amd64, arm64, armel, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
openjdk-8-jdk-headless | 8u212-b01-1 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
openjdk-8-jre | 8u212-b01-1 | amd64, arm64, armel, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
openjdk-8-jre-headless | 8u212-b01-1 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x
openjdk-8-jre-zero | 8u212-b01-1 | amd64, arm64, armhf, i386, ppc64el
openjdk-8-source | 8u212-b01-1 | all

Maintainer: OpenJDK Team 

--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.


Andreas

Bug#926239: Acknowledgement (unblock: facter/3.11.0-2)

[Apollon Oikonomopoulos]

Attaching the source debdiff I forgot :)
diff -Nru facter-3.11.0/debian/changelog facter-3.11.0/debian/changelog
--- facter-3.11.0/debian/changelog  2018-12-01 01:19:32.0 +0200
+++ facter-3.11.0/debian/changelog  2019-04-02 14:24:17.0 +0300
@@ -1,3 +1,13 @@
+facter (3.11.0-2) unstable; urgency=medium
+
+  * Acknowledge 3.11.0-1.1 NMU. Thanks to gregor herrmann!
+  * B-D on ruby (Closes: #897556)
+  * Do not allow unsuitable custom facts to override built-in facts
+(Closes: #926197)
+  * Bump Standards-Version to 4.3.0; no changes needed
+
+ -- Apollon Oikonomopoulos   Tue, 02 Apr 2019 14:24:17 
+0300
+
 facter (3.11.0-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru facter-3.11.0/debian/control facter-3.11.0/debian/control
--- facter-3.11.0/debian/control2018-12-01 01:16:40.0 +0200
+++ facter-3.11.0/debian/control2019-04-02 14:24:17.0 +0300
@@ -28,7 +28,8 @@
  libssl-dev,
  rapidjson-dev,
  ruby-all-dev,
-Standards-Version: 4.1.3
+ ruby,
+Standards-Version: 4.3.0
 Vcs-Git: https://salsa.debian.org/puppet-team/facter.git
 Vcs-Browser: https://salsa.debian.org/puppet-team/facter
 Homepage: https://github.com/puppetlabs/facter
diff -Nru facter-3.11.0/debian/patches/fix-custom-facts-overriding-core.patch 
facter-3.11.0/debian/patches/fix-custom-facts-overriding-core.patch
--- facter-3.11.0/debian/patches/fix-custom-facts-overriding-core.patch 
1970-01-01 02:00:00.0 +0200
+++ facter-3.11.0/debian/patches/fix-custom-facts-overriding-core.patch 
2019-04-02 14:21:58.0 +0300
@@ -0,0 +1,259 @@
+From 4b7d4a7bebe20433c170b57771645cf774f1f281 Mon Sep 17 00:00:00 2001
+From: Enis Inan 
+Date: Sat, 6 Oct 2018 18:44:17 -0700
+Subject: [PATCH] (FACT-1873) Use builtin fact if custom facts don't resolve or
+ have 0 wt.
+
+Previously, if any builtin facts have conflicting custom facts that all
+fail to resolve, and at least one of the custom facts has a weight > 0,
+Facter will not report a value for that fact. This is undesirable
+behavior because we always want to fall back to the builtin value if
+all custom facts fail to resolve. Note that the "weight > 0" part is
+important because Facter _will_ use the builtin value if all custom
+facts have 0 weight.
+
+Furthermore, the builtin fact should have precedence over 0 weight
+custom facts. The existing code enforces this condition when _all_
+custom facts have 0 weight, but it does _not_ enforce the condition
+when only _some_ custom facts have 0 weight. In the latter case, the 0
+weight custom facts will take precedence over the builtin fact value.
+
+This commit fixes the fact resolution logic so that it falls back to the
+built-in fact if all custom facts fail to resolve, while also ensuring
+that it has precedence over 0 weight custom facts.
+---
+ .../conflicts_with_builtin_fact.rb| 106 ++
+ lib/src/ruby/fact.cc  |  98 +---
+ 2 files changed, 163 insertions(+), 41 deletions(-)
+ create mode 100644 
acceptance/tests/custom_facts/conflicts_with_builtin_fact.rb
+
+diff --git a/acceptance/tests/custom_facts/conflicts_with_builtin_fact.rb 
b/acceptance/tests/custom_facts/conflicts_with_builtin_fact.rb
+new file mode 100644
+index ..34c5e615
+--- /dev/null
 b/acceptance/tests/custom_facts/conflicts_with_builtin_fact.rb
+@@ -0,0 +1,106 @@
++test_name 'Facter should appropriately resolve a custom fact when it 
conflicts with a builtin fact' do
++  tag 'risk:medium'
++
++  def create_custom_fact_on(host, custom_fact_dir, fact_file_name, fact)
++fact_file_contents = <<-CUSTOM_FACT
++Facter.add(:#{fact[:name]}) do
++  has_weight #{fact[:weight]}
++  setcode do
++#{fact[:value]}
++  end
++end
++CUSTOM_FACT
++
++fact_file_path = File.join(custom_fact_dir, fact_file_name) 
++create_remote_file(host, fact_file_path, fact_file_contents)
++  end
++
++  def clear_custom_facts_on(host, custom_fact_dir)
++step "Clean-up the previous test's custom facts" do
++  on(agent, "rm -f #{custom_fact_dir}/*")
++end
++  end
++
++  agents.each do |agent|
++custom_fact_dir = agent.tmpdir('facter')
++teardown do
++  on(agent, "rm -rf '#{custom_fact_dir}'")
++end
++
++fact_name = 'timezone'
++builtin_value = on(agent, facter('timezone')).stdout.chomp
++
++step "Verify that Facter uses the custom fact's value when its weight is 
> 0" do
++  custom_fact_value = "custom_timezone"
++  create_custom_fact_on(
++agent,
++custom_fact_dir,
++'custom_timezone.rb',
++name: fact_name,
++weight: 10,
++value: "'#{custom_fact_value}'"
++  )
++
++  on(agent, facter("--custom-dir=#{custom_fact_dir} timezone")) do 
|result|
++assert_match(/#{custom_fact_value}/, result.stdout.chomp, "Facter 
does not use the custom fact's value when its weight is > 0")
++  end
++end
++
++clear_custom_facts_on(agent, 

Bug#910805: stretch-pu: package dnsruby/1.54-2

[Santiago Ruano Rincón]

El 31/03/19 a las 20:08, Adam D. Barratt escribió:
> Control: tags -1 -moreinfo +confirmed
> 
> On Thu, 2018-10-11 at 19:36 +0100, Adam D. Barratt wrote:
> > Control: tags -1 + moreinfo
> > 
> > On Thu, 2018-10-11 at 15:51 +0200, Santiago Ruano Rincón wrote:
> > > I'd like to propose the attached dnsruby NMU to fix two bugs:
> > > 
> > > #908887: include latest DNS trust anchor (KSK-2017)
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908887
> > 
> > The metadata for that bug suggests that it also affects the package
> > in unstable - is that correct?
> > 
> > > #910754: dnsruby: warning: constant ::TimeoutError is deprecated
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910754
> > 
> > That bug has no version information at all. :-( Does it also affect
> > the package in unstable?
> 
> It looks like we never got a reply to the above questions, but they
> seem to have been resolved in the meantime, so please go ahead.

Ups, sorry! Indeed, I didn't answer your questions :-( (and cannot say
why)

Uploading the proposed package to stretch. Thanks!

 -- Santiago


signature.asc
Description: PGP signature

Bug#926239: unblock: facter/3.11.0-2

[Apollon Oikonomopoulos]

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

Please unblock package facter

3.11.0-2, uploaded today in unstable, adds a missing build-dependency 
and fixes a regression since the facter 2.x series.

The facter package was lacking an explicit B-D on ruby, which has been 
transitively satisfied via rake so far. However, since the source 
directly uses /usr/bin/ruby, it should really B-D on ruby itself (see 
#897556).

Additionally, the version in Buster introduces a small regression 
compared to the 2.x series, by allowing custom facts to completely 
override built-in facts, even when this should not happen. This issue 
was discovered by the DSA and has been fixed upstream, so I 
cherry-picked the relevant commit. See #926197 for details.

Other than that, the package in unstable acknowledges the previous NMU, 
and bumps Standards-Version to 4.3.0.

Full source debdiff since 3.11.0-1.1 attached.

unblock facter/3.11.0-2

Re: gpac_0.7.1+dfsg1-1_amd64.changes is NEW

[Chris Lamb]

[Adding alteh...@debian.org to CC]

Hi Reinhard,

> Please let me know if you have any questions and concerns about
> this upload.

Thorsten, you added a note to this; can you go ahead and expand /
accept /etc.?


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Re: gpac_0.7.1+dfsg1-1_amd64.changes is NEW

[Reinhard Tartler]

Dear ftp-master team,

On 2/15/19 7:20 AM, Debian FTP Masters wrote:
> binary:libgpac7 is NEW.
> binary:libgpac7 is NEW.
> 
> Your package has been put into the NEW queue, which requires manual action
> from the ftpteam to process. The upload was otherwise valid (it had a good
> OpenPGP signature and file hashes are valid), so please be patient.
> 
> Packages are routinely processed through to the archive, and do feel
> free to browse the NEW queue[1].
> 
> If there is an issue with the upload, you will receive an email from a
> member of the ftpteam.
> 
> If you have any questions, you may reply to this email.

Now about 6 weeks have passed since I've been uploading this package, and
I do have a question: Is there anything wrong with this package? As you can
see from https://ftp-master.debian.org/new/gpac_0.7.1+dfsg1-1.html, it fixes
RC bugs, and I would recommend to include it in the next stable release,
buster.

Please let me know if you have any questions and concerns about this upload.

I'm CC'ing the release team to inform them about this upload. It will
require a binNMU of the only dependent package, x264. I've test-built it
locally and don't expect any issues with that.

Thank you for your consideration.

Best,
Reinhard

Bug#926230: unblock: openstack-cluster-installer/21

[Thomas Goirand]

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

Dear release team,
Please unblock package openstack-cluster-installer

While continuing the development, I've found a number of issues which I
corrected and backported. This release 21 of openstack-cluster-installer
contains these bugfixes (no new feature).

I have attached the debdiff for the changes, though it may be hard to
read, so I would recommend reading individual commits from Salsa over
here:

https://salsa.debian.org/openstack-team/debian/openstack-cluster-installer/commits/debian/buster

The 8 commits are from 5th of March up to now.

Please unblock openstack-cluster-installer/21.

Cheers,

Thomas Goirand (zigo)
diff -Nru openstack-cluster-installer-20/debian/changelog 
openstack-cluster-installer-21/debian/changelog
--- openstack-cluster-installer-20/debian/changelog 2019-02-20 
14:12:23.0 +0100
+++ openstack-cluster-installer-21/debian/changelog 2019-03-05 
13:46:39.0 +0100
@@ -1,3 +1,18 @@
+openstack-cluster-installer (21) unstable; urgency=medium
+
+  * Bugfix release for Buster which includes:
+- Fixed reserve_ip_to_all_slaves_of_network() call in network_add API call.
+- Correctly check for $mgmt_net["iface2"] and not $onenet when calculating
+  --static-iface.
+- Fix block device list for swiftstore (statsd hostname was breaking it,
+ordering was broken).
+- Correctly set the erlang_cookie for rabbitmq as a random value.
+- Correctly use a a real random key for heat's encryption key.
+- Correct swift pipeline order when using encryption.
+- Correctly set unix rights of drives in /srv/node.
+
+ -- Thomas Goirand   Tue, 05 Mar 2019 13:46:39 +0100
+
 openstack-cluster-installer (20) unstable; urgency=medium
 
   * Set allow_resize_to_same_host to True on all nova nodes.
diff -Nru openstack-cluster-installer-20/puppet/manifests/controller.pp 
openstack-cluster-installer-21/puppet/manifests/controller.pp
--- openstack-cluster-installer-20/puppet/manifests/controller.pp   
2019-02-20 14:12:23.0 +0100
+++ openstack-cluster-installer-21/puppet/manifests/controller.pp   
2019-03-05 13:46:39.0 +0100
@@ -73,6 +73,7 @@
   $all_swiftproxy   = undef,
   $all_swiftproxy_ip= undef,
   $pass_mysql_rootuser  = undef,
+  $pass_rabbitmq_cookie = undef,
   $pass_keystone_db = undef,
   $pass_keystone_messaging  = undef,
   $pass_keystone_adminuser  = undef,
@@ -96,6 +97,7 @@
   $pass_neutron_db  = undef,
   $pass_neutron_messaging   = undef,
   $pass_neutron_authtoken   = undef,
+  $pass_heat_encryptkey = undef,
   $pass_heat_db = undef,
   $pass_heat_messaging  = undef,
   $pass_heat_authtoken  = undef,
@@ -1281,7 +1283,7 @@
   config_cluster   => true,
   cluster_nodes=> $all_masters,
   cluster_node_type=> 'ram',
-  erlang_cookie=> 'XAFSRAFNNFJOFSHLEUFT',
+  erlang_cookie=> $pass_rabbitmq_cookie,
   wipe_db_on_cookie_change => true,
 }->
 rabbitmq_vhost { '/':
@@ -1937,7 +1939,7 @@
   service_name => 'heat-api',
 }
 class { '::heat::engine':
-  auth_encryption_key   => '1234567890AZERTYUIOPMLKJHGFDSQ12',
+  auth_encryption_key   => $pass_heat_encryptkey[0,32],
 #  heat_metadata_server_url  => "${base_url}:8000/orchestration-cfn",
 #  heat_waitcondition_server_url => 
"${base_url}:8000/orchestration-cfn/v1/waitcondition",
 }
diff -Nru openstack-cluster-installer-20/puppet/manifests/swiftproxy.pp 
openstack-cluster-installer-21/puppet/manifests/swiftproxy.pp
--- openstack-cluster-installer-20/puppet/manifests/swiftproxy.pp   
2019-02-20 14:12:23.0 +0100
+++ openstack-cluster-installer-21/puppet/manifests/swiftproxy.pp   
2019-03-05 13:46:39.0 +0100
@@ -156,7 +156,7 @@
   # Because there's no ca_file option in castellan, we must
   # allow swiftproxy to run without encryption  in case we're
   # running on a PoC without a real certificate for the API
-  $pipeline_start = [ 'catch_errors', 'healthcheck' ]
+  $pipeline_start = [ 'catch_errors', 'healthcheck', 'proxy-logging', 'cache', 
'container_sync', 'bulk', 'ratelimit', 's3api', 's3token', 'authtoken', 
'keystone', 'copy', 'container-quotas', 'account-quotas', 'slo', 'dlo', 
'versioned_writes' ]
   if $swift_encryption_key_id == "" {
 $disable_encryption = true
 $pipeline_kms = $pipeline_start
@@ -164,7 +164,7 @@
 $disable_encryption = false
 $pipeline_kms = concat($pipeline_start, [ 'kms_keymaster', 'encryption' ])
   }
-  $pipeline = concat($pipeline_kms, [ 'proxy-logging', 'cache', 
'container_sync', 'bulk', 'ratelimit', 's3api', 's3token', 'authtoken', 
'keystone', 'copy', 'container-quotas', 'account-quotas', 'slo', 'dlo', 
'versioned_writes', 'proxy-server' ])
+  $pipeline = concat($pipeline_kms, [ 'proxy-logging', 

Bug#926224: unblock pbuilder/0.230.4

[Mattia Rizzolo]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock

Hi,

it seems we accidentally introduced a serious bug in the last upload.
Luckily the fix is trivial, but it was reported privately to me too late
to block the migration to testing.

anyway, here is the diff:


diffstat for pbuilder-0.230.3 pbuilder-0.230.4

 debian/changelog|8 
 pbuilder-createbuildenv |   12 
 2 files changed, 16 insertions(+), 4 deletions(-)

diff -Nru pbuilder-0.230.3/debian/changelog pbuilder-0.230.4/debian/changelog
--- pbuilder-0.230.3/debian/changelog   2019-03-26 15:44:52.0 +0100
+++ pbuilder-0.230.4/debian/changelog   2019-04-02 11:32:38.0 +0200
@@ -1,3 +1,11 @@
+pbuilder (0.230.4) unstable; urgency=medium
+
+  * createbuildenv:
++ Only try to print debootstrap.log if the file really exists.
++ Properly handle the case of a disabled internal cache.  Closes: #926115
+
+ -- Mattia Rizzolo   Tue, 02 Apr 2019 11:32:38 +0200
+
 pbuilder (0.230.3) unstable; urgency=medium

   [ Marcin Sulikowski ]
diff -Nru pbuilder-0.230.3/pbuilder-createbuildenv 
pbuilder-0.230.4/pbuilder-createbuildenv
--- pbuilder-0.230.3/pbuilder-createbuildenv2019-03-15 15:33:18.0 
+0100
+++ pbuilder-0.230.4/pbuilder-createbuildenv2019-04-02 11:25:17.0 
+0200
@@ -75,16 +75,20 @@
 if ! ( "${DEBOOTSTRAP}" \
 ${ARCHITECTURE:+--arch=$ARCHITECTURE} \
 --include=apt \
-"$USE_CACHE" \
+${USE_CACHE:+"$USE_CACHE"} \
 "${DEBOOTSTRAPOPTS[@]}" \
 "$DISTRIBUTION" \
 "$BUILDPLACE" \
 "$MIRRORSITE" \
 $DEBOOTSTRAPSCRIPT ) ; then
 log.e "$DEBOOTSTRAP failed"
-log.e "Tail of debootstrap.log:"
-tail -n 50 "$BUILDPLACE/debootstrap/debootstrap.log"
-log.e "End of debootstrap.log"
+if [ -f "$BUILDPLACE/debootstrap/debootstrap.log" ]; then
+log.e "Tail of debootstrap.log:"
+tail -n 50 "$BUILDPLACE/debootstrap/debootstrap.log"
+log.e "End of debootstrap.log"
+else
+log.e "debootstrap.log not present"
+fi
 exit 1
 fi



-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#926222: unblock: pbgenomicconsensus/2.3.2-2

[Andreas Tille]

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

Please unblock package pbgenomicconsensus


I admit the changes are more complex than I would have prefered them to
be.  The usage of the upstream Makefile inside the tests would have
required to re-do the workaround for missing data for some tests as they
were just done in debian/rules.  Instead I moved the code from d/rules
right into upstream makefile to keep the test consistent at package
build time and in autopkgtest.

Unfortunately further patches of the test suite are necessary to deal
with several warnings bloating the output.

Kind regards, Andreas.


unblock pbgenomicconsensus/2.3.2-2

-- System Information:
Debian Release: 9.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru pbgenomicconsensus-2.3.2/debian/changelog 
pbgenomicconsensus-2.3.2/debian/changelog
--- pbgenomicconsensus-2.3.2/debian/changelog   2019-01-11 21:19:28.0 
+0100
+++ pbgenomicconsensus-2.3.2/debian/changelog   2019-04-02 11:02:18.0 
+0200
@@ -1,3 +1,20 @@
+pbgenomicconsensus (2.3.2-2) unstable; urgency=medium
+
+  [ Afif Elghraoui ]
+  * Remove myself from Uploaders
+
+  [ Andreas Tille ]
+  * Add myself to Uploaders
+  * python-pbgenomicconsensus Depends: python-pbconsensuscore
+  * Test Depends: poa
+  * Ignore some warnings which are breaking test results, remove
+tests that are based on non-existing input data
+  * Move exclusion of tests to upstream Makefile via patch rather than
+in d/rules.  This is needed to run autopkgtest successfully
+Closes: #925909
+
+ -- Andreas Tille   Tue, 02 Apr 2019 11:02:18 +0200
+
 pbgenomicconsensus (2.3.2-1) unstable; urgency=medium
 
   * Team upload
diff -Nru pbgenomicconsensus-2.3.2/debian/control 
pbgenomicconsensus-2.3.2/debian/control
--- pbgenomicconsensus-2.3.2/debian/control 2019-01-11 21:19:28.0 
+0100
+++ pbgenomicconsensus-2.3.2/debian/control 2019-04-02 11:02:18.0 
+0200
@@ -1,6 +1,6 @@
 Source: pbgenomicconsensus
 Maintainer: Debian Med Packaging Team 

-Uploaders: Afif Elghraoui 
+Uploaders: Andreas Tille 
 Section: science
 Priority: optional
 Build-Depends: debhelper (>= 12~),
@@ -49,7 +49,8 @@
 Architecture: all
 Section: python
 Depends: ${misc:Depends},
- ${python:Depends}
+ ${python:Depends},
+ python-pbconsensuscore
 Suggests: python-consensuscore2
 Description: Pacific Biosciences variant and consensus caller (Python 2)
  The GenomicConsensus package provides Quiver, Pacific Biosciences'
diff -Nru 
pbgenomicconsensus-2.3.2/debian/patches/ignore_test_requiring_pbtestdata.patch 
pbgenomicconsensus-2.3.2/debian/patches/ignore_test_requiring_pbtestdata.patch
--- 
pbgenomicconsensus-2.3.2/debian/patches/ignore_test_requiring_pbtestdata.patch  
1970-01-01 01:00:00.0 +0100
+++ 
pbgenomicconsensus-2.3.2/debian/patches/ignore_test_requiring_pbtestdata.patch  
2019-04-02 11:02:18.0 +0200
@@ -0,0 +1,21 @@
+Description: Test requires 
https://github.com/PacificBiosciences/PacBioTestData which is not packaged
+Bug-Debian: https://bugs.debian.org/925909
+Author: Andreas Tille 
+Last-Update: Thu, 28 Mar 2019 13:40:21 +0100
+
+--- a/Makefile
 b/Makefile
+@@ -8,7 +8,12 @@ tests: unit-tests basic-tests
+ 
+ unit-tests:
+   # Unit tests
+-  py.test --junit-xml=nosetests.xml tests/unit
++  # ignore tests requiring 
https://github.com/PacificBiosciences/PacBioTestData which is not packaged
++  TMPDIR=$$(mktemp -d /tmp/test_ignore_XX) ; \
++  mv tests/unit/test_tool_contract.py $${TMPDIR} ; \
++  py.test --junit-xml=nosetests.xml tests/unit ; \
++  mv $${TMPDIR}/* tests/unit ; \
++  rmdir $${TMPDIR}
+ 
+ # Note: We need at least cram/0.7 for '--xunit-file'
+ # Note: The cram tests often need h5py.
diff -Nru 
pbgenomicconsensus-2.3.2/debian/patches/ignore_test_using_local_data.patch 
pbgenomicconsensus-2.3.2/debian/patches/ignore_test_using_local_data.patch
--- pbgenomicconsensus-2.3.2/debian/patches/ignore_test_using_local_data.patch  
1970-01-01 01:00:00.0 +0100
+++ pbgenomicconsensus-2.3.2/debian/patches/ignore_test_using_local_data.patch  
2019-04-02 11:02:18.0 +0200
@@ -0,0 +1,28 @@
+Description: Ignore tests that are based on non-existing input data that 
probably reside on upstreams local host
+Bug-Debian: https://bugs.debian.org/925909
+Author: Andreas Tille 
+Last-Update: Thu, 28 Mar 2019 13:40:21 +0100
+
+--- a/Makefile
 b/Makefile
+@@ -20,8 +20,18 @@ unit-tests:
+ 
+ basic-tests:
+   # End-to-end tests
+-  # One of these now needs mummer and exonerate.
+-  PATH=`pwd`:$(PATH) cram --verbose 

Bug#926217: unblock: libmysofa/0.6~dfsg0-3

[IOhannes m zmoelnig]

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

Please unblock package libmysofa

A vulnerability was discovered in libmysofa which has been
reported as CVE-2019-10672, resp. Debian bug #926125.
While upstream has released a new version of libmysofa to fix the issue, I just
backported the fixes to the version currently in testing.
The debdiff also includes updates to Vcs-* stanzas and maintainer address
(migrating away from the alioth addresses), which i consider non-invasive enough
to be included.

Since the bug is security related and RC, please unblock it in time for buster.

unblock libmysofa/0.6~dfsg0-3

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

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru libmysofa-0.6~dfsg0/debian/changelog 
libmysofa-0.6~dfsg0/debian/changelog
--- libmysofa-0.6~dfsg0/debian/changelog2017-11-20 15:43:42.0 
+0100
+++ libmysofa-0.6~dfsg0/debian/changelog2019-04-01 23:25:15.0 
+0200
@@ -1,3 +1,16 @@
+libmysofa (0.6~dfsg0-3) unstable; urgency=medium
+
+  [ IOhannes m zmölnig ]
+  * Backport fix for CVE-2019-10672 (Closes: #926125)
+
+  [ Ondřej Nový ]
+  * d/control: Set Vcs-* to salsa.debian.org
+
+  [ Felipe Sateler ]
+  * Change maintainer address to debian-multime...@lists.debian.org
+
+ -- IOhannes m zmölnig (Debian/GNU)   Mon, 01 Apr 2019 
23:25:15 +0200
+
 libmysofa (0.6~dfsg0-2) unstable; urgency=medium
 
   * Set Multi-Arch:same (Closes: #882230)
diff -Nru libmysofa-0.6~dfsg0/debian/control libmysofa-0.6~dfsg0/debian/control
--- libmysofa-0.6~dfsg0/debian/control  2017-11-20 15:43:42.0 +0100
+++ libmysofa-0.6~dfsg0/debian/control  2019-04-01 23:25:15.0 +0200
@@ -1,6 +1,6 @@
 Source: libmysofa
 Priority: optional
-Maintainer: Debian Multimedia Maintainers 

+Maintainer: Debian Multimedia Maintainers 
 Uploaders:
  IOhannes m zmölnig (Debian/GNU) ,
 Build-Depends:
@@ -12,8 +12,8 @@
 Standards-Version: 4.1.1
 Section: devel
 Homepage: https://github.com/hoene/libmysofa
-Vcs-Git: https://anonscm.debian.org/git/pkg-multimedia/libmysofa.git
-Vcs-Browser: https://anonscm.debian.org/git/pkg-multimedia/libmysofa.git
+Vcs-Git: https://salsa.debian.org/multimedia-team/libmysofa.git
+Vcs-Browser: https://salsa.debian.org/multimedia-team/libmysofa
 
 Package: libmysofa-dev
 Section: libdevel
diff -Nru libmysofa-0.6~dfsg0/debian/patches/CVE-2019-10672.patch 
libmysofa-0.6~dfsg0/debian/patches/CVE-2019-10672.patch
--- libmysofa-0.6~dfsg0/debian/patches/CVE-2019-10672.patch 1970-01-01 
01:00:00.0 +0100
+++ libmysofa-0.6~dfsg0/debian/patches/CVE-2019-10672.patch 2019-04-01 
23:25:15.0 +0200
@@ -0,0 +1,77 @@
+Description: backported fixes for CVE-2019-10672
+Author: Christian Höne/IOhannes m zmölnig
+Origin: upstream
+Applied-Upstream: d39a171e9c6a1c44dbdf43f9db6c3fbd887e38c1, 
83d21e38f4ed65c2e3d76fc792bdf4abde6ec148, 
05ff8a6903c8a357c6d6fd921276732767741670, 
2ed84bbcf261629adf16c56a5b4532670084842e
+Last-Update: 2019-04-01
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- libmysofa.orig/src/hdf/btree.c
 libmysofa/src/hdf/btree.c
+@@ -308,8 +308,11 @@
+   b = i / elements;
+   x = i % elements + start[0];
+   if (x < sx) {
++
+   j = x * size + b;
+-  ((char*)data->data)[j] = 
output[i];
++  if (j >= 0 && j < 
data->data_len) {
++  ((char*) data->data)[j] 
= output[i];
++  }
+   }
+   }
+   break;
+@@ -321,7 +324,9 @@
+   x = x / dy + start[0];
+   if (y < sy && x < sx) {
+   j = ((x * sy + y) * size) + b;
+-  ((char*)data->data)[j] = 
output[i];
++  if (j >= 0 && j < 
data->data_len) {
++  ((char*) data->data)[j] 
= output[i];
++  }
+   }
+   }
+

Bug#926162: unblock: opensaml/3.0.1-1

[wferi]

Control: tags -1 - moreinfo

Niels Thykier  writes:

> Please go ahead with the upload and remove the moreinfo tag when it is
> ready for unblocking.

Hi, opensaml 3.0.1-1 is already in unstable, ready for unblocking.
-- 
Thanks,
Feri

Processed: Re: Bug#926162: unblock: opensaml/3.0.1-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - moreinfo
Bug #926162 [release.debian.org] unblock: opensaml/3.0.1-1
Removed tag(s) moreinfo.

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

Bug#925357: marked as done (unblock: tomoyo-tools/2.6.0-20190305-1)

[Debian Bug Tracking System]

Your message dated Tue, 2 Apr 2019 15:21:19 +0900
with message-id <20190402152119.0c85ec228d1bfbae6d6d8...@iijmio-mail.jp>
and subject line Re: Bug#925357: unblock: tomoyo-tools/2.6.0-20190305-1
has caused the Debian Bug report #925357,
regarding unblock: tomoyo-tools/2.6.0-20190305-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.)


-- 
925357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: wishlist
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package tomoyo-tools

* I'd like to push tomoyo 2.6.0 for buster, since less upstream delta is
  better to reduce maintain cost.
* tomoyo-tools is leaf package, no worries about breaking other packages'
  behavior :) (and it's stable enough, IMHO).

 The blocker for update is debdiff is huge.

> $ wc -l tomoyo.debdiff
>   
> 
> 1528 tomoyo.debdiff

 However, most of above changes are almost same boring changes like this.

 diff -Nru tomoyo-tools-2.5.0-20170102/examples/candy.c 
tomoyo-tools-2.6.0-20190305/examples/candy.c
--- tomoyo-tools-2.5.0-20170102/examples/candy.c2017-01-04 
19:12:17.0 +0900
+++ tomoyo-tools-2.6.0-20190305/examples/candy.c2019-03-05 
09:00:00.0 +0900
@@ -2,11 +2,11 @@
  * candy.c
  *
  * An example program for CERBERUS.
- * ( http://osdn.jp/projects/tomoyo/document/winf2005-en.pdf )
+ * ( https://osdn.jp/projects/tomoyo/document/winf2005-en.pdf )
  *
  * Copyright (C) 2005-2011  NTT DATA CORPORATION
  *
- * Version: 2.5.0   2011/09/29
+ * Version: 2.6.0   2019/03/05
  *
  * This program is free software; you can redistribute it and/or modify it
  * under the terms of the GNU General Public License v2 as published by the

 URL change (use https), version and date update. I've striped down such
 things and diff size becomes just 255 lines (= upstream changes).

> $ wc -l tomoyo.diff 
> 255 tomoyo.diff

 And 1/3 of that is test file, remains are changes to update profile version.

diff --git a/kernel_test/tomoyo_bprm_test.c b/kernel_test/tomoyo_bprm_test.c
index c19d89e..1675ea6 100644
--- a/kernel_test/tomoyo_bprm_test.c
+++ b/kernel_test/tomoyo_bprm_test.c
@@ -178,6 +178,7 @@ int main(int argc, char *argv[])
ccs_test_init();
fprintf(domain_fp, "%s " BINDIR "/true\n", self_domain);
fprintf(domain_fp, "use_profile 255\n");
+   fprintf(domain_fp, "use_group 0\n");
fprintf(domain_fp, "select pid=%u\n", pid);
fprintf(domain_fp, "file read/write %s\n", proc_policy_domain_policy);
set_profile(3, "file::execute");
diff --git a/kernel_test/tomoyo_cond_test.c b/kernel_test/tomoyo_cond_test.c
index 123a2be..da5905d 100644
--- a/kernel_test/tomoyo_cond_test.c
+++ b/kernel_test/tomoyo_cond_test.c
@@ -388,7 +388,10 @@ static void stage_cond_test(void)
 int main(int argc, char *argv[])
 {
ccs_test_init();
-   fprintf(domain_fp, "ignore_global\n");
+   fprintf(domain_fp, "%s " BINDIR "/true\n", self_domain);
+   fprintf(domain_fp, "use_profile 255\n");
+   fprintf(domain_fp, "use_group 0\n");
+   fprintf(domain_fp, "%s\n", self_domain);
fprintf(domain_fp, "file read/write %s\n", proc_policy_domain_policy);
set_profile(3, "file::execute");
set_profile(3, "file::open");
diff --git a/kernel_test/tomoyo_new_file_test.c 
b/kernel_test/tomoyo_new_file_test.c
index 827c595..9c8ed87 100644
--- a/kernel_test/tomoyo_new_file_test.c
+++ b/kernel_test/tomoyo_new_file_test.c
@@ -118,6 +118,7 @@ static void stage_file_test(void)
size_t size = sizeof(buffer);
int pipe_fd[2] = { EOF, EOF };
int err = 0;
+   int flags;
int fd;
char pbuffer[1024];
struct stat sbuf;
@@ -184,6 +185,38 @@ static void stage_file_test(void)
write_domain_policy(policy, 1);
show_result(uselib("/tmp/uselib"), 0);
 
+   policy = "file write /dev/null";
+   fd = open("/dev/null", O_WRONLY);
+   show_result(fd, 0);
+   close(fd);
+   write_domain_policy(policy, 0);
+   fd = open("/dev/null", O_WRONLY);
+   show_result(fd, 1);
+   write_domain_policy(policy, 1);
+   flags = fcntl(fd, F_GETFL, 0) | O_APPEND;
+   policy = "file append /dev/null";
+   show_result(fcntl(fd, F_SETFL, flags), 0);
+   write_domain_policy(policy, 0);
+   show_result(fcntl(fd, F_SETFL, flags), 1);
+  

Bug#925350: unblock: ubuntu-keyring/2018.09.18.1-5

[Hideki Yamane]

On Sat, 23 Mar 2019 23:36:50 +0900 Hideki Yamane  wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock

 Should I provide any other info for unblocking this?


-- 
Hideki Yamane