Bug#966922: (No Subject)
Hi Scott, While resolving this bug, would you by the way bump libnitrokey to version 3.6? Szczepan released it this week. This new version introduces native support for LibremKey.
Processed: notfound 970638 in 0.3.6-1
Processing commands for cont...@bugs.debian.org: > notfound 970638 0.3.6-1 Bug #970638 [jag] jag: cannot upgrade from 0.3.6-1 to 0.3.8-1 No longer marked as found in versions jag/0.3.6-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 970638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: undertow: should not be part of Debian 11
Processing commands for cont...@bugs.debian.org: > found 970346 2.2.0-1 Bug #970346 [src:undertow] undertow: should not be part of Debian 11 Marked as found in versions undertow/2.2.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 970346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 970638 to jag: cannot upgrade from 0.3.6-1 to 0.3.8-1
Processing commands for cont...@bugs.debian.org: > retitle 970638 jag: cannot upgrade from 0.3.6-1 to 0.3.8-1 Bug #970638 [jag] jag: cannot upgrade from 3.6-1 to 3.8-1 Changed Bug title to 'jag: cannot upgrade from 0.3.6-1 to 0.3.8-1' from 'jag: cannot upgrade from 3.6-1 to 3.8-1'. > thanks Stopping processing here. Please contact me if you need assistance. -- 970638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970664: libvte-2.91-0: Terminal not displaying correctly
Package: libvte-2.91-0 Version: 0.62.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, After an upgrade of libvte gnome-terminal and other software using the library (gedit terminal plugin) doesn't work. Where the console should be there is some transparency and a effect similar to when you record a screen that shows what the camera sees (feedback). Reverting to 0.60.3-1 of libvte and gnome-terminal 3.36.2-3 fixes the issue. Regards. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=es_CL.UTF-8, LC_CTYPE=es_CL.UTF-8 (charmap=UTF-8), LANGUAGE=es_CL:es Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libvte-2.91-0 depends on: ii libatk1.0-0 2.36.0-2 ii libc62.31-3 ii libcairo21.16.0-4 ii libfribidi0 1.0.8-2 ii libgcc-s110.2.0-7 ii libglib2.0-0 2.66.0-2 ii libgnutls30 3.6.15-4 ii libgtk-3-0 3.24.23-1 ii libicu67 67.1-4 ii libpango-1.0-0 1.46.1-1 ii libpangocairo-1.0-0 1.46.1-1 ii libpcre2-8-0 10.34-7 ii libstdc++6 10.2.0-7 ii libsystemd0 246.5-1 ii libvte-2.91-common 0.62.0-1 ii zlib1g 1:1.2.11.dfsg-2 libvte-2.91-0 recommends no packages. libvte-2.91-0 suggests no packages. -- no debconf information
Bug#970663: mariadb-105: FTBFS on ppc64: InnoDB: Trying to delete tablespace 'test/bug21114_child' but there are 1 flushes and 0 pending i/o's on it
Source: mariadb-10.3 Version: 1:10.5.5-1~exp1 Severity: serious Justification: fails to build from source User: debian-powe...@lists.debian.org Usertags: ppc64 After uploading the latest mariadb-10.5 I noticed it fails to build. However, mariadb-10.4 built just fine on ppc64. The failure is this test that fails: main.parser_bug21114_innodb 'innodb' w5 [ fail ] Found warnings/errors in server log file! Test ended at 2020-09-12 17:31:51 line 2020-09-12 17:31:19 8 [Warning] InnoDB: Trying to delete tablespace 'test/bug21114_child' but there are 1 flushes and 0 pending i/o's on it. ^ Found warnings in /<>/builddir/mysql-test/var/5/log/mysqld.1.err ok
Bug#970662: mariadb-105: FTBFS on x32: operand size mismatch for `crc32'
Source: mariadb-10.5 Version: 1:10.5.5-1~exp1 Severity: serious Justification: fails to build from source User: debian-...@lists.debian.org Usertags: x32 After uploading the latest mariadb-10.5 I noticed it fails to build. However, mariadb-10.4 built just fine on x32. The failure is: [ 48%] Building CXX object storage/innobase/CMakeFiles/innobase_embedded.dir/ut/ut0crc32.cc.o cd /<>/builddir/storage/innobase && /usr/bin/x86_64-linux-gnux32-g++ -DBTR_CUR_ADAPT -DBTR_CUR_HASH_ADAPT -DCOMPILER_HINTS -DDBUG_TRACE -DEMBEDDED_LIBRARY -DHAVE_C99_INITIALIZERS -DHAVE_CONFIG_H -DHAVE_FALLOC_PUNCH_HOLE_AND_KEEP_SIZE=1 -DHAVE_IB_LINUX_FUTEX=1 -DHAVE_LZ4=1 -DHAVE_LZ4_COMPRESS_DEFAULT=1 -DHAVE_NANOSLEEP=1 -DHAVE_SCHED_GETCPU=1 -DHAVE_SNAPPY=1 -DLINUX_NATIVE_AIO=1 -DMUTEX_EVENT -DWITH_INNODB_DISALLOW_WRITES -D_FILE_OFFSET_BITS=64 -I/<>/wsrep-lib/include -I/<>/wsrep-lib/wsrep-API/v26 -I/<>/builddir/include -I/<>/storage/innobase/include -I/<>/storage/innobase/handler -I/<>/libbinlogevents/include -I/<>/tpool -I/<>/include -I/<>/sql -I/<>/builddir/extra/wolfssl -I/<>/extra/wolfssl/wolfssl -I/<>/extra/wolfssl/wolfssl/wolfssl -g -O2 -fdebug-prefix-map=/<>=. -specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pie -fPIC -fstack-protector --param=ssp-buffer-size=4 -Wconversion -Wno-sign-conversion -O2 -g -static-libgcc -fno-omit-frame-pointer -fno-strict-aliasing -Wno-uninitialized -fno-omit-frame-pointer -D_FORTIFY_SOURCE=2 -DDBUG_OFF -Wall -Wextra -Wformat-security -Wno-format-truncation -Wno-init-self -Wno-nonnull-compare -Wno-unused-parameter -Woverloaded-virtual -Wnon-virtual-dtor -Wvla -Wwrite-strings -Wdate-time -D_FORTIFY_SOURCE=2 -DUNIV_LINUX -D_GNU_SOURCE=1 -DHAVE_OPENSSL -DHAVE_WOLFSSL -DWOLFSSL_USER_SETTINGS -fPIC -fvisibility=hidden -std=gnu++11 -o CMakeFiles/innobase_embedded.dir/ut/ut0crc32.cc.o -c /<>/storage/innobase/ut/ut0crc32.cc /<>/storage/innobase/ut/ut0crc32.cc: Assembler messages: /<>/storage/innobase/ut/ut0crc32.cc:167: Error: operand size mismatch for `crc32' /<>/storage/innobase/ut/ut0crc32.cc:167: Error: operand size mismatch for `crc32' /<>/storage/innobase/ut/ut0crc32.cc:167: Error: operand size mismatch for `crc32' /<>/storage/innobase/ut/ut0crc32.cc:167: Error: operand size mismatch for `crc32' /<>/storage/innobase/ut/ut0crc32.cc:167: Error: operand size mismatch for `crc32' /<>/storage/innobase/ut/ut0crc32.cc:167: Error: operand size mismatch for `crc32' /<>/storage/innobase/ut/ut0crc32.cc:167: Error: operand size mismatch for `crc32' /<>/storage/innobase/ut/ut0crc32.cc:167: Error: operand size mismatch for `crc32' /<>/storage/innobase/ut/ut0crc32.cc:167: Error: operand size mismatch for `crc32' /<>/storage/innobase/ut/ut0crc32.cc:167: Error: operand size mismatch for `crc32' /<>/storage/innobase/ut/ut0crc32.cc:167: Error: operand size mismatch for `crc32' /<>/storage/innobase/ut/ut0crc32.cc:167: Error: operand size mismatch for `crc32' /<>/storage/innobase/ut/ut0crc32.cc:167: Error: operand size mismatch for `crc32' /<>/storage/innobase/ut/ut0crc32.cc:167: Error: operand size mismatch for `crc32' /<>/storage/innobase/ut/ut0crc32.cc:167: Error: operand size mismatch for `crc32' /<>/storage/innobase/ut/ut0crc32.cc:167: Error: operand size mismatch for `crc32' /<>/storage/innobase/ut/ut0crc32.cc:167: Error: operand size mismatch for `crc32' make[4]: *** [storage/innobase/CMakeFiles/innobase_embedded.dir/build.make:1499: storage/innobase/CMakeFiles/innobase_embedded.dir/ut/ut0crc32.cc.o] Error 1 make[4]: Leaving directory '/<>/builddir' make[3]: *** [CMakeFiles/Makefile2:5499: storage/innobase/CMakeFiles/innobase_embedded.dir/all] Error 2 make[3]: *** Waiting for unfinished jobs
Bug#970651: [Pkg-javascript-devel] Bug#970651: Bug#970651: rollup: Unable to build with current tsc
Quoting Pirate Praveen (2020-09-20 22:08:24) > > > On 2020, സെപ്റ്റംബർ 21 12:38:37 AM IST, Xavier Guimard > wrote: > >Package: rollup > >Version: 1.12.0-2 > >Severity: serious > >Tags: ftbfs > >Justification: Policy 7.7.7 > > > >node-rollup 1.12.0 can't be build with current typescript (4.0.2). It > >requires tsc 3.4.5 (tested with success). Output: > > I think the root cause is uploading major versions without > coordination. It should have been easily found out if all packages > using typescript was rebuilt before it was uploaded to unstable. I agree with the above. > I think we should create a release team within js team to handle it > like how release team works for transitions. What do you mean more concretely? That only a smaller elite group should (approve) upload to unstable, and everyone else should upload only to experimental, or...? - 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#967125: desmume: Unversioned Python removal in sid/bullseye
On Sun, 20 Sep 2020 23:51:22 +0200 Markus Koschany wrote: > > I believe this issue was fixed in libglade2-dev (#967157) and > monster-masher ^ should be desmume of course :-) signature.asc Description: OpenPGP digital signature
Bug#968893: Acknowledgement (mariadb-10.3: FTBFS on alpha: relocation truncated to fit)
Interestingly alpha built just fine on mariadb-10.5: https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.5=alpha=1%3A10.5.5-1%7Eexp1=1600077822=0
Bug#967125: marked as done (desmume: Unversioned Python removal in sid/bullseye)
Your message dated Sun, 20 Sep 2020 23:51:22 +0200 with message-id and subject line Re: desmume: Unversioned Python removal in sid/bullseye has caused the Debian Bug report #967125, regarding desmume: Unversioned Python removal in sid/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.) -- 967125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:desmume Version: 0.9.11-3 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- I believe this issue was fixed in libglade2-dev (#967157) and monster-masher was only affected by it back then. Hence I am going to close this bug report now. Markus signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#952686: closing 952686
close 952686 fixed 952686 4.3.0-2 thanks Hi, This bug has been fixed with the 4.3.0-2 upload. I am therefore closing this bug report. Cheers Cédric
Bug#957813: marked as done (slimevolley: ftbfs with GCC-10)
Your message dated Sun, 20 Sep 2020 21:50:05 + with message-id and subject line Bug#957813: fixed in slimevolley 2.4.2+dfsg-3 has caused the Debian Bug report #957813, regarding slimevolley: ftbfs with GCC-10 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.) -- 957813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957813 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:slimevolley Version: 2.4.2+dfsg-2 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/slimevolley_2.4.2+dfsg-2_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] /usr/bin/ld: CMakeFiles/slimevolley.dir/src/themes_general.o:./obj-x86_64-linux-gnu/./src/slime.h:96: multiple definition of `conf'; CMakeFiles/slimevolley.dir/src/audio.o:./obj-x86_64-linux-gnu/./src/slime.h:96: first defined here /usr/bin/ld: CMakeFiles/slimevolley.dir/src/themes_general.o:./obj-x86_64-linux-gnu/./src/slime.h:94: multiple definition of `tab_balles'; CMakeFiles/slimevolley.dir/src/audio.o:./obj-x86_64-linux-gnu/./src/slime.h:94: first defined here /usr/bin/ld: CMakeFiles/slimevolley.dir/src/themes_general.o:./obj-x86_64-linux-gnu/./src/slime.h:93: multiple definition of `nb_balles'; CMakeFiles/slimevolley.dir/src/audio.o:./obj-x86_64-linux-gnu/./src/slime.h:93: first defined here /usr/bin/ld: CMakeFiles/slimevolley.dir/src/themes_general.o:./obj-x86_64-linux-gnu/./src/slime.h:91: multiple definition of `touches'; CMakeFiles/slimevolley.dir/src/audio.o:./obj-x86_64-linux-gnu/./src/slime.h:91: first defined here /usr/bin/ld: CMakeFiles/slimevolley.dir/src/themes_general.o:./obj-x86_64-linux-gnu/./src/slime.h:90: multiple definition of `tab_joueurs'; CMakeFiles/slimevolley.dir/src/audio.o:./obj-x86_64-linux-gnu/./src/slime.h:90: first defined here /usr/bin/ld: CMakeFiles/slimevolley.dir/src/themes_general.o:./obj-x86_64-linux-gnu/./src/slime.h:71: multiple definition of `evenement'; CMakeFiles/slimevolley.dir/src/audio.o:./obj-x86_64-linux-gnu/./src/slime.h:71: first defined here /usr/bin/ld: CMakeFiles/slimevolley.dir/src/themes_std.o:./obj-x86_64-linux-gnu/./src/themes.h:51: multiple definition of `icone_fen'; CMakeFiles/slimevolley.dir/src/clavier.o:./obj-x86_64-linux-gnu/./src/themes.h:51: first defined here /usr/bin/ld: CMakeFiles/slimevolley.dir/src/themes_std.o:./obj-x86_64-linux-gnu/./src/themes.h:54: multiple definition of `img_max_jg'; CMakeFiles/slimevolley.dir/src/clavier.o:./obj-x86_64-linux-gnu/./src/themes.h:54: first defined here /usr/bin/ld: CMakeFiles/slimevolley.dir/src/themes_std.o:./obj-x86_64-linux-gnu/./src/themes.h:53: multiple definition of `img_grand_jg'; CMakeFiles/slimevolley.dir/src/clavier.o:./obj-x86_64-linux-gnu/./src/themes.h:53: first defined here /usr/bin/ld: CMakeFiles/slimevolley.dir/src/themes_std.o:./obj-x86_64-linux-gnu/./src/themes.h:54: multiple definition of `img_max_jd'; CMakeFiles/slimevolley.dir/src/clavier.o:./obj-x86_64-linux-gnu/./src/themes.h:54: first defined here /usr/bin/ld: CMakeFiles/slimevolley.dir/src/themes_std.o:./obj-x86_64-linux-gnu/./src/themes.h:53: multiple definition of `img_grand_jd'; CMakeFiles/slimevolley.dir/src/clavier.o:./obj-x86_64-linux-gnu/./src/themes.h:53: first defined here /usr/bin/ld: CMakeFiles/slimevolley.dir/src/themes_std.o:./obj-x86_64-linux-gnu/./src/themes.h:45: multiple definition of `theme_act'; CMakeFiles/slimevolley.dir/src/clavier.o:./obj-x86_64-linux-gnu/./src/themes.h:45: first defined
Bug#966214: marked as done (vienna-rna: FTBFS with GCC 10: multiple definition of ... due to -fno-common)
Your message dated Sun, 20 Sep 2020 21:50:20 + with message-id and subject line Bug#966214: fixed in vienna-rna 2.4.14+dfsg-2 has caused the Debian Bug report #966214, regarding vienna-rna: FTBFS with GCC 10: multiple definition of ... due to -fno-common 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.) -- 966214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vienna-rna Version: 2.4.14+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Hi, vienna-rna started to FTBFS when GCC 10 was made the default compiler: gcc -I./../../src/ViennaRNA -I./../../src -I/usr/include/json-c/ -I/usr/include/libsvm/ -Wl,-z,relro -o Kinfold baum.o cache.o globals.o main.o nachbar.o cmdline.o -fno-strict-aliasing -flto -L./../../src/ViennaRNA -lRNA -fopenmp -lgsl -lgslcblas -lmpfr -lgmp -lm /usr/bin/ld: globals.o:(.bss+0x0): multiple definition of `GSV'; baum.o:(.bss+0x0): first defined here /usr/bin/ld: globals.o:(.bss+0x60): multiple definition of `GAV'; baum.o:(.bss+0x60): first defined here /usr/bin/ld: globals.o:(.bss+0x8c0): multiple definition of `GTV'; baum.o:(.bss+0x8c0): first defined here /usr/bin/ld: main.o:(.bss+0x0): multiple definition of `GSV'; baum.o:(.bss+0x0): first defined here /usr/bin/ld: main.o:(.bss+0x60): multiple definition of `GAV'; baum.o:(.bss+0x60): first defined here /usr/bin/ld: main.o:(.bss+0x8c0): multiple definition of `GTV'; baum.o:(.bss+0x8c0): first defined here /usr/bin/ld: nachbar.o:(.bss+0x0): multiple definition of `GSV'; baum.o:(.bss+0x0): first defined here /usr/bin/ld: nachbar.o:(.bss+0x60): multiple definition of `GAV'; baum.o:(.bss+0x60): first defined here /usr/bin/ld: nachbar.o:(.bss+0x8c0): multiple definition of `GTV'; baum.o:(.bss+0x8c0): first defined here collect2: error: ld returned 1 exit status make[6]: *** [Makefile:485: Kinfold] Error 1 More information about the corresponding GCC change can be found here: https://gcc.gnu.org/gcc-10/porting_to.html "Default to -fno-common" Andreas --- End Message --- --- Begin Message --- Source: vienna-rna Source-Version: 2.4.14+dfsg-2 Done: Shayan Doust We believe that the bug you reported is fixed in the latest version of vienna-rna, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Shayan Doust (supplier of updated vienna-rna 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: Sun, 20 Sep 2020 20:50:20 +0100 Source: vienna-rna Architecture: source Version: 2.4.14+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Shayan Doust Closes: 966214 Changes: vienna-rna (2.4.14+dfsg-2) unstable; urgency=medium . [ Andreas Tille ] * Team upload. * debhelper-compat 13 (routine-update) * Remove trailing whitespace in debian/control (routine-update) * Remove trailing whitespace in debian/rules (routine-update) * Add salsa-ci file (routine-update) * Trim trailing whitespace. * debian/copyright: use spaces rather than tabs to start continuation lines. * Update renamed lintian tag names in lintian overrides. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Remove obsolete field Name from debian/upstream/metadata (already present in machine-readable debian/copyright). . [ Shayan Doust ] * Patch to fix gcc-10 FTBFS (Closes: #966214) * override_dh_missing for now due to mass files not installed Checksums-Sha1: 223d5865c07d9294075a079501801554c877c6f6 2462 vienna-rna_2.4.14+dfsg-2.dsc 38c2256a9d7cafea1a28bb10c807c59455d575e9 10208 vienna-rna_2.4.14+dfsg-2.debian.tar.xz 0fac7393d4524b6f1769cf1200bc1568658e40ca 11104 vienna-rna_2.4.14+dfsg-2_amd64.buildinfo Checksums-Sha256: 8ce72ac8d56847c4b0af6a05deff50153e4563673721ce22673f94fd0bce3ac5 2462 vienna-rna_2.4.14+dfsg-2.dsc 05b46be438e5fbd0c20b2e95ff4b9f21035306a855e865f73e88ab11d56d1aa2 10208
Processed: closing 952686
Processing commands for cont...@bugs.debian.org:
> close 952686
Bug #952686 [ruby-shoulda-matchers] ruby-shoulda-matchers: installs files with
generic names in /usr/bin
Marked Bug as done
> fixed 952686 4.3.0-2
Bug #952686 {Done: Cédric Boutillier }
[ruby-shoulda-matchers] ruby-shoulda-matchers: installs files with generic
names in /usr/bin
Marked as fixed in versions ruby-shoulda-matchers/4.3.0-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
952686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#957671: marked as done (pcsxr: ftbfs with GCC-10)
Your message dated Sun, 20 Sep 2020 21:35:23 + with message-id and subject line Bug#957671: fixed in pcsxr 1.9.94-5 has caused the Debian Bug report #957671, regarding pcsxr: ftbfs with GCC-10 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.) -- 957671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pcsxr Version: 1.9.94-4 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/pcsxr_1.9.94-4_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] | ~ ConfDlg.c: In function ‘OnConf_Sio1’: ConfDlg.c:308:22: warning: ‘%s’ directive writing up to 4095 bytes into a region of size between 0 and 4095 [-Wformat-overflow=] 308 | sprintf(Plugin, "%s/%s", Config.PluginsDir, Config.Sio1); | ^~ ~~~ In file included from /usr/include/stdio.h:867, from ConfDlg.c:19: /usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: ‘__builtin___sprintf_chk’ output between 2 and 8192 bytes into a destination of size 4096 36 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1, | ^~ 37 | __bos (__s), __fmt, __va_arg_pack ()); | ~ ConfDlg.c: In function ‘OnConf_Pad’: ConfDlg.c:329:22: warning: ‘%s’ directive writing up to 4095 bytes into a region of size between 0 and 4095 [-Wformat-overflow=] 329 | sprintf(Plugin, "%s/%s", Config.PluginsDir, Config.Pad1); | ^~ ~~~ In file included from /usr/include/stdio.h:867, from ConfDlg.c:19: /usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: ‘__builtin___sprintf_chk’ output between 2 and 8192 bytes into a destination of size 4096 36 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1, | ^~ 37 | __bos (__s), __fmt, __va_arg_pack ()); | ~ ConfDlg.c:345:23: warning: ‘%s’ directive writing up to 4095 bytes into a region of size between 0 and 4095 [-Wformat-overflow=] 345 | sprintf(Plugin, "%s/%s", Config.PluginsDir, Config.Pad2); | ^~ ~~~ In file included from /usr/include/stdio.h:867, from ConfDlg.c:19: /usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: ‘__builtin___sprintf_chk’ output between 2 and 8192 bytes into a destination of size 4096 36 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1, | ^~ 37 | __bos (__s), __fmt, __va_arg_pack ()); | ~ ConfDlg.c: In function ‘FindNetPlugin’: ConfDlg.c:807:24: warning: ‘%s’ directive writing up to 255 bytes into a region of size between 0 and 4095 [-Wformat-overflow=] 807 |sprintf(plugin, "%s/%s", Config.PluginsDir, ent->d_name); |^~ In file included from /usr/include/stdio.h:867, from ConfDlg.c:19: /usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: ‘__builtin___sprintf_chk’ output between 2 and 4352 bytes into a destination of size 4096 36 | return __builtin___sprintf_chk (__s,
Processed: found 970638 in 0.3.8-1
Processing commands for cont...@bugs.debian.org: > found 970638 0.3.8-1 Bug #970638 [jag] jag: cannot upgrade from 3.6-1 to 3.8-1 Marked as found in versions jag/0.3.8-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 970638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#956084: marked as done (inetutils-telnetd: CVE-2020-10188)
Your message dated Sun, 20 Sep 2020 21:32:09 + with message-id and subject line Bug#956084: fixed in inetutils 2:1.9.4-7+deb10u1 has caused the Debian Bug report #956084, regarding inetutils-telnetd: CVE-2020-10188 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.) -- 956084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: inetutils-telnetd Severity: critical Tags: security Justification: root security hole Looking in https://security-tracker.debian.org/tracker/CVE-2020-10188 : utility.c in telnetd in netkit telnet through 0.17 allows remote attackers to execute arbitrary code via short writes or urgent data, because of a buffer overflow involving the netclear and nextitem functions. Seems to me that inetutils contains the same (vulnerable) utility.c functions. Please check. Cheers, Paul Paul Szabo p...@maths.usyd.edu.au www.maths.usyd.edu.au/u/psz School of Mathematics and Statistics University of SydneyAustralia --- End Message --- --- Begin Message --- Source: inetutils Source-Version: 2:1.9.4-7+deb10u1 Done: =?utf-8?q?Moritz_M=C3=BChlenhoff?= We believe that the bug you reported is fixed in the latest version of inetutils, 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 956...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Moritz Mühlenhoff (supplier of updated inetutils 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: Fri, 18 Sep 2020 20:06:42 +0200 Source: inetutils Binary: inetutils-ftp inetutils-ftp-dbgsym inetutils-ftpd inetutils-ftpd-dbgsym inetutils-inetd inetutils-inetd-dbgsym inetutils-ping inetutils-ping-dbgsym inetutils-syslogd inetutils-syslogd-dbgsym inetutils-talk inetutils-talk-dbgsym inetutils-talkd inetutils-talkd-dbgsym inetutils-telnet inetutils-telnet-dbgsym inetutils-telnetd inetutils-telnetd-dbgsym inetutils-tools inetutils-tools-dbgsym inetutils-traceroute inetutils-traceroute-dbgsym Architecture: source amd64 Version: 2:1.9.4-7+deb10u1 Distribution: buster Urgency: medium Maintainer: Guillem Jover Changed-By: Moritz Mühlenhoff Description: inetutils-ftp - File Transfer Protocol client inetutils-ftpd - File Transfer Protocol server inetutils-inetd - internet super server inetutils-ping - ICMP echo tool inetutils-syslogd - system logging daemon inetutils-talk - talk to another user inetutils-talkd - remote user communication server inetutils-telnet - telnet client inetutils-telnetd - telnet server inetutils-tools - base networking utilities (experimental package) inetutils-traceroute - trace the IPv4 route to another host Closes: 956084 Changes: inetutils (2:1.9.4-7+deb10u1) buster; urgency=medium . * CVE-2020-10188 (Closes: #956084) Checksums-Sha1: f549ec0fd8f738d784d7f40860d44403273c695d 2739 inetutils_1.9.4-7+deb10u1.dsc c4f6c39284000956a6fd0a90a637897dd1b9dd88 96628 inetutils_1.9.4-7+deb10u1.debian.tar.xz 1e6a97b9de7763953df07079088c61ce354c95cd 186224 inetutils-ftp-dbgsym_1.9.4-7+deb10u1_amd64.deb 05fe489666325b390e7527deb9c2d233edd01353 250296 inetutils-ftp_1.9.4-7+deb10u1_amd64.deb 30cac7005a242c499518fb3cadbe1335b77ab265 202860 inetutils-ftpd-dbgsym_1.9.4-7+deb10u1_amd64.deb 0faa416d6f7ede49c74277d4f84162900f9d9ead 247524 inetutils-ftpd_1.9.4-7+deb10u1_amd64.deb 9b060bd0795f2744553ff0247c2796dc3282f006 108552 inetutils-inetd-dbgsym_1.9.4-7+deb10u1_amd64.deb abf8dc1f4c4edf357e3851e3e0c82f18d9cb40af 220368 inetutils-inetd_1.9.4-7+deb10u1_amd64.deb 2a88b1b1f4ed469f2c7b72ce51edb844c664ff39 209936 inetutils-ping-dbgsym_1.9.4-7+deb10u1_amd64.deb 4a114aabe6ef41e7b7df8bcdeb0f7a413853942e 226336 inetutils-ping_1.9.4-7+deb10u1_amd64.deb bc8878e075918ee3043c144b6fd293dfb9b94a40 115528 inetutils-syslogd-dbgsym_1.9.4-7+deb10u1_amd64.deb cc77073a041dcc114b8d7434ccb40779ffe62212 223676 inetutils-syslogd_1.9.4-7+deb10u1_amd64.deb b3b6bb716b76ef8de08c75b0da80be439e07b00f 103828 inetutils-talk-dbgsym_1.9.4-7+deb10u1_amd64.deb e40384cc1d92fa8a2c87ee9b6e93e539786b056b 209308 inetutils-talk_1.9.4-7+deb10u1_amd64.deb
Processed: Bug#957671 marked as pending in pcsxr
Processing control commands: > tag -1 pending Bug #957671 [src:pcsxr] pcsxr: ftbfs with GCC-10 Added tag(s) pending. -- 957671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957671: marked as pending in pcsxr
Control: tag -1 pending Hello, Bug #957671 in pcsxr 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/games-team/pcsxr/-/commit/ad106eb96a557077bb0558ae19fe1fd02f44eeb6 Work around FTBFS with GCC 10 and build with -fcommon. Closes: #957671 (this message was generated automatically) -- Greetings https://bugs.debian.org/957671
Bug#967174: marked as done (monster-masher: Unversioned Python removal in sid/bullseye)
Your message dated Sun, 20 Sep 2020 23:03:25 +0200 with message-id <10467f00-4c7c-195f-e52f-d42cfdc42...@debian.org> and subject line Re: Bug#967174: monster-masher: Unversioned Python removal in sid/bullseye has caused the Debian Bug report #967174, regarding monster-masher: Unversioned Python removal in sid/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.) -- 967174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967174 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:monster-masher Version: 1.8.1-8 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- On Tue, 18 Aug 2020 18:24:53 +0200 Graham Inggs wrote: > Hi Vincent > > On Tue, 18 Aug 2020 at 10:54, Vincent Cheng wrote: > > src:monster-masher has no build dependencies on python2, the only > > binary package it builds (monster-masher) has no runtime dependencies > > on python2, and this package has no autopkgtests. There's actually not > > a single line of python in this package. Can I go ahead and close this > > bug, or have I missed something? > > This may have been due to libglade2-dev not being installable (#967157) > > Regards > Graham I believe this issue was fixed in libglade2-dev and monster-masher was only affected by it back then. Hence I am going to close this bug report now. Markus signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#832931: marked as done (mariadb-10.0: FTBFS on powerpc)
Your message dated Mon, 21 Sep 2020 00:00:42 +0300 with message-id and subject line Re: Bug#832931: Bug#843926: jemalloc hard codes page size during build has caused the Debian Bug report #832931, regarding mariadb-10.0: FTBFS on powerpc 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.) -- 832931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mariadb-10.0 Version: 10.0.26-0+deb8u1 Severity: serious Justification: FTBFS Hi The recent mariadb-10.0 upload of 10.0.26-0+deb8u1 for jessie-security FTBFS on powerpc. I have attached the build log from buildd and the hanging build was reproducible on porterbox partch.debian.org for powerpc. Regards, Salvatore mariadb-10.0_10.0.26-0+deb8u1_powerpc-20160726-0537.gz Description: application/gzip --- End Message --- --- Begin Message --- There are no Debian buiildd logs around anymore to verify what the status for mariadb-10.0 was, but upstream did fix this and at least newer builds fine for powerpc: - mariadb-10.5: https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.5=powerpc=1%3A10.5.5-1%7Eexp1=1599932120=0 - mariadb-10.3: https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.3=powerpc=1%3A10.3.24-2=1599056427=0--- End Message ---
Bug#969261: fixed in cyrus-imapd 3.2.3-2
Control: reopen -1 Control: tags -1 + moreinfo Le 20/09/2020 à 22:18, Andy Dorman a écrit : > On Sun, 13 Sep 2020 16:18:27 + Debian FTP Masters > wrote: >> Source: cyrus-imapd >> Source-Version: 3.2.3-2 >> Done: Xavier Guimard >> >> We believe that the bug you reported is fixed in the latest version of >> cyrus-imapd, 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 969...@bugs.debian.org, >> and the maintainer will reopen the bug report if appropriate. >> >> Debian distribution maintenance software >> pp. >> Xavier Guimard (supplier of updated cyrus-imapd >> 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) >> > > Just FYI in case it might help someone. > > I had the same problem but simeply upgrading from 3.2.3-1 to 3.2.3-2 did > not allow cyrus-imapd to run. I had to manually recreate the /run/cyrus > dir and sub-directories with correct cyrus.mail ownership and > permissions before cyrus-imapd would start. > > ~# ls -al /run/cyrus > drwxr-xr-x 5 cyrus mail 100 Jan 18 2020 . > drwxr-xr-x 31 root root 1140 Sep 20 13:03 .. > drwx-- 5 cyrus mail 100 Jun 5 12:49 lock > drwx-- 2 cyrus mail 40 Sep 20 15:15 proc > drwxr-x--- 2 cyrus mail 60 Sep 20 13:03 socket Hi, I didn't succeed to reproduce this bug
Processed: Re: Bug#969261: fixed in cyrus-imapd 3.2.3-2
Processing control commands: > reopen -1 Bug #969261 [cyrus-imapd] cyrus-imapd: the service cyrus-imapd.service refuses to start after the upgrade of cyrus-imapd.3.2.3 from cyrus-imapd.3.2.2 and a reboot Bug 969261 is not marked as done; doing nothing. > tags -1 + moreinfo Bug #969261 [cyrus-imapd] cyrus-imapd: the service cyrus-imapd.service refuses to start after the upgrade of cyrus-imapd.3.2.3 from cyrus-imapd.3.2.2 and a reboot Added tag(s) moreinfo. -- 969261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reopening 969261
Processing commands for cont...@bugs.debian.org:
> reopen 969261
Bug #969261 {Done: Xavier Guimard } [cyrus-imapd] cyrus-imapd:
the service cyrus-imapd.service refuses to start after the upgrade of
cyrus-imapd.3.2.3 from cyrus-imapd.3.2.2 and a reboot
'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 cyrus-imapd/3.2.3-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
969261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969261
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#969261: fixed in cyrus-imapd 3.2.3-2
On Sun, 13 Sep 2020 16:18:27 + Debian FTP Masters wrote: Source: cyrus-imapd Source-Version: 3.2.3-2 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of cyrus-imapd, 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 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated cyrus-imapd 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) Just FYI in case it might help someone. I had the same problem but simeply upgrading from 3.2.3-1 to 3.2.3-2 did not allow cyrus-imapd to run. I had to manually recreate the /run/cyrus dir and sub-directories with correct cyrus.mail ownership and permissions before cyrus-imapd would start. ~# ls -al /run/cyrus drwxr-xr-x 5 cyrus mail 100 Jan 18 2020 . drwxr-xr-x 31 root root 1140 Sep 20 13:03 .. drwx-- 5 cyrus mail 100 Jun 5 12:49 lock drwx-- 2 cyrus mail 40 Sep 20 15:15 proc drwxr-x--- 2 cyrus mail 60 Sep 20 13:03 socket
Bug#970656: r-cran-isospecr: missing (unversioned) Breaks+Replaces: r-cran-isospec
Package: r-cran-isospecr Version: 2.1.2-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces This test intentionally skipped 'testing' to find file overwrite problems before packages migrate from 'unstable' to 'testing'. >From the attached log (scroll to the bottom...): Preparing to unpack .../r-cran-isospecr_2.1.2-2_amd64.deb ... Unpacking r-cran-isospecr (2.1.2-2) ... dpkg: error processing archive /var/cache/apt/archives/r-cran-isospecr_2.1.2-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/R/site-library/IsoSpecR/DESCRIPTION', which is also in package r-cran-isospec 1.9.1-5 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/r-cran-isospecr_2.1.2-2_amd64.deb cheers, Andreas r-cran-isospec=1.9.1-5_r-cran-isospecr=2.1.2-2.log.gz Description: application/gzip
Bug#970651: [Pkg-javascript-devel] Bug#970651: rollup: Unable to build with current tsc
Le 20/09/2020 à 22:08, Pirate Praveen a écrit : > > > On 2020, സെപ്റ്റംബർ 21 12:38:37 AM IST, Xavier Guimard > wrote: >> Package: rollup >> Version: 1.12.0-2 >> Severity: serious >> Tags: ftbfs >> Justification: Policy 7.7.7 >> >> node-rollup 1.12.0 can't be build with current typescript (4.0.2). It >> requires tsc 3.4.5 (tested with success). Output: > > I think the root cause is uploading major versions without coordination. It > should have been easily found out if all packages using typescript was > rebuilt before it was uploaded to unstable. > > I think we should create a release team within js team to handle it like how > release team works for transitions. +1
Bug#970651: [Pkg-javascript-devel] Bug#970651: rollup: Unable to build with current tsc
On 2020, സെപ്റ്റംബർ 21 12:38:37 AM IST, Xavier Guimard wrote: >Package: rollup >Version: 1.12.0-2 >Severity: serious >Tags: ftbfs >Justification: Policy 7.7.7 > >node-rollup 1.12.0 can't be build with current typescript (4.0.2). It >requires tsc 3.4.5 (tested with success). Output: I think the root cause is uploading major versions without coordination. It should have been easily found out if all packages using typescript was rebuilt before it was uploaded to unstable. I think we should create a release team within js team to handle it like how release team works for transitions. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#970654: libncarg-dev: ships libncl.a already provided by libncl-dev
Package: libncarg-dev Version: 6.6.2-3 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...): Selecting previously unselected package libncarg-dev:amd64. Preparing to unpack .../137-libncarg-dev_6.6.2-3_amd64.deb ... Unpacking libncarg-dev:amd64 (6.6.2-3) ... dpkg: error processing archive /tmp/apt-dpkg-install-vVrpbS/137-libncarg-dev_6.6.2-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libncl.a', which is also in package libncl-dev 2.1.21+git20190531.feceb81-3 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-vVrpbS/137-libncarg-dev_6.6.2-3_amd64.deb cheers, Andreas libncl-dev=2.1.21+git20190531.feceb81-3_libncarg-dev=6.6.2-3.log.gz Description: application/gzip
Processed: Bug#966214 marked as pending in vienna-rna
Processing control commands: > tag -1 pending Bug #966214 [src:vienna-rna] vienna-rna: FTBFS with GCC 10: multiple definition of ... due to -fno-common Added tag(s) pending. -- 966214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969436: marked as done (libsnmp-dev: missing Breaks+Replaces: libsnmp-perl (<< 5.9))
Your message dated Sun, 20 Sep 2020 21:29:13 +0200 with message-id <66fed510-462a-f9e1-1ccf-9874d68aa...@debian.org> and subject line Re: closed in net-snmp 5.9+dfsg-2 has caused the Debian Bug report #969436, regarding libsnmp-dev: missing Breaks+Replaces: libsnmp-perl (<< 5.9) 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.) -- 969436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libsnmp-dev Version: 5.9+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libsnmp-dev_5.9+dfsg-1_amd64.deb ... Unpacking libsnmp-dev (5.9+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/libsnmp-dev_5.9+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man3/SNMP.3pm.gz', which is also in package libsnmp-perl 5.8+dfsg-5 Errors were encountered while processing: /var/cache/apt/archives/libsnmp-dev_5.9+dfsg-1_amd64.deb cheers, Andreas libsnmp-perl=5.8+dfsg-5_libsnmp-dev=5.9+dfsg-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Version: 5.9+dfsg-2 Hi Craig, On Mon, 14 Sep 2020 14:15:38 +1000 Craig Small wrote: > Package: libsnmp-dev > Version: 5.9+dfsg-2 libsnmp-dev wasn't the package that this bug filed against at the moment you closed it. So, the bts doesn't consider the bug closed in unstable. (Hopefully I fixed that now, if not, I'll try harder). Paul signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#966214: marked as pending in vienna-rna
Control: tag -1 pending Hello, Bug #966214 in vienna-rna 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/med-team/vienna-rna/-/commit/daf364342855c34c4e29545b4cadd1993232840a Patch to fix gcc-10 FTBFS (Closes: #966214) (this message was generated automatically) -- Greetings https://bugs.debian.org/966214
Bug#969436: closed in net-snmp 5.9+dfsg-2
Hi On 20-09-2020 21:29, Paul Gevers wrote: > On Mon, 14 Sep 2020 14:15:38 +1000 Craig Small wrote: >> Package: libsnmp-dev >> Version: 5.9+dfsg-2 > > libsnmp-dev wasn't the package that this bug filed against at the moment > you closed it. So, the bts doesn't consider the bug closed in unstable. > (Hopefully I fixed that now, if not, I'll try harder). This text is obviously nonsense about the package part. It's still true about the bts part. Paul signature.asc Description: OpenPGP digital signature
Bug#970651: rollup: Unable to build with current tsc
Package: rollup Version: 1.12.0-2 Severity: serious Tags: ftbfs Justification: Policy 7.7.7 node-rollup 1.12.0 can't be build with current typescript (4.0.2). It requires tsc 3.4.5 (tested with success). Output: $ tsc --esModuleInterop src/ModuleLoader.ts:59:3 - error TS2322: Type '(id: string) => boolean' is not assignable to type '(id: string, ...args: T) => boolean'. Types of parameters 'id' and 'id' are incompatible. Type '[id: string, ...args: T]' is not assignable to type '[id: string]'. Source has 2 element(s) but target allows only 1. 59 return id => ids.has(id); ~
Bug#970608: src:coreutils: fails to migrate to testing for too long: FTBFS on arm64
Hi Michael, On 20-09-2020 18:21, Michael Stone wrote: > I thought debports architectures weren't supposed to prevent migration > to testing so I'm confused about why the package hasn't migrated. arm64 is a release architecture, already since jessie. https://www.debian.org/releases/jessie/ Paul signature.asc Description: OpenPGP digital signature
Bug#966831: marked as done (patat: Cannot fulfill the build dependencies)
Your message dated Sun, 20 Sep 2020 16:34:05 + with message-id and subject line Bug#966831: fixed in patat 0.8.6.1-1 has caused the Debian Bug report #966831, regarding patat: Cannot fulfill the build dependencies 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.) -- 966831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: patat Version: 0.8.4.0-1 Severity: serious Tags: ftbfs The following packages have unmet dependencies: builddeps:patat : Depends: libghc-ansi-terminal-dev (< 0.10) but 0.10.3-1 is to be installed Depends: libghc-pandoc-dev (< 2.8) but 2.9.1.1-3 is to be installed --- End Message --- --- Begin Message --- Source: patat Source-Version: 0.8.6.1-1 Done: =?utf-8?q?F=C3=A9lix_Sipma?= We believe that the bug you reported is fixed in the latest version of patat, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Félix Sipma (supplier of updated patat 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: Sun, 20 Sep 2020 18:07:59 +0200 Source: patat Architecture: source Version: 0.8.6.1-1 Distribution: unstable Urgency: medium Maintainer: Félix Sipma Changed-By: Félix Sipma Closes: 966831 Changes: patat (0.8.6.1-1) unstable; urgency=medium . * New upstream version 0.8.6.1 (Closes: #966831) * update Build-Depends * add patch to prevent building with stack when building the manpage * bump Standards-Version to 4.5.0 (no change required) * remove "-guest" suffix from Vcs-Git and Vcs-Browser * disable tests for now (goldplate not packaged yet) Checksums-Sha1: 05ed89b6b769f2880fe137d4d1eb74e0b3025a3d 2570 patat_0.8.6.1-1.dsc 4d1a42dcc160dd1014f982fca70fc74be6bfccf0 105658 patat_0.8.6.1.orig.tar.gz 72829d519c100e9946371d2e731bf69e103b53f5 3692 patat_0.8.6.1-1.debian.tar.xz Checksums-Sha256: 4ba4d5de4e721ecc9239780d92caacb7b41bb1c200644f6e714201ac1be42593 2570 patat_0.8.6.1-1.dsc b571511537bd75445f042061728f779beace93084bccee481027bfc1baaf9313 105658 patat_0.8.6.1.orig.tar.gz 1afcd9d2eb2b95e8022803b9ab0419dacb10d4261ccfde8beca5d3ecfeaf747c 3692 patat_0.8.6.1-1.debian.tar.xz Files: 491c7a5e3be0d4691346c78fbbc637df 2570 haskell optional patat_0.8.6.1-1.dsc 33d8f27c6073fcdf39280ae125992278 105658 haskell optional patat_0.8.6.1.orig.tar.gz bf5877b6e19970f2bc9a078d4616caa5 3692 haskell optional patat_0.8.6.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQR6zeIsS8L0XLQfqiQBpfxHUdFE8AUCX2d/ZwAKCRABpfxHUdFE 8GsiAPwNZLXBJ4UzwUj1cin1F/KNguI1jQLzVZWbUSkEeEGDcgD/dDUlcT+WORRF +Tl2RC3T6qYhXUvSKP4tDsXc8NhkXwM= =eb2/ -END PGP SIGNATURE End Message ---
Bug#970608: src:coreutils: fails to migrate to testing for too long: FTBFS on arm64
I thought debports architectures weren't supposed to prevent migration to testing so I'm confused about why the package hasn't migrated.
Bug#970638: jag: cannot upgrade from 3.6-1 to 3.8-1
Package: jag Version: 0.3.6-1 Severity: serious Justification: Policy 7.6.1 Dear Maintainer, Trying to upgrade jag from 3.6-1 to 3.8-1 fails, because the upgrade tries to overwrite files of jag-data. See the following apt upgrade output: Do you want to continue? [Y/n] Reading changelogs... Done (Reading database ... 248298 files and directories currently installed.) Preparing to unpack .../archives/jag_0.3.8-1_amd64.deb ... Unpacking jag (0.3.8-1) over (0.3.6-1) ... dpkg: error processing archive /var/cache/apt/archives/jag_0.3.8-1_amd64.deb (--unpack): trying to overwrite '/usr/share/games/jag/data/bonus/clock.png', which is also in package jag-data 0.3.6-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/jag_0.3.8-1_amd64.deb Have you moved clock.png without setting Breaks+Replaces properly as mentioned in policy 7.6.1? https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-in-other-packages -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (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 jag depends on: ii jag-data 0.3.6-1 ii libc62.31-3 ii libgcc-s110.2.0-9 ii libqt5core5a 5.14.2+dfsg-6 ii libqt5gui5 5.14.2+dfsg-6 ii libqt5opengl55.14.2+dfsg-6 ii libqt5widgets5 5.14.2+dfsg-6 ii libqt5x11extras5 5.14.2-2 ii libsdl2-2.0-02.0.12+dfsg1-2 ii libsdl2-mixer-2.0-0 2.0.4+dfsg1-2+b1 ii libstdc++6 10.2.0-9 ii libx11-6 2:1.6.12-1 ii libxrandr2 2:1.5.1-1 jag recommends no packages. jag suggests no packages. -- no debconf information
Bug#970462: marked as done (sweed: autopkgtest arm64 failure)
Your message dated Sun, 20 Sep 2020 15:34:17 + with message-id and subject line Bug#970462: fixed in sweed 3.2.1+dfsg-4 has caused the Debian Bug report #970462, regarding sweed: autopkgtest arm64 failure 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.) -- 970462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970462 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sweed Version: 3.2.1+dfsg-3 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package sweed, great. However, it fails on arm64. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? Paul [1] https://qa.debian.org/excuses.php?package=sweed https://ci.debian.net/data/autopkgtest/testing/arm64/s/sweed/6835041/log.gz signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: sweed Source-Version: 3.2.1+dfsg-4 Done: =?utf-8?q?=C3=89tienne_Mollier?= We believe that the bug you reported is fixed in the latest version of sweed, 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 970...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated sweed 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: Sun, 20 Sep 2020 16:43:53 +0200 Source: sweed Architecture: source Version: 3.2.1+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 970462 Changes: sweed (3.2.1+dfsg-4) unstable; urgency=medium . * Team upload. * Added patch for running autopkgtest on ARM64. (Closes: #970462) Checksums-Sha1: e93c276d816bb3e85dfa7e6574e3dd650d2e71f4 1982 sweed_3.2.1+dfsg-4.dsc 07859d811e785e59ec7572ee86c93f2fdb69e26e 7448 sweed_3.2.1+dfsg-4.debian.tar.xz 47282893b3fd536c611aa4be9bc0f4a03325a42d 5761 sweed_3.2.1+dfsg-4_amd64.buildinfo Checksums-Sha256: 8ae0f1aaae268e7c36139bd3f69849fdd8d06e32441b963637d610b4d6547686 1982 sweed_3.2.1+dfsg-4.dsc 14a67a1c399732269dc2ad5c987312d7e3fb6472ea813b214e21d965b8a4804a 7448 sweed_3.2.1+dfsg-4.debian.tar.xz c973865fad9f4acc0250ea96152f200a9b8ad0e6ac8413c6f0c0440b41a67a51 5761 sweed_3.2.1+dfsg-4_amd64.buildinfo Files: aa82d5b36e241df1afaa3b4158909b38 1982 science optional sweed_3.2.1+dfsg-4.dsc d581dc311f9bdbbe8403e7bec94a599c 7448 science optional sweed_3.2.1+dfsg-4.debian.tar.xz 37af7fca82208183d9e18163d92a9bcb 5761 science optional sweed_3.2.1+dfsg-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAl9nchYUHG5wYXRyYTk3 NEBnbWFpbC5jb20ACgkQALrnSzQzafHriQ/9FfM4drVYUcUAYjkMv6RNKdux5J0w 7BVGKwXcsxWIwslhKzSawx6GcFlPH2OfcRQ/E3RLzwrPaqQI/4JvfkAlsGYQZ80O ZHaLu8Ymm3IA86FZrrlkeg44U2wHg94xdmIXCHTpZ3ZWtEwxf+zkIKBUAbsLSQJG STm6NpCRpoUnsVFxRsFReE7eH1ujCVPLdUlQKbHn7g01+Zbaun4/DzqmVrt/krOX CXKL1KvB9e0gLj7NUfzOGu1ti7O+wlqjVeVnuMRFXpCAciW1paa1cl/gKnyJ/+Qw i+o0FHrkuz1r5u8sUK/skdZ8f9hA42DuEshJ/tALRa8dNx0FSJXHdkkne9KgB4/V axpW6PnCoe8E0wWYLBKBkdP8ptu3JLMdq3i7jtYDD1l7KZhEd/kZ/1rDZNaQ0T45 WsGQOZW6KzDJHRAwdypVN57mu2Cv9cleyv0Fa1qgmIjeqtIaekKiu/2CQi5uhscv HzS6zMP7tIy7xaKRR17UJCJivWkwrlc+rCwMaKYEOdmjdP8mSOtLWTm7ay1Hiz9E dEYUH6zjMiwR+EM9niYiHXDJZ7kkmKrJzDaNt3mQJsnipKStqHLR/3ZEK/ckD/Ia 5iODNcz94q/cIf9EhNlO/MvsHuthamlJWkkmxJ2Nn2J+OHBBNMUDuayE9i9lLpHK z4a10stVlRmhTPI= =EzxQ -END PGP SIGNATURE End Message ---
Bug#970462: [RFS] Bug#970462: sweed: autopkgtest arm64 failure
Hi, On Sun, 20 Sep 2020 at 20:34, Étienne Mollier wrote: > Control: tags -1 pending > > Greetings, > > I tried to investigate the issue of running SweeD autopkgtests > on arm64. It turned out to be caused by the assumption that the > "char" type was "signed" by default, while it is "unsigned" by > default at least on arm64. The patch I added makes several > targeted changes, so that the test suite goes through without > either crashing (segfault) or hanging (infinite loop). > > I also tried to ensure test results were unchanged compared to > other CPU architectures, and as far as I could see, they the > same on arm64 (with the patch) and on amd64 (without the patch). > > Changes are available on Salsa for review: > > https://salsa.debian.org/med-team/sweed > > Thanks Paul for having reported the issue, and Thanks Nilesh for > having written the test suite that allowed to catch the bug! :) > Thanks a lot! Uploaded! Kind Regards Nilesh
Bug#970462: [RFS] Bug#970462: sweed: autopkgtest arm64 failure
Control: tags -1 pending Greetings, I tried to investigate the issue of running SweeD autopkgtests on arm64. It turned out to be caused by the assumption that the "char" type was "signed" by default, while it is "unsigned" by default at least on arm64. The patch I added makes several targeted changes, so that the test suite goes through without either crashing (segfault) or hanging (infinite loop). I also tried to ensure test results were unchanged compared to other CPU architectures, and as far as I could see, they the same on arm64 (with the patch) and on amd64 (without the patch). Changes are available on Salsa for review: https://salsa.debian.org/med-team/sweed Thanks Paul for having reported the issue, and Thanks Nilesh for having written the test suite that allowed to catch the bug! :) Kind Regards, -- Étienne Mollier Old rsa/3072: 5ab1 4edf 63bb ccff 8b54 2fa9 59da 56fe fff3 882d New rsa/4096: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity. signature.asc Description: PGP signature
Processed: [RFS] Bug#970462: sweed: autopkgtest arm64 failure
Processing control commands: > tags -1 pending Bug #970462 [src:sweed] sweed: autopkgtest arm64 failure Added tag(s) pending. -- 970462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970462 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957602: marked as done (nettoe: ftbfs with GCC-10)
Your message dated Sun, 20 Sep 2020 14:50:08 + with message-id and subject line Bug#957602: fixed in nettoe 1.5.1-3 has caused the Debian Bug report #957602, regarding nettoe: ftbfs with GCC-10 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.) -- 957602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nettoe Version: 1.5.1-2 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/nettoe_1.5.1-2_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] Build:x86_64-pc-linux-gnu Host: x86_64-pc-linux-gnu make[1]: Leaving directory '/<>' dh_auto_build make -j1 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in src make[3]: Entering directory '/<>/src' gcc -DNETTOE_PORT=7501 -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -MT ai.o -MD -MP -MF .deps/ai.Tpo -c -o ai.o ai.c mv -f .deps/ai.Tpo .deps/ai.Po gcc -DNETTOE_PORT=7501 -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -MT board.o -MD -MP -MF .deps/board.Tpo -c -o board.o board.c mv -f .deps/board.Tpo .deps/board.Po gcc -DNETTOE_PORT=7501 -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -MT nettoe.o -MD -MP -MF .deps/nettoe.Tpo -c -o nettoe.o nettoe.c nettoe.c: In function ‘main’: nettoe.c:120:3: warning: ignoring return value of ‘setegid’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 120 | setegid(getgid()); | ^ nettoe.c:121:3: warning: ignoring return value of ‘setgid’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 121 | setgid(getgid()); | ^~~~ nettoe.c:122:3: warning: ignoring return value of ‘seteuid’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 122 | seteuid(getuid()); | ^ nettoe.c:123:3: warning: ignoring return value of ‘setuid’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 123 | setuid(getuid()); | ^~~~ mv -f .deps/nettoe.Tpo .deps/nettoe.Po gcc -DNETTOE_PORT=7501 -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -MT matrices.o -MD -MP -MF .deps/matrices.Tpo -c -o matrices.o matrices.c mv -f .deps/matrices.Tpo .deps/matrices.Po gcc -DNETTOE_PORT=7501 -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -MT terminal.o -MD -MP -MF .deps/terminal.Tpo -c -o terminal.o terminal.c terminal.c: In function ‘nettoe_term_set_color’: terminal.c:194:33: warning: ‘%d’ directive writing between 1 and 11 bytes into a region of size between 0 and 9 [-Wformat-overflow=] 194 | sprintf(cmd_str, "%c[%d;%dm", 0x1B, attrib, fg + 30); | ^~ terminal.c:194:26: note: directive argument in the range [-2147483618, 2147483647] 194 | sprintf(cmd_str, "%c[%d;%dm", 0x1B, attrib, fg + 30); | ^~~ In file included from
Processed: severity of 961373 is serious
Processing commands for cont...@bugs.debian.org: > # failed again > https://buildd.debian.org/status/fetch.php?pkg=slic3r-prusa=armhf=2.2.0%2Bdfsg1-2%2Bb2=1599918705=0 > severity 961373 serious Bug #961373 [src:slic3r-prusa] slic3r-prusa FTBFS on armhf: cc1plus: out of memory Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 961373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 948364 is important
Processing commands for cont...@bugs.debian.org: > # reduce severity until more info is provided > severity 948364 important Bug #948364 [audacity] audacity leaks memory and crashes Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 948364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970633: tt-rss: CVE-2020-25787 CVE-2020-25788 CVE-2020-25789
Source: tt-rss Version: 19.8+dfsg-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for tt-rss. CVE-2020-25787[0]: | An issue was discovered in Tiny Tiny RSS (aka tt-rss) before | 2020-09-16. It does not validate all URLs before requesting them. CVE-2020-25788[1]: | An issue was discovered in Tiny Tiny RSS (aka tt-rss) before | 2020-09-16. imgproxy in plugins/af_proxy_http/init.php mishandles | $_REQUEST["url"] in an error message. CVE-2020-25789[2]: | An issue was discovered in Tiny Tiny RSS (aka tt-rss) before | 2020-09-16. The cached_url feature mishandles JavaScript inside an SVG | document. 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-2020-25787 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25787 [1] https://security-tracker.debian.org/tracker/CVE-2020-25788 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25788 [2] https://security-tracker.debian.org/tracker/CVE-2020-25789 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25789 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#968335: kernel crash: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120
Hello, my gigabyte brix system (Celeron J3160) worked rock solid 24/7 up to now (stretch install, upgrade to buster) as a small server with zabbix/mariadb, some kvm virtual machines and docker containers. Mass storage is at 2 usb3 2T disks. After updating the kernel to 4.19.0-10-amd64 (Debian 4.19.132-1) the system froze after around 2-3 days. I rebooted and tried again with the same result. I did a fallback to 4.19.0-9-amd64 (4.19.118-2+deb10u1) and the system again runs stable for a month now. Unfortunately no information about the reason for the freeze could be found in the logs. But around one day after boot I found a similar warning in the log like it is reported in this report. Here is the message of the first try: Aug 9 00:00:02 brix kernel: [273566.195095] [ cut here ] Aug 9 00:00:02 brix kernel: [273566.195107] percpu ref (css_release) <= 0 (-399677) after switching to atomic Aug 9 00:00:02 brix kernel: [273566.195127] WARNING: CPU: 1 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120 Aug 9 00:00:02 brix kernel: [273566.195128] Modules linked in: fuse btrfs zstd_compress zstd_decompress xxhash xor raid6_pq ufs qnx4 hfsplus hfs minix vfat msdos fat jfs xfs dm_mod vhost_net vhost tap tun devlink ipt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo nft_counter nft_chain_nat_ipv4 nf_nat_ipv4 xt_addrtype nft_compat nf_tables nfnetlink xt_conntrack nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c br_netfilter nls_utf8 overlay isofs loop bridge stp llc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic btusb intel_rapl intel_powerclamp coretemp arc4 kvm_intel snd_hda_intel i915 snd_hda_codec iwlmvm kvm hci_uart mac80211 snd_hda_core btqca evdev snd_hwdep btrtl irqbypass snd_pcm btbcm drm_kms_helper crct10dif_pclmul btintel crc32_pclmul iwlwifi rtsx_pci_ms ghash_clmulni_intel snd_timer intel_cstate Aug 9 00:00:02 brix kernel: [273566.195176] bluetooth memstick cfg80211 iTCO_wdt pcspkr iTCO_vendor_support drm snd soundcore i2c_algo_bit drbg ansi_cprng ecdh_generic pcc_cpufreq video rfkill pwm_lpss_platform pwm_lpss acpi_pad intel_int0002_vgpio sg button ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp nfsd libiscsi_tcp libiscsi scsi_transport_iscsi auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb uas usb_storage hid_generic usbhid sd_mod crc32c_intel rtsx_pci_sdmmc ahci libahci aesni_intel xhci_pci xhci_hcd libata i2c_i801 r8169 sdhci_pci aes_x86_64 crypto_simd cryptd glue_helper cqhci sdhci usbcore lpc_ich realtek scsi_mod libphy rtsx_pci mmc_core mfd_core usb_common thermal fan i2c_hid hid Aug 9 00:00:02 brix kernel: [273566.195225] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.19.0-10-amd64 #1 Debian 4.19.132-1 Aug 9 00:00:02 brix kernel: [273566.195227] Hardware name: GIGABYTE GB-BACE-3160/MZBSWMP-00, BIOS F6 06/13/2018 Aug 9 00:00:02 brix kernel: [273566.195230] RIP: 0010:percpu_ref_switch_to_atomic_rcu+0xf8/0x120 Aug 9 00:00:02 brix kernel: [273566.195232] Code: 78 ff ff ff 80 3d 2b 71 d2 00 00 75 8c 49 8b 54 24 d8 49 8b 74 24 e8 48 c7 c7 68 98 29 a4 c6 05 11 71 d2 00 01 e8 f2 ae ca ff <0f> 0b e9 68 ff ff ff f0 49 83 6c 24 d8 01 75 9c 49 8b 44 24 e8 48 Aug 9 00:00:02 brix kernel: [273566.195234] RSP: 0018:9b017bc83ee0 EFLAGS: 00010282 Aug 9 00:00:02 brix kernel: [273566.195236] RAX: RBX: 7ff9e6c3 RCX: Aug 9 00:00:02 brix kernel: [273566.195238] RDX: 0041 RSI: a49f7b21 RDI: 0246 Aug 9 00:00:02 brix kernel: [273566.195239] RBP: 42a50401ac08 R08: R09: 00021980 Aug 9 00:00:02 brix kernel: [273566.195241] R10: 00018e1d3146539c R11: a49f7b06 R12: 9b0176c3e838 Aug 9 00:00:02 brix kernel: [273566.195242] R13: a452dce0 R14: 7fff R15: 0202 Aug 9 00:00:02 brix kernel: [273566.195244] FS: () GS:9b017bc8() knlGS: Aug 9 00:00:02 brix kernel: [273566.195245] CS: 0010 DS: ES: CR0: 80050033 Aug 9 00:00:02 brix kernel: [273566.195247] CR2: 7fce0683e9a0 CR3: 00015a20a000 CR4: 001026e0 Aug 9 00:00:02 brix kernel: [273566.195248] Call Trace: Aug 9 00:00:02 brix kernel: [273566.195252] Aug 9 00:00:02 brix kernel: [273566.195259] rcu_process_callbacks+0x218/0x4b0 Aug 9 00:00:02 brix kernel: [273566.195264] ? rebalance_domains+0x274/0x2c0 Aug 9 00:00:02 brix kernel: [273566.195268] __do_softirq+0xde/0x2d8 Aug 9 00:00:02 brix kernel: [273566.195273] irq_exit+0xba/0xc0 Aug 9 00:00:02 brix kernel: [273566.195276] smp_apic_timer_interrupt+0x74/0x140 Aug 9 00:00:02 brix kernel: [273566.195279] apic_timer_interrupt+0xf/0x20 Aug 9 00:00:02 brix kernel: [273566.195281] Aug 9 00:00:02 brix kernel: [273566.195284] RIP: 0010:cpuidle_enter_state+0xb9/0x320 Aug 9
Bug#958631: marked as done (prads: Build-Depends on deprecated dh-systemd which is going away)
Your message dated Sun, 20 Sep 2020 15:15:06 +0200 with message-id <87tuvsbndx.fsf@turbotape.localdomain> and subject line Re: prads: Build-Depends on deprecated dh-systemd which is going away has caused the Debian Bug report #958631, regarding prads: Build-Depends on deprecated dh-systemd which is going away 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.) -- 958631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: prads Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: dh-systemd-removal Hi, your package prads declares a build dependency on dh-systemd. dh-systemd was merged into debhelper in version 9.20160709 [1] and since stretch, dh-systemd is an empty transitional package. For bullseye we intend to drop this empty transitional package. Once we drop dh-systemd, this bug report will become RC. Please update your package accordingly. The change should be as simple as replacing the build dependency on dh-systemd with a build dependency on debhelper (>= 9.20160709). Regards, Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670 --- End Message --- --- Begin Message --- Version: 0.3.3-2 This bug was fixed with the upload of 0.3.3-2. Thanks for reporting the bug -- Stig Sandbeck Mathisen Debian Developer--- End Message ---
Bug#957706: marked as done (prads: ftbfs with GCC-10)
Your message dated Sun, 20 Sep 2020 15:15:57 +0200 with message-id <87pn6gbnci.fsf@turbotape.localdomain> and subject line Re: prads: ftbfs with GCC-10 has caused the Debian Bug report #957706, regarding prads: ftbfs with GCC-10 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.) -- 957706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:prads Version: 0.3.3-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/prads_0.3.3-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] /bin/sh: 1: git: not found cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -O3 -DRELEASE='""' -DCONFDIR='"/etc/prads/"' -D__USE_GNU -Wdate-time -D_FORTIFY_SOURCE=2 -c -o output-plugins/log_ringbuffer.o output-plugins/log_ringbuffer.c /bin/sh: 1: git: not found /bin/sh: 1: git: not found output-plugins/log_ringbuffer.c: In function ‘log_ringbuffer_connection’: output-plugins/log_ringbuffer.c:94:38: warning: ‘%s’ directive output may be truncated writing up to 45 bytes into a region of size between 0 and 236 [-Wformat-truncation=] 94 | "%ld%09ju|%s|%s|%ld|%u|%s|%u|%s|%u|%ju|%ju|%ju|%ju|%u|%u|%d", | ^~ .. 104 | dst_s, | ~ output-plugins/log_ringbuffer.c:94:9: note: directive argument in the range [0, 65535] 94 | "%ld%09ju|%s|%s|%ld|%u|%s|%u|%s|%u|%ju|%ju|%ju|%ju|%u|%u|%d", | ^~~~ output-plugins/log_ringbuffer.c:94:9: note: directive argument in the range [0, 255] output-plugins/log_ringbuffer.c:94:9: note: directive argument in the range [0, 255] In file included from /usr/include/stdio.h:867, from output-plugins/../common.h:5, from output-plugins/../prads.h:27, from output-plugins/log_ringbuffer.c:7: /usr/include/x86_64-linux-gnu/bits/stdio2.h:67:10: note: ‘__builtin___snprintf_chk’ output between 37 and 434 bytes into a destination of size 256 67 | return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1, | ^~~~ 68 |__bos (__s), __fmt, __va_arg_pack ()); |~ /bin/sh: 1: git: not found /bin/sh: 1: git: not found cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -O3 -DRELEASE='""' -DCONFDIR='"/etc/prads/"' -D__USE_GNU -Wdate-time -D_FORTIFY_SOURCE=2 -c -o output-plugins/log_sguil.o output-plugins/log_sguil.c /bin/sh: 1: git: not found /bin/sh: 1: git: not found output-plugins/log_sguil.c: In function ‘init_output_sguil’: output-plugins/log_sguil.c:34:40: warning: format ‘%ld’ expects argument of type ‘long int’, but argument 5 has type ‘int’ [-Wformat=] 34 | snprintf(filename, PATH_MAX, "%s.%ld", log_prefix, check_time); | ~~^ ~~ || | |long intint | %d /bin/sh: 1: git: not found /bin/sh: 1: git: not found cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -O3 -DRELEASE='""'
Bug#970550: [Pkg-javascript-devel] Bug#970550: replacing browserify with webpack or rollup - need help
On Sun, Sep 20, 2020 at 15:51, Nilesh Patra wrote: I've seen these almost same buffer based errors before - with webpack specifically - and manually creating a symlink helped. I did the same in this case and the build passes with "Buffer: true" I've pushed the commit to the same webpack branch Could you take a look and let me know if it made the situation better/worse? diaspora still fails at rake assets:precompile step with same error. I suspected it has something to do with version of buffer we have. libs-browser has buffer 4.3.0 in package.json but we have node-buffer 5.x. But even with buffer 4.9.2 embedded, it fails the same way.
Bug#970550: [Pkg-javascript-devel] Bug#970550: replacing browserify with webpack or rollup - need help
Hi, On Sun, 20 Sep 2020 at 15:18, Pirate Praveen wrote: > Control: tags -1 help > > On Sun, Sep 20, 2020 at 14:44, Pirate Praveen > wrote: > > The warning now changes to, > > > > (!) Missing shims for Node.js built-ins > > Creating a browser bundle that depends on 'path', 'url' and 'os'. You > > might need to include > > https://www.npmjs.com/package/rollup-plugin-node-builtins > > (!) Unresolved dependencies > > > https://rollupjs.org/guide/en#warning-treating-module-as-external-dependency > > path (imported by ../../../usr/share/nodejs/browserslist/index.js, > > commonjs-external:path, > > ../../../usr/share/nodejs/postcss/lib/input.js, > > ../../../usr/share/nodejs/browserslist/node.js, > > ../../../usr/share/nodejs/postcss/lib/map-generator.js, > > ../../../usr/share/nodejs/postcss/lib/previous-map.js) > > rollup-plugin-node-builtins is not packaged in debian. So I decided to > try webpack (code pushed to a separate branch 'webpack'), > > This has resulted in a situation where we need to handle Buffer > correctyly. > > with Buffer: true in webpack.config.js, the build fails with error > > ERROR in /usr/share/nodejs/postcss/lib/map-generator.js > Module not found: Error: Can't resolve > './../../../../../<>/buffer' in > '/usr/share/nodejs/postcss/lib' > @ /usr/share/nodejs/postcss/lib/map-generator.js 1:0-89 > @ /usr/share/nodejs/postcss/lib/lazy-result.js > @ /usr/share/nodejs/postcss/lib/processor.js > @ /usr/share/nodejs/postcss/lib/postcss.js > @ ./lib/autoprefixer.js > I've seen these almost same buffer based errors before - with webpack specifically - and manually creating a symlink helped. I did the same in this case and the build passes with "Buffer: true" I've pushed the commit to the same webpack branch Could you take a look and let me know if it made the situation better/worse? Thanks and Regards, Nilesh
Processed: replacing browserify with webpack or rollup - need help
Processing control commands: > tags -1 help Bug #970550 [libjs-autoprefixer] diaspora installation fails with ExecJS::ProgramError: TypeError: Cannot read property 'list' of undefined Added tag(s) help. -- 970550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970550: replacing browserify with webpack or rollup - need help
Control: tags -1 help
On Sun, Sep 20, 2020 at 14:44, Pirate Praveen
wrote:
The warning now changes to,
(!) Missing shims for Node.js built-ins
Creating a browser bundle that depends on 'path', 'url' and 'os'. You
might need to include
https://www.npmjs.com/package/rollup-plugin-node-builtins
(!) Unresolved dependencies
https://rollupjs.org/guide/en#warning-treating-module-as-external-dependency
path (imported by ../../../usr/share/nodejs/browserslist/index.js,
commonjs-external:path,
../../../usr/share/nodejs/postcss/lib/input.js,
../../../usr/share/nodejs/browserslist/node.js,
../../../usr/share/nodejs/postcss/lib/map-generator.js,
../../../usr/share/nodejs/postcss/lib/previous-map.js)
rollup-plugin-node-builtins is not packaged in debian. So I decided to
try webpack (code pushed to a separate branch 'webpack'),
This has resulted in a situation where we need to handle Buffer
correctyly.
with Buffer: true in webpack.config.js, the build fails with error
ERROR in /usr/share/nodejs/postcss/lib/map-generator.js
Module not found: Error: Can't resolve
'./../../../../../<>/buffer' in
'/usr/share/nodejs/postcss/lib'
@ /usr/share/nodejs/postcss/lib/map-generator.js 1:0-89
@ /usr/share/nodejs/postcss/lib/lazy-result.js
@ /usr/share/nodejs/postcss/lib/processor.js
@ /usr/share/nodejs/postcss/lib/postcss.js
@ ./lib/autoprefixer.js
with Buffer: "mock" or Buffer: false, the build passes, but now rake
assets:precompile in diaspora fails with the following error
root@diaspora-buster-main:/usr/share/diaspora# sudo -u diaspora -E -H
bundle exec rake assets:precompile
rake aborted!
ExecJS::RuntimeError: /tmp/execjs20200920-897-qyh1s1js:87
process.stdout.write('' + string);
^
TypeError: Cannot read property 'write' of undefined
at print (/tmp/execjs20200920-897-qyh1s1js:87:20)
at /tmp/execjs20200920-897-qyh1s1js:101:5
at /tmp/execjs20200920-897-qyh1s1js:1:40
at Object. (/tmp/execjs20200920-897-qyh1s1js:1:58)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js
(internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
/usr/share/diaspora/app/assets/config/manifest.js:9
(execjs):87
/usr/share/rubygems-integration/all/gems/autoprefixer-rails-8.6.5/lib/autoprefixer-rails/processor.rb:153:in
`runtime'
/usr/share/rubygems-integration/all/gems/autoprefixer-rails-8.6.5/lib/autoprefixer-rails/processor.rb:37:in
`process'
/usr/share/rubygems-integration/all/gems/autoprefixer-rails-8.6.5/lib/autoprefixer-rails/sprockets.rb:20:in
`run'
/usr/share/rubygems-integration/all/gems/autoprefixer-rails-8.6.5/lib/autoprefixer-rails/sprockets.rb:14:in
`call'
/usr/share/rubygems-integration/all/gems/rake-13.0.1/exe/rake:27:in
`'
Tasks: TOP => assets:precompile
(See full trace by running task with --trace)
root@diaspora-buster-main:/usr/share/diaspora#
libraryTarget="window", libraryTrget="umd" was also tried without
success.
Packaging rollup-plugin-node-builtins may be one option. Any ideas?
Bug#970577: marked as done (dpkg and zsh FTBFS: KEY_EVENT undeclared)
Your message dated Sun, 20 Sep 2020 09:34:55 +
with message-id
and subject line Bug#970577: fixed in ncurses 6.2+20200918-1
has caused the Debian Bug report #970577,
regarding dpkg and zsh FTBFS: KEY_EVENT undeclared
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.)
--
970577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dpkg
Version: 1.20.5
Severity: serious
Tags: ftbfs
dpkg FTBFS as of today:
| g++ -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\"
-DADMINDIR=\"/var/lib/dpkg\" -DLIBDIR=\"/usr/lib/dpkg\"
-DLOCALLIBDIR=\"/usr/local/lib/dpkg\" -idirafter ../../lib/compat -iquote .
-I.. -I../../lib -Wdate-time -D_FORTIFY_SOURCE=2 -fno-rtti -fno-exceptions
-Wall -Wextra -Wcast-align -Wduplicated-branches -Wduplicated-cond -Wformat
-Wformat-security -Wformat=2 -Winit-self -Wlogical-not-parentheses -Wlogical-op
-Wmissing-declarations -Wmissing-format-attribute
-Wno-missing-field-initializers -Wno-nonnull-compare -Wno-unused-parameter
-Wnull-dereference -Wpointer-arith -Wredundant-decls -Wregister -Wrestrict
-Wshadow -Wshift-negative-value -Wsizeof-array-argument -Wswitch-bool -Wvla
-Wwrite-strings -Wc++11-compat -Wcast-qual -Wold-style-cast
-Wzero-as-null-pointer-constant -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall -Wextra
-Wno-missing-field-initializers -Wno-nonnull-compare -Wno-unused-parameter -MT
curkeys.o -MD -MP -MF .deps/curkeys.Tpo -c -o curkeys.o ../../dselect/curkeys.cc
| mv -f .deps/pkgdisplay.Tpo .deps/pkgdisplay.Po
| mv -f .deps/pkginfo.Tpo .deps/pkginfo.Po
| mv -f .deps/pkgcmds.Tpo .deps/pkgcmds.Po
| In file included from ../../dselect/curkeys.cc:30:
| ./curkeys.h:168:5: error: ‘KEY_EVENT’ was not declared in this scope; did you
mean ‘KEY_OPEN’?
| 168 | { KEY_EVENT, "Event" },
| | ^
| | KEY_OPEN
| make[4]: *** [Makefile:617: curkeys.o] Error 1
| make[4]: *** Waiting for unfinished jobs
| mv -f .deps/pkgdepcon.Tpo .deps/pkgdepcon.Po
| mv -f .deps/pkgsublist.Tpo .deps/pkgsublist.Po
| mv -f .deps/pkgtop.Tpo .deps/pkgtop.Po
| mv -f .deps/pkglist.Tpo .deps/pkglist.Po
| make[4]: Leaving directory '/<>/build-tree/dselect'
| make[3]: *** [Makefile:650: all-recursive] Error 1
| make[3]: Leaving directory '/<>/build-tree/dselect'
| make[2]: *** [Makefile:743: all-recursive] Error 1
| make[2]: Leaving directory '/<>/build-tree'
| make[1]: *** [Makefile:609: all] Error 2
| make[1]: Leaving directory '/<>/build-tree'
| make: *** [debian/rules:74: build] Error 2
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
I suppose this is connected to a ncurses upload.
Helmut
--- End Message ---
--- Begin Message ---
Source: ncurses
Source-Version: 6.2+20200918-1
Done: Sven Joachim
We believe that the bug you reported is fixed in the latest version of
ncurses, 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 970...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sven Joachim (supplier of updated ncurses 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: Sun, 20 Sep 2020 11:16:40 +0200
Source: ncurses
Architecture: source
Version: 6.2+20200918-1
Distribution: unstable
Urgency: medium
Maintainer: Craig Small
Changed-By: Sven Joachim
Closes: 970577
Changes:
ncurses (6.2+20200918-1) unstable; urgency=medium
.
* New upstream patchlevel.
- Corrected condition for appending curses.events to the generated
curses.h (report by Sven Joachim, Closes: #970577).
* Version the Provides of the transitional -dev packages
by libncurses-dev.
Checksums-Sha1:
17211c548918e37c910388dfb852fab7a408fb3b 4106 ncurses_6.2+20200918-1.dsc
676ddf1e4050e5144fc1f73464bdab302076 3527965
ncurses_6.2+20200918.orig.tar.gz
31f84756aa971265802d667fbda745911e7d53d1 265
ncurses_6.2+20200918.orig.tar.gz.asc
0837356a0ad83cdd733f8e4e4561e97dc3b4888a 51396
ncurses_6.2+20200918-1.debian.tar.xz
66225a4e921191e72608866a6fbb0cf8616bd07f 5193
ncurses_6.2+20200918-1_source.buildinfo
Bug#970134: marked as done (libweston-9-dev: missing (unversioned) Breaks+Replaces: libweston-8-dev)
Your message dated Sun, 20 Sep 2020 09:23:14 + with message-id and subject line Bug#970134: fixed in weston 9.0.0-2 has caused the Debian Bug report #970134, regarding libweston-9-dev: missing (unversioned) Breaks+Replaces: libweston-8-dev 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.) -- 970134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libweston-9-dev Version: 9.0.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libweston-9-dev_9.0.0-1_amd64.deb ... Unpacking libweston-9-dev (9.0.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libweston-9-dev_9.0.0-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/weston/libexec_weston.so', which is also in package libweston-8-dev 8.0.0-1 Errors were encountered while processing: /var/cache/apt/archives/libweston-9-dev_9.0.0-1_amd64.deb Since libweston-8-dev is gone, the Breaks+Replaces can be unversioned. cheers, Andreas libweston-8-dev=8.0.0-1_libweston-9-dev=9.0.0-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: weston Source-Version: 9.0.0-2 Done: =?utf-8?b?SMOpY3RvciBPcsOzbiBNYXJ0w61uZXo=?= We believe that the bug you reported is fixed in the latest version of weston, 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 970...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Héctor Orón Martínez (supplier of updated weston 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: Sun, 20 Sep 2020 10:36:42 +0200 Source: weston Architecture: source Version: 9.0.0-2 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Héctor Orón Martínez Closes: 970134 Changes: weston (9.0.0-2) unstable; urgency=medium . * debian/libweston-9-dev.install: drop libexec_weston (Closes: #970134) Checksums-Sha1: 901e9f446adcbb55e688a48e8c93f4165bff0147 2843 weston_9.0.0-2.dsc 5f24507edd14fa7568fe3f799e10b27451237e05 22111 weston_9.0.0-2.diff.gz c41fc7f2a0c42505eb168f535dbff9b31252704a 5957 weston_9.0.0-2_source.buildinfo Checksums-Sha256: a1e46ac2e66f0a61904b2970949a837906bb0cab75f726a7189f96844f4d692e 2843 weston_9.0.0-2.dsc 219e19ea905d44bcaab2ddf6f8e002685f10f77e445f17f399a0cb3d44e3a77b 22111 weston_9.0.0-2.diff.gz 5b330f23c6097faa6a9fbded3db2b8842f7a98464748831ee73a0bc29ede55e1 5957 weston_9.0.0-2_source.buildinfo Files: b8abf4e4692037cb5b7069ecd57fd71b 2843 x11 optional weston_9.0.0-2.dsc 9334bf0fd5653b5170650734b6a42b8c 22111 x11 optional weston_9.0.0-2.diff.gz 88ac91fa1a7894e6b918995285e6efae 5957 x11 optional weston_9.0.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE6Q8IiVReeMgqnedOryKDqnbirHsFAl9nHCMACgkQryKDqnbi rHuRKg/+NbImbUUx+vJMArX4xoqnlJs0SB17/QXj1Q9B1WVR6eWA32OBBljEahIi Ua66WgfzxfQuic5eE58Y7Z8JK7G3eYjnav/u3TqADE2m204CNtp6PPDm/pRcCT2q dIR0vmawQYaaqshOFyyxZnyvIHx6N3/vj+/OsehBLWe0eN0++IWtPARFvCbBwEWH CpVSHK+VC1weKwHgynpM8TV3vcxlwDWZteHoQNGBHpWa58B7myc9ZLJqrKCBO0L6 f+hLoWHjlfBHzs8XtNkDJffSQVSqw4b+eUW5QQeNh4gN9/wzboNEsm36tHmau5Y2 SVZRUIbtjqCytVSGQyaexWLcgf3inBVIwhyIyX+tW2cdZIcdoFDYe/YsCYVIdfwM d5AKfAYk2MeS3QyLbJKwDE+AIbydTWRgZ/1OzRrLwz4GF5qZzXVQm1rFNDLxEuTB IgcOt+ByYQX5Bdxtf6RTedk8WfSMpJXdmQ5j/PBjlgjpgPKD8YUObYdSA1QqkqHO eT89s/9Pu1d1pHBLBuvS0lfytopT/CiYYHygVOdtrLq4aSlp8A+IMcEjW5l1E2+S 7921eWlRD77uchEm3ietT3yYsKkh334HHBXJox+VEY+SN/uHqkfN25Rh8OSNF0TH LkJSEwy1JIHgOOAYZu6rYudvL4mHBn4rQ1BJ+pzZHi6Ja1JTi+8= =GvmY -END PGP SIGNATURE End Message ---
Processed: Re: this is a bug in libjs-autoprefixer
Processing control commands: > reassign -1 libjs-autoprefixer Bug #970550 [ruby-autoprefixer-rails] diaspora installation fails with ExecJS::ProgramError: TypeError: Cannot read property 'list' of undefined Bug reassigned from package 'ruby-autoprefixer-rails' to 'libjs-autoprefixer'. No longer marked as found in versions ruby-autoprefixer-rails/8.6.5+dfsg-3. Ignoring request to alter fixed versions of bug #970550 to the same values previously set > found -1 8.6.5-2 Bug #970550 [libjs-autoprefixer] diaspora installation fails with ExecJS::ProgramError: TypeError: Cannot read property 'list' of undefined Marked as found in versions node-autoprefixer/8.6.5-2. -- 970550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970550: this is a bug in libjs-autoprefixer
Control: reassign -1 libjs-autoprefixer
Control: found -1 8.6.5-2
On Sun, Sep 20, 2020 at 14:28, Pirate Praveen
wrote:
ruby-autoprefixer-rails links to autoprefixer.js provided by
libjs-autoprefixer.
ls -l
/usr/share/rubygems-integration/all/gems/autoprefixer-rails-8.6.5/vendor/autoprefixer.js
lrwxrwxrwx 1 root root 54 Mar 1 2019
/usr/share/rubygems-integration/all/gems/autoprefixer-rails-8.6.5/vendor/autoprefixer.js
-> ../../../../../javascript/autoprefixer/autoprefixer.js
Build log has many lines like,
(!) Unresolved dependencies
https://rollupjs.org/guide/en#warning-treating-module-as-external-dependency
browserslist (imported by build/lib/autoprefixer.js,
commonjs-external:browserslist, build/lib/browsers.js,
build/lib/info.js)
https://buildd.debian.org/status/fetch.php?pkg=node-autoprefixer=all=9.8.0-1=1590223648=0
which means the umd bundle did not include those dependencies.
Upstream uses browserify to create the browser bundle, but it is not
packaged in debian. Hence we were forced to create our own rollup
configuration file.
One way out would be to include the dependencies in the bundle by
passing custom resolve path in rollup.config.js
After adding
let fileDest = 'autoprefixer.js'
const plugins = [
+ resolve({
+customResolveOptions: {
+ moduleDirectory: ['/usr/share/nodejs']
+}
+ }),
common()
]
module.exports = {
The warning now changes to,
(!) Missing shims for Node.js built-ins
Creating a browser bundle that depends on 'path', 'url' and 'os'. You
might need to include
https://www.npmjs.com/package/rollup-plugin-node-builtins
(!) Unresolved dependencies
https://rollupjs.org/guide/en#warning-treating-module-as-external-dependency
path (imported by ../../../usr/share/nodejs/browserslist/index.js,
commonjs-external:path, ../../../usr/share/nodejs/postcss/lib/input.js,
../../../usr/share/nodejs/browserslist/node.js,
../../../usr/share/nodejs/postcss/lib/map-generator.js,
../../../usr/share/nodejs/postcss/lib/previous-map.js)
Bug#970550: this is a bug in libjs-autoprefixer
reassign -1 libjs-autoprefixer found -1 8.6.5-2 On Fri, Sep 18, 2020 at 19:57, Pirate Praveen wrote: Control: reassign -1 ruby-autoprefixer-rails Control: found -1 8.6.5+dfsg-3 After replacing sass-rails, execjs and autoprefixer-rails (taking clues from the error log) with versions from rubygems.org, I found autoprefixer-rails version installed from rubygems.org fixes this issue, so the bug is in ruby-autoprefixer-rails. ruby-autoprefixer-rails links to autoprefixer.js provided by libjs-autoprefixer. ls -l /usr/share/rubygems-integration/all/gems/autoprefixer-rails-8.6.5/vendor/autoprefixer.js lrwxrwxrwx 1 root root 54 Mar 1 2019 /usr/share/rubygems-integration/all/gems/autoprefixer-rails-8.6.5/vendor/autoprefixer.js -> ../../../../../javascript/autoprefixer/autoprefixer.js
Processed: bug 968157 is forwarded to https://github.com/well-typed/cborg/issues/248
Processing commands for cont...@bugs.debian.org: > forwarded 968157 https://github.com/well-typed/cborg/issues/248 Bug #968157 [src:haskell-cborg] src:haskell-cborg: testsuite fails due to bus errors on armhf Set Bug forwarded-to-address to 'https://github.com/well-typed/cborg/issues/248'. > thanks Stopping processing here. Please contact me if you need assistance. -- 968157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968157 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: popplerkit.framework: diff for NMU version 0.0.20051227svn-8.1
Processing control commands: > tags 968719 + pending Bug #968719 [popplerkit.framework] popplerkit.framework FTBFS with poppler 0.85 Added tag(s) pending. -- 968719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968719: popplerkit.framework: diff for NMU version 0.0.20051227svn-8.1
Control: tags 968719 + pending
Dear maintainer,
I've prepared an NMU for popplerkit.framework (versioned as
0.0.20051227svn-8.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Cheers
--
Sebastian Ramacher
diff -Nru popplerkit.framework-0.0.20051227svn/debian/changelog popplerkit.framework-0.0.20051227svn/debian/changelog
--- popplerkit.framework-0.0.20051227svn/debian/changelog 2018-12-12 16:40:57.0 +0100
+++ popplerkit.framework-0.0.20051227svn/debian/changelog 2020-09-20 10:30:28.0 +0200
@@ -1,3 +1,12 @@
+popplerkit.framework (0.0.20051227svn-8.1) unstable; urgency=medium
+
+ * Non-maintainer upload
+
+ [ Peter Michael Green ]
+ * Fix build with poppler 0.85 (Closes: #968719)
+
+ -- Sebastian Ramacher Sun, 20 Sep 2020 10:30:28 +0200
+
popplerkit.framework (0.0.20051227svn-8) unstable; urgency=medium
[ Sebastien Bacher ]
diff -Nru popplerkit.framework-0.0.20051227svn/debian/patches/build_poppler85.patch popplerkit.framework-0.0.20051227svn/debian/patches/build_poppler85.patch
--- popplerkit.framework-0.0.20051227svn/debian/patches/build_poppler85.patch 1970-01-01 01:00:00.0 +0100
+++ popplerkit.framework-0.0.20051227svn/debian/patches/build_poppler85.patch 2020-09-20 10:29:40.0 +0200
@@ -0,0 +1,45 @@
+Description: Fix build with poppler 0.85
+Author: Peter Michael Green
+
+Index: popplerkit.framework-0.0.20051227svn/bindings/GNUmakefile
+===
+--- popplerkit.framework-0.0.20051227svn.orig/bindings/GNUmakefile
popplerkit.framework-0.0.20051227svn/bindings/GNUmakefile
+@@ -57,4 +57,8 @@ ifeq ($(POPPLER_0_20), YES)
+bindings_CCFLAGS += -DPOPPLER_0_20
+ endif
+
++ifeq ($(POPPLER_0_85), YES)
++ bindings_CCFLAGS += -DPOPPLER_0_20 -DPOPPLER_0_85
++endif
++
+ include $(GNUSTEP_MAKEFILES)/subproject.make
+Index: popplerkit.framework-0.0.20051227svn/bindings/poppler.cc
+===
+--- popplerkit.framework-0.0.20051227svn.orig/bindings/poppler.cc
popplerkit.framework-0.0.20051227svn/bindings/poppler.cc
+@@ -125,6 +125,8 @@ int poppler_init(const unsigned char* fc
+
+ #ifdef POPPLER_0_6
+ globalParams = new GlobalParams();
++#elif POPPLER_0_85
++ globalParams = std::make_unique(nullptr);
+ #else
+ globalParams = new GlobalParams(NULL);
+ #endif
+Index: popplerkit.framework-0.0.20051227svn/config.sh
+===
+--- popplerkit.framework-0.0.20051227svn.orig/config.sh
popplerkit.framework-0.0.20051227svn/config.sh
+@@ -69,6 +69,11 @@ if [ $? -eq 0 ]; then
+ POPPLER_VERSION="POPPLER_0_20"
+ fi
+
++${PKG_CONFIG} --atleast-version=0.85.0 poppler
++if [ $? -eq 0 ]; then
++ POPPLER_VERSION="POPPLER_0_85"
++fi
++
+ echo $POPPLER_VERSION
+
+ # include freetype, just to be sure
diff -Nru popplerkit.framework-0.0.20051227svn/debian/patches/series popplerkit.framework-0.0.20051227svn/debian/patches/series
--- popplerkit.framework-0.0.20051227svn/debian/patches/series 2018-12-12 16:40:57.0 +0100
+++ popplerkit.framework-0.0.20051227svn/debian/patches/series 2020-09-20 10:29:40.0 +0200
@@ -3,3 +3,4 @@
C++-compilation.patch
poppler020.patch
build_poppler71.patch
+build_poppler85.patch
signature.asc
Description: PGP signature
Processed: tagging 968719
Processing commands for cont...@bugs.debian.org: > tags 968719 + ftbfs Bug #968719 [popplerkit.framework] popplerkit.framework FTBFS with poppler 0.85 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 968719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Fixed upstream
Processing commands for cont...@bugs.debian.org: > tag 966850 +fixed-upstream Bug #966850 [src:iverilog] iverilog: FTBFS: parse.cc:299:10: fatal error: parse.hh: No such file or directory Added tag(s) fixed-upstream. > End of message, stopping processing here. Please contact me if you need assistance. -- 966850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
