Bug#998838: h5py: FTBFS on armhf
Control: tags -1 + patch Patch at: https://launchpadlibrarian.net/567918549/h5py_3.3.0-4_3.3.0-4ubuntu1.diff.gz
Processed: Re: h5py: FTBFS on armhf
Processing control commands: > tags -1 + patch Bug #998838 [src:h5py] h5py: FTBFS on armhf Added tag(s) patch. -- 998838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997418: marked as done (lammps: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.')
Your message dated Tue, 09 Nov 2021 05:53:03 +
with message-id
and subject line Bug#997418: fixed in lammps 20210122~gita77bb+ds1-3
has caused the Debian Bug report #997418,
regarding lammps: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
997418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lammps
Version: 20210122~gita77bb+ds1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering directory '/<>/doc/latex'
> latexmk -pdf -dvi- -ps- 'LAMMPS.tex'
> Rc files read:
> /etc/LatexMk
> latexmkrc
> Latexmk: This is Latexmk, John Collins, 21 September 2021, version: 4.75.
> Rule 'pdflatex': File changes, etc:
>Changed files, or newly in use since previous run(s):
> 'LAMMPS.tex'
>
> Run number 1 of rule 'pdflatex'
>
>
> Running 'pdflatex -recorder "LAMMPS.tex"'
>
> Latexmk: applying rule 'pdflatex'...
> This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2022/dev/Debian)
> (preloaded format=pdflatex)
> restricted \write18 enabled.
> entering extended mode
> (./LAMMPS.tex
> LaTeX2e <2021-06-01> patch level 1
> L3 programming layer <2021-08-27> (./sphinxmanual.cls
> Document Class: sphinxmanual 2019/12/01 v2.3.0 Document class (Sphinx manual)
> (/usr/share/texlive/texmf-dist/tex/latex/base/report.cls
> Document Class: report 2021/02/12 v1.4n Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)))
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/cmap/cmap.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty<>)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
> For additional information on amsmath, use the `?' option.
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def
> (/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def))
> (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf))
>
> ! LaTeX Error: File `tgtermes.sty' not found.
>
> Type X to quit or to proceed,
> or enter new name. (Default extension: sty)
>
> Enter file name:
> ! Emergency stop.
>
>
> l.37 \usepackage
> {tgheros}^^M
> ! ==> Fatal error occurred, no output PDF file produced!
> Transcript written on LAMMPS.log.
> Latexmk: Missing input file 'tgtermes.sty' (or dependence on it) from
> following:
> '! LaTeX Error: File `tgtermes.sty' not found.'
> Collected error summary (may duplicate other messages):
> pdflatex: Command for 'pdflatex' gave return code 1
> Refer to 'LAMMPS.log' for details
> Latexmk: Use the -f option to force complete processing,
> unless error was exceeding maximum runs, or warnings treated as errors.
> Latexmk: Examining 'LAMMPS.log'
> === TeX engine is 'pdfTeX'
> Latexmk: Errors, so I did not complete making targets
> make[3]: *** [Makefile:29: LAMMPS.pdf] Error 12
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/lammps_20210122~gita77bb+ds1-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: lammps
Source-Version: 20210122~gita77bb+ds1-3
Done: Anton Gladky
We believe that the bug you reported is fixed in the latest version of
lammps, 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
Bug#997436: marked as done (sfepy: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.')
Your message dated Tue, 09 Nov 2021 05:53:09 +
with message-id
and subject line Bug#997436: fixed in sfepy 2020.4-2
has caused the Debian Bug report #997436,
regarding sfepy: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
997436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sfepy
Version: 2020.4-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering directory '/<>/doc/_build/latex'
> latexmk -pdf -dvi- -ps- 'SfePy.tex'
> Rc files read:
> /etc/LatexMk
> latexmkrc
> Latexmk: This is Latexmk, John Collins, 21 September 2021, version: 4.75.
> Rule 'pdflatex': File changes, etc:
>Changed files, or newly in use since previous run(s):
> 'SfePy.tex'
>
> Run number 1 of rule 'pdflatex'
>
>
> Running 'pdflatex -recorder "SfePy.tex"'
>
> Latexmk: applying rule 'pdflatex'...
> This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2022/dev/Debian)
> (preloaded format=pdflatex)
> restricted \write18 enabled.
> entering extended mode
> (./SfePy.tex
> LaTeX2e <2021-06-01> patch level 1
> L3 programming layer <2021-08-27> (./sphinxmanual.cls
> Document Class: sphinxmanual 2019/12/01 v2.3.0 Document class (Sphinx manual)
> (/usr/share/texlive/texmf-dist/tex/latex/base/report.cls
> Document Class: report 2021/02/12 v1.4n Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)))
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/cmap/cmap.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty<>)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
> For additional information on amsmath, use the `?' option.
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
> (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def
> (/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def))
> (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf))
>
> ! LaTeX Error: File `tgtermes.sty' not found.
>
> Type X to quit or to proceed,
> or enter new name. (Default extension: sty)
>
> Enter file name:
> ! Emergency stop.
>
>
> l.37 \usepackage
> {tgheros}^^M
> ! ==> Fatal error occurred, no output PDF file produced!
> Transcript written on SfePy.log.
> Latexmk: Missing input file 'tgtermes.sty' (or dependence on it) from
> following:
> '! LaTeX Error: File `tgtermes.sty' not found.'
> Collected error summary (may duplicate other messages):
> pdflatex: Command for 'pdflatex' gave return code 1
> Refer to 'SfePy.log' for details
> Latexmk: Use the -f option to force complete processing,
> unless error was exceeding maximum runs, or warnings treated as errors.
> Latexmk: Examining 'SfePy.log'
> === TeX engine is 'pdfTeX'
> Latexmk: Errors, so I did not complete making targets
> make[3]: *** [Makefile:29: SfePy.pdf] Error 12
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/sfepy_2020.4-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: sfepy
Source-Version: 2020.4-2
Done: Anton Gladky
We believe that the bug you reported is fixed in the latest version of
sfepy, 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
Bug#997193: marked as done (hstr: FTBFS: hstr.c:743:44: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Tue, 09 Nov 2021 01:38:11 + with message-id and subject line Bug#997193: fixed in hstr 2.3+ds-2 has caused the Debian Bug report #997193, regarding hstr: FTBFS: hstr.c:743:44: error: format not a string literal and no format arguments [-Werror=format-security] 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.) -- 997193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997193 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hstr Version: 2.3+ds-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -DPACKAGE_NAME=\"hstr\" -DPACKAGE_TARNAME=\"hstr\" > -DPACKAGE_VERSION=\"2.3.0\" -DPACKAGE_STRING=\"hstr\ 2.3.0\" > -DPACKAGE_BUGREPORT=\"martin.dvo...@mindforger.com\" -DPACKAGE_URL=\"\" > -DPACKAGE=\"hstr\" -DVERSION=\"2.3.0\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 > -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 > -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 > -DHAVE_LIBNCURSESW=1 -DHAVE_LIBM=1 -DHAVE_LIBREADLINE=1 -DHAVE__BOOL=1 > -DHAVE_MALLOC=1 -DHAVE_MEMSET=1 -DHAVE_STRDUP=1 -DHAVE_STRSTR=1 -I. > -Wdate-time -D_FORTIFY_SOURCE=2 --pedantic -Wall -std=c99 -O2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o main.o main.c > hstr.c: In function ‘print_cmd_added_favorite_label’: > hstr.c:743:44: error: format not a string literal and no format arguments > [-Werror=format-security] > 743 | mvprintw(hstr->promptYNotification, 0, screenLine); > |^~ > cc1: some warnings being treated as errors > make[2]: *** [Makefile:417: hstr.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/hstr_2.3+ds-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: hstr Source-Version: 2.3+ds-2 Done: Daniel Echeverri We believe that the bug you reported is fixed in the latest version of hstr, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Echeverri (supplier of updated hstr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Nov 2021 18:24:35 -0500 Source: hstr Architecture: source Version: 2.3+ds-2 Distribution: unstable Urgency: medium Maintainer: Daniel Echeverri Changed-By: Daniel Echeverri Closes: 997193 Changes: hstr (2.3+ds-2) unstable; urgency=medium . * debian/patches + Add 04_fix_ftbfs_string_format_error.diff patch. + Fix string format error. (Closes: #997193) * debian/control + Bump Standards-Version to 4.6.0.1 Checksums-Sha1: 9498314b396ff24c70e6a1efef55dcd701e300b8 1866 hstr_2.3+ds-2.dsc 335156bb6e2fb42da0f025d12cb1ddeb9d0e21ab 3356 hstr_2.3+ds-2.debian.tar.xz 8355d254a99f5c8e03134f2d4531f2a9f3ea6700 6287 hstr_2.3+ds-2_amd64.buildinfo Checksums-Sha256: bb6a5c2451842439be9840f59359ff9c33a67c8d09e9cb88edcb5fa62ec9f670 1866 hstr_2.3+ds-2.dsc 8f5a25460fdc23b0669565b657647d027ab87c0f92ed819e09b7bb3673fcd9ed 3356 hstr_2.3+ds-2.debian.tar.xz 80d511f55dff56e53b62c0770d0d53ef52a679449f0db4b783d738e676335431 6287 hstr_2.3+ds-2_amd64.buildinfo Files: 29b6b530c22dd5df3fdba8864748535a 1866 utils optional hstr_2.3+ds-2.dsc 258e5bb12d396d5158a9c71674eef94d 3356 utils optional hstr_2.3+ds-2.debian.tar.xz 46384644ae08e59c7f3227c01fdb1dfe 6287 utils optional hstr_2.3+ds-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEE0NCFsWnDv9lASFj6IfwpUEtSMNsFAmGJzPMTHGVwc2lsb25A
Bug#998746: marked as done (/usr/lib/libreoffice/program/libmergedlo.so: undefined symbol: _ZN8MsLangId17getSystemLanguageEv)
Your message dated Tue, 09 Nov 2021 00:20:58 + with message-id and subject line Bug#998746: fixed in libreoffice 1:7.3.0~alpha1-4 has caused the Debian Bug report #998746, regarding /usr/lib/libreoffice/program/libmergedlo.so: undefined symbol: _ZN8MsLangId17getSystemLanguageEv 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.) -- 998746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998746 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libreoffice Version: 1:7.3.0~alpha1-3 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I wanted to file another bug (wishlist/normal), but then reportbug mentioned/recommended to try the latest version (from experimental), so I did a "aptitude full-upgrade ~ilibreoffice -t experimental" and that succeeded. But when trying to launch LO Writer from the menu, I saw it start up and then it disappeared again, without showing its window. To make sure there weren't any 'leftover' processes, I rebooted my machine. Trying to launch LO Writer failed again in the same way. So I tried to launch it from a Konsole window: $ libreoffice Warning: failed to launch javaldx - java may not function correctly /usr/lib/libreoffice/program/soffice.bin: symbol lookup error: /usr/lib/libreoffice/program/libmergedlo.so: undefined symbol: _ZN8MsLangId17getSystemLanguageEv I do have java installed on my machine, but not LO's java package(s), but I think that's irrelevent. This issue did not occur with LO version 1:7.2.2-1 Cheers, Diederik - -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: arm64 Kernel: Linux 5.14.0-4-amd64 (SMP w/16 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libreoffice depends on: ii libreoffice-base1:7.3.0~alpha1-3 ii libreoffice-calc1:7.3.0~alpha1-3 ii libreoffice-core1:7.3.0~alpha1-3 ii libreoffice-draw1:7.3.0~alpha1-3 ii libreoffice-impress 1:7.3.0~alpha1-3 ii libreoffice-math1:7.3.0~alpha1-3 ii libreoffice-report-builder-bin 1:7.3.0~alpha1-3 ii libreoffice-writer 1:7.3.0~alpha1-3 ii python3-uno 1:7.3.0~alpha1-3 Versions of packages libreoffice recommends: ii fonts-crosextra-caladea 20130214-2.1 ii fonts-crosextra-carlito 20130920-1.1 ii fonts-dejavu2.37-2 ii fonts-liberation1:1.07.4-11 ii fonts-liberation2 2.1.5-1 ii fonts-linuxlibertine5.3.0-6 ii fonts-noto-core 20201225-1 pn fonts-noto-extra pn fonts-noto-mono ii fonts-noto-ui-core 20201225-1 ii fonts-sil-gentium-basic 1.102-1.1 pn libreoffice-java-common pn libreoffice-nlpsolver pn libreoffice-report-builder pn libreoffice-script-provider-bsh pn libreoffice-script-provider-js ii libreoffice-script-provider-python 1:7.3.0~alpha1-3 pn libreoffice-sdbc-mysql ii libreoffice-sdbc-postgresql 1:7.3.0~alpha1-3 pn libreoffice-wiki-publisher Versions of packages libreoffice suggests: pn cups-bsd ii default-jre [java8-runtime]2:1.11-72 ii firefox94.0-1 ii firefox-esr91.3.0esr-1 ii ghostscript9.54.0~dfsg-5 ii gnupg 2.2.27-2 pn gpa ii gstreamer1.0-libav 1.18.5-1 ii gstreamer1.0-plugins-bad 1.18.5-1+b2 ii gstreamer1.0-plugins-base 1.18.5-1 ii gstreamer1.0-plugins-good 1.18.5-1+b1 ii gstreamer1.0-plugins-ugly 1.18.5-1 ii hunspell-en-us [hunspell-dictionary] 1:2020.12.07-1 ii hunspell-nl [hunspell-dictionary] 2:2.20.19-2 pn hyphen-hyphenation-patterns ii imagemagick
Bug#998435: marked as done (libreoffice-java-common: missing Breaks+Replaces: libreoffice-smoketest-data (<< 1:7.3.0~))
Your message dated Tue, 09 Nov 2021 00:20:57 + with message-id and subject line Bug#998435: fixed in libreoffice 1:7.3.0~alpha1-4 has caused the Debian Bug report #998435, regarding libreoffice-java-common: missing Breaks+Replaces: libreoffice-smoketest-data (<< 1:7.3.0~) 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.) -- 998435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libreoffice-java-common Version: 1:7.3.0~alpha1-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. This error may also be triggered by having a predecessor package from 'sid 'installed while installing the package from 'experimental'. 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 .../libreoffice-java-common_1%3a7.3.0~alpha1-3_all.deb ... Unpacking libreoffice-java-common (1:7.3.0~alpha1-3) ... dpkg: error processing archive /var/cache/apt/archives/libreoffice-java-common_1%3a7.3.0~alpha1-3_all.deb (--unpack): trying to overwrite '/usr/share/libreoffice/program/classes/smoketest.jar', which is also in package libreoffice-smoketest-data 1:7.2.2-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libreoffice-java-common_1%3a7.3.0~alpha1-3_all.deb cheers, Andreas libreoffice-smoketest-data=1:7.2.2-1_libreoffice-java-common=1:7.3.0~alpha1-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: libreoffice Source-Version: 1:7.3.0~alpha1-4 Done: Rene Engelhard We believe that the bug you reported is fixed in the latest version of libreoffice, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rene Engelhard (supplier of updated libreoffice package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Nov 2021 23:06:01 +0100 Source: libreoffice Architecture: source Version: 1:7.3.0~alpha1-4 Distribution: experimental Urgency: medium Maintainer: Debian LibreOffice Maintainers Changed-By: Rene Engelhard Closes: 998435 998746 Changes: libreoffice (1:7.3.0~alpha1-4) experimental; urgency=medium . * debian/rules: - disable LTO on mips64el - also uncomment smoketest.jar move to -smoketest-data again (although effectively unused..) (closes: #998435) - don't check for AUTOPKGTEST_TMP, it seems to not been set in build stage already (add hack to grep for autopkgtest in pwd instead). Don't run the checks in build* if in autopkgtest builds (as they are run later anyway) - Separate RUN_MAKE_CHECK into BUILD_TESTS/RUN_MAKE_CHECK - use -g1 on autopkgtest builds (saving disc space/time on all those copies...) - don't specify --without-cppunit in CONFIGURE_FLAGS_INDEP per default (only explicit build-indep builds) * debian/tests/*, debian/tests/patches/*: - move cppunit part out of smoketest-standalone.diff into cppunit-standalone.diff * debian/tests/control.in: - make uno superficial, it only runs the bridgetest; remove it from cppunit-subsequentcheck - move smoketest after the cppunit tests and run it only on the architectures those, too (also make it build-needed); add missing libreoffice-smoketest-data dependency * debian/tests/*: - only create config_host.mk when not existing (e.g. architectures having no tests with build-needed and thus there is no build which created it) - don't try to run test-extension/odk-build-examples* as root, skip them if doing so * debian/tests/control.in,
Bug#997125: marked as done (lam: FTBFS: ar: close.o: file format not recognized)
Your message dated Tue, 09 Nov 2021 00:19:44 + with message-id and subject line Bug#997125: fixed in lam 7.1.4-7 has caused the Debian Bug report #997125, regarding lam: FTBFS: ar: close.o: file format not recognized 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.) -- 997125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lam Version: 7.1.4-6.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > compiling ROMIO in directory mpi-io > make[5]: Entering directory '/<>/romio/mpi-io' > gcc -O3 -pthread -DLAM_BUILDING=1 -O3 -pthread -DFORTRANUNDERSCORE > -DHAVE_ROMIOCONF_H -I/<>/share/include > -I/<>/share/include -I/<>/romio/mpi-io -I../include > -I/<>/romio/mpi-io/../adio/include -I../adio/include -c close.c > gcc -O3 -pthread -DLAM_BUILDING=1 -O3 -pthread -DFORTRANUNDERSCORE > -DHAVE_ROMIOCONF_H -I/<>/share/include > -I/<>/share/include -I/<>/romio/mpi-io -I../include > -I/<>/romio/mpi-io/../adio/include -I../adio/include -c read.c > gcc -O3 -pthread -DLAM_BUILDING=1 -O3 -pthread -DFORTRANUNDERSCORE > -DHAVE_ROMIOCONF_H -I/<>/share/include > -I/<>/share/include -I/<>/romio/mpi-io -I../include > -I/<>/romio/mpi-io/../adio/include -I../adio/include -c open.c > gcc -O3 -pthread -DLAM_BUILDING=1 -O3 -pthread -DFORTRANUNDERSCORE > -DHAVE_ROMIOCONF_H -I/<>/share/include > -I/<>/share/include -I/<>/romio/mpi-io -I../include > -I/<>/romio/mpi-io/../adio/include -I../adio/include -c write.c > gcc -O3 -pthread -DLAM_BUILDING=1 -O3 -pthread -DFORTRANUNDERSCORE > -DHAVE_ROMIOCONF_H -I/<>/share/include > -I/<>/share/include -I/<>/romio/mpi-io -I../include > -I/<>/romio/mpi-io/../adio/include -I../adio/include -c > set_view.c > gcc -O3 -pthread -DLAM_BUILDING=1 -O3 -pthread -DFORTRANUNDERSCORE > -DHAVE_ROMIOCONF_H -I/<>/share/include > -I/<>/share/include -I/<>/romio/mpi-io -I../include > -I/<>/romio/mpi-io/../adio/include -I../adio/include -c iread.c > gcc -O3 -pthread -DLAM_BUILDING=1 -O3 -pthread -DFORTRANUNDERSCORE > -DHAVE_ROMIOCONF_H -I/<>/share/include > -I/<>/share/include -I/<>/romio/mpi-io -I../include > -I/<>/romio/mpi-io/../adio/include -I../adio/include -c iwrite.c > gcc -O3 -pthread -DLAM_BUILDING=1 -O3 -pthread -DFORTRANUNDERSCORE > -DHAVE_ROMIOCONF_H -I/<>/share/include > -I/<>/share/include -I/<>/romio/mpi-io -I../include > -I/<>/romio/mpi-io/../adio/include -I../adio/include -c iotest.c > gcc -O3 -pthread -DLAM_BUILDING=1 -O3 -pthread -DFORTRANUNDERSCORE > -DHAVE_ROMIOCONF_H -I/<>/share/include > -I/<>/share/include -I/<>/romio/mpi-io -I../include > -I/<>/romio/mpi-io/../adio/include -I../adio/include -c iowait.c > gcc -O3 -pthread -DLAM_BUILDING=1 -O3 -pthread -DFORTRANUNDERSCORE > -DHAVE_ROMIOCONF_H -I/<>/share/include > -I/<>/share/include -I/<>/romio/mpi-io -I../include > -I/<>/romio/mpi-io/../adio/include -I../adio/include -c seek.c > gcc -O3 -pthread -DLAM_BUILDING=1 -O3 -pthread -DFORTRANUNDERSCORE > -DHAVE_ROMIOCONF_H -I/<>/share/include > -I/<>/share/include -I/<>/romio/mpi-io -I../include > -I/<>/romio/mpi-io/../adio/include -I../adio/include -c > get_posn.c > gcc -O3 -pthread -DLAM_BUILDING=1 -O3 -pthread -DFORTRANUNDERSCORE > -DHAVE_ROMIOCONF_H -I/<>/share/include > -I/<>/share/include -I/<>/romio/mpi-io -I../include > -I/<>/romio/mpi-io/../adio/include -I../adio/include -c delete.c > gcc -O3 -pthread -DLAM_BUILDING=1 -O3 -pthread -DFORTRANUNDERSCORE > -DHAVE_ROMIOCONF_H -I/<>/share/include > -I/<>/share/include -I/<>/romio/mpi-io -I../include > -I/<>/romio/mpi-io/../adio/include -I../adio/include -c > read_all.c > gcc -O3 -pthread -DLAM_BUILDING=1 -O3 -pthread -DFORTRANUNDERSCORE > -DHAVE_ROMIOCONF_H -I/<>/share/include > -I/<>/share/include -I/<>/romio/mpi-io -I../include > -I/<>/romio/mpi-io/../adio/include -I../adio/include -c read_at.c > gcc -O3 -pthread -DLAM_BUILDING=1 -O3 -pthread -DFORTRANUNDERSCORE > -DHAVE_ROMIOCONF_H -I/<>/share/include > -I/<>/share/include -I/<>/romio/mpi-io -I../include > -I/<>/romio/mpi-io/../adio/include -I../adio/include -c > read_atall.c > gcc -O3 -pthread -DLAM_BUILDING=1 -O3 -pthread -DFORTRANUNDERSCORE > -DHAVE_ROMIOCONF_H -I/<>/share/include > -I/<>/share/include -I/<>/romio/mpi-io -I../include > -I/<>/romio/mpi-io/../adio/include -I../adio/include -c > iread_at.c > gcc -O3 -pthread -DLAM_BUILDING=1 -O3 -pthread -DFORTRANUNDERSCORE > -DHAVE_ROMIOCONF_H
Bug#997640: marked as done (pybluez: FTBFS: error in PyBluez setup command: use_2to3 is invalid.)
Your message dated Tue, 09 Nov 2021 00:05:26 +
with message-id
and subject line Bug#997640: fixed in pybluez 0.23-4
has caused the Debian Bug report #997640,
regarding pybluez: FTBFS: error in PyBluez setup command: use_2to3 is invalid.
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.)
--
997640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pybluez
Version: 0.23-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> rm -rf PyBluez.egg*
> dh_auto_clean
> I: pybuild base:232: python3.9 setup.py clean
> error in PyBluez setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make[1]: *** [debian/rules:23: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pybluez_0.23-3_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: pybluez
Source-Version: 0.23-4
Done: Nobuhiro Iwamatsu
We believe that the bug you reported is fixed in the latest version of
pybluez, 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 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu (supplier of updated pybluez package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 09 Nov 2021 08:42:15 +0900
Source: pybluez
Architecture: source
Version: 0.23-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Bluetooth Maintainers
Changed-By: Nobuhiro Iwamatsu
Closes: 997640
Changes:
pybluez (0.23-4) unstable; urgency=medium
.
* Team upload.
* Fix FTBFS error in PyBluez setup command (Closes: #997640)
- Add d/patches/Removed-2to3-command.patch.
Checksums-Sha1:
3feacf2d8ac03e748210bffdc0f11c5a55176748 2053 pybluez_0.23-4.dsc
6b22e01ea9936929c1786dc666ef430c25fd0695 4524 pybluez_0.23-4.debian.tar.xz
a3744f56ef3ad477b99b7a76e945ca585ba7614c 7067 pybluez_0.23-4_amd64.buildinfo
Checksums-Sha256:
f9638db1c642700e05b06b88c118f6c4d35bb4699590501b3a4e96e3bef4bc29 2053
pybluez_0.23-4.dsc
6ef64d8df9683693bc74b2078405a7a4ee02da8ab335419e5675c53e184f4815 4524
pybluez_0.23-4.debian.tar.xz
80f774555c9e3788707bc03eb523475f1313a988b700b34d2d6202de9b7155ea 7067
pybluez_0.23-4_amd64.buildinfo
Files:
7deb749cb5a2320bdb2f713468a73140 2053 python optional pybluez_0.23-4.dsc
6eb8d76c2788a39bc0b7cdc6c904bbf3 4524 python optional
pybluez_0.23-4.debian.tar.xz
27afd0c92b183bd0cbbfd0c4823157a3 7067 python optional
pybluez_0.23-4_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEXmKe5SMhlzV7hM9DMiR/u0CtH6YFAmGJuJIACgkQMiR/u0Ct
H6bCow//Vv3si6u1yy+tksd7uzX06zlkt9jGM/5bqj4HUiep/2FghWGJLDuweMSj
iiNazB+e2NBgC1dxVLEcyPKljeR6baWxiKOKw3jsE8/XBjN+kkhTfSkzt7PGzDHn
o3RBQ4oitqF8OyowFZMphJeyzio2irxaMTuvbzAPkw6I33qGgdViq2iPv4JGgeeQ
4k1RmQWvYpQbr3kbj9U8rAb7UxuC1ByXyQfycddRDn4fpErU2bASC4hxDh8WABEq
xCiynVza0KpfhePj8Cj0i+aXThfOsfGiz+7Kzhm7TT8COyBdQ9NT3Ib0JgfdJWjl
RZeRyPJcsO/wb3X03eHISYDfCN+3EtIoJ5JSQm5NyhS+ptXLX4SEif2P6KVK+6lQ
Fs4jbxvGHFJT86B/SQQGVgsEjbsVVbpMuVP+h/kp0fYFjsDvWOAqKIjwaAMdVAe9
WeGtZAQDUvHudI5okBHgWpJFOpjJ3n8Ckc5plvtpiIV4AE565oY2YpsNc75chvFU
m4E1rF41ZBlZBo2N0oz1qFQJkKYgye/eEEQIGi+syRL7wve1xQ4fIjmjAg/XRNYw
Bug#997752: marked as done (tdigest: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.)
Your message dated Tue, 09 Nov 2021 00:00:18 +
with message-id
and subject line Bug#997752: fixed in tdigest 1.2.0-2
has caused the Debian Bug report #997752,
regarding tdigest: FTBFS: Error: debian/control needs updating from
debian/control.in. Run 'pg_buildext updatecontrol'.
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.)
--
997752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997752
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tdigest
Version: 1.2.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -f tdigest.so libtdigest.a libtdigest.pc
> rm -f tdigest.so tdigest.o \
> tdigest.bc
> rm -f tdigest.o tdigest.bc
> rm -rf results/ regression.diffs regression.out tmp_check/ tmp_check_iso/
> log/ output_iso/
> make[1]: Leaving directory '/<>'
>dh_clean
>pg_buildext checkcontrol
> --- debian/control2020-10-09 12:40:46.0 +
> +++ debian/control.aql6ze 2021-10-23 06:28:52.934929870 +
> @@ -11,9 +11,9 @@
> Vcs-Git: https://salsa.debian.org/postgresql/tsigest.git
> Rules-Requires-Root: no
>
> -Package: postgresql-13-tdigest
> +Package: postgresql-14-tdigest
> Architecture: any
> -Depends: ${shlibs:Depends}, ${misc:Depends}, postgresql-13
> +Depends: ${shlibs:Depends}, ${misc:Depends}, postgresql-14
> Description: t-digest algorithm for on-line accumulation of rank-based
> statistics
> This PostgreSQL extension implements t-digest, a data structure for on-line
> accumulation of rank-based statistics such as quantiles and trimmed means.
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is
> required.
> make: *** [debian/rules:7: clean] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/tdigest_1.2.0-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: tdigest
Source-Version: 1.2.0-2
Done: Christoph Berg
We believe that the bug you reported is fixed in the latest version of
tdigest, 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 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christoph Berg (supplier of updated tdigest package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 08 Nov 2021 12:03:29 +0100
Source: tdigest
Binary: postgresql-14-tdigest postgresql-14-tdigest-dbgsym
Built-For-Profiles: nocheck
Architecture: source amd64
Version: 1.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers
Changed-By: Christoph Berg
Description:
postgresql-14-tdigest - t-digest algorithm for on-line accumulation of
rank-based statist
Closes: 995740 997752
Changes:
tdigest (1.2.0-2) unstable; urgency=medium
.
* Team upload for PostgreSQL 14. (Closes: #997752)
* Fix precision variation in tests on older PG versions and some
architectures. (Closes: #995740)
* Fix typo in Vcs-Git.
Checksums-Sha1:
c4594ca5883b0c1d93abef498ed8eb8203fd1a5c 2025 tdigest_1.2.0-2.dsc
62fcfa782454c5250c48acab97c31300a17a7511 2976 tdigest_1.2.0-2.debian.tar.xz
32f930279f9b08e304482204776740695cab94a8 45500
postgresql-14-tdigest-dbgsym_1.2.0-2_amd64.deb
931e10b42d4e9ce1030d9cee18b8871b4c1c9264 56796
postgresql-14-tdigest_1.2.0-2_amd64.deb
316bd80b4f7899fbeb9f2c609b7fad5de40d9243 10922 tdigest_1.2.0-2_amd64.buildinfo
Checksums-Sha256:
Bug#995740: marked as done (tdigest FTBFS on several architectures: tdigest_percentile test failure)
Your message dated Tue, 09 Nov 2021 00:00:18 + with message-id and subject line Bug#995740: fixed in tdigest 1.2.0-2 has caused the Debian Bug report #995740, regarding tdigest FTBFS on several architectures: tdigest_percentile test 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.) -- 995740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995740 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tdigest Version: 1.2.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=tdigest=1.2.0-1 ... == 1 of 1 tests failed. == The differences that caused some tests to fail can be viewed in the file "/<>/regression.diffs". A copy of the test summary that you see above is saved in the file "/<>/regression.out". make[1]: *** [/usr/lib/postgresql/13/lib/pgxs/src/makefiles/pgxs.mk:420: installcheck] Error 1 make[1]: Leaving directory '/<>' *** /tmp/pg_virtualenv.DgJ7kB/log/postgresql-13-regress.log (last 100 lines) *** 2021-09-30 12:05:02.867 UTC [3465319] LOG: starting PostgreSQL 13.4 (Debian 13.4-3) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 10.3.0-8) 10.3.0, 64-bit 2021-09-30 12:05:02.869 UTC [3465319] LOG: listening on IPv6 address "::1", port 5432 2021-09-30 12:05:02.869 UTC [3465319] LOG: listening on IPv4 address "127.0.0.1", port 5432 2021-09-30 12:05:02.870 UTC [3465319] LOG: listening on Unix socket "/tmp/.s.PGSQL.5432" 2021-09-30 12:05:02.880 UTC [3465324] LOG: database system was shut down at 2021-09-30 12:05:02 UTC 2021-09-30 12:05:02.903 UTC [3465319] LOG: database system is ready to accept connections Dropping cluster 13/regress ... regression.diffs diff -U3 /<>/test/expected/tdigest.out /<>/results/tdigest.out --- /<>/test/expected/tdigest.out 2021-09-11 13:55:48.0 + +++ /<>/results/tdigest.out2021-09-30 12:07:04.924491451 + @@ -1352,7 +1352,7 @@ (166024740,2147483647)) foo (count, value); tdigest_percentile - 30.358618321611857 + 30.358618321611853 (1 row) -- ### End 13 installcheck (FAILED with exit code 1) ### dh_pgxs_test: error: pg_buildext installcheck . . postgresql-%v-tdigest returned exit code 1 make: *** [debian/rules:7: binary-arch] Error 25 --- End Message --- --- Begin Message --- Source: tdigest Source-Version: 1.2.0-2 Done: Christoph Berg We believe that the bug you reported is fixed in the latest version of tdigest, 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 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Berg (supplier of updated tdigest package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 08 Nov 2021 12:03:29 +0100 Source: tdigest Binary: postgresql-14-tdigest postgresql-14-tdigest-dbgsym Built-For-Profiles: nocheck Architecture: source amd64 Version: 1.2.0-2 Distribution: unstable Urgency: medium Maintainer: Debian PostgreSQL Maintainers Changed-By: Christoph Berg Description: postgresql-14-tdigest - t-digest algorithm for on-line accumulation of rank-based statist Closes: 995740 997752 Changes: tdigest (1.2.0-2) unstable; urgency=medium . * Team upload for PostgreSQL 14. (Closes: #997752) * Fix precision variation in tests on older PG versions and some architectures. (Closes: #995740) * Fix typo in Vcs-Git. Checksums-Sha1: c4594ca5883b0c1d93abef498ed8eb8203fd1a5c 2025 tdigest_1.2.0-2.dsc 62fcfa782454c5250c48acab97c31300a17a7511 2976 tdigest_1.2.0-2.debian.tar.xz 32f930279f9b08e304482204776740695cab94a8 45500 postgresql-14-tdigest-dbgsym_1.2.0-2_amd64.deb 931e10b42d4e9ce1030d9cee18b8871b4c1c9264 56796 postgresql-14-tdigest_1.2.0-2_amd64.deb 316bd80b4f7899fbeb9f2c609b7fad5de40d9243 10922 tdigest_1.2.0-2_amd64.buildinfo Checksums-Sha256: e976fd22b82dc7a3fb76fdb1d4740c0804f61a717ba4031926335675bdde254b 2025 tdigest_1.2.0-2.dsc 9fdb1c1c5a905c6408e5cd90441e287726b43fe04e20a1ac9e928802600abf56 2976 tdigest_1.2.0-2.debian.tar.xz ed72f9c55c7f9606df9f22128867409e9bed024dbd1a2766e3400d4a2d2a2663 45500
Bug#997942: tomboy-ng: FTBFS with fpc 3.2.2
Ahh, thanks Graham, On Mon, 2021-11-08 at 13:03 +0200, Graham Inggs wrote: > > > very simple fix but as I am very close to releasing a new version > > anyway, maybe we can wait until them ? > > Sure, there's no reason to rush a fix now. Replying to this bug will > delay the pending autoremoval. Excellent. I may well be ready to act before the (25th) removal date anyway. The build test then wait for the Spanish translation... Philipp Huebner, my sponsor, tells me I can close this bug with an upload of the new version, so thats nice and tidy. > On Sun, 7 Nov 2021 at 02:41, David Bannon > > > that. How do I test my build against tools only available in sid ? > > > ...It is possible to install > individual packages from unstable on a testing system [1]. Indeed, I have just tried that, found it does what I need. I will build a Testing VM that can build packages, force sid's FPC (and maybe Lazarus) and test my build there. I expect it will be fine but will be happier if I can be sure. > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-pascal-devel OK, I have subscribed. I will find it interesting, if I can be useful, that would be good too. Davo
Bug#998746: marked as pending in libreoffice
Control: tag -1 pending Hello, Bug #998746 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/-/commit/cf59d579696157c2ce81915d19da415646fc7404 bump ure depends to >= 1:7.3.0~ (closes: #998746) (this message was generated automatically) -- Greetings https://bugs.debian.org/998746
Processed: Bug#998746 marked as pending in libreoffice
Processing control commands: > tag -1 pending Bug #998746 [libreoffice] /usr/lib/libreoffice/program/libmergedlo.so: undefined symbol: _ZN8MsLangId17getSystemLanguageEv Ignoring request to alter tags of bug #998746 to the same tags previously set -- 998746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998746 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#998435 marked as pending in libreoffice
Processing control commands: > tag -1 pending Bug #998435 [libreoffice-java-common] libreoffice-java-common: missing Breaks+Replaces: libreoffice-smoketest-data (<< 1:7.3.0~) Ignoring request to alter tags of bug #998435 to the same tags previously set -- 998435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998435: marked as pending in libreoffice
Control: tag -1 pending Hello, Bug #998435 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/-/commit/43e0bfb460555d5843938a2c59dedd06045c4f11 also uncomment smoketest.jar move to -smoketest-data again (although effectively unused..) (closes: #998435) (this message was generated automatically) -- Greetings https://bugs.debian.org/998435
Bug#995999: marked as pending in prometheus
Control: tag -1 pending Hello, Bug #995999 in prometheus 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/go-team/packages/prometheus/-/commit/28288181ca2b02383c51f8d8592636e8668f147a Fix build failure in test suite with Go 1.16 Patch taken from upstream commit 8bf7bc68f1d678ea82c392f80486a62e7973720b. Closes: #995999 (this message was generated automatically) -- Greetings https://bugs.debian.org/995999
Processed: Bug#995999 marked as pending in prometheus
Processing control commands: > tag -1 pending Bug #995999 [prometheus] FTBFS: FAIL: TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks Added tag(s) pending. -- 995999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986695: marked as done (prometheus-mongodb-exporter: MongoDB exporter segfaults when connecting with relatively recent MongoDB databases)
Your message dated Mon, 8 Nov 2021 23:22:19 +0100 with message-id and subject line Re: Bug#986695: prometheus-mongodb-exporter: MongoDB exporter segfaults when connecting with relatively recent MongoDB databases has caused the Debian Bug report #986695, regarding prometheus-mongodb-exporter: MongoDB exporter segfaults when connecting with relatively recent MongoDB databases 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.) -- 986695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: prometheus-mongodb-exporter Version: 1.0.0+git20180522.e755a44-1+b20 Severity: grave Tags: upstream Justification: renders package unusable Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Paragoumba To: Debian Bug Tracking System Subject: prometheus-mongodb-exporter: Mongodb Exporter segfaults with new versions of MongoDB Message-ID: <161798894396.8376.16006048479438587500.report...@5h4d0w-tp.pulseheberg.com> X-Mailer: reportbug 7.5.3~deb10u1 Date: Fri, 09 Apr 2021 19:22:23 +0200 Package: prometheus-mongodb-exporter Version: 1.0.0+git20180522.e755a44-1+b20 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, * What led up to the situation? I tried to install prometheus-mongodb-exporter to export statistics about my MongoDB instance. After multiple attempt to make it connect to the database, I stopped the systemd service and ran it by hand and noticed it segfaults upon connecting. * What exactly did you do (or not do) that was effective (or ineffective)? I checked multiple times the config and that proved to be ineffective. The problem doesn't come from a faulty configuration. The package is incompatible with the newer versions of MongoDB * What was the outcome of this action? It still segfaults * What outcome did you expect instead? I expect the software to connect successfully and export data It appears that the upstream github repository (https://github.com/dcu/mongodb_exporter) from which this package is built hasn't been updated in two years. This other repo (https://github.com/percona/mongodb_exporter) contains the same sources but is actively maintained. I know it's not unusual for the Debian packages to be several version late but this version is completely unusable and the only solution for now is to not use the package in the Debian repositories and to install it from source. -- System Information: Debian Release: 10.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-16-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages prometheus-mongodb-exporter depends on: ii daemon 0.6.4-1+b2 ii libc6 2.28-10 prometheus-mongodb-exporter recommends no packages. prometheus-mongodb-exporter suggests no packages. -- Configuration Files: /etc/default/prometheus-mongodb-exporter changed [not included] -- debconf-show failed -- System Information: Debian Release: 10.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-16-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages prometheus-mongodb-exporter depends on: ii daemon 0.6.4-1+b2 ii libc6 2.28-10 prometheus-mongodb-exporter recommends no packages. prometheus-mongodb-exporter suggests no packages. -- Configuration Files: /etc/default/prometheus-mongodb-exporter changed [not included] -- debconf-show failed --- End Message --- --- Begin Message --- Version: 1.0.0+git20180522.e755a44-3 On Sat, 2021-04-24 at 22:25:52 +0200, Chris Hofstaedtler wrote: > Control: fixed -1 prometheus-mongodb-exporter/1.0.0+git20180522.e755a44-3 > > > I tried to install prometheus-mongodb-exporter to export statistics > > about my MongoDB instance. After multiple attempt to > > make it connect to the database, I stopped the systemd service and ran > > it by hand and noticed it segfaults upon connecting. > > This would appear to be a duplicate of #942871. And closing the
Bug#997314: marked as done (python-hbmqtt: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13)
Your message dated Mon, 08 Nov 2021 21:35:58 +
with message-id
and subject line Bug#997314: fixed in python-hbmqtt 0.9.6-1.1
has caused the Debian Bug report #997314,
regarding python-hbmqtt: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.9 returned exit code 13
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.)
--
997314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-hbmqtt
Version: 0.9.6-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package python-hbmqtt
> dpkg-buildpackage: info: source version 0.9.6-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Stein Magnus Jodal
>
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> running clean
> removing '/<>/.pybuild/cpython3_3.9_hbmqtt/build' (and
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-hbmqtt using existing
> ./python-hbmqtt_0.9.6.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building python-hbmqtt in
> python-hbmqtt_0.9.6-1.debian.tar.xz
> dpkg-source: info: building python-hbmqtt in python-hbmqtt_0.9.6-1.dsc
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_hbmqtt/build/hbmqtt
> copying hbmqtt/errors.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/hbmqtt
> copying hbmqtt/__init__.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/hbmqtt
> copying hbmqtt/codecs.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/hbmqtt
> copying hbmqtt/session.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/hbmqtt
> copying hbmqtt/adapters.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/hbmqtt
> copying hbmqtt/client.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/hbmqtt
> copying hbmqtt/version.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/hbmqtt
> copying hbmqtt/broker.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/hbmqtt
> copying hbmqtt/utils.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/hbmqtt
> creating /<>/.pybuild/cpython3_3.9_hbmqtt/build/tests
> creating /<>/.pybuild/cpython3_3.9_hbmqtt/build/tests/plugins
> copying tests/plugins/__init__.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/tests/plugins
> copying tests/plugins/test_manager.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/tests/plugins
> copying tests/plugins/test_persistence.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/tests/plugins
> copying tests/plugins/test_authentication.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/tests/plugins
> creating /<>/.pybuild/cpython3_3.9_hbmqtt/build/tests/mqtt
> copying tests/mqtt/test_pubrel.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/tests/mqtt
> copying tests/mqtt/test_packet.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/tests/mqtt
> copying tests/mqtt/test_unsuback.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/tests/mqtt
> copying tests/mqtt/__init__.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/tests/mqtt
> copying tests/mqtt/test_subscribe.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/tests/mqtt
> copying tests/mqtt/test_suback.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/tests/mqtt
> copying tests/mqtt/test_publish.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/tests/mqtt
> copying tests/mqtt/test_pubrec.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/tests/mqtt
> copying tests/mqtt/test_puback.py ->
> /<>/.pybuild/cpython3_3.9_hbmqtt/build/tests/mqtt
> copying
Bug#997422: marked as done (minieigen: FTBFS: AttributeError: module 'sys' has no attribute 'setdefaultencoding')
Your message dated Mon, 08 Nov 2021 21:35:39 + with message-id and subject line Bug#997422: fixed in minieigen 0.50.3+dfsg1-13 has caused the Debian Bug report #997422, regarding minieigen: FTBFS: AttributeError: module 'sys' has no attribute 'setdefaultencoding' 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.) -- 997422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: minieigen Version: 0.50.3+dfsg1-12 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/doc' > PYTHONPATH=. sphinx-build -b html -d build/doctrees source build/html > Error in sitecustomize; set PYTHONVERBOSE for traceback: > AttributeError: module 'sys' has no attribute 'setdefaultencoding' > Running Sphinx v4.2.0 > > Configuration error: > There is a syntax error in your configuration file: Missing parentheses in > call to 'print'. Did you mean print(sys.path)? (conf.py, line 27) > > make[2]: *** [Makefile:40: html] Error 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/minieigen_0.50.3+dfsg1-12_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: minieigen Source-Version: 0.50.3+dfsg1-13 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of minieigen, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated minieigen package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Nov 2021 18:29:32 +0100 Source: minieigen Architecture: source Version: 0.50.3+dfsg1-13 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Anton Gladky Closes: 997061 997422 Changes: minieigen (0.50.3+dfsg1-13) unstable; urgency=medium . * [bffaf47] Add .gitlab-ci.yml * [aa4532e] Fix compilation with sphinx 4.2.0. (Closes: #997061, #997422) * [cf8e87b] Bump debhelper from old 12 to 13. * [0936e8e] Update standards version to 4.6.0, no changes needed. * [3ee4a1d] Update watch file format version to 4. Checksums-Sha1: 38cec539f7a88a3ce7b4f89fa25478bdc83d703d 2196 minieigen_0.50.3+dfsg1-13.dsc dd7e5fd4dc861eea181843d23d87baaffe5d77eb 9456 minieigen_0.50.3+dfsg1-13.debian.tar.xz b2726853ead65f042e538344e9975a8e4f010422 8047 minieigen_0.50.3+dfsg1-13_source.buildinfo Checksums-Sha256: 405674f2e8d3b8b8c2144aaf1ae4b3dcb3c26467622ace2a57bce80279b1 2196 minieigen_0.50.3+dfsg1-13.dsc db352d7466d1481791dceee608da5bf60bb5870281431655ec3e5d0f9beb0d6b 9456 minieigen_0.50.3+dfsg1-13.debian.tar.xz 9da957a0978d6aaf3f73a7123dfce95f9a701366168d5fce5fa0502c6b0a0ec2 8047 minieigen_0.50.3+dfsg1-13_source.buildinfo Files: 2c2535295b75afff15c07f83e9455eee 2196 libs optional minieigen_0.50.3+dfsg1-13.dsc d891bb304214d15106e55e3bd4ff5a12 9456 libs optional minieigen_0.50.3+dfsg1-13.debian.tar.xz d65bc07f71de70502eed0870982b4f20 8047 libs optional minieigen_0.50.3+dfsg1-13_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAmGJks4ACgkQ0+Fzg8+n /wYSlg/+Lnh98xntc97qNjoPvm40tzUZqByoI1v1QjNsZ3sn0X6xSPCNa/qqsAlA ndrWBgpkdSsHgWUa4zGpY09/R9XFE1qp5qhVYJqrZ3q4wg9T2ZjBD+nVymrmBYBM t+m8jSILen9f7WRZsigzURnsHowbtXL0hkoj1XUlMEa5s7Y+Z0gqbDz0r6Xf1jCu 4CCnAwPfufORMlCsBqcpKrSqcR9RFcUDDY+YARFbr+OJAzs7vuhBXEKhva7+YH8+ vLsgEaEQu23fyiXcAPNyV8ySaOwP2zyOsh3vSzek+ipKC3oMI98KZ4yZCV55d9Ki
Bug#998287: marked as done (r-cran-pdftools: autopkgtest failure: nrow(fonts) not equal to 3)
Your message dated Mon, 08 Nov 2021 21:36:20 +
with message-id
and subject line Bug#998287: fixed in r-cran-pdftools 3.0.1-2
has caused the Debian Bug report #998287,
regarding r-cran-pdftools: autopkgtest failure: nrow(fonts) not equal to 3
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.)
--
998287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-pdftools
Version: 3.0.1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
Your package r-cran-pdftools has an autopkgtest, great. However, it
fails. Can you please investigate the situation and fix it? I copied
some of the output at the bottom of this report.
The release team has announced [1] that failing autopkgtest are now
considered RC in testing.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-pdftools/16361110/log.gz
autopkgtest [17:58:47]: test run-unit-test: [---
BEGIN TEST poppler.R
R version 4.1.1 (2021-08-10) -- "Kick Things"
Copyright (C) 2021 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)
R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.
R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.
Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.
> library(pdftools)
Using poppler version 20.09.0
>
BEGIN TEST testthat.R
R version 4.1.1 (2021-08-10) -- "Kick Things"
Copyright (C) 2021 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)
R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.
R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.
Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.
> library(testthat)
> library(pdftools)
Using poppler version 20.09.0
>
> test_check("pdftools")
══ Skipped tests
═══
• On CRAN (1)
══ Failed tests
── Failure (test-chinese.R:7:3): reading Chinese text
──
`text` does not match "風險因素".
Actual value: "
T\+2\\n\\n\\n\\n17,300,000\\n\\n\\n\\n299,900\\n\\n\\n\\n\\n
36\.8%\\n34\.9%\\n4,300,000
6,900,000 7,100,000\\n300,000\\n\\n\\n
3\.7% 1\.5% 3\.4%0\.1%\\n\\n\\n\\n\\n
80%\\n 10%
80%\\n\\n\\n\\n\\n – 31 –\\n"
Backtrace:
█
1. └─testthat::expect_match(text, "風險因素") test-chinese.R:7:2
2. └─testthat:::expect_match_(...)
── Failure (test-chinese.R:11:3): reading Chinese text
─
nrow(fonts) not equal to 3.
1/1 mismatches
[1] 1 - 3 == -2
── Failure (test-chinese.R:13:3): reading Chinese text
─
fonts\$name\[2\] does not match "MSung".
Actual value: ""
Backtrace:
█
1. └─testthat::expect_match(fonts$name[2], "MSung") test-chinese.R:13:2
2. └─testthat:::expect_match_(...)
── Failure (test-chinese.R:14:3): reading Chinese text
─
fonts\$name\[3\] does not match "MHei".
Actual value: ""
Backtrace:
█
1. └─testthat::expect_match(fonts$name[3], "MHei") test-chinese.R:14:2
2. └─testthat:::expect_match_(...)
[ FAIL 4 | WARN 0 | SKIP 1 | PASS 20 ]
Error: Test failures
Execution halted
autopkgtest [17:58:49]: test run-unit-test: ---]
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r-cran-pdftools
Source-Version: 3.0.1-2
Done: Nilesh Patra
We believe that the bug you reported is fixed in the latest version of
r-cran-pdftools,
Bug#997061: marked as done (minieigen: FTBFS with sphinx 4.2.0)
Your message dated Mon, 08 Nov 2021 21:35:39 + with message-id and subject line Bug#997061: fixed in minieigen 0.50.3+dfsg1-13 has caused the Debian Bug report #997061, regarding minieigen: FTBFS with sphinx 4.2.0 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.) -- 997061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997061 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: minieigen Version: 0.50.3+dfsg1-12 Severity: serious Tags: ftbfs bookworm sid Hi Maintainer As can be seen in reproducible builds [1], minieigen FTBFS with sphinx 4.2.0. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/minieigen.html PYTHONPATH=. sphinx-build -b html -d build/doctrees source build/html Error in sitecustomize; set PYTHONVERBOSE for traceback: AttributeError: module 'sys' has no attribute 'setdefaultencoding' Running Sphinx v4.2.0 Configuration error: There is a syntax error in your configuration file: Missing parentheses in call to 'print'. Did you mean print(sys.path)? (conf.py, line 27) --- End Message --- --- Begin Message --- Source: minieigen Source-Version: 0.50.3+dfsg1-13 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of minieigen, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated minieigen package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Nov 2021 18:29:32 +0100 Source: minieigen Architecture: source Version: 0.50.3+dfsg1-13 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Anton Gladky Closes: 997061 997422 Changes: minieigen (0.50.3+dfsg1-13) unstable; urgency=medium . * [bffaf47] Add .gitlab-ci.yml * [aa4532e] Fix compilation with sphinx 4.2.0. (Closes: #997061, #997422) * [cf8e87b] Bump debhelper from old 12 to 13. * [0936e8e] Update standards version to 4.6.0, no changes needed. * [3ee4a1d] Update watch file format version to 4. Checksums-Sha1: 38cec539f7a88a3ce7b4f89fa25478bdc83d703d 2196 minieigen_0.50.3+dfsg1-13.dsc dd7e5fd4dc861eea181843d23d87baaffe5d77eb 9456 minieigen_0.50.3+dfsg1-13.debian.tar.xz b2726853ead65f042e538344e9975a8e4f010422 8047 minieigen_0.50.3+dfsg1-13_source.buildinfo Checksums-Sha256: 405674f2e8d3b8b8c2144aaf1ae4b3dcb3c26467622ace2a57bce80279b1 2196 minieigen_0.50.3+dfsg1-13.dsc db352d7466d1481791dceee608da5bf60bb5870281431655ec3e5d0f9beb0d6b 9456 minieigen_0.50.3+dfsg1-13.debian.tar.xz 9da957a0978d6aaf3f73a7123dfce95f9a701366168d5fce5fa0502c6b0a0ec2 8047 minieigen_0.50.3+dfsg1-13_source.buildinfo Files: 2c2535295b75afff15c07f83e9455eee 2196 libs optional minieigen_0.50.3+dfsg1-13.dsc d891bb304214d15106e55e3bd4ff5a12 9456 libs optional minieigen_0.50.3+dfsg1-13.debian.tar.xz d65bc07f71de70502eed0870982b4f20 8047 libs optional minieigen_0.50.3+dfsg1-13_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAmGJks4ACgkQ0+Fzg8+n /wYSlg/+Lnh98xntc97qNjoPvm40tzUZqByoI1v1QjNsZ3sn0X6xSPCNa/qqsAlA ndrWBgpkdSsHgWUa4zGpY09/R9XFE1qp5qhVYJqrZ3q4wg9T2ZjBD+nVymrmBYBM t+m8jSILen9f7WRZsigzURnsHowbtXL0hkoj1XUlMEa5s7Y+Z0gqbDz0r6Xf1jCu 4CCnAwPfufORMlCsBqcpKrSqcR9RFcUDDY+YARFbr+OJAzs7vuhBXEKhva7+YH8+ vLsgEaEQu23fyiXcAPNyV8ySaOwP2zyOsh3vSzek+ipKC3oMI98KZ4yZCV55d9Ki S7FlFDbeXF6SzSFNo9goGPbJlBNbWVQ4H/E0SvcxtKCAg4IYRPfl42sZonvuk1n6 QFtV97YifJIUsDxfqSMSvdry8fVsHhSvwB7sDSDHQiXk7DS8gi3AVHVEmjuUPM+D 1JBPZ5bB4qCZ4QB+2CgAFtScpm9btXGUvUn+SCauFPWka/nco81m9Tme0qJM3OGw TIVqDxcgJpiG1XsYm77KY1UhfIWPrAcjVGDwydYA12sBEWHrgSmnPK4JwYDlEOlI n/bsQmZamN4QFZWFmCpqDtlW0QVttOFPyECHObghxfF4KJ/lFP+828td5k/VqC4D nPSdgIQle0ZgtVnMrebeNmSNWLAMpYFakmkv25Bo67N8n2JY3nk= =7uUd -END PGP SIGNATURE End Message ---
Processed: Bug#998287 marked as pending in r-cran-pdftools
Processing control commands: > tag -1 pending Bug #998287 [src:r-cran-pdftools] r-cran-pdftools: autopkgtest failure: nrow(fonts) not equal to 3 Added tag(s) pending. -- 998287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998287: r-cran-pdftools: autopkgtest failure: nrow(fonts) not equal to 3
Hi Paul, On Mon, 8 Nov 2021 21:51:01 +0100 Paul Gevers wrote:> > Since this does not really look like a bug with this package, but rather > something very specific to "autopkgtest" or "schroot" environment is > triggering this, > I need your inputs to tackle this. I'd say the opposite. schroot's and lxc's generated with autopkgtest are cleaner than your own computer. Of course there's still something, so let's try to find out. Please excuse my choice of words being sloppy. I meant there's probably nothing wrong with the "code". > Would you have any idea as to what autopkgtest might do differently in a > chroot? Or what is specific there to be causing this? To my eye it looks like a font (or more) is (are) missing in the testbed. fonts\$name\[2\] does not match "MSung" and fonts\$name\[3\] does not match "MHei" suggest to me that something needs to provide them. Maybe that would fix the first issue too. Yep, this was a beginners mistake at my end, sorry for the noise. Just adding a test-dep on poppler-data did the trick. Thanks a lot for helping out, Nilesh OpenPGP_signature Description: OpenPGP digital signature
Bug#998287: marked as pending in r-cran-pdftools
Control: tag -1 pending Hello, Bug #998287 in r-cran-pdftools 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/r-pkg-team/r-cran-pdftools/-/commit/a79bc6ac9ac632f05e0bd8a89aad7fc4f54471ca Add test-dep on poppler-data (Closes: #998287) (this message was generated automatically) -- Greetings https://bugs.debian.org/998287
Processed: current version in unstable doeesn't fail it's autopkgtest
Processing commands for cont...@bugs.debian.org:
> fixed 982149 4.1.3-3
Bug #982149 {Done: Adrian Bunk }
[src:golang-github-xenolf-lego] golang-github-xenolf-lego: autopkgtest
regression: Build failure
Marked as fixed in versions golang-github-xenolf-lego/4.1.3-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
982149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#998287: r-cran-pdftools: autopkgtest failure: nrow(fonts) not equal to 3
Hi Nilesh, On 08-11-2021 17:41, Nilesh Patra wrote: > I could reproduce this (relevant part below). *But*, it passes when I > try run it locally with > > (i) "bash ./debian/tests/run-unit-tests" --> OK > > and also, inside a container with -- null > > (ii) "sudo autopkgtest -B ../*.deb -- null" --> Works perfect. Ack. > It does not work when I try running it in a schroot, or an lxc container > and gives errors similar to the one quoted below. So, something on your local system is interfering with the test. schroot and lxc are better in setting up a clean environment than the null runner. > I tried changing locales with several different permutations, but the > result is same. How about other environment variables? (Or fonts, see below) > Since this does not really look like a bug with this package, but rather > something very specific to "autopkgtest" or "schroot" environment is > triggering this, > I need your inputs to tackle this. I'd say the opposite. schroot's and lxc's generated with autopkgtest are cleaner than your own computer. Of course there's still something, so let's try to find out. > Would you have any idea as to what autopkgtest might do differently in a > chroot? Or what is specific there to be causing this? To my eye it looks like a font (or more) is (are) missing in the testbed. fonts\$name\[2\] does not match "MSung" and fonts\$name\[3\] does not match "MHei" suggest to me that something needs to provide them. Maybe that would fix the first issue too. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#997250: marked as done (lombok-ast: FTBFS: [ivy:compile] /<>/src/ecjTransformer/lombok/ast/ecj/EcjTreeConverter.java:1125: error: cannot find symbol)
Your message dated Mon, 08 Nov 2021 20:37:11 +
with message-id
and subject line Bug#997250: fixed in lombok-ast 0.2+ds-6
has caused the Debian Bug report #997250,
regarding lombok-ast: FTBFS: [ivy:compile]
/<>/src/ecjTransformer/lombok/ast/ecj/EcjTreeConverter.java:1125:
error: cannot find symbol
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.)
--
997250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lombok-ast
Version: 0.2+ds-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p build
> cp -r src/main main_backup
> cp -r lombok.ast_generatedSource/* src/main/
> cp -r lombok.ast_generatedSource build
> ant dist
> Buildfile: /<>/build.xml
>
> templateProcessor:
> [taskdef] Could not load definitions from resource
> org/apache/ivy/ant/antlib.xml. It could not be found.
> [compile:mkdir] Created dir: /<>/build/templateProcessor
> [compile:javac] Compiling 10 source files to
> /<>/build/templateProcessor
> [ivy:compile] warning: [options] bootstrap class path not set in conjunction
> with -source 8
> [ivy:compile] Note:
> /<>/src/template/lombok/ast/template/TemplateProcessor.java uses
> or overrides a deprecated API.
> [ivy:compile] Note: Recompile with -Xlint:deprecation for details.
> [ivy:compile] 1 warning
> [compile:javac] Creating empty
> /<>/build/templateProcessor/lombok/ast/template/package-info.class
> [mkdir] Created dir: /<>/build/templateProcessor/META-INF
> [mkdir] Created dir:
> /<>/build/templateProcessor/META-INF/services
> [jar] Building jar: /<>/build/templateProcessor.jar
>
> compile:
>[tstamp] Honouring environment variable SOURCE_DATE_EPOCH which has been
> set to 1611057397
> [compile:mkdir] Created dir: /<>/build/lombok.ast
> [compile:javac] Compiling 667 source files to
> /<>/build/lombok.ast
> [ivy:compile] warning: [options] bootstrap class path not set in conjunction
> with -source 6
> [ivy:compile] warning: [options] source value 6 is obsolete and will be
> removed in a future release
> [ivy:compile] warning: [options] target value 1.6 is obsolete and will be
> removed in a future release
> [ivy:compile] warning: [options] To suppress warnings about obsolete options,
> use -Xlint:-options.
> [ivy:compile]
> /<>/src/main/com/sun/tools/javac/model/AnnotationProxyMaker.java:84:
> warning: AnnotationParser is internal proprietary API and may be removed in
> a future release
> [ivy:compile] return AnnotationParser.annotationForMap(annoType,
> [ivy:compile]^
> [ivy:compile]
> /<>/src/main/com/sun/tools/javac/model/AnnotationProxyMaker.java:164:
> warning: ExceptionProxy is internal proprietary API and may be removed in a
> future release
> [ivy:compile] if (!(value instanceof ExceptionProxy) &&
> [ivy:compile]^
> [ivy:compile]
> /<>/src/main/com/sun/tools/javac/model/AnnotationProxyMaker.java:165:
> warning: AnnotationType is internal proprietary API and may be removed in a
> future release
> [ivy:compile]
> !AnnotationType.invocationHandlerReturnType(returnClass)
> [ivy:compile] ^
> [ivy:compile]
> /<>/src/main/com/sun/tools/javac/model/AnnotationProxyMaker.java:201:
> warning: ExceptionProxy is internal proprietary API and may be removed in a
> future release
> [ivy:compile] if (value == null || value instanceof
> ExceptionProxy) {
> [ivy:compile] ^
> [ivy:compile]
> /<>/src/main/com/sun/tools/javac/model/AnnotationProxyMaker.java:225:
> warning: EnumConstantNotPresentExceptionProxy is internal proprietary API
> and may be removed in a future release
> [ivy:compile] value = new
> EnumConstantNotPresentExceptionProxy(
> [ivy:compile] ^
> [ivy:compile]
> /<>/src/main/com/sun/tools/javac/model/AnnotationProxyMaker.java:252:
> warning: ExceptionProxy is internal proprietary API and may be removed in a
> future release
> [ivy:compile] value = new ExceptionProxy() {
> [ivy:compile] ^
> [ivy:compile]
> /<>/src/main/com/sun/tools/javac/model/AnnotationProxyMaker.java:271:
> warning: ExceptionProxy is internal proprietary API and may be removed in a
> future release
> [ivy:compile] private static
Bug#998837: marked as done (gnome-flashback: GNOME Flashback segfaults at login)
Your message dated Mon, 08 Nov 2021 20:35:33 +
with message-id
and subject line Bug#998837: fixed in gnome-flashback 3.42.0-2
has caused the Debian Bug report #998837,
regarding gnome-flashback: GNOME Flashback segfaults at login
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.)
--
998837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-flashback
Version: 3.42.0-1
Severity: important
Dear Maintainer,
After updating gnome-flashback today, I am unable to login to the "GNOME
Flashback (Metacity)" sesson - I immediately get the "Oh no, an error occured,
please log out" screen.
Poking around in `journalctl --user` I discovered the following entry at the
time of my login attempt:
gnome-flashback.service: Main process exited, code=killed, status=11/SEGV
After installing systemd-coredump, I managed to extract a backtrace:
#0 gf_logical_monitor_configs_have_monitor
(logical_monitor_configs=logical_monitor_configs@entry=0x55ec78aeb020 =
{...}, monitor_spec=monitor_spec@entry=0x55ec78ad1f50)
at ./backends/gf-logical-monitor-config.c:56
#1 0x55ec77c8bd48 in gf_monitors_config_new
(monitor_manager=monitor_manager@entry=0x7fa438003d70,
logical_monitor_configs=logical_monitor_configs@entry=0x55ec78aeb020 = {...},
layout_mode=layout_mode@entry=GF_LOGICAL_MONITOR_LAYOUT_MODE_PHYSICAL,
flags=flags@entry=GF_MONITORS_CONFIG_FLAG_NONE) at ./backends/gf-monitors-
config.c:179
#2 0x55ec77c934a6 in create_monitors_config
(match_rule=, positioning=MONITOR_POSITIONING_LINEAR,
config_flags=GF_MONITORS_CONFIG_FLAG_NONE, config_manager=,
config_manager=) at ./backends/gf-monitor-config-manager.c:603
#3 0x55ec77c8643b in gf_monitor_manager_ensure_configured
(manager=manager@entry=0x7fa438003d70) at ./backends/gf-monitor-manager.c:2786
#4 0x55ec77c98d79 in gf_monitor_manager_xrandr_ensure_initial_config
(manager=0x7fa438003d70) at ./backends/gf-monitor-manager-xrandr.c:699
#5 0x55ec77c85ce7 in gf_monitor_manager_setup (manager=0x7fa438003d70) at
./backends/gf-monitor-manager.c:2477
#6 0x55ec77c841c3 in gf_backend_new
(type=type@entry=GF_BACKEND_TYPE_X11_CM) at ./backends/gf-backend.c:377
#7 0x55ec77c823e0 in gf_application_init (application=0x55ec78ae4550) at
./gnome-flashback/gf-application.c:328
Looking at the code of gf_logical_monitor_configs_have_monitor(), it takes a
list of GfLogicalMonitorConfig, and the first one in the list looks like:
(gdb) print *((GfLogicalMonitorConfig *)l->data)
$5 = {layout = {x = 3, y = 0, width = 0, height = 0},
monitor_configs = 0xe0001 = {
...which seems very suspicious to me. The second one in the list looks like:
(gdb) print *((GfLogicalMonitorConfig *)logical_monitor_configs->next->data)
$9 = {layout = {x = 0, y = 0, width = 1920, height = 1080},
monitor_configs = 0x55ec78b1ac60 = {0x55ec78b1f020},
transform = GF_MONITOR_TRANSFORM_NORMAL, scale = 1, is_primary = 1,
is_presentation = 0}
...which seems to exactly match the monitor I'm using. There is no third item
in the list.
I walked up the stack to create_monitors_config() where this data structure is
created, and it looks like the `logical_monitor_configs` variable is created,
and then appended to, but never initialised. I don't know if that's actually
the problem, but it's consistent with the symptoms I'm seeing.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.14.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gnome-flashback depends on:
ii gnome-flashback-common 3.42.0-1
ii libasound2 1.2.5.1-1
ii libatk1.0-0 2.36.0-2
ii libc62.32-4
ii libcairo21.16.0-5
ii libcanberra-gtk3-0 0.30-8
ii libcanberra0 0.30-8
ii libgdk-pixbuf-2.0-0 2.42.6+dfsg-2
ii libgdm1 41.0-3
ii libglib2.0-0 2.70.0-3
ii libgnome-bluetooth13 3.34.5-4
ii libgnome-desktop-3-1941.0-1
ii libgnome-panel0 3.42.0-1
ii libgtk-3-0 3.24.30-3
ii libibus-1.0-51.5.25-2
ii libpam0g 1.4.0-10
ii libpango-1.0-0
Bug#997133: More information in the ubuntu bugtracker
I updated the git repository with the upstream patch that I mentioned in the Ubuntu bug, the FTBFS is fixed with it but autopkgtest is still failing. As Reinhard mentioned in the Ubuntu bug, autopgktest seems to always fail in Debian for some years, so I do not know if this would be a blocker. The error that I am getting is the following: Error parsing file: /tmp/autopkgtest.4L5Gnh/autopkgtest_tmp/_build/src/github.com/hashicorp/consul/agent/connect/ca/provider_vault.go:18:11: could not import github.com/hashicorp/vault/api (invalid package name: "") Error parsing file: /tmp/autopkgtest.4L5Gnh/autopkgtest_tmp/_build/src/github.com/hashicorp/consul/agent/connect/ca/provider_vault.go:18:11: could not import github.com/hashicorp/vault/api (invalid package name: "") Error parsing file: /tmp/autopkgtest.4L5Gnh/autopkgtest_tmp/_build/src/github.com/hashicorp/consul/agent/connect/ca/provider_vault.go:18:11: could not import github.com/hashicorp/vault/api (invalid package name: "") Error parsing file: /tmp/autopkgtest.4L5Gnh/autopkgtest_tmp/_build/src/github.com/hashicorp/consul/agent/connect/ca/provider_vault.go:18:11: could not import github.com/hashicorp/vault/api (invalid package name: "") Error parsing file: /tmp/autopkgtest.4L5Gnh/autopkgtest_tmp/_build/src/github.com/hashicorp/consul/agent/connect/ca/provider_vault.go:18:11: could not import github.com/hashicorp/vault/api (invalid package name: "") Error parsing file: /tmp/autopkgtest.4L5Gnh/autopkgtest_tmp/_build/src/github.com/hashicorp/consul/agent/connect/ca/provider_vault.go:18:11: could not import github.com/hashicorp/vault/api (invalid package name: "") Error parsing file: /tmp/autopkgtest.4L5Gnh/autopkgtest_tmp/_build/src/github.com/hashicorp/consul/agent/connect/ca/provider_vault.go:18:11: could not import github.com/hashicorp/vault/api (invalid package name: "") Error parsing file: /tmp/autopkgtest.4L5Gnh/autopkgtest_tmp/_build/src/github.com/hashicorp/consul/agent/connect/ca/provider_vault.go:18:11: could not import github.com/hashicorp/vault/api (invalid package name: "") Unable to find Provider in any go files under this path src/github.com/hashicorp/consul/agent/connect/ca/provider.go:10: running "mockery": exit status 1 This is happening because agent/connect/ca/provider_vault.go imports github.com/hashicorp/vault/api which was excluded as part of the vendor code but it is not available in Debian yet. We could also try to disable this agent for now to avoid shipping code without the needed dependencies. -- Lucas Kanashiro
Processed: bug 984232 is forwarded to https://github.com/cnr-isti-vclab/meshlab/commit/e53bab0c452d58f70b4af525f9df68199e1333d0
Processing commands for cont...@bugs.debian.org: > forwarded 984232 > https://github.com/cnr-isti-vclab/meshlab/commit/e53bab0c452d58f70b4af525f9df68199e1333d0 Bug #984232 [src:meshlab] meshlab: ftbfs with GCC-11 Set Bug forwarded-to-address to 'https://github.com/cnr-isti-vclab/meshlab/commit/e53bab0c452d58f70b4af525f9df68199e1333d0'. > thanks Stopping processing here. Please contact me if you need assistance. -- 984232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997133: marked as pending in consul
Control: tag -1 pending Hello, Bug #997133 in consul 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/go-team/packages/consul/-/commit/1f72fa496c2421b2b084bdc97ded7aa644e872c5 Add upstream patch to fix FTBFS (Closes: #997133) (this message was generated automatically) -- Greetings https://bugs.debian.org/997133
Processed: Bug#997133 marked as pending in consul
Processing control commands: > tag -1 pending Bug #997133 [src:consul] consul: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 -short -failfast -timeout 8m [...] returned exit code 1 Added tag(s) pending. -- 997133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998837: marked as pending in gnome-flashback
Control: tag -1 pending Hello, Bug #998837 in gnome-flashback 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/gnome-team/gnome-flashback/-/commit/8a5b0ece8f61c547723cfb78ee64c78ad4dfd0a7 Backport upstream patch to fix segfault on login. Closes: #998837. Thanks: Timothy Allen for the bug report. (this message was generated automatically) -- Greetings https://bugs.debian.org/998837
Processed: Bug#998837 marked as pending in gnome-flashback
Processing control commands: > tag -1 pending Bug #998837 [gnome-flashback] gnome-flashback: GNOME Flashback segfaults at login Added tag(s) pending. -- 998837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 996120 in 1.0.4-1
Processing commands for cont...@bugs.debian.org:
> fixed 996120 1.0.4-1
Bug #996120 {Done: Adrian Bunk } [src:ruby-acts-as-list]
ruby-acts-as-list: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
ArgumentError: wrong number of arguments (given 3, expected 2)
Marked as fixed in versions ruby-acts-as-list/1.0.4-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
996120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: 0.10.12 builds
Processing commands for cont...@bugs.debian.org: > tags 996117 fixed-upstream Bug #996117 [src:ruby-active-model-serializers] ruby-active-model-serializers: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 3) Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 996117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996120: marked as done (ruby-acts-as-list: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 3, expected 2))
Your message dated Mon, 8 Nov 2021 22:01:12 +0200 with message-id <20211108200112.GA5050@localhost> and subject line Re: Bug#996120: ruby-acts-as-list: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 3, expected 2) has caused the Debian Bug report #996120, regarding ruby-acts-as-list: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 3, expected 2) 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.) -- 996120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-acts-as-list Version: 1.0.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-acts-as-list was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: wrong number of arguments (given 3, expected 2) > > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/connection_adapters/abstract/schema_definitions.rb:364:in > `column' > /<>/test/test_list.rb:14:in `block in setup_db' > > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/connection_adapters/abstract/schema_statements.rb:309:in > `create_table' > /<>/test/test_list.rb:13:in `setup_db' > /<>/test/test_list.rb:638:in `setup' > > 194 runs, 66 assertions, 0 failures, 166 errors, 0 skips > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/test_default_scope_with_select.rb" "test/test_joined_list.rb" > "test/test_list.rb" "test/test_no_update_for_extra_classes.rb" > "test/test_no_update_for_scope_destruction.rb" > "test/test_no_update_for_subclasses.rb" > "test/test_scope_with_user_defined_foreign_key.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-acts-as-list/ruby-acts-as-list_1.0.3-1+rebuild1633375107_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- On Mon, Oct 11, 2021 at 09:43:54AM -0300, Antonio Terceiro wrote: > Source: ruby-acts-as-list > Version: 1.0.3-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: debian-r...@lists.debian.org > Usertags: ruby3.0 > > Hi, > > We are about to enable building against ruby3.0 on unstable. During a test > rebuild, ruby-acts-as-list was found to fail to build in that situation. > > To reproduce this locally, you need to install ruby-all-dev from experimental > on an unstable system or build chroot. > > Relevant part (hopefully): > > ArgumentError: wrong number of arguments (given 3, expected 2) > > > > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/connection_adapters/abstract/schema_definitions.rb:364:in > > `column' > > /<>/test/test_list.rb:14:in `block in setup_db' > > > > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/connection_adapters/abstract/schema_statements.rb:309:in > > `create_table' > > /<>/test/test_list.rb:13:in `setup_db' > > /<>/test/test_list.rb:638:in `setup' >... The problem appears to be fixed now (in ruby-activerecord?): https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-acts-as-list.html cu Adrian--- End Message ---
Processed: Bumping severity of 998837 to RC
Processing commands for cont...@bugs.debian.org: > severity 998837 grave Bug #998837 [gnome-flashback] gnome-flashback: GNOME Flashback segfaults at login Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 998837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997960: marked as done (Debspawn deletes anything mounted in a container)
Your message dated Mon, 08 Nov 2021 19:48:28 + with message-id and subject line Bug#997960: fixed in debspawn 0.5.1-1 has caused the Debian Bug report #997960, regarding Debspawn deletes anything mounted in a container 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.) -- 997960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debspawn Version: 0.5.0-1 Severity: serious Justification: Significant data loss I used debspawn interact to interactively explore what I needed to do to get a new upstream package building. To make that easier, I mounted my source trees and debian working environment in the container. On exit, debspawn deleted everything. In retrospect, I can understand why this is, but it's pretty hostile to the developer. I might be alone, but I find it very helpful to mount various things into containers when exploring why things don't work. My recommendation would be to check for bind mounts and make sure they can be unmounted before cleaning up. A fix that would have worked in my case but that may not generally be good enough would have been to restrict the container deletion to one-file-system. -- System Information: Debian Release: 11.1 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable'), (200, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-3-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debspawn depends on: ii debootstrap1.0.123 ii python33.9.2-3 ii python3-toml 0.10.1-1 ii systemd-container 247.3-6 ii zstd 1.4.8+dfsg-2.1 Versions of packages debspawn recommends: ii build-essential 12.9 ii devscripts 2.21.4 Versions of packages debspawn suggests: ii sudo 1.9.5p2-3 -- no debconf information --- End Message --- --- Begin Message --- Source: debspawn Source-Version: 0.5.1-1 Done: Matthias Klumpp We believe that the bug you reported is fixed in the latest version of debspawn, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klumpp (supplier of updated debspawn package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 08 Nov 2021 19:56:06 +0100 Source: debspawn Architecture: source Version: 0.5.1-1 Distribution: unstable Urgency: medium Maintainer: Matthias Klumpp Changed-By: Matthias Klumpp Closes: 989897 989907 997960 Changes: debspawn (0.5.1-1) unstable; urgency=medium . [ Matthias Klumpp ] * New upstream version: 0.5.1 - Adds a safeguard to unmount any (bin)mount points when removing a container, so no data gets deleted by accident (Closes: #997960). - Decouples image names from suite names, so people can give their own names to images for experimentation (Closes: #989897). - Changes the default bootstrap variant to "buildd". To access images created without a variant, users may need to pass `--variant=none` to debspawn or change the global default (Closes: #989907). * Add NEWS entry about changed default bootstrap variant . [ Debian Janitor ] * Bump debhelper from old 12 to 13 * Set upstream metadata fields Checksums-Sha1: d5ead798ccf9e0190364c43e066fcdde00faf318 2026 debspawn_0.5.1-1.dsc a9961a77a1fc6bcdf005609cd42f4b37ddea7d08 58842 debspawn_0.5.1.orig.tar.gz b99ca3e6689555467ef6dbe42369ff81101d1f06 4196 debspawn_0.5.1-1.debian.tar.xz 28e37696254ca72c0cb77e1f886ace5033250e86 7739 debspawn_0.5.1-1_source.buildinfo Checksums-Sha256: 3a01e538e06fa09131f8de175e90ff8375463583c7afa53095ea343fd83fba0f 2026 debspawn_0.5.1-1.dsc 3d0e10c3f11b75072970e8511fdbcb5669f323273bf186c149cda4700e1c1877 58842 debspawn_0.5.1.orig.tar.gz b1c714a2c4a31776651fb81e7368b322c2f1c2246efb29e45615738c718f77b0 4196 debspawn_0.5.1-1.debian.tar.xz
Bug#984020: marked as done (codeblocks: ftbfs with GCC-11)
Your message dated Mon, 08 Nov 2021 19:33:35 + with message-id and subject line Bug#984020: fixed in codeblocks 20.03-3.1 has caused the Debian Bug report #984020, regarding codeblocks: ftbfs with GCC-11 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.) -- 984020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:codeblocks Version: 20.03-3 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/codeblocks_20.03-3_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] /bin/bash ../../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../../../src/include -I/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -I/usr/include/wx-3.0 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread -I../../../src/include/scripting/include -I../../../src/include -I../../../src/sdk/wxscintilla/include -I../../../src/include/scripting/sqplus -DCB_AUTOCONF -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DBUILD_DATE="\"2020-04-18\"" -DBUILD_TIME="\"19:47:24\"" -DCB_PRECOMP -DPIC -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Winvalid-pch -fPIC -fexceptions -c -o projectpathpanel.lo projectpathpanel.cpp /bin/bash ../../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../../../src/include -I/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -I/usr/include/wx-3.0 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread -I../../../src/include/scripting/include -I../../../src/include -I../../../src/sdk/wxscintilla/include -I../../../src/include/scripting/sqplus -DCB_AUTOCONF -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DBUILD_DATE="\"2020-04-18\"" -DBUILD_TIME="\"19:47:24\"" -DCB_PRECOMP -DPIC -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Winvalid-pch -fPIC -fexceptions -c -o wiz.lo wiz.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../../src/include -I/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -I/usr/include/wx-3.0 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread -I../../../src/include/scripting/include -I../../../src/include -I../../../src/sdk/wxscintilla/include -I../../../src/include/scripting/sqplus -DCB_AUTOCONF -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DBUILD_DATE=\"2020-04-18\" -DBUILD_TIME=\"19:47:24\" -DCB_PRECOMP -DPIC -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Winvalid-pch -fPIC -fexceptions -c projectpathpanel.cpp -fPIC -DPIC -o .libs/projectpathpanel.o libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../../src/include -I/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -I/usr/include/wx-3.0 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread -I../../../src/include/scripting/include -I../../../src/include -I../../../src/sdk/wxscintilla/include -I../../../src/include/scripting/sqplus -DCB_AUTOCONF -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -DBUILD_DATE=\"2020-04-18\" -DBUILD_TIME=\"19:47:24\" -DCB_PRECOMP -DPIC -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
Bug#984020: codeblocks: diff for NMU version 20.03-3.1
On Mon, Nov 08, 2021 at 12:49:50PM -0400, David Prévot wrote: > Hi Adrian, > > Le 08/11/2021 à 11:55, Adrian Bunk a écrit : > > > I've prepared an NMU for codeblocks (versioned as 20.03-3.1) and > > uploaded it to DELAYED/14. > > Thanks! Feel free to reschedule it to DELAYED/0 ;). Thanks, done. > Regards > > David cu Adrian
Bug#996299: marked as done (ruby-invisible-captcha: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: require 'bundler/setup' # Set up gems listed in the Gemfile.)
Your message dated Mon, 08 Nov 2021 18:48:52 + with message-id and subject line Bug#996299: fixed in ruby-invisible-captcha 1.1.0-3 has caused the Debian Bug report #996299, regarding ruby-invisible-captcha: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: require 'bundler/setup' # Set up gems listed in the Gemfile. 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.) -- 996299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-invisible-captcha Version: 1.1.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-invisible-captcha was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > Failure/Error: require 'bundler/setup' # Set up gems listed in the Gemfile. > > Bundler::GemNotFound: > Could not find racc-1.4.16 in any of the sources > # > /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler.rb:149:in > `setup' > # ./spec/dummy/config/boot.rb:3:in `' > # ./spec/dummy/config/application.rb:1:in `' > # ./spec/dummy/config/environment.rb:2:in `require_relative' > # ./spec/dummy/config/environment.rb:2:in `' > # ./spec/spec_helper.rb:5:in `' > No examples found. > No examples found. > > > Finished in 0.5 seconds (files took 0.23192 seconds to load) > 0 examples, 0 failures, 1 error occurred outside of examples > > Finished in 0.5 seconds (files took 0.23192 seconds to load) > 0 examples, 0 failures, 1 error occurred outside of examples > > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-invisible-captcha/ruby-invisible-captcha_1.1.0-2+rebuild1633383610_amd64.build.txt signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-invisible-captcha Source-Version: 1.1.0-3 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of ruby-invisible-captcha, 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 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Leidert (supplier of updated ruby-invisible-captcha package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Nov 2021 19:07:21 +0100 Source: ruby-invisible-captcha Architecture: source Version: 1.1.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Daniel Leidert Closes: 996299 Changes: ruby-invisible-captcha (1.1.0-3) unstable; urgency=medium . * Team upload. * d/ruby-tests.rake: Remove all Gemfile.lock files between test runs (closes: #996299). Checksums-Sha1: cf81d594bfbd1b2c9b7b5346d150640d660df15d 2219 ruby-invisible-captcha_1.1.0-3.dsc 400f7c41635c59d12ce21ed51d2a449a5a210a1e 4056 ruby-invisible-captcha_1.1.0-3.debian.tar.xz 5e028e15eb0f2727fc3043838308149ed61d64db 11055 ruby-invisible-captcha_1.1.0-3_amd64.buildinfo Checksums-Sha256: 7278c146c8576e8ad9d5dc25446727377cd6c2b06c16ebb502aeeedce3937df7 2219 ruby-invisible-captcha_1.1.0-3.dsc ccc367b90b100681dfa68002dff821ace68d2a3e801d5dd4ca0463280b2d236b 4056 ruby-invisible-captcha_1.1.0-3.debian.tar.xz d9d1cde8e707fc415cf64636c97cb9d0b4f3d9b3cf136d01cd5db1785229d93a 11055 ruby-invisible-captcha_1.1.0-3_amd64.buildinfo Files: ef4e80e52c198093dba702952ad71894 2219 ruby optional ruby-invisible-captcha_1.1.0-3.dsc da6dfe41761e23e96ff14d474650fd88 4056 ruby optional ruby-invisible-captcha_1.1.0-3.debian.tar.xz fb27045d6ef89022bec60f45f52a76e8 11055 ruby optional
Bug#996302: marked as done (ruby-joiner: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: require 'bundler/setup')
Your message dated Mon, 08 Nov 2021 18:20:33 +
with message-id
and subject line Bug#996302: fixed in ruby-joiner 0.5.0-3
has caused the Debian Bug report #996302,
regarding ruby-joiner: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
Failure/Error: require 'bundler/setup'
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.)
--
996302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-joiner
Version: 0.5.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-joiner was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> Failure/Error: require 'bundler/setup'
>
> Bundler::GemNotFound:
> Could not find racc-1.4.16 in any of the sources
> #
> /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler.rb:149:in
> `setup'
> # ./spec/spec_helper.rb:2:in `'
> # ./spec/acceptance/paths_spec.rb:1:in `'
> No examples found.
>
>
> Finished in 0.5 seconds (files took 0.59366 seconds to load)
> 0 examples, 0 failures, 2 errors occurred outside of examples
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb failed
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-joiner/ruby-joiner_0.5.0-2+rebuild1633384371_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-joiner
Source-Version: 0.5.0-3
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-joiner, 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 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Leidert (supplier of updated ruby-joiner package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 08 Nov 2021 18:18:40 +0100
Source: ruby-joiner
Architecture: source
Version: 0.5.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Daniel Leidert
Closes: 996302
Changes:
ruby-joiner (0.5.0-3) unstable; urgency=medium
.
* Team upload.
* d/control (Build-Depends): Raise to dh 13.
(Standards-Version): Bump to 4.6.0.
* d/copyright: Add Upstream-Contact field.
* d/ruby-tests.rake: Remove Gemfile.lock between test runs (closes: #996302).
* d/rules: Use gem installation layout.
* d/watch: Minor improvements.
* d/patches/0004-bundler-strangety.patch: Add patch.
- Work around bundler in specs for autopkgtest.
* d/upstream/metadata: Add Archive field.
Checksums-Sha1:
bb20c868159fb11124da0ef5684e317a233d3b34 2102 ruby-joiner_0.5.0-3.dsc
fbed90cc27f555bf9603f5956c8fcd6565dbda74 3788 ruby-joiner_0.5.0-3.debian.tar.xz
7fda50d0f3695f3f0adb9132b64061b907d54bb2 10911
ruby-joiner_0.5.0-3_amd64.buildinfo
Checksums-Sha256:
cad20467881e469b43b8cb99eea94dfd37f3bd46b364e9e6c9ced9fa393d5064 2102
ruby-joiner_0.5.0-3.dsc
ab11abe8e5f5b9e4ebee9de11eab7c9d36dd0b9a10dbdcd147704cf27fd6521c 3788
ruby-joiner_0.5.0-3.debian.tar.xz
6c4416bae462d0439d037a444afbaf0986fbd927806b0edc3087834140ac4fad 10911
ruby-joiner_0.5.0-3_amd64.buildinfo
Files:
0dc9198ec0e17d3fe87bb9ec1cb7a985 2102 ruby optional ruby-joiner_0.5.0-3.dsc
4bfe82a078d4c1041a4c3d666576f351 3788 ruby optional
ruby-joiner_0.5.0-3.debian.tar.xz
30ce11add211065c23c35c6b4eae6d0a 10911 ruby optional
ruby-joiner_0.5.0-3_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmGJZJUACgkQS80FZ8KW
0F1aAA//RHzpx7vmkMpgz6ZZlGtiKXtIMRtlYwMCe5XSk+n8jDqFBPtXDT+F9krJ
iUklcjyNTkhz2UrXGZCooeF5XKU/16PBwQOJWeLOfDVoE9TN3E9oa1/dZc0DtjVR
Bug#997647: pystache: Tagged upstream version
Side note: the git version that I have used for the NMU is now available as 0.6.0.
Bug#997960: Debspawn deletes anything mounted in a container
Hi Sam! Am Mi., 27. Okt. 2021 um 21:24 Uhr schrieb Sam Hartman : > > Package: debspawn > Version: 0.5.0-1 > Severity: serious > Justification: Significant data loss > > I used debspawn interact to interactively explore what I needed to do to get > a new upstream package building. > To make that easier, I mounted my source trees and debian working environment > in the container. > > On exit, debspawn deleted everything. > In retrospect, I can understand why this is, but it's pretty hostile to the > developer. > I might be alone, but I find it very helpful to mount various things into > containers when exploring why things don't work. Ha! First of all, I'm very sorry for this issue, and I hope this didn't cause any bigger problems or a long recovery session. Debspawn does not really expect users to mount things as well behind its back... Bindmounts are evil sometimes, but ever since I deleted my whole root filesystem by accident, I became a lot more careful :-D > My recommendation would be to check for bind mounts and make sure they can be > unmounted before cleaning up. That is actually a rather annoying operation, as you need to parse `/proc/self/mountinfo` or call `findmnt` on every directory in order to not only find "real" mountpoints but also bindmounts. I tried the latter option though, and on my system I could only measure a slowdown of a few milliseconds, so that's IMHO perfectly fine as safety measure. > A fix that would have worked in my case but that may not generally be good > enough would have been to restrict the container deletion to one-file-system. That wouldn't find bindmounts though, and I'd rather catch these too :-) The new 0.5.1 release will have the change included and will just unmount any directory mountpoints upon container deletion - if the user decided to create mountpoints on *files*, deletion of those will likely just fail, which is fine with me (no data is lost and the user knows what (not) to do next time). Please give it a test with some scratch directory though before using this with important data - just in case! ;-) Cheers, Matthias
Processed: reassign 996377 to ruby-activesupport
Processing commands for cont...@bugs.debian.org: > # looks like a bug in ruby-activesupport affecting ruby-rspec-rails > reassign 996377 ruby-activesupport 2:6.0.3.7+dfsg-3 Bug #996377 [src:ruby-rspec-rails] ruby-rspec-rails: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Bug reassigned from package 'src:ruby-rspec-rails' to 'ruby-activesupport'. No longer marked as found in versions ruby-rspec-rails/4.0.1-2. Ignoring request to alter fixed versions of bug #996377 to the same values previously set Bug #996377 [ruby-activesupport] ruby-rspec-rails: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: Marked as found in versions rails/2:6.0.3.7+dfsg-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 996377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996302: marked as pending in ruby-joiner
Control: tag -1 pending Hello, Bug #996302 in ruby-joiner 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/ruby-team/ruby-joiner/-/commit/ab2ee7134fd58b23461b7feaa9f7abb3806206c8 Fix build failure * d/ruby-tests.rake: Remove Gemfile.lock between test runs (closes: #996302). (this message was generated automatically) -- Greetings https://bugs.debian.org/996302
Processed: Bug#996302 marked as pending in ruby-joiner
Processing control commands: > tag -1 pending Bug #996302 [src:ruby-joiner] ruby-joiner: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: require 'bundler/setup' Added tag(s) pending. -- 996302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996302 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997887: marked as done (r-cran-effectsize: autopkgtest regression on ppc64el: machine precision issue?)
Your message dated Mon, 08 Nov 2021 17:39:27 +
with message-id
and subject line Bug#997887: fixed in r-cran-effectsize 0.5-2
has caused the Debian Bug report #997887,
regarding r-cran-effectsize: autopkgtest regression on ppc64el: machine
precision issue?
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.)
--
997887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-effectsize
Version: 0.5-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of r-cran-effectsize the autopkgtest of
r-cran-effectsize fails in testing on ppc64el when that autopkgtest is
run with the binary packages of r-cran-effectsize from unstable. It
passes when run with only packages from testing. In tabular form:
passfail
r-cran-effectsize from testing0.5-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=r-cran-effectsize
https://ci.debian.net/data/autopkgtest/testing/ppc64el/r/r-cran-effectsize/16211124/log.gz
BEGIN TEST spelling.R
R version 4.1.1 (2021-08-10) -- "Kick Things"
Copyright (C) 2021 The R Foundation for Statistical Computing
Platform: powerpc64le-unknown-linux-gnu (64-bit)
R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.
R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.
Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.
> if (requireNamespace("spelling", quietly = TRUE)) {
+ spelling::spell_check_test(
+ vignettes = TRUE, error = FALSE,
+ skip_on_cran = TRUE
+ )
+ }
>
BEGIN TEST testthat.R
R version 4.1.1 (2021-08-10) -- "Kick Things"
Copyright (C) 2021 The R Foundation for Statistical Computing
Platform: powerpc64le-unknown-linux-gnu (64-bit)
R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.
R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.
Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.
> library(testthat)
> library(effectsize)
>
> test_check("effectsize")
Starting 2 test processes
══ Skipped tests
═══
• On CRAN (17)
• rstanarm cannot be loaded (1)
══ Failed tests
── Failure (test-eta_squared.R:89:5): aov
──
et1$CI_low (`actual`) not equal to et2$CI_low (`expected`).
`actual`: 0.20996729 0.
`expected`: 0.20996728 0.
[ FAIL 1 | WARN 1 | SKIP 18 | PASS 467 ]
Error: Test failures
Execution halted
autopkgtest [22:31:26]: test run-unit-test
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r-cran-effectsize
Source-Version: 0.5-2
Done: Nilesh Patra
We believe that the bug you reported is fixed in the latest version of
r-cran-effectsize, 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 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nilesh Patra (supplier of updated r-cran-effectsize 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:
Bug#997237: marked as done (lomiri-url-dispatcher: FTBFS: type_traits:44:3: error: template with C linkage)
Your message dated Mon, 08 Nov 2021 17:38:01 +
with message-id
and subject line Bug#997237: fixed in lomiri-url-dispatcher 0.1.0-5
has caused the Debian Bug report #997237,
regarding lomiri-url-dispatcher: FTBFS: type_traits:44:3: error: template with
C linkage
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.)
--
997237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lomiri-url-dispatcher
Version: 0.1.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/tools && /usr/bin/c++
> -I/usr/include/liblomiri-app-launch-0 -I/usr/include/glib-2.0
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/mirclient
> -I/usr/include/mircookie -I/usr/include/mircore -I/usr/include/libmount
> -I/usr/include/blkid -I/usr/include/gio-unix-2.0 -I/usr/include/json-glib-1.0
> -I/usr/include/libdbustest-1 -I/<>
> -I/<>/obj-x86_64-linux-gnu
> -I/<>/liblomiri-url-dispatcher -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wpedantic
> -Wextra -std=c++11 -fPIC -g -MD -MT
> tools/CMakeFiles/lomiri-url-dispatcher.dir/url-dispatcher.cpp.o -MF
> CMakeFiles/lomiri-url-dispatcher.dir/url-dispatcher.cpp.o.d -o
> CMakeFiles/lomiri-url-dispatcher.dir/url-dispatcher.cpp.o -c
> /<>/tools/url-dispatcher.cpp
> -- Looking for pthread_create in pthreads - not found
> -- Looking for pthread_create in pthread
> -- Looking for pthread_create in pthread - found
> -- Found Threads: TRUE
> -- Configuring done
> -- Generating done
> -- Build files have been written to:
> /<>/obj-x86_64-linux-gnu/tests/gmock
> cd /<>/obj-x86_64-linux-gnu/tests/gmock && /usr/bin/cmake -E
> touch
> /<>/obj-x86_64-linux-gnu/tests/GMock-prefix/src/GMock-stamp/GMock-configure
> /<>/tools/url-dispatcher.cpp: In lambda function:
> /<>/tools/url-dispatcher.cpp:35:55: warning: unused parameter
> ‘url’ [-Wunused-parameter]
>35 | lomiri_url_dispatch_send(argv[1], [](const gchar* url, gboolean
> success,
> | ~^~~
> In file included from /usr/include/glib-2.0/glib/glib-typeof.h:39,
> from /usr/include/glib-2.0/glib/gatomic.h:28,
> from /usr/include/glib-2.0/glib/gthread.h:32,
> from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
> from /usr/include/glib-2.0/glib.h:32,
> from /<>/service/overlay-tracker.h:21,
> from /<>/service/overlay-tracker.cpp:21:
> /usr/include/c++/11/type_traits:44:3: error: template with C linkage
>44 | template
> | ^~~~
> /<>/service/overlay-tracker.cpp:20:1: note: ‘extern "C"’ linkage
> started here
>20 | extern "C" {
> | ^~
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/lomiri-url-dispatcher_0.1.0-4_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: lomiri-url-dispatcher
Source-Version: 0.1.0-5
Done: Mike Gabriel
We believe that the bug you reported is fixed in the latest version of
lomiri-url-dispatcher, 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 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mike Gabriel (supplier of updated lomiri-url-dispatcher
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 08 Nov 2021 18:09:17 +0100
Source: lomiri-url-dispatcher
Architecture: source
Version: 0.1.0-5
Distribution:
Bug#984243: marked as done (mothur: ftbfs with GCC-11)
Your message dated Mon, 08 Nov 2021 17:38:08 +
with message-id
and subject line Bug#984243: fixed in mothur 1.46.1-1
has caused the Debian Bug report #984243,
regarding mothur: ftbfs with GCC-11
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.)
--
984243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mothur
Version: 1.44.3-2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
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-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.
The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/mothur_1.44.3-2_unstable_gcc11.log
The last lines of the build log are at the end of this report.
To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html
GCC 11 defaults to the GNU++17 standard. If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.
[...]
from source/datastructures/counttable.h:58,
from source/datastructures/optidata.hpp:15,
from source/datastructures/optimatrix.h:12,
from source/cluster.hpp:5,
from source/averagelinkage.cpp:5:
source/writer.h:19:34: error: expected ‘)’ before ‘<’ token
19 | OutputWriter (std::shared_ptr s) : sf(s) {}
| ~ ^
| )
source/writer.h:24:10: error: ‘shared_ptr’ in namespace ‘std’ does not name a
template type
24 | std::shared_ptr sf;
| ^~
source/writer.h:13:1: note: ‘std::shared_ptr’ is defined in header ‘’;
did you forget to ‘#include ’?
12 | #include "sharedwriter.hpp"
+++ |+#include
13 |
In file included from source/datastructures/sequence.hpp:22,
from source/datastructures/counttable.h:58,
from source/datastructures/optidata.hpp:15,
from source/datastructures/optimatrix.h:12,
from source/cluster.hpp:5,
from source/cluster.cpp:10:
source/writer.h:19:34: error: expected ‘)’ before ‘<’ token
19 | OutputWriter (std::shared_ptr s) : sf(s) {}
| ~ ^
| )
source/writer.h:24:10: error: ‘shared_ptr’ in namespace ‘std’ does not name a
template type
24 | std::shared_ptr sf;
| ^~
source/writer.h:13:1: note: ‘std::shared_ptr’ is defined in header ‘’;
did you forget to ‘#include ’?
12 | #include "sharedwriter.hpp"
+++ |+#include
13 |
source/writer.h: In member function ‘void OutputWriter::write(const string&)’:
source/writer.h:21:46: error: ‘sf’ was not declared in this scope
21 | void write (const string& dataToWrite) { sf->write(dataToWrite); }
| ^~
In file included from source/datastructures/sequence.hpp:22,
from source/datastructures/counttable.h:58,
from source/clusterclassic.h:9,
from source/clusterclassic.cpp:10:
source/writer.h:19:34: error: expected ‘)’ before ‘<’ token
19 | OutputWriter (std::shared_ptr s) : sf(s) {}
| ~ ^
| )
source/writer.h:24:10: error: ‘shared_ptr’ in namespace ‘std’ does not name a
template type
24 | std::shared_ptr sf;
| ^~
source/writer.h:13:1: note: ‘std::shared_ptr’ is defined in header ‘’;
did you forget to
Processed: severity of 929484 is important
Processing commands for cont...@bugs.debian.org: > severity 929484 important Bug #929484 [src:dmraid] Please drop dependency against libselinux and libsepol Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 929484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984020: codeblocks: diff for NMU version 20.03-3.1
Hi Adrian, Le 08/11/2021 à 11:55, Adrian Bunk a écrit : I've prepared an NMU for codeblocks (versioned as 20.03-3.1) and uploaded it to DELAYED/14. Thanks! Feel free to reschedule it to DELAYED/0 ;). Regards David OpenPGP_signature Description: OpenPGP digital signature
Processed: [bts-link] source package dnsdiag
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package dnsdiag > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #995015 (http://bugs.debian.org/995015) > # Bug title: dnsdiag: Error when running: DeprecationWarning > # * https://github.com/farrokhi/dnsdiag/issues/67 > # * remote status changed: (?) -> closed > # * closed upstream > tags 995015 + fixed-upstream Bug #995015 [dnsdiag] dnsdiag: Error when running: DeprecationWarning Bug #995016 [dnsdiag] dnsdiag: Error when running: DeprecationWarning Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. > usertags 995015 + status-closed There were no usertags set. Usertags are now: status-closed. > # remote status report for #995016 (http://bugs.debian.org/995016) > # Bug title: dnsdiag: Error when running: DeprecationWarning > # * https://github.com/farrokhi/dnsdiag/issues/67 > # * remote status changed: (?) -> closed > # * closed upstream > tags 995016 + fixed-upstream Bug #995016 [dnsdiag] dnsdiag: Error when running: DeprecationWarning Bug #995015 [dnsdiag] dnsdiag: Error when running: DeprecationWarning Ignoring request to alter tags of bug #995016 to the same tags previously set Ignoring request to alter tags of bug #995015 to the same tags previously set > usertags 995016 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 995015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995015 995016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Please switch libsemanage1-dev BD to libsemanage-dev
Processing commands for cont...@bugs.debian.org: > severity 998633 serious Bug #998633 [src:shadow] shadow: Please switch libsemanage1-dev BD to libsemanage-dev Severity set to 'serious' from 'important' > severity 998634 serious Bug #998634 [src:sssd] sssd: Please switch libsemanage1-dev BD to libsemanage-dev Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 998633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998633 998634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997237: marked as pending in lomiri-url-dispatcher
Control: tag -1 pending Hello, Bug #997237 in lomiri-url-dispatcher 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/ubports-team/lomiri-url-dispatcher/-/commit/375bf479b569f60f9fdea451459becc237bb2201 debian/patches: Add 0001_Fix-compile-error-with-new-glib-versions.patch. Fix FTBFS against latest GLib-2.0. Thanks to Luca Weiss. (Closes: #997237) (this message was generated automatically) -- Greetings https://bugs.debian.org/997237
Processed: Bug#997237 marked as pending in lomiri-url-dispatcher
Processing control commands: > tag -1 pending Bug #997237 [src:lomiri-url-dispatcher] lomiri-url-dispatcher: FTBFS: type_traits:44:3: error: template with C linkage Added tag(s) pending. -- 997237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997902: marked as done (llvm-toolchain-13: autopkgtest regression on amd64|arm64: debian/qualify-clang.sh: llvm manpage are missing (using llc as an example))
Your message dated Mon, 08 Nov 2021 16:49:33 + with message-id and subject line Bug#997902: fixed in llvm-toolchain-13 1:13.0.0-9 has caused the Debian Bug report #997902, regarding llvm-toolchain-13: autopkgtest regression on amd64|arm64: debian/qualify-clang.sh: llvm manpage are missing (using llc as an example) 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.) -- 997902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: llvm-toolchain-13 Version: 1:13.0.0-6 Severity: serious Justification: Release Team policy Tags: patch The autopkgtest that uses debian/qualify-clang.sh seems to be failing. I think this is a bug in debian/qualify-clang.sh rather than a bug in the actual packages: /usr/share/man/man1/llc-13.1.gz does exist in llvm-13_*.deb. The check that is failing is > # Test #995684 > if test /usr/share/man/man1/llc-$VERSION.1.gz; then > echo "llvm manpage are missing (using llc as an example)" > exit 1 > fi but I assume this should have been something more like: 8< # Test #995684 if ! test -f "/usr/share/man/man1/llc-$VERSION.1.gz"; then echo "llvm man pages are missing (using llc as an example)" exit 1 fi 8< I would suggest running the autopkgtests and making sure they pass locally on at least one architecture before uploading a new version to unstable. If llvm-toolchain-13 is too big to build locally, porterboxes and experimental are also useful routes to get things tested. smcv --- End Message --- --- Begin Message --- Source: llvm-toolchain-13 Source-Version: 1:13.0.0-9 Done: Sylvestre Ledru We believe that the bug you reported is fixed in the latest version of llvm-toolchain-13, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated llvm-toolchain-13 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 08 Nov 2021 14:09:25 +0100 Source: llvm-toolchain-13 Architecture: source Version: 1:13.0.0-9 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Sylvestre Ledru Closes: 997902 Changes: llvm-toolchain-13 (1:13.0.0-9) unstable; urgency=medium . * Upload to unstable (all green on exp) * Fix an autopkgtest test (Closes: #997902) Checksums-Sha1: f1fc86d3e6b2f136ef3fd8dd4e5d43bdeaf9930b 6612 llvm-toolchain-13_13.0.0-9.dsc f12d3069a07e0def50ba20dc4e163b2c9c9e052a 146296 llvm-toolchain-13_13.0.0-9.debian.tar.xz b0d5ca349c78a2c4628693d257ebd2d764ce038f 29065 llvm-toolchain-13_13.0.0-9_amd64.buildinfo Checksums-Sha256: 70e927449ff73cf9b44e1748dfb2584be6600d4b204682ddef89aead29e87cb6 6612 llvm-toolchain-13_13.0.0-9.dsc a9dcb2eda1f40f61ae1a14de8ce0a03bec2109040b3381453b9eb00266ab3fd7 146296 llvm-toolchain-13_13.0.0-9.debian.tar.xz d2e4cffab5490da748beaa4608b88b73c87f829251991b9c8919746e931e3990 29065 llvm-toolchain-13_13.0.0-9_amd64.buildinfo Files: 0d135a275c08edaa1c021f3896587d89 6612 devel optional llvm-toolchain-13_13.0.0-9.dsc 1ef758459897aab67f1967837388d24b 146296 devel optional llvm-toolchain-13_13.0.0-9.debian.tar.xz 0b03948e5abd8ac1f0b674adc2309e68 29065 devel optional llvm-toolchain-13_13.0.0-9_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmGJUK4ACgkQfmUo2nUv G+F2BRAAmTT0q6JMHhHh7UCqp2hRUMez2quK6yWY5dppyhsbG3Ns14JWol0Sz4PH HqIcHHi9vUe2xyIiv52ocddecpsSRkKOZSsoZ87DFje5haYFv1Cn/ns4EF36Hi7Q lTo7EBZ96MQOrGcUGp90fSTjLLmPtaE9vjrPlTkMzDsB7hhFlEy0T9whIBVW6KMR jts3azeS/L8UKkMEVMgrgrBws4WysvoTbxJgzqKKIoanCSJVsPx12WkLpH6TQ56Q ZobIXGZq7Bw4Gvjj6jSt0Srl43XcICmTnRSuF1hSy9ceQIot7frjHWYPwG5tCMfi IyERx1oP3eyGhKpWV4CeaDYDmGFR5mhY90jiwyQmaYZ6FXtRj16DFgOCSe/1cVEb Yzc8tZPm1RuyKEh6GM7AdlARALRdnXUxtc/+gA5uonYUkcFioPbidbreWwFJJCbI eWnKLl/bLjeIJozFPPlUYj9NE2SOLQHBw6LjiDLjQoCeohpHsd2T8ngCRrO5msEP rUKAeBkvuMLrplBNBnHKhiPTonMiINY5DJEAm0LvllSuLshbrtIrAMhm4LfYTICr j4KuJhmHBQ7ryaV+r5kuJOtxmXGzEJKm59CdIRLd03pJwgUWO4jwzKM2YusXz2i3 uj1FwhVsVz70pqlfiRn7NIi+Krs/GkpF3U1hVjsSJ/B4H9LucBE= =hdiz -END PGP SIGNATURE
Bug#997369: marked as done (ontospy: FTBFS: 'test -s debian/bash-completion' fails)
Your message dated Mon, 08 Nov 2021 16:50:16 + with message-id and subject line Bug#997369: fixed in ontospy 1.9.9.1~dfsg-1 has caused the Debian Bug report #997369, regarding ontospy: FTBFS: 'test -s debian/bash-completion' fails to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 997369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ontospy Version: 1.9.8.3~dfsg-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > PATH="/<>/debian/tmp/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" > PYTHONPATH="/<>/debian/tmp/usr/lib/python3.9/dist-packages" > prove debian/tests/*.t > debian/tests/ontospy-gendocs.t .. ok > debian/tests/ontospy-lib.t .. ok > debian/tests/ontospy-scan.t . ok > debian/tests/ontospy-ser.t .. ok > debian/tests/ontospy-shell.t ok > debian/tests/ontospy-utils.t ok > debian/tests/ontospy.t .. ok > All tests successful. > Files=7, Tests=88, 9 wallclock secs ( 0.04 usr 0.00 sys + 7.74 cusr 0.46 > csys = 8.24 CPU) > Result: PASS > PATH="/<>/debian/tmp/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" > PYTHONPATH="/<>/debian/tmp/usr/lib/python3.9/dist-packages" > _ONTOSPY_COMPLETE=source ontospy \ > > debian/bash-completion || true > test -s debian/bash-completion > make[1]: *** [debian/rules:27: execute_after_dh_auto_install] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/ontospy_1.9.8.3~dfsg-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: ontospy Source-Version: 1.9.9.1~dfsg-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of ontospy, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated ontospy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Nov 2021 23:40:04 +0100 Source: ontospy Architecture: source Version: 1.9.9.1~dfsg-1 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Closes: 997369 Changes: ontospy (1.9.9.1~dfsg-1) unstable; urgency=medium . [ upstream ] * new release(s) . [ Jonas Smedegaard ] * update copyright info: + stop strip stray log file when repackaging upstream source: no longer included upstream + update coverage + use Reference field (not License-Reference); tighten lintian overrides * declare compliance with Debian Policy 4.6.0 * relax to (build-)depend unversioned on python3-colorama python3-django python3-html5lib python3-pygments python3-pyparsing python3-rdflib python3-requests python3-django python3-pygments: required versions satisfied in all supported Debian releases * tighten to trust upstream testsuite during build (in addition to post-build testing) * drop obsolete patches * extend patch 2001 to cover badge in README.md file * tighten to trust upstream testsuite during build (in addition to post-build testing) * update post-build tests (cli tools now outputs to stderr) * update short descriptions to untie OWL from RDF * update shell completion commands; tighten build-dependency on python3-click closes: bug#997369, thanks to Lucas Nussbaum * update symlink paths to JavaScript libraries; stop (build-)depend on
Bug#998287: r-cran-pdftools: autopkgtest failure: nrow(fonts) not equal to 3
Hi Paul, On Mon, 1 Nov 2021 21:11:54 +0100 Paul Gevers wrote: Source: r-cran-pdftools Version: 3.0.1-1 X-Debbugs-CC: debian...@lists.debian.org I could reproduce this (relevant part below). *But*, it passes when I try run it locally with (i) "bash ./debian/tests/run-unit-tests" --> OK and also, inside a container with -- null (ii) "sudo autopkgtest -B ../*.deb -- null" --> Works perfect. It does not work when I try running it in a schroot, or an lxc container and gives errors similar to the one quoted below. I tried changing locales with several different permutations, but the result is same. Since this does not really look like a bug with this package, but rather something very specific to "autopkgtest" or "schroot" environment is triggering this, I need your inputs to tackle this. Would you have any idea as to what autopkgtest might do differently in a chroot? Or what is specific there to be causing this? I'd really appreciate any pointers. |── Failure (test-chinese.R:9:3): reading Chinese text ── |`text` does not match "風險因素". |Actual value: " T\+2\\n\\n\\n\\n 17,300,000\\n\\n\\n\\n299,900\\n\\n\\n\\n\\n 36\.8%\\n34\.9%\\n |4,300,000 6,900,000 7,100,000\\n300,000\\n\\n\\n 3\.7% 1\.5% 3\.4%0\.1%\\n\\n\\n\\n\\n 80%\\n 10% 80%\\n\\n\\n\\n\\n |– 31 –\\n" |Backtrace: |█ | 1. └─testthat::expect_match(text, "風險因素") test-chinese.R:9:2 | 2. └─testthat:::expect_match_(...) |── Failure (test-chinese.R:13:3): reading Chinese text ─ |nrow(fonts) not equal to 3. |1/1 mismatches |[1] 1 - 3 == -2 Thanks, Nilesh OpenPGP_signature Description: OpenPGP digital signature
Processed: codeblocks: diff for NMU version 20.03-3.1
Processing control commands: > tags 984020 + patch Bug #984020 [src:codeblocks] codeblocks: ftbfs with GCC-11 Added tag(s) patch. > tags 984020 + pending Bug #984020 [src:codeblocks] codeblocks: ftbfs with GCC-11 Added tag(s) pending. -- 984020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984020: codeblocks: diff for NMU version 20.03-3.1
Control: tags 984020 + patch Control: tags 984020 + pending Dear maintainer, I've prepared an NMU for codeblocks (versioned as 20.03-3.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru codeblocks-20.03/debian/changelog codeblocks-20.03/debian/changelog --- codeblocks-20.03/debian/changelog 2020-04-18 22:47:24.0 +0300 +++ codeblocks-20.03/debian/changelog 2021-11-08 15:51:13.0 +0200 @@ -1,3 +1,11 @@ +codeblocks (20.03-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Build with -std=gnu++14 to workaround FTBFS with gcc 11. +(Closes: #984020) + + -- Adrian Bunk Mon, 08 Nov 2021 15:51:13 +0200 + codeblocks (20.03-3) unstable; urgency=medium * Fix FTBFS on armel/armhf (Closes: #958085) diff -Nru codeblocks-20.03/debian/rules codeblocks-20.03/debian/rules --- codeblocks-20.03/debian/rules 2020-04-18 22:45:44.0 +0300 +++ codeblocks-20.03/debian/rules 2021-11-08 15:51:13.0 +0200 @@ -22,6 +22,8 @@ -DBUILD_DATE="\"\\\"`date -u -d @$(SOURCE_DATE_EPOCH) +%Y-%m-%d`\\\"\"" \ -DBUILD_TIME="\"\\\"`date -u -d @$(SOURCE_DATE_EPOCH) +%T`\\\"\"" +export DEB_CXXFLAGS_MAINT_APPEND += -std=gnu++14 + %: dh $@
Bug#984243: Help: mothur: ftbfs with GCC-11
Hi all, The problem can be fixed following these steps: 1. Revert the commit ff8928540e0d720b8a08ee4227c1bbadc2c1e733 (now, that is the last commit). 2. Apply this patch: >--- a/Makefile >+++ b/Makefile >@@ -118,8 +118,8 @@ endif ># > OBJECTS=$(patsubst %.cpp,%.o,$(wildcard $(addsuffix *.cpp,$(subdirs > OBJECTS+=$(patsubst %.c,%.o,$(wildcard $(addsuffix *.c,$(subdirs >-OBJECTS+=$(patsubst %.cpp,%.o,$(wildcard *.cpp)) >-OBJECTS+=$(patsubst %.c,%.o,$(wildcard *.c)) >+OBJECTS+=$(patsubst %.cpp,%.o,$(wildcard source/*.cpp)) >+OBJECTS+=$(patsubst %.c,%.o,$(wildcard source/*.c)) > > mothur : $(OBJECTS) uchime > $(CXX) $(LDFLAGS) $(TARGET_ARCH) -o $@ $(OBJECTS) $(LIBS) In fact, the ff8928540e0d720b8a08ee4227c1bbadc2c1e733 was applied toward a wrong Makefile, not the top one. Regards, Hamid On Mon, Nov 8, 2021 at 4:25 PM Andreas Tille wrote: > > Am Mon, Oct 25, 2021 at 09:16:30PM -0400 schrieb Aaron M. Ucko: > > Andreas Tille writes: > > > > > I'm wondering why the makefile stopped working just because a new compiler > > > version is used. :-( > > > > Along the way, you pulled in a new upstream version, whose makefile > > evidently wasn't quite right. > > I think I've found the reason for the failure: It is the overlong line: > > > g++ -Wl,-z,relro -Wl,-z,now -std=c++11 -pthread -Lsource/calculators/ > -Lsource/chimera/ -Lsource/classifier/ -Lsource/clearcut/ > -Lsource/commands/ -Lsource/communitytype/ -Lsource/datastructures/ > -Lsource/engines/ -Lsource/metastats/ -Lsource/read/ -Lsource/svm/ -o > mothur source/calculators/accuracy.o source/calculators/ace.o > source/calculators/bergerparker.o source/calculators/boneh.o > source/calculators/bootstrap.o source/calculators/bstick.o > source/calculators/calculator.o source/calculators/canberra.o > source/calculators/chao1.o source/calculators/coverage.o > source/calculators/diversityutils.o source/calculators/eachgapdist.o > source/calculators/eachgapignore.o source/calculators/efron.o > source/calculators/erarefaction.o source/calculators/f1score.o > source/calculators/fdr.o source/calculators/fn.o source/calculators/fp.o > source/calculators/fpfn.o source/calculators/geom.o > source/calculators/goodscoverage.o source/calculators/gower.o > source/calculators/hamming.o source/calculators/heip.o > source/calculators/hellinger.o source/calculators/igabundance.o > source/calculators/ignoregaps.o source/calculators/igrarefaction.o > source/calculators/invsimpson.o source/calculators/jackknife.o > source/calculators/kimura.o source/calculators/kmerdist.o > source/calculators/lnabundance.o source/calculators/lnrarefaction.o > source/calculators/lnshift.o source/calculators/logsd.o > source/calculators/lsabundance.o source/calculators/lsrarefaction.o > source/calculators/manhattan.o source/calculators/mcc.o > source/calculators/memchi2.o source/calculators/memchord.o > source/calculators/memeuclidean.o source/calculators/mempearson.o > source/calculators/metroig.o source/calculators/metrolognormal.o > source/calculators/metrologstudent.o source/calculators/metrosichel.o > source/calculators/npshannon.o source/calculators/npv.o > source/calculators/odum.o source/calculators/onegapdist.o > source/calculators/onegapignore.o source/calculators/parsimony.o > source/calculators/ppv.o source/calculators/prng.o source/calculators/qstat.o > source/calculators/sensitivity.o source/calculators/shannon.o > source/calculators/shannoneven.o source/calculators/shannonrange.o > source/calculators/sharedace.o source/calculators/sharedanderbergs.o > source/calculators/sharedbraycurtis.o source/calculators/sharedchao1.o > source/calculators/sharedjabund.o source/calculators/sharedjackknife.o > source/calculators/sharedjclass.o source/calculators/sharedjest.o > source/calculators/sharedjsd.o source/calculators/sharedkstest.o > source/calculators/sharedkulczynski.o > source/calculators/sharedkulczynskicody.o source/calculators/sharedlennon.o > source/calculators/sharedmarczewski.o source/calculators/sharedmorisitahorn.o > source/calculators/sharedochiai.o source/calculators/sharedrjsd.o > source/calculators/sharedsobs.o source/calculators/sharedsobscollectsummary.o > source/calculators/sharedsorabund.o source/calculators/sharedsorclass.o > source/calculators/sharedsorest.o source/calculators/sharedthetan.o > source/calculators/sharedthetayc.o source/calculators/shen.o > source/calculators/siabundance.o source/calculators/simpson.o sg++ > -Wl,-z,relro -Wl,-z,now -std=c++11 -pthread -Lsource/calculators/ > -Lsource/chimera/ -Lsource/classifier/ -Lsource/clearcut/ > -Lsource/commands/ -Lsource/communitytype/ -Lsource/datastructures/ > -Lsource/engines/ -Lsource/metastats/ -Lsource/read/ -Lsource/svm/ -o > mothur source/calculators/accuracy.o source/calculators/ace.o > source/calculators/bergerparker.o source/calculators/boneh.o > source/calculators/bootstrap.o
Processed: Bug#996238 marked as pending in ruby-hamster
Processing control commands: > tag -1 pending Bug #996238 [src:ruby-hamster] ruby-hamster: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: Added tag(s) pending. -- 996238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996238: marked as pending in ruby-hamster
Control: tag -1 pending Hello, Bug #996238 in ruby-hamster 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/ruby-team/ruby-hamster/-/commit/820b681654fad69da5dfaea23bcd09361e0441fd Add ruby-sorted-set to fix FTBFS * d/control (Build-Depends): Add ruby-sorted-set for Ruby 3 tests (closes: #996238). (this message was generated automatically) -- Greetings https://bugs.debian.org/996238
Processed: affects 998343
Processing commands for cont...@bugs.debian.org: > affects 998343 + src:pycuda Bug #998343 [python3-sphinx-copybutton] python3-sphinx-copybutton: clipboard.min.js is missing - causes new black upstream release to fail to build Added indication that 998343 affects src:pycuda > thanks Stopping processing here. Please contact me if you need assistance. -- 998343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: 2.9.1 builds
Processing commands for cont...@bugs.debian.org:
> tags 996121 fixed-upstream
Bug #996121 [src:ruby-acts-as-tree] ruby-acts-as-tree: FTBFS with ruby3.0:
ERROR: Test "ruby3.0" failed:
/usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/associations/builder/association.rb:51:in
`build_scope': undefined method `arity' for {:class_name=>"LevelMixin",
:primary_key=>"id", :foreign_key=>"parent_id", :counter_cache=>nil,
:touch=>false, :inverse_of=>:children, :optional=>true}:Hash (NoMethodError)
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
996121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: 0.8.0 builds
Processing commands for cont...@bugs.debian.org: > tags 996119 fixed-upstream Bug #996119 [src:ruby-activerecord-nulldb-adapter] ruby-activerecord-nulldb-adapter: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: Employee.create Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 996119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993093: icingaweb2-module-incubator: diff for NMU version 0.6.0-1.1
Dear maintainer, I've prepared an NMU for icingaweb2-module-incubator (versioned as 0.6.0-1.1) and uploaded it to DELAYED/15. Please feel free to tell me if I should cancel it. This is also needed for testing migration of icingaweb2-module-director 1.8.1-1. cu Adrian diff -Nru icingaweb2-module-incubator-0.6.0/debian/changelog icingaweb2-module-incubator-0.6.0/debian/changelog --- icingaweb2-module-incubator-0.6.0/debian/changelog 2021-01-06 11:34:26.0 +0200 +++ icingaweb2-module-incubator-0.6.0/debian/changelog 2021-11-08 16:03:21.0 +0200 @@ -1,3 +1,10 @@ +icingaweb2-module-incubator (0.6.0-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Source-only upload. + + -- Adrian Bunk Mon, 08 Nov 2021 16:03:21 +0200 + icingaweb2-module-incubator (0.6.0-1) unstable; urgency=medium * Initial release (Closes: #970538)
Processed: bug 996077 is forwarded to https://github.com/pulb/mailnag-gnome-shell/issues/73
Processing commands for cont...@bugs.debian.org: > forwarded 996077 https://github.com/pulb/mailnag-gnome-shell/issues/73 Bug #996077 [gnome-shell-mailnag] gnome-shell-mailnag: does not declare compatibility with GNOME Shell 41 Set Bug forwarded-to-address to 'https://github.com/pulb/mailnag-gnome-shell/issues/73'. > thanks Stopping processing here. Please contact me if you need assistance. -- 996077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996048: [Pkg-openssl-devel] Bug#996048: postfix-mta-sts-resolver: autopkgtest doesn't handle new version of ca-certificates nicely: rehash: warning: skipping ca-certificates.crt, it does not conta
On Tue, Oct 19, 2021 at 09:13:56AM +0200, Julien Cristau wrote: > On Mon, Oct 18, 2021 at 11:05:14PM +0200, Kurt Roeckx wrote: > > On Mon, Oct 18, 2021 at 10:40:59PM +0200, Julien Cristau wrote: > > > On Mon, Oct 18, 2021 at 02:50:50PM +0200, Benjamin Hof wrote: > > > > Hi, > > > > > > > > I think the following change might be the relevant one: > > > > > > > > --- a/update-ca-certificates > > > > +++ b/update-ca-certificates > > > > @@ -164,8 +164,6 @@ > > > >done > > > > fi > > > > > > > > -rm -f "$CERTBUNDLE" > > > > - > > > > ADDED_CNT=$(wc -l < "$ADDED") > > > > REMOVED_CNT=$(wc -l < "$REMOVED") > > > > > > > > It triggers this stderr output during openssl rehash (l. 184): > > > > > > > > rehash: warning: skipping ca-certificates.crt,it does not contain > > > > exactly one certificate or CRL > > > > > > > Ah, that makes sense. Annoying... > > > > > > Kurt/Sebastian, do you think there's a chance openssl rehash could grow > > > some sort of ignore option so update-ca-certificates could ask it to > > > skip ca-certificates.crt, to avoid spitting out a warning for it? > > > > As in rehash all files in that directory, excluding a file? I > > guess that's an option. I guess it's not an option to move the > > file to a different location. > > > Exactly. /etc/ssl/certs/ca-certificates.crt is the package's main > "interface" so I suspect it'd be quite painful to move. Likewise moving > the certs and hash symlinks themselves would break packages/scripts > looking them up that way. > > The other option for me would be to revert the fix for bug #920348. In any case, there is nothing happening here specific to postfix-mta-sts-resolver, the same problem would happen with any other package that does not permit stderr output in the autopkgtest when upgrading ca-certificates is tested. The failing part of the autopkgtest is a testing->unstable upgrade of ca-certificates. Any objections to reassigning this to ca-certificates? > Thanks, > Julien cu Adrian
Bug#998591: marked as done (bdebstrap: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13)
Your message dated Mon, 08 Nov 2021 13:48:28 +
with message-id
and subject line Bug#998591: fixed in bdebstrap 0.3.0-1
has caused the Debian Bug report #998591,
regarding bdebstrap: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.9 returned exit code 13
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.)
--
998591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bdebstrap
Version: 0.2.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package bdebstrap
> dpkg-buildpackage: info: source version 0.2.0-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Benjamin Drung
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --buildsystem pybuild --with python3
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> running clean
> removing '/<>/.pybuild/cpython3_3.9/build' (and everything under
> it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
> dpkg-source -b .
> dpkg-source: warning: cannot import key in
> bdebstrap-0.2.0/debian/upstream/signing-key.asc since GnuPG is not installed
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building bdebstrap using existing
> ./bdebstrap_0.2.0.orig.tar.xz
> dpkg-source: info: building bdebstrap using existing
> ./bdebstrap_0.2.0.orig.tar.xz.asc
> gpgv: Signature made Tue Jun 8 13:30:13 2021 UTC
> gpgv:using RSA key E7FAB70B3950275E6DA30975DD8CD5A5DE8C7E7A
> gpgv: Can't check signature: No public key
> dpkg-source: warning: failed to verify signature on
> ./bdebstrap_0.2.0.orig.tar.xz.asc
> dpkg-source: info: building bdebstrap in bdebstrap_0.2.0-1.debian.tar.xz
> dpkg-source: info: building bdebstrap in bdebstrap_0.2.0-1.dsc
> debian/rules binary
> dh binary --buildsystem pybuild --with python3
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build
> running build
> running doc
> running command: pandoc -s -t man bdebstrap.1.md -o bdebstrap.1
> running build_scripts
> creating build
> creating build/scripts-3.9
> copying and adjusting bdebstrap -> build/scripts-3.9
> changing mode of build/scripts-3.9/bdebstrap from 644 to 755
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9/build;
> python3.9 -m unittest discover -v -s /<>
> test_black (tests.test_black.BlackTestCase)
> Test: Run black code formatter on Python source code. ... Running following
> command:
> black --check --diff -l 99 /<>/bdebstrap tests
> /<>/setup.py
> ok
> test_debug (tests.test_config.TestArguments)
> Test --debug argument parsing. ... ok
> test_empty_args (tests.test_config.TestArguments)
> Test setting arguments to empty strings. ...
> /usr/lib/python3.9/unittest/case.py:1132: DeprecationWarning:
> assertDictContainsSubset is deprecated
> warnings.warn('assertDictContainsSubset is deprecated',
> ok
> test_malformed_env (tests.test_config.TestArguments)
> Test malformed --env parameter (missing equal sign). ... usage: python3.9 -m
> unittest [-h] [-c CONFIG] [-n NAME] [-e ENV] [-s]
> [-b OUTPUT_BASE_DIR] [-o OUTPUT] [-q] [-v]
> [--debug] [-f] [-t TMPDIR]
> [--variant
> {extract,custom,essential,apt,required,minbase,buildd,important,debootstrap,-,standard}]
> [--mode
> {auto,sudo,root,unshare,fakeroot,fakechroot,proot,chrootless}]
> [--aptopt APTOPT] [--keyring KEYRING]
> [--dpkgopt DPKGOPT] [--hostname HOSTNAME]
> [--install-recommends] [--packages PACKAGES]
> [--components COMPONENTS]
>
Bug#998241: marked as done (cufflinks: FTBFS: error: AM_INIT_AUTOMAKE expanded multiple times)
Your message dated Mon, 08 Nov 2021 13:48:35 + with message-id and subject line Bug#998241: fixed in cufflinks 2.2.1+dfsg.1-9 has caused the Debian Bug report #998241, regarding cufflinks: FTBFS: error: AM_INIT_AUTOMAKE expanded multiple times 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.) -- 998241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cufflinks Version: 2.2.1+dfsg.1-8 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) Hi, cufflinks recently started to FTBFS: dh_autoreconf sh: 1: svnversion: not found configure.ac:113: error: AM_INIT_AUTOMAKE expanded multiple times /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... configure.ac:16: the top level /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... configure.ac:113: the top level autom4te: error: /usr/bin/m4 failed with exit status: 1 aclocal: error: /usr/bin/autom4te failed with exit status: 1 autoreconf: error: aclocal failed with exit status: 1 dh_autoreconf: error: autoreconf -f -i returned exit code 1 make: *** [debian/rules:10: binary] Error 25 Andreas cufflinks_2.2.1+dfsg.1-8.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: cufflinks Source-Version: 2.2.1+dfsg.1-9 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of cufflinks, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated cufflinks package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Nov 2021 14:18:10 +0100 Source: cufflinks Architecture: source Version: 2.2.1+dfsg.1-9 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 998241 Changes: cufflinks (2.2.1+dfsg.1-9) unstable; urgency=medium . * Fix autoconf issue Closes: #998241 * Enable build using gcc-11 by forcing -std=c++14 * Remove redundant debian/gbp.conf * Standards-Version: 4.6.0 (routine-update) * cme fix dpkg-control Checksums-Sha1: 67556824c88ade082186c1b2ce54cd06c13ee579 2252 cufflinks_2.2.1+dfsg.1-9.dsc c86d3fef5574bdc19fe134da447e091dfd55d01b 15648 cufflinks_2.2.1+dfsg.1-9.debian.tar.xz a7924df63610713dca95f6c0bbbd9d81fd5e9e07 7514 cufflinks_2.2.1+dfsg.1-9_amd64.buildinfo Checksums-Sha256: e0a8d91e589976e8cb56deb7c97891e37e3f461ae3149a50f941322e62435456 2252 cufflinks_2.2.1+dfsg.1-9.dsc 6733f5f861fed212fc8d8ca0634fb7c9724ee7cd8b4085d2bd8700aca8d6bfe2 15648 cufflinks_2.2.1+dfsg.1-9.debian.tar.xz 9059d6f98dad37124189eb189b2e6c46025a35d783bbef25e97b7815ca5bdea6 7514 cufflinks_2.2.1+dfsg.1-9_amd64.buildinfo Files: bfc0de98c75d1c1abe1f9f0d5cb26759 2252 non-free/science optional cufflinks_2.2.1+dfsg.1-9.dsc 9e0794b6bfb58f7c33dfbb3a78e6ea4c 15648 non-free/science optional cufflinks_2.2.1+dfsg.1-9.debian.tar.xz fba6f828925a5d9cfc514879a43dea79 7514 non-free/science optional cufflinks_2.2.1+dfsg.1-9_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmGJJYERHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtEGsQ//T7H9XDWazbR87pbV6/OfcbqGK9YippRj azMB9NXJuzDRaHye2Sti3jH1rZiPibLIF1OUD3lNpeUjLGLIKhzgOIzxtc70kPSI GKEFKaQ7mtLiqpvRESbPqqLUZlsQTlG7o39NPrltHV0QXGerj6HFuWV/BW/1bJ8D sw5Bc7x8B6kgHaDYrerGLbofT6A1GEfXwSPNIzo8jP6x0kXsHwRhScFOkjR8Tg2V hMbEED3xMNuuW7DRKflmAtnCnGCuh24mKL9fyNq9T49jpM70rH+bXbdRTZeFR5Ve aMOnVwSBkdeoGWKS8lbcS6rd+2atH4Hv4MwzcMuOEe1YbNYt05WOgIDciMazpyq4 SqIypsbm9YbPJEdsGkaH6fBQY/bJPcnHBkjI++XRK+JrWJohjwdgs+awblwd4v/H Jb1d4glndpOLhT264uVqpubJcjt2+ldEDR8bbnk4pxNX57ZoKPK4F43wKInHQY2n WYtms6msO2AeoDsPWFiyAn5gj0og1GTYI4tUQ5JvkMeFiWN2W6KKu1zPapKmGx3z SwN5Xu6InHrp7Z0pGWOzRML51nQQDoDURixN2hP6Ljiuarrdy4Dl2o1psfN4Y75/ I0AdYdEjGCYTmB/Ecw6HqGziggs1OIGpMWJX/wHw5HEEs8szUrVuSR7waIcRz9Se RXJtupnfTuQ= =cUx1 -END PGP SIGNATURE End Message ---
Bug#995838: [htcondor-debian] Bug#995838: Should condor be removed?
I have a build of the recent 9.0.7 release. I want to run it through our integration tests before uploading later this week. ...Tim -- Tim Theisen (he, him, his) Release Manager HTCondor & Open Science Grid Center for High Throughput Computing Department of Computer Sciences University of Wisconsin - Madison 4261 Computer Sciences and Statistics 1210 W Dayton St Madison, WI 53706-1685 +1 608 265 5736 From: Tim Theisen Sent: Friday, October 29, 2021 8:36 AM To: Moritz Muehlenhoff ; 995...@bugs.debian.org <995...@bugs.debian.org> Subject: Re: [htcondor-debian] Bug#995838: Should condor be removed? I plan to upload a new version this weekend. -- Tim Theisen (he, him, his) Release Manager HTCondor & Open Science Grid Center for High Throughput Computing Department of Computer Sciences University of Wisconsin - Madison 4261 Computer Sciences and Statistics 1210 W Dayton St Madison, WI 53706-1685 +1 608 265 5736 From: htcondor-debian on behalf of Moritz Muehlenhoff Sent: Wednesday, October 6, 2021 12:01 PM To: Debian Bug Tracking System Subject: [htcondor-debian] Bug#995838: Should condor be removed? Source: condor Severity: serious condor came up as a candidate for removal from Debian: - Last upload was in 2018 - Three RC bugs, including various toolchain issues (GCC, Python 2) - Open security issues If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz ___ htcondor-debian mailing list htcondor-deb...@cs.wisc.edu https://lists.cs.wisc.edu/mailman/listinfo/htcondor-debian
Bug#984063: Please lets coordinate itk4/itk5 issues (Was: Bug#984063)
On Monday, November 8, 2021 1:09:43 A.M. CST Andreas Tille wrote: > Hi, > > this mail from Jose > > Am Sat, Nov 06, 2021 at 01:33:29AM +0100 schrieb Jose Luis Rivero: > > Hello! Gazebo maintainer here, affected by this RC bug. Looking into > > upstream repository there is a potential commit that can be used to patch > > this problem until new versions land in Debian: > > > > https://github.com/InsightSoftwareConsortium/ITK/commit/840f22feb351739359 > > a8fdb55304124823a3a8c9 Are you saying this will allow ITKv4 to be built with current gcc? At present, ITK is about to be removed from testing tomorrow because it won't build. > caused me having a look into the Git repository of insighttoolkit4[1]. > It is missing the NMU 4.13.3withdata-dfsg1-4.1 by Andreas Beckmann and > there are now the first commits done by Steve for insighttoolkit5 > version 5.2.1 which was ITPed by Ghislain[2]. Yep, I've already uploaded ITK 5 to Debian. https://ftp-master.debian.org/new/insighttoolkit5_5.2.1-1.html > I think we need to discuss whether > > 1. We want to simply replace insighttoolkit4 (which makes the > usage of the existing repository[1] sensible - but please inject > the NMU changes at least in d/changelog Yes. This is what I've communicated already 2-3 times on the list -- going back a year -- and in Ghislain's ITP. https://lists.debian.org/debian-med/2020/11/msg00212.html https://lists.debian.org/debian-med/2021/10/msg00149.html https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995829#10 > 2. We should start ITK5 in a new repository and maintain both > versions at least for some time in parallel until all packages > that currently use ITK4 are migrated. If we can get ITK4 to build with current compilers, my suggestion would be to make a v4 branch in the current repository. On the other hand, it's kind of 11th hour here. I'm much more focused on replacing v4 with v5 -- which, to be fair is already more than two years old. ITK v4 is no longer supported upstream. > In any case people who are interested in ITK should coordinate their > work and talk to each other which I'd like to kindly invite you to > do here on the Debian Med mailing list (any other channel is fine for > sure). Yes, I've always used debian-med for communications. Additional hands are always welcomed. -Steve signature.asc Description: This is a digitally signed message part.
Bug#998126: marked as done (pipewire-pulse-dbgsym: dbgsym files overlap between packages)
Your message dated Mon, 08 Nov 2021 13:19:27 + with message-id and subject line Bug#998126: fixed in pipewire 0.3.39-4 has caused the Debian Bug report #998126, regarding pipewire-pulse-dbgsym: dbgsym files overlap between packages 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.) -- 998126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pipewire-pulse-dbgsym Version: 0.3.39-3 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Selecting previously unselected package libpipewire-0.3-0-dbgsym:i386. (Reading database ... 127295 files and directories currently installed.) Preparing to unpack .../libpipewire-0.3-0-dbgsym_0.3.39-3_i386.deb ... Unpacking libpipewire-0.3-0-dbgsym:i386 (0.3.39-3) ... Selecting previously unselected package pipewire-bin-dbgsym. Preparing to unpack .../pipewire-bin-dbgsym_0.3.39-3_i386.deb ... Unpacking pipewire-bin-dbgsym (0.3.39-3) ... Selecting previously unselected package pipewire-pulse-dbgsym. Preparing to unpack .../pipewire-pulse-dbgsym_0.3.39-3_i386.deb ... Unpacking pipewire-pulse-dbgsym (0.3.39-3) ... dpkg: error processing archive /var/cache/apt/archives/pipewire-pulse-dbgsym_0.3.39-3_i386.deb (--unpack): trying to overwrite '/usr/lib/debug/.build-id/cd/853193bbd003d08fa699c60b1be36cccb92034.debug', which is also in package pipewire-bin-dbgsym 0.3.39-3 Errors were encountered while processing: /var/cache/apt/archives/pipewire-pulse-dbgsym_0.3.39-3_i386.deb needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) - -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'stable-security'), (500, 'testing') Architecture: i386 (i586) Kernel: Linux 5.14.0-2-686 (SMP w/1 CPU thread) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pipewire-pulse-dbgsym depends on: ii pipewire-pulse 0.3.39-3 pipewire-pulse-dbgsym recommends no packages. pipewire-pulse-dbgsym suggests no packages. -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmF9l5UACgkQrh+Cd8S0 17YhSA/9HcJ3tuhDmDyD/OAv1Qf0RYY1aA4pyLO5AiD/yFPL4JI1Oflx5wRi7DRE HIf4hDzv7m49A8fQ8kBCvKISfV8y+2BRulcwlYGeLBpHbb+d0F/BAanpPlnIJxA7 kXPDCjqISsOCOIuj5B9Ndx1rvK4vuFFoZtlDORQZ/pnxMfpkFEbNCteOAD9HQlq5 3if8rSlekcvtRGFC8SWI91wcRun2uVp9VE5masuWovGsvtIJgzLCvfd68keswk4J o179kFZRNEoTDuFXkSdcnHHXLHiE70IwFEAimKnTQD+ZvNCTAmnyV6AYpZC51vrH d1/pCSrdC2g5SMsXfLMyia0yEU6rZHuA0DeduApEvBStSFSh8++5yCzCFdrIZOJj vV6vLWCGV/yLRWVNOlUFhLWHEdwbj/dCJRhNjDPm/cjyU8pi7UuxqWPSDtMk1Zea DTrqJKywBjRmsA/5m54G+JyhEgUG/6yQnAbP+0ORpU2wzbaam/hItmXArdjOKasX bFNta1k47Fdru6JD76904n5wCFv/iqHuR7OdP1e/2cWq2bIiac3gBUrq1qPz6nxS jYmwxOvlRIXTh6wJ6IuoQgOp2Tq3uoUk4C6gWqTQwHQrM00Ij6Xmew+IS6imbKF0 3WPy/YR3JQRc8krTdL5HJPweuVQJbQchp7A3JdtWDBXIbdRpdMY= =0lWY -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: pipewire Source-Version: 0.3.39-4 Done: Dylan Aïssi We believe that the bug you reported is fixed in the latest version of pipewire, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dylan Aïssi (supplier of updated pipewire package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Nov 2021 13:29:23 +0100 Source: pipewire Architecture: source Version: 0.3.39-4 Distribution: unstable Urgency: medium Maintainer: Utopia Maintenance Team Changed-By: Dylan Aïssi Closes: 982853 998126 998129 998130 998167 998218 Changes: pipewire (0.3.39-4) unstable; urgency=medium . * Team upload. * Update d/watch to point to gitlab.freedesktop.org/pipewire instead of a mirror. * Add an upstream patch to only run SSE when supported (Closes: #998129, #998130) * Build zeroconf modules (Closes: #998218) - Add libavahi-client-dev in Build-Deps * Add patch
Bug#984243: Help: mothur: ftbfs with GCC-11
Andreas Tille writes: > which has an incomplete number of arguments that is interrupted > by '/usr/bin/ld') That looks like it might simply be an artifact of different buffering policies for standard output and standard error; I expect you'll find the remainder of the command line later on. > Any idea how to specify the number of object files more sensibly > to not explode the command line arguments too much? You (or upstream) could consider using internal static libraries. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#998833: mysql-workbench: FTBFS (error: '' may be used uninitialized [-Werror=maybe-uninitialized])
Control: tags -1 patch On 11/8/21 12:31, Bas Couwenberg wrote: Consider adding -Wno-error=maybe-uninitialized to CPPFLAGS in d/rules. The attached patch does so and resolves the issue. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1diff -Nru mysql-workbench-8.0.26+dfsg/debian/rules mysql-workbench-8.0.26+dfsg/debian/rules --- mysql-workbench-8.0.26+dfsg/debian/rules2021-02-11 02:18:05.0 +0100 +++ mysql-workbench-8.0.26+dfsg/debian/rules2021-11-08 09:51:39.0 +0100 @@ -9,7 +9,7 @@ ## "bindnow" causes run-time errors: #export DEB_BUILD_MAINT_OPTIONS=hardening=+bindnow -export DEB_CPPFLAGS_MAINT_APPEND= -Wno-error=deprecated-declarations +export DEB_CPPFLAGS_MAINT_APPEND= -Wno-error=deprecated-declarations -Wno-error=maybe-uninitialized # -Wno-error=deprecated-copy -Wno-error=format-overflow= # -std=c++11
Bug#998838: h5py: FTBFS on armhf
Source: h5py Version: 3.3.0-4 Severity: serious Tags: ftbfs Hi Maintainer As can be seen on reproducible builds [1], h5py FTBFS on armhf with the following error: build/h5py/_debian_h5py_serial/tests/test_dtype.py::TestVlen::test_compound_vlen_bool Fatal Python error: Bus error The cause is most likely an alignment error, which is exposed when running armhf on an arm64 kernel. There are often failures on the official buildds as well [2], depending on which host the build lands. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/h5py.html [2] https://buildd.debian.org/status/logs.php?pkg=h5py=armhf
Processed: Re: mysql-workbench: FTBFS (error: '' may be used uninitialized [-Werror=maybe-uninitialized])
Processing control commands: > tags -1 patch Bug #998833 [src:mysql-workbench] mysql-workbench: FTBFS (error: '' may be used uninitialized [-Werror=maybe-uninitialized]) Added tag(s) patch. -- 998833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996569: getmail6 naming issues
Sudip Mukherjee wrote: > > iiuc, getmail6 is not a "hostile fork". It is; I could explain it, but I already have. Quoting from the getmail documentation: Why do I say it's a "hostile" fork? Because I have communicated with the maintainer and indicated I would be thrilled to accept their changes bringing Python 3 compatibility, as long as they were in reviewable condition, so that I could be sure I wasn't introducing bugs into getmail when I merged their changes. [...] That maintainer has shown precisely zero interest in submitting his changes for me to merge into getmail; he literally ignores every question/request I have made on the subject. > getmail6 is a Python3 based fork which all the distros had to package > because you have declined to support Python3. Please do not put words into my mouth. I have never - not one single time - said anything to suggest I would, will, or do refuse to support Python 3. In fact, I have said exactly the opposite countless times. In case there is any doubt: there will be a Python 3 version of getmail. > Roland has offered to send you ( I think already sent you) patches. That would be another misunderstanding, then. He has never sent me any patch, much less anything reviewable. All I want is a simple, self-contained series of patches that change things in a way that is reviewable - you know, the standard way to submit patches, like the Linux kernel workflow and countless others. A single diff that just runs getmail through the 2to3 tool and then hacks on fixes until it runs will touch virtually every line in the code. That would be completely unreviewable, and nobody would expect that to be a workable way of submitting changes - but that's immaterial, as he hasn't even done that. > If I rename the package then I will need to add another transitional > package linking getmail6 with the new package which will not do > anything to help your problem. On the contrary -- it will help me *in future*. Please do rename the package and executable. > Renaming the executable is not possible as that will break lots of > user's scripts. Just have apt-listchanges tell people to change their scripts or crontabs from "getmail" to "wonderfulmailpuller" or whatever. I see these sorts of announcements regularly when I upgrade Debian packages, and particularly when updating a major version. You are removing getmail and installing a different package - you do this sort of thing all the time. It's a trivial fix, and I would argue it's *less* disruptive to users, because then at least people will be able to find the correct place to get support, rather than searching "getmail" and finding nothing related to their problem at all (because the bug isn't in getmail, and whereupon they then contact me). > And if the executables need to be renamed then that needs to be done from > upstream so that it is consistent in all other distros and pypi. Please > discuss that with Roland, the getmail6 upstream maintainer. As I have said, he obstinately refuses any name change, claiming equal rights to the name I have built up for 23 years. I'm really disappointed that Debian - or this package maintainer - doesn't give a damn about doing the right, ethical thing here. Charles -- -- Charles Cazabon Software, consulting, and services available at http://pyropus.ca/ --
Bug#984243: Help: mothur: ftbfs with GCC-11
Am Mon, Oct 25, 2021 at 09:16:30PM -0400 schrieb Aaron M. Ucko: > Andreas Tille writes: > > > I'm wondering why the makefile stopped working just because a new compiler > > version is used. :-( > > Along the way, you pulled in a new upstream version, whose makefile > evidently wasn't quite right. I think I've found the reason for the failure: It is the overlong line: g++ -Wl,-z,relro -Wl,-z,now -std=c++11 -pthread -Lsource/calculators/ -Lsource/chimera/ -Lsource/classifier/ -Lsource/clearcut/ -Lsource/commands/ -Lsource/communitytype/ -Lsource/datastructures/ -Lsource/engines/ -Lsource/metastats/ -Lsource/read/ -Lsource/svm/ -o mothur source/calculators/accuracy.o source/calculators/ace.o source/calculators/bergerparker.o source/calculators/boneh.o source/calculators/bootstrap.o source/calculators/bstick.o source/calculators/calculator.o source/calculators/canberra.o source/calculators/chao1.o source/calculators/coverage.o source/calculators/diversityutils.o source/calculators/eachgapdist.o source/calculators/eachgapignore.o source/calculators/efron.o source/calculators/erarefaction.o source/calculators/f1score.o source/calculators/fdr.o source/calculators/fn.o source/calculators/fp.o source/calculators/fpfn.o source/calculators/geom.o source/calculators/goodscoverage.o source/calculators/gower.o source/calculators/hamming.o source/calculators/heip.o source/calculators/hellinger.o source/calculators/igabundance.o source/calculators/ignoregaps.o source/calculators/igrarefaction.o source/calculators/invsimpson.o source/calculators/jackknife.o source/calculators/kimura.o source/calculators/kmerdist.o source/calculators/lnabundance.o source/calculators/lnrarefaction.o source/calculators/lnshift.o source/calculators/logsd.o source/calculators/lsabundance.o source/calculators/lsrarefaction.o source/calculators/manhattan.o source/calculators/mcc.o source/calculators/memchi2.o source/calculators/memchord.o source/calculators/memeuclidean.o source/calculators/mempearson.o source/calculators/metroig.o source/calculators/metrolognormal.o source/calculators/metrologstudent.o source/calculators/metrosichel.o source/calculators/npshannon.o source/calculators/npv.o source/calculators/odum.o source/calculators/onegapdist.o source/calculators/onegapignore.o source/calculators/parsimony.o source/calculators/ppv.o source/calculators/prng.o source/calculators/qstat.o source/calculators/sensitivity.o source/calculators/shannon.o source/calculators/shannoneven.o source/calculators/shannonrange.o source/calculators/sharedace.o source/calculators/sharedanderbergs.o source/calculators/sharedbraycurtis.o source/calculators/sharedchao1.o source/calculators/sharedjabund.o source/calculators/sharedjackknife.o source/calculators/sharedjclass.o source/calculators/sharedjest.o source/calculators/sharedjsd.o source/calculators/sharedkstest.o source/calculators/sharedkulczynski.o source/calculators/sharedkulczynskicody.o source/calculators/sharedlennon.o source/calculators/sharedmarczewski.o source/calculators/sharedmorisitahorn.o source/calculators/sharedochiai.o source/calculators/sharedrjsd.o source/calculators/sharedsobs.o source/calculators/sharedsobscollectsummary.o source/calculators/sharedsorabund.o source/calculators/sharedsorclass.o source/calculators/sharedsorest.o source/calculators/sharedthetan.o source/calculators/sharedthetayc.o source/calculators/shen.o source/calculators/siabundance.o source/calculators/simpson.o sg++ -Wl,-z,relro -Wl,-z,now -std=c++11 -pthread -Lsource/calculators/ -Lsource/chimera/ -Lsource/classifier/ -Lsource/clearcut/ -Lsource/commands/ -Lsource/communitytype/ -Lsource/datastructures/ -Lsource/engines/ -Lsource/metastats/ -Lsource/read/ -Lsource/svm/ -o mothur source/calculators/accuracy.o source/calculators/ace.o source/calculators/bergerparker.o source/calculators/boneh.o source/calculators/bootstrap.o source/calculators/bstick.o source/calculators/calculator.o source/calculators/canberra.o source/calculators/chao1.o source/calculators/coverage.o source/calculators/diversityutils.o source/calculators/eachgapdist.o source/calculators/eachgapignore.o source/calculators/efron.o source/calculators/erarefaction.o source/calculators/f1score.o source/calculators/fdr.o source/calculators/fn.o source/calculators/fp.o source/calculators/fpfn.o source/calculators/geom.o source/calculators/goodscoverage.o source/calculators/gower.o source/calculators/hamming.o source/calculators/heip.o source/calculators/hellinger.o source/calculators/igabundance.o source/calculators/ignoregaps.o source/calculators/igrarefaction.o source/calculators/invsimpson.o source/calculators/jackknife.o source/calculators/kimura.o source/calculators/kmerdist.o source/calculators/lnabundance.o source/calculators/lnrarefaction.o source/calculators/lnshift.o source/calculators/logsd.o source/calculators/lsabundance.o
Bug#998317: PostgreSQL 14 transition
Control: tag -1 pending Re: To Debian Bug Tracking System > Depends: postgresql-pgsphere, postgresql-q3c > > Alternatively, switch it to postgresql-14-pgsphere, postgresql-14-q3c > > (pgsphere itself still has problems with PG14 to be resolved, but > moving to the version-less dependency would already work now.) I uploaded an NMU implementing this to delayed/2; the diff is at https://salsa.debian.org/debian-astro-team/gavodachs/-/merge_requests/1 Christoph
Processed: Re: Bug#998317: PostgreSQL 14 transition
Processing control commands: > tag -1 pending Bug #998317 [gavodachs2-server] PostgreSQL 14 transition Added tag(s) pending. -- 998317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998108: Rebuild w/ new toolchain
On 08/11/2021 12:21, Jakob Haufe wrote: On Mon, 8 Nov 2021 10:25:24 +0100 Matthias Urlichs wrote: Looks like the problem is a toolchain matter and requires a rebuild with Rust 1.56. https://bugzilla.opensuse.org/show_bug.cgi?id=1192067 According to the build log, 94.0-1 has been built with 1.56. I read that bug as saying that 1.56 does not have any changes compared to 1.55 that are likely to change anything. They talk about 1.55 requiring llvm12, not llvm13. As far as I understand their fix was to go back to rust 1.55 with llvm12. When I look at the dependencies of firefox, it does depend on rust 1.56, which in turn was built with llvm13, so that's fine. However firefox also depends on libgl1-mesa-dri and mesa-va-drivers, which depend on llvm12. Maybe this discrepancy is the culprit? OpenPGP_signature Description: OpenPGP digital signature
Bug#996569: getmail6 naming issues
On Sun, Nov 7, 2021 at 11:39 PM Charles Cazabon wrote: > > Sudip Mukherjee wrote: > > > > So, my preference is: > > 1. rename the package and executable. As I have pointed out, this is the > normal, polite, accepted best practice when forking a project. The fact that > Roland claims to have "as much right to the getmail name" as I, the author, > do, just means that Debian should rename their package without waiting for > Roland to do the right thing. As I said, Debian is supposed to be about doing > what is ethical - so why do you object to renaming a hostile fork of an > actively-developed project which is namesquatting on the original project > name? iiuc, getmail6 is not a "hostile fork". getmail6 is a Python3 based fork which all the distros had to package because you have declined to support Python3. Roland has offered to send you ( I think already sent you) patches. There are many other projects whose python3 fork is now coexisting with the original project and the maintainers have realised the need to support the python3 fork. If I rename the package then I will need to add another transitional package linking getmail6 with the new package which will not do anything to help your problem. Renaming the executable is not possible as that will break lots of user's scripts. And if the executables need to be renamed then that needs to be done from upstream so that it is consistent in all other distros and pypi. Please discuss that with Roland, the getmail6 upstream maintainer. > > 2. If (1) is rejected, then drop "getmail6" completely. Restore the getmail > package that depends on python2.7 and everything will continue to work for > users who have getmail installed pre-upgrade, or who want to install it > afterwards. Not possible. Python 2.7 is there only for the build process and not for running applications. The following is quoted from Debian Bullseye release notes: Python 2 is already beyond its End Of Life, and will receive no security updates. It is not supported for running applications, and packages relying on it have either been switched to Python 3 or removed. However, Debian bullseye does still include a version of Python 2.7, as well as a small number of Python 2 build tools such as python-setuptools. These are present only because they are required for a few application build processes that have not yet been converted to Python 3. Not just Debian but all the distros need to have a Python3 version of getmail and getmail6 is the only alternative available now. I will be very very happy to remove getmail6 when you release a Python3 version of getmail. But until then I will only remove the transitional package. I don't see the need to communicate any further on this and to summarise what I have said: 1) I will remove the transitional package for now using this bug report. 2) Please do let me know after you have released a Python3 version of getmail and i will remove getmail6. -- Regards Sudip
Bug#998108: Rebuild w/ new toolchain
On Mon, 8 Nov 2021 10:25:24 +0100 Matthias Urlichs wrote: > Looks like the problem is a toolchain matter and requires a rebuild with > Rust 1.56. > > https://bugzilla.opensuse.org/show_bug.cgi?id=1192067 According to the build log, 94.0-1 has been built with 1.56. -- ceterum censeo microsoftem esse delendam. pgp_NIZBxyXUA.pgp Description: OpenPGP digital signature
Processed: Bug#995740 marked as pending in tdigest
Processing control commands: > tag -1 pending Bug #995740 [src:tdigest] tdigest FTBFS on several architectures: tdigest_percentile test failure Added tag(s) pending. -- 995740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995740 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995740: marked as pending in tdigest
Control: tag -1 pending Hello, Bug #995740 in tdigest 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/postgresql/tdigest/-/commit/9884a977183344ea172feeab50fe3891b99ed09a Fix precision variation in tests on older PG versions and some architectures. (Closes: #995740) (this message was generated automatically) -- Greetings https://bugs.debian.org/995740
Bug#997942: tomboy-ng: FTBFS with fpc 3.2.2
Hi David Apologies for the delayed response. On Sat, 30 Oct 2021 at 06:57, David Bannon wrote: > Thanks Graham. I noticed the same problem myself a few days ago. Its a > very simple fix but as I am very close to releasing a new version > anyway, maybe we can wait until them ? Sure, there's no reason to rush a fix now. Replying to this bug will delay the pending autoremoval. On Sun, 7 Nov 2021 at 02:41, David Bannon wrote: > However, Testing still has the 'older' compiler and it builds fine with > that. How do I test my build against tools only available in sid ? Development of Debian takes place in unstable (aka sid), and if you uploaded a new version of tomboy-ng to the archive, it would be built against all of the packages in unstable. It is possible to install individual packages from unstable on a testing system [1]. Take care to set priorities [2] so that you don't end up with all of the packages from unstable, unless you like living on the edge. I suggest subscribing to the Debian Pascal Packaging Team's mailing list [3], to keep up to date with FPC and Lazarus packaging developments. You are also welcome to join the team and you will have no shortage of sponsors for your uploads. Regards Graham [1] https://wiki.debian.org/DebianUnstable [2] https://wiki.debian.org/AptConfiguration [3] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-pascal-devel
Bug#998826: ceph-mgr-modules-core,ceph-mgr: both ship /usr/share/ceph/mgr/*
Package: ceph-mgr-modules-core,ceph-mgr Version: 16.2.6+ds-2 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 ceph-mgr. Preparing to unpack .../111-ceph-mgr_16.2.6+ds-2_amd64.deb ... Unpacking ceph-mgr (16.2.6+ds-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-3hMgRk/111-ceph-mgr_16.2.6+ds-2_amd64.deb (--unpack): trying to overwrite '/usr/share/ceph/mgr/balancer/__init__.py', which is also in package ceph-mgr-modules-core 16.2.6+ds-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-3hMgRk/111-ceph-mgr_16.2.6+ds-2_amd64.deb These files are shipped by both packages: usr/share/ceph/mgr/balancer/__init__.py usr/share/ceph/mgr/balancer/module.py usr/share/ceph/mgr/crash/__init__.py usr/share/ceph/mgr/crash/module.py usr/share/ceph/mgr/devicehealth/__init__.py usr/share/ceph/mgr/devicehealth/module.py usr/share/ceph/mgr/influx/__init__.py usr/share/ceph/mgr/influx/module.py usr/share/ceph/mgr/insights/__init__.py usr/share/ceph/mgr/insights/health.py usr/share/ceph/mgr/insights/module.py usr/share/ceph/mgr/iostat/__init__.py usr/share/ceph/mgr/iostat/module.py usr/share/ceph/mgr/localpool/__init__.py usr/share/ceph/mgr/localpool/module.py usr/share/ceph/mgr/orchestrator/README.md usr/share/ceph/mgr/orchestrator/__init__.py usr/share/ceph/mgr/orchestrator/_interface.py usr/share/ceph/mgr/orchestrator/module.py usr/share/ceph/mgr/pg_autoscaler/__init__.py usr/share/ceph/mgr/pg_autoscaler/module.py usr/share/ceph/mgr/progress/__init__.py usr/share/ceph/mgr/progress/module.py usr/share/ceph/mgr/progress/test_progress.py usr/share/ceph/mgr/prometheus/__init__.py usr/share/ceph/mgr/prometheus/module.py usr/share/ceph/mgr/rbd_support/__init__.py usr/share/ceph/mgr/rbd_support/common.py usr/share/ceph/mgr/rbd_support/mirror_snapshot_schedule.py usr/share/ceph/mgr/rbd_support/module.py usr/share/ceph/mgr/rbd_support/perf.py usr/share/ceph/mgr/rbd_support/schedule.py usr/share/ceph/mgr/rbd_support/task.py usr/share/ceph/mgr/rbd_support/trash_purge_schedule.py usr/share/ceph/mgr/restful/__init__.py usr/share/ceph/mgr/restful/api/__init__.py usr/share/ceph/mgr/restful/api/config.py usr/share/ceph/mgr/restful/api/crush.py usr/share/ceph/mgr/restful/api/doc.py usr/share/ceph/mgr/restful/api/mon.py usr/share/ceph/mgr/restful/api/osd.py usr/share/ceph/mgr/restful/api/perf.py usr/share/ceph/mgr/restful/api/pool.py usr/share/ceph/mgr/restful/api/request.py usr/share/ceph/mgr/restful/api/server.py usr/share/ceph/mgr/restful/common.py usr/share/ceph/mgr/restful/context.py usr/share/ceph/mgr/restful/decorators.py usr/share/ceph/mgr/restful/hooks.py usr/share/ceph/mgr/restful/module.py usr/share/ceph/mgr/selftest/__init__.py usr/share/ceph/mgr/selftest/module.py usr/share/ceph/mgr/status/__init__.py usr/share/ceph/mgr/status/module.py usr/share/ceph/mgr/telegraf/__init__.py usr/share/ceph/mgr/telegraf/basesocket.py usr/share/ceph/mgr/telegraf/module.py usr/share/ceph/mgr/telegraf/protocol.py usr/share/ceph/mgr/telegraf/utils.py usr/share/ceph/mgr/telemetry/__init__.py usr/share/ceph/mgr/telemetry/module.py usr/share/ceph/mgr/test_orchestrator/README.md usr/share/ceph/mgr/test_orchestrator/__init__.py usr/share/ceph/mgr/test_orchestrator/dummy_data.json usr/share/ceph/mgr/test_orchestrator/module.py usr/share/ceph/mgr/volumes/__init__.py usr/share/ceph/mgr/volumes/fs/__init__.py usr/share/ceph/mgr/volumes/fs/async_cloner.py usr/share/ceph/mgr/volumes/fs/async_job.py usr/share/ceph/mgr/volumes/fs/exception.py usr/share/ceph/mgr/volumes/fs/fs_util.py usr/share/ceph/mgr/volumes/fs/operations/__init__.py usr/share/ceph/mgr/volumes/fs/operations/access.py usr/share/ceph/mgr/volumes/fs/operations/clone_index.py usr/share/ceph/mgr/volumes/fs/operations/group.py usr/share/ceph/mgr/volumes/fs/operations/index.py usr/share/ceph/mgr/volumes/fs/operations/lock.py usr/share/ceph/mgr/volumes/fs/operations/pin_util.py usr/share/ceph/mgr/volumes/fs/operations/rankevicter.py usr/share/ceph/mgr/volumes/fs/operations/resolver.py usr/share/ceph/mgr/volumes/fs/operations/snapshot_util.py usr/share/ceph/mgr/volumes/fs/operations/subvolume.py usr/share/ceph/mgr/volumes/fs/operations/template.py usr/share/ceph/mgr/volumes/fs/operations/trash.py usr/share/ceph/mgr/volumes/fs/operations/versions/__init__.py usr/share/ceph/mgr/volumes/fs/operations/versions/auth_metadata.py usr/share/ceph/mgr/volumes/fs/operations/versions/metadata_manager.py usr/share/ceph/mgr/volumes/fs/operations/versions/op_sm.py usr/share/ceph/mgr/volumes/fs/operations/versions/subvolume_attrs.py usr/share/ceph/mgr/volumes/fs/operations/versions/subvolume_base.py usr/share/ceph/mgr/volumes/fs/operations/versions/subvolume_v1.py
Bug#997086: marked as done (sqlalchemy-i18n: FTBFS: build hangs during tests while connecting to postgresql)
Your message dated Mon, 08 Nov 2021 10:21:53 + with message-id and subject line Bug#997086: fixed in sqlalchemy-i18n 1.1.0-1 has caused the Debian Bug report #997086, regarding sqlalchemy-i18n: FTBFS: build hangs during tests while connecting to postgresql 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.) -- 997086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sqlalchemy-i18n Version: 1.0.3-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > conn = _connect(dsn, connection_factory=connection_factory, **kwasync) > psycopg2.OperationalError: connection to server at "localhost" (::1), port > 54469 failed: Connection refused > Is the server running on that host and accepting TCP/IP connections? > connection to server at "localhost" (127.0.0.1), port 54469 failed: > Connection refused > Is the server running on that host and accepting TCP/IP connections? > > 2021-10-23 07:44:56.935 UTC [28085] LOG: starting PostgreSQL 14.0 (Debian > 14.0-1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.3.0-11) 10.3.0, > 64-bit > 2021-10-23 07:44:56.935 UTC [28085] LOG: listening on IPv4 address > "127.0.0.1", port 54469 > 2021-10-23 07:44:56.935 UTC [28085] LOG: listening on Unix socket > "/tmp/tmpwfn7fr11/tmp/.s.PGSQL.54469" > 2021-10-23 07:44:56.937 UTC [28086] LOG: database system was shut down at > 2021-10-23 07:44:56 UTC > 2021-10-23 07:44:56.940 UTC [28085] LOG: database system is ready to accept > connections > make[1]: *** [debian/rules:18: override_dh_auto_test] Error 1 > make[1]: Leaving directory '/<>' > make: *** [debian/rules:5: binary] Error 2 > dpkg-buildpackage: error: debian/rules binary subprocess returned exit status > 2 > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://qa-logs.debian.net/2021/10/23/sqlalchemy-i18n_1.0.3-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: sqlalchemy-i18n Source-Version: 1.1.0-1 Done: Edward Betts We believe that the bug you reported is fixed in the latest version of sqlalchemy-i18n, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Edward Betts (supplier of updated sqlalchemy-i18n 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, 07 Nov 2021 11:08:28 + Source: sqlalchemy-i18n Architecture: source Version: 1.1.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Edward Betts Closes: 997086 Changes: sqlalchemy-i18n (1.1.0-1) unstable; urgency=medium . * New upstream release. * Update Standards-Version. * Fix failing tests. (Closes: #997086) Checksums-Sha1: a07095e77610379cb0776dd93dc82549971fd2be 2318 sqlalchemy-i18n_1.1.0-1.dsc 492155e3a91eecfaf8263fe94f600515942bfaf5 28197 sqlalchemy-i18n_1.1.0.orig.tar.gz 940296587fa358c46bd858d74362809f145a19b7 4120 sqlalchemy-i18n_1.1.0-1.debian.tar.xz ce7dd1d9c962685c1b887427f89366bc629ff05f 8710 sqlalchemy-i18n_1.1.0-1_source.buildinfo Checksums-Sha256: 3fedbd97b7ed98b3118f06456f698f9c45875e1cc2422aa985e7aa9d3c857fdc 2318 sqlalchemy-i18n_1.1.0-1.dsc de33376483a581ca14218d8f57a114466c5f72b674a95839b6c4564a6e67796f 28197 sqlalchemy-i18n_1.1.0.orig.tar.gz 57472a0bb79feb38778d83b8a94bf6433d76800dc92bef4e77b49fc1b6d87006 4120 sqlalchemy-i18n_1.1.0-1.debian.tar.xz
Bug#998823: python3-stone,stone: both ship /usr/bin/stone
Package: python3-stone,stone Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 2.4-1 Control: found -1 3.2.1-1 Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package stone. Preparing to unpack .../archives/stone_2.4-1_amd64.deb ... Unpacking stone (2.4-1) ... dpkg: error processing archive /var/cache/apt/archives/stone_2.4-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/stone', which is also in package python3-stone 3.2.1-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/stone_2.4-1_amd64.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/bin/stone usr/share/man/man1/stone.1.gz This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html python3-stone=3.2.1-1_stone=2.4-1.log.gz Description: application/gzip
Processed: python3-stone,stone: both ship /usr/bin/stone
Processing control commands: > found -1 2.4-1 Bug #998823 [python3-stone,stone] python3-stone,stone: both ship /usr/bin/stone There is no source info for the package 'python3-stone' at version '2.4-1' with architecture '' Marked as found in versions stone/2.4-1. > found -1 3.2.1-1 Bug #998823 [python3-stone,stone] python3-stone,stone: both ship /usr/bin/stone There is no source info for the package 'stone' at version '3.2.1-1' with architecture '' Marked as found in versions python-stone/3.2.1-1. -- 998823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984195: marked as done (libomxil-bellagio: ftbfs with GCC-11)
Your message dated Mon, 08 Nov 2021 09:50:50 + with message-id and subject line Bug#984195: fixed in libomxil-bellagio 0.9.3-7 has caused the Debian Bug report #984195, regarding libomxil-bellagio: ftbfs with GCC-11 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.) -- 984195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libomxil-bellagio Version: 0.9.3-6 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/libomxil-bellagio_0.9.3-6_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] config.status: creating test/components/audio_effects/Makefile config.status: creating test/components/resource_manager/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands make[1]: Leaving directory '/<>' dh_auto_build make -j4 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in src make[3]: Entering directory '/<>/src' Making all in base make[4]: Entering directory '/<>/src/base' /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../../include -I../../src -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -DCONFIG_DEBUG_LEVEL=0 -c -o libomxbase_la-omx_base_component.lo `test -f 'omx_base_component.c' || echo './'`omx_base_component.c /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../../include -I../../src -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -DCONFIG_DEBUG_LEVEL=0 -c -o libomxbase_la-omx_base_port.lo `test -f 'omx_base_port.c' || echo './'`omx_base_port.c /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../../include -I../../src -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -DCONFIG_DEBUG_LEVEL=0 -c -o libomxbase_la-omx_base_filter.lo `test -f 'omx_base_filter.c' || echo './'`omx_base_filter.c /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../../include -I../../src -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -DCONFIG_DEBUG_LEVEL=0 -c -o libomxbase_la-omx_base_sink.lo `test -f 'omx_base_sink.c' || echo './'`omx_base_sink.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../../include -I../../src -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror -DCONFIG_DEBUG_LEVEL=0 -c omx_base_port.c -fPIC -DPIC -o .libs/libomxbase_la-omx_base_port.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -I../../include -I../../src -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror
Bug#998822: python3-satpy: ships .../dist-packages/benchmarks/*.py
Package: python3-satpy Version: 0.31.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 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-satpy_0.31.0-1_all.deb ... Unpacking python3-satpy (0.31.0-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-satpy_0.31.0-1_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/benchmarks/__init__.py', which is also in package python3-skbio 0.5.6-4 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/python3-satpy_0.31.0-1_all.deb That is an overly generic python module name, either don't ship benchmarks/*.py at all (python3-skbio fixed it this way in sid, #991981) or move them to a namespaced location, e.g. benchmarks/satpy/*.py. cheers, Andreas
Bug#998679:
Hello, I have the same issue with firefox-esr 91.3.0esr-1. Downgrading to 91.2.0esr-1 remove the issue. Sylvain
Bug#998712: marked as done (irrlicht: invalid Uploaders field: missing comma between Vincent Cheng and Julien Puydt)
Your message dated Mon, 08 Nov 2021 09:04:02 + with message-id and subject line Bug#998712: fixed in irrlicht 1.8.4+dfsg1-3 has caused the Debian Bug report #998712, regarding irrlicht: invalid Uploaders field: missing comma between Vincent Cheng and Julien Puydt 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.) -- 998712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998712 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: irrlicht Version: 1.8.4+dfsg1-2 Severity: serious Justification: Policy 5.6.3 irrlicht 1.8.4+dfsg1-2 introduced an invalid uploaders field, that is missing a comma between Vincent Cheng and Julien Puydt. $ apt-cache showsrc irrlicht | grep -E '^$|^Version|^Uploaders' Version: 1.8.4+dfsg1-1.1 Uploaders: Christoph Egger , Vincent Cheng Version: 1.8.4+dfsg1-2 Uploaders: Vincent Cheng Julien Puydt According to Debian policy 5.6.3 the Uploaders field must separate individual uploaders using commas: List of the names and email addresses of co-maintainers of the package, if any. ... The format of each entry is the same as that of the Maintainer field, and multiple entries must be comma separated. This is causing the DDPO and BLS cron jobs to send error mails. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: irrlicht Source-Version: 1.8.4+dfsg1-3 Done: Julien Puydt We believe that the bug you reported is fixed in the latest version of irrlicht, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Puydt (supplier of updated irrlicht package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Nov 2021 09:43:35 +0100 Source: irrlicht Architecture: source Version: 1.8.4+dfsg1-3 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Julien Puydt Closes: 998712 Changes: irrlicht (1.8.4+dfsg1-3) unstable; urgency=medium . * Add comma between uploaders (Closes: #998712). Checksums-Sha1: d4fa1d585c31764d42f1cb5f71348cc9d9a0b15c 2390 irrlicht_1.8.4+dfsg1-3.dsc 9a6e0205a2c6fa7c95e32493df4900012ce57bd0 41536 irrlicht_1.8.4+dfsg1-3.debian.tar.xz 19a604cacc5d229dbe3fd1eb57fb71c5abacf42b 10260 irrlicht_1.8.4+dfsg1-3_source.buildinfo Checksums-Sha256: afaddfe34ba1e52a9b0cb66b9ce374f0d7c08ce8196397ee355438076a442f22 2390 irrlicht_1.8.4+dfsg1-3.dsc 84393d73b8a08fca6de629ad62601004b1afbc92db285cfc6d0467ea0d9a950e 41536 irrlicht_1.8.4+dfsg1-3.debian.tar.xz ec95bf868a96f9223afc0c9e2d11cafa9110240abd49b43b6179ec6ef560dc49 10260 irrlicht_1.8.4+dfsg1-3_source.buildinfo Files: ed710a743f2e8376b21f64b7e70317cc 2390 libs optional irrlicht_1.8.4+dfsg1-3.dsc a7a0161b3e9977b07a21e6a2618dc26a 41536 libs optional irrlicht_1.8.4+dfsg1-3.debian.tar.xz 51a3597764b258b66607e2c364b5e6a3 10260 libs optional irrlicht_1.8.4+dfsg1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmGI44ESHGpwdXlkdEBk ZWJpYW4ub3JnAAoJEATFO9f+AwVRp5MP/1HQ+ZVK2n7y9kyeDu/qxXiQxkVkY7al XBmEMl9qWIgcwtRq2uoFCvGnYqboVcnptJVHlBrjur2KPW/0a2dbQrjGDW2TOPAC XsDmXgRfX/xN4flmMQn9ftExIba/avzWTlIuR8SmxN3F66Ip3RwftvkIjvCcAqj9 wc0sE5wv2GmBQbl1TwwMC+107cjVm/+0vU47XWLAsvaeXdnG/JyqXDUAe9pxIqUp 3YamCmG982g9ZAjDjjUm+NsylF52vFCjhgUaqvteFQx5+at6a9eHq3oddVUrntVP mLh7EUos/Iu/FqJHTz+xtVlhrzeFWcGg+Egr47br9dGD613ZzbdzaUuOiMco3PHC e5Cv6UXGy0wxviAHVU4mJuW2EJejEf38wWte6p1dS73SmN0qaTwA6z3jMYSKOD+8 HNGGjwYzYP5C8O7RF3dqkbKqM5V12yAU59IRhcGvUMwkKPuxeoDdv64i9LMHca4+ RwEyV2CLb/95FePs3Qs7x788yOUnsuzURsODZ1taWNUjiRxKUx0nUrlrMwKmnjVu Oh0wVnvYnZce+RhEyFfjtkE7dbTUP/B5CeJKt/PBHKVyHft1tSLpkB0Ve7LbTkZW pTfmkoJ7eQkpMCtSpmnEUGc85CXUSd8SasBa22tyEpWg+MnKo4Ev/NcR86I17rh0 JcfXhH4F3PA3 =GMxp -END PGP SIGNATURE End Message ---
