[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#540132: marked as done ([UDD] has some strange information in the upload_history table)

Your message dated Thu, 5 Aug 2010 17:49:31 -0400
with message-id <20100805214931.GA15189@xanadu.blop.info>
and subject line Re: Bug#540132: [UDD] has some strange information in the upload_history table
has caused the Debian Bug report #540132,
regarding [UDD] has some strange information in the upload_history table
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
540132: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540132
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: qa.debian.org
Severity: normal
User: qa.debian.org@packages.debian.org
Usertags: udd

23:08 < Ryan52> lucas: I was trying to find a list of all the people who have sponsored my uploads, and noticed that UDD's upload_history table has some strange data, could you please take a look at (or tell me w
ho to complain to) the output of: SELECT * FROM upload_history WHERE changed_by_name LIKE 'Ryan Niebur' AND signed_by_name = ''
23:09 < Ryan52> ;
23:10 < Ryan52> lucas: oh, the problem with signed_by_name being empty for libopenid-ruby's upload was that a DM sponsored it. so I guess UDD (or wherever UDD gets this data from) does not take into account the D
M keyring and it should?
23:14 < Ryan52> lucas: hm, and for the crip one, it seems that all uploads signed by phil do that. I'm guessing that because signed_by doesn't include his email address, the (presumably) regexp splitting it into
signed_by_* is parsing it wrong. why it doesn't include his email address, I dunno...
23:26  * Ryan52 wonders if there's a place where bugs about UDD are supposed to be reported...

obviously I've now figured out the answer to the last part :)

-- 
_________________________
Ryan Niebur
ryanryan52@gmail.com

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
On 10/08/09 at 21:56 +0200, Lucas Nussbaum wrote:
> On 09/08/09 at 14:42 -0700, Ryan Niebur wrote:
> > On Sun, Aug 09, 2009 at 09:52:23AM +0100, Filippo Giunchedi wrote:
> > > On Wed, Aug 05, 2009 at 07:41:17PM -0700, Ryan Niebur wrote:
> > > > Package: qa.debian.org
> > > > Severity: normal
> > > > User: qa.debian.org@packages.debian.org
> > > > Usertags: udd
> > > > 
> > > > 23:08 < Ryan52> lucas: I was trying to find a list of all the people who have sponsored my uploads, and noticed that UDD's upload_history table has some strange data, could you please take a look at (or tell me w
> > > > ho to complain to) the output of: SELECT * FROM upload_history WHERE changed_by_name LIKE 'Ryan Niebur' AND signed_by_name = ''
> > > > 23:09 < Ryan52> ;
> > > > 23:10 < Ryan52> lucas: oh, the problem with signed_by_name being empty for libopenid-ruby's upload was that a DM sponsored it. so I guess UDD (or wherever UDD gets this data from) does not take into account the D
> > > > M keyring and it should?
> > > > 23:14 < Ryan52> lucas: hm, and for the crip one, it seems that all uploads signed by phil do that. I'm guessing that because signed_by doesn't include his email address, the (presumably) regexp splitting it into
> > > > signed_by_* is parsing it wrong. why it doesn't include his email address, I dunno...
> > > > 23:26  * Ryan52 wonders if there's a place where bugs about UDD are supposed to be reported...
> > > 
> > > the upload-history data is taken (for now) from
> > > http://qa.debian.org/~filippo/ddc/ and I couldn't find the wrong libopenid-ruby
> > > you were talking about, DM keyring should be accounted for
> > > 
> > 
> > I was talking about the one that that SQL query shows.
> 
> (To clarify: Filippo wrote a parser for debian-devel-changes@, and
> generates a text summary that I import in UDD. That's why it would be
> more helpful to provide more info about the package in question).
> 
> > > $ zgrep -A12 libopenid-ruby * | grep -i signed
> > > debian-devel-changes.200712.gz:Signed-By: Paul van Tilburg <paul@luon.net>
> > > debian-devel-changes.200803.gz:Signed-By: Antonio Terceiro <terceiro@softwarelivre.org>
> > > debian-devel-changes.200807.gz:Signed-By: Antonio Terceiro <terceiro@softwarelivre.org>
> > > debian-devel-changes.200905.gz:Signed-By: Antonio Terceiro <terceiro@softwarelivre.org>
> > > debian-devel-changes.200907.gz:Signed-By: Lucas Nussbaum <lucas@lucas-nussbaum.net>
> > > 
> > > for the other problem you are correct, the first uid for ED1A3933B2CFCDD8
> > > doesn't contain an email:
> > > 
> > > $ gpg --list-keys ED1A3933B2CFCDD8
> > > pub   1024D/B2CFCDD8 2003-01-08
> > > uid                  Philipp Kern
> > > uid                  Philipp Kern <phil@0x539.de>
> > > uid                  Philipp Kern <phil@philkern.de>
> > > uid                  Philipp Kern <pkern@debian.org>
> > > uid                  Philipp Kern <pkern@ubuntu.com>
> > > uid                  Philipp Kern <philipp.kern@fsmi.uni-karlsruhe.de>
> > > 
> > > I'm not sure how to fix this though, I'm relying on gpgv output
> > 
> > well the parsing is clearly broken... the name should be "Philipp
> > Kern" and the email address should be empty.
> 
> The split between name and email is not by the UDD importer using
> email.Utils.parseaddr (Python). Apparently, it doesn't like being asked
> to parse a string without an email.
> 
> The Signed-by columns are mostly provided for convenience. If you really
> want to know who signed an upload, use the key together with
> carnivore_keys to find out.

I've fixed it to do:
Signed_by_name = Signed_by
Signed_by_email empty
in the case of Signed_by not containing an email address

So I consider this bug fixed.
-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |

--- End Message ---
Reply to: