[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#241689: I'm going to NMU this

On Sun, 2004-08-29 at 16:47 +0200, Goswin von Brederlow wrote:

> this build-essential bug is holding up the sarge amd64 release and needs
> to be fixed asap. The RM team has agreed to let such trivial amd64 changes into
> and I plan to NMU build-essential unless you fix it yourself.
I wasn't aware:

(a) there was going to be a "sarge amd64 release"

(b) that you were a Debian Developer therefore *could* NMU a package.

(c) that a wishlist bug against an "informational list of packages" was
    more important than the hundreds of RC bugs still outstanding
    against sarge.

I have stated many times over that I do not consider the build-essential
package to be a "this is what build-essential *should* look like" list
but "this is what is *currently* build-essential" list.

If you actually bother to look at the current package you'll see that
the content of essential-packages-list-* for those architectures not yet
in sid is the string:

"No essential packages list is available for $ARCH in sid"

While one of those could be added for amd64, I don't see the urgency
this close to release.

You can obtain a "filled" essential-packages-list-amd64 file for your
archive yourselves by running make-esslist.sh with a different mirror=
and arches= setting.

In fact I suspect there are more changes to build-essential required for
amd64 than just this now.  I understand that there is a dependency on
gcc/g++ 3.4?  If that's correct you'll need to submit a change to the
build-essential list itself as that currently specifies 3.3:

Something like:

	gcc (>= 3:3.3) [!amd64] | gcc (>= 3:3.4) [amd64]

	g++ (>= 3:3.3) [!amd64] | g++ (>= 3:3.4) [amd64]

is probably sufficient.  You can use this bug report to file the actual
requirement, rather than opening a new one.

While I ordinarily welcome NMUs on my packages that fix valid bugs that
I haven't had the time to look at, this is not one of those.  This
change would be invalid, and I specifically ask you not to upload it to
the Debian archive.  Instead follow the changes I've outlined for your
own amd64 archive just as the other derivatives who include amd64 have

Once amd64 has been added to sid, build-essential in sid will be updated
to carry an essential-packages-list-amd64 file.

Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?

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

Reply to: