Simon Josefsson <[EMAIL PROTECTED]> writes:
> The second problem seems to be generic. The reason I looked at
> packages in testing was that they are the packages that are going to
> be released, and if I look at what's in unstable, it seems that I
> might miss what's going to be in etch (e.g., e2fsprogs seems to be
> frozen, and the version in unstable now doesn't seem to be going into
> etch).
>
> Should I look at packages in unstable, and only if the package is
> frozen, look at the one in testing, instead?
You should check the packages in testing. Then check the packages in
unstable.
Note what packages fixed the problem in unstable, file an RC bug for
the testing version and close it for the unstable version. That then
reflects the reality and will keep track of the problem.
Note what packages started to be buggy in sid. Hopefully none.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
