I tried reproducing this issue with several modified versions of
aardvark-dns to see if I could narrow down the cause.
I could not reproduce this with upstream source at head, nor with
upstream source at v1.0.3.
I did reproduce this issue both with the debian packaged version of
1.0.3, and with
Package: aardvark-dns
Version: 1.0.3-1+b1
Severity: important
DNS resolution of container names seems to fail from inside podman
containers with podman 4 and the netavark backend, both with rootless
and rootful containers.
>From what I can tell, it looks like aardvark-dns sees the queries, but
I can confirm that recompiling the kernel with CONFIG_RMI4_SMB=m (and only
that change) is sufficient to make the Touchpad & TrackPoint usable on the
X1 Carbon 6th gen. Without this, it's completely unusable.
This is a regression -- a Debian 9.6 (stretch) live CD does not have this
problem with
Package: installation-reports
Severity: normal
-- Package-specific info:
Boot method: USB
Image version: Buster Alpha 3 netinst ISO
https://cdimage.debian.org/cdimage/buster_di_alpha3/amd64/iso-cd/debian-buster-DI-alpha3-amd64-netinst.iso
Date: 2018-12-02
Machine: Lenovo X1 Carbon 6th Gen
Package: wnpp
Severity: normal
Yikes, my last upload of purity was over 7 years ago. I think there have been
approximately 2 bugs filed in that time. Unfortunately the packaging is really
out of date, and it needs some serious work.
I intend to resign from the project, so I am orphaning this
Package: installation-reports
Boot method: Netinst daily
Image version: (version verified from md5sum)
http://cdimage.debian.org/cdimage/daily-builds/daily/20090922-1/i386/iso-cd/debian-testing-i386-netinst.iso
Date: September 21, 2009
Machine: VMWare Fusion 2.05 on Apple MacBook Pro
Hi,
As others have pointed out, this bug is not fixed for users upgrading
from previous versions. Would it be possible to provide a warning of
some sort when the initramfs is too big and large-memory is not used?
At the very least, some information about this in the lilo
documentation
On Sep 22, 2008, at 2:54 AM, Philipp Kern wrote:
On Sun, Jul 20, 2008 at 11:16:30PM +0100, Justin Mason wrote:
this is indeed fixed upstream, but in SVN trunk:
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=4964#c22
I haven't even tried the patch against 3.2.x, as we weren't
let me know if you have any questions, comments or
concerns. Thanks in advance!
Duncan Findlay
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi,
Unless I've missed something, the patch for bug 366493 has
disappeared from the internet. It's not attached to the bug report,
and I can't find evidence of it in the vnc-list mail archives. Could
someone please post the patch to this bug report?
Thanks,
Duncan
--
To UNSUBSCRIBE,
to fix on Debian's side once
it propogates to stable.
--
Duncan Findlay
pgpHI7unxXnUd.pgp
Description: PGP signature
don't. If anacron is used, this shouldn't be a
problem.
--
Duncan Findlay
pgpvrIhGkWre2.pgp
Description: PGP signature
now that there's a cron job.
Thanks; I'll update that too.
--
Duncan Findlay
pgpepSNqAdxUF.pgp
Description: PGP signature
gcc.
Ah, good catch; I hadn't considered people without gcc and
libc6-dev... those people exist? :-P *duck*
I'll add a suggests: gcc and libc6-dev and update the README.
--
Duncan Findlay
pgptOyuDbuoUV.pgp
Description: PGP signature
a problem with it.)
I'd be happy to co-maintain the package if you would like a
co-maintainer. (Though I'm not going to have much time for Debian in
the next couple of weeks.)
--
Duncan Findlay
pgpdCWaUnm1oF.pgp
Description: PGP signature
run sa-compile
and then ignoring the plugin instead not starting and emiting something
that looks like a bug?
Spamd still runs, so it's just a spurious scary looking warning
message. I believe it has been fixed in the next upstream version.
--
Duncan Findlay
pgp89HJDeJ2Tw.pgp
Description: PGP
on the way spamassassin is installed and the last ones are
hardcoded defaults.
I'm not sure if it's a good idea to fix it; at the very least I think
it's somewhat complicated.
--
Duncan Findlay
pgpRSbs8hRGT9.pgp
Description: PGP signature
-compile.
--
Duncan Findlay
pgpE9rtSEbnmf.pgp
Description: PGP signature
Package: svn-buildpackage
Version: 0.6.18
Severity: minor
The svn-upgrade manpage refers to svn-buildpackage instead of
svn-upgrade (as the name of the command). I recommend a find/replace
from 'svn-buildpackage' to 'svn-upgrade'. :-)
-- System Information:
Debian Release: lenny/sid
APT
info is here, including a patch to 2.82:
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5312
Version 2.83 of Razor is available here:
http://sourceforge.net/project/showfiles.php?group_id=3978package_id=30227release_id=507010
--
Duncan Findlay
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
the subversion repository, once I commit
them. (Revision 88 on the trunk is pre-3.2.0)
svn://svn.debian.org/pkg-sa/spamassassin/trunk
--
Duncan Findlay
#! /bin/sh -e
## 10_edit_config_paths.dpatch by Duncan Findlay [EMAIL PROTECTED]
##
## All lines beginning with `## DP:' are a description of the patch
tag 377909 + fixed-upstream
thanks
Committed a change to upstream SVN, should be found in 3.2.1.
--
Duncan Findlay
pgpMbygbcCdoq.pgp
Description: PGP signature
tag 402241 + pending
thanks
The documentation changes have been committed upstream and will be in
3.2.1.
--
Duncan Findlay
pgpU9QaFIEOFJ.pgp
Description: PGP signature
module usage in update channels unless
--allowplugins is specified
These fixes have been applied in 3.1.7-2 which is awaiting propogation
to testing.
3.1.8 will be uploaded later.
--
Duncan Findlay
pgphc9cxHRecV.pgp
Description: PGP signature
aren't using the -c/--create-prefs
option for spamd (usually set in /etc/default/spamassassin), and if
this isn't enough, make sure you turn off use_bayes in the
spamassassin configuration. Please open a new bug if this isn't
sufficient.
Sorry for the delay in replying.
--
Duncan Findlay
version of razor are you using?
--
Duncan Findlay
pgplhieQLpPw3.pgp
Description: PGP signature
severity 402241 normal
thanks
On Thu, Dec 14, 2006 at 01:49:38PM +0100, Kjetil Kjernsmo wrote:
I think this bug should be downgraded, it is surely not an RC bug.
Downgrading to normal. This is definitely not RC, arguably it's a
documentation bug.
Thanks for the reminder, Kjetil.
--
Duncan
closed this bug is because I can't figure
out where this is documented. :-)
--
Duncan Findlay
pgpSQa2JpCkgg.pgp
Description: PGP signature
spamassassin it should
automatically find the new sa-update location.
--
Duncan Findlay
pgpHS4BDHiwbA.pgp
Description: PGP signature
On Wed, Oct 04, 2006 at 09:14:25PM +0200, martin f krafft wrote:
also sprach Duncan Findlay [EMAIL PROTECTED] [2006.10.04.2110 +0200]:
I believe this is incorrect. After restarting spamassassin it
should automatically find the new sa-update location.
How?
It looks in /var/lib/spamassassin
... is that correct?
Does this make sense?
--
Duncan Findlay
pgpzkKCUwL3qi.pgp
Description: PGP signature
/.spamassassin/user_prefs for user
prefs file
[10242] dbg: config: read file /home/andrew/.spamassassin/user_prefs
What's in /var/lib/spamassassin/3.001001? Did you create this
directory yourself? Did you run sa-update?
--
Duncan Findlay
signature.asc
Description: Digital signature
.
--
Duncan Findlay
signature.asc
Description: Digital signature
you provide it?
What are the permissions on it?
--
Duncan Findlay
signature.asc
Description: Digital signature
.
The logcheck entry:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ spamd\[[0-9]+\]: prefork: child states: I+$
is a bit restrictive. Child states other than I can and will occur in the
normal functioning of spamassassin.
Thanks,
--
Duncan Findlay
signature.asc
Description: Digital signature
FWIW).
http://mail-archives.apache.org/mod_mbox/spamassassin-users/200604.mbox/[EMAIL
PROTECTED]
--
Duncan Findlay
signature.asc
Description: Digital signature
the confusion. I didn't notice the typo in the error
message. --max-clients is apparently a typo for --max-children. This
is fixed in the to be packaged 3.1.1.
--
Duncan Findlay
signature.asc
Description: Digital signature
it if available.
I believe this is false for the 3.1.x (and up) versions of
spamassassin (in testing and unstable). In these version, razor is
disabled by default.
--
Duncan Findlay
signature.asc
Description: Digital signature
is released.
--
Duncan Findlay
signature.asc
Description: Digital signature
this patch? I'm not sure if it should even
be filed as security incident.
This does not qualify as a security issue, and as a result, it is
extremely unlikely to make it to sarge. I will update the package in
sid when 3.1.1 is released.
--
Duncan Findlay
signature.asc
Description: Digital signature
on spamd after applying this patch to make sure it
isn't doing something wrong.)
Hmm... my understanding of the bug is that if spamd is started up
without network, it complains (loudly) but continues to work without
network tests. Is this not the case?
--
Duncan Findlay
signature.asc
Description
down spamd, AFAIK.
--
Duncan Findlay
signature.asc
Description: Digital signature
: message_is_habeas_swe( ) at
/usr/share/perl5/Mail/SpamAssassin/Conf/Parser.pm line 693.
This is a configuration error. Try spamassassin --lint to track down
where it is.
--
Duncan Findlay
signature.asc
Description: Digital signature
/spamassassin)?
It looks like you're using vpopmail, is this correct? With what
options are you calling spamc with?
--
Duncan Findlay
signature.asc
Description: Digital signature
because of the note
on http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=334687 .
At least now you know that you are not the only one seeing the error message!
This bug must be a libmail-spf-query-perl bug -- SpamAssassin
definitely does not look for LMAP::CID2SPF. Reassigning.
--
Duncan
that it will no
longer hit. (Either way, please let me know.)
I'm going to add a note about trusted_networks to the README.Debian.
--
Duncan Findlay
signature.asc
Description: Digital signature
On Sat, Nov 05, 2005 at 10:03:16PM -0800, Don Armstrong wrote:
On Sun, 06 Nov 2005, Duncan Findlay wrote:
On Sat, Nov 05, 2005 at 07:18:16PM -0800, Don Armstrong wrote:
libnet-dns-perl is now required by M::SA::Dns
If it's not installed, a warning message is issued, spamassassin
still
Mail::SpamAssassin::Plugin::SPF in
/etc/spamassassin/init.pre
--
Duncan Findlay
signature.asc
Description: Digital signature
better with the same spams and the same bayesian
database and the same configuration.
Can you provide the output of sa-learn --dump magic --debug please?
--
Duncan Findlay
signature.asc
Description: Digital signature
to read the logs closely...
You don't happen to have a patch do you? I don't use logcheck, so
patches are welcome. (Not necessary, I can figure it out without a
patch, but it'd be nice!) :-)
--
Duncan Findlay
signature.asc
Description: Digital signature
though it is depended on by Net::DNS::Resolver.
Perhaps reassign this as a bug to libnet-dns-perl?
I need to look into this further, but cloning and reassigning to
libnet-dns-perl so Florian can take a look at it too.
Thanks,
--
Duncan Findlay
signature.asc
Description: Digital signature
On Fri, Sep 02, 2005 at 02:40:14PM -0600, Bob Proulx wrote:
merge 325887 213979 178277
thanks
Duncan Findlay wrote:
I'm a couple steps ahead of you :-)
This is fixed in experimental, and will go into unstable when
spamassassin 3.1.0 is released.
Very good! I will try
/.spamassassin.
web:~# vuserinfo -d [EMAIL PROTECTED]
/var/lib/vpopmail/domains/test.bogus/giuseppe
web:~#
It seems ok...
Maybe it has to do with the environment from which you call
spamc/spamd.
--
Duncan Findlay
signature.asc
Description: Digital signature
On Wed, Aug 17, 2005 at 03:14:41AM -0300, Henrique de Moraes Holschuh wrote:
On Tue, 16 Aug 2005, Duncan Findlay wrote:
This looks like it's just a timeout. Sometimes if SpamAssassin is
expiring Bayes tokens, it can take longer than ususal, and it appears
this is triggering a timeout
On Wed, Aug 17, 2005 at 03:14:41AM -0300, Henrique de Moraes Holschuh wrote:
On Tue, 16 Aug 2005, Duncan Findlay wrote:
This looks like it's just a timeout. Sometimes if SpamAssassin is
expiring Bayes tokens, it can take longer than ususal, and it appears
this is triggering a timeout
.
About the spamd group: spamassassin does not create a spamd user or
group - that was done locally.
--
Duncan Findlay
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
reassign 299804 perl
thanks
Spamd is segfaulting really early on here, so it's probably a perl
bug... (Sorry Brendan)
--
Duncan Findlay
signature.asc
Description: Digital signature
?
--
Duncan Findlay
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
bug report.
This must be something else.
--
Duncan Findlay
signature.asc
Description: Digital signature
. The
vulnerability allows certain misformatted long message headers to cause
spam checking to take a very long time.
A fixed package has already been given to the security team - but as
of yet they have failed to act on it.
--
Duncan Findlay
signature.asc
Description: Digital signature
should feel free to ask maintainers.
Even if Duncan Findlay decides that Spamassassin needs to be included
into volatile, it is up to him to contact the volatile team.
Right, and a bug report is a gentle prod in the right direction. This
bug report would be perfectly acceptable if it weren't
of packages perl-modules depends on:
ii perl 5.8.6-1Larry Wall's Practical Extraction
-- no debconf information
--
Duncan Findlay
signature.asc
Description: Digital signature
. :-)
--
Duncan Findlay
signature.asc
Description: Digital signature
to keep trying.
Thanks for your work on this package.
What work? :-)
--
Duncan Findlay
signature.asc
Description: Digital signature
.
Thanks,
Duncan Findlay
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
.
Could you provide any configuration files that might be relavent? I've
never seen files starting with __db.bayes_toks. Did you change your
Bayes database path?
--
Duncan Findlay
signature.asc
Description: Digital signature
hold your breath
for a response, you likely won't get one. You have the right to appeal
to the Technical Committee if you so desire.
I'm done dicussing this.
--
Duncan Findlay
signature.asc
Description: Digital signature
67 matches
Mail list logo
