Processed: Re: unarchiving 938850, reopening 938850, unarchiving 947278, reopening 947278
Processing control commands:
> close 991543 1.0~prerelease-2+rm
Bug #991543 {Done: Paul Wise } [python-xe] python-xe: python2
dependency. Shouldn't it get removed from Experimental?
There is no source info for the package 'python-xe' at version
'1.0~prerelease-2+rm' with architecture ''
Unable to make a source version for version '1.0~prerelease-2+rm'
Ignoring request to alter fixed versions of bug #991543 to the same values
previously set
Bug #991543 {Done: Paul Wise } [python-xe] python-xe: python2
dependency. Shouldn't it get removed from Experimental?
Bug 991543 is already marked as done; not doing anything.
> close 947278 1.0~prerelease-2+rm
Bug #947278 {Done: Paul Wise } [src:xmlelements] xmlelements:
missing Build-Depends: dh-python
The source 'xmlelements' and version '1.0~prerelease-2+rm' do not appear to
match any binary packages
Ignoring request to alter fixed versions of bug #947278 to the same values
previously set
Bug #947278 {Done: Paul Wise } [src:xmlelements] xmlelements:
missing Build-Depends: dh-python
Bug 947278 is already marked as done; not doing anything.
> close 938850 1.0~prerelease-2+rm
Bug #938850 {Done: Paul Wise } [src:xmlelements] xmlelements:
Python2 removal in sid/bullseye
The source 'xmlelements' and version '1.0~prerelease-2+rm' do not appear to
match any binary packages
Ignoring request to alter fixed versions of bug #938850 to the same values
previously set
Bug #938850 {Done: Paul Wise } [src:xmlelements] xmlelements:
Python2 removal in sid/bullseye
Bug 938850 is already marked as done; not doing anything.
--
938850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938850
947278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947278
991543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: unarchiving 938850, reopening 938850, unarchiving 947278, reopening 947278
Processing control commands: > close 991543 1.0~prerelease-2+rm Bug #991543 [python-xe] python-xe: python2 dependency. Shouldn't it get removed from Experimental? There is no source info for the package 'python-xe' at version '1.0~prerelease-2+rm' with architecture '' Unable to make a source version for version '1.0~prerelease-2+rm' Marked as fixed in versions 1.0~prerelease-2+rm. Bug #991543 [python-xe] python-xe: python2 dependency. Shouldn't it get removed from Experimental? Marked Bug as done > close 947278 1.0~prerelease-2+rm Bug #947278 [src:xmlelements] xmlelements: missing Build-Depends: dh-python The source 'xmlelements' and version '1.0~prerelease-2+rm' do not appear to match any binary packages Marked as fixed in versions xmlelements/1.0~prerelease-2+rm. Bug #947278 [src:xmlelements] xmlelements: missing Build-Depends: dh-python Marked Bug as done > close 938850 1.0~prerelease-2+rm Bug #938850 [src:xmlelements] xmlelements: Python2 removal in sid/bullseye The source 'xmlelements' and version '1.0~prerelease-2+rm' do not appear to match any binary packages Marked as fixed in versions xmlelements/1.0~prerelease-2+rm. Bug #938850 [src:xmlelements] xmlelements: Python2 removal in sid/bullseye Marked Bug as done -- 938850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938850 947278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947278 991543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991543 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938850: unarchiving 938850, reopening 938850, unarchiving 947278, reopening 947278
Control: close 991543 1.0~prerelease-2+rm
Control: close 947278 1.0~prerelease-2+rm
Control: close 938850 1.0~prerelease-2+rm
On Thu, 2022-07-28 at 01:19 +0200, Chris Hofstaedtler wrote:
> Not sure how you determined this
I have a pair of scripts (attached) and a crontab for this:
cd ~/.cache/detect-reintroduced-packages
cat /var/lib/apt/lists/*.debian.org_*_dists_*_*_source_Sources > Sources
cp Sources Sources.old.tmp
debian-reopen-reintroduced-bugs
mv Sources.old.tmp Sources.old
> it looks like src:xmlelements is not in unstable/experimental now?
https://tracker.debian.org/news/1257974/removed-10prerelease-2-from-experimental/
> Maybe the bugs want to be closed again?
Not sure why ftp-master didn't do that. Agreed, doing so above
and also closing the additional bug that got filed too.
--
bye,
pabs
https://wiki.debian.org/PaulWise
debian-reopen-reintroduced-bugs
Description: application/shellscript
#!/usr/bin/python3
# pabs got this from themill on #debian-devel 2020-05
# written by Stuart Prescott
import sys
from typing import List, Dict
from debian.deb822 import Sources, Removals
def source_packages(filename: str) -> List[str]:
with open(filename) as fh:
source_pkgs = []
for s in Sources.iter_paragraphs(fh):
if s.get('Extra-Source-Only') == 'yes':
continue
source_pkgs.append(s['Source'] if 'Source' in s else s['Package'])
return source_pkgs
def removed_packages(filename: str) -> Dict[str, str]:
with open(filename) as fh:
removed_pkgs: List[Dict[str, str]] = []
for r in Removals.iter_paragraphs(fh):
if 'sources' not in r:
continue
if r['suite'] == 'unstable':
removed_pkgs.extend(r.sources)
return {r['source']: r for r in removed_pkgs}
old_sources = source_packages('Sources.old')
new_sources = source_packages('Sources')
added_sources = set(new_sources) - set(old_sources)
if not added_sources:
sys.exit(0)
rm_sources = removed_packages('removals-full.822')
reintroduced_sources = [s for s in added_sources if s in rm_sources]
if reintroduced_sources:
print("Found reintroduced sources:")
for s in reintroduced_sources:
if 'also-bugs' in rm_sources[s]:
extra_msg = 'extra triage needed'
else:
extra_msg = ''
print(" {source}/{version}{extra}".format(
source=s,
extra=extra_msg,
version=rm_sources[s]['version'],
))
sys.exit(1)
signature.asc
Description: This is a digitally signed message part
Bug#1012962: marked as done (kseexpr: ftbfs with GCC-12)
Your message dated Thu, 28 Jul 2022 04:50:54 + with message-id and subject line Bug#1012962: fixed in kseexpr 4.0.4.0-3 has caused the Debian Bug report #1012962, regarding kseexpr: ftbfs with GCC-12 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.) -- 1012962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012962 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:kseexpr Version: 4.0.4.0-2 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/kseexpr_4.0.4.0-2_unstable_gcc12.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. [...] @@ -605,16 +607,16 @@ (optional=templinst)_ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 4.0.4.0 (optional=templinst)_ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED1Ev@Base 4.0.4.0 (optional=templinst)_ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED2Ev@Base 4.0.4.0 - (optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE16_M_insert_uniqueIS5_EESt4pairISt17_Rb_tree_iteratorIS5_EbEOT_@Base 4.0.4.0 +#MISSING: 4.0.4.0-2# (optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE16_M_insert_uniqueIS5_EESt4pairISt17_Rb_tree_iteratorIS5_EbEOT_@Base 4.0.4.0 (optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE4findERKS5_@Base 4.0.4.0 - (optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN7KSeExpr21ExprLocalFunctionNodeEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE17_M_emplace_uniqueIJS6_IS5_SA_S6_ISt17_Rb_tree_iteratorISB_EbEDpOT_@Base 4.0.4.0 - (optional=templinst|arch=armel armhf hppa m68k sh4 x32)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN7KSeExpr21ExprLocalFunctionNodeEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE4findERS7_@Base 4.0.4.0 +#MISSING: 4.0.4.0-2# (optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN7KSeExpr21ExprLocalFunctionNodeEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE17_M_emplace_uniqueIJS6_IS5_SA_S6_ISt17_Rb_tree_iteratorISB_EbEDpOT_@Base 4.0.4.0 + (optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN7KSeExpr21ExprLocalFunctionNodeEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE4findERS7_@Base 4.0.4.0 (optional=templinst)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S6_IS5_N7KSeExpr8ExprFuncEEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE24_M_get_insert_unique_posERS7_@Base 4.0.4.0 (optional=templinst|arch=amd64 arm64 hppa ia64 m68k riscv64 sh4 sparc64 x32)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S6_IS5_N7KSeExpr8ExprFuncEEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISB_ERS7_@Base 4.0.4.0 - (optional=templinst|arch=armel armhf hppa m68k sh4 x32)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S6_IS5_N7KSeExpr8ExprFuncEEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE4findERS7_@Base 4.0.4.0 -
Processed: severity of 1015861 is serious
Processing commands for cont...@bugs.debian.org: > severity 1015861 serious Bug #1015861 [bamtools] bamtools: FTBFS with upcoming doxygen 1.9.4 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1015861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1015865 is serious
Processing commands for cont...@bugs.debian.org: > severity 1015865 serious Bug #1015865 [liblog4c3] liblog4c3: FTBFS with upcoming doxygen 1.9.4 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1015865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1015864 is serious
Processing commands for cont...@bugs.debian.org: > severity 1015864 serious Bug #1015864 [gr-radar] gr-radar: FTBFS with upcoming doxygen 1.9.4 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1015864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015864 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012963: marked as done (kpmcore: ftbfs with GCC-12)
Your message dated Thu, 28 Jul 2022 04:24:43 + with message-id and subject line Bug#1012963: fixed in kpmcore 21.12.3-2 has caused the Debian Bug report #1012963, regarding kpmcore: ftbfs with GCC-12 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.) -- 1012963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012963 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:kpmcore Version: 21.12.3-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/kpmcore_21.12.3-1_unstable_gcc12.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. [...] Normalized debian/libkpmcore11/usr/share/locale/pa/LC_MESSAGES/kpmcore.mo Normalized debian/libkpmcore11/usr/share/locale/hu/LC_MESSAGES/kpmcore.mo Normalized debian/libkpmcore11/usr/share/locale/ro/LC_MESSAGES/kpmcore.mo Normalized debian/libkpmcore11/usr/share/locale/ar/LC_MESSAGES/kpmcore.mo Normalized debian/libkpmcore11/usr/share/locale/nb/LC_MESSAGES/kpmcore.mo Normalized debian/libkpmcore11/usr/share/locale/el/LC_MESSAGES/kpmcore.mo Normalized debian/libkpmcore11/usr/share/locale/ca@valencia/LC_MESSAGES/kpmcore.mo Normalized debian/libkpmcore11/usr/share/locale/eu/LC_MESSAGES/kpmcore.mo Normalized debian/libkpmcore11/usr/share/locale/fr/LC_MESSAGES/kpmcore.mo Normalized debian/libkpmcore11/usr/share/locale/ga/LC_MESSAGES/kpmcore.mo Normalized debian/libkpmcore11/usr/share/locale/gl/LC_MESSAGES/kpmcore.mo Normalized debian/libkpmcore11/usr/share/locale/ko/LC_MESSAGES/kpmcore.mo Normalized debian/libkpmcore11/usr/share/locale/nn/LC_MESSAGES/kpmcore.mo Normalized debian/libkpmcore11/usr/share/locale/zh_CN/LC_MESSAGES/kpmcore.mo Normalized debian/libkpmcore11/usr/share/locale/ja/LC_MESSAGES/kpmcore.mo Normalized debian/libkpmcore11/usr/share/locale/uk/LC_MESSAGES/kpmcore.mo Normalized debian/libkpmcore11/usr/share/locale/da/LC_MESSAGES/kpmcore.mo Normalized debian/libkpmcore11/usr/share/locale/ug/LC_MESSAGES/kpmcore.mo Normalized debian/libkpmcore11/usr/share/locale/hr/LC_MESSAGES/kpmcore.mo Normalized debian/libkpmcore11/usr/share/locale/de/LC_MESSAGES/kpmcore.mo Normalized debian/libkpmcore11/usr/share/locale/pt/LC_MESSAGES/kpmcore.mo Normalized debian/libkpmcore11/usr/share/locale/sl/LC_MESSAGES/kpmcore.mo dh_compress dh_fixperms dh_missing dh_dwz -a dh_strip -a debian/rules override_dh_makeshlibs make[1]: Entering directory '/<>' dh_makeshlibs -Xlibpmdummybackendplugin -Xlibpmsfdiskbackendplugin dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libkpmcore11/DEBIAN/symbols doesn't match completely debian/libkpmcore11.symbols --- debian/libkpmcore11.symbols (libkpmcore11_21.12.3-1_amd64) +++ dpkg-gensymbolsayenrO 2022-06-10 08:58:43.893972549 + @@ -1394,7 +1394,8 @@ (arch=!armel !riscv64)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 21.12.1 (arch=armel
Processed: tagging 1012962
Processing commands for cont...@bugs.debian.org: > tags 1012962 + pending Bug #1012962 [src:kseexpr] kseexpr: ftbfs with GCC-12 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012962 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1012963
Processing commands for cont...@bugs.debian.org: > tags 1012963 + pending Bug #1012963 [src:kpmcore] kpmcore: ftbfs with GCC-12 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012963 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015742: bug not reproduced
control: severity -1 |wishlist| Hi, This bug is not reproduced after I reinstall the OS(stable + testing). I think this bug is take palace only in the OS which mixed the stable + testing + sid in my notebook at that time. -- 肖盛文 xiao sheng wen https://www.atzlinux.com 《铜豌豆 Linux》基于 Debian 的 Linux 中文 桌面 操作系统 Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com Debian salsa: https://salsa.debian.org/atzlinux-guest GnuPG Public Key: 0x00186602339240CB OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: bug not reproduced
Processing commands for cont...@bugs.debian.org: > severity 1015742 wishlist Bug #1015742 [nheko] nheko: symbol lookup error: nheko: undefined symbol Severity set to 'wishlist' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 1015742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015742 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 1012980 in libkf5libkleo/4:22.04.1-1, closing 1012980
Processing commands for cont...@bugs.debian.org: > fixed 1012980 libkf5libkleo/4:22.04.1-1 Bug #1012980 [src:libkf5libkleo] libkf5libkleo: ftbfs with GCC-12 Marked as fixed in versions libkf5libkleo/4:22.04.1-1. > close 1012980 Bug #1012980 [src:libkf5libkleo] libkf5libkleo: ftbfs with GCC-12 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1012980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999260: marked as done (linklint: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Thu, 28 Jul 2022 02:41:58 +
with message-id
and subject line Bug#999260: fixed in linklint 2.3.5-5.3
has caused the Debian Bug report #999260,
regarding linklint: missing required debian/rules targets build-arch and/or
build-indep
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.)
--
999260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linklint
Version: 2.3.5-5.2
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep
Dear maintainer,
Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules
Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.
This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.
Best,
Lucas
--- End Message ---
--- Begin Message ---
Source: linklint
Source-Version: 2.3.5-5.3
Done: Håvard F. Aasen
We believe that the bug you reported is fixed in the latest version of
linklint, 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 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Håvard F. Aasen (supplier of updated linklint 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: Wed, 27 Jul 2022 23:46:47 +0200
Source: linklint
Architecture: source
Version: 2.3.5-5.3
Distribution: unstable
Urgency: medium
Maintainer: Felipe Augusto van de Wiel (faw)
Changed-By: Håvard F. Aasen
Closes: 999260
Changes:
linklint (2.3.5-5.3) unstable; urgency=medium
.
* Non-maintainer upload.
* Include missing build target. (Closes: #999260)
- Using dh sequencer.
- Add dependency on ${misc:Depends}.
- Since we only build for 'all', move dependency from BD-indep to BD.
* Change to debhelper-compat.
* Bump debhelper to 10.
* Add dependency on ${perl:Depends}.
Checksums-Sha1:
82cdd004a7528bb7de7be0f666ee8be85964696b 1681 linklint_2.3.5-5.3.dsc
555b48eee3c91faddfb7e06fc52211054561b282 9531 linklint_2.3.5-5.3.diff.gz
fb4bb1f487ef59de85bfcc2bdea2444cb7c666fc 5903
linklint_2.3.5-5.3_source.buildinfo
Checksums-Sha256:
06da1f8d507c6292c57895e99c27a7844429e3514e6e8884906c288d1ecdba77 1681
linklint_2.3.5-5.3.dsc
cd632449d028a9c9c1b67be2899e3415aff6d3da1d6a7e1a70cc65fcebbf4533 9531
linklint_2.3.5-5.3.diff.gz
24c6dd95e19cb63b54813b3388830f94a2d934f350cf8f8d179852e6498fe193 5903
linklint_2.3.5-5.3_source.buildinfo
Files:
597de1492488437fd0efd15a8e9d60f1 1681 web optional linklint_2.3.5-5.3.dsc
96d1de7065c434286a9a90918a7f9171 9531 web optional linklint_2.3.5-5.3.diff.gz
e3252c0f9e585588c6ca437ce509fb68 5903 web optional
linklint_2.3.5-5.3_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmLh7V8ACgkQweDZLphv
fH5mDw//cf3vXoIyCOJO0vBWuL8zYn/hyHqFLHmHZX+l3Y8EEuOlyzYPbmOlPBGF
W5rGlknUM/LqIWnKCPYj64CUQDETe93UI1CpVtjrgbnjdBY3clQKxuqI00j4qy1O
+tSPP0gcjVwadW5ONcGu9pjdx04ztnA0AfWlm0ZvlmozEDF3uvh5PiPwAVR6u1oa
+V5LaM/NNMzOTNHyEUytiwDsAeF1s9R6h6IJm9K33Z4hfIyuGB1a/mzlblll5wyw
dLxogNcegyHLfho98EQ9/tzkLjqYxl7jXb3WkznFAzwtWKhUtpUvL1K4AMkUJrEB
6R0Ry2IBUJ8ezvtUmHSMvMzRaLEXLx2ItkjinQoTqTT+xQ6OLK51Cp8Kjawt15Ci
puZbXNAqQwxiF/rUF4lMmB32tTlLTZwJSeD/yGZMick8uRNnxoQZhfw2zJBbMtiE
qYqG32u6BZUOE7pfdMjoxd6LxR/6/4b0svJPJTpUIaQMTfrgsWR7VDkBQzJf5yH0
goknMPJIgC3QhxeVFbVtb/ifNvM7CuGTpdrOpAsYIPnKkdJGNUeFDhMOhLuYlGn5
MHW61mI9a4sFn1PSNS7AFbOZtIhWuqMqHYuxIFcC2xbAidk9C0RjUaq/QzE5iAvZ
DPTJZI8G32A5HKuJXwhwHAx4CIWsGMX3ZGhd0gNHrPv6b28PZ4w=
=cTgb
-END PGP SIGNATURE End Message ---
Bug#1014512: freeipa: FTBFS: AttributeError: module 'collections' has no attribute 'Iterable'
On Thu, 07 Jul 2022 12:51:31 +0200 Andreas Beckmann wrote: > Package: freeipa > Version: 4.9.8-1+exp1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > > Hi, > > freeipa recently started to FTBFS in experimental (but not in sid) after > some (transitive) build dependency got upgraded: > > ... > Making all in css > make[5]: Entering directory '/build/freeipa-4.9.8/install/ui/css' > python3 -m lesscpy -x ../less/ipa.less > ipa.css > Traceback (most recent call last): > File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main > return _run_code(code, main_globals, None, > File "/usr/lib/python3.10/runpy.py", line 86, in _run_code > exec(code, run_globals) > File "/usr/lib/python3/dist-packages/lesscpy/__main__.py", line 4, in > run() > File "/usr/lib/python3/dist-packages/lesscpy/scripts/compiler.py", line 176, in run > p.parse(filename=args.target, debuglevel=args.debug) > File "/usr/lib/python3/dist-packages/lesscpy/lessc/parser.py", line 153, in parse > self.result = self.parser.parse( > File "/usr/lib/python3/dist-packages/ply/yacc.py", line 333, in parse > return self.parseopt_notrack(input, lexer, debug, tracking, tokenfunc) > File "/usr/lib/python3/dist-packages/ply/yacc.py", line 1120, in parseopt_notrack > p.callable(pslice) > File "/usr/lib/python3/dist-packages/lesscpy/lessc/parser.py", line 259, in p_statement_import > recurse.parse(filename=filename, debuglevel=0) > File "/usr/lib/python3/dist-packages/lesscpy/lessc/parser.py", line 156, in parse > self.post_parse() > File "/usr/lib/python3/dist-packages/lesscpy/lessc/parser.py", line 171, in post_parse > self.result = list(utility.flatten(out)) > File "/usr/lib/python3/dist-packages/lesscpy/lessc/utility.py", line 28, in flatten > if isinstance(elm, collections.Iterable) and not isinstance(elm, string_types): > AttributeError: module 'collections' has no attribute 'Iterable' > make[5]: *** [Makefile:660: ipa.css] Error 1 > make[5]: Leaving directory '/build/freeipa-4.9.8/install/ui/css' > ... > > Andreas Not really a freeipa related bug. collections.Iterable :1: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated since Python 3.3, and in 3.10 it will stop working python3-lesscpy install /usr/lib/python3/dist-packages/lesscpy/lessc/utility.py file. lessc utility.py in turn import collections.Iterable that must be changed to collections.abc.Iterable.
Processed: Re: Bug#1013451: openssh-client: double free or corruption
Processing control commands: > reassign -1 libssl3 Bug #1013451 [openssh-client] openssh-client: double free or corruption Bug reassigned from package 'openssh-client' to 'libssl3'. No longer marked as found in versions openssh/1:9.0p1-1. Ignoring request to alter fixed versions of bug #1013451 to the same values previously set > affects -1 openssh-client Bug #1013451 [libssl3] openssh-client: double free or corruption Added indication that 1013451 affects openssh-client -- 1013451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013451: openssh-client: double free or corruption
Control: reassign -1 libssl3 Control: affects -1 openssh-client * Antonio : [..] > #6 0x77b2bd2cin ??() from /usr/lib/x86_64-linux-gnu/libcrypto.so.3 > #7 0x77b1858ein BN_mod_exp_mont_consttime_x2() from > /usr/lib/x86_64-linux-gnu/libcrypto.so.3 > #8 0x77c77b6din ??() from /usr/lib/x86_64-linux-gnu/libcrypto.so.3 > #9 0x77c79010in ??() from /usr/lib/x86_64-linux-gnu/libcrypto.so.3 > #10 0x77c7d0d1in RSA_sign() from > /usr/lib/x86_64-linux-gnu/libcrypto.so.3 > #11 0x555d6ee0in ssh_rsa_sign(key=key@entry=0x556c89e0, > sigp=sigp@entry=0x7fffc3c0, > lenp=lenp@entry=0x7fffc3c8, data=data@entry=0x556b6e70 "", > datalen=, > alg_ident=alg_ident@entry=0x556b2da0 "rsa-sha2-512") at > ../../ssh-rsa.c:206 [..] * Andreas Tille : > 2022-06-23 10:54:50 status installed libssl3:amd64 3.0.4-1 Might have been https://github.com/openssl/openssl/issues/18625 ? Reassigning to libssl3 so the OpenSSL maintainers can make a decision about this bug. Chris
Bug#1014706: marked as done (bcc: provides c-compiler while not providing cc alternative)
Your message dated Thu, 28 Jul 2022 00:36:55 + with message-id and subject line Bug#1014706: fixed in linux86 0.16.17-3.4 has caused the Debian Bug report #1014706, regarding bcc: provides c-compiler while not providing cc alternative 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.) -- 1014706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ikiwiki-hosting-web Version: 0.20180719-2 Severity: important Depends: ..., gcc | c-compiler,... There is no defined semantics what "c-compiler" actually provides, e.g. 'cc' might or might not be provided. There are mysterious ppc64el debci failures that might be related to bcc being installed on ppc64el while tcc gets installed on other architectures. Please change this dependency to either only gcc, or a list of known-working C compiler alternatives. --- End Message --- --- Begin Message --- Source: linux86 Source-Version: 0.16.17-3.4 Done: Chris Hofstaedtler We believe that the bug you reported is fixed in the latest version of linux86, 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 1014...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Hofstaedtler (supplier of updated linux86 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: Wed, 27 Jul 2022 23:53:56 + Source: linux86 Architecture: source Version: 0.16.17-3.4 Distribution: unstable Urgency: medium Maintainer: Juan Cespedes Changed-By: Chris Hofstaedtler Closes: 1014706 Changes: linux86 (0.16.17-3.4) unstable; urgency=medium . * Non-maintainer upload. * Drop Provides: c-compiler. Cant pretend a 16bit x86 compiler would satisfy /usr/bin/cc on all architectures. Closes: #1014706 Checksums-Sha1: 4ac1b3ba711043bb79b75baf155c84a9f0cfb5d9 1710 linux86_0.16.17-3.4.dsc 865b181e628009daab85ea4bccab36408722d205 11781 linux86_0.16.17-3.4.diff.gz 33480eecee840b2f79b7fb422c991f7d6868c71f 4768 linux86_0.16.17-3.4_source.buildinfo Checksums-Sha256: 6cd878afc1386135cb6cc44f620e0c83b202337e0469faec53335a813cb90366 1710 linux86_0.16.17-3.4.dsc dc9e588faa8bea0540d0c612082a7f8fa84998b6816673acdf0fe7a537cb5fea 11781 linux86_0.16.17-3.4.diff.gz 47fdc7d33015ab29b106b20ca2a63937242aed889981239cf6953dd797dbf97a 4768 linux86_0.16.17-3.4_source.buildinfo Files: 5b7ac3c520dad0fe7fa61f9a9162911f 1710 devel optional linux86_0.16.17-3.4.dsc 97db56f7b2311b2bc5388c03eda4 11781 devel optional linux86_0.16.17-3.4.diff.gz 103154abafaee7b12ce1313e92df89f0 4768 devel optional linux86_0.16.17-3.4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmLh0Y4ACgkQXBPW25MF LgNsaQ/9EBrEMMmya34gjime7qQkIwzxjDfm7G7KSGFeAjbfMwtnmKy2vF+c5mrs DFhKyFXSlP0pbVSM5jP4q/MGfQmmlnJNjbYfHlPZn7Ok65/dDG3jMuvbjuBQCDvi nxgmZfpak46POI7dRYIWDY06sj18vumrIy8NVmlNW9BXKFxaR7PM/VS62wX7UGz1 P3qZE/eeRmswKJLJtRIRQkuw/QSDZGRG4mu7Accie6A3BOsZYZ3gFtyM+vU7YoIj WOVQQZBCzeykPIvknXwuOdIzImSN8pShWhdg/Ht3ar1lQfiAWnzR+EO1bWCxNJ90 IslKn5PzcMMJkRUuIerKTjrr7hLMl5mEuAVWz3Mtki/9uvC403LX2xK2VLgF64AX TthmmqmcKDMk/b1AfIoozH9ovIWql2+t/40b5Tcr8pvaPRCrhaYDBu1LYLPrcUTI 2Swzdp7gWc6x0a1tDUsgwDy/hXFLMsKCHFmBclzm3K0KwBQ/R44YyKnuuIHoi0GD LV5km9pDOQBkTmAdaHQRJ7c+ci1wh+PGbHmM+r4jo+r9TIgyFh3PZfAnrXnWUEgl 1NlwK8wPZx5VCneq9NhxW2RJf68EjkgR2Ud3dCwuf+aIoi1aKKh8Bo9XKG01eOZM S++fKskqUeldyPOTnZ13nP54DNpJzz5YwysVQtw8FDgWIhWMJ+Y= =K8j7 -END PGP SIGNATURE End Message ---
Processed: Re: Bug#1012021: [Pkg-javascript-devel] Bug#1012021: unreproducible here
Processing control commands: > reassign -1 webpack Bug #1012021 [yarnpkg] yarnpkg: segfault while building greenbone-security-assistant on !amd64 Bug reassigned from package 'yarnpkg' to 'webpack'. No longer marked as found in versions node-yarnpkg/1.22.19+~cs24.27.18-1. Ignoring request to alter fixed versions of bug #1012021 to the same values previously set -- 1012021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012021: [Pkg-javascript-devel] Bug#1012021: unreproducible here
Control: reassign -1 webpack > greenbone-security-assistant/node_modules/webpack/lib/util/createHash.js ... > >>> code: 'ERR_OSSL_EVP_UNSUPPORTED' ... This appears to be caused by OpenSSL disabling md4. C.f. https://stackoverflow.com/a/69476335/2298386 Either this is already fixed in webpack, or webpack needs to fix it. Chris
Processed: 996039 xinput is surely related to xorg
Processing commands for cont...@bugs.debian.org: > # does not "break unrelated software" > severity 996039 normal Bug #996039 [xorg] xorg: Insignia Tablet, NS-P10W8100, touchpad upside down/inverted, using Mate/lighdm. Severity set to 'normal' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 996039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996039 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 994758 is forwarded to https://github.com/doug-gilbert/sg3_utils/issues/19
Processing commands for cont...@bugs.debian.org: > forwarded 994758 https://github.com/doug-gilbert/sg3_utils/issues/19 Bug #994758 [libsgutils2-2] Soname change without package name change Set Bug forwarded-to-address to 'https://github.com/doug-gilbert/sg3_utils/issues/19'. > thanks Stopping processing here. Please contact me if you need assistance. -- 994758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961283: marked as done (libhttp-tiny-perl: Don't release with bullseye)
Your message dated Thu, 28 Jul 2022 01:24:56 +0200 with message-id and subject line Re: Bug#961283: libhttp-tiny-perl: Don't release with bullseye has caused the Debian Bug report #961283, regarding libhttp-tiny-perl: Don't release with bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 961283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libhttp-tiny-perl Version: 0.076-1 Severity: serious Justification: maintainer libhttp-tiny-perl at this version should not be released with bullseye, since perl contains the same version. --- End Message --- --- Begin Message --- Version: 0.080-1 On Fri, 22 May 2020 16:15:31 +0100, Dominic Hargreaves wrote: > libhttp-tiny-perl at this version should not be released with > bullseye, since perl contains the same version. I'm closing this bug now with version 0.080-1, as¹: v5.32.00.076 v5.32.10.076 v5.34.00.076 v5.34.10.076 v5.36.00.080 so 0.80 is newer than what is in bullseye (5.32) and the current bookworm (5.34); and I'm about to upload 0.82 now which is newer than what we can expect to be in the released bookworm (5.36). Cheers, gregor ¹ corelist -a HTTP::Tiny -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature --- End Message ---
Bug#938850: unarchiving 938850, reopening 938850, unarchiving 947278, reopening 947278
Hi Paul, * Paul Wise [210726 04:00]: > # src:xmlelements was reintroduced: > https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org [..] > Not sure how you determined this, but it looks like src:xmlelements is not in unstable/experimental now? Maybe the bugs want to be closed again? Thanks, Chris
Processed: golang-github-pkg-term: FTBFS in bullseye
Processing commands for cont...@bugs.debian.org:
> reopen 1002231
Bug #1002231 {Done: Stephen Gelman }
[src:golang-github-pkg-term] golang-github-pkg-term: FTBFS: dh_auto_test:
error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/pkg/term
github.com/pkg/term/termios returned exit code 1
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions golang-github-pkg-term/1.1.0-4.
> found 1002231 1.1.0-3
Bug #1002231 [src:golang-github-pkg-term] golang-github-pkg-term: FTBFS:
dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4
github.com/pkg/term github.com/pkg/term/termios returned exit code 1
Ignoring request to alter found versions of bug #1002231 to the same values
previously set
> fixed 1002231 1.1.0-4
Bug #1002231 [src:golang-github-pkg-term] golang-github-pkg-term: FTBFS:
dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4
github.com/pkg/term github.com/pkg/term/termios returned exit code 1
Marked as fixed in versions golang-github-pkg-term/1.1.0-4.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1002231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1002231: golang-github-pkg-term: FTBFS in bullseye
reopen 1002231 found 1002231 1.1.0-3 fixed 1002231 1.1.0-4 thanks Hi. Since packages in stable must build in stable and this happens in bullseye as well, please consider an upload for bullseye (or tell me how I can help to have this fixed in bullseye). Thanks.
Processed: Re: Bug#948318: openssh-server: Unable to restart sshd restart after upgrade to version 8.1p1-2
Processing control commands: > reassign -1 glibc Bug #948318 [openssh-server] openssh-server: Unable to restart sshd restart after upgrade to version 8.1p1-2 Bug reassigned from package 'openssh-server' to 'glibc'. No longer marked as found in versions openssh/1:8.1p1-2. Ignoring request to alter fixed versions of bug #948318 to the same values previously set -- 948318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#948318: openssh-server: Unable to restart sshd restart after upgrade to version 8.1p1-2
Control: reassign -1 glibc Dear glibc Maintainers, this bug appears to be an upgrade issue where (old versions?) of libc6 might have done something wrong. Maybe you can decide what to do with/about this bug. It does not look like openssh-server would be the right place to fix anything about it. Chris
Bug#977765: [Pkg-fonts-devel] Bug#977765: src:gsfonts: package superseded by fonts-urw-base35
* Fabian Greffrath [220727 23:01]: [..] > My stance on this: In theory it should be technically possible to replace > the gsfonts (and gsfonts-x11) package with fonts-urw-base35 and I believe > this would be the right step, given that the latter font set is actively > maintained and extended - and actually used by ghostscript both upstream and > in Debian. And as a matter of fact, I have prepared this transition since I > uploaded the fonts-urw-base35 package for the first time. So, why haven't I > triggered this transition yet? [..] > So, to summarize: Yes, I think we should replace gsfonts+gsfonts-x11 with > fonts-urw-base35 at a given time and this transition is already prepared for > the most part. But I don't see this as a pressing issue right now, given the > lack of real-world issues this apparently causes, given the lack of bug > reports we received during the past 5 years - and given how late in the > release cycle we are to introduce a potentially disruptive change like this. Maybe now is the time? Chris
Bug#994355: marked as done (python-ldap: Removal of the python3-*-dbg packages in sid/bookworm)
Your message dated Thu, 28 Jul 2022 00:57:23 +0200 with message-id <20220727225723.hbst5wcmtbiaz...@zeha.at> and subject line #994355: python-ldap: Removal of the python3-*-dbg packages in sid/bookworm has caused the Debian Bug report #994355, regarding python-ldap: Removal of the python3-*-dbg packages in sid/bookworm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 994355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-ldap Version: 3.2.0-4 Severity: serious Tags: sid bookworm User: debian-pyt...@lists.debian.org Usertags: pydbg-removal Python 3.8 upstream now has a common ABI for normal and debug extension builds, so we can drop the python3-*-dbg packages. Details at https://lists.debian.org/debian-python/2021/09/msg4.html Stop building the python3-*-dbg package, but be careful that all the reverse dependencies are also removed. Please check for dependencies, build dependencies AND autopkg tests. If help is needed, please ask on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 3.4.0-1~exp1 Quoting the changelog: python-ldap (3.4.0-1~exp1) experimental; urgency=low [..] * Replace python3-ldap-dbg with python3-ldap-dbgsym. -- Michael Fladischer Sat, 15 Jan 2022 20:40:07 +--- End Message ---
Bug#936765: marked as done (jinja2: Python2 removal in sid/bullseye)
Your message dated Thu, 28 Jul 2022 00:44:57 +0200 with message-id <20220727224457.acv22gfjtndph...@zeha.at> and subject line #936765: jinja2: Python2 removal in sid/bullseye has caused the Debian Bug report #936765, regarding jinja2: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 936765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936765 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:jinja2 Version: 2.10.1-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:jinja2 If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 3.0.1-1 Quoting the 3.0.1-1 changelog: jinja2 (3.0.1-1) experimental; urgency=medium [ Thomas Goirand ] [..] * Killed the python2 package. -- Thomas Goirand Fri, 17 Sep 2021 23:25:00 +0200--- End Message ---
Processed: unarchive bug which happens in stable
Processing commands for cont...@bugs.debian.org:
> unarchive 1002231
Bug #1002231 {Done: Stephen Gelman }
[src:golang-github-pkg-term] golang-github-pkg-term: FTBFS: dh_auto_test:
error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/pkg/term
github.com/pkg/term/termios returned exit code 1
Unarchived Bug 1002231
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1002231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: linklint: diff for NMU version 2.3.5-5.3
Processing control commands: > tags 999260 + patch Bug #999260 [src:linklint] linklint: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999260 + pending Bug #999260 [src:linklint] linklint: missing required debian/rules targets build-arch and/or build-indep Added tag(s) pending. -- 999260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999260 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016132: marked as done (perlindex: autopkgtest regression: Failed test 1 in t/basic.t at line 48)
Your message dated Wed, 27 Jul 2022 21:34:53 + with message-id and subject line Bug#1016132: fixed in perlindex 1.606-3 has caused the Debian Bug report #1016132, regarding perlindex: autopkgtest regression: Failed test 1 in t/basic.t at line 48 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.) -- 1016132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016132 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: perlindex Version: 1.606-2 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of perlindex the autopkgtest of perlindex fails in testing when that autopkgtest is run with the binary packages of perlindex from unstable. It passes when run with only packages from testing. In tabular form: passfail perlindex from testing1.606-2 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=perlindex https://ci.debian.net/data/autopkgtest/testing/amd64/p/perlindex/23178942/log.gz t/basic.t .. 1..2 # Running under perl version 5.034000 for linux # Current time local: Wed Jun 29 09:45:34 2022 # Current time GMT: Wed Jun 29 09:45:34 2022 # Using Test.pm version 1.31 not ok 1 # Failed test 1 in t/basic.t at line 48 not ok 2 # Failed test 2 in t/basic.t at line 54 Failed 2/2 subtests Test Summary Report --- t/basic.t (Wstat: 0 Tests: 2 Failed: 2) Failed tests: 1-2 Files=1, Tests=2, 0 wallclock secs ( 0.03 usr 0.00 sys + 0.03 cusr 0.00 csys = 0.06 CPU) Result: FAIL autopkgtest [09:45:34]: test autodep8-perl-build-deps OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: perlindex Source-Version: 1.606-3 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of perlindex, 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 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated perlindex 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: Wed, 27 Jul 2022 21:55:22 +0200 Source: perlindex Architecture: source Version: 1.606-3 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 1016132 Changes: perlindex (1.606-3) unstable; urgency=medium . * autopkgests: skip smoke test. t/basic.t either needs the source tree or a complete rewrite to work with the installed package. (Closes: #1016132) * autopkgtests: add debian/tests/pkg-perl/use-name to enable use.t. * Update years of packaging copyright. * Declare compliance with Debian Policy 4.6.1. * Set Rules-Requires-Root: no. Checksums-Sha1: 3ab139f683c7b35cc4bd1003a69697a1605cc09b 2372 perlindex_1.606-3.dsc 183c9df1da92234a1ebb3989ab296cfeba98009d 10352 perlindex_1.606-3.debian.tar.xz Checksums-Sha256: 6a63ddd175894bacab832ae30467cc4643134fc0244df8dcb8bdc7799a1b8eba 2372 perlindex_1.606-3.dsc af5f2b279d826fd2ff27ffa4dc215e50cd4bf7cb549c229f2a4986525ebc0883 10352 perlindex_1.606-3.debian.tar.xz Files: 241c24b9cf16a79835baee496fbb1a7e 2372 perl optional perlindex_1.606-3.dsc 9d32c511d0373950ad93d9be2b22c258 10352 perl optional perlindex_1.606-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmLhmPBfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgYGIw//VLcRinZ7mGfC7483y5Ll25l+/A5zcYRwiRAwtfeGtLC6sWsa5IiJ5CSb WK6GZas1RQgBNpwn7v+EWVIWT8HkFdXUGJ/xHacZxpcVsDqmPPp/y9lmFco+HtVl lTnICCXS2eIFcxfYJ7Kv0j1UalxE4IR0Gfgs/bLjrfCZxBJrTuhXbfDZ8eu3iCfp
Bug#961834: clearlooks-phenix-theme
On Fri, Jul 22, 2022 at 10:30 AM David Daynard wrote: > This package is unmaintained upstream since 2016. There is a maintained fork > at https://github.com/jsane-h8ms/clearlooks-phenix which adds support for > using the theme under Mate as well as removing the many GTK deprecation > warnings this theme currently creates. > > This should fix most of the other open bugs against this package as well. Could you ask the fork maintainer if they'd be willing to tag a new release? Thank you, Jeremy Bicha
Bug#1016140: rails: CVE-2022-32224
Source: rails X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for rails. CVE-2022-32224[0]: https://github.com/advisories/GHSA-3hhc-qp5v-9p2j If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-32224 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32224 Please adjust the affected versions in the BTS as needed.
Bug#1016139: net-snmp: CVE-2022-24810 CVE-2022-24809 CVE-2022-24808 CVE-2022-24807 CVE-2022-24806 CVE-2022-24805
Source: net-snmp X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for net-snmp. 5.9.3 fixes the following issues: - These two CVEs can be exploited by a user with read-only credentials: - CVE-2022-24805 A buffer overflow in the handling of the INDEX of NET-SNMP-VACM-MIB can cause an out-of-bounds memory access. - CVE-2022-24809 A malformed OID in a GET-NEXT to the nsVacmAccessTable can cause a NULL pointer dereference. - These CVEs can be exploited by a user with read-write credentials: - CVE-2022-24806 Improper Input Validation when SETing malformed OIDs in master agent and subagent simultaneously - CVE-2022-24807 A malformed OID in a SET request to SNMP-VIEW-BASED-ACM-MIB::vacmAccessTable can cause an out-of-bounds memory access. - CVE-2022-24808 A malformed OID in a SET request to NET-SNMP-AGENT-MIB::nsLogTable can cause a NULL pointer dereference - CVE-2022-24810 A malformed OID in a SET to the nsVacmAccessTable can cause a NULL pointer dereference. - To avoid these flaws, use strong SNMPv3 credentials and do not share them. If you must use SNMPv1 or SNMPv2c, use a complex community string and enhance the protection by restricting access to a given IP address range. - Thanks are due to Yu Zhang of VARAS@IIE and Nanyu Zhong of VARAS@IIE for reporting the following CVEs that have been fixed in this release, and to Arista Networks for providing fixes. Please adjust the affected versions in the BTS as needed.
Bug#1015028: marked as pending in celery
Control: tag -1 pending Hello, Bug #1015028 in celery 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/python-team/packages/celery/-/commit/b7cdb430274319a69be2aeec1252a3e52027a1ce Add upstream patch to fix compatibility with billiard 4 (Closes: #1015028). (this message was generated automatically) -- Greetings https://bugs.debian.org/1015028
Processed: Bug#1015028 marked as pending in celery
Processing control commands: > tag -1 pending Bug #1015028 [src:celery] celery: FTBFS: test failures due to billiard upgrade: ImportError: cannot import name 'buf_t' from 'billiard.compat' Added tag(s) pending. -- 1015028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015028 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libmad: diff for NMU version 0.15.1b-10.1
Processing control commands: > tags 965663 + patch Bug #965663 [src:libmad] libmad: Removal of obsolete debhelper compat 5 and 6 in bookworm Ignoring request to alter tags of bug #965663 to the same tags previously set > tags 965663 + pending Bug #965663 [src:libmad] libmad: Removal of obsolete debhelper compat 5 and 6 in bookworm Ignoring request to alter tags of bug #965663 to the same tags previously set > tags 990838 + pending Bug #990838 [libmad0-dev] libmad0-dev: Library version in pkgconfig is not updated Ignoring request to alter tags of bug #990838 to the same tags previously set -- 965663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965663 990838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libmad: diff for NMU version 0.15.1b-10.1
Processing control commands: > tags 965663 + patch Bug #965663 [src:libmad] libmad: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965663 + pending Bug #965663 [src:libmad] libmad: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) pending. > tags 990838 + pending Bug #990838 [libmad0-dev] libmad0-dev: Library version in pkgconfig is not updated Added tag(s) pending. -- 965663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965663 990838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013578: golang-github-prometheus-exporter-toolkit: FTBFS in bullseye
found 1013578 0.5.1-2 thanks This also happens in stable.
Processed: golang-github-prometheus-exporter-toolkit: FTBFS in bullseye
Processing commands for cont...@bugs.debian.org: > found 1013578 0.5.1-2 Bug #1013578 [src:golang-github-prometheus-exporter-toolkit] golang-github-prometheus-exporter-toolkit: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/prometheus/exporter-toolkit/web github.com/prometheus/exporter-toolkit/web/kingpinflag returned exit code 1 Marked as found in versions golang-github-prometheus-exporter-toolkit/0.5.1-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1013578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unarchive because it happens in stable
Processing commands for cont...@bugs.debian.org:
> unarchive 1002783
Bug #1002783 {Done: Nilesh Patra }
[src:golang-github-biogo-graph] golang-github-biogo-graph: FTBFS: dh_auto_test:
error: cd _build && go test -vet=off -v -p 4 github.com/biogo/graph returned
exit code 1
Unarchived Bug 1002783
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1002783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1016133: fpga-icestorm: autopkgtest regression: new test can't be run on s390x due to missing yosys
Source: fpga-icestorm Version: 0~20220603git2bc5417-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of fpga-icestorm the autopkgtest of fpga-icestorm fails in testing when that autopkgtest is run with the binary packages of fpga-icestorm from unstable. It passes when run with only packages from testing. In tabular form: passfail fpga-icestorm from testing0~20220603git2bc5417-1 all others from testingfrom testing I copied some of the output at the bottom of this report. It seems to need to mark your new test to be not executed on s390x. You can do so by adding an "Architecture: !s390x" line to the new test definition in d/t/control. 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=fpga-icestorm https://ci.debian.net/data/autopkgtest/testing/s390x/f/fpga-icestorm/24083107/log.gz Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) autopkgtest-satdep:s390x < 0 @iU K Nb Ib > Broken autopkgtest-satdep:s390x Depends on yosys:s390x < none @un H > Removing autopkgtest-satdep:s390x because I can't find yosys:s390x Done OpenPGP_signature Description: OpenPGP digital signature
Processed: Fwd: libbluray: FTBFS in bullseye: error: BDFileSystemImpl is not abstract and does not override abstract method isInvalid(File) in FileSystem
Processing commands for cont...@bugs.debian.org:
> reopen 1011716
Bug #1011716 {Done: Sebastian Ramacher } [src:libbluray]
libbluray: FTBFS: [javac]
/<>/src/libbluray/bdj/java-j2se/java/io/BDFileSystemImpl.java:21:
error: BDFileSystemImpl is not abstract and does not override abstract method
isInvalid(File) in FileSystem
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libbluray/1:1.3.1-2.
> found 1011716 1:1.2.1-4+deb11u1
Bug #1011716 [src:libbluray] libbluray: FTBFS: [javac]
/<>/src/libbluray/bdj/java-j2se/java/io/BDFileSystemImpl.java:21:
error: BDFileSystemImpl is not abstract and does not override abstract method
isInvalid(File) in FileSystem
Marked as found in versions libbluray/1:1.2.1-4+deb11u1.
> fixed 1011716 1:1.3.1-2
Bug #1011716 [src:libbluray] libbluray: FTBFS: [javac]
/<>/src/libbluray/bdj/java-j2se/java/io/BDFileSystemImpl.java:21:
error: BDFileSystemImpl is not abstract and does not override abstract method
isInvalid(File) in FileSystem
Marked as fixed in versions libbluray/1:1.3.1-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1011716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011716
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1016132: perlindex: autopkgtest regression: Failed test 1 in t/basic.t at line 48
Source: perlindex Version: 1.606-2 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of perlindex the autopkgtest of perlindex fails in testing when that autopkgtest is run with the binary packages of perlindex from unstable. It passes when run with only packages from testing. In tabular form: passfail perlindex from testing1.606-2 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=perlindex https://ci.debian.net/data/autopkgtest/testing/amd64/p/perlindex/23178942/log.gz t/basic.t .. 1..2 # Running under perl version 5.034000 for linux # Current time local: Wed Jun 29 09:45:34 2022 # Current time GMT: Wed Jun 29 09:45:34 2022 # Using Test.pm version 1.31 not ok 1 # Failed test 1 in t/basic.t at line 48 not ok 2 # Failed test 2 in t/basic.t at line 54 Failed 2/2 subtests Test Summary Report --- t/basic.t (Wstat: 0 Tests: 2 Failed: 2) Failed tests: 1-2 Files=1, Tests=2, 0 wallclock secs ( 0.03 usr 0.00 sys + 0.03 cusr 0.00 csys = 0.06 CPU) Result: FAIL autopkgtest [09:45:34]: test autodep8-perl-build-deps OpenPGP_signature Description: OpenPGP digital signature
Bug#1011716: Fwd: libbluray: FTBFS in bullseye: error: BDFileSystemImpl is not abstract and does not override abstract method isInvalid(File) in FileSystem
reopen 1011716 found 1011716 1:1.2.1-4+deb11u1 fixed 1011716 1:1.3.1-2 thanks Hi. Since packages in stable must build in stable and this happens in bullseye as well, please consider an upload for bullseye (or tell me how I can help to have this fixed in bullseye). Thanks.
Processed: unarchive as it happens in stable
Processing commands for cont...@bugs.debian.org:
> unarchive 1011716
Bug #1011716 {Done: Sebastian Ramacher } [src:libbluray]
libbluray: FTBFS: [javac]
/<>/src/libbluray/bdj/java-j2se/java/io/BDFileSystemImpl.java:21:
error: BDFileSystemImpl is not abstract and does not override abstract method
isInvalid(File) in FileSystem
Unarchived Bug 1011716
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1011716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011716
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Processed (with 1 error): adjust the bts situation more to reality
Processing commands for cont...@bugs.debian.org: > tag 1010814 ftbfs Bug #1010814 [src:faketime] src:faketime: fails to migrate to testing for too long: FTBFS on 32 bit architectures Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1010814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016129: [fgont/ipv6toolkit] Cannot send packets in one direction (other works) (Issue #78)
Cc libpcap maintainers; context is #1016129 on debbugs. From diffing around between a buster and a bullseye system, I could track this bug down: libpcap0.8: 1.10.0-2 500 500 http://deb.debian.org/debian bullseye/main amd64 Packages 1.10.0-2~bpo10+1 100 100 http://deb.debian.org/debian buster-backports/main amd64 Packages 1.8.1-6+deb10u1 500 500 http://deb.debian.org/debian buster/main amd64 Packages Installing 1.10.0-2~bpo10+1 on buster breaks ipv6toolkit. Installing 1.10.0-2~bpo10+1 on bullseye does not fix ipv6toolkit, installing 1.8.1-6+deb10u1 on bullseye (which temporarily breaks tcpdump) does fix ipv6toolkit. So there’s either something in the newer libpcap that breaks ipv6toolkit, or something in ipv6toolkit that’s not yet compatible with newer libpcap. bye, //mirabilos -- Yay for having to rewrite other people's Bash scripts because bash suddenly stopped supporting the bash extensions they make use of -- Tonnerre Lombard in #nosec
Bug#1012674: zlib: contrib/testzlib included (lintian: source-ships-excluded-file)
On Wed, Jul 27, 2022 at 09:00:09PM +0200, vollan...@gmail.com wrote: > There is no licence on this code, it is juste free!! If that's the goal they should have a clear statement that they're in the public domain, without an explicit license grant of some kind the default is that things are copyrighted and all rights reserved. signature.asc Description: PGP signature
Processed (with 1 error): adjust the bts situation more to reality
Processing commands for cont...@bugs.debian.org:
> reopen 1010814
Bug #1010814 {Done: Paul Gevers } [src:faketime]
src:faketime: fails to migrate to testing for too long: FTBFS on 32 bit
architectures
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions faketime/0.9.10-2.
> tag 1010814 ftfbs
Unknown tag/s: ftfbs.
Recognized are: patch wontfix moreinfo unreproducible help security upstream
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye
bullseye-ignore bookworm bookworm-ignore trixie trixie-ignore.
> thank
Stopping processing here.
Please contact me if you need assistance.
--
1010814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1012674: zlib: contrib/testzlib included (lintian: source-ships-excluded-file)
Hello There is no licence on this code, it is juste free!! Regards Gilles Vollant -Message d'origine- De : Bastian Germann Envoyé : samedi 11 juin 2022 16:32 À : sub...@bugs.debian.org Objet : Bug#1012674: zlib: contrib/testzlib included (lintian: source-ships-excluded-file) Source: zlib Version: 1:1.2.11.dfsg-4 Severity: serious Justification: non-free source in main X-Debbugs-Cc: i...@winimage.com Hi! The contrib/testzlib files by Gilles Vollant are rightfully marked to be excluded from Debian by d/copyright because they are unlicensed and thus non-free. While 1:1.2.8.dfsg-5 still excluded the files, they have since reappeared. Please fix this with a new orig tarball. There is even a new upstream version 1.2.12 available which you could import and fix this without even changing the dfsg suffix! I have copied the original author who might shine a light on the supposed license. The zlib FAQ says that the contrib/ files have their own license but there is none for testzlib. Thanks, Bastian
Bug#1016110: marked as done (ruby3.1: reproducible builds: embeds path to various binaries)
Your message dated Wed, 27 Jul 2022 18:42:08 + with message-id and subject line Bug#1016110: fixed in ruby3.1 3.1.2-2 has caused the Debian Bug report #1016110, regarding ruby3.1: reproducible builds: embeds path to various binaries 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.) -- 1016110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby3.0 Severity: normal Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: usrmerge shell X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org The paths to various binaries, which differs on a usrmerge vs. non-usrmerge system, are embedded in rbconfig.rb: https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/ruby3.0.html /usr/lib/x86_64-linux-gnu/ruby/3.0.0/rbconfig.rb CONFIG["EGREP"]·=·"/bin/grep·-E" vs. CONFIG["EGREP"]·=·"/usr/bin/grep·-E" Patch attached which passes variables to configure to use the non-usrmerge locations, as usrmerge installations typically have compatibility symlinks, but not vice-versa. The patch also sets variables to ensure consistent values for bash, which can be triggered when /bin/sh points to bash. This patch alone does not fix all reproducibility issues (e.g. build paths on unstable and experimental), but should build reproducibly once it migrates to bookworm/testing! Thanks for maintaining ruby3.0! live well, vagrant From d0a1365cba685b8ab22be92463d28fb79d55a03b Mon Sep 17 00:00:00 2001 From: Vagrant Cascadian Date: Fri, 25 Feb 2022 23:17:08 + Subject: [PATCH] debian/rules: Pass variables to configure to make the package build reproducibly regardless of usrmerge. The variables EGREP, GREP, MAKEDIRS, MKDIR_P and SHELL should all point to their non-usrmerge locations. https://tests.reproducible-builds.org/debian/issues/paths_vary_due_to_usrmerge_issue.html --- debian/rules | 8 1 file changed, 8 insertions(+) diff --git a/debian/rules b/debian/rules index 76fa0b6..2d2c086 100755 --- a/debian/rules +++ b/debian/rules @@ -64,6 +64,14 @@ configure_options += --with-compress-debug-sections=no export DEB_BUILD_MAINT_OPTIONS = hardening=+bindnow optimize=-lto configure_options += $(shell dpkg-buildflags --export=configure) +# Pass variables to ensure consistent values when built on a usrmerge +# or non-usrmerge system. +configure_options += EGREP='/bin/grep -E' +configure_options += GREP='/bin/grep' +configure_options += MAKEDIRS='/bin/mkdir -p' +configure_options += MKDIR_P='/bin/mkdir -p' +configure_options += SHELL='/bin/sh' + # For more info see #999351 ifneq (,$(filter $(DEB_HOST_ARCH),alpha)) export DEB_CFLAGS_MAINT_APPEND += -O1 -- 2.30.2 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby3.1 Source-Version: 3.1.2-2 Done: Antonio Terceiro We believe that the bug you reported is fixed in the latest version of ruby3.1, 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 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro (supplier of updated ruby3.1 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: Wed, 27 Jul 2022 15:08:57 -0300 Source: ruby3.1 Architecture: source Version: 3.1.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Antonio Terceiro Closes: 1012247 1016110 Changes: ruby3.1 (3.1.2-2) unstable; urgency=medium . [ Antonio Terceiro ] * debian/rules: delete build artifacts from default gems * Drop ppc64el-specific test exclusions * debian/genprovides: don't generate ruby-rake * Stop providing ruby-ruby2-keywords for now ruby-ruby2-keywords is its own packages, and is now included in Ruby itself. If libruby3.1 Provides: ruby-ruby2-keywords, the actual binary will not be installed, and builds and tests will fail on ruby3.0 after ruby3.1 is added as a supported version: build dependency resolution will assume ruby-ruby2-keywords is provided by libruby3.1, and ruby3.0 will not actually have access to it.
Bug#1016131: libapache2-mod-jk: Apache does not start after upgrade (JkWorkersFile only allowed once)
Package: libapache2-mod-jk Version: 1:1.2.48-1 Severity: critical Justification: breaks unrelated software X-Debbugs-Cc: t...@mirbsd.de After upgrading from buster to bullseye, apache2 does not start any more if libapache2-mod-jk was installed and active prior to the upgrading: $ sudo cleanenv / /etc/init.d/apache2 start Starting Apache httpd web server: apache2 failed! The apache2 configtest failed. ... (warning). Output of config test was: AH00526: Syntax error on line 23 of /etc/apache2/mods-available/httpd-jk.conf: JkWorkersFile only allowed once Action 'configtest' failed. The Apache error log may have more information. This is caused by: $ sudo fgrep -ri JkWorkersFile /etc/ /etc/apache2/mods-available/jk.conf:JkWorkersFile /etc/libapache2-mod-jk/workers.properties /etc/apache2/mods-available/httpd-jk.conf:JkWorkersFile /etc/libapache2-mod-jk/workers.properties Both files exist… $ ll /etc/apache2/mods-available/jk.conf /etc/apache2/mods-available/httpd-jk.conf -rw-r--r-- 1 root root 4802 Oct 14 2018 /etc/apache2/mods-available/httpd-jk.conf -rw-r--r-- 1 root root 4802 Jun 4 2020 /etc/apache2/mods-available/jk.conf … and belong to the same package(!): $ dpkg -S /etc/apache2/mods-available/jk.conf /etc/apache2/mods-available/httpd-jk.conf libapache2-mod-jk: /etc/apache2/mods-available/jk.conf libapache2-mod-jk: /etc/apache2/mods-available/httpd-jk.conf My best guess is that the conffile was renamed but the renaming process was done improperly / violating Policy. As both files are identical… $ md5sum /etc/apache2/mods-available/jk.conf /etc/apache2/mods-available/httpd-jk.conf f6ebd56d10bf0dcb17d79b2133cb9f5c /etc/apache2/mods-available/jk.conf f6ebd56d10bf0dcb17d79b2133cb9f5c /etc/apache2/mods-available/httpd-jk.conf … I guess I can manually deactivate and remove one. Looking at https://packages.debian.org/bullseye/libapache2-mod-jk and https://packages.debian.org/bullseye/amd64/libapache2-mod-jk/filelist httpd-jk.conf seems to be the one that has to go (this is a hint for other people running into this issue). The root cause of this is that applications using mod_jk in buster had to do a workaround to load httpd-jk.conf due to #928813 so… # work around Debian #928813 # either /etc/apache2/conf-available/httpd-jk.conf with a2enconf httpd-jk # *or* /etc/apache2/mods-available/jk.conf with a2enmod jk # would be correct, but here we are Include /etc/apache2/mods-available/httpd-jk.conf … ends up loading this twice because the old file was not removed during the upgrade. $ sudo rm /etc/apache2/mods-available/httpd-jk.conf $ sudo cleanenv / /etc/init.d/apache2 start Starting Apache httpd web server: apache2 .. This helped, indeed. -- System Information: Debian Release: 11.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'oldstable-updates'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-21-amd64 (SMP w/3 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages libapache2-mod-jk depends on: ii apache2-bin [apache2-api-20120211] 2.4.54-1~deb11u1 ii libc6 2.31-13+deb11u3 libapache2-mod-jk recommends no packages. Versions of packages libapache2-mod-jk suggests: pn libapache-mod-jk-doc ii tomcat9 9.0.64-1wtf1 -- no debconf information
Bug#1016129: ipv6toolkit: Error while performing Neighbor Discovery for the Destination Address
Package: ipv6toolkit Version: 2.0+ds.1-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: t...@mirbsd.de Control: forwarded -1 https://github.com/fgont/ipv6toolkit/issues/78 $ sudo tcp6 -i eth1 -d fec0::1 -y 500 -a 13 -P 600 Error while performing Neighbor Discovery for the Destination Address Error while learning Souce Address and Next Hop $ sudo udp6 -i eth1 -d fe80::5054:ff:fe76:ba6 -y 500 -a 13 -P 600 -s fe80::5054:ff:feb7:47b9 Error while performing Neighbor Discovery for the Destination Address Error while learning Souce Address and Next Hop Background info: $ ip a show dev eth1 3: eth1: mtu 1500 qdisc jhtb state UP group default qlen 1000 link/ether 52:54:00:b7:47:b9 brd ff:ff:ff:ff:ff:ff altname enp0s7 altname ens7 inet 10.82.222.130/25 brd 10.82.222.255 scope global eth1 valid_lft forever preferred_lft forever inet6 fec0::2/64 scope site valid_lft forever preferred_lft forever inet6 fe80::5054:ff:feb7:47b9/64 scope link valid_lft forever preferred_lft forever $ ping6 fec0::1 PING fec0::1(fec0::1) 56 data bytes 64 bytes from fec0::1: icmp_seq=1 ttl=64 time=0.477 ms 64 bytes from fec0::1: icmp_seq=2 ttl=64 time=0.353 ms ^C --- fec0::1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 0.353/0.415/0.477/0.062 ms I suspect that this broke with the upgrade from buster to bullseye because it worked in one direction (fec0::2→1) before whereas the other didn’t (fec0::1 already ran bullseye). Downgrading just the ipv6toolkit package did not help. -- System Information: Debian Release: 11.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-16-amd64 (SMP w/3 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages ipv6toolkit depends on: ii ieee-data 20210605.1 ii libc6 2.31-13+deb11u3 ii libpcap0.8 1.10.0-2 ipv6toolkit recommends no packages. ipv6toolkit suggests no packages. -- no debconf information
Processed: ipv6toolkit: Error while performing Neighbor Discovery for the Destination Address
Processing control commands: > forwarded -1 https://github.com/fgont/ipv6toolkit/issues/78 Bug #1016129 [ipv6toolkit] ipv6toolkit: Error while performing Neighbor Discovery for the Destination Address Set Bug forwarded-to-address to 'https://github.com/fgont/ipv6toolkit/issues/78'. -- 1016129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013662: core-async-clojure: FTBFS randomly in bullseye
reopen 1013662 retitle 1013662 core-async-clojure: FTBFS randomly in bullseye found 1013662 1.3.610-4 fixed 1013662 1.3.610-6 thanks Hi. Since packages in stable must build in stable and this happens in bullseye as well, please consider an upload for bullseye (or tell me how I can help to have this fixed in bullseye). The package not only fails 100% of the time on single-CPU systems (which is already annoying enough), the build appears to be extremely unreliable on multi-core systems (it fails randomly around 50% of the time on my own autobuilders having 2 CPUs). Thanks.
Processed: core-async-clojure: FTBFS randomly in bullseye
Processing commands for cont...@bugs.debian.org:
> reopen 1013662
Bug #1013662 {Done: Jérôme Charaoui }
[src:core-async-clojure] core-async-clojure: FTBFS: make[1]: ***
[debian/rules:22: override_dh_auto_test] Error 1
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions core-async-clojure/1.3.610-6.
> retitle 1013662 core-async-clojure: FTBFS randomly in bullseye
Bug #1013662 [src:core-async-clojure] core-async-clojure: FTBFS: make[1]: ***
[debian/rules:22: override_dh_auto_test] Error 1
Changed Bug title to 'core-async-clojure: FTBFS randomly in bullseye' from
'core-async-clojure: FTBFS: make[1]: *** [debian/rules:22:
override_dh_auto_test] Error 1'.
> found 1013662 1.3.610-4
Bug #1013662 [src:core-async-clojure] core-async-clojure: FTBFS randomly in
bullseye
Marked as found in versions core-async-clojure/1.3.610-4.
> fixed 1013662 1.3.610-6
Bug #1013662 [src:core-async-clojure] core-async-clojure: FTBFS randomly in
bullseye
Marked as fixed in versions core-async-clojure/1.3.610-6.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1013662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: fixed 1013531 in 5.7.4-2
Processing commands for cont...@bugs.debian.org: > fixed 1013531 5.7.4-2 Bug #1013531 [src:maim] maim: FTBFS: unsatisfiable build-dependencies: libslopy7.6, libslopy-dev Marked as fixed in versions maim/5.7.4-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1013531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013531 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python2.7 removal severity
Processing commands for cont...@bugs.debian.org: > severity 938492 serious Bug #938492 [src:six] six: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 938168 serious Bug #938168 [src:python-setuptools] python-setuptools: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > severity 938198 serious Bug #938198 [src:python-stdlib-extensions] python-stdlib-extensions: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 938168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938168 938198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938198 938492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bump severity; we want python2.7 removed
Processing commands for cont...@bugs.debian.org: > severity 937085 serious Bug #937085 [src:mozilla-devscripts] mozilla-devscripts: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 937085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016127: src:guestfs-tools: fails to migrate to testing for too long: FTBFS on i386 and ppc64el
Source: guestfs-tools Version: 1.48.1-1 Severity: serious Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:guestfs-tools has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package failed to build from source on i386 and ppc64el while it built there successfully in the past. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=guestfs-tools OpenPGP_signature Description: OpenPGP digital signature
Bug#1016126: freeipa-server required libndr.so.1 and it's present only on Debian stable version
Package: freeipa-server Version: 4.9.8-1+exp1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: lu...@gnuabordo.com.br Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I tried to install freeipa-server just for testing environment. The environment is Debian fresh installation in lxc container. Installation ends up with an error when it try to create the REALM kdb5_util: Unable to load requested database module 'ipadb.so': plugin symbol 'kdb_function_table' not found while creating database '/var/lib/krb5kdc/principal' So I investigated the library required by ipadb.so ldd /usr/lib/x86_64-linux-gnu/krb5/plugins/kdb/ipadb.so it's noticed libndr.so.1 is required and not present. The required library is present by samba-libs on Debian bullseye, the stable version by now. Unstable and Sid version install libndr.so.2 in turn. *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-10-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages freeipa-server depends on: ii 389-ds-base 2.0.15-1+b1 ii acl 2.3.1-1 ii adduser 3.123 ii apache2 2.4.54-2 ii certmonger 0.79.15-1+b2 ii chrony 4.2-2 ii fonts-font-awesome 5.0.10+really4.7.0~dfsg-4.1 ii fonts-open-sans 1.11-2 ii freeipa-client 4.9.8-1+exp1 ii freeipa-common 4.9.8-1+exp1 ii gssproxy0.8.4-2 ii krb5-admin-server 1.20-1 ii krb5-kdc1.20-1 ii krb5-kdc-ldap 1.20-1 ii krb5-otp1.20-1 ii krb5-pkinit 1.20-1 ii ldap-utils 2.5.12+dfsg-2 ii libapache2-mod-auth-gssapi 1.6.3-1+b1 ii libapache2-mod-lookup-identity 1.0.0-1 ii libapache2-mod-wsgi-py3 4.9.0-1+b1 ii libc6 2.33-8 ii libgssapi-krb5-21.20-1 ii libjs-dojo-core 1.15.4+dfsg1-1 ii libjs-jquery3.6.0+dfsg+~3.5.13-1 ii libjs-scriptaculous 1.9.0-2.1 ii libk5crypto31.20-1 ii libkrad01.20-1 ii libkrb5-3 1.20-1 ii libldap-2.4-2 2.4.59+dfsg-1+b1 ii libnss3-tools 2:3.81-1 ii libpopt01.18-3 ii libpwquality1 1.4.4-1+b1 ii libsasl2-modules-gssapi-mit 2.1.28+dfsg-6 ii libssl1.1 1.1.1o-1 ii libsss-certmap0 2.7.3-1 ii libsss-nss-idmap0 2.7.3-1 ii libtalloc2 2.3.3-4 ii libunistring2 1.0-1 ii libuuid12.38-5 ii libverto1 0.3.1-1 ii libwbclient02:4.16.3+dfsg-1 ii oddjob 0.34.7-1 ii p11-kit 0.24.1-1 ii pki-ca 11.0.3-4 ii pki-kra 11.0.3-4 ii python3 3.10.5-3 ii python3-dateutil2.8.1-6 ii python3-gssapi 1.6.12-2+b1 ii python3-ipaserver 4.9.8-1+exp1 ii python3-ldap3.4.0-2+b1 ii python3-systemd 234-4+b1 ii samba-libs 2:4.16.3+dfsg-1 ii slapi-nis 0.56.7-1 ii ssl-cert1.1.2 ii sssd-dbus 2.7.3-1 ii systemd-sysv251.3-1 Versions of packages freeipa-server recommends: ii freeipa-server-dns 4.9.8-1+exp1 freeipa-server suggests no packages. -- no debconf information
Bug#1016026: marked as done (haskell-mono-traversable FTBFS on 32bit: test timeout)
Your message dated Wed, 27 Jul 2022 15:39:07 + with message-id and subject line Bug#1016026: fixed in haskell-mono-traversable 1.0.15.3-2 has caused the Debian Bug report #1016026, regarding haskell-mono-traversable FTBFS on 32bit: test timeout 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.) -- 1016026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-mono-traversable Version: 1.0.15.3-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=haskell-mono-traversable=1.0.15.3-1 ... Running debian/hlibrary.setup test --builddir=dist-ghc --show-details=direct E: Build killed with signal TERM after 150 minutes of inactivity Running dist-ghc/build/test/test manually: ... Containers Data.Map difference +++ OK, passed 100 tests. lookup +++ OK, passed 100 tests. insert +++ OK, passed 100 tests. delete +++ OK, passed 100 tests. singletonMap +++ OK, passed 100 tests. findWithDefault +++ OK, passed 100 tests. insertWith +++ OK, passed 100 tests. insertWithKey +++ OK, passed 100 tests. insertLookupWithKey +++ OK, passed 100 tests. adjustMap +++ OK, passed 100 tests. adjustWithKey +++ OK, passed 100 tests. updateMap +++ OK, passed 100 tests. updateWithKey +++ OK, passed 100 tests. updateLookupWithKey +++ OK, passed 100 tests. alter +++ OK, passed 100 tests. unionWith +++ OK, passed 100 tests. unionWithKey +++ OK, passed 100 tests. unionsWith +++ OK, passed 100 tests. mapWithKey +++ OK, passed 100 tests. omapKeysWith +++ OK, passed 100 tests. Data.IntMap difference +++ OK, passed 100 tests. lookup +++ OK, passed 100 tests. insert +++ OK, passed 100 tests. delete +++ OK, passed 100 tests. singletonMap +++ OK, passed 100 tests. findWithDefault +++ OK, passed 100 tests. insertWith +++ OK, passed 100 tests. insertWithKey +++ OK, passed 100 tests. insertLookupWithKey +++ OK, passed 100 tests. adjustMap +++ OK, passed 100 tests. adjustWithKey +++ OK, passed 100 tests. updateMap +++ OK, passed 100 tests. updateWithKey +++ OK, passed 100 tests. updateLookupWithKey +++ OK, passed 100 tests. alter +++ OK, passed 100 tests. unionWith +++ OK, passed 100 tests. unionWithKey +++ OK, passed 100 tests. unionsWith +++ OK, passed 100 tests. mapWithKey +++ OK, passed 100 tests. omapKeysWith +++ OK, passed 100 tests. Data.HashMap difference +++ OK, passed 100 tests. lookup +++ OK, passed 100 tests. insert +++ OK, passed 100 tests. delete +++ OK, passed 100 tests. singletonMap +++ OK, passed 100 tests. findWithDefault +++ OK, passed 100 tests. insertWith +++ OK, passed 100 tests. insertWithKey +++ OK, passed 100 tests. insertLookupWithKey +++ OK, passed 100 tests. adjustMap +++ OK, passed 100 tests. adjustWithKey +++ OK, passed 100 tests. updateMap +++ OK, passed 100 tests. updateWithKey +++ OK, passed 100 tests. updateLookupWithKey +++ OK, passed 100 tests. alter +++ OK, passed 100 tests. <-- no more output, and test runs with 100% CPU forever --> --- End Message --- --- Begin Message --- Source: haskell-mono-traversable Source-Version: 1.0.15.3-2 Done: Scott Talbert We believe that the bug you reported is fixed in the latest version of haskell-mono-traversable, 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 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Talbert (supplier of updated haskell-mono-traversable 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: Wed, 27 Jul 2022 11:01:18 -0400 Source: haskell-mono-traversable Architecture: source Version: 1.0.15.3-2
Bug#1012940: forwarded upstream
Control: forwarded -1 https://github.com/dl1ksv/gr-funcube/issues/7 I have forwarded the bug report to upstream. Sophie
Processed: forwarded upstream
Processing control commands: > forwarded -1 https://github.com/dl1ksv/gr-funcube/issues/7 Bug #1012940 [src:gr-funcube] gr-funcube: ftbfs with GCC-12 Set Bug forwarded-to-address to 'https://github.com/dl1ksv/gr-funcube/issues/7'. -- 1012940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006471: ruby3.0: reproducible builds: embeds path to various binaries
On Wed, 27 Jul 2022 at 08:49:27 -0300, Antonio Terceiro wrote: > > On Fri, 25 Feb 2022 at 15:26:51 -0800, Vagrant Cascadian wrote: > > > The paths to various binaries, which differs on a usrmerge > > > vs. non-usrmerge system, are embedded in rbconfig.rb: > > > > > > /usr/lib/x86_64-linux-gnu/ruby/3.0.0/rbconfig.rb > > > > > > CONFIG["EGREP"]·=·"/bin/grep·-E" > > > vs. > > > CONFIG["EGREP"]·=·"/usr/bin/grep·-E" > > > > If these CONFIG variables are used for something at runtime, then this > > will become a practical problem as soon as Debian starts using merged-/usr > > buildds. > > Those variables are read from config.status during the builds. Maybe > this should be fixed centrally in autoconf instead? autoconf is designed to support arbitrarily bad host OSs, including those that are non-POSIX or otherwise defective, where the only fully-functional grep might be /opt/sw/addons/misc/gnu/grep or something; so it has a tendency to discover a known-good absolute path and save that. This is great if you're building Ruby on an awful 1990s Unix machine and the result of AC_PROG_EGREP will only be used during build, or if it is used at runtime but you only plan to run the resulting Ruby binaries on that same machine, but it goes wrong when facts about the build system start to diverge from facts about the host system. In this case, the fact that is different is the merged-/usr status of the build system and the host system, but it could be almost anything. The macros that Ruby uses to find these commands are probably AC_PROG_GREP, AC_PROG_EGREP, etc., which are not explicitly documented to output an absolute path (the documentation just says "whatever is chosen"), but looking at their implementation, it seems they do: they are like AC_PATH_PROG rather than AC_CHECK_PROG. It's entirely possible that Ruby is not doing this deliberately, those macros might well be a dependency for something else. Is the Ruby build intentionally putting EGREP into rbconfig.rb for use by some other component, or is it just populating that file with everything that Autoconf happens to have discovered, on the off chance that it might become necessary at some point? If the latter, then that seems like it will cause unpredictable action-at-a-distance if Autoconf stops needing to discover some particular thing (for instance if Autoconf's maintainers decide that they are only going to support systems where the first grep in PATH is POSIX.1-2001 compliant, and stop checking for a possibly-better-quality grep elsewhere). smcv
Bug#1013053: marked as done (tinymux: ftbfs with GCC-12)
Your message dated Wed, 27 Jul 2022 13:34:19 + with message-id and subject line Bug#1013053: fixed in tinymux 2.12.0.10-1 has caused the Debian Bug report #1013053, regarding tinymux: ftbfs with GCC-12 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.) -- 1013053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:tinymux Version: 2.10.1.14-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/tinymux_2.10.1.14-1_unstable_gcc12.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. [...] _build.cpp:11:22: warning: macro "__DATE__" might prevent reproducible builds [-Wdate-time] 11 | char szBuildDate[] = __DATE__ " " __TIME__; | ^~~~ _build.cpp:11:35: warning: macro "__TIME__" might prevent reproducible builds [-Wdate-time] 11 | char szBuildDate[] = __DATE__ " " __TIME__; | ^~~~ g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O -DSTUB_SLAVE -c comsys.cpp g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O -DSTUB_SLAVE -c conf.cpp g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O -DSTUB_SLAVE -c cque.cpp g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O -DSTUB_SLAVE -c create.cpp g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O -DSTUB_SLAVE -c db.cpp g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O -DSTUB_SLAVE -c db_rw.cpp db.cpp: In function ‘void load_restart_db()’: db.cpp:3686:10: warning: ignoring return value of ‘char* fgets(char*, int, FILE*)’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 3686 | fgets(buf, 3, f); | ~^~~ g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O -DSTUB_SLAVE -c eval.cpp g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O -DSTUB_SLAVE -c file_c.cpp g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O -DSTUB_SLAVE -c flags.cpp g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O -DSTUB_SLAVE -c funceval.cpp g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O -DSTUB_SLAVE -c funceval2.cpp g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O -DSTUB_SLAVE -c
Bug#1013940: New version of nfft breaks its autopkgtest (Was: nfft breaks pynfft autopkgtest on i386: Segmentation fault
Andreas Tille writes: > [1] https://salsa.debian.org/science-team/nfft/-/jobs/3041717 | + gcc -Wall -DNFFT_PRECISION_SINGLE -lnfft3f -lfftw3f -o simple_test simple_test.c | /usr/bin/ld: /tmp/ccaUJ49M.o: in function `simple_test_nfft_1d': | simple_test.c:(.text+0x2c): undefined reference to `nfftf_init_1d' [...] Please try listing simple_test.c ahead of the libraries, which the linker otherwise discards as apparently unneeded. -- 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#1006471: ruby3.0: reproducible builds: embeds path to various binaries
Control: clone -1 -2 Control: reassign -2 src:ruby3.1 Control: retitle -2 ruby3.1: reproducible builds: embeds path to various binaries Hi, On Sun, Jul 17, 2022 at 12:04:45PM +0100, Simon McVittie wrote: > Control: severity -1 serious > > On Fri, 25 Feb 2022 at 15:26:51 -0800, Vagrant Cascadian wrote: > > The paths to various binaries, which differs on a usrmerge > > vs. non-usrmerge system, are embedded in rbconfig.rb: > > > > > > https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/ruby3.0.html > > > > /usr/lib/x86_64-linux-gnu/ruby/3.0.0/rbconfig.rb > > > > CONFIG["EGREP"]·=·"/bin/grep·-E" > > vs. > > CONFIG["EGREP"]·=·"/usr/bin/grep·-E" > > If these CONFIG variables are used for something at runtime, then this > will become a practical problem as soon as Debian starts using merged-/usr > buildds. The problem scenario is: > > - ruby3.0 is built on a merged-/usr buildd > - /usr/bin/grep is recorded in rbconfig.rb > - this build of ruby3.0 is installed on a non-merged-/usr system during > the upgrade from Debian 11 to Debian 12 > - whatever feature uses CONFIG["EGREP"] will not work, because > non-merged-/usr systems only have /bin/grep > > Technical Committee resolution > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994388#110 recommends > that this class of bug is treated as release-critical, so I'm raising the > severity of this bug report. > > If none of the affected CONFIG variables are actually used for anything > on installed systems, then the severity of this bug can be downgraded > to non-RC (but it would be better to fix it anyway, because reproducible > builds are a useful goal for other reasons). Those variables are read from config.status during the builds. Maybe this should be fixed centrally in autoconf instead? > > Patch attached which passes variables to configure to use the > > non-usrmerge locations, as usrmerge installations typically have > > compatibility symlinks, but not vice-versa. > > To clarify: in Debian, merged-/usr installations are *guaranteed* to > have these compatibility symlinks. The patch looks appropriate to me, > although I have not tested it. Sure. signature.asc Description: PGP signature
Processed: Re: Bug#1006471: ruby3.0: reproducible builds: embeds path to various binaries
Processing control commands: > clone -1 -2 Bug #1006471 [src:ruby3.0] ruby3.0: reproducible builds: embeds path to various binaries Bug 1006471 cloned as bug 1016110 > reassign -2 src:ruby3.1 Bug #1016110 [src:ruby3.0] ruby3.0: reproducible builds: embeds path to various binaries Bug reassigned from package 'src:ruby3.0' to 'src:ruby3.1'. Ignoring request to alter found versions of bug #1016110 to the same values previously set Ignoring request to alter fixed versions of bug #1016110 to the same values previously set > retitle -2 ruby3.1: reproducible builds: embeds path to various binaries Bug #1016110 [src:ruby3.1] ruby3.0: reproducible builds: embeds path to various binaries Changed Bug title to 'ruby3.1: reproducible builds: embeds path to various binaries' from 'ruby3.0: reproducible builds: embeds path to various binaries'. -- 1006471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006471 1016110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Fixed in unstable already
Processing commands for cont...@bugs.debian.org: > fixed #1016089 2.0.4-1 Bug #1016089 [src:mistune] mistune: CVE-2022-34749 Marked as fixed in versions mistune/2.0.4-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1016089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#951490: marked as done (haskell-yaml: please split yaml2json out into a separate package)
Your message dated Wed, 27 Jul 2022 11:35:51 + with message-id and subject line Bug#951490: fixed in haskell-yaml 0.11.8.0-1 has caused the Debian Bug report #951490, regarding haskell-yaml: please split yaml2json out into a separate package 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.) -- 951490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951490 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-yaml Version: 0.8.32-4+b1 Severity: wishlist /usr/bin/yaml2json is a potentially useful tool for many different people, not just haskell hackers. The dep chain for libghc-yaml-dev is quite large. On my system, it ruled out installing over a 3G network connection, even though I already have lots of Haskell dev packages installed. Please consider splitting it out into a separate binary package. -- System Information: Debian Release: 10.2 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Jonathan Dowland https://jmtd.net --- End Message --- --- Begin Message --- Source: haskell-yaml Source-Version: 0.11.8.0-1 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-yaml, 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 951...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated haskell-yaml 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: Wed, 27 Jul 2022 14:08:54 +0300 Source: haskell-yaml Architecture: source Version: 0.11.8.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Ilias Tsitsimpis Closes: 951490 Changes: haskell-yaml (0.11.8.0-1) unstable; urgency=medium . * New upstream release * Declare compliance with Debian policy 4.6.1 * Drop the yaml2json and json2yaml binaries (Closes: #951490) Checksums-Sha1: f8c7bb53eb5d2667b8e607017ddbb5b5302470a1 3249 haskell-yaml_0.11.8.0-1.dsc eaf94f872e4e554b558122f7f2d70bb559d11dd8 31674 haskell-yaml_0.11.8.0.orig.tar.gz bdec8ab18726eec10d8d9a474ab324a5a90d37d8 5216 haskell-yaml_0.11.8.0-1.debian.tar.xz 331fce5804abd6572674eb066a4f968d54ed7938 13498 haskell-yaml_0.11.8.0-1_amd64.buildinfo Checksums-Sha256: 701ad7a257d0ee8c4f59d98a95bbe38f8b08df2f6e6c558917e4cd9e10dc2c19 3249 haskell-yaml_0.11.8.0-1.dsc f61a4e829bb75e17f5da39ea7b9d8d221a100a0f0cb1258bb9584a1829cd0ae8 31674 haskell-yaml_0.11.8.0.orig.tar.gz 49c25a8b1f24a296394ab8708e08527de2dce518f0e1c42a2d079ec75e5e5da6 5216 haskell-yaml_0.11.8.0-1.debian.tar.xz 8b960d6c3240a475f88d4e17da6f7518674c2be836d483b8fd484b4d8ccd7ec1 13498 haskell-yaml_0.11.8.0-1_amd64.buildinfo Files: b6d199606c130611363b6b267303e56d 3249 haskell optional haskell-yaml_0.11.8.0-1.dsc 1e461cf28ed970106ae52a78ac4edd5c 31674 haskell optional haskell-yaml_0.11.8.0.orig.tar.gz 8df8cd27aee5d537a37cad9bab8c49fb 5216 haskell optional haskell-yaml_0.11.8.0-1.debian.tar.xz 6f88a51e3bd93a501a37e556c8ddbbff 13498 haskell optional haskell-yaml_0.11.8.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAmLhHs4UHGlsaWFzdHNp QGRlYmlhbi5vcmcACgkQ16hngMxkQDz/9xAAsBpY6f6RsEXhwjxkPrub9Zoe7V1i oYdUdfKivtKyo8gPdY+myizazQ35Gw6vNCMYvudK3irV++fgzDfxeNu0QLS1jhA5 W6SGgNTcaMRgzJkfkE8YDu44u2ct8oh6nMuXWV2fRWYPbSm2QZfPsKKA2aiVwc0y V7Igu/FiC3SlOm26VKepZuVvNjEsDlV3uWcvecoNRg7e4uPAA37LOde1cspC/1RK 8mZCw70zuBFGUfm3ejU1qy2kYup4eVTQeEUuOsMl+UgoHuDjCArJuS8n/b/Dqtiy sBFX0vh+AFKiB2sILwGl9/lh2v3mHYl87KAx3mRSv/9j4KGQrJ/Y71eryc13OUXx FWD3nw9NsNxrsbXsYea2kvkij3N0E/Djd7g4OwLwNyTLRfz6VaFTaWUB1cTxYWPa cAzyqSg454QeeXSdW4CQxcGvXt2Zp6eeh4C+WJxIZLvXwB6VSOpsInHtP5g+WWLo
Bug#1013940: New version of nfft breaks its autopkgtest (Was: nfft breaks pynfft autopkgtest on i386: Segmentation fault
Hi, I was tempted to upload the patch suggested by Bernhard which I applied to the commit of Ileana with the new upstream version. Unfortunately the new upstream version fails the autopkgtest[1] (which was the same when I tried version 3.5.2 which prevented me from uploading). Does anybody have a clue how to fix this? Kind regards Andreas. [1] https://salsa.debian.org/science-team/nfft/-/jobs/3041717 -- http://fam-tille.de
Bug#1015123: latex-cjk-chinese-arphic: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
Some observations: Going back to fontforge version 20201107~dfsg-4 and its dependencies, I notice the following warning message: 21900/1114292: Add extrema... Simplifying outlines... NaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creation22000/1114292: Add extrema... Simplifying outlines... A more recent version of Fontforge will just let the application hang. I will have to contact upstream to figure out what is causing this. -- Danai On Sun, 17 Jul 2022 at 16:15, Danai SAE-HAN (韓達耐) wrote: > Very interesting; font bkai gets stuck during the fontforge compilation at > 21900/1114292 and stays at 100% CPU usage. Other fonts seem fine. > This requires a bit more investigating. My gut tells me the recent > fontforge upload has a regression somewhere. > > -- > Danai > > On Sat, 16 Jul 2022 at 22:42, Danai SAE-HAN (韓達耐) > wrote: > >> Thanks Lucas, I'll look at it tonight. >> >> On Sat, 16 Jul 2022, 22:04 Lucas Nussbaum, wrote: >> >>> Source: latex-cjk-chinese-arphic >>> Version: 1.24 >>> Severity: serious >>> Justification: FTBFS >>> Tags: bookworm sid ftbfs >>> User: lu...@debian.org >>> Usertags: ftbfs-20220716 ftbfs-bookworm >>> >>> Hi, >>> >>> During a rebuild of all packages in sid, your package failed to build >>> on amd64. >>> >>> >>> Relevant part (hopefully): >>> > Reading subfont definition file >>> `/usr/share/texlive/texmf-dist/fonts/sfd/ttf2pk/Unicode.sfd'... >>> > Writing extended font definition file `c70bsmi.fdx'... >>> > >>> > # Remove the *.enc files; they're not used. >>> > ( cd build/bsmi00lp && rm -f *.enc ) >>> > >>> > # Create a Type1 font map. >>> > >>> > # Create entries for the font definition file >>> > # `c00bsmi.fd' (which uses UBig5 encoding). >>> > >>> > # Create entries for the font definition file >>> > # `c70bsmi.fd' (which uses Unicode encoding). >>> > >>> > touch build-stamp.bsmi >>> > E: Build killed with signal TERM after 150 minutes of inactivity >>> >>> >>> The full build log is available from: >>> >>> http://qa-logs.debian.net/2022/07/16/latex-cjk-chinese-arphic_1.24_unstable.log >>> >>> All bugs filed during this archive rebuild are listed at: >>> >>> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org >>> or: >>> >>> https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=lu...@debian.org=1=1=1=1#results >>> >>> A list of current common problems and possible solutions is available at >>> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to >>> contribute! >>> >>> If you reassign this bug to another package, please marking it as >>> 'affects'-ing >>> this package. See https://www.debian.org/Bugs/server-control#affects >>> >>> If you fail to reproduce this, please provide a build log and diff it >>> with mine >>> so that we can identify if something relevant changed in the meantime. >>> >>>
Bug#1016102: rsync: The --remove-source-files destroys data when source & destination are the same (data loss!)
Package: rsync Version: 3.2.3-4+deb11u1 Severity: critical Justification: causes serious data loss X-Debbugs-Cc: debbug.rs...@sideload.33mail.com I accidentally ran: $ rsync -va --progress --remove-source-files "$dir_with_many_files" "$dir_with_many_files" Due to a typo when using bash history substitution, the source and destination were both directories and they both named the same directory. The expectation is that rsync should detect movement from A to A and do nothing apart from warning the user that there is nothing to do. Instead, because of the “--remove-source-files” option, rsync DESTROYS all the files in "$dir_with_many_files" irrevokably. There needs to be a safeguard that prevents --remove-source-files from having effect if: * Files are not copied to the destination (for any reason) * The source and destination are the same I suffered data loss because of this. At the very least, if it’s really intended for “rsync --remove-source-files $A $A” to effectively behave like “rm -rf $A/*”, there AT LEAST needs to be a very loud warning prompting the user for confirmation. But I conjecture that there never is a legit scenario where “rsync --remove-source-files” simply destroys files without safely ensuring they exist somewhere in the end. -- System Information: Debian Release: 11.4 APT prefers stable-updates APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 'testing'), (990, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-16-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages rsync depends on: ii init-system-helpers 1.60 ii libacl1 2.2.53-10 ii libc62.31-13+deb11u3 ii liblz4-1 1.9.3-2 ii libpopt0 1.18-2 ii libssl1.11.1.1n-0+deb11u3 ii libxxhash0 0.8.0-2 ii libzstd1 1.4.8+dfsg-2.1 ii lsb-base 11.1.0 ii zlib1g 1:1.2.11.dfsg-2+deb11u1 rsync recommends no packages. Versions of packages rsync suggests: ii openssh-client 1:8.4p1-5+deb11u1 ii openssh-server 1:8.4p1-5+deb11u1 ii python3 3.9.2-3 -- no debconf information
Bug#1016067: marked as done (rpcbind installation fails due to missing user _rpc)
Your message dated Wed, 27 Jul 2022 10:07:32 + with message-id and subject line Bug#1016064: fixed in rpcbind 1.2.6-6 has caused the Debian Bug report #1016064, regarding rpcbind installation fails due to missing user _rpc 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.) -- 1016064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rpcbind Version: 1.2.6-4 Severity: grave Justification: renders package unusable Hi, since the d/postinst file has been removed, on a fresh VM rpcbind can no longer be installed: --8<-- root@kvmsid:~# apt install rpcbind Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: rpcbind 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 51.9 kB of archives. After this operation, 164 kB of additional disk space will be used. Get:1 http://ftp.de.debian.org/debian sid/main amd64 rpcbind amd64 1.2.6-5 [51.9 kB] Fetched 51.9 kB in 0s (242 kB/s) Selecting previously unselected package rpcbind. (Reading database ... 26717 files and directories currently installed.) Preparing to unpack .../rpcbind_1.2.6-5_amd64.deb ... Unpacking rpcbind (1.2.6-5) ... Setting up rpcbind (1.2.6-5) ... /usr/lib/tmpfiles.d/rpcbind.conf:2: Failed to resolve user '_rpc': No such process ^ Created symlink /etc/systemd/system/multi-user.target.wants/rpcbind.service → /lib/systemd/system/rpcbind.service. Created symlink /etc/systemd/system/sockets.target.wants/rpcbind.socket → /lib/systemd/system/rpcbind.socket. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145. -->8-- Executing the adduser command from the former postinst script manually and running `dpkg --configure -a` fixed the problem. Even though the migration path from postinst might be obsolete, creating the _rpc user isn't. Thanks, Daniel --- End Message --- --- Begin Message --- Source: rpcbind Source-Version: 1.2.6-6 Done: Josue Ortega We believe that the bug you reported is fixed in the latest version of rpcbind, 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 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josue Ortega (supplier of updated rpcbind 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: Wed, 27 Jul 2022 03:20:27 -0600 Source: rpcbind Architecture: source Version: 1.2.6-6 Distribution: unstable Urgency: medium Maintainer: Josue Ortega Changed-By: Josue Ortega Closes: 1016064 Changes: rpcbind (1.2.6-6) unstable; urgency=medium . * Add missing postinst script creating _rpc user (Closes: #1016064) Checksums-Sha1: c82600c0471db602be55b1535c13170d4b61a00b 1946 rpcbind_1.2.6-6.dsc e06b06f6b4d5d1b43fa1c57e7e6df41f59155eb4 12508 rpcbind_1.2.6-6.debian.tar.xz a8290f56d84a9c74a9e3b83302a20380f626e715 6149 rpcbind_1.2.6-6_amd64.buildinfo Checksums-Sha256: 37f2568e472462154d4b4f610beb961c3921a80aee71e8bc3fe2c73cce01681f 1946 rpcbind_1.2.6-6.dsc 10f0691a09fd6d174ac9d64cfe7c63786002b2fcbcff303b604e8c5b88cf1584 12508 rpcbind_1.2.6-6.debian.tar.xz 531a668e4cada06f710fb75eedf85f7a15a10c930adffb45eb01ef67018c8d71 6149 rpcbind_1.2.6-6_amd64.buildinfo Files: 9a6e988e91a1906b3968b68803735733 1946 net optional rpcbind_1.2.6-6.dsc 8aa93e384141a0e4da70b6ce79cf8135 12508 net optional rpcbind_1.2.6-6.debian.tar.xz 06b2e62f3dd3df58501fa6df10e6cef7 6149 net optional rpcbind_1.2.6-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAmLhBv4RHGpvc3VlQGRl Ymlhbi5vcmcACgkQAVCdXKtK/T+qRxAAgwnnQ7lxajPczEdO7VBCMXIKrMYIgOFH W2ufR3P04xJQFeWZTZntZcbvgEMZWznuNzvdNFkeKEbwHA+45ktGz8W2fMGMThLO +hx9pLd7xwnlEe3kbaF3iOF5WY9U4gl1EGsvjsoSbfK0kQaPJTDBr4gAGDroKDyY +gG1dkMr5UQfXJaz4Nz+oIK8BYs6IaeT1WTm3l96aDtXvY0PmXaUdxIbSmRYsiZ8 QMdJ8XPKq6OwWwc5CeTwNo8EIDCUkFrO4FW2txhF0hTC95mK4Xj90sVopMC0H1zb 4TyAMdg4wdxRKBCbxn81yPXAZ1jS11M802hZcU3vxNzyFRppVc8V40yloXKIxK1r
Bug#1016064: marked as done (rpcbind: rpcbind.service fails with "cannot get uid of '_rpc': Success")
Your message dated Wed, 27 Jul 2022 10:07:32 + with message-id and subject line Bug#1016064: fixed in rpcbind 1.2.6-6 has caused the Debian Bug report #1016064, regarding rpcbind: rpcbind.service fails with "cannot get uid of '_rpc': Success" 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.) -- 1016064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rpcbind Version: 1.2.6-4 Severity: serious A fresh installation of rpcbind fails to start the service: systemd[1]: Starting RPC bind portmap service... rpcbind[314]: cannot get uid of '_rpc': Success systemd[1]: rpcbind.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: rpcbind.service: Failed with result 'exit-code'. systemd[1]: Failed to start RPC bind portmap service. That's because the `_rpc` user does not exist. Upgrading from an earlier image (with 1.2.6-3) works because earlier versions created it: # id _rpc uid=108(_rpc) gid=65534(nogroup) groups=65534(nogroup) Release -4 said "Remove obsolete debian/postinst file", and most of it may be obsolete, but not this bit: if [ "$1" = configure ] ; then # run daemon as non-root (see #852066) adduser --force-badname --system --quiet --home /run/rpcbind --no-create-home _rpc Please put this back. Or better yet, use systemd's User=, DynamicUser=, and RuntimeDirectory= options to contain all of the setup in the unit. Thanks! Martin signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: rpcbind Source-Version: 1.2.6-6 Done: Josue Ortega We believe that the bug you reported is fixed in the latest version of rpcbind, 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 1016...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Josue Ortega (supplier of updated rpcbind 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: Wed, 27 Jul 2022 03:20:27 -0600 Source: rpcbind Architecture: source Version: 1.2.6-6 Distribution: unstable Urgency: medium Maintainer: Josue Ortega Changed-By: Josue Ortega Closes: 1016064 Changes: rpcbind (1.2.6-6) unstable; urgency=medium . * Add missing postinst script creating _rpc user (Closes: #1016064) Checksums-Sha1: c82600c0471db602be55b1535c13170d4b61a00b 1946 rpcbind_1.2.6-6.dsc e06b06f6b4d5d1b43fa1c57e7e6df41f59155eb4 12508 rpcbind_1.2.6-6.debian.tar.xz a8290f56d84a9c74a9e3b83302a20380f626e715 6149 rpcbind_1.2.6-6_amd64.buildinfo Checksums-Sha256: 37f2568e472462154d4b4f610beb961c3921a80aee71e8bc3fe2c73cce01681f 1946 rpcbind_1.2.6-6.dsc 10f0691a09fd6d174ac9d64cfe7c63786002b2fcbcff303b604e8c5b88cf1584 12508 rpcbind_1.2.6-6.debian.tar.xz 531a668e4cada06f710fb75eedf85f7a15a10c930adffb45eb01ef67018c8d71 6149 rpcbind_1.2.6-6_amd64.buildinfo Files: 9a6e988e91a1906b3968b68803735733 1946 net optional rpcbind_1.2.6-6.dsc 8aa93e384141a0e4da70b6ce79cf8135 12508 net optional rpcbind_1.2.6-6.debian.tar.xz 06b2e62f3dd3df58501fa6df10e6cef7 6149 net optional rpcbind_1.2.6-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAmLhBv4RHGpvc3VlQGRl Ymlhbi5vcmcACgkQAVCdXKtK/T+qRxAAgwnnQ7lxajPczEdO7VBCMXIKrMYIgOFH W2ufR3P04xJQFeWZTZntZcbvgEMZWznuNzvdNFkeKEbwHA+45ktGz8W2fMGMThLO +hx9pLd7xwnlEe3kbaF3iOF5WY9U4gl1EGsvjsoSbfK0kQaPJTDBr4gAGDroKDyY +gG1dkMr5UQfXJaz4Nz+oIK8BYs6IaeT1WTm3l96aDtXvY0PmXaUdxIbSmRYsiZ8 QMdJ8XPKq6OwWwc5CeTwNo8EIDCUkFrO4FW2txhF0hTC95mK4Xj90sVopMC0H1zb 4TyAMdg4wdxRKBCbxn81yPXAZ1jS11M802hZcU3vxNzyFRppVc8V40yloXKIxK1r duhiUZLo0RWdbkIT9bX5OAUEtoF5zz51rBKwPXrNCYp6NFvlgbpWAQUXs/LWr+j+ gJ6ixRCmoEiI+NPy/cqGrgGdvfQ0HG2mcV4q6o1Yr/OzagYxbYekGPArxGQnt1B9 bB2cbdCzwCkT0a5ybV/Ix7SCNsmlHID4Q9TpKqKRwBIqJJf60xr+fkNkZ8NvKGsn tXqWlZOnLKFsTL214zy97dh71epl58s0ddpRaHSoloiLptt1WKXYP5E5kuzVEA94 /IMW6MZDTFLUEhMZIvgEkyzgpje6+wIFl3RP1EU90kbVKGSHCUqzW1Mn5rG1ZReX lEC9gL0+VeM= =XZa+ -END PGP SIGNATURE End Message ---
Processed: severity 1016067 serious
Processing commands for cont...@bugs.debian.org: > severity 1016067 serious Bug #1016067 [rpcbind] rpcbind installation fails due to missing user _rpc Severity set to 'serious' from 'grave' > merge 1016067 1016064 Bug #1016067 [rpcbind] rpcbind installation fails due to missing user _rpc Bug #1016064 [rpcbind] rpcbind: rpcbind.service fails with "cannot get uid of '_rpc': Success" Merged 1016064 1016067 > End of message, stopping processing here. Please contact me if you need assistance. -- 1016064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016064 1016067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): merge 1016064 1016067
Processing commands for cont...@bugs.debian.org: > merge 1016064 1016067 Bug #1016064 [rpcbind] rpcbind: rpcbind.service fails with "cannot get uid of '_rpc': Success" Unable to merge bugs because: severity of #1016067 is 'grave' not 'serious' Failed to merge 1016064: Did not alter merged bugs. > End of message, stopping processing here. Please contact me if you need assistance. -- 1016064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016064 1016067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013025: marked as done (qtwebengine-opensource-src: ftbfs with GCC-12)
Your message dated Wed, 27 Jul 2022 09:05:06 + with message-id and subject line Bug#1013025: fixed in qtwebengine-opensource-src 5.15.10+dfsg-4 has caused the Debian Bug report #1013025, regarding qtwebengine-opensource-src: ftbfs with GCC-12 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.) -- 1013025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:qtwebengine-opensource-src Version: 5.15.8+dfsg-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/qtwebengine-opensource-src_5.15.8+dfsg-1_unstable_gcc12.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. [...] [12940/32901] /usr/bin/g++ -MMD -MF obj/skia/skia/SkSLVariableReference.o.d -DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DOFFICIAL_BUILD -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNO_UNWIND_TABLES -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DSK_CODEC_DECODES_PNG -DSK_CODEC_DECODES_WEBP -DSK_ENCODE_PNG -DSK_ENCODE_WEBP -DSK_USER_CONFIG_HEADER=\"../../skia/config/SkUserConfig.h\" -DSK_GL -DSK_CODEC_DECODES_JPEG -DSK_ENCODE_JPEG -DSK_USE_LIBGIFCODEC -DSK_VULKAN_HEADER=\"../../skia/config/SkVulkanConfig.h\" -DSK_VULKAN=1 -DSK_SUPPORT_GPU=1 -DSK_GPU_WORKAROUNDS_HEADER=\"gpu/config/gpu_driver_bug_workaround_autogen.h\" -DSKIA_IMPLEMENTATION=1 -DSK_GAMMA_EXPONENT=1.2 -DSK_GAMMA_CONTRAST=0.2 -DSK_DEFAULT_FONT_CACHE_LIMIT=20971520 -DUSE_SYSTEM_LIBJPEG -DUSING_SYSTEM_ICU=1 -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_STATIC -DUCHAR_TYPE=uint16_t -DUSE_SYSTEM_ZLIB=1 -Igen -I../../3rdparty/chromium -I../../3rdparty/chromium/third_party/skia -I../. ./3rdparty/chromium/third_party/libgifcodec -I../../3rdparty/chromium/third_party/vulkan/include -I../../3rdparty/chromium/third_party/vulkan_headers/include -I../../3rdparty/chromium/third_party/perfetto/include -Igen/third_party/perfetto/build_config -Igen/third_party/perfetto -Igen -Igen -Igen -Igen -Igen -Igen -Igen -I../../3rdparty/chromium/third_party/abseil-cpp -I../../3rdparty/chromium/third_party/boringssl/src/include -I../../3rdparty/chromium/third_party/protobuf/src -Igen/protoc_out -I../../3rdparty/chromium/third_party/harfbuzz-ng/src/src -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -fno-unwind-tables -fno-asynchronous-unwind-tables -fPIC -pipe -pthread -m64 -fno-omit-frame-pointer -g0 -fvisibility=hidden -Wno-unused-local-typedefs -Wno-maybe-uninitialized -Wno-deprecated-declarations -fno-delete-null-pointer-checks -Wno-comments -Wno-packed-not-aligned -Wno-dangling-else -Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident -fdata-sect ions -ffunction-sections -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -std=gnu++14 -fno-exceptions -fno-rtti -fvisibility-inlines-hidden -std=c++17 -Wno-narrowing -Wno-class-memaccess -Wno-attributes -Wno-class-memaccess -Wno-subobject-linkage -Wno-invalid-offsetof -Wno-return-type -Wno-deprecated-copy -c ../../3rdparty/chromium/third_party/skia/src/sksl/ir/SkSLVariableReference.cpp -o obj/skia/skia/SkSLVariableReference.o [12941/32901] /usr/bin/g++ -MMD -MF obj/skia/skia/SkSLIRGenerator.o.d -DUSE_UDEV
Processed: Bug#1013025 marked as pending in qtwebengine-opensource-src
Processing control commands: > tag -1 pending Bug #1013025 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: ftbfs with GCC-12 Added tag(s) pending. -- 1013025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013025 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013025: marked as pending in qtwebengine-opensource-src
Control: tag -1 pending Hello, Bug #1013025 in qtwebengine-opensource-src 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/qt-kde-team/qt/qtwebengine/-/commit/32198a3e0694401b745b4d01add18cdcddf658b4 Add a patch to fix build with GCC 12. Closes: #1013025. (this message was generated automatically) -- Greetings https://bugs.debian.org/1013025
Bug#1008369: scikit-learn testing migration
Control: tags -1 unreproducible Control: tags -1 moreinfo Control: severity -1 important Hi, BTW, there is another bug in scikit-learn, but I can't reproduce it and have set tags accordingly. Could someone else please give it a try? Kind regards Andreas. Am Wed, Jul 20, 2022 at 09:23:28PM +0200 schrieb Andreas Tille: > Hi Nilesh, > > Am Wed, Jul 20, 2022 at 06:21:19PM +0530 schrieb Nilesh Patra: > > On 7/20/22 4:50 PM, Andreas Tille wrote: > > > Before we stop progress in Debian for many other architectures since we > > > cant't solve this on our own or otherwise are burning patience of > > > upstream I'd alternatively consider droping armel as supported > > > architecture. > > > > I am definitely +1 for this, however scikit-learn is a key package and > > dropping > > it from armel would mean dropping several revdeps as well. > > I am a bit unsure if that is fine or not. > > Its not fine at all and I would not be happy about it. However, the other > side of a key package is, that lots of package have testing removal warnings > on architectures which are widely used and we have real trouble because of > this. > > Kind regards > > Andreas. > > -- > http://fam-tille.de > > -- http://fam-tille.de
Processed: Re: scikit-learn testing migration
Processing control commands:
> tags -1 unreproducible
Bug #1008369 [src:scikit-learn] scikit-learn: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13
Added tag(s) unreproducible.
> tags -1 moreinfo
Bug #1008369 [src:scikit-learn] scikit-learn: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13
Added tag(s) moreinfo.
> severity -1 important
Bug #1008369 [src:scikit-learn] scikit-learn: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13
Severity set to 'important' from 'serious'
--
1008369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1011918: marked as done (ktimer: FTBFS: "The list of supported platorms is ''" (empty))
Your message dated Wed, 27 Jul 2022 06:06:22 + with message-id and subject line Bug#1011918: fixed in ktimer 4:22.04.3-1 has caused the Debian Bug report #1011918, regarding ktimer: FTBFS: "The list of supported platorms is ''" (empty) 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.) -- 1011918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ktimer Version: 4:21.12.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --with kf5 >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=kf5 > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu > -DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DKDE_INSTALL_USE_QT_SYS_PATHS=ON .. > -- The C compiler identification is GNU 11.3.0 > -- The CXX compiler identification is GNU 11.3.0 > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > -- Looking for __GLIBC__ > -- Looking for __GLIBC__ - found > -- Performing Test _OFFT_IS_64BIT > -- Performing Test _OFFT_IS_64BIT - Success > -- Performing Test HAVE_DATE_TIME > -- Performing Test HAVE_DATE_TIME - Success > -- Performing Test BSYMBOLICFUNCTIONS_AVAILABLE > -- Performing Test BSYMBOLICFUNCTIONS_AVAILABLE - Success > CMake Error at /usr/share/ECM/kde-modules/KDEMetaInfoPlatformCheck.cmake:24 > (file): > file STRINGS file "/<>/metainfo.yaml" > cannot be read. > Call Stack (most recent call first): > /usr/share/ECM/kde-modules/KDEFrameworkCompilerSettings.cmake:71 (include) > CMakeLists.txt:16 (include) > > > CMake Error at /usr/share/ECM/kde-modules/KDEMetaInfoPlatformCheck.cmake:69 > (message): > Your current platform 'Linux' is not supported. The list of supported > platorms is ''.If you think this is a mistake or you are working on > enabling the platform please build with the KF_IGNORE_PLATFORM_CHECK > variable set to true > Call Stack (most recent call first): > /usr/share/ECM/kde-modules/KDEFrameworkCompilerSettings.cmake:71 (include) > CMakeLists.txt:16 (include) > > > -- Configuring incomplete, errors occurred! > See also "/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log". > cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt > ==> CMakeCache.txt <== > # This is the CMakeCache file. > # For build in directory: /<>/obj-x86_64-linux-gnu > # It was generated by CMake: /usr/bin/cmake > # You can edit this file to change values found and used by cmake. > # If you do not want to change any of the values, simply exit the editor. > # If you do want to change a value, simply edit, save, and exit the editor. > # The syntax for the file is as follows: > # KEY:TYPE=VALUE > # KEY is the name of a variable in the cache. > # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. > # VALUE is the current value for the KEY. > > > # EXTERNAL cache entries > > > //Build the project with gcov support > BUILD_COVERAGE:BOOL=OFF > > //Build against Qt 6 > BUILD_WITH_QT6:BOOL=OFF > > //Path to a program. > CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line > > //Path to a program. > CMAKE_AR:FILEPATH=/usr/bin/ar > > //Choose the type of build, options are: None Debug Release RelWithDebInfo > // MinSizeRel ... > CMAKE_BUILD_TYPE:STRING=Debian > > //Enable/Disable color output during build. > CMAKE_COLOR_MAKEFILE:BOOL=ON > > //CXX compiler > CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/c++ > > //A wrapper around 'ar' adding the appropriate '--plugin' option > // for the GCC compiler >
