Re: different .diff.gz for different platforms (armel) prohibiting upload

[Luk Claes]

Holger Levsen wrote:
> Hi,
> 
> On Montag, 28. September 2009, Rene Engelhard wrote:
>> I just said that there are buildd admins/porters who are hard to deal
>> with because they just don't care about build failures not caused by
>> the package to be built and neither with any package else but by
>> buildd/machine/arch issues.
> [...]
>> At which time it'll get even more funny when buildds don't try to
>> build stuff - and yes, even security buildds. You really believe
>> a DSA is possible nowadays without uploading handbuilt binaries? Then
>> you haven't seen reality.
> 
> Well, I think this reality sucks and should be fixed. Uploading manually 
> build 
> security packages is a workaround which is error prone, as could be seen in 
> the last months, where there were several uploads done in wrong build 
> environments.
> 
> If there are really such non-caring buildd admins/porters this should be 
> fixed 
> at the root of the problem and not by using a workaround, which introduces 
> new problems and doesnt touch the root at all.

The real problem IMHO is that we have only very few real porters left.
Some of them apparently think that unless they are contacted directly
there are no issues while many buildd admins are swamped with other work
and don't get to filing bugs for porting issues.

To all people interested, please have a look at the buildd pages [1] and
file bugs where necessary (please don't file duplicates nor file bugs
when fixing the build chroot or setting a dep-wait would suffice).

Cheers

Luk

[1] https://buildd.debian.org/status (click on the architecture you are
interested in and look at the Failed, Build-Attempted and Maybe-Failed
categories)


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: different .diff.gz for different platforms (armel) prohibiting upload

[Holger Levsen]

On Sonntag, 4. Oktober 2009, Julien Cristau wrote:
> > Well, I think this reality sucks and should be fixed.
> Hahaha.  Good luck with that plan :)

I find your lack of faith disturbing.


signature.asc
Description: This is a digitally signed message part.

Re: different .diff.gz for different platforms (armel) prohibiting upload

[Julien Cristau]

On Sun, Oct  4, 2009 at 09:25:44 +0200, Holger Levsen wrote:

> Well, I think this reality sucks and should be fixed.

Hahaha.  Good luck with that plan :)

Cheers,
Julien


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: different .diff.gz for different platforms (armel) prohibiting upload

[Holger Levsen]

Hi,

On Montag, 28. September 2009, Rene Engelhard wrote:
> I just said that there are buildd admins/porters who are hard to deal
> with because they just don't care about build failures not caused by
> the package to be built and neither with any package else but by
> buildd/machine/arch issues.
[...]
> At which time it'll get even more funny when buildds don't try to
> build stuff - and yes, even security buildds. You really believe
> a DSA is possible nowadays without uploading handbuilt binaries? Then
> you haven't seen reality.

Well, I think this reality sucks and should be fixed. Uploading manually build 
security packages is a workaround which is error prone, as could be seen in 
the last months, where there were several uploads done in wrong build 
environments.

If there are really such non-caring buildd admins/porters this should be fixed 
at the root of the problem and not by using a workaround, which introduces 
new problems and doesnt touch the root at all.


regards,
Holger


signature.asc
Description: This is a digitally signed message part.

Re: different .diff.gz for different platforms (armel) prohibiting upload

[Russ Allbery]

Goswin von Brederlow  writes:
> Steffen Moeller  writes:

>> As a sidenote, and to promote the summary on
>> http://wiki.debian.org/buildd a bit, there is a non-free buildd
>> network. This has taken perfect care of my non-free packages so far,
>> but it seems defunct for mips and armel these days.

> Non-free has autobuilders on an opt-in basis. Where legally possible
> maintainers should opt-in and not build packages themself.

Yes, this thread is about a build for armel, for which see Steffen's
comment above.

-- 
Russ Allbery (r...@debian.org)   


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: different .diff.gz for different platforms (armel) prohibiting upload

[Rene Engelhard]

On Mon, Sep 28, 2009 at 09:48:00PM +0800, Holger Levsen wrote:
> Hi,
> 
> On Montag, 28. September 2009, Rene Engelhard wrote:
> > > That said uploading missing binaries yourself is not the rigt way
> > > forward, official build daemons must be able to build it and you should
> > > work with buildd maintainers and porters to get your package built (and
> > > building).
> > If they listened or cared about problems, and not just ignore them, yes...
> 
> Uhm, no.

