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

Bug#705580: marked as done (qa.debian.org: [UDD] import of long descriptions seems to be broken)

Your message dated Fri, 26 Apr 2013 09:20:29 +0200
with message-id <[🔎] 20130426072029.GB22990@xanadu.blop.info>
and subject line Re: Bug#705580: qa.debian.org: [UDD] import of long descriptions seems to be broken
has caused the Debian Bug report #705580,
regarding qa.debian.org: [UDD] import of long descriptions seems to be broken
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

705580: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705580
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: qa.debian.org
Severity: important


since some days the import of long descriptions for releases 'sid'
and 'experimental' are broken:

udd=> SELECT package, language, distribution, release, component, description, long_description from descriptions where long_description != '' and release in ('sid','experimental');
 package | language | distribution | release | component | description | long_description 
(0 Zeilen)

The import of the descriptions is done by the ddtp importer that is
reading files named Translation-<lang>.bz2 in


I verified that these files are available as usual.  I just learned
about directories Translation-<lang>.diff which are new to me and did
not existed when I worked on the ddtp importer (which is ignoring
these dirs).

I verified that the importer works properly on my test host:

udd=# SELECT language, count(*) from descriptions where long_description != '' and release in ('sid','experimental') group by language order by language;
 language | count 
 ca       |    27
 cs       |  4416
 da       | 11650
 de       | 12517
 en       | 42395
 es       |  2534
 eu       |    40
 fi       |   718
 fr       |  5587
 hr       |    39
 hu       |   253
 it       | 22308
 ja       |  7477
 km       |    24
 ko       |   937
 nl       |   232
 pl       |  5003
 pt       |  3847
 pt_BR    |  4153
 ru       |  3022
 sk       |  2827
 sr       |   346
 sv       |   337
 uk       |  6234
 vi       |    68
 zh_CN    |  1045
 zh_TW    |   174
(27 Zeilen)

So something seems to be broken only on ullmann.d.o but I do not have
any idea what this might be.  Unfortunately I do not feel able to
check this due to a very weak connection to this host.

This problem does exist probably for one week because one of its effects
was reported last Thursday[1] and the cron job that was creating the
broken pages was running on Wed, 2013-04-10.  I vaguely remember that the
broken descriptions in the tasks pages as reported[1] were OK on last
Sunday evening - but I'm not fully sure.  In any case you might expect a
temporary / random problem.

Hope anybody with better access to ullmann.d.o can have a look.

Kind regards


[1] https://lists.debian.org/debian-science/2013/04/msg00045.html

-- System Information:
Debian Release: 6.0.7
Architecture: i386 (i686)

Kernel: Linux 2.6.36-xenU-4814-i386 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message ---
On 20/04/13 at 23:12 +0200, Andreas Tille wrote:
> Hi,
> to provide more info about this:  I noticed today that the descriptions
> were gone again.  I mad a backup of the files mentioned below and also
> the logfile that is written and forced the import again.  Any idea what
> might cause the problem is really welcome.
> Kind regards

Hi Andreas,

I think this was caused by a bug in the new archive gatherer. See
commit 8c9c0f51b469bdc9bcd6d6dd9b06d8e36fb2c023. I think it's fixed now,
but please double-check in a few days and reopen if necessary.


--- End Message ---

Reply to: