Your message dated Mon, 23 Sep 2013 21:42:37 +0100
with message-id <20130923204237.ga10...@riva.ucam.org>
and subject line Re: Bug#723094: dh-python uninstallable on buildds
has caused the Debian Bug report #723094,
regarding dh-python uninstallable on buildds
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 ow...@bugs.debian.org
immediately.)
--
723094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723094
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dh-python
Version: 1.20130913-1
Severity: grave
Justification: renders package unusable
sip4 is now BD-uninstallable everywhere (the experimental upload) due to:
sip4 (= 4.15.2-1) build-depends on one of:
- python3-all-dbg (= 3.3.2-15)
python3-all-dbg (= 3.3.2-15) depends on one of:
- python3 (= 3.3.2-15)
python3 (= 3.3.2-15) depends on one of:
- dh-python (= 1.20130913-1)
dh-python (= 1.20130913-1) depends on missing:
- python3:any (>= 3.2.3-3~)
It looks like the multi-arch changes in the last upload were premature.
--- End Message ---
--- Begin Message ---
On Mon, Sep 16, 2013 at 03:57:08PM +0100, Colin Watson wrote:
> On Mon, Sep 16, 2013 at 07:58:04AM -0400, Scott Kitterman wrote:
> > sip4 is now BD-uninstallable everywhere (the experimental upload) due to:
> >
> > sip4 (= 4.15.2-1) build-depends on one of:
> > - python3-all-dbg (= 3.3.2-15)
> > python3-all-dbg (= 3.3.2-15) depends on one of:
> > - python3 (= 3.3.2-15)
> > python3 (= 3.3.2-15) depends on one of:
> > - dh-python (= 1.20130913-1)
> > dh-python (= 1.20130913-1) depends on missing:
> > - python3:any (>= 3.2.3-3~)
> >
> > It looks like the multi-arch changes in the last upload were premature.
>
> Given that this could have been fixed at any point since wheezy, and
> wasn't, I think it's clear that we need some kind of forcing function to
> get our infrastructure fixed. I've already fixed some related things
> and am willing to spend time on it this week one way or another.
This is fixed now and the buildds are catching up:
http://lists.debian.org/debian-wb-team/2013/09/msg00032.html
https://buildd.debian.org/status/package.php?p=sip4&suite=experimental
--
Colin Watson [cjwat...@debian.org]
--- End Message ---