? What do you disagree with? I didn't say upload of random binaries should
be allowed..

I just said that there are buildd admins/porters who are hard to deal
with because they just don't care about build failures not caused by
the package to be built and neither with any package else but by
buildd/machine/arch issues.

> regards,
>   Holger, looking forward to the day the archive will _only_ accept 
> source-only
>   uploads (or throw away the binaries...)

At which time it'll get even more funny when buildds don't try to
build stuff - and yes, even security buildds. You really believe
a DSA is possible nowadays without uploading handbuilt binaries? Then
you haven't seen reality.

Grüße/Regards,

Rene
-- 
 .''`.  René Engelhard -- Debian GNU/Linux Developer
 : :' : http://www.debian.org | http://people.debian.org/~rene/
 `. `'  r...@debian.org | GnuPG-Key ID: D03E3E70
   `-   Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: different .diff.gz for different platforms (armel) prohibiting upload

[Holger Levsen]

Hi,

On Montag, 28. September 2009, Rene Engelhard wrote:
> > That said uploading missing binaries yourself is not the rigt way
> > forward, official build daemons must be able to build it and you should
> > work with buildd maintainers and porters to get your package built (and
> > building).
> If they listened or cared about problems, and not just ignore them, yes...

Uhm, no.


regards,
Holger, looking forward to the day the archive will _only_ accept 
source-only
uploads (or throw away the binaries...)


signature.asc
Description: This is a digitally signed message part.

Re: different .diff.gz for different platforms (armel) prohibiting upload

[Rene Engelhard]

Hi,

On Sun, Sep 27, 2009 at 10:59:51AM +0200, Raphael Hertzog wrote:
> That said uploading missing binaries yourself is not the rigt way forward,
> official build daemons must be able to build it and you should work with
> buildd maintainers and porters to get your package built (and building).

If they listened or cared about problems, and not just ignore them, yes...

Grüße/Regards,

Rene
-- 
 .''`.  René Engelhard -- Debian GNU/Linux Developer
 : :' : http://www.debian.org | http://people.debian.org/~rene/
 `. `'  r...@debian.org | GnuPG-Key ID: D03E3E70
   `-   Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: different .diff.gz for different platforms (armel) prohibiting upload

[Goswin von Brederlow]

Steffen Moeller  writes:

> Russ Allbery wrote:
>> Raphael Hertzog  writes:
>> 
>>> That said uploading missing binaries yourself is not the rigt way forward,
>>> official build daemons must be able to build it and you should work with
>>> buildd maintainers and porters to get your package built (and building).
>> 
>> I thought that statement didn't apply to non-free packages?
>
> This is also my understanding, Raphael has probably missed the indication of
> the package being in non-free.
>
> As a sidenote, and to promote the summary on http://wiki.debian.org/buildd a
> bit, there is a non-free buildd network. This has taken perfect care of my
> non-free packages so far, but it seems defunct for mips and armel these days.
>
> Cheers,
>
> Steffen

Non-free has autobuilders on an opt-in basis. Where legally possible
maintainers should opt-in and not build packages themself.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: different .diff.gz for different platforms (armel) prohibiting upload

[Steffen Moeller]

Hi Raphael,

Raphael Hertzog wrote:
> On Sun, 27 Sep 2009, Steffen Moeller wrote:
>> I tried to help it out with my OpenMoko running Debian, and while it builds, 
>> I
>> cannot upload since the .diff.gz generated by dpkg-buildpackage -sd is not
>> bit-identical to the .diff.gz that is in the archive. The unpacked diff.gz
>> however _is_ identical. You then the the .dsc and the .changes to disagree 
>> with
>> the various checksums.
> 
> That's why you don't rebuild the source package and use dpkg-buildpackage -B
> like the buildds in those situations.

have many many thanks, I as not aware of -B being different from -sd for an
all-arch-dependent package. I know now.

[ Uploading job mgltools-molkit_1.5.4.cvs.20090603-1_armel
 mgltools-molkit_1.5.4.cvs.20090603-1_armel.deb 2879.3 kB, ok (26 s, 110.74 
kB/s)
 mgltools-molkit_1.5.4.cvs.20090603-1_armel.changes 1.1 kB, ok (1 s, 1.10 kB/s) 
]

The .diff.gz is indeed no longer an issue, as it seems.

Happy now!

Steffen


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: different .diff.gz for different platforms (armel) prohibiting upload

