Your message dated Sat, 17 Nov 2012 13:39:22 +0100
with message-id <[email protected]>
and subject line Re: propup stable -> t-p-u -> unstable broken when some archs 
got removed from testing/unstable meanwhile
has caused the Debian Bug report #296561,
regarding propup stable -> t-p-u -> unstable broken when some archs got removed 
from testing/unstable meanwhile
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.)


-- 
296561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=296561
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Version: N/A; reported 2005-02-23
Severity: normal

xview is not supported on 64 bit architectures, and since I'm subscribed
to the xview pts I'm getting daily notifications since the last security
fix for xview.

Rejected: no source found for xview 3.2p1.4-16woody2 (xview-examples_3.2p1.4-16w
oody2_ia64.deb).
Warning: Propogating upload to testing-proposed-updates
Rejected: no source found for xview 3.2p1.4-16woody2 (xview-clients_3.2p1.4-16wo
ody2_ia64.deb).
Warning: Propogating upload to testing-proposed-updates
Rejected: no source found for xview 3.2p1.4-16woody2 (xviewg_3.2p1.4-16woody2_ia
64.deb).
Warning: Propogating upload to testing-proposed-updates
Rejected: no source found for xview 3.2p1.4-16woody2 (olwm_3.2p1.4-16woody2_ia64
.deb).
Warning: Propogating upload to testing-proposed-updates
Rejected: no source found for xview 3.2p1.4-16woody2 (xviewg-dev_3.2p1.4-16woody
2_ia64.deb).
Warning: Propogating upload to testing-proposed-updates
Rejected: no source found for xview 3.2p1.4-16woody2 (olvwm_4.4.3.2p1.4-16woody2
_ia64.deb).
Warning: Propogating upload to testing-proposed-updates


===

Despite being ACCEPTed, this package failed the database sanity checks
at the time of install.  This should only happen rarely and in
corner-cases (a binary upload of a package which has since been
melanie'd for example), so no code to do the necessary unaccept
actions has been written.  These actions (e.g. bug reopening,
announcement rescinding, etc.) will have to be done by hand.  Also,
the files have been left in the accepted directory; please deal with
them as well.



--- End Message ---
--- Begin Message ---
Currently there is no automatic propogating in dak so this can no longer
happen ;)

Ansgar

--- End Message ---

Reply via email to