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

2019-03-26 Thread Robie Basak 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package python-trustme

This fixes an FTBFS. The package previously built fine, pulling in
python3-idna implicitly via python3-cryptography via python3-openssl.
Since then, python3-cryptography stopped depending on python3-idna,
exposing the bug that python-trustme's build does actually depend on
python3-idna but this wasn't explicitly declared. This change declares
explicitly what was being pulled in previously, so shouldn't in itself
cause any functional change; only the FTBFS will be fixed (along with
the usual regression risk associated with a rebuild).

diff -Nru python-trustme-0.4.0/debian/changelog 
python-trustme-0.4.0/debian/changelog
--- python-trustme-0.4.0/debian/changelog   2018-10-13 22:48:59.0 
+0100
+++ python-trustme-0.4.0/debian/changelog   2019-03-26 23:23:50.0 
+
@@ -1,3 +1,10 @@
+python-trustme (0.4.0-2) unstable; urgency=medium
+
+  * Explicitly build-depend on python3-idna to fix FTBFS.
+Closes: #925566.
+
+ -- Robie Basak   Tue, 26 Mar 2019 23:22:42 +
+
 python-trustme (0.4.0-1) unstable; urgency=low
 
   * Initial release. Closes: #910951.
diff -Nru python-trustme-0.4.0/debian/control 
python-trustme-0.4.0/debian/control
--- python-trustme-0.4.0/debian/control 2018-10-13 22:48:59.0 +0100
+++ python-trustme-0.4.0/debian/control 2019-03-26 23:21:57.0 +
@@ -6,6 +6,7 @@
 Build-Depends: debhelper (>= 9~),
dh-python,
python3,
+   python3-idna,
python3-openssl,
python3-pytest,
python3-service-identity,

unblock python-trustme/0.4.0-2


signature.asc
Description: PGP signature

Bug#925501: marked as done (unblock: horizon/14.0.2-3)

2019-03-26 Thread Debian Bug Tracking System 
Your message dated Tue, 26 Mar 2019 22:18:26 +
with message-id 
and subject line unblock horizon
has caused the Debian Bug report #925501,
regarding unblock: horizon/14.0.2-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.)


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

The changelog is self-explanatory:

horizon (3:14.0.2-3) unstable; urgency=medium

  * openstack-dashboard: Add Breaks against obsolete packages from Stretch:
python-app-catalog-ui, python-designate-dashboard, python-ironic-ui,
python-murano-dashboard, python-zaqar-ui (Closes: #925226). Thanks a lot
to Andreas Beckmann for his report, patch and tests.

 -- Thomas Goirand   Mon, 25 Mar 2019 21:44:52 +0100

So, according to Andreas and his tests, the above Breaks: are needed to
correctly perform an upgrade from Stretch to Buster.

Please unblock horizon/14.0.2-3 to allow this fix to enter Buster.
--- End Message ---
--- Begin Message ---
Unblocked horizon.--- End Message ---

Bug#925460: marked as done (unblock: nwchem/6.8.1-5)

2019-03-26 Thread Debian Bug Tracking System 
Your message dated Tue, 26 Mar 2019 22:11:04 +
with message-id 
and subject line unblock nwchem
has caused the Debian Bug report #925460,
regarding unblock: nwchem/6.8.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.)


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


diff -Nru nwchem-6.8.1/debian/changelog nwchem-6.8.1/debian/changelog
--- nwchem-6.8.1/debian/changelog   2019-01-21 23:29:56.0 +0100
+++ nwchem-6.8.1/debian/changelog   2019-03-25 09:52:20.0 +0100
@@ -1,3 +1,11 @@
+nwchem (6.8.1-5) unstable; urgency=medium
+
+  * Team upload
+  * Fix clean target
+Closes: #924817
+
+ -- Andreas Tille   Mon, 25 Mar 2019 09:52:20 +0100
+
 nwchem (6.8.1-4) unstable; urgency=medium

   * debian/patches/15_testsuite_print_output_on_failure.patch: Fixed patch.
diff -Nru nwchem-6.8.1/debian/rules nwchem-6.8.1/debian/rules
--- nwchem-6.8.1/debian/rules   2019-01-02 16:00:09.0 +0100
+++ nwchem-6.8.1/debian/rules   2019-03-25 09:52:20.0 +0100
@@ -85,7 +85,7 @@
-(cd $(CURDIR)/doc && make realclean)
rm -rf $(CURDIR)/bin $(CURDIR)/lib $(CURDIR)/src/tools/lib
rm -rf $(CURDIR)/QA/scratchdir $(CURDIR)/QA/testoutputs
-   rm -f src/util/util_version.F src/stubs.F src/util/util_module_avail.F
+   rm -f src/util/util_version.F src/stubs.F src/util/util_module_avail.F 
src/util/util_nwchem_version.F
find $(CURDIR) -name "*.stamp" | xargs rm -f
dh_auto_clean
rm -f src/config/NWCHEM_CONFIG src/config/nwchem_config.h



unblock nwchem/6.8.1-5

-- 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)
--- End Message ---
--- Begin Message ---
Unblocked nwchem.--- End Message ---

Bug#925569: stretch-pu: package flatpak/0.8.9-0+deb9u3

2019-03-26 Thread Simon McVittie 
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

I've prepared a flatpak update for stable to fix CVE-2019-10063 in
the next point release. The security team told me they don't intend to
release a DSA for this.

May I upload?

I've uploaded 1.2.3-2 to unstable to fix the same thing, although I'm
hoping to replace it with a new upstream release.

Thanks,
smcv
diffstat for flatpak-0.8.9 flatpak-0.8.9

 changelog   |   11 +++
 patches/run-Only-compare-the-lowest-32-ioctl-arg-bits-for-TIOCSTI.patch |   32 ++
 patches/series  |1 
 3 files changed, 43 insertions(+), 1 deletion(-)

