severity 902972 normal
The SONAME of this library changed, but the ABI did not. There's no
benefit in forcing users to rebuild, and I'm unclear on how this
violates policy, so I'm downgrading the severity to unblock migration.
--
Matthew Garrett | mj...@srcf.ucam.org
not a regression over Sarge.
--
Matthew Garrett | [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
=1.1.2.4hideattic=0only_with_tag=xf-3_3_3
ought to make it pretty clear)
--
Matthew Garrett | [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Sorry? 12 of the files in the source tree contain explicit Nvidia
copyright statements. The others tend to have no copyrights at all, but
are generally written by Mark Vojkovich who is an nvidia employee.
--
Matthew Garrett | [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
, and according to prevailing attitudes on
debian-legal should be removed from Debian.
--
Matthew Garrett | [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
.
--
Matthew Garrett | [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Right. I can build a working binary if I do two things:
1) Add -march=i386 to the gnu-efi and elilo builds
2) Use plain binutils-2.16.1, and not binutils-2.16.1cvs20060117
The first of these is easy, the second involves finding out what's
broken in binutils. What fun.
--
Matthew Garrett
000a 0002f060 0002f060 00029a60
2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
I'm afraid I don't really know toolchains well enough to go much further
myself.
--
Matthew Garrett | [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
. Scanning
the Gentoo binutils and gcc patches doesn't show anything terribly
obvious, so it sounds like tracking this down won't be terribly good
fun.
--
Matthew Garrett | [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Package: elilo
Severity: grave
Justification: renders package unusable
On IA32 systems, attempting to run elilo.efi gives:
'elilo' not found
Exit status code: Invalid Parameter
The Sarge version gives
Exit status code: Load Error
I have a working elilo.efi that was built on a gentoo system
/memmove.c, libntp/mktime.c, libntp/random.c, libntp/strerror.c,
libntp/strstr.c, ntpd/refclock_jupiter.c, and ntpd/refclock_mx4200.c.
These should be referenced in debian/copyright.
BSD with advertising isn't GPL compatible.
--
Matthew Garrett | [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL
remove your material instead.
--
Matthew Garrett | [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Glenn Maynard [EMAIL PROTECTED] wrote:
On Fri, Jul 01, 2005 at 11:08:24PM +0100, Matthew Garrett wrote:
a) Remove the material concerned from the installation guide in woody
and sarge and get new versions uploaded to the archive. Apologise
profusely. Potentially still be sued.
d) Add
Glenn Maynard [EMAIL PROTECTED] wrote:
On Fri, Jul 01, 2005 at 11:58:07PM +0100, Matthew Garrett wrote:
Yes. And?
So you think it's acceptable to have a work in main, whose license is
if you're Debian, you're never allowed to remove this work, or I'll
sue you for an unrelated, already-fixed
I chatted to rml about this at LCA - it ought to only affect the Suse
codepath, so I'm not too worried about it. I'll take another look to
make sure that we're not affected.
--
Matthew Garrett | [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
piece of string at the moment,
so an NMU would be helpful.
Thanks,
--
Matthew Garrett | [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
that it should be
considered a free software license. I think a firm conclusion is going
to have to wait until we actually have a project-wide discussion of how
the DFSG should be interpreted nowadays, especially in the face of
issues that weren't considered when they were written.
--
Matthew Garrett
17 matches
Mail list logo
