On Wed, Mar 13, 2024 at 03:57:06PM +0100, Lucas Nussbaum wrote:
> > === FAILURES
> > ===
> > ___ TestUtils.test_init_once_and_debug_mode
> >
> >
> > self = >
dex 9bd33d11..bc3b921c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+cloud-init-22.4.2 (22.4.2-2~bpo11+1) bullseye-security; urgency=medium
+
+ * Rename package to cloud-init-22.4.2 for bullseye-lts
+
+ -- Noah Meyerhans Tue, 30 Apr 2024 13:14:06 -0700
+
cloud-init (22
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: cloud-i...@packages.debian.org, t...@security.debian.org
Control: affects -1 + src:cloud-init
Hi folks. This isn't a straightforward stable proposed-updates
On Thu, Apr 18, 2024 at 10:17:27AM +0200, Arthur LUTZ wrote:
>A small heads up on this issue, we have some minor impacts :
>* sudo commands show a warning
>
> sudo: unable to resolve host example: Name or service not known
Thanks for the report. This is resolved with the 20240429
Source: cloud-init
Version: 21.1.4-1
Severity: serious
Tags: ftbfs upstream
Justification: fails to build from source
Cloud-init's test fails in a non-networked build environment, as visible in
recent buildd logs, e.g.
On Wed, Apr 24, 2024 at 10:02:47AM +0200, Alessandro Vesely wrote:
> > > Stopping S.M.A.R.T. daemon smartd.
> > > Stopping SpamAssassin Mail Filter Daemon spamd.
> > > start-stop-daemon: warning: this system is not able to track process names
> > > longer than 15 characters. please use --exec
On Sun, Apr 14, 2024 at 02:09:05PM +0200, Alessandro Vesely wrote:
> Sorry for the delay. Today a new kernel image was loaded, so I had to
> reboot. I attach a screenshot of the closing session. Near the bottom, it
> says:
>
> Stopping S.M.A.R.T. daemon smartd.
> Stopping SpamAssassin Mail
On Thu, Apr 18, 2024 at 10:17:27AM +0200, Arthur LUTZ wrote:
>Hi,
>A small heads up on this issue, we have some minor impacts :
>* sudo commands show a warning
>
> sudo: unable to resolve host example: Name or service not known
>
>On a more problematic side (but not breaking) we
Control: tags -1 + upstream
On Tue, Apr 16, 2024 at 02:05:17PM -0700, Noah Meyerhans wrote:
> > in light of the recent xz security breach, I'd like to ask if it
> > would be possible to rework systemd readiness notification and socket
> > activation patches to not link against
On Wed, Apr 03, 2024 at 06:26:46PM +0200, Paul Menzel wrote:
> Sorry, I have the feeling we talk past each other. I do not want to create
> an initrd. I want to boot *without* an initrd, and the only missing piece is
> building VIRTIO_BLK into the Linux kernel.
>
> Ubuntu also builds this into
On Thu, Apr 04, 2024 at 08:34:28PM +0200, Jörg-Volker Peetz wrote:
> in light of the recent xz security breach, I'd like to ask if it
> would be possible to rework systemd readiness notification and socket
> activation patches to not link against libsystemd as just achieved for
> the
Control: tags -1 + confirmed upstream
Control: severity -1 minor
On Fri, Apr 05, 2024 at 10:04:29PM +, Einhard Leichtfuß wrote:
> when the Dovecot configuration contains an `!include` statement with a
> wildcard that does not match anything, dovecot prints an error and
> terminates.
>
>
On Wed, Apr 03, 2024 at 09:39:40PM -0700, Flavio Veloso Soares wrote:
> Hi Noah - I guess I'll be doing bullseye->bookworm installs in the meantime,
> until 12.6 so I can fill bug reports (if any).
It should be plenty to start with the bookworm images and simply remove
the libnss-resolve package.
Control: tags -1 + pending
On Wed, Apr 03, 2024 at 06:48:56PM -0700, Flavio Veloso Soares wrote:
> Is this the correct forum to report issues/ask question about the official
> Debian images on AWS?
The BTS isn't really the correct forum to ask questions about any Debian
topics, but it is the
Control: tags -1 + moreinfo
On Mon, Feb 12, 2024 at 10:42:31AM +0100, Alessandro Vesely wrote:
> /etc/init.d/spamd still uses --name instead of --exec.
> This is noticeable on shutdown, what the system waits
> for some time trying to kill spamd, and then complains
> something about its
On Sun, Feb 04, 2024 at 09:24:30AM +0200, Graham Inggs wrote:
> debian-cloud-images 0.0.7 introduced a dependency on systemd-timesyncd
> (not mentioned in the changelog), which makes the dependencies of
> debian-cloud-images-packages unsatisfiable [1] due to a conflict with
> chrony.
>
> The
On Fri, Jan 12, 2024 at 08:00:48AM +0100, Alexandre Detiste wrote:
> >> Or should the Debian package depend on python3-six?
> >
> > That s the fast solution
>
> Yes please do that, I've checked awscli upstream and it's a bit of a mess
> with so many pull request; I'll check again later.
Here's
Source: python-s3transfer
Severity: wishlist
Newer versions of python-boto3 will require python-s3transfer >= 0.10.0, so in
order to unblock those I'd like to request that python-s3transfer be updated
soon.
I'm happy to perform the upload myself with the maintainer's acknowledgement.
Thank you!
On Thu, Jan 11, 2024 at 02:27:23PM -0500, Jeremy Bícha wrote:
> There is a diff at
> https://launchpad.net/ubuntu/+source/awscli/2.14.6-1ubuntu1 for this
> issue. You can ignore the build failure since that doesn't seem to
> currently affect Debian Unstable.
Thanks, I've applied that patch and
On Sun, Dec 31, 2023 at 11:39:42AM +0100, Damian wrote:
> The fix for #1028030 introduced a regression for amavisd-new. Its hook [1] is
> never run as long as spamd is not installed.
Right, it seems like this:
if [ -d /etc/spamassassin/sa-update-hooks.d ]; then
run-parts
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: python-b...@packages.debian.org
Control: affects -1 + src:python-boto
Python-boto has long ago been superseded upstream by python-boto3, which has
been in Debian for several releases.
On Tue, Dec 12, 2023 at 08:14:41PM +0100, Andreas Tille wrote:
> maybe we need to remove python-boto and fix all its rdepends.
>
> According to upstream[1]:
>
> This repo, boto was deprecated in 2020 and the last supported Python 3
> version was 3.4. It's unlikely this package will ever work
On 11/6/2023 2:53 PM, Patrik Schindler wrote:
The removal of the sysvinit script was intentional. Per Debian policy
section 9.3.1, "Packages including a service unit may optionally
include an init script to support other init systems". Spamd provides
a service unit. There is no requirement
Control: tags -1 + pending
On 11/15/2023 2:31 PM, Martin Schwenke wrote:
This was reported upstream via:
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8130
and fixed in the trunk via commit:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: dovecot-antis...@packages.debian.org
Control: affects -1 + src:dovecot-antispam
nmu dovecot-antispam_2.0+20171229-1+b12 . ANY . unstable . -m "Rebuild for
dovecot 2.3.21"
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: dovecot-fts-xap...@packages.debian.org
Control: affects -1 + src:dovecot-fts-xapian
nmu dovecot-fts-xapian_1.5.5-1+b3 . ANY . unstable . -m "Rebuild for dovecot
2.3.21"
Control: tags -1 + wontfix
Control: severity -1 wishlist
On 11/6/2023 8:41 AM, Patrik Schindler wrote:
Surprisingly, after upgrading to Bookworm, the SysVinit script to start
spamassassin is no longer there. This renders spamassassin unusable for
SysVinit users without manual intervention.
On Sun, Sep 24, 2023 at 04:09:31PM -0700, Noah Meyerhans wrote:
> > > Could we use the Debian AWS account to host that service?
> >
> > I would assume that a service like snapshot would be within the scope
> > for our AWS usage. Noah?
>
> It makes sense and I wi
On Fri, Sep 22, 2023 at 05:12:21PM +0200, Bastian Blank wrote:
> > Could we use the Debian AWS account to host that service?
>
> I would assume that a service like snapshot would be within the scope
> for our AWS usage. Noah?
It makes sense and I will look into it. Let's not start anything
This is done with https://salsa.debian.org/debian/dovecot/-/merge_requests/33
Also, I'm curious to see what happens if you invoke the
write_files_deferred module by hand with a command like
$ sudo cloud-init single --name cc_write_files_deferred \
--frequency always --report
It should generate messages in /var/log/cloud-init.log.
On 7/14/23 06:49, Sven Strickroth wrote:
I'm not able to reproduce the behavior you describe. defer seems to
work as expected. For example:
admin@ip-10-0-0-87:~$ ec2-metadata --ami-id
ami-id: ami-0544719b13af6edc3
admin@ip-10-0-0-87:~$ sudo cat /var/lib/cloud/instance/user-data.txt
Control: tags -1 + moreinfo
On Thu, Jul 13, 2023 at 05:30:52PM +0200, Sven Strickroth wrote:
> starting with the shipped version in Debian 12 the write_files feature with
> defer option does not work any more.
I'm not able to reproduce the behavior you describe. defer seems to
work as
Source: dovecot
Version: 1:2.3.19.1+dfsg1-2.1
Severity: normal
The Dovecot Lucene FTS backend is not supported and should not be built or
shipped by Debian. Supported alternatives (dovecot-solr and
dovecot-fts-xapian) are available in Debian and users should migrate to those
instead.
-- System
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: dovecot-antis...@packages.debian.org
Control: affects -1 + src:dovecot-antispam
nmu dovecot-antispam_2.0+20171229-1+b11 . ANY . unstable . -m "Rebuild for
dovecot
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: dovecot-fts-xap...@packages.debian.org
Control: affects -1 + src:dovecot-fts-xapian
nmu dovecot-fts-xapian_1.5.5-1+b2 . ANY . unstable . -m "Rebuild for dovecot
Control: tags -1 + patch
Proposed fix is at
https://salsa.debian.org/cloud-team/cloud-init/-/merge_requests/9
On Sat, Apr 04, 2020 at 11:49:42AM +0100, Nick Holloway wrote:
> Package: cloud-init
> Version: 18.3-6
Confirmed that the behavior as described is still an issue in cloud-init
22.4.2-1 in bookworm.
> The command "locale-gen" does not accept a locale as an argument, but
> only generates the
Control: tags -1 + pending
On 6/12/2023 8:58 PM, Steve Langasek wrote:
I've applied the attached (very dirty) patch to libmail-dmarc-perl in
Ubuntu, which is sufficient to let the package build in Launchpad. Having
looked at some of the surrounding tests, I'm not sure this would let the
Control: tags -1 - moreinfo
On Sun, Apr 30, 2023 at 08:08:55AM +0200, Paul Gevers wrote:
> > Please go ahead and remove the moreinfo tag once the upload happened.
>
> Already several years we don't accept uploader built binaries in testing.
> Unfortunately, we can't binNMU arch:all binaries, so
On Wed, Apr 19, 2023 at 07:50:32AM +0800, Martin Michlmayr wrote:
> * Martin Michlmayr [2023-04-13 18:23]:
> > A Google search has led to:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1985587
> > The proposed patch seems relevant to Debian's spamd service file too:
> >
@@ -1,3 +1,9 @@
+spamassassin (4.0.0-5) unstable; urgency=medium
+
+ * Update spamd.service to order after network-online.target (Closes:
#1034347)
+
+ -- Noah Meyerhans Sun, 16 Apr 2023 13:28:05 -0700
+
spamassassin (4.0.0-4) unstable; urgency=medium
* Revert "drop unused params
On Sat, Apr 15, 2023 at 03:56:02AM -0400, Ed Lawson wrote:
> 23-04-13T16:2056:26.075987-04:00 800-mini-1 spamd[938]: spamd: connection
> from localhost [::1]:44842 to port 783, fd 5
> 2023-04-13T16:56:26.077471-04:00 800-mini-1 spamd[938]: spamd: setuid to
> elawson succeeded
>
+
+ * Install systemd services to /lib/systemd/system. (Closes: 1034212)
+
+ -- Noah Meyerhans Thu, 13 Apr 2023 10:22:32 -0700
+
amazon-ec2-net-utils (2.3.0-2) unstable; urgency=medium
* Set Maintainer to the cloud team and add myself to Uploaders
diff -Nru amazon-ec2-net-utils-2.3.0/debian
On 4/4/2023 9:26 AM, Noah Meyerhans wrote:
Hi Dirk. Since we don't have this in the archive yet, I've refiled this
as an RFP. Once it's packaged, we can add it to the AMIs.
Well, *now* I've refiled it as an RFP, now that I can correctly spell
"wnpp" :)
noah
Control: reassign -1 wnpp.debian.org
Control: retitle -1 RFP: amazon-ec2-hibinit-agent -- Amazon EC2 instance
hibernation support
> So the request is to also ship the agent preinstalled in the Debian AMIs. See
> https://packages.ubuntu.com/search?keywords=ec2-hibinit-agent=names
> for Ubuntu
On Sat, Apr 01, 2023 at 09:53:06AM -0400, Ed Lawson wrote:
> Spamassassin does not start and is not functional. I have two computers
> running Debian Sid and spamassissin is not working on either. When I
> run systemctl status spamassassin it reports "Units spamassassin.service
> could not be
Package: offlineimap3
Version: 0.0~git20211018.e64c254+dfsg-2
Severity: important
I have an offlineimap configuration that retrieves authentication material
from .netrc. This configuration stopped working with the most recent update
in testing. See below for the offlineimap command output.
On 1/5/2023 7:11 PM, Matt Corallo wrote:
Ah, sorry for the noise, the package was split. Seems funny to do in a
backport.
backports pull changes from what's in bookworm (testing). Nothing was
"done" in the backport, it was a straight pull. Preserving bullseye's
package structure would have
On Wed, Jan 04, 2023 at 06:58:30PM +0200, Adrian Bunk wrote:
> https://buildd.debian.org/status/logs.php?pkg=spamassassin=amd64
>
> ...
> Jan 4 03:57:23.254 [3488924] dbg: logger: adding facilities: all
> Jan 4 03:57:23.255 [3488924] dbg: logger: logging level is DBG
> Jan 4 03:57:23.257
On Wed, Nov 02, 2022 at 05:31:33PM +0100, Francesco Potortì wrote:
> Starting few days ago, I get many of these in syslog:
>
> plugin: eval failed: Unknown encoding 'MIME-Header' at
> /usr/share/perl5/Mail/SpamAssassin/Message.pm line 1090, line 8342.
> plugin: eval failed: Unknown encoding
On Tue, Jan 03, 2023 at 03:26:37AM +0100, Marco d'Itri wrote:
> > Debian's default sysctl settings should reside in procps (as it owns
> > /sbin/sysctl and /etc/sysctl* settings) rather than some unrelated
> > package.
> Nowadays systemd is a source of common sysctl settings among different
>
On Tue, Jan 03, 2023 at 01:48:29AM +0100, Adam Borowski wrote:
> Most settings are in /etc/sysctl.conf, especially network related ones.
>
> That /usr/lib/sysctl.d/ path doesn't have its settings applied normally.
systemd-sysctl is run by default and processes /usr/lib/sysctl.d/. This
is the
On Tue, Jan 03, 2023 at 01:36:30AM +0100, Adam Borowski wrote:
> > > I'm entirely happy to reassign this request to systemd and have the
> > > setting applied more broadly.
> > Some options:
> > - conflict with systemd < version_with_the_new_default
> > - wait for a full release and then just drop
On Mon, Jan 02, 2023 at 10:09:44PM +0100, Marco d'Itri wrote:
> > With that in place, unprivileged users are able to excute ping for both
> > IPv4 and IPv6 targets without cap_net_raw (currently set as either a
> > file-based attribute on the ping binary or acquired via setuid). But
> > since
tags -1 + pending
> This package ships /usr/share/zsh/vendor-completions/_awscli which I
> expect it to work like other files in zsh/vendor-completions.
>
> For example, I should have `aws` completion if I just called `compinit`
> in my zshrc.
>
> But I still need to `source
Package: wnpp
Severity: wishlist
Owner: Noah Meyerhans
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: amazon-ec2-net-utils
Version : 2.3.0
Upstream Contact: Noah Meyerhans
* URL : https://github.com/amazonlinux/amazon-ec2-net-utils
* License
Also it seems that generating this file triggers an OOM condition on
salsa. https://salsa.debian.org/noahm/awscli/-/jobs/3693800
Package: awscli
Version: 2.9.9-1
Severity: normal
Just making sure this is recorded:
The aws(1) man page installed by awscli 2.9.9-1 is not useful. Ideally it
should be split up in to per service pages, e.g. aws-vpc(1), aws-ec2(2), etc.
for all services (some services already have their own
On 12/12/2022 6:44 AM, Sam Hartman wrote:
>> From my quick read: Michael Biebl proposes dropping
>> network-pre.target
Ross> from cloud-init's After=, and replacing it with each of the
Ross> config backends that cloud-init supports. This sounds pretty
Ross> reasonable,
Package: cloud.debian.org
Severity: normal
Certain functionality built in to cloud-init depends on a reasonably
accurate clock, such as apt repo metadata signature verification. In the
case where a system's hardware clock is far out of sync, chrony may not have
completed synchronization before
Package: wnpp
Severity: wishlist
Owner: Noah Meyerhans
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-cl...@lists.debian.org
* Package name: aws-crt-python
Version : 0.15.3
Upstream Author : Amazon Web Services
* URL : https://github.com/awslabs/aws-crt-python
Control: tags -1 + moreinfo
On Sat, Nov 19, 2022 at 10:23:12AM -0500, Michael Welsh Duggan wrote:
> The addition of the
>
> ProtectSystem=full
>
> clause to the spamd service module prevents spamd from writing to user
> bayes files. Here is a log from spamd:
Hi Michael. Per the systemd
On Fri, Nov 04, 2022 at 05:37:21PM +0100, Bastian Blank wrote:
> > > Are you sure this library can have a 1 as ABI? Can you please reproduce
> > > the ABI stability promisses?
> > Allegedly upstream has recently committed to proper SONAME and ABI
> > management in support of efforts to get these
On Fri, Nov 04, 2022 at 08:32:25AM +0100, Bastian Blank wrote:
> > My first pass only produces -dev packages with headers and static libraries.
> > To test them out, build the debian/sid branch from these repos, in this
> > order:
> > - https://salsa.debian.org/rvandegrift/aws-c-common
>
> Are
On Thu, Nov 03, 2022 at 09:35:14PM -0700, Ross Vandegrift wrote:
> > Honestly, filing some of the ITPs would be quite helpful at this point.
> > We'll need to get the following projects packaged:
> >
> > aws-c-auth
> > aws-c-cal
> > aws-c-compression
> > aws-c-event-stream
> > aws-c-http
>
> I
Package: wnpp
Severity: wishlist
Owner: Noah Meyerhans
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: aws-checksums
Version : 0.1.13
Upstream Author : Amazon Web Services
* URL : https://github.com/awslabs/aws-checksums
* License : Apache 2.0
Package: wnpp
Severity: wishlist
Owner: Noah Meyerhans
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: aws-c-common
Version : 0.8.4
Upstream Author : Amazon Web Services
* URL : https://github.com/awslabs/aws-c-common
* License : Apache 2.0
On Wed, Nov 02, 2022 at 07:55:51PM -0700, Ross Vandegrift wrote:
> > > - the aws-cli2-temp repo is based on upstream, not our awscli repo. I was
> > > intentionally being sloppy to quickly get through a test.
> >
> > Same. I essentially Debianized the upstream v2 repo from scratch,
> >
Package: wnpp
Severity: wishlist
Owner: Noah Meyerhans
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: s2n-tls
Version : 1.3.26
Upstream Author : Amazon Web Services
* URL : https://github.com/aws/s2n-tls
* License : Apache 2.0
Programming Lang
On Mon, Oct 31, 2022 at 10:50:19PM -0700, Noah Meyerhans wrote:
> > aws-crt-python is the hard part. It depends on a bunch of C libraries which
> > follow a more modern development style. They:
> > - provide no abi/api stability guarantees.
> > - have versioned releases
Hi Ross,
On Tue, Oct 05, 2021 at 11:10:43PM -0600, Ross Vandegrift wrote:
> > 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.
>
> Using the source dist poc from
Package: wnpp
Severity: wishlist
* Package name: aws-sdk-go-v2
Version : 2022-10-27
Upstream Author : Amazon Web Services (https://aws.amazon.com/)
* URL : https://github.com/aws/aws-sdk-go-v2
* License : Apache 2.0
Programming Lang: Go
Description :
Control: reassign -1 aide
Control: retitle -1 aide's spamassassin script does not correctly handle
spamassassin prerelease version strings
On Fri, Oct 21, 2022 at 01:05:21PM +0200, Thomas Dorner wrote:
> > > The problem is that the current version number 4.0.0~rc3-3.1 does
> > > not match the
On Tue, Oct 18, 2022 at 10:08:32AM +0200, Thomas Dorner wrote:
> The problem is that the current version number 4.0.0~rc3-3.1 does not
> match the expected schema of N.N.N-N. As only the first 3 numbers are
> used anyway, I've created a patch (attached) making the regular
> expression less rigid
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
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
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
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
-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
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 <
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
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
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
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
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
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
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 even
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
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
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
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
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
1 - 100 of 736 matches
Mail list logo
