Thanks for the bug report JorgeAxel, thanks for the patch, I'll upload
ASAP
El vie, 24-03-2017 a las 02:46 +0100, Axel Beckert escribió:
> Control: tag -1 + patch
>
> Hi Jorge and Hector,
>
> Jorge Moraleda wrote:
> > mssh incorrectly installs local files to /usr/@DATADIRNAME@/locale
>
> Jorge:
Thanks,
I'm fixing the upstream code first, I'll update the package ASAP
El lun, 08-06-2015 a las 14:22 +0200, Rodolphe PELLOUX-PRAYER escribió:
> Package: mssh
> Followup-For: Bug #788017
>
> This issue could be fixed by applying these two patches.
>
> The first one is to port mssh to vte-2.91
I just uploaded a new version of mssh 1.3
Unfortunately I have no access to an environment like the one you
describe.
Could you please test this new version and tell me if the bug still
applies?
Regards,
Héctor
Hi,
I cannot reproduce the bug either.
Can you give me more info?
Please, execute xcdroast on a terminal and send me the output please.
Regards,
Héctor
severity 393575 normal
thanks
El lun, 16-10-2006 a las 23:22 +0200, Aurelien Jarno escribió:
> Package: lirc
> Version: 0.8.0-7
> Severity: serious
> Justification: Policy 10.6
>
> Maintainer scripts should not create device files directly. They should
> call makedev instead. Refer to Policy Man
Why don't you ask before doing an NMU?.
You didn't test the patch, did you?
Because it has a bug which break old working behavior.
Now cdrecord.proDVD doesn't work (which even in been non free, it will
break working instalations).
Regards,
Héctor
P.D: Please, even in 0-day NMU period send a "I'm
El lun, 31-07-2006 a las 14:24 +0200, Riccardo Stagni escribió:
> On Mon, Jul 31, 2006 at 01:30:40PM +0200, Nico Golde wrote:
> > I thought about your solutions but here comes mine :)
> > From fetchmail(1):
> > Normally, calling fetchmail with a daemon in the background sends a
> > wake-up signal
Package: wnpp
Severity: normal
I do not have a system using zmailer any longer, so I consider that someone
else should be more able to maintain properly the package.
Héctor
Hi Xavier,
Can you confirm if this bug still applies to current version? 6.3.4-1
There have been quite a few changes on latest versions.
In case you can reproduce it, please send the output from
strace -tt -e trace=network -p $(head -n1 /var/run/fetchmail/fetchmail.pid)
Regards,
Héctor
El vie, 12-05-2006 a las 03:52 +0200, Matthias Andree escribió:
> The attached patch has been committed to the upstream SVN repository
> and is supposed to fix the issue.
>
This weekend I'll try to upload a package with this patch to
experimental, so it can be tested.
Regards,
Héctor
tags 283203 + patch
thanks
Here there is a patch for pnmquant to allow it to use stdin as input.
Regards,
Héctor
--- pnmquant.orig 2006-04-26 11:35:30.0 +0200
+++ pnmquant 2006-04-26 11:32:47.0 +0200
@@ -9,6 +9,7 @@
use Getopt::Long;
use File::Temp "tempfile";
use File::Spec;
El lun, 13-03-2006 a las 16:26 +0100, Francesco Potorti` escribió:
> Generally speaking, a trace that does not log date and time is an error:
> you don't know when things happened. If the log is in the same format
> as it is now, but with time logged, that would be a great improvement.
>
True, bu
El dom, 05-03-2006 a las 11:42 -0800, Kevin Dalley escribió:
> Package: fetchmail
> Version: 6.3.2-2
> Severity: serious
> Justification: Policy 9.1.1
>
> fetchmail uses the file /var/lib/fetchmail/.fetchmail.pid, which is
> not cleaned up on startup. A system crash causes fetchmail to believe
>
El lun, 13-03-2006 a las 12:19 +0100, Francesco Potorti` escribió:
> Package: fetchmail
> Version: 6.3.2-2
> Severity: normal
>
> I track testing. When passing from 6.3.1 to 6.3.2, fetchmail stopped
> logging like this:
>
...
> That is, the time and date of getting mail is missing, and moreover
El vie, 17-02-2006 a las 17:13 +0100, Stephan Kramer escribió:
> Sorry to attach to resolved bug, but I'm not really content with the way this
> transition is done. I'm assuming most people when asked whether they want to
> replace a fetchmail configuration file, would respond No as they don't wan
package fetchmail
close 348302
thanks
This bug is already fixed. If you don't like the upgrade path please
open a new bug stating that.
> To me, a non-Debian bystander,
> this looks like rewording the question might already do the job.
Maybe, but that would be another bug, and please don't reope
El jue, 19-01-2006 a las 13:34 +0100, Gilles escribió:
> Package: fetchmail
> Version: 6.3.1-4
> Severity: normal
>
> Hi.
>
> The error:
>
> Setting up fetchmail (6.3.1-4) ...
> usermod: invalid option -- -
> Usage: usermod [-u uid [-o]] [-g group] [[-G group,...] [-a]]
> [-
El lun, 16-01-2006 a las 08:37 +0100, Eduard Bloch escribió:
> Package: fetchmail
> Version: 6.3.1-2
> Severity: normal
>
> Hello,
>
> after upgrading fetchmail to the recent version, it does no longer
> start and tells me to "Edit /etc/default/fetchmailrc". I did, but could
> not find the proble
Package: perforate
Version: 1.1-2
Severity: wishlist
Tags: patch
Here is a patch to give finddup the functionality to define the dirs it
should look into.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architect
Ok, I tested
ii linux-image-2.6.14-rc5-686 2.6.13+2.6.14-rc5-0experimental.1 Linux
kernel 2.6.14 image on PPro/Celeron/PII/PIII/P4 machines
and not only I get the same error but continues a little bit. It adds,
BUG: soft lockup detected on CPU#0!
Pid: 1, comm: Swapper
and
El mar, 25-10-2005 a las 10:26 +0200, Sven Luther escribió:
> On Tue, Oct 25, 2005 at 10:11:30AM +0200, Héctor García wrote:
> > Package: linux-image-2.6.13-1-386
> > Version: 2.6.13-1
> > Severity: critical
> > Justification: breaks the whole system
> >
> >
Package: linux-image-2.6.13-1-386
Version: 2.6.13-1
Severity: critical
Justification: breaks the whole system
On booting this image and also booting the -1-686 image I get the same
error.
PCI: Cannot allocate resource region 7 of bridge :00:10.1
PCI: Cannot allocate resource region 8 of bridg
El mar, 04-10-2005 a las 13:08 +0200, Nico Golde escribió:
>...
>
> I request assistance with maintaining the fetchmail package.
>
>...
Well, I use for my everyday mail and I'm starting to again have time for
Debian, so as soon as I put my packages up-to-date (a couple of weeks),
I'll write you
> You did notice that the author claims the problems not to be exploitable,
> right?
Yes, right before the original submitter claims that is it indeed
exploitable.
> Should be fixed anyway, but without further investigation it may
> not require a CVE id or a DSA.
>
My understanding of the expl
El vie, 25-03-2005 a las 21:54 +0100, Moritz Muehlenhoff escribió:
> Package: smail
> Severity: grave
> Tags: security patch
> Justification: user security hole
>
> [Dear security-team, this should affect Woody as well]
>
> Sean <[EMAIL PROTECTED] has discovered two vulnerabilities in smail,
> th
25 matches
Mail list logo
