On Tue, Oct 11, 2016 at 08:40:13AM +0100, Neil Williams wrote:
> I could file 15 RC bugs against dpkg-cross for the flagrant
> disregard of ALL Debian Policy, if you really want proof of the
> abominations that hide within it. 

file at least one?

> However, cross-config has none of
> those issues, so to allow cross-config to exist in Stretch I want to
> see the removal of the dpkg-cross and libdebian-dpkgcross-perl binary
> packages instead. These should have been removed from Debian before we
> released Lenny, let alone Jessie. Yay for the inertia of cross-building
> in Debian.

the way to get a package removed in Debian is to file a RM bug.

uploading another package replacing it and assuming everybody knows that
the old package is useless and buggy is not the way to go and doesnt

see this bug report for evidence.

> cross-config exists solely to allow the removal of the dpkg-cross and
> libdebian-dpkgcross-perl binaries. Even then, the contents of
> cross-config could end up in other packages just as easily.
then please file a bug for the removal of dpkg-cross.

> > There is a reason why dpkg-cross is not part of jessie.
> > 
> > Wookey, should we add a blocker bug keep it out of jessie?
> Holger: did you mean Stretch?

I ment stretch and *I* never spoke of jessie in this bug report. Helmut
added this confusion.

I explicitly said "dpkg-cross is even part of testing!"

> However, Stretch must not release with the dpkg-cross and
> libdebian-dpkgcross-perl binary packages.

Please file bugs (to get those binary packages removed).

> If the new upload doesn't
> happen by the end of November 2017, then (as agreed at DebConf16), I'll
> have to do it as a final QA upload, leaving only the cross-config
> binary package.

And this now finally made me realize cross-config is coming from the
same source package :)

Anyhow, dpkg-cross is part of testing (Stretch) and according to you it
shouldnt. So please fix this.

And, to repeat myself, indicating that it shouldnt be used, via a public
bug in the BTS against dpkg-cross would be helpful. (Not hiding problems
and all that.)


Attachment: signature.asc
Description: Digital signature

Reply via email to