Your message dated Sat, 19 Jul 2025 07:24:00 +0000
with message-id <1dce49968aa15f5d2fa090669350f1a97b7509e6.ca...@debian.org>
and subject line Re: snapd: autopkgtest regression: error: nothing matches
provider filter
has caused the Debian Bug report #1108759,
regarding snapd: autopkgtest regression: error: nothing matches provider filter
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1108759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: snapd
Version: 2.68.3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Your package has an autopkgtest, great. However, it fails since May
2025. Can you please investigate the situation and fix it? I copied some
of the output at the bottom of this report.
The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing.
More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
With my Release Team member hat on I allow you to tag this bug as
trixie-ignore if this is nearly completely a test issue as it's so late
in the freeze and it's not worth removing the package from trixie
because of a failing test at this moment unless it exposes a much bigger
issue. Having said that, if this is a test only issue and a fix is
possible without fully removing the autopkgtest and without making the
test superficial, it's still welcome, but it would need to happen soon.
Paul
[1] https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html
https://ci.debian.net/data/autopkgtest/testing/amd64/s/snapd/61893275/log.gz
94s Fetching snap "snapd"
94s 2025/07/03 01:08:09.734964 store_download.go:142: no host system
xdelta3 available to use deltas
96s Fetching assertions for "snapd"
97s Install the snap with:
97s snap ack snapd_24718.assert
97s snap install snapd_24718.snap
97s + mv snapd_24718.snap snapd_1337.foo.snap.keep
97s + . /etc/os-release
97s + PRETTY_NAME=Debian GNU/Linux 13 (trixie)
97s + NAME=Debian GNU/Linux
97s + VERSION_ID=13
97s + VERSION=13 (trixie)
97s + VERSION_CODENAME=trixie
97s + DEBIAN_VERSION_FULL=13.0
97s + ID=debian
97s + HOME_URL=https://www.debian.org/
97s + SUPPORT_URL=https://www.debian.org/support
97s + BUG_REPORT_URL=https://bugs.debian.org/
97s + dpkg --print-architecture
97s + SPREAD_DEBUG_EACH=0 SPREAD_REUSE_SNAPD=1
SPREAD_USE_PREBUILT_SNAPD_SNAP=true /tmp/go/bin/spread -v
autopkgtest:debian-13-amd64:tests/smoke/
97s 2025-07-03 01:08:12 Found
/tmp/autopkgtest.ej1g9E/build.nFc/src/spread.yaml.
108s error: nothing matches provider filter
109s autopkgtest [01:08:25]: test integrationtests: -----------------------]
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: snapd
Source-Version: 2.68.3-3
Done: Zygmunt Bazyli Krynicki <m...@zygoon.pl>
This was fixed with the upload of src:snapd 2.68.3-3, but there wasn't
a Closes stanza in the changelog to automatically close this bug.
https://tracker.debian.org/news/1650947/accepted-snapd-2683-3-source-into-unstable/
signature.asc
Description: This is a digitally signed message part
--- End Message ---
