Bug#990569: marked as done (libnode72: Missing dependency on libuv)
Your message dated Sat, 03 Jul 2021 20:19:55 + with message-id and subject line Bug#990569: fixed in nodejs 12.21.0~dfsg-5 has caused the Debian Bug report #990569, regarding libnode72: Missing dependency on libuv 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.) -- 990569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990569 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnode72 Version: 12.21.0~dfsg-4 Severity: serious Justification: Policy 3.5 Hi, i just realized libnode72 doesn't depend on libuv, even being built with --shared-libuv. Something is broken, will investigate quickly. Jérémy -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (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 libnode72 depends on: ii libbrotli1 1.0.9-2+b2 ii libc-ares2 1.17.1-1 ii libc6 2.31-12 ii libgcc-s1 10.2.1-6 ii libicu67 67.1-7 ii libnghttp2-14 1.43.0-1 ii libssl1.1 1.1.1k-1 ii libstdc++6 10.2.1-6 ii zlib1g 1:1.2.11.dfsg-2 libnode72 recommends no packages. libnode72 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 12.21.0~dfsg-5 Done: Jérémy Lal We believe that the bug you reported is fixed in the latest version of nodejs, 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 990...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated nodejs 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: Sat, 03 Jul 2021 20:50:29 +0200 Source: nodejs Architecture: source Version: 12.21.0~dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy Lal Closes: 990569 Changes: nodejs (12.21.0~dfsg-5) unstable; urgency=medium . * Patch uvwasi.gyp to honour --shared-libuv. Closes: #990569. Checksums-Sha1: 4f2bdc2390be36577d2584a6ef478f71604477b9 3455 nodejs_12.21.0~dfsg-5.dsc 3d86eea197cd038a1070e27f11f3e38f9dc9329c 136152 nodejs_12.21.0~dfsg-5.debian.tar.xz 0e00b5042f2b15be64878a7c5dbb6a249ebe1641 9231 nodejs_12.21.0~dfsg-5_source.buildinfo Checksums-Sha256: 79bc2792f67fd820162533ab3d5eb517cec6aa0b34dcba6f6837a30a17b4dfb1 3455 nodejs_12.21.0~dfsg-5.dsc 35e0b28999aa2cb484822bb9ffc3fea3eea3ad384e936663dabe41fa5547a9da 136152 nodejs_12.21.0~dfsg-5.debian.tar.xz 81e890ae07aba3d1830a415f660d4a6092e34fb85f8930001335ae9b820aa893 9231 nodejs_12.21.0~dfsg-5_source.buildinfo Files: 31d5f0132557455aa7b8a53636fa38cc 3455 javascript optional nodejs_12.21.0~dfsg-5.dsc b3df941ada9ae136206c93029d223c99 136152 javascript optional nodejs_12.21.0~dfsg-5.debian.tar.xz 5ed5ee5800fca7f0719e7312c4bc711a 9231 javascript optional nodejs_12.21.0~dfsg-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAmDgsZgSHGthcG91ZXJA bWVsaXgub3JnAAoJEGYRwF7dOfN0lPQP/1z8gH6o5eGuzHCbB+QrtMYUxYtoGrko TQkPdODuOylVNLmfuwQpCKn7YAuopWKEAeC42kahUQMOJWM95EIuJrql9RYxOw/7 klfRqm/9gdsWAUvDvsudz9FC6AVMiFt+RIFAvcVtv6xx/iy+pKw/VwSI+GduEn2K 9U/EkWI3mx5RVm7K4A73U5RZWkzbPjij0yKGEzToCSMCTFExgZ+e/L8vpuVgfuXK 4ogZh2GpZG0VwrqenJfTStVbQnj+LkBOhyBBrmnmUaq5KsmnLsfNlBnZfESMgxZY FeGLboaQDCe9hJjDIZujXO0jK98Hk2xr49vOcqzR095GA7ruJomxyVrbVtYiPEYh kDIeFyi19TEi3uaS5PdZddK7QdnJqdJCyPkPLWKb6tqGnotd/mbdUxkRGZhR49Bl veUuqYLyEM+1PQ52fR3sVy5/9M9bkM4Zh7JpOmWS685tSl+gcD+wxuvAgUm9l+qH gwzHPj9ynZgfg4AMQH6oGBW4PlVewUupmhCbKdJZ6XO0/E+SDNwkuqW5cXZusgfz 6b4QSxn1uL+1WOe+ipQC2Zh14b8P13lp5aurioikvAK+FP0IzKqBmfHmdIZA+U89 0lwZu9BVnmXoh3DEay4wp+tq9crJzPRp2cuYvsQUU48yhOtJca7pPoCRNZf2GGCN 2anMJNiaNX7u =2zOs -END PGP SIGNATURE End Message ---
Bug#986522: marked as done (golang-github-vdemeester-shakers: FTBFS: unsatisfiable build-dependency: golang-check.v1-dev (>= 0.0+git20150729.11d3bc7-3~) (versioned dep on a virtual pkg?))
Your message dated Sat, 03 Jul 2021 19:48:46 + with message-id and subject line Bug#986573: Removed package(s) from unstable has caused the Debian Bug report #986522, regarding golang-github-vdemeester-shakers: FTBFS: unsatisfiable build-dependency: golang-check.v1-dev (>= 0.0+git20150729.11d3bc7-3~) (versioned dep on a virtual pkg?) 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.) -- 986522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-vdemeester-shakers Version: 0.0~git20160210.0.24d7f1d-2.1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210406 ftbfs-bullseye Hi, During a rebuild of all packages in bullseye, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 9), dh-golang, golang-any, > golang-check.v1-dev (>= 0.0+git20150729.11d3bc7-3~) | > golang-github-go-check-check-dev, build-essential, fakeroot > Filtered Build-Depends: debhelper (>= 9), dh-golang, golang-any, > golang-check.v1-dev (>= 0.0+git20150729.11d3bc7-3~), build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [425 B] > Get:5 copy:/<>/apt_archive ./ Packages [495 B] > Fetched 1877 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: golang-check.v1-dev (>= > 0.0+git20150729.11d3bc7-3~) > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2021/04/06/golang-github-vdemeester-shakers_0.0~git20160210.0.24d7f1d-2.1_testing.log 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. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Version: 0.0~git20160210.0.24d7f1d-2.1+rm Dear submitter, as the package golang-github-vdemeester-shakers 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/986573 The version of this package that was in Debian prior to this removal can still be found using http://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. Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Bug#985859: marked as done (cpqarrayd - ship with bullseye? - no driver support)
Your message dated Sat, 03 Jul 2021 19:48:20 + with message-id and subject line Bug#986483: Removed package(s) from unstable has caused the Debian Bug report #985859, regarding cpqarrayd - ship with bullseye? - no driver support 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.) -- 985859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985859 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cpqarrayd Version: 2.3.6 Severity: serious Linux upstream has removed the "cciss" driver in 4.14-rc1. cpqarrayd needs the cciss driver to function. I imagine we shouldn't ship software that did not work with buster's kernel in bullseye. Chris --- End Message --- --- Begin Message --- Version: 2.3.6+rm Dear submitter, as the package cpqarrayd 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/986483 The version of this package that was in Debian prior to this removal can still be found using http://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. Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Bug#975921: marked as done (mali-midgard: Contains auto-generated file without corresponding source)
Your message dated Sat, 03 Jul 2021 19:47:13 +
with message-id
and subject line Bug#986453: Removed package(s) from unstable
has caused the Debian Bug report #975921,
regarding mali-midgard: Contains auto-generated file without corresponding
source
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.)
--
975921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mali-midgard
Version: 16.0+pristine-4
Severity: serious
mali_base_hwconfig_issues.h currently has:
> /* AUTOMATICALLY GENERATED FILE. If you want to amend the issues/features,
> * please update base/tools/hwconfig_generator/hwc_{issues,features}.py
> * For more information see base/tools/hwconfig_generator/README
> */
Unless patches to this file are accepted, this is not the preferred
form, and the mentioned scripts do not exist (I assume they are
Arm-internal scripts).
Jess
--- End Message ---
--- Begin Message ---
Version: 16.0+pristine-4+rm
Dear submitter,
as the package mali-midgard 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/986453
The version of this package that was in Debian prior to this removal
can still be found using http://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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Bug#986422: marked as done (Does not work with current DHCP servers)
Your message dated Sat, 03 Jul 2021 19:45:43 + with message-id and subject line Bug#985708: Removed package(s) from unstable has caused the Debian Bug report #986422, regarding Does not work with current DHCP servers 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.) -- 986422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ftp.debian.org Severity: normal I'm both maintainer and upstream for this package, I haven't developped or tested it for years, I'm possitive that it wouldn't work with current versions of isc dhcp server. Also, there are alternatives to it that should be better suited for the time being. So it should be removed from the distribution before we ship a non working piece of software with Bullseye. Regards. -- Manty/BestiaTester -> http://manty.net --- End Message --- --- Begin Message --- Version: 0.9+nmu1+rm Dear submitter, as the package autodns-dhcp 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/985708 The version of this package that was in Debian prior to this removal can still be found using http://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. Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Bug#904627: marked as done (cons: unusable due to obsolete dependency on cwd in @INC)
Your message dated Sat, 03 Jul 2021 19:39:24 + with message-id and subject line Bug#984941: Removed package(s) from unstable has caused the Debian Bug report #904627, regarding cons: unusable due to obsolete dependency on cwd in @INC 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.) -- 904627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cons Version: 2.3.0.1+2.2.0-2 Severity: grave Tags: a11y upstream Justification: renders package unusable Dear Maintainer, cons unfortunately fails immediately and no longer succeeds on building even a single C source file: do "Construct" failed, '.' is no longer in @INC; did you mean do "./Construct"? at /usr/bin/cons line 689. cons: don't know how to construct "example" '.' was removed from @INC in Perl 5.26, although this has been far from optimal long before and I can't say when exactly it turned fatal. Just in case no one feels like fixing this anymore, I think it would be nice to at least mention the problems in the description, not least because cons comes with a fairly whopping (and good) man page at almost 2000 pp. As enjoyable a read as it makes for, some people might just waste a lot of time, esp. since the changelog promises a last known-to-be-good version (yes, dating from 2006). Regards, Oliver -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cons depends on: ii perl [libdigest-md5-perl] 5.26.2-6 cons recommends no packages. cons suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 2.3.0.1+2.2.0-2+rm Dear submitter, as the package cons 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/984941 The version of this package that was in Debian prior to this removal can still be found using http://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. Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Bug#984644: marked as done (node-xmlhttprequest-ssl: Unmaintained fork of node-xmlhttprequest)
Your message dated Sat, 03 Jul 2021 19:36:13 + with message-id and subject line Bug#984643: Removed package(s) from unstable has caused the Debian Bug report #984644, regarding node-xmlhttprequest-ssl: Unmaintained fork of node-xmlhttprequest 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.) -- 984644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-xmlhttprequest-ssl Severity: serious node-xmlhttprequest-ssl is an unmaintained fork of node-xmlhttprequest. It should be removed from Bullseye --- End Message --- --- Begin Message --- Version: 1.6.0-1.1+rm Dear submitter, as the package node-xmlhttprequest-ssl 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/984643 The version of this package that was in Debian prior to this removal can still be found using http://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. Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Bug#982405: marked as done (libwww-freshmeat-perl: Does this package still make sense?)
Your message dated Sat, 03 Jul 2021 19:36:38 + with message-id and subject line Bug#984683: Removed package(s) from unstable has caused the Debian Bug report #982405, regarding libwww-freshmeat-perl: Does this package still make sense? 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.) -- 982405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libwww-freshmeat-perl Version: 0.22-2.1 Severity: serious Freshmeat became Freecode, which became read-only in 2014. There seems to be an active spinoff at http://freshcode.club/ but libwww-freshmeat-perl seems to hardcode freshmeat.net --- End Message --- --- Begin Message --- Version: 0.22-2.1+rm Dear submitter, as the package libwww-freshmeat-perl 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/984683 The version of this package that was in Debian prior to this removal can still be found using http://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. Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Bug#980885: marked as done (manpages-es-extra: Suitable for Bullseye?)
Your message dated Sat, 03 Jul 2021 19:37:43 + with message-id and subject line Bug#984734: Removed package(s) from unstable has caused the Debian Bug report #980885, regarding manpages-es-extra: Suitable for Bullseye? 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.) -- 980885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: manpages-es-extra Version: 0.8a-19.1 Severity: important X-Debbugs-Cc: Mario Blättermann Hello Javier, as stated in the description, manpages-es-extra is really outdated with no hope of receiving any further updates. Is this really suitable for bullseye? Manpages-es is already (long) gone. Manpages-l10n is in the process of importing all previous spanish translations (where possible). By using po4a, we are able to keep all pages up to date. If enough content (>= 80%) is still translated, the page is shipped (with all outdated paragraphs in english), while the remaining pages are not shipped (but might be reactivated later). We also attempt to unfuzzy trivial strings (like version number changes or updated markup), so some pages with only editorial changes might actually still reach 80% (and thus being shipped). And if further translators come along, they can much more easily pick up and recomplete/update the pages. So far, we haven't imported any of the pages from manpage-es-extra, but this will happen soon, but too late before the freeze. So there are two possible approaches: 1. If the release-managers agree we will update manpages-l10n in March *with* pages form manpages-es-extra (those which make 80%). Then they are proper in Bullseye. 2. We provide backports for manpages-es, which will include pages from manpages-es-extra (newer, but of course file conflicts). So I suggest to remove manpages-es-extra from Bullseye. This would ease 1. above (i.e. increase the chances for late acceptance in March of a new version with updated pages). Also please consider if the outdated manpages-es-extra still does users a service? Of course, if 1. does not work out, these man pages will only be available via backports, i.e. 2. Mario (the upstream maintainer of manpages-l10n and the primary importer of the pages from manpages-es-extra) is in CC, he can give more details where necessary. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') manpages-es-extra depends on no packages. Versions of packages manpages-es-extra recommends: pn manpages-es Versions of packages manpages-es-extra suggests: ii konqueror [man-browser] 4:20.12.0-4 ii man-db [man-browser] 2.9.3-2 -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Version: 0.8a-19.1+rm Dear submitter, as the package manpages-es-extra 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/984734 The version of this package that was in Debian prior to this removal can still be found using http://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. Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Bug#972184: marked as done (python-crypto: do not release with bullseye)
Your message dated Sat, 03 Jul 2021 19:25:50 + with message-id and subject line Bug#979318: Removed package(s) from unstable has caused the Debian Bug report #972184, regarding python-crypto: do not release with bullseye 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.) -- 972184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-crypto Version: 2.6.1-13.1 Severity: serious Tags: sid bullseye Control: block -1 by 971289 971290 971291 971292 971293 971294 971296 971297 971298 971299 971300 971301 971302 971304 971307 971308 971309 971310 971311 971313 971315 971316 971317 python-crypto is no longer maintained and has ben replaced by pycryptodome. Let's remove it. -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Version: 2.6.1-13.1+rm Dear submitter, as the package python-crypto 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/979318 The version of this package that was in Debian prior to this removal can still be found using http://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. Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Bug#990183: libopenscap8: libopenscap.so.8 is missing from libopenscap8 and is expected by scap-workbench
On Sat, 3 Jul 2021 21:36:53 +0900
Hideki Yamane wrote:
> Mostly done, still have an error with autopkgtest for python3-openscap
Updated. Passed all salsa-ci test as below, and eliminate most of
lintian warning/info.
https://salsa.debian.org/henrich/openscap/-/pipelines/265972
diff -Nru openscap-1.3.4/debian/changelog openscap-1.3.4/debian/changelog
--- openscap-1.3.4/debian/changelog 2021-02-02 00:22:30.0 +0900
+++ openscap-1.3.4/debian/changelog 2021-06-30 16:33:53.0 +0900
@@ -1,3 +1,37 @@
+openscap (1.3.4-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+
+ * Package structure changes
+- Apply soname change (libopenscap8 -> 25)
+- Split libopenscap25 to openscap-scanner, openscap-utils and
+ openscap-common
+- Drop -dbg package and unnecessary lintian-overrides
+ * debian/control
+- Specify https for upstream URL
+- Use debhelper-compat (= 13) to not forget to install necessary files
+ with dh_missing
+- Add missing dependencies: libacl1-dev, libblkid-dev, libglib2.0-dev,
+ libyaml-dev, librpm-dev, libpopt-dev, libprocps-dev, libopendbx1-dev,
+ libxmlsec1-dev, doxygen, graphviz, asciidoc,
+ * Drop unnecessary debian/compat
+ * debian/rules
+- Enable documentation build
+- Enable hardening
+ * Add openscap-common.docs to install HTML docs
+ * debian/openscap-scanner.install
+- Install bash-completion
+ * openscap-utils.install
+- Install autotailor and scap-as-rpm
+ * Add debian/openscap-{scanner,utils}.manpages
+
+ * Trim trailing whitespace.
+ * Update watch file format version to 4.
+ * Set upstream metadata fields: Bug-Database, Bug-Submit.
+ * Drop unnecessary dependency on dh-autoreconf.
+
+ -- Hideki Yamane Wed, 30 Jun 2021 16:33:53 +0900
+
openscap (1.3.4-1) unstable; urgency=medium
* New upstream version 1.3.4
diff -Nru openscap-1.3.4/debian/compat openscap-1.3.4/debian/compat
--- openscap-1.3.4/debian/compat2021-02-02 00:22:30.0 +0900
+++ openscap-1.3.4/debian/compat1970-01-01 09:00:00.0 +0900
@@ -1 +0,0 @@
-11
diff -Nru openscap-1.3.4/debian/control openscap-1.3.4/debian/control
--- openscap-1.3.4/debian/control 2021-02-02 00:22:30.0 +0900
+++ openscap-1.3.4/debian/control 2021-06-30 16:33:53.0 +0900
@@ -2,7 +2,7 @@
Priority: optional
Maintainer: Pierre Chifflier
Uploaders: Philippe Thierry
-Build-Depends: debhelper (>= 13),
+Build-Depends: debhelper-compat (= 13),
cmake,
libpcre3-dev,
libxml2-dev,
@@ -18,19 +18,30 @@
libattr1-dev,
libldap2-dev,
libbz2-dev,
+libacl1-dev,
+libblkid-dev,
+libglib2.0-dev,
+libyaml-dev,
+librpm-dev,
+libpopt-dev,
+libprocps-dev,
+libopendbx1-dev,
+libxmlsec1-dev,
+doxygen, graphviz,
+asciidoc,
pkg-config,
dh-python,
chrpath,
libdbus-1-dev
+Section: admin
X-Python3-Version: >= 3.9
Standards-Version: 4.5.1
-Section: libs
-Homepage: http://www.open-scap.org/
+Homepage: https://www.open-scap.org/
Package: libopenscap-dev
Section: libdevel
Architecture: linux-any
-Depends: libopenscap8 (= ${binary:Version}), ${misc:Depends},
${python3:Depends}, libjs-jquery
+Depends: libopenscap25 (= ${binary:Version}), ${misc:Depends},
${python3:Depends}, libjs-jquery
Description: Set of libraries enabling integration of the SCAP line of
standards
OpenSCAP is a set of open source libraries providing an easier path
for integration of the SCAP line of standards. SCAP is a line of
@@ -48,13 +59,13 @@
.
This package contains the development files for OpenSCAP.
-Package: libopenscap8
+Package: libopenscap25
Section: libs
Architecture: linux-any
-Conflicts: libopenscap0, libopenscap1, libopenscap3
-Replaces: libopenscap0, libopenscap1, libopenscap3
+Conflicts: libopenscap0, libopenscap1, libopenscap3, libopenscap8,
+Replaces: libopenscap0, libopenscap1, libopenscap3, libopenscap8,
Pre-Depends: ${misc:Pre-Depends}
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends},
Description: Set of libraries enabling integration of the SCAP line of
standards
OpenSCAP is a set of open source libraries providing an easier path
for integration of the SCAP line of standards. SCAP is a line of
@@ -69,11 +80,13 @@
* Common Vulnerability Scoring System (CVSS)
* Extensible Configuration Checklist Description Format (XCCDF)
* Open Vulnerability and Assessment Language (OVAL)
+ .
+ This package contains libraries for OpenSCAP.
Package: python3-openscap
Section: python
Architecture: linux-any
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}, libopenscap8
(= ${binary:Version})
+Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}, libopenscap25
(= ${binary:Version})
X-Python3-Version: ${python3:Versions}
Provides: ${python3:Provides}
Description: Set of libraries enabling integration of the SCAP line of
Bug#990458: marked as done (autosize build is broken (throws error is diaspora web console))
Your message dated Sat, 03 Jul 2021 17:48:26 +
with message-id
and subject line Bug#990458: fixed in autosize.js 4.0.2~dfsg1-7
has caused the Debian Bug report #990458,
regarding autosize build is broken (throws error is diaspora web console)
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.)
--
990458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjs-autosize
Severity: grave
Version: 4.0.2~dfsg1-5
Control: affects -1 ruby-rails-assets-autosize,diaspora
I think during transition to babel7 something broke.
This causes diaspora ui to break,
Uncaught ReferenceError: module is not defined
at
main-e074888ae8b7a9cd9ffd9335b56c44872cea8212be3599667e8dd56947c37546.js:3
at $.fn.charCount
(main-e074888ae8b7a9cd9ffd9335b56c44872cea8212be3599667e8dd56947c37546.js:3)
at
main-e074888ae8b7a9cd9ffd9335b56c44872cea8212be3599667e8dd56947c37546.js:3
This leads to,
(t((t={exports:{}}).exports),e.autosize=t.exports)}("undefined"!=typeof
globalThis?globalThis:"undefined"!=typeof
self?self:this,function(e){"use strict";function n(a){function e(){var
e=window.getComputedStyle(a,null);"vertical"===e.resize?a.style.resize="none":"both"===e.resize&&(a.style.resize="horizontal"),r="content-box"===e.boxSizing?-(parseFloat(e.paddingTop)+parseFloat(e.paddingBottom)):parseFloat(e.borderTopWidth)+parseFloat(e.borderBottomWidth),isNaN(r)&&(r=0),i()}function
o(e){var
t=a.style.width;a.style.width="0px",a.offsetWidth,a.style.width=t,a.style.overflowY=e}function
n(e){for(var t=[];e&& instanceof
Element;)e.parentNode.scrollTop&({node:e.parentNode,scrollTop:e.parentNode.scrollTop}),e=e.parentNode;return
t}function s(){var
e,t;0!==a.scrollHeight&&(e=n(a),t=document.documentElement&,a.style.height="",a.style.height=a.scrollHeight+r+"px",l=a.clientWidth,e.forEach(function(e){e.node.scrollTop=e.scrollTop}),t&&(document.documentElement.scrollTop=t))}function
i(){s();var
e=Math.round(parseFloat(a.style.height)),t=window.getComputedStyle(a,null),n="content-box"===t.boxSizing?Math.round(parseFloat(t.height)):a.offsetHeight;if(nr,l,c,u,d;a&&&"TEXTAREA"===a.nodeName&&!p.has(a)&&(c=l=r=null,u=function
u(){a.clientWidth!==l&()},d=function(t){window.removeEventListener("resize",u,!1),a.removeEventListener("input",i,!1),a.removeEventListener("keyup",i,!1),a.removeEventListener("autosize:destroy",d,!1),a.removeEventListener("autosize:update",i,!1),Object.keys(t).forEach(function(e){a.style[e]=t[e]}),p["delete"](a)}.bind(a,{height:a.style.height,resize:a.style.resize,overflowY:a.style.overflowY,overflowX:a.style.overflowX,wordWrap:a.style.wordWrap}),a.addEventListener("autosize:destroy",d,!1),"onpropertychange"in
a&&"oninput"in
a&("keyup",i,!1),window.addEventListener("resize",u,!1),a.addEventListener("input",i,!1),a.addEventListener("autosize:update",i,!1),a.style.overflowX="hidden",a.style.wordWrap="break-word",p.set(a,{destroy:d,update:i}),e())}function
t(e){e=p.get(e);e&()}function
i(e){e=p.get(e);e&()}e["default"]=void 0;var
a,o,p="function"==typeof Map?new Map:(a=[],o=[],{has:function
r(e){return-1o[a.indexOf(e)]},set:function
c(e,t){-1===a.indexOf(e)&&(a.push(e),o.push(t))},"delete":function
u(e){e=a.indexOf(e);-1m(e){return new Event(e,{bubbles:!0})};try{new
Event("test")}catch(d){m=function m(e){var
t=document.createEvent("Event");return t.initEvent(e,!0,!1),t}}var
s=null;"undefined"==typeof window||"function"!=typeof
window.getComputedStyle?((s=function s(e){return
e}).destroy=function(e){return e},s.update=function(e){return
e}):((s=function s(e,t){return
e&(e.length?e:[e],function(e){return
n(e,t)}),e}).destroy=function(e){return
e&(e.length?e:[e],t),e},s.update=function(e){return
e&(e.length?e:[e],i),e}),e["default"]=s,module.exports=exports["default"]}),$.fn.charCount=function(i)
--- End Message ---
--- Begin Message ---
Source: autosize.js
Source-Version: 4.0.2~dfsg1-7
Done: Pirate Praveen
We believe that the bug you reported is fixed in the latest version of
autosize.js, 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 990...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pirate Praveen (supplier of updated autosize.js package)
(This message was generated automatically at their request; if you
believe that there is a problem
Processed: reduce severity
Processing commands for cont...@bugs.debian.org:
> severity 990493 important
Bug #990493 {Done: Pirate Praveen }
[node-babel-plugin-add-module-exports] node-babel-plugin-add-module-exports
broken with babel-preset-env 7
Severity set to 'important' from 'grave'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
990493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#990240: soapyosmo: does not link with boost chrono
On Wed, Jun 23, 2021 at 08:50:13PM +0200, Sebastian Ramacher wrote: > Indeed, soapyosmo does not link with boost chrono. Reassigning > accordingly. The attached patch updates the build to link against boost chrono. However, the patched build alone does not resolve the crash of sdrangelove on my system until I also install the updated hamlib4 from experimental. That is, sdrangelove appears to be affected by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980472. I'm not sure what the plans are for the hamlib4 with respect to Bullseye. Any concerns with an upload of soapyosmo to get us one step closer? The patch/debdiff is attached. Thanks, tony diff -Nru soapyosmo-0.2.5/debian/changelog soapyosmo-0.2.5/debian/changelog --- soapyosmo-0.2.5/debian/changelog 2019-10-20 08:31:08.0 -0700 +++ soapyosmo-0.2.5/debian/changelog 2021-07-03 09:31:09.0 -0700 @@ -1,3 +1,10 @@ +soapyosmo (0.2.5-4) UNRELEASED; urgency=medium + + * Team upload. + * Add boost::chrono to build (Closes: #990240) + + -- tony mancill Sat, 03 Jul 2021 09:31:09 -0700 + soapyosmo (0.2.5-3) unstable; urgency=medium * Upload to unstable diff -Nru soapyosmo-0.2.5/debian/control soapyosmo-0.2.5/debian/control --- soapyosmo-0.2.5/debian/control 2019-10-20 08:29:52.0 -0700 +++ soapyosmo-0.2.5/debian/control 2021-07-03 09:31:09.0 -0700 @@ -7,6 +7,7 @@ debhelper (>= 12), cmake, libboost-dev, +libboost-chrono-dev, libboost-system-dev, libboost-thread-dev, libosmosdr-dev, diff -Nru soapyosmo-0.2.5/debian/patches/boost_chrono.patch soapyosmo-0.2.5/debian/patches/boost_chrono.patch --- soapyosmo-0.2.5/debian/patches/boost_chrono.patch 1969-12-31 16:00:00.0 -0800 +++ soapyosmo-0.2.5/debian/patches/boost_chrono.patch 2021-07-03 09:31:09.0 -0700 @@ -0,0 +1,10 @@ +--- a/CMakeLists.txt b/CMakeLists.txt +@@ -102,6 +102,7 @@ + SET(BOOST_REQUIRED_COMPONENTS + thread + system ++chrono + ) + + if(UNIX AND NOT BOOST_ROOT AND EXISTS "/usr/lib64") diff -Nru soapyosmo-0.2.5/debian/patches/series soapyosmo-0.2.5/debian/patches/series --- soapyosmo-0.2.5/debian/patches/series 2019-09-22 18:12:05.0 -0700 +++ soapyosmo-0.2.5/debian/patches/series 2021-07-03 09:31:09.0 -0700 @@ -1 +1,2 @@ internal-common-library +boost_chrono.patch signature.asc Description: PGP signature
Processed: bug 987360 is forwarded to https://github.com/swaywm/swaylock/issues/181
Processing commands for cont...@bugs.debian.org: > forwarded 987360 https://github.com/swaywm/swaylock/issues/181 Bug #987360 [swaylock] swaylock: Occassional unlock without password entered Set Bug forwarded-to-address to 'https://github.com/swaywm/swaylock/issues/181'. > thanks Stopping processing here. Please contact me if you need assistance. -- 987360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990635: kakoune: Fatal error: unable to bind listen socket Permission denied
Package: kakoune Version: 2020.01.16-2 Followup-For: Bug #990635 Dear Maintainer, thanks for the fast response. Here the tests (on fish): 1. ACK : ls -ld /run/user/1000/kakoune/ drwx--x--x 2 root root 40 Jun 21 18:11 /run/user/1000/kakoune// 2. Changed to user and group and now kakoune (kak cmd) works for me (that only user in the system, personal machine). Thanks for mantaining kakoune for debian (I would love to see kakoune, or at least the ideas, working and its concepts also intregated on other IDEs!) xiscu -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (900, 'testing'), (10, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kakoune depends on: ii libc6 2.31-12 ii libgcc-s1 10.2.1-6 ii libncursesw6 6.2+20201114-2 ii libstdc++610.2.1-6 ii libtinfo6 6.2+20201114-2 kakoune recommends no packages. kakoune suggests no packages. -- no debconf information
Bug#990644: libstorj-dev does not include headers
Package: libstorj-dev Version: 1.0.3-1.1 Severity: serious $ dpkg -L libstorj-dev | sort /. /usr /usr/lib /usr/lib/libstorj.a /usr/lib/libstorj.la /usr/lib/libstorj.so /usr/share /usr/share/doc /usr/share/doc/libstorj-dev /usr/share/doc/libstorj-dev/changelog.Debian.gz /usr/share/doc/libstorj-dev/copyright $
Bug#990575: marked as done (php8.0: CVE-2021-21704 CVE-2021-21705)
Your message dated Sat, 03 Jul 2021 15:19:52 + with message-id and subject line Bug#990575: fixed in php8.0 8.0.8-1 has caused the Debian Bug report #990575, regarding php8.0: CVE-2021-21704 CVE-2021-21705 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.) -- 990575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990575 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php8.0 Version: 8.0.7-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for php8.0, they are fixed in 8.0.8 upstream. CVE-2021-21704[0]: | PHP: firebird issues CVE-2021-21705[1]: | PHP: SSRF bypass in FILTER_VALIDATE_URL If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-21704 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-21704 [1] https://security-tracker.debian.org/tracker/CVE-2021-21705 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-21705 Regards, Salvatore --- End Message --- --- Begin Message --- Source: php8.0 Source-Version: 8.0.8-1 Done: Ondřej Surý We believe that the bug you reported is fixed in the latest version of php8.0, 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 990...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý (supplier of updated php8.0 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: Thu, 01 Jul 2021 17:25:46 +0200 Source: php8.0 Architecture: source Version: 8.0.8-1 Distribution: unstable Urgency: medium Maintainer: Debian PHP Maintainers Changed-By: Ondřej Surý Closes: 990575 Changes: php8.0 (8.0.8-1) unstable; urgency=medium . * New upstream version 8.0.8 (Closes: #990575) + CVE-2021-21705: SSRF bypass in FILTER_VALIDATE_URL + CVE-2021-21704: Stack buffer overflow in firebird_info_cb + CVE-2021-21704: SIGSEGV in firebird_handle_doer + CVE-2021-21704: SIGSEGV in firebird_stmt_execute + CVE-2021-21704: Crash while parsing blob data in firebird_fetch_blob Checksums-Sha1: 1760371c403d04ed81630e89287feaeca302e926 5656 php8.0_8.0.8-1.dsc a3799800e0f25474ce4125789afccba5c2877e0e 10674548 php8.0_8.0.8.orig.tar.xz 7be5ba620f360c83e0aa5671014cbda22fa54394 866 php8.0_8.0.8.orig.tar.xz.asc 58182dc578e4ab2796eee1acf9706b5fb4582928 64364 php8.0_8.0.8-1.debian.tar.xz 479d004496839e65c8aca8e6869923fd220323dd 31837 php8.0_8.0.8-1_amd64.buildinfo Checksums-Sha256: ea61fa5bb2067f51d948b15ecfaf0cda18c37c48bb1015339d35a36bd430d633 5656 php8.0_8.0.8-1.dsc dc1668d324232dec1d05175ec752dade92d29bb3004275118bc3f7fc7cbfbb1c 10674548 php8.0_8.0.8.orig.tar.xz 64129c26bb229c8198a3369a16552d4b28ef16bd6ca25fc46c963fd7370d511e 866 php8.0_8.0.8.orig.tar.xz.asc 8a044dca2cea686c2b3658502e590b4e5703c6e6000fa10fc9702237508d 64364 php8.0_8.0.8-1.debian.tar.xz be83d75edcdfe630a352a8f2c20b7291c3515c1e98986320244e5c65b404703d 31837 php8.0_8.0.8-1_amd64.buildinfo Files: bec1d9fa65dc2d40eaa04e4fd6dbc333 5656 php optional php8.0_8.0.8-1.dsc ff8897b914cb8de9d218bbae877decc7 10674548 php optional php8.0_8.0.8.orig.tar.xz 7cb0329e7db8cc5c7d3985325f5b0124 866 php optional php8.0_8.0.8.orig.tar.xz.asc 842d45806006e817cd6dce2466e39213 64364 php optional php8.0_8.0.8-1.debian.tar.xz e3bcfc05a18c413f74dc04eef95fb310 31837 php optional php8.0_8.0.8-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmDge7NfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u WcLaKRAAq0X4cmrRBeCqOTsXssmjKfy/GHjxQ9UY1o4OgQjSOPQegZSXegZP30fG zbZznDxtQAeVReio45hkVsBLVgU73M1MPyiH/KVCwf0dq8i2XDESonvpakVVmBG1 yIDSBa7zkN6ofW/cLlktzpZsQICs03Vl8e6XlDvP6nz7Q92uVC/jQjTK1VXN7vD/ hISFW2daD8+mq5ajYpW0o+Ak6fdjVqRSurniaJSJMNTcdeaycRvYdg0NePnGOCRj 3+BPFrDzs+e95nz6KZbIbGPKPvI7CalX1MX7N8kgKuAhoPs0HL85J4C9xulOTnth wp6Ozb6/TuCgZqDEFQVygvbe7xo9nQNb4TGcv+3aQ4hSRU3X1Jgu7cLCWgNpKU0t
Bug#990458: libjs-autosize is not fixed by node-babel-plugin-add-module exports update
On Sat, 03 Jul 2021 18:11:20 +0530 Pirate Praveen wrote: > But this is babel 6 to babel 7 migration. The code transpiled by babel > 6 works fine, but moving to babel 7 broke it. One possibility is that the add-module-exports plugin is not compatible with babel 7's umd plugin (@babel/plugin-transform-modules-umd).
Bug#990635: kakoune: Fatal error: unable to bind listen socket Permission denied
On Sat, Jul 03, 2021 at 04:03:07PM +0300, Peter Pentchev wrote: > Control: tag -1 confirmed upstream patch pending > > On Sat, Jul 03, 2021 at 01:39:49PM +0200, xiscu wrote: > > Package: kakoune > > Version: 2020.01.16-2 > > Severity: grave > > Justification: renders package unusable > > > > Dear Maintainer, > > i'm currently unable to use kakoune as it gives a Permission denied error > > on start > > (reinstalling the package hasn't solved the problem). The programm worked > > for me, > > but currently i get: > > > > Fatal error: unable to bind listen socket '/run/user/1000/kakoune/3781950': > > Permission denied > > Hi, > > Yes, you did stumble into an upstream kakoune bug that is fixed in > a later upstream release that is not in Debian yet. The problem is that > Kakoune determines the name of a "user-specific directory to put some > stuff in" using your desktop environment's idea of a "user-specific > directory to put some stuff in", i.e. the XDG_RUNTIME_DIR environment > variable that is set upon the start of your GUI session. However, if you > *first* run `sudo kak something` (and you have told sudo to preserve > the environment variables!) or `su kak something` (and su, by default, > does preserve the environment variables), as the first thing you do > after restarting your computer, before running Kakoune as yourself, > then Kakoune will create its own directory while running as root, and > the directory will not be writable by your actual user account. > So if later you run it from your user account, it will not be able to > put stuff into that directory. This has happened with other tools, too, > and this is actually part of the reason why sudo does NOT preserve all > the environment variables by default. (Note: I'm not saying "don't use > su, use sudo!"; I'm just saying "su does some weird things by default, > sudo tries to prevent some problems by doing *other* weird things by > default, and it is not always the better choice, but it does help > prevent *some* problems") > > I will test and adapt the patches for this problem... FTR, just to have it out there before I upload the bugfix version, the patches in question are: https://github.com/mawww/kakoune/commit/7751c7e188bfc7b2f7e4a70e33032677d84597e5 https://github.com/mawww/kakoune/commit/db9ef82398a08bdf985ff26bfb230fb0cd1221a5 > ...but in the meantime, > a short-term solution for your current situation is: > > 1. Make sure the problem is what I think it is: > >ls -ld /run/user/1000/kakoune > >...and check that it is owned by "root", not by your user account > > 2. Change its owner to your user account: > >sudo chown "$(id -un):$(id -gn)" /run/user/1000/kakoune > >or, if using su: > >su -c "chown '$(id -un)' /run/user/1000/kakoune" ...arrgh, *of course* this should have been: su -c "chown '$(id -un):$(id -gn)' /run/user/1000/kakoune" Sorry about that! Although it would work with just the username, too, since Kakoune would still be able to write into an owner-writable directory. >...of course, you can put your account's username and groupname >directly instead of the "$(id -un):$(id -gn)" construct :) G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: PGP signature
Processed: Re: Bug#990635: kakoune: Fatal error: unable to bind listen socket Permission denied
Processing control commands: > tag -1 confirmed upstream patch pending Bug #990635 [kakoune] kakoune: Fatal error: unable to bind listen socket Permission denied Added tag(s) upstream, confirmed, patch, and pending. -- 990635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990635 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990635: kakoune: Fatal error: unable to bind listen socket Permission denied
Control: tag -1 confirmed upstream patch pending On Sat, Jul 03, 2021 at 01:39:49PM +0200, xiscu wrote: > Package: kakoune > Version: 2020.01.16-2 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > i'm currently unable to use kakoune as it gives a Permission denied error on > start > (reinstalling the package hasn't solved the problem). The programm worked for > me, > but currently i get: > > Fatal error: unable to bind listen socket '/run/user/1000/kakoune/3781950': > Permission denied Hi, Yes, you did stumble into an upstream kakoune bug that is fixed in a later upstream release that is not in Debian yet. The problem is that Kakoune determines the name of a "user-specific directory to put some stuff in" using your desktop environment's idea of a "user-specific directory to put some stuff in", i.e. the XDG_RUNTIME_DIR environment variable that is set upon the start of your GUI session. However, if you *first* run `sudo kak something` (and you have told sudo to preserve the environment variables!) or `su kak something` (and su, by default, does preserve the environment variables), as the first thing you do after restarting your computer, before running Kakoune as yourself, then Kakoune will create its own directory while running as root, and the directory will not be writable by your actual user account. So if later you run it from your user account, it will not be able to put stuff into that directory. This has happened with other tools, too, and this is actually part of the reason why sudo does NOT preserve all the environment variables by default. (Note: I'm not saying "don't use su, use sudo!"; I'm just saying "su does some weird things by default, sudo tries to prevent some problems by doing *other* weird things by default, and it is not always the better choice, but it does help prevent *some* problems") I will test and adapt the patches for this problem, but in the meantime, a short-term solution for your current situation is: 1. Make sure the problem is what I think it is: ls -ld /run/user/1000/kakoune ...and check that it is owned by "root", not by your user account 2. Change its owner to your user account: sudo chown "$(id -un):$(id -gn)" /run/user/1000/kakoune or, if using su: su -c "chown '$(id -un)' /run/user/1000/kakoune" ...of course, you can put your account's username and groupname directly instead of the "$(id -un):$(id -gn)" construct :) That should fix it until the next time you restart your computer, since Kakoune will see that the directory already exists and will not attempt to recreate it. Even after you restart your computer, the problem will only show up if you run Kakoune through su *before* running it from your own user account. ...and I will indeed upload a bugfix version in the next couple of days. Thanks for using Kakoune, and thanks for making its Debian package better by reporting this problem! G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: PGP signature
Bug#990458: libjs-autosize is not fixed by node-babel-plugin-add-module exports update
On Sat, Jul 3, 2021 at 12:29 pm, Akshay S Dinesh wrote: https://stackoverflow.com/questions/33505992/babel-6-changes-how-it-exports-default But most importantly https://kentcdodds.com/blog/misunderstanding-es6-modules-upgrading-babel-tears-and-a-solution But this is babel 6 to babel 7 migration. The code transpiled by babel 6 works fine, but moving to babel 7 broke it. and looks like autosize upstream moved their build system to microbundle (an absctraction of rollup and babel with a set of plugins) which is not packaged yet.
Bug#990183: libopenscap8: libopenscap.so.8 is missing from libopenscap8 and is expected by scap-workbench
On Fri, 2 Jul 2021 00:43:02 +0200
Sebastian Ramacher wrote:
> Yes, but note that this needs to happen soon as it has to pass NEW.
Mostly done, still have an error with autopkgtest for python3-openscap
https://salsa.debian.org/henrich/openscap/-/pipelines/265919
(It doesn't have git repo, so I pushed it under my user at salsa).
It includes fixes a *lot* (sorry at this freeze time, but...), if it should
be shrunk, we can rebase it.
diff -Nru openscap-1.3.4/debian/changelog openscap-1.3.4/debian/changelog
--- openscap-1.3.4/debian/changelog 2021-02-02 00:22:30.0 +0900
+++ openscap-1.3.4/debian/changelog 2021-06-30 16:33:53.0 +0900
@@ -1,3 +1,37 @@
+openscap (1.3.4-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+
+ * Package structure changes
+- Apply soname change (libopenscap8 -> 25)
+- Split libopenscap25 to openscap-scanner, openscap-utils and
+ openscap-common
+- Drop -dbg package and unnecessary lintian-overrides
+ * debian/control
+- Specify https for upstream URL
+- Use debhelper-compat (= 13) to not forget to install necessary files
+ with dh_missing
+- Add missing dependencies: libacl1-dev, libblkid-dev, libglib2.0-dev,
+ libyaml-dev, librpm-dev, libpopt-dev, libprocps-dev, libopendbx1-dev,
+ libxmlsec1-dev, doxygen, graphviz, asciidoc,
+ * Drop unnecessary debian/compat
+ * debian/rules
+- Enable documantation build
+- Enable hardening
+ * Add openscap-common.docs to install HTML docs
+ * debian/openscap-scanner.install
+- Install bash-completion
+ * openscap-utils.install
+- Install autotailor and scap-as-rpm
+ * Add debian/openscap-{scanner,utils}.manpages
+
+ * Trim trailing whitespace.
+ * Update watch file format version to 4.
+ * Set upstream metadata fields: Bug-Database, Bug-Submit.
+ * Drop unnecessary dependency on dh-autoreconf.
+
+ -- Hideki Yamane Wed, 30 Jun 2021 16:33:53 +0900
+
openscap (1.3.4-1) unstable; urgency=medium
* New upstream version 1.3.4
diff -Nru openscap-1.3.4/debian/compat openscap-1.3.4/debian/compat
--- openscap-1.3.4/debian/compat2021-02-02 00:22:30.0 +0900
+++ openscap-1.3.4/debian/compat1970-01-01 09:00:00.0 +0900
@@ -1 +0,0 @@
-11
diff -Nru openscap-1.3.4/debian/control openscap-1.3.4/debian/control
--- openscap-1.3.4/debian/control 2021-02-02 00:22:30.0 +0900
+++ openscap-1.3.4/debian/control 2021-06-30 16:33:53.0 +0900
@@ -2,7 +2,7 @@
Priority: optional
Maintainer: Pierre Chifflier
Uploaders: Philippe Thierry
-Build-Depends: debhelper (>= 13),
+Build-Depends: debhelper-compat (= 13),
cmake,
libpcre3-dev,
libxml2-dev,
@@ -18,19 +18,30 @@
libattr1-dev,
libldap2-dev,
libbz2-dev,
+libacl1-dev,
+libblkid-dev,
+libglib2.0-dev,
+libyaml-dev,
+librpm-dev,
+libpopt-dev,
+libprocps-dev,
+libopendbx1-dev,
+libxmlsec1-dev,
+doxygen, graphviz,
+asciidoc,
pkg-config,
dh-python,
chrpath,
libdbus-1-dev
+Section: admin
X-Python3-Version: >= 3.9
Standards-Version: 4.5.1
-Section: libs
-Homepage: http://www.open-scap.org/
+Homepage: https://www.open-scap.org/
Package: libopenscap-dev
Section: libdevel
Architecture: linux-any
-Depends: libopenscap8 (= ${binary:Version}), ${misc:Depends},
${python3:Depends}, libjs-jquery
+Depends: libopenscap25 (= ${binary:Version}), ${misc:Depends},
${python3:Depends}, libjs-jquery
Description: Set of libraries enabling integration of the SCAP line of
standards
OpenSCAP is a set of open source libraries providing an easier path
for integration of the SCAP line of standards. SCAP is a line of
@@ -48,13 +59,13 @@
.
This package contains the development files for OpenSCAP.
-Package: libopenscap8
+Package: libopenscap25
Section: libs
Architecture: linux-any
-Conflicts: libopenscap0, libopenscap1, libopenscap3
-Replaces: libopenscap0, libopenscap1, libopenscap3
+Conflicts: libopenscap0, libopenscap1, libopenscap3, libopenscap8,
+Replaces: libopenscap0, libopenscap1, libopenscap3, libopenscap8,
Pre-Depends: ${misc:Pre-Depends}
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends},
Description: Set of libraries enabling integration of the SCAP line of
standards
OpenSCAP is a set of open source libraries providing an easier path
for integration of the SCAP line of standards. SCAP is a line of
@@ -69,11 +80,13 @@
* Common Vulnerability Scoring System (CVSS)
* Extensible Configuration Checklist Description Format (XCCDF)
* Open Vulnerability and Assessment Language (OVAL)
+ .
+ This package contains libraries for OpenSCAP.
Package: python3-openscap
Section: python
Architecture: linux-any
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}, libopenscap8
(= ${binary:Version})
+Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}, libopenscap25
(=
Bug#990458: libjs-autosize is not fixed by node-babel-plugin-add-module exports update
https://stackoverflow.com/questions/33505992/babel-6-changes-how-it-exports-default But most importantly https://kentcdodds.com/blog/misunderstanding-es6-modules-upgrading-babel-tears-and-a-solution 03-Jul-2021 16:56:56 Pirate Praveen : > Control: reopen -1 > > On Wed, 30 Jun 2021 22:40:13 +0530 Pirate Praveen > wrote: >> and this is working with diaspora. Thanks again for tracking down the >> issue. > > Looks like I was wrong here and it is still failing with libjs-autosize built > with latest node-babel-plugin-add-module-exports. > > You can see this on browser console of > https://diaspora.publicvm.com/statistics (setup by Rojin for testing).
Bug#990513: texlive-extra-utils: make4ht unusable because make4ht-logging.lua is missing
On Sat, Jul 03, 2021 at 12:41:12PM +0200, Janusz S. Bień wrote: > On Sat, Jul 03 2021 at 11:51 +03, Adrian Bunk wrote: > > On Thu, Jul 01, 2021 at 08:55:36AM +0200, Hilmar Preuße wrote: > > [...] > > > This locally installed more recent version of make4ht requires something > > that is not required by the version of make4ht in buster. > > What makes you think so? The commit I linked to added the requirement for make4ht-logging.lua > Janusz cu Adrian
Bug#990635: kakoune: Fatal error: unable to bind listen socket Permission denied
Package: kakoune Version: 2020.01.16-2 Severity: grave Justification: renders package unusable Dear Maintainer, i'm currently unable to use kakoune as it gives a Permission denied error on start (reinstalling the package hasn't solved the problem). The programm worked for me, but currently i get: Fatal error: unable to bind listen socket '/run/user/1000/kakoune/3781950': Permission denied Thanks in advanve, xiscu -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (900, 'testing'), (10, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kakoune depends on: ii libc6 2.31-12 ii libgcc-s1 10.2.1-6 ii libncursesw6 6.2+20201114-2 ii libstdc++610.2.1-6 ii libtinfo6 6.2+20201114-2 kakoune recommends no packages. kakoune suggests no packages. -- no debconf information
Processed: libjs-autosize is not fixed by node-babel-plugin-add-module exports update
Processing control commands:
> reopen -1
Bug #990458 {Done: Pirate Praveen } [libjs-autosize]
autosize build is broken (throws error is diaspora web console)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions autosize.js/4.0.2~dfsg1-6.
--
990458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#990458: libjs-autosize is not fixed by node-babel-plugin-add-module exports update
Control: reopen -1 On Wed, 30 Jun 2021 22:40:13 +0530 Pirate Praveen wrote: > and this is working with diaspora. Thanks again for tracking down the > issue. Looks like I was wrong here and it is still failing with libjs-autosize built with latest node-babel-plugin-add-module-exports. You can see this on browser console of https://diaspora.publicvm.com/statistics (setup by Rojin for testing).
Processed: bug 989792 is forwarded to https://github.com/canonical/dqlite/issues/315
Processing commands for cont...@bugs.debian.org: > forwarded 989792 https://github.com/canonical/dqlite/issues/315 Bug #989792 [src:dqlite] dqlite assumes a kernel configured with 4kB page size Set Bug forwarded-to-address to 'https://github.com/canonical/dqlite/issues/315'. > thanks Stopping processing here. Please contact me if you need assistance. -- 989792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: golang-github-sylabs-sif: diff for NMU version 1.0.9-2.1
Processing control commands: > tags 983583 + patch Bug #983583 [src:golang-github-sylabs-sif] FTBFS on mips64el and mipsel Added tag(s) patch. -- 983583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983583 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 988707
Processing commands for cont...@bugs.debian.org:
> tags 988707 + fixed
Bug #988707 {Done: A. Maitland Bottoms }
[src:qthid-fcd-controller] qthid-fcd-controller: triggers lintian autoreject
tag 'bogus-mail-host'
Added tag(s) fixed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
988707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#983583: golang-github-sylabs-sif: diff for NMU version 1.0.9-2.1
Control: tags 983583 + patch
Dear maintainer,
I've prepared an NMU for golang-github-sylabs-sif (versioned as
1.0.9-2.1) and uploaded it to DELAYED/2. Please feel free to tell
me if I should cancel it.
cu
Adrian
diff -Nru golang-github-sylabs-sif-1.0.9/debian/changelog golang-github-sylabs-sif-1.0.9/debian/changelog
--- golang-github-sylabs-sif-1.0.9/debian/changelog 2020-02-28 09:16:12.0 +0200
+++ golang-github-sylabs-sif-1.0.9/debian/changelog 2021-07-03 13:32:11.0 +0300
@@ -1,3 +1,11 @@
+golang-github-sylabs-sif (1.0.9-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add fix from YunQiang Su for architecture-dependent behaviour
+in mmap() prot. (Closes: #983583)
+
+ -- Adrian Bunk Sat, 03 Jul 2021 13:32:11 +0300
+
golang-github-sylabs-sif (1.0.9-2) unstable; urgency=medium
* Build-Depends correction (Closes: #951538).
diff -Nru golang-github-sylabs-sif-1.0.9/debian/patches/load-mmap.patch golang-github-sylabs-sif-1.0.9/debian/patches/load-mmap.patch
--- golang-github-sylabs-sif-1.0.9/debian/patches/load-mmap.patch 1970-01-01 02:00:00.0 +0200
+++ golang-github-sylabs-sif-1.0.9/debian/patches/load-mmap.patch 2021-07-03 13:32:11.0 +0300
@@ -0,0 +1,16 @@
+Description: Fix architecture-dependent behaviour in mmap() prot
+Author: YunQiang Su
+Bug-Debian: https://bugs.debian.org/983583
+Forwarded: not-needed (https://github.com/sylabs/sif/commit/5ef4cc53eb9bf04e79fb96428daedd5f576fb71d)
+
+--- golang-github-sylabs-sif-1.0.9.orig/pkg/sif/load.go
golang-github-sylabs-sif-1.0.9/pkg/sif/load.go
+@@ -92,7 +92,7 @@ func (fimg *FileImage) mapFile(rdonly bo
+ flags := syscall.MAP_PRIVATE
+
+ if !rdonly {
+- prot = syscall.PROT_WRITE
++ prot = syscall.PROT_WRITE | syscall.PROT_READ
+ flags = syscall.MAP_SHARED
+ }
+
diff -Nru golang-github-sylabs-sif-1.0.9/debian/patches/series golang-github-sylabs-sif-1.0.9/debian/patches/series
--- golang-github-sylabs-sif-1.0.9/debian/patches/series 1970-01-01 02:00:00.0 +0200
+++ golang-github-sylabs-sif-1.0.9/debian/patches/series 2021-07-03 13:32:11.0 +0300
@@ -0,0 +1 @@
+load-mmap.patch
Bug#990513: marked as done (texlive-extra-utils: make4ht unusable because make4ht-logging.lua is missing)
Your message dated Sat, 3 Jul 2021 11:51:10 +0300 with message-id <20210703085110.GA21983@localhost> and subject line Re: Bug#990513: texlive-extra-utils: make4ht unusable because make4ht-logging.lua is missing has caused the Debian Bug report #990513, regarding texlive-extra-utils: make4ht unusable because make4ht-logging.lua is missing 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.) -- 990513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990513 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: texlive-extra-utils Version: 2018.20190227-2 Severity: grave Dear Maintainer, Because of make4ht prerequisits texlive-extra-utils should depend on texlive-luatex which should contain make4ht-logging.lua but this is not the case, at least in buster and bullseye. Cf. https://github.com/michal-h21/make4ht/issues/47 for the upstream discussion. Regards JSB -- System Information: Debian Release: 10.10 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-17-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages texlive-extra-utils depends on: ii libunicode-linebreak-perl 0.0.20190101-1 ii python 2.7.16-1 ii tex-common 6.11 ii texlive-base 2018.20190227-2 ii texlive-binaries 2018.20181218.49446-1 ii texlive-latex-base 2018.20190227-2 Versions of packages texlive-extra-utils recommends: ii ghostscript9.27~dfsg-2+deb10u4 ii libfile-homedir-perl 1.004-1 ii liblog-log4perl-perl 1.49-1 ii libyaml-tiny-perl 1.73-1 ii ruby 1:2.5.1 ii texlive-latex-recommended 2018.20190227-2 Versions of packages texlive-extra-utils suggests: pn chktex pn dvidvi pn dvipng pn fragmaster pn lacheck pn latexdiff ii latexmk 1:4.61-0.1 pn purifyeps pn xindy Versions of packages tex-common depends on: ii dpkg 1.19.7 ii ucf 3.0038+nmu1 Versions of packages tex-common suggests: ii debhelper 12.1.1 Versions of packages texlive-extra-utils is related to: ii tex-common6.11 ii texlive-binaries 2018.20181218.49446-1 -- no debconf information -- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien --- End Message --- --- Begin Message --- On Thu, Jul 01, 2021 at 08:55:36AM +0200, Hilmar Preuße wrote: > Control: tags -1 + buster > > Am 01.07.2021 um 07:42 teilte Janusz S. Bień mit: > > Hi Janusz, > > > Because of make4ht prerequisits texlive-extra-utils should depend on > > texlive-luatex which should contain make4ht-logging.lua but this is not > > the case, at least in buster and bullseye. > > > > Cf. https://github.com/michal-h21/make4ht/issues/47 for the upstream > > discussion. > > > AFAICT the requested file is in texlive-extra-utils itself: > > hille@sid:~ $ apt-file search make4ht-logging.lua > texlive-extra-utils: > /usr/share/texlive/texmf-dist/scripts/make4ht/make4ht-logging.lua > > This is for Debian unstable / testing. So in my eyes the issue is for > buster. I tag it buster for now, but I have doubt that we'll make attempts > to fix it. This is not a bug in the Debian package: Upstream make4ht gained th dependency after the release of buster: https://github.com/michal-h21/make4ht/commit/902313dbcf17d08fa588d585f9895fa07f97135b Quoting the relevant part from the linked upstream discussion: make4ht installed locally: jsbien@JSBbuster:~/work/make4ht$ which make4ht /home/jsbien/.local/bin/make4ht This locally installed more recent version of make4ht requires something that is not required by the version of make4ht in buster. This is not something that is (or can be) supported by the Debian packages in buster. > Hilmar cu Adrian--- End Message ---
