Bug#1037233: .../odbc/statement.rb:89: warning: rb_tainted_str_new_cstr is deprecated

Package: ruby-odbc Version: 0.8-2 Severity: normal Tags: patch Dear Maintainer, As I mentioned at the end of: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941707 Using ruby-odbc under Bullseye's Ruby generates warnings of the deprecation of tainting, as can be demonstrated by running

Bug#941707: ruby-odbc: [RubyODBC]Cannot allocate SQLHENV (ODBC::Error)

Control: fixed 941707 0.8-2 The reproducer I gave here, which still seems reliable for me on Buster, doesn't reproduce the problem for me on Bullseye with 0.8-2, despite nothing in the change log at

Bug#1031650: lwm: description misspells "include"

Package: lwm Version: 1.2.2-6+b1 Severity: minor Dear Maintainer, Not the most interesting of bug reports, sorry, but the package Description tells me that lwm "doesn't iclude icons, icon docs, button bars or root menus"... or the "n" that I imagine was intended in "iclude". -- System

Bug#944139: debmirror archive.debian.org fails due to missing binary-all

The introducing commit suggested in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944139#15 doesn't look right to me. I had success reverting the active part of https://salsa.debian.org/debian/debmirror/-/commit/82bf56b2246bdf22470fd2751b359c82932c3833#81f3803dd9887f397ffdeebc8973c6de39a38df9

Bug#994728: libtirpc3:amd64: rpcbind stops replying to subnet broadcast CALLIT after one stray UDP datagram

On Sun, 19 Sep 2021 19:11:26 -0700 Martin Dorey wrote: > Package: libtirpc3 > Version: 1.1.4-0.4 My production occurrence was always on Stretch, but I'd thought that the patch might be more easily accepted against a less stale branch. It applies to Stretch too, where I've ju

Bug#999442: systemd: reproducible hang on upgrade, in try-restart systemd-networkd.service

After an upgrade to systemd 247.3-6~bpo10+1 from buster-backports, I can no longer reproduce the problem in 15+ minutes of trying, when it always took less than 1 minute before. I think it's fixed. Sorry for the noise. Starting at: https://bugzilla.redhat.com/show_bug.cgi?id=1845456

Bug#994728: libtirpc3:amd64: rpcbind stops replying to subnet broadcast CALLIT after one stray UDP datagram

Package: libtirpc3 Version: 1.1.4-0.4 Severity: normal Tags: patch Dear Maintainer, My NIS setup stops working occasionally. The clients rely on subnet broadcast CALLIT requests to locate the NIS servers. The rpcbind process on the NIS server sees the requests but fails to send the reply. The

Bug#981912: libsdes4j-java: provoked IDS to block download thinking it's Unix.Trojan.Chalubo

Package: libsdes4j-java Version: 1.1.4-1.1 Severity: normal Dear Maintainer, This isn't a bug in the package, just a warning about a problem getting the package. Our debmirror job has been failing: Download of pool/main/s/sdes4j/libsdes4j-java-doc_1.1.4-1.1_all.deb failed: 500 Status read

Bug#855662: fakeroot: when msgrcv is interrupted by a signal, faked accidentally reprocesses the previous message

I've no reason to think that the patch I supplied here, some years ago now, was anything but a good idea, but it seems that my coworker Susi Berrington has found the real cause of my pain. According to: https://github.com/systemd/systemd/issues/2039 (Change default value of RemoveIPC in

Bug#941619: ruby-odbc: ODBC dlopen regression in Debian 10

I've raised this bug again, in a hopefully more coherent way, as: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941707 ruby-odbc: [RubyODBC]Cannot allocate SQLHENV (ODBC::Error) Sorry for the noise.

Bug#941707: ruby-odbc: [RubyODBC]Cannot allocate SQLHENV (ODBC::Error)

Package: ruby-odbc Version: 0.8-1+b1 Severity: normal Tags: patch Dear Maintainer, ruby-odbc does this, at least for me, on Buster: martind@neutrino:~$ ruby -we 'require "odbc"; ODBC.drivers()' Traceback (most recent call last): 1: from -e:1:in `' -e:1:in `drivers': INTERN (0)

Bug#941564: /usr/lib/ruby/vendor_ruby/dbd/odbc/statement.rb:18: warning: constant ::Fixnum is deprecated

Package: ruby-dbd-odbc Version: 0.2.5+gem2deb-1 Severity: normal Dear Maintainer, On Buster, which has Ruby >= 2.4, I see a warning from the first call of execute() on an ODBC statement handle. I can reproduce this simply with: martind@neutrino:~$ ruby -e 'require "dbd/ODBC"; handle = nil;

Bug#870579: aren't CALLIT replies still going to come from a random port?

I've looked at the changes in 1.2.5-8 and I don't see how they'll make rpcbind reply from port 111 like portmap used to. If I'm right, then this bug isn't fixed yet. I just happened across a change that looks more hopeful to me:

Bug#909064: libc6:amd64: getaddrinfo AF_INET6 behaves differently with nscd

Package: libc6 Version: 2.19-18+deb8u10 Severity: normal Tags: upstream ipv6 patch Dear Maintainer, The behavior of the test program from https://bugzilla.redhat.com/show_bug.cgi?id=1416496 (titled "getaddrinfo() call returns wrong IPv6 address if nscd is used") when asked to return the IPv6

Bug#895946: rake: LoadError from Get::Ext::RakeBuilder trying to find rake

Looking into this further, I see that it's just a particular case of a more general problem: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710814 rubygems-integration: fails to override bin_path The raiser, nearly five years ago, appeared more confident than I am about where the solution

Bug#895946: rake: LoadError from Get::Ext::RakeBuilder trying to find rake

Package: rake Version: 10.5.0-2 Severity: normal Dear Maintainer, Installing a gem that contains mkrf_conf, for example the three year old "beta" of unf, causes rubygems/ext/builder.rb to take its RakeBuilder code path, rather than, for example, the ExtConfBuilder path that the last "release"

Bug#759533: alien: Converted rpm won't be installed on Fedora system

Following a similar report , I found that much the same thing has been reported upstream as Generated RPM files un-necessarily conflict with package "filesystem" .

Bug#856439: fakeroot doesn't detect and handle message queue and semaphore id collision

On Fri, 3 Mar 2017 02:13:08 + Martin Dorey <martin.do...@hds.com> wrote: > I see a flaw in my patch that could lead to it closing the same id twice if > it has to retry twice - I should have reset the ids after cleanup(). Please find the fixed patch belatedly attached. The p

Bug#869705: debmirror: dists/wheezy-proposed-updates/Release fails gpg validation

tags 869705 fixed stop The last record I have of these errors was 2017-07-30. The times on the Release and Release.gpg files at http://ftp.debian.org/debian/dists/wheezy-proposed-updates/ are now the same. Sorry for the noise.

Bug#650425: Please add options to set the port range for nfs clients

Christoph Anton Mitterer wrote, regarding rpcbind, some four years ago: > It seems to always reserve one random (not 873) port in addition... why > does it do so at all? I think it's used to make remote "callit" requests, to receive their asynchronous replies and to forward those replies onto

Bug#870579: rpcbind callit replies from a random reserved udp port, making firewalling hard

Package: rpcbind Version: 0.2.0-8 Severity: normal Dear Maintainer, I just upgraded a NIS server from Squeeze to Wheezy, hence from portmap to rpcbind. Yes, I know it's 2017 and there's Jessie, if not Stretch :). Some of that server's clients stopped being able to find it with ypbind's

Bug#869705: debmirror: dists/wheezy-proposed-updates/Release fails gpg validation

Package: debmirror Version: 1:2.25 Severity: normal Dear Maintainer, Bad me - I'm deliberately raising this bug against the wrong package. My Google fu has been too weak to determine how to report problems with the archive. Colin's always been so helpful in the past. I'm sorry for abusing his

