Bug#1067831: libaio: the t64 package slipped through and is in testing

Hi, On Fri, 05 Apr 2024, Guillem Jover wrote: > > Would it be problematic to add the same compat symlink in the main > > library package? > > I think so yes, because if the intention is to reverse the SONAME > bump (while adding the t64 symlinks also on the reintroduced libaio1 > package), then

Bug#1067831: libaio: the t64 package slipped through and is in testing

Hi Guillem, On mer., 27 mars 2024, Guillem Jover wrote: > A binNMU would fix that, but given that no one has apparently asked > for that yet, I think instead I'll just add (later today) a compat > symlink only for the udeb for the old SONAME, because the new SONAME is > ABI compatible, but done

Bug#1067490: tracker.debian.org: Display release-team blocks more prominently

Hi, top-posting and leaving quite some context because the main point of my message is to actually share your bug report to the release team. If I remember correctly, tracker.debian.org is not doing any fancy treatment. We are just turning some YAML into HTML:

Bug#1036214: Tracking gets confused by using copysrc on binnmu'ed packages

Hello, On Wed, 17 May 2023, Christoph Berg wrote: > Ever since, I've seen warnings from reprepro that the tracking > database was missing references when copysrc'ing a new version into a > distribution when the previous version in there had been binnmued. But > since everything worked as

Bug#1060270: /lib/cryptsetup/askpass: coordinated move to /usr for DEP17

Hello, On Tue, 23 Jan 2024, Guilhem Moulin wrote: > On Tue, 23 Jan 2024 at 10:15:02 +0100, Raphael Hertzog wrote: > > when do you plan to upload a cryptsetup moving the files to /usr? > > I can have a look after the week-end or in early February. There are > other issu

Bug#1063878: di-utils: chroot-setup.sh creates ineffective diversions (DEP17)

On Wed, 14 Feb 2024, Raphael Hertzog wrote: > i.e. is the the file-loss triggered only by the bad path in the > dpkg-divert call or is it triggered by the upgrade of dpkg between > both dpkg-divert calls? > > I thought it was the latter... and that would explain why OpenQA is

Bug#1063878: di-utils: chroot-setup.sh creates ineffective diversions (DEP17)

(Adding Colin as one of the debian-installer-utils comaintainers) Hi, On Tue, 13 Feb 2024, Helmut Grohne wrote: > I also see that https://openqa.debian.net/ has recent successes. dpkg > migrated to trixie about two weeks ago. I would have expected that this > breaks an d-i. Do you have an

Bug#1060270: /lib/cryptsetup/askpass: coordinated move to /usr for DEP17

