Subject: Missing version dependency on libuv1
Package: bind9
X-Debbugs-Cc: d...@galexander.org
Version: 1:9.19.19-1
Severity: normal
I used "apt install" to upgrade bind9:amd64 to version 1:9.19.19-1.
apt failed and then I got this error from everything bind-related, such
as dig in
I updated to 3.04+git20210103-2 amd64, and it's usable again! I am still
using continuousView. Memory usage remained below 150MB even after
extensively navigating a large PDF.
Thank you! This is a big improvement in usability for me.
- Greg
On Thu, Mar 04, 2021 at 07:05:55AM +0100, Florian
Package: isc-dhcp-client
Version: 4.4.1-2.1+b2
Severity: normal
Dear Maintainer,
I believe I have found the exact bug anticipated by Sven Ulland in his
fix for #834532. Here is a quote from his report:
> A problem remains: If dhclient is terminated and started again, it starts with
>
I experience this same problem. When browsing around the end of an 800
page PDF, xpdf will consume 250MB/sec! Also, it is very slow. I have
manually downgraded xpdf from 3.04-13 several times on different
computers because of this bug. Is xpdf abandoned? I understand if it's
difficult to
Hi again - Sorry I had a problem and didn't check if this bug is already
listed. It may be the same as bug #250626. I'm not clear on how to
merge it so I'll leave that for someone else if it's appropriate.
However, this bug should not be given severity of "wishlist", it occurred
on a normal
severity 792394 important
tags 792394 patch ipv6
Hi! I ran into this same problem. The patch
07-dual-family-transport.patch changed it to use host order instead of
network order when sending the UDP port number to the remote host.
Background: When a vtun client connects, it first connects on a
Package: grub-common
Version: 2.02+dfsg1-4
Severity: important
Dear Maintainer,
I upgraded from an old version of grub using Debian's
"apt-get install grub-pc", and it overwrote my /boot/grub/grub.cfg
without prompting me, and without making a backup copy. My old grub.cfg
was hand-crafted,
Hi Michael -
Thanks for the attempt to remedy.
My problem is I start my VPN (openvpn) from /etc/rc.local, from
/etc/acpi/actions/lm_lid.sh, and from su under a regular user shell
(getty -> bash -> xinit -> rxvt -> bash -> su), depending on the
situation. I have used the same shell script for
Package: systemd
Version: 232-22
Severity: important
Dear Maintainer,
My specific problem is that systemd doesn't umount NFS before killing the
network, which has previously been reported in Oct 2015 as Debian bug
#800707, has not been fixed, and has been bumped several times by other
users
Package: libxrandr-dev
Version: 2:1.5.1-1
Severity: important
Dear Maintainer,
The pkg-config file for libxrandr-dev
(/usr/lib/arm-linux-gnueabihf/pkgconfig/xrandr.pc on my computer)
contains this line:
Requires: xproto randrproto >= 1.5
But the apt info for it (/var/lib/apt/lists/
Package: libgdk-pixbuf2.0-0
Version: 2.32.3-1.2
Severity: important
Dear Maintainer,
This is a version interaction between several packages, so I'm sorry if
libgdk isn't really where it belongs. I labelled it important because
the interaction renders many other packages unusable, but the bug is
Package: bitlbee
Version: 3.2.1+otr4-1
Severity: important
Dear Maintainer,
Upgrading the bitlbee packages to 3.2.1+otr4-1 lead to *all* messages to
non-OTR peers to be *silently* dropped. Seriously. I believe this is
the same bug as:
http://bugs.bitlbee.org/bitlbee/ticket/1109
You'll no
Control: severity -1 grave
You are wrong. Debian is very good about supporting an indefinite
upgrade path. It is *the* useful feature of Debian. I have been using
Debian since 0.93rc6 and I have only re-installed from scratch once in
that entire time period. I have this debate with about one
*SNAP SALUTE*
Okay, do a little survey, since you seem to be proud of your connections
within the Debian community.
Next time you're chatting with your friends in high places, ask them
if they religiously apt-get upgrade every box for for every new release,
or if Debian is generally able to
Consider the different path taken by the texinfo project:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709443
We're seeing a reasonable number of these sorts of failures in
#debian over the past few days.
I'm not wrong about the desire within the Debian community to use the
dependency
Control: severity -1 grave
Hi guys -
The fact that some systems have been specifically found to have
dpkg 1.15.something installed is not a reason to demote this bug.
My system happened to have dpkg 1.probablyalotolderthan15 installed, and
it failed on this bug. apt-get would not upgrade mutt
Package: mysql-server-5.5
Version: 5.5.24+dfsg-2
Severity: important
Dear Maintainer,
Upon upgrading to mysql-server-5.5, I find that /var/run/mysqld has been
needlessly renamed to /run/mysqld.
Pointless renaming is considered harmful!
You forgot to update a few things when you performed this
the mysql-5.5
package). However libdbd-mysql-perl has not yet been binNMU'ed so that
would be why that is picking up the old location.
If you have any more information please let me know. Otherwise can I
close the ticket?
On 07/06/12 18:10, Greg Alexander wrote:
Package: mysql-server
Hi -
I use Debian specifically because it upgrades cleanly from antiquity.
I've never reinstalled Debian from scratch except when buying all-new
hardware, and usually not even then. I had a computer from Debian
0.93rc6 to woody, and several others from woody to present day.
So this problem
I'm a dissatisfied debian user. My machine just auto-upgraded xpdf for
no particular reason. This auto-upgrade indicates that the package must
be maintained. However, the upgrade reintroduced this bug that i had
painstakingly patched on my local machine, even though debian bug tracker
has been
Package: mpg321
Version: 0.2.13-2
Severity: normal
This is a repeat of bug #286176, which was either never fixed or broken
immediately thereafter.
The mpg321 man page says, of -a:
For -o alsa, specify card:device; defaults to 0:0.
Without -o, the default is ao_default_driver_id(). With -o
Package: boa
Version: 0.94.14rc21-3.1
Severity: wishlist
Tags: upstream
Sorry if this is not the correct venue for this request...it seems the
upstream maintainer has abandoned it?
Anyways, I have some CGI which relies (*sigh*) on using ';' to separate
the query string rather than '?', as in:
Hi -
I encounter this bug with some frequency as I use continuous view as a
default setting in my .xpdfrc (continuousView yes). It reproduces
readily for me with a 32-bit x86 3.02-11 xpdf, using the PLRM.pdf.
I have been able to trigger the same failure mode outside of continuous
mode, but it is
I have determined that rndc hangs (for reconfig or for stop, probably for
anything) whenever the 'lo' interface is down. This poses a particular
problem because /etc/init.d/bind9 stop and /etc/network/if-down.d/bind9
both use rndc to control bind, and on my system both happen to be
executed after
Package: udev
Version: 146-5
udev 146-5 was installed as a result of dependencies while I was
upgrading my computer. I happened to be in the process of installing a
new kernel that had inotify support, but I was at the moment running a
kernel without inotify support. The udev preinstall script
Thank you for your response!
Older versions of udev would complain on startup about missing inotify
support, but would (mostly) function. This is the correct behavior, as
This one does not and me and the upstream maintainer are not interested
in revisiting this design decision.
This is
Hello -
If the next version of glibc stopped running under the Linux kernel,
period, would you also tag it upstream wontfix?
Seriously guys, when the glibc people make a big mistake like this,
you are not distributing a working distribution when you follow their
lead. upstream is not a carte
My mistake! I forgot that I was using Windows!
I will never again forget that newer = better and works = wrong, thank
you for the thorough schooling.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Judging by the volume of responses, I'll assume I've hit a nerve.
You all are aware that what is happening with glibc is unfriendly but
you're not sure why.
The reason why is that libc6 is not a random package which you can
individually decide to upgrade or not upgrade, it is a critical base
Hello,
Please, people, stop accepting that this package has to be
unnecessarily feature poor.
Here is the state of things in the unzip 5.52-8 debian package:
(a) files 2GByes
(b) files 2GB 4GB no
(c) files 4GBno
Here is the state of things after Paul Slootman's patch:
We are hungry today. Worry about tomorrow when it gets here.
I am trying to improve the Debian distribution so that its unzip
utility is at least as powerful as Windows'.
Thanks,
- Greg
On Sat, Dec 31, 2005 at 05:56:28PM +0100, Santiago Vila wrote:
On Sat, 31 Dec 2005, Greg Alexander wrote
Hello -
I am writing in regards to bug #192253 on bugs.debian.org,
reporting that unzip cannot handle 2GB-4GB zip files.
A patch to fix this problem is provided in 2003 by Paul Slootman.
The upstream version has not been updated to correct this problem,
and it appears that debian is waiting on
32 matches
Mail list logo
