Bug#520854: PTS: no longer lists the number of Ubuntu bugs

[Paul Wise]

Package: qa.debian.org
Severity: normal

The PTS no longer lists the number of Ubuntu bugs in the Ubuntu section
of the page. Here are a couple of examples (static copies attached):

http://packages.qa.debian.org/c/chromium.html
https://bugs.launchpad.net/ubuntu/+source/chromium

http://packages.qa.debian.org/f/fonttools.html
https://bugs.launchpad.net/ubuntu/+source/fonttools

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


chromium-debian-pts.html.gz
Description: GNU Zip compressed data


chromium-ubuntu-bugs.html.gz
Description: GNU Zip compressed data


fonttools-debian-pts.html.gz
Description: GNU Zip compressed data


fonttools-ubuntu-bugs.html.gz
Description: GNU Zip compressed data


signature.asc
Description: This is a digitally signed message part

Re: does /var/games have to be deleted on purge? (if it's empty..)

[Paul Wise]

On Tue, Apr 7, 2009 at 2:33 AM, Russ Allbery  wrote:

> I don't see much real benefit in going out of our way to remove /var/games
> and it looks like it would be a bit annoying (at the least, require adding
> purge code to all games that put files in /var/games that would usually
> never be triggered).  My inclination would be to say that this behavior is
> fine and perhaps we should officially bless it somewhere.

A single rmdir in every game using /var/games isn't that hard,
especially since they have to remove the files from there.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: does /var/games have to be deleted on purge? (if it's empty..)

[Paul Wise]

On Wed, Apr 8, 2009 at 7:51 PM, Holger Levsen  wrote:

> On Mittwoch, 8. April 2009, Bill Allombert wrote:
>> Unless policy is changed to make clear that /var/games can be removed
>> at any time, and thus that package cannot just ship /var/games in the
>> deb and expect it to be available when running the postinst, or at any
>> latter time, I have to object with this bug reports because this
>> introduces a race condition.
>
> I dont understand, can you please explain what race condition you mean?

How about this:

Game a gets installed and ships /var/games
Game b gets installed and ships /var/games
Game a gets purged and removes /var/games
User starts game b and gets a high score
Game b tries to save the high score but fails because /var/games doesn't exist

-- 
bye,
pabs

http://wiki.debian.org/PaulWise
http://synfig.org/User:PaulWise
http://bonedaddy.net/pabs3/


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: debian/watch sf redirector docs ?

[Paul Wise]

On Wed, May 13, 2009 at 9:02 AM, Raphael Geissert
 wrote:

> Sure, go ahead and see your watch files fail within a month, or whenever
> sourceforge makes yet another change on their website.
> It has already happened with the ftp mirror, the website, the
> downloads.sf.net pages, now the rest of the mirrors, and will happen again.
> The pourpose of the redirector is to provide the information without having
> to deal with sourceforge's mess.

Sourceforge seems to be improving a lot lately (for example: git VCS
option, support via IRC). I suggest that they might be open to
providing a permanent solution to this, like direct access to an
apache-generated index of files available for each project.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: debian/watch sf redirector docs ?

[Paul Wise]

On Wed, May 13, 2009 at 11:12 AM, Raphael Geissert
 wrote:

> "Improving" is very subjective, but I do plan to make another attempt.

I find the recent changes to be a vast improvement on the old web
interface and the old set of features.

> There was a ticket open which tried to reach an agreement, but I can no
> longer find it anywhere in alexandria.

They switched to trac for sf.net bug reports and docs:

http://p.sf.net/sourceforge/getsupport
https://apps.sourceforge.net/trac/sourceforge/

Your ticket was probably transferred into trac from the tracker, you
should have got a mail about closing the tracker ticket and another
about opening the trac one.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: script to query WNPP bugs using debtags

[Paul Wise]

On Tue, Jun 16, 2009 at 7:26 AM, Serafeim Zanikolas wrote:

> Perhaps someone could point out where from I can grab the code for
> wnpp.debian.net? (see below why)

See the first result here:

http://www.google.com/search?q=wnpp.debian.net+code

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: UDD news

[Paul Wise]

On Sat, Jun 20, 2009 at 11:27 PM, Andreas Tille wrote:

> I alsohave a question: I have read that carnivore tables are
> used for MIA status but I have no idea how.  I'm considering
> to add soem information about the maintainer to the blends bugs
> pages and this would be interesting.

That information is not public so it probably should not be added to UDD.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#506203: QA: 506203: proposed patch

[Paul Wise]

On Wed, 2008-11-19 at 20:05 +0900, Paul Wise wrote:

> I propose this patch to fix this issue:

That patch has bitrotten since the URLs changed over time and oldpeople
no longer runs PHP. I've attached a new patch.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise
Index: wml/developer.wml
===
--- wml/developer.wml	(revision 2213)
+++ wml/developer.wml	(working copy)
@@ -196,7 +196,6 @@
 $initial = strtoupper(substr($login, 0, 1));
 $maintainer_data .= "Reports: " .
 html_a("Buildd", "http://buildd.debian.org/pkg.cgi?maint=$ulogin";) . " - " .
-html_a("Igloo", "http://people.debian.org/~igloo/status.php?email=$ulogin";) . " - " .
 html_a("Lintian", "http://lintian.debian.org/reports/maintainer/$ulogin.html";) . " - " .
 // down since 2006-11 - html_a("Checklib", "http://rerun.lefant.net/checklib/maintainers.$initial.html#$ulogin";) . " - " .
 html_a("Debtags", "http://debtags.alioth.debian.org/todo.html?maint=$ulogin";) . " - " .
@@ -940,7 +939,7 @@
 } else {
 $buildd_display = html_td(
 html_a("Buildd", "http://buildd.debian.org/build.php?pkg=$urlpackage";) . html_br() .
-html_a("More", "http://people.debian.org/~igloo/status.php?packages=$urlpackage";)
+html_a("More", "http://buildd.debian.org/~luk/status/package.php?p=$urlpackage";)
 );
 }
 $line .= $buildd_display;


signature.asc
Description: This is a digitally signed message part

Re: Debconf QA BOF summary / handling of orphaned packages

[Paul Wise]

On Wed, Jul 29, 2009 at 12:53 PM, Lucas
Nussbaum wrote:

> Removal of orphaned packages
> 
> The audience clearly want orphaned packages to be removed. I'm not quite
> sure it's reasonable to do that. However, clearly, there's no opposition
> to this idea. When snapshots.debian.org will be fully fonctional, a web
> interface will allow users to fetch and install removed packages.

I forgot to mention it during the discussion, but s.d.o isn't an
optimal solution due to library ABI bumps and so on. I think a proper
solution is something like unsupported.debian.net or
debian-unsupported.org, documented here (but not yet worked on):

http://wiki.debian.org/MergeDerivedDistributions#DebianUnsupported

This is similar to the below idea:

> Move of orphaned packages to another place
> ==
> Another possible solution would be to move orphaned packages to another
> section/archive area (i.e something sitting next to unstable or
> experimental), or just to experimental.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Bug#541013: O: at -- Delayed job execution and batch processing

[Paul Wise]

On Tue, Aug 11, 2009 at 6:30 PM, Alexander Reichle-Schmehl
 wrote:

> Anyone interested in co maintaining that?  Upstream is non existent,
> there are quite some bugs in the bts and the package is priority
> standard.  Doesn't sound like a package someone should adopt all alone.

It is worth noting that at least Fedora and Gentoo use Debian's at
package for their upstream, so it might be a good idea to start an
alioth project and invite other distributions to collaborate there.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#545785: PTS: lintian link issues

[Paul Wise]

Package: qa.debian.org
Severity: normal
User: qa.debian@packages.debian.org
Usertags: pts

[Copies of all the html from the links below is in the attached tarball]

The libicns PTS page links to lintian.d.o even though there are no
lintian complaints for libicns:

http://packages.qa.debian.org/libi/libicns.html
http://lintian.debian.org/maintainer/mat...@eisbox.net.html#libicns
http://lintian.debian.org/full/mat...@eisbox.net.html#libicns

Other lintian-clean packages do not link to lintian.d.o, examples:

http://packages.qa.debian.org/c/chromium-bsu.html
http://packages.qa.debian.org/c/clamav-unofficial-sigs.html
http://packages.qa.debian.org/e/e00compr.html
http://lintian.debian.org/maintainer/p...@debian.org.html#flasm
http://lintian.debian.org/full/p...@debian.org.html#flasm

Some packages do not link to lintian.d.o, despite having issues, for eg:

http://packages.qa.debian.org/f/flasm.html
http://lintian.debian.org/maintainer/p...@debian.org.html#flasm
http://lintian.debian.org/full/p...@debian.org.html#flasm

Others link to the lintian.d.o maintainer report when there are no
warnings or errors, for example:

http://packages.qa.debian.org/libe/libemail-simple-creator-perl.html
http://lintian.debian.org/full/p...@debian.org.html#libemail-simple-creator-perl
http://lintian.debian.org/maintainer/p...@debian.org.html#libemail-simple-creator-perl

When a package has lintian errors or warnings, I think the PTS should
link to the maintainer report. 

When a package has no lintian errors or warnings, I think the PTS should
link to the full report.

When a package has no lintian complaints, I think the PTS should not
link to any lintian reports.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


pts-lintian-issues.tar.gz
Description: application/compressed-tar


signature.asc
Description: This is a digitally signed message part

Re: No more userdir on merkel (Was: UDD upload-history update-command broken)

[Paul Wise]

On Tue, Oct 13, 2009 at 11:16 PM, Raphael Geissert  wrote:
>> On Tue, Oct 13, 2009 at 04:16:33PM +0200, Sandro Tosi wrote:
>>> Am I the only one quite unhappy with this change? If I'm alone, no
>>> problem, I'll find something else, but if we are a bit more, what do
>>> you think about contacting DSA and ask to rethink about this change?
>
> I've asked them to re-enable it and it was denied, at least for the qa.d.o
> case. One of the reasons was so that stuff that matters isn't restricted to
> a person, so that in the event the person doesn't have time or whatever,
> anyone else can take over.

I can only applaud this reasoning for such a policy change.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Gathering package upstream meta-data in the UDD. (was: Re: more formally indicating the registration URL)

[Paul Wise]

This idea of extra metadata storage is really excellent.

I'd like to suggest the following:

Move this thread to debian-devel for a wider discussion.

Move the upstream-metadata.yaml, Homepage, debian/watch out of source
packages since they need to be able to change independently of the
Debian package. Not sure what the right location is, but I'd suggest
UDD could be the canonical location for it and a web interface at
alioth be the way to edit it (like the debtags interface).

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

add information on what was adopted to the WNPP report?

[Paul Wise]

On Fri, Nov 13, 2009 at 8:28 AM,   wrote:

> Total number of orphaned packages: 683 (new: 20)
> Total number of packages offered up for adoption: 147 (new: 0)
> Total number of packages requested help for: 53 (new: 0)

This is kinda depressing, it would be nice to see information on what
was adopted in the WNPP report.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: RFC: organising focused BSPs

[Paul Wise]

I consider this to be an absolutely excellent idea.

We in the Debian Games team considered a similar concept:

http://wiki.debian.org/Games/Parties

Absolutely the main point of these is to get more/new people involved
(especially those not yet involved in Debian), *not* to get stuff
done. Getting stuff done is a nice side-effect of them of course ;)

For the first one we planned to a screenshots party since making
screenshots doesn't require a whole lot of skill and would thus be a
nice way to introduce the concept to the wider Debian using community
and get new people interested in helping improve gaming in Debian.
Unfortunately this is currently stalled due to lack of time on my part
to finish building the web interface I started for co-ordinating the
party. I'm hoping I'll find time to do this before squeeze though.

http://wiki.debian.org/Games/Parties/Screenshots

Later on we planned to do bug finding and fixing parties as we attract
more folks to the team.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: RFC: organising focused BSPs

[Paul Wise]

On Tue, Dec 1, 2009 at 12:19 AM, Stefano Zacchiroli  wrote:

> To make understand what this is about I suggest using a common name and
> I don't think it would be wise to overload "BSP". I don't mind choosing
> "Bug Day" for Debian too. If you like it, you can probably just go ahead
> and announce the "X.org Bug Day" on d-d-a.

