Bug#933125: buster-pu: package systemd/241-5+deb10u1

2019-08-20 Thread Adam D. Barratt
Hi,

Apologies for missing your mail originally.

On Sun, 2019-08-18 at 19:36 +0200, Michael Biebl wrote:
> Hi Adam
> 
> Am 16.08.19 um 22:08 schrieb Adam D. Barratt:
> > Control: tags -1 + confirmed
> > 
> > On Fri, 2019-07-26 at 21:43 +0200, Michael Biebl wrote:
[...]
> > > 241-5+deb10u1 is identical to 241-7 which has been uploaded to
> > > unstable/bullseye and we haven't received any regression reports
> > > so
> > > far.
> > 
> > In that case, feel free to make it -7~deb10u1, with the appropriate
> > changelog wrangling, if that would be preferable.
> 
> I considered adding a changelog entry like this as it seemed the most
> obvious correct one:
> 
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,3 +1,9 @@
> +systemd (241-7~deb10u1) buster; urgency=medium
> +
> +  * Rebuild for buster
> +
> + -- Michael Biebl   Sat, 17 Aug 2019 11:00:59
> +0200
> +
>  systemd (241-7) unstable; urgency=medium
> 
>[ Michael Biebl ]
[...]
> But this then triggers warnings from dpkg-genchanges:
> 
> dpkg-genchanges: warning: the current version (241-7~deb10u1) is
> earlier than the previous one (241-7)
> 
> and lintian:
> W: systemd: latest-debian-changelog-entry-without-new-version
[...]
> Adam, so I wonder, what's the proper changelog wrangling in this
> case?

I would say this and ignore the warnings. It looks like you already did
that. :-)

Regards,

Adam



Bug#933125: buster-pu: package systemd/241-5+deb10u1

2019-08-18 Thread Michael Biebl
Hi Adam

Am 16.08.19 um 22:08 schrieb Adam D. Barratt:
> Control: tags -1 + confirmed
> 
> On Fri, 2019-07-26 at 21:43 +0200, Michael Biebl wrote:
>> I'd like to make a stable upload for systemd, fixing the following
>> issues:
> [...]
>> 241-5+deb10u1 is identical to 241-7 which has been uploaded to
>> unstable/bullseye and we haven't received any regression reports so
>> far.
> 
> In that case, feel free to make it -7~deb10u1, with the appropriate
> changelog wrangling, if that would be preferable.


I considered adding a changelog entry like this as it seemed the most
obvious correct one:

--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+systemd (241-7~deb10u1) buster; urgency=medium
+
+  * Rebuild for buster
+
+ -- Michael Biebl   Sat, 17 Aug 2019 11:00:59 +0200
+
 systemd (241-7) unstable; urgency=medium

   [ Michael Biebl ]



But this then triggers warnings from dpkg-genchanges:

dpkg-genchanges: warning: the current version (241-7~deb10u1) is earlier
than the previous one (241-7)

and lintian:
W: systemd: latest-debian-changelog-entry-without-new-version



To avoid that, I could rewrite the old changelog entry for 241-7 like this

--- a/debian/changelog
+++ b/debian/changelog
@@ -1,4 +1,4 @@
-systemd (241-7) unstable; urgency=medium
+systemd (241-7~deb10u1) buster; urgency=medium

   [ Michael Biebl ]
   * network: Fix failure to bring up interface with Linux kernel 5.2.



Rewriting the old changelog entry for 241-7 feels wrong though.

Adam, so I wonder, what's the proper changelog wrangling in this case?


Regards,
Michael

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



signature.asc
Description: OpenPGP digital signature


Bug#933125: buster-pu: package systemd/241-5+deb10u1

2019-08-16 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Fri, 2019-07-26 at 21:43 +0200, Michael Biebl wrote:
> I'd like to make a stable upload for systemd, fixing the following
> issues:
[...]
> 241-5+deb10u1 is identical to 241-7 which has been uploaded to
> unstable/bullseye and we haven't received any regression reports so
> far.

In that case, feel free to make it -7~deb10u1, with the appropriate
changelog wrangling, if that would be preferable.

Regards,

Adam



Bug#933125: buster-pu: package systemd/241-5+deb10u1

2019-07-27 Thread Cyril Brulebois
Hi,

Michael Biebl  (2019-07-26):
> 241-5+deb10u1 is identical to 241-7 which has been uploaded to
> unstable/bullseye and we haven't received any regression reports so
> far.
> 
> None of those changes should touch udev-udeb, i.e. d-i.
> That said, I've added kibi/debian-boot to CC for his ack.

No objections, thanks.


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


signature.asc
Description: PGP signature


Bug#933125: buster-pu: package systemd/241-5+deb10u1

