Package: netatalk
Version: 2.0.2-3
Severity: important
The default installation of netatalk will not create /var/spool/netatalk/.
This causes the papd childs to fail while trying to access the printer. As
a result, the macintosh clients will be blocked untill the timeout occures.
TODO:
1) Create
I have to agree with Klaus Knopper. This is ridiculous. Just because you
think internalizing the library would
be insecure, all the users are forced to write C wrappers or compile their
own ntfs-3g, which bosth will in effect be WAY LESS SECURE, because of the
very reasons you are trying to avo
Package: perl-base
Version: 5.10.1-17squeeze3
Severity: important
Tags: upstream
Some versions of perl, including 5.10.1-17squeeze3, have problems matching
utf-8 characters:
$ LANG=en_US.UTF-8 perl -e 'use utf8; "Herbert Grönemeyer" =~ /(.*?)\s*\(with
(.*)\)$/i'
Malformed UTF-8 character (unex
On Fri, 10 Jul 2015, Michael Biebl wrote:
> Am 10.07.2015 um 14:05 schrieb Bodo Eggert:
> > Package: systemd
> > Version: 215-17+deb8u1
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > when I boot my system, some of the NFS shares don't g
Reported upstream as Bug 952945
https://bugzilla.mozilla.org/show_bug.cgi?id=952945
My ¢¢: If I select the tabs to stay opened, the list of opened tabs
obviously should not be cleared.
Package: debian-installer
Severity: normal
Dear Maintainer,
the mkfs.ext3 program will check for DOS disklabels before formating.
Creating an extended partition and then deciding to replace it with a
primary partition causes the new partition to have one.
Therefore the installation stopped when
Package: busybox
Version: 1:1.22.0-9+deb8u1
Severity: normal
Tags: d-i
Dear Maintainer,
The valid hostname "52-54-0-12-34-56" is recognized as bad while it should be
valid according to rfc1123 (Section 2.1).
-
Capture of the DHCP reply:
be1.lrz.bootps > 192.168.7.107.bootpc: BOOTP/DHCP,
On Sun, 21 Jun 2015, Geert Stappers wrote:
> Control: tag -1 moreinfo
> On Sun, Jun 21, 2015 at 02:14:17PM +0200, Bodo Eggert wrote:
> > The valid hostname "52-54-0-12-34-56" is recognized as bad
> > while it should be valid according to rfc1123 (Section 2.1).
>
This bug just crashed my system by generating 2.2 GB of logs and caused a
day of debugging - exactly when I needed to leave for a week.
9 matches
Mail list logo