I personally like the Party part of the BSP name, even if it is
minimised by turning the phrase into an acronym. Perhaps calling it a
Debian X Party would be good?

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: How long does debtag information need to propagate to UDD

[Paul Wise]

On Tue, Dec 15, 2009 at 11:38 PM, Andreas Tille  wrote:

> So my question is: How to track the path the information on the public
> DebTags interface to UDD?  I might try and read the code of the debtags
> importer but my hope is somebody is able to give a quick answer and has
> an idea who is really responsible (DebTags maintainers or UDD importer
> or even somebody else) and how this can be fixed.

IIRC the debtags admins (enrico) approve the changes and then they are
automatically added to the Packages files in the archive. Presumably
UDD then imports them from there.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: How to re-upload a removed package?

[Paul Wise]

On Wed, Dec 16, 2009 at 12:52 AM, Alejandro Rios
 wrote:

> 1. Should I upload it to unstable or to proposed-updates?

That depends on your intention. At the minimum, the security issue
should be fixed in oldstable even though security support for it
expires in February. For that you need to follow this procedure:

http://www.debian.org/doc/developers-reference/pkgs.html#bug-security

By uploading to unstable and more importantly maintaining the package
in the future you ensure that destar will remain available in Debian
and be available in future releases.

> 2. If uploading to unstable, should I make other changes different from
> those that are related to the security bugs (i.e. for lintian warnings,
> standars version), or not?

If you intend for the package to be available in future Debian
releases, you should do some or all of the following:

Clean up the package for lintian, policy, dh7, dpkg-source v3 etc.

Get in contact with upstream (which seems to have become active again
since destar was removed) to get the security issue fixed there and a
new release made. If you have time you could also get involved in
developing the software to ensure it does not get removed from Debian
again.

Contact the former maintainers of the Debian destar package - Debian
VoIP Team - and ask them if they would be interested in maintaining it
now that upstream is active again. If so you could join the team and
help them maintain it in their SVN repository. If not, then you could
maintain it yourself through sponsorship:

http://people.debian.org/~mpalmer/debian-mentors_FAQ.html
http://wiki.debian.org/SponsorChecklist

When a package is removed from Debian, all the bugs are closed (by
Marco Rodrigues). So you should look at the bug list (archived and
non-archived) for destar and reopen the ones that are closed in
version 0.2.2-5.2+rm, then try to get them fixed:

http://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;src=destar

Fix all the issues listed on the PTS page:

http://packages.qa.debian.org/d/destar.html

Ensure that the package will pass the NEW queue:

http://ftp-master.debian.org/REJECT-FAQ.html

Import the changes from the Ubuntu package:

https://launchpad.net/ubuntu/+source/destar

Look at the Ubuntu bugs too (inc closed ones):

https://bugs.launchpad.net/ubuntu/+source/destar

The next Debian/Ubuntu releases are quite soon so you'll need to do
the above fairly quickly.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: How long does debtag information need to propagate to UDD

[Paul Wise]

On Sun, Dec 20, 2009 at 2:39 AM, Lucas Nussbaum
 wrote:

> UDD imports debtags from
> http://svn.debian.org/viewsvn/*checkout*/debtags/tagdb/tags (that code
> was written by zack). Should we do something else?

It appears that those are the tags after approval by enrico, so that
should be fine.

Looks like enrico has not had time to do approval for a long time, so
it might be that either debtags is abandoned or the canonical location
of the data is now elsewhere, best ask enrico about this:

http://svn.debian.org/wsvn/debtags/tagdb/?op=log

Another issue I can think of would be there might be a delay between
enrico committing and dak importing those, during which time UDD would
have different debtags to the Tag: fields is in the Packages files.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#562109: patch for maintainers-needed.pl

[Paul Wise]

On Thu, 2009-12-24 at 00:44 +0100, Serafeim Zanikolas wrote:

> ps. I understand that maintainers-needed.pl isn't actively maintained (funny
> that) and I'm not a DD to apply it myself, so I'm cc'ing Paul who's requested
> the feature in the first place

While I'm subscribed to debian-qa, I'm not a member of the qa unix group
on alioth so I cannot commit your change, sorry. Hopefully someone who
is will look at and apply your patch. Thanks a lot for creating it.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

add font review links to the PTS?

[Paul Wise]

Hi all,

pkg-fonts would like to add links from the PTS to our font review
pages for each binary package containing a font. What information
would the PTS need in order for us to add this? Here are some links to
the review index, the review for ttf-dejavu-core and DejaVu Sans.

http://pkg-fonts.alioth.debian.org/review/
http://pkg-fonts.alioth.debian.org/review/pkg-ttf-dejavu-core.html
http://pkg-fonts.alioth.debian.org/review/fnt-7508dfc17b253ba3187842cad3fab4c9.html

Later down the track we might like to add problems mentioned by
fontlint and other font validators to the todo section of the PTS.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: add font review links to the PTS?

[Paul Wise]

On Fri, Jan 29, 2010 at 5:26 PM, Stefano Zacchiroli  wrote:

> I confess it is not clear to me the purpose of adding this to the
> PTS. Or better, it is not clear to me in which part of the PTS you want
> that. Do you want a link in the links section like the homepage
> stuff. That would be reasonable. Otherwise, if you want it as a "TODO",
> I'm not sure which kind of TODO message you envisage (maybe I've just
> not ended up on the right pages in the current font review page).

Initially just a link in the links section. Later on when we figure
out how to parse the fontlint, otvalid etc output, possibly something
in the TODO section, probably like what is shown for lintian
complaints from lintian.d.o.

> In both cases, the steps to have integration are pretty much the
> standard ones:
>
> - Provide a complete index in a single file, giving all the information
>  the PTS would need to generate font-review-related information at each
>  pulse.
>
>  Ideally, the index should be source-package oriented, but we can leave
>  also with binary-package oriented indexes. If you want me to name a
>  file format for the index, I vote for YAML.

A binary-package oriented index would be easier, otherwise we'd need
to call dpkg a lot or rewrite the review script in something other
than shell.

> - If you just want links, the index should map packages to the relevant
>  links. That way you will be able to change the URL scheme without
>  needing interaction with us. If you want also TODO items, that
>  information should be added to, we can discuss details once it is
>  clear which kind of TODO you will need.

How about something like this? (not sure if it is valid YAML)

link:
text: Font review
- package: a2ps
url: http://pkg-fonts.alioth.debian.org/review/pkg-a2ps.html
- package: adonthell-data
url: http://pkg-fonts.alioth.debian.org/review/adonthell-data.html
todo:
text: The Debian font review
url: http://pkg-fonts.alioth.debian.org/review/
- type: fontlint
  text: fontlint complaint(s)
- type: fontlint
  text: fontlint complaint(s)
- package: a2ps
  fontlint: 3
- package: adonthell-data
  fontlint: 2

Initially the todo items would not be present and we would add them later.

> Well, this seems to go in the TODO/problem directions, but if you
> already have that information I'd prefer doing the integration once and
> for all, what would be the point in diluting it?

The information for the TODO stuff is (mostly) in the review pages
already, the main issue is parsing it into a useful form for the PTS.

PS: this is something that could probably benefit from #509416 being
implemented.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: add font review links to the PTS?

[Paul Wise]

On Fri, Jan 29, 2010 at 8:16 PM, Stefano Zacchiroli  wrote:

> OK then, we'll do the mapping binary -> source, we already have the
> needed map.

Great, thanks.

>> How about something like this? (not sure if it is valid YAML)
>
> Nope, this one is structured "purpose"-first, package then. I'd prefer a
> package-first, purpose-then. E.g. (YAML not checked as well):
>
>  ---
>  package: a2ps
>  font_url: http://pkg-fonts.alioth.debian.org/review/pkg-a2ps.html
>  issues:
>    
>  todo:
>    ...
>  ---
>  package: a2ps
>  font_url: http://pkg-fonts.alioth.debian.org/review/pkg-a2ps.html
>  ---
>
> and so on. Of course "issues" and "todo" can be absent.
>
> Does that fly for you?

Sure.

Will file a PTS bug with more details once the YAML output is
implemented and valid.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Missing information about binary packages in new queue

[Paul Wise]

On Sat, Jan 30, 2010 at 10:44 PM, Andreas Tille  wrote:
> On Sat, Jan 30, 2010 at 03:03:24PM +0100, Torsten Werner wrote:
>> Andreas Tille schrieb:
>> > How do I get the short and long description of
>> > the package acetoneiso which is currently in new?
>>
>> are you looking for
>> ?
>
> Sure - but FORMERLY these pages contained the information I was refering
> to.  As I said we just used the information on these page.  At least I
> can not read the long description (I admit my claim that the short
> description is missing was wrong) or the Dependency relations etc.
> Please have a look into the old output form.  If needed I can send you a
> copy of the old DAK code (status from 20.01.2009) which was generating
> the pages in show_new.py.
>
> If I remember right the "Navigation" at right bottom of these pages
> showed more items.  This stuff is just missing.

Here are some examples of the old format of these pages:

http://web.archive.org/web/20080630193353/http://ftp-master.debian.org/new/qmail-run_2.0.0.html
http://web.archive.org/web/20080608063628/ftp-master.debian.org/new/libgit-ruby_1.0.7-1.html
http://web.archive.org/web/20080609071041/ftp-master.debian.org/new/x11proto-dri2_1.1-1.html
http://web.archive.org/web/20080601184737/ftp-master.debian.org/new/icedtea-gcjwebplugin_1.0-1.html

The stuff that is missing includes control file, lintian info, .deb
contents, copyright and file listing for each binary package. Most of
that is not available in new.822.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#570087: PTS: fonts review URLs

[Paul Wise]

Package: qa.debian.org
Severity: normal
User: qa.debian@packages.debian.org
Usertags: pts
X-Debbugs-CC: pkg-fonts-de...@lists.alioth.debian.org

Please add a "fonts" link to the links section of the PTS. The YAML
based mapping of binary package names to font review pages is here:

http://pkg-fonts.alioth.debian.org/review/debian-font-review.yaml

It is updated with an @weekly cron job on alioth, which uses UTC. It is
only updated weekly since it takes a while to run and because it relies
on the Contents files, which IIRC are only updated weekly.

The font review pages currently contain font meta-data (including
embedded copyright & license info), fontconfig information, Unicode
coverage and fontlint output (which checks fonts for problems).

The Debian Fonts Task Force intends to improve these review pages over
time, adding new meta-data, QA checks and to improve the image previews.

Eventually we aim to add lines to the PTS TODO section for buggy fonts.
We'll submit another bug report when the preparation for that is done.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Re: Prototype script to determine last commit and last upload.

[Paul Wise]

On Sat, Apr 10, 2010 at 1:29 AM, Mehdi Dogguy  wrote:
> Niels Thykier wrote:
>>
>> The second script[3] we made was a script to determine the last upload
>> by  parsing the changelog of packages and look for an email in the
>> signature line.
>
> How is it different from who-uploads (from devscripts)?

who-uploads looks at GPG signatures, not changelog signature lines.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/u2ue13a36b31004091723n23ed1b14veffd0bbddd914...@mail.gmail.com

Bug#577176: PTS: display info from security team's embedded-code-copies file

[Paul Wise]

Package: qa.debian.org
Severity: wishlist
User: debian-qa@lists.debian.org
Usertags: pts
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org

It would be nice if the PTS could parse the security team's
embedded-code-copies file[1] and put a TODO note for those source
packages that are marked as  (embed). Some other types might
also be appropriate for a TODO note, CCing the security team for input.

 1. http://svn.debian.org/wsvn/secure-testing/data/embedded-code-copies 
svn://svn.debian.org/svn/secure-testing/data/embedded-code-copies

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#582038: qa.debian.org: [PTS] Please link to UbuntuDiff

[Paul Wise]

On Tue, May 18, 2010 at 5:29 PM, Mehdi Dogguy  wrote:

> ²: no, the source code of UbuntuDiff is not Ubuntu specific.

Have you considered renaming it to derivs.d.n, generating the same
info for other Debian derivatives and then feeding all that into UDD?
That would mean that the ubuntu section on the PTS could be renamed to
"Derivatives".

Also:

http://wiki.debian.org/MergeDerivedDistributions

-- 
bye,
pabs

http://wiki.debian.org/PaulWise



--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktiksueywn0uwpuxdividnhpqeo0laz_ay1f23...@mail.gmail.com

