[Pkg-shadow-devel] 0xx patches sorting

[Christian Perrier]

> What is remaining:
>   * 006_libmisc.dpatch
>     + chowntty.c
>       I'm not sure we should keep this one. It was introduced in the fi=
rst
>       debian 4.0.3 and was not present in the previous 200xxxxx-xx vers=
ion
>       I still don't see the rationale.
>     + failure.{c,h}
>       I still don't see the rationale. I will check google.
>       such patch was already applied upstream (on other files), so mayb=
e
>       it should be kept.

If it is already applied upstream, then just put it as 3xx and do not
dig harder....We keep it in the transition phase and it will be there
when we resync with upstream.

>   * 008_src.dpatch
>     + login.c
>     + su.c
>       these patches are quite long. It will be difficult to split them,
>       seek the rationale in the changelog, and check if applied upstrea=
m
>       (which has a lot of changes since 4.0.3)

Yep. If you think they may be hard to dig in, you can take another
way:

-open a 5xx series where we will put patches we consider dropping when
syncing with upstream but indeed are unsure whether they have to be
kept or not. We will NOT use the 5xx patches when releasing the first
versions of 4.0.9 (or .10...) in Debian but we will have them ready in
case they're needed.


> Looks nice. I will be there.
> We will see if it's too short/ambitious ;)
>=20
> PS: you did not commit the patches for the last sarge and sid packages.


Hmmm, you mean SVN is not synced with the released packages=A0?

Damn, I was sure I did it...

I'll try to find some time for doing it.

For sarge, that may be right. But sid, are you sure?