Bug#1087981: linux-image-6.1.0-27-amd64: detected stalls in kernel log, system very slow on IO (regression)

Hi Salvatore, sorry, I somehow missed your mail. Am 21.03.25 um 21:07 schrieb Salvatore Bonaccorso: While we had no followup after your last email, I wonder now if you still experience the issues with the most recent 6.1.y kernel available in Debian (6.1.128-1). Can you report back? Can you t

Bug#1087981: linux-image-6.1.0-27-amd64: detected stalls in kernel log, system very slow on IO (regression)

ri, Nov 22, 2024 at 10:35:08PM +0100, Salvatore Bonaccorso wrote: Hi Willi, On Thu, Nov 21, 2024 at 09:47:06PM +0100, Willi Mann wrote: Hi Salvatore, Am 21.11.24 um 17:02 schrieb Salvatore Bonaccorso: hi, Can you please provide a full boot log to see if we can pin-point the cause? Full log

Bug#1087981: linux-image-6.1.0-27-amd64: detected stalls in kernel log, system very slow on IO (regression)

Hi Salvatore, Am 21.11.24 um 17:02 schrieb Salvatore Bonaccorso: hi, Can you please provide a full boot log to see if we can pin-point the cause? Full log of a boot with the 6.1.0-28 version attached - which after some time running unfortunately also shows the "detected stalls" message. H

Bug#1087981: linux-image-6.1.0-27-amd64: detected stalls in kernel log, system very slow on IO (regression)

Package: src:linux Version: 6.1.115-1 Severity: important Tags: upstream Hi, I'm seeing regularly kernel logs of the form below, combined with the system feeling terribly slow. This is a regression as I didn't have these problems with linux-image-6.1.0-26-amd64. The issue occurs on a VPS. The pr

Bug#947425: incron crashes in IncronTabEntry::GetSafePath due to use-after-free bug

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 c

Bug#921198: testing also affected

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

Bug#921198: hard to track down

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

Bug#852931: closing this bug

Control: close -1 Hi, I'm closing this bug as the problem was caused by a user-supplied regex. Willi

Bug#871473: logwatch: Logwatch email messages fail with vanilla exim4 install: message is too big (transport limit = 1)

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 that

Bug#907319: logwatch has erroneous mdadm device detection

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, > > Per

Bug#816570: fix uploaded to DELAYED

+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 Sat, 21 Oct 2017 16:22:07 +0200 + mrtrix (0.2.12-2) unstable; urgency=medium * Add patch to include to fix FTBFS due to

Bug#875696: patch

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 ==

Bug#875954: there should be patch somewhere...

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

Bug#795296: "You are not allowed to save the configuration" (both root and ordinary user)

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 >>> session started wit

Bug#795296: "You are not allowed to save the configuration" (both root and ordinary user)

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? >

Bug#795296: "You are not allowed to save the configuration" (both root and ordinary user)

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 >>>>

Bug#795296: "You are not allowed to save the configuration" (both root and ordinary user)

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 re

Bug#795296: "You are not allowed to save the configuration" (both root and ordinary user)

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

Bug#856230: ITP: python-django-progressbarupload -- Progress bar for Django (Python 2)

Package: wnpp Severity: wishlist Owner: Willi Mann * Package name: python-django-progressbarupload Version : 0.1.7 Upstream Author : Samuel Goldszmidt * URL : https://github.com/ouhouhsami/django-progressbarupload * License : BSD Programming Lang: Python

Bug#849531: Possible security problem, new logwatch sends mails with charset UTF-8

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 data.

Bug#849531: [Logwatch-devel] Bug#849531: Possible security problem, new logwatch sends mails with charset UTF-8

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-parameter

Bug#849531: [Logwatch-devel] Bug#849531: Bug#849531: Possible security problem, new logwatch sends mails with charset UTF-8

s case, 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

Bug#849531: [Logwatch-devel] Bug#849531: Possible security problem, new logwatch sends mails with charset UTF-8

we started this project with. (I’m > looking at you Solaris 7/8) > > > -Mike > >From 162f8b2e7fae134e65761dc64e0a8d29c9c172d4 Mon Sep 17 00:00:00 2001 From: Willi Mann Date: Sat, 14 Jan 2017 15:32:39 +0100 Subject: [PATCH 1/2] Add outputencoding parameter --- conf/logwatc

Bug#849869: jessie-pu: package unrtf/0.21.5-3

> 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 the

Bug#849869: jessie-pu: package unrtf/0.21.5-3

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 re

Bug#849869: jessie-pu: package 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 -- Willi Mann Sun, 01 Jan 2017 19:50:41 +0100 debdiff attached. Let me know whether this intended upload is fine with you. Willi -- System

Bug#849531: [Logwatch-devel] Bug#849531: Possible security problem,new logwatch sends mails with charset UTF-8

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 $inputfil

