Package: libdvilib2-16
Version: 1.3.2-1
Severity: serious
libdvilib2-16 needs to conflict with libdvilib2-13 to ensure a smooth
transition. Otherwise, the following error occrus:
Unpacking libdvilib2-16 (from .../libdvilib2-16_1.3.2-1_i386.deb) ...
dpkg: error processing
/var/cache/apt/archives/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julien Cristau wrote:
> Hi,
> the problem was that the toplevel Makefile touches boot/Makefile.dep,
> and in some cases it lead to build failures because Makefile.dep
> wouldn't properly regenerated.
> This touching is useless, as far as I can see, so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Randall Donald wrote:
> Does
> http://www.khensu.org/nvidia-kernel-legacy-2.6.18-1-686_1.0.7184
> +2_i386.deb
> work for you? It loads for me.
Yup, the module in that package loads fine.
- -m
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/L
Package: nvidia-kernel-legacy-2.6.18-1-686
Version: 1.0.7184+1
Severity: grave
I just upgraded to the stock i686 2.6.18 Debian kernel (2.6.18-3)
and installed the corresponding nvidia-legacy package. After rebooting,
the kernel module fails to load:
# modprobe nvidia
nvidia: disagrees about abo
raw sound effects are from two sound
search engines, but I was unable to find their exact origins. Do you
know the original owner and the license for distributing these files?
Thanks,
- -Mike Furr
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Langasek wrote:
> Your point is non-obvious to me. A Replaces: w/o Conflicts: makes sense
> only if ownership of files has moved from one package to another, which is
> not the case here since the two versions of the package aren't necessarily
>
Package: nvidia-kernel-legacy-source
Version: 1.0.7174-2
Severity: serious
The template file in the legacy source package needs to Replace
nvidia-kernel-#KVERS# in addition to conflicting with it so that us
old-time card users can "upgrade" to the legacy packages. See policy
7.5 for more info.
P
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Justin Pryzby wrote:
> I intend to NMU a fix for this bug sponsored by Thomas Viehmann; the
> attached patch simply drops the dependency on xlibs-dev, because there
> is no actual direct dependency.
That's fine. Please go ahead.
- -Mike
-BEGIN P
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thijs Kinkhorst wrote:
> Hello Mike,
Hello!
>>After discussing the situation with upstream, we agreed that vegastrike
>>would better serve our users if it was not shipped in sarge.
> Sarge has been released, will vegastrike be ready at the time of etc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
How much memory (physical & swap) does your machine have? When you run
the game, how is currently free?
- -Mike
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDoio/7ZPKKRJLJvMRAhwZAJwJyDmuhwzg6SVhRbdIV1TyOkMbeACfW+Xx
ViEZWcz5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Falk Hueffner wrote:
> On Wed, Dec 07, 2005 at 08:54:03PM -0500, Mike Furr wrote:
>>This is actually a bug in binutils (338148). I'll leave this bug
>>here just so it doesn't get reported again.
> AFAICT, 338148 is about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Falk Hueffner wrote:
> On Wed, Dec 07, 2005 at 08:54:03PM -0500, Mike Furr wrote:
>>This is actually a bug in binutils (338148). I'll leave this bug
>>here just so it doesn't get reported again.
> AFAICT, 338148 is about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florian Weimer wrote:
> Unfortunately, this patch doesn't fix the problem. Maybe Ocaml itself
> needs to be compiled with -ffunctio-sections, or the linker error
> message is wrong.
Yes, I reopened the bug (#332902) after seeing this too. It appears
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Langasek wrote:
> Rather, the segfault happens in camlPrintf__entry, which is called
> from caml_startup__code_begin. I can't find a definition for
> camlPrintf__entry anywhere, and I do in fact see some
> suspicious-looking differences when dis
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is actually a bug in binutils (338148). I'll leave this bug here
just so it doesn't get reported again.
- -Mike
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDl5I57ZPKKRJLJvMRArvPAJ9UoLsRKdF9H7rJ65TQGU+qbTBl1QCggDVU
jMd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Langasek wrote:
> This is a false positive on the check for affected C++ libraries; although
> the felix package does ship a .so file in /usr/lib, it contains no soname
> and the package provides no shlibs, so there's no way that there could be
>
Package: ladspa-sdk
Version: 1.1-3
Severity: serious
ladspa-sdk FTBFS on m68k due to an ICE[1]:
make[1]: Entering directory `/build/buildd/ladspa-sdk-1.1/src'
cc -I. -O3 -fPIC -o plugins/amp.o -c plugins/amp.c
plugins/amp.c: In function '_init':
plugins/amp.c:314: internal compiler error: Segmenta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A Mennucc wrote:
> the real problem is that , for some reason, the Conflict
> line in the source is different from the one in the binary package.
> The conflicts line in the binary lacks the "libsnmpkit2c102" entry.
Hmm... weird, its definitely not in
Package: libsnmpkit2c2
Version: 0.9-9
Severity: serious
libsnmp2c102 can not be upgraded to libsnmp2c2 because the latter lacks
a "Replaces: libsnmp2c102" and thus dpkg refuses to overwrite files
existing in both packages.
-- System Information:
Debian Release: testing/unstable
APT prefers uns
Package: moagg
Severity: serious
moagg's Build-Depends contains the entry:
libsdl1.2-dev ((>=1.2.7+1.2.8cvs20041007-5.2)
which has an extra parenthesis which needs to be removed.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Archi
+libmusicbrainz-2.1 (2.1.1-3.2) unstable; urgency=low
+
+ * Non-maintainer upload
+ * Really apply 64-bit pointer patch (Closes: #316584)
+
+ -- Mike Furr <[EMAIL PROTECTED]> Tue, 2 Aug 2005 16:28:17 -0400
+
libmusicbrainz-2.1 (2.1.1-3.1) unstable; urgency=low
* Non-maintainer upload
Adeodato Simó wrote:
I can't see this patch in your NMU diff, and it doesn't seem to be in
the uploaded package either (as found on gluck_delayed/DONE). Just
mentioning in case it can be useful.
Bah, you are absolutely right. Sorry about that. I prepared the
package and then my chroot br
Package: gnome-vfs2
Severity: serious
libgnomevfs2-common has a dep on libfam0c102. However, libfam0c102 has
been replaced by libfam0 as part of the C++ transition. Therefore
gnome-vfs2 and all of its rdeps are uninstallable with the new version
of fam. Please upload a new version of gnome-vfs2
:37.553732007
+
@@ -1,3 +1,11 @@
+libmusicbrainz-2.1 (2.1.1-3.1) unstable; urgency=low
+
+ * Non-maintainer upload
+ * Rebuild against g++-4.0 (Closes: #319411)
+ * Applied amd64 g++-4.0 patch (Closes: #316584)
+
+ -- Mike Furr <[EMAIL PROTECTED]> Thu, 21 Jul 2005 21:29:05 +
+
libmusicbrai
Package: libmusicbrainz-2.1
Severity: grave
This package needs to be built with the new g++ version. I'm preparing
an NMU and will upload it to the 0-day queue and post the patch here.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Since libfam-dev is broken with gcc-4.0, it would be great
if the package was updated asap. If you are still busy, I would be
happy to upload a new version with the one line diff described in this bug.
Cheers,
- -Mike
-BEGIN PGP SIGNATURE-
V
Package: libfam-dev
Version: 2.7.0-7.1
Severity: grave
fam.h contains the line:
#include "limits.h"
which should be
#include
otherwise, gcc-4.0's preprocessor will go into an infinite loop and no
program using fam.h can be compiled.
-- System Information:
Debian Release: testing/unstable
APT
ian/changelog 2005-07-10 20:23:21.366793385 +
@@ -1,3 +1,12 @@
+fam (2.7.0-7.1) unstable; urgency=low
+
+ * Non-maintainer upload
+ * Rebuild against new CXX ABI
+- new binary pkg is called libfam0 to match what ubuntu has done
+- Closes: 317700
+
+ -- Mike Furr <[EMAIL PROTECTED]> Su
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Leidert wrote:
> AFAIK it should be libfam0c2 (like libaspell15c2, libwpd8c2, ...). See:
> http://groups.google.com/groups?as_umsgid=%3C4mf37-Fq-11%40gated-at.bofh.it%3E
No, it can be either, see:
http://lists.debian.org/debian-devel-announce/20
Package: fam
Version: 2.7.0-7
Severity: grave
fam needs to be rebuilt for the c++ transition. Today marks 5 days since
the new gcc packages were uploaded (the only c++ dep) and so I plan to
NMU into DELAYED/2-day. The new binary name will be libfam0 to match
what ubuntu has done.
-- System Info
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Regis Boudin wrote:
> Hi,
Hello,
> To fixes are possible. Either making the dlopen against the library
> soname, 'libxmms.so.1', which is a quick fix (patch attached) but will
> be broken if the soname changes, but I doubt it will for XMMS.
This fix s
Package: perl4caml
Severity: grave
This package is built from the wrong OCaml version(it slipped in with a
bad dependency) and thus is completely useless in Debian. I'm uploading
a new version now, but since Sarge is frozen, if it doesn't get built in
time or some such, this package shouldn't be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adrian Bunk wrote:
> Package: libgetopt-ocaml-dev
> Version: 0.0.20040811-1
> Severity: grave
>
> libgetopt-ocaml-dev lacks dependencies.
> Some Ocaml dependencies are for sure required.
No dependencies are required for its 'functionality', but I supp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Samuel Mimram wrote:
> Please also note that some files of this package are under the Q Public
> License which is generally considered as non-DFSG-free. If someone
> decides to maintain it, he will certainly have to deal this issue with
> upstream (I d
Package: vegastrike
Version: 0.4.3-1
Severity: grave
After discussing the situation with upstream, we agreed that vegastrike
would better serve our users if it was not shipped in sarge. Upstream
development is progressing at a nice pace and thus having old versions
around would only generate anno
Package: libzip-ocaml-dev
Version: 1.01-13
Severity: grave
Files /usr/lib/ocaml/3.08/zip/zip.cmxa and /usr/lib/ocaml/3.08/unix.cmxa
make inconsistent assumptions over implementation Unix
Although interesting enough, this only occurs with the native code, not
byte code.
:-(
-- System Information
36 matches
Mail list logo
