[Pkg-shadow-devel] Re: [Adduser-devel] (forw) [Pkg-shadow-commits] r502 - branches/experimental/debian/patches

[Christian Perrier]

Back on this discussion we had a few weeks ago, Marc.

Quoting Marc Haber (mh+0523mail at zugschlus.de):
> On Thu, Sep 01, 2005 at 11:54:33AM +0200, Christian Perrier wrote:
> > > OK, I'll conflict with passwd versions which return 3 on shadow failure.
> > 
> > Which includes from 4.0.3-37 up to 4.0.11.1-1
> > 
> > unstable currently has 4.0.3-39 (held by a RC bug and thus will not go
> >                                  to testing)
> > testing has 4.0.3-35
> 
> So I'll upload a next adduser version conflicting with passwd >= 4.0.12.
> 
> > What will happen on shadow in the future:
> > 
> > -upload of 4.0.12-1 soon in experimental
> >  (fixes the RC bug)
> > 
> > -upstream will release 4.0.13
> > 
> > -upload of 4.0.13-1 in unstable near the end of September.
> >  (fixes the RC bug in unstable and hopefully enters testing 10 days later)
> 
> And as soon as 4.0.13 is in unstable, I'll upload a fixed adduser
> conflicting with passwd << 4.0.13.


While we're still investigating #328090, I anyway plan to upload a
4.0.12-2 version of the shadow package *to unstable* This is a long
awaited resync with upstream and actually a consequence of the huge
effort by the shadow team last months....

This is a slight change from the initial plan of uploading the first
resynced version as 4.0.13-1.

This is mainly because upstream is late in his schedule and I want to
have a resynced version in unstable as soon as possible.

>From the above plan, this means that the current adduser package
will conflict with 4.0.12-2....so you need to have a new adduser
package which conflicts with shadow versions <<4.0.12 and then upload
it immediately after I upload my new shadow...or upload it the very
same day.

(shadow 4.0.12-1 was uploaded to experimental and must anyway not
conflict with the future adduser as it already implements the new exit
codes)

As a reminder for you, this process is needed because chage exit codes
have been changed between shado 4.0.3 and shadow 4.0.12. New codes
are:

/*
 * Exit codes used by shadow programs
 */
#define E_SUCCESS       0       /* success */
#define E_NOPERM        1       /* permission denied */
#define E_USAGE         2       /* invalid command syntax */
#define E_BAD_ARG       3       /* invalid argument to option */
#define E_SHADOW_NOTFOUND 15    /* no shadow password file */

So, the "shadow file not found" exit code will be 15 .

As I don't want to take you by surprise, just let me know when you
think you'll be ready for this. No need for hurry.