On Tue, Sep 27, 2022 at 07:28:22PM +0200, Matus UHLAR - fantomas wrote:
> the /etc/init.d/spamd init script loads /etc/default/spamassassin while
> package is bundled with /etc/default/spamd
>
> this is apparently unintentional
>
>
> It may be welcome when upgrading from versions <4 if admin con
Adding some tracing to the dhclient-script, I can see that
/etc/dhcp/dhclient-exit-hooks.d/rfc3442-classless-routes is trying to add
the routes with calls like:
ip -4 route add 169.254.169.254/32 via 169.254.0.1 dev ens5
However, because there's no route to 169.254.0.1, the call fails with
"Error
Package: cloud.debian.org
Severity: important
User: cloud.debian@packages.debian.org
Usertags: aws image
When AWS originally launched IPv6-only VPC subnets, the DHCPv4 server
handed out a link-local v4 address and a default route that was a
blackhole for most destinations. It did route traffi
Package: cloud.debian.org
Severity: normal
User: cloud.debian@packages.debian.org
Usertags: aws infrastructure
Per recent email from AWS, we need to update the usage instructions associated
with our AWS Marketplace AMI listings. The requirements are documented at
https://docs.aws.amazon.com/m
-0700
@@ -1,3 +1,10 @@
+dovecot (1:2.3.13+dfsg1-2+deb11u1) bullseye; urgency=medium
+
+ * [4b5dac8] d/patches: cherry-pick fix for CVE-2022-30550 (Closes: #1016351)
+ * [597ba7f] salsa-ci: build with bullseye
+
+ -- Noah Meyerhans Sun, 31 Jul 2022 17:47:06 -0700
+
dovecot (1:2.3.13+dfsg1-2
Control: tags -1 + pending
The fix targeting sid is pending review on salsa.
My inclination is that this won't need a DSA and can wait for a bullseye point
release, but I'm open to other opinions.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu dovecot-fts-xapian_1.5.5-1 . ANY . unstable . -m "rebuild for
dovecot-abi-2.3.abiv19"
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu dovecot-antispam_2.0+20171229-1 . ANY . unstable . -m "rebuild for
dovecot-abi-2.3.abiv19"
Package: wnpp
Severity: wishlist
* Package name: libmail-dmarc-perl
Version : 1.20211209
Upstream Author : Marc Bradshaw
* URL : https://metacpan.org/pod/Mail::DMARC
* License : GPL-1+ or Artistic
Programming Lang: Perl
Description : Perl implementation
Package: spamassassin
Version: 4.0.0~0.0svn1899920-1
Severity: important
Tags: upstream experimental
Forwarded: https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7977
When passing an mbox file to sa-learn, expected training does not occur:
noahm@74805e6e29ad:/tmp$ sa-learn --spam --mbox < spam-2
Package: cloud.debian.org
Severity: normal
User: cloud.debian@packages.debian.org
Usertags: + aws infrastructure
The IDs for buster-backports AMIs for AWS are queryable via SSM public
parameters at /aws/service/debian/release/10-backports/ However, the release
pipeline is apparently not updat
On Sat, Mar 19, 2022 at 10:41:39AM +0100, Salvatore Bonaccorso wrote:
> > >From the upstream discussion on the linux-pci mailing list [*]:
> >
> > > Yes. My understanding is that the issue is because AWS is using older
> > > versions of Xen. They are in the process of updating their fleet to a
> >
>From the upstream discussion on the linux-pci mailing list [*]:
> Yes. My understanding is that the issue is because AWS is using older
> versions of Xen. They are in the process of updating their fleet to a
> newer version of Xen so the change introduced with Stefan's commit
> isn't an issue any
Control: reassign -1 src:linux
Control: forcemerge 1006346 -1
On Sat, Mar 12, 2022 at 01:21:23AM +, Reilly Brogan wrote:
> I bisected this issue and it was introduced in kernel 5.10.88 as commit
> e5949933f313c9e2c30ba05b977a047148b5e38c "PCI/MSI: Mask MSI-X vectors
> only on success", thus pr
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
dovecot-antispam needs to be rebuild against the latest dovecot ABI.
nmu dovecot-antispam_2.0+20171229-1+b9 . ANY . unstable . -m "rebuild for
dovecot-abi-2.3.abiv18"
Control: tags -1 + moreinfo
Hello Karsten,
On Fri, Feb 25, 2022 at 01:57:08PM +0100, karsten wrote:
> i think this is not a bug and spamassassin is simply not using the rules.
> First i have added my own rules to /etc/spamassassin/local.cf without success.
> Because this has no effect i put the f
Control: reassign -1 src:linux
Control: tags -1 + upstream
> Amazon EC2 instance types with Enhanced Networking use the ixgbevf.ko
> driver. The current AMIs successfully probe the ixgbevf driver and spawn
> dhclient as expected, but dhclient appears to never receive a lease. Older
> AMIs do wor
Package: cloud.debian.org
Severity: important
(I suspect this is actually a kernel issue, but I'm starting with
cloud.debian.org as that's where I've observed the issue and I want to rule
out cloud configuration issues.)
Amazon EC2 instance types with Enhanced Networking use the ixgbevf.ko
driver
On Tue, Feb 22, 2022 at 08:27:10PM +0100, Marco d'Itri wrote:
> On Feb 22, Noah Meyerhans wrote:
>
> > For servers, the ideal situation is somewhat less clear, but there was
> > at least some interest in using systemd-networkd (with or without
> > netplan).
> Why
On Tue, Feb 22, 2022 at 11:22:08AM +0200, Martin-Éric Racine wrote:
> Given how upstream ISC will stop development of its DHCP suite by the end of
> 2022 [1], Debian will need to select a new stock DHCP client to ship with
> Priority:Important.
>
> dhcpcd5 seems like the most potential replaceme
Control: tags -1 + pending
On Fri, Feb 18, 2022 at 10:16:23AM +0100, Vincent Lefevre wrote:
> I got the following mail due to sa-update error via /etc/cron.daily:
>
>
> /etc/cron.daily/spamassassin:
> config: invalid regexp for __URI_TR
Control: forarded -1 https://github.com/systemd/systemd/issues/22538
On Wed, Feb 16, 2022 at 08:11:15AM +0100, Michael Biebl wrote:
> Am 16.02.22 um 02:14 schrieb Noah Meyerhans:
> > However, starting with the systemd 250 upstream releases, configuration of
> > these i
Package: systemd
Version: 250.3-2
Severity: important
Dear Maintainer,
I'm using systemd-networkd on an Amazon EC2 virtual machine with the following
.network file:
admin@ip-10-0-0-80:~$ cat /etc/systemd/network/20-eni.network
[Match]
Driver=ena
[Link]
MTUBytes=9001
[Network]
DHCP=yes
IPv6Dupl
Control: reassign -1 src:dpkg
Control: severity -1 wishlist
> root@debian:~# ls -l `which ping`
> -rwxr-xr-x 1 root root 77432 Aug 23 19:08 /usr/bin/ping
> root@debian:~# getcap `which ping`
> /usr/bin/ping cap_net_raw=ep
> root@debian:~#
>
>
> This looks like a limitation that would only be pos
Control: tags -1 + bullseye
On Wed, Feb 02, 2022 at 08:36:22AM +0100, Binarus wrote:
> IMPORTANT NOTE:
> According to other reports of the same problem, ping behaves correctly when
> IPv6 is *not* disabled at the kernel command line, but *is* instead disabled
> via sysctl (e.g. sysctl -w net.ipv
On Thu, Dec 09, 2021 at 04:02:24PM +0100, Paul Gevers wrote:
> Source: python-boto
> Version: 2.49.0-3
> Severity: serious
We should probably pursue the removal of this package before the
bookworm release rather than trying to drag it forward for another
release. It's dead upstream in favor of th
On Sun, Dec 05, 2021 at 07:58:17PM +0300, Dmitry Alexandrov wrote:
> >> So what's happening with chromium in both sid and stable? I saw on
> >> d-release that it was removed from testing (#998676 and #998732), with a
> >> discussion about ending security support for it in stable.
> >
> > The pro
On Fri, Feb 26, 2021 at 06:58:50PM +0100, Vincent Blut wrote:
> > > I think the distinction is that the other packages that tweak sysctl
> > > values don't claim to be doing so on behalf of the kernel team. If
> > > the
> > > kernel team is responsible for the values being set, then the
> > > sett
Control: tags -1 + moreinfo
On Fri, Nov 19, 2021 at 01:55:09PM +0100, Michael Hatzold wrote:
>
>* What led up to the situation?
> apt dist-upgrade
>* What exactly did you do (or not do) that was effective (or
> ineffective)?
> apt dist-upgrade
>* What was the outcome of this acti
On Wed, Nov 10, 2021 at 05:05:12PM +0100, Martin Zobel-Helas wrote:
> Due to an update on the Azure side, it would be helpful to support the
> newer API version of IMDS within cloud-init, a patch, that didn't make
> it to stable, as of the time the change was made, changes on cloud-init
> weren't a
ven release's feed with by looking for
strings like "bullseye not affected by" in the log.
Note that this change is implemented on top of the changes from webwml
mr !737.
>From b13f0185aa73b7dcf40c1e204cde5ba79d1b9226 Mon Sep 17 00:00:00 2001
From: Noah Meyerhans
Date: Mon, 8 Nov 2
Package: security.debian.org
Severity: important
X-Debbugs-Cc: s...@debian.org
There are two classes of issue with different statuses in the
security-tracker database and JSON feed that are not distinguished in the
OVAL feeds. Consider the following two entries from the bullseye oval
feeds[1]:
C
Package: libnginx-mod-http-lua
Severity: wishlist
Tags: patch
Currently libnginx-mod-http-lua declares architecture-specific build-deps to
choose either liblua5.1 or libluajit-5.1. For the arm64 architecture,
liblua5.1 is used even though luajit is availabile on this architecture.
I've locally b
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: dovecot-antis...@packages.debian.org, dove...@packages.debian.org
nmu dovecot-antispam_2.0+20171229-1 . ANY . unstable . -m "rebuild for
2.3.abiv16"
Dovecot-antispam needs a r
On Thu, Sep 09, 2021 at 09:35:05PM +0200, Paul Gevers wrote:
> > Warning: `wicd` will no longer be available after the upgrade, so if
> > you use it to connect to the internet through wifi, you will be cut
> > off. To prevent this, you should change to a connection manager that
> > *will* stil
Control: tag -1 - moreinfo
On Sat, Sep 04, 2021 at 10:45:26AM +0100, Jonathan Wiltshire wrote:
> Control: tag -1 confirmed moreinfo
>
> On Fri, Aug 13, 2021 at 03:07:46PM -0600, Ross Vandegrift wrote:
> > The version of sudo in bullseye introduces a new syntax for includes,
> > "@includedir". Th
Package: cloud.debian.org
Severity: wishlist
User: cloud.debian@packages.debian.org
Usertags: aws image
AWS has recently announced that VPC-internal services are available via
IPv6. In order to facilitate deployments that don't configure IPv4
addresses, we should enable support for accessing
On Tue, Aug 31, 2021 at 12:20:31PM +, Jeremy Stanley wrote:
> On 2021-08-31 10:54:02 + (+), Anton Scharnowski wrote:
> [...]
> > We run an OpenStack platform. The Issue leads to no IPv6 capabilty
> > on the VM until you manually execute a DHCPv6 request.
> [...]
>
> As an aside, do not
Control: tags -1 + upstream fixed upstream
On Tue, Jan 12, 2021 at 01:57:27PM +0100, Matteo Croce wrote:
> At boot cloud-init waits 120 seconds for an ephemeral disk, but some
> VM types doesn't have ephemeral storage at all, so this just blocks
> the boot for 120 seconds:
>
> Jan 12 11:23:13 mcr
Control: tags -1 + moreinfo
On Mon, Aug 23, 2021 at 04:39:55PM -0700, Francois Marier wrote:
>
> When I run "spamassassin -r" from mutt, I get the following error:
>
> Can't locate Mail/SpamAssassin/Bayes.pm:
> /var/lib/spamassassin/compiled/5.032/3.004006/Mail/SpamAssassin/Bayes.pm:
> Per
On Wed, Aug 18, 2021 at 10:59:01PM +1000, James Healy wrote:
> I note there's some discussion in #966573 about packaging v2 and there's
> some complexity there.
>
> With the bullseye freeze over and the v2 plans uncertain, are you open
> to updating this package to the most recent release in the 1
> [ Tests ]
>
> The upstream fix adds a unit test for this issue. This and the other tests
> pass during package build.
Also note that the patch is included upstream with 21.2-1, which is
currently in unstable and has been tested.
noah
On Wed, Aug 11, 2021 at 08:11:27PM -0600, Ross Vandegrift wrote:
> > > 2. I will implement a temporary change to our bullseye images to revert
> > > the
> > >sudoers file to use the old syntax that cloud-init will detect.
> >
> > This is implemented by
> > https://salsa.debian.org/cloud-team/
On Wed, Aug 11, 2021 at 02:05:39PM -0700, Noah Meyerhans wrote:
> 2. I will implement a temporary change to our bullseye images to revert the
>sudoers file to use the old syntax that cloud-init will detect.
This is implemented by
https://salsa.debian.org/cloud-team/debian-cloud-
On Sat, Aug 07, 2021 at 08:30:17PM -0600, Ross Vandegrift wrote:
> > > > In the sudoers file there is a duplicate includedir
> > > > statement; at the end of the file you will find the following contents:
> > > >
> > > > """
> > > > # See sudoers(5) for more information on "@include" directives:
>
Control: severity -1 important
Please see https://www.debian.org/Bugs/Developer#severities
On Wed, Jul 28, 2021 at 05:22:43PM +0200, Thomas Goirand wrote:
> After spawning a VM, it takes a long time to get networking (output from
> the console):
>
> cloud-init[281]: Cloud-init v. 20.2 running 'i
-controlled location
- CVE-2021-33515: Sensitive information could be redirected to an
attacker-controlled address because of a STARTTLS command injection
bug in the submission service
-- Noah Meyerhans Tue, 20 Jul 2021 08:05:19 -0700
[ Impact ]
We release bullseye with known
On Mon, Jul 19, 2021 at 08:21:45AM -0700, Noah Meyerhans wrote:
> > > CVE-2021-33515[0]:
> > > | The submission service in Dovecot before 2.3.15 allows STARTTLS
> > > | command injection in lib-smtp. Sensitive information can be redirected
> > >
On Sat, Jul 17, 2021 at 09:05:32PM +0200, Salvatore Bonaccorso wrote:
> > CVE-2021-33515[0]:
> > | The submission service in Dovecot before 2.3.15 allows STARTTLS
> > | command injection in lib-smtp. Sensitive information can be redirected
> > | to an attacker-controlled address.
> >
> > https://d
Package: amazon-ec2-utils
Version: 1.3+git20200518-2
Severity: normal
The primary purpose of the amazon-ec2-utils package is to install some udev
rules to configure various hardware conveniences. For example, these
install symlinks providing compatibility symlinks for block devices such
that /dev
Control: severity -1 wishlist
Control: forwarded -1 https://github.com/aws/aws-cli/issues/6186
awscli v2 remains quite difficult to package, but it seems that upstream
is looking to address this. See
https://github.com/aws/aws-cli/issues/6186 for details and tracking.
We'll continue to track ups
On Thu, Jun 17, 2021 at 05:54:03AM +, Yuhua Zou wrote:
>The version of package cloud-init in official repository of Debian 10.9 is
>20.2.
>This version 20.2 is far behind the latest released version 21.2.
>Please check [1]https://github.com/canonical/cloud-init
>
>With clou
On Mon, Jun 07, 2021 at 11:00:42PM +0200, Vladimir Tiukhtin wrote:
> I use "ca-certs" to supply additional certificates. With just one certiticate
> everything
> works as expected, however when provided more than one, cloud-init adds them
> into a single
> file which causes "openssl rehash" to fa
Control: tags -1 - moreinfo
On Sat, May 29, 2021 at 01:34:22PM +0200, Sebastian Ramacher wrote:
> > The 3.4.6-1 debdiff is at
> > https://people.debian.org/~noahm/spamassassin_3.4.6-1.debdiff
>
> Assuming that the upload happens soon, please go ahead with 3.4.6-1
> together with the fix for #9470
Discussing the path forward for bullseye with the release team in
#988686
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
We briefly discussed spamassassin 3.4.6-1 as a new upstream release for
bullseye in #987022. To quote the original request:
> If it was completely up to me, I'd want 3.4.6-1 released with
On Mon, May 17, 2021 at 07:57:23PM +0200, Guillem Jover wrote:
> > -if [ $code -eq 104 ] && \
> > -! command -v systemctl > /dev/null ; then
> > -# We're not using systemd and thus may have some sysvinit cleanup
> > -# to do in order to comply with policy 9.3.3.1
> >
-if [ $code -eq 104 ] && \
-! command -v systemctl > /dev/null ; then
-# We're not using systemd and thus may have some sysvinit cleanup
-# to do in order to comply with policy 9.3.3.1
-
-if [ -z "$ENABLED" -o "$ENABLED" = 0 ]; then
-# The rc?d sy
Control: tags -1 - moreinfo
On Tue, Apr 20, 2021 at 02:26:00PM -0700, Noah Meyerhans wrote:
> On Tue, Apr 20, 2021 at 08:53:48PM +0200, Ivo De Decker wrote:
> > > The debdiff for 3.4.6-1 is at [5]. The debdiff for 3.4.5~pre1-4 is at
> > > [6].
> >
> > I s
On Mon, May 10, 2021 at 09:00:34PM +0200, Moritz Mühlenhoff wrote:
> > Hi, since this package was brought into Debian in ~2018, there have been
> > several transformations in the GCE guest software stack and thus the
> > current landscape is very different. Google doesn't actually maintain the
> >
Control: unarchive 964596
Control: forcemerge 964596 954321
Control: archive 964596
This was resolved with the release of the Debian 10.5 AMIs for AWS last
year. The issue was tracked in #964596, so I'll merge this bug with
that one...
noah
signature.asc
Description: PGP signature
On Thu, Apr 29, 2021 at 12:31:21PM +0200, Paul Gevers wrote:
> The previous Debian default was to restrict this feature to processes
> running as root, because it exposed more security issues in the
> kernel. However, the security benefits of more widespread sandboxing
> probably now outweigh this
On Tue, Apr 20, 2021 at 08:53:48PM +0200, Ivo De Decker wrote:
> > The debdiff for 3.4.6-1 is at [5]. The debdiff for 3.4.5~pre1-4 is at
> > [6].
>
> I suggest you upload 3.4.5~pre1-4 to unstable and 3.4.6-1 to experimental. I
> haven't looked at 3.4.5~pre1-4 in detail yet, but I suspect it will
On Mon, Apr 19, 2021 at 06:19:35PM +0200, Felix Zielcke wrote:
> > I have upgraded a buster system to bullseye.
> > Even though dovecot starts up fine with the old config, systemd fails
> > to notify that. And kills it again:
> >
> > # systemctl start dovecot
> >
> > Job for dovecot.service faile
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
(I sent a similar message to debian-release recently, but am opening a
bug under the expectation that the post will get lost in the noise.)
There are a few issues in spamassassin that need
On Tue, Apr 13, 2021 at 11:36:11AM +0200, Bastian Blank wrote:
> > > Where was that discussed?
> > It was discussed in
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947759
> > , with responses from both Ben and Noah.
>
> As this is incomplete at best, I intend to revert that change.
>
> O
On Thu, Apr 08, 2021 at 11:01:26PM +0200, Bastian Blank wrote:
> > In order for that to work, though, the
> > key needs to be available in *binary* format. So we still do need gpg
> > to do the conversion.
>
> No, apt does not require a binary key file. Just give
On Thu, Apr 08, 2021 at 04:32:37PM +, Jarosław Wygoda wrote:
>I tried to add complete key on debian 10 and it turns out it requires
>gnupg. Here's a relevant cloud-init config and error.
>apt:
> preserve_sources_list: true
> sources:
> docker.list:
> source
Control: tags -1 - moreinfo
On Sat, Apr 03, 2021 at 08:00:20AM +0200, Paul Gevers wrote:
> > This package contains a snapshot of the code and configuration used by the
> > cloud team to generate the images for azure, aws, and openstack. The cloud
> > team does not build directly from the packages
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package debian-cloud-images
Primarily I'm requesting this because this source package provides the
debian-cloud-images-packages package that is a key package (see
https://bug
On Sun, Mar 28, 2021 at 11:47:34AM +, Laura Smith wrote:
> Running sa-compile (may take a long time)
> chmod: changing permissions of
> '/var/lib/spamassassin/compiled/5.028/3.004002/Mail/SpamAssassin/CompiledRegexps/body_0.pm':
> Operation not permitted
> dpkg: error processing package sa-co
Control: severity -1 important
On Mon, Mar 29, 2021 at 01:44:15AM +0200, Stephan Helma wrote:
> Severity: grave
> Justification: renders package unusable
Downgrading from grave because I've been unable to reproduce it when
testing various upgrade scenarios. I suspect a local issue that's not
ful
Source: spamassassin
Version: 3.4.2-1+deb10u2
Severity: grave
Tags: security patch upstream
Justification: user security hole
X-Debbugs-Cc: Debian Security Team
CVE-2020-1946
Quoting from https://www.openwall.com/lists/oss-security/2021/03/24/3 :
In Apache SpamAssassin before 3.4.5, maliciou
-2021-3429. (Closes: #985540)
+
+ -- Noah Meyerhans Fri, 19 Mar 2021 09:18:59 -0700
+
cloud-init (20.4.1-1) unstable; urgency=medium
* d/watch: switch upstream to github
diff -Nru cloud-init-20.4.1/debian/patches/dont_log_generated_passwords.patch
cloud-init-20.4.1/debian/pa
gelog2021-03-19 09:43:23.0 -0700
@@ -1,3 +1,10 @@
+cloud-init (20.2-2~deb10u2) buster; urgency=high
+
+ * Avoid logging generated passwords to world-readable log files.
+CVE-2021-3429. (Closes: #985540)
+
+ -- Noah Meyerhans Fri, 19 Mar 2021 09:43:23 -0700
+
cloud-init (20.2-2~deb10u
Package: cloud-init
Version: 20.4-1
Severity: grave
Tags: security upstream patch
Justification: user security hole
X-Debbugs-Cc: Debian Security Team
cloud-init has the ability to generate and set a randomized password for
system users. This functionality is enabled at runtime by passing
cloud-
+1,11 @@
+iputils (3:20180629-2+deb10u2) buster; urgency=medium
+
+ * Backport upstream fix for ping rounding errors (Closes: #920434)
+ * Backport upstream fix for tracepath target corruption
+(Closes: #976277)
+
+ -- Noah Meyerhans Mon, 08 Mar 2021 11:46:59 -0800
+
iputils (3:20180629-2+de
On Wed, Mar 10, 2021 at 10:33:18AM +0100, Bernhard Schmidt wrote:
> a colleague reported a bug against SpamAssassin 3.4.2 and later where
> multi-value DNS records are not queried correctly.
>
> Initially the response was that this would not be fixed in 3.4 (4.0 is not
> affected), but the changes
On Mon, Feb 15, 2021 at 09:30:48AM +, Sudip Mukherjee wrote:
> > In a situation where the IMAP server is unreachable for some reason,
> > offlineimap attempts to log a message describing the problem, but instead
> > seems to encounter a coding error in offlineimap itself.
>
> Can you please tr
On Wed, Mar 03, 2021 at 05:35:42PM +0100, Louis Bouchard wrote:
> Thank you for the quick update. I just want to mention that this makes the
> Debian Buster cloud image unusable for any VM with more than 64 cpus.
Is it the number of physical cores that matters, rather than the SMT
threads? Becaus
bullseye was already released as stable, this bug would warrant
a fix in a stable point release. This issue should most definitely be
fixed during the bullseye freeze.
noah
>From 80b2e21783ae8e3348e8952c3055cf2cd3c500ce Mon Sep 17 00:00:00 2001
From: Noah Meyerhans
Date: Thu, 25 Feb 2021 06:
Package: offlineimap3
Version: 0.0~git20210105.00d395b+dfsg-2
Severity: normal
Dear Maintainer,
In a situation where the IMAP server is unreachable for some reason,
offlineimap attempts to log a message describing the problem, but instead
seems to encounter a coding error in offlineimap itself.
Control: forcemerge 970386 -1
On Fri, Feb 05, 2021 at 07:46:39AM +0100, Henrik Stoerner wrote:
> since late january I have seen a couple of crashes of imapd in the logs. The
> error message logged is
>
> Panic: file message-parser.c: line 174 (message_part_finish): assertion
> failed: (ctx->nes
On Wed, Jan 27, 2021 at 12:57:07PM +, Wookey wrote:
> Current arm hardware such as graviton2 (AWS arm64 hardware) has
> 'Coherent Mesh Network' interconnect (between components in a
> soc). It's important that support for this is built in the kernel so
> it can be used.
>
> This requires CONFI
On Thu, Jan 28, 2021 at 08:40:51AM -0500, micah wrote:
> > I've prepared and tested an update and requested SRM approval in
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981239
> >
> > With any luck this makes it into 10.8
>
> Thanks Noah!!
The fix is approved and uploaded, so it should b
I've prepared and tested an update and requested SRM approval in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981239
With any luck this makes it into 10.8
noah
s. (Closes: #970386)
+
+ -- Noah Meyerhans Wed, 27 Jan 2021 16:35:17 -0800
+
dovecot (1:2.3.4.1-5+deb10u5) buster-security; urgency=high
* Import upstream fix for security issues:
diff -Nru dovecot-2.3.4.1/debian/patches/bug970386.patch
dovecot-2.3.4.1/debian/patches/bug970386.patch
-
On Wed, Jan 27, 2021 at 08:38:39AM -0500, micah wrote:
> It looks like you were going to get this fixed in Buster 10.7 release,
> but I didn't see it come through. Did it get refused by the release
> managers, or is there something else holding it up?
I was hoping to also fix
https://bugs.debian.o
For what it's worth, I just checked on NetBSD to see how their ping
behaves, and it also accepts link-local IPv6 addresses without a scope
ID. Similar to iputils, if a scope ID is unspecified, it chooses one
based on the routing configuration.
This doesn't make the behavior "correct", of course,
On Mon, Jan 25, 2021 at 11:51:11AM -0500, Joe Nahmias wrote:
> Just wanted to ask if there's anything I can do to help? I could try
> updating the package to the latest upstream release, which should fix
> those issues, but hesitate to do that without maintainer agreement. Given
> the timing, I'd h
On Mon, Jan 25, 2021 at 01:19:48PM +0100, Marc SCHAEFER wrote:
> > https://github.com/iputils/iputils/pull/100
>
> Interesting. They interpret the fact that link-local works as expected as
> `broken', and fixed it.
>
> > I agree that this is the normal way of fully specifying a link-local
> > add
On Sat, Jan 23, 2021 at 10:27:24AM +0100, Marc SCHAEFER wrote:
>$ ping6 fe80::1
>PING fe80::1(fe80::1) 56 data bytes
>From fe80::9e8e:99ff:fe3c:5523%eth0: icmp_seq=1 Destination unreachable:
> Address unreachable
>
> Link-local addresses are ambiguous: they lack the scope ID, unless y
On Wed, Jan 20, 2021 at 11:39:16PM +0100, Vincent Blut wrote:
> > We could do that. However, in the past (earlier in this bug, even) it's
> > been pointed out that other packages should not be responsible for
> > setting kernel policies, so changes like this should be the
> > responsibility of the
Control: tags -1 + patch
A proposed patch is at
https://salsa.debian.org/kernel-team/linux/-/merge_requests/309
On Wed, Jan 20, 2021 at 10:22:16PM +0100, Vincent Blut wrote:
> My proposal would differ from yours though in that it would not touch the
> kernel
> configuration but would instead consist in patching procps to provide a
> configuration file (let's say default_qdisc.conf) to set the value of the
>
On Sun, Jan 17, 2021 at 10:29:44PM -0300, Ivan Baldo wrote:
> I think we want the mq qdisc to distribute the load between cores, to
> support very high speed network cards or too slow CPUs.
Yep, you're right. Though it's not about CPU cores, but about tx queues
on the NIC hardware.
> Also
On Tue, Jan 19, 2021 at 09:28:58AM +0100, Simon Josefsson wrote:
> Hi. I noticed the following in my log recently. Any ideas?
>
> Jan 6 14:55:54 uggla kernel: [145284.855936] imap[18530]: segfault at 8 ip
> 55c38b20f97c sp 7ffe4b40 error 4 in imap[55c38b1f7000+24000]
> Jan 6 14:55
On Thu, Apr 23, 2020 at 03:34:06PM -0700, Matt Taggart wrote:
> #890343 was originally opened against systemd asking to install the upstream
> systemd sysctl.d/50-default.conf file that sets:
>
> net.core.default_qdisc = fq_codel
>
> As explained in #950701 (and the systemd debian changelog) the
Control: severity -1 wishlist
> We have included spamassassin in a custom installer. During installation
> 'start-stop-daemon' is not available (fake)
> sa-compile relies on start-stop-daemon to be working (sa-compile.postinst
> line 17-19)
> or it wil error trying to 'chmod' a directory which d
> Thanks. Pending currently with the ongoing rebase in the v4.19.y
> series in
> https://salsa.debian.org/kernel-team/linux/-/merge_requests/295 .
>
> Just we need to check if this warrants a regression update issued
> earlier via stable-updates.
If possible, I'd vote for an release via stable-up
101 - 200 of 762 matches
Mail list logo
