Bug#923769: unblock: spl-linux/0.7.13-1

2019-03-04 Thread Mo Zhou 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-CC: a...@debian.org

Please unblock package spl-linux
which will land on unstable shortly.

(explain the reason for the unblock here)

  New upstream release (released several hours ago).

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

  Maybe this is much better than the hard-to-review debdiff:
  
https://salsa.debian.org/zfsonlinux-team/spl/compare/debian%2F0.7.12-2...debian%2F0.7.13-1

unblock spl-linux/0.7.13-1

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

Bug#923555: marked as done (unblock: kombu/4.2.1-2)

2019-03-04 Thread Debian Bug Tracking System 
Your message dated Tue, 05 Mar 2019 07:17:00 +
with message-id <85fc307f-2e11-634c-bac9-5edd7ac2f...@thykier.net>
and subject line Re: unblock: kombu/4.2.1-2
has caused the Debian Bug report #923555,
regarding unblock: kombu/4.2.1-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.)


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

Please unblock package kombu

the package FTBFS due to failing tests and 4.2.1-2 adds an upstream patch that
addressed this issue.
It also bumped standards version to 4.3.0 with no changes necessary and cleans
up build artifacts that were introduced by a newer pytest release since tha last
upload.

See attached debdiff for changes.

unblock kombu/4.2.1-2

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

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

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAlx5mRMRHGZsYWRpQGRl
Ymlhbi5vcmcACgkQ/9PIi5l90Wo5HQf/Za1iUTzre1+QLjIAicFsbldIcV/2wOKP
BAe4XXVixv+y9IX/o3bIR3TkmJ5Yd3Bf/hhfXMxvINXPbd/OQsPXiB4Qx9TcPL61
DuX5cL4Fd6D4pFNtZMpyyvL6mppIXlcdlG2kGmXc/T8GVNg/1Z4uI+kwIRYIu+V5
alGNbuQzAUiVmsyGZf5tADCffkQAtbGzQucaJ+V1WZbBTSmBGauWreCgh8+XvgDj
8Phm/XwpHyZ/QD6hZ16vdTZ3v3VePqQpuzBl6RXfx7xMNBj3HiQQsgL6OVrw6xcQ
pbQElG6ueN0SM2jTjvL8Pj6c51rlSDHOw9CqxngMU4Y21BSQZNa81A==
=wcSM
-END PGP SIGNATURE-
diff -Nru kombu-4.2.1/debian/changelog kombu-4.2.1/debian/changelog
--- kombu-4.2.1/debian/changelog2018-06-20 10:02:04.0 +0200
+++ kombu-4.2.1/debian/changelog2019-03-01 20:03:25.0 +0100
@@ -1,3 +1,16 @@
+kombu (4.2.1-2) unstable; urgency=high
+
+  [ Ondřej Nový ]
+  * Use 'python3 -m sphinx' instead of sphinx-build for building docs
+
+  [ Michael Fladischer ]
+  * Apply upstream patch PR#978 to fix failing unittests of pyamqp
+transport (Closes: #921787).
+  * Clean up pytest artifacts to allow two builds in a row.
+  * Bump Standards-Version to 4.3.0.
+
+ -- Michael Fladischer   Fri, 01 Mar 2019 20:03:25 +0100
+
 kombu (4.2.1-1) unstable; urgency=low
 
   [ Ondřej Nový ]
diff -Nru kombu-4.2.1/debian/clean kombu-4.2.1/debian/clean
--- kombu-4.2.1/debian/clean2018-06-20 10:02:04.0 +0200
+++ kombu-4.2.1/debian/clean2019-03-01 20:03:25.0 +0100
@@ -1 +1,4 @@
 kombu.egg-info/
+.pytest_cache/README.md
+.pytest_cache/v/cache/nodeids
+.pytest_cache/v/cache/stepwise
diff -Nru kombu-4.2.1/debian/control kombu-4.2.1/debian/control
--- kombu-4.2.1/debian/control  2018-06-20 10:02:04.0 +0200
+++ kombu-4.2.1/debian/control  2019-03-01 20:03:25.0 +0100
@@ -55,7 +55,7 @@
 Build-Conflicts:
  python-cjson,
  python-sphinx,
-Standards-Version: 4.1.4
+Standards-Version: 4.3.0
 Homepage: https://github.com/celery/kombu/
 Vcs-Git: https://salsa.debian.org/python-team/modules/kombu.git
 Vcs-Browser: https://salsa.debian.org/python-team/modules/kombu
diff -Nru 
kombu-4.2.1/debian/patches/0004-Fix-failing-unittests-of-pyamqp-transport.patch 
kombu-4.2.1/debian/patches/0004-Fix-failing-unittests-of-pyamqp-transport.patch
--- 
kombu-4.2.1/debian/patches/0004-Fix-failing-unittests-of-pyamqp-transport.patch 
1970-01-01 01:00:00.0 +0100
+++ 
kombu-4.2.1/debian/patches/0004-Fix-failing-unittests-of-pyamqp-transport.patch 
2019-03-01 20:03:25.0 +0100
@@ -0,0 +1,27 @@
+From: Matus Valo 
+Date: Thu, 3 Jan 2019 06:43:31 -0800
+Subject: Fix failing unittests of pyamqp transport.
+
+Failing unittests were caused by commit 
f16df2a17630c9804a6da614443c5e862271823f in pyamqp.
+---
+ t/unit/transport/test_pyamqp.py | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/t/unit/transport/test_pyamqp.py b/t/unit/transport/test_pyamqp.py
+index 8292991..32094b4 100644
+--- a/t/unit/transport/test_pyamqp.py
 b/t/unit/transport/test_pyamqp.py
+@@ -68,11 +68,11 @@ class test_Channel:
+ assert self.channel.connection is None
+ 
+ def test_basic_consume_registers_ack_status(self):
+-self.channel.wait_returns = 'my-consumer-tag'
++self.channel.wait_returns =

Bug#923762: marked as done (unblock: mblaze/0.5.1-1)

2019-03-04 Thread Debian Bug Tracking System 
Your message dated Tue, 05 Mar 2019 07:12:00 +
with message-id <810d5c1c-a186-12f0-4159-e60721dc1...@thykier.net>
and subject line Re: Bug#923762: unblock: mblaze/0.5.1-1
has caused the Debian Bug report #923762,
regarding unblock: mblaze/0.5.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.)


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

