Bug#702085: marked as done (UDD: upload_history importer broken since move to new-master)
Your message dated Sat, 15 Jun 2013 20:52:40 +0000
with message-id <[🔎] 20130615205240.GA2735@emyr.net>
and subject line Re: [UDD] Suspected problem of upload_history importer
has caused the Debian Bug report #702085,
regarding UDD: upload_history importer broken since move to new-master
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.)
--
702085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702085
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: UDD: upload_history importer broken since move to new-master
- From: Lucas Nussbaum <lucas@lucas-nussbaum.net>
- Date: Sat, 2 Mar 2013 17:13:30 +0100
- Message-id: <20130302161330.GA18232@xanadu.blop.info>
Package: qa.debian.org
Severity: serious
User: qa.debian.org@packages.debian.org
Usertags: udd
Hi,
The upload history data is generated by parsing the debian-devel-changes
mailing list archives.
The way it used to work is:
- a script on master parses the archives mbox and generates a summarized version
- the summarized version is exported in http://master.debian.org/~lucas/ddc-parser/
- on ullmann, a script downloads those files and import them into the DB
This is broken since the move to the new master, since it doesn't have an httpd
anymore.
A solution that would work for me would be to have a regular (r)sync of
debian-devel-changes archives from master to ullmann.debian.org. That would
also allow to drop the dependency on my user account on master.debian.org.
A service affected by that is the cgi used to generate the "new contributors"
section of the weekly news.
Lucas
--- End Message ---
--- Begin Message ---
Hi,
We suggest the following procedure to route debian-devel-changes@l.d.o emails into udd:
1) As user 'udd' on ullmann.debian.org, please do:
mkdir /srv/udd.debian.org/incoming-mail
echo '/srv/udd.debian.org/incoming-mail/changes' > ~udd/.forward-changes
2) In order to receive new debian-devel-changes emails, please subscribe
udd-changes@ullmann.debian.org to debian-devel-changes@lists.debian.org. Note that
a confirmation email will be saved in /srv/udd.debian.org/incoming-mail/changes and you
will need to reply to it in order for your subscription to be confirmed.
3) In order to capture historical debian-devel-changes emails, please use rsync, once,
to obtain the archive from master.debian.org:/home/debian/lists/debian-devel-changes/ to
your own machine. Then, rsync from your own machine to ullmann:/home/lucas. Finally, as
user 'udd' on ullmann, copy from /home/lucas to /srv/udd.debian.org/incoming-mail/changes.
Additionally, you may wish to subscribe udd-changes@ullmann.debian.org to
debian-changes@lists.debian.org, debian-stable-changes@lists.debian.org and
debian-backport-changes@lists.debian.org; and repeat the capture procedure detailed
in (3) for the corresponding archives.
Thanks,
Debian System Administration Team
--- End Message ---
Reply to: