Package: ethereal
Version: 0.10.13-1.2
Severity: serious
Justification: Policy 2.3
The latest ethereal NMU is linked against OpenSSL which is not legal.
Ethereal is licensed under the GPL while the OpenSSL license has an advertising
clause that renders it incompatible with the GPL.
Ethereal must
On Mon, Jan 02, 2006 at 12:00:03PM -0800, Daniel Burrows wrote:
> What does "info threads" show, and what do you get if you switch to
> each thread in turn (using "thread") and check the backtrace?
>
> Daniel
Unfortunately, "info threads" makes gdb exit (I don't know why), but here is
the cap
On Tue, Dec 20, 2005 at 08:36:19AM -0800, Daniel Burrows wrote:
> On Mon, Dec 19, 2005 at 11:27:36PM -0500, Ivan Nestlerode <[EMAIL PROTECTED]>
> was heard to say:
> > On Mon, Dec 19, 2005 at 08:05:27PM -0800, Daniel Burrows wrote:
> > > Unfortunately, backtraces a
On Mon, Dec 19, 2005 at 08:05:27PM -0800, Daniel Burrows wrote:
> On Mon, Dec 19, 2005 at 10:48:31PM -0500, Ivan Nestlerode <[EMAIL PROTECTED]>
> was heard to say:
> > The scenario required to reproduce the crash is even simpler now.
> > I have a handful of packages on h
On Sun, Dec 18, 2005 at 09:35:37PM -0800, Daniel Burrows wrote:
> If your system is still in a state where you can reproduce this, what would
> be ideal would be to post a bzipped tarfile of the following somewhere
> (assuming of course that the data are yours to post):
>
> - /etc/apt
> - /v
Package: filelight
Version: 0.99beta6-1+b1
Severity: minor
Running filelight from a shell results in tons of messages on stderr
(without clicking on anything at all). A sampling:
filelight: >> void RadialMap::Map::setRingBreadth()
filelight: >> void RadialMap::Map::paint(unsigned int)
filelight:
Package: filelight
Version: 0.99beta6-1+b1
Severity: normal
If you start filelight from a shell (to see stdout/stderr easily), you
see this after exiting it with "Quit" from the menu:
$ filelight 2>/dev/null
*** glibc detected *** free(): invalid pointer: 0x41752ac0 ***
Alarm clock
-Ivan
-- Sys
Package: aptitude
Version: 0.4.1-1
Severity: normal
I just attempted to downgrade all the binary packages from e2fsprogs
using aptitude. It segfaulted:
# aptitude
Ouch! Got SIGSEGV, dying..
Segmentation fault
I had the following things going on:
mozilla-firefox on hold at version 1.0.7-a
libw
Package: alsa-source
Version: 1.0.10-2
Severity: important
When attempting to upgrade alsa-source today, I got the following error
messages:
Preconfiguring packages ...
alsa-source failed to preconfigure, with exit status 127
(Reading database ... 122403 files and directories currently installed.
On Tue, Dec 06, 2005 at 07:31:20PM -0800, Daniel Burrows wrote:
> Could you please send me the following files? (specifically, place a
> .tar.bz2 somewhere that I can download it)
>
> - /etc/apt
> - ~/.aptitude/config
> - /var/lib/apt/lists
> - /var/lib/aptitude
> - /var/lib/dpkg/stat
Package: aptitude
Version: 0.4.0-5
Severity: important
After running an update this evening, I found myself unable to use
aptitude as it kept getting stuck saying it was "Resolving dependencies".
Basic operations on the preview screen would hang aptitude (trying to
upgrade something that was on h
After filing this bug a long time ago, I just tried to reproduce it and
it seems to be fixed now. I'm not sure exactly when it got fixed, but here are
the relevant package versions on my system now.
-Ivan
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy
On Mon, Nov 07, 2005 at 07:18:49PM -0800, Daniel Burrows wrote:
> When several versions of a package are available, it's sometimes a bit
> confusing which one gets picked as the target of an action (when it matters).
> In this case, aptitude is showing you the reverse dependencies of
> libgnomepr
Package: aptitude
Version: 0.4.0-2
Severity: normal
After recently upgrading to the 0.4.0 version of aptitude, I noticed
that pressing 'r' to show reverse dependencies produces incorrect results
sometimes (haven't figured out the pattern yet; maybe when the dependency is a
strict = on the version)
Package: libssl0.9.7-dbg
Version: 0.9.7g-3
Severity: normal
The .so files in the libssl0.9.7-dbg package do not seem to work.
Were they built properly?
/tmp$ ldd ossl-test
linux-gate.so.1 => (0xe000)
libcrypto.so.0.9.7 => /usr/lib/i686/cmov/libcrypto.so.0.9.7 (0xb7edb000)
Package: kxmleditor
Version: 1.1.4-1
Severity: important
kxmleditor is currently uninstallable in unstable because it still
depends on the kdelibs4 from before the kde/c++ transition.
It needs to be rebuilt against the transitioned library.
Thanks,
-Ivan
-- System Information:
Debian Release: t
Package: kmyfirewall
Version: 0.9.6.2-1
Severity: important
kmyfirewall is currently uninstallable in unstable because it still
depends on the kdelibs4 from before the kde/c++ transition.
It needs to be rebuilt against the transitioned library.
Thanks,
-Ivan
-- System Information:
Debian Releas
Package: filelight
Version: 0.6.4.1-1
Severity: normal
filelight is currently uninstallable in unstable because it still
depends on the kdelibs4 from before the kde/c++ transition.
It needs to be rebuilt against the transitioned library.
Thanks,
-Ivan
-- System Information:
Debian Release: test
Package: libqt4-dev
Version: 4.0.0-1
Severity: important
I just attempted to walk through the tutorial in qt4-doc.
I copied their "Hello World" program and attempted to build it, and ran
into a missing Xinerama library:
$ vi test.cpp
$ qmake -project
$ qmake
$ make
g++ -c -pipe -g -Wall -W -D_RE
Package: libgcrypt11-doc
Version: 1.2.1-1
Severity: important
The latest version of libgcrypt11-doc doesn't install properly. I tried
changing /bin/sh to bash but that did not fix anything.
The error message:
Selecting previously deselected package libgcrypt11-doc.
(Reading database ... 101778 f
Package: rezound
Version: 0.12.0beta-1
Severity: normal
When I start rezound from the command line, I get the following error
message:
using path '/usr/share/rezound' for share data directory
error - Error reading user macro store -- bool CPath::touch(bool, bool)
const -- error touching path name
Package: aptitude
Version: 0.2.15.9-2
Followup-For: Bug #304748
This bug is worse than it sounds.
I've used aptitude for over a year with no major problems to speak of,
but in the past couple of hours I've wasted a decent chunk of it due to
this bug and a key-binding related to it.
For whatever
On Thu, Apr 14, 2005 at 03:10:04PM +1000, Drew Parsons wrote:
> I don't think anyone understands the Debian font system ;)
>
> Nautilus provides me with a nice graphical view of a010035l.pfb and
> tells me it's "URW Gothic L". The URW fonts are provided by gsfonts:
>
> $ dpkg -L gsfonts
> ...
>
On Tue, Apr 12, 2005 at 02:21:24PM +1000, Drew Parsons wrote:
> On Mon, 2005-04-11 at 21:03 -0700, Debian Bug Tracking System wrote:
> > Processing commands for [EMAIL PROTECTED]:
> >
> > > reassign 303930 xprint
> > Bug#303930: mozilla-firefox: printing does not work
> > Bug reassigned from packa
Package: xprint
Version: 1:0.1.0.alpha1-10
Followup-For: Bug #303930
xprint on my system is currently broken. It used to work a few weeks
ago, and I assume that once of the recent upgrades may have caused the
problems (around the package name transition time).
What originally looked like a firef
Package: mozilla-firefox
Version: 1.0.2-3
Severity: normal
I cannot print anything from mozilla-firefox. The system is using CUPS
but I do not think the problem is at that level because I can print
things with lpr from other applications (text and postscript) just fine.
I have tried using firefo
Package: python2.3-libxslt1
Version: 1.1.12-4
Severity: normal
The python bindings for libxml2 and libxslt1 just had their packages renamed.
I attempted to remove the old dummy packages
(libxml2-python2.3 and libxslt1-python2.3), but I cannot do so because
python2.3-libxslt1 has a versioned depend
Package: java-package
Version: 0.19
Severity: wishlist
It would be nice if the .deb packages generated by make-jpkg would set
different alternatives priorities depending on the version of the SDK/JRE
that is being installed.
For example, I have generated .deb packages for both the 1.3 and 1.4 Sun
Package: alsa-base
Version: 1.0.8-2
Severity: normal
I took a look in /var/log/boot recently and I saw a bunch of errors from
the ALSA startup script:
Sun Jan 23 22:43:53 2005: bootlogd.
Sun Jan 23 22:43:53 2005: Activating swap.
Sun Jan 23 22:43:53 2005: Checking root file system...
Sun Jan 23 2
29 matches
Mail list logo