diff -Nru flatpak-0.8.9/debian/changelog flatpak-0.8.9/debian/changelog
--- flatpak-0.8.9/debian/changelog	2019-02-11 21:13:02.0 +
+++ flatpak-0.8.9/debian/changelog	2019-03-26 21:11:16.0 +
@@ -1,10 +1,19 @@
+flatpak (0.8.9-0+deb9u3) stretch; urgency=medium
+
+  * d/p/run-Only-compare-the-lowest-32-ioctl-arg-bits-for-TIOCSTI.patch:
+Reject all ioctls that the kernel will interpret as TIOCSTI,
+including those where the high 32 bits in a 64-bit word are nonzero.
+(Closes: #925541, CVE-2019-10063)
+
+ -- Simon McVittie   Tue, 26 Mar 2019 21:11:16 +
+
 flatpak (0.8.9-0+deb9u2) stretch-security; urgency=medium
 
   * d/p/Don-t-expose-proc-when-running-apply_extra.patch:
 Backport patch from upstream v1.2.3: do not let the apply_extra
 script for a system installation modify the host-side executable
 via /proc/self/exe, similar to CVE-2019-5736 in runc
-(Closes: #922059)
+(Closes: #922059; CVE-2019-8308)
 
  -- Simon McVittie   Mon, 11 Feb 2019 21:13:02 +
 
diff -Nru flatpak-0.8.9/debian/patches/run-Only-compare-the-lowest-32-ioctl-arg-bits-for-TIOCSTI.patch flatpak-0.8.9/debian/patches/run-Only-compare-the-lowest-32-ioctl-arg-bits-for-TIOCSTI.patch
--- flatpak-0.8.9/debian/patches/run-Only-compare-the-lowest-32-ioctl-arg-bits-for-TIOCSTI.patch	1970-01-01 01:00:00.0 +0100
+++ flatpak-0.8.9/debian/patches/run-Only-compare-the-lowest-32-ioctl-arg-bits-for-TIOCSTI.patch	2019-03-26 21:11:16.0 +
@@ -0,0 +1,32 @@
+From: Ryan Gonzalez 
+Date: Mon, 25 Mar 2019 13:00:15 -0500
+Subject: run: Only compare the lowest 32 ioctl arg bits for TIOCSTI
+
+Closes #2782.
+
+Closes: #2783
+Approved by: alexlarsson
+
+(cherry picked from commit a9107feeb4b8275b78965b36bf21b92d5724699e)
+
+Origin: upstream, 1.2.4, commit:8e0aaf4b70d6d7c02c331c655e1a05763485085e
+Bug: https://github.com/flatpak/flatpak/issues/2782
+Bug-Debian: https://bugs.debian.org/925541
+Bug-CVE: CVE-2019-10063
+---
+ common/flatpak-run.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/common/flatpak-run.c b/common/flatpak-run.c
+index 9a69f7b..b3ed2ea 100644
+--- a/common/flatpak-run.c
 b/common/flatpak-run.c
+@@ -3866,7 +3866,7 @@ setup_seccomp (GPtrArray  *argv_array,
+ {SCMP_SYS (clone), _A0 (SCMP_CMP_MASKED_EQ, CLONE_NEWUSER, CLONE_NEWUSER)},
+ 
+ /* Don't allow faking input to the controlling tty (CVE-2017-5226) */
+-{SCMP_SYS (ioctl), _A1(SCMP_CMP_EQ, (int)TIOCSTI)},
++{SCMP_SYS (ioctl), _A1 (SCMP_CMP_MASKED_EQ, 0xu, (int) TIOCSTI)},
+   };
+ 
+   struct
diff -Nru flatpak-0.8.9/debian/patches/series flatpak-0.8.9/debian/patches/series
--- flatpak-0.8.9/debian/patches/series	2019-02-11 21:13:02.0 +
+++ flatpak-0.8.9/debian/patches/series	2019-03-26 21:11:16.0 +
@@ -1 +1,2 @@
 Don-t-expose-proc-when-running-apply_extra.patch
+run-Only-compare-the-lowest-32-ioctl-arg-bits-for-TIOCSTI.patch

Re: Fixing stretch debian-installer on armhf

2019-03-26 Thread Vagrant Cascadian 
On 2019-03-09, Adam D. Barratt wrote:
> On Thu, 2019-03-07 at 22:01 +, Ben Hutchings wrote:
>> On Thu, 2019-03-07 at 14:39 +0100, Cyril Brulebois wrote:
>> [...]
>> > > * Rebuild the debian-installer images, pulling in updates from
>> > >   stretch-updates, leaving only armhf netboot targets broken. 
>> > 
>> > Expanding a bit: rebuilding src:debian-installer from the stretch
>> > branch, which has s-p-u enabled, would fetch the fixed kernel and a
>> > couple of its udebs, at build time; the resulting netboot images
>> > wouldn't know about s-p-u though at run time, and would try to load
>> > udebs from stretch.
>> 
>> [...]
>> 
>> Why is that a problem?  The only change made in 4.9.144-3.1 is in the
>> kernel image, and the module udebs don't have versioned dependencies.
>
> However, as an additional data point, the kernel currently sat in NEW
> and destined for stable has an ABI bump. If that's accepted, then I
> assume things will "just work" in the meantime as the old binary
> packages will hang around until they're decrufted, but it's worth
> bearing in mind.

A debian-installer build for stretch-proposed-updates was made, which
may not get merged into stretch before the next point release. For the
time being:

  
https://deb.debian.org/debian/dists/stretch-proposed-updates/main/installer-armhf/

I've successfully tested version "20170615+deb9u5+b3", as well as at
least one other person. It should continue to work until the next point
release, and I'll do at least some minimal testing of the next point
release on armhf before pushing it to stretch so this doesn't happen
again.

More details in:

  https://bugs.debian.org/924129


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#925559: unblock: netlib-java/0.9.3-5

2019-03-26 Thread Andreas Tille 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package netlib-java


diff -Nru netlib-java-0.9.3/debian/changelog netlib-java-0.9.3/debian/changelog
--- netlib-java-0.9.3/debian/changelog  2019-01-13 21:11:05.0 +0100
+++ netlib-java-0.9.3/debian/changelog  2019-03-26 16:47:32.0 +0100
@@ -1,3 +1,10 @@
+netlib-java (0.9.3-5) unstable; urgency=medium
+
+  * Fix URLClassLoader
+Closes: #923759
+
+ -- Andreas Tille   Tue, 26 Mar 2019 16:47:32 +0100
+
 netlib-java (0.9.3-4) unstable; urgency=medium
 
   * Deactivate watch file since in debian/README.source is declared that
diff -Nru netlib-java-0.9.3/debian/patches/series 
netlib-java-0.9.3/debian/patches/series
--- netlib-java-0.9.3/debian/patches/series 2019-01-13 21:11:05.0 
+0100
+++ netlib-java-0.9.3/debian/patches/series 2019-03-26 16:47:32.0 
+0100
@@ -1 +1,2 @@
 update_classpath.patch
+URLClassLoader.patch
diff -Nru netlib-java-0.9.3/debian/patches/URLClassLoader.patch 
netlib-java-0.9.3/debian/patches/URLClassLoader.patch
--- netlib-java-0.9.3/debian/patches/URLClassLoader.patch   1970-01-01 
01:00:00.0 +0100
+++ netlib-java-0.9.3/debian/patches/URLClassLoader.patch   2019-03-26 
16:47:32.0 +0100
@@ -0,0 +1,48 @@
+From: Markus Koschany 
+Date: Mon, 25 Mar 2019 14:44:22 +0100
+Bug-Debian: https://bugs.debian.org/923759
+Subject: URLClassLoader
+
+---
+ src/org/netlib/generate/JavaGenerator.java | 14 --
+ 1 file changed, 12 insertions(+), 2 deletions(-)
+
+diff --git a/src/org/netlib/generate/JavaGenerator.java 
b/src/org/netlib/generate/JavaGenerator.java
+index fda8e9d..15815de 100644
+--- a/src/org/netlib/generate/JavaGenerator.java
 b/src/org/netlib/generate/JavaGenerator.java
+@@ -51,6 +51,8 @@ import org.netlib.util.doubleW;
+ import org.netlib.util.floatW;
+ import org.netlib.util.intW;
+ 
++import java.net.MalformedURLException;
++
+ /**
+  * Due to the depressing number of LAPACK routines, it is much more efficient 
to
+  * auto-generate the Java code for the wrapper and corresponding Java and JNI
+@@ -643,7 +645,8 @@ class JavaGenerator {
+* @return all classes in a given package
+* @see 
http://forum.java.sun.com/thread.jspa?threadID=757391=4326850
+*/
+-  private List> getClasses(String packageName, IClassFilter 
filter) {
++  private List> getClasses(String packageName, IClassFilter 
filter)
++  throws MalformedURLException{
+   String packagePath = packageName.replace('.', '/');
+ //ArrayList classpath = new ArrayList();
+ //String[] classpathString = 
System.getProperty("java.class.path").split(":");
+@@ -658,7 +661,14 @@ class JavaGenerator {
+ //log(Level.SEVERE, classpathString[i] + 
" " + ex.getMessage());
+ //}
+ //}
+-  URL [] classpath = ((URLClassLoader) 
ClassLoader.getSystemClassLoader()).getURLs();
++  URL url1 = new URL("file:///usr/share/java/junit-3.8.2.jar");
++  URL url2 = new URL("file:///usr/share/java/f2jutil-0.8.1.jar");
++  URL url3 = new 
URL("file:///usr/share/java/jlapack-blas-0.8.jar");
++  URL url4 = new 
URL("file:///usr/share/java/jlapack-lapack-0.8.jar");
++  URL url5 = new 
URL("file:///usr/share/java/jlapack-xerbla-0.8.jar");
++  URL url6 = new 
URL("file:///build/netlib-java-0.9.3/build/classes/");
++
++  URL [] classpath = { url1, url2, url3, url4, url5, url6 };
+   List> result = new ArrayList>();
+   System.out.println(Arrays.toString(classpath));
+   for (URL url : classpath) {


unblock netlib-java/0.9.3-5

-- 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)

Re: Bug#924129: debian-installer: Kernel for armhf for stretch unbootable

2019-03-26 Thread Adam D. Barratt 
On Tue, 2019-03-26 at 10:39 -0700, Vagrant Cascadian wrote:
> On 2019-03-26, Adam D. Barratt wrote:
> > On 2019-03-15 06:44, Adam D. Barratt wrote:
> > > The updated images for armhf have been available in p-u for a
> > > couple of
> > > days now.
> > > 
> > > Feedback would be appreciated, as we would like to be able to
> > > accept
> > > the new kernel upload into p-u, which will block a further
> > > rebuild here
> > > as it brings an ABI bump. (The existing images should continue to
> > > work
> > > until the older packages are decrufted in the next point
> > > release.)
> > 
> > Thanks to Peter for the feedback.
> > 
> > Vagrant (or anyone else) - anything to add?
> 
> Just tested fine on BananaPI:
> 
>   https://cdn-aws.deb.debian.org/debian/dists/stretch-proposed-update
> s/main/installer-
> armhf/20170615+deb9u5+b3/images/netboot/netboot.tar.gz
> 
> Installed to SATA. No surprises or anything unusual.
> 
> I'd say it's ready; please push it into stretch.

Thanks for testing.

As I mentioned on IRC, we can't "push it into stretch" without a point
release, and the whole point of this exercise was to avoid having to
schedule another short-notice point release.

However, assuming KiBi has no objections, it sounds like we can go
ahead with getting the -9 ABI kernel into p-u in preparation for the
9.9 point release in a few weeks time. Assuming I haven't missed
anything, the d-i version in p-u should continue to be suitable for
installing stretch on armhf in the meantime (at least until the p-u
freeze hits, at which point d-i will get rebuilt against the new
kernel).

Regards,

Adam

Bug#925489: unblock: elogind/241.1-1+debian1

2019-03-26 Thread Michael Biebl 
Am 26.03.19 um 19:45 schrieb Adam Borowski:
> On Tue, Mar 26, 2019 at 06:52:11PM +0100, Michael Biebl wrote:
>> Just to set the record straight here:
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923244
>>
>> This bug report is from Mon, 25 Feb 2019 11:49:14 +
> 
> That's the "plan 3" bug.  We had plan 1 over a year ago.

I'm not aware of such a bug report. References please.

>> That this all is getting rushed on the last minute is not the fault of
>> the policykit-1 maintainers and I'm not amused that Adam tries to paint
>> it like that.
> 
> I'm not amused either how long it takes to get any response to even a
> single-line patch that had been discussed before.  But, the blame game is
> counterproductive. 

Why did you start it then?

> It had been requested that the point of alternative gets moved.  That
> request is now fulfilled, the code is uploaded, and has seen 12 days of
> testing.  At this point, I kindly request your review.  Is the current
> version of elogind, as packaged by Mark Hindley, good enough for you?

You honestly think with a behaviour like yours I'm motivated to review
your package and spend my time on it? The motivation/time I had dropped
basically to zero reading what you wrote.

If you had a carefully layed out plan, why do we have chaotic and rushed
bug reports like [1]. That doesn't look like a well thought out plan to me.

Anyway, I don't have any interest anymore to spend more time on this, so
don't expect any responses from me from now on.

Michael


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922160#31
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#925489: unblock: elogind/241.1-1+debian1

2019-03-26 Thread Adam Borowski 
On Tue, Mar 26, 2019 at 06:52:11PM +0100, Michael Biebl wrote:
> Just to set the record straight here:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923244
> 
> This bug report is from Mon, 25 Feb 2019 11:49:14 +

That's the "plan 3" bug.  We had plan 1 over a year ago.

> That this all is getting rushed on the last minute is not the fault of
> the policykit-1 maintainers and I'm not amused that Adam tries to paint
> it like that.

I'm not amused either how long it takes to get any response to even a
single-line patch that had been discussed before.  But, the blame game is
counterproductive.  Could we please discuss how to fix present state?

It had been requested that the point of alternative gets moved.  That
request is now fulfilled, the code is uploaded, and has seen 12 days of
testing.  At this point, I kindly request your review.  Is the current
version of elogind, as packaged by Mark Hindley, good enough for you?


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Did ya know that typing "test -j8" instead of "ctest -j8"
⢿⡄⠘⠷⠚⠋⠀ will make your testsuite pass much faster, and fix bugs?
⠈⠳⣄

Bug#925489: unblock: elogind/241.1-1+debian1

2019-03-26 Thread Michael Biebl 
Am 26.03.19 um 14:54 schrieb Adam Borowski:
> It's not a "niche" area.  Without this, any modern GUI desktop environments
> are not installable with any pid 1 other than systemd.  That'd be a massive
> regression that's certainly not acceptable (and it's caused by removal of a
> systemd component with a hard dependency).
> 
> This regression had a plan, with coded and tested patches by January 2018
> (with a refresh + retesting in June, then November, December).  In that
> plan, policykit packages had alternatives built against elogind.  Yet
> patches did not get applied.  Plan 2 was to dlopen() relevant libraries.
> 

Just to set the record straight here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923244

This bug report is from Mon, 25 Feb 2019 11:49:14 +

That this all is getting rushed on the last minute is not the fault of
the policykit-1 maintainers and I'm not amused that Adam tries to paint
it like that.




signature.asc
Description: OpenPGP digital signature

Bug#925549: marked as done (unblock: libdatetime-timezone-perl/1:2.23-1+2019a)

2019-03-26 Thread Debian Bug Tracking System 
Your message dated Tue, 26 Mar 2019 17:42:57 +
with message-id 
and subject line unblock libdatetime-timezone-perl
has caused the Debian Bug report #925549,
regarding unblock: libdatetime-timezone-perl/1:2.23-1+2019a
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I've uploaded libdatetime-timezone-perl/1:2.23-1+2019a to sid. It
contains the Olson timezone database 2019a as perl data files in a
quilt patch.

Changes in 2019a:

Palestine "springs forward" on 2019-03-30 instead of 2019-03-23.
Metlakatla "fell back" to rejoin Alaska Time on 2019-01-20 at 02:00.

Manually condensed debdiff attached.

As the above mentioned changes are already in effect, this might
warrant some aging as well.


unblock libdatetime-timezone-perl/1:2.23-1+2019a


Thanks in advance,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlyaYq1fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgaZmhAAk5W8oNoQBpF7sVwrSip9VaNM87/eCMGsw5FfRfcvAHJTuKwK30d678eP
q5q2cbDvl6q7k6oZhqvDNTSvQxCPyGcnkOHfLpbjeTJoeB3wwyGpvkbt6yhVx3aA
POgoSXoWG1BiuWHAROQyUjqn+Usp/2tzNp60k0u9JYpGbe1K6FqUthEVNYLQ371j
vWlh3/ZFkZMu/kSASRrKGUe0Gf14YzX1JTUwGKq88PGb0foYd4rjY1I40CyYSlsb
GRFQVi/TfjDFrDRcwoPxz/mMp44bRen2P4tzP9WjTHvsr7cFLPG/RT7u05GnlIRi
+sp0D4+SF0aw/unbaEHGpRJ35DhrohsX2qMvXahG2bx1zW2ulLE328Sj3VL5gUab
Uq2XShvM80WyO2X9eJsOCc64sql1ffddah7BiZhEAe4aGJjpQvXKeYTAWQepDPAw
2NW3pPmmWdbvd6ObwNgTmI5WVyoViQkfQnYoG+g8NB+JTAHfgTucqM1sL8yRcVA1
2i+du4h3Fft/DxggWmJtWoH/MHzGZiGoEmr0pvTGsahw8ZefSkmkyc21ZI230686
sF2jHOH26CDUTLkQVpKhEX/KYZl3C4NtfRCIlVolk4WTiU1R5qRmaD00qCLeiwNl
upLadfiWRXdMAxm7kiFFhFFaG+8JSsk11HBxt44WNtl6TdHMdWQ=
=PMRt
-END PGP SIGNATURE-
diff -Nru libdatetime-timezone-perl-2.23/debian/changelog 
libdatetime-timezone-perl-2.23/debian/changelog
--- libdatetime-timezone-perl-2.23/debian/changelog 2018-12-31 
16:21:58.0 +0100
+++ libdatetime-timezone-perl-2.23/debian/changelog 2019-03-26 
18:05:11.0 +0100
@@ -1,3 +1,10 @@
+libdatetime-timezone-perl (1:2.23-1+2019a) unstable; urgency=medium
+
+  * Update to Olson database version 2019a.
+This update contains contemporary changes for Palestine and Metlakatla.
+
+ -- gregor herrmann   Tue, 26 Mar 2019 18:05:11 +0100
+
 libdatetime-timezone-perl (1:2.23-1+2018i) unstable; urgency=high
 
   * Import upstream version 2.23.
diff -Nru libdatetime-timezone-perl-2.23/debian/patches/olson-2019a 
libdatetime-timezone-perl-2.23/debian/patches/olson-2019a
--- libdatetime-timezone-perl-2.23/debian/patches/olson-2019a   1970-01-01 
01:00:00.0 +0100
+++ libdatetime-timezone-perl-2.23/debian/patches/olson-2019a   2019-03-26 
18:05:11.0 +0100
@@ -0,0 +1,14273 @@
+Description: Update to Olson DB 2019a
+Origin: vendor
+Author: gregor herrmann 
+Last-Update: 2019-03-26
+
+--- a/lib/DateTime/TimeZone/Africa/Abidjan.pm
 b/lib/DateTime/TimeZone/Africa/Abidjan.pm
+@@ -3,7 +3,7 @@
+ # DateTime::TimeZone module distribution in the tools/ directory
+ 
+ #
+-# Generated from /tmp/L68fv1TlrY/africa.  Olson data version 2018i
++# Generated from debian/tzdata/africa.  Olson data version 2019a
+ #
+ # Do not edit this file directly.
+ #
+@@ -43,11 +43,11 @@
+ ],
+ ];
+ 
+-sub olson_version {'2018i'}
++sub olson_version {'2019a'}
+ 
+ sub has_dst_changes {0}
+ 
+-sub _max_year {2028}
++sub _max_year {2029}
+ 
+ sub _new_instance {
+ return shift->_init( @_, spans => $spans );
+--- a/lib/DateTime/TimeZone/Asia/Gaza.pm
 b/lib/DateTime/TimeZone/Asia/Gaza.pm
+@@ -3,7 +3,7 @@
+ # DateTime::TimeZone module distribution in the tools/ directory
+ 
+ #
+-# Generated from /tmp/L68fv1TlrY/asia.  Olson data version 2018i
++# Generated from debian/tzdata/asia.  Olson data version 2019a
+ #
+ # Do not edit this file directly.
+ #
+@@ -367,8 +367,44 @@
+ ],
+ [
+ 62314347600, #utc_start 1975-08-30 21:00:00 (Sat)
+-62617960800, #  utc_end 1985-04-13 22:00:00 (Sat)
++62469698400, #  utc_end 1980-08-01 22:00:00 (Fri)
+ 62314354800, #  local_start 1975-08-30 23:00:00 (Sat)
++62469705600, #local_end 1980-08-02 00:00:00 (Sat)
++7200,
++0,
++'IST',
++],
++[
++62469698400, #utc_start 1980-08-01 22:00:00 (Fri)
++62473327200, #  utc_end 1980-09-12

Re: Bug#924129: debian-installer: Kernel for armhf for stretch unbootable

2019-03-26 Thread Vagrant Cascadian 
On 2019-03-26, Adam D. Barratt wrote:
> On 2019-03-15 06:44, Adam D. Barratt wrote:
>> The updated images for armhf have been available in p-u for a couple of
>> days now.
>> 
>> Feedback would be appreciated, as we would like to be able to accept
>> the new kernel upload into p-u, which will block a further rebuild here
>> as it brings an ABI bump. (The existing images should continue to work
>> until the older packages are decrufted in the next point release.)
>
> Thanks to Peter for the feedback.
>
> Vagrant (or anyone else) - anything to add?

Just tested fine on BananaPI:

  
https://cdn-aws.deb.debian.org/debian/dists/stretch-proposed-updates/main/installer-armhf/20170615+deb9u5+b3/images/netboot/netboot.tar.gz

Installed to SATA. No surprises or anything unusual.

I'd say it's ready; please push it into stretch.

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#925548: stretch-pu: package libdatetime-timezone-perl/1:2.09-1+2019a

2019-03-26 Thread gregor herrmann 
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I've uploaded libdatetime-timezone-perl/1:2.09-1+2019a to strech. It
contains the Olson timezone database 2019a as perl data files in a
quilt patch.

Changes in 2019a:

Palestine "springs forward" on 2019-03-30 instead of 2019-03-23.
Metlakatla "fell back" to rejoin Alaska Time on 2019-01-20 at 02:00.

Manually condensed debdiff attached.

As the above mentioned changes are already in effect, this might be
material for stable-updates as well.


Thanks in advance,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlyaYq9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYm9w//a7MOYRqCmtoAn7rcXeWPzJM0e2qIWOhKsnAhwpfiCW735iqMsi+BMC3N
0lrDkiM53ecuFjE3rsabm/bBRz83qzddrzUGjFeXUQCBragOIGy7+CVLJpPsK0k1
QmjnK2lKCxwBdwLiCSCfHRhBNS5C8amtEEJ2A6YY3imeGszHUdvxiXNPJ89lOf+u
eegqhurmh3GRaub3zbtc5kUdYZ/RqZdKB7nuWRANEqr809BrqmPigF4ZHn1SOWvh
hvy5ad32gG59++A42Kc6wDAelf2QzCuVEOecvSk/uN2gjHqXtvuekN322J0NgN/6
5w01f6i9kaQbDUplb59C2OQO8V6tO46TQu+56U2MCsLA81JCPCvHNeAPSNtic73b
pGO8wPEgnWxj09Sgdu3usdC/aVvY9Mls929dZE0sLKCt/+JfWp8UNfm3eTE7hFyN
b+J6A9VAKAyF8sI03hA6HsDZdXlsrLtyonRgBnHsAoKr66Jf1tz3PHO+I3rD+8FQ
t0E+vq1RQgph+mUygCevNUufGsvqFkHUEVc5xE/FuuCywlQBaupvv4D4a0V3MbRy
wYHpYK6hFwfSMovmjIcgddgoTI17motsYP0BlL9HzSn/2xPmt72Bjo24DGl+05Oi
w1m2z1jBVQn6nzsFeCzkQTbO1c9nltqLBGC2/EBfjFG7UupWvCg=
=2Vlu
-END PGP SIGNATURE-
diff -Nru libdatetime-timezone-perl-2.09/debian/changelog 
libdatetime-timezone-perl-2.09/debian/changelog
--- libdatetime-timezone-perl-2.09/debian/changelog 2018-12-31 
16:38:55.0 +0100
+++ libdatetime-timezone-perl-2.09/debian/changelog 2019-03-26 
18:22:03.0 +0100
@@ -1,3 +1,10 @@
+libdatetime-timezone-perl (1:2.09-1+2019a) stretch; urgency=medium
+
+  * Update to Olson database version 2019a.
+This update contains contemporary changes for Palestine and Metlakatla.
+
+ -- gregor herrmann   Tue, 26 Mar 2019 18:22:03 +0100
+
 libdatetime-timezone-perl (1:2.09-1+2018i) stretch; urgency=medium
 
   * Update to Olson database version 2018i.
diff -Nru libdatetime-timezone-perl-2.09/debian/patches/olson-2019a 
libdatetime-timezone-perl-2.09/debian/patches/olson-2019a
--- libdatetime-timezone-perl-2.09/debian/patches/olson-2019a   1970-01-01 
01:00:00.0 +0100
+++ libdatetime-timezone-perl-2.09/debian/patches/olson-2019a   2019-03-26 
18:22:03.0 +0100
@@ -0,0 +1,14677 @@
+Description: Update to Olson DB 2019a
+Origin: vendor
+Author: gregor herrmann 
+Last-Update: 2019-03-26
+
+--- a/lib/DateTime/TimeZone/Africa/Abidjan.pm
 b/lib/DateTime/TimeZone/Africa/Abidjan.pm
+@@ -3,7 +3,7 @@
+ # DateTime::TimeZone module distribution in the tools/ directory
+ 
+ #
+-# Generated from debian/tzdata/africa.  Olson data version 2018i
++# Generated from debian/tzdata/africa.  Olson data version 2019a
+ #
+ # Do not edit this file directly.
+ #
+@@ -43,11 +43,11 @@
+ ],
+ ];
+ 
+-sub olson_version {'2018i'}
++sub olson_version {'2019a'}
+ 
+ sub has_dst_changes {0}
+ 
+-sub _max_year {2028}
++sub _max_year {2029}
+ 
+ sub _new_instance {
+ return shift->_init( @_, spans => $spans );
+--- a/lib/DateTime/TimeZone/Asia/Gaza.pm
 b/lib/DateTime/TimeZone/Asia/Gaza.pm
+@@ -3,7 +3,7 @@
+ # DateTime::TimeZone module distribution in the tools/ directory
+ 
+ #
+-# Generated from debian/tzdata/asia.  Olson data version 2018i
++# Generated from debian/tzdata/asia.  Olson data version 2019a
+ #
+ # Do not edit this file directly.
+ #
+@@ -367,8 +367,44 @@
+ ],
+ [
+ 62314347600, #utc_start 1975-08-30 21:00:00 (Sat)
+-62617960800, #  utc_end 1985-04-13 22:00:00 (Sat)
++62469698400, #  utc_end 1980-08-01 22:00:00 (Fri)
+ 62314354800, #  local_start 1975-08-30 23:00:00 (Sat)
++62469705600, #local_end 1980-08-02 00:00:00 (Sat)
++7200,
++0,
++'IST',
++],
++[
++62469698400, #utc_start 1980-08-01 22:00:00 (Fri)
++62473327200, #  utc_end 1980-09-12 22:00:00 (Fri)
++62469709200, #  local_start 1980-08-02 01:00:00 (Sat)
++62473338000, #local_end 1980-09-13 01:00:00 (Sat)
++10800,
++1,
++'IDT',
++],
++[
++62473327200, #utc_start 1980-09-12 22:00:00 (Fri)
++62588239200, #  utc_end 1984-05-04 22:00:00 (Fri)
++62473334400, #  local_start 1980-09-13 00:00:00 (Sat)
++62588246400, #local_end 1984-05-05 00:00:00 (Sat)
++7200,
++0,
++'IST',
++],
++[
++62588239200, #utc_start 1984-05-04 22:00:00 (Fri)
++62597916000, #  utc_end 1984-08-24 22:00:00 (Fri)
++6258825, #  local_start 1984-05-05 01:00:00 (Sat)
++62597926800, #local_end 1984-08-25 01:00:00 (Sat)
++10800,
++1,
++'IDT',
++],
++[
++62597916000, #utc_start 1984-08-24 22:00:00 (Fri)
++62617960800, #  utc_end 1985-04-13 22:00:00 (Sat)
++62597923200, #

Bug#925549: unblock: libdatetime-timezone-perl/1:2.23-1+2019a

2019-03-26 Thread gregor herrmann 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I've uploaded libdatetime-timezone-perl/1:2.23-1+2019a to sid. It
contains the Olson timezone database 2019a as perl data files in a
quilt patch.

Changes in 2019a:

Palestine "springs forward" on 2019-03-30 instead of 2019-03-23.
Metlakatla "fell back" to rejoin Alaska Time on 2019-01-20 at 02:00.

Manually condensed debdiff attached.

As the above mentioned changes are already in effect, this might
warrant some aging as well.


unblock libdatetime-timezone-perl/1:2.23-1+2019a


Thanks in advance,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlyaYq1fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgaZmhAAk5W8oNoQBpF7sVwrSip9VaNM87/eCMGsw5FfRfcvAHJTuKwK30d678eP
q5q2cbDvl6q7k6oZhqvDNTSvQxCPyGcnkOHfLpbjeTJoeB3wwyGpvkbt6yhVx3aA
POgoSXoWG1BiuWHAROQyUjqn+Usp/2tzNp60k0u9JYpGbe1K6FqUthEVNYLQ371j
vWlh3/ZFkZMu/kSASRrKGUe0Gf14YzX1JTUwGKq88PGb0foYd4rjY1I40CyYSlsb
GRFQVi/TfjDFrDRcwoPxz/mMp44bRen2P4tzP9WjTHvsr7cFLPG/RT7u05GnlIRi
+sp0D4+SF0aw/unbaEHGpRJ35DhrohsX2qMvXahG2bx1zW2ulLE328Sj3VL5gUab
Uq2XShvM80WyO2X9eJsOCc64sql1ffddah7BiZhEAe4aGJjpQvXKeYTAWQepDPAw
2NW3pPmmWdbvd6ObwNgTmI5WVyoViQkfQnYoG+g8NB+JTAHfgTucqM1sL8yRcVA1
2i+du4h3Fft/DxggWmJtWoH/MHzGZiGoEmr0pvTGsahw8ZefSkmkyc21ZI230686
sF2jHOH26CDUTLkQVpKhEX/KYZl3C4NtfRCIlVolk4WTiU1R5qRmaD00qCLeiwNl
upLadfiWRXdMAxm7kiFFhFFaG+8JSsk11HBxt44WNtl6TdHMdWQ=
=PMRt
-END PGP SIGNATURE-
diff -Nru libdatetime-timezone-perl-2.23/debian/changelog 
libdatetime-timezone-perl-2.23/debian/changelog
--- libdatetime-timezone-perl-2.23/debian/changelog 2018-12-31 
16:21:58.0 +0100
+++ libdatetime-timezone-perl-2.23/debian/changelog 2019-03-26 
18:05:11.0 +0100
@@ -1,3 +1,10 @@
+libdatetime-timezone-perl (1:2.23-1+2019a) unstable; urgency=medium
+
+  * Update to Olson database version 2019a.
+This update contains contemporary changes for Palestine and Metlakatla.
+
+ -- gregor herrmann   Tue, 26 Mar 2019 18:05:11 +0100
+
 libdatetime-timezone-perl (1:2.23-1+2018i) unstable; urgency=high
 
   * Import upstream version 2.23.
diff -Nru libdatetime-timezone-perl-2.23/debian/patches/olson-2019a 
libdatetime-timezone-perl-2.23/debian/patches/olson-2019a
--- libdatetime-timezone-perl-2.23/debian/patches/olson-2019a   1970-01-01 
01:00:00.0 +0100
+++ libdatetime-timezone-perl-2.23/debian/patches/olson-2019a   2019-03-26 
18:05:11.0 +0100
@@ -0,0 +1,14273 @@
+Description: Update to Olson DB 2019a
+Origin: vendor
+Author: gregor herrmann 
+Last-Update: 2019-03-26
+
+--- a/lib/DateTime/TimeZone/Africa/Abidjan.pm
 b/lib/DateTime/TimeZone/Africa/Abidjan.pm
+@@ -3,7 +3,7 @@
+ # DateTime::TimeZone module distribution in the tools/ directory
+ 
+ #
+-# Generated from /tmp/L68fv1TlrY/africa.  Olson data version 2018i
++# Generated from debian/tzdata/africa.  Olson data version 2019a
+ #
+ # Do not edit this file directly.
+ #
+@@ -43,11 +43,11 @@
+ ],
+ ];
+ 
+-sub olson_version {'2018i'}
++sub olson_version {'2019a'}
+ 
+ sub has_dst_changes {0}
+ 
+-sub _max_year {2028}
++sub _max_year {2029}
+ 
+ sub _new_instance {
+ return shift->_init( @_, spans => $spans );
+--- a/lib/DateTime/TimeZone/Asia/Gaza.pm
 b/lib/DateTime/TimeZone/Asia/Gaza.pm
+@@ -3,7 +3,7 @@
+ # DateTime::TimeZone module distribution in the tools/ directory
+ 
+ #
+-# Generated from /tmp/L68fv1TlrY/asia.  Olson data version 2018i
++# Generated from debian/tzdata/asia.  Olson data version 2019a
+ #
+ # Do not edit this file directly.
+ #
+@@ -367,8 +367,44 @@
+ ],
+ [
+ 62314347600, #utc_start 1975-08-30 21:00:00 (Sat)
+-62617960800, #  utc_end 1985-04-13 22:00:00 (Sat)
++62469698400, #  utc_end 1980-08-01 22:00:00 (Fri)
+ 62314354800, #  local_start 1975-08-30 23:00:00 (Sat)
++62469705600, #local_end 1980-08-02 00:00:00 (Sat)
++7200,
++0,
++'IST',
++],
++[
++62469698400, #utc_start 1980-08-01 22:00:00 (Fri)
++62473327200, #  utc_end 1980-09-12 22:00:00 (Fri)
++62469709200, #  local_start 1980-08-02 01:00:00 (Sat)
++62473338000, #local_end 1980-09-13 01:00:00 (Sat)
++10800,
++1,
++'IDT',
++],
++[
++62473327200, #utc_start 1980-09-12 22:00:00 (Fri)
++62588239200, #  utc_end 1984-05-04 22:00:00 (Fri)
++62473334400, #  local_start 1980-09-13 00:00:00 (Sat)
++62588246400, #local_end 1984-05-05 00:00:00 (Sat)
++7200,
++0,
++'IST',
++],
++[
++62588239200, #utc_start 1984-05-04 22:00:00 (Fri)
++62597916000, #  utc_end 1984-08-24 22:00:00 (Fri)
++6258825, #  local_start 1984-05-05 01:00:00 (Sat)
++62597926800, #local_end 1984-08-25 01:00:00 (Sat)
++10800,
++1,
++'IDT',
++],
++[
++62597916000, #utc_start 1984-08-24 22:00:00 (Fri)
++62617960800, #  utc_end 1985-04-13 22:00:00 (Sat)

Re: Glibc 2.28 breaks collation for PostgreSQL (and others?)

2019-03-26 Thread Philipp Kern 
On 3/26/2019 3:20 PM, Christoph Berg wrote:
> We were thinking about doing something like that, but that doesn't
> work for the general case - most libc upgrades do not break
> everything, and reindexing would be overkill. It might help for the
> 2.28 upgrade, but getting this to work consistently would require lots
> of scripting with lots of cornercases to cover. I don't think it is
> possible to get this working reliably now, especially as we would need
> to push that "fix" into stretch-proposed-updates as well. (Because
> libc6 will likely be upgraded first, before the new postgresql-common
> version could take action.)

Technically the latter could be solved by libc6 in testing adding a
breaks on postgresql-common. As neither postgresql-common nor
postgresql-client-common seem to depend on libc6 at all, it doesn't
immediately seem crazy to me to do that.

But I don't dispute that the complexity could be high to do this
properly. It's unfortunate that this came up that late, given that it
was already a problem for users of testing.

Kind regards
Philipp Kern

Bug#925536: unblock: pbuilder/0.230.3

2019-03-26 Thread Mattia Rizzolo 
Package: release.debian.org
User: release.debian@packages.debian.org
Usertag: unblock

Dear RT,

please unblock pbuilder/0.230.3, fixing a couple of bugs.
You could argue they are minor, but at least the systemd slice thingy,
and the cross-build one are quite annoying.

The other two new "features" are tiny and easily reviewable (and the
more scary one is covered by the testsuite).

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 pbuilder-0.230.2 pbuilder-0.230.3

 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/Documentation/pbuilder-doc.de.po   |4 -
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/Documentation/pbuilder-doc.fr.po   |2 
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/Documentation/pbuilder-doc.ja.po   |2 
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/Documentation/pbuilder-doc.po  |2 
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/Documentation/pbuilder-doc.xml |2 
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/debian/changelog   |   29 +++
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/debian/control |2 
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/pbuilder-apt-config|2 
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/pbuilder-buildpackage  |4 -
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/pbuilder-buildpackage-funcs|   33 
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/pbuilder-checkparams   |2 
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/pbuilder-createbuildenv|6 +
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/pbuilder-modules   |4 -
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/pbuilder.8 |3 
 /tmp/pyRgYqk0Z_/pbuilder-0.230.3/t/test_pbuilder-buildpackage-funcs |   23 +-
 t/data/fool's \"data /dsc   |   37 ++
 16 files changed, 125 insertions(+), 32 deletions(-)

diff -Nru pbuilder-0.230.2/debian/changelog pbuilder-0.230.3/debian/changelog
--- pbuilder-0.230.2/debian/changelog	2019-02-28 16:42:09.0 +0100
+++ pbuilder-0.230.3/debian/changelog	2019-03-26 15:44:52.0 +0100
@@ -1,9 +1,38 @@
+pbuilder (0.230.3) unstable; urgency=medium
+
+  [ Marcin Sulikowski ]
+  * buildpackage-funcs: Fix whitespace handling in .dsc paths.  MR: !4
+
+  [ Hideki Yamane ]
+  * createbuildenv:
++ Use packages from APTCACHE during debootstrap.  Closes: #432088; MR: !6
+  * doc:
++ Use deb.debian.org as defalut example.  MR: !5
+  * pbuilder.8:
++ Mention qemu-debootstrap as a valid --debootstrap option.  MR: !7
+
+  [ Mattia Rizzolo ]
+  * modules:
++ Always call `systemctl stop` if using systemd's cgroups, preventing
+  stray slices from being left behind.
+
+  [ James Clarke ]
+  * buildpackage-funcs:
++ While setting up the cross-build env, only look at installed bin:gcc,
+  not all available ones.
++ Print a useful error if GCC version detection fails.
++ Handle minor GCC versions and unversioned GCC dependencies.
+
+ -- Mattia Rizzolo   Tue, 26 Mar 2019 15:44:52 +0100
+
 pbuilder (0.230.2) unstable; urgency=medium
 
   [ Mattia Rizzolo ]
   * buildpackage:
 + Fixup the dpkg-dev 1.13.19 check for dpkg-source not supporting
   specifying the extraction directory.  Closes: #918368
++ Do not hardcode libstdc++-6-dev while setting up a cross-build
+  environment, instead check at runtime which version to use.
   Thanks to Helmut and James for finding the (maybe) best formula.
   * d/control:
 + Bump Standards-Version to 4.3.0, no changes needed.
diff -Nru pbuilder-0.230.2/debian/control pbuilder-0.230.3/debian/control
--- pbuilder-0.230.2/debian/control	2019-02-21 11:40:54.0 +0100
+++ pbuilder-0.230.3/debian/control	2019-03-15 15:33:18.0 +0100
@@ -24,7 +24,7 @@
 Architecture: all
 Multi-Arch: foreign
 Depends:
- debootstrap | cdebootstrap,
+ debootstrap (>= 1.0.97) | cdebootstrap,
  dpkg-dev (>= 1.17.0),
  ${misc:Depends},
 Recommends:
diff -Nru pbuilder-0.230.2/Documentation/pbuilder-doc.de.po pbuilder-0.230.3/Documentation/pbuilder-doc.de.po
--- pbuilder-0.230.2/Documentation/pbuilder-doc.de.po	2018-11-23 11:51:49.0 +0100
+++ pbuilder-0.230.3/Documentation/pbuilder-doc.de.po	2019-03-15 15:29:22.0 +0100
@@ -2359,11 +2359,11 @@
 #, no-wrap
 msgid ""
 "pbuilder create --distribution sid --debootstrapopts --arch --debootstrapopts i386 \\\n"
-"  --basetgz /var/cache/pbuilder/base-i386.tgz --mirror http://ftp.jp.debian.org/debian\n"
+"  --basetgz /var/cache/pbuilder/base-i386.tgz --mirror http://deb.debian.org/debian\n"
 "linux32 pbuilder build --basetgz /var/cache/pbuilder/base-i386.tgz"
 msgstr ""
 "pbuilder create --distribution sid --debootstrapopts --arch --debootstrapopts i386 \\\n"
-"  --basetgz

Re: Glibc 2.28 breaks collation for PostgreSQL (and others?)

2019-03-26 Thread Christoph Berg 
Re: Philipp Kern 2019-03-26 <66988de0-f9be-14c0-6b64-df64261fe...@philkern.de>
> I suspect this is why MySQL keeps a whole zoo of collations internally
> that never change.

DB2 and Oracle bundle ICU for that reason, afaict. (But bundling
software has other problems, as we all know...)

> Is there a way upon next (re)start to have a startup script check for
> this case and reindex automatically then - at the expense of a hugely
> enlarged downtime? Say, with a flag file that keeps the glibc major
> version at last restart time around - for the first iteration on this?

We were thinking about doing something like that, but that doesn't
work for the general case - most libc upgrades do not break
everything, and reindexing would be overkill. It might help for the
2.28 upgrade, but getting this to work consistently would require lots
of scripting with lots of cornercases to cover. I don't think it is
possible to get this working reliably now, especially as we would need
to push that "fix" into stretch-proposed-updates as well. (Because
libc6 will likely be upgraded first, before the new postgresql-common
version could take action.)

> That's at least better than silent data corruption, even if still
> disruptive. On the other hand I guess you'd need to start the cluster
> for serving anyway for reindex to work and would then serve broken data
> in the meantime, too?

That's part of the problem, yes.

Christoph

Bug#925489: unblock: elogind/241.1-1+debian1

2019-03-26 Thread Adam Borowski 
It's not a "niche" area.  Without this, any modern GUI desktop environments
are not installable with any pid 1 other than systemd.  That'd be a massive
regression that's certainly not acceptable (and it's caused by removal of a
systemd component with a hard dependency).