Dear release team,

I uploaded a new version of mblaze, which reset the package's transition
countdown, which will cause it to miss the hard freeze window:

  https://qa.debian.org/excuses.php?package=mblaze


I did so as the newest upstream release includes security-relevant changes:

  mblaze (0.5.1-1) unstable; urgency=high (security fixes)
  
* New upstream release (2019-03-03)
  + Fixes for buffer-overflows, found by fuzzing.
  + Fixes for memleaks.
  
* Remove unused lintian override
* debian/rules: Remove useless dh_missing invocation.
  A single binary package is being produced.
  
   -- Nicolas Braud-Santoni   Mon, 04 Mar 2019 18:40:01 +0100


Moreover, version 0.5-1 closes several Debian bugs (including a RC one):

  mblaze (0.5-1) unstable; urgency=medium
  
* New upstream release (2019-02-09)
  + Closes: 921891
  + GNUmakefile: correct reference to SOURCE_DATE_EPOCH, patch by Chris Lamb
Closes: #907537 
  
* Rename mless and msort to mblaze-less and mblaze-sort
  Closes: #887988 correctly, avoids conflicts on mpdtoys & msort
  
* Switch to debhelper 12.
  The compatibility level is now controlled by a Build-Depends.
  
* Declare compliance with policy v4.2.1.
  No change required.
  
* debian/rules
  + Make dh_missing fail the build
  + Symlink docs from mblaze-* to mblaze
  
   -- Nicolas Braud-Santoni   Tue, 12 Feb 2019 11:44:33 +0100


The debdiff is attached.


Best,

  nicoo

unblock mblaze/0.5.1-1

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

Kernel: Linux 4.19.0-2-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) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEU7EqA8ZVHYoLJhPE5vmO4pLV7MsFAlx9wacRHG5pY29vQGRl
Ymlhbi5vcmcACgkQ5vmO4pLV7MsdVw//X2febyz+EoW+0lN1iSGZYSeqJhIzC11m
zOippy/KMeCjbjPuqgI1xBTuLBzNYbV+Y6gwf94+4O8KdqRcxHhjP1zE5ttWqVQD
bzMmIB4hr1xIua11OG9Oy1FdG+Fs49nqmaYvo4q7k0qg0VfohwBJEuHnPZEea14y
iT/7o/nnhqNnhZIlNv1dhCJWA00hlMt18/7QjG9bSdYRo8iJUdNmkVY750Adv1+S
MicSLHtnGy+/2AGYxU/0oW6sPFPBLiXli9gpqN6KhwdF4L6aroRnMswfbThxtc/s
GmFETyK/UIJ/6N5pt3ff9fSeU3CHvJclNm4TljKFPfGg4r49Oj+rZeXepddg5Acv
7AaXhB3gMZEwgKtmM02kqwMDdWPRZ3Fwlo6La/3ZJuflNnaBgytlr90Bh8lCAyPI
rMjrtP0jcWq1EIRWUgqCaIPFMfvwPMAyTRtORfzOdGtC9ZOBnEBzuqNgHqv5qpEt
dLQGHFRQJwDrpFc0veWqXZ01UcIO39fNFIMxUf1nAYw80NRcMRvvCT8IUucCLybq
PKn6lLwUfyu+MbfIdyuw7F9hSgMVINmTX1lH8u+Mk1L9p2sn+96JXh1YWAVtrVhn
+k8sSA2P5lOBWQLrRtq34VIjv9zlNRKz+5JO4vbdQ9AuZI+0C77PKK08nnixPCrc
EL4q69REWC0=
=AOMb
-END PGP SIGNATURE-
diff -Nru mblaze-0.4/blaze822.c mblaze-0.5.1/blaze822.c
--- mblaze-0.4/blaze822.c   2018-08-15 17:16:45.0 +0200
+++ mblaze-0.5.1/blaze822.c 2019-03-03 17:12:56.0 +0100
@@ -152,14 +152,20 @@
 // never writes more than dstmax to dst
 // returns how many bytes were appended
 static size_t
-safe_append(char *dst, size_t dstmax, char *strbeg, char *strend)
+safe_append(char *dst, size_t dstmax, char *srcbeg, char *srcend)
 {
-   size_t dstlen = strlen(dst);
-   if (dstmax - dstlen - 1 < strend - strbeg)
-   strend = strbeg + (dstmax - dstlen - 1);
-   memcpy(dst + dstlen, strbeg, strend - strbeg);
-   dst[dstlen + (strend - strbeg)] = 0;
-   return strend - strbeg;
+   size_t srclen = srcend - srcbeg;
+   size_t dstlen = strnlen(dst, dstmax);
+
+   if (dstlen == dstmax)
+   return 0;
+
+   if (dstmax - dstlen < srclen + 1)
+   srclen = dstmax - dstlen - 1;
+   memcpy(dst + dstlen, srcbeg, srclen);
+   dst[dstlen + srclen]

Bug#923587: marked as done (Please give back radare2-cutter on armhf, mipsel)

2019-03-04 Thread Debian Bug Tracking System 
Your message dated Tue, 05 Mar 2019 06:51:00 +
with message-id 
and subject line Re: Bug#923587: Please give back radare2-cutter on armhf, 
mipsel
has caused the Debian Bug report #923587,
regarding Please give back radare2-cutter on armhf, mipsel
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.)


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