[Steffen Moeller]

Russ Allbery wrote:
> Raphael Hertzog  writes:
> 
>> That said uploading missing binaries yourself is not the rigt way forward,
>> official build daemons must be able to build it and you should work with
>> buildd maintainers and porters to get your package built (and building).
> 
> I thought that statement didn't apply to non-free packages?

This is also my understanding, Raphael has probably missed the indication of
the package being in non-free.

As a sidenote, and to promote the summary on http://wiki.debian.org/buildd a
bit, there is a non-free buildd network. This has taken perfect care of my
non-free packages so far, but it seems defunct for mips and armel these days.

Cheers,

Steffen


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: different .diff.gz for different platforms (armel) prohibiting upload

[Russ Allbery]

Raphael Hertzog  writes:

> That said uploading missing binaries yourself is not the rigt way forward,
> official build daemons must be able to build it and you should work with
> buildd maintainers and porters to get your package built (and building).

I thought that statement didn't apply to non-free packages?

-- 
Russ Allbery (r...@debian.org)   


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: different .diff.gz for different platforms (armel) prohibiting upload

[Julien Cristau]

On Sun, Sep 27, 2009 at 10:53:01 +0200, Steffen Moeller wrote:

> Hello,
> 
> my non-free package mgltools-molkit built nicely everywhere, but the armel
> could yet not be uploaded - blocking the autodocktools to arrive in testing.
> 
> I tried to help it out with my OpenMoko running Debian, and while it builds, I
> cannot upload since the .diff.gz generated by dpkg-buildpackage -sd is not
> bit-identical to the .diff.gz that is in the archive. The unpacked diff.gz
> however _is_ identical. You then the the .dsc and the .changes to disagree 
> with
> the various checksums.
> 
You're not supposed to upload the source twice.  You upload the source
once, and other architectures do binary-only uploads.

Cheers,
Julien


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: different .diff.gz for different platforms (armel) prohibiting upload

[Raphael Hertzog]

Hi,

On Sun, 27 Sep 2009, Steffen Moeller wrote:
> I tried to help it out with my OpenMoko running Debian, and while it builds, I
> cannot upload since the .diff.gz generated by dpkg-buildpackage -sd is not
> bit-identical to the .diff.gz that is in the archive. The unpacked diff.gz
> however _is_ identical. You then the the .dsc and the .changes to disagree 
> with
> the various checksums.

That's why you don't rebuild the source package and use dpkg-buildpackage -B
like the buildds in those situations.

That said uploading missing binaries yourself is not the rigt way forward,
official build daemons must be able to build it and you should work with
buildd maintainers and porters to get your package built (and building).

Cheers,
-- 
Raphaël Hertzog


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

different .diff.gz for different platforms (armel) prohibiting upload

[Steffen Moeller]

Hello,

my non-free package mgltools-molkit built nicely everywhere, but the armel
could yet not be uploaded - blocking the autodocktools to arrive in testing.

I tried to help it out with my OpenMoko running Debian, and while it builds, I
cannot upload since the .diff.gz generated by dpkg-buildpackage -sd is not
bit-identical to the .diff.gz that is in the archive. The unpacked diff.gz
however _is_ identical. You then the the .dsc and the .changes to disagree with
the various checksums.

I have performed the armel-builds and uploads for a series of other mgltools-*
packages, hence while the error may be on my side, I would be somewhat 
surprised.

Is there a standard procedure to follow? Shall I somehow (how?) invoke
dpkg-genchanges manually with the .diff.gz being exchanged with the original
again? Is there some other trick of the trade?

And: if my error report is correct, is the logic possibly flawed to reject the
upload even though the contents of the .diff.gz are identical?

$ LANG=C diff mgltools-molkit_1.5.4.cvs.20090603-1.diff.gz
../mgltools-molkit_1.5.4.cvs.20090603-1.diff.gz && echo identical ||echo differ
Binary files mgltools-molkit_1.5.4.cvs.20090603-1.diff.gz and
../mgltools-molkit_1.5.4.cvs.20090603-1.diff.gz differ
differ

now with zdiff:

$ LANG=C zdiff mgltools-molkit_1.5.4.cvs.20090603-1.diff.gz
../mgltools-molkit_1.5.4.cvs.20090603-1.diff.gz && echo identical ||echo 
different
identical


Many thanks

Steffen



signature.asc
Description: OpenPGP digital signature