Bug#1073234: bookworm-pu: package gdk-pixbuf/2.42.10+dfsg-1+deb12u1
On Fri, Jun 14, 2024 at 5:18 PM Salvatore Bonaccorso wrote: > > Package: release.debian.org > Severity: normal > Tags: bookworm > X-Debbugs-Cc: gdk-pix...@packages.debian.org, Simon McVittie > , car...@debian.org > Control: affects -1 + src:gdk-pixbuf > User: release.debian@packages.debian.org > Usertags: pu > > Hi stable release managers, CC'ing Simon, > > [ Reason ] > gdk-pixbuf is affected by CVE-2022-48622, a memory corruption via > crafted .ani files, cf. #1071265. > > [ Impact ] > At least denial of service but potentially as well arbitrary code > execution. But we have classified in no-dsa and it does not warrant a > DSA on its own. > > [ Tests ] > Manual test against the poc in the upstream issue > https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/202 . > > [ Risks ] > Isolated changes, and the fix has been exposed in sid and trixie. > > [ Checklist ] > [x] *all* changes are documented in the d/changelog > [x] I reviewed all changes and I approve them > [x] attach debdiff against the package in (old)stable > [x] the issue is verified as fixed in unstable > > [ Changes ] > Three commits cherry-picked from upstream: > > * ANI: Reject files with multiple anih chunks (CVE-2022-48622) > (Closes: #1071265) > * ANI: Reject files with multiple INAM or IART chunks > * ANI: Validate anih chunk size > > The two other commits are not for CVE-2022-48622 but additional > hardening and fixing changes related to the ANI code. > > Simon, ideally we should do as well the fixup in bullseye, but I have > not looked at that version yet. Salvatore, I pushed commits a few days ago to the debian/bookworm and debian/bullseye branches of https://salsa.debian.org/gnome-team/gdk-pixbuf based directly on similar work that had been done by Ubuntu Security but I hadn't made time to do further testing and reach out to Debian Security. Do you want to use those versions or the version you have prepared now? Thank you, Jeremy Bícha
Bug#1073005: transmission: consider switching back to vendored libb64
On Fri, Jun 14, 2024 at 9:29 AM Alexandre Rossi wrote: > Regarding those valid points, because there is not reason to have the same > source in multiple packages, there are only 2 paths compliant with the Debian > policy: > > 1) Fix those points in src:libb64 for transmission and all rdepends > 2) Remove src:libb64 from Debian and then vendor in transmission source > > I'll try to move towards 1) and see how it goes. So for now, this is a > wontfix because against DFSG. I agree that it would be helpful if many of these issues were fixed for all users of libb64. On the other hand, this does not fix the fact that libb64 has been unmaintained since 2013 and therefore it still wouldn't be a good candidate to complete Ubuntu's Main Inclusion process even if the other issues were fixed. Therefore, Ubuntu will need to keep vendoring libb64 in transmission. I am unaware of any maintained version of libb64. I disagree that this violates the Debian Free Software Guidelines although it does violate what is normally considered "best practice" in Debian development. However, there are many exceptions to this best practice in Debian and there is a lot of vendored code. (Even after your recent work, transmission still has vendored code and that is not a DFSG violation). Notably, Debian ftpmasters routinely accept new packages that have vendored code as long as the code is correctly documented in debian/copyright (which had been done for transmission). See https://wiki.debian.org/EmbeddedCopies Thank you, Jeremy Bícha
Bug#1073156: freerdp2: Add autopkgtest
Source: freerdp2 Version: 2.11.5+dfsg1-1 Tags: patch Please apply this merge request to add autopkgtests for freerdp2. This has previously been done for freerdp3. https://salsa.debian.org/debian-remote-team/freerdp2/-/merge_requests/16 https://ci.debian.net/packages/f/freerdp3/ Thank you, Jeremy Bícha
Bug#1073151: rust-yoke: unsatisfiable dependency librust-yoke-derive-0.7-dev
Source: rust-yoke Version: 0.7.3-1 Severity: serious X-Debbugs-CC: sylves...@debian.org Control: block -1 by 1073146 librust-yoke-dev is uninstallable because it has Depends: librust-yoke-derive-0.7-dev It also has unsatisfiable Depends: librust-zerofrom-0.1+derive-dev (see the blocking bug) These issues are preventing rust-yoke from reaching Testing. https://tracker.debian.org/pkg/rust-yoke https://release.debian.org/transitions/html/rust.html https://piuparts.debian.org/sid/state-dependency-does-not-exist.html#librust-yoke-dev Thank you, Jeremy Bícha
Bug#1073145: rust-bcrypt: unsatisfiable dependency librust-getrandom-0.2+js-dev
Source: rust-bcrypt Version: 0.15.1-1 Severity: serious Control: affects -1 src:rust-getrandom X-Debbugs-CC: b...@debian.org librust-bcrypt-dev is uninstallable because it has Depends: librust-getrandom-0.2+js-dev While rust-getrandom 0.2 is packaged in Debian, librust-getrandom-0.2+js-dev is not. This issue is preventing rust-bcrypt from reaching Testing. https://tracker.debian.org/pkg/rust-bcrypt https://release.debian.org/transitions/html/rust.html https://piuparts.debian.org/sid/state-dependency-does-not-exist.html#librust-bcrypt-dev Thank you, Jeremy Bícha
Bug#1073146: rust-zerofrom: unsatisfiable dependency librust-zerofrom-derive-0.1-dev
Source: rust-zerofrom Version: 0.1.3-1 Severity: serious X-Debbugs-CC: sylves...@debian.org librust-zerofrom-dev is uninstallable because it has Depends: librust-zerofrom-derive-0.1-dev This issue is preventing rust-zerofrom from reaching Testing. https://tracker.debian.org/pkg/rust-zerofrom https://release.debian.org/transitions/html/rust.html https://piuparts.debian.org/sid/state-dependency-does-not-exist.html#librust-zerofrom-dev Thank you, Jeremy Bícha
Bug#1073077: krita: Fails to build with jpeg-xl 0.9
Source: krita Version: 1:5.2.2+dfsg-3 Severity: important Tags: ftbfs X-Debbugs-CC: jpeg...@packages.debian.org krita fails to build with jpeg-xl 0.9 available in Debian Experimental. I tried cherry-picking 2 patches which I thought might fix the issue but the build still fails for me. https://invent.kde.org/graphics/krita/-/commit/6ddb599 https://invent.kde.org/graphics/krita/-/commit/546765d Build logs https://launchpad.net/ubuntu/+source/krita/1:5.2.2+dfsg-3build3 https://launchpad.net/~jbicha/+archive/ubuntu/arch2/+sourcepub/16216044/+listing-archive-extra Thank you, Jeremy Bícha
Bug#1073069: magic-wormhole: Fails to build with Python 3.12
Source: magic-wormhole Version: 0.13.0-1 Severity: important Tags: ftbfs magic-wormhole 0.13.0-1 fails to build when the default Python 3 is switched to 3.12 (as was done with Ubuntu 24.04 LTS and will happen in Debian "soon"). This issue is fixed in magic-wormhole 0.14.0 so I recommend upgrading to that version. You can also close LP: #2068774 with your upload. https://launchpad.net/bugs/2068774 Thank you, Jeremy Bícha
Bug#1072821: wireshark: binNMUs revert t64 transition
On Sun, Jun 9, 2024 at 9:21 AM Bálint Réczey wrote: > I've just added sid and oracular. I can't recall any upload targeting > devel in Ubuntu, but it may work, thus I can add that as well. > I expect the next upstream SO version bump to take place this > summer/autumn, thus the code is expected to be short-lived. > Is there any better example of generating a t64 transitioned control > file for one set of releases and a not transitioned one for backports? I have seen 'devel' used for the upload series a few times in Ubuntu, but it's unusual. The simplest way to handle backporting is to ensure your package is not built on affected 32-bit architectures (armel & armhf for Debian release architectures). I'm not aware of anyone attempting debian/rules tweaks like you did for Debian Backports, but I've never worked with Debian Backports either. Thank you, Jeremy Bícha
Bug#1073050: rdma-core: Fails to build on several architectures: dh_install missing files
Source: rdma-core Version: 52.0-1 Severity: serious Tags: ftbfs rdma-core is failing to build on multiple architectures including the release architectures armel and armhf. Build logs https://buildd.debian.org/status/package.php?p=rdma-core Build log excerpt -- dh_install: warning: ibverbs-providers missing files: usr/lib/*/libhns.so.* dh_install: warning: libibverbs-dev missing files: usr/include/infiniband/hnsdv.h dh_install: warning: libibverbs-dev missing files: usr/lib/*/libhns.a dh_install: warning: libibverbs-dev missing files: usr/lib/*/libhns.so dh_install: warning: libibverbs-dev missing files: usr/lib/*/pkgconfig/libhns.pc dh_install: warning: libibverbs-dev missing files: usr/share/man/man3/hnsdv_*.3 dh_install: warning: libibverbs-dev missing files: usr/share/man/man7/hnsdv.7 Thank you, Jeremy Bícha
Bug#1073005: transmission: consider switching back to vendored libb64
Source: transmission Version: 4.0.6+dfsg-1 transmission-gtk is included in Ubuntu Desktop's default install (specifically the expanded install option). This means that transmission-gtk is in Ubuntu main and all its dependencies must be in Ubuntu main instead of in Ubuntu universe. libb64 is in Ubuntu universe. After an initial review, I determined that libb64 does not seem like a good candidate for Ubuntu's Main Inclusion process [1]. Therefore, I will need to re-vendor libb64 inside the transmission package. If Debian does the same, then it would be possible for Debian and Ubuntu to share the same packaging, allowing package improvements to more quickly reach Ubuntu during the part of Ubuntu's development cycle when automatic sync is enabled. Specifically: - libb64 has been unmaintained since 2013 https://sourceforge.net/p/libb64/git/commit_browser - libb64 has several open bugs, some of which have security implications https://sourceforge.net/p/libb64/bugs/ - libb64 is missing a pkgconfig file which is a relatively simple standard way for other software to use libb64 https://launchpad.net/bugs/1534293 - The Debian packaging is not using simple dh rules. The packaging seems to otherwise be fairly modern but it's more complicated than typical Debian packages. https://salsa.debian.org/alteholz/libb64/-/blob/master/debian/rules Reference -- [1] https://github.com/canonical/ubuntu-mir Thank you, Jeremy Bícha
Bug#1073004: transmission-qt: Switch to qt6
Package: transmission-qt Version: 4.0.6+dfsg-1 Please consider switching transmission-qt to build with Qt6 instead of Qt5. I think the Debian Qt/KDE team is going to try to switch to KDE 6 in time for the next major release of Debian (Debian 13 "Trixie"). Therefore, as long as the transmission qt6 build works reasonably well, I think it would be a better fit than the qt5 build. Thank you, Jeremy Bícha
Bug#1072993: please add OnlyShowIn=GNOME;Unity; in com.mattjakeman.ExtensionManager.desktop
On Tue, Jun 11, 2024 at 8:54 AM xiao sheng wen wrote: > The gnome-shell-extension-manager is only use in GNOME, so add field: > > OnlyShowIn=GNOME;Unity; While this could be done as a Debian specific patch, this could be useful to people using other distros too. Could you report this request to the upstream project at https://github.com/mjakeman/extension-manager/issues ? Also, you could try to submit your own git merge request there for this if you want. Note that Unity does not use GNOME Shell at all so you don't want Unity in the OnlyShowIn field. Thank you, Jeremy Bícha
Bug#1070815: libdrm-intel1 should be compiled for arm64
Control: reopen -1 Control: severity -1 serious Control: tags -1 +ftbfs -patch After this change, libdrm is failing to build on arm64. Build log excerpt dh_install: warning: Cannot find (any matches for) "usr/lib/*/libdrm_intel.so.1*" (tried in ., debian/tmp) dh_install: warning: libdrm-intel1 missing files: usr/lib/*/libdrm_intel.so.1* Full build log - Click Build-Attempted at https://buildd.debian.org/status/package.php?p=libdrm Thank you, Jeremy Bícha
Bug#1052660: gst-plugins-bad1.0: Fails to build: netsim build test failing
On Tue, Jun 11, 2024 at 7:02 AM Emilio Pozuelo Monfort wrote: > On Mon, 25 Sep 2023 15:52:57 -0400 Jeremy Bicha > wrote: > > Forwarded: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3000 > > > > gst-plugins-bad1.0's elements_netsim build test began failing sometime > > after July 6 but before August 15 because of a change in its build > > depends. > > > > Also reported as https://launchpad.net/bugs/2037323 > > I don't see this happening on the Debian buildds from looking at a few old > logs. > Not sure if it's fixed or if it was specific to some buildd configuration, but > for now let's downgrade the bug. We simply ignore the test failure. Thank you for downgrading! https://salsa.debian.org/gstreamer-team/gst-plugins-bad1.0/-/blob/master/debian/patches/Skip-failing-tests.patch Jeremy Bícha
Bug#1072914: xdg-terminal-exec: [Debdiff] Run upstream tests and provide manual page.
Thank you very much for adding the build test override and autopkgtests. I have applied those improvements with minor tweaks. Could you please forward the manpage upstream? I consider a missing manpage to usually be a fairly minor Debian bug but I'd be happy to cherry-pick that after it is accepted upstream. Anyway, the manpage is a separate fix from the tests so in the future I encourage you to split it into a separate commit or merge request (or Debian bug). Jeremy Bícha
Bug#1060474: Bug#1072960: pulseaudio: diff for NMU version 16.1+dfsg1-5.1
On Mon, Jun 10, 2024 at 6:24 PM Chris Hofstaedtler wrote: > I've prepared an NMU for pulseaudio (versioned as 16.1+dfsg1-5.1) and > uploaded it to DELAYED/7. Please feel free to tell me if I > should delay it longer. Feel free to upload now without delay. Thank you, Jeremy Bícha
Bug#1072963: jpeg-xl: Failing autopkgtests on non-amd64
Source: jpeg-xl Version: 0.9.2-6 Severity: serious Tags: experimental jpeg-xl in experimental has autopkgtests that are failing on all architectures except for amd64. Specifically, the problem is that debian/libjxl-gdk-pixbuf.postinst and debian/libjxl-gdk-pixbuf.postrm have hardcoded the amd64 architecture which means that libjxl-gdk-pixbuf is uninstallable on architectures other than amd64. https://ci.debian.net/packages/j/jpeg-xl/unstable/arm64/ https://salsa.debian.org/debian-phototools-team/libjxl/-/blob/debian/experimental/debian/libjxl-gdk-pixbuf.postinst Thank you, Jeremy Bícha
Bug#1072943: jpeg-xl: Simplify symbols file
Source: jpeg-xl Version: 0.9.2-6 Tags: patch I'm submitting a merge request with multiple improvements to the symbols file (most from Gianfranco Costamagna) https://salsa.debian.org/debian-phototools-team/libjxl/-/merge_requests/4 Thank you, Jeremy Bícha
Bug#1072938: jupyterhub: Unsatisfiable Build-Depends python3-pydantic (>= 2)
Source: jupyterhub Version: 5.0.0+ds1-1 Severity: serious Tags: ftbfs Control: block -1 by 1052028 Control: unblock 107192 by 1052028 X-Debbugs-CC: lola...@debian.org jupyterhub is unable to build from source because it has Build-Depends: python3-pydantic >=2 but the latest version of python3-pydantic in Debian is 1.10.14. Thank you, Jeremy Bícha
Bug#1072879: fonts-conf.5: some remarks and editorial fixes for this man page
Control: tags -1 upstream On Sun, Jun 9, 2024 at 1:15 PM Bjarni Ingi Gislason wrote: > Package: fontconfig-config > Version: 2.15.0-1.1 > Severity: minor > Tags: patch > > Dear Maintainer, > >* What led up to the situation? > > Checking for defects with > > [test-]groff -mandoc -t -K utf8 -ww -b -z The manpage is generated by the upstream build, not by Debian-specific code. Please work with upstream to fix manpage issues in fontconfig rather than in Debian directly. https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues Thank you, Jeremy Bícha
Bug#1072821: wireshark: binNMUs revert t64 transition
That debian/rules code seems fragile. Beyond sid, it also doesn't recognize several other valid upload targets: experimental, oracular (for Ubuntu), devel (for Ubuntu), forky (not valid yet but it will be the release after trixie). Thank you, Jeremy Bícha
Bug#1072863: RM: libpoppler-qt6-3t64 libpoppler-qt6-dev [i386] -- RoM; ANAIS for specific packages
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: popp...@packages.debian.org, sramac...@debian.org Control: affects -1 src:poppler poppler's qt6 bindings are no longer built on i386. Previously, we have already removed i386 binary packages for the 3 reverse dependencies: photoqt, qpdfview, texworks after coordination with their maintainers. poppler's other binary packages are still built on i386 so please only remove these 2 packages. dak rm -R -b libpoppler-qt6-3t64 libpoppler-qt6-dev -a i386 Thank you, Jeremy Bícha
Bug#1070972: epiphany-browser fails to render webpages - blank pages
On Sat, Jun 8, 2024 at 2:42 PM Dennis Camera wrote: > I am seeing the same bug with Epiphany 43.1 on Debian bookworm (12.5) > since upgrading libwebkit2gtk-4.1-0 from version 2.42.5 to 2.44.2. > > I attached the output of webkit://gpu at the end of this e-mail. Thank you for the details. Please file a new bug for your issue even though it might appear to be similar to an existing bug. In your case, you are providing graphics details which can help if this bug is specific to your graphics drivers. The original reporter did not provide that information so it would be difficult to know whether they are affected by a graphics driver bug. More importantly, your issue is with Debian 12, but the original report is about Debian Testing which has many differences compared to Debian 12. Thank you, Jeremy Bícha
Bug#1072835: jpeg-xl: Failing autopkgtests
Source: jpeg-xl Version: 0.9.2-5 Severity: serious Tags: experimental jpeg-xl in experimental has failing autopkgtests. https://release.debian.org/britney/pseudo-excuses-experimental.html#jpeg-xl https://ci.debian.net/packages/j/jpeg-xl/unstable/amd64/ autopkgtest log excerpt == md5sum: traffic_light-0-ec0.ppm: No such file or directory traffic_light-0-ec0.ppm: FAILED open or read traffic_light-0-ec1.pgm: FAILED open or read md5sum: traffic_light-0-ec1.pgm: No such file or directory md5sum: traffic_light-1-ec0.ppm: No such file or directory traffic_light-1-ec0.ppm: FAILED open or read md5sum: traffic_light-1-ec1.pgm: No such file or directory traffic_light-1-ec1.pgm: FAILED open or read md5sum: traffic_light-2-ec0.ppm: No such file or directory traffic_light-2-ec0.ppm: FAILED open or read md5sum: traffic_light-2-ec1.pgm: No such file or directory traffic_light-2-ec1.pgm: FAILED open or read md5sum: traffic_light-3-ec0.ppm: No such file or directory traffic_light-3-ec0.ppm: FAILED open or read md5sum: traffic_light-3-ec1.pgm: No such file or directory traffic_light-3-ec1.pgm: FAILED open or read md5sum: animation_patches-0-ec0.ppm: No such file or directory animation_patches-0-ec0.ppm: FAILED open or read md5sum: animation_patches-0-ec1.pgm: No such file or directory animation_patches-0-ec1.pgm: FAILED open or read md5sum: animation_patches-1-ec0.ppm: No such file or directory animation_patches-1-ec0.ppm: FAILED open or read md5sum: animation_patches-1-ec1.pgm: No such file or directory animation_patches-1-ec1.pgm: FAILED open or read pq_gradient.pgm: OK md5sum: WARNING: 12 listed files could not be read Thank you, Jeremy Bícha
Bug#1051615: rust-minijinja: Uninstallable dependencies
Control: reopen -1 librust-mininija-dev is still uninstallable because it has Depends: librust-v-htmlescape-0.15+default-dev and librust-indexmap-1+default-dev but neither of those exist in Debian. This was detected by Britney and piuparts lists the specific missing dependencies. https://tracker.debian.org/pkg/rust-minijinja Thank you, Jeremy Bícha
Bug#1072773: rust-launchpadlib: Missing dependency: librust-keyring-dev
Source: rust-launchpadlib Version: 0.2.0-1 Severity: serious X-Debbugs-CC: jel...@debian.org librust-launchpadlib-dev is uninstallable because it has Depends: librust-keyring-2+default-dev but that package does not exist in Debian. britney has detected this and is preventing migration to Testing. piuparts also shows the specific missing dependency. https://tracker.debian.org/pkg/rust-launchpadlib Thank you, Jeremy Bícha
Bug#1072712: ITP: tinysparql -- rename of tracker
Package: wnpp Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org, debian-gtk-gn...@lists.debian.org Control: affects -1 src:tracker Owner: jeremy.bi...@canonical.com Package Name: tinysparql Version: 3.8 (not yet released yet) Upstream Author: Sam Thursfield, Carlos Garnacho and others License: GPL-2+. Library: LGPL-2.1+ Programming Lang: C Description: metadata database, indexer and search tool TinySPARQL is an advanced framework for first class objects with associated metadata and tags. It provides a one stop solution for all metadata, tags, shared object databases, search tools and indexing. . TinySPARQL was previously known as Tracker. Other Info -- TinySPARL is a rename of the Tracker file indexer included by default in GNOME. The primary driver for this rename is that privacy-conscious curious users are disturbed by the persistent background process named tracker-miner-fs-3. It sounds like something is tracking users perhaps for malicious reasons. Miner brings to mind cryptocurrency miners that could have been installed without authorization. Concerned users can complain or may try to disable or remove these services and break core functionality of their desktop environment. The Debian GNOME team intends to package tinysparql (and the tracker-miners replacement named localsearch) in Experimental probably in July. The intent is for the new binary packages to replace the existing tracker packages. We expect to do the transition in Unstable later in the year. https://gitlab.gnome.org/GNOME/tracker/-/issues/437 Thanks, Jeremy Bícha
Bug#1072711: ITP: localsearch -- rename of tracker-miners
Package: wnpp Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org, debian-gtk-gn...@lists.debian.org Control: affects -1 src:tracker-miners Owner: jeremy.bi...@canonical.com Package Name: localsearch Version: 3.8 (not yet released yet) Upstream Author: Sam Thursfield, Carlos Garnacho and others License: GPL-2+ (some parts are LGPL-2.1+) Programming Lang: C Description: metadata database, indexer and search tool - filesystem indexer This package contains the indexer for indexing your files and folders. . localsearch is an advanced framework for first class objects with associated metadata and tags. It provides a one stop solution for all metadata, tags, shared object databases, search tools and indexing. . localsearch was previously known as Tracker Miners. Other Info -- localsearch is a rename of the tracker-miners file indexer included by default in GNOME. The primary driver for this rename is that privacy-conscious curious users are disturbed by the persistent background process named tracker-miner-fs-3. It sounds like something is tracking users perhaps for malicious reasons. Miner brings to mind cryptocurrency miners that could have been installed without authorization. Concerned users can complain or may try to disable or remove these services and break core functionality of their desktop environment. The Debian GNOME team intends to package localsearch (and the tracker replacement named tinysparql) in Experimental probably in July. The intent is for the new binary packages to replace the existing tracker-miners packages. We expect to do the transition in Unstable later in the year. https://gitlab.gnome.org/GNOME/tracker-miners/-/issues/346 Thanks, Jeremy Bícha
Bug#1072700: lintian-brush: Don't correct debhelper-but-no-misc-depends for compat 14+
I worked around this in my package by using a Lintian override to suppress debhelper-but-no-misc-depends https://salsa.debian.org/gnome-team/gnome-boxes/-/blob/debian/latest/debian/source/lintian-overrides Thank you, Jeremy Bícha
Bug#1072700: lintian-brush: Don't correct debhelper-but-no-misc-depends for compat 14+
Source: lintian-brush Version: 0.152 Control: block -1 by 1067653 Please don't run debhelper-but-no-misc-depends.py when the dh compat level is set to 14 or higher. Perhaps this issue ought to be fixed by having lintian not emit this warning for dh compat 14+ packages. See the blocked bug. I filed this bug because maybe lintian-brush may want to handle this independently until lintian is fixed. https://manpages.debian.org/unstable/debhelper-compat-upgrade-checklist#v14 Thank you, Jeremy Bícha
Bug#1072698: debhelper: Mark 14 as stable?
Source: debhelper Version: 13.15.3 Do you intend to mark debhelper 14 as stable in time for the next major Debian stable release (Debian 13 "Trixie")? There are interesting features and improvements in compat 14 that I would like to use in my packages but I hesitate because as long as 14 is open for development, there is a risk that changes could cause packages to fail to build. Thank you, Jeremy Bícha
Bug#1072491: Acknowledgement (libglib2.0-0t64: Dead keys stopped working, again!)
On Thu, Jun 6, 2024 at 11:12 AM Michael Rasmussen wrote: > Reason: Either the package gnome-session-bin was uninstalled or > gnome-session-bin is now a requirement for working dead keys? What desktop are you using? gnome-session-bin is a required dependency for many desktops. Thank you, Jeremy Bícha
Bug#1072679: ITP: papers -- PDF document viewer for GNOME
Package: wnpp Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org, debian-gtk-gn...@lists.debian.org Control: affects -1 src:papers Owner: jeremy.bi...@canonical.com Package Name: papers Version: 46.1 Upstream Author: Pablo Correa Gómez, Markus Göllnitz, Evince authors License: GPL-2+ Programming Lang: C and Rust Description: PDF document viewer for GNOME Papers is a simple multi-page document viewer. It can display and print DjVu, Portable Document Format (PDF) and XML Paper Specification (XPS) files. When supported by the document, it also allows searching for text, copying text to the clipboard, hypertext navigation, and table-of-contents bookmarks. Other Info -- Papers is a fork of Evince. Papers uses GTK4 and libadwaita (evince uses GTK3). The app now uses Rust for some features. Papers has been proposed to replace Evince as the default PDF viewer for GNOME 47. Evince is not just an app but also libraries for other apps to support PDF (etc.) viewing. Papers also provides those libraries but they have been renamed and use GTK4 now. Those other apps may not be ready for GTK4 yet so we will keep the Evince libraries available for Debian 13. It hasn't yet been finalized what formats the app will support beyond PDF. DVI support has been dropped upstream. Debian, like most distros, has continued to enable viewing PostScript files in Evince although the Evince developers have disabled that by default for years. This package will be maintained by the Debian GNOME team. Packaging will be at https://salsa.debian.org/gnome-team/papers The upstream source is at https://gitlab.gnome.org/GNOME/Incubator/papers Thanks, Jeremy Bícha
Bug#1072657: rust-subtile: Fails to build
Source: rust-subtile Version: 0.1.7-1 Severity: serious Tags: ftbfs rust-subtile is failing to build. https://buildd.debian.org/status/package.php?p=rust-subtile Build log excerpt --- error[E0433]: failed to resolve: use of undeclared crate or module `profiling` --> src/image/mod.rs:71:3 | 71 | #[profiling::function] | ^ use of undeclared crate or module `profiling` Thank you, Jeremy Bícha
Bug#1072541: gedit: Update to 47
Source: gedit Version: 46.2-3 Severity: wishlist Control: affects -1 src:gedit-plugins Control: block -1 by 1072540 There is a new version of gedit available. However, it requires a new version of tepl which has been renamed to libgedit-tepl (no other reverse dependencies except gedit-plugins which has also been updated). More importantly, it intentionally breaks translations. See the blocking bug. Thank you, Jeremy Bícha
Bug#1072540: gedit: 47 drops all translations
Source: gedit Severity: important Tags: l10n X-Debbugs-CC: budgie-desktop-environm...@packages.debian.org gedit 47 has disabled all translations because key UI libraries are not hosted on https://gitlab.gnome.org/ . This is particularly frustrating because it is the gedit maintainer's decision to move the libraries to https://github.com/gedit-technology Thank you, Jeremy Bícha
Bug#1072512: debci: mutter fails tests
Control: severity -1 important Control: tags -1 upstream On Mon, Jun 3, 2024 at 4:16 AM Drew Parsons wrote: > Source: mutter > Version: 44.8-3.1 > Severity: serious > Justification: debci > Control: affects -1 libxcursor-dev > > mutter is failing tests in debci. > This is blocking migration of libxcursor to testing. The tests passed on retry and libxcursor is no longer blocked from migrating. Sorry that the autopkgtests are flaky. :( Thank you, Jeremy Bícha
Bug#1072130: geary: FTBFS: MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)
On Tue, May 28, 2024 at 6:39 PM Santiago Vila wrote: > --- stderr --- > MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER) > glx: failed to create drisw screen > > (test-client:335985): GLib-Net-WARNING **: 16:07:18.084: Failed to load TLS > database: System trust contains zero trusted certificates; please investigate > your GnuTLS configuration The actual error is "Failed to load TLS database" which makes the build failure a duplicate of https://bugs.debian.org/1064744 (which was already marked as affecting geary). For instance, the ZINK error is also seen with Test 8 but Test 8 passes. However, I'll go ahead and do an upload to get rid of the ZINK stderr in the build tests to make this more obvious. Thank you, Jeremy Bícha
Bug#1064372: evolution: segfault during startup
Are you still experiencing this crash with evolution 3.52.1 in Debian Testing (or 3.52.2 which will reach Testing in a few days)? Thank you, Jeremy Bícha
Bug#1072124: gnome-shell: CVE-2024-36472
On Tue, May 28, 2024 at 5:37 PM Moritz Muehlenhoff wrote: > > On Tue, May 28, 2024 at 05:33:32PM -0400, Jeremy Bícha wrote: > > Control: forwarded -1 > > https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7688 > > > > On Tue, May 28, 2024 at 5:24 PM Moritz Mühlenhoff wrote: > > > CVE-2024-36472[0]: > > > | In GNOME Shell through 45.7, a portal helper can be launched > > > | automatically (without user confirmation) based on network responses > > > | provided by an adversary (e.g., an adversary who controls the local > > > | Wi-Fi network), and subsequently loads untrusted JavaScript code, > > > | which may lead to resource consumption or other impacts depending on > > > | the JavaScript code's behavior. > > > > The initial GNOME issue was closed already (the CVE was requested by > > someone who is not a GNOME developer). But GNOME Shell may change the > > workflow for the captive portal helper so we can leave this bug open, > > pointing to the new issue that was opened upstream. > > Yeah, the never filed a bug for the botched CVE assignment, this is the > bug reference explocitly for the followup actionable filed by Michael > Catanzaro Oh, the bug reporter actually requested 2 CVEs. CVE-2024-36472 which you already filed the Debian bug for, is https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7688 and is recognized as valid by GNOME. The other CVE, CVE-2023-50977, was closed already in NIST. Thank you, Jeremy Bícha
Bug#1072124: gnome-shell: CVE-2024-36472
Control: forwarded -1 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7688 On Tue, May 28, 2024 at 5:24 PM Moritz Mühlenhoff wrote: > CVE-2024-36472[0]: > | In GNOME Shell through 45.7, a portal helper can be launched > | automatically (without user confirmation) based on network responses > | provided by an adversary (e.g., an adversary who controls the local > | Wi-Fi network), and subsequently loads untrusted JavaScript code, > | which may lead to resource consumption or other impacts depending on > | the JavaScript code's behavior. The initial GNOME issue was closed already (the CVE was requested by someone who is not a GNOME developer). But GNOME Shell may change the workflow for the captive portal helper so we can leave this bug open, pointing to the new issue that was opened upstream. Thank you, Jeremy Bícha
Bug#1065553: marked as done (fonts-jetbrains-mono: Jetbrains-Mono 2.304 broken in Gnome Terminal)
> Tried again, and the problem goes away if I close all open gnome-terminals, > so this bug can be closed. > I guess it's a problem in gnome-terminal that doesn't detect the font file > changed, and tries accessing glyphs in wrong locations in the font file > (based on the older file). There is a longstanding bug where apps need to be restarted to make use of updated fonts. A particularly serious report of this is https://bugs.debian.org/788791 which is mitigated because the Cantarell font (the default UI font for Debian's GNOME Shell) is only updated rarely. Thank you, Jeremy Bícha
Bug#1071546: rust-curve25519-dalek: failing autopkgtests
Source: rust-curve25519-dalek Version: 4+20240207+dfsg-3 Severity: serious rust-curve25519-dalek's autopkgtests are failing in 3 places. The failing autopkgtests are preventing migration to Testing. https://qa.debian.org/excuses.php?package=rust-curve25519-dalek error: none of the selected packages contains these features: fiat_backend error: none of the selected packages contains these features: bench error[E0412]: cannot find type `StaticSecret` in this scope Thank you, Jeremy Bícha
Bug#1071528: ITP: hardinfo2 -- Hardinfo2 offers System Information and Benchmark for Linux Systems
On Mon, May 20, 2024 at 11:09 AM Lucas Castro wrote: > Package: wnpp > Severity: wishlist > Owner: Lucas Castro > X-Debbugs-Cc: debian-de...@lists.debian.org > > * Package name: hardinfo2 > Version : 2.1.2 > Upstream Contact: Name > * URL : https://hardinfo2.org/ > * License : GPL-2 > Programming Lang: C > Description : Hardinfo2 offers System Information and Benchmark for > Linux Systems > > Hardinfo2 is based on hardinfo, which have not been released >10 years. > Hardinfo2 is the reboot that was needed. > > Hardinfo2 offers System Information and Benchmark for Linux Systems. It is > able to > obtain information from both hardware and basic software. It can benchmark > your system and compare > to other machines online. > > Features include: > - Report generation (in either HTML or plain text) > - Online Benchmarking - compare your machine against other machines > > Status > -- > - Capabilities: Hardinfo2 currently detects most software and hardware > detected by the OS. > - Features: Online database for exchanging benchmark results. > - Development: Currently done by contributors, hwspeedy maintains > > Hardinfo2 is based on hardinfo, which have not been released >10 years. > Hardinfo2 is the reboot that was needed. Please see https://bugs.debian.org/1071373 (ITS: hardinfo) and coordinate with Boyuan Yang on updating hardinfo. Thank you, Jeremy Bícha
Bug#1071537: rust-snow: autopkgtest failures
Source: rust-snow Version: 0.9.6-4 Severity: serious rust-snow's autopkgtest is still failing which prevents migration to Testing. https://qa.debian.org/excuses.php?package=rust-snow Excerpt -- error[E0599]: no function or associated item named `new` found for struct `snow::Builder` in the current scope --> tests/vectors.rs:151:37 | 151 | let mut init_builder = Builder::new(params.clone()); | ^^^ function or associated item not found in `Builder<'_>` Thank you, Jeremy Bícha
Bug#1071517: hardinfo: Unnecessary Build-Depends libsoup2.4
Package: hardinfo Version: 0.5.1+git20180227-2.1 Severity: important Tags: trixie sid User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: libsoup2 X-Debbugs-CC: by...@debian.org hardinfo has Build-Depends: libsoup2.4-dev but doesn't use libsoup at all. I checked with rgrep -i soup Thank you, Jeremy Bícha
Bug#1071514: RM: qpdfview [i386] -- RoM; NBS; no reverse dependencies
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: qpdfv...@packages.debian.org Control: affects -1 src:qpdfview poppler's qt6 bindings are no longer built on i386. This means that qpdfview is no longer buildable on i386; therefore, please remove qpdfview from i386. qpdfview has no reverse dependencies, but both lqxt and xfe have Recommends: qpdfview. Please let me know if we need to update those packages to drop the Recommends on i386. I got approval from Debian's qpdfview maintainer Louis-Philippe Véronneau before filing this bug. Thank you, Jeremy Bícha
Bug#1071513: RM: photoqt [i386] -- RoQA; NBS; no reverse dependencies
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: phot...@packages.debian.org Control: affects -1 src:photoqt poppler's qt6 bindings are no longer built on i386. This means that photoqt is no longer buildable on i386; therefore, please remove photoqt from i386. photoqt has no reverse dependencies. Thank you, Jeremy Bícha
Bug#1071253: rust-snow: autopkgtest failures
Control: retitle -1 rust-snow: autopkgtest failures rust-snow builds now but its autopkgtests fail which blocks migration to Testing. I saw this in a brief look at the autopkgtest log but there may be other errors: error: no matching package named `aes-gcm` found https://qa.debian.org/excuses.php?package=rust-snow Thank you, Jeremy Bícha
Bug#1071259: foxtrotgps: Unnecessary Build-Depends libsoup2.4
Patch attached Thank you, Jeremy Bícha From: Jeremy Bicha Date: Fri, 17 May 2024 12:15:28 +0200 Subject: Drop obsolete Build-Depends: libsoup2.4-dev Closes: #1071259 --- debian/control | 1 - 1 file changed, 1 deletion(-) diff --git a/debian/control b/debian/control index 6281f17..6759913 100644 --- a/debian/control +++ b/debian/control @@ -13,7 +13,6 @@ Build-Depends: libglade2-dev, libgps-dev, libgtk2.0-dev, - libsoup2.4-dev, libsqlite3-dev, libxml2-dev, texinfo,
Bug#1071259: foxtrotgps: Unnecessary Build-Depends libsoup2.4
Package: foxtrotgps Version: 1.2.2+bzr332-1 Severity: important Tags: trixie sid patch User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: libsoup2 foxtrotgps has Build-Depends: libsoup2.4-dev but doesn't use libsoup at all. I checked with rgrep -i soup foxtrotgps uses Beautiful Soup (python3-bs4) which is different than libsoup. In my follow-up email, I am attaching a patch to fix this issue Thank you, Jeremy Bícha
Bug#1071252: rust-libp2p-identity: fails to build
Source: rust-libp2p-identity
Version: 0.2.8+ds-4
Severity: serious
Tags: ftbfs
rust-libsp2p-identity fails to build from source in Unstable because
of a build test error:
https://buildd.debian.org/status/package.php?p=rust-libp2p-identity
Running
`/<>/target/x86_64-unknown-linux-gnu/release/deps/keypair_api-0ab69a7110130a15`
running 1 test
test calling_keypair_api ... FAILED
failures:
calling_keypair_api stdout
thread 'calling_keypair_api' panicked at 'internal error: entered
unreachable code', identity/src/keypair.rs:329:9
stack backtrace:
0: rust_begin_unwind
at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5
1: core::panicking::panic_fmt
at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14
2: core::panicking::panic
at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:117:5
3: libp2p_identity::keypair::Keypair::from_protobuf_encoding
at ./src/keypair.rs:329:9
4: keypair_api::calling_keypair_api
at ./tests/keypair_api.rs:5:13
5: keypair_api::calling_keypair_api::{{closure}}
at ./tests/keypair_api.rs:4:26
6: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
7: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a
verbose backtrace.
Thank you,
Jeremy Bícha
Bug#1071253: rust-snow: Fails to build, missing crate x25519_dalek
Source: rust-snow Version: 0.9.6-2 Tags: ftbfs rust-snow fails to build in Unstable. This is an excerpt from the build log: https://buildd.debian.org/status/package.php?p=rust-snow error[E0432]: unresolved import `x25519_dalek` --> tests/general.rs:13:5 | 13 | use x25519_dalek as x25519; | ^^ no external crate `x25519_dalek` Thank you, Jeremy Bícha
Bug#1071250: rust-imap-codec: Fails to build: error: no matching package named `libfuzzer-sys` found
Source: rust-imap-codec Version: 1.0.0-2 Severity: serious Tags: ftbfs rust-imap-codec fails to build from source in Unstable. This line shows in its build log: error: no matching package named `libfuzzer-sys` found https://buildd.debian.org/status/package.php?p=rust-imap-codec Thank you, Jeremy Bícha
Bug#1061179: Bug#1060019: transition: poppler 24.02
libpoppler134 has migrated to Testing and I don't see libpoppler126 there any more so I'm closing the poppler transition bug. Thank you, Jeremy Bícha
Bug#1071141: gnome-remote-desktop: `/usr/lib/tmpfiles.d/gnome-remote-desktop-tmpfiles.conf:2: Failed to resolve user 'gnome-remote-desktop': No such process`
On Wed, May 15, 2024 at 7:51 AM Paul Menzel wrote: > gnome-remote-desktop (46.1-3) wird eingerichtet ... > /usr/lib/tmpfiles.d/gnome-remote-desktop-tmpfiles.conf:2: Failed to > resolve user 'gnome-remote-desktop': No such process > /usr/lib/tmpfiles.d/gnome-remote-desktop-tmpfiles.conf:3: Failed to > resolve user 'gnome-remote-desktop': No such process > Creating group 'gnome-remote-desktop' with GID 987. > > The failure lines were printed in red. Yes, I am tracking this in https://bugs.debian.org/1070119 and https://bugs.debian.org/1070473 Thank you, Jeremy Bícha
Bug#1070119: gnome-remote-desktop: missing gnome-remote-desktop user setup in salsa upcoming 46 version
Control: reopen -1 Control: retitle -1 gnome-remote-desktop: long delay when first installing version 46 Control: block 1050237 by -1 I'm not happy with the performance of what I've implemented because it still has the 90 second delay even though gnome-remote-desktop is otherwise working now. See also https://bugs.debian.org/1070473 Thank you, Jeremy Bícha
Bug#1070862: poppler: possibly unintended revert of t64 renames for non-main library in 24.x
Control: severity -1 serious On Fri, May 10, 2024 at 1:48 PM Simon McVittie wrote: > Please bump this up to RC if analysis shows that it is a genuine problem, > or close it if analysis shows that I'm being overly cautious. I think it is appropriate to bump this to RC. I will try to get this upload done by tomorrow; I'm in the midst of a busy travel week. Thank you, Jeremy Bícha
Bug#1070836: rust-apple-nvram: Switch from rust-nix 0.26 to 0.27
Source: rust-apple-nvram Version: 0.2.0-1 Severity: serious Tags: ftbfs upstream sid X-Debbugs-CC: andr...@fatal.se rust-apple-nvram Depends and Build-Depends: rust-nix 0.26 but Unstable has rust-nix 0.27 instead. I tried doing a simple version bump from 0.26 to 0.27 in the package but dh_auto_test failed. Thank you, Jeremy Bícha
Bug#1070405: darktable: Please drop unused Build-Depends: libsoup2.4-dev
On Mon, May 6, 2024 at 2:46 PM David Bremner wrote: > > Jeremy Bícha writes: > > > Source: darktable > > Version: 4.6.1-2 > > > > Please drop Build-Depends: libsoup2.4-dev . It isn't used at all and > > we would eventually like to remove libsoup2.4 from Debian. > > > > Thank you, > > Jeremy Bícha > > How can I verify that it is not used? rgrep -i soup Also: https://github.com/darktable-org/darktable/commit/228fcf0041773 Thank you, Jeremy Bícha
Bug#1070644: gnome-remote-desktop: System .service file enabled but not the user one?
Control: forwarded -1 https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/merge_requests/260 It looks like upstream is proposing to split gnome-remote-desktop's new systemd systemd service into two system services to fix this issue. It's unclear whether they will land this in 46.x Thank you, Jeremy Bícha
Bug#1070644: gnome-remote-desktop: System .service file enabled but not the user one?
Control: severity -1 serious On Mon, May 6, 2024 at 11:03 AM Laurent Bigonville wrote: > > Package: gnome-remote-desktop > Version: 46.1-3 > Severity: normal > > Hello, > > It seems that the system systemd .service is enabled at boot, while the > user one is not. > > Any reason why the former is enabled and the later is not? > > Not sure I see the rational here That could be a critical bug so I'm bumping the severity. I think the service ought not run unless it is enabled and it shouldn't be enabled by default. (There is GUI in gnome-control-center to enable it but that GUI is patched out for Unstable.) Thank you, Jeremy Bícha
Bug#1070473: debhelper: Run dh_installsysusers after dh_installtmpfiles
On Mon, May 6, 2024 at 7:33 AM Luca Boccassi wrote: > Am I reading this correctly, that the package is using tmpfiles to > create a home directory? I'm not sure that was foreseen as a use case > to be honest, I'd bring it upstream Yes. Should I bring the issue upstream to systemd or upstream to gnome-remote-desktop? Thank you, Jeremy Bícha
Bug#1070473: debhelper: Run dh_installsysusers after dh_installtmpfiles
On Mon, May 6, 2024 at 2:06 AM Niels Thykier wrote: > > Jeremy Bícha: > > Source: debhelper > > Version: 13.15.3 > > Control: affects -1 src:gnome-remote-desktop > > X-Debbugs: syst...@packages.debian.org > > > > gnome-remote-desktop 46 upstream has decided to implement both > > tmpfiles.d and sysusers.d to create a system user and its home > > directory. systemd-tmpfiles needs to run before systemd-sysusers. If > > not, on a new install, this command hangs for about 90 seconds: > > > > Creating user 'gnome-remote-desktop' (GNOME Remote Desktop) with UID > > *** and GID ***. > > > > Then this error: > > Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 148. > > > > Then the installation completes successfully. > > > > Therefore, I recommend that debhelper automatically runs > > dh_installtmpfiles before running dh_installsysusers in case any other > > projects want to do what gnome-remote-desktop does. > > > > I was able to workaround this issue: > > https://salsa.debian.org/gnome-team/gnome-remote-desktop/-/commit/8490919 > > > > Thank you, > > Jeremy Bícha > > > > Hi Michael and Luca > > What is the correct order for tmpfiles vs. sysusers? > > I thought the order was sysusers (to create the user) and then tmpfiles > (to create files/directories and set ownership accordingly). In this bug > report, the request is to have the directories first before the user is > created. > > Could you please assert what the correct order is for the default case? There is a circular dependency here. $ cat /usr/lib/tmpfiles.d/gnome-remote-desktop-tmpfiles.conf # tmpfiles.d file to ensure the existence of the home directory for gnome-remote-desktop user d /var/lib/gnome-remote-desktop 0700 gnome-remote-desktop gnome-remote-desktop d /etc/gnome-remote-desktop 0755 gnome-remote-desktop gnome-remote-desktop $ cat /usr/lib/sysusers.d/gnome-remote-desktop-sysusers.conf # sysusers.d file to ensure the existence of the gnome-remote-desktop user u gnome-remote-desktop - "GNOME Remote Desktop" /var/lib/gnome-remote-desktop The 90 second hang if systemd-sysusers is run before /var/lib/gnome-remote-desktop exists is annoying, but systemd-tmpfiles errors if the gnome-remote-desktop user doesn't exist yet. Running tmpfiles, then sysusers, then tmpfiles again works except for that 90 second hang. I had to remove the gnome-remote-desktop package, then remove the gnome-remote-desktop user and the directories and then reboot to test changes properly. Thank you, Jeremy Bícha
Bug#1070463: gnome-remote-desktop: 46 has failing build tests
Control: severity -1 important Control: unblock 1050237 by -1 On Sun, May 5, 2024 at 1:15 PM Jeremy Bícha wrote: > The build tests were passing with version 45. It is not clear to me > why the tests are failing in Debian Experimental but passing in Ubuntu > 24.04 LTS. I have ignored gnome-remote-desktop's test failures for now in Debian since it is a higher priority to land GNOME Shell 46 in Testing. Maybe there is a missing dependency and getting more things in Unstable would help. Thank you, Jeremy Bícha
Bug#1070473: debhelper: Run dh_installsysusers after dh_installtmpfiles
Source: debhelper Version: 13.15.3 Control: affects -1 src:gnome-remote-desktop X-Debbugs: syst...@packages.debian.org gnome-remote-desktop 46 upstream has decided to implement both tmpfiles.d and sysusers.d to create a system user and its home directory. systemd-tmpfiles needs to run before systemd-sysusers. If not, on a new install, this command hangs for about 90 seconds: Creating user 'gnome-remote-desktop' (GNOME Remote Desktop) with UID *** and GID ***. Then this error: Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 148. Then the installation completes successfully. Therefore, I recommend that debhelper automatically runs dh_installtmpfiles before running dh_installsysusers in case any other projects want to do what gnome-remote-desktop does. I was able to workaround this issue: https://salsa.debian.org/gnome-team/gnome-remote-desktop/-/commit/8490919 Thank you, Jeremy Bícha
Bug#1053866: transition: jpeg-xl
Control: block -1 by 1061627 I was able to build all the reverse dependencies in Ubuntu 24.04 LTS against jpeg-xl from experimental. But jpeg-xl won't be able to migrate to Testing until its autopkgtests are fixed. https://release.debian.org/britney/pseudo-excuses-experimental.html#jpeg-xl See the blocking bug. Thank you, Jeremy Bícha
Bug#1060019: transition: poppler 24.02
Control: retitle -1 transition: poppler 24.02 Control: affects -1 src:poppler Since originally requesting this transition, I have updated the version to 24.02. I believe all reverse dependencies can be binNMU'd for this. Thank you, Jeremy Bícha
Bug#1070119: gnome-remote-desktop: missing gnome-remote-desktop user setup in salsa upcoming 46 version
On Sun, May 5, 2024 at 2:51 PM Jeremy Bícha wrote: > Where did you get gnome-remote-desktop 46.1-1_amd64.deb from? It has > not been successfully built on Debian's buildds yet. Oh, I guess it was mentioned in your bug title: you built it from Salsa. Thank you, Jeremy Bícha
Bug#1070119: gnome-remote-desktop: missing gnome-remote-desktop user setup in salsa upcoming 46 version
Where did you get gnome-remote-desktop 46.1-1_amd64.deb from? It has not been successfully built on Debian's buildds yet. Thank you, Jeremy Bícha
Bug#1070463: gnome-remote-desktop: 46 has failing build tests
Source: gnome-remote-desktop Version: 46.1-1 Severity: serious Tags: ftbfs experimental Control: block 1050237 by -1 X-Debbugs-CC: ma...@ubuntu.com gnome-remote-desktop's build tests are failing. This is blocking the GNOME Shell 46 transition since GNOME Shell & GNOME Remote Desktop should have the same major version, at least while the projects are under heavy development. The build tests were passing with version 45. It is not clear to me why the tests are failing in Debian Experimental but passing in Ubuntu 24.04 LTS. Thank you, Jeremy Bícha
Bug#1070462: transition: evolution-data-server 3.52
Package: release.debian.org User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: evolution-data-ser...@packages.debain.org One of the evolution-data-server libraries had a soname bump. I believe everything should be binNMUable without issue. This tracker is good: https://release.debian.org/transitions/html/auto-evolution-data-server.html On behalf of the Debian GNOME team, Jeremy Bicha
Bug#1070348: pipewire: pipewire-pulse: warningin syslog every second for snap_get_audio_permissions
On Sat, May 4, 2024 at 4:00 AM Dylan Aïssi wrote: > > Hello Sergio and Jeremy, > > Le sam. 4 mai 2024 à 05:48, Michael Welsh Duggan a écrit : > > > > After updating my linux kernel to 6.7.12-1, I keep getting the following > > message in my syslog, once a second: > > > > pipewire-pulse[]: default: snap_get_audio_permissions: kernel lacks > > 'fine grained unix mediation'; snap audio permissions won't be honored. > > > > It seems that snap support in pipewire requires a kernel feature > (fine grained unix mediation) that is not yet enabled in Debian. > > I'm thinking of disabling for now the snap support in Debian since > there is no point in keeping it enabled if it's unusable. But, I will > keep it enabled for Ubuntu. What do you think? That makes sense to me. Thank you, Jeremy Bícha
Bug#1063026: helvum: Upcoming gtk update
Control: severity -1 serious Control: tags -1 + ftbfs Jonas, the Rust GTK crates were uploaded to Unstable today. Could you upload your helvum package from Experimental to Unstable? Thank you, Jeremy Bícha
Bug#1070405: darktable: Please drop unused Build-Depends: libsoup2.4-dev
Source: darktable Version: 4.6.1-2 Please drop Build-Depends: libsoup2.4-dev . It isn't used at all and we would eventually like to remove libsoup2.4 from Debian. Thank you, Jeremy Bícha
Bug#1070404: srain: Please update to 1.7.0
Source: srain Version: 1.7.0 Severity: wishlist Please update srain to 1.7.0. One detail I am interested in is that it switches from libsoup2.4 to libsoup3. https://github.com/SrainApp/srain/releases Thank you, Jeremy Bícha
Bug#1070399: RM: pmix [armel armhf i386] -- RoQA; NBS; no arch-specific reverse dependencies
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: p...@packages.debian.org Control: affects -1 src:pmix Please remove pmix on 32-bit architectures. It is no longer built there and its only reverse dependency, openmpi has already been updated to only use pmix on 64-bit architectures. This will allow several packages to migrate from Unstable to Testing (it is one of the blockers for gst-plugins-bad1.0). Thank you, Jeremy Bícha
Bug#1034878: #1034878 meld gives python traceback if run as root
Control: forwarded -1 https://gitlab.gnome.org/GNOME/meld/-/issues/846 Control: severity -1 minor On Sat, May 4, 2024 at 8:42 AM wrote: > Bug #1034878 - meld gives python traceback if run as root is caused by the > call to Gtk.Settings.get_default() in settings.py at about line 56. In general, GNOME developers and the Debian GNOME team don't want you running apps as root/sudo. We do expect some things to be broken if you try it anyway. However, you can try raising this issue directly with the upstream meld developers who may be willing to apply a fix for the issue. I notice that someone already reported a similar issue today but maybe you can add a comment with your additional research. https://gitlab.gnome.org/GNOME/meld/-/issues/846 Thank you, Jeremy Bícha
Bug#1067169: gnome-control-center: Disable location services?
On Thu, Apr 18, 2024 at 10:33 AM Arnaud Ferraris wrote: > TBH I would prefer it if those services were kept enabled in Debian, as > those are useful to mobile users. Moreover, it seems an alternative to > MLS is being worked on, although I don't know what its current status > is, nor whether it'll be live before MLS goes down. But if it's ready > soon enough (that's a big "if", granted), then g-c-c will likely need a > small patch to switch to it, without user-visible disruption. Thank you for your reply. After further consideration, both Ubuntu 24.04 LTS and Fedora 40 have re-enabled location service settings in gnome-control-center for now. Therefore, I have kept location services enabled in Debian Unstable too. https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3032 Jeremy Bícha
Bug#1070323: RM: gnome-shell-extension-bluetooth-quick-connect -- RoM; unmaintained, obsolete with gnome-shell 45
The new upstream project is https://github.com/Extensions-Valhalla/gnome-bluetooth-quick-connect Thank you, Jeremy Bícha
Bug#1052090: gnome-shell-extension-bluetooth-quick-connect: needs update for GNOME Shell 45
On Sun, Sep 17, 2023 at 9:33 AM Simon McVittie wrote: > I don't intend to put time into this change myself, because I no longer > use this extension (see #1043008), so I'm marking this as serious already > (justification: "in the package maintainer's opinion, makes the package > unsuitable for release"). If anyone else in the GNOME team wants to see > this extension stay available in Debian, now is your chance to take over > the package, at which point the severity of this bug becomes your choice. > > If nobody steps up to maintain it, I will ask for this extension to be > removed when we are ready for the GNOME Shell 45 transition. Simon, I filed the removal bug. I haven't really seen complaints during the 6 months that the extension was removed from Testing. The upstream project was archived. However I noted in the removal bug, that there is a fork: https://github.com/Extensions-Valhalla/gnome-bluetooth-quick-connect But the fork switched to TypeScript which might make it difficult to package for Debian main. Thank you, Jeremy Bícha
Bug#1070323: RM: gnome-shell-extension-bluetooth-quick-connect -- RoM; unmaintained, obsolete with gnome-shell 45
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc:gnome-shell-extension-bluetooth-quick-conn...@packages.debian.org Control: affects -1 src:gnome-shell-extension-bluetooth-quick-connect Please remove gnome-shell-extension-bluetooth-quick-connect from Debian. It is no longer maintained upstream: https://github.com/bjarosze/gnome-bluetooth-quick-connect Its functionality has basically been incorporated into GNOME Shell 45 which we intend to land in Unstable soon after the t64 transition completes. There does happen to be a forked version but it uses TypeScript. I've not looked closely at that version but in my experience, GNOME Typescript packages are difficult to package for Debian main. On behalf of the Debian GNOME Maintainers, Jeremy Bícha
Bug#1068123: Breaks phosh << 0.37.0-2
Control: severity -1 important On Sun, Mar 31, 2024 at 6:03 AM Guido Günther wrote: > gnome-session 46 dropped `--builtin` and `--systemd`. This breaks phosh < > 0.37.0-2. Would be great to have a proper `Breaks: ` relationship > to ease upgrades. I'm lowering the severity since phosh 0.38 landed in Testing today and it would be good for gnome-session to migrate also. But I can do another gnome-session upload soon. What exact gnome-session binary-package do you think we need to add the Breaks: to? I know that Budgie was also affected by the change; that's why budgie-session exists now. Thank you, Jeremy Bícha
Bug#1070269: bluez: Please update to 5.75
Source: bluez Version: 5.73-1 Severity: wishlist bluez 5.75 is available. Please update to it. Perhaps it helps https://bugs.debian.org/1069012 ? Also I submitted several merge requests for the Debian package at https://salsa.debian.org/bluetooth-team/bluez/-/merge_requests Thank you, Jeremy Bícha
Bug#1070250: telepathy-glib: Fails to build with glib 2.80
Source: telepathy-glib Severity: serious Version: 0.24.2-0.3 Tags: ftbfs upstream X-Debbugs-CC: bi...@debian.org Please cherry-pick the glib commit from https://gitlab.freedesktop.org/telepathy/telepathy-glib/-/commits/master to fix the build with glib 2.80 (currently in experimental but will be uploaded to Unstable as soon as the t64 transitions clear out). There is also a commit there to port examples from Python 2 to 3. Thank you, Jeremy Bícha
Bug#1070247: telepathy-glib: Fails to build with glib 2.80
Source: telepathy-glib Severity: serious Version: 0.24.2-0.3 Tags: ftbfs upstream X-Debbugs-CC: bi...@debian.org Please cherry-pick the glib commit from https://gitlab.freedesktop.org/telepathy/telepathy-glib/-/commits/master to fix the build with glib 2.80 (currently in experimental but will be uploaded to Unstable as soon as the t64 transitions clear out). There is also a commit there to port examples from Python 2 to 3. Thank you, Jeremy Bícha
Bug#1019042: [Pkg-rust-maintainers] Bug#1019042: rust-qwertone: FTBFS - dep issue
Control: severity -1 serious This issue is now RC since it's not possible to build qwertone on Unstable now. But I expect qwertone will get an upload to fix this issue within a few days. See https://salsa.debian.org/debian/qwertone/-/merge_requests/1 Thank you, Jeremy Bícha
Bug#1058652: RM: python-boto -- ROM; orphaned upstream, replaced by python-boto3
Control: tags -1 -moreinfo The reverse dependencies have been taken care of now. Thank you, Jeremy Bícha
Bug#1070186: python3-datalad: Don't recommend python3-boto
Package: python3-datalad Version: 0.19.6-2 Severity: serious Debian Policy § 2.2 says that packages in main (like python3-datalad) are not allowed to have Recommends on packages that are not in main (unless it is only a non-default alternative for a package in main). python3-datalad Recommends: python3-boto but python3-boto has been removed from Testing and will likely be removed from Unstable soon. See https://bugs.debian.org/1058652 The replacement is python3-boto3 but the package will likely need changes to upstream code to work with the new version. Thank you, Jeremy Bícha
Bug#1070119: gnome-remote-desktop: missing gnome-remote-desktop user setup in salsa upcoming 46 version
On Tue, Apr 30, 2024 at 11:29 AM Alban Browaeys wrote: > So I did not mean mixinf gnome-shell/gnome-remote-desktop version. My > interest was into connection via RDP to a not unlocked or already > opened remote Gnome Shell. > > As of now I us the "Allow Locked Remote Desktop" extension and gdm3 > autologin on the remote gnome shell user session. > I would like to get rid of these hacks (especially since I have to set > an empty password on my gnome keyring for such a setup). Well you'll also need gnome-control-center built without the "revert the remote desktop changes" patch. Our priority is to get the t64 transitions migrated to Testing, then upload GNOME Shell 46 to Unstable (with Release Team permission). The Debian GNOME team may not have time or interest in maintaining two versions of gnome-control-center for people trying to use Remote Login right now. Thank you, Jeremy Bícha
Bug#1070119: gnome-remote-desktop: missing gnome-remote-desktop user setup in salsa upcoming 46 version
Control: severity -1 important On Tue, Apr 30, 2024 at 9:57 AM Alban Browaeys wrote: > The issue seems to be that the user gnome-remote-desktop is not existing > thus the system wide systemd gnome-remote-desktop.service fails to > start: The gnome-remote-desktop user is new for gnome-remote-desktop 46. The user ought to be created by the package and it seems to work for Ubuntu 24.04 LTS (which uses the same packaging). > I found no issue tracker on the salsa project for gnome-remote-desktop > so opened the issue here. I wouldn't open an upstream bug for this issue yet since we should assume this is a Debian packaging issue until confirmed otherwise. > I believe the bug is import as it prevents opening a new desktop session > (but it still works when connection to an existing session). Yes, I've bumped the severity but what do you mean about connecting to an existing session? It's not intended to run, for instance, gnome-remote-desktop 45 with gnome-shell 46 or with gnome-shell 44 but I guess the package dependencies aren't set quite that strict. Thank you, Jeremy Bícha
Bug#1070094: RM: rust-gtk3-macros -- RoM; unmaintained library
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rust-gtk3-mac...@packages.debian.org Control: affects -1 src:rust-gtk3-macros Please remove rust-gtk3-macros from Debian. It is part of the Rust GTK3 stack that is no longer maintained and is incompatible with the Rust GNOME 46 packages. https://bugs.debian.org/1064375 On behalf of the Debian Rust Maintainers, Jeremy Bícha
Bug#1070093: RM: rust-gdk-sys -- RoM; unmaintained library
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rust-gdk-...@packages.debian.org Control: affects -1 src:rust-gdk-sys Please remove rust-gdk-sy from Debian. It is part of the Rust GTK3 stack that is no longer maintained and is incompatible with the Rust GNOME 46 packages. https://bugs.debian.org/1064375 On behalf of the Debian Rust Maintainers, Jeremy Bícha
Bug#1070091: RM: rust-gdk -- RoM; unmaintained library
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rust-...@packages.debian.org Control: affects -1 src:rust-gdk Please remove rust-gdk from Debian. It is part of the Rust GTK3 stack that is no longer maintained and is incompatible with the Rust GNOME 46 packages. https://bugs.debian.org/1064375 On behalf of the Debian Rust Maintainers, Jeremy Bícha
Bug#1070092: RM: rust-gtk -- RoM; unmaintained library
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rust-...@packages.debian.org Control: affects -1 src:rust-gtk Please remove rust-gtk from Debian. Rust GTK3 is no longer maintained and is incompatible with the Rust GNOME 46 packages. https://bugs.debian.org/1064375 On behalf of the Debian Rust Maintainers, Jeremy Bícha
Bug#1070090: RM: rust-gdkx11- RoM; unmaintained library
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rust-gdk...@packages.debian.org Control: affects -1 src:rust-gdkx11 Please remove rust-gdkx11 from Debian. It is part of the Rust GTK3 stack that is no longer maintained and is incompatible with the Rust GNOME 46 packages. https://bugs.debian.org/1064375 On behalf of the Debian Rust Maintainers, Jeremy Bícha
Bug#1070086: RM: rust-gtk-sys -- RoM; unmaintained library
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove Tags: moreinfo X-Debbugs-Cc: rust-gtk-...@packages.debian.org Control: affects -1 src:rust-gtk-sys Control: block -1 by 1064373 Please remove rust-gtk-sys from Debian. It is part of the Rust GTK3 stack that is no longer maintained and is incompatible with the Rust GNOME 46 packages. https://bugs.debian.org/1064375 On behalf of the Debian Rust Maintainers, Jeremy Bícha
Bug#1070089: RM: rust-gdkx11-sys-- RoM; unmaintained library
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rust-gdkx11-...@packages.debian.org Control: affects -1 src:rust-gdkx11-sys Please remove rust-gdkx11-sys from Debian. It is part of the Rust GTK3 stack that is no longer maintained and is incompatible with the Rust GNOME 46 packages. https://bugs.debian.org/1064375 On behalf of the Debian Rust Maintainers, Jeremy Bícha
Bug#1070088: RM: rust-atk-sys -- RoM; unmaintained library
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rust-atk-...@packages.debian.org Control: affects -1 src:rust-atk-sys Please remove rust-atk-sys from Debian. It is part of the Rust GTK3 stack that is no longer maintained and is incompatible with the Rust GNOME 46 packages. https://bugs.debian.org/1064375 On behalf of the Debian Rust Maintainers, Jeremy Bícha