2019-07-26 Thread Michael Biebl
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

Hi,

I'd like to make a stable upload for systemd, fixing the following
issues:

systemd (241-5+deb10u1) buster; urgency=medium

  * ask-password: Prevent buffer overflow when reading from keyring.
Fixes a possible memory corruption that causes systemd-cryptsetup to
crash either when a single large password is used or when multiple
passwords have already been pushed to the keyring. (Closes: #929726)

https://salsa.debian.org/systemd-team/systemd/commit/3baec22e1fcd89a3b6d93d9a3e59bf7fa7114714

  * Clarify documentation regarding %h/%u/%U specifiers.
Make it clear, that setting "User=" has no effect on those specifiers.
Also ensure that "%h" is actually resolved to "/root" for the system
manager instance as documented in the systemd.unit man page.
(Closes: #927911)

https://salsa.debian.org/systemd-team/systemd/commit/fef3138711bd858d1718b458d257fa73317d532d

  * network: Behave more gracefully when IPv6 has been disabled.
Ignore any configured IPv6 settings when IPv6 has been disabled in the
kernel via sysctl. Instead of failing completely, continue and log a
warning instead. (Closes: #929469)

https://salsa.debian.org/systemd-team/systemd/commit/2f37176282a3f02d8839158441ba70fe3975d2b0

  * network: Fix failure to bring up interface with Linux kernel 5.2.
Backport two patches from systemd master in order to fix a bug with 5.2
kernels where the network interface fails to come up with the following
error: "enp3s0: Could not bring up interface: Invalid argument"
(Closes: #931636)

https://salsa.debian.org/systemd-team/systemd/commit/cce6b9e2c23c315659147cb28ad1a8947995a997

  * Use /usr/sbin/nologin as nologin shell.
In Debian the nologin shell is installed in /usr/sbin, not /sbin.
(Closes: #931850)

https://salsa.debian.org/systemd-team/systemd/commit/b0c697c519b731094d4ad11ae59afd76c1901aae

  [ Mert Dirik ]
  * 40-systemd: Don't fail if SysV init script uses set -u and $1 is unset
(Closes: #931719)

https://salsa.debian.org/systemd-team/systemd/commit/3f1c8e9d4c9bc5f49a13b2415f8f8845423f347f

241-5+deb10u1 is identical to 241-7 which has been uploaded to
unstable/bullseye and we haven't received any regression reports so far.

None of those changes should touch udev-udeb, i.e. d-i.
That said, I've added kibi/debian-boot to CC for his ack.

Regards,
Michael


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 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
diff --git a/debian/changelog b/debian/changelog
index ed55c95..a421cb9 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,33 @@
+systemd (241-5+deb10u1) buster; urgency=medium
+
+  * ask-password: Prevent buffer overflow when reading from keyring.
+Fixes a possible memory corruption that causes systemd-cryptsetup to
+crash either when a single large password is used or when multiple
+passwords have already been pushed to the keyring. (Closes: #929726)
+  * Clarify documentation regarding %h/%u/%U specifiers.
+Make it clear, that setting "User=" has no effect on those specifiers.
+Also ensure that "%h" is actually resolved to "/root" for the system
+manager instance as documented in the systemd.unit man page.
+(Closes: #927911)
+  * network: Behave more gracefully when IPv6 has been disabled.
+Ignore any configured IPv6 settings when IPv6 has been disabled in the
+kernel via sysctl. Instead of failing completely, continue and log a
+warning instead. (Closes: #929469)
+  * network: Fix failure to bring up interface with Linux kernel 5.2.
+Backport two patches from systemd master in order to fix a bug with 5.2
+kernels where the network interface fails to come up with the following
+error: "enp3s0: Could not bring up interface: Invalid argument"
+(Closes: #931636)
+  * Use /usr/sbin/nologin as nologin shell.
+In Debian the nologin shell is installed in /usr/sbin, not /sbin.
+(Closes: #931850)
+
+  [ Mert Dirik ]
+  * 40-systemd: Don't fail if SysV init script uses set -u and $1 is unset
+(Closes: #931719)
+
+ -- Michael Biebl   Fri, 26 Jul 2019 21:32:04 +0200
+
 systemd (241-5) unstable; urgency=medium
 
   * Revert "Add check to switch VTs only between K_XLATE or K_UNICODE"
diff --git a/debian/extra/init-functions.d/40-systemd 
b/debian/extra/init-functions.d/40-systemd
index 4fa9b9c..e944acb 100644
--- a/debian/extra/init-functions.d/40-systemd
+++ b/debian/extra/init-functions.d/40-systemd
@@ -8,12 +8,12 @@ if [ -d /run/systemd/system ]; then