Re: dependent packages blocked from testing
On Fri, Jul 19, 2013 at 07:53:51AM +0200, Tobias Frost wrote:
> Ltt-controls has not been built on all archs (those out of date messages on the PTS). Seems that there are build deps not available.
> (Take a look at the buildds status page)
It waits for ust to be built on ia64, mips, mipsel, s390, s390x and sparc.
Out of those, ia64 build just fails while mips, mipsel, s390x and sparc
need systemtap-sdt-dev, which does not exist on those arches for at least
quite some time. s390 has "No entry in s390 database" which I have no idea
about.
> Jon Bernard <jbernard@debian.org> schrieb:
>
> >Hello,
> >
> >I'm facing a problem with two packages that are blocked from migrating
> >into
> >testing. I'm having trouble seeing a clear path forward and I wonder
> >if anyone
> >could point me in a better direction.
> >
> >The specific packages are ltt-control[1] and ust[2]. If the source
> >packages
> >only built a single binary package, then apt's arbitrary selection of
> >one to
> >break the dependency chain would work, from what I understand. But in
> >this case
> >each source package builds several binary packages and I do not see a
> >clean way
> >out of this (other than asking the release team to manually move them,
> >but
> >I would prefer to find a proper solution). Is there any advise for
> >this
> >situation? Specifically, how do I get out of this mess cleanly, and
> >what could
> >I have done differently to prevent this from ever happening?
> >
> >[1]: http://release.debian.org/migration/testing.pl?package=ltt-control
> >[2]: http://release.debian.org/migration/testing.pl?package=ust
> >
> >Cheers,
> >
>
--
WBR, wRAR
Reply to: