[Piuparts-devel] Bug#760716: Bug#760716: Problem with piuparts wanting to remove systemd-sysv

[Holger Levsen]

control: severity -1 important
# makes other packages look bad, eg gnome-shell-pomodoro :)

Hi Joseph,

thanks for your bug report!

On Sonntag, 7. September 2014, Joseph Herlant wrote:
> I am packaging gnome-shell-pomodoro-data and found out that piuparts
> fails testing it on piuparts.debian.org because at some point,
> /etc/piuparts/scripts/pre_remove_exceptions script wants to install
> sysvinit-core to remove systemd-sysv.

yes, it does this, as gnome-shell* pulls in systemd-sysv, but for comparing 
with the initial state we need to get sysvinit-core back, as this is/was the 
initial state.

Once "the initial state", aka the system installed with debootstrap, has 
changed to use systemd-sysv by default, we (the piuparts maintainers) will 
need to change this logic. Maybe this time has come now? 
 
> Then the purge fails because files of the systemd-sysv have disappeared,
> which is normal if piuparts removes the systemd-sysv package!

systemd-sysv should only be removed after purge of your package...

> As systemd-sysv is the default init system in Debian,
> I don't understand the behavior of piuparts here.

is it really the default by now? I mean, it has been decided to be, yes, but:

will debootstrap from sid already install systemd-sysv by default?
will debootstrap from wheezy do the same?
 
> Note that I don't have the issue when I run:
> `sudo piuparts ./gnome-shell-pomodoro-data_0.10.2-5_all.deb`
> on my pc, so it might be related to specific options used on
> piuparts.debian.org.

thats because the scripts are not run by default, also see #752256


cheers,
	Holger
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/piuparts-devel/attachments/20140907/d9fa7d1d/attachment.sig>