This regression had a plan, with coded and tested patches by January 2018
(with a refresh + retesting in June, then November, December).  In that
plan, policykit packages had alternatives built against elogind.  Yet
patches did not get applied.  Plan 2 was to dlopen() relevant libraries.

Then, once a required one-line patch was finally applied to src:systemd
(already in testing), policykit maintainers requested plan 3: to change
libelogind0 to implement 100% of libsystemd0's ABI, so the alternative
works at a different level:

Plan 1:
 ├─ policykit-systemd ─── libsystemd0 ─── systemd
 │
 └─ policykit-elogind ─── libelogind0 ─── elogind

Plan 2:
 └─ policykit ─── libsystemd0 ─┬─ systemd
   │
   └─ elogind

Plan 3:
 └─ policykit ─┬─ libsystemd0 ─── systemd
   │
   └─ libelogind0 ─── elogind

(Consumers of logind API other than policykit go mostly via libpam-*d).

With help of elogind's upstream, this request has been implemented.  Of
course, such a change has a pretty large debdiff.  Yet, with no reports of
regression within 12 days of testing in unstable, I believe it should be
relatively safe.

I'm not really happy with asking for an unblock for such a debdiff -- but
if this can't go in, we'd need to use one of the other plans.  Please say
if you consider that to be better.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Did ya know that typing "test -j8" instead of "ctest -j8"
⢿⡄⠘⠷⠚⠋⠀ will make your testsuite pass much faster, and fix bugs?
⠈⠳⣄