Bug#570087: PTS: fonts review URLs

[Paul Wise]

tags 570087 + patch
thanks

On Tue, 2010-02-16 at 19:39 +0800, Paul Wise wrote:

> Please add a "fonts" link to the links section of the PTS. The YAML
> based mapping of binary package names to font review pages is here.

I've attached a naive and untested patch to implement this. I may be
missing something but adding new links to the PTS seems trivial so I
assume that my patch works properly.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise
Index: www/xsl/pts.xsl
===
--- www/xsl/pts.xsl	(revision 2391)
+++ www/xsl/pts.xsl	(working copy)
@@ -913,6 +913,12 @@
 	  
 	
   
+  
+	
+	  fonts
+	
+  
 
   
 
Index: www/bin/other_to_xml.py
===
--- www/bin/other_to_xml.py	(revision 2391)
+++ www/bin/other_to_xml.py	(working copy)
@@ -21,6 +21,14 @@
 source2binaries = {} # maps a source package to its binaries
 binary2source = {}   # maps a binary package to its source
 
+def read_font_reviews(fname):
+y = yaml.load(file(fname))
+packages = {} # maps pkg to the font review for it
+for pkg, data in y.iteritems():
+if data.has_key('url'):
+packages[pkg] = data['url']
+return packages
+
 def read_shortdesc(fname):
 global binary2source
 source_descs = {} # source package -> (binary package -> short description)
@@ -330,6 +338,8 @@
 # read short descriptions
 shortdescs = read_shortdesc(os.path.join(dir, "shortdesc.txt"))
 
+font_reviews = read_font_reviews(os.path.join(dir, "debian-font-review.yaml"))
+
 # Create the XML documents
 while 1:
 line = sys.stdin.readline()
@@ -581,6 +591,13 @@
 else:
 shortdesc_sig = ''.__hash__()
 
+# Add font review links
+if font_reviews.has_key(pkg):
+elt = doc.createElement("fonts")
+elt.setAttribute('href', font_reviews[pkg])
+else:
+root_elt.setAttribute("fonts", "no")
+
 # Get security issues
 if security.has_key(pkg):
 root_elt.setAttribute('security', security[pkg])
Index: www/bin/update_incoming.sh
===
--- www/bin/update_incoming.sh	(revision 2391)
+++ www/bin/update_incoming.sh	(working copy)
@@ -169,6 +169,9 @@
 # retrieve package descriptions from UDD
 nice_wget http://qa.debian.org/data/pts/shortdesc.txt shortdesc.txt
 
+# download the Debian fonts review
+nice_wget http://pkg-fonts.alioth.debian.org/review/debian-font-review.yaml debian-font-review.yaml
+
 # What more ?
 
 # Decompress all files


signature.asc
Description: This is a digitally signed message part

Re: [poll] Ubuntu column on DDPO visible by default?

[Paul Wise]

On Tue, Aug 3, 2010 at 4:40 PM, Lucas Nussbaum  wrote:

> Actually, I think that the problem with the current DDPO is that its
> goal is to enable developers to deduce tasks from a summary of data, so
> it makes sense to provide as much information as possible.
>
> Often, it would be possible to deduce the tasks from the information
> automatically (bugs, missing builds, etc) so it would also make sense to
> have a tasks-oriented view, similar to what ddpo-by-mail provides but
> with more tasks. That's something that could be easily done using UDD,
> it just needs someone to do it.

If you do that, please remember to close #461898 and come see me for a
free $BEVERAGE. For now I'm using the PTS pages as a substitute.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlkti=4umofv+qer_m5h+q_4e6qnyixqqz3ns75i...@mail.gmail.com

Re: [poll] Ubuntu column on DDPO visible by default?

[Paul Wise]

On Thu, Aug 26, 2010 at 2:36 PM, Holger Levsen  wrote:

> P.S.: IOW: why should the _Debian_ PTS care about a single, derivative and
> highlight that in its PTS? (By default, for all users. Having that column on
> demand is a nice thing for those who care. But enabling it for all and by
> default is IMO a marketing desaster, also for internal "marketing" and
> motivation)

It would be great if more derivatives would publish links to their
patches and bug trackers.

Does DebianEdu have a separate bug tracker and auto-generate patches
against Debian packages?

During the derivatives BoF at DebConf I asked the other two
represented derivatives (Webconverger, grml) if they could do the
same, but they either didn't have a bug tracker or always file bugs in
our bug tracker as appropriate and they are both livecd distros so
their derivativeness is about package selection.

I'd personally like to see non-Debian-derived distros linked from PTS
pages too, currently I resort to using whohas for finding patches and
bugs for my packages in those.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktintj4wjyb-srhdxeimjffazkypgsasc1b_=m...@mail.gmail.com

Re: Keeping content of binary and source packages in UDD (Was: Search for a file in all Debian source packages)

[Paul Wise]

On Fri, Oct 1, 2010 at 2:45 PM, Andreas Tille  wrote:

> But in principle it does sound like a good idea to feed this information
> into UDD.  What do you think about keeping content of binary and source
> packages inside UDD?

Sounds very good to me.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktimj2rzpz-m2pqxqvai21dwnwocxiznkozrc7...@mail.gmail.com

Re: Bug #602932: tilecache: Invalid maintainer address

[Paul Wise]

2010/11/13 René Mayorga :
> On Thu, Nov 11, 2010 at 09:25:15PM +0100, Ralf Treinen wrote:
>> Hi,
>>
> Hi Ralf,
>
>> this looks like a case for the MIA team: Bug#602932, the email address
>> of the maintainer is not valid. The maintainer does not seem to be a dd.
>
> Tanks for pointing this to the MIA team.
>
> BTW, this package it could be a good candidate for removal/orphan:
>  + It has a low popcon,
>  + It looks unmaintained
>  + Maintainer looks inactive
>
> I'm not sure if there is any more alternatives for this software already on
> Debian so I do not have any strong point about removal or orphan.
>
> I'm CCing d...@l.d.o to have more eyes on it.

There was a thread about tilecache on the Debian GIS team list
recently. tilecache maintenance will be taken over by David Paleino
and others from the team.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktim__nztj=wfjku5ny6ys4e5hao39fq--wcr=...@mail.gmail.com

Re: UDD: Difference in DEHS table between unstable_upstream and experimental_upstream

[Paul Wise]

Taking a random sample tkgate:

http://dehs.alioth.debian.org/report.php?package=tkgate
http://dehs.alioth.debian.org/wwiz_detail.php?id=33498256&type=watch
http://dehs.alioth.debian.org/wwiz_detail.php?id=33496155&type=watch

Yes it looks like DEHS knows unstable/experimental can and do have
different watch files.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktikauzwdxe9trnagw7cxidbimo-bf4pv3rcjf...@mail.gmail.com

Bug#609800: qa.debian.org: please add NEW queue info to madison.php

[Paul Wise]

Package: qa.debian.org
Severity: wishlist

Please add information about the NEW queue to madison.php so that
rmadison will show information about source and binary packages in the
NEW queue. Machine-readable information about the NEW queue is here:

http://ftp-master.debian.org/new.822

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#609802: qa.debian.org: please add NEW queue info to the PTS

[Paul Wise]

Package: qa.debian.org
Severity: wishlist

Please add information about the NEW queue to the PTS so that it will
show information about source and binary packages in the NEW queue when
those packages don't yet exist in Debian. Machine-readable information
about the NEW queue is here:

http://ftp-master.debian.org/new.822

Currently we just get a generic 404 page for binary packages and a nice
"This package is not part of any Debian distribution" message for source
packages in NEW. It would be great if both of these were changed to the
normal page minus everything that can't be extracted from new.822.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Re: Q & A work?

[Paul Wise]

