Bug#1006596: marked as done (libxrt-utils: ships /usr/bin/mpd, already provided by mpd)
Your message dated Tue, 31 May 2022 05:20:58 + with message-id and subject line Bug#1006596: fixed in xrt 202020.2.8.832+dfsg-2 has caused the Debian Bug report #1006596, regarding libxrt-utils: ships /usr/bin/mpd, already provided by mpd 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.) -- 1006596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libxrt-utils Version: 202020.2.8.832+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Preparing to unpack .../libxrt-utils_202020.2.8.832+dfsg-1_amd64.deb ... Unpacking libxrt-utils (202020.2.8.832+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/libxrt-utils_202020.2.8.832+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/mpd', which is also in package mpd 0.23.5-1+b1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libxrt-utils_202020.2.8.832+dfsg-1_amd64.deb cheers, Andreas mpd=0.23.5-1+b1_libxrt-utils=202020.2.8.832+dfsg-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: xrt Source-Version: 202020.2.8.832+dfsg-2 Done: Nobuhiro Iwamatsu We believe that the bug you reported is fixed in the latest version of xrt, 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 1006...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nobuhiro Iwamatsu (supplier of updated xrt 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: Tue, 31 May 2022 10:39:44 +0900 Source: xrt Binary: libxrt-dev libxrt-utils libxrt-utils-dbgsym libxrt1 libxrt1-dbgsym Architecture: source amd64 Version: 202020.2.8.832+dfsg-2 Distribution: experimental Urgency: medium Maintainer: Debian Xilinx Package Maintainers Changed-By: Nobuhiro Iwamatsu Description: libxrt-dev - Xilinx Runtime (XRT) - development files libxrt-utils - Xilinx Runtime (XRT) - runtime -- utilities libxrt1- Xilinx Runtime (XRT) - runtime libraries Closes: 1006524 1006596 1007184 1008476 Changes: xrt (202020.2.8.832+dfsg-2) experimental; urgency=medium . * Fix reproducible builds in version.h (Closes: #1007184) d/patches/0008-src-CMake-version.cmake-Consistently-use-UTC-timezon.patch. Thanks to Vagrant Cascadian . * Fix package long descriptions. (Closes: #1008476, #1006524) * Rename /usr/bin/mpd to /usr/bin/xrt_mpd. (Closes: #1006596) Checksums-Sha1: dd02d37ae69280447624aeda538bcb23edcd2289 2499 xrt_202020.2.8.832+dfsg-2.dsc c9a382c2fa6afea175f9d13a4d5b01bc56dfb600 12144 xrt_202020.2.8.832+dfsg-2.debian.tar.xz 6ca54c81c068ff53285633ba49979f60dd445a1e 102164 libxrt-dev_202020.2.8.832+dfsg-2_amd64.deb d15d2ada18291ae5fd32a38c1603fc04d2023a24 3063936 libxrt-utils-dbgsym_202020.2.8.832+dfsg-2_amd64.deb 31514c4b42adca654ac162911bd416177fa6da46 16 libxrt-utils_202020.2.8.832+dfsg-2_amd64.deb 6121d62172967593d9f88e44356a4fab75100713 44795272 libxrt1-dbgsym_202020.2.8.832+dfsg-2_amd64.deb 30c9f1907236cbb47aa82383f6ac42f8245a98b5 2007824 libxrt1_202020.2.8.832+dfsg-2_amd64.deb c231bd82ee0e64776fc21f12d98df95beba74bb7 9880 xrt_202020.2.8.832+dfsg-2_amd64.buildinfo Checksums-Sha256: 91898f22e338580d37afc7daede951325c0b0cb6de6698532989c42aac77efe9 2499 xrt_202020.2.8.832+dfsg-2.dsc 33d4c6f222b44e9690f8875c3e4245bd332e5a4358b9048598fb580b943e5a39 12144 xrt_202020.2.8.832+dfsg-2.debian.tar.xz 6d884c31ab6e0a3c1eb32349ac6726fa9c064adb82752b713712864580a47a95 102164 libxrt-dev_202020.2.8.832+dfsg-2_amd64.deb 48503dda5ba32429dad38e271465d93226b33b1507bdd9d2666096b924157fd9 3063936 libxrt-utils-dbgsym_202020.2.8.832+dfsg-2_amd64.deb 77e0dda8fa2cf447bf628a6b54a1c1de42f7cea81aa3a375b7d61472ea24d746 16 libxrt-utils_202020.2.8.832+dfsg-2_amd64.deb 597ccfec5682e5eebbb346cba4e45b253db52f7599967778774f678aa39b60ca 44795272
Bug#1009739: fixed in yade 2022.01a-8
Hi Bernhard, Thank you very much for this information and for fixing it! I have just uploaded boost1.74_1.74.0-15 with this fix and will revert the workaround in yade! Best regards Anton
Bug#1012154: binfmt-support.service errors with "unable to close /proc/sys/fs/binfmt_misc/register: File exists"
Package: binfmt-support Version: 2.2.1-2 Severity: grave Justification: renders package unusable Dear Maintainer, The binfmt-support service fails to start, with the following output: systemd[1]: Starting Enable support for additional executable binary formats... update-binfmts[536]: update-binfmts: warning: unable to close /proc/sys/fs/binfmt_misc/register: File exists update-binfmts[536]: update-binfmts: warning: unable to close /proc/sys/fs/binfmt_misc/register: File exists update-binfmts[536]: update-binfmts: warning: unable to close /proc/sys/fs/binfmt_misc/register: File exists update-binfmts[536]: update-binfmts: exiting due to previous errors systemd[1]: binfmt-support.service: Main process exited, code=exited, status=2/INVALIDARGUMENT systemd[1]: binfmt-support.service: Failed with result 'exit-code'. systemd[1]: Failed to start Enable support for additional executable binary formats. Best, Facundo -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-3-amd64 (SMP w/6 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages binfmt-support depends on: ii libc6 2.33-7 ii libpipeline1 1.5.6-1 ii lsb-base 11.2 binfmt-support recommends no packages. binfmt-support suggests no packages. -- no debconf information
Processed: tagging 1010451
Processing commands for cont...@bugs.debian.org: > tags 1010451 + pending Bug #1010451 [src:gdb-avr] gdb-avr: Missing build dependency on libgmp-dev Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1010451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997767: marked as done (open-ath9k-htc-firmware: FTBFS: patching fails)
Your message dated Mon, 30 May 2022 20:13:51 + with message-id and subject line open-ath9k-htc-firmware FTBFS fixed has caused the Debian Bug report #997767, regarding open-ath9k-htc-firmware: FTBFS: patching fails 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.) -- 997767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: open-ath9k-htc-firmware Version: 1.4.0-106-gc583009+dfsg1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > mkdir -p /<>/cross-toolchain/binutils-source > cd /<>/cross-toolchain/binutils-source && \ > tar --strip-components=1 -xf /usr/src/binutils/binutils-*.tar.* && \ > patch -p1 < /<>/local/patches/binutils-2.34_fixup.patch && > \ > patch -p1 < /<>/local/patches/binutils.patch && \ > autoreconf --install --force && \ > rm -rf ./zlib/ > patching file bfd/xtensa-modules.c > patching file bfd/xtensa-modules.c > Hunk #12 FAILED at 252. > Hunk #15 FAILED at 20799. > Hunk #16 FAILED at 20894. > Hunk #21 succeeded at 21121 with fuzz 1. > Hunk #22 FAILED at 21141. > 4 out of 24 hunks FAILED -- saving rejects to file bfd/xtensa-modules.c.rej > patching file include/xtensa-config.h > Hunk #1 succeeded at 43 (offset -1 lines). > Hunk #2 succeeded at 55 (offset -1 lines). > Hunk #3 succeeded at 99 (offset -1 lines). > Hunk #4 succeeded at 113 (offset -1 lines). > Hunk #5 succeeded at 151 (offset -1 lines). > make[1]: *** [debian/cross-toolchain.mk:33: > /<>/cross-toolchain/stamp-binutils_unpack] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/open-ath9k-htc-firmware_1.4.0-106-gc583009+dfsg1-1_unstable.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. --- End Message --- --- Begin Message --- Version: 1.4.0-108-gd856466+dfsg1-1 Whoops, forgot to close this in the changelog. Anyway, a new upload that doesn't require passing through NEW was just uploaded, hence closing this bug. signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#1012148: haskell-hslua-module-text_0.2.1-2.1_mips64el-buildd.changes REJECTED
Source: haskell-hslua-module-text Severity: serious Version: 0.2.1-2.1 On 2022-05-30 15:34, Debian FTP Masters wrote: > libghc-hslua-module-text-dev_0.2.1-2.1_mips64el.deb: has 1 file(s) with a > timestamp too far in the past: > usr/share/doc/libghc-hslua-module-text-dev/changelog.gz (Thu Jan 1 > 00:00:00 1970) > > > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > >
Bug#1012146: haskell-hslua-module-system_0.2.1-2.1_mips64el-buildd.changes REJECTED
Source: haskell-hslua-module-system Severity: serious Version: 0.2.1-2.1 On 2022-05-28 15:18, Debian FTP Masters wrote: > libghc-hslua-module-system-dev_0.2.1-2.1_mips64el.deb: has 1 file(s) with a > timestamp too far in the past: > usr/share/doc/libghc-hslua-module-system-dev/changelog.gz (Thu Jan 1 > 00:00:00 1970) > > > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > >
Processed: bug 1011730 is forwarded to https://github.com/rototor/pdfbox-graphics2d/issues/43
Processing commands for cont...@bugs.debian.org: > forwarded 1011730 https://github.com/rototor/pdfbox-graphics2d/issues/43 Bug #1011730 [src:libpdfbox-graphics2d-java] libpdfbox-graphics2d-java: FTBFS: dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode test returned exit code 1 Set Bug forwarded-to-address to 'https://github.com/rototor/pdfbox-graphics2d/issues/43'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1011730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011730 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1012138
Processing commands for cont...@bugs.debian.org: > tags 1012138 + upstream Bug #1012138 [src:sox] CVE-2021-40426 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006258: marked as done (rstudio crashes)
Your message dated Mon, 30 May 2022 21:35:51 +0200 with message-id <8c4d06d0-18f6-b1cb-6763-5447d4539...@debian.org> and subject line Re: rstudio crashes has caused the Debian Bug report #1006258, regarding rstudio crashes 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.) -- 1006258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rstudio Version: 2022.02.0+443 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: l...@castermans.org Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? upon crash a white screen is shown, need to KILL it; fully reproducible * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'experimental'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-rc3-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE=nl Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages rstudio depends on: ii libc6 2.34-0experimental3 ii libclang-dev1:13.0-54 ii libedit23.1-20210910-1 ii libpq5 14.2-1 ii libsqlite3-03.37.2-2 ii libssl1.1 1.1.1m-1 ii libxkbcommon-x11-0 1.4.0-1 Versions of packages rstudio recommends: ii r-base 4.1.2-2 rstudio suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- On Tue, 22 Feb 2022 07:46:46 +0100 Luc Castermans wrote: Package: rstudio Version: 2022.02.0+443 Hi, rstudio is not part of Debian (and neither Ubuntu), please report any issues you encounter directly to the provider of this package. Thanks, Andreas--- End Message ---
Bug#1012130: [Pkg-javascript-devel] Bug#1012130: node-source-map: Browser bundle unusable
Strangely --target node works Le 30 mai 2022 21:01:42 GMT+02:00, Pirate Praveen a écrit : > > >On തി, മേയ് 30 2022 at 07:45:32 വൈകു +02:00:00 +02:00:00, Yadd > wrote: >> Package: node-source-map >> Version: 0.7.0++dfsg2+really.0.6.1-10 >> Severity: serious >> Tags: ftbfs >> Justification: FTBFS >> Control: affects -1 src:node-terser src:ruby-terser src:ruby-uglifier >> >> Build with webpack 5 produces an unusable bundle. See for example >> https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-terser/22213688/log.gz >> >> Error is "self is not defined". This can be fixed using a --target >> option. >> >I tried with --target web, but that does not seem to work. Can you try? > >Also tried --mode production, and > >globalObject: 'this' in output section of webpack.config.js > > > -- Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
Processed: reassign 1012097 to libnss-nis, tagging 1012097
Processing commands for cont...@bugs.debian.org: > reassign 1012097 libnss-nis 3.1-4 Bug #1012097 [libnssswitch-nis] NIS broken in sid Warning: Unknown package 'libnssswitch-nis' Bug reassigned from package 'libnssswitch-nis' to 'libnss-nis'. No longer marked as found in versions 3.1-4. Ignoring request to alter fixed versions of bug #1012097 to the same values previously set Bug #1012097 [libnss-nis] NIS broken in sid Marked as found in versions libnss-nis/3.1-4. > tags 1012097 + sid bookworm Bug #1012097 [libnss-nis] NIS broken in sid Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012138: CVE-2021-40426
Source: sox Version: 14.4.2+git20190427-3 Severity: grave Tags: security X-Debbugs-Cc: Debian Security Team https://talosintelligence.com/vulnerability_reports/TALOS-2021-1434 The report states that upstream was notified, but we need to figure out whether this was addressed by upstream already or not (and if so, in which commit) Cheers, Moritz
Bug#1011793:
Looks like it's a python bug: https://github.com/python/cpython/issues/91257
Processed: bug 1011793 is forwarded to https://github.com/tlsfuzzer/python-ecdsa/issues/285
Processing commands for cont...@bugs.debian.org:
> forwarded 1011793 https://github.com/tlsfuzzer/python-ecdsa/issues/285
Bug #1011793 [src:python-ecdsa] python-ecdsa: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit
code 13
Set Bug forwarded-to-address to
'https://github.com/tlsfuzzer/python-ecdsa/issues/285'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1011793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1011793:
Upstream issue: https://github.com/tlsfuzzer/python-ecdsa/issues/285
Processed: node-source-map: Browser bundle unusable
Processing control commands: > affects -1 src:node-terser src:ruby-terser src:ruby-uglifier Bug #1012130 [node-source-map] node-source-map: Browser bundle unusable Added indication that 1012130 affects src:node-terser, src:ruby-terser, and src:ruby-uglifier -- 1012130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012130 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012130: node-source-map: Browser bundle unusable
Package: node-source-map Version: 0.7.0++dfsg2+really.0.6.1-10 Severity: serious Tags: ftbfs Justification: FTBFS Control: affects -1 src:node-terser src:ruby-terser src:ruby-uglifier Build with webpack 5 produces an unusable bundle. See for example https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-terser/22213688/log.gz Error is "self is not defined". This can be fixed using a --target option.
Bug#1011146: Autoremoval of non related package
Hello, I received an email for auto removal for source-highlight which has nothing to do with nvidia-graphics-drivers. If my assumption is wrong, please let me know what sort of changes you would expect me to make. Regards, Kartik
Processed: [bts-link] source package src:osk-sdl
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:osk-sdl > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1006642 (http://bugs.debian.org/1006642) > # Bug title: osk-sdl: autopkgtest failure (with gcc-12) > # * https://gitlab.com/postmarketOS/osk-sdl/-/issues/143 > # * remote status changed: opened -> closed > # * closed upstream > tags 1006642 + fixed-upstream Bug #1006642 [src:osk-sdl] osk-sdl: autopkgtest failure (with gcc-12) Added tag(s) fixed-upstream. > usertags 1006642 - status-opened Usertags were: status-opened. There are now no usertags set. > usertags 1006642 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1006642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:pyml
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:pyml > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1009430 (http://bugs.debian.org/1009430) > # Bug title: pyml: FTBFS: Test 'run file with filename' ... fails (?) > # * https://github.com/thierry-martinez/pyml/pull/75 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1009430 + fixed-upstream Bug #1009430 [src:pyml] pyml: FTBFS: Test 'run file with filename' ... fails (?) Added tag(s) fixed-upstream. > usertags 1009430 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1009430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011816: [Pkg-javascript-devel] Bug#1004471: Update node-terser to latest upstream (node-terser 5)
On 30/05/2022 18:21, Yadd wrote: On 30/05/2022 14:37, Yadd wrote: There is something broken with cjs/mjs. I'm going to fix that. Cheers, Yadd Le Lundi, Mai 30, 2022 13:07 CEST, Jonas Smedegaard a écrit: Quoting Yadd (2022-05-30 12:05:41) here is a debdiff (debian part only) to update terser to version 5.13.1. This fixes also #1011816 (FTBFS) Thanks! It seems you are sharing that patch as a proposal, as you only pushed some parts of it to git. ...and I disagree with some minor parts of it, so that's good: I will take a look at it, and when I get a better sense of it reply back here in more detail which parts I disagree with. Hi Jonas, I fixed: * debdiff: diff from debian/latest (still only debian/ directory) * commonjs use Now autopkgtest passed except pure browser test (command2): webpack produces a bundle unusable for domino test, maybe for browser... "webpack produces..." => in node-source-map ["self is not defined"] I think mocha test could be added to autopkgtest now Cheers, Yadd
Bug#1011816: [Pkg-javascript-devel] Bug#1004471: Update node-terser to latest upstream (node-terser 5)
On 30/05/2022 14:37, Yadd wrote:
There is something broken with cjs/mjs. I'm going to fix that.
Cheers,
Yadd
Le Lundi, Mai 30, 2022 13:07 CEST, Jonas Smedegaard a écrit:
Quoting Yadd (2022-05-30 12:05:41)
here is a debdiff (debian part only) to update terser to version 5.13.1.
This fixes also #1011816 (FTBFS)
Thanks!
It seems you are sharing that patch as a proposal, as you only pushed
some parts of it to git.
...and I disagree with some minor parts of it, so that's good: I will
take a look at it, and when I get a better sense of it reply back here
in more detail which parts I disagree with.
Hi Jonas,
I fixed:
* debdiff: diff from debian/latest (still only debian/ directory)
* commonjs use
Now autopkgtest passed except pure browser test (command2): webpack
produces a bundle unusable for domino test, maybe for browser...
I think mocha test could be added to autopkgtest now
Cheers,
Yadddiff --git a/debian/changelog b/debian/changelog
index bf31486e..af5ba64d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,20 @@
+node-terser (5.13.1-1) UNRELEASED; urgency=medium
+
+ * Team upload
+ * Declare compliance with policy 4.6.1
+ * Fix debian/rules for parallel build (manpage needs bundle file)
+ * New upstream version 5.13.1
+ * Refresh patches
+ * Add patches to fix test
+ * Add links during build
+ * Render mocha test required
+ * Update nodejs dependency to nodejs:any
+ * Fix commander patch
+ * Use pkg-js-autopkgtest in require test because type=module
+ * Fix commonjs usage
+
+ -- Yadd Mon, 30 May 2022 18:14:52 +0200
+
node-terser (4.8.0-2) experimental; urgency=medium
* update copyright info:
diff --git a/debian/clean b/debian/clean
index 479d4e14..51146a4a 100644
--- a/debian/clean
+++ b/debian/clean
@@ -1,5 +1,6 @@
debian/js/
debian-man/
dist/bundle*
+node_modules/
README.html
README.txt
diff --git a/debian/control b/debian/control
index e4610eca..929149f3 100644
--- a/debian/control
+++ b/debian/control
@@ -78,7 +78,7 @@ Architecture: all
Depends:
node-commander (>= 7),
node-terser (= ${source:Version}),
- nodejs,
+ nodejs:any,
${misc:Depends},
Recommends:
node-source-map-support,
diff --git a/debian/libjs-terser.links b/debian/libjs-terser.links
index 73aef070..bfd0d2ae 100644
--- a/debian/libjs-terser.links
+++ b/debian/libjs-terser.links
@@ -1 +1 @@
-usr/share/nodejs/terser/dist/bundle.min.js
usr/share/javascript/terser/bundle.js
+usr/share/nodejs/terser/dist/bundle.min.cjs
usr/share/javascript/terser/bundle.js
diff --git a/debian/node-terser.install b/debian/node-terser.install
index 338e037d..9fe7de5a 100644
--- a/debian/node-terser.install
+++ b/debian/node-terser.install
@@ -1,2 +1,2 @@
package.json lib tools main.js /usr/share/nodejs/terser
-dist/bundle.min.js /usr/share/nodejs/terser/dist
+dist/bundle.min.cjs /usr/share/nodejs/terser/dist
diff --git a/debian/patches/1001_commander.patch
b/debian/patches/1001_commander.patch
index abcf1fa5..24717184 100644
--- a/debian/patches/1001_commander.patch
+++ b/debian/patches/1001_commander.patch
@@ -4,231 +4,219 @@ Description: support node module commander release 8
(and possibly v7 as well),
at the expense of compatibility with older releases of commander.
Author: Yadd
-Last-Update: 2022-02-06
+Last-Update: 2022-05-30
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
a/bin/terser
-+++ b/bin/terser
-@@ -25,6 +25,15 @@
- program.version(info.name + " " + info.version);
- program.parseArgv = program.parse;
- program.parse = undefined;
-+var argv = [];
-+process.argv.forEach(function(arg){
-+ if(arg.match(/^-([pcmbode]+)$/)) {
-+argv = argv.concat(RegExp.$1.split('').map(s => { return '-'+s }));
-+ }
-+ else argv.push(arg);
-+});
-+process.argv = argv;
-+
- if (process.argv.includes("ast")) program.helpInformation = describe_ast;
- else if (process.argv.includes("options")) program.helpInformation =
function() {
- var text = [];
+
+--- a/lib/cli.js
b/lib/cli.js
+@@ -26,6 +26,15 @@
+ program.parseArgv = program.parse;
+ program.parse = undefined;
+
++var argv = [];
++process.argv.forEach(function(arg){
++ if(arg.match(/^-([pcmbode]+)$/)) {
++argv = argv.concat(RegExp.$1.split('').map(s => { return '-'+s }));
++ }
++ else argv.push(arg);
++});
++process.argv = argv;
++
+ if (process.argv.includes("ast")) program.helpInformation = describe_ast;
+ else if (process.argv.includes("options")) program.helpInformation =
function() {
+ var text = [];
@@ -62,10 +71,11 @@
- program.option("--warn", "Print warning messages.");
- program.option("--wrap ", "Embed everything as a function with
“exports” corresponding to “name” globally.");
- program.arguments("[files...]").parseArgv(process.argv);
--if (program.configFile) {
--options = JSON.parse(read_file(program.configFile));
-+const opts = program.opts();
-+if (opts.configFile) {
-+options =
Bug#1012125: astroquery: Autopkgtests failure due to trying to write to /usr/lib
Source: astroquery
Version: 0.4.6+dfsg-2
Severity: serious
Justification: RT
X-Debbugs-Cc: simon.cho...@canonical.com
Hi,
The autopkgtests for 0.4.6+dfsg-2 fail with attempts to write to
locations in /usr/lib, preventing the package from migrating to testing.
>From
>https://ci.debian.net/data/autopkgtest/unstable/amd64/a/astroquery/21778465/log.gz
> :
=== short test summary info
FAILED
../../../../usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py::TestESAHubble::test_download_product_by_calibration
FAILED
../../../../usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py::TestESAHubble::test_download_product_by_product_type
FAILED
../../../../usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py::TestESAHubble::test_get_postcard
FAILED
../../../../usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py::TestESAHubble::test_cone_search
FAILED
../../../../usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py::TestESAHubble::test_cone_search_coords
FAILED
../../../../usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py::TestESAHubble::test_get_artifact
= 6 failed, 973 passed, 588 skipped, 2 xfailed, 150 warnings in 53.54s =
Details of the first failure:
__ TestESAHubble.test_download_product_by_calibration __
self =
def test_download_product_by_calibration(self):
parameters = {'observation_id': "J6FL25S4Q",
'cal_level': "RAW",
'filename': "J6FL25S4Q.vot",
'verbose': True}
ehst = ESAHubbleClass(self.get_dummy_tap_handler())
> ehst.download_product(observation_id=parameters['observation_id'],
calibration_level=parameters['cal_level'],
filename=parameters['filename'],
verbose=parameters['verbose'])
/usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py:101:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/astroquery/esa/hubble/core.py:106: in
download_product
response = self._request('GET', self.data_url, save=True, cache=True,
/usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/test_esa_hubble.py:39:
in get_mockreturn
shutil.copy(response + '.test', response)
/usr/lib/python3.10/shutil.py:417: in copy
copyfile(src, dst, follow_symlinks=follow_symlinks)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
src =
'/usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/data/J6FL25S4Q.vot.test'
dst =
'/usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/data/J6FL25S4Q.vot'
[snip]
with open(src, 'rb') as fsrc:
try:
> with open(dst, 'wb') as fdst:
E PermissionError: [Errno 13] Permission denied:
'/usr/lib/python3/dist-packages/astroquery/esa/hubble/tests/data/J6FL25S4Q.vot'
/usr/lib/python3.10/shutil.py:256: PermissionError
Bug#1011823: marked as done (purple-xmpp-http-upload: FTBFS: dpkg-shlibdeps: error: cannot find library libjabber.so.0 needed by debian/purple-xmpp-http-upload/usr/lib/x86_64-linux-gnu/purple-2/jabber
Your message dated Mon, 30 May 2022 15:05:00 + with message-id and subject line Bug#1011823: fixed in purple-xmpp-http-upload 0.2.4-2 has caused the Debian Bug report #1011823, regarding purple-xmpp-http-upload: FTBFS: dpkg-shlibdeps: error: cannot find library libjabber.so.0 needed by debian/purple-xmpp-http-upload/usr/lib/x86_64-linux-gnu/purple-2/jabber_http_file_upload.so (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '') 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.) -- 1011823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: purple-xmpp-http-upload Version: 0.2.4-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_shlibdeps -l/usr/lib/purple-2 > dpkg-shlibdeps: error: cannot find library libjabber.so.0 needed by > debian/purple-xmpp-http-upload/usr/lib/x86_64-linux-gnu/purple-2/jabber_http_file_upload.so > (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '') > dpkg-shlibdeps: error: cannot continue due to the error above > Note: libraries are not searched in other binary packages that do not have > any shlibs or symbols file. > To help dpkg-shlibdeps find private libraries, you might need to use -l. > dh_shlibdeps: error: dpkg-shlibdeps > -Tdebian/purple-xmpp-http-upload.substvars -l/usr/lib/purple-2 > debian/purple-xmpp-http-upload/usr/lib/x86_64-linux-gnu/purple-2/jabber_http_file_upload.so > returned exit code 2 > dh_shlibdeps: error: Aborting due to earlier error > make[1]: *** [debian/rules:12: override_dh_shlibdeps] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/05/25/purple-xmpp-http-upload_0.2.4-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=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 --- Source: purple-xmpp-http-upload Source-Version: 0.2.4-2 Done: Arnaud Ferraris We believe that the bug you reported is fixed in the latest version of purple-xmpp-http-upload, 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 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Arnaud Ferraris (supplier of updated purple-xmpp-http-upload 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, 30 May 2022 16:37:52 +0200 Source: purple-xmpp-http-upload Architecture: source Version: 0.2.4-2 Distribution: unstable Urgency: medium Maintainer: DebianOnMobile Maintainers Changed-By: Arnaud Ferraris Closes: 1011823 Changes: purple-xmpp-http-upload (0.2.4-2) unstable; urgency=medium . [ Evangelos Ribeiro Tzaras ] * Adjust shlibdeps override; Closes: #1011823, thanks to Lucas Nussbaum Checksums-Sha1: aef8be848af3ab5977927db54e8f9f1946a882de 2191 purple-xmpp-http-upload_0.2.4-2.dsc 6193b6853e5bbcd7516a339e8b875d1b7efefe74 2468 purple-xmpp-http-upload_0.2.4-2.debian.tar.xz 8ecf3bf7bb98548fc8d46a9129fa47cc52fb9d0a 9454 purple-xmpp-http-upload_0.2.4-2_source.buildinfo Checksums-Sha256: b871270ff7db6ec6532984499611b68c3f866417403d577211200100f7425378 2191 purple-xmpp-http-upload_0.2.4-2.dsc ee10c19abf318b05f1d7f2f4b15d5cb842a8b6da41701853eed32af5ee309454 2468 purple-xmpp-http-upload_0.2.4-2.debian.tar.xz df091f29feaf8d937948846c0db0213260d0080b07cf2219cb201199b64fda66
Processed: Direct curl 7.83 issue, python-tornado is a collateral victim
Processing commands for cont...@bugs.debian.org:
> reassign #1011696 curl
Bug #1011696 [src:python-tornado] python-tornado: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p "3.9 3.10" returned exit code 13
Bug reassigned from package 'src:python-tornado' to 'curl'.
No longer marked as found in versions python-tornado/6.1.0-3.
Ignoring request to alter fixed versions of bug #1011696 to the same values
previously set
> affects #1011696 python-tornado
Bug #1011696 [curl] python-tornado: FTBFS: dh_auto_test: error: pybuild --test
-i python{version} -p "3.9 3.10" returned exit code 13
Added indication that 1011696 affects python-tornado
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1011696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1012059: bind9: autopkgtest regression on amd64 and armhf: connection refused
Hi Ondrej, With a recent upload of bind9 the autopkgtest of bind9 fails in testing on amd64 and armhf when that autopkgtest is run with the binary packages of bind9 from unstable. It passes when run with only packages from testing. In tabular form: I have had a brief look and it seems we are just too quick. Adding a sleep 1 into the setup function makes the test succeed. However, I cannot figure out the current repository layout anymore. debian/main appears to be outdated. The closest thing that matches Debian sid right now is the isc/9.18 branch. Could you please tell me how to handle this repository? Bernhard
Processed: Bug#1011823 marked as pending in purple-xmpp-http-upload
Processing control commands: > tag -1 pending Bug #1011823 [src:purple-xmpp-http-upload] purple-xmpp-http-upload: FTBFS: dpkg-shlibdeps: error: cannot find library libjabber.so.0 needed by debian/purple-xmpp-http-upload/usr/lib/x86_64-linux-gnu/purple-2/jabber_http_file_upload.so (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '') Ignoring request to alter tags of bug #1011823 to the same tags previously set -- 1011823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011823: marked as pending in purple-xmpp-http-upload
Control: tag -1 pending Hello, Bug #1011823 in purple-xmpp-http-upload 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/DebianOnMobile-team/purple-xmpp-http-upload/-/commit/f480bf62f1640548d02f5af4a0a0659344a53b05 Adjust shlibdeps override Closes: #1011823, thanks to Lucas Nussbaum (this message was generated automatically) -- Greetings https://bugs.debian.org/1011823
Processed: tagging 1012120
Processing commands for cont...@bugs.debian.org: > tags 1012120 + confirmed bookworm sid Bug #1012120 [libwww-dict-leo-org-perl] libwww-dict-leo-org-perl: does not connect anymore Added tag(s) bookworm, sid, and confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012120: libwww-dict-leo-org-perl: does not connect anymore
Control: tag + confirmed bookworm sid On Mon, 30 May 2022 15:39:39 +0200, Stephan Lachnit wrote: > The package does not seem to work anymore. Calling it results in `Connection > failed:` with no further information. Tested on multiple networks and > machines. > A debug log is given below. Probably an upstream issue. > Debug log: > > $ leo --debug test > %DEBUG: connecting to site: dict.leo.org port 443 > %DEBUG: GET /dictQuery/m-vocab/ende/query.xml?lp=ende=test HTTP/1.0 > Connection failed: > $ A bit of debugging in the code shows that the "only" problem is 216 close $conn or die "Connection failed: $!\n"; in /usr/share/perl5/WWW/Dict/Leo/Org.pm. If I change the die() to a warn() or comment out the line, everything works. I have no idea why "close $conn" fails, it might be related to changes in OpenSSL3 and/or IO::Socket::SSL ($conn = new IO::Socket::SSL(...)). -- $conn->close() fails as well without any further information. So this is easy to workaround, I'd still appreciate if someone has more clues what's going on here in order to produce a proper fix. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1012120: libwww-dict-leo-org-perl: does not connect anymore
Package: libwww-dict-leo-org-perl Version: 2.02-2 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: stephanlach...@debian.org, gre...@debian.org The package does not seem to work anymore. Calling it results in `Connection failed:` with no further information. Tested on multiple networks and machines. A debug log is given below. Probably an upstream issue. Cheers, Stephan Debug log: $ leo --debug test %DEBUG: connecting to site: dict.leo.org port 443 %DEBUG: GET /dictQuery/m-vocab/ende/query.xml?lp=ende=test HTTP/1.0 Connection failed: $ -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-3-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, 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 Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libwww-dict-leo-org-perl depends on: ii libio-socket-ssl-perl 2.074-2 ii liburi-encode-perl 1.1.1-1 ii libxml-simple-perl 2.25-1 ii perl 5.34.0-4 libwww-dict-leo-org-perl recommends no packages. libwww-dict-leo-org-perl suggests no packages. -- no debconf information
Bug#991566: marked as done (r-cran-bookdown: Please package version 0.25)
Your message dated Mon, 30 May 2022 13:34:38 + with message-id and subject line Bug#991566: fixed in r-cran-bookdown 0.26+dfsg-1 has caused the Debian Bug report #991566, regarding r-cran-bookdown: Please package version 0.25 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.) -- 991566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991566 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: r-cran-bookdown Version: 0.21+dfsg-1 Severity: wishlist Dear Maintainer, Upstream released bookdown version 0.22 last april[1]. It includes interesting new features and bugfixes. Would you consider packaging it? Thanks for your work on bookdown in debian. [1] https://github.com/rstudio/bookdown/releases/tag/v0.22 --- End Message --- --- Begin Message --- Source: r-cran-bookdown Source-Version: 0.26+dfsg-1 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of r-cran-bookdown, 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 991...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated r-cran-bookdown 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, 30 May 2022 18:23:08 +0530 Source: r-cran-bookdown Architecture: source Version: 0.26+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Nilesh Patra Closes: 991566 Changes: r-cran-bookdown (0.26+dfsg-1) unstable; urgency=medium . * Team Upload. . [ Nilesh Patra] * New upstream version 0.26+dfsg (Closes: #991566) * Update test-deps * Update versioned-dep on B-D in acc with dh-update-R * Remove bs4_book.html which generate privacy breaches * Update lintian overrides . [ Andreas Tille ] * Fix watchfile to detect new versions on github (routine-update) * New upstream version * Standards-Version: 4.6.0 (routine-update) * dh-update-R to update Build-Depends (routine-update) * Remove constraints unnecessary since buster: + Build-Depends: Drop versioned constraint on r-cran-knitr and r-cran-tinytex. Checksums-Sha1: 2ebce1f453bbb0598bda6be8b8192f8a8a0e3a0a 2315 r-cran-bookdown_0.26+dfsg-1.dsc 2368b80c724f6efce0d628959d708a137abd0cfe 117 r-cran-bookdown_0.26+dfsg.orig.tar.xz dc4d0128818e01e951a38ea8bc86082f2567b64b 73752 r-cran-bookdown_0.26+dfsg-1.debian.tar.xz 9ccb23c95ca7b7a6281fd3b6117a655d3fc89aa5 12623 r-cran-bookdown_0.26+dfsg-1_amd64.buildinfo Checksums-Sha256: b00626abc7f994d295eee48d0861786dd0406e2cfdce290c10c7fff3c3934ff2 2315 r-cran-bookdown_0.26+dfsg-1.dsc 734469802b00296a3effc0a7d27734d5e65bac67b26fa8923ad71b7ed9afcfae 117 r-cran-bookdown_0.26+dfsg.orig.tar.xz 154efc8c1e92c65bd2b0486082453a29389ac76a6525fb36b6a21898d0c3f038 73752 r-cran-bookdown_0.26+dfsg-1.debian.tar.xz 2832fa9467100ff174bb3280f84def8cba5353fd91e60f3fd6d9cf5f28a66edd 12623 r-cran-bookdown_0.26+dfsg-1_amd64.buildinfo Files: 20b27c82727e0867b844ec591a0b9177 2315 gnu-r optional r-cran-bookdown_0.26+dfsg-1.dsc b797440f1d81a675e1cfef21d929c9cd 117 gnu-r optional r-cran-bookdown_0.26+dfsg.orig.tar.xz e10ddc8ce93638785de4b1a5fb6d4c32 73752 gnu-r optional r-cran-bookdown_0.26+dfsg-1.debian.tar.xz b0ce4104ef4e7b8b9db6386885f43b97 12623 gnu-r optional r-cran-bookdown_0.26+dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmKUw50SHG5pbGVzaEBk ZWJpYW4ub3JnAAoJEAC650s0M2nxE8EQAJFJFqpoiD/9W4O48aUua6fDIObWOTfG GH7b/aPwb0Wgm93mMSBbqgA8z2rfoNvP807d+UMlsfKl/Ht/GQmnzlXpLLVAMv0Q X9WgguX0HTxl4LRMzkbN98wn7N4gWyvXjoAqQPbtMHQOWBeK7HxUI8S9XONYAihk 7kgKdc3hZSGkn3NdKLRgcyRqcA/CYVTWaFCf/aEDIcTKX+VNNdsJmH/adhONxl2c SiumTDa6olpn1QE4ny8r4skNC3x+oGu+ahDSyL9Vc5NDI5VxWuU5s105F2jHgOpP 7674P8KdZSXlv7RzKzx8po3upmiImaTHBax3usoMW2ORHZA09d0MPRApAD9iMgS4 FRA8N3TWd3NXKf8RmU4kzRjHT6NoLHrMM8YTnjLRtgN6O656fvx4/fySKHIsLN0i 3Bsmt8tpzAQ0bqxdAiRxf+ArxfbRp5qmBplQbDLRWmwqn/L1C0id8YD+mFTYBmOT IguP1C+LtLZv0sI8gjArXs+7nbJAvE3I26hq6bgqKI9hq/G6eLmeK2JPG62H0Dr/ tkYydf0to23hLDXtdMHTGS1qor1vgSEszSFWw4IkcYRLPGRiz6yjbtR+jNjo+ecq
Bug#1009402: [Debichem-devel] Bug#1009402: Bug#1009402: molmodel: FTBFS: demangle.hpp:23:33: error: ‘string_view’ in namespace ‘std’ does not name a type
Hi, On 2022-05-26 16:24, Adrian Bunk wrote: > The remaining problem can be fixed with the same change as > https://salsa.debian.org/debichem-team/macromoleculebuilder/-/blob/master/debian/patches/drop-CMAKE_CXX_STANDARD.patch Thanks for the suggestion - it worked! Best, Andrius
Bug#1011816: Bug#1004471: Update node-terser to latest upstream (node-terser 5)
There is something broken with cjs/mjs. I'm going to fix that. Cheers, Yadd Le Lundi, Mai 30, 2022 13:07 CEST, Jonas Smedegaard a écrit: > Quoting Yadd (2022-05-30 12:05:41) > > here is a debdiff (debian part only) to update terser to version 5.13.1. > > This fixes also #1011816 (FTBFS) > > Thanks! > > It seems you are sharing that patch as a proposal, as you only pushed > some parts of it to git. > > ...and I disagree with some minor parts of it, so that's good: I will > take a look at it, and when I get a better sense of it reply back here > in more detail which parts I disagree with. > > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private
Bug#1011863: guix: FTBFS: tests fail
Hi, On 26/05/22 at 22:06 -0700, Vagrant Cascadian wrote: > Would it be at all possible to update your script to compress and attach > data over a certain size? This was well over 5 lines long, the vast > majority of which were actually tests that passed! It crashes and/or > hangs my mail client when I try to open the original mail in this bug > report, so it really is a practical problem for me! Oops, I missed that one. The log editing is a partially manual process. I need to add a stronger verification that I did not forget to trim the log. To-Do item added ;) Lucas signature.asc Description: PGP signature
Bug#1011816: Bug#1004471: Update node-terser to latest upstream (node-terser 5)
Quoting Yadd (2022-05-30 12:05:41) > here is a debdiff (debian part only) to update terser to version 5.13.1. > This fixes also #1011816 (FTBFS) Thanks! It seems you are sharing that patch as a proposal, as you only pushed some parts of it to git. ...and I disagree with some minor parts of it, so that's good: I will take a look at it, and when I get a better sense of it reply back here in more detail which parts I disagree with. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1011928: trilinos FTBFS: isinf was not defined in this scope
Hi To be clear, does this failure only happen with libtbb-dev/experimental? I didn't see this failure while building trilinos locally with sbuild in unstable, and it still builds (when it doesn't time out) on reproducible builds [1]. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/trilinos.html
Bug#1011816: Update node-terser to latest upstream (node-terser 5)
Hi,
here is a debdiff (debian part only) to update terser to version 5.13.1.
This fixes also #1011816 (FTBFS)
Cheers,
Yadddiff --git a/debian/changelog b/debian/changelog
index bf31486e..e23e2739 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,16 @@
+node-terser (5.13.1-1) UNRELEASED; urgency=medium
+
+ * Team upload
+ * Declare compliance with policy 4.6.1
+ * Fix debian/rules for parallel build (manpage needs bundle file)
+ * New upstream version 5.13.1
+ * Refresh patches
+ * Add patches to fix test
+ * Add links during build
+ * Render mocha test required
+
+ -- Yadd Mon, 30 May 2022 12:03:45 +0200
+
node-terser (4.8.0-2) experimental; urgency=medium
* update copyright info:
diff --git a/debian/clean b/debian/clean
index 479d4e14..51146a4a 100644
--- a/debian/clean
+++ b/debian/clean
@@ -1,5 +1,6 @@
debian/js/
debian-man/
dist/bundle*
+node_modules/
README.html
README.txt
diff --git a/debian/patches/1001_commander.patch
b/debian/patches/1001_commander.patch
index abcf1fa5..fdaa927b 100644
--- a/debian/patches/1001_commander.patch
+++ b/debian/patches/1001_commander.patch
@@ -4,231 +4,220 @@ Description: support node module commander release 8
(and possibly v7 as well),
at the expense of compatibility with older releases of commander.
Author: Yadd
-Last-Update: 2022-02-06
+Last-Update: 2022-05-30
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
a/bin/terser
-+++ b/bin/terser
-@@ -25,6 +25,15 @@
- program.version(info.name + " " + info.version);
- program.parseArgv = program.parse;
- program.parse = undefined;
-+var argv = [];
-+process.argv.forEach(function(arg){
-+ if(arg.match(/^-([pcmbode]+)$/)) {
-+argv = argv.concat(RegExp.$1.split('').map(s => { return '-'+s }));
-+ }
-+ else argv.push(arg);
-+});
-+process.argv = argv;
-+
- if (process.argv.includes("ast")) program.helpInformation = describe_ast;
- else if (process.argv.includes("options")) program.helpInformation =
function() {
- var text = [];
+
+--- a/lib/cli.js
b/lib/cli.js
+@@ -26,6 +26,15 @@
+ program.parseArgv = program.parse;
+ program.parse = undefined;
+
++var argv = [];
++process.argv.forEach(function(arg){
++ if(arg.match(/^-([pcmbode]+)$/)) {
++argv = argv.concat(RegExp.$1.split('').map(s => { return '-'+s }));
++ }
++ else argv.push(arg);
++});
++process.argv = argv;
++
+ if (process.argv.includes("ast")) program.helpInformation = describe_ast;
+ else if (process.argv.includes("options")) program.helpInformation =
function() {
+ var text = [];
@@ -62,10 +71,11 @@
- program.option("--warn", "Print warning messages.");
- program.option("--wrap ", "Embed everything as a function with
“exports” corresponding to “name” globally.");
- program.arguments("[files...]").parseArgv(process.argv);
--if (program.configFile) {
--options = JSON.parse(read_file(program.configFile));
-+const opts = program.opts();
-+if (opts.configFile) {
-+options = JSON.parse(read_file(opts.configFile));
- }
--if (!program.output && program.sourceMap && program.sourceMap.url !=
"inline") {
-+if (!opts.output && opts.sourceMap && opts.sourceMap.url != "inline") {
- fatal("ERROR: cannot write source map to STDOUT");
- }
- [
-@@ -79,87 +89,87 @@
- "toplevel",
- "wrap"
- ].forEach(function(name) {
--if (name in program) {
--options[name] = program[name];
-+if (name in opts) {
-+options[name] = opts[name];
+ program.option("--toplevel", "Compress and/or mangle variables in
toplevel scope.");
+ program.option("--wrap ", "Embed everything as a function with
“exports” corresponding to “name” globally.");
+ program.arguments("[files...]").parseArgv(process.argv);
+-if (program.configFile) {
+-options = JSON.parse(read_file(program.configFile));
++const opts = program.opts();
++if (opts.configFile) {
++options = JSON.parse(read_file(opts.configFile));
+ }
+-if (!program.output && program.sourceMap && program.sourceMap.url !=
"inline") {
++if (!opts.output && opts.sourceMap && opts.sourceMap.url != "inline") {
+ fatal("ERROR: cannot write source map to STDOUT");
+ }
+
+@@ -80,76 +90,76 @@
+ "toplevel",
+ "wrap"
+ ].forEach(function(name) {
+-if (name in program) {
+-options[name] = program[name];
++if (name in opts) {
++options[name] = opts[name];
+ }
+ });
+
+-if ("ecma" in program) {
+-if (program.ecma != (program.ecma | 0)) fatal("ERROR: ecma must be an
integer");
+-const ecma = program.ecma | 0;
++if ("ecma" in opts && opts.ecma != undefined) {
++if (opts.ecma != (opts.ecma | 0)) fatal("ERROR: ecma must be an
integer");
++const ecma = opts.ecma | 0;
+ if (ecma > 5 && ecma < 2015)
+ options.ecma = ecma + 2009;
+ else
+ options.ecma = ecma;
+ }
Bug#965762: marked as done (opusfile: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Mon, 30 May 2022 09:50:08 +
with message-id
and subject line Bug#965762: fixed in opusfile 0.12-1
has caused the Debian Bug report #965762,
regarding opusfile: Removal of obsolete debhelper compat 5 and 6 in 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.)
--
965762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opusfile
Version: 0.9+20170913-1
Severity: normal
Usertags: compat-5-6-removal
Hi,
The package opusfile uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].
Please bump the debhelper compat at your earliest convenience
/outside the freeze/!
* Compat 13 is recommended (supported in stable-backports)
* Compat 7 is the bare minimum
PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.
If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.
At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".
Thanks,
~Niels
[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html
[2] https://release.debian.org/bullseye/FAQ.html
[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.
Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: opusfile
Source-Version: 0.12-1
Done: IOhannes m zmölnig (Debian/GNU)
We believe that the bug you reported is fixed in the latest version of
opusfile, 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 965...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU) (supplier of updated
opusfile 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, 30 May 2022 11:22:59 +0200
Source: opusfile
Architecture: source
Version: 0.12-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: IOhannes m zmölnig (Debian/GNU)
Closes: 881788 899138 923031 935590 935591 965762 1007053 1009854
Changes:
opusfile (0.12-1) unstable; urgency=medium
.
* Upload to unstable.
* Fix upstream contact.
.
opusfile (0.12-1~exp1) experimental; urgency=medium
.
* New upstream version 0.12 (Closes: #935591, #881788)
.
* Salvage the package on behalf of the multimedia-team (Closes: #1009854)
* Install libraries into multi-arch locations
(Closes: #935590, #923031, #899138) (LP: #1883753)
* Drop empty dbg package (switching to automatic dbgsym packages)
* Add build-dependency hints to .symbols file
* Mark lib*.la files as not-installed
* Install AUTHORS and README.md
* Remove trailing whitespace from d/changelog
* d/control
+ Declare that building this package does not require 'root' powers.
+ Use Priority "optional" instead of the obsolete "extra"
+ ${misc:Depends} for libopusfile-doc
+ Fix package descriptions
+ Update Vcs-* stanzas
+ Make the doc-package "suggest" the dev-package
* d/copyright
+ Convert to DEP-5
+ Add 'licensecheck' target to d/rules
+ Generate d/copyright_hints
* Add salsa-ci configuration
* Add watch file
* Add gbp.conf
* Switch to 3.0 source format (Closes: #1007053)
* Bump dh-compat to 13 (Closes: #965762)
+ Drop old build script in favour of shortform 'dh'
* Bump standards version to 4.6.0
Checksums-Sha1:
644a6f75b8e18965a5528c17b656137c8387d3b4 2342 opusfile_0.12-1.dsc
2ace54a27bbbc3d2197e2aedc998a2cbd05c187d 5572 opusfile_0.12-1.debian.tar.xz
Checksums-Sha256:
ec927da64a60051ec315bb93d7871132249b7453f77d5b4858bfce75323d0b0d 2342
opusfile_0.12-1.dsc
0eae81e129f0f9583984b2ae9a45b0304b63635a34581eb4577c65344b62de22 5572
opusfile_0.12-1.debian.tar.xz
Files:
f885e886a0bc9b93e2175355d35d751e 2342 sound optional
Processed: bug 1005719 is forwarded to https://github.com/mumble-voip/mumble/pull/5354
Processing commands for cont...@bugs.debian.org: > forwarded 1005719 https://github.com/mumble-voip/mumble/pull/5354 Bug #1005719 [src:mumble] mumble: FTBFS with OpenSSL 3.0 Set Bug forwarded-to-address to 'https://github.com/mumble-voip/mumble/pull/5354'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1005719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012097: NIS broken in sid
Package: libnssswitch-nis
Version: 3.1-4
Severity: grave
It seems that currently unstable has a totally not working NIS binding for
users. I
performed my trials using an existing setup (bullseye-based NIS master+slaves
and
clients network in the real life).
I recently upgraded a bullseye NIS client box to sid for testing and discovered
that while
ypbind-mt is regularly working, the usual mapping of NIS users has gone.
To be sure of the issue I prepared a vagrant bullseye VM and bound that to
the regular bullseye NIS master as usual: perfectly working.
Then I full-upgraded to sid with the same broken result:
vagrant@debian:/etc$ ypcat passwd
[...]
lovergine:x:2003:2000:Francesco Lovergine (trial),,,:/home/lovergine:/bin/bash
[...]
{sorry, I stripped the full output for privacy)
vagrant@debian:/etc$ id lovergine
id: ‘lovergine’: no such user
vagrant@debian:/etc$ cat /etc/nsswitch.conf
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.
passwd: compat systemd
group: compat systemd
shadow: compat
gshadow:compat
hosts: files dns
networks: files
protocols: db files
services: db files
ethers: db files
rpc:db files
netgroup: nis
vagrant@debian:/etc$ cat /etc/passwd
root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
bin:x:2:2:bin:/bin:/usr/sbin/nologin
sys:x:3:3:sys:/dev:/usr/sbin/nologin
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/usr/sbin/nologin
man:x:6:12:man:/var/cache/man:/usr/sbin/nologin
lp:x:7:7:lp:/var/spool/lpd:/usr/sbin/nologin
mail:x:8:8:mail:/var/mail:/usr/sbin/nologin
news:x:9:9:news:/var/spool/news:/usr/sbin/nologin
uucp:x:10:10:uucp:/var/spool/uucp:/usr/sbin/nologin
proxy:x:13:13:proxy:/bin:/usr/sbin/nologin
www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin
backup:x:34:34:backup:/var/backups:/usr/sbin/nologin
list:x:38:38:Mailing List Manager:/var/list:/usr/sbin/nologin
irc:x:39:39:ircd:/run/ircd:/usr/sbin/nologin
gnats:x:41:41:Gnats Bug-Reporting System
(admin):/var/lib/gnats:/usr/sbin/nologin
nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
_apt:x:100:65534::/nonexistent:/usr/sbin/nologin
systemd-timesync:x:101:101:systemd Time
Synchronization,,,:/run/systemd:/usr/sbin/nologin
systemd-network:x:102:103:systemd Network
Management,,,:/run/systemd:/usr/sbin/nologin
systemd-resolve:x:103:104:systemd Resolver,,,:/run/systemd:/usr/sbin/nologin
messagebus:x:104:105::/nonexistent:/usr/sbin/nologin
_chrony:x:105:112:Chrony daemon,,,:/var/lib/chrony:/usr/sbin/nologin
sshd:x:106:65534::/run/sshd:/usr/sbin/nologin
vagrant:x:1000:1000::/home/vagrant:/bin/bash
systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
_rpc:x:107:65534::/run/rpcbind:/usr/sbin/nologin
+::
My next step will be running a full-sid setup for a test network, but I don't
see any reason why the working NIS maps could be broken, my guess is that
the problem is connected to some inner libnss/libc issue.
-cheers
--
Francesco P. Lovergine
Processed: notfixed 990562 in 2:7.0~rc4-1, fixed 990562 in 1:7.0~rc4-1, tagging 965762, tagging 1012083
Processing commands for cont...@bugs.debian.org:
> notfixed 990562 2:7.0~rc4-1
Bug #990562 {Done: Michael Tokarev } [src:qemu] qemu:
CVE-2021-3611: intel-hda: segmentation fault due to stack overflow
The source 'qemu' and version '2:7.0~rc4-1' do not appear to match any binary
packages
No longer marked as fixed in versions 2:7.0~rc4-1.
> fixed 990562 1:7.0~rc4-1
Bug #990562 {Done: Michael Tokarev } [src:qemu] qemu:
CVE-2021-3611: intel-hda: segmentation fault due to stack overflow
The source 'qemu' and version '1:7.0~rc4-1' do not appear to match any binary
packages
Marked as fixed in versions qemu/1:7.0~rc4-1.
> tags 965762 + experimental
Bug #965762 {Done: IOhannes m zmölnig (Debian/GNU) }
[src:opusfile] opusfile: Removal of obsolete debhelper compat 5 and 6 in
bookworm
Added tag(s) experimental.
> tags 1012083 + sid bookworm
Bug #1012083 [src:quickfix] quickfix FTBFS on riscv64
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1012083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012083
965762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965762
990562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1011794: marked as done (node-jsdom: FTBFS: tests fail)
Your message dated Mon, 30 May 2022 07:04:09 + with message-id and subject line Bug#1011794: fixed in node-jsdom 19.0.0+~cs153.23.47-4 has caused the Debian Bug report #1011794, regarding node-jsdom: FTBFS: tests fail 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.) -- 1011794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-jsdom Version: 19.0.0+~cs153.23.47-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > cd debian/build_modules/webidl2 && babeljs-7 -d dist --presets > @babel/preset-env --plugins @babel/plugin-transform-runtime lib/ > Successfully compiled 31 files with Babel (2034ms). > dh_auto_build --buildsystem=nodejs > parse5/lerna.json found > > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > Found debian/nodejs/xmlchars/build > cd ./xmlchars && sh -ex ../debian/nodejs/xmlchars/build > + tsc --outDir . > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > Found debian/nodejs/domexception/build > cd ./domexception && sh -ex ../debian/nodejs/domexception/build > + node scripts/generate.js > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > Found debian/nodejs/whatwg-url/build > cd ./whatwg-url && sh -ex ../debian/nodejs/whatwg-url/build > + node scripts/transform.js > No build command found, searching known files > Found debian/nodejs/whatwg-encoding/build > cd ./whatwg-encoding && sh -ex ../debian/nodejs/whatwg-encoding/build > + mkdir -p lib > + cp ../debian/nodejs/whatwg-encoding/missing/labels-to-names.json > ../debian/nodejs/whatwg-encoding/missing/supported-names.json lib/ > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > Found debian/nodejs/saxes/build > cd ./saxes && sh -ex ../debian/nodejs/saxes/build > + tsc > + mv build/dist/saxes.d.ts build/dist/saxes.js build/dist/saxes.js.map . > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > cp debian/whatwg-encoding/* whatwg-encoding/lib/ > cp debian/tr46/* tr46/lib/ > node ./scripts/webidl/convert.js > node ./scripts/generate-js-globals.js > cp debian/missing/* lib/jsdom/living/generated/ > ln -s lib/jsdom/living/generated . > ln -s ../scripts/eslint-plugin node_modules || true > make[1]: Leaving directory '/<>' >dh_auto_test --buildsystem=nodejs > parse5/lerna.json found > > ln -s ../debian/tests/test_modules/mocha-sugar-free > node_modules/mocha-sugar-free > ln -s ../debian/tests/test_modules/server-destroy > node_modules/server-destroy > ln -s ../. node_modules/jsdom > cd ./decimaljs && sh -ex ../debian/nodejs/decimaljs/test > + node test/test.js > > Testing decimal.js > > Testing absoluteValue... 100 of 100 tests passed in 3 ms > Testing acos... 50 of 50 tests passed in 72 ms > Testing acosh... 50 of 50 tests passed in 24 ms > Testing asin... 50 of 50
Bug#1011758: marked as done (smarty3: CVE-2022-29221 - template authors can inject php code by choosing malicious filenames)
Your message dated Mon, 30 May 2022 06:50:05 +
with message-id
and subject line Bug#1011758: fixed in smarty3 3.1.45-1
has caused the Debian Bug report #1011758,
regarding smarty3: CVE-2022-29221 - template authors can inject php code by
choosing malicious filenames
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.)
--
1011758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011758
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: smarty3
Version: 3.1.39-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: codeh...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for smarty3.
CVE-2022-29221[0]:
| Smarty is a template engine for PHP, facilitating the separation of
| presentation (HTML/CSS) from application logic. Prior to versions
| 3.1.45 and 4.1.1, template authors could inject php code by choosing a
| malicious {block} name or {include} file name. Sites that cannot fully
| trust template authors should upgrade to versions 3.1.45 or 4.1.1 to
| receive a patch for this issue. There are currently no known
| workarounds.
If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2022-29221
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29221
Please adjust the affected versions in the BTS as needed.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.17.0-2-amd64 (SMP w/6 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: smarty3
Source-Version: 3.1.45-1
Done: Mike Gabriel
We believe that the bug you reported is fixed in the latest version of
smarty3, 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 1011...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mike Gabriel (supplier of updated smarty3 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, 30 May 2022 08:24:30 +0200
Source: smarty3
Architecture: source
Version: 3.1.45-1
Distribution: unstable
Urgency: medium
Maintainer: Mike Gabriel
Changed-By: Mike Gabriel
Closes: 1011758
Changes:
smarty3 (3.1.45-1) unstable; urgency=medium
.
* New upstream release.
- CVE-2021-21408: Prevent template authors from running restricted static
php methods. (see smarty4 bug #1010375).
- CVE-2021-29454: Prevent template authors from running arbitrary PHP code
by crafting a malicious math string. (see smarty4 bug #1010375, as well).
- CVE-2022-29221: Prevent template authors from injecting PHP code by
choosing malicious filenames. (Closes: #1011758).
* debian/watch:
+ Only watch 3.x versions of Smarty.
* debian/control:
+ Bump Standards-Version: to 4.6.1. No changes needed.
* debian/copyright:
+ Update copyright attributions.
Checksums-Sha1:
63ceee77103b035d6f069c36e24d7172d4bd72dc 1980 smarty3_3.1.45-1.dsc
5125692feefb89d40e5a08ea586d22a2b1e21c0d 265781 smarty3_3.1.45.orig.tar.gz
4c25d3866cf57a4863f765a5ec617842457b051a 5780 smarty3_3.1.45-1.debian.tar.xz
1103fce3b88174d4b4669176d63bb655981d2823 6780 smarty3_3.1.45-1_source.buildinfo
Checksums-Sha256:
19dae472ffbc91d1834036fce8b9f5862e479f83e8c737b72562e817b1947da9 1980
smarty3_3.1.45-1.dsc
4e8dcc8b52ea097b93d32aa432cb552547568ae328505d25af078d63354a9a83 265781
smarty3_3.1.45.orig.tar.gz
c4edf77410cae38bf829f0a90ee1f7fb18d62b6386101e851450eb9abd07a8b7 5780
smarty3_3.1.45-1.debian.tar.xz
b86b89e55e7eccfe82ec1f9f751ae079694aef9fa542908b6926dfe59284c358 6780
smarty3_3.1.45-1_source.buildinfo
Files:
266cff1a53aca7cb2e77ffa9a2d8b007 1980 web optional smarty3_3.1.45-1.dsc
c1b5d7acb43485c43973f0fb1e0d64c6 265781 web optional smarty3_3.1.45.orig.tar.gz
8ebcbddef610a7961748465ee462bf29 5780 web optional
Bug#1012077: linuxinfo FTBFS on riscv64
Hello Alan, On Sun, May 29, 2022 at 02:45:29PM -0400, Alan Beadle wrote: > Package: linuxinfo > Version: 3.3.3-1 > Severity: serious > Tags: ftbfs patch upstream > Justification: fails to build from source > X-Debbugs-Cc: ab.bea...@gmail.com > > Dear Maintainer, > > linuxinfo currently fails to build on riscv64 due to this architecture not > being > supported by upstream. I am attaching a patch which adds placeholder support > for > this architecture and allows building the riscv64 debian package from source. > > Please consider applying this patch (or similar) for the next upload. > In addition, the /proc information below is for a riscv64 VisionFive V1 SBC. Thanks a lot! This was on my wishlist already. I'll review and possibly ammend your patch next weekend and then will proceed with an upload. Greetings Helge -- 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
