[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#925489: marked as done (unblock: elogind/241.1-1+debian1)

Your message dated Mon, 8 Apr 2019 16:52:48 +0200
with message-id <20190408145245.dphltjjlkmax6ttd@debian.org>
and subject line Re: unblock: elogind/241.1-1+debian1
has caused the Debian Bug report #925489,
regarding unblock: elogind/241.1-1+debian1
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 owner@bugs.debian.org
immediately.)


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

Please unblock package elogind.

Version 241.1-1+debian1 of src:elogind has been in unstable for 11 days with no
regressions reported.

I am aware that the debdiff against testing (239.3+20190131-1+debian1) is
significantly larger than you would normally want at this stage in the release
cycle. However, I believe it is warranted and ask for your consideration.

The benefits of migration centre around this version of elogind providing ABI
compatibility between libelogind0 and libsystemd0 (see #923244). This means that
packages compiled against libsystemd-dev headers work correctly with either
libsystemd0 or libelogind0 runtime libraries. This is particularly important for
policykit-1 authorization of many desktop functions (particularly restart, halt,
suspend and for pkexec which is essential for synaptic) on non-systemd init
installations.

It is also worth pointing out that as elogind is derived from systemd which is
alrelady at version 241-2 in testing. Therefore, much of the contained upstream
code is already in included in buster.

In addition, at the moment this is rather a niche area into which few 'regular'
users will dip their toes; systemd is not currently uninstallable by APT once it
is PID 1 and so elogind systems can only be installed from scratch and do not
happen without considerable knowledge and care.

Many thanks. I look forward to your thoughts.

Mark

-- System Information:
Debian Release: 8.11
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-7-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

--- End Message ---
--- Begin Message --- 
Hi,

On Mon, Mar 25, 2019 at 07:47:00PM +0000, Mark Hindley wrote:
> Please unblock package elogind.
> 
> Version 241.1-1+debian1 of src:elogind has been in unstable for 11 days with no
> regressions reported.
> 
> I am aware that the debdiff against testing (239.3+20190131-1+debian1) is
> significantly larger than you would normally want at this stage in the release
> cycle. However, I believe it is warranted and ask for your consideration.
> 
> The benefits of migration centre around this version of elogind providing ABI
> compatibility between libelogind0 and libsystemd0 (see #923244). This means that
> packages compiled against libsystemd-dev headers work correctly with either
> libsystemd0 or libelogind0 runtime libraries. This is particularly important for
> policykit-1 authorization of many desktop functions (particularly restart, halt,
> suspend and for pkexec which is essential for synaptic) on non-systemd init
> installations.
> 
> It is also worth pointing out that as elogind is derived from systemd which is
> alrelady at version 241-2 in testing. Therefore, much of the contained upstream
> code is already in included in buster.
> 
> In addition, at the moment this is rather a niche area into which few 'regular'
> users will dip their toes; systemd is not currently uninstallable by APT once it
> is PID 1 and so elogind systems can only be installed from scratch and do not
> happen without considerable knowledge and care.
> 
> Many thanks. I look forward to your thoughts.

This change is way to big to be unblocked.

Thanks,

Ivo

--- End Message ---
Reply to: