Yet anouther workaround: instead of patching (Thanks, Ingo!) mountall and all the other packages depending on "plymouth" now, one could install plymouth-pseudo package. This way the dependency would be satisfied but one can still receive updates on the other Ubuntu packages:
$ apt-get install equivs $ equivs-control plymouth-dummy $ vi plymouth-dummy [...] $ grep -v ^\# plymouth-dummy Section: misc Priority: optional Standards-Version: 3.6.2 Package: plymouth-dummy Provides: plymouth Version: 1.0 Description: plymouth-dummy, see LP# 556372 $ equivs-build plymouth-dummy $ ls -lgo plymouth-dummy* -rw-r----- 1 826 2010-04-08 16:45 plymouth-dummy -rw-r--r-- 1 2040 2010-04-08 16:47 plymouth-dummy_1.0_all.deb $ dpkg -i plymouth-dummy_1.0_all.deb Maybe the "Version:" tag has to be altered at some point later (when e.g. mountall depends on plymouth-2.0 or something). I did this here and it's running fine so far. Of course, if at some point they add some magical functional dependency to plymouth, one would be forced to install the real "plymouth" eventually. -- Please remove the plymouth dependency from mountall / cryptsetup https://bugs.launchpad.net/bugs/556372 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
