Control: reassign -1 src:libdmapsharing 3.9.13-1
Control: merge 1055324 -1
Control: found 1055324 3.9.13-2
Control: affects 1055324 + totem
On Fri, 10 May 2024 at 00:07:54 +0200, Alban Browaeys wrote:
> When I open totem then quit it (whatver I dod inside totem even if I do
> nothing), I get this
Control: retitle -1 libglib2.0-dev:i386 on amd64 should not require qemu-user
Control: severity -1 wishlist
Control: tags -1 + help
On Wed, 08 May 2024 at 23:32:03 +0100, Simon McVittie wrote:
> > So, I now have to install qemu-user as dependency, which comes with a few
> > oth
Source: flatpak
Version: 1.14.8-1
Severity: important
Tags: help upstream
User: debian...@lists.debian.org
Usertags: flaky
X-Debbugs-Cc: debian...@lists.debian.org
Control: affects -1 + src:glib2.0
Control: found -1 1.4.6-1
One of the tests in Flatpak's extensive test-suite appears to be "flaky":
Source: fwupd
Version: 1.9.19-1
Severity: important
User: debian...@lists.debian.org
Usertags: flaky
X-Debbugs-Cc: debian...@lists.debian.org
Control: affects -1 + src:glib2.0
Control: found -1 1.9.16-1
fwupd appears to have a "flaky" autopkgtest: that is, an autopkgtest
that usually passes, but
Source: clevis
Version: 20-1
Severity: important
User: debian...@lists.debian.org
Usertags: flaky
X-Debbugs-Cc: debian...@lists.debian.org
Control: affects -1 + src:glib2.0
clevis appears to have a "flaky" autopkgtest: that is, an autopkgtest
that usually passes, but is not reliable.
This means
On Wed, 08 May 2024 at 23:24:57 +0200, Christian Klein wrote:
> I install both the i386 and amd64 version for multi-arch support.
>
> With the newest versions, a dependency to python was added.
>
> Unfortunately, the package has two dependencies for python:
> "python3:any"
> and
> "python3 |
Control: reassign -1 libglib2.0-0 2.80.0-10
Control: affects -1 + gnome-shell
Control: fixed -1 2.80.1-1
On Wed, 08 May 2024 at 23:10:19 +0200, Thomas Renard wrote:
> updating from testing version of gnome-shell to unstable version (44.9-2)
> looses the
> umlauts of a german keyboard.
This is
Control: forwarded -1 https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4053
Control: tags -1 + pending
On Wed, 08 May 2024 at 10:42:21 -0300, Pedro Carvalho wrote:
> After upgrading to version 2.74.6-2+deb12u1, I have noticed the following
> symbols are missing for some applications:
>
> ´ `
Control: forwarded -1 https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4053
Control: tags -1 + pending
On Wed, 08 May 2024 at 14:11:32 +0200, Hannah Stern wrote:
> Set the "<>" key (German keyboard) to compose (xmodmap), in combination
> with an US keyboard layout. Type compose " a
On Wed, 08 May 2024 at 03:48:21 +, unfathomabl...@protonmail.com wrote:
> Latest upgrade from 2.74.6-2 to 2.74.6-2+deb12u1 broke input of Japanese
> characters GTK programs (such as firefox, gedit etc).
For users of testing/unstable, this will be fixed as soon as I can,
probably by version
Control: reassign -1 libglib2.0-0 2.74.6-2+deb12u1
Control: affects -1 + gnome-shell
On Wed, 08 May 2024 at 11:42:10 +0200, pham...@bluewin.ch wrote:
> After today's update, the dead keys on my keyboard no longer work
This is a regression in GLib triggered by fixing CVE-2024-34397. I'm
testing a
Control: severity 1070706 normal
Control: severity 1070714 normal
On Tue, 07 May 2024 at 22:53:33 +0200, Cyril Brulebois wrote:
> Simon McVittie (2024-05-07):
> > do the release/installer teams consider udeb dependencies
> > on non-udeb packages, by udebs that d-i does not curren
On Tue, 07 May 2024 at 22:02:12 +0200, Paul Gevers wrote:
> On 07-05-2024 7:49 p.m., Simon McVittie wrote:
> > The version in testing, 4.12.5+ds-3, has the same dependencies, so this
> > is not a regression.
>
> Is it? It seems that the version in unstable depends on libpng
Control: tags -1 + d-i
Control: found -1 4.12.5+ds-3
Control: retitle -1 gtk4 udeb has unsatisfiable dependencies
Control: clone -1 -2
Control: retitle -2 libvte-2.91-0-udeb depends on both GTK 3 and GTK 4
Control: reassign -2 src:vte2.91 0.75.92-1
On Tue, 07 May 2024 at 15:44:02 +0100, Peter
As the one who reported the issue in the glibc upstream tracker, I'm now
of the opinion it's not a glibc bug, but rather issues with the
individual packages that are now FTBFS. As far as I know, this is either
a parser pretending to be GCC without implementing all the GCC features
(e.g.
ishing part for them and see about adding
an incremental snapshot.d.o copy while it is still working.
/Simon
signature.asc
Description: PGP signature
Control: retitle 1057620 doomsday: segfault in _XFlush() when Qt is using
native Wayland
On Mon, 06 May 2024 at 00:31:31 +0200, Bernhard Übelacker wrote:
> Bug 1062969 / Bug 1065714 mentions a workaround
> to be able to run doomsday with wayland:
>
> SDL_VIDEODRIVER=x11 QT_QPA_PLATFORM=xcb
ver? Or did you use some tool
to discover this that isn't linked from the PTS?
A patch like the one below seems to fix this. But maybe we should raise
a lintian wishlist bug report too.
/Simon
From 4144c80941d5d099b2ff6678750bae5419c74b6a Mon Sep 17 00:00:00 2001
From: Simon Josefsson
Date: Fri, 3 May
Package: chromium-common
Version: 124.0.6367.118-1~deb12u1
Severity: normal
Control: block 1038319 by -1
X-Debbugs-Cc: libu2f-h...@packages.debian.org
libu2f-udev has been an empty transitional package since Debian 11
(the version in Debian 10 had content). Please remove chromium-common's
With bookworm 'nut-scanner -S' works without problems.
Thanks for your work and support!
Simon
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.8.4-2-pve (SMP w/1 CPU thread; PREEMPT)
Kernel taint
Source: glib2.0
Version: 2.78.4-7
Severity: important
Tags: ftbfs trixie sid patch upstream fixed-upstream
Forwarded: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3945
X-Debbugs-Cc: Matthew Vernon
Control: fixed -1 2.80.0-7
GLib contains GRegex, an API wrapper around pcre2 (or pcre in
w *.orig.tar.gz uploads too often. So I prefer to not
fix this bug until we have to upload a more recent gnulib into the
archive for other reasons. I don't expect that to take long: I'm
planning to do new release of several projects (oath-toolkit, libidn2,
inetutils, etc) that use gnulib, and
p works but FUSE doesn't
+- New upstream stable release 1.14.8
+ + Respin of 1.14.7 reverting unintended submodule changes
+- d/control: Move dbus-system-bus from Depends to Recommends.
+ `flatpak run` no longer has a working system bus as a hard requirement
+ (verified in `podman
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: coreut...@packages.debian.org, p...@packages.debian.org,
debian-b...@lists.debian.org
Control: affects -1 + src:coreutils src:pam
coreutils_9.4-3.1 and pam_1.5.3-7 aren't
those bugs the attention that
they deserve.
I don't have the capacity either, but I have added it to my list of
things I should be looking into.
Simon
On Mon, 29 Apr 2024 at 17:12:05 +0200, Sebastian Ramacher wrote:
> It will also help dak to decruft the pre-t64 from unstable and render
> game-data-packages as good on the transition trackers.
OK. Would it be OK to make these dependencies be of the form
"libasound2t64 | libasound2" and so on, or
On Sun, 28 Apr 2024 at 17:27:21 +0200, Sebastian Ramacher wrote:
> quake4 has hard-coded dependencies on shared libraries (at least
> libasound2) that were renamed as part of the t64 transition. Please
> update the dependencies accordingly.
quake4 is i386-only, and i386 has Provides for the old
Control: retitle -1 python-icalendar: FTBFS with tzdata 2024a:
UnknownTimeZoneError: 'America/Godthab'
On Thu, 25 Apr 2024 at 18:27:15 +0200, Santiago Vila wrote:
> E pytz.exceptions.UnknownTimeZoneError: 'America/Godthab'
This was presumably triggered by this change in tzdata
Control: retitle -1 ruby-curb: test regression with curl 8.7.1: client read
function EOF fail, only only 4/5 of needed bytes read
User: debian...@lists.debian.org
Usertags: breaks needs-update
On Thu, 18 Apr 2024 at 22:42:11 +0200, Sebastian Ramacher wrote:
> Error:
On Wed, 24 Apr 2024 at 09:24:14 +0200, Francesco Potortì wrote:
> 2024-04-23T04:21:41.887252+02:00 tucano gvfsd-wsdd[1507271]: Failed to spawn
> the wsdd daemon: Failed to execute child process “wsdd” (No such file or
> directory)
> 2024-04-23T04:21:41.887324+02:00 tucano gvfsd-network[318402]:
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: flat...@packages.debian.org
Control: affects -1 + src:flatpak
After the dust has settled from CVE-2024-32462, I would like to do a
stable-update of Flatpak using the
; The patch attached to this bug report fixes the problem for me.
> Hopefully, it will not introduce false negatives.
Thanks for the patch. I've fixed it slightly differently to
reduce the chance of false negatives.
Best,
Simon
[1]
https://ruderich.org/simon/gitweb/?p=blhc/blhc.git;a=commi
If they could be modified to show the build
dependencies then I'll adapt blhc to detect this case.
Best,
Simon
--
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9
signature.asc
Description: PGP signature
So the suggested first approach should work fine and
cause the less additional maintenance overhead.
Best,
Simon
--
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9
signature.asc
Description: PGP signature
a patched
gnulib source code, before the package is building it.
/Simon
[1]
https://blog.josefsson.org/2024/04/13/reproducible-and-minimal-source-only-tarballs/
signature.asc
Description: PGP signature
Control: retitle -1 nautilus: FTBFS on arm64:
test-nautilus-search-engine-tracker timed out
(cc'ing Lucas in case whatever heuristics are parsing the log can be
improved)
On Sat, 20 Apr 2024 at 14:09:18 +0200, Lucas Nussbaum wrote:
> Relevant part (hopefully):
> > (tracker-miner-fs-3:3061640):
Control: retitle -1 libgweather4: FTBFS on arm64: Location 'Greenland' has
invalid timezone 'America/Godthab'
On Sat, 20 Apr 2024 at 14:06:28 +0200, Lucas Nussbaum wrote:
> Relevant part (hopefully):
> > # GLib-GIO-DEBUG: Failed to initialize portal (GNetworkMonitorPortal) for
> >
On Fri, 19 Apr 2024 at 14:09:24 +0200, Emilio Pozuelo Monfort wrote:
> On 19/04/2024 12:49, Simon McVittie wrote:
> > Fix CVE-2024-32462, a sandbox escape vulnerability, without having to
> > wait for the whole 64-bit time_t transition.
>
> Please go ahead once you're read
efine([flatpak_interface_age], [0])
m4_define([flatpak_binary_age],
diff -Nru flatpak-1.14.5/debian/changelog flatpak-1.14.6/debian/changelog
--- flatpak-1.14.5/debian/changelog 2023-12-08 12:25:50.0 +
+++ flatpak-1.14.6/debian/changelog 2024-04-19 11:00:13.0 +0100
@@ -1,3 +
Package: ansible
Version: 9.4.0+dfsg-1
Dear Maintainers
Thank you for updating and maintaining Ansible.
Ansible in Debian contains arista.eos collection version 6.2.2. Current
upstream version is 9.0.0. An update would be much appreciated.
Regards
Simon
the 'gnulib' package this way, to reduce
xz-related risks with vendored gnulib code. Should libntlm's
debian/control now include a 'Static-Built-Using: gnulib'?
/Simon
signature.asc
Description: PGP signature
it is intended or is due to a bug in a script
> (the "Fix gnulib-tool --version" seems to have done nothing
> significant).
The current version scheme is intentional, but I'm open to changing it.
That was a unrelated fix: before 'gnulib-tool --version' tried to parse
/usr/share/doc
Control: tags -1 + patch
On Thu, 25 Aug 2022 at 20:22:41 +0100, Simon McVittie wrote:
> [Evolution] depends on clutter-1.0, which is no longer maintained
> upstream (and has been effectively unmaintained for a while).
>
> It looks as though disabling the "contact maps"
Control: retitle -1 clutter-1.0: build-time tests fail on loong64
Control: tags -1 + moreinfo
On Thu, 18 Apr 2024 at 02:26:08 +, wuruilong wrote:
> The clutter software fails to compile on loongarch architecture,
> please refer to the attached patch to fix it.
This is not a fix, this is a
Package: ruby-rubygems
Version: 3.4.20-1
Severity: important
X-Debbugs-Cc: s...@nedra.be
* What led up to the situation?
Trying to build a website with Jekyll (through "bundle exec jekyll serve").
* What exactly did you do (or not do) that was effective (or ineffective)?
1. Running
git-archive' releases. We can
nudge upstream's to sign 'git-archive' exports of their projects,
though.
/Simon
[1]
https://blog.josefsson.org/2024/04/13/reproducible-and-minimal-source-only-tarballs/
signature.asc
Description: PGP signature
you think? I hope I'm not stepping on anyone's toes here. The
package was orphaned and is a critical component to be able to build
source-only tarballs for other packages in Debian.
/Simon
Simon Josefsson writes:
> Hi. I noticed gnulib in Debian was orphaned. I work upstream on gnu
On Wed, 10 Apr 2024 at 11:54:02 +0200, Christian Kastner wrote:
> I've already filed an MR at vmdb2 upstream that fixes the logic, but I
> thought it might be best to track the issue here as well. Please feel
> free to close this bug if you think it is superfluous.
If there's no actionable bug in
:31.0 +0200
@@ -1,3 +1,9 @@
+libelfin (0.3-3.1ubuntu1) noble; urgency=medium
+
+ * Fix autopkgtests against newer clang (Closes: 1065084, LP: #2060786)
+
+ -- Simon Chopin Wed, 10 Apr 2024 11:33:31 +0200
+
libelfin (0.3-3.1build1) noble; urgency=medium
* No-change rebuild for CVE-2024-3094
Package: python3-djangorestframework
Version: 3.14.0-2
Severity: normal
X-Debbugs-Cc: si...@lyngshede.dk
Dear Maintainer,
When deploying a Django application, using the staticfiles module, the
application will throw a 500, if the user attempts to access the a REST
endpoint using a normal
.5/debian/changelog 2024-03-31 10:08:02.0 +0200
+++ mpg123-1.32.5/debian/changelog 2024-04-03 20:29:56.0 +0200
@@ -1,3 +1,13 @@
+mpg123 (1.32.5-1ubuntu1) noble; urgency=medium
+
+ [ Steve Langasek ]
+ * Rename libraries for 64-bit time_t transition. (Closes: #1063140)
+
+
on vendored gnulib
code.
/Simon
Package: urlwatch
Version: 2.28-2
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A recommended
Package: telegram-send
Version: 0.37-2
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: python3-subliminal
Version: 2.1.0-3
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: sqlfluff
Version: 2.3.5-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: snakemake
Version: 7.32.4-2
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Source: rope
Version: 1.13.0-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A recommended
Package: python3-satpy
Version: 0.47.0-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: qiime
Version: 2024.2.0-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Source: pytoolconfig
Version: 1.3.1-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: python3-pytools
Version: 2023.1.1-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: python3-ulmo
Version: 0.8.8+dfsg1-3
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: python3-rply
Version: 0.7.7-3
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: python3-requests-cache
Version: 0.9.8-2
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in
Package: python3-os-faults
Version: 0.2.1-3
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: python3-openstacksdk
Version: 1.5.0-2
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2].
Package: python3-npe2
Version: 0.7.2-2
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: python3-miio
Version: 0.5.12-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: python3-mbed-ls
Version: 1.6.2+dfsg-10
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2].
Package: python3-ironicclient
Version: 5.4.0-2
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2].
Package: python3-fs
Version: 2.4.16-3
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Source: python-fastparquet
Version: 2024.2.0-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2].
Package: python3-fissix
Version: 21.6.6-3
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: python3-etesync
Version: 0.12.1-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: python3-datacache
Version: 1.2.1-2
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: python3-cobra
Version: 0.29.0-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: python3-pyspectral
Version: 0.13.0+ds-2
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in
Package: pyopencl
Version: 2023.1.3-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: pydoctor
Version: 23.9.1-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: python3-pycuda
Version: 2024.1~dfsg-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2].
Package: ptpython
Version: 3.0.26-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: printrun-common
Version: 2.0.1-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Source: platformdirs
Version: 4.2.0-1
Severity: important
Control: block 1060427 by -1
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A recommended replacement
Package: python3-pantalaimon
Version: 0.10.5-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2].
Package: python3-pako
Version: 0.3.1-2
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: openmotor
Version: 0.5.0-2
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: ofxstatement-plugins
Version: 20210310+nmu1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in
Package: ofxstatement
Version: 0.7.1-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: nvchecker
Version: 2.5-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A recommended
Package: python3-napari
Version: 0.5.0~a1-5
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: mu-editor
Version: 1.0.3+dfsg-6
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: python3-libpysal
Version: 4.10-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Source: jack-mixer
Version: 18-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A recommended
Package: python3-intake
Version: 0.6.6-3
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Source: defcon
Version: 0.10.3-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A recommended
Package: glean-parser
Version: 13.0.0-1
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A
Package: git-phab
Version: 2.9.0~git20170531+6877964-2
Severity: important
Control: block 1060427 by -1
Tags: trixie sid
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in
Package: python3-genx
Version: 3.6.22-2
Severity: important
Control: block 1060427 by -1
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A recommended
Package: crossgrader
Version: 0.0.3+nmu3
Severity: important
Control: block 1060427 by -1
User: debian-pyt...@lists.debian.org
Usertags: appdirs-removal
python3-appdirs is dead upstream[1] and its Debian maintainer has indicated
that it should not be included in trixie[2]. A recommended
1 - 100 of 15447 matches
Mail list logo