Bug#276419: [Pkg-shadow-devel] Bug#276419: Do we fix this in 4.0.14-4?

[Christian Perrier]

  -publish an announcement in d-d
  -include a technical document in /usr/share/doc/passwd
 
 I think it is still too early to call it a survey.
 I need more time to check:
  * the Debian native packages
  * the packages that uses cron
  * the packages that install an init.d
  * the maintainer scripts
(based on the selction of Bill Allombert)
 
 I've started the 3 first points.

OK. need more time noticed. So, this will obviously not be for this
release.

  If the patch that adds this is ready then we can go for it. If it
  isn't and you feel it's needed, then convince me..:)
 
 I'm not sure, but the patch that adds this is probably just the removal
 of a debian patch.

Yes. But if we need a variable to revert the behaviour to the old
behaviour then it needs to be implemented somewhere, no?



Anyway, bug solution delayedmaybe some day, this bug will be the
last one...:)




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

Bug#276419: Do we fix this in 4.0.14-4?

[Christian Perrier]

The upload of 4.0.14-4 will happen soon.

We have the opportunity of fixing this bug now. From Nicolas survey,
it does not seem likely to harm critical things (inclusing sarge to
etch upgrades, see thread back in November), so the only actions
(besides stopping to apply the 423 patch) are communication:

-publish an announcement in d-d
-include a technical document in /usr/share/doc/passwd

There was a proposal for POSIXLY_CORRECT variableI'm not deeply
convinced to add this complexity unless it proves really useful
(backword compatibility...but with what?).

If the patch that adds this is ready then we can go for it. If it
isn't and you feel it's needed, then convince me..:)




-- 






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