[CCing you Dean since I'm not sure you are subscribed]

On Sun, Jan 16, 2011 at 10:44 AM, Dean Loros  wrote:

> I would like to help with testing. Ideas on where I could get involved with Q 
> & A?

In Debian we tend to focus on automated testing since it is more
scalable. We have automated source and binary package checking
(lintian), automated build testing (thanks to lucas), automated
build-time testing (thanks to upstream test suites), automated package
install testing (piuparts), automated system install testing
(BabelBox), automated font linting (pkg-fonts review) and now
automated source code analysis (daca).

One thing we currently lack on the automated testing front is
automated post-install testing of individual packages and I think also
automated post-install system testing.

lintian: http://lintian.debian.org/
piuparts: http://piuparts.debian.org/
BabelBox: http://wiki.debian.org/DebianInstaller/BabelBox
pkg-fonts review: http://pkg-fonts.alioth.debian.org/review/
daca: http://qa.debian.org/daca/

On the side of non-automated testing we seem to not have any
organised. If you would like to start organising regular Debian
testing days, that would be great. Fedora has test days too. I planned
to organise something similar for the Debian games team but never got
around to it.

fedora: http://fedoraproject.org/wiki/QA/Test_Days
games parties: http://wiki.debian.org/Games/Parties

> I was/am involved with Gnome-Shell for the last couple of years & know most 
> of the
> stack.

I'm sure the Debian GNOME team could use some help processing incoming
bugreports and triaging old bug reports.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktinnffkn97aa+vhf6ez6pcsbyneopzm9annhk...@mail.gmail.com

Bug#614681: qa.debian.org: mention manpage-alert (from devscripts) on qa.d.o/man-pages.html

[Paul Wise]

Package: qa.debian.org
Severity: wishlist

Please mention manpage-alert (from devscripts) on qa.d.o/man-pages.html
since it is much better for people to document commands that are on
their system than it is for them to document random commands throughout
the distribution.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

removing old automake versions from Debian?

[Paul Wise]

Hi Eric, QA folks,

It seems that automake1.4 no longer has any reverse (build-)deps and we
are at the start of the wheezy cycle, so now might be a good time to
remove it. If you agree, please file a removal request.

automake1.7 still has 30 source packages with build-deps on it. Seems to
me that removing it is quite achievable in the wheezy cycle.

automake1.9 has 2 binary packages with deps on it and 142 source
packages with build-deps on it. Removing this is probably also
achievable within the wheezy cycle.

automake1.10 has only 37 source packages with build-deps on it, so it
could also be removed. On the other hand it is a relatively recent
release so various upstream developers running testing might be relying
on it.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Re: replacement of merkel services in DDPortfolio

[Paul Wise]

On Tue, 2011-04-05 at 13:22 +0200, Jan Dittberner wrote:
 
> I changed an entry in the ddportfolioservice [1] to reflect the new
> location to lookup DD assigned debian.net domain names (Paul: thanks
> for the Wiki edit). There are some more merkel URLs that stopped
> working. Do you know whether there are replacements on other Debian
> hosts? The URLs in question are:
> 
> * all messages (i.e., full text search for developer name on all bug logs)
>   
> http://merkel.debian.org/~don/cgi/search.cgi?phrase=Jan+Dittberner;search=search

I thought UDD might be able to do this, but it doesn't have the right
options. Maybe Don can comment on where this is moving, CCed.

> * keylog (per-key upload list) (note: uses key fingerprint)
>   
> http://merkel.debian.org/~enrico/keylog/B2FF1D95CE8F7A22DF4CF09BA73E008FB8DD.html

Code is here:

git://git.debian.org/~enrico/keylog.git

CCing enrico, hopefully he can give us the status of any replacement.

> * MIA database information
>   ssh merkel.debian.org /srv/qa.debian.org/mia/mia-query ja...@debian.org
> 
> * Group membership information
>   ssh merkel.debian.org id jandd

These can be replaced with any other Debian machine, I chose master.d.o
for the wiki page.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#627572: pts: update to accept Standards-Version: 3.9.2

[Paul Wise]

Package: qa.debian.org
Severity: normal
User: qa.debian@packages.debian.org
Usertags: pts

The PTS needs to be updated to accept Standards-Version: 3.9.2 instead
of Standards-Version: 3.9.1.

http://packages.qa.debian.org/w/warzone2100.html

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Re: RFH: handle bug reports for removed packages

[Paul Wise]

On Sun, May 29, 2011 at 6:27 PM, Martin Michlmayr  wrote:

> I'm looking for someone to take care of bugs of packages that have
> been removed from Debian.  More information on the task is below.
> Anyone interested?

IIRC the FTP masters took over at least part of this. For eg:

http://bugs.debian.org/596536

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/BANLkTi�4-qa_c05nzjm55tkqwbyzq...@mail.gmail.com

Bug#628886: PTS: strip whitespace from pre-redirection URLs

[Paul Wise]

Package: qa.debian.org
Severity: wishlist
User: debian-qa@lists.debian.org
Usertags: pts
Tags: patch

Please apply the below patch to the PTS apache configuration to strip
whitespace from input URLs before performing the redirects. This is
useful when copy and pasting package names and accidentally including
extra whitespace.

--- a/apache.conf
+++ b/apache.conf
@@ -15,11 +15,11 @@
 RewriteEngine on
 RewriteRule ^/$ /common/index.html [L,R]
 RewriteRule ^/favicon\.ico$ http://www.debian.org/favicon.ico [L,R]
-RewriteRule ^/lib([^/])([^/]+)$ /lib$1/lib$1$2.html [L,R]
-RewriteRule ^/([^/])([^/]+)$ /$1/$1$2.html [L,R]
-RewriteCond %{QUERY_STRING} ^src=lib(.)(.+)$
+RewriteRule ^/\s*lib([^/])([^/]+)\s*$ /lib$1/lib$1$2.html [L,R]
+RewriteRule ^/\s*([^/])([^/]+)\s*$ /$1/$1$2.html [L,R]
+RewriteCond %{QUERY_STRING} ^src=\s*lib(.)(.+)\s*$
 RewriteRule ^/common/index.html$ /lib%1/lib%1%2.html? [L,R,NE]
-RewriteCond %{QUERY_STRING} ^src=(.)(.+)$
+RewriteCond %{QUERY_STRING} ^src=\s*(.)(.+)\s*$
 RewriteRule ^/common/index.html$ /%1/%1%2.html? [L,R,NE]
 
 

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#628886: PTS: strip whitespace from pre-redirection URLs

[Paul Wise]

On Fri, 2011-06-03 at 15:28 +0200, Raphael Hertzog wrote:

> This patch does not strip trailing whitespaces. The [^/]+ or .+ are greedy
> and will eat the whitespaces. Thus \s*$ will always match the empty
> string. Please update your patch.

Ah, thanks, updated patch below:

--- a/apache.conf
+++ b/apache.conf
@@ -15,11 +15,11 @@
 RewriteEngine on
 RewriteRule ^/$ /common/index.html [L,R]
 RewriteRule ^/favicon\.ico$ http://www.debian.org/favicon.ico [L,R]
-RewriteRule ^/lib([^/])([^/]+)$ /lib$1/lib$1$2.html [L,R]
-RewriteRule ^/([^/])([^/]+)$ /$1/$1$2.html [L,R]
-RewriteCond %{QUERY_STRING} ^src=lib(.)(.+)$
+RewriteRule ^/\s*lib([^/\s])([^/\s]+)\s*$ /lib$1/lib$1$2.html [L,R]
+RewriteRule ^/\s*([^/\s])([^/\s]+)\s*$ /$1/$1$2.html [L,R]
+RewriteCond %{QUERY_STRING} ^src=\s*lib([^\s])([^\s]+)\s*$
 RewriteRule ^/common/index.html$ /lib%1/lib%1%2.html? [L,R,NE]
-RewriteCond %{QUERY_STRING} ^src=(.)(.+)$
+RewriteCond %{QUERY_STRING} ^src=\s*([\s])([\s]+)\s*$
 RewriteRule ^/common/index.html$ /%1/%1%2.html? [L,R,NE]
 

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#628886: PTS: strip whitespace from pre-redirection URLs

[Paul Wise]

On Fri, 2011-06-03 at 21:53 +0800, Paul Wise wrote:

> Ah, thanks, updated patch below:

Bah, had some typos, fixed:

--- a/apache.conf
+++ b/apache.conf
@@ -15,11 +15,11 @@
 RewriteEngine on
 RewriteRule ^/$ /common/index.html [L,R]
 RewriteRule ^/favicon\.ico$ http://www.debian.org/favicon.ico [L,R]
-RewriteRule ^/lib([^/])([^/]+)$ /lib$1/lib$1$2.html [L,R]
-RewriteRule ^/([^/])([^/]+)$ /$1/$1$2.html [L,R]
-RewriteCond %{QUERY_STRING} ^src=lib(.)(.+)$
+RewriteRule ^/\s*lib([^/\s])([^/\s]+)\s*$ /lib$1/lib$1$2.html [L,R]
+RewriteRule ^/\s*([^/\s])([^/\s]+)\s*$ /$1/$1$2.html [L,R]
+RewriteCond %{QUERY_STRING} ^src=\s*lib([^\s])([^\s]+)\s*$
 RewriteRule ^/common/index.html$ /lib%1/lib%1%2.html? [L,R,NE]
-RewriteCond %{QUERY_STRING} ^src=(.)(.+)$
+RewriteCond %{QUERY_STRING} ^src=\s*([^\s])([^\s]+)\s*$
 RewriteRule ^/common/index.html$ /%1/%1%2.html? [L,R,NE]
 
 

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

DebConf11 and DebCamp?

[Paul Wise]

Hi all,

Anyone going to DebConf11 and or DebCamp?

What will other QA people be working on?

I'm hoping people knowledgeable about rmadison, the PTS, DDPO and UDD
will be at DebCamp. I intend to work on integration of the derivatives
census into Debian infrastructure and having such people around would
be very helpful, since my initial focus for integration will be the
sources.list snippets and resulting packages information.

http://wiki.debian.org/Derivatives/Census
http://wiki.debian.org/Derivatives/Integration

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/banlktin4zksbehsngdhcxfab47xsadx...@mail.gmail.com

Re: [daca] http://qa.debian.org/daca is 404

[Paul Wise]

On Sun, Jun 12, 2011 at 8:17 PM, Stefano Zacchiroli wrote:

> As per subject. Has DACA moved somewhere else?

It seems to be available here, I guess a symlink went missing:

http://qa.debian.org/~geissert/daca/

Perhaps it should be moved into quantz:/srv/qa.debian.org/?

> /me, working on Coccinelle runs on the Debian archive

Nice :)

I think it would be nice to link DACA from the PTS to promote use of
its tools among maintainers.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/banlktin20+x8mnu7_khudcaqtecxdv-...@mail.gmail.com

Re: Lintian as a static analysis framework

[Paul Wise]

On Thu, Jul 7, 2011 at 6:24 PM, Stefano Zacchiroli wrote:

> - the reborn of a sources.debian.org service (sort of browsable /
>  highlighted/ searchable Debian sources at your fingertips on the web)

Is there any info about this?

Last year Noel was working on such a project also:

http://wiki.debian.org/source.debian.org

At one point there was source.debian.net running OpenGrok, a very nice
Java-based source code indexer.

> - Coccinelle [1] runs on the whole of Debian sources, meant to be
>  integrated with DACA [2]

Very nice.

> I've ended up cooking up my own code for the above (not all is done
> yet), but there clearly a good part of it that could be factored out
> (and done better). Do you think the framework you're imagining at this
> point could help with any or all of the above?  If yes, I'll be happy to
> provide testing and/or comment on whether the design would fit the need
> of the above use cases.

I'm thinking yes but I'm not that familiar with lintian internals so I
will leave that to them.

> FWIW, I believe many other wannabe entrants in DACA would benefit from
> the addressing of similar use cases.

Yeah, DACA was my initial thought here. Why not have a
source-has-warnings-from-cppcheck lintian warning and logs for those
on lintian.d.o. Same goes for lots of the other existing checkers
listed in the mentors metrics[1] ideas; jpeginfo --check, pngcheck,
mp3diags, desktop-file-validate, fontlint, gettext-lint etc.

Of course, the addition of these many external checkers will mean more
CPU and I/O time. I guess the lintian vendor stuff could be leveraged
to have a set of profiles for different amounts of checking. In
addition this could mean that a more distributed approach to
processing packages for lintian.d.o would be better.

Looking at the metrics again, I'm also thinking about debexpo, Mole,
puiparts and that some consolidation of efforts would be nice. With a
few feature additions, maybe it would even be possible to merge
rpmlint one day ;)

1. http://wiki.debian.org/DebianMentorsNet#Metrics

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6HXEhOnqt0Arwe5DhC3ctXXVvbOFbfEbS0q04ooWJMV=q...@mail.gmail.com

Re: Lintian as a static analysis framework

[Paul Wise]

On Fri, Jul 8, 2011 at 9:25 AM, Stefano Zacchiroli wrote:

> I haven't yet chosen the technology for code indexing, but if anyone has
> experience with *multi-language* code indexers, I'd be happy to hear
> from you. I've looked around a bit, but I've found good technologies
> only for specific languages and I really don't want to have to run
> different indexers for different languages and maintain some proxy code
> that queries all of them in parallel. Hence the fallback I had in mind
> was some non-programming-language thing, like dear old Xapian. But I
> welcome better suggestions.

OpenGrok has support for multiple languages (C, C++, Fortran, Java,
Lisp, Perl, PHP, Python, shell, SQL, Tcl, VB and others), using
"analysers":

http://www.norbye.org/jenkins/job/OpenGrok/javadoc/overview-tree.html

> I guess that would clash with the dear old tension among minimizing
> lintian dependencies and being able to do very specific checks. We
> really don't want to have lintian depend on all static analysis tools
> out there and, last time I've checked, lintian maintainers didn't want
> to have conditional tests (i.e. tests active only when a specific other
> package is installed) to maintain test reproducibility.  I know lintian
> maintainers have been struggling with this design decision for a while,
> but I don't know the current state of the discussion.

Right. Thats where the profiles/vendor stuff comes in I think. A
default profile runs only the set of tests that are implemented within
lintian. Any tests that run external commands are in a secondary
profile and lintian warns/fails if the deps for that are missing and
are needed.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caktje6gchedee7ret7zm03omz_uhhxozje90atq-prv4rfq...@mail.gmail.com

Re: I18n data from browsable source archive (Was: Lintian as a static analysis framework)

[Paul Wise]

On Fri, Jul 8, 2011 at 10:00 AM, Andreas Tille wrote:

> Would you consider such i18n analysis as one such thing?

I guess adding i18n collectors to lintian could help achieve what you want.

Especially if lintian were to start running gettext-lint (and similar)
over the collected i18n data.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6Em7__KompvcfoKW2BXmY=mKK6REQ-=sqvxkasjngu...@mail.gmail.com

Re: Lintian as a static analysis framework

[Paul Wise]

On Fri, Jul 8, 2011 at 12:30 PM, Niels Thykier wrote:

> We could do it like that, though the vendor profiles specification
> actually deliberately did not answer the question of how to add
> third-party checks.  I know some people already do this, so we have made
> Lintian behave sanely to it.
>  The official "API" for adding third-party checks (and collections) is
> on my TODO list (this incl. #359059 for those interested).

I don't think running external checkers should be third-party checks,
they should be integrated into lintian like all the other checks. The
only thing that is different for them would be the decision about when
to run them, which is IMO the role for profiles.

For example:

full: run all the tests available in lintian, no matter if they
conflict or not ;)
debian-full: run all the tests that make sense in Debian, including
stuff like cppcheck
debian: run all the tests that aren't too I/O or CPU intensive
debian-ftpmaster: run only the ones ftpmaster care about
emdebian: same as debian but minus the checks for stuff they remove
(docs, i18n etc)
debathena: same as debian but minus the NMU checks

I guess 3rd-party checks are interesting for some
derivatives/groups/individuals, but I tend to think all checks should
be integrated into lintian and the decision of when to run them be
made via profiles.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caktje6hodmmgwp7k2fc5mct1smkhlh0y_zmjy1kzk313apc...@mail.gmail.com

Bug#614681: Mentioning manpages-alert on QA web pages

[Paul Wise]

On Sat, 2011-08-27 at 08:53 +0200, Giovanni Mascellani wrote:

> I'm fixing your bug about mentioning manpages-alert on QA webpages.

Thanks! It is fun to find out what bugs I filed ages ago :)

> But I'm not native English, so please tell me if the attached
> formulation is good.

Seems reasonable to me, the debian-l10n-english list might be the best
place to get advice about spelling and grammar though.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Re: Load on udd.d.o

[Paul Wise]

