Your message dated Sat, 29 Nov 2014 09:35:40 -0500
with message-id <6329991.9dq0ncmp26@kitterman-optiplex-9020m>
and subject line Re: Bug#766928 closed by Scott Kitterman
<deb...@kitterman.com> (Re: Bug#766928: Uninstallable as it depends on systemd)
has caused the Debian Bug report #766928,
regarding Uninstallable as it depends on systemd
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.)
--
766928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Package: k3b
Version: 2.0.2-8
Severity: important
Version 2.0.2-8 is uninstallable now as it pulls in the full systemd
that will never ever end on any of my systems.
Version 2.0.2-7.1 was fine.
- -- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (800, 'unstable'), (110, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.17.1 (SMP w/8 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to
de_DE)
Shell: /bin/sh linked to /bin/dash
- --
Klaus Ethgen http://www.ethgen.ch/
pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen <kl...@ethgen.de>
Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQGcBAEBCgAGBQJUTXugAAoJEKZ8CrGAGfasB4QL/1PhpG0Lp9f4I9KJqyl0RtPT
B1cSL8Fjk+MyQxL+yLxgQbt71UjhYeIctnuxdTcmW4PXeg5xSjA4JUefq/3/1UjO
uh8yXMIXNIpTHsPKf7uWK8vCjr/fqSBgnW9kNbwgU0CfWhBhnP7lPAxx2jzMWAxo
vuJ4MjHl3OCm9gFNFSpBQrxQRrIHrqWDB/BpA0w37Zcja3BR8jdAXAwh9nXLj/eR
FUlDa3lbOE+S6Ump+OYEK1EShkMa8LqrkXiTjREOGoCAEB5We798MZ9ycKfrHIv1
o1YixPGvw1xm9kGTmAoGmk4UxFBiFPd7fJvgMl5oFkzab/EAEIkhUFAJnxe4jj6B
c0oNCBHEaPTybnfJLRu0dGJ2Zmw9FQUnFvi8h6TBB1Wlvo3MbNCgiMU1PvsV1R6f
OXkiTddNQ7wlZUaEMyhbleXSVtVFce3uBLYEYY0IrIiGTKjNi2DhBJTxwLWAWcU+
V0mC4Z3MzEVWe+Hcxvs2pyUPdKgbwDRPKy1nYxYqXA==
=MdHh
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On Saturday, November 29, 2014 10:49:37 AM Klaus Ethgen wrote:
> > > Am Mo den 27. Okt 2014 um 18:03 schrieb Ralf Jung:
> > > > > Not really a k3b issue. k3b needs udisks2 for reliable operation,
> > > > > so
> >
> > adding
> >
> > > > > the missing dependency is correct for k3b. If there's an issue
> > > > > here,
> >
> > then
> >
> > > > > it's with udisk2's dependencies. Reassigning.
> > > >
> > > > It's also factually wrong, k3b can be installed without installing
> > > > systemd. I can run the following on my system:
> > > >
> > > > $ sudo aptitude -s install systemd-sysv- sysvinit-core systemd-shim
> > > > k3b
> > > >
> > > > which clearly shows that there's no hard dependency from k3b to
> > > > systemd-sysv.
> > >
> > > There is: k3b -> udisks2 -> libpam-systemd -> systemd
> > >
> > > Hard dependency to systemd for no reason.
> > >
> > > Please fix that issue. It is easy to fix as the dependency to udisks2 is
> > > not needed (maybe lowering it to recommended).
> >
> > Sigh. No. You aren't correct:
> >
> > Package: libpam-systemd
> > Depends: libc6 (>= 2.17), libcap2 (>= 1:2.10), libpam0g (>= 0.99.7.1),
> > systemd (= 215-7), libpam-runtime (>= 1.0.1-6), dbus, systemd-shim (>=
> > 8-2) | systemd- sysv
> >
> > Note the alternative depends on systemd-sysv. If you install systemd-sysv
> > then there's no systemd pulled in. Don't open the bug again. This has
> > already been investigated and there's no systemd dependency.
>
> You are not correct, sorry, I did not speak about the part at the end.
> Let me highlight the relevant part:
> Package: libpam-systemd
> Depends: libc6 (>= 2.17), libcap2 (>= 1:2.10), libpam0g (>= 0.99.7.1),
> systemd (= 215-7), libpam-runtime (>= 1.0.1-6), dbus, systemd-shim (>= 8-2)
> | systemd-sysv
> _______________________________________________________________________^^^^
> ^^^^^^^^^^^^^
>
> (sorry for the overlong line.)
>
> As you can see, the part at the end is totally useless as the package
> depends for a full blown systemd.
Yes. You end up with systemd installed and I did speak imprecisely. While
systemd is installed, if you install systemd-shim then systemd will not be the
running init system, you will still have sysv init.
I'm asking you again: Please don't reopen the bug. Playing bug status ping
pong with maintainers isn't something that's acceptable in Debian.
Scott K
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
_______________________________________________
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras
