Package: logcheck
Version: 1.4.2
Followup-For: Bug #1041524
Dear Maintainer,
I also had the problem of duplicated journalctl/rsyslogd messages with
different time formatting, but otherwise than suggested in this bug I'd
like to move to the precision format - and thus came up with a patch to
Package: tar
Version: 1.27.1-2+deb8u1
Severity: normal
Dear Maintainer,
the following happens:
# /bin/tar cz -p -P --atime-preserve --warning=no-file-ignored
--warning=no-file-changed --one-file-system /
/bin/tar: /etc/machine-id: Cannot utime: Read-only file system
/bin/tar:
Hi Julien,
On Sat, May 30, 2015 at 12:26:58PM +0200, Julien ÉLIE wrote:
So maybe the issue comes from Perl... Is it possible to disable the
Perl filters in inn.conf to see if it then works OK?
I don't know where/how to disable the filters in the configuration but
I disabled them immediately
On Thu, May 28, 2015 at 06:26:36PM +0200, Stefan Froehlich wrote:
On Thu, May 28, 2015 at 03:58:51PM +0200, Marco d'Itri wrote:
Good: inn_1.7.2q-41_amd64.deb
Fail: inn_1.7.2q-41+b1_amd64.deb
I don't know anything about the differences of these two versions.
However, 41 has been running
On Sun, May 10, 2015 at 11:36:59PM +0200, Marco d'Itri wrote:
What would really help is if you could test some of the older packages
to find out which one introduced this regression:
http://snapshot.debian.org/package/inn/
Good: inn_1.7.2q-41_amd64.deb
Fail: inn_1.7.2q-41+b1_amd64.deb
(There
On Thu, May 28, 2015 at 03:58:51PM +0200, Marco d'Itri wrote:
Good: inn_1.7.2q-41_amd64.deb
Fail: inn_1.7.2q-41+b1_amd64.deb
I do not think that this is right, because 41+b1 is just a binNMU which
is supposed to be in every way identical to 41.
I don't know anything about the differences
On Mon, May 04, 2015 at 01:58:54AM +0200, Marco d'Itri wrote:
Can you check if a non-streaming feed (IHAVE only, i.e. streaming:
false in innfeed.conf) triggers the bug too?
A little bit unexpected but luckily: the problems stopped immediately
when switching to non-streaming.
Another
Package: mutt
Version: 1.5.21-6.2+deb7u2
Severity: wishlist
Dear Maintainer,
when mutt is called before any mail has arrived (i.e. $MAIL does
not yet exist), it asks $MAIL does not exist. Create it? ([yes]/no)
upon every invocation.
This question is kind of pointless: in many cases, the
Package: logcheck-database
Version: 1.3.13
Severity: minor
With sendmail, self-signed certificates trigger a warning like:
| Oct 2 13:02:07 hostname sm-mta[24652]: STARTTLS=client, relay=host.example.,
version=TLSv1/SSLv3, verify=FAIL, cipher=DHE-RSA-AES256-SHA, bits=256/256
There is a
On Sat, Jan 21, 2012 at 02:26:47PM +0100, Andreas Metzler wrote:
Does glxgears (from mesa-utils) work for you?
Actually it does not:
| sfroehli@sokrates:~$ glxgears
| X Error of failed request: BadRequest (invalid request code or no such
| operation)
| Major opcode of failed request: 137
On Sat, Jan 21, 2012 at 02:58:04PM +0100, Andreas Metzler wrote:
Using the software renderer instead of DRI (apt-get --purge install
libgl1-mesa-swx11) might work.
Unfortunately, this doesnt' work either :-(
| sokrates:~# apt-get --purge install libgl1-mesa-swx11
| The following extra packages
On Tue, Jan 17, 2012 at 07:18:17PM +0100, Andreas Metzler wrote:
Does it also crash with software rendering?
env LIBGL_ALWAYS_SOFTWARE=1 hugin
Unfortunately: yes.
Stefan
sfroehli@sokrates:~$ env LIBGL_ALWAYS_SOFTWARE=1 hugin
*** glibc detected *** hugin: free(): invalid pointer:
On Tue, Jan 10, 2012 at 07:17:13PM +0100, Andreas Metzler wrote:
hugin segfaults right at startup [...]
would you mind checking whether 2011.4.0 works for you? It is
available in sid/wheezy and squeeze-backports.
No problem (with checking), unfortunately it changes pretty nothing. If I can
Package: hugin
Version: 2010.0.0+dfsg-3+b1
Severity: grave
Justification: renders package unusable
hugin segfaults right at startup due to an invalid free(). This bug differs
from 649171 and 551006, as no canvas is displayed at all. Below you can find
backtrace and memory map.
Package: mysql-common
Version: 5.1.49-3
Severity: minor
mysql-5.1-5.1.49/sql-common/client.c contains (amongst others):
|case 27:
| if (opt_arg)
|options-max_allowed_packet= atoi(opt_arg);
| break;
This allows max_allow_packet to be specified as found in
Package: mysql-5.1-server
Version: mysql-server-5.1
Severity: grave
Justification: renders package unusable
Tried to build MySQL-5.1 from source, as I need some minor tweaks in
myisam/ftdefs.h. Building failed. What I did was:
| $ apt-get source mysql-server-5.1
| $ cd mysql-5.1-5.1.49
| $ vi
Package: awstats
Version: 6.9.5~dfsg-5
Severity: normal
awstats comes together with a cron job. This job looks for all
configuration files within /etc/awstats/ (which is good) but includes
awstats.conf hardcoded (which is bad).
If there is no master configuration file (which seems to be quite
17 matches
Mail list logo
