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

Bug#883573: marked as done (Reevaluate libpam-systemd systemd-sysv dependency ordering (746578))

Your message dated Fri, 16 Feb 2018 09:57:15 +0100
with message-id <2258543.kbQRyQoti9@odyx.org>
and subject line Re: Bug#883573: Call for vote on waiving libpam-systemd dependencies' ordering
has caused the Debian Bug report #883573,
regarding Reevaluate libpam-systemd systemd-sysv dependency ordering (746578)
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.)


-- 
883573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883573
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: tech-ctte
Severity: normal
Control: block 883569 by -1

Dear CTTE,

In 746578, the CTTE decided that the dependency be swapped
to systemd-shim | systemd-sysv in order to prevent systems
from being upgraded installing systemd.

This argument should be moot now. Either dependency is satisfied
on systems now, so an upgrade won't change anything.

More importantly, several packages now require just systemd-sysv. If
apt is told to install libpam-systemd and such a package in the same
operation (especially in a chroot I'd say, since that's where neither
shim nor sysv is installed), it may fail to resolve dependencies
because it picks systemd-shim first and fails to replace it with
systemd-sysv later. See #883555 for an example.

I thus opened bug 883569 against systemd, but mbiebl would like to
get permission from the you first.

> Package: libpam-systemd
> Version: 235-3
> Severity: important
>
> libpam-systemd depending on systemd-shim first causes severe trouble with
> resolving dependencies, as APT picks systemd-shim but then later sees a
> package which needs systemd-sysv and fails.
>
> I understand the order was necessary for preventing upgrades to stretch
> from migrating to systemd, but with the packages now widely installed,
> this should not be a problem anymore, as the dependencies are satisfied
> already, so APT won't switch them.

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer                              i speak de, en

--- End Message ---
--- Begin Message --- 
Le vendredi, 9 février 2018, 09.14:49 h CET Didier 'OdyX' Raboud a écrit :
> === Resolution ===
> 
> In 2014, it was resolved in #746578 that the libpam-systemd binary package
> alternative dependency on systemd-shim and systemd-sysv shall be set in that
> order, in order to avoid unwanted init system changes accross upgrades.
> Debian Stretch has since been released.
> 
> The Committee therefore resolves that:
> 
> 1. The Technical Commitee decision from 2014-11-15 in bug #746578 is
> repealed.
> 
> This means Debian's normal policies and practices take over and the
> libpam-systemd package's dependencies are set free from specific ordering
> constraints.  The migration should be managed according to Debian's usual
> backwards-compatibility arrangements.
> 
> === End Resolution ===

A week is gone and all 6 submitted votes are all in favour; the TC adopts the 
above resolution. Thank you for your patience.

I will send a short d-d-a email today.

Cheers,
    OdyX

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


--- End Message ---
Reply to: