Hmm. This is a complex one. The addresses of local variables are
always non-NULL, as required by the C/C++ standards (and common
sense). And its often the case explicitly testing this in code
indicates a potential logic error, assert (hwparams) instead of
assert (hwparams) for example.
This problem persists in squeeze. IMHO, it needs to have a higher
priority! Corrupting mailboxes is not cool.
Cheers, Ben
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Fri, Mar 04, 2011 at 01:18:52PM +0100, Jonas Smedegaard wrote:
Is this issue so severe that we should consider ripping out the
daemons also from the stable release of Debian?
I think so, yes. If it had been removed earlier, it would have
prompted me to seek out a newer/better IMAP server.
On Sat, Mar 05, 2011 at 01:23:21AM +0100, Jonas Smedegaard wrote:
...there's obviously also the approach of actually reading the full
bugreport (as I did only after replying to your earlier post) and
try follow one of the solutions proposed by Mike Young.
For the record, tried all of the
Hi.
Please find attached a patch to add config.guess support for the ARM
hard-float gnueabi variant (armhf, arm-*-linux-gnueabihf).
This is fine, thanks.
Ben
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Tue, May 10, 2011 at 04:20:29PM -0300, Henrique de Moraes Holschuh wrote:
Should you accept the patch, I'd appreciate if you could email me a
notice when it gets pushed to your public git repository.
Done.
Ben
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
Thanks, using the WSGI method works much better (and is probably
preferrable).
Cheers,
Ben
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: radicale
Version: 0.6.4
Severity: grave
Justification: renders package unusable
After a while (days), the radicale server no longer negotiates SSL connections
with clients. openssl s_client shows CONNECTED, but no certificate is sent.
This only happens on the IPv4 interface, not IPv6.
Package: python-radicale
Version: 0.6.4-1
Severity: normal
The version of python-radicale in stable depends on a version of Python (=
2.6.6-7~)
that is not available in stable. Is this dependency really accurate? Can
python-radicale
really not run under Python 2.6.6-3+squeeze6?
-- System
Package: sysvinit-utils
Version: 2.88dsf-34
Severity: normal
Dear Maintainer,
When running last(1), IPv6 addresses are truncated, eg:
bje pts/02402:b800:7003:7 Sat Feb 2 10:07 - 10:07 (00:00)
It would be nice if these could be shown in full.
-- System Information:
Debian
On Mon, Feb 04, 2013 at 12:31:34AM +, Roger Leigh wrote:
I think this is just a limitation of the field width for this output
format--it's not IPv6 related as far as I can tell. Does last -a
look better?
Yes, the addresses are printed correctly when -a is used.
Cheers, Ben
--
To
On Sun, Feb 24, 2013 at 12:35:56AM +, Roger Leigh wrote:
If you're happy with using -a, do you mind if this bug is closed?
Fine with me. It's really no different to displaying a very long
domain name.
Cheers, Ben
signature.asc
Description: Digital signature
Package: debianutils
Version: 4.4+b1
Severity: normal
Dear Maintainer,
The which(1) man page says: "It does not follow symbolic links". However
`which' does in fact:
$ ln -s /usr/bin link
$ export PATH=~/link:$PATH
$ which uptime
/home/bje/link/uptime
In a modern Linux system, not following
Package: mutt
Version: 1.8.3+neomutt20170609-2
Severity: important
Dear Maintainer,
Mutt segfaults, intermittently, when paging through a message. It happens
several times a week, so hardly a rare occurrence.
* What outcome did you expect instead?
No segfault.
I upgraded to the latest
Package: mailman
Version: 1:2.1.23-1+deb9u1
Severity: important
Dear Maintainer,
At some point (not necessarily the most recent Mailman update), list traffic
has been shunted due to the following exception:
Oct 14 10:56:46 2017 (5640) SHUNTING:
Package: mutt
Version: 1.8.3+neomutt20170609-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
mutt is corrupting my mbox when writing back the mbox after deleting messages
(and quiting mutt). I have a partial message in the start of the mbox, which
makes mutt unable to
Hi Ellmar
> > mutt is corrupting my mbox when writing back the mbox after deleting
> > messages
> > (and quiting mutt). I have a partial message in the start of the mbox,
> > which
> > makes mutt unable to read any of the messages in the mbox.
>
> The following predication I don't understand?
On Thu, Oct 05, 2017 at 11:00:10PM +0200, Elimar Riesebieter wrote:
> How does the corruption looks like?
One partial message in my mbox, then a From line for the start of the
next message, and the rest of the mbox is OK.
> Well, is it possible to open your mbox?
Yes, but not in mutt.
> Maybe
As a workaround, I have switched to using the IMAP server that runs on
localhost.
signature.asc
Description: PGP signature
Package: radvd
Version: 1:2.16-1
Severity: important
Tags: ipv6
Dear Maintainer,
radvd is not starting on system boot (which runs systed). However, once
the system is running, 'service radvd start' works fine. I confirmed this
by grepping /var/log/daemon.log:
Dec 4 16:19:11 mailhub
Package: src:linux
Version: 4.9.88-1
Severity: normal
Dear Maintainer,
For several weeks I have been experiencing hard lockups of my system (running a
Via C7 CPU).
When the system locks up, there is no panic message on the console,
numlock/caps lock are
inoperative, and a hard reset is the
I fixed this problem by running: systemctl enable radvd. This created
a new sym link that was not present before:
/etc/systemd/system/multi-user.target.wants/radvd.service ->
/lib/systemd/system/radvd.service
My problem is now fixed, but is this a problem with the packaging or
was this just a
After weeks of troubleshooting, I have come to the conclusion that
Debian kernels no longer work on the Via C7. Even newly available
motherboards were released over 6 years ago.
On Wed, Feb 28, 2018 at 03:55:57PM +0100, Thorsten Glaser wrote:
> I really have no other idea that???s in scope. After all,
> CC_FOR_BUILD is the *only* tool guaranteed to correspond to the
> target (in FreeWRT speak; --build= in GNU autotools speak) system.
We're trying to guess the build
Package: autotools-dev
Severity: normal
Dear Maintainer,
The upstream config.guess/sub repository includes manual pages. These should be
included
in the Debian autotools-dev package for completeness.
-- System Information:
Debian Release: 10.6
APT prefers stable-updates
APT policy: (500,
Package: autotools-dev
Severity: wishlist
Dear Maintainer,
Given that these scripts are often used by system users, these scripts
should be somewhere found on the $PATH. I propose /usr/bin as a reasonable
place to put them.
-- System Information:
Debian Release: 10.6
APT prefers
26 matches
Mail list logo