radare2-cutter could not be built against radare2 between 3.2.1+dfsg-2
and 3.2.1+dfsg-5 due to missing build-dependencies (#923341).

  gb radare-cutter_1.7.4-2 . armhf mipsel

Thank you.

Cheers,
-Hilko
--- End Message ---
--- Begin Message ---
Hilko Bengen:
> Package: release.debian.org
> Severity: normal
> 
> radare2-cutter could not be built against radare2 between 3.2.1+dfsg-2
> and 3.2.1+dfsg-5 due to missing build-dependencies (#923341).
> 
>   gb radare-cutter_1.7.4-2 . armhf mipsel
> 
> Thank you.
> 
> Cheers,
> -Hilko
> 

Scheduled for radare2-cutter (I assumed the lack of "2" in the gb
command was a typo given radare-cutter did not exist).

Thanks,
~Niels--- End Message ---

Re: Is the freeze the start or end of the day?

2019-03-04 Thread Niels Thykier 
Hi Rebecca,

I realise that the answer now is probably less relevant as your enquiry
had a deadline that has now passed.

Rebecca N. Palmer:
> i.e. are we effectively frozen (due to 10 day testing migration) now?
> 

At the time you wrote, "no".  But "when" it became effectively frozen is
a bit harder to say.  But then, I would rather that we talk about the
concrete packages than last minute uploads.

> I uploaded two new-to-me packages last night, in a hurry after "fix some
> d/copyright lintian errors" became "notice that d/copyright is 5 years
> out of date and that the package contains apparent[0] copyright
> violations".  They both failed to build (one on armhf and one
> everywhere[1]).  Do I fix them from where I've got to, or do I have to
> go back to the version in testing and only make changes that would be
> allowed under full freeze?
> 
> [...]

What packages are we talking about?

Thanks,
~Niels

Bug#923740: unblock: pacemaker/2.0.1-1

2019-03-04 Thread Niels Thykier 
Ferenc Wágner:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Dear Release Team,
> 
> Please advise about the situation with Pacemaker.
> 
> At the moment pacemaker_2.0.1~rc5-1 is 6 days old in unstable (it was
> uploaded on the day following its release) and now that it finally built
> on all architectures (it triggered a linker bug on amd64) I expect it to
> migrate to testing this week, well before the full freeze.
> 
> However, Pacemaker 2.0.1 final was released today and includes a single
> code change only, with the following commit message (the change itself
> is the deletion of lines at the end of the debdiff below):
> 
> High: libcrmcommon: complete interrupted live migrations correctly
> 
> 8435966 (2.0.0) got the sense of compare_version() wrong when
> attempting to remove the old behavior for recording partial live
> migrations, instead re-introducing it.
> 
> This causes a regression in behavior when a transition containing a
> live migration is aborted after the migrate_to has been initiated
> but before the migrate_from has been initiated. In that case, it
> would schedule a full start on the destination node rather than a
> migrate_from.
> 
> I think we should release buster with Pacemaker 2.0.1, thus with this
> fix and the small documentation fixes also bundled with it.  The added
> include directives just make previously indirect includes explicit, and
> our build doesn't use the abi-check script, so that change is a no-op.
> Full debdiff from 2.0.1~rc5-1 (which is on its way to testing):
> 
> [...]
> 
> Even if I uploaded 2.0.1-1 now, it would miss the freeze date by a day,
> kicking out 2.0.1~rc5-1 as well, which would be quite a shame,
> considering that it's almost as good as the final, and definitely better
> than 2.0.1~rc4-1 currently in testing.  Could you please provide a way
> for 2.0.1-1 final (not uploaded yet) to reach buster?
> 
> Thanks,
> Feri.
> 
> unblock pacemaker/2.0.1-1
> 

Hi Feri,

Thanks for filing the report.

Please let the current version of pacemaker as it is and then ping us on
this bug once it have.

Thanks,
~Niels

Freeze exception for pyres and remotecv

2019-03-04 Thread Marcelo Jorge Vieira 
Hi!

Could you, please, unblock pyres and remotecv?
The new pyres version closes #917658.


Cheers,

-- 
Marcelo Jorge Vieira
xmpp:me...@jabber-br.org
http://metaldot.alucinados.com


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

Bug#923762: unblock: mblaze/0.5.1-1

2019-03-04 Thread Nicolas Braud-Santoni 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear release team,

I uploaded a new version of mblaze, which reset the package's transition
countdown, which will cause it to miss the hard freeze window:

  https://qa.debian.org/excuses.php?package=mblaze


I did so as the newest upstream release includes security-relevant changes:

  mblaze (0.5.1-1) unstable; urgency=high (security fixes)
  
* New upstream release (2019-03-03)
  + Fixes for buffer-overflows, found by fuzzing.
  + Fixes for memleaks.
  
* Remove unused lintian override
* debian/rules: Remove useless dh_missing invocation.
  A single binary package is being produced.
  
   -- Nicolas Braud-Santoni   Mon, 04 Mar 2019 18:40:01 +0100


Moreover, version 0.5-1 closes several Debian bugs (including a RC one):

  mblaze (0.5-1) unstable; urgency=medium
  
* New upstream release (2019-02-09)
  + Closes: 921891
  + GNUmakefile: correct reference to SOURCE_DATE_EPOCH, patch by Chris Lamb
Closes: #907537 
  
* Rename mless and msort to mblaze-less and mblaze-sort
  Closes: #887988 correctly, avoids conflicts on mpdtoys & msort
  
* Switch to debhelper 12.
  The compatibility level is now controlled by a Build-Depends.
  
* Declare compliance with policy v4.2.1.
  No change required.
  
* debian/rules
  + Make dh_missing fail the build
  + Symlink docs from mblaze-* to mblaze
  
   -- Nicolas Braud-Santoni   Tue, 12 Feb 2019 11:44:33 +0100


The debdiff is attached.


Best,

  nicoo

unblock mblaze/0.5.1-1

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

Kernel: Linux 4.19.0-2-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) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEU7EqA8ZVHYoLJhPE5vmO4pLV7MsFAlx9wacRHG5pY29vQGRl
Ymlhbi5vcmcACgkQ5vmO4pLV7MsdVw//X2febyz+EoW+0lN1iSGZYSeqJhIzC11m
zOippy/KMeCjbjPuqgI1xBTuLBzNYbV+Y6gwf94+4O8KdqRcxHhjP1zE5ttWqVQD
bzMmIB4hr1xIua11OG9Oy1FdG+Fs49nqmaYvo4q7k0qg0VfohwBJEuHnPZEea14y
iT/7o/nnhqNnhZIlNv1dhCJWA00hlMt18/7QjG9bSdYRo8iJUdNmkVY750Adv1+S
MicSLHtnGy+/2AGYxU/0oW6sPFPBLiXli9gpqN6KhwdF4L6aroRnMswfbThxtc/s
GmFETyK/UIJ/6N5pt3ff9fSeU3CHvJclNm4TljKFPfGg4r49Oj+rZeXepddg5Acv
7AaXhB3gMZEwgKtmM02kqwMDdWPRZ3Fwlo6La/3ZJuflNnaBgytlr90Bh8lCAyPI
rMjrtP0jcWq1EIRWUgqCaIPFMfvwPMAyTRtORfzOdGtC9ZOBnEBzuqNgHqv5qpEt
dLQGHFRQJwDrpFc0veWqXZ01UcIO39fNFIMxUf1nAYw80NRcMRvvCT8IUucCLybq
PKn6lLwUfyu+MbfIdyuw7F9hSgMVINmTX1lH8u+Mk1L9p2sn+96JXh1YWAVtrVhn
+k8sSA2P5lOBWQLrRtq34VIjv9zlNRKz+5JO4vbdQ9AuZI+0C77PKK08nnixPCrc
EL4q69REWC0=
=AOMb
-END PGP SIGNATURE-
diff -Nru mblaze-0.4/blaze822.c mblaze-0.5.1/blaze822.c
--- mblaze-0.4/blaze822.c   2018-08-15 17:16:45.0 +0200
+++ mblaze-0.5.1/blaze822.c 2019-03-03 17:12:56.0 +0100
@@ -152,14 +152,20 @@
 // never writes more than dstmax to dst
 // returns how many bytes were appended
 static size_t