On Sun, Oct 23, 2011 at 7:46 PM, Peter Palfrader wrote:
> On Sun, 23 Oct 2011, Lucas Nussbaum wrote:
>
>> But the main problem, anyway, is that samosa is a bit low on RAM (only 6
>> GB), and a bit slow on I/O. In the long term, it would be useful to move
>> UDD to a faster box...
>
> We probably don't have anything like that tho.

Is this something that the publicity team could help with; putting out
a call for donations like was done for snapshot.debian.org?

http://www.debian.org/News/2009/20090208

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6F6r8WjT05fdFs=mn+ifpwxxdfrqgogpqd8patavef...@mail.gmail.com

Re: Bug#639481: dbi-link: Please move from postgresql-8.4 to postgresql-9.1

[Paul Wise]

On Sun, Nov 13, 2011 at 2:13 AM, Fernando Ike wrote:

>   This package isn't more necessary, because version 9.1 implemented sql/med
> and upstream no more maintain.
>
>   Hi QA Team, consider remove package unstable/testing repository?

http://wiki.debian.org/ftpmaster_Removals

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6HMA=zc8Gu1�fGRKOaQefwf9pz=hoatjohvvmz...@mail.gmail.com

Bug#650039: packages.qa.d.o: please add links to new buildd log check

[Paul Wise]

On Sat, Nov 26, 2011 at 4:22 AM, Bernhard R. Link wrote:

> Please add links to the new buildd log checks on
> http://buildd.debian.org/~brlink to packages.qa.debian.org.
>
> I guess what is needed is something like the following patch,
> which is totally untested as I could not come up with a way
> to test it (modeled after how lintian is done):

Excellent idea!

I would strongly encourage you to get it officially integrated with
the buildd stuff instead of leaving it in your home directory.

I will take a look at testing and committing the patch later today.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise



-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6H3Q2O+p3-+qWzcS5e3O+7C+hAVOG6vrT8+6h=jl88...@mail.gmail.com

Re: RFS: pgtcl (QA upload)

[Paul Wise]

On Fri, Dec 30, 2011 at 7:19 PM, Andrew Shadura wrote:

>   * Add homepage.
>   * Add watch file.

The sites you gave for these just gives me connection refused, did you
test them?

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caktje6ftscuvol3hbgbp3n2ckxvgh0jepl+k0vqq+m_faz8...@mail.gmail.com

Re: WNPP maintenance

[Paul Wise]

How about moving that script into the QA VCS? We can then run the cron
jobs on quantz.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caktje6gkwgtdfntsaebw_vr_go20vcqjfeej65gcv6m4f7y...@mail.gmail.com

Re: DEP-2: Debian Package Maintenance Hub

[Paul Wise]

This proposal has a lot of potiential to change Debian for the better,
thanks a lot.


I had planned to work on the BTS IRC bot from #debian-devel-changes
and enable it to forward stuff to more channels based on package name,
but it sounds like this proposal obsoletes that bot too.


I guess this proposal could also obsolete the low threshold NMU list:

http://wiki.debian.org/LowThresholdNmu


The DMUA mechanism currently depends on Maintainer/Uploaders, how do
you see DEP-2 interacting with it? Personally I would very much like
the DMUA mechanism go away and be replaced by something much more
explicit (my initial thought was an OpenPGP-based mail bot).


One thing that I have always wanted to see was better connections
between Debian and our users. Would this also enable say these?

 * the QA team to notify users a package is about to be removed
 * the security team to notify users they need to update
 * package developers to ask people to test a new feature


I wonder what kinds of commitments we might want people to document
about packages, some thoughts:

I use foo but could easily switch to something else.
I use foo rarely but want it to be available when I do.
I use foo often and it is an integral part of my workflow.
I have access to commit upstream on foo.
I am willing to triage bug reports on foo.
I am willing to review VCS commits on foo.
I am willing to fix only RC bugs on foo.
I am willing to do usual package maintainence.
I want to know when foo is updated in stable.


I wonder if this discussion should be brought to
debian-project/debian-devel, especially the maintainer/commitment
stuff will be quite far reaching.


As someone who has done a few PTS patches, I would welcome the
technology changes you plan. I do worry that not using static HTML
will reduce the performance though.


The data export thing sounds a bit like DDE, by Enrico Zini:

http://dde.debian.net/dde/


I wonder about the alioth FusionForge instance and how this will
interact with it.


-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caktje6fl_qucn13hh3pyxpqdkrytyf3r0mlg_nxz1etcvzw...@mail.gmail.com

Re: [UDD] Changing aux.py to fix quoting

[Paul Wise]

On Sat, Feb 4, 2012 at 4:46 PM, Andreas Tille wrote:

> since I switched to PostgreSQL 9.1 I realised that quoting "'"
> characters does not work any mory by escaping it using "\" signs.
> I wonder, how at all aux.py could work for others.  Because I have
> the feeling that I missed something I'm just asking for comments
> for the following patch to not break any UDD application.
>
> So what do you think about this which is needed *at my machine running
> testing*:

Sounds like you want to be using prepared statements, otherwise you
risk SQL injections.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6HthDv6m=y+0QHHQzHzmFJzj-18=n_e2onwnxhttdm...@mail.gmail.com

Re: [UDD] Changing aux.py to fix quoting

[Paul Wise]

On Sun, Feb 5, 2012 at 12:29 AM, Andreas Tille wrote:

> The quotation is actually used to feed strings into prepared statements.

Thats confusing, isn't the whole point of prepared statements that you
don't have to escape things?

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caktje6f845ujyqkd8n1c5qbhmq7f4s2azuxghrqdv_gutm3...@mail.gmail.com

Re: [UDD] Changing aux.py to fix quoting

[Paul Wise]

On Mon, Feb 6, 2012 at 3:58 AM, Andreas Tille wrote:
> On Sun, Feb 05, 2012 at 10:11:24AM +0800, Paul Wise wrote:
>> On Sun, Feb 5, 2012 at 12:29 AM, Andreas Tille wrote:
>>
>> > The quotation is actually used to feed strings into prepared statements.
>>
>> Thats confusing, isn't the whole point of prepared statements that you
>> don't have to escape things?
>
> Hmmm, good point.  I have not invented this quote function which has the
> additional purpose to care for proper utf-8 encoding.
>
> The current ddtp_gatherer.py is using things like:
>
>  query = "PREPARE ddtp_delete (text, text) AS DELETE FROM %s WHERE release = 
> $1 AND language = $2" % my_config['table']
>  cur.execute(query)
>  ...
>  query = "EXECUTE ddtp_delete (%s, %s)" % (quote(rel), quote(lang))
>  cur.execute(query)
>
> At least the code I wrote is using quote exclusively in connection with
> EXECUTE of a previousely PREPAREd statement.  The purpose was the
> (enforced) UTF-8 conversion.  When using it with PostgreSQL I needed
> to change the quoting as described in the initial mail.

I wasn't talking about PREPARE statements, hadn't even heard of them.

It appears the code is using standard Python string interpolation (and
thus needs the slash insertion) instead of what I was referring to:

  query = " EXECUTE ddtp_packages_recieve_description_md5
(%s, %s, %s, %s, %s)" % \
tuple([quote(item) for item in (self.pkg.package,
self.pkg.distribution, self.pkg.component, \
 self.pkg.release, self.pkg.version)])
  self.log.debug("execute query %s", query)
  cur.execute(query)

Looks like the reason for using string interpolation instead of
prepared statements was to be able to print out the queries for
debugging.

What I was referring to when I was talking about prepared statements
was stuff like this (from the derivatives census code):

cur.execute('SELECT version FROM srcpkg WHERE name=%s AND version=%s
LIMIT 1;', (name, version))

Notice there is no string interpolation here (despite using %s in the
string) and psycopg2/postgres handles the individual variables instead
of pre-encoding them and stuffing them into a query string using
Python string interpolation.

Here is how I would rewrite the above example from the ddtp_gatherer.py:

  cur.execute('EXECUTE
ddtp_packages_recieve_description_md5 (%s, %s, %s, %s, %s)',
(self.pkg.package, self.pkg.distribution, self.pkg.component,
self.pkg.release, self.pkg.version))

Instead of manually logging queries, I would probably use the
LoggingConnection class instead of the normal connection class.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6HbarnxuJfZ88xnbU0B-2=3zoxx0sgzkjvrvxxkw3b...@mail.gmail.com

Re: [UDD] Bug importer is missing files

[Paul Wise]

On Thu, Feb 16, 2012 at 2:59 AM, Don Armstrong wrote:

> [For those following along at home, to fix, we'd do this:
> bts found 48057 openssh/1:4.2p1-5 , notfound 48057 openssh-client/1:4.2p1-5 ; 
> ]

Why wouldn't that be src:openssh?

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caktje6etusk42y9p3g81ob_f9opu8kar1vmf_2luxmpaaqh...@mail.gmail.com

Bug#660170: qa.debian.org: please import security information from the security tracker

[Paul Wise]

Package: qa.debian.org
Severity: wishlist
User: qa.debian@packages.debian.org
Usertags: udd
X-Debbugs-CC: security-trac...@packages.debian.org

It would be very nice to import the information from the security
tracker into UDD. The data is available here:

svn://svn.debian.org/svn/secure-testing/data/

There is already code for parsing the data and updating an SQL database
in the same SVN repository:

svn://svn.debian.org/svn/secure-testing/

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Re: [UDD] Popcon input file contains illegal line

[Paul Wise]

>From IRC:

 I have no idea.  Bill handle most of that part of popcon. :)
Report a bug. :)
 could be related to multiarch, which I know popcon at the
moment do not work well with.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caktje6eur1oerv8mg2exrkftbgx-sowvvialmc1b63f6kcy...@mail.gmail.com

clang.d.n on the PTS?

[Paul Wise]

Sylvestre Ledru wrote:

> Recently, I have been working on a side project for Debian. The goal
> was to rebuild of the Debian archive (the distribution) with clang, a
> new C/C++ compiler.
...

> The result are detailed and explained here:
> http://clang.debian.net/

Would it be possible for this to export a file for consumption by the
PTS so people maintaining packages with clang issues can easily find out
about those issues by looking at the PTS? Some possible formats for such
a file might be these existing ones:

http://lintian.debian.org/qa-list.txt
http://pkg-fonts.alioth.debian.org/review/debian-font-review.yaml

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Re: clang.d.n on the PTS?

[Paul Wise]

On Wed, 2012-02-29 at 12:25 +0100, Sylvestre Ledru wrote:

> For course!

Excellent.

> Sorry for the dumb question but what the number means ?

The count of lintian tags of each type (error, warning, info, pedantic,
experimental) triggered by the package.

> Do you have a preferred format ?

The PTS uses XML internally, but we can consume anything that can be
easily read by python.

> What kind of information do you would like to have ?

There are two kinds of information consumed by the PTS.

First is the TODO items listed in the central column. I'm less familiar
with how those work, but I guess we need to know which packages to put
the todo items on, text of the todo items and where links should point
to.

Second is the links on the right. For those we need some way to know
which packages to put the link on and where the link should point to.

> PS: I am registered to debian-qa 

Sorry. I am also subscribed.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Re: clang.d.n on the PTS?

[Paul Wise]

On Wed, Feb 29, 2012 at 7:25 PM, Sylvestre Ledru wrote:

> Glad to know that this work is already interesting people :)

Also, could you add a note to DeveloperNews about this?

http://wiki.debian.org/DeveloperNews

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caktje6egpuy6e4eohdkkkrxdmqxwekfaezn40f1pi66gvok...@mail.gmail.com

Re: [UDD] Popcon input file contains illegal line

[Paul Wise]

On Thu, Mar 1, 2012 at 6:59 AM, Andreas Tille wrote:
> On Fri, Feb 17, 2012 at 08:53:22PM +0800, Paul Wise wrote:
>> >From IRC:
>>
>>  I have no idea.  Bill handle most of that part of popcon. :)
>> Report a bug. :)
>
> A bug to what package???

I assume popularity-contest, there are other popcon.d.o bug filed there.

>>  could be related to multiarch, which I know popcon at the
>> moment do not work well with.
>
> The problem has become worse.  Instead of one single problematic
> line the output says now:
>
> /org/udd.debian.org/tmp/all-popcon-results.txt.gz:279 - illegal package name 
> Package: 7kaa-data:all                      0     0     0     1

Looking at the file it seems that the format has changed. I suggest
UDD needs to adapt to the new format rather than popcon.debian.org
reverting to the old format.