Bug#849855: unblock: unrtf/0.21.9-clean-3

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 ignor

Bug#849705: unrtf: Stack buffer overflow

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. https://anonscm.debian

Bug#849531: Possible security problem, new logwatch sends mails with charset UTF-8

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,

Bug#849705: unrtf: Stack buffer overflow

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

Bug#849531: [Logwatch-devel] Bug#849531: Possible security problem,new logwatch sends mails with charset UTF-8

6 c3 b7 || > 0170 c3 b8 c3 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:j

Bug#849531: Possible security problem, new logwatch sends mails with charset UTF-8

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.

Bug#849705: unrtf: Stack buffer overflow

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

Bug#849531: Possible security problem, new logwatch sends mails with charset UTF-8

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 > > Curr

Bug#841925: latexmk 4.48 in Debian

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 w

Bug#841925: new upstream version 4.48 is available

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

Bug#834971: Acknowledgement (hash-slinger: 2.7 versions should depend on python-m2crypto (>= 0.24.0))

Hi, m2crypto has now been accepted to jessie-backports: https://tracker.debian.org/news/792433 Bye Willi

Bug#834971: hash-slinger: 2.7 versions should depend on python-m2crypto (>= 0.24.0)

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 ve

Bug#819572: PATCH for amavis (Fwd: Bug#819572: logwatch: redundant argument in sprintf at .../amavis line 1338, <> line 321 message)

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 out

Bug#819572: PATCH for amavis (Fwd: Bug#819572: logwatch: redundant argument in sprintf at .../amavis line 1338, <> line 321 message)

in sprintf at .../amavis line 1338, <> line 321 message Weitersenden-Datum: Wed, 30 Mar 2016 16:27:01 + Weitersenden-Von: Nayr Weitersenden-An: debian-bugs-dist@lists.debian.org Weitersenden-CC: Willi Mann Datum: Wed, 30 Mar 2016 11:34:48 -0400 Von: Nayr Antwort an: Nayr

Bug#819572: logwatch: redundant argument in sprintf at .../amavis line 1338, <> line 321 message

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 201

Bug#819572: logwatch: redundant argument in sprintf at .../amavis line 1338, <> line 321 message

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 Relea

Bug#824034: Fwd: Bug#824034: $ignore_services breaks on close parentheses

Weitersenden-Von: Jonny Lamb Weitersenden-An: debian-bugs-dist@lists.debian.org Weitersenden-CC: Willi Mann Datum: Wed, 11 May 2016 16:12:53 +0100 Von: Jonny Lamb Antwort an: Jonny Lamb , 824...@bugs.debian.org An: sub...@bugs.debian.org Package: logwatch Version: 7.4.3-1 Severity: normal Tags

Bug#812528: Redundant argument in sprintf for postfix script

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 i

Bug#812528: Redundant argument in sprintf for postfix script

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 i

Bug#812393: logwatch has iptables, but not ip6tables

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 by

Bug#812235: /usr/sbin/sendmail: setuid/setgid: Operation not permitted

pn couriergrey ii evolution [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 Date:

Bug#809756: Clarification

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.

Bug#805030: libssh: newer upstream versions?

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 t

Bug#805030: libssh: newer upstream versions?

ry version), the other removes the -dbg package as they are now built automatically. Bye Willi From 2792f1aa02aaac6aaf1570c3d16d17e13241bad4 Mon Sep 17 00:00:00 2001 From: Willi Mann Date: Sat, 9 Jan 2016 16:37:49 +0100 Subject: [PATCH 1/2] debian/libssh-gcrypt-4.lintian-overrides: Adapt override

Bug#805030: libssh: newer upstream versions?

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 &

Bug#805030: libssh: newer upstream versions?

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

Bug#752337: setools: Logwatch script in wrong location, produces error when package is removed but not purged

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 wrote: >>>> Hi, >>>> >&

Bug#752337: setools: Logwatch script in wrong location, produces error when package is removed but not purged

Hi, Am 2015-12-28 um 01:28 schrieb Laurent Bigonville: > On Sun, 22 Jun 2014 21:14:55 +0200 Willi Mann wrote: >> >> Hi, >> >> I think the script /etc/logwatch/scripts/services/seaudit-report-service >> should be shipped in /usr/share/logwatch/scripts/services,

Bug#805030: libssh: newer upstream versions?

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

Bug#800468: crashes in liblmdb on start-up

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 libthread_db enabled] >> Using hos

Bug#800468: crashes in liblmdb on start-up

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, ret=0x7fffcd574788

Bug#797817: linklint: does not support HTTP 307 (temporary redirect) status code

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 p

Bug#795296: "You are not allowed to save the configuration" (both root and ordinary user)

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 I

Bug#792915: Logwatch fails to parse log statements

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

Bug#782653: openmpi: (non-)reproducibility of build failure