-safe_append(char *dst, size_t dstmax, char *strbeg, char *strend)
+safe_append(char *dst, size_t dstmax, char *srcbeg, char *srcend)
 {
-   size_t dstlen = strlen(dst);
-   if (dstmax - dstlen - 1 < strend - strbeg)
-   strend = strbeg + (dstmax - dstlen - 1);
-   memcpy(dst + dstlen, strbeg, strend - strbeg);
-   dst[dstlen + (strend - strbeg)] = 0;
-   return strend - strbeg;
+   size_t srclen = srcend - srcbeg;
+   size_t dstlen = strnlen(dst, dstmax);
+
+   if (dstlen == dstmax)
+   return 0;
+
+   if (dstmax - dstlen < srclen + 1)
+   srclen = dstmax - dstlen - 1;
+   memcpy(dst + dstlen, srcbeg, srclen);
+   dst[dstlen + srclen] = 0;
+
+   return srclen;
 }
 
 static size_t
@@ -213,8 +219,9 @@
s++;
if (*addr || *disp)
break;
+   } else {
+   s++;
}
-   s++;
} else if (*s == '<') {
char tok[1024] = { 0 };
char *c = tok;
@@ -222,7 +229,9 @@
s++;
while (*s && c < e && *s != '>') {
s = skip_comment(s);
-   if (*s == '"') {
+   if (!*s) {
+   break;
+   } else if (*s == '"') {

Bug#923740: unblock: pacemaker/2.0.1-1

2019-03-04 Thread Ferenc Wágner 
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Dear Release Team,

Please advise about the situation with Pacemaker.

At the moment pacemaker_2.0.1~rc5-1 is 6 days old in unstable (it was
uploaded on the day following its release) and now that it finally built
on all architectures (it triggered a linker bug on amd64) I expect it to
migrate to testing this week, well before the full freeze.

However, Pacemaker 2.0.1 final was released today and includes a single
code change only, with the following commit message (the change itself
is the deletion of lines at the end of the debdiff below):

High: libcrmcommon: complete interrupted live migrations correctly

8435966 (2.0.0) got the sense of compare_version() wrong when
attempting to remove the old behavior for recording partial live
migrations, instead re-introducing it.

This causes a regression in behavior when a transition containing a
live migration is aborted after the migrate_to has been initiated
but before the migrate_from has been initiated. In that case, it
would schedule a full start on the destination node rather than a
migrate_from.

I think we should release buster with Pacemaker 2.0.1, thus with this
fix and the small documentation fixes also bundled with it.  The added
include directives just make previously indirect includes explicit, and
our build doesn't use the abi-check script, so that change is a no-op.
Full debdiff from 2.0.1~rc5-1 (which is on its way to testing):

diff -Nru pacemaker-2.0.1~rc5/abi-check pacemaker-2.0.1/abi-check
--- pacemaker-2.0.1~rc5/abi-check   2019-02-25 22:35:40.0 +0100
+++ pacemaker-2.0.1/abi-check   2019-03-04 20:55:07.0 +0100
@@ -76,7 +76,8 @@
 
 EOF
 
-abi-compliance-checker -l $PACKAGE -dump_abi $DESC
+abi-compliance-checker -l $PACKAGE -dump_abi $DESC \
+-dump-path abi_dumps/${PACKAGE}/${PACKAGE}_${VERSION}.abi.tar.gz
 rm -rf $BUILD_ROOT
 }
 
diff -Nru pacemaker-2.0.1~rc5/ChangeLog pacemaker-2.0.1/ChangeLog
--- pacemaker-2.0.1~rc5/ChangeLog   2019-02-25 22:35:40.0 +0100
+++ pacemaker-2.0.1/ChangeLog   2019-03-04 20:55:07.0 +0100
@@ -1,103 +1,75 @@
-* Mon Feb 25 2019 Ken Gaillot  Pacemaker-2.0.1-rc5
-- Changesets: 17
-- Diff:   15 files changed, 1037 insertions(+), 677 deletions(-)
-
-- Changes since Pacemaker-2.0.1-rc4
-  + scheduler: regression test compatibility with glib 2.59.0
-
-* Tue Jan 29 2019 Ken Gaillot  Pacemaker-2.0.1-rc4
-- Changesets: 42
- 15 files changed, 216 insertions(+), 137 deletions(-)
-
-- Changes since Pacemaker-2.0.1-rc3
-  + attrd: clear election dampening when the writer leaves
-  + controller: clear election dampening when DC is lost
-  + scheduler: don't order non-DC shutdowns before DC fencing
-  + libcrmservice: cancel DBus call when cancelling systemd/upstart actions
-  + tools: remove duplicate fence history state in crm_mon XML output
-  + build: offer configure option to disable tests broken with glib 2.59.0
-  + build: minor logging fixes to allow compatibility with GCC 9 -Werror
-
-* Thu Jan 10 2019 Ken Gaillot  Pacemaker-2.0.1-rc3
-- Changesets: 27
-- Diff:   20 files changed, 375 insertions(+), 195 deletions(-)
-
-- Changes since Pacemaker-2.0.1-rc2
-  + attrd: start new election immediately if writer is lost
-  + attrd: detect alert configuration changes when CIB is entirely replaced
-  + controller: avoid transition timeout if resource cleaned while operation
-is in-flight (regression in 2.0.1-rc1)
-  + libstonithd: restore C++ compatibility (regression in 2.0.1-rc1)
-  + tools: fix crm_resource --clear when lifetime was used with ban/move
-  + tools: fix crm_resource --move when lifetime was used with previous move
-
-* Wed Dec 19 2018 Ken Gaillot  Pacemaker-2.0.1-rc2
-- Changesets: 12
-- Diff:   2 files changed, 6 insertions(+), 2 deletions(-)
-
-- Changes since Pacemaker-2.0.1-rc1
-  + libpe_status: avoid double free of stop_needed list (regression in 
2.0.1-rc1)
-  + tools: stonith_admin -I doesn't require an agent (regression in 2.0.1-rc1)
-
-* Wed Dec 12 2018 Ken Gaillot  Pacemaker-2.0.1-rc1
-- Changesets: 481
- 164 files changed, 7717 insertions(+), 4398 deletions(-)
+* Mon Mar 4 2019 Ken Gaillot  Pacemaker-2.0.1-1
+- Changesets: 592
+ 173 files changed, 9268 insertions(+), 5344 deletions(-)
 
 - Features added since Pacemaker-2.0.0
-  + Pacemaker bundles now support podman container management
-  + fencing: SBD may now be used in a cluster that has guest nodes or bundles
-  + fencing: synchronize fencing history among all nodes
-  + fencing: stonith_admin now has option to clear fence history
-  + tools: crm_mon now supports showing fencing action failures and history
+  + Pacemaker bundles support podman for container management
+  + fencing: SBD may be used in a cluster that has guest nodes or bundles
+  + fencing: fencing history is synchronized among all nodes
+  + fencing:

Bug#906016: transition: gjs built with mozjs60

2019-03-04 Thread Cyril Brulebois 
Hi,

Simon McVittie  (2019-03-02):
> On Tue, 05 Feb 2019 at 10:16:56 +, Simon McVittie wrote:
> > > > * Require task-gnome-desktop to be installable on s390x, but modify
> > > >   meta-gnome3 so that on s390x, gnome-core installs something that is 
> > > > not
> > > >   the full GNOME 3 desktop used on other architectures, for example
> > > >   the GNOME-2-derived gnome-session-flashback
> 
> In the absence of other progress, I've staged this in git. I'll release
> it soon if nobody else in the team gets there first. The resulting
> metapackage appears to be installable on a s390x buster qemu VM with only
> sid as an apt source (so, only able to see the version of gjs in sid that
> we want to migrate, and not the one in buster that we want to supersede).
> 
> On Fri, 08 Feb 2019 at 18:10:01 +0100, Emilio Pozuelo Monfort wrote:
> > My worry if I were to do that is that the installer would still offer to 
> > install
> > GNOME on s390x, and I don't know what would happen if one chose that (I 
> > suppose
> > apt would realise it's uninstallable and give a proper error, but maybe 
> > things
> > would explode).
> > 
> > So if we're going to make task-gnome-desktop uninstallable there, maybe the
> > installer shouldn't offer to install it, and that needs changes somewhere in
> > tasksel or d-i.
> 
> Some questions whose answers I think might be relevant to determining
> how much effort is justifiable here:
> 
> * Do s390x users install with debian-installer?
> * If so, do they install desktop tasks that way?
> * Does GNOME (the desktop, as opposed to individual apps) work on s390x
>   in earlier Debian releases? (If, as I suspect, the answer is "we don't
>   know, nobody has tried it" then that is itself useful information.)

I don't have any answers here. My searching debian-boot@ for “s390x” in
the body and “installation-report” in the subject returned this small
list of bug reports: #575682, #296930, #608407, #694771, #851790,
#859889, #923524 (which you know about…).


Anyway, just to confirm: if one hacks an archive to get gnome-core out
of the amd64's Packages file, tasksel (run from a chroot rather than
from d-i, configured with this hacked repository) still lists the gnome
desktop task as an available option…


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


signature.asc
Description: PGP signature

Bug#923730: marked as done (unblock: deap/1.0.2.post2-6)

2019-03-04 Thread Debian Bug Tracking System 
Your message dated Mon, 04 Mar 2019 18:08:00 +
with message-id 
and subject line Re: Bug#923730: unblock: deap/1.0.2.post2-6
has caused the Debian Bug report #923730,
regarding unblock: deap/1.0.2.post2-6
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.)


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


I uploaded the change

   * Use imgmath Sphinx extension instead of deprecated pngmath.
 Closes: #921778

created by Sascha Steinbiss  in BSP at the DCSO office in 
Berlin.

Since Git contained the following non-invasive changes:

   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/watch: Use https protocol
   * d/tests: Use AUTOPKGTEST_TMP instead of ADTTMP

I kept these and they are part of the upload and the attached debdiff.

Thanks for your work as release team

 Andreas.



unblock deap/1.0.2.post2-6

-- System Information:
Debian Release: 9.6
  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 deap-1.0.2.post2/debian/changelog deap-1.0.2.post2/debian/changelog
--- deap-1.0.2.post2/debian/changelog   2017-07-24 18:49:20.0 +0200
+++ deap-1.0.2.post2/debian/changelog   2019-03-04 17:10:51.0 +0100
@@ -1,3 +1,18 @@
+deap (1.0.2.post2-6) unstable; urgency=medium
+
+  * Team upload.
+
+  [ Ondřej Nový ]
+  * d/control: Set Vcs-* to salsa.debian.org
+  * d/watch: Use https protocol
+  * d/tests: Use AUTOPKGTEST_TMP instead of ADTTMP
+
+  [ Sascha Steinbiss ]
+  * Use imgmath Sphinx extension instead of deprecated pngmath.
+Closes: #921778
+
+ -- Andreas Tille   Mon, 04 Mar 2019 17:10:51 +0100
+
 deap (1.0.2.post2-5) unstable; urgency=medium
 
   * Team upload.
diff -Nru deap-1.0.2.post2/debian/control deap-1.0.2.post2/debian/control
--- deap-1.0.2.post2/debian/control 2017-07-24 18:49:17.0 +0200
+++ deap-1.0.2.post2/debian/control 2019-03-04 17:10:51.0 +0100
@@ -19,8 +19,8 @@
  pandoc
 Standards-Version: 4.0.0
 Homepage: http://deap.gel.ulaval.ca/doc/default/
-Vcs-Git: https://anonscm.debian.org/git/python-modules/packages/deap.git
-Vcs-Browser: https://anonscm.debian.org/cgit/python-modules/packages/deap.git
+Vcs-Git: https://salsa.debian.org/python-team/modules/deap.git
+Vcs-Browser: https://salsa.debian.org/python-team/modules/deap
 
 Package: python-deap
 Architecture: all
diff -Nru deap-1.0.2.post2/debian/patches/0003-remove-pngmath.patch 
deap-1.0.2.post2/debian/patches/0003-remove-pngmath.patch
--- deap-1.0.2.post2/debian/patches/0003-remove-pngmath.patch   1970-01-01 
01:00:00.0 +0100
+++ deap-1.0.2.post2/debian/patches/0003-remove-pngmath.patch   2019-03-04 
17:10:51.0 +0100
@@ -0,0 +1,17 @@
+Description: replace pngmath with imgmath
+ The pngmath Sphinx extension has been deprecated in Sphinx 1.4 and
+ was removed for good in Sphinx 1.8. It can be replaced safely by the
+ imgmath extension, which is also available in 1.4 (so also in stretch).
+Author: Sascha Steinbiss 
+Last-Update: 2019-02-09
+--- a/doc/conf.py
 b/doc/conf.py
+@@ -27,7 +27,7 @@
+ # coming with Sphinx (named 'sphinx.ext.*') or your custom ones
+ 
+ extensions = ['sphinx.ext.autodoc', 'sphinx.ext.doctest', 'sphinx.ext.todo',
+-  'sphinx.ext.pngmath', 'sphinx.ext.intersphinx', 
'sphinx.ext.extlinks'] 
++  'sphinx.ext.imgmath', 'sphinx.ext.intersphinx', 
'sphinx.ext.extlinks']
+ 
+ try:
+ import matplotlib
diff -Nru deap-1.0.2.post2/debian/patches/series 
deap-1.0.2.post2/debian/patches/series
--- deap-1.0.2.post2/debian/patches/series  2017-07-15 20:38:22.0 
+0200
+++ deap-1.0.2.post2/debian/patches/series  2019-03-04 17:10:51.0 
+0100
@@ -1,2 +1,3 @@
 0001-fix-docs.patch
 0002-fix-tests.patch