Bug#925532: unblock: fish/3.0.2-2

2019-03-26 Thread Mo Zhou 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package fish

(explain the reason for the unblock here)

Fish's completion script for systemctl starts to print garbage on
the screen since systemd-241. This revision merely fixes the very
annoying behaviour.

Closes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925308

unblock fish/3.0.2-2

(include/attach the debdiff against the package in testing)

~/D/fish ❯❯❯ debdiff --diffstat fish_3.0.2-1.dsc fish_3.0.2-2.dsc
dpkg-source: warning: extracting unsigned source package 
(/home/lumin/Debian/fish/fish_3.0.2-2.dsc)
diffstat for fish-3.0.2 fish-3.0.2

 changelog |7 +++
 patches/c6ec4235136e82c709e8d7b455f7c463f9714b48.diff |   33 ++
 patches/series|1 
 3 files changed, 41 insertions(+)

(...) dch diff truncated

diff -Nru 
fish-3.0.2/debian/patches/c6ec4235136e82c709e8d7b455f7c463f9714b48.diff 
fish-3.0.2/debian/patches/c6ec4235136e82c709e8d7b455f7c463f9714b48.diff
--- fish-3.0.2/debian/patches/c6ec4235136e82c709e8d7b455f7c463f9714b48.diff 
1970-01-01 00:00:00.0 +
+++ fish-3.0.2/debian/patches/c6ec4235136e82c709e8d7b455f7c463f9714b48.diff 
2019-03-26 13:14:08.0 +
@@ -0,0 +1,33 @@
+Source: 
https://github.com/fish-shell/fish-shell/commit/c6ec4235136e82c709e8d7b455f7c463f9714b48
+Fixes: https://github.com/fish-shell/fish-shell/issues/5689
+Closes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925308
+diff --git a/share/completions/systemctl.fish 
b/share/completions/systemctl.fish
+index e42c2aa63..eeeb58cf0 100644
+--- a/share/completions/systemctl.fish
 b/share/completions/systemctl.fish