Hi! Am 2015-04-19 um 00:29 schrieb Mario Lang: > Willi Mann 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 >>

Bug#782033: kexec-tools: bug only when sysvinit is used

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 b/debian/kexec-loa

Bug#782669: enigmail: Can't decrypt messages vom "OpenPGP für Windows Phone"

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 de/store/app/openpgp-f%C3%BCr-windows-phone/0a1906e2-eb48-4cdb-bbab- > 30ea308b9065> I cannot decr

Bug#782653: openmpi: (non-)reproducibility of build failure

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

Bug#755722: should be fixed in jessie

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"

Bug#745195: fixed, but more testing intended

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

Bug#745195: status

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 upstrea

Bug#775933: enigmail: calls 'gpg --list-keys' before encrypting. This is slow, esp. with gpg2

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 larg

Bug#772811: unrtf: fixes for stable (CVE-2014-9274 CVE-2014-9275)

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 Descriptio

Bug#773748: unblock: unrtf/0.21.5-2

- Fix Invalid read of size 4 in attr_get_param +- attr_get_param(): Silence a warning message again + + -- Willi Mann 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

Bug#772811: unrtf: CVE-2014-9274 CVE-2014-9275

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 Wi

Bug#772811: unrtf: CVE-2014-9274 CVE-2014-9275

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 sch

Bug#771399: unblock: enigmail/2:1.7.2-3

3) unstable; urgency=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 Sun, 23 Nov 2014 15:47:07 +0100 + enigmail

Bug#769311: unblock: logwatch/7.4.1-2

tch-7.4.1/debian/changelog 2014-10-08 19:32: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.

Bug#769165: unblock: enigmail/2:1.7.2-2

table; urgency=medium + + * Update 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 Sun, 02 Nov 2014 19:12:49

Bug#749886: Processed: bug 749886 is forwarded to https://sourceforge.net/p/enigmail/bugs/361

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 c

Bug#765937: [enigmail] Incompatible with armhf

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 fixe

Bug#760845: reopen - needs more care

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

Bug#765937: [enigmail] Incompatible with armhf

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 p

Bug#752391: enigmail: icedove crashes with SIGSEGV when sending emails unencrypted while for one recpient a key is present

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

Bug#764515: ITP: libsys-meminfo-perl -- Perl module to query the total free and used physical memory

Package: wnpp Severity: wishlist Owner: Willi Mann * Package name: libsys-meminfo-perl Version : 0.98 Upstream Author : Sylvain Cresto > * URL : http://search.cpan.org/~scresto/Sys-MemInfo/MemInfo.pm * License : "same as Perl" Programming

Bug#761399: Adding suggestion to libsys-cpu-perl

e all Version: 7.4.1-1 Distribution: unstable Urgency: medium Maintainer: Willi Mann Changed-By: Willi Mann Description: logwatch - log analyser with nice output written in Perl Closes: 710146 Changes: logwatch (7.4.1-1) unstable; urgency=medium . * Imported Upstream version 7.4.1 (svn re

Bug#710146: Unmatched entries for apparmo

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 p

Bug#756186: logwatch: Uninitialized variable ($bb) in logwatch exim script.

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 >> >>

Bug#756186: logwatch: Uninitialized variable ($bb) in logwatch exim script.

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, line 3480. >>> >>> This looks to be an error in

Bug#756186: logwatch: Uninitialized variable ($bb) in logwatch exim script.

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, line 3480. > > This looks to be an error in initializing the $bb variable. Further > inve

Bug#590150: logwatch: Logwatch doesn't detect freshclam.log

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 followin

Bug#611205: logwatch: hostlimit doesn't work

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 ha

Bug#552309: reports unmatched entries for clamav-milter

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 > Sever

Bug#755834: Fails to install if interface list is empty

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 isc-dhcp-server

Bug#754538: sqwebmail fails to install due to non-existant /var/www directory

>> 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 nowada

Bug#754538: sqwebmail fails to install due to non-existant /var/www directory

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 man-d

Bug#754211: logwatch reports false positive kernel errors

-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.

Bug#745195: Fwd: Bug#745195: unrtf 0.21 outputs hex.junk to stdout

Original-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 Weitersenden-An: debian-bugs-dist@lists.debian.org Weitersenden-CC: Willi Mann Datum: Fri, 18 Apr 2014 20:48:5

Bug#749129: possible fix

ourier (0.73.1-1.2) UNRELEASED; urgency=low + + * Non-maintainer 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 +

Bug#752620: enigmail can't be installed anymore after icedove update from 2014-06-25

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

Bug#752337: setools: Logwatch script in wrong location, produces error when package is removed but not purged

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 scr

Bug#749931: ijsgutenprint: Fails on upgrade, with wheezy dpkg

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

Bug#749129: courier-mta-ssl: fails to install

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 (0.73

  1   2   3   4   5   6   >