[Pkg-shadow-devel] How to process with bug reports

[Nicolas François]

Hi,

I'm having a look at some bug reports.

#263805:
 * I could reproduce it with shadow 4.0.3-29, but not with the current
   version nor 4.0.3-29.1

   Can I close it with a mail to 263805-done, or should it be logged in
   the debian changelog?


Some bugs (e.g. #249611) can be fixed safely.
(I'm putting in this category bugs dealing with program strings and
documentation)
Do we plan to fix them for Sarge?
Do I commit fixes in the sarge branch?
Do I commit fixes in the sid branch?


Note: Tomasz, you may want to apply the patch proposed in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=249611
to in your CVS.



There's a lot of reports complaining about {user,group}{add,mod,del}.
I personally consider these commands as low level, and prefer commands
from the adduser package for higher level operations (creating a user and
her home directory, ...).
Would it be an option to fix these bugs by documenting the behavior of the
commands.

Tomasz may want to have these bugs fixed in his source, however, some are
really Debian specific, and could be deal with in a Debian specific way.
For example, for #121262, we could indicate that all files from /etc/skel
are copied, even *.dpkg-old files, and point user to adduser, which do not
copy *.dpkg-old files.


Just to inform you (this is not a reservation nor a warranty), I will try
to deal with gshadow/gpasswd/newgrp/sg related bugs.


-- 
Nekral