Bug#1035780: jed-common: Fails to upgrade: unable to install new version of '/usr/share/jed/doc/txt/abbrev.txt': No such file or directory
Package: jed-common Version: 1:0.99.20~pre.178+dfsg-2 Severity: serious jed-common fails to upgrade from 1:0.99.20~pre.178+dfsg-1 to 1:0.99.20~pre.178+dfsg-2 for me as follows: Preparing to unpack .../4-jed-common_1%3a0.99.20~pre.178+dfsg-2_all.deb ... Unpacking jed-common (1:0.99.20~pre.178+dfsg-2) over (1:0.99.20~pre.178+dfsg-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-OeNOOg/4-jed-common_1%3a0.99.20~pre.178+dfsg-2_all.deb (--unpack): unable to install new version of '/usr/share/jed/doc/txt/abbrev.txt': No such file or directory […] dpkg: dependency problems prevent configuration of jed: jed depends on jed-common (= 1:0.99.20~pre.178+dfsg-2); however: Version of jed-common on system is 1:0.99.20~pre.178+dfsg-1. dpkg: error processing package jed (--configure): dependency problems - leaving unconfigured […] Errors were encountered while processing: jed -- System Information: Debian Release: 12.0 APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'testing-security'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-7-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages jed-common depends on: ii slsh 2.3.3-3 jed-common recommends no packages. Versions of packages jed-common suggests: ii emacs-gtk [info-browser] 1:28.2+1-14 ii info [info-browser] 6.8-6+b1 iu jed [info-browser]1:0.99.20~pre.178+dfsg-2 ii konqueror [info-browser] 4:22.12.3-1 ii pinfo [info-browser] 0.6.13-1.3 -- no debconf information -- debsums errors found: debsums: changed file /usr/share/doc/jed-common/changelog.Debian.gz (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/abbrev.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/color.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/compile.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/dfa.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/edt.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/emacs.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/filelock.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/fold.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/hooks.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/ide-mode.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/jed_faq.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/linux-keys.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/menus.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/mouse.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/pc-keys.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/program.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/recentx.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/rgrep.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/rmail.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/script.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/sessions.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/syntax.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/undo.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/utf8.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/wjed.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/wordstar.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/xjed.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/xrenderfont.txt (from jed-common package) debsums: missing file /usr/share/doc/jed-common/txt/yankpop.txt (from jed-common package)
Bug#1035650: elpa-org version older than built-in Org in bookworm
On 09/05/2023 05:00, Nicholas D Steeves wrote: It's what at least two users want Intention of my bug report is to ensure that it was a conscious decision to keep a bit outdated Org version. I hope, only a small part of users will really notice the difference with built-in version. I consider Org-9.6 as desired, but unrealistic, a dummy package as a compromise. Release notes can advise the former to remove elpa-org, but we shouldn't advise elpa-org-contrib users to use 'equivs' to make emacs Provide a virtual elpa-org. If you are against equivs then elpa-org dependency must be dropped from elpa-org-contrib. Unfortunately the latter requires a change of a package in testing. You're describing the "dummy package" approach. I was advocating for the "virtual package" approach (with version-qualified Provides <- this is key) There is a minor issue with the dummy package approach. Some (I hope rare) users may try to install emacs-27 from bullseye and dummy elpa-org (if it would be uploaded to bookworm at all of course) getting Org version (emacs built-in) significantly less than they may expect from the version of the elpa-org Debian package. The following consideration are mostly concerning trixie, but still might affect current decision. Adding Org version to emacs-el "Provides" is a reasonable idea since org-contrib, at least formally, does not require latest Org release, however it is possible that Package-Requires inside the .el file was not up to date. So likely org-contrib may be run with built-in Org. However I think "elpa-org" is a bit confusing name for virtual package. Something like emacs-pkg-org in both emacs-el and elpa-org may be better. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033400#25 suggests to not ship Org in the emacs-el Debian package. Certainly it is possible to split built-in Org into a separate package and to add it to "Recommends" of emacs-el. However it increases maintenance cost while benefits are not clear to me. Perhaps it is better to discuss splitting in #1033400. I think, users who relies on latest Org features and fixes, stick to other methods than elpa-org Debian package (and sometimes are bitten by e.g. package.el bugs). It is another reason to respect Debian release policy, but be more carefully with updates in future.
Bug#1035772:
With https://invent.kde.org/multimedia/kmplayer/-/commit/6b01d442146d58d940a2bf919da5767867406120 (unreleased), this dependency was removed.
Bug#1035772: kmplayer: FTBFS: Could NOT find KF5 (missing: KDELibs4Support)
Source: kmplayer Severity: serious Version: 1:0.12.0b-3 Even with #997118 fixed, the build fails with: CMake Error at /usr/share/cmake-3.25/Modules/FindPackageHandleStandardArgs.cmake:230 (message): Could NOT find KF5 (missing: KDELibs4Support) (found version "5.103.0") Call Stack (most recent call first): /usr/share/cmake-3.25/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE) /usr/share/ECM/find-modules/FindKF5.cmake:93 (find_package_handle_standard_args) CMakeLists.txt:30 (find_package) -- Configuring incomplete, errors occurred!
Bug#1034875: kitty: Should not handle application/x-sh mime type by executing the script
On Wed, Apr 26, 2023 at 02:50:47PM +0200, Raphael Hertzog wrote: > Executing the script as default open action is IMO a very bad idea > because what you get by email is largely to not be trusted so I would > suggest that kitty be modified to not execute scripts in its URL > launcher mode (or that it gets some interactive confirmation from the > user before executing it). Upstream has added support for prompting if a file is executable[0]. However, the current upstream version of kitty has rewritten all of its kittens in go, so the changes aren't trivially backported. For bookworm, I'm going to stop installing kitty-open.desktop, by default. Install, I will ship it under /usr/share/doc/kitty/examples and add a note to README.Debian about it. [0]: https://github.com/kovidgoyal/kitty/commit/537cabca710f64b838d3b8b1dc986db596fb29d4 Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1035650: elpa-org version older than built-in Org in bookworm
tldr: Dear team, are there any objections to making a team upload using
the dummy package approach? It's what at least two users want, and it
guards against harming relations with upstream Emacs. The existing
state of things is between useless, embarrassing, and harmful, so let's
fix this.
Sean Whitton writes:
> Hello,
>
> On Sun 07 May 2023 at 04:42PM -04, Nicholas D Steeves wrote:
>
>> Is there a practical argument against adding versioned Provides to
>> either emacs-common or emacs-el (as appropriate)? Something like
>>
> I believe that changes of this nature are not appropriate at this stage
> of the freeze. I wish we had done something about this sooner, but
> elpa-org is undermaintained.
>
With a potential harm argument ("not appropriate"), shouldn't one also
consider the social cost of doing nothing? With users, as well as to
our rapport with upstream? See below.
> I don't think we should kick it out, because having a slightly older Org
> seems less bad than also kicking out the rdeps, on balance.
>
Another way of articulating the problem:
(without elpa-org installed) M-x org-version
Org mode version 9.5.5 (release_9.5.5 @ /usr/share/emacs/28.2/lisp/org/)
(with elpa-org installed) M-x org-version
Org mode version 9.5.2 (9.5.2 @ /usr/share/emacs/site-lisp/elpa/org-9.5.2/)
Elpa-org shadows the built-in copy. 9.5.3's bug fixes appear to
indicate that 9.5.2 may be unusable for users of Org's
bibliography-related functions, and of course there are a number of
other bug fixes between 9.5.2 and 9.5.5. Is it really conscionable to
/disable/ bug fixes that Emacs 25 provides in built-in Org-mode? Is it
really conscionable to do this to upstream? When we ask them to
accommodate us for native-comp-related things, shouldn't we also
demonstrate that we support their work in other areas of Emacs?
All users who have elpa-org installed in bullseye will be affected when
upgrading, as well as all elpa-org-contrib users. Release notes can
advise the former to remove elpa-org, but we shouldn't advise
elpa-org-contrib users to use 'equivs' to make emacs Provide a virtual
elpa-org.
Maxim Nikulin writes:
> On 07/05/2023 20:34, David Bremner wrote:
>> Maxim Nikulin writes:
>
> I am against *removing* elpa-org from bookworm. I have a hope that it is
> possible to submit *empty* elpa-org package and it still can be accepted
> to bookworm. No dependencies will be broken, users will get a few more
> fixes from built-in Org shipped in emacs-el. If a newer Org appear later
> in next Debian releases (or in backports) users will get it.
>
You're describing the "dummy package" approach. I was advocating for
the "virtual package" approach (with version-qualified Provides <- this
is key), but yes, either approach works :) Some people find empty
packages ugly/cruft so I prefer to avoid them when possible, but it
sounds like this isn't consensus for this approach at this time. Thus,
yes, now I agree with you!
> Almost unrelated to bookworm (and so having less priority) issue: coming
> Emacs-29 will have built-in Org-9.6 and difference between versions will
> be substantial. Benefits of empty elpa-org in comparison to outdated Org
> will be more important.
>
Agreed!
Regards,
Nicholas
signature.asc
Description: PGP signature
Processed: Re: freebirth: crashes at startup
Processing control commands: > severity -1 grave Bug #995854 [freebirth] freebirth: crashes at startup Severity set to 'grave' from 'normal' -- 995854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1035766 to sse2-support,sse3-support,sse4.2-support, found 1035766 in 15
Processing commands for cont...@bugs.debian.org:
> reassign 1035766 sse2-support,sse3-support,sse4.2-support
Bug #1035766 [sse4.2-support,sse3-support] sse{2,3,4.2}-support: copyright file
missing after upgrade (policy 12.5)
Bug reassigned from package 'sse4.2-support,sse3-support' to
'sse2-support,sse3-support,sse4.2-support'.
No longer marked as found in versions 15.
Ignoring request to alter fixed versions of bug #1035766 to the same values
previously set
> found 1035766 15
Bug #1035766 [sse2-support,sse3-support,sse4.2-support] sse{2,3,4.2}-support:
copyright file missing after upgrade (policy 12.5)
Marked as found in versions isa-support/15.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1035766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 1 error): reassign 1035766 to sse2-support,sse3-support,sse4.2-support ...
Processing commands for cont...@bugs.debian.org:
> reassign 1035766 sse2-support,sse3-support,sse4.2-support 15
Unknown command or malformed arguments to command.
> retitle 1035766 sse{2,3,4.2}-support: copyright file missing after upgrade
> (policy 12.5)
Bug #1035766 [sse4.2-support,sse3-support] {sse3,sse4.2}-support: copyright
file missing after upgrade (policy 12.5)
Changed Bug title to 'sse{2,3,4.2}-support: copyright file missing after
upgrade (policy 12.5)' from '{sse3,sse4.2}-support: copyright file missing
after upgrade (policy 12.5)'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1035766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1035767: gxmms2: Non-working maintainer address
Source: gxmms2 Version: 0.7.1-3 Severity: serious Justification: Policy 3.3 X-Debbugs-Cc: bdr...@debian.org X-Debbugs-Cc: and...@0x63.nu Mail delivery failed: returning message to sender This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: r...@debian.org Unrouteable address Reporting-MTA: dns; mitropoulos.debian.org Action: failed Final-Recipient: rfc822;r...@debian.org Status: 5.0.0
Bug#1035766: {sse3,sse4.2}-support: copyright file missing after upgrade (policy 12.5)
Package: sse4.2-support,sse3-support Version: 15 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package misses the copyright file after an upgrade, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory. This was observed on the following upgrade paths: bullseye -> bookworm >From the attached log (scroll to the bottom...): 0m42.0s ERROR: WARN: Inadequate results from running adequate! sse4.2-support: missing-copyright-file /usr/share/doc/sse4.2-support/copyright MISSING COPYRIGHT FILE: /usr/share/doc/sse4.2-support/copyright # ls -lad /usr/share/doc/sse4.2-support drwxr-xr-x 2 root root 40 May 3 12:07 /usr/share/doc/sse4.2-support # ls -la /usr/share/doc/sse4.2-support/ total 0 drwxr-xr-x 2 root root 40 May 3 12:07 . drwxr-xr-x 113 root root 2300 May 3 12:07 .. 0m39.1s ERROR: WARN: Inadequate results from running adequate! sse3-support: missing-copyright-file /usr/share/doc/sse3-support/copyright MISSING COPYRIGHT FILE: /usr/share/doc/sse3-support/copyright # ls -lad /usr/share/doc/sse3-support drwxr-xr-x 2 root root 40 May 3 13:55 /usr/share/doc/sse3-support # ls -la /usr/share/doc/sse3-support/ total 0 drwxr-xr-x 2 root root 40 May 3 13:55 . drwxr-xr-x 113 root root 2300 May 3 13:55 .. Additional info may be available here: https://wiki.debian.org/MissingCopyrightFile Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14) to perform the conversion, ideally using d/$PACKAGE.maintscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. cheers, Andreas sse4.2-support_15.log.gz Description: application/gzip
Bug#1035765: python-rlp-doc: copyright file missing after upgrade (policy 12.5)
Package: python-rlp-doc Version: 0.5.1-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package misses the copyright file after an upgrade, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory. This was observed on the following upgrade paths: bullseye -> bookworm >From the attached log (scroll to the bottom...): 0m46.7s ERROR: WARN: Inadequate results from running adequate! python-rlp-doc: missing-copyright-file /usr/share/doc/python-rlp-doc/copyright MISSING COPYRIGHT FILE: /usr/share/doc/python-rlp-doc/copyright # ls -lad /usr/share/doc/python-rlp-doc drwxr-xr-x 2 root root 40 May 3 13:13 /usr/share/doc/python-rlp-doc # ls -la /usr/share/doc/python-rlp-doc/ total 0 drwxr-xr-x 2 root root 40 May 3 13:13 . drwxr-xr-x 127 root root 2620 May 3 13:13 .. Additional info may be available here: https://wiki.debian.org/MissingCopyrightFile Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14) to perform the conversion, ideally using d/$PACKAGE.maintscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. cheers, Andreas python-rlp-doc_0.5.1-3.log.gz Description: application/gzip
Bug#1035764: libtsm-dev: copyright file missing after upgrade (policy 12.5)
Package: libtsm-dev Version: 4.0.2-0.3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package misses the copyright file after an upgrade, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory. This was observed on the following upgrade paths: bullseye -> bookworm >From the attached log (scroll to the bottom...): MISSING COPYRIGHT FILE: /usr/share/doc/libtsm-dev/copyright # ls -lad /usr/share/doc/libtsm-dev drwxr-xr-x 2 root root 40 May 3 14:43 /usr/share/doc/libtsm-dev # ls -la /usr/share/doc/libtsm-dev/ total 0 drwxr-xr-x 2 root root 40 May 3 14:43 . drwxr-xr-x 114 root root 2320 May 3 14:43 .. Additional info may be available here: https://wiki.debian.org/MissingCopyrightFile Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14) to perform the conversion, ideally using d/$PACKAGE.maintscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. cheers, Andreas libtsm-dev_4.0.2-0.3.log.gz Description: application/gzip
Bug#1034443: python3-brial: uninstallable on arcitectures where sagemath is unavailable
Hi Tobias, On Sat, 6 May 2023 10:24:41 + Tobias Hansen wrote: Note that we could also just remove python3-sage and the autopkgtest. I assume you mean python3-brial here. Nothing in Debian depends on it Not true (and it's too late in the freeze to do that [1]): paul@mulciber ~ $ reverse-depends python3-brial Reverse-Recommends == * science-mathematics-dev * singular-data Paul PS: please cc me on reply, I'm not subscribed to this bug. [1] https://release.debian.org/testing/freeze_policy.html#appropriate OpenPGP_signature Description: OpenPGP digital signature
Bug#1035692: marked as done (jed-common: unhandled symlink to directory conversion: /usr/share/doc/jed-common/txt -> ../../jed/doc/txt)
Your message dated Mon, 08 May 2023 19:33:48 + with message-id and subject line Bug#1035692: fixed in jed 1:0.99.20~pre.178+dfsg-2 has caused the Debian Bug report #1035692, regarding jed-common: unhandled symlink to directory conversion: /usr/share/doc/jed-common/txt -> ../../jed/doc/txt to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1035692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jed-common Version: 1:0.99.20~pre.178+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: bullseye -> bookworm For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14) to perform the conversion, ideally using d/$PACKAGE.maintscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. >From the attached log (scroll to the bottom...): 0m39.5s ERROR: installs objects over existing directory symlinks: /usr/share/doc/jed-common/txt/abbrev.txt (jed-common) != /usr/share/jed/doc/txt/abbrev.txt (?) /usr/share/doc/jed-common/txt -> ../../jed/doc/txt /usr/share/doc/jed-common/txt/color.txt (jed-common) != /usr/share/jed/doc/txt/color.txt (?) /usr/share/doc/jed-common/txt -> ../../jed/doc/txt /usr/share/doc/jed-common/txt/compile.txt (jed-common) != /usr/share/jed/doc/txt/compile.txt (?) /usr/share/doc/jed-common/txt -> ../../jed/doc/txt /usr/share/doc/jed-common/txt/dfa.txt (jed-common) != /usr/share/jed/doc/txt/dfa.txt (?) /usr/share/doc/jed-common/txt -> ../../jed/doc/txt /usr/share/doc/jed-common/txt/edt.txt (jed-common) != /usr/share/jed/doc/txt/edt.txt (?) /usr/share/doc/jed-common/txt -> ../../jed/doc/txt /usr/share/doc/jed-common/txt/emacs.txt (jed-common) != /usr/share/jed/doc/txt/emacs.txt (?) /usr/share/doc/jed-common/txt -> ../../jed/doc/txt /usr/share/doc/jed-common/txt/filelock.txt (jed-common) != /usr/share/jed/doc/txt/filelock.txt (?) /usr/share/doc/jed-common/txt -> ../../jed/doc/txt /usr/share/doc/jed-common/txt/fold.txt (jed-common) != /usr/share/jed/doc/txt/fold.txt (?) /usr/share/doc/jed-common/txt -> ../../jed/doc/txt /usr/share/doc/jed-common/txt/hooks.txt (jed-common) != /usr/share/jed/doc/txt/hooks.txt (?) /usr/share/doc/jed-common/txt -> ../../jed/doc/txt /usr/share/doc/jed-common/txt/ide-mode.txt (jed-common) != /usr/share/jed/doc/txt/ide-mode.txt (?) /usr/share/doc/jed-common/txt -> ../../jed/doc/txt /usr/share/doc/jed-common/txt/jed_faq.txt (jed-common) != /usr/share/jed/doc/txt/jed_faq.txt (?) /usr/share/doc/jed-common/txt -> ../../jed/doc/txt /usr/share/doc/jed-common/txt/linux-keys.txt (jed-common) != /usr/share/jed/doc/txt/linux-keys.txt (?) /usr/share/doc/jed-common/txt -> ../../jed/doc/txt /usr/share/doc/jed-common/txt/menus.txt (jed-common) != /usr/share/jed/doc/txt/menus.txt (?) /usr/share/doc/jed-common/txt -> ../../jed/doc/txt /usr/share/doc/jed-common/txt/mouse.txt (jed-common) != /usr/share/jed/doc/txt/mouse.txt (?) /usr/share/doc/jed-common/txt -> ../../jed/doc/txt /usr/share/doc/jed-common/txt/pc-keys.txt (jed-common) != /usr/share/jed/doc/txt/pc-keys.txt (?) /usr/share/doc/jed-common/txt -> ../../jed/doc/txt /usr/share/doc/jed-common/txt/program.txt (jed-common) != /usr/share/jed/doc/txt/program.txt (?) /usr
Processed: Bug#1035692 marked as pending in jed
Processing control commands: > tag -1 pending Bug #1035692 [jed-common] jed-common: unhandled symlink to directory conversion: /usr/share/doc/jed-common/txt -> ../../jed/doc/txt Added tag(s) pending. -- 1035692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035692: marked as pending in jed
Control: tag -1 pending Hello, Bug #1035692 in jed reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/jed/-/commit/40d282d560572a7807e19cc92240b285c7642cdc Avoid installing *.txt over a directory symlink (closes: #1035692) + d/jed-common.maintscript: Add symlink_to_dir command for the directory /usr/share/jed/doc/txt + d/jed-common.links: Removed file + d/rules: Create file d/jed-common.links by adding individual symbolic links /usr/share/jed/doc/txt/*.txt point to the files in /usr/share/doc/jed-common/txt/ + d/clean: Remove the file d/jed-common.links Gbp-Dch: Full (this message was generated automatically) -- Greetings https://bugs.debian.org/1035692
Bug#1034694: gnome-core: Cannot install due to pipewire-audio dependency
Package: gnome-core Version: 1:43+1 Followup-For: Bug #1034694 X-Debbugs-Cc: witold.bary...@gmail.com Here: root@debian:~# sudo apt -V --simulate remove pulseaudio Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: bind9-host (1:9.18.12-1) bind9-libs (1:9.18.12-1) libfstrm0 (0.6.1-1) libjemalloc2 (5.3.0-1) libmaxminddb0 (1.7.1-1) libprotobuf-c1 (1.4.1-1+b1) libuv1 (1.44.2-1) Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: liblua5.3-0 (5.3.6-2) libpipewire-0.3-modules (0.3.65-3) libwireplumber-0.4-0 (0.4.13-1) pipewire (0.3.65-3) pipewire-bin (0.3.65-3) pipewire-pulse (0.3.65-3) wireplumber (0.4.13-1) Suggested packages: libspa-0.2-bluetooth (0.3.65-3) wireplumber-doc (0.4.13-1) The following packages will be REMOVED: libcanberra-pulse (0.30-10) pulseaudio (16.1+dfsg1-2+b1) The following NEW packages will be installed: liblua5.3-0 (5.3.6-2) libpipewire-0.3-modules (0.3.65-3) libwireplumber-0.4-0 (0.4.13-1) pipewire (0.3.65-3) pipewire-bin (0.3.65-3) pipewire-pulse (0.3.65-3) wireplumber (0.4.13-1) 0 upgraded, 7 newly installed, 2 to remove and 0 not upgraded. Remv libcanberra-pulse [0.30-10] Remv pulseaudio [16.1+dfsg1-2+b1] Inst liblua5.3-0 (5.3.6-2 Debian:testing [amd64]) Inst libpipewire-0.3-modules (0.3.65-3 Debian:testing [amd64]) Inst libwireplumber-0.4-0 (0.4.13-1 Debian:testing [amd64]) Inst pipewire-bin (0.3.65-3 Debian:testing [amd64]) Inst pipewire (0.3.65-3 Debian:testing [amd64]) Inst pipewire-pulse (0.3.65-3 Debian:testing [amd64]) Inst wireplumber (0.4.13-1 Debian:testing [amd64]) Conf liblua5.3-0 (5.3.6-2 Debian:testing [amd64]) Conf libpipewire-0.3-modules (0.3.65-3 Debian:testing [amd64]) Conf libwireplumber-0.4-0 (0.4.13-1 Debian:testing [amd64]) Conf pipewire-bin (0.3.65-3 Debian:testing [amd64]) Conf pipewire (0.3.65-3 Debian:testing [amd64]) Conf pipewire-pulse (0.3.65-3 Debian:testing [amd64]) Conf wireplumber (0.4.13-1 Debian:testing [amd64]) root@debian:~# Regards, Witold
Processed: severity of 1035350 is normal
Processing commands for cont...@bugs.debian.org: > severity 1035350 normal Bug #1035350 [postfix] postfix: postinst script modifies configuration files despite local changes Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1035350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035598: /var/lib/dpkg/info/kanboard.postinst: 24: lighty-enable-mod: not found
Kanboard uses a varitey of databases and webservers. None of those dependencies should block installation. -Phil -- .--, | Fortuitous Technologies - DevOps, Design & Development | | A Stitch in Design Saves Nine - http://fortuitous.com | | Philip Carinhas, CEO * p...@fortuitous.com * 512-351-7783 | `-' signature.asc Description: PGP signature
Processed: Re: Bug#1035592: Info received (Bug#1035592: openbox: Openbox does not present a desktop)
Processing control commands: > severity -1 normal Bug #1035592 [openbox] openbox: Openbox does not present a desktop Severity set to 'normal' from 'grave' -- 1035592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035592 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035592: Info received (Bug#1035592: openbox: Openbox does not present a desktop)
Control: severity -1 normal
Bug#1034758: marked as done (x2goserver-common: fails to purge - command (deluser|delgroup) in postrm not found)
Your message dated Mon, 08 May 2023 14:49:23 + with message-id and subject line Bug#1034758: fixed in x2goserver 4.1.0.3-7 has caused the Debian Bug report #1034758, regarding x2goserver-common: fails to purge - command (deluser|delgroup) in postrm not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1034758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: x2goserver-common Version: 4.1.0.3-6 Severity: wishlist Hi, During a test with piuparts I noticed your package failed to purge due to a command not found. According to policy 7.2 you cannot rely on the depends being available during purge, only the essential packages are available for sure. The fix should be easy: your package is using adduser/addgroup or deluser/delgroup from the adduser package, which is only priority important. Using useradd/groupadd or userdel/groupdel from the passwd package (priority required) should fix this problem. There is ongoing discussion how to handle system users on package removal, see https://bugs.debian.org/621833 Consensus seems to be not to remove system users (to avoid reusing user/group IDs which could grant access to the wrong files) but to "lock" them (where "locking"/"unlocking" is not yet precisely defined). Until that has been decided it should be sufficient to have the postrm script ignore any errors from deluser/delgroup: deluser/delgroup ... || true Piuparts log is here: https://piuparts.debian.org/sid/fail/x2goserver-common_4.1.0.3-6.log Regards, Patrice -- System Information: Debian Release: 12.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-7-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages x2goserver-common depends on: ii adduser 3.132 x2goserver-common recommends no packages. x2goserver-common suggests no packages. --- End Message --- --- Begin Message --- Source: x2goserver Source-Version: 4.1.0.3-7 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of x2goserver, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated x2goserver package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 08 May 2023 16:25:39 +0200 Source: x2goserver Architecture: source Version: 4.1.0.3-7 Distribution: unstable Urgency: medium Maintainer: Debian Remote Maintainers Changed-By: Mike Gabriel Closes: 1034758 Changes: x2goserver (4.1.0.3-7) unstable; urgency=medium . * debian/x2goserver-*.postrm: + Ignore failures from deluser/delgroup. (Closes: #1034758). Checksums-Sha1: d2ebb3fec0b49bff415bfd47ca8f6cd6a855c17f 3157 x2goserver_4.1.0.3-7.dsc 5b0ec3ab931112a323c133be2383acf18a05eacf 43628 x2goserver_4.1.0.3-7.debian.tar.xz 60fe991db46e4e41ed71f184ec9b04ca24882382 6378 x2goserver_4.1.0.3-7_source.buildinfo Checksums-Sha256: cd3f8be89ac24ff2b4b5ed8a650700d3ea3bb48b608c92859775b81e5042bed5 3157 x2goserver_4.1.0.3-7.dsc d0c62c64ba134824a53cd7945ed46192dacc1a637999fa48f7295f02ad5d2731 43628 x2goserver_4.1.0.3-7.debian.tar.xz 433e7ce8cf34b900103995aee2699101cf8150fcd33d3c2a33711ca67d1edf8f 6378 x2goserver_4.1.0.3-7_source.buildinfo Files: 124ff0bc0d2a46861d5d2e2cf4194912 3157 x11 optional x2goserver_4.1.0.3-7.dsc 8d9f93593f659d709c5aa2e6383005d0 43628 x11 optional x2goserver_4.1.0.3-7.debian.tar.xz d7d9f64837ea3254492d23a10ecb6fb7 6378 x11 optional x2goserver_4.1.0.3-7_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmRZBvYVHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxaP0QAK7o14rb16OaC7RGR9mQEND7enWq SHZkca0U4fgxndwxUNhvZ/Jr0BnXMVWAuEFgaE9X43b788vnPTIkJ2K+R2UvFZvx eQGOWIjvlH1bN1QToU7BYAU
Bug#1034875: kitty: Should not handle application/x-sh mime type by executing the script
On Sat, May 06, 2023 at 04:07:56PM +0200, Gabriel Corona wrote: > Hi, > > > In the mean time, it's probably a good idea to drop > > "application/x-sh;application/x-shellscript" from the list of supported > > mime type to limit the risk. (I assume that even with "text/plain" and a > > .sh file extension or a shebang, kitty might still decide to execute the > > script... so the issue is not entirely fixed, but it reduces the number > > of > > cases where "kitty +open" is invoked on shell scripts) > > Indeed, you can use a file with MIME type such as text/ascii or > x-scheme-handler/kitty and a .tool file extension and it will be executed > through kitty. > > Affected software include: mail clients (mutt, Thunderbird [3,4]), browsers > (Firefox [1,2]), PDF viewers (Okular [5]). > > [1] https://www.gabriel.urdhr.fr/img/kitty-firefox1.png > [2] https://www.gabriel.urdhr.fr/img/kitty-firefox2.png > [3] https://www.gabriel.urdhr.fr/img/kitty-thunderbird1.png > [4] https://www.gabriel.urdhr.fr/img/kitty-thunderbird2.png The above examples prompt the user, so they're making an explicit choice. That's less of an issue. > > Or it's the users responsibility to configure their system to > > view shell files rather than execute them, if they are in the habit of > > clicking exe's attached to emails or otherwise clicking untrusted shell > > scripts. > > Or it is our responsibility to ship with a secure by default configuration? I'm leaning towards shipping kitty-open.desktop under /usr/share/doc/kitty/examples and adding a note to README.Debian about how to install it and the implications. I've not used this particular functionality of Kitty, so I'm not sure how this will change the usual user experience. However, I think this is a safer default and provides more information to the user. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1032007: marked as done (Don't release with bookworm)
Your message dated Mon, 08 May 2023 13:30:27 + with message-id and subject line Bug#1035611: Removed package(s) from unstable has caused the Debian Bug report #1032007, regarding Don't release with bookworm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1032007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032007 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-uber-go-atomic Version: 1.8.0-2 Severity: serious X-Debbugs-Cc: z...@debian.org Duplicated with https://tracker.debian.org/pkg/golang-go.uber-atomic --- End Message --- --- Begin Message --- Version: 1.8.0-2+rm Dear submitter, as the package golang-github-uber-go-atomic has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1035611 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1032106: marked as done (Don't release with bookworm)
Your message dated Mon, 08 May 2023 13:29:53 + with message-id and subject line Bug#1035610: Removed package(s) from unstable has caused the Debian Bug report #1032106, regarding Don't release with bookworm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1032106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032106 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-hashicorp-terraform-plugin-test Version: 1.3.0+git20200503.328f99a-3 Severity: serious X-Debbugs-Cc: z...@debian.org Upstream repo https://github.com/hashicorp/terraform-plugin-test is archived. No reverse-depends. --- End Message --- --- Begin Message --- Version: 1.3.0+git20200503.328f99a-3+rm Dear submitter, as the package golang-github-hashicorp-terraform-plugin-test has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1035610 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1002979: marked as done (FTBFS with camlp5 8.00.02)
Your message dated Mon, 08 May 2023 13:31:27 + with message-id and subject line Bug#1035729: Removed package(s) from unstable has caused the Debian Bug report #1002979, regarding FTBFS with camlp5 8.00.02 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1002979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002979 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: geneweb Version: 6.08+git20181019+dfsg-3 Severity: important Tags: ftbfs Dear Maintainer, Your package FTBFS with camlp5 8.00.02 with the following error: > camlp5r pa_extend.cmo q_MLast.cmo -o pa_macro5.ppo pa_macro5.ml > File "pa_macro5.ml", line 162, characters 51-52: > While expanding quotation "patt": > Parse error: end of input expected after [patt] (in [patt_eoi]) This was discovered while preparing the transition to OCaml 4.13.1. Packages rebuilt with OCaml 4.13.1 are available at: https://ocaml.debian.net/transitions/ocaml-4.13.1/ Cheers, -- Stéphane -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Version: 6.08+git20181019+dfsg-3+rm Dear submitter, as the package geneweb has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1035729 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1017902: Ships autogenerated files that can't be renegerated with the code in Debian main
https://github.com/morpheism/poppler-sharp/pull/7 suggests this is generated via gapi.
Bug#1017182: marked as done (grads: FTBFS: (.text+0xc8): undefined reference to `libdap::DDS::var_begin()')
Your message dated Mon, 8 May 2023 13:41:20 +0100 with message-id and subject line closing - previously fixed has caused the Debian Bug report #1017182, regarding grads: FTBFS: (.text+0xc8): undefined reference to `libdap::DDS::var_begin()' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1017182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: grads Version: 3:2.2.1-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: > /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libgadap.a(gaUtils.o): > in function `findOuterSequence(libdap::DDS&)': > (.text+0xc8): undefined reference to `libdap::DDS::var_begin()' > /usr/bin/ld: (.text+0xf2): undefined reference to `libdap::DDS::var_end()' > libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -fPIC -rdynamic > -Wl,--as-needed -o stnmap stnmap.o gamach.o galloc.o gaddes.sa.o gautil.sa.o > gatxt.o -L/usr/lib -lreadline -lncurses -lm > -L/usr/lib/x86_64-linux-gnu/hdf5/serial -lcairo -lfreetype > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2022/08/13/grads_2.2.1-5_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220813&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- close 1017182 thanks This bug was previously fixed in 3:2.2.1-5 regards Alastair -- Alastair McKinstry, GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5 e: mckins...@debian.org, im: @sceal.ie:mckinstry--- End Message ---
Processed: user debian...@lists.debian.org, usertagging 1026856, usertagging 1004066, affects 1004066 ...
Processing commands for cont...@bugs.debian.org:
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 1026856 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 1004066 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1004066 + groestlcoin-qt groestlcoin-tx groestlcoind
Bug #1004066 [src:groestlcoin] groestlcoin: FTBFS pubkey.cpp:181:96: error:
invalid conversion from 'secp256k1_xonly_pubkey*' to 'size_t'
Added indication that 1004066 affects groestlcoin-qt, groestlcoin-tx, and
groestlcoind
> usertags 915072 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 915072 + keysafe-bin
Bug #915072 [src:keysafe] keysafe: build-depends on many no longer available
libghc-*-dev versions
Added indication that 915072 affects keysafe-bin
> affects 936854 + libewf3
Bug #936854 {Done: Bastian Germann } [src:libewf] libewf:
Python2 removal in sid/bullseye
Added indication that 936854 affects libewf3
> found 1020264 5.8.1-1~exp1
Bug #1020264 {Done: Jessica Clarke } [src:polyml] polyml
FTBFS with glibc 2.34
Marked as found in versions polyml/5.8.1-1~exp1 and reopened.
> usertags 1020264 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1020264 + libpolyml11
Bug #1020264 [src:polyml] polyml FTBFS with glibc 2.34
Added indication that 1020264 affects libpolyml11
> usertags 1005713 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 1005713 + libtensorflow-framework2
Bug #1005713 [src:tensorflow] tensorflow FTBFS; bazel still tries to download
during build.
Added indication that 1005713 affects libtensorflow-framework2
> usertags 1005717 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 1005717 21.1~r2311+dfsg-2
Bug #1005717 {Done: Håvard F. Aasen } [src:nzbget]
nzbget: FTBFS with OpenSSL 3.0
Marked as found in versions nzbget/21.1~r2311+dfsg-2 and reopened.
> usertags 1004616 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 1001628 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 945742 piuparts
There were no usertags set.
Usertags are now: piuparts.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1004066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004066
1005713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005713
1005717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005717
1020264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020264
915072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915072
936854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936854
945742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1035732: libkscreenlocker5: Endless loop when using PAM
Package: libkscreenlocker5 Version: 5.20.5-1 Severity: critical Tags: patch upstream Justification: breaks the whole system Dear Maintainer, * What led up to the situation? A variation of upstream bug report https://bugs.kde.org/show_bug.cgi?id=438099 pam-configuration with auth[success=2 default=ignore] pam_krb5.so minimum_uid=1000 auth[success=1 default=ignore] pam_unix.so nullok try_first_pass authrequisite pam_deny.so and pressing "enter" to unlock the screen without entering a password. * What was the outcome of this action? Endless loop of kcheckpass[74114]: pam_krb5(kde:auth): pam_sm_authenticate: entry kcheckpass[74114]: pam_krb5(kde:auth): (user ) error getting password: Conversation error kcheckpass[74114]: pam_krb5(kde:auth): authentication failure; logname= uid= euid= tty=:1 ruser= rhost= kcheckpass[74114]: pam_krb5(kde:auth): pam_sm_authenticate: exit (failure) kcheckpass[74114]: pam_unix(kde:auth): conversation failed kcheckpass[74114]: pam_unix(kde:auth): auth could not identify password for [] (here more than 250 times / second) till next unlock attempt with a password. Flooding /var/log/auth.log and central authentication services. (Thus an unintentional "enter" on a locked screen can result in at least completely filled disks.) * What outcome did you expect instead? Authentication failure. Please include the short patch https://invent.kde.org/plasma/kscreenlocker/-/commit/fca315cf72826f93eda7a026016b33818b9d1f39 to kscreenlocker-5.20.5 in bullseye. The critical part has been completely rewritten in kscreenlocker-5.27.2 (testing) and the problem probably doesn't apply there. Best regards, Andreas Poenicke BTW: Hotfix: Separate /etc/pam.d/kde configuration with "use_first_pass" instead of "try_first_pass", like auth[success=2 default=ignore] pam_krb5.so minimum_uid=1000 auth[success=1 default=ignore] pam_unix.so use_first_pass authrequisite pam_deny.so Which should be ok for kscreenlocker in most cases. -- System Information: Debian Release: 11.7 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-22-amd64 (SMP w/16 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:de Shell: /bin/sh linked to /usr/bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libkscreenlocker5 depends on: ii kpackagetool5 5.78.0-3 ii libc6 2.31-13+deb11u6 ii libkf5configcore5 5.78.0-4 ii libkf5configgui5 5.78.0-4 ii libkf5coreaddons5 5.78.0-4 ii libkf5crash5 5.78.0-3 ii libkf5declarative5 5.78.0-2 ii libkf5globalaccel-bin 5.78.0-3 ii libkf5globalaccel5 5.78.0-3 ii libkf5i18n55.78.0-2 ii libkf5idletime55.78.0-2 ii libkf5notifications5 5.78.0-2 ii libkf5package5 5.78.0-3 ii libkf5quickaddons5 5.78.0-2 ii libkf5waylandclient5 4:5.78.0-2 ii libkf5waylandserver5 4:5.78.0-2 ii libkf5windowsystem55.78.0-2 ii libkf5xmlgui5 5.78.0-2 ii libpam0g 1.4.0-9+deb11u1 ii libqt5core5a 5.15.2+dfsg-9 ii libqt5dbus55.15.2+dfsg-9 ii libqt5gui5 5.15.2+dfsg-9 ii libqt5network5 5.15.2+dfsg-9 ii libqt5qml5 5.15.2+dfsg-6 ii libqt5quick5 5.15.2+dfsg-6 ii libqt5widgets5 5.15.2+dfsg-9 ii libqt5x11extras5 5.15.2-2 ii libstdc++6 10.2.1-6 ii libwayland-client0 1.18.0-2~exp1.1 ii libwayland-server0 1.18.0-2~exp1.1 ii libx11-6 2:1.7.2-1 ii libxcb-keysyms10.4.0-1+b2 ii libxcb11.14-3 ii libxi6 2:1.7.10-1 ii psmisc 23.4-2 Versions of packages libkscreenlocker5 recommends: ii kde-config-screenlocker 5.20.5-1 libkscreenlocker5 suggests no packages. -- no debconf information -- Karlsruher Institut für Technologie Institut für Theoretische Festkörperphysik Institut für Theorie der Kondensierten Materie Dr. Andreas Poenicke Wolfgang-Gaede-Str. 1, Gebäude 30.23, D-76128 Karlsruhe Telefon: +49-721-608-43365 Fax: +49-721-608-47040 E-Mail: andreas.poeni...@kit.eduWWW: www.tfp.kit.edu KIT - Die Forschungsuniversität in der Helmholtz-Gemeinschaft
Bug#1035605: marked as done (gnuserv: fails to upgrade from 'bullseye': ERROR: install script from gnuserv package failed)
Your message dated Mon, 08 May 2023 09:48:49 + with message-id and subject line Bug#1035605: fixed in gnuserv 3.12.8-12 has caused the Debian Bug report #1035605, regarding gnuserv: fails to upgrade from 'bullseye': ERROR: install script from gnuserv package failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1035605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035605 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnuserv Version: 3.12.8-11 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'bullseye'. It installed fine in 'bullseye', then the upgrade to 'bookworm' fails. >From the attached log (scroll to the bottom...): Setting up gnuserv (3.12.8-11) ... update-alternatives: using /usr/bin/gnuattach.emacs to provide /usr/bin/gnuattach (gnuattach) in auto mode update-alternatives: using /usr/bin/gnuclient.emacs to provide /usr/bin/gnuclient (gnuclient) in auto mode update-alternatives: using /usr/bin/gnudoit.emacs to provide /usr/bin/gnudoit (gnudoit) in auto mode Install emacsen-common for emacs emacsen-common: Handling install of emacsen flavor emacs Install gnuserv for emacs install/gnuserv: Handling install for emacsen flavor emacs gzip: install.log.gz already exists; not overwritten ERROR: install script from gnuserv package failed dpkg: error processing package gnuserv (--configure): installed gnuserv package post-installation script subprocess returned error exit status 1 cheers, Andreas gnuserv_3.12.8-11.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gnuserv Source-Version: 3.12.8-12 Done: Alexander Zangerl We believe that the bug you reported is fixed in the latest version of gnuserv, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexander Zangerl (supplier of updated gnuserv package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 May 2023 19:40:21 +1000 Source: gnuserv Architecture: source Version: 3.12.8-12 Distribution: unstable Urgency: critical Maintainer: Alexander Zangerl Changed-By: Alexander Zangerl Closes: 1035605 Changes: gnuserv (3.12.8-12) unstable; urgency=critical . * fix bad install.log.gz handling (closes: #1035605) Checksums-Sha1: f788713251c42ff1869e99f0f38ef940d930eb9e 1684 gnuserv_3.12.8-12.dsc b0799a762f09b1bdcb2b4f8ed6dda0f90b33149c 12004 gnuserv_3.12.8-12.debian.tar.xz 966b51823a206ae41da05792627f59de3fb954b6 11541 gnuserv_3.12.8-12_amd64.buildinfo Checksums-Sha256: 373dc48f34c3cd1d5ce5ebaaa774a168d723f0e87229d8de0ca92a225b5e9409 1684 gnuserv_3.12.8-12.dsc c30125a048e1922c32300094ecff3c26b8abd826260171e64e0236a0fec2711e 12004 gnuserv_3.12.8-12.debian.tar.xz 5797fa700266d0ef5895f97951344915caa7e0f4eb52f319e33f673ab5ec 11541 gnuserv_3.12.8-12_amd64.buildinfo Files: faed5cd67749942f7c051dfacba26044 1684 editors optional gnuserv_3.12.8-12.dsc bd73f9c8e017378651d7e784005a0e66 12004 editors optional gnuserv_3.12.8-12.debian.tar.xz 03ee918e5695f68f2173cf0e70d59c32 11541 editors optional gnuserv_3.12.8-12_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJkWMTnAAoJED06g4g30PqNjvsP/jozWy/oFoGiW5MV98r/mjEI Qck6uJ5fGH16Mx6YOmctp4zsiDFQz4ivOOCdXJku6lDoEcndC+7izs0Hc9ecWZB6 uOUdjOu7dtdMetj5T1QS53bEiJxk3Y0uO4eXRseQNLFeMHLnPhY+qDVZVfuM9r9d BC9LGk1GwKSm9wKDDLe6xRff4zy/sd4bLzhpcbxtmb2/HNKb1YIVZHea0lIqu8Vi X+520yMkkrVci7e1TQKfx9C4LtzEbF0xf1I0GN1wUip02rTd+IBGxmZcoX3dNJYw BxXOO6cgeaUqojxuPcbzXe6LckUbA74z3TwE8s6c8Z649+JYJ/BHLzFmzeu1pAH2 Mihexn5+Rjzw7xV2dYis8gD8XHoz4v/RHoOldg0JW3FMplsVKS9G1eX3PPCoKdLt kDKPi+roAQ17vZmDuxj3ss8gcl7yf6PeczweT4wo4DYc0wDOgeFUJK2XDkrfxn3K 2poEOeX21KifEY32N+ZttjCq/6XdeJzCTAbLSfo1d8tS3chJ9eZGUjW4naAyKaYj SWUpVD06qBO28xcFu+QEAQvQ4ljWl1NE+hpkjDCMKd/6OxcmaPFC1TQA254oIcpr GQQigoMXwQBpmc3BWJv92ji2yd2tBDSzx1SuZqTBZDelLYkbRf9dn9I/z3r3csSr eIaEkOpVnyN/HsBoMW43 =ZfeN -END PGP SIGNATURE End Message ---
Bug#1035720: openstack-dashboard: fails to install: TypeError: requires_system_checks must be a list or tuple.
Package: openstack-dashboard
Version: 3:23.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the attached log (scroll to the bottom...):
...
2713 static files copied to '/var/lib/openstack-dashboard/static'.
/usr/lib/python3/dist-packages/django/conf/__init__.py:267:
RemovedInDjango50Warning: The USE_L10N setting is deprecated. Starting with
Django 5.0, localized formatting of data will always be enabled. For example
Django will display numbers and dates using the format of the current locale.
warnings.warn(USE_L10N_DEPRECATED_MSG, RemovedInDjango50Warning)
/usr/lib/python3/dist-packages/debreach/__init__.py:6: DeprecationWarning:
distutils Version classes are deprecated. Use packaging.version instead.
version_info = version.StrictVersion(__version__).version
Traceback (most recent call last):
File "/usr/share/openstack-dashboard/manage.py", line 23, in
execute_from_command_line(sys.argv)
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
line 442, in execute_from_command_line
utility.execute()
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
line 436, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
^^
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
line 275, in fetch_command
klass = load_command_class(app_name, subcommand)
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
line 49, in load_command_class
return module.Command()
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line
284, in __init__
raise TypeError("requires_system_checks must be a list or tuple.")
TypeError: requires_system_checks must be a list or tuple.
dpkg: error processing package openstack-dashboard (--configure):
installed openstack-dashboard package post-installation script subprocess
returned error exit status 1
Processing triggers for ca-certificates (20230311) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Errors were encountered while processing:
openstack-dashboard
cheers,
Andreas
openstack-dashboard_3:23.1.0-1.log.gz
Description: application/gzip
Bug#1035719: mdns-reflector: missing Depends: libcap2-bin
Package: mdns-reflector Version: 0.0.1+git20230316.f1bd0f1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package mdns-reflector. (Reading database ... (Reading database ... 4788 files and directories currently installed.) Preparing to unpack .../mdns-reflector_0.0.1+git20230316.f1bd0f1-1_amd64.deb ... Unpacking mdns-reflector (0.0.1+git20230316.f1bd0f1-1) ... Setting up mdns-reflector (0.0.1+git20230316.f1bd0f1-1) ... Creating _mdns.reflector system user. adduser: Warning: The home dir /dev/null you specified can't be accessed: Allowing use of questionable username. Adding system user `_mdns.reflector' (UID 150) ... Adding new group `_mdns.reflector' (GID 150) ... Adding new user `_mdns.reflector' (UID 150) with group `_mdns.reflector' ... Not creating home directory `/dev/null'. /var/lib/dpkg/info/mdns-reflector.postinst: 41: setcap: not found dpkg: error processing package mdns-reflector (--configure): installed mdns-reflector package post-installation script subprocess returned error exit status 127 Errors were encountered while processing: mdns-reflector cheers, Andreas mdns-reflector_0.0.1+git20230316.f1bd0f1-1.log.gz Description: application/gzip
Bug#1034120: marked as done (sensible-utils: Broken shell invocation handling)
Your message dated Mon, 08 May 2023 09:03:44 + with message-id and subject line Bug#1034120: fixed in sensible-utils 0.0.19 has caused the Debian Bug report #1034120, regarding sensible-utils: Broken shell invocation handling to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1034120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sensible-utils Version: 0.0.18 Severity: serious Hi! I installed this some time ago, and started seeing issues, but was still wondering why no one had reported this already and whether this was a local issue of mine, until I realized now this is an experimental only upload. In any case, when calling «dch» I'm getting stuff like: ,--- $ dch debian/changelog.dch": 1: Syntax error: Unterminated quoted string dch: fatal error at line 1742: Error editing debian/changelog `--- Regards, Guillem --- End Message --- --- Begin Message --- Source: sensible-utils Source-Version: 0.0.19 Done: Bastien Roucariès We believe that the bug you reported is fixed in the latest version of sensible-utils, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastien Roucariès (supplier of updated sensible-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 May 2023 07:56:01 + Source: sensible-utils Architecture: source Version: 0.0.19 Distribution: experimental Urgency: medium Maintainer: Anibal Monsalve Salazar Changed-By: Bastien Roucariès Closes: 1034120 Changes: sensible-utils (0.0.19) experimental; urgency=medium . * Bug fix: "Broken shell invocation handling", thanks to Guillem Jover (Closes: #1034120). Checksums-Sha1: 031b184274f6ac21aef78d8131cc48a80a713e59 1737 sensible-utils_0.0.19.dsc 8f7912fb66038e47cd973dca8056cf677f70c471 70900 sensible-utils_0.0.19.tar.xz e83a3d790dc498974e54b9c73c244c081a0416b0 6397 sensible-utils_0.0.19_amd64.buildinfo Checksums-Sha256: 758218a18c89964da1b2bcfb1e457949ef4e9ccc18a5b9061bb547b617167e1b 1737 sensible-utils_0.0.19.dsc 3af5fe874c9e643b3d413d4f1b71009194c9093225e9dd49de86e2e604721d69 70900 sensible-utils_0.0.19.tar.xz 141fa2991088cd7b65487e49c3f9434dbb6923a36bc047d02add3021c333cac7 6397 sensible-utils_0.0.19_amd64.buildinfo Files: 2e97f2b42c9d0837ac3c79ebba86f776 1737 utils required sensible-utils_0.0.19.dsc d236393ced30375771c5ca5d1866fbd6 70900 utils required sensible-utils_0.0.19.tar.xz bfbd00484b57ee92d79ade17fe462c1f 6397 utils required sensible-utils_0.0.19_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAmRYtdgRHHJvdWNhQGRl Ymlhbi5vcmcACgkQADoaLapBCF9Jww/+MEbYx2UhwWgX6WLCd1ZogCZ/0T7iG/zy k5zMDwu+3DkVnme/Gu1AaIWafBYLVqsSsEELiwl1mgvEX0UocDT40rMxvvuiCaPX LD19u0aDLMPqWBAyRMKwF0mhDs/WklU1c+08qH5VYYoKi1ZRMkCYMXPgd0px9zYX r18rVoMnzfMBRpRv1LQwQ0CXRpEi97iR1VkGQ2frSgymGZ/Nkqkpyr9bB15GLwvb 2B9O6Jbdp1z1BCdyHnu59Q8fE9/sqUiPJELPT7dwlQqQcn1Ohw2r84HfOtui9mKk zCVEYDX9vYH0f7dbTHtbTIROVgp+ZW6MhkQN3C+lBWuwEQt+ZHbPixuGcAteMWEA h0g7HfKMpejjKXhsPpTvLBk2JDuoVpXrkjULwOaIFckEjPra6N4BfDPlXrR0BIbx KZ5gjWh5iRvBf8PCWxy+IPIeM6HcdDgSQOCrXb4dooMxVZ7GMrkI33GoV06NZQIX MS9/RXERwXrNI445mbL4ZgTbzvhKFVxGX0yYaKgFnHaFXPi4Lelq94MkSA7Kzwnc /ttnbPZWtxKe4v07AN5xJ9h60+7j8q8jHj7OnV+8fwB5r0ha+9k6cPCYwiohlYSR y9X83wxuv7+iqTFpY8nX6MreeeKIuQNmaoqJrzgZghYO/bhykNCqW3wWYzhVJMUr oBMyIaKXtCU= =P4Ve -END PGP SIGNATURE End Message ---
Processed: retitle 1026439 to xtide: FTBFS (invalid conversion from ‘char**’ to ‘const char**’)
Processing commands for cont...@bugs.debian.org: > retitle 1026439 xtide: FTBFS (invalid conversion from ‘char**’ to ‘const > char**’) Bug #1026439 [src:xtide] xtide: FTBFS (invalid conversion from ‘char**’ to Changed Bug title to 'xtide: FTBFS (invalid conversion from ‘char**’ to ‘const char**’)' from 'xtide: FTBFS (invalid conversion from ‘char**’ to'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 965794
Processing commands for cont...@bugs.debian.org: > tags 965794 - pending Bug #965794 [python3-ooolib] python-ooolib: Removal of obsolete debhelper compat 5 and 6 in bookworm Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 965794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1034367: marked as pending in golang-v2ray-core
On 2023-05-07 14:34:09 -0700, Roger Shimizu wrote: > > I'm afraid this fix is incomplete. The source package still contains the > > data files with a non-free license and hence Debian is redistrbuting > > them. golang-v2ray-core needs to be repacked to completly get rid of the > > files. > > Yes, current fix just removes the geoip data from binary package. > For source package, considering current hard freeze status, we cannot > update the source package. > I plan to do it after bookworm releasing. > > For bookworm, can I lower the severity to keep this package? > Otherwise, this package and rdepends package will be removed from > testing/bookworm suite soon. There is still time to fix it and the fix should be easy. Add those files to Files-Excluded in debian/copyright, repack the source, upload. After doing that, please file an unblock request and feel free to ping me so that I can unblock the package. Cheers -- Sebastian Ramacher
Bug#1035713: google-android-ndk-r23b-installer: broken symlinks: /usr/lib/android-sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/linux-x86_64/*/bin/as -> /buildbot/src/android/...
Package: google-android-ndk-r23b-installer Version: 23.1.7779620+1675172737 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) broken symlinks. 1m10.3s ERROR: FAIL: Broken symlinks: /usr/lib/android-sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/linux-x86_64/aarch64-linux-android/bin/as -> /buildbot/src/android/ndk-release-r23/out/linux/android-ndk-r23b/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android-as (google-android-ndk-r23b-installer) /usr/lib/android-sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/linux-x86_64/arm-linux-androideabi/bin/as -> /buildbot/src/android/ndk-release-r23/out/linux/android-ndk-r23b/toolchains/llvm/prebuilt/linux-x86_64/bin/arm-linux-androideabi-as (google-android-ndk-r23b-installer) /usr/lib/android-sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/linux-x86_64/i686-linux-android/bin/as -> /buildbot/src/android/ndk-release-r23/out/linux/android-ndk-r23b/toolchains/llvm/prebuilt/linux-x86_64/bin/i686-linux-android-as (google-android-ndk-r23b-installer) /usr/lib/android-sdk/ndk/23.1.7779620/toolchains/llvm/prebuilt/linux-x86_64/x86_64-linux-android/bin/as -> /buildbot/src/android/ndk-release-r23/out/linux/android-ndk-r23b/toolchains/llvm/prebuilt/linux-x86_64/bin/x86_64-linux-android-as (google-android-ndk-r23b-installer) These targets look like build-time paths that should not be present in binary packages. cheers, Andreas
