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 u
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
do
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 th
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
Parti
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 pa
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
Processor:
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 wou
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 planni
me contributions.
Please 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,
tive
here, since it's pretty much impossible to fix on Debian's side once
it propogates to stable.
--
Duncan Findlay
pgpHI7unxXnUd.pgp
Description: PGP signature
e question is, to a certain extent, how many people use
anacron, and how many don't. If anacron is used, this shouldn't be a
problem.
--
Duncan Findlay
pgpvrIhGkWre2.pgp
Description: PGP signature
TW, the README.Debian has some old text about sa-update being manual
> and "quite new", which seems outdated now that there's a cron job.
Thanks; I'll update that too.
--
Duncan Findlay
pgpepSNqAdxUF.pgp
Description: PGP signature
nd makes no
> mention of needing 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
he first couple of paths listed are
set based 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
age "warning: please 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.
--
D
.9.x. (At least, I
haven't found 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
means you need to run sa-compile.
--
Duncan Findlay
pgpE9rtSEbnmf.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
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
other updates for this version of the package,
they should be available from 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 <[E
.
The SpamAssassin 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=3978&package_id=30227&release_id=507010
--
Duncan Findlay
--
To U
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 prefers
0: disable perl 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
discussed in this bug.
I think you need to make sure you 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
s
Which
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.
--
ven't closed this bug is because I can't figure
out where this is documented. :-)
--
Duncan Findlay
pgpSQa2JpCkgg.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.
> Ho
estarting spamassassin it should
automatically find the new sa-update location.
--
Duncan Findlay
pgpHS4BDHiwbA.pgp
Description: PGP signature
correct?
Does this make sense?
--
Duncan Findlay
pgpzkKCUwL3qi.pgp
Description: PGP signature
42] dbg: config: using "/home/andrew/.spamassassin" for user state dir
> [10242] dbg: config: using "/home/andrew/.spamassassin/user_prefs" for user
> prefs file
> [10242] dbg: config: read file /home/andrew/.spamassassin/user_prefs
What's in /var/lib/spamassassin/3.
duce the bug.
--
Duncan Findlay
signature.asc
Description: Digital signature
ges I'm missing.
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
Could you provide it?
What are the permissions on it?
--
Duncan Findlay
signature.asc
Description: Digital signature
amAssassin/show_bug.cgi?id=4696 FWIW).
http://mail-archives.apache.org/mod_mbox/spamassassin-users/200604.mbox/[EMAIL
PROTECTED]
--
Duncan Findlay
signature.asc
Description: Digital signature
I don't think it'd be terribly
> obvious to a new user.
Whoops!
Now I see 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
or Razor and use 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
nt when 3.1.1 is released.
--
Duncan Findlay
signature.asc
Description: Digital signature
ld you please include 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
signa
n't caused me any problems, but you
> should keep an eye 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
e one message through, but not take down spamd, AFAIK.
--
Duncan Findlay
signature.asc
Description: Digital signature
options are you using with spamd (in /etc/default/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
l function: __HABEAS_SWE: 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
e set
them and try checking this e-mail again? You may find 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
s package 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. Reassig
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 ins
thout libnet-dns-perl
(unless you use an ipv6 nameserver and don't have libsocket6-perl),
and without libmail-spf-query-perl. The error messages even go away if
you set "dns_available no" in /etc/spamassassin/local.cf and comment
out "loadplugin Mail::SpamAssassin::Plugin::SPF" in
/etc/spamassassin/init.pre
--
Duncan Findlay
signature.asc
Description: Digital signature
sa-learn and spamassassin
> seems to perform much 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
less likely
> 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
erl, even
> 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
turning "Error: unable to setuid/.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
> > th
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
> > th
ebian?
--
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
n 3.2.
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]
I created from the
original upstream bug report.
This must be something else.
--
Duncan Findlay
signature.asc
Description: Digital signature
versions 3.0.1, 3.0.2, and 3.0.3. 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 Findl
aintainers knowing/desiring it, but users
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 r
x27;unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-2-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions 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
libraries. :-)
--
Duncan Findlay
signature.asc
Description: Digital signature
is so limited. :-(
I'm going 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]
something fairly obvious to be that badly
> wrong... the filenames in the stat() and open() calls don't even
> match. It doesn't appear to be related to the input data, so it's
> probably a race condition.
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
Package: apt
Version: 0.6.25
Severity: important
Tags: experimental
As of recently, apt-get seems to no longer be able to verify
signatures. I'm not sure if this is a problem with the mirrors or if
it's a flaw in apt-get which may have resulted from some upgrade
pacakge or something.
Anyways, her
top of our heads.
If you feel obliged to respond to this mail, don't 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
clone 290501 -1
reassign 290501 debbugs
reassign -1 spamassassin
severity -1 normal
thanks
This is a well publicised API change. I can put a Conflicts: for
debbugs (<= current-version), but that's it. I don't think this is RC
for spamassassin.
--
Duncan Findlay
signature.as
69 matches
Mail list logo