BTW, please switch that to /srv instead of /org

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caktje6eidcgkzo4cqhunnjkom2kl5k-kxlabha-ec-f0e0_...@mail.gmail.com

Bug#581169: HEAnet sourceforge mirror: permission denied errors

[Paul Wise]

Hi HEAnet mirror operators,

The Debian project[1] QA group[2] is currently relying[3] on this
command to detect new versions of software that is packaged in Debian:

rsync -Pvan --log-file=/dev/null --list-only ftp.heanet.ie::sourceforge

Currently that produces the following errors, would it be possible for
you to grant read permissions on these directories and to alter your
mirroring process so it automatically fixes any permissions issues
propagated from your upstream, presumably sourceforge itself? That said,
when I visit the locations below via my web browser on the sourceforge
site, I am able to view and download the relevant files via my local
mirror, so this issue might be specific to HEAnet.

Are you interested in us adding mirr...@heanet.ie to the MAILTO field in
the cron job that runs the above rsync command? This would enable you to
be notified whenever there are issues with your sourceforge mirror.

rsync: opendir "/a/ao/aoo-extensions/1242/0" (in sourceforge) failed: 
Permission denied (13)
rsync: opendir "/a/ao/aoo-extensions/1551/0" (in sourceforge) failed: 
Permission denied (13)
rsync: opendir "/a/ao/aoo-extensions/1622" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/1736" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/1795" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/1804/1" (in sourceforge) failed: 
Permission denied (13)
rsync: opendir "/a/ao/aoo-extensions/1811/2" (in sourceforge) failed: 
Permission denied (13)
rsync: opendir "/a/ao/aoo-extensions/1858" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/1933" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/2038" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/2040" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/2195" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/2290" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/2418" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/252" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/2524/0" (in sourceforge) failed: 
Permission denied (13)
rsync: opendir "/a/ao/aoo-extensions/2542" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/2577" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/2730" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/2991" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/3007" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/3329" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/3475" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/4" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/402/1" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/5" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/5015" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/627" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/673/0" (in sourceforge) failed: Permission 
denied (13)
rsync: opendir "/a/ao/aoo-extensions/847/0" (in sourceforge) failed: Permission 
denied (13)

 1. http://www.debian.org/
 2. http://qa.debian.org/
 3. 
http://anonscm.debian.org/viewvc/qa/trunk/data/watch/update-sf-list?view=markup

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Re: cpuid and other packages needs updates (maintainer mia?)

[Paul Wise]

On Fri, Mar 23, 2012 at 5:37 AM, Touko Korpela wrote:

> Cpuid hasn't updated in more than five years. Bugs aren't answered.  Also 
> other packages by this
> maintainer (Aurélien GÉRÔME) haven't seen updates for many years.

According to the MIA db, his last known mail was in Debian was Dec 2010:

http://lists.debian.org/debian-powerpc/2010/12/msg00103.html

CCing the MIA team as per devref 7.4:

http://www.debian.org/doc/manuals/developers-reference/beyond-pkging.html#mia-qa

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6FMV+ZbGrPYQvgYWOshsHoBs+is=6mp9lyv43ero+x...@mail.gmail.com

Bug#667593: debcheck: check for obsolete transitional packages

[Paul Wise]

Package: qa.debian.org
Severity: wishlist
User: qa.debian@packages.debian.org
Usertags: debcheck

It would be good if debcheck could check for obsolete transitional
packages so that maintainers can know that it is time to remove them.

The default time period should probably encourage the removal of
transitional packages that were introduced in oldstable after oldstable
is moved to archive.debian.org.

Debian doesn't support upgrades from oldstable to oldstable+2 so maybe
debcheck should encourage the removal of transitional packages that were
introduced in stable after it is renamed to oldstable.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Re: Bug#668051: RM: aafigure -- RoQA; orphaned, unused

[Paul Wise]

On Sat, Apr 14, 2012 at 2:16 AM, Clint Adams wrote:
> On Fri, Apr 13, 2012 at 08:08:13PM +0200, Jakub Wilk wrote:
>> Thanks. This will teach me to never orphan packages, but pretend
>> that I'm maintaining them instead.
>
> I hate learning that lesson.

Likewise. Such removals make me want to quit Debian just a little bit
more and maintain packages just a little bit less.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caktje6es1ujiv9xonr0rjcvchfn+d0mffg4ykxrk_evqojx...@mail.gmail.com

Re: Link dead

[Paul Wise]

On Sat, Apr 21, 2012 at 9:41 AM, Andreas Kohlbach wrote:

> on http://qa.debian.org/developer.php?packages=aircrack-ng the link to
> http://cdn.debian.net/debian/pool/main/a/aircrack-ng/ (when clicking at
> "pool") is dead.

I guess this is expected since it isn't in any supported release.

> AFAIK aircrack-ng was kicked from most Debian versions but sid.

It will be back soonish btw:

http://trac.aircrack-ng.org/ticket/953

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6HcYM-WMOu+TSvz5=me-5u2hjyqaofejnu2tjp45fo...@mail.gmail.com

Re: (semi) automatic check for broken links in package descriptions

[Paul Wise]

On Thu, Apr 26, 2012 at 4:42 AM, Simon Kainz wrote:

> after getting frustrated by broken links in some package descriptions, i
> hacked up a script to check for broken links in the packages descriptions.
>
> (see http://simon.familiekainz.at/dropbox/errs.html, based on wheezy/amd64)
> for an example. Is this worth investing some work into it? I'd gladly do,
> and (mass)file some bugs and imrove the script,  if this is of some interest
> for QA/Debian and not being done already.

That sounds like a useful project to add to qa.d.o and the PTS, even
more so if it could detect parked domains or other spammy stuff.

Can you describe how it works? Does it check only the Homepage fields
or also links in the Description and Vcs-* fields?

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caktje6fz+pq6528vu06k2y6hn7rfycngrjdmed7xxzeo3b5...@mail.gmail.com

Re: (semi) automatic check for broken links in package descriptions

[Paul Wise]

On Thu, Apr 26, 2012 at 2:17 PM, Simon Kainz wrote:

> Well, currently i only check the "Homepage" fields. I thought about the
> other links as well, but processing the Homepage entries seemed to me a
> first reasonable step. Processing the other URLs is surely doable.

Ok.

> I think I will restructure my current scripts and make the whole thing
> more modular, to make it easy to add more locations to search for urls.

Sounds good.

> Also I need to process source packages as well, which I currently don't.

Hmm, which parts of the source package would you process?

> How would one incorporate the found data into PTS/qa.d.o website/...? Is
> there a documented/proper way? Or should I just do this on my own and
> PTS would link against my data?

Check the qa.d.o code from SVN and figure out a way to integrate your code.

svn://svn.debian.org/svn/qa/trunk

If you want to run this on your own, that works too.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caktje6ewcrmkeqystc+flrmzki2+xatnmgz5cuqpydnu74o...@mail.gmail.com

Re: (semi) automatic check for broken links in package descriptions

[Paul Wise]

On Thu, Apr 26, 2012 at 3:54 PM, Simon Kainz wrote:

> Some more detail: Currently it is a mix of bash scripts, awk, and wget
> --spider to check if i get something else than 200 OK bakc from the
> server. I process /var/lib/apt/lists/... but i think i should use
> grep-aptavail to process the fresh package files from some mirror.

qa.d.o has local mirrors on the filesystem at:

/srv/mirrors/debian{,-backports,-security}

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caktje6etqi9qnrdzahkj_vdxrifd8_urwcz_uuygl+s2zq4...@mail.gmail.com

Bug#672587: DDPO: versions not updated since several days

[Paul Wise]

On Fri, May 18, 2012 at 2:10 PM, Bart Martens wrote:

> So DDPO looks good for now.  But the problem is not solved.

Based on this file it looks like the trigger is meant to come from
stabile.debian.org, so I guess we should contact DSA about this.

svn://svn.debian.org/svn/qa/trunk/home/.ssh/authorized_keys

-- 
bye,
pabs

http://wiki.debian.org/PaulWise



--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6HZ4-RZrXoZXQYHOEEKjexD=gaytffdnoqeg9gan9p...@mail.gmail.com

Re: Keeping a record of programming language in upstream metadata

[Paul Wise]

On Thu, May 24, 2012 at 3:59 PM, Andreas Tille wrote:

> What do you think?

I think the implemented-in::* debtags should suffice and already
exist. I guess it is hard for people to remember to debtag their
packages, hopefully the PTS links to the debtags site will help. If
you want that to be determined automatically, probably reviving DACA
is the way to go since ohcount determines which languages are used by
a source package:

http://qa.debian.org/daca/ohcount/

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caktje6ejsku0_pnog_y42kpej98hshh6fuyffbxpxwzes52...@mail.gmail.com

Re: Maintainer responsible for or only doing maintenance?

[Paul Wise]

On Sat, Jun 2, 2012 at 1:33 AM, Jonas Smedegaard wrote:

> Today I find the Maintainer field a joke.

Both the Maintainer and Uploaders fields are less than useful for a
number of reasons:

They are tied to the source package, this is bad because people's
commitment to and responsiblity for packages changes over time
independent of source package uploads.

They are not sufficient to represent reality. While we have some
definition in, there are many different styles of maintainership and
different levels of commitment.

I would like to see Debian get rid of the Maintainer and Uploaders
fields and instead implement something like DEP-2 where we have a list
of people, what they are willing to work on and the things they are
willing to do.

For example, as a Debian member with upload privelidges who is part of
the games team I could specify that I am willing to fix RC bugs in all
packages with Section: games, sponsor updates for packages in Section:
games, sponsor new uploads when the meet QA criteria X, am upstream
for chromium-bsu and am willing to deal with bugs filed against iotop.

People in the security team might say they are willing to fix bugs
tagged security on any package in the archive, except for web browser
foo.

In this way we will get a much more realistic picture of the
commitment of the Debian community to the software that we are
shipping. Registering this level of detail might not be something
individuals are willing to do though.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6HHnndBAULd-zuUk-C=q=shvvtf_2ergej1yffikxz...@mail.gmail.com

Re: DUCK - the Debian Url Checker

[Paul Wise]

On Wed, Jun 6, 2012 at 9:18 PM, Simon Kainz wrote:

> as I had some problems in the past finding upstream sources and
> homepages, I hacked up some scripts to monitor and display the results
> of the Upstream Homepage entries in the package control files.
>
> Please take a look at http://debian.tugraz.at/duck/

Great! In addition to the other comments made:

Could you add some machine-readable results (in XML/YAML/JSON/etc) for
the PTS/DDPO to consume?

Would you like to host it on a debian.net domain instead?

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6FTUUa31pR+Jx+YTu0ifcMctjCUuts-Nh=j91djphk...@mail.gmail.com

Re: DUCK - the Debian Url Checker

[Paul Wise]

On Thu, Jun 7, 2012 at 1:03 PM, Simon Kainz wrote:

> Yes, certainly. I took a look at http://wiki.debian.org/DebianDotNet, but as
> I am not in the Debian keyring, who is there to ask for?

Any Debian member can add a domain, including myself. Which domain
would you like me to register and what should I point it at?
duck.debian.net is taken already.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6EB6zvb9OvuW_f3M3wwden6fMMNv5PE=q8ggw_srdh...@mail.gmail.com

Re: DUCK - the Debian Url Checker

[Paul Wise]

On Thu, Jun 7, 2012 at 3:53 PM, Ricardo Mones wrote:

>  Mmm, not taken, just a similar one, from what I can see:
>
> $ ldapsearch -x dnsZoneEntry=duck*|grep dns
> # filter: dnsZoneEntry=duck*
> dnsZoneEntry: duckcorp IN A 193.200.42.177
> dnsZoneEntry: duckcorp IN MX 10 mx.duckcorp.org.
> dnsZoneEntry: duckcorp IN MX 20 mx0.hivane.net.
> dnsZoneEntry: duckcorp IN MX 20 mx2.hivane.net.

Hmm, when I loaded it in my browser I thought it redirected to
people.d.o/~madduck, I guess I put in the wrong URL.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6GADB56vqGUpxFfRAPL8qoK1y=dsd8hpxsfnufvp7e...@mail.gmail.com

Re: DUCK - the Debian Url Checker

[Paul Wise]

On Fri, Jun 8, 2012 at 3:32 PM, Simon Kainz wrote:

> as madduck freed duck.debian.net, please point duck.debian.net to
> 129.27.3.93.

Done in LDAP, will be live once it percolates through Debian's infrastructure.

> I'll also add my page to http://wiki.debian.org/DebianNetDomains - I
> already have a wiki account, so i'll also create a personal page.

Cool.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise
http://bonedaddy.net/pabs3/


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6E9Cs7VzfiNdA4XC9A5jgNDETdoTLT9mST+=a_su8z...@mail.gmail.com

Re: Talk: "Debian QA: an entrance gate to Debian project"

[Paul Wise]

On Sun, Jun 17, 2012 at 1:10 AM, Mònica Ramírez wrote:

> Debian Day organizer contacted me to give a talk. Ana suggested me to
> talk about Debian QA and I added "Debian QA, una puerta de entrada a
> Debian" (in English "Debian QA: an entrance gate to Debian project").

Excellent idea!

> But, as I think that 2 (or more) brains think more than 1, I'd like to
> know if you can add some more.

* Work on central QA infrastructure (DDPO/PTS/etc)
* Work on more automated pre-upload and post-upload checks

As an example of the latter, there is a researcher working on a
project called clonewise, which aims to automatically detect embedded
code copies across the Debian archives. I'm hoping this will help the
security team with their work.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caktje6gw8veyact2vwv+01qg3nvw_+6ateg-j4ea+2sbkz0...@mail.gmail.com

Re: Talk: "Debian QA: an entrance gate to Debian project"

[Paul Wise]

On Sun, Jun 17, 2012 at 1:10 AM, Mònica Ramírez wrote:

> Debian Day organizer contacted me to give a talk. Ana suggested me to
> talk about Debian QA and I added "Debian QA, una puerta de entrada a
> Debian" (in English "Debian QA: an entrance gate to Debian project").
>
> The main idea is to give tasks to do for non-dd newbies related to
> Debian QA. I made the following list:

I note that no-one has yet registered a QA BoF, would you like to do that?

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6ETMMyMEXBrPub-UN7KCt0Um0As0q4_ppL=ovs0e+n...@mail.gmail.com

Re: UDD migration to ullmann.debian.org

[Paul Wise]

On Wed, Jun 27, 2012 at 3:33 PM, Stephen Gran wrote:

> I see the advantage of having a udd replica set somewhere, if
> latency and read performance on ullmann is problematic.
...
> postgres has native replication support.  I don't see a need to reinvent
> the wheel here, do you?

For some reason I thought the plan was to split the import host from
the query host(s) and use postgres replication to migrate data from
the import host onto alioth and any other machines using UDD. Am I
misremembering or is that a bad plan for some reason?

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6F-bpCEwYjsw5BB2rORPxV8ob+z_Afiww0+j1271=h...@mail.gmail.com

Re: Question about PTS

[Paul Wise]

On Mon, Aug 20, 2012 at 4:59 PM, Lucas Nussbaum wrote:

>> Some time ago PTS checked http://mentors.debian.net/ for new source packages
>> which were waiting for a sponsor. If new version of source package available
>> an appropriate item was added in todo section on package page.

Nothing changed with that.

>> But now there is no such item. What happened?

Sounds like a bug, which package?

The PTS only looks at the unstable suite of mentors, I have a
half-completed patch to expand that to all the suites though.

> Indeed. Does mentors.debian.net provide a dump of all relevant info,
> that we could easily import in UDD?

mentors has the normal Sources files one would expect in any apt repo,
for these suites:

oldstable stable unstable experimental oldstable-backports
oldstable-backports-sloppy stable-backports oldstable-security
stable-security testing-security oldstable-proposed-updates
stable-proposed-updates testing-proposed-updates UNRELEASED

With apt sources.list lines like this:

deb-src http://mentors.debian.net/debian unstable main contrib non-free

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6FesSAKuLX81oW=r6cw4mhdg368xvdvv+bb2cqc4rd...@mail.gmail.com

Bug#685327: qa.debian.org: report packager on package migration fail

[Paul Wise]

On Tue, Aug 21, 2012 at 2:24 AM, Ritesh Raj Sarraf wrote:

> When a package is uploaded to unstable, after the 10 day window it
> automatically migrates to testing.
>
> If there are issues (which could be bug reports, or unsatisfied
> packages, or policy violations), the package does not migrate. It would
> be helpful that under such scenarios, the packager is sent an email
> about the migration failure.

I would think this is something for the release team's scripts. I
asked about it on the IRC channel of the release team and was told
that you should just run this in crontab `grep-excuses 'Ritesh Raj
Sarraf'`. I guess this bug should just be closed.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caktje6eu5-j1v2ky_iztfka2vpmitc9ff9d_banhbiao0u3...@mail.gmail.com

Bug#686324: qa.debian.org: DDPO shows Paul Slootman when I ask for Paul Wise

[Paul Wise]

Package: qa.debian.org
Severity: normal
User: qa.debian@packages.debian.org
Usertags: ddpo

This page should show my packages:

http://qa.debian.org/developer.php?login=Paul+Wise

Instead it shows the ones for another Paul:

Packages overview for Paul Slootman
Maintainer: Paul Slootman  

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#686326: PTS: mentors.d.n integration doesn't use suites other than unstable

[Paul Wise]

Package: qa.debian.org
Severity: normal
User: qa.debian@packages.debian.org
Usertags: pts

It is possible to upload packages for any Debian suite to
mentors.debian.net and the mentors site will accept them and list the
source packages into the appropriate Sources file for the suite.
Unfortunately the PTS has does not look at suites other than unstable so
if someone uploads a package to experimental or squeeze-backports then
the mentors to-do item will not be shown in the PTS. I have attached a
partial patch for this, but I need help with the XSL parts.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise
Index: xsl/pts-issues.xsl
===
--- xsl/pts-issues.xsl	(revision 2833)
+++ xsl/pts-issues.xsl	(working copy)
@@ -69,7 +69,7 @@
 	http://mentors.debian.net";>mentors.debian.net has
 	http://mentors.debian.net/package/{$escaped-package}";>version
 	   of this package, you
-	should consider sponsoring its upload.
+	should consider sponsoring their upload.
   
 
   
Index: bin/filter_mentors.pl
===
--- bin/filter_mentors.pl	(revision 2833)
+++ bin/filter_mentors.pl	(working copy)
@@ -113,14 +113,15 @@
 	print STDERR "$0: warning: mentors packages index appears empty, continuing without\n";
 }
 
