Package: plymouth
Version: 0.8.3-18+b1
Severity: critical
Justification: breaks the whole system
Hi, I finally upgraded my system to wheezy.
As usual, there was a small glich in a package which gave me a bit of
surprize.
Case:
I had plymouth installed with aptitude manually.
Upgrade from squeeze version 0.8.3-9.1 to wheezy version 0.8.3-18+b1
performed.
old version 0.8.3-9.1:
plymouth recommends plymouth-themes-all
plymouth-themes-all depends plymouth-themes-script
So I have these as autoinstall
new version 0.8.3-18+b1:
plymouth does not recommend plymouth-themes-all nor plymouth-themes-script
So autoinstalled plymouth-themes-script will be removed by aptitude
As described in bug#613040, plymouth without plymouth-themes-script will
break initramfs generation script causing unbootable system. I think
squeeze version fixed it. So the bug#613040 may be closed for squeeze.
But wheezy suffer it again. Thus, I files separately.
Proposed resolution idea #1:
Depends: plymouth-themes-script
But this depends on plymouth-drm which depends on plymouth
Cyclic dependency.... ooops. I am not good enough to suggest
solution.
Proposed resolution idea #2:
Make another package split with cleaner dependency
Something along:
plymoth depends on plymouth-themes-script
plymouth-themes-script depends plymouth-drm
plymouth-drm suggest plymouth (if this is sufficient)
(... I think you know what is needed better than I do.
you may need to merge/move package contents etc too.)
Regards,
Osamu
PS: Since I had my system set to a dual boot Debian system, system was
actually bootable even after this major brakage. I was also careful
enough not to turn off PC while it was broken. But that is not
something this package should demand.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.39-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
