Hi,

I recently upgraded and encountered the same problem.

Here is my analysis :

plymouth has been splitted in plymouth and plymouth-drm.
script.so, the script engine for themes that was in the "plymouth" package is 
now in plymouth-drm.

Now, suppose you've got a plymouth theme requiring script.so installed on your 
system. This theme is configured by default in /etc/plymouth/plymouthd.conf.
When you'll upgrade plymouth packages (to testing's version), the first package 
to be upgraded by apt/aptitude will likely be plymouth, before plymouth-drm is
installed. And plymouth launches update-initramfs (both from postinst and with a
trigger !).
update-initramfs will run plymouth's hook, which will it turn
  1/ discover which theme is used on the system (plymouthd.conf)
  2/ find what dependencies does this theme have
  3/ include those dependencies in the initramfs.
As you've guessed by now, one of those dependencies is script.so; and it has 
been removed from plymouth package; and plymouth-drm is not installed yet ; and 
neither is the new version of the theme which now depends on plymouth-drm.
Therefore update-initramfs will fail with a message like this one (in french,
sorry):

E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-2.6.32-5-686
dpkg : erreur de traitement de initramfs-tools (--unpack) :
 le sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
configured to not write apport reports
                                      Des erreurs ont été rencontrées pendant 
l'exécution :
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)


Of course /etc/plymouth/plymouthd.conf is a conffile, and user could chose to 
use plymouth's version which uses theme not depending on script.so; but
conffiles are processed after postinst and triggers so it never reaches this
point.


Now, I'm not sure yet about what's the best solution to this problem:
 - erase user's conffile plymouthd.conf in postinst before update-initramfs. 
But 
   I'm not sure this is the Debian way.
 - fix plymouth's initramfs hook so it doesn't fail if theme has missing files, 
   and fallbacks on plymouth's default provided theme (text)
 - make sure plymouth-drm is installed before plymouth is upgraded
 - put plymouth-drm back into plymouth
 - what Osamu proposed
 - something else.


Regards,

Anisse



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to