Re: Packages with 5+ years of pending changes
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Mario,
On 24/02/14 16:45, Mario Lang wrote:
> Hi.
>
> 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.
> 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. Some of the dates I saw were very old though, 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.
>
> I am not familiar enough with practices in pkg-perl currently to
> really be of help right now, except for generating this list. It
> is probably a good starting point for anyone interested in QA. 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.
>
> Here is the list, sorted by date. The actual list of packages
> with UNRELEASED changes is much longer, I trimmed this one to avoid
> flooding you. If you are interested in the full list, get it from
> git.debian.org:~mlang/pp/output.sorted
>
>
{SNIP LONG LIST}
>
>
>
> _______________________________________________
> pkg-perl-maintainers mailing list
> pkg-perl-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-perl-maintainers
>
>
I can't guarantee to provide you lots of answers as I'm still very new
to the pkg-perl team myself! I have CC'd the debian-perl mailing list
as that may be a better place to handle any ongoing discussion.
- From what I know most of the details about how the team functions etc
are in [1].
I'm particularly interested in the URL check failures you mentioned as
I began looking at the list of watch problems on pkg-perl PET [2]...
but seems there are a number of anomalies there!
I shall try and have look at some of the errors from DUCK to see if I
can fix any of them!
Cheers,
Daniel
[1] http://pkg-perl.alioth.debian.org/policy.html
[2] http://pet.debian.net/pkg-perl/pet.cgi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQEcBAEBAgAGBQJTC65ZAAoJEMw/9yOWzAkJMi4IAKnO/7wEEq3+8lXL/Zm/SGH3
ny17Yai40XlDmE+cGpMz4l9Az+3UFcX5THtee3Lg1dySM4zOPPcmyVIe0cakuA4P
KXlqdmP49y4IKeTp8JBdsbPEo0VdLVbmk5PaM39mG12xhLdpr1cZEgVgRopylj8U
D8op2bL4jbhidjLqf6HVKpfGF/n564C2S4w9IzhZXdhsSlaCoERpOzJymLTN1XSV
K8IkIKlbFB3PNnjtn3ML7oACXxFVoA+IFXW1uKmYR9Rsl3XAo2Mq1tGsXaUh4cSQ
+Nq4LLQ7Yr6IiKCvq4ErYVFfCXtqj2LmjFounxvqQPBCD0nPAiMWOsfxP/gT1mM=
=hZiq
-----END PGP SIGNATURE-----
Reply to: