FYI, today's daily build solves both of these issues: the shishid
package is renamed to shishi-kdc, and there is a libpam-shishi
package. They are lintian clean too.
One question: How to handle the package renaming? Should shishi-kdc
have these fields:
Provides: shishid
Conflicts: shishid
Replaces: shishid
This seems to be the only thing left for 0.0.26 and a new upload.
/Simon
Elrond <[EMAIL PROTECTED]> writes:
> Package: shishi
> Version: 0.0.25-1
> Severity: serious
>
> Hi,
>
> I file this bug mostly to stop shishi from migrating from
> unstable to testing, because:
>
> We (shishi debian team) consider/plan
> 1) Renaming shishid to shishi-kdc
> 2) Adding pam_shishi
>
> As (1) has a bigger impact, if shishi were in testing, we
> decided: If we want to do it, it should be done before any
> migration to testing.
>
> That said, (1) requires manual approval by the ftp masters.
> Which is somewhat annoying to them for only a rename.
>
> (2) on the other hand requires that too. So the idea is to
> combine both to annoy the ftp-masters only once.
>
>
> This bug also is here to give
> - us the time to decide on (1) and (2)
> - us the time to do (1) correctly
> - us the time to do (2)
> - debian users a very slight chance of knowing, that a
> rename might happen
>
>
> Elrond
_______________________________________________
Help-shishi mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/help-shishi
