Package: linux-source-2.6.12
Version: 2.6.12-10
Severity: minor
Attached is a small patch that fixes this potential minor confusion.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to
Package: libc6
Version: 2.3.5-7
Followup-For: Bug #327784
ldconfig is still broken in release 2.3.5-7.
The report for version 2.3.2.ds1-22 was to report that ldconfig was
*not* broken in that release.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy:
As a workaround to this problem, I've found using an older working version
of ldconfig with the newest libc6 debian packages will allow make apt
to work.
1 ) First, backup the broken ldconfig and make a soft link to it (even
though it doesn't deserve a backup).
$ cd /sbin
$ mv ldconfig ldconfig
Package: libc6
Version: 2.3.2.ds1-22
Followup-For: Bug #327784
I had an old .deb file for this version of libc6 and the bug does not
exist for ldconfig, it exits successfully.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architectu
On Sat, 15 Oct 2005, Romain Francoise wrote:
> Your patch removes this 'intelligence' and as a result, rcsdiff will
> always skip diff generation when the revisions are identical, which is
> wrong if the user specified -y or -D.
>
> The "bug" is that RCS considers a long option name as a case wher
Package: rcs
Version: 5.7-16
Severity: normal
Providing the rcsdiff command with a revision number and a symbolic
name for the same revision creates different error results depending on
whether the option is a long option or is either of the short options
"-DNAME" or "-Y".
Here is a recreatio
Package: libc6
Version: 2.3.5-6
Followup-For: Bug #327784
I was in the process of upgrading with aptitude and also ran into this
bug with ldconfig. It's a real nuisance. I recall, ldconfig bug was
failing for dpkg on the libuuid1 package, which consequently made me
lose an upgrade to e2fsprogs,
For those who missed the subject of the original bug report message, the
patch allows pdiff to read standard input when "-" is given as a filename.
Obviously, giving more than two "-" files is not checked, but the diff and
wdiff utilities do give these errors.
I'm pretty sure the patch doesn't con
Package: wdiff
Version: 0.5-14
Severity: normal
When giving a file device on the command-line for wdiff results in
missing data in the output. This can be avoided by saving the file to
a regular file and providing the file to wdiff rather than a device.
Perhaps wdiff is reading the file twice?
Package: a2ps
Version: 1:4.13b-4.2
Severity: wishlist
Pdiff doesn't accept data on standard input, only because the
alternative of using device files causes wdiff to fail (see
Bug#305898). A patch below provides support for this feature.
*** pdiff.diff
--- /usr/bin/pdiff 2004-12-05 13:12:1
10 matches
Mail list logo