+@@ -1,13 +1,13 @@
+-set -l systemd_version (systemctl --version | string match "systemd*" | 
string replace -r "\D*(\d+)"  '$1')
++set -l systemd_version (systemctl --version | string match "systemd*" | 
string replace -r "\D*(\d+)\D.*"  '$1')
+ set -l commands list-units list-sockets start stop reload restart try-restart 
reload-or-restart reload-or-try-restart \
+ isolate kill is-active is-failed status show get-cgroup-attr set-cgroup-attr 
unset-cgroup-attr set-cgroup help \
+ reset-failed list-unit-files enable disable is-enabled reenable preset mask 
unmask link load list-jobs cancel dump \
+ list-dependencies snapshot delete daemon-reload daemon-reexec 
show-environment set-environment unset-environment \
+ default rescue emergency halt poweroff reboot kexec exit suspend hibernate 
hybrid-sleep switch-root list-timers \
+ set-property
+-if test $systemd_version -gt 208
++if test $systemd_version -gt 208 2>/dev/null
+ set commands $commands cat
+-if test $systemd_version -gt 217
++if test $systemd_version -gt 217 2>/dev/null
+ set commands $commands edit
+ end
+ end
+@@ -79,7 +79,7 @@ complete -f -c systemctl -l version -d 'Print a short 
version and exit'
+ complete -f -c systemctl -l no-pager -d 'Do not pipe output into a pager'
+ 
+ # New options since systemd 220
+-if test $systemd_version -gt 219
++if test $systemd_version -gt 219 2>/dev/null
+ complete -f -c systemctl -l firmware-setup -n 
"__fish_seen_subcommand_from reboot" -d "Reboot to EFI setup"
+ complete -f -c systemctl -l now -n "__fish_seen_subcommand_from enable" 
-d "Also start unit"
+ complete -f -c systemctl -l now -n "__fish_seen_subcommand_from disable 
mask" -d "Also stop unit"
diff -Nru fish-3.0.2/debian/patches/series fish-3.0.2/debian/patches/series
--- fish-3.0.2/debian/patches/series2019-02-11 16:26:40.0 +
+++ fish-3.0.2/debian/patches/series2019-03-26 13:16:52.0 +
@@ -1,3 +1,4 @@
 use-system-python
 isolate-home-tests
 use-curdir-not-pwd
