On Sat, Mar 18, 2017 at 20:16:53 +0100, Michael Biebl wrote:
> Asking the release team for their input.
>
Care to summarize the issue? I didn't understand from your mail...
Cheers,
Julien
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintaine
Processing control commands:
> reassgin -1 molly-guard
Unknown command or malformed arguments to command.
> found -1 0.6.4
Bug #856024 [systemd-sysv] molly-guard: causes failure to update systemd-sysv
There is no source info for the package 'systemd-sysv' at version '0.6.4' with
architecture ''
Control: reassgin -1 molly-guard
Control: found -1 0.6.4
Am 18.03.2017 um 19:11 schrieb Francois Marier:
> Control: reassign -1 systemd-sysv
>
>> This looks like a genuine bug in molly-guard,
>
> Yes and that's tracked in bug #837928.
>
> The present bug is specifically about the interaction be
Am 18.03.2017 um 19:11 schrieb Francois Marier:
> Control: reassign -1 systemd-sysv
>
>> This looks like a genuine bug in molly-guard,
>
> Yes and that's tracked in bug #837928.
And why is that bug not treated as RC then?
> The present bug is specifically about the interaction between
> molly-g
Control: reassign -1 systemd-sysv
This looks like a genuine bug in molly-guard,
Yes and that's tracked in bug #837928.
The present bug is specifically about the interaction between
molly-guard and systemd-sysv.
so this RC bug should be assigned to molly-guard.
Adding a Breaks to systemd-
Processing control commands:
> reassign -1 systemd-sysv
Bug #856024 [molly-guard] molly-guard: causes failure to update systemd-sysv
Bug reassigned from package 'molly-guard' to 'systemd-sysv'.
No longer marked as found in versions molly-guard/0.6.4.
Ignoring request to alter fixed versions of bug
Processing control commands:
> reassign -1 molly-guard
Bug #856024 [systemd-sysv] molly-guard: causes failure to update systemd-sysv
Bug reassigned from package 'systemd-sysv' to 'molly-guard'.
Ignoring request to alter found versions of bug #856024 to the same values
previously set
Ignoring requ
