Package: incron
Version: 0.5.12-1
Severity: grave
Tags: security patch upstream
Hi,
incron crashes for me frequently. As incron runs as root, but is controllable
by users, this bug might be security-relevant, so I'm reporting it a severity
grave and tagging it security. Please downgrade if you
Hi,
as the problem is not new, I've marked the version in testing as
affected and I changed the title of the bug accordingly.
Willi
Hi,
just for the record, I tried to reproduce the build failure on eller
(mipsel porterbox), but it builds fine there. I'm wondering whether the
timeout set on line 232 of tests/srp.c (40 seconds) is too short for
slower build hosts.
Willi
Control: close -1
Hi,
I'm closing this bug as the problem was caused by a user-supplied regex.
Willi
Hi Peter,
Am 08.08.17 um 11:41 schrieb Peter Collinson:
> Alternative and better solution: I added --encode=base64 to
> 00logwatch in cron.daily, after ensuring that libmime-tools-perl
> was installed. Line wrapping is no longer a problem.
the problem with the base64 option is
Hi,
does the patch really work for you? I'm surprised because you used \S
which means "all non-whitespace characters", but I think you intended
otherwise.
Willi
Am 26.08.18 um 14:44 schrieb Reco:
> Package: logwatch
> Version: 7.4.3+git20161207-2
> Severity: normal
>
> Dear Maintainer,
>
>
+1,10 @@
+mrtrix (0.2.12-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix build error with ambigous call to round (closes: #816570)
+
+ -- Willi Mann <wi...@debian.org> Sat, 21 Oct 2017 16:22:07 +0200
+
mrtrix (0.2.12-2) unstable; urgency=medium
* Add patch to i
Control: tag -1 + patch
Hi,
attached is a patch that fixes the problem with the @piddir@. Note
however, that by default, the LISTS variable in the config file is
empty. As long as LISTS is empty, the webmlm will still not start.
Bye
Willi
Index: courier-0.76.3/courier/configure.ac
Hi,
according to the previous maintainer, this bug was fixed in version
0.75.0-15. However, I never verified that (I reported the bug back then)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812235
Bye
Willi
Hi Maxy,
Am 2017-04-06 um 19:24 schrieb Maximiliano Curia:
> El 2017-03-31 a las 21:25 +0200, Willi Mann escribió:
>> Am 2017-03-31 um 18:25 schrieb Maximiliano Curia:
>
>>> Do you have another session started as root? Do you have another X
>>>
Hi Maxy,
Am 2017-03-31 um 18:25 schrieb Maximiliano Curia:
>
>> in the SDDM settings window, it tells me the same as when I try it as
>> ordinary user (I'm not allowed to save the configuration, transl. from
>> German).
>
>>> The changes made as root weren't applied to the /etc/sddm.conf file?
Hi Maxy!
> El 2017-03-22 a las 19:52 +0100, Willi Mann escribió:
>> Am 2017-03-21 um 10:58 schrieb Maximiliano Curia:
>>> El 2017-03-20 a las 19:22 +0100, Willi Mann escribió:
>>>> the problem still exists. Let me know if you any idea how to track
>>>>
Control: tag -1 - moreinfo
Am 2017-03-21 um 10:58 schrieb Maximiliano Curia:
>
> ¡Hola Willi!
>
> El 2017-03-20 a las 19:22 +0100, Willi Mann escribió:
>> the problem still exists. Let me know if you any idea how to track
>> this down.
>
> Sorry, I can't reprodu
Control: reopen -1
Hi Maxy,
the problem still exists. Let me know if you any idea how to track this
down.
Willi
Am 2017-03-16 um 20:11 schrieb Maximiliano Curia:
> ¡Hola Willi!
>
> El 2015-08-12 a las 20:11 +0200, Willi Mann escribió:
>> Package: kde-config-sddm Version: 4:5
Package: wnpp
Severity: wishlist
Owner: Willi Mann <wi...@debian.org>
* Package name: python-django-progressbarupload
Version : 0.1.7
Upstream Author : Samuel Goldszmidt
* URL : https://github.com/ouhouhsami/django-progressbarupload
* License
Hi,
Am 2016-12-28 um 10:09 schrieb Klaus Ethgen:
> Package: logwatch
> Version: 7.4.3+git20161207-1
> Severity: critical
>
> Current logwatch did change from sending mails with charset iso-8859-1
> to UTF-8. This openes up a potential security hole as UTF-8 is not able
> to display all 8bit
Hi Klaus,
Am 2017-01-15 um 17:43 schrieb Klaus Ethgen:
> Hi Willi,
>
> Am Sa den 14. Jan 2017 um 16:43 schrieb Willi Mann:
>> in order to come closer to a fix for this issue, I propose the following
>> two patches:
>
>
>> 0001-Add-outputencoding-parame
e, the pager
will not be invoked. I also made the pager configurable and it can be
set to am empty string to disable). I updated the help text in the
second patch to document that better.
Willi
>From 162f8b2e7fae134e65761dc64e0a8d29c9c172d4 Mon Sep 17 00:00:00 2001
From: Willi Mann <wi...@wm1.
tarted this project with. (I’m
> looking at you Solaris 7/8)
>
>
> -Mike
>
>From 162f8b2e7fae134e65761dc64e0a8d29c9c172d4 Mon Sep 17 00:00:00 2001
From: Willi Mann <wi...@wm1.at>
Date: Sat, 14 Jan 2017 15:32:39 +0100
Subject: [PATCH 1/2] Add outputencoding parameter
--
> Uploaded. Unfortunately, I realized after the upload that the debdiff
> got bloated by my pbuilder build. I guess because unapply-patches is not
> set. Let me know whether I should fix that.
False alarm- the diff is still fine. It just wasn't a good idea to
compare the 2 unpacked versions of
Hi,
Am 2017-01-05 um 20:55 schrieb Adam D. Barratt:
>> The changelog is:
>> unrtf (0.21.5-3+deb8u1) stable; urgency=medium
>>
>> * Add patch from upstream to fix CVE-2016-10091 (buffer overflow in various
>> cmd_ functions) closes: 849705
>
> Please go ahead.
Uploaded. Unfortunately, I
+deb8u1) stable; urgency=medium
* Add patch from upstream to fix CVE-2016-10091 (buffer overflow in various
cmd_ functions) closes: 849705
-- Willi Mann <wi...@debian.org> Sun, 01 Jan 2017 19:50:41 +0100
debdiff attached.
Let me know whether this intended upload is fine with you.
Hi,
Am 2017-01-01 um 00:20 schrieb Jason Pyeron:
> Not exactly a valid test, besides it works for me. The issue is internal
> ascii data being written as ascii but instructing consumers
> it is uft8.
>
> $ cat utf8_test.pl
> #!/usr/bin/perl
> #
> use strict;
> use File::Slurp;
>
> my
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please lower the testing migration delay for package unrtf. It fixes
CVE-2016-10091 (buffer overflow). Debdiff attached. Note that the changes to
import-orig.sh in the debdiff can be
Hi,
> Not sure yet if that would warrant a DSA, possibly it could be updated
> via the upcoming point release as well.
I pushed a jessie branch to the git repository with the patch from
upstream (some hunks had to be ignored). I also uploaded a patched
version to unstable.
Dear Security Team,
I would like to get your input on bug #849531 [1]. A short summary:
Logwatch is a log summarizer that parses various logfiles and reports a
summary, either via e-mail or to stdout. Parts of the input are copied
verbatim w.r.t. to their encoding to the output (e.g., usernames,
Hi Jean-Francois,
Are you fine with attached patch? I saw that two other cmd_ functions
follow the same pattern, so they are probably also vulnerable, right?
thanks
Willi
Am 2016-12-30 um 19:16 schrieb Jean-Francois Dockes:
> Willi Mann writes:
> > Hi Dave,
> > Hi Jean-Francoi
3 b9 c3 ba c3 bb c3 bc c3 bd c3 be c3 bf ||
> 0180
>
> This confirms that binmode utf8 is needed to print out the full ASCII range.
>
>> -Original Message-
>> From: Jason Pyeron [mailto:jpye...@pdinc.us]
>> Sent: Friday, December
Hi Klaus,
Am 2016-12-30 um 18:36 schrieb Klaus Ethgen:
> Hi Willi,
>
> Am Fr den 30. Dez 2016 um 18:18 schrieb Willi Mann:
>> can you elaborate how this could be exploited?
>
> Well, log principally contains untrusted data that could be injected
> from untrusted source.
Hi Dave,
Hi Jean-Francois,
I got the following bug report, apparrently describing a buffer overflow
in unrtf - which I can reproduce. Do you have a suggestion for a fix?
I'm also CCing debian's security team.
WM
Am 2016-12-30 um 01:44 schrieb Skylake:
> Package: unrtf
> Version: 0.21.9-clean-2
Hi Klaus,
can you elaborate how this could be exploited? What would be your
suggested fix?
I'm including the upstream mailing list in the conversation.
thanks you
Willi
Am 2016-12-28 um 10:09 schrieb Klaus Ethgen:
> Package: logwatch
> Version: 7.4.3+git20161207-1
> Severity: critical
>
>
Dear Ohura,
I really would like to see latexmk 4.48 in stretch. I prepared an
updated package for latexmk. It is available from
https://publish.willi.space/2016-11-24-pL0GZHx4VTk/
Feel free to take it and upload it if you are fine with it. I can also
do an upload if you want.
Let me know
Package: latexmk
Version: 1:4.41-1
Severity: wishlist
Hi,
It would be great if you could package version 4.48 of latexmk.
thanks
Willi
Hi,
m2crypto has now been accepted to jessie-backports:
https://tracker.debian.org/news/792433
Bye
Willi
Package: hash-slinger
Version: 2.7-1~bpo8+1
Severity: normal
Hi,
the SNI functionality in the tlsa tool requires a python-m2crypto version that
is more recent than the version in jessie - the testing/unstable version
pf python-m2crypto works. This is especially problematic for the hash-slinger
Hi,
Am 2016-07-29 um 05:11 schrieb Nayr:
> Willi,
> Sorry that I wasn't clearer, but your patch was missing a line
> break. I added a '\n' to the patch when I posted my reply. So my
> previously attached amavis.path file is different from what you
> submitted.
thanks for pointing this
in sprintf at
.../amavis line 1338, <> line 321 message
Weitersenden-Datum: Wed, 30 Mar 2016 16:27:01 +
Weitersenden-Von: Nayr <debian-b...@nayr.us>
Weitersenden-An: debian-bugs-dist@lists.debian.org
Weitersenden-CC: Willi Mann <wi...@debian.org>
Datum: Wed, 30 Mar 2016 11:34:
Hi,
thanks for your fast reply.
Could you try attached patch and let me know whether it works for you?
In case you don't know how to apply the patch (as root):
patch /usr/share/logwatch/scripts/services/amavis < /tmp/amavis.patch
thanks
Willi
--- /usr/share/logwatch/scripts/services/amavis
Hi,
any chance that you send me a logfile that demonstrates this problem? I
don't have access to any machine running amavis...
thanks
WM
Am 2016-03-30 um 17:34 schrieb Nayr:
> Package: logwatch
> Version: 7.4.2-1
> Severity: normal
>
> Dear Maintainer,
>
> -- System Information:
> Debian
Weitersenden-Von: Jonny Lamb <jo...@debian.org>
Weitersenden-An: debian-bugs-dist@lists.debian.org
Weitersenden-CC: Willi Mann <wi...@debian.org>
Datum: Wed, 11 May 2016 16:12:53 +0100
Von: Jonny Lamb <jo...@debian.org>
Antwort an: Jonny Lamb <jo...@debian.org>, 824...
Hi Eric,
Am 2016-01-24 um 18:54 schrieb Eric Dorland:
> Package: logwatch
> Version: 7.4.1+svn20151218rev302-1
> Severity: minor
>
> I'm getting the following warning when the postfix script runs:
could you verify whether attached version of the postfix script fixes
this issue? (unpack and Copy
Hi Eric,
Am 2016-01-24 um 18:54 schrieb Eric Dorland:
> Package: logwatch
> Version: 7.4.1+svn20151218rev302-1
> Severity: minor
>
> I'm getting the following warning when the postfix script runs:
could you verify whether attached version of the postfix script fixes
this issue? (unpack and Copy
Control: tag -1 upstream ipv6
Hi,
> I am using logwatch on dualstack system (IPv4 & IPv6). Logwatch has
> section for iptables which only manages IPv4.
>
> I believe logwatch shuld also include ip6tables as I am only seeing
> traffic with one internet protocol instead of the two that are used
[mail-reader] 3.18.3-1
ii icedove [mail-reader]38.5.0-1+b1
ii kmail [mail-reader] 4:4.14.10-2
ii mutt [mail-reader] 1.5.24-1
>From cead264474c0fdaa1723fa2b6a30bd839b1505d4 Mon Sep 17 00:00:00 2001
From: Willi Mann <wi...@debian.org>
Date: Thu, 21 Jan 2016 20:40:42 +010
Am 2016-01-20 um 09:13 schrieb Mobile Perpetuum:
> Hi, I confirm this bug in version 7.4.1+svn20151218rev302-1
Just for the record: what Mobile Perpetuum reports is not the same bug.
It is another problem with postfix that appears to require to execute a
specific printf call in order to occur.
Hi Chris,
I did some testing on the reverse dependencies of libssh-4 (not
libssh-gcrypt-4) for basic functionality with libssh where this appeared
to be feasible (see attachment). From what I've seen so far, I'm
confident that we won't cause big breakage. Of course, ibssh-gcrypt-4
should also be
moves the -dbg
package as they are now built automatically.
Bye
Willi
From 2792f1aa02aaac6aaf1570c3d16d17e13241bad4 Mon Sep 17 00:00:00 2001
From: Willi Mann <wi...@debian.org>
Date: Sat, 9 Jan 2016 16:37:49 +0100
Subject: [PATCH 1/2] debian/libssh-gcrypt-4.lintian-overrides: Adapt overri
Hi Chris,
Am 2016-01-08 um 07:57 schrieb Chris Knadle:
> Willi Mann:
>>
>> Could you make the git repo somewhere available?
>
>git clone git://git.coredump.us/debian/libssh.git
>
> I use git-buildpackage and pristine-tar, and the clone will contain all that
&
Hi,
sorry I did not find time to answer earlier.
Am 2015-12-02 um 01:22 schrieb Chris Knadle:
> Mike Gabriel:
>> Hi Willi, hi Laurent,
>>
>> On Sa 28 Nov 2015 19:29:01 CET, Willi Mann wrote:
>>
>>> Hi Laurent, Hi Mike,
>>>
>>> is there
Hi,
Am 2015-12-28 um 01:28 schrieb Laurent Bigonville:
> On Sun, 22 Jun 2014 21:14:55 +0200 Willi Mann <wi...@wm1.at> wrote:
>>
>> Hi,
>>
>> I think the script /etc/logwatch/scripts/services/seaudit-report-service
>> should be shipped in /usr/share/logwatch/
Hi,
Am 2015-12-28 um 13:07 schrieb Laurent Bigonville:
> Le 28/12/15 09:55, Willi Mann a écrit :
>> Hi,
>>
>> Am 2015-12-28 um 01:28 schrieb Laurent Bigonville:
>>> On Sun, 22 Jun 2014 21:14:55 +0200 Willi Mann <wi...@wm1.at> wrote:
>>>> Hi,
>>
Hi Laurent, Hi Mike,
is there a particular reason why libssh wasn't updated to newer upstream
versions?
Bye
Willi
signature.asc
Description: OpenPGP digital signature
Am 2015-10-03 um 19:42 schrieb Felix Geyer:
> Hi,
>
> On Sat, 03 Oct 2015 15:58:34 +0200 Mario Blättermann
> wrote:
>> Same behavior on a freshly installed Stretch. The gdb output:
>>
>> (gdb) run
>> Starting program: /usr/bin/dolphin
>> [Thread debugging using
Package: dolphin
Version: 4:15.08.1-1
Severity: grave
Hi,
dolphin crashes on every attempt to start (i.e. it shows the window with the
directory content for a second and then segfaults) with the following
backtrace:
bt full
#0 mdb_txn_begin (env=0x0, parent=0x0, flags=131072,
Package: linklint
Version: 2.3.5-5
Severity: normal
Tags: patch
linklint does not support the HTTP 307 (temporary redirect) status code. When a
server answers with 307, linklint reports an "unknown error". This is easy to
fix - see attached patch.
Please consider adding this patch to the debian
Package: kde-config-sddm
Version: 4:5.3.2-1
Severity: normal
Hi,
I get the message in the subject when I go to the SDDM config unit. It happens
both when I go there as ordinary user and as root. Let me know whether I can
provide further information to resolve this bug.
thanks
Willi
-- System
Hi,
--archives is the default, which solves most of the problems you
describe. The only known problem that remains is support for alternative
compression methods (gz and bzip2 are supported, but xz is not supported).
If you report bugs, please use reportbug, as the upstream version only
makes it
Hi!
Am 2015-04-19 um 00:29 schrieb Mario Lang:
Willi Mann wi...@debian.org writes:
was anybody of you able to reproduce this build failure in a clear
chroot environment?
No.
I failed to reproduce it in a jessie pbuilder environment, and also on
an another machine (mixed jessie/wheezy
Hi,
was anybody of you able to reproduce this build failure in a clear
chroot environment? I failed to reproduce it in a jessie pbuilder
environment, and also on an another machine (mixed jessie/wheezy).
WM
signature.asc
Description: OpenPGP digital signature
Hi,
Am 2015-04-15 um 23:46 schrieb derMaria:
whenever I get a mail from someone who encrypted the Message with OpenPGP für
Windows Phone from Christoph Müller http://www.windowsphone.com/de-
de/store/app/openpgp-f%C3%BCr-windows-phone/0a1906e2-eb48-4cdb-bbab-
30ea308b9065 I cannot decrypt the
Hi,
I could only reproduce this bug with sysvinit as init system. I think
one could use runlevel (if it exists) to detect whether a real shutdown
is running. Maybe something like the attached patch could fix the
problem (not yet tested).
WM
diff --git a/debian/kexec-load.init.d
Hi,
I think this bug should get fixed for jessie. I don't want to raise the
severity of this bug myself as it was already lowered once, but please
fix this bug before the release.
thanks
Willi
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
Just a status update on this bug: The upload of unrtf 0.21.5-3 fixes
this bug, but I intend to do more testing before asking for an unblock.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Control: tag -1 + pending
I've upgraded this bug to RC status because it is a regression from
wheezy. It is especially bad because it may bite some reverse
dependencies that use unrtf as part of a processing chain.
Salvatore Bonaccorso has already proposed a fix for this bug, based on
the
Hi,
Am 2015-01-21 um 18:42 schrieb Daniel Kahn Gillmor:
On Wed 2015-01-21 12:25:13 -0500, Andrew Gallagher wrote:
Is this all really necessary? It would be hundreds of times faster to call
'gpg --list-keys $email' for each recipient in turn.
This is likely true if you have a large
Hi,
Just in order to avoid duplicate effort: I have prepared (but not yet
tested) an upload for wheezy-security of unrtf, fixing CVE-2014-9274
CVE-2014-9275. It is available in the alioth git repository:
http://anonscm.debian.org/cgit/collab-maint/unrtf.git/
Bye
Willi
signature.asc
of size 4 in attr_get_param
+- attr_get_param(): Silence a warning message again
+
+ -- Willi Mann wi...@debian.org Mon, 22 Dec 2014 20:20:33 +0100
+
unrtf (0.21.5-1) unstable; urgency=low
* Imported Upstream version 0.21.5
diff -Nru unrtf-0.21.5/debian/patches/0001-check-that-accesses
Hi Salvatore,
we were working in parallel unfortunately, as I prepared the same
patches in the morning. However, I also added 2 patches by
Fabian Keil. I'll upload tomorrow in the evening, you can have a look at
http://anonscm.debian.org/cgit/collab-maint/unrtf.git/
comments welcome.
thanks
Hi Dave,
does 0.21.7 solve both security issues reported? If yes, could point
send me the individual patches that fix these issues? The Debian branch
for the next stable distribution is already frozen, so I cannot fix
these bugs with new upstream versions.
thanks
Willi
Am 2014-12-11 um 12:16
=medium
+
+ * d/rules - clean: Fake config/autoconf.mk if it doesn't exist, don't call
+configure. Fixes FTBFS on ppc64el. closes: #760845
+ * Make enigmail use the right XPCOM_TARGET name on ppc64 archs.
+
+ -- Willi Mann wi...@debian.org Sun, 23 Nov 2014 15:47:07 +0100
+
enigmail (2:1.7.2-2
:36.0 +0200
+++ logwatch-7.4.1/debian/changelog 2014-11-03 20:02:44.0 +0100
@@ -1,3 +1,10 @@
+logwatch (7.4.1-2) unstable; urgency=medium
+
+ * Revert upstream change on fail2ban service config. This makes fail2ban
+reporting work again. Closes: #766901
+
+ -- Willi Mann wi
config.* files by using autotools-dev. closes: #760845
+ * Update Standards-Version 3.9.5 - 3.9.6
+ * Make enigmail use the right XPCOM_TARGET name on arm{el,hf}, powerpc, and
+mipsel. Closes: #765937 (hopefully)
+
+ -- Willi Mann wi...@debian.org Sun, 02 Nov 2014 19:12:49 +0100
+
enigmail (2
Control: tag -1 + fixed-upstream
Hi Gabriele,
please close the upstream bug report, the patch has already been included.
http://sourceforge.net/p/enigmail/source/ci/7132d0b43068ff8dbeb386dcec879090cc934c33/
thanks
Willi
Am 2014-11-04 um 02:09 schrieb Debian Bug Tracking System:
Processing
Control: found -1 2:1.7.2-2
Bug is still there, missed the actual problem.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi,
last known-working versions on armel are for me
Icedove 24.5.0-2
Enigmail 1.6-4
could you test enigmail 1.7.2-2? It is currently available from
http://incoming.debian.org/debian-buildd/pool/main/e/enigmail/
Tomorrow, it will be available from unstable. I don't know whether it
fixes
Hi,
Am 2014-10-19 um 13:44 schrieb Thomas Maass:
Package: enigmail
Version: 2:1.7.2-1
Depends (Version) | Installed
===-+-
libc6 (= 2.4) | 2.19-11
icedove (= 24.0) | 31.0-3
do you know whether this is a new problem? Did it work with icedove 24?
Did previous
Thank you anyway for this bug report. It helps to decide how to handle
enigmail for the upcoming icedove major upgrade in stable.
WM
Am 2014-10-21 um 19:19 schrieb Michael Strobel:
The bug can be closed since it doesn't occur in version 1.7 of enigmail.
Cheers
Michael
On 06/23/2014 11:53
Version: 7.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Willi Mann wi...@debian.org
Changed-By: Willi Mann wi...@debian.org
Description:
logwatch - log analyser with nice output written in Perl
Closes: 710146
Changes:
logwatch (7.4.1-1) unstable; urgency=medium
.
* Imported Upstream
Package: wnpp
Severity: wishlist
Owner: Willi Mann wi...@debian.org
* Package name: libsys-meminfo-perl
Version : 0.98
Upstream Author : Sylvain Cresto scre...@gmail.com
* URL : http://search.cpan.org/~scresto/Sys-MemInfo/MemInfo.pm
* License : same as Perl
Control: tag -1 + upstream
Am 2014-09-13 um 16:32 schrieb Chris:
Hi,
just for the records. The attached patch was included in upstream rev223
https://sourceforge.net/p/logwatch/patches/31/
With the next sync of this package against upstream this bug can be closed.
thank you for
Am 2014-08-07 11:28, schrieb Jeremiah C. Foster:
On Thu, Aug 07, 2014 at 06:52:48AM +0200, Willi Mann wrote:
Sorry I didn't see this earlier, but I think the fix is to change line
478 in /usr/share/logwatch/scripts/services/exim from
( $bb ) = ($ThisOne =~ m
Am 2014-08-02 22:21, schrieb Jeremiah C. Foster:
Hi Jeremiah,
Logwatch is mailing reports which contain the line;
Use of uninitialized value $bb in concatenation (.) or string at
/usr/share/logwatch/scripts/services/exim line 490, STDIN line 3480.
This looks to be an error in
Hi,
Am 2011-01-26 18:48, schrieb Tony Lill:
setting hostlimit=yes has no effect, for two reasons
1) The documentations and comments in the config file says to set
hostlimit = yes, but in actuality, you have to set it to the
hostname
2) Even if you do this, a bug in the code that handles
Hi,
can you please tell me whether this problem is still reproducible? I
could not reproduce it with the logwatch version version in wheezy.
thanks
WM
Am 2010-07-24 11:24, schrieb Aniruddha:
Package: logwatch
Version: 7.3.6.cvs20080702-2
Severity: normal
Logwatch gives the following
Hi,
Dear Maintainer,
Logwatch is mailing reports which contain the line;
Use of uninitialized value $bb in concatenation (.) or string at
/usr/share/logwatch/scripts/services/exim line 490, STDIN line 3480.
This looks to be an error in initializing the $bb variable. Further
Hi,
this bug seems to got fixed in upstream SVN revision 53, which would be
some upload between squeeze and wheezy. Can you confirm that this bug is
no longer reproducible?
thanks
WM
Am 2009-10-25 13:15, schrieb Bartosz Fenski aka fEnIo:
Package: logwatch
Version: 7.3.6.cvs20090906-1
Package: isc-dhcp-server
Version: 4.3.0+dfsg-1
Severity: serious
Hi,
with systemd installed, isc-dhcp-server fails to install because starting the
daemon fails. This must have worked (in the sense that the postinst script
succeeded) with sysvinit as I have the same (non-)setup of
Package: sqwebmail
Version: 0.73.1-1.2
Severity: serious
Justification: fails to install
Hi Racke,
sqwebmail fails to install if the directory /var/www does not exist (which
apparently does not exist if nginx is installed as httpd-cgi):
Entpacken von sqwebmail (0.73.1-1.2) ...
Trigger für
Should be easy to fix - I guess (but am not sure) the most proper way to fix
this is to ship /var/www as part of the sqwebmail package. If you create it
in the maintainer script, it is problematic to decide whether to delete it
on package removal.
It is quite likely that nowadays a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Control: tag -1 + fixed-upstream
Hi,
thank you for your report. The ERST message is fixed in upstream svn
revision 117 (so you can get it via logwatch from testing), the mount
option problem is fixed in svn revision 183, which is not yet uploaded.
-Nachricht
Betreff: Bug#745195: unrtf 0.21 outputs hex.junk to stdout
Weitersenden-Datum: Fri, 18 Apr 2014 19:00:02 +
Weitersenden-Von: Matus UHLAR - fantomas uh...@fantomas.sk
Weitersenden-An: debian-bugs-dist@lists.debian.org
Weitersenden-CC: Willi Mann wi...@debian.org
Datum: Fri, 18 Apr
upload.
+ * Change mkesmptdcert to make cert-filename controllable by parameter.
+ * Create esmptd.pem in temporary path and then move it to /etc/courier.
+This way, mkesmptdcert no longer has to work on an dangling symlink as
+destination. (closes: #749129)
+
+ -- Willi Mann wi
Hi,
thank you for your report. Please post the output of
apt-cache policy enigmail
thanks
WM
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: setools-gui
Version: 3.3.8-3
Severity: normal
Hi,
I think the script /etc/logwatch/scripts/services/seaudit-report-service
should be shipped in /usr/share/logwatch/scripts/services, unless it is really
expected to be modified by the user like a configuration file.
Additionally, the
Package: ijsgutenprint
Version: 5.2.10-1
Severity: grave
Hi,
On upgrade, ijsgutenprint fails on wheezy:
Vorbereitung zum Ersetzen von ijsgutenprint 5.2.9-1 (durch
.../ijsgutenprint_5.2.10-1_amd64.deb) ...
dpkg-maintscript-helper: error: command dir_to_symlink is unknown
Hint: upgrading dpkg to
Hi Racke,
Selecting previously unselected package courier-mta-ssl.
(Reading database ... 8752 files and directories currently installed.)
Preparing to unpack .../courier-mta-ssl_0.73.1-1.1_amd64.deb ...
Unpacking courier-mta-ssl (0.73.1-1.1) ...
Setting up courier-mta-ssl
Hi,
you are the current owner of the ITP of massif-visualizer. What is the
current state? Do you need help? I would really like to see
massif-visualizer in jessie.
WM
signature.asc
Description: OpenPGP digital signature
), but not
before Thursday.
Bye
Willi
From 43a0424d6de39643036c421dc185fae0086c44c2 Mon Sep 17 00:00:00 2001
From: Willi Mann wi...@wm1.at
Date: Sun, 27 Apr 2014 14:56:48 +0200
Subject: [PATCH 1/3] Fix maildrop to build against courier authlib
---
debian/rules|1 +
libs/maildrop
tag 740602 + pending
thanks
Marking this bug as pending as a fix is in pkgs repository:
http://anonscm.debian.org/gitweb/?p=pkg-games/deng.git;a=commitdiff;h=f7ffda75d23d1e471cf6a42f21d42e991a2172d3;hp=9b14820b38c3e1ea99b686bbc469a42c9bbef9b8
Greetings from Salzburg BSP
WM
--
To UNSUBSCRIBE,
Apparently, the reason for this bug is that courier-imap now needs a
dhparams.pem. At least, I could reproduce this bug (using offlineimap),
and found the following message in network dump:
MEAE2 NO STARTTLS failed: couriertls: /etc/courier/dhparams.pem:
error:02001002:system library:fopen:No
1 - 100 of 558 matches
Mail list logo