[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#424879: marked as done (developers-reference: Document best practise for update-alternatives)

Your message dated Sat, 10 Sep 2022 13:31:51 +0100
with message-id <aa35e778dc9ad3fe9614fda423248e3f8506e21d.camel@adam-barratt.org.uk>
and subject line Closing requests for updates included in 11.5
has caused the Debian Bug report #101870,
regarding developers-reference: Document best practise for update-alternatives
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
101870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=101870
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: developers-reference
Version: 3.8.8

Hi,

It seems that the usage of update-alternatives in postinst/prerm 
is underdocumented.

Policy does mention update-alternatives but just points to the
update-alternatives manpage.  That itself just says that it's
"usually called from the postinst or prerm scripts".

I think it would be good that there was better documentation for it on
how to use it in the maintainer scripts.  During which part of the
script it should do what, and things like that.

I'm not sure what the best place to document this is, but the
developers-reference seems to be a good place to me.


Kurt

--- End Message ---
--- Begin Message --- 
Package: release.debian.org
Version: 11.5

Hi,

Each of the updates referenced by these bugs was included in today's
11.5 point release.

Regards,

Adam

--- End Message ---
Reply to: