Bug#1014133: asterisk: Asterisk fails to build from source
Quoting Ralf Schlatterbeck (2022-06-30 21:18:49) > On Thu, Jun 30, 2022 at 08:28:19PM +0200, Jonas Smedegaard wrote: > > I am not very familiar with asterisk as packaged for Bullseye - only > > know that it was pretty unusually done. > > > > Maybe try build in a pristine build-environment. > > What do you mean by this? Personally I use cowbuilder but some prefer sbuild. Both are mentioned e.g. at https://wiki.debian.org/Packaging#Suggested_tools_to_create_an_environment_for_packaging > > Maybe try get directly in touch with Bernhard Schmidt who prepared the > > work for Bullseye but possibly doesn't follow these bugs nowadays. > > I'll try! > Can you give me a hint how to find his mail address? It is listed in the changelog for the releases he finalized. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#876621: marked as done (redmine-recaptcha: missing build dependency on rename)
Your message dated Thu, 30 Jun 2022 22:50:36 + with message-id and subject line Bug#876621: fixed in redmine-recaptcha 0.1.0+git20121018-4 has caused the Debian Bug report #876621, regarding redmine-recaptcha: missing build dependency on rename 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.) -- 876621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876621 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: redmine-recaptcha Version: 0.1.0+git20121018-3 Severity: serious Tags: buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/redmine-recaptcha.html ... dh_install # In Redmine 2.x .rhtml files are .html.erb. find debian/redmine-plugin-recaptcha -type f -name '*.rhtml' -print0 | xargs -0 rename 's/.rhtml$/.html.erb/' xargs: rename: No such file or directory debian/rules:8: recipe for target 'override_dh_install' failed make[1]: *** [override_dh_install] Error 127 --- End Message --- --- Begin Message --- Source: redmine-recaptcha Source-Version: 0.1.0+git20121018-4 Done: Jelmer Vernooij We believe that the bug you reported is fixed in the latest version of redmine-recaptcha, 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 876...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jelmer Vernooij (supplier of updated redmine-recaptcha package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 30 Jun 2022 23:35:24 +0100 Source: redmine-recaptcha Architecture: source Version: 0.1.0+git20121018-4 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Jelmer Vernooij Closes: 843442 876621 Changes: redmine-recaptcha (0.1.0+git20121018-4) unstable; urgency=medium . [ Lucas Kanashiro ] * Put this package under Debian Ruby team maintenance * Add Duck and I to the uploaders list (Closes: #843442) * debian/rules: use mv to rename .rhtml files to .html.erb (fix FTBFS) (Closes: #876621) * Update VCS urls to point to salsa * Set the priority to optional to be compliant with Debian Policy * Create watch file * Declare compliance with Debian Policy 4.1.4 * Bump debhelper compatibility level to 11 . [ Utkarsh Gupta ] * Add salsa-ci.yml Checksums-Sha1: 4eeb03f853d4edefc4400360cbff5e04c8ba173a 2204 redmine-recaptcha_0.1.0+git20121018-4.dsc e5e029811db0a01c15861aa60ce1f3b9fca55efe 3724 redmine-recaptcha_0.1.0+git20121018-4.debian.tar.xz 99675292d86911ce0a239aeb88e25d91371b6918 6210 redmine-recaptcha_0.1.0+git20121018-4_amd64.buildinfo Checksums-Sha256: 2d52c8f98031eb9e36dfdec3542dec2256de2056255d5bb124d4de809921a008 2204 redmine-recaptcha_0.1.0+git20121018-4.dsc 7a6936ed215621551e7f3c6e4c1742a5f4d460217c7bdda94ec8782067e4dc3f 3724 redmine-recaptcha_0.1.0+git20121018-4.debian.tar.xz 0b0b9d68216a72a63037d1575ef09bb321097975b002ca0c5e2ddf4c0940ce4e 6210 redmine-recaptcha_0.1.0+git20121018-4_amd64.buildinfo Files: 9ea12995fcc763fd8440577d37501dc8 2204 ruby optional redmine-recaptcha_0.1.0+git20121018-4.dsc 3b85412a11c38b1ab001277ea1754a85 3724 ruby optional redmine-recaptcha_0.1.0+git20121018-4.debian.tar.xz 8db7a8bf76a8878a239df506500c4992 6210 ruby optional redmine-recaptcha_0.1.0+git20121018-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAmK+JV4ACgkQV5wWDUye I+hVOA//dWtbAksGCpLLL1lLZ6SfHpjK+Pn4FsMI46OScfJzhtEPBBeGk/brDaSI DlcFMyYUa+vaB29kc+WyNKpH/JKA7pxlnS/Cz6n4SNHW9pZ6STK6D2MomptdsBly PZ2bddpTgCB7PRQjacLngneJ0Yf2oeCxxdVPdK9HMaHg/Trbv1l5tuhRBXnribKq 7iUT1h8jeBSX0zobd4Dzab/Gplj98hL9EnUcWksXQjSCVyzjw8ph8J4X3MC+2vQh D8MYSvNbZ+eMV/16s1gLkJWekzu92v5VYZC+XJ/AcmGtgmarGFBrkSdZ9LDH53ez 8eLf8/8/FQfjJS6Crj3WSsRws5VhZo5zAjOdYMnVem7lv1Sim0Ucco16P980r8bg l3Px5ks6NfLENT6xGU176lm3kUOZTg/wHKDFq3ourjW1Zmu/bi+ORp9V6a1NNcs5 kGtwgpJJsfZFRPaZrp+9eow6cTxemJEPze0aUQaJDhRrJ3AOPdTphNMoqf8DedpX B9WVCZKFjPjVdWqwO0EWCpNlMvw5XhgQ705dFZ1ISXq3twhgtcCz8o9gmjQaPnO8 yOoSBaY1gaMdIyMG9LMTkav1YUal7liMdihoTqO2a3reFjcJilrLPbw1/l1sT8Ho Zf4poneZf3b9D1ffRX5HFvTr1/Mk+qrItUASOoMPwqDdqSUOZDk= =gI2h -END PGP SIGNATURE End Message ---
Bug#1014127: marked as done (uhd: binary-any FTBFS)
Your message dated Thu, 30 Jun 2022 21:49:49 + with message-id and subject line Bug#1014127: fixed in uhd 4.2.0.0+ds1-2 has caused the Debian Bug report #1014127, regarding uhd: binary-any FTBFS 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.) -- 1014127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014127 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: uhd Version: 4.2.0.0+dfsg-1 Severity: serious Tags: ftbfs Control: found -1 4.2.0.0+ds1-1 https://buildd.debian.org/status/logs.php?pkg=uhd=4.2.0.0%2Bdfsg-1 https://buildd.debian.org/status/logs.php?pkg=uhd=4.2.0.0%2Bds1-1 ... dh_installman -a -O--sourcedirectory=host -O--buildsystem=cmake\+ninja dh_installman: error: Cannot find (any matches for) "usr/share/man/man1/usrpctl.1.gz" (tried in ., debian/tmp) dh_installman: error: Aborting due to earlier error --- End Message --- --- Begin Message --- Source: uhd Source-Version: 4.2.0.0+ds1-2 Done: A. Maitland Bottoms We believe that the bug you reported is fixed in the latest version of uhd, 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. A. Maitland Bottoms (supplier of updated uhd 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: Thu, 30 Jun 2022 17:00:07 -0400 Source: uhd Architecture: source Version: 4.2.0.0+ds1-2 Distribution: unstable Urgency: medium Maintainer: A. Maitland Bottoms Changed-By: A. Maitland Bottoms Closes: 1014127 Changes: uhd (4.2.0.0+ds1-2) unstable; urgency=medium . * Fix manpage installation for binary-any builds (Closes: #1014127) Checksums-Sha1: 68d87228e3283dfb97adf2eee475711e149e95d1 2935 uhd_4.2.0.0+ds1-2.dsc 24ecafb3374b3dfd910f55d6f98e89b925b26201 59484 uhd_4.2.0.0+ds1-2.debian.tar.xz 069c677d706a65a4312285eab3aefa5a990538c9 24636 uhd_4.2.0.0+ds1-2_amd64.buildinfo Checksums-Sha256: 3c6119709829ff47d2cc84fb54c65621cdb7517fd9d6630be621aa8f58ab245c 2935 uhd_4.2.0.0+ds1-2.dsc a3a0e64effe60e6c75f77a9a0ab09ec40e3064cd6c44ebbe5212fd8cc79b7658 59484 uhd_4.2.0.0+ds1-2.debian.tar.xz a56c8c65207cae5c4b7a228388385bd11024c14602c2f45ecb7a67466c5c2ffa 24636 uhd_4.2.0.0+ds1-2_amd64.buildinfo Files: 57a69aa7701a70f96de193985c00ce4c 2935 science optional uhd_4.2.0.0+ds1-2.dsc 1b2009df04dbec4202f2cd62fd1b5b64 59484 science optional uhd_4.2.0.0+ds1-2.debian.tar.xz b98e1120177458122cf55b92af1bcb35 24636 science optional uhd_4.2.0.0+ds1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAmK+FR4ACgkQUEHxiR9E 4JC4VA//S2Z8jI8q8u53t83aIEYELmViWzCWgd1WQj7UIWcHmGGffupHwbG6Ez/t J38Pf7oZ5NxcmbWhAfWPLXhDIfTnYd00ZXMLIxCFV/EfN1qxagcpYNTeobPIN+v6 MEHYvQ9sAAacYRwxIBT+Qf2TIyS7k8oDNhTJY80lZhT2cW4u5qM6+X7ACHg/KrAC SucJoVoeGt5+PqMXGCnOxO+75ZFbiFS7d/5SjZrm+up6py7pdqLPwrJ8qtYh2BlG 4OVOuiMtf9Rtr1kvI0u9jz3fNPSic73v+fOpnGhUsHPoIXvFrUXJ//+KMwilEHX4 2oNSHA6yM99dFY54w4alKOhegScwNSmobiIKevcjRnrD6+9XncQxyFROsZr39wEp dNUnZtnfcaeGd0Wm/2tNB0hyF86Y4XFmfhfOEZ5TBioC4QCp8VpywBeqT+tcqBEk 4rw3MuMjOnXR/NZAjs5cV/AX/A3Do2J7auRo0PQmg9wuO1an/q4hbcc9GYq8aqW1 v06jtvaic9sTMzMRZHTSV9oHaW2Pprd827HLqOVZyj8gHdfan4l6BRKYEvYx7MpR lWRHbWbnflR/moV+SSfKuxF5mK7qS4REIwIGPDHWrVXVHltzjuYxA+/nq65wfJG6 2QnX1RwEkOgF5gFsHWmD1ZZlA/cj0Ai4HjcuCAe4qPkE6BFl8SY= =LSp3 -END PGP SIGNATURE End Message ---
Processed: closing 1013789
Processing commands for cont...@bugs.debian.org: > close 1013789 1.1.1-1 Bug #1013789 [src:haskell-memoize] haskell-memoize FTBFS: error: Expecting one more argument to ‘TyVarBndr’ Marked as fixed in versions haskell-memoize/1.1.1-1. Bug #1013789 [src:haskell-memoize] haskell-memoize FTBFS: error: Expecting one more argument to ‘TyVarBndr’ Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1013789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1014019
Processing commands for cont...@bugs.debian.org: > close 1014019 1.4.1.4-1 Bug #1014019 [src:haskell-pqueue] haskell-pqueue FTBFS: Encountered missing or private dependencies: base >=4.8 && <4.15 Marked as fixed in versions haskell-pqueue/1.4.1.4-1. Bug #1014019 [src:haskell-pqueue] haskell-pqueue FTBFS: Encountered missing or private dependencies: base >=4.8 && <4.15 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1014019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014019 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1013791
Processing commands for cont...@bugs.debian.org: > close 1013791 0.4.6.1-1 Bug #1013791 [src:haskell-inspection-testing] haskell-inspection-testing FTBFS: Encountered missing or private dependencies: base >=4.9 && <4.15, ghc >=8.0.2 && <8.11 Marked as fixed in versions haskell-inspection-testing/0.4.6.1-1. Bug #1013791 [src:haskell-inspection-testing] haskell-inspection-testing FTBFS: Encountered missing or private dependencies: base >=4.9 && <4.15, ghc >=8.0.2 && <8.11 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1013791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013574: marked as done (ardour: FTBFS: ../libs/backends/jack/jack_audiobackend.cc:887:21: error: ‘jack_client_stop_thread’ was not declared in this scope; did you mean ‘jack_client_create_thread’
Your message dated Thu, 30 Jun 2022 21:18:52 + with message-id and subject line Bug#1013574: fixed in ardour 1:6.9.0+ds0-2 has caused the Debian Bug report #1013574, regarding ardour: FTBFS: ../libs/backends/jack/jack_audiobackend.cc:887:21: error: ‘jack_client_stop_thread’ was not declared in this scope; did you mean ‘jack_client_create_thread’? 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.) -- 1013574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ardour Version: 1:6.9.0+ds0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220624 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > [ 735/1095] Compiling libs/backends/dummy/dummy_audiobackend.cc > 05:44:16 runner ['/usr/bin/g++', '-I/<>', '-g', '-O2', > '-ffile-prefix-map=/<>=.', '-fstack-protector-strong', > '-Wformat', '-Werror=format-security', '-I/usr/include/qm-dsp', > '-DHAVE_RF64_RIFF', '-DWAF_BUILD', '-DNDEBUG', '-fshow-column', '-O3', > '-fomit-frame-pointer', '-ffast-math', '-fstrength-reduce', '-pipe', > '-DARCH_X86', '-mmmx', '-msse', '-mfpmath=sse', '-DUSE_XMMINTRIN', > '-DBUILD_SSE_OPTIMIZATIONS', '-DLXVST_64BIT', '-Wall', '-Wpointer-arith', > '-Wcast-qual', '-Wcast-align', '-Wno-unused-parameter', > '-DBOOST_SYSTEM_NO_DEPRECATED', '-D_ISOC9X_SOURCE', '-D_LARGEFILE64_SOURCE', > '-D_FILE_OFFSET_BITS=64', '-DPROGRAM_NAME="Ardour"', '-DPROGRAM_VERSION="6"', > '-std=c++11', '-DBOOST_NO_AUTO_PTR', '-DBOOST_BIND_GLOBAL_PLACEHOLDERS', > '-Woverloaded-virtual', '-Wno-unused-local-typedefs', > '-D__STDC_LIMIT_MACROS', '-D__STDC_FORMAT_MACROS', '-DCANVAS_COMPATIBILITY', > '-DCANVAS_DEBUG', '-DBOOST_ERROR_CODE_HEADER_ONLY', '-fPIC', > '-F/System/Library/Frameworks', '-F/Library/Frameworks', > '-Ilibs/backends/dummy', '-I../libs/backends/dummy', '-Ilibs/ardour', > '-I../libs/ardour', '-Ilibs/midi++2', '-I../libs/midi++2', '-Ilibs/evoral', > '-I../libs/evoral', '-Ilibs/audiographer', '-I../libs/audiographer', > '-Ilibs/audiographer/src', '-I../libs/audiographer/src', '-Ilibs/ptformat', > '-I../libs/ptformat', '-Ilibs/pbd', '-I../libs/pbd', '-Ilibs/evoral/libsmf', > '-I../libs/evoral/libsmf', '-Ilibs/temporal', '-I../libs/temporal', > '-Ilibs/lua', '-I../libs/lua', '-Ilibs/zita-resampler', > '-I../libs/zita-resampler', '-Ilibs/zita-convolver', > '-I../libs/zita-convolver', '-I/usr/include/glibmm-2.4', > '-I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include', '-I/usr/include/glib-2.0', > '-I/usr/lib/x86_64-linux-gnu/glib-2.0/include', '-I/usr/include/sigc++-2.0', > '-I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include', '-I/usr/include/libxml2', > '-I/<>/build', '-DINTERNAL_SHARED_LIBS=1', > '-DUSE_EXTERNAL_LIBS=1', '-DHAVE_ALSA=1', '-DHAVE_PULSEAUDIO=1', > '-DHAVE_GLIB=1', '-DHAVE_GLIB_2_68=1', '-DHAVE_GTHREAD=1', '-DHAVE_GLIBMM=1', > '-DHAVE_SNDFILE=1', '-DHAVE_GIOMM=1', '-DHAVE_CURL=1', '-DHAVE_ARCHIVE=1', > '-DHAVE_LO=1', '-DHAVE_TAGLIB=1', '-DHAVE_VAMPSDK=1', '-DHAVE_VAMPHOSTSDK=1', > '-DHAVE_RUBBERBAND=1', '-DEXPORT_VISIBILITY_HIDDEN=0', '-DENABLE_NLS=1', > '-DLXVST_SUPPORT=1', '-DVST3_SUPPORT=1', '-DPTFORMAT=1', > '-DFPU_AVX_FMA_SUPPORT=1', '-DCONFIG_ARCH="x86_64"', > '-DHAVE_TOOLS_SANITY_CHECK=1', '-DHAVE_TOOLS_GCCABICHECK=1', > '-DHAVE_LIBS_CLEARLOOKS_NEWER=1', '-DHAVE_LIBFLUIDSYNTH=1', > '-DHAVE_LIBS_FLUIDSYNTH=1', '-DHAVE_HIDAPI=1', '-DHAVE_LIBS_HIDAPI=1', > '-DHAVE_LIBLTC=1', '-DHAVE_LIBS_LIBLTC=1', '-DHAVE_LIBS_LUA=1', > '-DHAVE_LIBS_PTFORMAT=1', '-DHAVE_BASE_PITCH_H=1', '-DHAVE_LIBS_QM_DSP=1', > '-DHAVE_FFTW3F=1', '-DHAVE_AUBIO=1', '-DHAVE_AUBIO4=1', > '-DHAVE_LIBS_VAMP_PLUGINS=1', '-DHAVE_LIBS_VAMP_PYIN=1', > '-DHAVE_LIBS_ZITA_RESAMPLER=1', '-DHAVE_LIBS_ZITA_CONVOLVER=1', > '-DHAVE_XML=1', '-DHAVE_SIGCPP=1', '-DHAVE_EXECINFO=1', > '-DHAVE_POSIX_MEMALIGN=1', '-DHAVE_GETMNTENT=1', '-DHAVE_LOCALTIME_R=1', > '-DHAVE_LIBS_PBD=1', '-DHAVE_LIBS_MIDIPP2=1', '-DHAVE_LIBS_EVORAL=1', > '-DHAVE_USB=1', '-DHAVE_CWIID_H=1', '-DHAVE_BLUETOOTH_H=1', '-DHAVE_CWIID=1', > '-DBUILD_WIIMOTE=1', '-DHAVE_WEBSOCKETS=1', '-DHAVE_CONTROL_PROTOCOL=1', > '-DHAVE_FADERPORT=1', '-DHAVE_FADERPORT8=1', '-DHAVE_CC121=1', > '-DHAVE_GENERIC_MIDI=1', '-DHAVE_MACKIE=1', '-DHAVE_US2400=1', > '-DHAVE_LAUNCH_CONTROL_XL=1', '-DHAVE_PANGOMM=1', '-DHAVE_CAIROMM=1', > '-DHAVE_PUSH2=1', '-DHAVE_CONTOURDESIGN=1', '-DHAVE_WIIMOTE=1', > '-DHAVE_LIBS_SURFACES=1', '-DHAVE_2IN2OUT=1', '-DHAVE_1IN2OUT=1', > '-DHAVE_VBAP=1',
Bug#980023: petri-foo: FTBFS with GCC 10
Control: forwarded -1 https://github.com/petri-foo/Petri-Foo/pull/43 This is essentially the same patch.
Processed: Re: petri-foo: FTBFS with GCC 10
Processing control commands: > forwarded -1 https://github.com/petri-foo/Petri-Foo/pull/43 Bug #980023 [src:petri-foo] petri-foo: FTBFS with GCC 10 Set Bug forwarded-to-address to 'https://github.com/petri-foo/Petri-Foo/pull/43'. -- 980023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010834: marked as done (biosyntax-vim: Unusable with vim-addon-manager because of outdated manifest)
Your message dated Thu, 30 Jun 2022 20:36:18 + with message-id and subject line Bug#1010834: fixed in biosyntax 1.0.0b-3 has caused the Debian Bug report #1010834, regarding biosyntax-vim: Unusable with vim-addon-manager because of outdated manifest 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.) -- 1010834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010834 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: biosyntax-vim Version: 1.0.0b-2 Severity: important Dear Maintainer, The instructions in README.Debian say that the addon should be installed with vim-addon-manager, however: $ vim-addons install biosyntax Warning: ignoring 'biosyntax' which is missing source files Helpfully, vim-addon-manager can list the files it's complaining about: $ vim-addons files biosyntax | while read -r f; do test -e "/usr/share/vim/addons/$f" || echo "$f"; done ftdetect/cwl.vim ftdetect/nexus.vim ftdetect/pml.vim syntax/cwl.vim syntax/nexus.vim syntax/pml.vim It looks like the manifest file at debian/biosyntax-vim.yaml includes extra files that are no longer included in the upstream package: https://salsa.debian.org/med-team/biosyntax/-/blob/580479a8ea5f26f67608fa38f4910180f4136b20/debian/biosyntax-vim.yaml vs https://salsa.debian.org/med-team/biosyntax/-/tree/b87d9d2c964e1c30ff82ff7c0883e82576d89043/vim -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages biosyntax-vim depends on: ii biosyntax-common 1.0.0b-2 ii vim 2:8.2.4793-1 ii vim-gtk3 [vim]2:8.2.4793-1 Versions of packages biosyntax-vim recommends: ii vim-addon-manager 0.5.10 biosyntax-vim suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: biosyntax Source-Version: 1.0.0b-3 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of biosyntax, 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 1010...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated biosyntax package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 30 Jun 2022 21:47:49 +0200 Source: biosyntax Architecture: source Version: 1.0.0b-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1010834 1010836 Changes: biosyntax (1.0.0b-3) unstable; urgency=medium . * Team upload. . [ Andreas Tille ] * Fix debian/biosyntax-vim.yaml to mention only those includes that are shipped by upstream Closes: #1010834 . [ Étienne Mollier ] * d/biosyntax-gedit.install: move specs to /usr/share/gtksourceview-4. Thanks to Carl Suster (Closes: #1010836) * Standards-Version: 4.6.1 (routine-update) * Set upstream metadata fields: Repository-Browse. Checksums-Sha1: f097e94cc13bba5e6e7b74252b96acdb7118f223 2382 biosyntax_1.0.0b-3.dsc 447f8c2bc62435556ef59c71146eff9666292d07 5200 biosyntax_1.0.0b-3.debian.tar.xz Checksums-Sha256: 2940f59629c40d1577a2a6854860c63b235231320eb9f265d502bc62bd3d0a4e 2382 biosyntax_1.0.0b-3.dsc 559112d5983b58a4aa9094a7eede4a48f86e897acf686d43262328a65c7fe05a 5200 biosyntax_1.0.0b-3.debian.tar.xz Files: 64c94c1f9a34aa296a708c6002638359 2382 science optional biosyntax_1.0.0b-3.dsc f7dda35c56432782a5f169f787620de2 5200 science optional biosyntax_1.0.0b-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmK+BhsUHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdpaXhAAhGcSSeWYvu7nYMtC2qwc+66B4sad HBDwyFAlMuVOZHt6xkiTyvPmoCVNHuYFqav5o3Y8PD66N5T7d8KLK5ji79YGSZ4M Hw7DbWcuyIKJYF1qnAeJMRCyioNvw3WjUQ4EljU86bKvG2ZqSEERoMnnihWK8sUK
Bug#1010836: marked as done (biosyntax-gedit: No longer works with recent versions of gedit)
Your message dated Thu, 30 Jun 2022 20:36:18 + with message-id and subject line Bug#1010836: fixed in biosyntax 1.0.0b-3 has caused the Debian Bug report #1010836, regarding biosyntax-gedit: No longer works with recent versions of gedit 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.) -- 1010836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: biosyntax-gedit Version: 1.0.0b-2 Severity: important Dear Maintainer, The gedit support for biosyntax works by dropping files in: /usr/share/gtksourceview-3.0/ The README.Debian says that this should cause a theme to appear in gedit at Edit > Preferences > Font & Color > bioSyntax No such entry appears. I notice that gedit depends on libgtksourceview-4-0 and that there exist directories /usr/share/gtksourceview-4/ /usr/share/gtksourceview-5/ I tested copying the style definition to the corresponding place under gtksourceview-4/ and gedit picked it up properly, so it seems that the files should be installed at that path instead. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages biosyntax-gedit depends on: ii biosyntax-common 1.0.0b-2 ii gedit 42.0-2 biosyntax-gedit recommends no packages. biosyntax-gedit suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: biosyntax Source-Version: 1.0.0b-3 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of biosyntax, 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 1010...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated biosyntax package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 30 Jun 2022 21:47:49 +0200 Source: biosyntax Architecture: source Version: 1.0.0b-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1010834 1010836 Changes: biosyntax (1.0.0b-3) unstable; urgency=medium . * Team upload. . [ Andreas Tille ] * Fix debian/biosyntax-vim.yaml to mention only those includes that are shipped by upstream Closes: #1010834 . [ Étienne Mollier ] * d/biosyntax-gedit.install: move specs to /usr/share/gtksourceview-4. Thanks to Carl Suster (Closes: #1010836) * Standards-Version: 4.6.1 (routine-update) * Set upstream metadata fields: Repository-Browse. Checksums-Sha1: f097e94cc13bba5e6e7b74252b96acdb7118f223 2382 biosyntax_1.0.0b-3.dsc 447f8c2bc62435556ef59c71146eff9666292d07 5200 biosyntax_1.0.0b-3.debian.tar.xz Checksums-Sha256: 2940f59629c40d1577a2a6854860c63b235231320eb9f265d502bc62bd3d0a4e 2382 biosyntax_1.0.0b-3.dsc 559112d5983b58a4aa9094a7eede4a48f86e897acf686d43262328a65c7fe05a 5200 biosyntax_1.0.0b-3.debian.tar.xz Files: 64c94c1f9a34aa296a708c6002638359 2382 science optional biosyntax_1.0.0b-3.dsc f7dda35c56432782a5f169f787620de2 5200 science optional biosyntax_1.0.0b-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmK+BhsUHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdpaXhAAhGcSSeWYvu7nYMtC2qwc+66B4sad HBDwyFAlMuVOZHt6xkiTyvPmoCVNHuYFqav5o3Y8PD66N5T7d8KLK5ji79YGSZ4M Hw7DbWcuyIKJYF1qnAeJMRCyioNvw3WjUQ4EljU86bKvG2ZqSEERoMnnihWK8sUK 7/XKENJW0oSX1HZsmKGtA2X884T0uFt+X9prqYyyJacgQmoLEM4/wPju1DQlZggk JQppSFaGpo59yvhBH5ctIqkpGj/A1Dmz7vGBHyPgvIeauTpus9B5ez44WNr50jH+ TdMIpDoxXtQYsJKp+JlZ0vKbIsH5P+71Ob6NK0tgRbJs6mPCAFoAK81JOqab5m1V snQrjXqHDvQQO+GgOlJsRFkMjUlcIK3xQbkkRV2rLcCL7RWAT2n+u5lNtOMnQmJp 5sdx/N0+yP7RT0PBta+COlwFjXzU4u68jk+p1kGWWBdFfhkuxRr6MwALRLhJgyz2 qLg5bT3BqkSmPBJWCbEncyiXbkhlwibugAQ52CbOz3dM0tUIUoStuGnHsu61bH7g
Bug#1014115: uninstall does not properly remove enablement symlinks
On Thu, 30 Jun 2022 at 20:20, Michael Biebl wrote: > > > Am 30.06.22 um 18:18 schrieb Michael Biebl: > > Am 30.06.22 um 17:31 schrieb Luca Boccassi: > >> On Thu, 30 Jun 2022 at 15:44, Michael Biebl wrote: > >>> > >>> Am 30.06.22 um 16:32 schrieb Luca Boccassi: > On Thu, 30 Jun 2022 at 15:24, Michael Biebl wrote: > > > > Am 30.06.22 um 16:13 schrieb Luca Boccassi: > >> On Thu, 30 Jun 2022 at 15:08, Michael Biebl wrote: > >>> > >>> Am 30.06.22 um 14:26 schrieb Michael Biebl: > This might be a bug in i-s-h, but filing against systemd-homed for > now. > > systemd-homed.service: > [Install] > WantedBy=multi-user.target > Alias=dbus-org.freedesktop.home1.service > Also=systemd-homed-activate.service systemd-userdbd.service > > systemd-homed-activate.service: > [Install] > WantedBy=systemd-homed.service > Also=systemd-homed.service > > → we have a circular dependency here, maybe deb-systemd-helper > get's > confused by that > >>> > >>> > >>> I just checked that we can mitigate this issue by removing this > >>> circular > >>> Also= dependency. It is indeed deb-systemd-helper getting > >>> confused by > >>> that and as a result not writing proper state files to > >>> /var/lib/systemd/deb-systemd-helper. > >>> So the damage is already done during installation in postinst. > >>> Thus raising to RC to warn users from installing systemd-homed atm. > >>> > >>> I propose a patch like the attached one, i.e. dropping the Also= > >>> from > >>> systemd-homed-active.service. WDYT? > > > > Are you against shipping this patch for the time being until we have a > > proper fix? > > Given the problem is that i-s-h doesn't generate the correct postinst, > can we instead add a workaround to the postinst itself? > >>> > >>> No, it's not an incorrect postinst. The generated postinst code looks > >>> fine afaics. > >>> > >>> It's deb-systemd-helper failing in postinst [1] (due to the circular > >>> Also=) and subsequently not writing any state files to > >>> /var/lib/systemd/deb-systemd-helper (which means it can't clean up the > >>> state on purge). > >>> > >>> > >>> I'm pasting the error message again, for reference > >>> > Setting up systemd-homed (251.2-7) ... > Created symlink > /etc/systemd/system/systemd-homed.service.wants/systemd-homed-activate.service > -> /lib/systemd/system/systemd-homed-activate.service. > Created symlink > /etc/systemd/system/dbus-org.freedesktop.home1.service -> > /lib/systemd/system/systemd-homed.service. > Created symlink > /etc/systemd/system/multi-user.target.wants/systemd-homed.service -> > /lib/systemd/system/systemd- > homed.service. > Deep recursion on subroutine "main::get_link_closure" at > /usr/bin/deb-systemd-helper line 253, <$fh> line 23. > /usr/bin/deb-systemd-helper: error: unable to read > /lib/systemd/system/systemd-homed.service > Deep recursion on subroutine "main::get_link_closure" at > /usr/bin/deb-systemd-helper line 253, <$fh> line 41. > /usr/bin/deb-systemd-helper: error: unable to read > /lib/systemd/system/systemd-homed-activate.service > >> > >> I see, then could it be fixed in the postinst manually after the calls > >> added by the helper? > > > > I don't see how. > > Let me put this differently: this would mean manually implementing in > shell what deb-systemd-helper is doing in perl and creating the state > files ourselves. > Feasible, yes. Doable, I'd say no. > I'd rather prefer a one-line patch. The problem is some files leftover, no? Just delete them in the postinst or postrm?
Bug#1013163:
I'm having trouble reproducing this locally in a Docker container using qemu on sid: it seems to work here. Similarly a Bookworm docker in qemu into which I installed the sid package also seems to test OK. (Ran the full autopkgtest suite in it, and while it did appear to fail an assertion elsewhere in the tests, it didn't break the test suite?) I'm not sure what would cause this failure. Can these tests be re-run?
Bug#1010122: Patch to resolve FTBFS
Dear Debian Maintainer, The following change resolves the FTBFS on architectures != amd64: ``` diff -Nru scamper-20211212/debian/rules scamper-20211212/debian/rules --- scamper-20211212/debian/rules 2022-01-20 07:45:28.0 -0600 +++ scamper-20211212/debian/rules 2022-06-30 14:32:24.0 -0500 @@ -24,6 +24,6 @@ rm debian/tmp/usr/bin/sc_warts2csv rm debian/tmp/usr/share/man/man1/sc_wartsfix.1 rm debian/tmp/usr/share/man/man1/sc_warts2csv.1 - rm debian/tmp/usr/lib/x86_64-linux-gnu/libscamperfile.la + rm debian/tmp/usr/lib/*/libscamperfile.la rm debian/tmp/usr/share/man/man5/warts.5 rm debian/tmp/usr/share/man/man3/libscamperfile.3 ``` Thank you, William 'jawn-smith' Wilson
Bug#1014133: asterisk: Asterisk fails to build from source
On Thu, Jun 30, 2022 at 08:28:19PM +0200, Jonas Smedegaard wrote: > I am not very familiar with asterisk as packaged for Bullseye - only > know that it was pretty unusually done. > > Maybe try build in a pristine build-environment. What do you mean by this? > Maybe try get directly in touch with Bernhard Schmidt who prepared the > work for Bullseye but possibly doesn't follow these bugs nowadays. I'll try! Can you give me a hint how to find his mail address? Thanks for your *very* quick answer! Ralf -- Dr. Ralf Schlatterbeck Tel: +43/2243/26465-16 Open Source Consulting www: www.runtux.com Reichergasse 131, A-3411 Weidling email: off...@runtux.com
Bug#1014115: uninstall does not properly remove enablement symlinks
Am 30.06.22 um 18:18 schrieb Michael Biebl: Am 30.06.22 um 17:31 schrieb Luca Boccassi: On Thu, 30 Jun 2022 at 15:44, Michael Biebl wrote: Am 30.06.22 um 16:32 schrieb Luca Boccassi: On Thu, 30 Jun 2022 at 15:24, Michael Biebl wrote: Am 30.06.22 um 16:13 schrieb Luca Boccassi: On Thu, 30 Jun 2022 at 15:08, Michael Biebl wrote: Am 30.06.22 um 14:26 schrieb Michael Biebl: This might be a bug in i-s-h, but filing against systemd-homed for now. systemd-homed.service: [Install] WantedBy=multi-user.target Alias=dbus-org.freedesktop.home1.service Also=systemd-homed-activate.service systemd-userdbd.service systemd-homed-activate.service: [Install] WantedBy=systemd-homed.service Also=systemd-homed.service → we have a circular dependency here, maybe deb-systemd-helper get's confused by that I just checked that we can mitigate this issue by removing this circular Also= dependency. It is indeed deb-systemd-helper getting confused by that and as a result not writing proper state files to /var/lib/systemd/deb-systemd-helper. So the damage is already done during installation in postinst. Thus raising to RC to warn users from installing systemd-homed atm. I propose a patch like the attached one, i.e. dropping the Also= from systemd-homed-active.service. WDYT? Are you against shipping this patch for the time being until we have a proper fix? Given the problem is that i-s-h doesn't generate the correct postinst, can we instead add a workaround to the postinst itself? No, it's not an incorrect postinst. The generated postinst code looks fine afaics. It's deb-systemd-helper failing in postinst [1] (due to the circular Also=) and subsequently not writing any state files to /var/lib/systemd/deb-systemd-helper (which means it can't clean up the state on purge). I'm pasting the error message again, for reference Setting up systemd-homed (251.2-7) ... Created symlink /etc/systemd/system/systemd-homed.service.wants/systemd-homed-activate.service -> /lib/systemd/system/systemd-homed-activate.service. Created symlink /etc/systemd/system/dbus-org.freedesktop.home1.service -> /lib/systemd/system/systemd-homed.service. Created symlink /etc/systemd/system/multi-user.target.wants/systemd-homed.service -> /lib/systemd/system/systemd- homed.service. Deep recursion on subroutine "main::get_link_closure" at /usr/bin/deb-systemd-helper line 253, <$fh> line 23. /usr/bin/deb-systemd-helper: error: unable to read /lib/systemd/system/systemd-homed.service Deep recursion on subroutine "main::get_link_closure" at /usr/bin/deb-systemd-helper line 253, <$fh> line 41. /usr/bin/deb-systemd-helper: error: unable to read /lib/systemd/system/systemd-homed-activate.service I see, then could it be fixed in the postinst manually after the calls added by the helper? I don't see how. Let me put this differently: this would mean manually implementing in shell what deb-systemd-helper is doing in perl and creating the state files ourselves. Feasible, yes. Doable, I'd say no. I'd rather prefer a one-line patch. OpenPGP_signature Description: OpenPGP digital signature
Processed: closing 1013796
Processing commands for cont...@bugs.debian.org: > close 1013796 9.2.0.7-1 Bug #1013796 [src:haskell-hxt-regex-xmlschema] haskell-hxt-regex-xmlschema FTBFS: Parse error in pattern: !n Marked as fixed in versions haskell-hxt-regex-xmlschema/9.2.0.7-1. Bug #1013796 [src:haskell-hxt-regex-xmlschema] haskell-hxt-regex-xmlschema FTBFS: Parse error in pattern: !n Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1013796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008544: marked as done (gnome-shell-extension-draw-on-your-screen: does not declare compatibility with GNOME Shell 42)
Your message dated Thu, 30 Jun 2022 19:07:15 + with message-id and subject line Bug#1014130: Removed package(s) from unstable has caused the Debian Bug report #1008544, regarding gnome-shell-extension-draw-on-your-screen: does not declare compatibility with GNOME Shell 42 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.) -- 1008544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008544 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell-extension-draw-on-your-screen Version: 11-2 Severity: normal Tags: bookworm sid User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: gnome-shell-42 The metadata.json for this extension doesn't declare compatibility with GNOME 42. I don't know whether the actual code will need changes or not: the conservative assumption is that it probably will (so please test). gnome-shell 42 is in experimental and will be entering unstable soon, at which point this will become a RC bug. In versions of GNOME Shell up to 3.38, metadata.json didn't matter much, because validation of extensions' metadata against the installed Shell version was disabled by default; but since GNOME 40 the default has changed back to enabling the version check by default, in an effort to avoid issues caused by outdated extensions remaining enabled. As a result, GNOME Shell extensions in bookworm should probably have a dependency like: Depends: gnome-shell (>= x), gnome-shell (<< y~) where x and y are set according to metadata.json. gnome-shell-extension-caffeine is a good example of this technique. During the GNOME Shell 42 transition, this extension will be removed from testing if it continues to be incompatible. Thanks, smcv --- End Message --- --- Begin Message --- Version: 11-2+rm Dear submitter, as the package gnome-shell-extension-draw-on-your-screen has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1014130 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---
Processed: Bug#1013574 marked as pending in ardour
Processing control commands: > tag -1 pending Bug #1013574 [src:ardour] ardour: FTBFS: ../libs/backends/jack/jack_audiobackend.cc:887:21: error: ‘jack_client_stop_thread’ was not declared in this scope; did you mean ‘jack_client_create_thread’? Added tag(s) pending. -- 1013574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013574: marked as pending in ardour
Control: tag -1 pending Hello, Bug #1013574 in ardour 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/multimedia-team/ardour/-/commit/062c872dc27bebac13dc0b39091d446b16b0be32 Fix compilation with newer jackd1 Closes: #1013574 (this message was generated automatically) -- Greetings https://bugs.debian.org/1013574
Bug#1014133: asterisk: Asterisk fails to build from source
Hi Ralf, Quoting Ralf Schlatterbeck (2022-06-30 19:58:38) > Package: asterisk > Version: 1:16.16.1~dfsg-1+deb11u1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > > Dear Maintainer, > > I'm trying to build asterisk from source (bullseye) using: > > dpkg-buildpackage -rfakeroot > > Looks like the verification of the needed pjproject sub-project fails. > The last relevant lines from configure: > > configure:9241: checking for embedded pjproject (may have to download) > configure:9243: result: configuring > configure:9310: result: failed > configure:9312: Unable to configure third-party/pjproject > configure:9314: error: Re-run the ./configure command with 'NOISY_BUILD=yes' > appended to see error details. > > If I re-run this, it tries to download the pjproject tarball and fails > to verify the checksum. > If I clean (debian/rules clean) and configure by hand it seems to be > able to verify (but fails later with a different error). > > Let me know if I'm missing some trick here and if you need additional > information. > My plan (why I'm trying to re-build) is to include a simple patch to > res/res_pjsip_messaging.c to allow content-types other than text/plain. > But I'm failing on the unmodified Debian sources. I am not very familiar with asterisk as packaged for Bullseye - only know that it was pretty unusually done. Maybe try build in a pristine build-environment. Maybe try get directly in touch with Bernhard Schmidt who prepared the work for Bullseye but possibly doesn't follow these bugs nowadays. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1014137: src:cpu-x: invalid maintainer address
Source: cpu-x Version: 4.3.1-1 Tags: sid Severity: serious X-Debbugs-Cc: Mike Gabriel The maintainer address for cpu-x is invalid, see below. Ansgar > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > > martin.wimpr...@ubuntu.com > host mx.ubuntu.com [185.125.188.73] > SMTP error from remote mail server after RCPT > TO:: > 550 5.1.1 : Recipient address rejected: > User unknown in relay recipient table Reporting-MTA: dns; mitropoulos.debian.org Action: failed Final-Recipient: rfc822;martin.wimpress@ubuntu.com Status: 5.0.0 Remote-MTA: dns; mx.ubuntu.com Diagnostic-Code: smtp; 550 5.1.1 : Recipient address rejected: User unknown in relay recipient table
Processed: tagging 1014125, bug 1014125 is forwarded to https://github.com/strukturag/libheif/issues/207 ...
Processing commands for cont...@bugs.debian.org: > tags 1014125 + upstream Bug #1014125 [src:libheif] libheif: CVE-2020-23109 Added tag(s) upstream. > forwarded 1014125 https://github.com/strukturag/libheif/issues/207 Bug #1014125 [src:libheif] libheif: CVE-2020-23109 Set Bug forwarded-to-address to 'https://github.com/strukturag/libheif/issues/207'. > tags 1014124 + upstream Bug #1014124 [src:nomacs] nomacs: CVE-2020-23884 Added tag(s) upstream. > forwarded 1014124 https://github.com/nomacs/nomacs/issues/516 Bug #1014124 [src:nomacs] nomacs: CVE-2020-23884 Set Bug forwarded-to-address to 'https://github.com/nomacs/nomacs/issues/516'. > tags 1014122 + upstream Bug #1014122 [src:libelfin] libelfin: CVE-2020-24821 CVE-2020-24822 CVE-2020-24823 CVE-2020-24824 CVE-2020-24825 CVE-2020-24826 CVE-2020-24827 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1014122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014122 1014124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014124 1014125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014135: src:gjiten: invalid maintainer address
Source: gjiten Version: 3.1-1 Severity: serious Tags: sid X-Debbugs-Cc: Ludovic Drolez The maintainer address for gjiten is invalid, see below. Ansgar > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > > b...@users.sourceforge.net > host mx.sourceforge.net [216.105.38.6] > SMTP error from remote mail server after RCPT > TO:: > 550 unknown user Reporting-MTA: dns; mitropoulos.debian.org Action: failed Final-Recipient: rfc822;b0ti@users.sourceforge.net Status: 5.0.0 Remote-MTA: dns; mx.sourceforge.net Diagnostic-Code: smtp; 550 unknown user
Bug#1014070: marked as done (libengine-gost-openssl: Missing build dependency on pkg-config)
Your message dated Thu, 30 Jun 2022 18:21:37 + with message-id and subject line Bug#1014070: fixed in libengine-gost-openssl 3.0.1-2 has caused the Debian Bug report #1014070, regarding libengine-gost-openssl: Missing build dependency on pkg-config 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.) -- 1014070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libengine-gost-openssl Version: 3.0.1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=libengine-gost-openssl=sid ... -- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE) CMake Error at CMakeLists.txt:114 (message): Unable to discover the OpenSSL engines directory. Provide the path using -DOPENSSL_ENGINES_DIR -- Configuring incomplete, errors occurred! --- End Message --- --- Begin Message --- Source: libengine-gost-openssl Source-Version: 3.0.1-2 Done: Wartan Hachaturow We believe that the bug you reported is fixed in the latest version of libengine-gost-openssl, 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. Wartan Hachaturow (supplier of updated libengine-gost-openssl 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: Thu, 30 Jun 2022 15:02:22 +0300 Source: libengine-gost-openssl Binary: gostsum gostsum-dbgsym libengine-gost-openssl libengine-gost-openssl-dbgsym libengine-gost-openssl1.1 Architecture: source amd64 Version: 3.0.1-2 Distribution: unstable Urgency: medium Maintainer: Wartan Hachaturow Changed-By: Wartan Hachaturow Description: gostsum- Utility to compute GOST hashes libengine-gost-openssl - Loadable module for openssl implementing GOST algorithms libengine-gost-openssl1.1 - dummy package for upgrades from libengine-gost-openssl1.1 Closes: 1014070 Changes: libengine-gost-openssl (3.0.1-2) unstable; urgency=medium . * Add pkg-config to Build-Depends (Closes: #1014070) Checksums-Sha1: 1132055d5f9f3919ab0c29fd0881acea1804c5d7 2087 libengine-gost-openssl_3.0.1-2.dsc 8e94809982c5e5257c8863ac336272a0db5c08d2 5716 libengine-gost-openssl_3.0.1-2.debian.tar.xz 3153b21c1113ad97f09a1e730d2f9d3c220c3458 66144 gostsum-dbgsym_3.0.1-2_amd64.deb c3ea163e8b49c3377f70f077e651d05056d7e37d 37724 gostsum_3.0.1-2_amd64.deb 526a9b03972cdeb78f5a4d1c65cfa07af570c001 1444888 libengine-gost-openssl-dbgsym_3.0.1-2_amd64.deb 849eb75f614219c335095d5320cf07b8383af0ad 5204 libengine-gost-openssl1.1_3.0.1-2_amd64.deb 5a04c08a8891b5de70266d9b44b86e12da21c519 8017 libengine-gost-openssl_3.0.1-2_amd64.buildinfo bb2f771c1669b08315fca005f672a1c566238301 505800 libengine-gost-openssl_3.0.1-2_amd64.deb Checksums-Sha256: 7b051686acef5f7b2eff30cb95ecc209e2c4f04e06352d939ca2a91fb022318b 2087 libengine-gost-openssl_3.0.1-2.dsc b02c200777acfebf2fd112b3f401831c67ebaf86460d97ee9696dd86f70fd605 5716 libengine-gost-openssl_3.0.1-2.debian.tar.xz a0f44736075956b4db94839110d0b39214109aff2351ba3114d34cfd90906ea3 66144 gostsum-dbgsym_3.0.1-2_amd64.deb 0542de51b6803348492ebf44e05ea5bb165a845a8b5f61f19b84baf6711378bf 37724 gostsum_3.0.1-2_amd64.deb d48e614d1a8ae038f800db745e3a877f3f6addd9fead1a5d59e3ad48ca157383 1444888 libengine-gost-openssl-dbgsym_3.0.1-2_amd64.deb 944182a73d96995553556013bf944ea67f71e7549d84bda0397bb8d8b9ef094d 5204 libengine-gost-openssl1.1_3.0.1-2_amd64.deb a05394087d50503ceea9010601acf4076aa70c66a84f1c56dc4f3223d6552638 8017 libengine-gost-openssl_3.0.1-2_amd64.buildinfo 2e1daafb33e7b9b4c1183785b0468365bd2dc5d90eb29ed8ebf95ee5a8ea8de1 505800 libengine-gost-openssl_3.0.1-2_amd64.deb Files: aa18fe546fda91e896930bf7e1891ec0 2087 libs optional libengine-gost-openssl_3.0.1-2.dsc 25777aaaf1ac938c31d3a3c0fec32379 5716 libs optional libengine-gost-openssl_3.0.1-2.debian.tar.xz b27d1d863a07d2366288050f959a2ffc 66144 debug optional gostsum-dbgsym_3.0.1-2_amd64.deb 965bd2a1b7c6dec592bf0fe61d238724 37724 utils optional gostsum_3.0.1-2_amd64.deb ae43ceac6588cc0aff5d368489fe5df4 1444888 debug optional
Processed: Re: Bug#1014114: installation of crypt.h in the multiarch location breaks the GCC and LLVM multilib builds
Processing control commands: > clone -1 -2 Bug #1014114 [libcrypt-dev] installation of crypt.h in the multiarch location breaks the GCC and LLVM multilib builds Bug 1014114 cloned as bug 1014134 > reassign -2 src:gcc-12 Bug #1014134 [libcrypt-dev] installation of crypt.h in the multiarch location breaks the GCC and LLVM multilib builds Bug reassigned from package 'libcrypt-dev' to 'src:gcc-12'. No longer marked as found in versions 4.4.28-1. Ignoring request to alter fixed versions of bug #1014134 to the same values previously set > tags -2 = ftbfs Bug #1014134 [src:gcc-12] installation of crypt.h in the multiarch location breaks the GCC and LLVM multilib builds Added tag(s) ftbfs. > retitle -2 gcc-12 FTBFS in unstable on amd64: > ../../src/gcc/config/i386/i386.h:2356:10: fatal error: insn-attr-common.h: No > such file or directory Bug #1014134 [src:gcc-12] installation of crypt.h in the multiarch location breaks the GCC and LLVM multilib builds Changed Bug title to 'gcc-12 FTBFS in unstable on amd64: ../../src/gcc/config/i386/i386.h:2356:10: fatal error: insn-attr-common.h: No such file or directory' from 'installation of crypt.h in the multiarch location breaks the GCC and LLVM multilib builds'. > tags -1 + moreinfo Bug #1014114 [libcrypt-dev] installation of crypt.h in the multiarch location breaks the GCC and LLVM multilib builds Added tag(s) moreinfo. -- 1014114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014114 1014134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014133: asterisk: Asterisk fails to build from source
Package: asterisk Version: 1:16.16.1~dfsg-1+deb11u1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear Maintainer, I'm trying to build asterisk from source (bullseye) using: dpkg-buildpackage -rfakeroot Looks like the verification of the needed pjproject sub-project fails. The last relevant lines from configure: configure:9241: checking for embedded pjproject (may have to download) configure:9243: result: configuring configure:9310: result: failed configure:9312: Unable to configure third-party/pjproject configure:9314: error: Re-run the ./configure command with 'NOISY_BUILD=yes' appended to see error details. If I re-run this, it tries to download the pjproject tarball and fails to verify the checksum. If I clean (debian/rules clean) and configure by hand it seems to be able to verify (but fails later with a different error). Let me know if I'm missing some trick here and if you need additional information. My plan (why I'm trying to re-build) is to include a simple patch to res/res_pjsip_messaging.c to allow content-types other than text/plain. But I'm failing on the unmodified Debian sources. -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-15-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages asterisk depends on: ii adduser 3.118 ii asterisk-config 1:16.16.1~dfsg-1+deb11u1 ii asterisk-core-sounds-en 1.6.1-1 ii asterisk-modules 1:16.16.1~dfsg-1+deb11u1 ii libc62.31-13+deb11u3 ii libcap2 1:2.44-1 ii libcrypt11:4.4.18-4 ii libedit2 3.1-20191231-2+b1 ii libjansson4 2.13.1-1.1 ii libpopt0 1.18-2 ii libsqlite3-0 3.34.1-3 ii libssl1.11.1.1n-0+deb11u3 ii libsystemd0 247.3-7 ii liburiparser10.9.4+dfsg-1+deb11u1 ii libuuid1 2.36.1-8+deb11u1 ii libxml2 2.9.10+dfsg-6.7+deb11u2 ii libxslt1.1 1.1.34-4 ii lsb-base 11.1.0 Versions of packages asterisk recommends: ii asterisk-moh-opsound-gsm 2.03-1.1 ii asterisk-voicemail [asterisk-voicemail-storage] 1:16.16.1~dfsg-1+deb11u1 ii sox 14.4.2+git20190427-2 Versions of packages asterisk suggests: pn asterisk-dahdi ii asterisk-dev 1:16.16.1~dfsg-1+deb11u1 pn asterisk-doc pn asterisk-ooh323 pn asterisk-opus pn asterisk-vpb -- no debconf information
Bug#1014115: uninstall does not properly remove enablement symlinks
Am 30.06.22 um 16:32 schrieb Luca Boccassi: On Thu, 30 Jun 2022 at 15:24, Michael Biebl wrote: - masking a service upon uninstallation This is a sad reality, as packages still ship legacy SysV init scripts which are conffiles and would suddenly become active if a package is removed but not purged. At some point we should just nuke the sysv unit generator upstream. It's been 10+ years, there was plenty of time to add native units where needed. Then this becomes moot - the old init scripts would be just inert when booting under systemd. Dropping SysV init support would indeed solve that issue. $ apt-file search /etc/init.d/ | wc -l 1311 $ apt-file search /etc/init.d/ | cut -f1 -d':' | sort -u | wc -l 1180 So we have 1180 package shipping 1311 SysV init scripts. According to [1], we have 314 source packages which lack 365 service units. So our coverage is only about 72%. Dropping systemd-sysv-generator would break quite a lot of packages. Too many imho. Before we can do this, there should be a more active push to get the remaining packages migrated. A MBF seems like a good first step. This needs someone though to actively work on this. Any volunteers? [1] https://lintian.debian.org/tags/missing-systemd-service-for-init.d-script OpenPGP_signature Description: OpenPGP digital signature
Processed: [bts-link] source package src:handbrake
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:handbrake > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1004828 (http://bugs.debian.org/1004828) > # Bug title: handbrake: FTBFS with ffmpeg 5.0 > # * https://github.com/HandBrake/HandBrake/issues/4105 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1004828 + fixed-upstream Bug #1004828 [src:handbrake] handbrake: FTBFS with ffmpeg 5.0 Added tag(s) fixed-upstream. > usertags 1004828 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1004828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:lua-luaossl
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:lua-luaossl > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1005697 (http://bugs.debian.org/1005697) > # Bug title: lua-luaossl: FTBFS with OpenSSL 3.0 > # * https://github.com/wahern/luaossl/issues/195 > # * remote status changed: open -> closed > # * closed upstream > tags 1005697 + fixed-upstream Bug #1005697 [src:lua-luaossl] lua-luaossl: FTBFS with OpenSSL 3.0 Added tag(s) fixed-upstream. > usertags 1005697 - status-open Usertags were: status-open. There are now no usertags set. > usertags 1005697 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1005697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005697 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010430: marked as done (tifffile breaks skimage autopkgtest: asarray() got an unexpected keyword argument 'multifile')
Your message dated Thu, 30 Jun 2022 17:22:35 +
with message-id
and subject line Bug#1010430: fixed in skimage 0.19.3-1
has caused the Debian Bug report #1010430,
regarding tifffile breaks skimage autopkgtest: asarray() got an unexpected
keyword argument 'multifile'
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.)
--
1010430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tifffile, skimage
Control: found -1 tifffile/20220426-1
Control: found -1 skimage/0.18.3-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of tifffile the autopkgtest of skimage fails in
testing when that autopkgtest is run with the binary packages of
tifffile from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
tifffile from testing20220426-1
skimagefrom testing0.18.3-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 of tifffile to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?
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=tifffile
https://ci.debian.net/data/autopkgtest/testing/amd64/s/skimage/21268058/log.gz
___ test_tifffile_kwarg_passthrough
def test_tifffile_kwarg_passthrough ():
img = imread(fetch('data/multipage.tif'), key=[1],
multifile=False, multifile_close=True, fastij=True,
is_ome=True)
/usr/lib/python3/dist-packages/skimage/io/tests/test_tifffile.py:41: _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ /usr/lib/python3/dist-packages/skimage/io/_io.py:48: in imread
img = call_plugin('imread', fname, plugin=plugin, **plugin_args)
/usr/lib/python3/dist-packages/skimage/io/manage_plugins.py:207: in
call_plugin
return func(*args, **kwargs)
/usr/lib/python3/dist-packages/skimage/io/_plugins/tifffile_plugin.py:30: in
imread
return tifffile_imread(fname, **kwargs)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
files = '/usr/lib/python3/dist-packages/skimage/data/../data/multipage.tif'
aszarr = False
kwargs = {'fastij': True, 'key': [1], 'multifile': False,
'multifile_close': True}
kwargs_file = {'is_ome': True}, kwargs_seq = {}
tif =
def imread(
files: str
| os.PathLike
| FileHandle
| BinaryIO
| Sequence[str | os.PathLike]
| None = None,
*,
aszarr: bool = False,
**kwargs,
) -> numpy.ndarray | ZarrTiffStore | ZarrFileSequenceStore:
"""Return image data from TIFF file(s) as numpy array or zarr
storage.
Refer to the TiffFile and TiffSequence classes and their
asarray
functions for documentation.
Parameters
--
files : path-like, binary stream, or sequence
File name, seekable binary stream, glob pattern, or sequence of
file names. May be None (default) if 'container' is specified.
aszarr : bool
If True, return file sequences, series, or single pages as
zarr storage instead of numpy array (experimental).
**kwargs
Optional extra arguments.
Parameters 'name', 'offset', 'size', and 'is_' flags are
passed to
TiffFile or TiffSequence.imread.
Parameters 'imread', 'container', 'sort', 'pattern',
'axesorder',
and 'categories' are passed to TiffSequence.
Other parameters are passed to the asarray or aszarr functions.
The first image series in the file is returned if no
arguments are
provided.
Returns
---
numpy.ndarray or zarr storage
Image data from the specified pages.
Zarr storage instances must be closed after use.
See TiffPage.asarray for operations that are applied (or not)
to the raw data stored in the file.
"""
kwargs_file = parse_kwargs(
Bug#1011444: marked as done (ruby-gitlab-markup: missing Breaks+Replaces: ruby-github-markup (<< 1.7.0+dfsg-4~))
Your message dated Thu, 30 Jun 2022 16:36:11 + with message-id and subject line Bug#1011444: fixed in ruby-gitlab-markup 1.8.0-3 has caused the Debian Bug report #1011444, regarding ruby-gitlab-markup: missing Breaks+Replaces: ruby-github-markup (<< 1.7.0+dfsg-4~) 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.) -- 1011444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011444 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ruby-gitlab-markup Version: 1.8.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces This test intentionally skipped 'testing' to find file overwrite problems before packages migrate from 'unstable' to 'testing'. >From the attached log (scroll to the bottom...): Preparing to unpack .../ruby-gitlab-markup_1.8.0-1_all.deb ... Unpacking ruby-gitlab-markup (1.8.0-1) ... dpkg: error processing archive /var/cache/apt/archives/ruby-gitlab-markup_1.8.0-1_all.deb (--unpack): trying to overwrite '/usr/lib/ruby/vendor_ruby/github/commands/rest2html', which is also in package ruby-github-markup 1.7.0+dfsg-3 Errors were encountered while processing: /var/cache/apt/archives/ruby-gitlab-markup_1.8.0-1_all.deb (There is no file conflict with ruby-github-markup (1.7.0+dfsg-4) in sid.) cheers, Andreas ruby-github-markup=1.7.0+dfsg-3_ruby-gitlab-markup=1.8.0-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: ruby-gitlab-markup Source-Version: 1.8.0-3 Done: Pirate Praveen We believe that the bug you reported is fixed in the latest version of ruby-gitlab-markup, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated ruby-gitlab-markup package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 30 Jun 2022 20:51:38 +0530 Source: ruby-gitlab-markup Architecture: source Version: 1.8.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Pirate Praveen Closes: 1011444 Changes: ruby-gitlab-markup (1.8.0-3) unstable; urgency=medium . * Team Upload * Add Breaks: ruby-github-markup (<< 1.7.0+dfsg-4~) (Closes: #1011444) Checksums-Sha1: fc090ee1f841eb5cb008dca90b67c1180a9f17c8 2408 ruby-gitlab-markup_1.8.0-3.dsc ec1a38eb46db0c5b0a77cbc1bc7a6fa70b4e0240 5224 ruby-gitlab-markup_1.8.0-3.debian.tar.xz 7833233e70318eabe1cce75cb2b92d67e8c41648 10197 ruby-gitlab-markup_1.8.0-3_amd64.buildinfo Checksums-Sha256: 3f1162d87aa68dac7dc463dd02cec633de7a8dedce683c093e901969dc8ba452 2408 ruby-gitlab-markup_1.8.0-3.dsc 14cd2c9cc59db7877289faccd536c69614ba690743781fb22ee5a2c0bcfef142 5224 ruby-gitlab-markup_1.8.0-3.debian.tar.xz 8324545bf3a791004b1033ad1231c41f9bef376a3dc8f4d07a99cb61c885c0aa 10197 ruby-gitlab-markup_1.8.0-3_amd64.buildinfo Files: 7ec0cd76824162af3ed38af83eabd258 2408 ruby optional ruby-gitlab-markup_1.8.0-3.dsc a54687f77b89220a78f3af2836cf0c89 5224 ruby optional ruby-gitlab-markup_1.8.0-3.debian.tar.xz fa253f3cb09f06a83c0f647fd5c4abde 10197 ruby optional ruby-gitlab-markup_1.8.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0whj4mAg5UP0cZqDj1PgGTspS3UFAmK9w1QACgkQj1PgGTsp S3X97g/+KtVwX/Lyxg7w7eOn85sSDALp5DHFJjSeL5uRY4I12SYXaAkcPujawFOw t1LXSGdZtj1AQGDAQLfmPro07vPe1eStzAI6YILUHHVVYWGAP7c/v2mU7w/l7uir jAHf7BmW6Py57qo09phOEkmiOyNOicyYIJloN3kim0jdqm8vQy0R375MDZlX7u1u je06SXMfa9QNZfrwzC51m5xJVqSdDl/YlT6wdIobmVtmKsT3DCi/IIDO5rYegfc6 Wd0mOQSd3PpW//LGVwRT6BvLE8Ipu6O+1j87BmkV+GO+ZgkO2IAM6WEinPwOJ08e PUWBDs+21Zt+r17pDQ2m3+39ZGjNEqFALSuJ1yhC0CYsaSglBkKJkzJx3IIRl/ek r7dDnHadFH6SUTOyczPfgnwWI1/DjVC59frYqIJXFDHzyViEOrlj+IWZoGZGZ25d
Bug#1014100: We should do an update of all qiime2 modules as soon as possible (Was: Bug#1014100: qiime: autopkgtest needs update for new version of python-decorator)
On 30.06.22 11:51, Andreas Tille wrote: I'd like to point out to this serious bug. Steffen, would you mind koordinating (not doing alone) an upgrade of the qiime infrastructure to make sure everything will go smoothly? I added "to be updated" tags to all the qiime2 packages on https://docs.google.com/spreadsheets/d/1tApLhVqxRZ2VOuMH_aPUgFENQJfbLlB_PFH_Ah_q7hM/edit#gid=1986383821 Yes, these updates are overdue. I'll see what I can do, help is of course much appreciated. Many thanks! Steffen
Bug#1014115: uninstall does not properly remove enablement symlinks
Am 30.06.22 um 17:31 schrieb Luca Boccassi: On Thu, 30 Jun 2022 at 15:44, Michael Biebl wrote: Am 30.06.22 um 16:32 schrieb Luca Boccassi: On Thu, 30 Jun 2022 at 15:24, Michael Biebl wrote: Am 30.06.22 um 16:13 schrieb Luca Boccassi: On Thu, 30 Jun 2022 at 15:08, Michael Biebl wrote: Am 30.06.22 um 14:26 schrieb Michael Biebl: This might be a bug in i-s-h, but filing against systemd-homed for now. systemd-homed.service: [Install] WantedBy=multi-user.target Alias=dbus-org.freedesktop.home1.service Also=systemd-homed-activate.service systemd-userdbd.service systemd-homed-activate.service: [Install] WantedBy=systemd-homed.service Also=systemd-homed.service → we have a circular dependency here, maybe deb-systemd-helper get's confused by that I just checked that we can mitigate this issue by removing this circular Also= dependency. It is indeed deb-systemd-helper getting confused by that and as a result not writing proper state files to /var/lib/systemd/deb-systemd-helper. So the damage is already done during installation in postinst. Thus raising to RC to warn users from installing systemd-homed atm. I propose a patch like the attached one, i.e. dropping the Also= from systemd-homed-active.service. WDYT? Are you against shipping this patch for the time being until we have a proper fix? Given the problem is that i-s-h doesn't generate the correct postinst, can we instead add a workaround to the postinst itself? No, it's not an incorrect postinst. The generated postinst code looks fine afaics. It's deb-systemd-helper failing in postinst [1] (due to the circular Also=) and subsequently not writing any state files to /var/lib/systemd/deb-systemd-helper (which means it can't clean up the state on purge). I'm pasting the error message again, for reference Setting up systemd-homed (251.2-7) ... Created symlink /etc/systemd/system/systemd-homed.service.wants/systemd-homed-activate.service -> /lib/systemd/system/systemd-homed-activate.service. Created symlink /etc/systemd/system/dbus-org.freedesktop.home1.service -> /lib/systemd/system/systemd-homed.service. Created symlink /etc/systemd/system/multi-user.target.wants/systemd-homed.service -> /lib/systemd/system/systemd- homed.service. Deep recursion on subroutine "main::get_link_closure" at /usr/bin/deb-systemd-helper line 253, <$fh> line 23. /usr/bin/deb-systemd-helper: error: unable to read /lib/systemd/system/systemd-homed.service Deep recursion on subroutine "main::get_link_closure" at /usr/bin/deb-systemd-helper line 253, <$fh> line 41. /usr/bin/deb-systemd-helper: error: unable to read /lib/systemd/system/systemd-homed-activate.service I see, then could it be fixed in the postinst manually after the calls added by the helper? I don't see how. OpenPGP_signature Description: OpenPGP digital signature
Bug#1013603: marked as done (python-enmerkar: FTBFS: tests fail)
Your message dated Thu, 30 Jun 2022 16:08:00 + with message-id and subject line Bug#1013603: fixed in python-enmerkar 0.7.1-4 has caused the Debian Bug report #1013603, regarding python-enmerkar: FTBFS: tests fail to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1013603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013603 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-enmerkar Version: 0.7.1-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220624 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > make[1]: pyversions: No such file or directory > py3versions: no X-Python3-Version in control file, using supported versions > pkgos-dh_auto_install --no-py2 --in-tmp > + PKGOS_USE_PY2=yes > + PKGOS_USE_PY3=yes > + PKGOS_IN_TMP=no > + PKGOS_USE_PY2=no > + shift > + PKGOS_IN_TMP=yes > + shift > + dpkg-parsechangelog -SSource > + SRC_PKG_NAME=python-enmerkar > + echo python-enmerkar > + sed s/python-// > + PY_MODULE_NAME=enmerkar > + [ no = yes ] > + [ yes = yes ] > + py3versions -vr > + PYTHON3S=3.9 3.10 > + [ no = yes ] > + [ yes = yes ] > + [ yes = yes ] > + TARGET_DIR=tmp > + pwd > + python3.9 setup.py install --install-layout=deb --root > /<>/debian/tmp > running install > /usr/lib/python3/dist-packages/setuptools/command/install.py:34: > SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and > pip and other standards-based tools. > warnings.warn( > running build > running build_py > creating build > creating build/lib > creating build/lib/enmerkar > copying enmerkar/__init__.py -> build/lib/enmerkar > copying enmerkar/middleware.py -> build/lib/enmerkar > copying enmerkar/extract.py -> build/lib/enmerkar > creating build/lib/enmerkar/management > copying enmerkar/management/__init__.py -> build/lib/enmerkar/management > creating build/lib/enmerkar/templatetags > copying enmerkar/templatetags/__init__.py -> build/lib/enmerkar/templatetags > copying enmerkar/templatetags/babel.py -> build/lib/enmerkar/templatetags > creating build/lib/enmerkar/management/commands > copying enmerkar/management/commands/__init__.py -> > build/lib/enmerkar/management/commands > copying enmerkar/management/commands/babel.py -> > build/lib/enmerkar/management/commands > running install_lib > creating /<>/debian/tmp > creating /<>/debian/tmp/usr > creating /<>/debian/tmp/usr/lib > creating /<>/debian/tmp/usr/lib/python3 > creating /<>/debian/tmp/usr/lib/python3/dist-packages > creating /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar > copying build/lib/enmerkar/__init__.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar > copying build/lib/enmerkar/middleware.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar > copying build/lib/enmerkar/extract.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar > creating > /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/management > creating > /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/management/commands > copying build/lib/enmerkar/management/commands/__init__.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/management/commands > copying build/lib/enmerkar/management/commands/babel.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/management/commands > copying build/lib/enmerkar/management/__init__.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/management > creating > /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/templatetags > copying build/lib/enmerkar/templatetags/__init__.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/templatetags > copying build/lib/enmerkar/templatetags/babel.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/templatetags > byte-compiling > /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/__init__.py > to __init__.cpython-39.pyc > byte-compiling > /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/middleware.py > to middleware.cpython-39.pyc > byte-compiling > /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/extract.py > to extract.cpython-39.pyc > byte-compiling > /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/management/commands/__init__.py > to __init__.cpython-39.pyc > byte-compiling > /<>/debian/tmp/usr/lib/python3/dist-packages/enmerkar/management/commands/babel.py > to babel.cpython-39.pyc > byte-compiling >
Bug#1000474: marked as done (icingaweb2: Does not work with PHP 8.1)
Your message dated Thu, 30 Jun 2022 16:02:23 + with message-id and subject line Bug#1000474: fixed in icingaweb2 2.11.0-1 has caused the Debian Bug report #1000474, regarding icingaweb2: Does not work with PHP 8.1 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.) -- 1000474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000474 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: icingaweb2 Version: 2.9.5-1 Severity: important Tags: upstream Control: forwarded -1 https://github.com/Icinga/icingaweb2/issues/4609 Control: block 976811 by -1 Dear Maintainer, icingaweb2 does not work with php8.1 from experimental. The web page shows lots of deprecations and a fatal error: Deprecated: Return type of Icinga\Application\Libraries::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/php/Icinga/Application/Libraries.php on line 20 Deprecated: Return type of Icinga\Application\Config::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/php/Icinga/Application/Config.php on line 125 Deprecated: Return type of Icinga\Application\Config::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/php/Icinga/Application/Config.php on line 145 Deprecated: Return type of Icinga\Application\Config::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/php/Icinga/Application/Config.php on line 175 Deprecated: Return type of Icinga\Application\Config::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/php/Icinga/Application/Config.php on line 165 Deprecated: Return type of Icinga\Application\Config::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/php/Icinga/Application/Config.php on line 155 Deprecated: Return type of Icinga\Application\Config::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/php/Icinga/Application/Config.php on line 135 Deprecated: Return type of Icinga\Web\Session\SessionNamespace::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/php/Icinga/Web/Session/SessionNamespace.php on line 35 Deprecated: Return type of Zend_Controller_Action_HelperBroker_PriorityStack::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/icingaweb2/library/vendor/Zend/Controller/Action/HelperBroker/PriorityStack.php on line 91 Deprecated: Return type of Zend_Controller_Action_HelperBroker_PriorityStack::offsetExists($priorityOrHelperName) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/icingaweb2/library/vendor/Zend/Controller/Action/HelperBroker/PriorityStack.php on line 102 Deprecated: Return type of Zend_Controller_Action_HelperBroker_PriorityStack::offsetGet($priorityOrHelperName) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/icingaweb2/library/vendor/Zend/Controller/Action/HelperBroker/PriorityStack.php on line 117 Deprecated: Return type of Zend_Controller_Action_HelperBroker_PriorityStack::offsetSet($priority, $helper) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/icingaweb2/library/vendor/Zend/Controller/Action/HelperBroker/PriorityStack.php on
Bug#1014115: uninstall does not properly remove enablement symlinks
On Thu, 30 Jun 2022 at 15:44, Michael Biebl wrote: > > Am 30.06.22 um 16:32 schrieb Luca Boccassi: > > On Thu, 30 Jun 2022 at 15:24, Michael Biebl wrote: > >> > >> Am 30.06.22 um 16:13 schrieb Luca Boccassi: > >>> On Thu, 30 Jun 2022 at 15:08, Michael Biebl wrote: > > Am 30.06.22 um 14:26 schrieb Michael Biebl: > > This might be a bug in i-s-h, but filing against systemd-homed for > > now. > > > > systemd-homed.service: > > [Install] > > WantedBy=multi-user.target > > Alias=dbus-org.freedesktop.home1.service > > Also=systemd-homed-activate.service systemd-userdbd.service > > > > systemd-homed-activate.service: > > [Install] > > WantedBy=systemd-homed.service > > Also=systemd-homed.service > > > > → we have a circular dependency here, maybe deb-systemd-helper get's > > confused by that > > > I just checked that we can mitigate this issue by removing this circular > Also= dependency. It is indeed deb-systemd-helper getting confused by > that and as a result not writing proper state files to > /var/lib/systemd/deb-systemd-helper. > So the damage is already done during installation in postinst. > Thus raising to RC to warn users from installing systemd-homed atm. > > I propose a patch like the attached one, i.e. dropping the Also= from > systemd-homed-active.service. WDYT? > >> > >> Are you against shipping this patch for the time being until we have a > >> proper fix? > > > > Given the problem is that i-s-h doesn't generate the correct postinst, > > can we instead add a workaround to the postinst itself? > > No, it's not an incorrect postinst. The generated postinst code looks > fine afaics. > > It's deb-systemd-helper failing in postinst [1] (due to the circular > Also=) and subsequently not writing any state files to > /var/lib/systemd/deb-systemd-helper (which means it can't clean up the > state on purge). > > > I'm pasting the error message again, for reference > > > Setting up systemd-homed (251.2-7) ... > > Created symlink > > /etc/systemd/system/systemd-homed.service.wants/systemd-homed-activate.service > > -> /lib/systemd/system/systemd-homed-activate.service. > > Created symlink /etc/systemd/system/dbus-org.freedesktop.home1.service -> > > /lib/systemd/system/systemd-homed.service. > > Created symlink > > /etc/systemd/system/multi-user.target.wants/systemd-homed.service -> > > /lib/systemd/system/systemd- > > homed.service. > > Deep recursion on subroutine "main::get_link_closure" at > > /usr/bin/deb-systemd-helper line 253, <$fh> line 23. > > /usr/bin/deb-systemd-helper: error: unable to read > > /lib/systemd/system/systemd-homed.service > > Deep recursion on subroutine "main::get_link_closure" at > > /usr/bin/deb-systemd-helper line 253, <$fh> line 41. > > /usr/bin/deb-systemd-helper: error: unable to read > > /lib/systemd/system/systemd-homed-activate.service I see, then could it be fixed in the postinst manually after the calls added by the helper?
Processed: Re: armhf: gcc has wrong configuration
Processing control commands: > reassign -1 src:valgrind Bug #1014091 [gcc-11] armhf: gcc has wrong configuration Bug reassigned from package 'gcc-11' to 'src:valgrind'. No longer marked as found in versions gcc-11/11.3.0-3. Ignoring request to alter fixed versions of bug #1014091 to the same values previously set > severity -1 serious Bug #1014091 [src:valgrind] armhf: gcc has wrong configuration Severity set to 'serious' from 'normal' -- 1014091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014091 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: uhd: binary-any FTBFS
Processing control commands: > found -1 4.2.0.0+ds1-1 Bug #1014127 [src:uhd] uhd: binary-any FTBFS Marked as found in versions uhd/4.2.0.0+ds1-1. -- 1014127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014127 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014127: uhd: binary-any FTBFS
Source: uhd Version: 4.2.0.0+dfsg-1 Severity: serious Tags: ftbfs Control: found -1 4.2.0.0+ds1-1 https://buildd.debian.org/status/logs.php?pkg=uhd=4.2.0.0%2Bdfsg-1 https://buildd.debian.org/status/logs.php?pkg=uhd=4.2.0.0%2Bds1-1 ... dh_installman -a -O--sourcedirectory=host -O--buildsystem=cmake\+ninja dh_installman: error: Cannot find (any matches for) "usr/share/man/man1/usrpctl.1.gz" (tried in ., debian/tmp) dh_installman: error: Aborting due to earlier error
Bug#1014124: nomacs: CVE-2020-23884
Source: nomacs X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for nomacs. CVE-2020-23884[0]: | A buffer overflow in Nomacs v3.15.0 allows attackers to cause a denial | of service (DoS) via a crafted MNG file. https://github.com/nomacs/nomacs/issues/516 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-2020-23884 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-23884 Please adjust the affected versions in the BTS as needed.
Bug#1014115: uninstall does not properly remove enablement symlinks
Am 30.06.22 um 16:32 schrieb Luca Boccassi: On Thu, 30 Jun 2022 at 15:24, Michael Biebl wrote: Am 30.06.22 um 16:13 schrieb Luca Boccassi: On Thu, 30 Jun 2022 at 15:08, Michael Biebl wrote: Am 30.06.22 um 14:26 schrieb Michael Biebl: This might be a bug in i-s-h, but filing against systemd-homed for now. systemd-homed.service: [Install] WantedBy=multi-user.target Alias=dbus-org.freedesktop.home1.service Also=systemd-homed-activate.service systemd-userdbd.service systemd-homed-activate.service: [Install] WantedBy=systemd-homed.service Also=systemd-homed.service → we have a circular dependency here, maybe deb-systemd-helper get's confused by that I just checked that we can mitigate this issue by removing this circular Also= dependency. It is indeed deb-systemd-helper getting confused by that and as a result not writing proper state files to /var/lib/systemd/deb-systemd-helper. So the damage is already done during installation in postinst. Thus raising to RC to warn users from installing systemd-homed atm. I propose a patch like the attached one, i.e. dropping the Also= from systemd-homed-active.service. WDYT? Are you against shipping this patch for the time being until we have a proper fix? Given the problem is that i-s-h doesn't generate the correct postinst, can we instead add a workaround to the postinst itself? No, it's not an incorrect postinst. The generated postinst code looks fine afaics. It's deb-systemd-helper failing in postinst [1] (due to the circular Also=) and subsequently not writing any state files to /var/lib/systemd/deb-systemd-helper (which means it can't clean up the state on purge). I'm pasting the error message again, for reference Setting up systemd-homed (251.2-7) ... Created symlink /etc/systemd/system/systemd-homed.service.wants/systemd-homed-activate.service -> /lib/systemd/system/systemd-homed-activate.service. Created symlink /etc/systemd/system/dbus-org.freedesktop.home1.service -> /lib/systemd/system/systemd-homed.service. Created symlink /etc/systemd/system/multi-user.target.wants/systemd-homed.service -> /lib/systemd/system/systemd- homed.service. Deep recursion on subroutine "main::get_link_closure" at /usr/bin/deb-systemd-helper line 253, <$fh> line 23. /usr/bin/deb-systemd-helper: error: unable to read /lib/systemd/system/systemd-homed.service Deep recursion on subroutine "main::get_link_closure" at /usr/bin/deb-systemd-helper line 253, <$fh> line 41. /usr/bin/deb-systemd-helper: error: unable to read /lib/systemd/system/systemd-homed-activate.service OpenPGP_signature Description: OpenPGP digital signature
Bug#1014115: uninstall does not properly remove enablement symlinks
On Thu, 30 Jun 2022 at 15:24, Michael Biebl wrote: > > Am 30.06.22 um 16:13 schrieb Luca Boccassi: > > On Thu, 30 Jun 2022 at 15:08, Michael Biebl wrote: > >> > >> Am 30.06.22 um 14:26 schrieb Michael Biebl: > >>> This might be a bug in i-s-h, but filing against systemd-homed for > >>> now. > >>> > >>> systemd-homed.service: > >>> [Install] > >>> WantedBy=multi-user.target > >>> Alias=dbus-org.freedesktop.home1.service > >>> Also=systemd-homed-activate.service systemd-userdbd.service > >>> > >>> systemd-homed-activate.service: > >>> [Install] > >>> WantedBy=systemd-homed.service > >>> Also=systemd-homed.service > >>> > >>> → we have a circular dependency here, maybe deb-systemd-helper get's > >>> confused by that > >> > >> > >> I just checked that we can mitigate this issue by removing this circular > >> Also= dependency. It is indeed deb-systemd-helper getting confused by > >> that and as a result not writing proper state files to > >> /var/lib/systemd/deb-systemd-helper. > >> So the damage is already done during installation in postinst. > >> Thus raising to RC to warn users from installing systemd-homed atm. > >> > >> I propose a patch like the attached one, i.e. dropping the Also= from > >> systemd-homed-active.service. WDYT? > > Are you against shipping this patch for the time being until we have a > proper fix? Given the problem is that i-s-h doesn't generate the correct postinst, can we instead add a workaround to the postinst itself? > >> I've also cloned the issue for i-s-h, as we might want to fix that > >> properly. My perl is a bit rusty, so would appreciate help with that. > >> > >> @bluca: do you think the attached patch is suitable for upstream? > >> > >> I find this circular Also= dependency kinda odd, I have to admit. > > > > I don't think so, this seems clearly a bug in i-s-h. Ideally we should > > really drop all of that and just use presets as RPMs do... but it's a > > lot of work. > > We have i-s-h/deb-systemd-helper for a couple of reasons (none of which > can be solved by presets afaics) > > - distinction between uninstalled/purged state in Debian. > We want to ensure that if you have a install/remove/install sequence, > the enablement state of the service is preserved. > For that we need to keep additional state, that is only removed on purge. > If we remove the enablement symlinks on remove, we can't preserve the state. > If we remove the enablement symlinks on purge, the service files are no > longer around, so we can't do a proper cleanup. i-s-h could be reduced to ship snippets that simply maintain this state after a remove till the next install/purge? > - masking a service upon uninstallation > This is a sad reality, as packages still ship legacy SysV init scripts > which are conffiles and would suddenly become active if a package is > removed but not purged. At some point we should just nuke the sysv unit generator upstream. It's been 10+ years, there was plenty of time to add native units where needed. Then this becomes moot - the old init scripts would be just inert when booting under systemd. > I certainly would like to get rid of i-s-h, but I don't see how that is > doable. > > Regards, > Michael > >
Bug#1013299: Fwd: Patch "net/sched: move NULL ptr check to qdisc_put() too" has been added to the 4.19-stable tree
Patch has been added to the 4.19 queue:
-- Forwarded Message --
Subject: Patch "net/sched: move NULL ptr check to qdisc_put() too" has been
added to the 4.19-stable tree
Date: donderdag 30 juni 2022, 15:29:23 CEST
From: gre...@linuxfoundation.org
To: didi.deb...@cknow.org, gre...@linuxfoundation.org, t...@mirbsd.de,
vla...@mellanox.com
CC: stable-comm...@vger.kernel.org
This is a note to let you know that I've just added the patch titled
net/sched: move NULL ptr check to qdisc_put() too
to the 4.19-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
net-sched-move-null-ptr-check-to-qdisc_put-too.patch
and it can be found in the queue-4.19 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let know about it.
>From didi.deb...@cknow.org Thu Jun 30 15:24:25 2022
From: Diederik de Haas
Date: Thu, 30 Jun 2022 00:49:38 +0200
Subject: net/sched: move NULL ptr check to qdisc_put() too
To: sta...@vger.kernel.org
Cc: Vlad Buslov , Diederik de Haas
, Thorsten Glaser
Message-ID: <20220629224938.7760-1-didi.deb...@cknow.org>
From: Diederik de Haas
In commit 92833e8b5db6c209e9311ac8c6a44d3bf1856659 titled
"net: sched: rename qdisc_destroy() to qdisc_put()" part of the
functionality of qdisc_destroy() was moved into a (for linux-4.19.y)
new function qdisk_put(), and the previous calls to qdisc_destroy()
were changed to qdisk_put().
This made it similar to f.e. 5.10.y and current master.
There was one part of qdisc_destroy() not moved over to qdisc_put() and
that was the check for a NULL pointer, causing oopses.
(See upstream commit: 6efb971ba8edfbd80b666f29de12882852f095ae)
This patch fixes that.
Fixes: 92833e8b5db6c209e9311ac8c6a44d3bf1856659
Reported-by: Thorsten Glaser
Link: https://bugs.debian.org/1013299
Signed-off-by: Diederik de Haas
Signed-off-by: Greg Kroah-Hartman
---
net/sched/sch_generic.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--- a/net/sched/sch_generic.c
+++ b/net/sched/sch_generic.c
@@ -970,8 +970,6 @@ static void qdisc_destroy(struct Qdisc *
const struct Qdisc_ops *ops;
struct sk_buff *skb, *tmp;
- if (!qdisc)
- return;
ops = qdisc->ops;
#ifdef CONFIG_NET_SCHED
@@ -1003,6 +1001,9 @@ static void qdisc_destroy(struct Qdisc *
void qdisc_put(struct Qdisc *qdisc)
{
+ if (!qdisc)
+ return;
+
if (qdisc->flags & TCQ_F_BUILTIN ||
!refcount_dec_and_test(>refcnt))
return;
Patches currently in stable-queue which might be from didi.deb...@cknow.org
are
queue-4.19/net-sched-move-null-ptr-check-to-qdisc_put-too.patch
-
signature.asc
Description: This is a digitally signed message part.
Bug#1014120: libowfat FTBFS: ln: failed to create hard link 'libowfat/buffer.h'
Source: libowfat Version: 0.32-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=libowfat=0.32-1 ... /usr/bin/make -f /<>/GNUmakefile -C build-glibc SRC=/<>/ CFLAGS="-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I.." DIET='' make[2]: Entering directory '/<>/build-glibc' ln -f /<>/buffer.h libowfat/buffer.h ln: failed to create hard link 'libowfat/buffer.h' => '/<>/buffer.h': No such file or directory make[2]: *** [/<>/GNUmakefile:217: libowfat/buffer.h] Error 1
Bug#1014115: uninstall does not properly remove enablement symlinks
Am 30.06.22 um 16:13 schrieb Luca Boccassi: On Thu, 30 Jun 2022 at 15:08, Michael Biebl wrote: Am 30.06.22 um 14:26 schrieb Michael Biebl: This might be a bug in i-s-h, but filing against systemd-homed for now. systemd-homed.service: [Install] WantedBy=multi-user.target Alias=dbus-org.freedesktop.home1.service Also=systemd-homed-activate.service systemd-userdbd.service systemd-homed-activate.service: [Install] WantedBy=systemd-homed.service Also=systemd-homed.service → we have a circular dependency here, maybe deb-systemd-helper get's confused by that I just checked that we can mitigate this issue by removing this circular Also= dependency. It is indeed deb-systemd-helper getting confused by that and as a result not writing proper state files to /var/lib/systemd/deb-systemd-helper. So the damage is already done during installation in postinst. Thus raising to RC to warn users from installing systemd-homed atm. I propose a patch like the attached one, i.e. dropping the Also= from systemd-homed-active.service. WDYT? Are you against shipping this patch for the time being until we have a proper fix? I've also cloned the issue for i-s-h, as we might want to fix that properly. My perl is a bit rusty, so would appreciate help with that. @bluca: do you think the attached patch is suitable for upstream? I find this circular Also= dependency kinda odd, I have to admit. I don't think so, this seems clearly a bug in i-s-h. Ideally we should really drop all of that and just use presets as RPMs do... but it's a lot of work. We have i-s-h/deb-systemd-helper for a couple of reasons (none of which can be solved by presets afaics) - distinction between uninstalled/purged state in Debian. We want to ensure that if you have a install/remove/install sequence, the enablement state of the service is preserved. For that we need to keep additional state, that is only removed on purge. If we remove the enablement symlinks on remove, we can't preserve the state. If we remove the enablement symlinks on purge, the service files are no longer around, so we can't do a proper cleanup. - masking a service upon uninstallation This is a sad reality, as packages still ship legacy SysV init scripts which are conffiles and would suddenly become active if a package is removed but not purged. I certainly would like to get rid of i-s-h, but I don't see how that is doable. Regards, Michael OpenPGP_signature Description: OpenPGP digital signature
Bug#1010355: Fwd: Bug#1010355: CVE-2022-0530: null pointer dereference on invalid UTF-8 input
Am Thu, Jun 30, 2022 at 02:16:55PM +0200 schrieb Santiago Vila:
> Dear Steven and Mark:
>
> I plan to apply the attached patches (from Enrico Zini) to fix CVE-2022-0529
> and CVE-2022-0530 in Debian unzip, but before doing so I would like to have
> some feedback from upstream (i.e. you) or either from the Security Team
> (also in CC).
>
> Details about the bug here:
>
> https://bugs.debian.org/1010355
>
> The test cases triggering the bug are here:
>
> https://github.com/ByteHackr/unzip_poc
Hi,
note that we need some additional clarification on what the scope of
CVE-2022-0529 and CVE-2022-0530 is. Both originated from Red Hat Bugzilla:
---
https://bugzilla.redhat.com/show_bug.cgi?id=2051395 is the public reference
for CVE-2022-0530 and this links to a private Red Hat bug
SIGSEGV during the conversion of an utf-8 string to a local string:
https://bugzilla.redhat.com/show_bug.cgi?id=2048569
---
https://bugzilla.redhat.com/show_bug.cgi?id=2051402 is the public reference
for CVE-2022-0529 and this links to a different private Red Hat bug:
Heap out-of-bound writes and reads during conversion of wide string to local
string
https://bugzilla.redhat.com/show_bug.cgi?id=2048572
---
The description of the CVE-2022-0529 Red Hat bugzilla entry indicates there is
more than the two proposed patches fix, the two patches don't address any
OOB heap write.
I'm adding the Red Hat engineer who created the bugs to CC, Sandipan Roy.
@Sandipan, the unzip upstream authors are CCed to this mail to land fixes
for the unzip vulnerabilities you found. Would it be possible to open up
bz#2048572 and bz#2048569 with the full details of these security
vulnerabilities
so that upstream can review/merge the patches and clarify the status of
CVE-2022-0529?
Cheers,
Moritz
> Thanks.
> From: Enrico Zini
> Subject: Fix wide string conversion
> Bug-Debian: https://bugs.debian.org/1010355
> X-Debian-version: 6.0-27
>
> --- a/process.c
> +++ b/process.c
> @@ -2507,13 +2507,15 @@
>char buf[9];
>char *buffer = NULL;
>char *local_string = NULL;
> + size_t buffer_size;
>
>for (wsize = 0; wide_string[wsize]; wsize++) ;
>
>if (max_bytes < MAX_ESCAPE_BYTES)
> max_bytes = MAX_ESCAPE_BYTES;
>
> - if ((buffer = (char *)malloc(wsize * max_bytes + 1)) == NULL) {
> + buffer_size = wsize * max_bytes + 1;
> + if ((buffer = (char *)malloc(buffer_size)) == NULL) {
> return NULL;
>}
>
> @@ -2552,7 +2554,11 @@
>/* no MB for this wide */
> /* use escape for wide character */
> char *escape_string = wide_to_escape_string(wide_string[i]);
> -strcat(buffer, escape_string);
> +size_t buffer_len = strlen(buffer);
> +size_t escape_string_len = strlen(escape_string);
> +if (buffer_len + escape_string_len + 1 > buffer_size)
> + escape_string_len = buffer_size - buffer_len - 1;
> +strncat(buffer, escape_string, escape_string_len);
> free(escape_string);
> }
>}
> From: Enrico Zini
> Subject: Fix null pointer dereference on invalid UTF-8 input
> Bug-Debian: https://bugs.debian.org/1010355
> X-Debian-version: 6.0-27
>
> --- a/fileio.c
> +++ b/fileio.c
> @@ -2361,6 +2361,9 @@
>/* convert UTF-8 to local character set */
>fn = utf8_to_local_string(G.unipath_filename,
> G.unicode_escape_all);
> + if (fn == NULL)
> +return PK_ERR;
> +
>/* make sure filename is short enough */
>if (strlen(fn) >= FILNAMSIZ) {
> fn[FILNAMSIZ - 1] = '\0';
> --- a/process.c
> +++ b/process.c
> @@ -2611,6 +2611,8 @@
>int escape_all;
> {
>zwchar *wide = utf8_to_wide_string(utf8_string);
> + if (wide == NULL)
> +return NULL;
>char *loc = wide_to_local_string(wide, escape_all);
>free(wide);
>return loc;
Bug#1014115: uninstall does not properly remove enablement symlinks
On Thu, 30 Jun 2022 at 15:08, Michael Biebl wrote: > > Am 30.06.22 um 14:26 schrieb Michael Biebl: > > This might be a bug in i-s-h, but filing against systemd-homed for > > now. > > > > systemd-homed.service: > > [Install] > > WantedBy=multi-user.target > > Alias=dbus-org.freedesktop.home1.service > > Also=systemd-homed-activate.service systemd-userdbd.service > > > > systemd-homed-activate.service: > > [Install] > > WantedBy=systemd-homed.service > > Also=systemd-homed.service > > > > → we have a circular dependency here, maybe deb-systemd-helper get's > > confused by that > > > I just checked that we can mitigate this issue by removing this circular > Also= dependency. It is indeed deb-systemd-helper getting confused by > that and as a result not writing proper state files to > /var/lib/systemd/deb-systemd-helper. > So the damage is already done during installation in postinst. > Thus raising to RC to warn users from installing systemd-homed atm. > > I propose a patch like the attached one, i.e. dropping the Also= from > systemd-homed-active.service. WDYT? > > I've also cloned the issue for i-s-h, as we might want to fix that > properly. My perl is a bit rusty, so would appreciate help with that. > > @bluca: do you think the attached patch is suitable for upstream? > > I find this circular Also= dependency kinda odd, I have to admit. I don't think so, this seems clearly a bug in i-s-h. Ideally we should really drop all of that and just use presets as RPMs do... but it's a lot of work. Kind regards, Luca Boccassi
Processed: Re: Bug#1014115: uninstall does not properly remove enablement symlinks
Processing control commands: > clone -1 -2 Bug #1014115 [systemd-homed] uninstall does not properly remove enablement symlinks Bug 1014115 cloned as bug 1014119 > reassign -2 init-system-helpers Bug #1014119 [systemd-homed] uninstall does not properly remove enablement symlinks Bug reassigned from package 'systemd-homed' to 'init-system-helpers'. No longer marked as found in versions systemd/251.2-7. Ignoring request to alter fixed versions of bug #1014119 to the same values previously set > retitle -2 deb-systemd-helper fails with circular Also= Bug #1014119 [init-system-helpers] uninstall does not properly remove enablement symlinks Changed Bug title to 'deb-systemd-helper fails with circular Also=' from 'uninstall does not properly remove enablement symlinks'. > found -2 1.63 Bug #1014119 [init-system-helpers] deb-systemd-helper fails with circular Also= Marked as found in versions init-system-helpers/1.63. > severity -1 serious Bug #1014115 [systemd-homed] uninstall does not properly remove enablement symlinks Severity set to 'serious' from 'important' > tags -1 + patch Bug #1014115 [systemd-homed] uninstall does not properly remove enablement symlinks Added tag(s) patch. -- 1014115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014115 1014119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014119 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014114: installation of crypt.h in the multiarch location breaks the GCC and LLVM multilib builds
On Jun 30, Matthias Klose wrote: > installation of crypt.h in the multiarch location breaks the GCC and LLVM > multilib builds. > > For libsanitizer, crypt.h is needed to determine the size of a struct, the > library itself is not needed. Moving it to the MA location makes it > unavailable for the non-multilib builds. > > Unfortunately the changelog doesn't mention anything why it was moved. > > So either it should be moved back to /usr/include, or we need multilib > builds for libxcrypt. It was discussed in #1004102 (and is documented in the git commit), where Helmut was positive that this would not cause any issues. Helmut? (Why can't we retire multilib for good?) -- ciao, Marco signature.asc Description: PGP signature
Bug#1010355: Fwd: Bug#1010355: CVE-2022-0530: null pointer dereference on invalid UTF-8 input
Dear Steven and Mark:
I plan to apply the attached patches (from Enrico Zini) to fix
CVE-2022-0529 and CVE-2022-0530 in Debian unzip, but before doing so I
would like to have some feedback from upstream (i.e. you) or either from
the Security Team (also in CC).
Details about the bug here:
https://bugs.debian.org/1010355
The test cases triggering the bug are here:
https://github.com/ByteHackr/unzip_poc
Thanks.From: Enrico Zini
Subject: Fix wide string conversion
Bug-Debian: https://bugs.debian.org/1010355
X-Debian-version: 6.0-27
--- a/process.c
+++ b/process.c
@@ -2507,13 +2507,15 @@
char buf[9];
char *buffer = NULL;
char *local_string = NULL;
+ size_t buffer_size;
for (wsize = 0; wide_string[wsize]; wsize++) ;
if (max_bytes < MAX_ESCAPE_BYTES)
max_bytes = MAX_ESCAPE_BYTES;
- if ((buffer = (char *)malloc(wsize * max_bytes + 1)) == NULL) {
+ buffer_size = wsize * max_bytes + 1;
+ if ((buffer = (char *)malloc(buffer_size)) == NULL) {
return NULL;
}
@@ -2552,7 +2554,11 @@
/* no MB for this wide */
/* use escape for wide character */
char *escape_string = wide_to_escape_string(wide_string[i]);
-strcat(buffer, escape_string);
+size_t buffer_len = strlen(buffer);
+size_t escape_string_len = strlen(escape_string);
+if (buffer_len + escape_string_len + 1 > buffer_size)
+ escape_string_len = buffer_size - buffer_len - 1;
+strncat(buffer, escape_string, escape_string_len);
free(escape_string);
}
}
From: Enrico Zini
Subject: Fix null pointer dereference on invalid UTF-8 input
Bug-Debian: https://bugs.debian.org/1010355
X-Debian-version: 6.0-27
--- a/fileio.c
+++ b/fileio.c
@@ -2361,6 +2361,9 @@
/* convert UTF-8 to local character set */
fn = utf8_to_local_string(G.unipath_filename,
G.unicode_escape_all);
+ if (fn == NULL)
+return PK_ERR;
+
/* make sure filename is short enough */
if (strlen(fn) >= FILNAMSIZ) {
fn[FILNAMSIZ - 1] = '\0';
--- a/process.c
+++ b/process.c
@@ -2611,6 +2611,8 @@
int escape_all;
{
zwchar *wide = utf8_to_wide_string(utf8_string);
+ if (wide == NULL)
+return NULL;
char *loc = wide_to_local_string(wide, escape_all);
free(wide);
return loc;
Bug#1013706: marked as done (python-pytest-xprocess: FTBFS: pytest7 regression, pytest.PytestUnraisableExceptionWarning: Exception ignored)
Your message dated Thu, 30 Jun 2022 12:08:24 + with message-id and subject line Bug#1013706: fixed in python-pytest-xprocess 0.18.1-4 has caused the Debian Bug report #1013706, regarding python-pytest-xprocess: FTBFS: pytest7 regression, pytest.PytestUnraisableExceptionWarning: Exception ignored 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.) -- 1013706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pytest-xprocess Version: 0.18.1-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-pyt...@lists.debian.org Usertags: pytest7 Hi, During a selected rebuild of python packages in sid, your package failed to build with pytest version 7.1.2-1. The full build log is available from: http://qa-logs.debian.net/2022/06/09/pytest/python-pytest-xprocess_0.18.1-3_unstable_pytest-exp.log I had a closer look at the error log and identified the regression as: 'pytest.PytestUnraisableExceptionWarning: Exception ignored'. Hopefully, that's helpful! All bugs filed during this rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=pytest7;users=debian-pyt...@lists.debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=pytest7=debian-pyt...@lists.debian.org=1=1=1=1#results If you reassign this bug to another package, please mark 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 the one provided so that we can identify if something relevant changed in the meantime. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python-pytest-xprocess Source-Version: 0.18.1-4 Done: Thomas Goirand We believe that the bug you reported is fixed in the latest version of python-pytest-xprocess, 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 1013...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated python-pytest-xprocess 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: Thu, 30 Jun 2022 13:30:21 +0200 Source: python-pytest-xprocess Architecture: source Version: 0.18.1-4 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Closes: 1013706 Changes: python-pytest-xprocess (0.18.1-4) unstable; urgency=medium . * Blacklist test_interruption_cleanup() which is failing (Closes: #1013706). Checksums-Sha1: 343c7a5f37cb0ce0bc0ac254dfa0a3614e4e835b 2327 python-pytest-xprocess_0.18.1-4.dsc 2d5cb1bcc6569fea785f4426e0e087597cf3817b 2680 python-pytest-xprocess_0.18.1-4.debian.tar.xz 216f35782932906fdb2d697d6638b3f64b7a3934 8744 python-pytest-xprocess_0.18.1-4_amd64.buildinfo Checksums-Sha256: c9ac2a8ed59b4a048ea3b864816b071ebd4c18cd6848f67a2f83d3e42becb334 2327 python-pytest-xprocess_0.18.1-4.dsc dec2bb4f59b1a0ec1769456b7da822f6a455108df4f962d8a92fa6f283256b09 2680 python-pytest-xprocess_0.18.1-4.debian.tar.xz d1f20ba54a9aac2634db7989e6c779e6e9457845afea685f6bd08eb732fb8fd6 8744 python-pytest-xprocess_0.18.1-4_amd64.buildinfo Files: b01d79e5f9ae093b474cace56dc488bc 2327 python optional python-pytest-xprocess_0.18.1-4.dsc 18ddc6a2e29cf6fda7082db222795aec 2680 python optional python-pytest-xprocess_0.18.1-4.debian.tar.xz 952d1956986667baef30a0603b31aebc 8744 python optional python-pytest-xprocess_0.18.1-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmK9i8sACgkQ1BatFaxr Q/5pxA/5AS/aj3MENRUErHyvp/vJs1R2p7ZBnxTS47yKjlZADWTg9N9Ufel51Yw7 azVbYL7tTD/9ht+hupDTKFjFtldq5WjhSX4E+xQyo4UBXHjvJ/qadPUspkaZmUXL sY8Fa0dVrzQpCzH41ytapMWpupdMUJ/I25EJGCipLtRFgh/mn81t7HPff8npmDfc 23p7SZba8Pl1qIIRR6xHAUXgZPLU7jY8+Aix/XaDEe2cUlrQ/eAc7omojIXLqeCZ 9mo9xxJ3HfLWLXPZ8p8NYqyZHCBaQyHkRVa9KY9REpFj37dN+fG551Asm8xWO6jH 4RG7dgaw1ScT/I9uSgSBXaMIcDWE7FEPVi7RXS1T2JVFn3qZRcPL1bWDvJeADACC
Bug#1014114: installation of crypt.h in the multiarch location breaks the GCC and LLVM multilib builds
Package: libcrypt-dev Version: 4.4.28-1 Severity: serious installation of crypt.h in the multiarch location breaks the GCC and LLVM multilib builds. For libsanitizer, crypt.h is needed to determine the size of a struct, the library itself is not needed. Moving it to the MA location makes it unavailable for the non-multilib builds. Unfortunately the changelog doesn't mention anything why it was moved. So either it should be moved back to /usr/include, or we need multilib builds for libxcrypt.
Bug#1013647: marked as done (apertium-es-gl: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met)
Your message dated Thu, 30 Jun 2022 12:04:36 + with message-id and subject line Bug#1013647: fixed in apertium-es-gl 1.0.9-3 has caused the Debian Bug report #1013647, regarding apertium-es-gl: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met 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.) -- 1013647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013647 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-es-gl Version: 1.0.9-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220624 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for gawk... (cached) gawk > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.7.1... yes > checking for apertium-lex-tools >= 0.2.7... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > make[1]: *** [debian/rules:17: override_dh_auto_configure] Error 1 > make[1]: Leaving directory '/<>' The full build log is available from: http://qa-logs.debian.net/2022/06/24/apertium-es-gl_1.0.9-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220624=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: apertium-es-gl Source-Version: 1.0.9-3 Done: Kartik Mistry We believe that the bug you reported is fixed in the latest version of apertium-es-gl, 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 1013...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kartik Mistry (supplier of updated apertium-es-gl 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: Thu, 30 Jun 2022 13:28:36 +0530 Source: apertium-es-gl Architecture: source Version: 1.0.9-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Kartik Mistry Closes: 1013647 Changes: apertium-es-gl (1.0.9-3) unstable; urgency=medium . * debian/control: + Updated Build-Depends: apertium-lex-tools -> apertium-lex-tools-dev (Closes: #1013647) + Updated Standards-Version to 4.6.1 * Updated debian/copyright. * Updated debian/watch. Checksums-Sha1: 17bff54d9fe92bec748868c32ac8a20717394e29 2113 apertium-es-gl_1.0.9-3.dsc fa58c380613a59dd729b34dea6ded4ecd84bde66 3144 apertium-es-gl_1.0.9-3.debian.tar.xz Checksums-Sha256: d426f7ea98ea3001bb5134f227b2981106c8f5268ebd24f74486996adcb04747 2113 apertium-es-gl_1.0.9-3.dsc d754c6d39dc991fd7a80dc5abddd03dc66bbdeafb0e77fa6de6677392c52e5d4 3144 apertium-es-gl_1.0.9-3.debian.tar.xz Files: 0e3f55dd7527798bafc7e351bdb12848 2113 science optional apertium-es-gl_1.0.9-3.dsc df5cd45407db567e5c8caad84a847334 3144 science optional apertium-es-gl_1.0.9-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEa2MbXvVUr2sRlmKSAsHT8ng6pN4FAmK9iRYACgkQAsHT8ng6 pN430g//UbBSrcdvHtU2SlshCjO5B+zO3dVO8+PtUlZQBX/uHf44NUTyWafEkW22 tsrIJ/tg9QJgYsV/drVLXPv/EHIQoe4gxMpo6jSIjovUUfBL8Yw9c64m7LoB0Q+p
Bug#1012600:
The 2.1.5 packages have made their way into bookworm, and my system is now happily running kernel 5.18 with ZFS.
Bug#1014104: mothur: autopkgtest regression: did not complete cluster.
Hi Tomasz, could you please have a look? Kind regards Andreas. Am Thu, Jun 30, 2022 at 11:42:46AM +0200 schrieb Paul Gevers: > Source: mothur > Version: 1.48.0-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: regression > > Dear maintainer(s), > > With a recent upload of mothur the autopkgtest of mothur fails in testing > when that autopkgtest is run with the binary packages of mothur from > unstable. It passes when run with only packages from testing. In tabular > form: > >passfail > mothur from testing1.48.0-1 > all others from testingfrom testing > > I copied some of the output at the bottom of this report. > > Currently this regression is blocking the migration to testing [1]. Can you > please investigate the situation and fix it? > > More information about this bug and the reason for filing it can be found on > https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation > > Paul > > [1] https://qa.debian.org/excuses.php?package=mothur > > https://ci.debian.net/data/autopkgtest/testing/amd64/m/mothur/23197987/log.gz > > Linux version > > Using ReadLine > mothur v.1.48.0 > Last updated: 5/20/22 > by > Patrick D. Schloss > > Department of Microbiology & Immunology > > University of Michigan > http://www.mothur.org > > When using, please cite: > Schloss, P.D., et al., Introducing mothur: Open-source, > platform-independent, community-supported software for describing and > comparing microbial communities. Appl Environ Microbiol, 2009. > 75(23):7537-41. > > Distributed under the GNU General Public License > > Type 'help()' for information on the commands that are available > > For questions and analysis support, please visit our forum at > https://forum.mothur.org > > Type 'quit()' to exit program > > [NOTE]: Setting random seed to 19760620. > > Batch Mode > > > > mothur > unique.seqs(fasta=HA.fasta) > 599 259 > > Output File Names: HA.unique.fasta > HA.count_table > > > mothur > dist.seqs(fasta=HA.unique.fasta, countends=F, cutoff=0.01) > > Using 2 processors. > > Sequence TimeNum_Dists_Below_Cutoff > 0 0 0 > 200 0 3443 > 100 0 5025 > 258 0 15965 > 182 0 16617 > > It took 0 secs to find distances for 259 sequences. 32582 distances below > cutoff 0.01. > > > Output File Names: HA.unique.dist > > > mothur > cluster(method=furthest, column=HA.unique.dist, name=HA.names, > cutoff=0.01, precision=1000) > Unable to open HA.names. Trying mothur's executable directory HA.names. > Unable to open HA.names. > Unable to open HA.names > > Using 2 processors. > [ERROR]: did not complete cluster. > > mothur > summary.single(list=HA.unique.fn.list, calc=nseqs-sobs-chao, > label=unique-0.001-0.003-0.005-0.008) > Unable to open HA.unique.fn.list. Trying mothur's executable directory > HA.unique.fn.list. > Unable to open HA.unique.fn.list. > Unable to open HA.unique.fn.list > No valid current files. You must provide a list, sabund, rabund or shared > file before you can use the collect.single command. > [ERROR]: did not complete summary.single. > > mothur > heatmap.bin(scale=linear, label=unique-0.001-0.003) > No valid current files. You must provide a list, sabund, rabund, relabund or > shared file. > [ERROR]: did not complete heatmap.bin. > > mothur > rarefaction.single(calc=sobs-chao, label=unique-0.001-0.003, > freq=10) > No valid current files. You must provide a list, sabund, rabund or shared > file before you can use the collect.single command. > > Using 2 processors. > [ERROR]: did not complete rarefaction.single. > > mothur > quit() > > > It took 0 seconds to run 7 commands from test.batch batch file. > > Logfile : mothur.1656579650.logfile > > > > > > > Detected 4 [ERROR] messages, please review. > > > > autopkgtest [09:00:51]: test run-unit-test > > ___ > Debian-med-packaging mailing list > debian-med-packag...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging -- http://fam-tille.de
Bug#1013706: marked as pending in python-pytest-xprocess
Control: tag -1 pending Hello, Bug #1013706 in python-pytest-xprocess 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/python-pytest-xprocess/-/commit/a234d82653bd9d733351e42ea75938701ba12bc9 Blacklist test_interruption_cleanup() which is failing (Closes: #1013706). (this message was generated automatically) -- Greetings https://bugs.debian.org/1013706
Processed: Bug#1013706 marked as pending in python-pytest-xprocess
Processing control commands: > tag -1 pending Bug #1013706 [src:python-pytest-xprocess] python-pytest-xprocess: FTBFS: pytest7 regression, pytest.PytestUnraisableExceptionWarning: Exception ignored Added tag(s) pending. -- 1013706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: early transition to gcc-12 breaks src:pcl on armhf/el
Processing control commands: > severity -1 serious Bug #1013316 [dh-fortran-mod] early transition to gcc-12 breaks src:pcl on armhf/el Severity set to 'serious' from 'normal' > tags -1 + ftbfs Bug #1013316 [dh-fortran-mod] early transition to gcc-12 breaks src:pcl on armhf/el Added tag(s) ftbfs. > affects -1 + src:pcl Bug #1013316 [dh-fortran-mod] early transition to gcc-12 breaks src:pcl on armhf/el Added indication that 1013316 affects src:pcl -- 1013316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: gcc-12 breaks glibc autopkgtest on arm64: XFAIL: posix/annexc
Processing control commands: > found -1 gcc-12/12.1.0-5 Bug #1014109 [src:gcc-12, src:glibc] gcc-12 breaks glibc autopkgtest on arm64: XFAIL: posix/annexc Marked as found in versions gcc-12/12.1.0-5. > found -1 glibc/2.33-7 Bug #1014109 [src:gcc-12, src:glibc] gcc-12 breaks glibc autopkgtest on arm64: XFAIL: posix/annexc Marked as found in versions glibc/2.33-7. -- 1014109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014109: gcc-12 breaks glibc autopkgtest on arm64: XFAIL: posix/annexc
Source: gcc-12, glibc
Control: found -1 gcc-12/12.1.0-5
Control: found -1 glibc/2.33-7
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of gcc-12 the autopkgtest of glibc fails in testing
on arm64 when that autopkgtest is run with the binary packages of gcc-12
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
gcc-12 from testing12.1.0-5
glibc from testing2.33-7
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of gcc-12 to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?
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=gcc-12
https://ci.debian.net/data/autopkgtest/testing/arm64/g/glibc/23190432/log.gz
'GCONV_PATH=/tmp/autopkgtest-lxc.s8o48hbj/downtmp/build.Y8r/src/build-tree/arm64-libc/iconvdata
LOCPATH=/tmp/autopkgtest-lxc.s8o48hbj/downtmp/build.Y8r/src/build-tree/arm64-libc/localedata
LC_ALL=C' '
/tmp/autopkgtest-lxc.s8o48hbj/downtmp/build.Y8r/src/build-tree/arm64-libc/elf/ld-linux-aarch64.so.1
--library-path
/tmp/autopkgtest-lxc.s8o48hbj/downtmp/build.Y8r/src/build-tree/arm64-libc:/tmp/autopkgtest-lxc.s8o48hbj/downtmp/build.Y8r/src/build-tree/arm64-libc/math:/tmp/autopkgtest-lxc.s8o48hbj/downtmp/build.Y8r/src/build-tree/arm64-libc/elf:/tmp/autopkgtest-lxc.s8o48hbj/downtmp/build.Y8r/src/build-tree/arm64-libc/dlfcn:/tmp/autopkgtest-lxc.s8o48hbj/downtmp/build.Y8r/src/build-tree/arm64-libc/nss:/tmp/autopkgtest-lxc.s8o48hbj/downtmp/build.Y8r/src/build-tree/arm64-libc/nis:/tmp/autopkgtest-lxc.s8o48hbj/downtmp/build.Y8r/src/build-tree/arm64-libc/rt:/tmp/autopkgtest-lxc.s8o48hbj/downtmp/build.Y8r/src/build-tree/arm64-libc/resolv:/tmp/autopkgtest-lxc.s8o48hbj/downtmp/build.Y8r/src/build-tree/arm64-libc/mathvec:/tmp/autopkgtest-lxc.s8o48hbj/downtmp/build.Y8r/src/build-tree/arm64-libc/support:/tmp/autopkgtest-lxc.s8o48hbj/downtmp/build.Y8r/src/build-tree/arm64-libc/nptl';
\
../scripts/evaluate-test.sh posix/wordexp-tst $? false false >
/tmp/autopkgtest-lxc.s8o48hbj/downtmp/build.Y8r/src/build-tree/arm64-libc/posix/wordexp-tst.test-result
$* test failed
/tmp/autopkgtest-lxc.s8o48hbj/downtmp/build.Y8r/src/build-tree/arm64-libc/posix/annexc
'aarch64-linux-gnu-gcc-10' \
'-I../csu -I../iconv -I../locale -I../localedata -I../iconvdata
-I../assert -I../ctype -I../intl -I../catgets -I../math -I../setjmp
-I../signal -I../stdlib -I../stdio-common -I../libio -I../dlfcn
-I../nptl -I../malloc -I../string -I../wcsmbs -I../timezone -I../time
-I../dirent -I../grp -I../pwd -I../posix -I../io -I../termios
-I../resource -I../misc -I../socket -I../sysvipc -I../gmon -I../gnulib
-I../wctype -I../manual -I../shadow -I../gshadow -I../po -I../argp
-I../rt -I../conform -I../debug -I../mathvec -I../support -I../nptl_db
-I../inet -I../resolv -I../nss -I../hesiod -I../sunrpc -I../nis
-I../nscd -I../login -I../elf -I../include
-I/tmp/autopkgtest-lxc.s8o48hbj/downtmp/build.Y8r/src/build-tree/arm64-libc
-I../sysdeps/unix/sysv/linux/aarch64 -I../sysdeps/aarch64/nptl
-I../sysdeps/unix/sysv/linux/generic
-I../sysdeps/unix/sysv/linux/wordsize-64
-I../sysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux
-I../sysdeps/nptl -I../sysdeps/pthread -I../sysdeps/gnu
-I../sysdeps/unix/inet -I../sysdeps/unix/sysv -I../sysdeps/unix
-I../sysdeps/posix -I../sysdeps/aarch64/fpu
-I../sysdeps/aarch64/multiarch -I../sysdeps/aarch64
-I../sysdeps/wordsize-64 -I../sysdeps/ieee754/ldbl-128
-I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32
-I../sysdeps/ieee754 -I../sysdeps/generic -nostdinc -isystem
/usr/lib/gcc/aarch64-linux-gnu/10/include -isystem
/tmp/autopkgtest-lxc.s8o48hbj/downtmp/build.Y8r/src/debian/include -I..'
>
/tmp/autopkgtest-lxc.s8o48hbj/downtmp/build.Y8r/src/build-tree/arm64-libc/posix/annexc.out;
\
../scripts/evaluate-test.sh posix/annexc $? true false >
/tmp/autopkgtest-lxc.s8o48hbj/downtmp/build.Y8r/src/build-tree/arm64-libc/posix/annexc.test-result
${*} test failed
$@ test failed
$* quoted test failed
$@ quoted test failed
$# test failed
$2 ${3} $4 test failed
${11} test failed
"a $@ b" test failed
-
/tmp/autopkgtest-lxc.s8o48hbj/downtmp/build.Y8r/src/build-tree/arm64-libc/posix/wordexp-test-result10
differ: char 1, line 1
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1014108: python-ldap: autopkgtest regression: Command 'slapadd' not found
Source: python-ldap
Version: 3.4.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of python-ldap the autopkgtest of python-ldap fails
in testing when that autopkgtest is run with the binary packages of
python-ldap from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
python-ldapfrom testing3.4.0-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it? It seems like a missing
new (test) dependency.
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=python-ldap
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-ldap/23177881/log.gz
==
ERROR: setUpClass (t_bind.TestBinds)
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
603, in setUpClass
cls.server = cls.server_class()
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
233, in __init__
self._find_commands()
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
262, in _find_commands
self.PATH_SLAPADD = self._find_command('slapadd')
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
277, in _find_command
raise ValueError(
ValueError: Command 'slapadd' not found. Set the BIN environment
variable to override slapdtest's search path.
==
ERROR: setUpClass (t_cext.TestLdapCExtension)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.v0m7b8wh/downtmp/autopkgtest_tmp/Tests/t_cext.py",
line 30, in setUpClass
super().setUpClass()
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
603, in setUpClass
cls.server = cls.server_class()
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
233, in __init__
self._find_commands()
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
262, in _find_commands
self.PATH_SLAPADD = self._find_command('slapadd')
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
277, in _find_command
raise ValueError(
ValueError: Command 'slapadd' not found. Set the BIN environment
variable to override slapdtest's search path.
==
ERROR: setUpClass (t_edit.EditionTests)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.v0m7b8wh/downtmp/autopkgtest_tmp/Tests/t_edit.py",
line 16, in setUpClass
super().setUpClass()
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
603, in setUpClass
cls.server = cls.server_class()
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
233, in __init__
self._find_commands()
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
262, in _find_commands
self.PATH_SLAPADD = self._find_command('slapadd')
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
277, in _find_command
raise ValueError(
ValueError: Command 'slapadd' not found. Set the BIN environment
variable to override slapdtest's search path.
==
ERROR: setUpClass (t_ldap_options.TestLDAPObjectOptions)
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
603, in setUpClass
cls.server = cls.server_class()
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
233, in __init__
self._find_commands()
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
262, in _find_commands
self.PATH_SLAPADD = self._find_command('slapadd')
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
277, in _find_command
raise ValueError(
ValueError: Command 'slapadd' not found. Set the BIN environment
variable to override slapdtest's search path.
==
ERROR: setUpClass (t_ldap_sasl.TestSasl)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.v0m7b8wh/downtmp/autopkgtest_tmp/Tests/t_ldap_sasl.py",
line 49,
Bug#1014100: We should do an update of all qiime2 modules as soon as possible (Was: Bug#1014100: qiime: autopkgtest needs update for new version of python-decorator)
Hi,
I'd like to point out to this serious bug. Steffen, would you mind
koordinating (not doing alone) an upgrade of the qiime infrastructure to
make sure everything will go smoothly?
Kind regards
Andreas.
Am Thu, Jun 30, 2022 at 11:30:21AM +0200 schrieb Paul Gevers:
> Source: qiime
> Version: 2021.8.0-2
> Severity: serious
> X-Debbugs-CC: python-decora...@packages.debian.org
> Tags: sid bookworm
> User: debian...@lists.debian.org
> Usertags: needs-update
> Control: affects -1 src:python-decorator
>
> Dear maintainer(s),
>
> With a recent upload of python-decorator the autopkgtest of qiime fails in
> testing when that autopkgtest is run with the binary packages of
> python-decorator from unstable. It passes when run with only packages from
> testing. In tabular form:
>
>passfail
> python-decorator from testing5.1.1-2
> qiime from testing2021.8.0-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 of python-decorator to
> testing [1]. Of course, python-decorator shouldn't just break your
> autopkgtest (or even worse, your package), but it seems to me that the
> change in python-decorator was intended and your package needs to update to
> the new situation. To me it looks like the references need updating for the
> new version but I might be wrong.
>
> If this is a real problem in your package (and not only in your
> autopkgtest), the right binary package(s) from python-decorator should
> really add a versioned Breaks on the unfixed version of (one of your)
> package(s). Note: the Breaks is nice even if the issue is only in the
> autopkgtest as it helps the migration software to figure out the right
> versions to combine in the tests.
>
> 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=python-decorator
>
> https://ci.debian.net/data/autopkgtest/testing/amd64/q/qiime/23173367/log.gz
>
> FF.FFF..
> ==
> FAIL: test_callable_and_async_signature_with_artifacts_and_parameters
> (qiime2.sdk.tests.test_method.TestMethod)
> --
> Traceback (most recent call last):
> File
> "/tmp/autopkgtest-lxc.t_q3d0jx/downtmp/autopkgtest_tmp/qiime2/sdk/tests/test_method.py",
> line 223, in test_callable_and_async_signature_with_artifacts_and_parameters
> self.assertEqual(parameters, exp_parameters)
> AssertionError: Lists differ: [('in[20 chars]ts1: list">), ('ints2',
> )] != [('in[20 chars]ts1: IntSequence1 |
> IntSequence2">), ('ints2',[147 chars]t">)]
>
> First differing element 0:
> ('ints1', )
> ('ints1', )
>
> Diff is 735 characters long. Set self.maxDiff to None to see it.
>
> ==
> FAIL: test_callable_and_async_signature_with_no_parameters
> (qiime2.sdk.tests.test_method.TestMethod)
> --
> Traceback (most recent call last):
> File
> "/tmp/autopkgtest-lxc.t_q3d0jx/downtmp/autopkgtest_tmp/qiime2/sdk/tests/test_method.py",
> line 242, in test_callable_and_async_signature_with_no_parameters
> self.assertEqual(parameters, exp_parameters)
> AssertionError: Lists differ: [('ma[26 chars]ng1: dict">), ('mapping2',
> )] != [('ma[26 chars]ng1: Mapping">),
> ('mapping2', )]
>
> First differing element 0:
> ('mapping1', )
> ('mapping1', )
>
> - [('mapping1', ),
> ? ^ ^^
>
> + [('mapping1', ),
> ? ^^
>
> - ('mapping2', )]
> ? ^ ^^
>
> + ('mapping2', )]
> ? ^^
>
>
>
Bug#1013585: marked as done (octave-jsonlab: FTBFS: dh_missing: error: missing files, aborting)
Your message dated Thu, 30 Jun 2022 09:49:52 + with message-id and subject line Bug#1013585: fixed in octave-jsonlab 2.0-2 has caused the Debian Bug report #1013585, regarding octave-jsonlab: FTBFS: dh_missing: error: missing files, aborting 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.) -- 1013585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: octave-jsonlab Version: 2.0-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220624 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > mkdir inst > cp *.m inst > rm -rf inst/Contents.m > cp ChangeLog.txt NEWS > cp LICENSE_GPLv3.txt COPYING > make[1]: Leaving directory '/<>' >dh_auto_build -O--buildsystem=octave >dh_auto_test -O--buildsystem=octave >create-stamp debian/debhelper-build-stamp >dh_testroot -O--buildsystem=octave >dh_prep -O--buildsystem=octave >dh_installdirs -O--buildsystem=octave >dh_auto_install -O--buildsystem=octave > octave --no-gui --no-history --silent --no-init-file --no-window-system > /usr/share/dh-octave/install-pkg.m > /<>/debian/tmp/usr/share/octave/packages > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/octave/packages > warning: creating installation directory > /<>/debian/tmp/usr/share/octave/packages > warning: called from > install at line 36 column 5 > pkg at line 603 column 9 > /usr/share/dh-octave/install-pkg.m at line 38 column 1 > > For information about changes from previous versions of the jsonlab package, > run 'news jsonlab'. >dh_octave_check -O--buildsystem=octave > Checking package... > Checking m files ... > Checking C++ files ... > Summary: 0 tests, 0 passed, 0 known failures, 0 skipped >dh_install -O--buildsystem=octave >dh_installdocs -O--buildsystem=octave >dh_installchangelogs -O--buildsystem=octave >dh_octave_changelogs -O--buildsystem=octave >dh_installexamples -O--buildsystem=octave >dh_octave_examples -O--buildsystem=octave > dh_octave_examples: warning: skipping link from > usr/share/doc/octave-jsonlab/examples to self > dh_octave_examples: warning: skipping link from > usr/share/doc/matlab-jsonlab/examples to self >dh_installsystemduser -O--buildsystem=octave >dh_perl -O--buildsystem=octave >dh_link -O--buildsystem=octave >dh_strip_nondeterminism -O--buildsystem=octave >dh_compress -O--buildsystem=octave >dh_fixperms -O--buildsystem=octave >dh_missing -O--buildsystem=octave > dh_missing: warning: usr/share/octave/packages/jsonlab-2.0/base64decode.m > exists in debian/tmp but is not installed to anywhere (related file: > "inst/base64decode.m") > dh_missing: warning: usr/share/octave/packages/jsonlab-2.0/base64encode.m > exists in debian/tmp but is not installed to anywhere (related file: > "inst/base64encode.m") > dh_missing: warning: usr/share/octave/packages/jsonlab-2.0/decodevarname.m > exists in debian/tmp but is not installed to anywhere (related file: > "inst/decodevarname.m") > dh_missing: warning: usr/share/octave/packages/jsonlab-2.0/doc-cache exists > in debian/tmp but is not installed to anywhere > dh_missing: warning: usr/share/octave/packages/jsonlab-2.0/encodevarname.m > exists in debian/tmp but is not installed to anywhere (related file: > "inst/encodevarname.m") > dh_missing: warning: > usr/share/octave/packages/jsonlab-2.0/fast_match_bracket.m exists in > debian/tmp but is not installed to anywhere (related file: > "inst/fast_match_bracket.m") > dh_missing: warning: usr/share/octave/packages/jsonlab-2.0/gzipdecode.m > exists in debian/tmp but is not installed to anywhere (related file: > "inst/gzipdecode.m") > dh_missing: warning: usr/share/octave/packages/jsonlab-2.0/gzipencode.m > exists in debian/tmp but is not installed to anywhere (related file: > "inst/gzipencode.m") > dh_missing: warning: usr/share/octave/packages/jsonlab-2.0/isoctavemesh.m > exists in debian/tmp but is not installed to anywhere (related file: > "inst/isoctavemesh.m") > dh_missing: warning: usr/share/octave/packages/jsonlab-2.0/jdatadecode.m > exists in debian/tmp but is not installed to anywhere (related file: > "inst/jdatadecode.m") > dh_missing: warning: usr/share/octave/packages/jsonlab-2.0/jdataencode.m > exists in debian/tmp but is not installed to anywhere (related file: > "inst/jdataencode.m") > dh_missing: warning:
Bug#1014104: mothur: autopkgtest regression: did not complete cluster.
Source: mothur Version: 1.48.0-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of mothur the autopkgtest of mothur fails in testing when that autopkgtest is run with the binary packages of mothur from unstable. It passes when run with only packages from testing. In tabular form: passfail mothur from testing1.48.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=mothur https://ci.debian.net/data/autopkgtest/testing/amd64/m/mothur/23197987/log.gz Linux version Using ReadLine mothur v.1.48.0 Last updated: 5/20/22 by Patrick D. Schloss Department of Microbiology & Immunology University of Michigan http://www.mothur.org When using, please cite: Schloss, P.D., et al., Introducing mothur: Open-source, platform-independent, community-supported software for describing and comparing microbial communities. Appl Environ Microbiol, 2009. 75(23):7537-41. Distributed under the GNU General Public License Type 'help()' for information on the commands that are available For questions and analysis support, please visit our forum at https://forum.mothur.org Type 'quit()' to exit program [NOTE]: Setting random seed to 19760620. Batch Mode mothur > unique.seqs(fasta=HA.fasta) 599 259 Output File Names: HA.unique.fasta HA.count_table mothur > dist.seqs(fasta=HA.unique.fasta, countends=F, cutoff=0.01) Using 2 processors. SequenceTimeNum_Dists_Below_Cutoff 0 0 0 200 0 3443 100 0 5025 258 0 15965 182 0 16617 It took 0 secs to find distances for 259 sequences. 32582 distances below cutoff 0.01. Output File Names: HA.unique.dist mothur > cluster(method=furthest, column=HA.unique.dist, name=HA.names, cutoff=0.01, precision=1000) Unable to open HA.names. Trying mothur's executable directory HA.names. Unable to open HA.names. Unable to open HA.names Using 2 processors. [ERROR]: did not complete cluster. mothur > summary.single(list=HA.unique.fn.list, calc=nseqs-sobs-chao, label=unique-0.001-0.003-0.005-0.008) Unable to open HA.unique.fn.list. Trying mothur's executable directory HA.unique.fn.list. Unable to open HA.unique.fn.list. Unable to open HA.unique.fn.list No valid current files. You must provide a list, sabund, rabund or shared file before you can use the collect.single command. [ERROR]: did not complete summary.single. mothur > heatmap.bin(scale=linear, label=unique-0.001-0.003) No valid current files. You must provide a list, sabund, rabund, relabund or shared file. [ERROR]: did not complete heatmap.bin. mothur > rarefaction.single(calc=sobs-chao, label=unique-0.001-0.003, freq=10) No valid current files. You must provide a list, sabund, rabund or shared file before you can use the collect.single command. Using 2 processors. [ERROR]: did not complete rarefaction.single. mothur > quit() It took 0 seconds to run 7 commands from test.batch batch file. Logfile : mothur.1656579650.logfile Detected 4 [ERROR] messages, please review. autopkgtest [09:00:51]: test run-unit-test OpenPGP_signature Description: OpenPGP digital signature
Bug#1004821: libam7xxx: FTBFS with ffmpeg 5.0
On Sat, 25 Jun 2022 13:04:46 +0300 Nicholas Guriev wrote: > This patch should help. Although, call to deprecated av_init_packet() > remains. > It is to be replaced with av_packet_alloc() / av_packet_free() logic. Thank you, Nicholas, this is a good first step. I'll try to find time this week-end to push a new package compatible with FFmpeg 5.0. Take care, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#1014103: django-auth-ldap: autopkgtest regression: Command 'slapadd' not found
Source: django-auth-ldap
Version: 4.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of django-auth-ldap the autopkgtest of
django-auth-ldap fails in testing when that autopkgtest is run with the
binary packages of django-auth-ldap from unstable. It passes when run
with only packages from testing. In tabular form:
passfail
django-auth-ldap from testing4.0.0-1
all others from testingfrom testing
I copied some of the output at the bottom of this report. Seems like
you're missing a test dependency?
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=django-auth-ldap
https://ci.debian.net/data/autopkgtest/testing/amd64/d/django-auth-ldap/23174684/log.gz
Creating test database for alias 'default'...
Found 88 test(s).
System check identified no issues (0 silenced).
E
==
ERROR: setUpClass (tests.tests.LDAPTest)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.5awdudxv/downtmp/autopkgtest_tmp/tests/tests.py",
line 132, in setUpClass
cls.server = slapdtest.SlapdObject()
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
233, in __init__
self._find_commands()
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
262, in _find_commands
self.PATH_SLAPADD = self._find_command('slapadd')
File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line
277, in _find_command
raise ValueError(
ValueError: Command 'slapadd' not found. Set the BIN environment
variable to override slapdtest's search path.
--
Ran 0 tests in 0.001s
FAILED (errors=1)
Destroying test database for alias 'default'...
autopkgtest [03:12:39]: test upstream
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1014102: redis breaks python-redis autopkgtest: 14 tests fail
Source: redis, python-redis
Control: found -1 redis/5:7.0.2-2
Control: found -1 python-redis/3.5.3-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of redis the autopkgtest of python-redis fails in
testing when that autopkgtest is run with the binary packages of redis
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
redis from testing5:7.0.2-2
python-redis from testing3.5.3-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 of redis to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?
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=redis
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-redis/23173373/log.gz
=== FAILURES
===
__ TestRedisCommands.test_acl_getuser_setuser
__
self =
r = Redis>>
request = >
@skip_if_server_version_lt(REDIS_6_VERSION)
def test_acl_getuser_setuser(self, r, request):
username = 'redis-py-user'
def teardown():
r.acl_deluser(username)
request.addfinalizer(teardown)
# test enabled=False
assert r.acl_setuser(username, enabled=False, reset=True)
assert r.acl_getuser(username) == {
'categories': ['-@all'],
'commands': [],
'enabled': False,
'flags': ['off'],
'keys': [],
'passwords': [],
}
E AssertionError: assert {'categories'...': False, ...} ==
{'categories'... ['off'], ...}
E Omitting 4 identical items, use -vv to show
E Differing items:
E {'keys': b''} != {'keys': []}
E {'flags': ['off', 'sanitize-payload']} != {'flags': ['off']}
E Left contains 2 more items:
E {'channels': b'', 'selectors': []}
E Use -v to get the full diff
tests/test_commands.py:108: AssertionError
___ TestRedisCommands.test_acl_list
self =
r = Redis>>
request = >
@skip_if_server_version_lt(REDIS_6_VERSION)
def test_acl_list(self, r, request):
username = 'redis-py-user'
def teardown():
r.acl_deluser(username)
request.addfinalizer(teardown)
assert r.acl_setuser(username, enabled=False, reset=True)
users = r.acl_list()
assert 'user %s off -@all' % username in users
E AssertionError: assert ('user %s off -@all' % 'redis-py-user')
in ['user default on nopass ~* &* +@all', 'user redis-py-user off
sanitize-payload resetchannels -@all']
tests/test_commands.py:196: AssertionError
__ TestRedisCommands.test_config_set
___
self =
r = Redis>>
def test_config_set(self, r):
data = r.config_get()
rdbname = data['dbfilename']
try:
assert r.config_set('dbfilename', 'redis_py_test.rdb')
tests/test_commands.py:379: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = Redis>>
name = 'dbfilename', value = 'redis_py_test.rdb'
def config_set(self, name, value):
"Set config item ``name`` with ``value``"
return self.execute_command('CONFIG SET', name, value)
redis/client.py:1243: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = Redis>>
args = ('CONFIG SET', 'dbfilename', 'redis_py_test.rdb'), options = {}
pool = ConnectionPool>
command_name = 'CONFIG SET', conn =
Connection
def execute_command(self, *args, **options):
"Execute a command and return a parsed response"
pool = self.connection_pool
command_name = args[0]
conn = self.connection or pool.get_connection(command_name,
**options)
try:
conn.send_command(*args)
return self.parse_response(conn, command_name, **options)
redis/client.py:901: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _
self = Redis>>
connection = Connection
command_name = 'CONFIG SET', options = {}
def parse_response(self, connection, command_name, **options):
"Parses a response from the Redis server"
try:
response = connection.read_response()
redis/client.py:915: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _
self = Connection
def read_response(self):
"Read the response from a
Processed: redis breaks python-redis autopkgtest: 14 tests fail
Processing control commands: > found -1 redis/5:7.0.2-2 Bug #1014102 [src:redis, src:python-redis] redis breaks python-redis autopkgtest: 14 tests fail Marked as found in versions redis/5:7.0.2-2. > found -1 python-redis/3.5.3-2 Bug #1014102 [src:redis, src:python-redis] redis breaks python-redis autopkgtest: 14 tests fail Marked as found in versions python-redis/3.5.3-2. -- 1014102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python-fakeredis: autopkgtest needs update for new version of redis: error message changed
Processing control commands: > affects -1 src:redis Bug #1014101 [src:python-fakeredis] python-fakeredis: autopkgtest needs update for new version of redis: error message changed Added indication that 1014101 affects src:redis -- 1014101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014101: python-fakeredis: autopkgtest needs update for new version of redis: error message changed
Source: python-fakeredis
Version: 1.6.1-1
Severity: serious
X-Debbugs-CC: re...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:redis
Dear maintainer(s),
With a recent upload of redis the autopkgtest of python-fakeredis fails
in testing when that autopkgtest is run with the binary packages of
redis from unstable. It passes when run with only packages from testing.
In tabular form:
passfail
redis from testing5:7.0.2-2
python-fakeredis from testing1.6.1-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of redis to testing
[1]. Of course, redis shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in redis was
intended and your package needs to update to the new situation. It seems
the failure is just an error message that got improved.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from redis should really add a
versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.
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=redis
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-fakeredis/23195767/log.gz
=== FAILURES
===
test_failed_script_error[real]
r = >
async def test_failed_script_error(r):
await r.set('foo', 'bar')
with pytest.raises(aioredis.ReplyError, match='^ERR Error
running script'):
await r.eval('return redis.call("ZCOUNT", KEYS[1])', ['foo'])
E aioredis.errors.ReplyError: ERR Wrong number of args calling
Redis command from script script:
2558dbbbe1424be2d1e9af6eece6309035f8696f, on @user_script:1.
test/test_aioredis1.py:158: ReplyError
During handling of the above exception, another exception occurred:
r = >
async def test_failed_script_error(r):
await r.set('foo', 'bar')
with pytest.raises(aioredis.ReplyError, match='^ERR Error running
script'):
E AssertionError: Regex pattern '^ERR Error running script' does
not match 'ERR Wrong number of args calling Redis command from script
script: 2558dbbbe1424be2d1e9af6eece6309035f8696f, on @user_script:1.'.
test/test_aioredis1.py:157: AssertionError
OpenPGP_signature
Description: OpenPGP digital signature
Processed: qiime: autopkgtest needs update for new version of python-decorator
Processing control commands: > affects -1 src:python-decorator Bug #1014100 [src:qiime] qiime: autopkgtest needs update for new version of python-decorator Added indication that 1014100 affects src:python-decorator -- 1014100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014100 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014100: qiime: autopkgtest needs update for new version of python-decorator
Source: qiime
Version: 2021.8.0-2
Severity: serious
X-Debbugs-CC: python-decora...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python-decorator
Dear maintainer(s),
With a recent upload of python-decorator the autopkgtest of qiime fails
in testing when that autopkgtest is run with the binary packages of
python-decorator from unstable. It passes when run with only packages
from testing. In tabular form:
passfail
python-decorator from testing5.1.1-2
qiime from testing2021.8.0-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 of python-decorator
to testing [1]. Of course, python-decorator shouldn't just break your
autopkgtest (or even worse, your package), but it seems to me that the
change in python-decorator was intended and your package needs to update
to the new situation. To me it looks like the references need updating
for the new version but I might be wrong.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from python-decorator should
really add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.
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=python-decorator
https://ci.debian.net/data/autopkgtest/testing/amd64/q/qiime/23173367/log.gz
FF.FFF..
==
FAIL: test_callable_and_async_signature_with_artifacts_and_parameters
(qiime2.sdk.tests.test_method.TestMethod)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.t_q3d0jx/downtmp/autopkgtest_tmp/qiime2/sdk/tests/test_method.py",
line 223, in test_callable_and_async_signature_with_artifacts_and_parameters
self.assertEqual(parameters, exp_parameters)
AssertionError: Lists differ: [('in[20 chars]ts1: list">), ('ints2',
)] != [('in[20 chars]ts1:
IntSequence1 | IntSequence2">), ('ints2',[147 chars]t">)]
First differing element 0:
('ints1', )
('ints1', )
Diff is 735 characters long. Set self.maxDiff to None to see it.
==
FAIL: test_callable_and_async_signature_with_no_parameters
(qiime2.sdk.tests.test_method.TestMethod)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.t_q3d0jx/downtmp/autopkgtest_tmp/qiime2/sdk/tests/test_method.py",
line 242, in test_callable_and_async_signature_with_no_parameters
self.assertEqual(parameters, exp_parameters)
AssertionError: Lists differ: [('ma[26 chars]ng1: dict">), ('mapping2',
)] != [('ma[26 chars]ng1: Mapping">),
('mapping2', )]
First differing element 0:
('mapping1', )
('mapping1', )
- [('mapping1', ),
? ^ ^^
+ [('mapping1', ),
? ^^
- ('mapping2', )]
? ^ ^^
+ ('mapping2', )]
? ^^
==
FAIL: test_callable_and_async_signature
(qiime2.sdk.tests.test_pipeline.TestPipeline)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lxc.t_q3d0jx/downtmp/autopkgtest_tmp/qiime2/sdk/tests/test_pipeline.py",
line 78, in test_callable_and_async_signature
self.assertEqual(parameters, exp_parameters)
AssertionError: Lists differ:
Bug#1013515: marked as done (ironic-ui: FTBFS: Errors while processing: openstack-dashboard sbuild-build-depends-main-dummy)
Your message dated Thu, 30 Jun 2022 09:19:07 + with message-id and subject line Bug#1013515: fixed in ironic-ui 5.1.0-3 has caused the Debian Bug report #1013515, regarding ironic-ui: FTBFS: Errors while processing: openstack-dashboard sbuild-build-depends-main-dummy 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.) -- 1013515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ironic-ui Version: 5.1.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220624 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. I'm filing this once, but the same issue affects many other packages build-depending on openstack-dashboard (obviously). Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 10), dh-python, > openstack-pkg-tools, python3-all, python3-pbr, python3-setuptools, > python3-sphinx, build-essential, fakeroot, openstack-dashboard (>= > 3:20.0.0+git2020.09.21.27036cc0eb), python3-coverage, python3-django, > python3-django-nose, python3-hacking, python3-ironicclient, > python3-openstackdocstheme, python3-oslotest, python3-six, python3-subunit, > python3-testscenarios, python3-testtools, subunit > Filtered Build-Depends: debhelper-compat (= 10), dh-python, > openstack-pkg-tools, python3-all, python3-pbr, python3-setuptools, > python3-sphinx, build-essential, fakeroot, openstack-dashboard (>= > 3:20.0.0+git2020.09.21.27036cc0eb), python3-coverage, python3-django, > python3-django-nose, python3-hacking, python3-ironicclient, > python3-openstackdocstheme, python3-oslotest, python3-six, python3-subunit, > python3-testscenarios, python3-testtools, subunit > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [534 B] > Get:5 copy:/<>/apt_archive ./ Packages [609 B] > Fetched 2106 B in 0s (141 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > The following additional packages will be installed: > autoconf automake autopoint autotools-dev bsdextrautils ca-certificates dbus > dbus-bin dbus-daemon dbus-session-bus-common dbus-system-bus-common > debhelper dh-autoreconf dh-python dh-strip-nondeterminism docutils-common > dwz file flake8 fonts-font-awesome fonts-glyphicons-halflings > fonts-materialdesignicons-webfont fonts-roboto-fontface gettext gettext-base > groff-base ieee-data intltool-debian jq libapparmor1 libarchive-zip-perl > libbsd0 libdbus-1-3 libdebhelper-perl libelf1 libexpat1 > libfile-stripnondeterminism-perl libice6 libicu71 libjq1 > libjs-angular-file-upload libjs-angular-gettext libjs-angular-schema-form > libjs-angularjs libjs-angularjs-smart-table libjs-bootstrap libjs-bootswatch > libjs-d3 libjs-jquery libjs-jquery-cookie libjs-jquery-metadata > libjs-jquery-tablesorter libjs-jquery-ui libjs-jquery.quicksearch > libjs-jsencrypt libjs-lrdragndrop libjs-magic-search libjs-objectpath > libjs-rickshaw libjs-sphinxdoc libjs-spin.js libjs-term.js libjs-tv4 > libjs-twitter-bootstrap-datepicker libjs-underscore libjson-perl > libmagic-mgc libmagic1 libmd0 libmpdec3 libncursesw6 libonig5 libpipeline1 > libpsl5 libpython3-stdlib libpython3.10-minimal libpython3.10-stdlib > libpython3.9-minimal libpython3.9-stdlib libreadline8 libsigsegv2 libsm6 > libsqlite3-0 libsub-override-perl libsubunit-perl libtool libuchardet0 > libx11-6 libx11-data libxau6 libxcb1 libxdmcp6 libxext6 libxml2 libxmu6 > libxslt1.1 libxt6 libyaml-0-2 m4 man-db media-types netbase openssl > openstack-dashboard openstack-pkg-tools po-debconf pyflakes3 > python-babel-localedata python3 python3-alabaster python3-all > python3-appdirs python3-asgiref python3-attr python3-autopage python3-babel > python3-blinker python3-bson
Processed: Bug#1013515 marked as pending in ironic-ui
Processing control commands: > tag -1 pending Bug #1013515 [src:ironic-ui] ironic-ui: FTBFS: Errors while processing: openstack-dashboard sbuild-build-depends-main-dummy Added tag(s) pending. -- 1013515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013515: marked as pending in ironic-ui
Control: tag -1 pending Hello, Bug #1013515 in ironic-ui 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/openstack-team/horizon-plugins/ironic-ui/-/commit/b99e62f640b4bb5844100e54889e034c4455b7fd * Fix Django 4.x compat (Closes: #1013515): - Add django-4.x-ugettext_lazy-is-removed.patch - Add django-4.x-url-is-removed.patch (this message was generated automatically) -- Greetings https://bugs.debian.org/1013515
Bug#1013642: marked as done (apertium-eng-cat: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met)
Your message dated Thu, 30 Jun 2022 08:34:08 + with message-id and subject line Bug#1013642: fixed in apertium-eng-cat 1.0.1-5 has caused the Debian Bug report #1013642, regarding apertium-eng-cat: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met 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.) -- 1013642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apertium-eng-cat Version: 1.0.1-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220624 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking pkg-config is at least version 0.9.0... yes > checking for apertium >= 3.6.0... yes > checking for lttoolbox >= 3.5.0... yes > checking for cg3 >= 1.3.0... yes > checking for apertium-lex-tools >= 0.2.2... no > configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not > met > > No package 'apertium-lex-tools' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS > and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2022/06/24/apertium-eng-cat_1.0.1-4_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220624=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: apertium-eng-cat Source-Version: 1.0.1-5 Done: Kartik Mistry We believe that the bug you reported is fixed in the latest version of apertium-eng-cat, 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 1013...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kartik Mistry (supplier of updated apertium-eng-cat 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: Thu, 30 Jun 2022 12:16:16 +0530 Source: apertium-eng-cat Architecture: source Version: 1.0.1-5 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Kartik Mistry Closes: 1013642 Changes: apertium-eng-cat (1.0.1-5) unstable; urgency=medium . * debian/control: + Updated Build-Depends: apertium-lex-tools -> apertium-lex-tools-dev (Closes: #1013642) + Updated Standards-Version to 4.6.1 * Updated debian/watch. * Updated debian/copyright. Checksums-Sha1: 6d175f062421b0869d5e0dbf1a53d2518b46e237 2223 apertium-eng-cat_1.0.1-5.dsc cd3e21ed8f2dc68ffacfff893c1f2d030779bb5f 3996 apertium-eng-cat_1.0.1-5.debian.tar.xz Checksums-Sha256: 20405947c8fd411a277ab7558a781ae33af806ea80b89fea89cb417924f604a5 2223 apertium-eng-cat_1.0.1-5.dsc 53d97eab16be8b5c0ba16239d007790805bcc209e6c1b8cdee7faed68c5b98e6 3996 apertium-eng-cat_1.0.1-5.debian.tar.xz Files: d07f70570bf82be5e1f58bfdeb78faba 2223 science optional apertium-eng-cat_1.0.1-5.dsc fbb2af206625f5e1628ed82820118dd6 3996 science optional apertium-eng-cat_1.0.1-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEa2MbXvVUr2sRlmKSAsHT8ng6pN4FAmK9VtsACgkQAsHT8ng6 pN60+hAAomx4LDpnbAYzzXbE6PCBzvO/KC5llhpvu+mpMtpFDYDWzHpEckcb0hqz jqKu+6awAweqTI+tfVz/TQlR4c7GRBXTMVbNI51zYZGYqN55LilUmkcwbBA1Zzev fWvWpyJ513340XnvpwtOYB1C1rofol/MevGaOi1bF+9VNvu+tt9un9UhbqWYk2HQ
Processed: reassign 1013497 to src:djangorestframework
Processing commands for cont...@bugs.debian.org: > reassign 1013497 src:djangorestframework Bug #1013497 [src:django-countries] django-countries: FTBFS: ModuleNotFoundError: No module named 'pytz' Bug reassigned from package 'src:django-countries' to 'src:djangorestframework'. No longer marked as found in versions django-countries/7.3.2-1. Ignoring request to alter fixed versions of bug #1013497 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1013497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984331: riscv64 usertags for #984331 ld issue
user debian-ri...@lists.debian.org usertag 984331 + riscv64 stop Hi, sipxtapi still FTBFS in riscv64: https://buildd.debian.org/status/fetch.php?pkg=sipxtapi=riscv64=3.3.0%7Etest18%2Bdfsg.1-0.1=1588496881=0 libtool: link: g++ -g -O2 "-fdebug-prefix-map=/<>=." -fstack-protector-strong -Wformat -Werror=format-security -DHAVE_SPEEX -D__pingtel_on_posix__ -D_linux_ -D_REENTRANT -D_FILE_OFFSET_BITS=64 -fmessage-length=0 -Wall -Wformat -Wwrite-strings -Wpointer-arith -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/basicImClient basicImClient.o ../../../sipXtackLib/src/.libs/libsipXtack.so ../../../sipXsdpLib/src/.libs/libsipXsdp.so ../../../sipXportLib/src/.libs/libsipXport.so /usr/bin/ld: ../../../sipXtackLib/src/.libs/libsipXtack.so: undefined reference to `_res_opcodes' collect2: error: ld returned 1 exit status make[7]: *** [Makefile:494: basicImClient] Error 1 This ld issue cause many packages FTBFS in riscv64. -- 肖盛文 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
Bug#1014094: xsimd: autopkgtest regression on i386: ‘any’ is not a member of ‘xsimd’
Source: xsimd Version: 8.1.0-4 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of xsimd the autopkgtest of xsimd fails in testing when that autopkgtest is run with the binary packages of xsimd from unstable. It passes when run with only packages from testing. In tabular form: passfail xsimd from testing8.1.0-4 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=xsimd https://ci.debian.net/data/autopkgtest/testing/i386/x/xsimd/23188370/log.gz Testing with gcc: mandelbrot.cpp: In function ‘xsimd::batch xsimd::mandel(const xsimd::batch_bool&, const xsimd::batch&, const xsimd::batch&, int)’: mandelbrot.cpp:74:25: error: ‘any’ is not a member of ‘xsimd’ 74 | if (!xsimd::any(active)) | ^~~ mandelbrot.cpp: In function ‘void xsimd::mandelbrot(float, float, float, float, int, int, int, int*)’: mandelbrot.cpp:112:71: error: ‘aligned_mode’ is not a member of ‘xsimd’; did you mean ‘aligned_free’? 112 | auto programIndex = float_batch_type::load([0], xsimd::aligned_mode()); | ^~~~ | aligned_free autopkgtest [18:16:18]: test command1 OpenPGP_signature Description: OpenPGP digital signature
Processed: broken packages are removed from testing so shouldn't block migration anymore
Processing commands for cont...@bugs.debian.org: > reassign 1010821 src:xml2rfc 3.12.4-1 Bug #1010821 [src:pypdf2, src:xml2rfc] pypdf2 breaks xml2rfc autopkgtest: lxml.etree.XMLSyntaxError: PCDATA invalid Char value 1 Bug reassigned from package 'src:pypdf2, src:xml2rfc' to 'src:xml2rfc'. No longer marked as found in versions pypdf2/1.27.12-1 and xml2rfc/3.12.4-1. Ignoring request to alter fixed versions of bug #1010821 to the same values previously set Bug #1010821 [src:xml2rfc] pypdf2 breaks xml2rfc autopkgtest: lxml.etree.XMLSyntaxError: PCDATA invalid Char value 1 Marked as found in versions xml2rfc/3.12.4-1. > affects 1010821 src:pypdf2 Bug #1010821 [src:xml2rfc] pypdf2 breaks xml2rfc autopkgtest: lxml.etree.XMLSyntaxError: PCDATA invalid Char value 1 Added indication that 1010821 affects src:pypdf2 > reassign 1010820 src:bookletimposer 0.3.1-1 Bug #1010820 [src:pypdf2, src:bookletimposer] pypdf2 breaks bookletimposer autopkgtest: Can't get Fields array Bug reassigned from package 'src:pypdf2, src:bookletimposer' to 'src:bookletimposer'. No longer marked as found in versions bookletimposer/0.3.1-1 and pypdf2/1.27.12-1. Ignoring request to alter fixed versions of bug #1010820 to the same values previously set Bug #1010820 [src:bookletimposer] pypdf2 breaks bookletimposer autopkgtest: Can't get Fields array Marked as found in versions bookletimposer/0.3.1-1. > affects 1010820 src:pypdf2 Bug #1010820 [src:bookletimposer] pypdf2 breaks bookletimposer autopkgtest: Can't get Fields array Added indication that 1010820 affects src:pypdf2 > thanks Stopping processing here. Please contact me if you need assistance. -- 1010820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010820 1010821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010821 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Fwd:
Processing commands for cont...@bugs.debian.org: > block 928224 by 1014091 Bug #928224 [valgrind] Valgrind is broken on armhf 928224 was not blocked by any bugs. 928224 was blocking: 983377 Added blocking bug(s) of 928224: 1014091 > End of message, stopping processing here. Please contact me if you need assistance. -- 928224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014090: python3-poetry: Missing dependency on python3-cachecontrol
Package: python3-poetry Version: 1.1.12+dfsg-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: tipos...@tiscali.it Dear Maintainer, I installed poetry and this happened $ poetry init Traceback (most recent call last): File "/usr/bin/poetry", line 5, in from poetry.console import main File "/usr/lib/python3/dist-packages/poetry/console/__init__.py", line 1, in from .application import Application File "/usr/lib/python3/dist-packages/poetry/console/application.py", line 7, in from .commands.about import AboutCommand File "/usr/lib/python3/dist-packages/poetry/console/commands/__init__.py", line 4, in from .check import CheckCommand File "/usr/lib/python3/dist-packages/poetry/console/commands/check.py", line 2, in from poetry.factory import Factory File "/usr/lib/python3/dist-packages/poetry/factory.py", line 18, in from .repositories.pypi_repository import PyPiRepository File "/usr/lib/python3/dist-packages/poetry/repositories/pypi_repository.py", line 11, in from cachecontrol import CacheControl ModuleNotFoundError: No module named 'cachecontrol' Please fix the dependencies Best -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-poetry depends on: ii python3 3.10.4-1+b1 ii python3-cachecontrol0.12.11-1 ii python3-cachy 0.3.0-4 ii python3-cleo0.8.1-4 ii python3-clikit 0.6.2-3 ii python3-html5lib1.1-3 ii python3-importlib-metadata 4.6.4-1 ii python3-lockfile1:0.12.2-2.2 ii python3-packaging 21.3-1 ii python3-pexpect 4.8.0-3 ii python3-pkginfo 1.8.2-1 ii python3-poetry-core 1.0.7-2 ii python3-requests2.27.1+dfsg-1 ii python3-requests-toolbelt 0.9.1-2 ii python3-shellingham 1.4.0-1 ii python3-tomlkit 0.9.2-1 ii python3-virtualenv 20.15.0+ds-1 python3-poetry recommends no packages. python3-poetry suggests no packages. -- no debconf information