Hello Jonas & Guilhem, when do you plan to upload a cryptsetup moving the files to /usr? Jonas, you should also update cryptsetup-nuke-password at the same time (cf #1060269). I can help if needed. Looking forward to see those two bugs fixed. -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋

Bug#1060897: Bug #1060897: furo: documentation generated with Debian's furo package doesn't work standalone

Control: reopen -1 On Fri, 19 Jan 2024, Debian Bug Tracking System wrote: > furo (2023.09.10+dfsg-3) unstable; urgency=medium > . >* included the code from normalize.css into furo.css instead of > the include directive. Closes: #1060897 Thanks for this fix! Unfortunately, this only

Bug#1060897: standalone is permitted, when the local web server is in use

Hi, On Thu, 18 Jan 2024, Georges Khaznadar wrote: > On Thu, 18 Jan 2024 13:55:20 +0100 Raphael Hertzog wrote: > > [...] reported here and that you can see here: > > https://hertzog.pages.debian.net/-/debusine/-/jobs/5153568/artifacts/docs/_build/html/index.html > > w

Bug#1060897: standalone is permitted, when the local web server is in use

Hi Georges, On Thu, 18 Jan 2024, Georges Khaznadar wrote: > Would you like to enable documents generated with furo to be usable even > when accessed under a file:// scheme? Yes, but I'd also like them to work when hosted on a random non-Debian webserver. My use case is documentation generated

Bug#1060897: furo: documentation generated with Debian's furo package doesn't work standalone

On Tue, 16 Jan 2024, Raphaël Hertzog wrote: > - the dark/light theme switcher is hidden because I have a ".no-js" class > that is not removed by _static/scripts/furo.js because that script fails > on the first import line (Uncaught SyntaxError: import declarations may > only appear at top

Bug#1060192: tracker.debian.org: SSL connection extremely slow and sometimes timing out

On Sun, 07 Jan 2024, Helge Kreutzmann wrote: > Package: tracker.debian.org > Severity: important > > Yesterday and today connections to packages.debian.org is *extremely* packages.debian.org is entirely unrelated to tracker.debian.org. It's managed by the web team AFAIK. That said if the issue

Bug#1042989: ITP: Incus -- Powerful system container and virtual machine manager

Hello, On Tue, 26 Dec 2023, Mathias Gibbens wrote: > On Mon, 2023-12-25 at 12:52 +0100, Raphael Hertzog wrote: > > I would really like to see incus in unstable/testing and even in > > bookworm-backports at some point. > > Given the large number of new/updated dependencies

Bug#1042989: ITP: Incus -- Powerful system container and virtual machine manager

Hello, On Sat, 21 Oct 2023, Free Ekanayaka wrote: > raft 0.17.7-1 is now in unstable, and I've uploaded cowsql 1.15.3-1, > which is waiting in the NEW queue. This one is available in unstable now. I would really like to see incus in unstable/testing and even in bookworm-backports at some point.

Bug#1054220: Off-by-one when selecting days in activity window

forwarded -1 https://github.com/projecthamster/hamster/issues/590 On Thu, 19 Oct 2023, Lee Garrett wrote: > steps to reproduce: > > - click on the + icon ("add activity") in the main window > - on the start time, clik on the arrow next to the date > - (a calendar pops up) > - click on e.g.

Bug#1053488: ITP: django-jsonfield -- Reusable JSONField for Django Models

Hello Edward, On Thu, 05 Oct 2023, Edward Betts wrote: > jsonfield is a reusable model field that allows you to store validated JSON, > automatically handling serialization to and from the database. It is > particularly useful when your app needs to be database-agnostic or when the >

Bug#839403: apt: define default pin priority for a source in sources.list directly

Hello, On Sat, 01 Oct 2016, Raphaël Hertzog wrote: > Hello I would like to be able to use something like this in my > sources.list: > > deb [pin-priority=500] http://ftp.debian.org/debian experimental main Today I stumbled upon another case where something like this would have been useful, to

Bug#1053462: debian-security-support: merge .ended and .limited files together

On Wed, 04 Oct 2023, Santiago Ruano Rincón wrote: > > We could have a single file per release with 3 fields: > > > > * package (or package regexp) > > * supported (true/false), trues implies limited support, false means not > > supported > > * comment (should explain the limitation if supported

Bug#975301: split security-support-limited into release specific files

Hi, On Tue, 26 Sep 2023, Santiago Ruano Rincón wrote: > > > Agreed, a split makes sense, it causes marginal additional overhead and > > > makes > > > the whole setup more explicit. > > > > cloning this bug once more so we don't forget about this. > > (I think the moreinfo tag comes from the

Bug#1051785: gdm3 won't allow logins when a smarcard with a x.509 credential is plugged in

Hello, On Tue, 12 Sep 2023, Paul Tagliamonte wrote: > I upgraded my sid system, and post-upgrade gdm3 isn't showing my face > when I reboot, and entering my username causes it to loop back to > username entry again (no password prompt). After some help from smcv, I > narrowed down the issue to

Bug#1041708: apt: Manpages have wrong advice on APT::Default-Release preventing security updates

Hi, Le samedi 19 août 2023, David Kalnischkies a écrit : > > Agreed. It would be nice to document that we can use regex here and > > that it actually makes sense to do so as most Debian release are actually > > composed of multiple repositories. > > The problem is that regex is NOT supported at

Bug#1041708: apt: Manpages have wrong advice on APT::Default-Release preventing security updates

Hello, Le samedi 22 juillet 2023, Daniel Gröber a écrit : > > (eventually an update/security fix will be part of stable via a point > > release, so such a setting considerably delays the updates, but doesn't > > prevent them as such. While I wouldn't recommended it, there might be > > people

Bug#1040757: dose: (W)CudfAdd: package ncurses-base:amd64 (= 6.4-4) is not associate with an integer in the given universe

Hello Ralf, Le samedi 15 juillet 2023, Ralf Treinen a écrit : > In fact it is not related to dose-distcheck being outdated on quantz, I > get the same error with dose-distcheck on sid. > > Since I do not have time to dig further into this atm (leaving for vacation) > I have now desactivated the

Bug#1041523: tracker.debian.org: displays autopkgtest for other src:package on same page

Hello, On Thu, 20 Jul 2023, Martin-Éric Racine wrote: > The tracker at shows autopkgtest > results for both this src:package and for another src:package. I see no autopkgtest results at all. They are only shown when something fails... and in that case, it

Bug#1026408: cryptsetup-nuke-password: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

Hello Paulo, thank you for your NMU. I imported the NMU in Git. In the future, it would be best if you could submit a merge request straight away instead of sharing a debdiff (or even commit directly your changes). Cheers, On Mon, 19 Jun 2023, Paulo Henrique de Lima Santana wrote: > Hi, > > I

Bug#1038121: tracker.debian.org: debian/patches check vs. single-debian-patch in debian/source/local-options

Hello, On Thu, 15 Jun 2023, Thorsten Glaser wrote: > Unsure if this is the right pseudopackage; if not, please reassign. > > The “new” Debian tracker shows: > > debian/patches: 1 patch to forward upstream > > The package however uses the single-debian-patch mechanism > to let a diff be

Bug#1036661: hamster-time-tracker: missing dependency on python3-gi-cairo

Control: tag -1 + pending On Wed, 24 May 2023, Gerald Jansen wrote: > see https://github.com/projecthamster/hamster/issues/722 Thanks for the report. I committed a fix in the repository. Now waiting for the next upstream release that shouldn't be too far in the future from what I saw in recent

Bug#1035972: isc-dhcp EOL'ed

Hello Santiago, On Thu, 11 May 2023, Santiago Ruano Rincón wrote: > ISC is not longer maintaing any of the components of isc-dhcp (client, > relay or server): > https://lists.isc.org/pipermail/dhcp-users/2022-October/022786.html > https://www.isc.org/blogs/isc-dhcp-eol/ > > I propose to mark it

Bug#1034875: kitty: Should not handle application/x-sh mime type by executing the script

Package: kitty Version: 0.26.5-4 Severity: serious Tags: security X-Debbugs-Cc: Debian Security Team Hello, I was reading https://lists.debian.org/20230425190728.ga1471...@subdivi.de in mutt and that mail contains 3 shell scripts as attachments (application/x-sh). I wanted to have a look at the

Bug#1028615: tracker.debian.org: tracker.d.o should display results of reproducible rebuilds, not just reproducible CI results

Hello Holger, On Fri, 14 Apr 2023, Holger Levsen wrote: > On Fri, Jan 13, 2023 at 06:49:48PM +0100, Holger Levsen wrote: > > since some years, tracker.d.o is thankfully showing results from > > https://tests.reproducible-builds.org/debian - which was and is awesome! > > However, these are just

Bug#1031780: tracker.debian.org: add information about patches

Hi Guillem & Holger, On Sun, 26 Feb 2023, Guillem Jover wrote: > The links for diaspora do not seem to be working though, as at least > the «+» in the version string is not getting encoded, and UDD gives: Duh, I forgot to urlencode the parameters, fixed. (That thought actually popped up in my

Bug#1031780: tracker.debian.org: add information about patches

Hello Paul, On Mon, 27 Feb 2023, Paul Wise wrote: > On Sun, 2023-02-26 at 17:02 +0100, Raphael Hertzog wrote: > > > I added the required support in tracker.debian.org > > Personally I think we should replace the Ubuntu panel with a patches > panel, as I have done for the o

Bug#1031780: tracker.debian.org: add information about patches

Hi, On Wed, 22 Feb 2023, Lucas Nussbaum wrote: > UDD now includes data about patches (see > https://lists.debian.org/debian-qa/2023/01/msg2.html ). This data is > already exposed on https://udd.debian.org/patches.cgi and > https://udd.debian.org/dmd/ (see the Patches column in >

Bug#1030734: link to upstream bug tracker and repository

Hi, On Sat, 25 Feb 2023, Jelmer Vernooij wrote: > > FWIW, I don't plan to work on this (at least not in the short term) but > > I'll happily review MR and answer questions. > > I might spend some time on this, but would appreciate any further hints > on where to add this if the information is

Bug#1031393: tracker.debian.org: .dsc links to debian/pool/updates broken

Control: forcemerge 850409 -1 Hello, On Thu, 16 Feb 2023, Holger Levsen wrote: > the links to the .dsc files for (at least) stable-sec and stable-p-u > on https://tracker.debian.org/pkg/spip are 404 > yeah those paths are broken > debian/pool/updates isn't a thing > either

Bug#1030734: link to upstream bug tracker and repository

Hello, On Mon, 06 Feb 2023, Jelmer Vernooij wrote: > A large number of Debian packages now has upstream metadata, including links > to > upstream repositories (Repository-Browse) and bugtrackers (Bug-Database / > Bug-Submit). Would it be possible to link to those from tracker? It's of course

Bug#1028310: hamster-time-tracker: please make the build reproducible

Control: tag -1 + pending Hi, On Mon, 09 Jan 2023, Chris Lamb wrote: > Whilst working on the Reproducible Builds effort [0] we noticed that > hamster-time-tracker could not be built reproducibly. > > This is because it varied depending on whether it was built with a > 32- or 64-bit kernel. This

Bug#1030748: tracker.debian.org doesn't display the correct linux kernel rc upstream version

Hello, On Tue, 07 Feb 2023, xevilstar wrote: > I have noticed that on https://tracker.debian.org/pkg/linux the new > upstream version takes ages to update. How long is "ages" for you? > for example now it displays "A > new upstream version is available: 6.2~rc6" while on >

Bug#1002819: autopkgtest: --pin-packages assumes that the release has a "Suite" name

(Adding Colin Watson as he might have feedback on Ubuntu's uses of the various Release fields and on the likeliness to fix/change them) Hello, On Wed, 01 Feb 2023, Paul Gevers wrote: > > I fear I've probably forgotten most of these details, so please pardon > > me for this response… Wasn't the

Bug#893083: hello: Packaging should be hosted on salsa.debian.org

On Mon, 26 Dec 2022, Santiago Vila wrote: > So, suppose that someone has a package requiring the above for "gbp > buildpackage" to work. > Does the package have a disclaimer somewhere saying "plain dpkg-buildpackage > is not supported > here" or something alike? You can document any discrepancy

Bug#893083: hello: Packaging should be hosted on salsa.debian.org

Hello, On Fri, 23 Dec 2022, Santiago Vila wrote: > For example, this one: > > I have just imported version 2.10-2. Now dpkg-buildpackage > does not work because it expects some timestamps to be the ones in the > orig.tar.gz where upstream maintainer already ran autoconf and friends. > > I know

Bug#1026802: python3.10: Should be built with --with-ssl-default-suites=openssl

Package: python3.10 Version: 3.10.9-1 Severity: wishlist User: de...@kali.org Usertags: origin-kali X-Debbugs-Cc: de...@kali.org Hello Mathias (and other Python maintainers), it would be nice if python3.10 (and future versions) could be built with --with-ssl-default-suites=openssl. Starting

Bug#1021728: tracker.debian.org: Please include the new "non-free-firmware" section

Hello Gunnar, On Thu, 13 Oct 2022, Gunnar Wolf wrote: > Last week I uploaded raspi-firmware to non-free-firmware (and was > promptly processed through NEW, whee!). > > Two days ago, it successfully migrated to Texting. > > I am now building the Raspberry Pi images for Bookworm , and >

Bug#1020056:

Hello, Le jeudi 13 octobre 2022, Thomas Braun a écrit : > so I think it should be as easy as adding cppzmq-dev to the build > dependencies. > > $diff -Nur control control.new > --- control 2022-10-13 16:19:07.384578078 +0200 > +++ control.new 2022-10-13 16:19:03.972578004 +0200 > @@ -7,6

Bug#1010660: Got the error in Kali too

Hello, we have been bitten by this in Kali too. In our case Arnaud Rebillout worked around it by adding a hint. Here's what he said: The issue was a circular dependency between `libnginx-mod-http-lua/1:0.10.22-2` and `lua-resty-core/0.1.24-2`. It was solved with the following hints: #

Bug#1018288: waagent: Debian specific patch breaks kali support

Hello, Le lundi 29 août 2022, Bastian Blank a écrit : > On Sun, Aug 28, 2022 at 12:38:21PM +0200, Raphaël Hertzog wrote: > > Please re-add the import statement. There's a merge request lying around > > since one year: > > https://salsa.debian.org/cloud-team/waagent/-/merge_requests/3 > > This

Bug#1012563: wireplumber: right click broken in firefox 100.0.2-1

Hello Dylan, On Tue, 13 Sep 2022, Dylan Aïssi wrote: > Do you have a special audio configuration? No. > > So somehow, wireplumber + pipewire-pulse is not properly > > detected as something that can be controlled with the "pulse-rust" audio > > backend when it likely should be that way... > >

Bug#1019259: devscripts: The command uscan with the option 'dehs' doesn't always generate valid XML ouput

Control: tags -1 - moreinfo Hello Yadd, Please keep the bug submitter on copy, otherwise you can't expect to get replies. Le mardi 06 septembre 2022, Yadd a écrit : > uscan generates a valid XML on STDOUT and displays messages on STDERR. Use > `uscan --dehs 2>/dev/null` That was my expectation

Bug#1018878: live-build: dealing with firmware files provided by multiple packages

Package: live-build Version: 1:20220505 Severity: normal User: de...@kali.org Usertags: origin-kali Looking closely at the issue that I reported in #1018873, I realize that the Contents file have those entries: lib/firmware/nvidia/470.141.03/gsp.bin

Bug#1018873: live-build --firmware-chroot option is broken due to nvidia-tesla{-470,}-kernel-support

Package: nvidia-tesla-kernel-support Version: 510.85.02-1 Severity: important User: de...@kali.org Usertags: origin-kali X-Debbugs-Cc: raph...@offensive-security.com, Andreas Beckmann , sop...@offensive-security.com Control: affects -1 live-build Hello, if you run live-build with non-free

Bug#1018288: waagent: Debian specific patch breaks kali support

Hello Bastian, On Mon, 29 Aug 2022, Bastian Blank wrote: > On Sun, Aug 28, 2022 at 12:38:21PM +0200, Raphaël Hertzog wrote: > > Please re-add the import statement. There's a merge request lying around > > since one year: > > https://salsa.debian.org/cloud-team/waagent/-/merge_requests/3 > > This

Bug#601203: Released fix in git

Control: tags -1 + pending Hello, I fixed this issue in git now: https://salsa.debian.org/images-team/debian-cd/-/commit/8513b237afbdb59a4a59d1bc707d37f0aa9138f7 This was on top of a first cleanup where I turned $add_rec and $add_sug into global variables:

Bug#1016090: python-django breaks lots of autopkgtests

Hi, On Mon, 01 Aug 2022, Chris Lamb wrote: > Regardless of that though, I think we have two options: > > a) Revert back to the 3.2.14 LTS version in Debian unstable. > > b) Wait for the 4.x stream to become designated LTS. I believe this >should happen with version 4.2, due for release in

Bug#1016090: python-django breaks lots of autopkgtests

On Tue, 26 Jul 2022, Paul Gevers wrote: > Source: python-django > Control: found -1 python-django/2:4.0.6-1 I'm surprised that we uploaded an non-LTS release to unstable. Chris, why did you do that? > I note that the changelog has this: > "This security release mitigates the issue, but we have

Bug#1013493: python-django-jsonfield: FTBFS: ImportError: cannot import name 'ugettext_lazy' from 'django.utils.translation' (/usr/lib/python3/dist-packages/django/utils/translation/__init__.py)

Hello, On Fri, 24 Jun 2022, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. Thanks but I will not fix this bug. Intsead I have asked to remove this package from unstable since it has been superseded by a native field provided by Django:

Bug#1015174: lvm2-udeb: uninstallable, depends on non-udeb libsystemd0

Control: tags -1 + patch Control: user de...@kali.org Control: usertags -1 + kali-patch On Sun, 17 Jul 2022 05:50:20 +0200 Cyril Brulebois wrote: > I suppose the journal bits could be patched out for the udeb build (right > now, configure ends up defining SYSTEMD_JOURNAL_SUPPORT to 1 there), but

Bug#1014837: distro-info-data: update ELTS data

Hi, On Tue, 12 Jul 2022, Thorsten Glaser wrote: > 10 Busterbuster2017-06-17 2019-07-06 2022-08-14 > 2024-06-30 2026-06-30 > 11 Bullseye bullseye 2019-07-06 2021-08-14 2024-08-14 > > However, ELTS support got prolonged: see >

Bug#1014376: openvpn: Using unreleased version with backwards incompatible changes is not a good idea

On Wed, 06 Jul 2022, Bernhard Schmidt wrote: > > As such I really believe that this git snapshot should have stayed in > > experimental. Why was it uploaded to unstable before its upstream > > release? > > I respectfully disagree. This is what unstable/testing is for. 2.6 is to be > released

Bug#997818: [Pkg-utopia-maintainers] Bug#997818: wireplumber: Failed to preset unit, file /etc/systemd/user/pipewire-session-manager.service already exists

Hi, On Sat, 30 Oct 2021 01:37:53 +0200 Michael Biebl wrote: > > Am 30.10.2021 um 01:21 schrieb Laurent Bigonville: > > That also looks RC to me, leaving a dangling symlink is never good, not > > too sure how to fix this. > > This preserves the enablement state of the service, similar to how

Bug#1011063: scp: Received message too long 1163022927

On Mon, 16 May 2022 07:44:26 -0400 Stefano Rivera wrote: > Now that openssh 1:9.0p1-1 uses the SFTP protocol by default, uploads to > services using scp are broken. Note that not all uploads are broken. They are broken when the server side has a forced command that is expecting scp usage. I have

Bug#815189: sftp uploader uses wrong user name ordering

Control: tags -1 + patch Hello, On Fri, 19 Feb 2016 21:55:21 +0100 Michael Kuhn wrote: > When using the sftp uploader, the user name from the SSH configuration > is always preferred, that is, the order is currently: login name, dput > profile, SSH configuration. This is backwards because one

Bug#1008773: ftpsync: Using commands with parameters as hooks breaks ftpsync on bullseye/debian 11

Control: tags -1 + patch I have prepared a merge request with a fix for this issue: https://salsa.debian.org/mirror-team/archvsync/-/merge_requests/4 (Note that there's another outstanding merge request there that you might want to merge too) I'm attaching the patch as well. -- ⢀⣴⠾⠻⢶⣦⠀

Bug#1008772: xrdp: Please integrate NMUs and gitlab MR

Source: xrdp Version: 0.9.17-2 Severity: wishlist Tags: patch User: de...@kali.org Usertags: origin-kali Hello, I have just uploaded an NMU prepared by a Kali contributor (in the NM queue). Please find the relevant "git am" patches attached. (The two patches by Arnaud are also in

Bug#1004256: messages to dispatch+aide_cont...@tracker.debian.org get multiplied

Hi, On Sun, 23 Jan 2022, Marc Haber wrote: > I regularly use pack...@packages.debian.org as Maintainer address for my > packages. Having an implicit mailing list for package maintenance issues > is extremele helpful and I appreciate that features. > > Since a few weeks, messages to those

Bug#1003478: python-django: cannot import name 'RequestSite' from partially initialized module 'django.contrib.sites.requests' (most likely due to a circular import)

On Thu, 13 Jan 2022, Chris Lamb wrote: > This should be fixed in bullseye-backports in 2:3.2.10-2~bpo11+2 and > in bullseye itself via 2:2.2.26-1~deb11u1 (see #1003659 for the unblock > request). Thank you Chris! -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋The Debian Handbook:

Bug#992536: libasound2-udeb: missing /usr/share/alsa/ctl

Hi alsa maintainers, having this bug unfixed in unstable/testing for so long is a bit of a pity. Can you consider uploading a fixed version please? If not, do you want an NMU? Thank you in advance. Le jeudi 19 août 2021, Samuel Thibault a écrit : > Source: alsa-lib > Version: 1.2.5.1-1 >

Bug#1002819: autopkgtest: --pin-packages assumes that the release has a "Suite" name

Hi, On Fri, 31 Dec 2021, Paul Gevers wrote: > > Otherwise I would like to suggest to create two entries, one with > > "Pin: release a=foo" and one with "Pin: release n=foo" so that > > we are sure to match on any of the 3 fields. > > I'll have to check and think about this. I remember that I had

Bug#1002819: autopkgtest: --pin-packages assumes that the release has a "Suite" name

Control: tags -1 + patch Control: user de...@kali.org Control: usertag -1 + kali-patch On Wed, 29 Dec 2021, Raphaël Hertzog wrote: > I noticed that /etc/apt/preferences.d/autopkgtest-default-release uses > another syntax that seems to cover more cases: > > Package: * > Pin: release kali-rolling

Bug#1002458: "version in VCS newer than in repository" might be a bit overzealous

On Mon, 27 Dec 2021, Christoph Berg wrote: > Re: Raphael Hertzog > > Christoph, would it be possible to export a supplementary flag showing > > when the changes in NEW or COMMITS contain only changes to > > debian/changelog? > > The proper first step is to change

Bug#1002462: "build log checks report 1 warning" dated a year and 9 uploads ago

Hi, On Wed, 22 Dec 2021, Marc Haber wrote: > for sudo, on https://tracker.debian.org/pkg/sudo, I see an "action > needed" Build log checks report 1 warning". This warning is shown as > having been created on 2020-12-21, while the link points to build logs > from last week. Is this intended? Yes,

Bug#1002461: actions needed should show affected version

Hi, On Wed, 22 Dec 2021, Marc Haber wrote: > in sudo's tracker page, I see that lintian reports 29 errors and 5 > warnings. The link leads me to https://lintian.debian.org/sources/sudo > which tells me that the linan reports are from vresion 1.9.6-1~exp2 and > the lintian run was a month ago. >

Bug#1002458: "version in VCS newer than in repository" might be a bit overzealous

Hi, On Wed, 22 Dec 2021, Marc Haber wrote: > when I upload a package (for example, foo 1.0-1), I immediately create a > new changelog stanza for a new version foo 1.0.2~1 so that noone > accidentally makes a commit that might end up in the changelog for the > already-uploaded version 1.0-1. > >

Bug#1001190: tracker.debian.org: news: emails: show Message-ID header, link to lists.d.o/msgid-search

Hi, On Tue, 07 Dec 2021, Paul Wise wrote: > Not necessarily, there are several options for this that would make it > a very generic feature, some ideas: > > When the List-Archive header exists and contains a URL, the link could > be to that URL. This works for Debian lists and mailman lists and

Bug#1001190: tracker.debian.org: news: emails: show Message-ID header, link to lists.d.o/msgid-search

Hi, On Mon, 06 Dec 2021, Paul Wise wrote: > In the news emails, please show the Message-ID header and make the > value inside the angled brackets <> a link to the Debian lists > msgid-search. For example [1] should link to [2]. > >    1. >

Bug#998319: tryton-server: Should provide a ready-to-use production-grade server config

Hi, On Tue, 02 Nov 2021, Mathias Behrle wrote: > A robust production grade setup will run the Tryton server not only behind a > reverse proxy, but inside a wsgi server. > > My prefered concept for the solution would be two additional packages: > > tryton-server-uwsgi > tryton-server-nginx > >

Bug#994275: Reverting breaking changes in debianutils

On Mon, 01 Nov 2021, Sean Whitton wrote: > Of course we should be exploring the new avenues that you mention. But > becoming more willing to break unstable/testing than we are at present > might also be good for our project. Maybe, maybe not. What are you basing your assertion on? From my

Bug#994275: Reverting breaking changes in debianutils

On Sun, 24 Oct 2021, Clint Adams wrote: > > In any case, a message saying that which is deprecated when in fact > > `which` will stay around (but maintained in another packages) is not > > helpful. > > Tell me, what would be helpful? A coordinated take over of the binary with a proper transition

Bug#993678: Fails to produce PDF output when using scale.by.width - produces broken lstlisting/lstcode options

Control: tags -1 + patch Le samedi 04 septembre 2021, Daniel Leidert a écrit : > While building a PDF we stumbled upon an issue. Some of our XML files contain > screen elements with non UTF-8 characters. When we enable scaling for listing > elements: > > scale.by.width > > dblatex fails. The

Bug#997522: logidee-tools: FTBFS: make[2]: kpsepath: No such file or directory

Control: tag -1 + wontfix On Sat, 23 Oct 2021, Lucas Nussbaum wrote: > Source: logidee-tools > Version: 1.2.19 > > During a rebuild of all packages in sid, your package failed to build > on amd64. Note that I requested removal of this package so I will not handle this bug. See

Bug#994040: "SystemError: initialization of _psycopg raised unreported exception" when running under WSGI

Hello, Le dimanche 03 octobre 2021, Sébastien Helleu a écrit : > In my case, setting "WSGIApplicationGroup" to "%{GLOBAL}" doesn't help much. > > But I found another solution, by enabling Daemon mode, as recommended by the > Django docs: >

Bug#993678: Fails to produce PDF output when using scale.by.width - produces broken lstlisting/lstcode options

Control: forwarded -1 https://sourceforge.net/p/dblatex/bugs/129/ Hello, I have forwarded this bug to the upstream bug tracker and I pinged the upstream author by email to try to draw his attention to this issue. Cheers, -- Raphaël Hertzog

Bug#995445: logidee-tools: creates incorrect TeX code, breaks other packages via autopkgtests

Hello, On Fri, 01 Oct 2021, Norbert Preining wrote: > The failed autopkgtest can be boiled down to the following example (all > the code is as taken from the logidee-tools generated code): Sorry that logidee-tools created issues for you. For the record, I have just requested the removal of that

Bug#994275: Draft resolution for reverting changes in debianutils

Hi, On Wed, 13 Oct 2021, David Bremner wrote: > >The which(1) program must not print any deprecation warnings. > > I remain to be convinced on this point. If I understand the issue > correctly the problem is with autopkgtests failing because they were not > expecting output on stderr. I

Bug#993204: Bug#996079: gnome-shell-timer: does not declare compatibility with GNOME Shell 41

Control: forcemerge 993204 996079 Le dimanche 10 octobre 2021, Simon McVittie a écrit : > Package: gnome-shell-timer > > The metadata.json for this extension doesn't declare compatibility with > GNOME 41. I don't know whether the actual code will need changes or not: > the conservative

Bug#993578: 90gpg-agent generator: `gpgconf --check-programs` can hang

Control: severity -1 serious Control: tags -1 + patch Hello, I have been bitten by this bug for multiple months without having a clue of what was going on... when I resumed my laptop without wifi, the GNOME session would be blocked for a minute or so. With the patch in

Bug#994808: upgrade issue

Hi, On Wed, 22 Sep 2021, Andreas B. Mundt wrote: > If I don't hear back from you, I'll upload the package with the fix > later today in the early evening. Thanks for the quick upload! > Concerning the autopkgtests: Can you point me to a package that > implements a test to detect these kind of

Bug#994808: upgrade issue

Hello, Le mardi 21 septembre 2021, Andreas B. Mundt a écrit : > I have to investigate further, but does it really work for you? Thanks for testing. Unfortunately, our testing was not sufficient indeed. We tested in a chroot (thus without systemd) and the code path is really different there: the

Bug#992243: buster-pu: package psmisc/23.2-1+deb10u1

Hello, On Sat, 04 Sep 2021, Adam D. Barratt wrote: > On Mon, 2021-08-16 at 12:02 +0200, Raphael Hertzog wrote: > > I would like to update "psmisc" in buster to fix a regression in > > "killall". The bug https://bugs.debian.org/912748 was never fixed in > >

Bug#993204: gnome-shell-timer: does not declare compatibility with GNOME Shell 40

Control: severity -1 serious Hi, On Sat, 28 Aug 2021, Simon McVittie wrote: > When we do the GNOME 40 transition, hopefully soon, we will have to > either update this extension or remove it from testing. It would be > useful to get a fixed version into experimental. This extension is

Bug#993141: simple-cdd: default.downloads is missing packages used by debian-installer

Package: simple-cdd Version: 0.6.8 Severity: important User: de...@kali.org Usertags: origin-kali X-Debbugs-Cc: raph...@offensive-security.com, debian...@lists.debian.org While diagnosing a failure to boot an encryted install, I discovered that simple-cdd was not properly adding

Bug#992966: simple-cdd: fails to validate Release file with a good signature and a signature that can't be checked

Control: severity -1 important Bumping the severity on suggestion of #debian-release. On Wed, 25 Aug 2021, Raphaël Hertzog wrote: > Right now if you try to use simple-cdd on a stretch or buster system (to > build stretch/buster images), you get failures like this one: I was a bit to quick in my

Bug#992243: buster-pu: package psmisc/23.2-1+deb10u1

Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: raph...@freexian.com csm...@debian.org Hello, I would like to update "psmisc" in buster to fix a regression in "killall". The bug https://bugs.debian.org/912748 was

Bug#991166: ftpsync: Contents* and dep11/* metadata are incorrectly updated in stage1

Control: tags -1 + patch I have prepared a MR for this: https://salsa.debian.org/mirror-team/archvsync/-/merge_requests/2 Changes are trivial but they are currently untested. Cheers, -- Raphaël Hertzog ◈ Offensive Security ◈ Kali Linux Developer

Bug#990426: www.debian.org: Clarify status of list of old TC decisions

Hi, On Mon, 28 Jun 2021, Sean Whitton wrote: > -NB that decisions from before the 1st of April 2002 are not yet > -recorded here. > +NB that no decisions from before the 1st of April 2002 are yet recorded > +here yet. That wording doesn't seem correct for me. Maybe: « Note that no decisions from

Bug#888831: NS_ERROR_NET_INADEQUATE_SECURITY error on armhf/arm64 at least

Control: severity -1 serious Control: found -1 firefox-esr/78.11.0esr-1 Control: tag -1 + bullseye Hello, it looks like this issue resurfaced again and it happens in bullseye right now (with firefox-esr 78.11.0esr-1 and libnss3 2:3.61-1). If you upgrade to the version of libnss3 in unstable

Bug#988658: RFP: python3-pyupgrade -- Automatically upgrade syntax for newer versions of the Python language

Package: wnpp Severity: wishlist X-Debbugs-Cc: debian-pyt...@lists.debian.org * Package name: python3-pyupgrade Version : 2.16.0 Upstream Author : Anthony Sottile * URL : https://github.com/asottile/pyupgrade * License : BSD Programming Lang: Python

Bug#962290: smuxi-frontend-gnome: freezes when I click on the channel with a recent notification

Control: tags -1 - moreinfo unreproducible Hello, Le mercredi 10 février 2021, Raphael Hertzog a écrit : > > Can you please open a terminal and run Smuxi in debug mode like this: > > smuxi-frontend-gnome -d > > I'll try to get you this soon. Finally I reproduced the issu

Bug#960154: Feed UDD with just-in-time packaging hints from Lintian

Hi, On Wed, 14 Apr 2021, Lucas Nussbaum wrote: > I think that in Debian, we would aim for a better separation between: > > A/ QA tools development, focused on getting the good tools to analyze > packages (output: tools, as Debian packages) > > B/ infrastructure that mass-process the archive

Bug#962290: smuxi-frontend-gnome: freezes when I click on the channel with a recent notification

On Fri, 26 Feb 2021 10:10:19 +0100 Raphael Hertzog wrote: > On Thu, 11 Feb 2021, Mirco Bauer wrote: > > Can you please open a terminal and run Smuxi in debug mode like this: > > smuxi-frontend-gnome -d > > I did that for multiple days but it looks like the issue is go

  1   2   3   4   5   6   7   8   9   10   >