Your message dated Sat, 17 Nov 2012 14:28:49 +0100
with message-id <[email protected]>
and subject line Re: Bug#693163: dak: proper error message for already known
.changes file
has caused the Debian Bug report #693163,
regarding dak: proper error message for already known .changes file
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 [email protected]
immediately.)
--
693163: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693163
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
User: [email protected]
Usertag: dak
>> There was an uncaught exception when processing your upload:
>> Traceback (most recent call last):
[...]
>> File "/srv/ftp-master.debian.org/dak/dak/daklib/archive.py", line 1008, in
>> _install_changes
>> self.transaction.session.flush()
[...]
>> IntegrityError: (IntegrityError) duplicate key value violates unique
>> constraint "known_changes_changesname_key"
>> DETAIL: Key (changesname)=(gnome-themes-standard_3.4.2-2.1_amd64.changes)
>> already exists.
This should give a proper error message instead of a traceback.
Ansgar
--- End Message ---
--- Begin Message ---
Ansgar Burchardt <[email protected]> writes:
>>> There was an uncaught exception when processing your upload:
>>> Traceback (most recent call last):
> [...]
>>> File "/srv/ftp-master.debian.org/dak/dak/daklib/archive.py", line 1008,
>>> in _install_changes
>>> self.transaction.session.flush()
> [...]
>>> IntegrityError: (IntegrityError) duplicate key value violates unique
>>> constraint "known_changes_changesname_key"
>>> DETAIL: Key (changesname)=(gnome-themes-standard_3.4.2-2.1_amd64.changes)
>>> already exists.
>
> This should give a proper error message instead of a traceback.
Fixed in 76bcea909c8a45646123385d82793e8d00ba87b7. It gives now a much
nicer error: "cclive_0.7.10-1_multi.changes is already known."
Ansgar
--- End Message ---