Package: gr-osmosdr
Version: 0.1.4-14
Severity: grave
I installed gr-osmosdr and tried to run it only to get an error:
wx._core.PyAssertionError: C++ assertion "ok" failed at
../src/unix/glx11.cpp(589) in GetGLXVersion(): GLX version not found
The full output of the command is:
linux; GNU C++
After I did a service restart docker the issue disappeared, I'm
leaving the bug open so you may consider if there is any fix that is
needed for this case or you can close the issue.
Baruch
Package: docker.io
Version: 1.13.1~ds2-3
Severity: grave
I dist-upgraded my system today and tried to do a docker build, it
fails with the error:
Incorrect Usage: flag provided but not defined: -console
... (mostly runc help message)
flag provided but not defined: -console
oci runtime error:
Package: node-liftoff
Version: 2.3.0-1
Severity: grave
Justification: renders package unusable
node-liftoff depends on node-extend >= 3.0.0 but only 2.0.0 is available
in the debian repository which makes this package uninstallable.
-- System Information:
Debian Release: stretch/sid
APT
Package: electrum
Version: 1.8-1
Severity: critical
I installed electrum and tried to run it from gui and console and only got
the following:
$ electrum
Error: Could not import PyQt4 on Linux systems, you may try 'sudo apt-get
install python-qt4'
After installing python-qt4 the software starts
Kumar Appaiah wrote:
tags 527516 + patch
thanks
Please find attached a patch to redefine stack_t to stack_t_, as well
as add a few more changes to prevent the build from failing.
I shall prepare an NMU if needed. Please let me know.
I'm short of time lately, please go on with an NMU.
Looks fine to me. I won't be able to do anything soon anyway so you can
upload it immediately to the archive.
Baruch
* Cyril Brulebois [EMAIL PROTECTED] [071009 00:28]:
tag 444530 patch pending
thanks
Lucas Nussbaum [EMAIL PROTECTED] (29/09/2007):
Package: gbdfed
Severity: serious
Looks fine to me, go ahead with immediate upload.
Baruch
* Cyril Brulebois [EMAIL PROTECTED] [071009 13:51]:
tag 444532 patch pending
thanks
Lucas Nussbaum [EMAIL PROTECTED] (29/09/2007):
Justification: FTBFS on i386
Hi.
Please find attached for the NMU I prepared. Since it is
Package: bug-triage
Version: 0.1-1
Severity: grave
Any query other than bug number doesn't show any bug report, this makes
the program quite unusable.
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.22-rc4-mexhat
Debian Release: lenny/sid
500 unstable
* Lior Kaplan [EMAIL PROTECTED] [070705 01:46]:
Michael Ablassmeier wrote:
while running archive wide piuparts tests your package failed on install
with
the following error:
Unpacking culmus (from .../culmus_0.101-7_all.deb) ...
ln: creating symbolic link
ivritex should be removed from testing so that it won't block texlive,
there is someone who said he is working on merging the needed ivritex
bits into upstream babel. I'll try to see how that goes and if we can
simply remove ivritex or just make it a setup package for Hebrew fonts.
Baruch
* Ralf
* Stephen Gran [EMAIL PROTECTED] [070404 02:25]:
Package: kvm
Version: 14-1
Severity: serious
Unpacking replacement kvm ...
dpkg: error processing /var/cache/apt/archives/kvm_18-1_i386.deb (--unpack):
trying to overwrite `/usr/share/modass/packages/kvm-source', which is also
in package
This is in fact a bug in debhelper and it was already filed as #406921.
We'll see how that bug progresses, if it won't we'll look into putting a
patch in for now.
Cheers,
Baruch
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
The package is not in etch at all so there is not point asking for its
removal. In any case the way to ask for a package removal from testing
is by a bug report to ftp-masters, this is detailed in the maintainer
manuals.
I never had a plan for KVM to be in etch, it came too late and is still
in
* Steve Langasek [EMAIL PROTECTED] [070114 15:43]:
On Sun, Jan 14, 2007 at 12:01:44PM +0200, Baruch Even wrote:
The package is not in etch at all so there is not point asking for its
removal. In any case the way to ask for a package removal from testing
is by a bug report to ftp-masters
* Ritesh Raj Sarraf [EMAIL PROTECTED] [061217 02:35]:
Package: kvm-source
Version: 7-1
Severity: grave
Justification: renders package unusable
I'm currently using kvm source 7-1 on 2.6.19. I noticed that even though
the kvm module is listed in lsmod output, upon load there was no message
This package should not be built on other arches, it is meaningless for
any but i386 and will be useful for amd64 in a later version. The
package has Architecture: i386, why is it being auto-built at all?
Baruch
* Bastian Blank [EMAIL PROTECTED] [061125 18:04]:
Package: kvm
Version: 4-1
I got remote access to an amd64 machine and reproduced the bug with
debug symbols for gbdfed (no debug symbols on gtk).
(gdb) bt
#0 0x2abaf82bd07b in raise () from /lib/libc.so.6
#1 0x2abaf82be84e in abort () from /lib/libc.so.6
#2 0x2abaf82f35e9 in __fsetlocking () from
A different run, a different backtrace
(gdb) bt
#0 0x2ad51ef370d4 in pango_cairo_show_error_underline () from
/usr/lib/libpangocairo-1.0.so.0
#1 0x2ad51e6835b5 in gtk_entry_new () from /usr/lib/libgtk-x11-2.0.so.0
#2 0x2ad51e6ea64d in _gtk_marshal_BOOLEAN__BOXED () from
There seems to be two possible ways to trigger a bug on amd64, if I load
the font from the menu it crashes when double clicking a letter to edit
it. The crash happens somewhere in Pango.
If I load the font from the command line, the crash happens right after
I single click on a letter, this crash
Thanks for the bug report.
I do not have access to an amd64 machine that can forward X11
connections to test it and debug the issue. Maybe you can help me with
this?
I've forwarded the bug report to the upstream author since it is an
upstream bug, maybe he'll be able to test and fix this.
Hi,
I got access to an amd64 machine with remote X control and was able to
reproduce the bug. I'm currently trying to understand the reason for
this but it proves to be non-trivial.
As to the removal of xmbdfed, the program contained code which failed
to comply with the DFSG so Debian couldn't
* Baruch Even [EMAIL PROTECTED] [061024 09:57]:
One thing that jumps to the eye from memset analysis is that in fontgrid
you memset sometimes with sizeof(unsigned long) and sometimes with
sizeof(guint32), on 64 bit machines the first will be double the size!
This seems to have done the trick
Upstream author released version 1.2 which fixes this issue:
http://crl.nmsu.edu/~mleisher/gbdfed-1.2.tar.bz2
I will package it within 24 hours.
Cheers,
Baruch
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
* Daniel Richard G. [EMAIL PROTECTED] [061025 06:59]:
Baruch, your debug-fu is impressive. I usually resort to Valgrind in cases
like these, and couldn't make heads nor tails of the logs; they were all
over the place.
Mark's 1.2 code is working beautifully for me, and so should the updated
I've reported it to the upstream author. Thanks for the bug report!
Baruch
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Aug 2006 14:24:06 +0200
From: Jose A. Ortega Ruiz [EMAIL PROTECTED]
Organization: IEEC
To: Baruch Even [EMAIL PROTECTED]
References: [EMAIL PROTECTED]
Hi Baruch. I'm attaching a couple of patches that should fix the
compilation errors (actually warnings, but i have -Werr) you reported.
I noticed
the package.
Regards,
Baruch Even
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi,
Anything new about this bug? You said that you'll ask for removal of
zpkg from unstable once it's not needed. I was looking through RC bugs
that affect etch and there is no update on this issue for a year now.
Thanks,
Baruch
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for the bug report on bidiv, it seems to be an issue with cdbs
overriding the package LDFLAGS (and CFLAGS), I've uploaded now an
updated version to fix this FTBFS.
Thanks,
Baruch
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Thanks for the bug report, I will try to get to it sooner rather than
later, but if someone has this NMU-ready, please feel free to upload at
will. With the expected patch in a bug-report.
Regards,
Baruch
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
Thanks!
Steve Langasek wrote:
tags 34604 patch
thanks
On Mon, Jan 09, 2006 at 11:04:30AM +, Baruch Even wrote:
Thanks for the bug report, I will try to get to it sooner rather than
later, but if someone has this NMU-ready, please feel free to upload at
will. With the expected patch
The patch definitely worked for me, I've applied it to a 2.1.1 version
of the package I created for my use and it solved the frequent crashes.
Baruch
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
tag 259939 + pending
thanks
The package was removed from testing due to FTBFS bug due to gcc 4.0
incompatibility.
I've uploaded a fixed version to the 7 days delayed queue on gluck. This
applies the patch available in the bug report and adds two new build
dependencies, libxp-dev and
Package: katoob
Version: 0.3.8-1
Severity: grave
katoob depends on libaspell15 which has been replaced with
libaspell15c2. The package needs to be rebuilt to correct this.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Brian Nelson wrote:
On Sat, Jul 23, 2005 at 08:28:59PM +0100, Baruch Even wrote:
katoob depends on libaspell15 which has been replaced with
libaspell15c2. The package needs to be rebuilt to correct this.
Please don't.
I (aspell maintainer) am undoing the libaspell15 transition, so
[EMAIL PROTECTED] wrote:
Hi All,
Since there's a workaround, what do you think on reducing the sevirity of
this bug report. This will allow clumus 0.101-2 to get into sarge.
Since this is a real functionality issue and we want OOo to work out of
the box without the user needing anything special
37 matches
Mail list logo
