(Debian maintainer for gdnsd here)
Since this bug was filed, gdnsd acquired autopkgtests, that among other
things test that the package works in a clean container. In Debian, it
does, and 3.5.2-1 has migrated to bullseye and will be part of that
release. In Ubuntu, it does not because of this
** Changed in: geoipupdate (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772087
Title:
Base configuration doesn't work.
To manage
** Changed in: geoipupdate (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904797
Title:
geoipupdate fails with 40` HTML error
To manage
** Changed in: gdnsd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633806
Title:
package gdnsd 1.11.1-1 failed to install/upgrade: subprocess installed
** Changed in: gdnsd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707431
Title:
package gdnsd 2.2.0-1ubuntu1 failed to install/upgrade: subprocess
** Changed in: gdnsd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636926
Title:
package gdnsd 1.11.1-1 [modified: usr/bin/gdnsd_geoip_test
usr/sbin/gdnsd
** Changed in: jemalloc (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1333581
Title:
Segfault with Varnish 3.05 on Ubuntu 14.04 libjemalloc.so.1
** Changed in: jemalloc (Ubuntu)
Status: Triaged => Invalid
** Changed in: glibc (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714514
Title:
geoipupdate 4.6.0-1 (just landed in Debian) is documenting the new
behavior better, including a config file change, plus a README.Debian
adjustment.
** Changed in: geoipupdate (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
As the message says, a user account is required to run geoipupdate. This wasn't
always the case, but changed on Dec 30th, 2019 (over a year ago) which may be
why it surprised you:
https://blog.maxmind.com/2019/12/18/significant-changes-to-accessing-and-using-geolite2-databases/
geoipupdate
** Changed in: librdkafka (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903595
Title:
librdkafka1 several versions behind
To manage notifications about
Fixed upstream in 1.6.9 and 1.7.1+, which are part of all Ubuntu
releases (at least) since bionic/18.04
(Please file bugs against the Debian BTS in the future - this is where
the package's development happens, I don't monitor Launchpad bug reports
closely)
** Changed in: radsecproxy (Ubuntu)
rdkafka.pc in the right, multiarch location. (Closes:
#766759)
-- Faidon Liambotis parav...@debian.org Sun, 26 Oct 2014 06:47:07
+0200
librdkafka (0.8.5-1) unstable; urgency=medium
* New upstream release.
- Fixes kFreeBSD FTBFS.
* Ship rdkafka.pc pkg-config in librdkafka-dev.
-- Faidon
Tetsuo, see my comments above for the diagnosis of two different bugs.
I've already identified (b) as well and it's completely orthogonal to
the bug in question. No idea about (a), though, your comment is
interesting.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Pretty sure that's it. -12 is -ENOMEM, and there are two sites in that
commit that return -ENOMEM, right when we have an error message from the
failure to spawn the SCSI error handler thread.
Note that the oops/backtrace is a red herring. There is a secondary,
unrelated bug in the mptsas code
Well, Pierre gave the full output, so the answer to your question is yes
(that's really easy to verify).
The merge commit doesn't look like having any relevant code changes, so
this is a dead end.
I actually think that limiting to drivers/scsi was a bad idea from the
start. The v3.12..v3.13-rc1
We're also experiencing the same issue when booting the trusty installer
on a Dell PowerEdge R610 with a Dell SAS 6/iR controller (LSI SAS1068E),
resulting in the inability to install/run this system. This is an
extremely popular controller, prevalent in a signifcant portion of Dell
systems (or
** Bug watch added: Debian Bug tracker #647535
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647535
** Also affects: cheese (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647535
Importance: Unknown
Status: Unknown
--
You received this bug notification because
I'm also affected by this bug, but I'm using Debian, not Ubuntu :)
Crawling the web for this bug, I encountered this bug and the libv4l PPA
suggestion was particulary helpful (thanks!).
I've tried to find why and it seems that the libv4l PPA version links
against libjpeg62, while the Oneiric one
19 matches
Mail list logo
