Re: Packages with 5+ years of pending changes
Hi Mario,
I also Cc rather debian-perl@ldo than pkg-perl-maintainers@lado as the
latter is not thought for discussions.
Mario Lang wrote:
> A quick look at duck.debian.net revealed that a lot
> of the URL check failures (roughly 700) are due to packages
> From pkg-perl.
Yeah, that's a legacy of the switch from SVN to Git back in 2011
during DebConf11.
> While looking at a few samples, I found some packages which had
> already fixed Vcs-* fields in the git repo but were never uploaded,
> still UNRELEASED.
That should be _all_ affected packages as this was IIRC fixed by doing
a mass-commit over all packages shortly after the conversion from SVN
to Git.
> Some of the dates I saw were very old though,
Glad you didn't do that a few months ago, it would have looked worse.
;-)
(Background: I recently uploaded all packages of pkg-perl which
haven't been uploaded for more than 6 years, i.e. all which were last
uploaded before 2008. I stopped in 2008 because the packages last
uploaded in 2008 were too many for a one-man job. :-)
> so I thought I'd generate a list of pkg-perl repos which are
> UNRELEASED (possibly carrying pending fixes) with a rather old
> change date. It turns out that there are 107 packages that have a
> change date of 5+ years ago and are still UNRELEASED.
That's better when I last counted at the beginning of 2014. It were
IIRC about 115 or 120 last uploaded in 2008.
> I am not familiar enough with practices in pkg-perl currently to
> really be of help right now, except for generating this list.
We track those at http://pet.debian.net/pkg-perl/pet.cgi -- all with
"UNRELEASED" should be in the "work in progress" section if they don't
belong to other sections (RC bugs, newer upstream version, etc.)
Often those package with "UNRELEASED" have only changes which alone
don't validate an upload. But the changes are made so that they are
ready in case there is a more important reason to validate an upload.
Often these changes were made with mass-commits (via "mr commit")
which fix the same issue in many, sometimes over thousand packages in
the same way. pkg-perl has some scripts for that, see the
pkg-perl-tools package.
> It is probably a good starting point for anyone interested in QA.
Definitely, at least was that my though when I saw packages last
uploaded in 2006 a few months ago. ;-)
> If you have some documentation about how you usually want things
> done in pkg-perl, please point me at it, I am interested to tackle
> some of these myself once I know enough about how pkg-perl works.
Please have a look at those two pages, they should explain most of how
pkg-perl works, especially the git workflow:
http://pkg-perl.alioth.debian.org/git.html
http://pkg-perl.alioth.debian.org/policy.html
Regards, Axel
--
,''`. | Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
Reply to: