* Marc Haber

> [this is probably serious, a policy violation]

  No.  Let me quote <http://www.debian.org/Bugs/Developer#severities>:

    [serious] is a severe violation of Debian policy (roughly, it
    violates a "must" or "required" directive), [...]

  Also, if that weren't enough, the function in question is only run if
 the package is upgraded from version 1.2.0-1 or earlier.  This makes
 the "bug" only appear when upgrading from an unreleased version of
 Munin - in other words:  It won't affect new installs of Sarge, nor
 Woody->Sarge upgrades.  Hence, it cannot be considered release
 critical.  In my opinion, anyway.

> Munin-node's postinst's function move_startup_links fiddles around
> with symlinks in /etc/rcx.d. This should be changed to use the
> abstraction layer to allow interoperation with file-rc and other
> runlevel control mechanisms.

  I'd like to, but as far as I know update-rc.d doesn't provide me with
 the functionality I require.  Munin-node's init setup was formerly set
 to "default", which caused #298793.  To fix that during upgrades, I
 need to:

  1) Verify that the user hasn't overridden the startup ordering, if so
     I don't touch it (user configuration is sacred).
  2) Remove the old symlinks.
  3) Add the new symlinks.

  I cannot see how I can accomplish 1) with the update-rc.d abstraction
 layer.  I can do 2) and 3), of course, but due to 1) I need to make
 assumptions on the data structures underneath the abstraction layer
 anyway, so it seems pointless to mix'n'match approaches.

  I'd value any suggestions you might have on how to deal with it,
 though.

  Regarding the Subject field, you mention invoke-rc.d.  I use
 dh_installinit, which opportunistically uses invoke-rc.d if it's
 available, or falls back on calling the /etc/init.d/-script directly if
 not.  Have you made a backport using an old version of Debhelper which
 didn't use invoke-rc.d?  The munin-node 1.2.3-1 in the archive do
 indeed use invoke-rc.d, so I'll assume that part of the report is
 invalid, unless you elaborate a bit what's supposed to be the problem.

Kind regards,
-- 
Tore Anderson



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to