+0003-remove-pngmath.patch
diff -Nru deap-1.0.2.post2/debian/tests/python3-deap 
deap-1.0.2.post2/debian/tests/python3-deap
--- deap-1.0.2.post2/debian/tests/python3-deap  2017-07-15 20:38:22.0 
+0200
+++ deap-1.0.2.post2/debian/tests/python3-deap  2019-03-04 17:10:51.0 
+0100
@@ -1,6 +1,6 @@
 #!/bin/sh
 set -e -u
 export PYTHONWARNINGS=d
-cp -a deap/tests/ "$ADTTMP"
-cd

Re: Problems with shim and shim-signed in unstable, and proposed solutions to unblock us

2019-03-04 Thread Cyril Brulebois 
Steve McIntyre  (2019-03-04):
> And Mark says:
> 
> "we don't want to go rewinding version numbers in unstable; that could
> lead to all sorts of unforeseeable breakage.
> 
> much as we'd expected. Any more feedback please? Cyril prefers
> approach #2 below, I prefer #3.

To clarify: #2 was my preferred approach when we first tried to get #3 to
work, seeing how many things could need tweaking; #2 is mostly about
re-uploading packages that we know were working (albeit with different
version numbers), which looked more reassuring.

Given the amount of research we've done since then, it seems that we've
ironed out what could be an issue (mostly the fact we moved files from one
binary package to another one), and we didn't spot other packages having
relationships to either binary packages, that could have an issue with the
new layout. Building a binary package for real, even if in a chroot with
some specific versions also looks cleaner to me than repacking and
re-uploading old binaries.

