On Tue, 05 Aug 2025 at 20:25:29 -0400, M. Zhou wrote:
Package: libatlas3-base
...
+Depends: libblas3 (= ${binary:Version}), ${misc:Depends}
...
Description: transitional package
Should this be (>= ${binary:Version}) instead of (=)?
In other packages that migrated to another name via a tran
for following through with a bug report. I'll see
if I'm able to set it up and use it once this has been confirmed fixed.
/Simon
signature.asc
Description: PGP signature
Chris Hofstaedtler writes:
> * Simon Josefsson [250723 12:11]:
>>Ah, right, although this bug would not necessarily have any activity
>>since the real issue was golang-github-containers-ocicrypt but that is
>>now fixed in testing. And the autoremoval was for 2025-08-22, n
il will bump it further if your theory is correct...
/Simon
Ondřej Surý writes:
> I believe the auto removal counter resets when there’s an activity on
> the bug. Or at least it was the case in the past (or my memory is
> failing me).
>
> Ondrej
> --
> Ondřej Surý (He/Him)
here...
/Simon
Simon Josefsson writes:
> severity 1108992 normal
> thanks
>
> Bastian Germann writes:
>
>> I have already filed bug#1109540 (unblock:
>> golang-github-containers-ocicrypt/1.1.10-3)
>
> It seems the autoremoval is more aggresive than the overri
upload, please don't wait for me.
/Simon
From f54c8aee95597558491fbbbff6fe87d406ff9722 Mon Sep 17 00:00:00 2001
From: Simon Josefsson
Date: Mon, 21 Jul 2025 10:33:31 +0200
Subject: [PATCH] Use Breaks: instead of Conflicts:.
---
debian/control | 8
1 file changed, 4 insertions(
not use the autoremoval mechanism to
achieve this. Then the release team can wait for
golang-github-containers-ocicrypt to enter testing, and then remove
opendnssec from testing.
/Simon
signature.asc
Description: PGP signature
Oh thank you!
/Simon
> 19 juli 2025 kl. 22:05 skrev Bastian Germann :
>
>
> I have already filed bug#1109540 (unblock:
> golang-github-containers-ocicrypt/1.1.10-3)
where we should ask the
release team (?) to migrate that package to testing earlier? Or should
the RC severity of 1108992 be lowered? Or something else?
/Simon
signature.asc
Description: PGP signature
Control: tag -1 pending
Hello,
Bug #1051785 in gdm3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/gnome-team/gdm/-/commit/a282369756946506a53b1ec55f8a2009af7c
Control: tag -1 pending
Hello,
Bug #1051785 in gdm3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/gnome-team/gdm/-/commit/dc6ab49be2bfdd730a8a7176020217cafc1d
Control: unblock 1035983 by 1109107 1109108
Control: block -2 by 1035983
On Mon, 19 May 2025 at 17:57:50 +0200, Santiago Vila wrote:
El 19/5/25 a las 16:43, Simon McVittie escribió:
Is this still the same failure mode described in the bug title, with "Address already in
use" and "co
On Thu, 10 Jul 2025 at 14:12:20 +0100, Simon McVittie wrote:
Workarounds and possible solutions
==
enable-smartcard-authentication=false
...
This is the brute-force approach that makes sure password
authentication definitely always works as expected, at the
Control: tags -1 + moreinfo
On Thu, 12 Jun 2025 at 15:40:04 +0100, Simon McVittie wrote:
the default configuration of gdm is such
that, if a user has a smart card (e.g. Yubikey) plugged in, but *has
not* enrolled it for smartcard authentication, then gdm doesn't work
as intended for ord
aybe having a list of
known URLs and have the client try all of them would be more reliable.
It may become a cat and mouse chase.
/Simon
signature.asc
Description: PGP signature
Source: mozjs140
Version: 140.0-2
Severity: serious
Justification: rc_policy.txt §6a
User: debian...@lists.debian.org
Usertags: fails-always
The new mozjs140 source package builds successfully (on release
architectures other than armel), but is failing its superficial
autopkgtest, which links a
On Sat, 28 Jun 2025 at 18:31:49 +0200, Ben Hutchings wrote:
On this desktop system /home is mounted from an NFS server. This was
usable in bookworm. After upgrading to trixie, the shell doesn't
appear for several minutes, and then takes over a minute to respond to
some buttons.
I'm not at all
On Fri, 27 Jun 2025 at 04:19:40 +0200, Santiago Vila wrote:
I'm Cc:ing Simon McVittie who fixed a similar bug not a long time ago,
maybe he can explain better than me.
Are you referring to #1102099 in game-data-packager?
That was a rather different situation, where running Inkscape wi
On Fri, 27 Jun 2025 at 17:30:05 -0400, Jeremy Bícha wrote:
libgstreamer1.0-dev has set Multi-Arch: same, but beginning with
gstreamer 1.26, Gst-1.0.gir varies across architectures. See
https://launchpad.net/bugs/2115325 where this issue was originally
reported for more details.
As I noted in the
On Fri, 27 Jun 2025 at 04:19:40 +0200, Santiago Vila wrote:
On Fri, Jun 27, 2025 at 10:49:10AM +0900, Osamu Aoki wrote:
I understand disabling dbus-run-session solves build issue.
In an earlier message where I was not cc'd, Santiago wrote:
There was a package which failed in a similar way, an
On Tue, 24 Jun 2025 at 08:16:42 +, Graham Inggs wrote:
rdflib's autopkgtest is currently regressed in testing on all
architectures [1]. I've copied what I hope is the relevant part of
the log below.
A more relevant part seems to be:
87s # A url that returns content-type text/html
On Wed, 18 Jun 2025 at 20:54:55 +0200, Salvatore Bonaccorso wrote:
The following vulnerability was published for gdk-pixbuf.
(Choosing RC level, since jmm is planning a DSA, so we should have
that fixed as well in trixie)
Fix uploaded to trixie and unblock requested. The same patch is likely
t
Control: tag -1 pending
Hello,
Bug #1107994 in gdk-pixbuf reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/gnome-team/gdk-pixbuf/-/commit/ca851768ace1210cc2c4a56
On Thu, 12 Jun 2025 at 16:12:15 +0200, Marco Trevisan wrote:
On giu 12 2025, at 3:18 pm, Simon McVittie wrote:
In debian we actually have the `gdm-auth-config` that should allow to
manage this without having to handle this, it also allows to use distro
scripts (I did put one in our gdm's d
On Thu, 12 Jun 2025 at 14:24:36 +0200, Raphael Hertzog wrote:
On Sat, 27 Jul 2024, Luca Boccassi wrote:
I can confirm this works (I too have a yubikey with a cert for
unrelated purposes).
So we should deploy this by default IMO. I have setup a new computer
today and I have again been bitten by
On Sun, 02 Feb 2025 at 20:05:41 +0100, Ole Streicher wrote:
the build of the "giza" package currently fails in some environments
due to an issue with xvfb-run [1], which is used from debian/rules.
The problem is that the xvfb-run script only checks that Xvfb is
running (by signalling with sign
e too fast.
/Simon
Santiago Vila writes:
> tags 1106316 patch
> thanks
>
> Hello.
>
> There was already a patch called
>
> 0001-Don-t-hard-fail-on-slow-systems.-624.patch
>
> to fix a similar problem in another test. If you were to do the same
> with "TestSign
Control: tag -1 pending
Hello,
Bug #1102610 in sonata reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/mpd-team/sonata/-/commit/8eb11678b63cd78f3b3af97dbd2ae9641
Package: xdg-desktop-portal
Version: 1.20.1+ds-2
Severity: serious
Justification: maintainer says so
Tags: upstream
The version of x-d-p in unstable crashes when contacted by a Flatpak app
${APP_ID} which does not export a .desktop file named
files/share/applications/${APP_ID}.desktop.
org.gnom
On Fri, 16 May 2025 at 12:45:43 +0200, Santiago Vila wrote:
Regarding the flakiness itself, I get a failure rate around 20%
on machines with 1 CPU and 30% on machines with 2 CPUs. This is
greater than the reference thresholds given by Paul in one
of the gcr bugs.
I'd like to propose a patch, but
Control: retitle -1 epiphany-browser: FTBFS w/test failure in bookworm:
webkit_settings_set_enable_dns_prefetching is deprecated and does nothing
On Mon, 19 May 2025 at 09:50:34 +, Santiago Vila wrote:
FTBFS: 4/13 Embed shell test FAIL - 13/13 Web view test FAIL
This looks like the same r
Control: tags -1 + pending
On Wed, 16 Apr 2025 at 19:50:46 +0100, Simon McVittie wrote:
https://github.com/doitsujin/dxvk/pull/4853 is an untested implementation
of the "generic CPU" code path that I suggested in the bug report.
This was applied in the packaging git repo as part of
Paul Gevers writes:
> Hi Noah,
>
> On Thu, 08 May 2025 10:10:06 +0200 Simon Josefsson
> wrote:
>> The testing migration seems a bit unclear to me, can you take a look if
>> this will actually migrate? It is scheduled for autoremoval right now.
>> https://tracker
you need a dependence on 'dovecot (>= 2.4~)' in
gsasl/libgssglue, and a 'Breaks: gsasl (<< 2.2.2-1.1~), libgsasl (<<
0.9-1.1~)' in dovecot.
Feel free to merge your merge requests and push release tags into the
git repository, I gave them thumbs up:
https://s
Control: found -1 1:18.1.8-17
On Sat, 26 Apr 2025 at 15:34:17 +0200, Helmut Grohne wrote:
libc++-18-dev explicitly declares the ability to coinstall via
Multi-Arch: same. Attempting to do this practically fails though.
$ mmdebstrap --variant=essential --verbose unstable /dev/null
--architectur
shortcuts in
this area, and channel bindings have bad interop history. I am traveling so no
laptop but feel free to nmu as you prefer.
/Simon
> 1 maj 2025 kl. 22:50 skrev Noah Meyerhans :
>
> Control: tags -1 + patch
>
>> On Thu, May 01, 2025 at 03:56:11PM -0400, Noah Meyerhan
/permissions problem or
additional GSSAPI flag check that dovecot didn’t do before.
Alas I am traveling without laptop for the next few days so will have no
ability to debug anything.
/Simon
> 29 apr. 2025 kl. 22:33 skrev Noah Meyerhans :
>
> On Tue, Apr 29, 2025 at 10:22:21PM +02
.0.1.1, session=
/Simon
> 29 apr. 2025 kl. 21:21 skrev Noah Meyerhans :
>
> Source: gsasl
> Version: 2.2.0-1
> Severity: serious
> Justification: autopkgtest regression
>
> Dovecot 2.4 is currently in unstable and trying to migrate to testing. It's
> currently
On Tue, 29 Apr 2025 at 10:30:56 +0100, Simon McVittie wrote:
On Fri, 21 Mar 2025 at 13:31:14 +0100, Helmut Grohne wrote:
Please either move those libraries to a multiarch location or remove
"Multi-Arch: same" from the libmlir-19 binary package. Given the freeze
timing I recommend
expected.
On Fri, Apr 25, 2025, at 11:56 AM, Simon McVittie wrote:
Will llvm-toolchain-20 prereleases (in experimental) also need an
upload? The llvm-toolchain-20 package doesn't seem to have a bug open
yet - should we clone this one?
if they still use the lowered/old baseline, yes.
The 20
Control: tags -1 + patch
On Mon, 07 Apr 2025 at 09:44:53 +0200, Helmut Grohne wrote:
[Various -dev packages] fail to coinstall despite explicitly declaring that
capability via Multi-Arch: same. Most of them install
architecture-dependent files to architecture-independent filenames below
/usr/lib
Control: tags -1 + patch
On Fri, 21 Mar 2025 at 13:31:14 +0100, Helmut Grohne wrote:
libmlir-19 fails to coinstall despite it explicitly stating that
capability.
mmdebstrap --variant=apt --verbose '' /dev/null 'deb
http://deb.debian.org/debian unstable main' --architectures=amd64,i386
--inclu
Control: tags -1 + pending
On Fri, 21 Mar 2025 at 13:31:14 +0100, Helmut Grohne wrote:
Please either move those libraries to a multiarch location or remove
"Multi-Arch: same" from the libmlir-19 binary package. Given the freeze
timing I recommend doing the latter.
This appears to have been fix
Control: clone -1 -2
Control: retitle -2 libmlir-18 is Multi-Arch: same but fails to coinstall
Control: reassign -2 libmlir-18 1:18.1.8-17
Control: found -2 libmlir-18 1:18.1.8-18
On Fri, 21 Mar 2025 at 13:31:14 +0100, Helmut Grohne wrote:
libmlir-19 fails to coinstall despite it explicitly stat
On Wed, 23 Apr 2025 at 10:26:03 +0100, Simon McVittie wrote:
While checking why the fix for #1057621 wasn't migrating to testing, I
noticed that the updated valgrind has failed to build on [32-bit]
...
I see that valgrind's configure check for mpi-c is failing:
checking for mpicc..
Control: tags 1100481 + pending
On Mon, 21 Apr 2025 at 15:18:49 +0200, Chris Hofstaedtler wrote:
On Fri, Mar 14, 2025 at 12:53:26PM +0200, Adrian Bunk wrote:
On Sat, Dec 31, 2022 at 07:24:51PM +0100, Jakub Wilk wrote:
> This package has "libunwind-dev" in Provides, but it's not fully compatible
t.cgi?bug=1095863#70:
On 13-02-2025 17:32, Simon McVittie wrote:
- Officially keep current baseline, intentionally violate the baseline in
rustc (and maybe LLVM?) so that rustc produces working code, and
have the release team announce that the resulting baseline violations
are not to
Control: tags -1 + patch
On Wed, 23 Apr 2025 at 15:59:00 +0100, Simon McVittie wrote:
I think the "option 2" that I proposed is entirely feasible for trixie,
actually. I'm testing an implementation now.
https://salsa.debian.org/xorg-team/lib/mesa/-/merge_requests/55 works
suc
wrote:
On 23/04/2025 10:47, Simon McVittie wrote:
Fixing the C regression by reinstating the first --slave line
seems considerably simpler, and might be enough to fix valgrind on
32-bit. Should we clone this bug into a C part which can certainly be
fixed, and a Fortran part which might need
On Tue, 15 Apr 2025 at 16:52:56 +0200, Helmut Grohne wrote:
On Tue, Apr 15, 2025 at 01:47:54PM +0100, Simon McVittie wrote:
I think a regression for amd64/i386 co-installation would have a
considerably larger practical negative impact on Debian users
This reasoning convinces me. As it stands
On Wed, 19 Mar 2025 at 18:10:34 -0100, Graham Inggs wrote:
It seems the BTS considers that 4.3.0-2 will re-introduce this bug to
testing because the changelog entry for 4.2.1-4 above was dropped from
debian/changelog.
As far as I can see, the BTS is correct: there are changes from 4.2.1-4
and 4
On Sun, 13 Apr 2025 at 13:14:49 +0300, Adrian Bunk wrote:
214s autopkgtest [01:51:54]: test mpi-compile-run-cc-pkgconf-mpi-c:
[---
214s Package mpi-c was not found in the pkg-config search path.
...
This is related to two lines disappearing from the
libmpich-dev postinst:
Source: valgrind
Version: 1:3.24.0-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-...@lists.debian.org, debian-powe...@lists.debian.org,
mp...@packages.debian.org
User: debian-...@lists.debian.org
Usertags: armhf
Control: forwarded -1 https://github.com/doitsujin/dxvk/pull/4853
On Wed, 16 Apr 2025 at 17:45:32 +0100, Simon McVittie wrote:
> There seem to be two places in the dxvk codebase that #error out if the
> CPU architecture is not recognised.
>
> 1. src/util/util_bit.h
> 2
Source: dxvk
Version: 2.6.1-1
Severity: serious
Tags: upstream ftbfs experimental
Justification: built successfully in the past on armhf
dxvk 2.6.1 with DXVK Native enabled doesn't build successfully on armhf:
> c++ -Isrc/wsi/libwsi.a.p -Isrc/wsi -I../src/wsi -Iinclude -I../include
> -I../includ
ith GPLv2 and that all code
that link to OpenSSL has to have a GPL+OpenSSL exception. Does anyone
recall how and when this decision was made?
Licensing wrt to libcurl and OpenSSL has been discussed before:
https://lists.debian.org/debian-legal/2004/08/msg00221.html
/Simon
signature.asc
Descrip
chitectures that are not yet in Debian at
all (amd64/musl-linux-amd64).
> On Mon, Apr 14, 2025 at 05:23:01PM +0100, Simon McVittie wrote:
> > Loaders are expected to be able to recognise that a particular driver is not
> > for them, and gracefully not load it. In practice this works fi
. I believe it would be
better to work with rights holders to work out problems rather than to
ignore requests and throw legal arguments at them.
/Simon
signature.asc
Description: PGP signature
On Mon, 14 Apr 2025 at 18:48:02 +0200, Michel Dänzer wrote:
> On 2025-04-14 18:23, Simon McVittie wrote:
> >
> > I can see two ways to resolve #980148 without needing to change the
> > search path for Vulkan drivers:
> >
> > 1. [rename the files to have a
On Fri, 04 Apr 2025 at 20:42:48 +0200, Helmut Grohne wrote:
> On Fri, Jan 15, 2021 at 12:06:14PM +0100, Michel Dänzer wrote:
> > On 2021-01-15 12:02 p.m., Thorsten Glaser wrote:
> > > Package: mesa-vulkan-drivers
> > > […]
> > > Multi-Arch: same
> > >
> > > The file /usr/share/vulkan/icd.d/intel_i
On Sun, 13 Apr 2025 at 11:58:57 +0100, Samuel Henrique wrote:
Based on the replies to https://mastodon.social/@bagder/114329630276196304,
where there was some uncertainty around where the issue comes from, I figured I
should clarify it here:
git on Debian ends up indirectly linked to OpenSSL thr
23/01/2025 15:32, Simon McVittie wrote:
> The current version of librsvg is not migrating to testing because it
> FTBFS on mips64el. This appears to be caused by a kernel or hardware
> issue where otherwise-working code fails with EFAULT in a read() call
> on bookworm kernels (see #10932
who isn't all that
familiar with Go and Go library namespaces, the policy could also
clarify exactly what the "import name" refers to. For me it is
ambiguous (I "import" the package from github.com/smallstep/crypto/...).
/Simon
signature.asc
Description: PGP signature
Control: tag -1 pending
Hello,
Bug #1102402 in golang-github-smallstep-scep reported by you has been fixed in
the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/go-team/packages/golang-github-smal
Jérémy Lal writes:
> To avoid the odd-ness of assigning a RC bug to ftp.debian.org,
> I'd rather create a new Removal Request, then block 1100967 with it ?
Of course, thank you!
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102636
/Simon
signature.asc
Description: PGP signature
's not do anything more about this -- the upstream issue above
suggests that the package name we keep will be the right one in the
future. There are never promises that will really happen, but it seems
there is a lot of work to revert this for no particular advantage except
compliance
Control: tag -1 pending
Hello,
Bug #1102613 in oci-seccomp-bpf-hook reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/go-team/packages/oci-seccomp-bpf-hook/-/comm
y build scripts. I'll do an upload shortly cleaning this up a bit
as part of regular Go team maintainance, and will fix the FTBFS this way
too, but happy to resolve it some other way too.
/Simon
signature.asc
Description: PGP signature
lready prematurely migrated to. Given that there are no reverse
dependencies on golang-step-crypto-dev now, I think the simplest way out
of this mess is to ask for that package to be dropped.
/Simon
signature.asc
Description: PGP signature
Control: tag -1 pending
Hello,
Bug #1101345 in golang-github-xanzy-go-gitlab reported by you has been fixed in
the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/go-team/packages/golang-gitlab-git
On Fri, 04 Apr 2025 at 12:08:04 -0400, Jeremy Bícha wrote:
Then file removal requests for armel for cjs, cinnamon, and
cinnamon-desktop-environment.
This is time-sensitive, due to the freeze starting soon and the old
binaries blocking migration of cjs. As a result I opened
https://bugs.debian
this package
> is trying to access Internet and b) Maybe there are missing build-depends.
>
> - In either case, weird cases like this one are the reason I always offer
> a VM to test in case it's necessary.
Maybe you could add 'c) Maybe you uploaded a new version of a build
de
Control: tag -1 pending
Hello,
Bug #1102099 in game-data-packager reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/games-team/game-data-packager/-/commit/d38a724
On Tue, 25 Mar 2025 at 12:34:26 +, Simon McVittie wrote:
On Tue, 25 Mar 2025 at 14:17:32 +0300, Vladimir K wrote:
$ /usr/libexec/gvfsd-fuse -f /run/user/1000/gvfs
fuse: both 'want' and 'want_ext' are set
Laszlo, I assume this is not the result you expected afte
Control: retitle -1 game-data-packager: FTBFS: inkscape SIGABRT after throwing
an instance of 'Gio::DBus::Error'
Control: tags -1 = confirmed
"ninja: build stopped: subcommand failed" is a very generic error
message to be quoting (it's hardly better than "something is wrong").
The problem here
Control: tag -1 pending
Hello,
Bug #1101904 in litetlog reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/go-team/packages/litetlog/-/commit/7919a3eb35b326239eea5
github.com/smallstep
namespace. I doubt we can finish that transition before trixie though.
/Simon
signature.asc
Description: PGP signature
ick fix or workaround, or
even better long-term improvements, feel free to propose patches or do
uploads.
/Simon
Helmut Grohne writes:
> Attempting to coinstall golang-step-crypto-dev and
> golang-github-smallstep-crypto-dev results in an error.
>
> mmdebstrap --variant=ap
of these two library packages.
Meanwhile, it seems fine for golang-gitlab-gitlab-org-api-client-go-dev
to stay out of testing until we have resolved this.
/Simon
Helmut Grohne writes:
> Package: golang-gitlab-gitlab-org-api-client-go-dev
> Version: 0.123.0-1
> Severity: serious
>
somehow. Testing for regressions in e.g. Salsa CI
pipeline is not supported.
/Simon
signature.asc
Description: PGP signature
On Tue, 25 Mar 2025 at 14:26:42 +0100, László Böszörményi (GCS) wrote:
I think the break might be caused by the FUSE_CAP_* enum ->
defines conversion [1]. I need to check, but maybe the bits are
changed? I mean with enum FUSE_CAP_ATOMIC_O_TRUNC might have a value
of x and with defines now it migh
On Tue, 25 Mar 2025 at 13:47:33 +, Simon McVittie wrote:
I also wonder whether it would be better for fuse_set_feature_flag()
and fuse_unset_feature_flag() to set/unset the relevant flag in
conn->want *and* conn->want_ext, if it happens to be below the 32-bit
boundary. Th
Package: libfuse3-4
Version: 3.17.1-1
Severity: serious
Justification: regression in code that is (AFAICS) following upstream
recommendations
X-Debbugs-Cc: Michael Anderson , Vladimir K
Control: affects -1 + src:gvfs gvfs-fuse
On Tue, 25 Mar 2025 at 09:34:40 +, Michael Anderson wrote:
>Than
On Mon, 24 Mar 2025 at 17:38:05 -0400, Jeremy Bícha wrote:
Here are some links to third-party projects that have had to adapt to
changes in the new pygobject:
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/8653
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/
Control: clone -1 -2
Control: reassign -2 libfuse3-4
Control: retitle -2 libfuse3-4: regression in filesystems that use
fuse_conn_info.want
Control: severity -2 important
Control: forwarded -2 https://github.com/libfuse/libfuse/issues/1171
On Sat, 22 Mar 2025 at 13:34:36 +0100, László Böszörmény
Control: tag -1 pending
Hello,
Bug #1101025 in gvfs reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/gnome-team/gvfs/-/commit/bbd8df734d9a5b2d9fce013b20e1cb6f33c
Control: tag -1 pending
Hello,
Bug #1101046 in xdg-desktop-portal reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/debian/xdg-desktop-portal/-/commit/cbfdb750be4
On Sat, 22 Mar 2025 at 16:40:11 +0100, László Böszörményi (GCS) wrote:
On Sat, Mar 22, 2025 at 4:27 PM Simon McVittie wrote:
I think your footnotes have got lost?
I don't know if it was lost or not. It's in the bug log at least:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
On Sat, 22 Mar 2025 at 13:34:36 +0100, László Böszörményi (GCS) wrote:
Quick check done. It seems in the past FUSE capabilities were a 32
bit bitfield. It was moved to a 64 bit struct, causing an ABI break.
It was handled by the SONAME bump and more importantly the FUSE helper
functions started t
Control: tag -1 pending
Hello,
Bug #1098553 in golang-github-digitorus-pkcs7 reported by you has been fixed in
the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/go-team/packages/golang-github-dig
Control: tag -1 pending
Hello,
Bug #1100347 in golang-opentelemetry-otel reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/go-team/packages/golang-opentelemetry-o
lifecycle is managed including protection against unauthorized access.
/Simon
signature.asc
Description: PGP signature
On Tue, 11 Mar 2025 at 20:13:10 +0100, Bastian Germann wrote:
Control: clone -1 -2
Control: reassign -2 libstartup-notification0-dev
Please change sn_startup_sequence_get_last_active_time (and for
consistency, sn_startup_sequence_get_initiated_time as well) argument *tv_sec
to have a time_t type
On Fri, 14 Mar 2025 at 10:42:09 +, Luca Boccassi wrote:
Bumping severity as the package is uninstallable due to this issue.
d/control hardcodes the version range, so it needs a source update:
Package: python3-zstandard
Architecture: any
Depends:
${misc:Depends},
${python3:Depends},
${shlibs
On Fri, 14 Mar 2025 at 17:08:19 -0400, Jeremy Bícha wrote:
I'm thinking about closing this bug since the real bug is
https://bugs.debian.org/1100054 and practically we're going to fix
things there rather than change gobject-introspection.
This issue isn't causing practical problems for users of
Package: systemd-boot-tools
Version: 257.4-2
Severity: serious
Justification: Policy 7.6.1
> Preparing to unpack .../05-systemd-boot-tools_257.4-2+b1_amd64.deb ...
> Unpacking systemd-boot-tools (257.4-2+b1) ...
> dpkg: error processing archive
> /tmp/apt-dpkg-install-0VZjmc/05-systemd-boot-tools
Control: retitle 1100147 libstartup-notification0-dev: request to change
API/ABI of sn_startup_sequence_get_last_active_time on 32-bit
Control: tags 1100147 = moreinfo
Control: severity 1100147 wishlist
Control: submitter 1100147 b...@debian.org
Control: forwarded 1100147
https://gitlab.freedesk
ed my laptop.
Since then, I've had a baffling issue where the screen would stop repainting,
until [some workarounds]
...
While composing this reply I was doing a build of mutter with the patch from
upstream merge request 4321 that Simon has pointed out upthread (phew, lots of
tests during build
Control: tag -1 pending
Hello,
Bug #1100142 in glib reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/gnome-team/glib/-/commit/f15d051638c9d29ae308631432d0d84ae5e
Control: tag -1 pending
Hello,
Bug #1099743 in mutter reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/gnome-team/mutter/-/commit/fa7de224e6f64655dcd2f14ab794dad
1 - 100 of 1469 matches
Mail list logo