+c6ec4235136e82c709e8d7b455f7c463f9714b48.diff


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (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_PROPRIETARY_MODULE, 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Re: Glibc 2.28 breaks collation for PostgreSQL (and others?)

2019-03-26 Thread Philipp Kern 
On 3/26/2019 9:45 AM, Christoph Berg wrote:
> Unfortunately not. PostgreSQL supports ICU, but not as the global
> locale for clusters/databases, which is still libc only. And even if
> it was supported, it's not the default, and we are still breaking all
> installations.

I suspect this is why MySQL keeps a whole zoo of collations internally
that never change.

>>> I've been thinking about this for some time, and the best I could come
>>> up so far is "raise a debconf note that people need to invoke REINDEX
>>> DATABASE". The open question about this plan is, how should this note
>>> be triggered.
>>
>> That might not work for unique indices because locale data changes
>> could cause strings to sort the same that were distinct before the
>> update.
> 
> Well, that's not an argument for silently doing nothing. And I doubt
> that this case even exists, for any two distinct strings, the
> collation should output a consistent "less than" or "greater than"
> answer.
> 
> I forgot to mention Plan 3: Mention this in the release notes.
> That should be done anyway, the question being if that is enough.
> My suspicion is that few people actually read the release notes, so
> some notification from inside the system would be needed as well.
> Be it a debconf note, and/or a NEWS.Debian entry somewhere.

Is there a way upon next (re)start to have a startup script check for
this case and reindex automatically then - at the expense of a hugely
enlarged downtime? Say, with a flag file that keeps the glibc major
version at last restart time around - for the first iteration on this?

That's at least better than silent data corruption, even if still
disruptive. On the other hand I guess you'd need to start the cluster
for serving anyway for reindex to work and would then serve broken data
in the meantime, too?

Kind regards
Philipp Kern

Bug#925508: unblock: debian-edu-install/2.10.21

2019-03-26 Thread Cyril Brulebois 
Wolfgang Schweer  (2019-03-25):
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> 
> Please unblock package debian-edu-install
> 
> This is a very tiny change needed to set the right Debian Edu version 
> for the release. Holger Levsen uploaded the package already.
> 
> Full source debdiff against the version in testing attached.
> 
> Cced to debian-boot@ and Cyril Brulebois because an ack is needed due to 
> udebs.
> 
> unblock debian-edu-install/2.10.21

No objections, thanks.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#925525: unblock: glusterfs/5.5-1

2019-03-26 Thread Patrick Matthäi 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hello,

I would like to upload glusterfs 5.5-1 (currently in experimental) to sid and
target this release for buster. It is a bugfix only release, also for a
regression, and has got small changes:

$ diff -Naur glusterfs-5.4/ glusterfs-5.5/ --exclude=.pc --exclude=tests 
--exclude=ChangeLog --exclude=VERSION --exclude=debian --exclude=configure 
--exclude=Makefile --exclude=glusterfs.spec|diffstat
 events/src/peer_eventsapi.py   |8 +--
 extras/systemd/glusterd.service.in |5 +---
 extras/systemd/glustereventsd.service.in   |7 ++
 libglusterfs/src/common-utils.c|   15 -
 libglusterfs/src/common-utils.h|4 +--
 libglusterfs/src/globals.h |4 ++-
 rpc/xdr/src/glusterfs3.h   |2 +
 rpc/xdr/src/glusterfs4-xdr.x   |1
 xlators/cluster/afr/src/afr-self-heal-data.c   |   28 +++--
 xlators/mgmt/glusterd/src/glusterd-brick-ops.c |2 -
 xlators/mgmt/glusterd/src/glusterd-handshake.c |2 -
 xlators/mgmt/glusterd/src/glusterd-utils.c |   12 +++---
 12 files changed, 52 insertions(+), 38 deletions(-)

If you agree with it I would prepare a 5.5-2 for unstable.

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

Kernel: Linux 4.19.0-2-amd64 (SMP w/2 CPU cores)
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)
LSM: AppArmor: enabled

Re: Bug#924129: debian-installer: Kernel for armhf for stretch unbootable

2019-03-26 Thread Adam D. Barratt 

On 2019-03-15 06:44, Adam D. Barratt wrote:

The updated images for armhf have been available in p-u for a couple of
days now.

Feedback would be appreciated, as we would like to be able to accept
the new kernel upload into p-u, which will block a further rebuild here
as it brings an ABI bump. (The existing images should continue to work
until the older packages are decrufted in the next point release.)


Thanks to Peter for the feedback.

Vagrant (or anyone else) - anything to add?

KiBi - do you have any opinions on us going ahead with accepting the new 
kernel (including the ABI bump) into p-u?


Regards,

Adam

Bug#924493: stretch-pu: package publicsuffix/20190221.0923-0+deb9u1

2019-03-26 Thread Daniel Kahn Gillmor 
On Wed 2019-03-13 11:12:26 -0400, Daniel Kahn Gillmor wrote:
> Package: release.debian.org
> Severity: normal
> Tags: stretch
> User: release.debian@packages.debian.org
> Usertags: pu
> Control: affects -1 src:publicsuffix
>
> Please consider an update to publicsuffix in debian stretch.

Ping!

If 20190221.0923-0+deb9u1 of publicsuffix could make it into stretch, we
could close https://bugs.debian.org/879008, a concern from a user that
they're not getting frequent enough updates about the state of the known
publicly-registerable DNS suffixes.