-my %unstable;
+my %suite;
+my $dist = $ARGV[0];
 
 foreach my $component ( "main", "contrib", "non-free" )
 {
 	my $package;
 	my $version;
 
-	open INPUT, ")
 	{
 		chomp;
@@ -130,9 +131,9 @@
 
 		if( /^$/ )
 		{
-			$unstable{$package} = $version
-if( ! defined $unstable{$package}
-or Dpkg::Version::version_compare( $unstable{$package}, $version ) < 0 );
+			$suite{$package} = $version
+if( ! defined $suite{$package}
+or Dpkg::Version::version_compare( $suite{$package}, $version ) < 0 );
 
 			$package = undef;
 			$version = undef;
@@ -153,11 +154,11 @@
 	return if( defined $seen{$package}{$version} );
 	$seen{$package}{$version} = 1;
 
-	return if( defined $unstable{$package} and $unstable{$package} eq $version );
+	return if( defined $suite{$package} and $suite{$package} eq $version );
 
-	return if( defined $unstable{$package}
+	return if( defined $suite{$package}
 		and $version !~ /~bpo\d+\+\d+$/
-		and Dpkg::Version::version_compare( $unstable{$package}, $version ) > 0 );
+		and Dpkg::Version::version_compare( $suite{$package}, $version ) > 0 );
 
 	return if( ! defined $mentorsneedssponsor{$package} and $keys_mentorsneedssponsor > 0 );
 
@@ -173,8 +174,8 @@
 	my $version;
 	my $block = "";
 
-	open INPUT, "Sources-mentors_${component}_new" or die;
+	open INPUT, "Sources-mentors-$dist\_${component}_new" or die;
 	while()
 	{
 		chomp;
Index: bin/update_incoming.sh
===
--- bin/update_incoming.sh	(revision 2833)
+++ bin/update_incoming.sh	(working copy)
@@ -10,11 +10,17 @@
 security="http://security.debian.org";
 backports="http://backports.debian.org/debian-backports/";
 piuparts="http://piuparts.debian.org";
+mentors="http://mentors.debian.net/debian";
 
 official_distros="oldstable stable testing unstable experimental"
 pu_distros="oldstable-proposed-updates stable-updates stable-proposed-updates testing-proposed-updates"
 security_distros="oldstable stable testing"
 backports_distros="oldstable-backports oldstable-backports-sloppy stable-backports"
+mentors_distros="oldstable stable unstable experimental
+oldstable-backports oldstable-backports-sloppy stable-backports
+oldstable-security stable-security testing-security
+oldstable-proposed-updates stable-proposed-updates testing-proposed-updates 
+UNRELEASED"
 
 umask 002
 set -e
@@ -77,6 +83,12 @@
   $* > "$dest" || (echo "Failure while executing $* . Continuing ..." ; cp "$dest.bak" "$dest")
 }
 
+nice_mv() {
+  if [ -f "$1" ] ; then
+mv -f "$1" "$2"
+  fi
+}
+
 # Download all Sources.gz
 for comp in main contrib non-free
 do
@@ -92,8 +104,12 @@
   get $backports/dists/$dist/$comp/source/Sources.gz \
 	Sources-${dist}_$comp.gz
 done
-get http://mentors.debian.net/debian/dists/unstable/$comp/source/Sources.gz \
-Sources-mentors_$comp.gz
+for dist in $mentors_distros ; do
+  # Ignore errors since mentors currently only generates Sources files for
+  # suites that some packages use
+  get $mentors/dists/$dist/$comp/source/Sources.gz \
+Sources-mentors-${dist}_$comp.gz > /dev/null
+done
 done
 
 # Download update_excuses.html
@@ -193,9 +209,11 @@
 done
 
 # filter out some packages from Sources-mentors_*
-../bin/filter_mentors.pl
-mv Sources-mentors_main_new Sources-mentors_main
-mv Sources-mentors_contrib_new Sources-mentors_contrib
-mv Sources-mentors_non-free_new Sources-mentors_non-free
+for dist in $mentors_distros ; do
+../bin/filter_mentors.pl ${dist}
+nice_mv Sources-mentors-${dist}_main_new Sources-mentors-${dist}_main
+nice_mv Sources-mentors-${dist}_contrib_new Sources-mentors-

Re: [proposal] change color for version number if upstream uses github and just check master

[Paul Wise]

On Sat, Sep 15, 2012 at 5:03 AM, Hideki Yamane wrote:

>  It has watch results and show version number with pink color if upstream
>  released newer version than Debian package. However, if upstream uses
>  github and sometimes watch file is check just its master branch in git
>  (without enough thought).
>
>  master in git is "always" newer than the package in Debian repository.
>  So, I suggest you to change its color to other if package watches master
>  branch.

It is up to the maintainer to put the right URLs and regexes in
debian/watch. If they don't want master they should be more specific
with their regex or use the github tags URL.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caktje6gzvuye9akr7zmypjx1x755+q1tnka4ezwhx_crlay...@mail.gmail.com

[udd] [PATCH] Fix references to old Ubuntu releases

[Paul Wise]

---
 web/bugs.cgi|2 +-
 web/cgi-bin/attic/sources_in_ubuntu_but_not_in_debian_by_popcon.cgi |2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/web/bugs.cgi b/web/bugs.cgi
index c136b3d..82097b7 100755
--- a/web/bugs.cgi
+++ b/web/bugs.cgi
@@ -39,7 +39,7 @@ FILTERS = [
  ['outdatedwheezy', 'outdated binaries in wheezy', "bugs.source in (select 
distinct p1.source from packages_summary p1, packages_summary p2 where 
p1.source = p2.source and p1.release='wheezy' and p2.release='wheezy' and 
p1.source_version != p2.source_version)"],
  ['outdatedsid', 'outdated binaries in sid', "bugs.source in (select distinct 
p1.source from packages_summary p1, packages_summary p2 where p1.source = 
p2.source and p1.release='sid' and p2.release='sid' and p1.source_version != 
p2.source_version)"],
  ['needmig', 'different versions in wheezy and sid', "bugs.source in (select 
s1.source from sources s1, sources s2 where s1.source = s2.source and 
s1.release = 'wheezy' and s2.release='sid' and s1.version != s2.version)"],
- ['newerubuntu', 'newer in Ubuntu than in sid', "bugs.source in (select 
s1.source from sources_uniq s1, ubuntu_sources s2 where s1.source = s2.source 
and s1.release = 'sid' and s2.release='precise' and s1.version < s2.version)"],
+ ['newerubuntu', 'newer in Ubuntu than in sid', "bugs.source in (select 
s1.source from sources_uniq s1, ubuntu_sources s2 where s1.source = s2.source 
and s1.release = 'sid' and s2.release='quantal' and s1.version < s2.version)"],
  ['rtwheezy-will-remove', 'RT tag for wheezy: will-remove', "id in (select id 
from bugs_usertags where email='release.debian@packages.debian.org' and 
tag='wheezy-will-remove')"],
  ['rtwheezy-can-defer', 'RT tag for wheezy: can-defer', "id in (select id from 
bugs_usertags where email='release.debian@packages.debian.org' and 
tag='wheezy-can-defer')"],
  ['rtwheezy-is-blocker', 'RT tag for wheezy: is-blocker', "id in (select id 
from bugs_usertags where email='release.debian@packages.debian.org' and 
tag='wheezy-is-blocker')"],
diff --git 
a/web/cgi-bin/attic/sources_in_ubuntu_but_not_in_debian_by_popcon.cgi 
b/web/cgi-bin/attic/sources_in_ubuntu_but_not_in_debian_by_popcon.cgi
index c04f948..4d00ca6 100755
--- a/web/cgi-bin/attic/sources_in_ubuntu_but_not_in_debian_by_popcon.cgi
+++ b/web/cgi-bin/attic/sources_in_ubuntu_but_not_in_debian_by_popcon.cgi
@@ -10,7 +10,7 @@ my $dbh = 
DBI->connect("dbi:Pg:dbname=udd;port=5452;host=localhost", "guest") or
 my $sth = $dbh->prepare(

Re: Bug#685039: developers-reference: please document what is needed to reintroduce a package

[Paul Wise]

On Sun, 2012-09-16 at 19:53 +0800, Paul Wise wrote:

> My patch does not seem to have been committed to the SVN repository,
> could someone do that please?

Apparently I need an ack on my patch to devref about the procedures
needed when re-introducing packages. I would appreciate it if someone
from the debian-qa list (CCed) could take a look at the patch and
suggest if the patch needs to be changed or is suitable for committing.

http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=20;filename=reintroducing-packages.patch;att=1;bug=685039

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Re: Bug#685039: developers-reference: please document what is needed to reintroduce a package

[Paul Wise]

On Sun, 2012-09-16 at 13:28 +, Bart Martens wrote:

> I'm looking at this now.  I agree with most of your patch.  I'm having doubts
> on this paragraph :
...
> I suggest to replace the paragraph quoted above by these two paragraphs :

Done in the attached patch, thanks.

Based on feedback from IRC I also changed the ftp-master removals link
to http://ftp-master.debian.org/#removed since the page I was linking to
was about pending removals instead of completed ones.

> Other than that, I read good info in your patch, so I think it's a good
> addition.

Thanks for the ack!

-- 
bye,
pabs

http://wiki.debian.org/PaulWise
Index: common.ent
===
--- common.ent	(revision 9361)
+++ common.ent	(working copy)
@@ -28,6 +28,7 @@
 
 
 
+
 
 
 
Index: pkgs.dbk
===
--- pkgs.dbk	(revision 9361)
+++ pkgs.dbk	(working copy)
@@ -1238,7 +1238,7 @@
 
 
 
-Moving, removing, renaming, adopting, and orphaning packages
+Moving, removing, reintroducing, renaming, adopting, and orphaning packages
 
 Some archive manipulation operations are not automated in the Debian upload
 process.  These procedures should be manually followed by maintainers.  This
@@ -1385,6 +1385,51 @@
 
 
 
+
+Reintroducing packages
+
+Packages are often removed due to release-critical bugs, absent maintainers,
+too few users or poor quality in general. There are some things you should be
+aware of when reintroducing removed packages.
+
+
+You should check why the package was removed in the first place. This
+information can be found in the removal item in the news section of the PTS
+page for the package or by browsing the log of
+http://&ftp-master-host;/#removed";>removals.
+The removal bug will tell you why the package was removed and will give some
+indication of what you will need to work on in order to reintroduce the package.
+It may indicate that the best way forward is to switch to some other piece of
+software instead of reintroducing the package.
+
+
+It may be appropriate to contact the former maintainers to find out if
+they are working on reintroducing the package, interested in co-maintaining
+the package or interested in sponsoring the package if needed.
+You should do all the things required before introducing new packages
+().
+
+
+You should base your work on the latest packaging available that is suitable.
+That might be the latest version from unstable, which will
+still be present in the snapshot archive.
+
+
+The version control system used by the previous maintainer might contain useful
+changes, so it might be a good idea to have a look there.  Check if the control
+file of the previous package contained any headers linking to the version
+control system for the package and if it still exists.
+
+
+Package removals from unstable (not testing, stable or oldstable) trigger the
+closing of all bugs related to the package. You should look through all the
+closed bugs (including archived bugs) and unarchive and reopen any that were
+closed in a version ending in +rm and still apply. Any that
+no longer apply should be marked as fixed in the correct version if that is
+known.
+
+
+
 
 Replacing or renaming packages
 


signature.asc
Description: This is a digitally signed message part

Re: Bug#685039: developers-reference: please document what is needed to reintroduce a package

[Paul Wise]

On Mon, 2012-09-17 at 08:51 +0800, Paul Wise wrote:

> Done in the attached patch, thanks.

I didn't see the comments from Charles Plessy as I wasn't subscribed to
the bug and he did not CC me. I've attached a new version adopting his
suggestions.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise
Index: common.ent
===
--- common.ent	(revision 9361)
+++ common.ent	(working copy)
@@ -28,6 +28,7 @@
 
 
 
+
 
 
 
Index: pkgs.dbk
===
--- pkgs.dbk	(revision 9361)
+++ pkgs.dbk	(working copy)
@@ -1238,7 +1238,7 @@
 
 
 
-Moving, removing, renaming, adopting, and orphaning packages
+Moving, removing, reintroducing, renaming, adopting, and orphaning packages
 
 Some archive manipulation operations are not automated in the Debian upload
 process.  These procedures should be manually followed by maintainers.  This
@@ -1486,6 +1486,53 @@
 
 
 
+
+Reintroducing packages
+
+Packages are often removed due to release-critical bugs, absent maintainers,
+too few users or poor quality in general. There are some things you should be
+aware of when reintroducing removed packages.
+
+
+You should check why the package was removed in the first place. This
+information can be found in the removal item in the news section of the PTS
+page for the package or by browsing the log of
+http://&ftp-master-host;/#removed";>removals.
+The removal bug will tell you why the package was removed and will give some
+indication of what you will need to work on in order to reintroduce the package.
+It may indicate that the best way forward is to switch to some other piece of
+software instead of reintroducing the package.
+
+
+It may be appropriate to contact the former maintainers to find out if
+they are working on reintroducing the package, interested in co-maintaining
+the package or interested in sponsoring the package if needed.
+
+
+You should do all the things required before introducing new packages
+().
+
+
+You should base your work on the latest packaging available that is suitable.
+That might be the latest version from unstable, which will
+still be present in the snapshot archive.
+
+
+The version control system used by the previous maintainer might contain useful
+changes, so it might be a good idea to have a look there.  Check if the control
+file of the previous package contained any headers linking to the version
+control system for the package and if it still exists.
+
+
+Package removals from unstable (not testing, stable or oldstable) trigger the
+closing of all bugs related to the package. You should look through all the
+closed bugs (including archived bugs) and unarchive and reopen any that were
+closed in a version ending in +rm and still apply. Any that
+no longer apply should be marked as fixed in the correct version if that is
+known.
+
+
+
 
 
 


signature.asc
Description: This is a digitally signed message part

collab-qa vs qa alioth groups?

[Paul Wise]

Anyone know why the collab-qa and qa alioth groups are separate?

Would it be a good idea to merge them?

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caktje6hssm+9kxpfg2k_50tztcqtjkyz10nkpkie5wgokzx...@mail.gmail.com

Re: collab-qa vs qa alioth groups?

[Paul Wise]

On Wed, Oct 10, 2012 at 1:09 PM, Lucas Nussbaum wrote:

> The qa group maps to the Unix qa group. So you can't add non-DDs to qa.
> (or at least it was the case when collab-qa was created).

Hmm, I wouldn't have thought group membership would have ever been
synced from alioth to other Debian hosts. It doesn't seem to be the
case now anyway.

pabs@chianamo ~ $ ssh master.debian.org getent group popcon ; ssh
alioth.debian.org getent group popcon
popcon:x:1213:ballombe,pere
popcon:x:11213:bubulle,pere,pootle-guest,ballombe,apenwarr

webwml is another example of a group that is different between alioth
and other Debian hosts.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6GqGFyXHwLu_Sm5Y0=mqeoa42e3kebdsf_w8gt4izr...@mail.gmail.com

Bug#690414: PTS: screenshots related improvements

[Paul Wise]

Package: qa.debian.org
Severity: normal
User: qa.debian@packages.debian.org
Usertags: pts

For packages that have screenshots on screenshots.d.n, the PTS should
link to them so maintainers know about them and can review them.

It would also be good to have a todo item for packages that need a
screenshot, using various criteria such as debtags or dependencies.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Re: Putting cross-build status info somewhere useful

[Paul Wise]

On Thu, Nov 1, 2012 at 8:46 AM, Wookey wrote:

> I've been running a cross-buildd for a while now (if somewhat
> sporadically), which builds a subset of packages using standard debian
> (emdebian.org) toolchains in standard sbuild chroots, to determine
> which packages are currently cross-buildable using multiarch mechanisms.

Excellent.

What would it take to expand that to the full archive built all the time?

> The current results are generated by a (fairly dim) perl script which
> parses build-logs. It would be easy to make it spit out summaries in a
> different form: e.g. a testfile list of:
> package, version, arch, status

I would suggest that the file should be space separated (drop the
commas) and after the status should come the URL to a build log for
the PTS to link to.

> And apprently something like this (along with a reader) is what is
> needed to put the info in UDD (from whence it could be consumed by
> other software).

If you want to implement this yourself, tips below, otherwise, please
provide the summary file you mentioned above and report a bug against
qa.debian.org about it.

The PTS is not UDD based so you need to implement separate
downloading/parsing for both right now.

I don't know much about UDD but for the PTS check out the code:

svn://svn.debian.org/svn/qa/trunk/pts/www

Add some commands to the bin/update_incoming.sh script so that your
summary file gets downloaded into the incoming directory.

Edit the bin/other_to_xml.py script to load the summary file. The
lintian summary file is similar so I would suggest looking at how this
is done and adapting it.

Edit the xsl/pts.xsl template file to add a new issue-crossbuild
template to the todo-list template.

You will also want to add a link to the crossbuild status in the links
box at the right, probably in the buildd: item after the ports link,
so something like "buildd: logs, exp, ports, cross".

As far as testing it goes, you probably want to do that by logging
into qa.d.o and copying the existing data to your home directory. You
will want to look at the bin/do_all.sh script to find out what to run.
bin/generate_html.sh is the script that generates the HTML and takes a
list of package names on stdin, which is handy for testing.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/caktje6epiav_vag6jq9oybbz--03gvtu_f0owp3rudnicmz...@mail.gmail.com

Re: Putting cross-build status info somewhere useful

[Paul Wise]

On Thu, 2012-11-01 at 19:34 +, Wookey wrote:

> A machine set up to do the builds. Ubuntu are planning to set this up
> for all of main over next couple of months (in the form of Colin
> Watson, who groks buildd (current set-up uses hacked rebuildd and is
> not entirely satisfactory or reliable). It should be possible to set up nearly
> identical config for Ubuntu and Debian if we have somewhere to do it.
> 
> Do we have a box that can just run builds all the time?

I expect with DSA's new VM stuff we can have a VM for this.

> Thanks for the comprehensive response. I'll look into that.

No probs, hope it helps.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part