Stefano Zacchiroli wrote:
Hi Mike,
can you please tell me which .cmx* files you're missing.
Sure.
[...]
Moreover, also checking which *.cmx* files have been built by
the world.opt target of camlp5 at the end of the build process I see:
[...]
./odyl/odyl.cmxa
./odyl/odyl.cmx
Enrico Tassi wrote:
Package name: matita
Stefano already has some packages for this on his gluck page[1], have
you talked to him about the status of those?
Cheers,
-Mike
[1] - deb http://people.debian.org/~zack unstable helm
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
Mike Furr wrote:
Enrico Tassi wrote:
Package name: matita
Stefano already has some packages for this on his gluck page[1], have
you talked to him about the status of those?
Err, nevermind. I forgot he only supplied meta packages for the deps
(been a few months since I last looked
Package: wnpp
Severity: wishlist
Owner: Mike Furr [EMAIL PROTECTED]
Package name: ocaml-reins
Version : 0.1a
Upstream Author : Mike Furr [EMAIL PROTECTED]
URL : http://ocaml-reins.sf.net
License : LGPL 2.1 w/ standand OCaml linking exception
Programming
Sylvain Le Gall wrote:
The command:
otags -v *.ml -o -
Run in a directory full of OCaml source file doesn't output anything.
Running the same command on Etch (i.e. with ocaml 3.09.2) output a TAG
file...
I think there is a problem, or i am missing something.
It looks like otags is missing
Package: camlp5
Version: 4.08-1
Severity: normal
Although the world.opt target in the upstream camlp5 distribution builds
native code versions of the library, the install target does not seem to
actually install them. It would be great if it could be patched so that
all of the native code
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
I don't understand why this is not an RC bug (and has not yet been fixed
despite fixed-upstream). I have been unable to run any code which uses
TTF_Render*_Solid without getting the error described.
As such, I would also request that the fix be back-ported and submitted
for inclusion in Etch r1
Package: wnpp
Severity: normal
I request an adopter for the chromium package. The game is dead upstrem,
but clearly still has a large set of users. It has recently been discovered
that some of the music is non-free and some of the sounds are
non-distributable. The issues are discussed in
Package: wnpp
Severity: normal
I request an adopter for the vegastrike suite of packages. The data
package is pretty big weighing in at ~150MB making it one of the larger
packages in Debian. It has a pretty good user base, and upstream is still
active. However, development is quite slow
Package: tuareg-mode
Version: 1:1.45.4-1
Severity: normal
The tuareg feature show type at point requires the caml-types.el which
is in the ocaml-mode package and so doesn't work if the latter is not
installed. So, tuareg-mode should probably recommend or suggest
ocmal-mode. I would say
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for all of your hard work with these bugs. Sorry I haven't been
more responsive, I've been crazy busy.
However, I'll upload a new chromium package within a day or two to
incorporate your fixes.
Thanks again!
- -Mike
-BEGIN PGP
-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 the
-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
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Keegan Quinn wrote:
When running terminatorX (sid/i386 build 3.82-7) I am consistently
getting freezes (the UI stops responding) when opening Ogg Vorbis and MP3
files.
[...]
The resulting build has working Ogg Vorbis and MP3 support and does not
and 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
Package: x11-common
Version: 6.9.0.dfsg.1-6
Severity: minor
x11-common Conflicts against the package 'XFS-XTT', but this should
be 'xfs-xtt' as all package names are required to be lower case by
policy. I'm not sure if the current package tools enforce this
difference, but its probably best to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tobias Frost wrote:
Package: vegastrike
Version: 0.4.3-4
Followup-For: Bug #359173
For me, it works, when disabling sound.
If sounds are enabled, I also experience the very same crash.
Maybe this is a sound-related crash?
Thanks for the
Gonéri Le Bouder wrote:
I still have the problem with libsdl-net1.2 (1.2.5-6).
I just uploaded -7 which *actually* fixes this. Sorry about that.
-m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Langasek wrote:
Well, except that a) using apt to install the new package would
automatically handle this upgrade case for you
That requires me to setup my own apt repository though (and
README.Debian talks about using dpkg).
(and there
-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.
-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 PGP
-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 etch?
-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
-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 ocaml not setting .prologue
-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 ocaml not setting .prologue
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Falk Hueffner wrote:
AFAICS, the caml_apply2 posted to
http://caml.inria.fr/mantis/view.php?id=3912 does not indicate an
actual problem. .prologue 0 means the function will not rely on pv
($27) being set correctly, and it will not clobber gp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There are several command line options which are useful when debugging
this...
$ ocamlopt -S foo.ml
generates the assembly output for foo.ml in foo.s
$ ocamlopt -dstartup -o foo foo.ml
preserves the startup asm file as /tmp/camlstartup* (this will
-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
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
-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
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sven Luther wrote:
On Wed, Nov 09, 2005 at 12:44:15AM -0500, Mike Furr wrote:
(as soon as I figure out why this assembly code is all of sudden
segfaulting...)
Because binutils is a broken mess taken from a random devel CVS snapshot ?
I don't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Stork wrote:
libnumerix-ocaml-dev doesn't contain a libnumerix-ocaml file and
therefore can't be used for native compilation.
I don't understand what's wrong. libnumerix-ocaml has nothing to do
with native compilation, only the -dev is needed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Stork wrote:
I had to install /usr/lib/ocaml/3.08.3/numerix/libnumerix-ocaml.a by
hand from the source to make ocamlc -custom ... or ocamlopt ...
work.
Ah I see. For some reason, I missed that the library changed names and
therefore it
Package: debbugs
Severity: normal
I recently closed bug 328042 via changelog with package version
0.9.12-10. It turned out that the fix was incorrect, so I wanted
to reopen it. Trying out the new syntax, I sent in the command
found 328042 0.9.12-10
However, this did not reopen the bug which
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:
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
-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 the
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')
(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
diff -urN libmusicbrainz-2.1
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
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
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,
: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 +
+
libmusicbrainz-2.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well, obviously the patch mentioned above is brain dead. A better
approach might be to move the #include inside the #ifndef, but I don't
really know the reason for it being outside of it in the first place, so
I trust you'll find the best solution.
Package: libfam-dev
Version: 2.7.0-7.1
Severity: grave
fam.h contains the line:
#include limits.h
which should be
#include limits.h
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:
Package: libc6-dev
Version: 2.3.2.ds1-22
Severity: normal
/usr/include/limits.h tries to include limits.h from
/usr/lib/gcc/.../include, via:
#include_next limits.h
on line 124 which is outside of its ifdef on _LIBC_LIMITS_H_
Thus, with the preprocessor shipped with gcc-4.0, this may cause an
-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-
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
-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:
/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] Sun, 10 Jul
Package: wnpp
Severity: wishlist
Owner: Mike Furr [EMAIL PROTECTED]
* Package name: omake
Version : 0.9.4
Upstream Author : Jason Hickey [EMAIL PROTECTED]
* URL : http://omake.metaprl.org
* License : GPL
Description : build system with automated
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luca Bruno wrote:
You can find the italian debconf translation attached.
Please apply it.
Perfect timing, I was just preparing an upload for the new jack library.
:)
Cheers,
- -Mike
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
xmms just segv'd on me again. Apparently the way to reproduce this bug
is to report it solved and then wait a bit :-(. The messages on my
console before the crash are:
Message: alsa mixer timed out
ALSA lib simple.c:952:(simple_add1) helem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here is the backtrace from my most recent xmms crash:
Message: alsa mixer timed out
Message: alsa mixer timed out
Message: alsa mixer timed out
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1214145616 (LWP 9065)]
-type == SND_MIXER_ELEM_SIMPLE' failed.
Mike Furr wrote:
, but I'm not using a recent version of the alsa modules. If I
still have issues after upgrading my kernel, I'll post any details there.
I've now upgraded to kernel v2.6.11 and built new modules from
alsa-source 1.0.9b-1
xmms no longer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Hood wrote:
Do you still get this segfault with libasound2 1.0.9?
After using xmms for a while today, the segfault seems to no longer
occur. Thanks for the follow-up. Feel free to close this now.
I do however get a lot of annoying messages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Kerrisk wrote:
Joey, Mike,
I will add a note under BUGS to the man page to point
out this bug in older kernels. That will appear in
man-pages-2.04.
Great, thanks. Sorry for not checking more recent kernel versions. I
tend not to
-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
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
Richard Jones wrote:
About 2-3 weeks ago I put the latest perl4caml and a working debian/
config into subversion on alioth. Can someone help me to upload this?
Sure. How do want to have this package maintained? I know that you are
subscribed
Package: manpages-dev
Version: 2.02-1
Severity: normal
The epoll_ctl(2) man page states that when using the op parameter
EPOLL_CTL_DEL, The event is ignored and can be NULL. However, if
epoll_ctl is passed a value of NULL in its event paramter in this
case, it returns EFAULT (which is also not
-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 suppose
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
datareaver wrote:
Package: vegastrike
Version: 0.4.3-1
Followup-For: Bug #296503
Thanks for the report, I'll try to get to this soon
- -Mike
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (GNU/Linux)
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julien PUYDT wrote:
my little pet project's opt build-target was broken by the recent
package upgrade (transition to 3.08.3) because the two mentioned files
are missing.
Oops, I broke my build environment (to test a non-opt build) and forgot
to
Package: wnpp
Severity: wishlist
Owner: Mike Furr [EMAIL PROTECTED]
Package name: ocaml-getopt
Version : 0.0.20040811
Upstream Author : Alain Frisch [EMAIL PROTECTED]
URL : http://www.http://www.eleves.ens.fr/home/frisch/soft.html
License : MIT
Joachim Breitner wrote:
Hi,
after blind stabbing into chromium's OpenAL sources, I had a look at
SuSE's sources and found this hack. I dunno how bad it is, but it works:
Thanks for this! I haven't had a chance to try it out yet, but I should
be able to get to it later this week.
Cheers,
-Mike
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Jochens wrote:
| Please add support for the ppc64 architecture.
Have you verified that the package builds okay on that arch(or even
better, runs)? I see in the vegastrike source, there is at least one
mention of an #ifdef on __powerpc64__...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joachim Breitner wrote:
| Hi,
Hello,
| I just wanted to say that I can confirm this bug, and that the game
| would be more fun with audio effects :-)
Yeah, I know. I've tried a couple of times to find out what is causing
this and haven't had much
Christopher Knadle wrote:
#0 0xb79987ab in raise () from /lib/tls/libc.so.6
#1 0xb7999f12 in abort () from /lib/tls/libc.so.6
#2 0xb799226f in __assert_fail () from /lib/tls/libc.so.6
#3 0xb7cd1695 in native_blitbuffer () from /usr/lib/libopenal.so.0
#4 0xb7cd5d42 in _alcDeviceWrite () from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Burrows wrote:
| The player's guide documents vslauncher as the standard way to start
a new
| game and to modify your settings. Unfortunately, it's missing and
vsinstall
| only seems to work once (now it just starts the game with my current
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Burrows wrote:
| http://vegastrike.sourceforge.net/forums/viewtopic.php?t=3532
|
| Basically, after a ship is destroyed or you eject cargo, you can't
tractor
| anything (except the enemy pilot's escape capsule). Apparently this
is a bug
| in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christopher Knadle wrote:
|Let me know what you would like me to test next.
|Thanks.
Sorry for the delay in getting back to you. I built a version of the
main binary with all the debugging symbols which I uploaded here:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Burrows wrote:
| Package: vegastrike
| Version: 0.4.3-1
|
| I just spent about 15 minutes trying to quit Vegastrike after
realizing that
| it didn't have in-game documentation of how to play.
D'oh!
| I finally had to find
| another computer,
Chris Knadle wrote:
NOTE: I was remiss in not submitting a bug report for the _previous_
version of Vegastrike, which also segfaulted on startup on this system.
Hmm...that's unfortunate. :-(
What kind of graphics card do you have? Which drivers are you using
with it?
Are you able to use other 3D
After playing with the recently uploaded 0.4.3, save games now seem to
persist across saved games.
enjoy,
-Mike
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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
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
Miroslav Kure wrote:
Hi, in attachement there is initial Czech translation (cs.po) of
terminatorx debconf messages, please include it.
Thanks! I'll upload it in a few days.
-Mike
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: xmms
Version: 1.2.10-2
Severity: important
Since upgrading to libasound2 1.0.7, xmms segfaults within 15 minutes of
starting when using the alsa plugin. It doesn't always occur with
any particular song(like in 288872) and although I do see the torrent of
messages reported in #287583,
84 matches
Mail list logo