thanks for your work on keeping Debian's stable release in good shape :)

 --dkg


signature.asc
Description: PGP signature

Re: Glibc 2.28 breaks collation for PostgreSQL (and others?)

2019-03-26 Thread Christoph Berg 
Re: Florian Weimer 2019-03-25 <87o95yhp3h@mid.deneb.enyo.de>
> > For PostgreSQL, this means that the ordering of indexes on disk is
> > becoming corrupt, and all "text" (varchar, char, ...) indexes need to
> > be rebuilt. (And worse, if that is not done immediately, the tables
> > might become corrupt because some tuples aren't index-visible anymore
> > due to the incorrect btree ordering.)
> 
> That's fairly normal in a glibc update.  glibc upstream prefers it
> this way.  I've discussed it several times with other glibc
> maintainers.

Changes are normal. What's not normal here is the scale of the
changes, indexes will break for virtually all users.

> My understanding is that ICU provides versioned collation tables,
> which would allow you to avoid this issue.
> 
>   

Unfortunately not. PostgreSQL supports ICU, but not as the global
locale for clusters/databases, which is still libc only. And even if
it was supported, it's not the default, and we are still breaking all
installations.

> > I've been thinking about this for some time, and the best I could come
> > up so far is "raise a debconf note that people need to invoke REINDEX
> > DATABASE". The open question about this plan is, how should this note
> > be triggered.
> 
> That might not work for unique indices because locale data changes
> could cause strings to sort the same that were distinct before the
> update.

Well, that's not an argument for silently doing nothing. And I doubt
that this case even exists, for any two distinct strings, the
collation should output a consistent "less than" or "greater than"
answer.

I forgot to mention Plan 3: Mention this in the release notes.
That should be done anyway, the question being if that is enough.
My suspicion is that few people actually read the release notes, so
some notification from inside the system would be needed as well.
Be it a debconf note, and/or a NEWS.Debian entry somewhere.

I deem this to be release-critical for PostgreSQL users. The reason
I'm asking here is to get input which plan is the best.

Christoph