Bug#863007: half a gig of nonsense in /usr/share/doc/openjdk-7-jre-headless/test-amd64

This is probably a useless me-too. Sorry if so, but there aren't any yet, so it might look like it's only the OP. It's not. I saw the same on two machines today, the smaller upgrade being from 7u121-2.6.8-2~deb8u1 to 7u131-2.6.9-2~deb8u1. My attention was drawn to the system by the

Bug#866238: debmirror: failed to remove stale InRelease file for Stretch

Package: debmirror Version: 1:2.25 Severity: normal Dear Colin and co, Before manual intervention to work around this issue, our two Debian mirrors had files debian/dists/stretch/InRelease, starting like this: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Origin: Debian Label: Debian Suite:

Bug#856439: fakeroot doesn't detect and handle message queue and semaphore id collision

I've had a failure with the same symptom from a patched build. I see a flaw in my patch that could lead to it closing the same id twice if it has to retry twice - I should have reset the ids after cleanup(). I don't see how that could explain the remaining issue. Perhaps there's something

Bug#855662: fakeroot: when msgrcv is interrupted by a signal, faked accidentally reprocesses the previous message

> A new bug is better Agreed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856439 ( fakeroot doesn't detect and handle message queue and semaphore id collision

Bug#856439: fakeroot doesn't detect and handle message queue and semaphore id collision

Package: fakeroot Version: 1.20.2-1 Severity: normal Tags: patch Dear Maintainer, I'm raising this as requested by Clint in: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855662#15 Fixing that bug (fakeroot: when msgrcv is interrupted by a signal, faked accidentally reprocesses the

Bug#855662: fakeroot: when msgrcv is interrupted by a signal, faked accidentally reprocesses the previous message

> Good luck. Sadly, after several days of parallel package building later, I've had another failure. Happily, now errno's been preserved by my previous patch, I have A New Clue: FAKEROOT: r=-1, received message type=1, message=3 FAKEROOT, get_msg: Identifier removed errno=43, EINTR=4 On this

Bug#855662: fakeroot: when msgrcv is interrupted by a signal, faked accidentally reprocesses the previous message

Package: fakeroot Version: 1.20.2-1 Severity: normal Tags: patch Dear Maintainer, I'm trying to track down an intermittent failure that originally presented like this: dh_md5sums dh_builddeb -- -Znone dpkg-deb: building package `mercury-main-4604p00p1099' in

Bug#855441: tigervnc-xorg-extension redraw issues

Package: tigervnc-xorg-extension Version: 1.7.0+dfsg-2 Severity: normal Dear Maintainer, I'd really like to be able to connect to :0 on my work computer from home. I used to do that with vino and gnome-fallback on Wheezy. The full Gnome 3 experience is slow and generates several Mbit/s of

Bug#855350: tigervnc-xorg-extension: Loading the tigervnc the extension makes the x server practically unusable

> i could not find a way to actually pass options I eventually managed to get a default configured Stretch box to accept a remote connection using: mad@shuttle:~$ cat /usr/share/X11/xorg.conf.d/75-vnc-mad.conf Section "Device" Identifier "Device" EndSection Section "Screen" Identifier "Screen"

Bug#851842: [Pkg-tigervnc-devel] Bug#851842: Bug#851842: Bug#851842: tigervnc-xorg-extension - libvnc.so fails to load with undefined symbol: gnutls_bye

Does a patch --dry-run after the build offer to use -R? I bet not, meaning the patch has been lost. Upstream's intention is to patch files that are generated.

Bug#851842: [Pkg-tigervnc-devel] Bug#851842: tigervnc-xorg-extension - libvnc.so fails to load with undefined symbol: gnutls_bye

On Fri, 20 Jan 2017 22:10:29 +0100 Ola Lundqvist wrote: > I have now been able to reproduce the problem. It is not solved by > merely adding more dependencies. I have to look further to find the > cause of the problem. Hey Ola, I think I can help. First, though, I'm delighted

Bug#737155: work-around for ntpq -p truncation

I think we can call this fixed by upstream's addition of support for -w: (4.2.7p461) 2014/08/14 Released by Harlan Stenn * [Bug 1128] ntpq truncates "remote" host information. https://bugs.ntp.org/show_bug.cgi?id=1128: ntpq -n output truncates IPv6 addresses ... perhaps taking

Bug#831322: debmirror consistently failing on unlink step for files in dep11 directory

Not the same file every day and a second run immediately after the first failure succeeds for me, on the three occurrences that I've noticed so far, making it just a minor issue for me. It might have been happening to me every day for a while but any earlier failures will have been obscured by

Bug#827132: debhelper: make-4.2 renamed --jobserver-fds to --jobserver-auth causing parallel build issues

Package: debhelper Version: 9.20120909 Severity: normal Dear Maintainer, The make-4.2 announcement at https://lists.gnu.org/archive/html/info-gnu/2016-05/msg00013.html includes [ * The interface to GNU make's "jobserver" is stable as documented in the manual, for tools which may want to

Bug#654924: Re: Helping with tigervnc 1.5.0

I'm concerned why /etc/vnc.conf and /usr/bin/tigervncserver set a depth of 32. Per man Xtigervnc, that will cause problems for applications, problems that I've just described in a little more detail at http://stackoverflow.com/a/37428300/18096. I think it should be 24, a setting which

Bug#654924: Helping with tigervnc 1.5.0

On Tue, 26 Jan 2016 11:42:22 -0500 Geoffrey Thomas wrote: > ... I > built tigervnc 1.5.0 from git (4a25ccd) on jessie, with a no-change > backport of fltk1.3 1.3.3-6 Thanks for this encouraging post. Sadly, the build on Jessie seems to have broken since. This fixed

Bug#737155: work-around for ntpq -p truncation

Looks like this was discussed upstream under https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/325111, which contains a readvar work-around.

Bug#635317: now believed addressed upstream

http://savannah.gnu.org/bugs/?33034 was closed with http://git.savannah.gnu.org/cgit/make.git/commit/?id=53b4a9e66800dde643d3ce7966c5193001e3f12e, which seems to address the problem sufficiently in limited testing in my Debian environment. I imagine it will now be challenging to get several years

Bug#665408: tzdata: San Luis and Cairo wrongly show UTC

Package: tzdata Version: 2011n-0lenny1 Severity: normal On a server with tzdata 2009l-0lenny1: dsatow@mercury11:~$ LANG= TZ=America/Argentina/San_Luis date Thu Mar 22 21:41:43 WART 2012 dsatow@mercury11:~$ LANG= TZ=Africa/Cairo date Fri Mar 23 03:41:55 EET 2012 dsatow@mercury11:~$ On a server

Bug#638256: race condition causes many syslog messages: File a[[:xdigit:]]{13} is in wrong format - aborting

Package: at Version: 3.1.10.2 Severity: normal Tags: patch In my experience, when a file system fills up, it often seems that there's room in the inode table when there's no room for file bodies. Unintentionally empty files become common. If /var/spool/cron/atjobs ends up containing a

Bug#628178: html2text: -width -1 is accepted but causes a crash with some Html

Package: html2text Version: 1.3.2a-5 Severity: normal Nowhere in the man page does it suggest that -width -1 is legal, so why am I using it? Well, it seemed to work for me in one application, and saved my having to pick a magic number. After all, html2text didn't say it was a usage error. Then

Bug#616502: dpkg: malloc failed (-1739558537 bytes): Cannot allocate memory for file = 2 GiB

Package: dpkg Version: 1.14.25 Severity: wishlist Tags: patch A debug version, packaged in the wrong way with embedded debugging information, of a non-Free and non-free, amd64-specific package contains a file whose size is larger than 2 GiB. With the patched dpkg and full --debug output, I see

Bug#587587: insserv: Starting nxserver depends on rmnologin and therefore on system facility `$all' which can not be true!

Petter's suggested fix worked for me too, thanks, digging me out of this hole: Accept this solution? [Y/n/q/?] The following NEW packages will be installed: samba-dbg The following packages will be upgraded: libwbclient0 samba samba-common samba-doc smbclient swat winbind 7 packages upgraded,

Bug#571652: exuberant-ctags: endless loop on unmatched { in makefile

Package: exuberant-ctags Version: 1:5.7-4 Severity: normal Tags: patch Test case: mart...@whitewater:/tmp$ echo -n { Makefile mart...@whitewater:/tmp$ /usr/bin/ctags-exuberant Makefile (doesn't terminate) Where it gets stuck: (gdb) bt #0 0x7ff276a7d960 in read () from /lib/libc.so.6 #1

Bug#499826: totem: Allow screensaver to activate: checkbox has reversed meaning

Fantastic - this bug gives me a work-around for https://bugs.launchpad.net/ubuntu/+source/xine-lib/+bug/216939. That had been driving me nuts when using totem-xine concurrently with rdesktop or vncviewer to a Windows box. Simply uncheck the box which looks like it should be checked. No need for

Bug#534408: debian-policy: Installed-Size is defined as kilobytes but dpkg-gencontrol fills it in with kibibytes

Package: debian-policy Version: 3.7.2.2 Severity: minor debian-policy appears to define Installed-Size's units as thousands of bytes: 5.6.20 Installed-Size This field appears in the control files of binary packages, and in the Packages files. It gives the total amount of disk space required

Bug#531078: socat: execs children with SIGCHLD ignored

Thanks, that's very gracious. Today we tripped over a real symptom of this problem. When running via socat: mart...@mercury1-a:~$ sudo dpkg -i ~/software.jessies.org/work/evergreen/.generated/amd64_Linux/bin/org.jes sies.evergreen_5.204.2884_amd64.deb dpkg: unrecoverable fatal error, aborting:

Bug#531078: socat: execs children with SIGCHLD ignored

Package: socat Version: 1.4.3.1-1 Severity: normal Tags: patch I don't currently know that I'm experiencing any symptom of this, other than a warning generated by what I'm told is an obsolete warning flag to Perl. mart...@whitewater:~$ perl -we 0 mart...@whitewater:~$ socat - EXEC:'perl -we 0'

Bug#481512: libmagic1: couldn't open file doesn't say which file or why

Package: file Version: 4.24-2 Severity: normal Tags: patch This change in magic.c, introduced between 4.23 and 4.24, caused a backup job of ours to produce a large number of mysterious messages saying couldn't open file. It took quite some digging to work out (from find /usr/lib -type f | xargs

Bug#481523: libmagic1: file_error_core causes crash in vasprintf

Package: file Version: 4.24-2 Severity: normal Tags: patch When I made my original change suggested in Bug#481512 (libmagic1: couldn't open file doesn't say which file or why), I ran into a crash in strlen from vasprintf caused by a regression introduced between 4.23 and 4.24 upstream, in the

Bug#456259: wget aborts on negative length

This is probably fixed upstream per http://www.mail-archive.com/wget%40sunsite.dk/msg10697.html. I didn't refer to the upstream changes in making the patch submitted with this bug, so it would probably be a bad idea to apply my patch.

Bug#456259: wget: aborts with no message when http server returns negative size

Package: wget Version: 1.10.2-2 Severity: normal Tags: patch Note the negative length returned by my http server here. The file's larger than 2GiB and I'm sure there's a server bug there. But wget could easily handle it more gracefully - all the code for doing so is there. First, though, here's

Bug#450396: libdbi-ruby1.8: DBI.available_drivers() always empty

Package: libdbi-ruby1.8 Version: 0.1.1-1 Severity: normal Tags: patch $ ruby -e 'require dbi;puts(DBI.available_drivers())' $ dpkg --listfiles libdbd-odbc-ruby1.8 | grep ODBC.rb /usr/lib/ruby/1.8/DBD/ODBC/ODBC.rb $ dpkg --listfiles libdbi-ruby1.8 | grep dbi.rb /usr/lib/ruby/1.8/dbi.rb $ diff -u

Bug#404131: Me too

For what little it's worth, I'm seeing the same behavior on two Debian boxes, each with one statically configured interface. $ sudo nm-tool NetworkManager Tool State: disconnected print_devices(): didn't get a reply from NetworkManager. There are no available network devices. $ $

Bug#404131: Me too

Don't run Network Manager with a statically configure interface, it's not supported by Network Manager. I'm not trying to run Network Manager to *manage* a statically configured interface. I was just trying to run Network Manager while I had a statically configured interface. What actually

Bug#409988: xserver-xorg: upgrade from xfree86 sarge failed with 'Can't call method choices on an undefined value'

Package: xserver-xorg Version: 1:7.1.0-11 Severity: normal Upgrading from sarge (where I guess we were using xfree86) to etch failed with: Setting up xserver-xorg (7.1.0-11) ... xserver-xorg postinst warning: Migrating xserver-xfree86 debconf values to xserver-xorg. Can't call method choices

Bug#409988: Acknowledgement (xserver-xorg: upgrade from xfree86 sarge failed with 'Can't call method choices on an undefined value')

This incorrectly indented, tasteless, dangerous hack: $ diff -u /usr/share/perl5/Debconf/Question.pm /net/gollum/usr/ share/perl5/Debconf/Question.pm --- /usr/share/perl5/Debconf/Question.pm2006-12-20 11:31:31.0 -0800 +++ /net/gollum/usr/share/perl5/Debconf/Question.pm

Bug#409101: discover-data: fails to find any display devices

Package: discover-data Version: 2.2007.01.21 Severity: normal Recently there was a change: diff -r 2.2006.12.28/lib/discover/pci-busclass.xml 2.2007.01.21/lib/discover/pci-busclass.xml 19,20c19,20 busclass id=0280 name=network/ busclass id=0300 name=display/ --- busclass id=0280

Bug#392849: free(): invalid pointer every time I quit

Package: zinf Version: 2.2.5-5.2 Severity: normal Every time I quit, I see a message like: *** glibc detected *** free(): invalid pointer: 0xa574f0e0 *** If I run zinf from gdb, I get: *** glibc detected *** free(): invalid pointer: 0xa574f0e0 *** Program received signal SIGABRT, Aborted.

Bug#386641: closed by Mark Brown [EMAIL PROTECTED] (Bug#386641: fixed in nis 3.17-1)

I tested 3.17-2 with sudo kill -PIPE and saw that it didn't die, whereas nis from sarge did die. Looking at the source, though, I think Mark Brown just applied my first patch. man 2 clone suggests that the signal handling thread will be ignoring SIGPIPE, inheriting that setting from the main

Bug#386641: nis: ypbind dies with SIGPIPE when NIS server unreachable

I'm afraid I was rushing my patch on Friday evening and my ypbind died, probably the same way as previously, over the weekend. I was missing a line adding SIGPIPE to the sigs_to_catch in the signal handling thread, not just the sigs_to_block in the main thread. I've attached an updated patch

Bug#386641: nis: ypbind dies with SIGPIPE when NIS server unreachable

Package: nis Version: 3.16-2 Severity: normal Tags: patch When our NIS server becomes unavailable, all of our NIS clients die a few minutes later. I strace()d one on a deliberate outage and found that it died with SIGPIPE. Here's an extract from the strace output and a suggestion for a patch.

Bug#386489: aptitude: show ~nsun-java5 only lists sun-java5-bin

Package: aptitude Version: 0.4.3-1 Severity: normal aptitude install ~nsun-java5 gives at least every appearance of installing all of: sun-java5-bin - Sun Java(TM) Runtime Environment (JRE) 5.0 sun-java5-demo - Sun Java(TM) Development Kit (JDK) 5.0 demos and examples sun-java5-doc - Sun JDK(TM)

Bug#386489: aptitude: show ~nsun-java5 only lists sun-java5-bin

tags 386489 patch This seems to fix it for me, perhaps in the intended manner, although I've probably indented it all wrongly. --- /tmp/cmdline_show.cc.orig 2006-09-07 17:51:21.0 -0700 +++ /tmp/cmdline_show.cc.new2006-09-07 17:50:40.0 -0700 @@ -535,7 +535,8 @@

Bug#384135: linux-image-2.6.17-2-686: description doesn't mention new support for SMP

Package: linux-image-2.6.17-2-686 Version: 2.6.17-6 Severity: minor It seems unfortunate that the package description doesn't mention that you no longer need a -smp kernel to support hyperthreading. I'd deferred upgrading for some time because I was waiting for a package I no longer need. The

Bug#316378: autofs: Deadlock causes automount failure

I ran into this too and spammed the autofs list. Joe Pruett points me at http://www.mail-archive.com/autofs@linux.kernel.org/msg05016.html, in which Ian Kent suggests disabling the autofs locking, providing that mount locks mtab properly. Does Debian's mount do that?

Bug#316378: autofs: Deadlock causes automount failure

martin Ian Kent suggests disabling the autofs locking, providing that martin mount locks mtab properly. Does Debian's mount do that? steinar strace seems to indicate that it does: Cool. I have *no* idea what I'm doing here but... [EMAIL PROTECTED]:/tmp$ apt-get source autofs [EMAIL

Bug#366659: dpkg-dev: usage error goes to stdout instead of stderr

Package: dpkg-dev Version: 1.13.19 Severity: minor Tags: patch I redirected the output of dpkg-scanpackages into a Packages file but a usage error was produced, which I then didn't see. This confused me, not to mention apt-get. $ dpkg-scanpackages /dev/null $ Patched version: $

Bug#365120: tic: undefined symbol: _tracef

Package: ncurses-bin Version: 5.5-1.1 Severity: minor With -v levels above 1, tic fails with a message as below: [EMAIL PROTECTED]:/tmp$ infocmp term.tic [EMAIL PROTECTED]:/tmp$ tic -v2 term.tic term.tic, line 2, 'xterm' tic: symbol lookup error: tic: undefined symbol: _tracef [EMAIL

Bug#357515: flex: project web page location doesn't work

Package: flex Version: 2.5.33-2 Severity: minor The Description field displayed by (eg) dpkg --status flex says: The project web page is at http://lex.sf.net/ That doesn't work, at least not or me and at the moment. http://flex.sf.net/ works and seems more plausible. -- System Information:

Bug#348008: man-db: --quiet doesn't Produce no warnings as the man page claims

Package: man-db Version: 2.4.3-3 Severity: minor man mandb says: -q, --quiet Produce no warnings. /etc/cron.daily/man-db says: start-stop-daemon --start --pidfile /dev/null \ --startas /usr/bin/mandb --oknodo --chuid man \

Bug#343274: x2vnc: selection cannot be pasted into Java applications on amd64

Package: x2vnc Version: 1.6-3 Severity: normal Tags: patch I mailed Ola to say (paraphrasing a little): A coworker recently tried to use x2vnc on an amd64 and ran into another problem with the same line of code as was behind Bug#191697. Upstream's accepted (but not yet released) a patch I

Bug#341200: rxvt: selection cannot be pasted into Java applications on amd64

Package: rxvt Version: 1:2.6.4-9 Severity: normal Tags: patch When pasting the X11 selection into Sun's Java implementation, specifically: java version 1.5.0_05 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_05-b05) Java HotSpot(TM) Client VM (build 1.5.0_05-b05, mixed mode,