Re,

On 11/15/2014 03:49 PM, Andreas Beckmann wrote:
On 2014-11-14 19:48, Thomas Liske wrote:
On 11/14/2014 01:07 PM, Andreas Beckmann wrote:
during a test with piuparts I noticed your package prompts the user
badly.  Prompting in maintainer scripts must be done by communicating
through a program such as debconf which conforms to the Debian
Configuration Management Specification, version 2 or higher.

the Debian Policy does not apply - the observed bug is within the
upstream perl core.

The Policy applies to upstream bugs too, as long as they are found in Debian. 
:-)

You are quoting a section applying to debian maintainer scripts - the maintainer script in needrestart does not use debconf nor is it buggy at all. needrestart is launched by apt outside of dpkg - it's "just" apt which hangs due to the buggy DPkg::Post-Invoke command.

So the package can be installed/upgraded/removed without problems... it's just the dpkg frontend which hangs due to the bug ;-P


But that's just academic - the bug is silly and needs to be fixed for jessie without any doubt.


I think this is triggered by a division by zero in the same code path as
in #767370. This could be triggered if no kernel images were found or no

I could verify that the bug disappears if I use
   --extra-old-packages linux-image-amd64
so merging the two reports.

Thanks for confirming & merging!


process being a restart candidates. Both conditions occure rarely in the
wild. Therefore the severity of this issue should be not higher than
normal.

No kernel installed is not uncommon in virtualized environments - this
is where the bug was found initially.
I would agree on a lower severity if piuparts was the only way to
trigger the bug.

Paravirtualized using libvirt AFAIK - there are many other virtualization environments requiring a kernel image inside the container. But the bug should keep a severity of serious[1] if it violates the debian policy.

[1] https://www.debian.org/Bugs/Developer#severities


The current upload you want to get into jessie was only uploaded with
priority=low. If the upstream fix for this bug here gets backported
and uploaded with priority=medium it would be eligible for migration
at the same time. I think you should do that, especially since I do
not see an unblock request for the current version in sid.

The patch for #767370 and #769544 has not been uploaded by Patrick, yet.


HTH,
Thomas

--

    ::  WWW:                         http://fiasko-nw.net/~thomas/  ::
   :::  Jabber:                   xmpp:tho...@jabber.fiasko-nw.net  :::
    ::  flickr:              http://www.flickr.com/photos/laugufe/  ::


--
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