Long story short: #3 looks good to me.


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


signature.asc
Description: PGP signature

Bug#923730: unblock: deap/1.0.2.post2-6

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

Please unblock package deap


I uploaded the change

   * Use imgmath Sphinx extension instead of deprecated pngmath.
 Closes: #921778

created by Sascha Steinbiss  in BSP at the DCSO office in 
Berlin.

Since Git contained the following non-invasive changes:

   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/watch: Use https protocol
   * d/tests: Use AUTOPKGTEST_TMP instead of ADTTMP

I kept these and they are part of the upload and the attached debdiff.

Thanks for your work as release team

 Andreas.



unblock deap/1.0.2.post2-6

-- System Information:
Debian Release: 9.6
  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 deap-1.0.2.post2/debian/changelog deap-1.0.2.post2/debian/changelog
--- deap-1.0.2.post2/debian/changelog   2017-07-24 18:49:20.0 +0200
+++ deap-1.0.2.post2/debian/changelog   2019-03-04 17:10:51.0 +0100
@@ -1,3 +1,18 @@
+deap (1.0.2.post2-6) unstable; urgency=medium
+
+  * Team upload.
+
+  [ Ondřej Nový ]
+  * d/control: Set Vcs-* to salsa.debian.org
+  * d/watch: Use https protocol
+  * d/tests: Use AUTOPKGTEST_TMP instead of ADTTMP
+
+  [ Sascha Steinbiss ]
+  * Use imgmath Sphinx extension instead of deprecated pngmath.
+Closes: #921778
+
+ -- Andreas Tille   Mon, 04 Mar 2019 17:10:51 +0100
+
 deap (1.0.2.post2-5) unstable; urgency=medium
 
   * Team upload.
