Hi *,
please compare
http://lists.debian.org/debian-devel-changes/2013/02/msg00141.html
with, for example,
http://lists.debian.org/debian-devel-changes/2013/02/msg00140.html
and tell me whether you’re seeing what I am seeing:
• As, apparently (he’s done it for bind9 and util-linux too) normal
f
On 2013-02-06, Thorsten Glaser wrote:
> ??? As, apparently (he???s done it for bind9 and util-linux too) normal
> for LaMont, he???s
> ??? uploading (hand-built¹) binaries for two architectures
I've uploaded several architectures at once in the past on multiple
occasions.
http://www.google.co
On Wed, Feb 06, 2013 at 11:33:39AM -0700, LaMont Jones wrote:
> mergechanges is responsible for the differences you're seeing:
> dpkg-source is run (yes, on an ubuntu system), and then binaries are built
> on a system that is running sid, both amd64 and i386 binaries, since at
> least one of those
On Wed, Feb 06, 2013 at 06:11:03PM +, Thorsten Glaser wrote:
> please compare
> http://lists.debian.org/debian-devel-changes/2013/02/msg00141.html
> with, for example,
> http://lists.debian.org/debian-devel-changes/2013/02/msg00140.html
> and tell me whether you’re seeing what I am seeing:
> •
LaMont Jones dixit:
>mergechanges is responsible for the differences you're seeing:
[…]
>uploaded (again from the ubuntu system, but the bits are firmly cast on sid.)
OK, thanks for the explanation.
>least one of those buildds has bitten me with bad binaries in the past.
Hm. I think that’s no r
Hi,
Thorsten Glaser wrote:
> • In addition to that, this time,
> ‣ it’s got an Original-Maintainer field
> ‣ “Maintainer: Ubuntu Developers ”
> … excuse me, what?
This would have been catched by Lintian:
E maintainer-address-causes-mail-loops-or-bounces
Ubuntu Developers
W unkno
Thorsten Glaser writes:
> I’ve been seeing this on d-d-changes for a while now. Please explain,
> otherwise I’m going to call for an binNMU (on every binary you uploaded)
> before wheezy is released, since we obviously cannot trust these bina‐
> ries and they’re not exactly leaf packages with < 10
Sune Vuorela vuorela.dk> writes:
> What's the problem here ?
It’s a trust question. If something differs, people wonder why.
If something broke in the past, people are more wary.
The answer showed that there’s nothing to worry except for the
maintainer address merge failure, though (this is why
Just for the future, could folks try to avoid subject lines like this? It
comes across as a call-out, which sets things off on a confrontational
footing, and does kind of annoying things like cause the thread to show up
if one searches the list archives for someone's name.
LaMont handled it very
Russ Allbery debian.org> writes:
> Just for the future, could folks try to avoid subject lines like this? It
> comes across as a call-out, which sets things off on a confrontational
Oh, okay. Sorry.
> LaMont handled it very well, and not everyone is bothered by it, but it
> seems like an unnec
On Wed, Feb 06, 2013 at 11:33:39AM -0700, LaMont Jones wrote:
> [...] binaries are built
> on a system that is running sid, both amd64 and i386 binaries, since at
> least one of those buildds has bitten me with bad binaries in the past.
[...]
> The packages you're seeing are built on a sid amd64 bo
Le Wed, Feb 06, 2013 at 06:47:16PM +, Thorsten Glaser a écrit :
>
> Considering that Debian wants to move to allow only buildd-built
> binaries into the archive *anyway*, I think that should rather
> get fixed, if it isn’t already.
Hi Thorsten,
in my understanding, the rough consensus is to
On 06/02/2013 22:35, Russ Allbery wrote:
Just for the future, could folks try to avoid subject lines like this? It
comes across as a call-out, which sets things off on a confrontational
footing, and does kind of annoying things like cause the thread to show up
if one searches the list archives f
Hi,
On Wed, 06 Feb 2013, LaMont Jones wrote:
> On Wed, Feb 06, 2013 at 11:33:39AM -0700, LaMont Jones wrote:
> > mergechanges is responsible for the differences you're seeing:
> > dpkg-source is run (yes, on an ubuntu system), and then binaries are built
> > on a system that is running sid, both a
14 matches
Mail list logo
