Bug#1064634: qemu-system-x86: possible race-condition in qemu nat layer or virtio-net

2024-02-26 Thread g1pi
> Please take it with upstream qemu, - eg, qemu-de...@nongnu.org mailing > list or qemu gitlab repository issue tracking. Reported to qemu-devel: https://lists.gnu.org/archive/html/qemu-devel/2024-02/msg05412.html g.b.

Bug#1040458: bookworm: please document that /etc/init.d/rsyslog is gone

2023-07-06 Thread g1pi
Hi, On Thu, Jul 06, 2023 at 10:18:39AM +0200, Paul Gevers wrote: > Hi, > > So something along the lines of: > > Hosts not running the default init system (systemd) should check if all > relevant services are restarted after the upgrade. Some packages have > stopped shipping their own init

Bug#1040364: orphan-sysvinit-scripts: add triggers to restart daemons

2023-07-05 Thread g1pi
On Wed, Jul 05, 2023 at 06:36:23PM +0200, Thorsten Glaser wrote: > On Wed, 5 Jul 2023, g...@libero.it wrote: > > This is bad. Let’s ask the debhelper maintainers why this > is no longer present, as the absence breaks orphan-sysvinit-scripts. > I'm not sure that breaks o-s-s. o-s-s has a

Bug#1040364: orphan-sysvinit-scripts: add triggers to restart daemons

2023-07-05 Thread g1pi
On Wed, Jul 05, 2023 at 04:39:33PM +0100, Matthew Vernon wrote: > > I'd normally expect a package postinst to > invoke-rc.d or similar. > Me too. But Bookworm disagrees. Release Notes don't even mention that rsyslogd does not start at boot anymore unless you use systemd. The section > #

Bug#1040364: orphan-sysvinit-scripts: add triggers to restart daemons

2023-07-04 Thread g1pi
On Wed, Jul 05, 2023 at 12:07:09AM +0200, Thorsten Glaser wrote: > > [...] > > for t in "$@"; do > > But I don’t think the trigger on the binary is necessary, > the trigger on the systemd thing would already catch it. > Right. I forgot to remove the binary from the triggers list after

Bug#950714: closed upstream

2020-02-06 Thread g1pi
tags 950714 + upstream thanks

Bug#835421: [Pkg-mutt-maintainers] Bug#835421: mutt: Bug in POP3 authentication via SASL mechanism DIGEST-MD5

2016-08-25 Thread g1pi
On Thu, Aug 25, 2016 at 04:13:24PM +, Antonio Radici wrote: > tag 835421 +pending > thanks > > Thanks for the patch, I will forward it upstream and if it's OK we will add it > to the next mutt release Sorry, I've already opened a ticket upstream too, but forgot to reference it:

Bug#745593: use the loader, Luke

2014-05-05 Thread g1pi
It seems very similar to #702605. A work-around: tell the loader to resolve all symbols at startup, via the LD_BIND_NOW environment variable. e.g.: env LD_BIND_NOW=1 icedove Currently I'm using lightning (not iceowl) and icedove does not crash. Regards, g1 -- To UNSUBSCRIBE,

Bug#731330: posted upstream

2013-12-06 Thread g1pi
at http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59406 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#702605: icedove does not start if ~/.icedove is empty.

2013-05-04 Thread g1pi
Hello On Sat, May 04, 2013 at 07:47:59PM +0200, Carsten Schoenert wrote: Hello, On Sat, Mar 09, 2013 at 04:56:18PM +0100, g...@libero.it wrote: [...] Do you remember at which point in time people started to submit bugs about random failures to load shared objects? I believe they

Bug#702605: icedove does not start if ~/.icedove is empty.

2013-03-09 Thread g1pi
On Sat, Mar 09, 2013 at 03:00:01PM +0100, Carsten Schoenert wrote: yes, mostly icedove is working with this little trick. The error happens because of some libc changes that comes with the new released version that was coming in the past into squeeze. We already talked about that issue and