diff -Nru deap-1.0.2.post2/debian/control deap-1.0.2.post2/debian/control
--- deap-1.0.2.post2/debian/control 2017-07-24 18:49:17.0 +0200
+++ deap-1.0.2.post2/debian/control 2019-03-04 17:10:51.0 +0100
@@ -19,8 +19,8 @@
  pandoc
 Standards-Version: 4.0.0
 Homepage: http://deap.gel.ulaval.ca/doc/default/
-Vcs-Git: https://anonscm.debian.org/git/python-modules/packages/deap.git
-Vcs-Browser: https://anonscm.debian.org/cgit/python-modules/packages/deap.git
+Vcs-Git: https://salsa.debian.org/python-team/modules/deap.git
+Vcs-Browser: https://salsa.debian.org/python-team/modules/deap
 
 Package: python-deap
 Architecture: all
diff -Nru deap-1.0.2.post2/debian/patches/0003-remove-pngmath.patch 
deap-1.0.2.post2/debian/patches/0003-remove-pngmath.patch
--- deap-1.0.2.post2/debian/patches/0003-remove-pngmath.patch   1970-01-01 
01:00:00.0 +0100
+++ deap-1.0.2.post2/debian/patches/0003-remove-pngmath.patch   2019-03-04 
17:10:51.0 +0100
@@ -0,0 +1,17 @@
+Description: replace pngmath with imgmath
+ The pngmath Sphinx extension has been deprecated in Sphinx 1.4 and
+ was removed for good in Sphinx 1.8. It can be replaced safely by the
+ imgmath extension, which is also available in 1.4 (so also in stretch).
+Author: Sascha Steinbiss 
+Last-Update: 2019-02-09
+--- a/doc/conf.py
 b/doc/conf.py
+@@ -27,7 +27,7 @@
+ # coming with Sphinx (named 'sphinx.ext.*') or your custom ones
+ 
+ extensions = ['sphinx.ext.autodoc', 'sphinx.ext.doctest', 'sphinx.ext.todo',
+-  'sphinx.ext.pngmath', 'sphinx.ext.intersphinx', 
'sphinx.ext.extlinks'] 
++  'sphinx.ext.imgmath', 'sphinx.ext.intersphinx', 
'sphinx.ext.extlinks']
+ 
+ try:
+ import matplotlib
diff -Nru deap-1.0.2.post2/debian/patches/series 
deap-1.0.2.post2/debian/patches/series
--- deap-1.0.2.post2/debian/patches/series  2017-07-15 20:38:22.0 
+0200
+++ deap-1.0.2.post2/debian/patches/series  2019-03-04 17:10:51.0 
+0100
@@ -1,2 +1,3 @@
 0001-fix-docs.patch
 0002-fix-tests.patch
+0003-remove-pngmath.patch
diff -Nru deap-1.0.2.post2/debian/tests/python3-deap 
deap-1.0.2.post2/debian/tests/python3-deap
--- deap-1.0.2.post2/debian/tests/python3-deap  2017-07-15 20:38:22.0 
+0200
+++ deap-1.0.2.post2/debian/tests/python3-deap  2019-03-04 17:10:51.0 
+0100
@@ -1,6 +1,6 @@
 #!/bin/sh
 set -e -u
 export PYTHONWARNINGS=d
-cp -a deap/tests/ "$ADTTMP"
-cd "$ADTTMP/tests/"
+cp -a deap/tests/ "$AUTOPKGTEST_TMP"
+cd "$AUTOPKGTEST_TMP/tests/"
 py3versions -i | tr ' ' '\n' | xargs -I {} env {} -m unittest discover -v 2>&1
diff -Nru deap-1.0.2.post2/debian/tests/python-deap 
deap-1.0.2.post2/debian/tests/python-deap
--- deap-1.0.2.post2/debian/tests/python-deap   2017-07-15 20:38:22.0 
+0200
+++ deap-1.0.2.post2/debian/tests/python-deap   2019-03-04 17:10:51.0 
+0100
@@ -1,6 +1,6 @@
 #!/bin/sh
 set -e -u
 export PYTHONWARNINGS=d
-cp -a deap/tests/ "$ADTTMP"
-cd "$ADTTMP/tests/"
+cp -a deap/tests/ "$AUTOPKGTEST_TMP"
+cd "$AUTOPKGTEST_TMP/tests/"
 pyversions -i | tr ' ' '\n' | xargs -I {} env {} -m unittest discover -v 2>&1
diff -Nru deap-1.0.2.post2/debian/watch deap-1.0.2.post2/debian/watch
--- deap-1.0.2.post2/debian/watch

Re: Problems with shim and shim-signed in unstable, and proposed solutions to unblock us

2019-03-04 Thread Steve McIntyre 
I've had a reply from Mark (ftpteam) in IRC:

On Sun, Mar 03, 2019 at 11:35:45PM +, Steve McIntyre wrote:

...

>So, we're looking at three hacky options options here to work our way
>out of this hole. In (probably?) descending order of hackitude:
>
>1. Ask the nice ftpmaster people to bodge the archive by hand:
>1a. Remove the current shim source and binary packages from
>unstable (version 15+1533136590.3beb971-2)
>1b. Copy the older source and binary from buster back into
>unstable for us.
>1c. We're not even sure if this is *possible*, let alone a nice
>thing to do - thoughts?
>1d. Expecting that this might break all kinds of tools inside and
>outside of the archive maybe?

And Mark says:

"we don't want to go rewinding version numbers in unstable; that could
lead to all sorts of unforeseeable breakage.

much as we'd expected. Any more feedback please? Cyril prefers
approach #2 below, I prefer #3.

>OR
>
>2. Upload new bodged versions of shim and shim-signed to get us
>   back to working with the previously-signed shimx64.efi.signed
>   binary
>2a. Create new shim and shim-signed source packages, along with
>matching binary packages.
>2b. These binary packages will contain the *exact* same EFI
>binaries as we have in buster but with a higher version number
>in the packaging.
>2c. As we cannot *exactly* reproduce the binaries sensibly, we
>will have to hand-hack the contents of the binary packages.
>2d. We *know* this is grotty too, but we can at least make this
>work entirely at a package level.
>2e. Already tested and working: Cyril has built packages like this
>and I have tested the results successfully on my test SB
>system here.
>
>Current versions in buster:
> - shim:
>- source: 0.9+1474479173.6c180c6-1
>- binary: 0.9+1474479173.6c180c6-1
> - shim-signed:
>- source: 1.28+nmu1
>- binary: 1.28+nmu1+0.9+1474479173.6c180c6-1
>
>Possible versions targetting sid:
> - shim:
> - source: 16+1474479173.6c180c6-1 (bumped “epoch-like” N+
>   prefix, but same contents as 0.9+1474479173.6c180c6-1)
> - binary: 16+1474479173.6c180c6-1
> - shim-signed:
> - source: 1.28+nmu2 (new upload to adjust the Depends)
> - binary: 1.28+nmu2+16+1474479173.6c180c6-1
>
>OR
>
>3. Upload new version of the shim-signed source package and a
>   (lightly) bodged binary package
>3a. Use versions:
> - source: 1.28+nmu2
> - binary: 1.28+nmu2+0.9+1474479173.6c180c6-1
>3b. Needs as build-deps an old version of sbsigntool (0.6-3.2) and
>specifically version 0.9+1474479173.6c180c6-1 of shim in the
>build chroot
>3c. Then upload source+amd64
>3d. New shim-signed binary package changes in a few ways:
>* new version of the binary now include fbx64.efi.signed and
>  mmx64.efi.signed (copied across from the shim binary package)
>* add Replaces: shim (= 0.9+1474479173.6c180c6-1) so we don't
>  conflict on those binaries
>* remove Depends: shim (the whole point!)
>* change Build-Depends to list the specific versions used for
>  shim and sbsigntool
>3e. Already tested and working. I built this (source and binary
>debdiffs attached) and tested OK on SB system
>3f. This package is instantly RC-buggy due to the unavailable
>build-deps. We know...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Is there anybody out there?


signature.asc
Description: PGP signature

Bug#922826: Poke regarding unblock

2019-03-04 Thread Jonathan Carter 
Dear release team

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

calamares, calamares-settings-debian and live-wrapper are now all over
10 days old (originally remove because of calamares buggy dep on
pythonqt that has since been resolved.

Please unblock so that we can get live builds working again.

Thanks,

-Jonathan

-- 
  ⢀⣴⠾⠻⢶⣦⠀  Jonathan Carter (highvoltage) 
  ⣾⠁⢠⠒⠀⣿⡁  Debian Developer - https://wiki.debian.org/highvoltage
  ⢿⡄⠘⠷⠚⠋   https://debian.org | https://jonathancarter.org
  ⠈⠳⣄  Be Bold. Be brave. Debian has got your back.