Bug#999730: mtr: Fix FTBFS with glib2.0 >= 2.70 and deprecated GTimeVal of gtk+2.0
Hi, I've accepted a patch into upstream that fixes the format errors. Roger. On Mon, Nov 15, 2021 at 05:21:45PM +0100, Lukas Märdian wrote: > Package: mtr > Version: 0.94-2 > Severity: serious > Tags: patch ftbfs > Justification: fails to build from source (but built successfully in the past) > User: ubuntu-de...@lists.ubuntu.com > Usertags: origin-ubuntu jammy ubuntu-patch > X-Debbugs-Cc: sl...@ubuntu.com > > Hi Robert, > > mtr fails to build from source, if compiled against glib2.0 >= v2.70, due to > usage of deprecated GTimeVal in gtk+2.0 headers (that's a dependency of mtr). > > In Ubuntu, the attached patch was applied to achieve the following: > > * Fix FTBFS with glib >= 2.70 & deprecated definitions of GTimeVal in > gtk+2.0 > > > Thanks for considering the patch. > > Cheers, > Lukas > > Build log: > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread > -I/usr/include/gtk-2.0 -I/usr/lib/s390x-linux-gnu/gtk-2.0/include > -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/libpng16 -I/usr/include/s390x-linux-gnu > -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi > -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/harfbuzz > -I/usr/include/glib-2.0 -I/usr/lib/s390x-linux-gnu/glib-2.0/include > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16-g > -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects > -fstack-protector-strong -Wformat -Werror=format-security -Wall > -Wno-pointer-sign -c -o ui/mtr-gtk.o `test -f 'ui/gtk.c' || echo > '../'`ui/gtk.c > ../ui/curses.c: In function ‘mtr_curses_hosts’: > ../ui/curses.c:435:17: error: format not a string literal and no format > arguments [-Werror=format-security] > 435 | printw(fmt_ipinfo(ctl, addr)); > | ^~ > ../ui/curses.c:488:21: error: format not a string literal and no format > arguments [-Werror=format-security] > 488 | printw(fmt_ipinfo(ctl, addrs)); > | ^~ > ../ui/curses.c: In function ‘mtr_curses_graph’: > ../ui/curses.c:653:17: error: format not a string literal and no format > arguments [-Werror=format-security] > 653 | printw(fmt_ipinfo(ctl, addr)); > | ^~ > ../ui/curses.c: In function ‘mtr_curses_redraw’: > ../ui/curses.c:703:5: error: format not a string literal and no format > arguments [-Werror=format-security] > 703 | mvprintw(1, maxx - 25, iso_time(&t)); > | ^~~~ > ../ui/curses.c:763:42: error: format not a string literal and no format > arguments [-Werror=format-security] > 763 | mvprintw(rowstat - 1, startstat, msg); > | ^~~ > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects > -fstack-protector-strong -Wformat -Werror=format-security -Wall > -Wno-pointer-sign -c -o packet/packet.o ../packet/packet.c > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects > -fstack-protector-strong -Wformat -Werror=format-security -Wall > -Wno-pointer-sign -c -o packet/cmdparse.o ../packet/cmdparse.c > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects > -fstack-protector-strong -Wformat -Werror=format-security -Wall > -Wno-pointer-sign -c -o packet/command.o ../packet/command.c > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects > -fstack-protector-strong -Wformat -Werror=format-security -Wall > -Wno-pointer-sign -c -o packet/probe.o ../packet/probe.c > In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37, > from /usr/include/gtk-2.0/gtk/gtkwidget.h:36, > from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35, > from /usr/include/gtk-2.0/gtk/gtkbin.h:35, > from /usr/include/gtk-2.0/gtk/gtkwindow.h:36, > from /usr/include/gtk-2.0/gtk/gtkdialog.h:35, > from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32, > from /usr/include/gtk-2.0/gtk/gtk.h:33, > from ../ui/gtk.c:31: > /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is > deprecated [-Wdeprecated-declarations] > 236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags); > | ^~~~ > In file included from /usr/include/glib-2.0/gobject/gobject.h:24, > from /usr/include/glib-2.0/gobject/gbinding.h:29, > from /usr/include/glib-2.0/glib-object.h:22, > from /usr/include/glib-2.0/gio/gioenums.h:28, > from /usr/inclu
Bug#994055: marked as done (cunit: FTBFS: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Tue, 16 Nov 2021 08:37:13 + with message-id and subject line Bug#994055: fixed in cunit 2.1-3-dfsg-2.4 has caused the Debian Bug report #994055, regarding cunit: FTBFS: format not a string literal and no format arguments [-Werror=format-security] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 994055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cunit Version: 2.1-3-dfsg-2.3 Severity: serious Tags: ftbfs bookworm sid Your package FTBFS with libncurses-dev 6.2+20210905-1, as several mvwprintw() calls now trigger format warnings from gcc which dpkg-buildflags turns into errors thanks to -Werror=format-security: , | Curses.c: In function 'show_suite_level_help': | Curses.c:955:37: error: format not a string literal and no format arguments [-Werror=format-security] | 955 | mvwprintw(details_pad.pPad, 0, 0, szTemp); | | ^~ | Curses.c:959:37: error: format not a string literal and no format arguments [-Werror=format-security] | 959 | mvwprintw(details_pad.pPad, 2, 0, szTemp); | | ^~ | Curses.c: In function 'list_tests': | Curses.c:1071:37: error: format not a string literal and no format arguments [-Werror=format-security] | 1071 | mvwprintw(details_pad.pPad, 0, 0, szTemp); | | ^~ | Curses.c:1078:37: error: format not a string literal and no format arguments [-Werror=format-security] | 1078 | mvwprintw(details_pad.pPad, 1, 0, szTemp); | | ^~ | Curses.c: In function 'curses_set_options_run': | Curses.c:1161:39: error: format not a string literal and no format arguments [-Werror=format-security] | 1161 | mvwprintw(details_pad.pPad, 2, 0, szTemp); | | ^~ | cc1: some warnings being treated as errors ` A full build log is at [1]. See #993179 for the change in ncurses which lead to these new errors. 1. https://ci.debian.net/data/autopkgtest/testing/amd64/c/cunit/15168126/log.gz --- End Message --- --- Begin Message --- Source: cunit Source-Version: 2.1-3-dfsg-2.4 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of cunit, 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 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated cunit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 09 Nov 2021 20:42:23 +0100 Source: cunit Architecture: source Version: 2.1-3-dfsg-2.4 Distribution: unstable Urgency: medium Maintainer: Azat Khuzhin Changed-By: Paul Gevers Closes: 994055 Changes: cunit (2.1-3-dfsg-2.4) unstable; urgency=medium . * Non-maintainer upload . [ Sven Joachim ] * Fix string format errors with recent ncurses (Closes: #994055) Checksums-Sha1: 4bf0a0fa35bbfead279be8d4b99d8264bd9ba660 1987 cunit_2.1-3-dfsg-2.4.dsc 8bc6ea83572e1afeec921a3ea93291962fd9843a 8096 cunit_2.1-3-dfsg-2.4.debian.tar.xz Checksums-Sha256: 1426a5571831a7f7772047a8bb68a4a51ad8b6dfba966cd76df72b7fc3444bad 1987 cunit_2.1-3-dfsg-2.4.dsc e7a09a24c7db0e2aa9feb444fe38957286ebfc63b355c308957794f064b5881d 8096 cunit_2.1-3-dfsg-2.4.debian.tar.xz Files: d47fd93309271439c0674157b2ae128b 1987 libs optional cunit_2.1-3-dfsg-2.4.dsc 3e3d410f3d04e83b16e45ebc296d0c98 8096 libs optional cunit_2.1-3-dfsg-2.4.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmGMM7gACgkQnFyZ6wW9 dQoKnwf/Z9toaTgPba2fGHudqyey1jrGzPQi31GpJBSZNlYZTmy+njyMgpT1cEuT Has7NqWET+MH72YaVmqPq6xuYhA7JIk4w7e/q5TQXiU+8gLFVDlwr5b0rp3/NqRq z2bsYhjCSNHc8NeSDbzUILcq01w2N3Eo3KvHoa3Ip3nfeZWSgHdHAJa5VDVTvb8D 6jJf8HwOrTyAFdlmV3QOBjEFylJ1FNbc5/EVnoPssZ0Bw7CEaTGWnNBMYjG09+zt vQ/vAGbYSUsk2JzsOe0HnbCqBU4ZqO1b21dbc0jd/OfJgUg7lZPa7lsVsjBTtc+L aAI8h0a+AgeHOTeTCSeGJYGvIB0X5w== =3zxx -END PGP SIGNATURE End Message ---
Bug#999760: opencv: libopencv-*4.5d: missing Breaks+Replaces: libopencv-*4.5
Source: opencv Version: 4.5.4+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. This error may also be triggered by having a predecessor package from 'sid 'installed while installing the package from 'experimental'. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libopencv-core4.5d_4.5.4+dfsg-2_amd64.deb ... Unpacking libopencv-core4.5d:amd64 (4.5.4+dfsg-2) ... dpkg: error processing archive /var/cache/apt/archives/libopencv-core4.5d_4.5.4+dfsg-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libopencv_core.so.4.5.4', which is also in package libopencv-core4.5:amd64 4.5.4+dfsg-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../libopencv-flann4.5d_4.5.4+dfsg-2_amd64.deb ... Unpacking libopencv-flann4.5d:amd64 (4.5.4+dfsg-2) ... dpkg: error processing archive /var/cache/apt/archives/libopencv-flann4.5d_4.5.4+dfsg-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libopencv_flann.so.4.5.4', which is also in package libopencv-flann4.5:amd64 4.5.4+dfsg-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../libopencv-imgproc4.5d_4.5.4+dfsg-2_amd64.deb ... Unpacking libopencv-imgproc4.5d:amd64 (4.5.4+dfsg-2) ... dpkg: error processing archive /var/cache/apt/archives/libopencv-imgproc4.5d_4.5.4+dfsg-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libopencv_imgproc.so.4.5.4', which is also in package libopencv-imgproc4.5:amd64 4.5.4+dfsg-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../libopencv-features2d4.5d_4.5.4+dfsg-2_amd64.deb ... Unpacking libopencv-features2d4.5d:amd64 (4.5.4+dfsg-2) ... dpkg: error processing archive /var/cache/apt/archives/libopencv-features2d4.5d_4.5.4+dfsg-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libopencv_features2d.so.4.5.4', which is also in package libopencv-features2d4.5:amd64 4.5.4+dfsg-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../libopencv-calib3d4.5d_4.5.4+dfsg-2_amd64.deb ... Unpacking libopencv-calib3d4.5d:amd64 (4.5.4+dfsg-2) ... dpkg: error processing archive /var/cache/apt/archives/libopencv-calib3d4.5d_4.5.4+dfsg-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.5.4', which is also in package libopencv-calib3d4.5:amd64 4.5.4+dfsg-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libopencv-core4.5d_4.5.4+dfsg-2_amd64.deb /var/cache/apt/archives/libopencv-flann4.5d_4.5.4+dfsg-2_amd64.deb /var/cache/apt/archives/libopencv-imgproc4.5d_4.5.4+dfsg-2_amd64.deb /var/cache/apt/archives/libopencv-features2d4.5d_4.5.4+dfsg-2_amd64.deb /var/cache/apt/archives/libopencv-calib3d4.5d_4.5.4+dfsg-2_amd64.deb This seems to affect all libopencv-*4.5d packages. cheers, Andreas libopencv-core4.5=4.5.4+dfsg-1_libopencv-core4.5d=4.5.4+dfsg-2.log.gz Description: application/gzip
Bug#999761: fastjet: ships a copy of siscone
Source: fastjet Version: 3.4.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. These files are in both libfastjetplugins-dev and libsiscone-dev: usr/include/siscone/area.h usr/include/siscone/circulator.h usr/include/siscone/defines.h usr/include/siscone/geom_2d.h usr/include/siscone/hash.h usr/include/siscone/momentum.h usr/include/siscone/protocones.h usr/include/siscone/quadtree.h usr/include/siscone/ranlux.h usr/include/siscone/reference.h usr/include/siscone/siscone.h usr/include/siscone/siscone_error.h usr/include/siscone/split_merge.h usr/include/siscone/vicinity.h usr/lib/x86_64-linux-gnu/libsiscone.a usr/lib/x86_64-linux-gnu/libsiscone.so These files are in both libfastjetplugins-dev and libsiscone-spherical-dev: usr/include/siscone/spherical/geom_2d.h usr/include/siscone/spherical/hash.h usr/include/siscone/spherical/momentum.h usr/include/siscone/spherical/protocones.h usr/include/siscone/spherical/siscone.h usr/include/siscone/spherical/split_merge.h usr/include/siscone/spherical/vicinity.h usr/lib/x86_64-linux-gnu/libsiscone_spherical.a usr/lib/x86_64-linux-gnu/libsiscone_spherical.so There are conflicts between the library packages, too ... cheers, Andreas
Bug#995452: libpam-ssh breaks the agent-forwarding of normal ssh
Looks like my spam filter ate the notification that you answered, and/or since my post was "additional information only", I did not get a notification in the first place. My /etc/pam.d/sddm: (lines wrapped by email client marked with \) - #%PAM-1.0 # Block login if they are globally disabled authrequisite pam_nologin.so authrequiredpam_succeed_if.so user != root quiet_success # authsufficient pam_succeed_if.so user ingroup nopasswdlogin @include common-auth # gnome_keyring breaks QProcess -auth optionalpam_gnome_keyring.so -auth optionalpam_kwallet5.so -auth optionalpam_ssh.so use_first_pass @include common-account # SELinux needs to be the first session rule. This ensures that any # lingering context has been cleared. Without this it is possible that a # module could execute code in the wrong domain. session [success=ok ignore=ignore module_unknown=ignore default=bad] \ pam_selinux.so close # Create a new session keyring. session optionalpam_keyinit.so force revoke session requiredpam_limits.so session requiredpam_loginuid.so @include common-session # SELinux needs to intervene at login time to ensure that the process \ starts # in the proper default security context. Only sessions which are \ intended # to run in the user's context should be run after this. session [success=ok ignore=ignore module_unknown=ignore default=bad] \ pam_selinux.so open -session optional pam_gnome_keyring.so auto_start -session optional pam_kwallet5.so auto_start -session optional pam_ssh.so @include common-password # From the pam_env man page # Since setting of PAM environment variables can have side effects to \ other modules, this module should be the last one on the stack. # Load environment from /etc/environment session requiredpam_env.so # Load environment from /etc/default/locale and ~/.pam_environment session requiredpam_env.so envfile=/etc/default/locale \ user_readenv=1 - And my /etc/pam.d/login: - # # The PAM configuration file for the Shadow `login' service # # Enforce a minimal delay in case of failure (in microseconds). # (Replaces the `FAIL_DELAY' setting from login.defs) # Note that other modules may require another minimal delay. (for \ example, # to disable any delay, you should add the nodelay option to pam_unix) auth optional pam_faildelay.so delay=300 # Outputs an issue file prior to each login prompt (Replaces the # ISSUE_FILE option from login.defs). Uncomment for use # auth required pam_issue.so issue=/etc/issue # Disallows other than root logins when /etc/nologin exists # (Replaces the `NOLOGINS_FILE' option from login.defs) auth requisite pam_nologin.so # SELinux needs to be the first session rule. This ensures that any # lingering context has been cleared. Without this it is possible # that a module could execute code in the wrong domain. # When the module is present, "required" would be sufficient \ (When SELinux # is disabled, this returns success.) session [success=ok ignore=ignore module_unknown=ignore default=bad] \ pam_selinux.so close # Sets the loginuid process attribute sessionrequired pam_loginuid.so # Prints the message of the day upon successful login. # (Replaces the `MOTD_FILE' option in login.defs) # This includes a dynamically generated part from /run/motd.dynamic # and a static (admin-editable) part from /etc/motd. sessionoptional pam_motd.so motd=/run/motd.dynamic sessionoptional pam_motd.so noupdate # SELinux needs to intervene at login time to ensure that the process # starts in the proper default security context. Only sessions which are # intended to run in the user's context should be run after this. # pam_selinux.so changes the SELinux context of the used \ TTY and configures # SELinux in order to transition to the user context with the next \ execve() # call. session [success=ok ignore=ignore module_unknown=ignore default=bad] \ pam_selinux.so open # When the module is present, "required" would be sufficient (When \ SELinux # is disabled, this returns success.) # This module parses environment configuration file(s) # and also allows you to use an extended config # file /etc/security/pam_env.conf. # # parsing /etc/environment needs "readenv=1" session required pam_env.so readenv=1 # locale variables are also kept into /etc/default/locale in etch # reading this file *in addition to /etc/environment* does not hurt session required pam_env.so readenv=1 envfile=/etc/default\ /locale # Standard Un*x authentication. @include common-auth # This allows certain extra groups to be granted to a user # based on things like time of day, tty, service, and user. # Please edit /etc/security/group.conf to fit your needs # (Replaces the `CONSOLE_GROUPS' option in login.defs) auth
Processed: tagging 995624
Processing commands for cont...@bugs.debian.org: > tags 995624 + bookworm sid Bug #995624 [src:pktstat] pktstat FTBFS: error: format not a string literal and no format arguments [-Werror=format-security] Added tag(s) bookworm and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 995624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999764: gcc-12: file conflicts with gcc-11 due to missing Breaks+Replaces or renaming
Source: gcc-12 Version: 12-2023-1 Severity: serious To avoid repeating this bug on every new major upstrema release, I'd suggest to add Conflicts+Replaces+Provides: some-new-virtual-package to all intentionally not co-installable packages in addition to the Breaks+Replaces that is needed now. File conflicts with src:gcc-11: gcc-12-locales: usr/share/locale/be/LC_MESSAGES/cpplib-11.mo usr/share/locale/be/LC_MESSAGES/gcc-11.mo usr/share/locale/ca/LC_MESSAGES/cpplib-11.mo usr/share/locale/da/LC_MESSAGES/cpplib-11.mo usr/share/locale/da/LC_MESSAGES/gcc-11.mo usr/share/locale/de/LC_MESSAGES/cpplib-11.mo usr/share/locale/de/LC_MESSAGES/gcc-11.mo usr/share/locale/el/LC_MESSAGES/cpplib-11.mo usr/share/locale/el/LC_MESSAGES/gcc-11.mo usr/share/locale/eo/LC_MESSAGES/cpplib-11.mo usr/share/locale/es/LC_MESSAGES/cpplib-11.mo usr/share/locale/es/LC_MESSAGES/gcc-11.mo usr/share/locale/fi/LC_MESSAGES/cpplib-11.mo usr/share/locale/fi/LC_MESSAGES/gcc-11.mo usr/share/locale/fr/LC_MESSAGES/cpplib-11.mo usr/share/locale/fr/LC_MESSAGES/gcc-11.mo usr/share/locale/hr/LC_MESSAGES/gcc-11.mo usr/share/locale/id/LC_MESSAGES/cpplib-11.mo usr/share/locale/id/LC_MESSAGES/gcc-11.mo usr/share/locale/ja/LC_MESSAGES/cpplib-11.mo usr/share/locale/ja/LC_MESSAGES/gcc-11.mo usr/share/locale/nl/LC_MESSAGES/cpplib-11.mo usr/share/locale/nl/LC_MESSAGES/gcc-11.mo usr/share/locale/pt_BR/LC_MESSAGES/cpplib-11.mo usr/share/locale/ru/LC_MESSAGES/cpplib-11.mo usr/share/locale/ru/LC_MESSAGES/gcc-11.mo usr/share/locale/sr/LC_MESSAGES/cpplib-11.mo usr/share/locale/sr/LC_MESSAGES/gcc-11.mo usr/share/locale/sv/LC_MESSAGES/cpplib-11.mo usr/share/locale/sv/LC_MESSAGES/gcc-11.mo usr/share/locale/tr/LC_MESSAGES/cpplib-11.mo usr/share/locale/tr/LC_MESSAGES/gcc-11.mo usr/share/locale/uk/LC_MESSAGES/cpplib-11.mo usr/share/locale/uk/LC_MESSAGES/gcc-11.mo usr/share/locale/vi/LC_MESSAGES/cpplib-11.mo usr/share/locale/vi/LC_MESSAGES/gcc-11.mo usr/share/locale/zh_CN/LC_MESSAGES/cpplib-11.mo usr/share/locale/zh_CN/LC_MESSAGES/gcc-11.mo usr/share/locale/zh_TW/LC_MESSAGES/cpplib-11.mo usr/share/locale/zh_TW/LC_MESSAGES/gcc-11.mo gnat-12: usr/bin/gnat usr/bin/gnatbind usr/bin/gnatchop usr/bin/gnatclean usr/bin/gnatgcc usr/bin/gnathtml usr/bin/gnatkr usr/bin/gnatlink usr/bin/gnatls usr/bin/gnatmake usr/bin/gnatname usr/bin/gnatprep usr/bin/x86_64-linux-gnu-gnat usr/bin/x86_64-linux-gnu-gnatbind usr/bin/x86_64-linux-gnu-gnatchop usr/bin/x86_64-linux-gnu-gnatclean usr/bin/x86_64-linux-gnu-gnatgcc usr/bin/x86_64-linux-gnu-gnathtml usr/bin/x86_64-linux-gnu-gnatkr usr/bin/x86_64-linux-gnu-gnatlink usr/bin/x86_64-linux-gnu-gnatls usr/bin/x86_64-linux-gnu-gnatmake usr/bin/x86_64-linux-gnu-gnatname usr/bin/x86_64-linux-gnu-gnatprep usr/lib/x86_64-linux-gnu/libgnarl.so usr/lib/x86_64-linux-gnu/libgnat.so usr/share/man/man1/gnat.1.gz usr/share/man/man1/gnatbind.1.gz usr/share/man/man1/gnatchop.1.gz usr/share/man/man1/gnatclean.1.gz usr/share/man/man1/gnathtml.1.gz usr/share/man/man1/gnatkr.1.gz usr/share/man/man1/gnatlink.1.gz usr/share/man/man1/gnatls.1.gz usr/share/man/man1/gnatmake.1.gz usr/share/man/man1/gnatname.1.gz usr/share/man/man1/gnatprep.1.gz usr/share/man/man1/x86_64-linux-gnu-gnat.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatbind.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatchop.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatclean.1.gz usr/share/man/man1/x86_64-linux-gnu-gnathtml.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatkr.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatlink.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatls.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatmake.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatname.1.gz usr/share/man/man1/x86_64-linux-gnu-gnatprep.1.gz libstdc++6-12-dbg: usr/lib/x86_64-linux-gnu/debug/libstdc++.a usr/lib/x86_64-linux-gnu/debug/libstdc++.so usr/lib/x86_64-linux-gnu/debug/libstdc++.so.6 usr/lib/x86_64-linux-gnu/debug/libstdc++fs.a lib32stdc++6-12-dbg: usr/lib32/debug/libstdc++.a usr/lib32/debug/libstdc++.so usr/lib32/debug/libstdc++.so.6 usr/lib32/debug/libstdc++fs.a libx32stdc++6-12-dbg: usr/libx32/debug/libstdc++.a usr/libx32/debug/libstdc++.so usr/libx32/debug/libstdc++.so.6 usr/libx32/debug/libstdc++fs.a libgccjit-12-doc: usr/share/info/factorial.png usr/share/info/factorial1.png usr/share/info/libgccjit.info.gz usr/share/info/sum-of-squares.png usr/share/info/sum-of-squares1.png libstdc++-12-doc: usr/share/man/man3/C++Intro.3cxx.gz usr/share/man/man3/SGIextensions.3cxx.gz usr/share/man/man3/__gnu_cxx.3cxx.gz usr/share/man/man3/__gnu_cxx::_Caster.3cxx.gz usr/share/man/man3/__gnu_cxx::_Char_types.3cxx.gz usr/share/man/man3/__gnu_cxx::_ExtPtr_allocator.3cxx.gz usr/share/man/man3/__gnu_cxx::_Invalid_type.3cxx.gz ... libtsan2: usr/lib/x86_64-linux-gnu/libtsan_preinit.o Andreas
Bug#999767: rdkit: FTBFS on buildds / reproducible builds without network access
Source: rdkit Version: 202103.5-1 Severity: serious Tags: ftbfs Justification: Policy 4.9 According to Debian Policy 4.9: | For packages in the main archive, required targets must not attempt | network access, except, via the loopback interface, to services on the | build host that have been started by the build. However rdkit tries to download fonts from google.com during the configure stage, leading to a build failure when network is not available: ... | == Updating Filters.cpp from pains file | == Done updating pains files | Downloading https://fonts.google.com/download?family=Comic%20Neue... | CMake Error at Code/cmake/Modules/RDKitUtils.cmake:224 (MESSAGE): | The md5 checksum for | /build/1st/rdkit-202103.5/Code/GraphMol/MolDraw2D/Comic_Neue.zip is | incorrect; expected: 23ed3f833c1ae0adb141a26b4a30d73e, found: | d41d8cd98f00b204e9800998ecf8427e | Call Stack (most recent call first): | Code/GraphMol/MolDraw2D/CMakeLists.txt:16 (downloadAndCheckMD5) | | | -- Configuring incomplete, errors occurred! | See also "/build/1st/rdkit-202103.5/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log". | See also "/build/1st/rdkit-202103.5/obj-x86_64-linux-gnu/CMakeFiles/CMakeError.log". | cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt | ==> CMakeCache.txt <== ... The full build log can be found there: https://buildd.debian.org/status/fetch.php?pkg=rdkit&arch=riscv64&ver=202103.5-1&stamp=1636998503&raw=0 Or there: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rdkit.html
Bug#999768: lintian: false report: adopted-extended-field XS-Autobuild
Package: lintian Version: 2.112.0 Severity: serious Lintian now reports I: nvidia-graphics-drivers source: adopted-extended-field XS-Autobuild (in section for source) [debian/control:26] but that field is not usable as Autobuild, dpkg/sid does not accept it: dpkg-gencontrol: warning: unknown information field 'Autobuild' in input data in general section of control info file dpkg-genchanges: warning: unknown information field 'Autobuild' in input data in general section of control info file dpkg-source: warning: unknown information field 'Autobuild' in input data in general section of control info file Andreas
Bug#998593: marked as done (arch-test: FTBFS: win64.o:fake:(.text+0x27): relocation truncated to fit: R_X86_64_32S against `.data')
Your message dated Tue, 16 Nov 2021 12:33:29 + with message-id and subject line Bug#998593: fixed in arch-test 0.17-2 has caused the Debian Bug report #998593, regarding arch-test: FTBFS: win64.o:fake:(.text+0x27): relocation truncated to fit: R_X86_64_32S against `.data' 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.) -- 998593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998593 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: arch-test Version: 0.17-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > x86_64-linux-gnu-as --64 amd64.s -o amd64.o > x86_64-linux-gnu-as --x32 x32.s -o x32.o > x86_64-linux-gnu-as --32 i386.s -o i386.o > i686-w64-mingw32-as win32.s -o win32.o > x86_64-linux-gnu-ld -melf_x86_64 -s amd64.o -o arch-test-amd64 > x86_64-linux-gnu-ld -melf32_x86_64 -s x32.o -o arch-test-x32 > x86_64-linux-gnu-ld -melf_i386 -s i386.o -o arch-test-i386 > i686-w64-mingw32-ld -s win32.o -lkernel32 -o arch-test-win32 > x86_64-w64-mingw32-as win64.s -o win64.o > mips64el-linux-gnuabi64-as -32 -EB mips.s -o mips.o > mips64el-linux-gnuabi64-as -32 -EL mips.s -o mipsel.o > x86_64-w64-mingw32-ld -s win64.o -lkernel32 -o arch-test-win64 > mips64el-linux-gnuabi64-as -n32 -EB mipsn32.s -o mipsn32.o > mips64el-linux-gnuabi64-ld -melf32btsmip -s mips.o -o arch-test-mips > mips64el-linux-gnuabi64-ld -melf32ltsmip -s mipsel.o -o arch-test-mipsel > win64.o:fake:(.text+0x27): relocation truncated to fit: R_X86_64_32S against > `.data' > make[1]: *** [Makefile:65: arch-test-win64] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/11/04/arch-test_0.17-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: arch-test Source-Version: 0.17-2 Done: Adam Borowski We believe that the bug you reported is fixed in the latest version of arch-test, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adam Borowski (supplier of updated arch-test 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: Tue, 16 Nov 2021 13:05:14 +0100 Source: arch-test Architecture: source Version: 0.17-2 Distribution: unstable Urgency: medium Maintainer: Adam Borowski Changed-By: Adam Borowski Closes: 998593 Changes: arch-test (0.17-2) unstable; urgency=medium . * Temporarily disable win64 (binutils issue); closes: #998593. Checksums-Sha1: d0838cc5fc7310496d013e3063e11ae6c2a06aa7 2439 arch-test_0.17-2.dsc 06b0072e66ceaa38a8f52b61727764eaf639d187 4236 arch-test_0.17-2.debian.tar.xz ad59024659273ead647ce04a4de5e1e0e36872b4 6102 arch-test_0.17-2_source.buildinfo Checksums-Sha256: 88432dc537610bd08e1026f8ed103fccb47178986a9a6c103cd031a8b29416ef 2439 arch-test_0.17-2.dsc 9ae56547f4fad10ffb617ead92e237fcbb651626e080dcc52211ab5e6f876929 4236 arch-test_0.17-2.debian.tar.xz 93912ac23a3bc0832d28133d47c225de8a6d5972d704118bc27ef64d3064d676 6102 arch-test_0.17-2_source.buildinfo Files: 5715bcdfe9b03c9b943d568611599934 2439 admin optional arch-test_0.17-2.dsc ed85bb2af1b4c1c24890bfc425d729dc 4236 admin optional arch-test_0.17-2.debian.tar.xz c0e2a81ce9862f568f207c200144ab96 6102 admin optional arch-test_0.17-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmGTonsACgkQweDZLphv fH6SBRAAoKxfoXQj4VBQQnWrKTElhfI1Cm0SmMHYTon3jTch7zG+kiNwSLPhwJWc EUbsIhBEz107mp49QnfB8JI3GVsv4YljTMpZ9Si9gOgEH4ImiYOWkcnQ2pP30RHF zZYwX2nyhChM4
Bug#999754: Acknowledgement (tcsh: character class expansion is badly broken)
> Suggested resolutionn is to update the buster package to tcsh 6.23.00. Sorry, I should have written 'update the bullseye package'. Kimmon Suominen's suggested patches would doubtless be better from a distribution stability perspective, and I'm fine with that approach as well.
Bug#999773: ksh93u+m: missing Breaks+Replaces: ksh (<< 20210511)
Package: ksh93u+m
Version: 1.0.0~beta.1-1
Severity: serious
Tags: patch
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid 'installed while installing the package from 'experimental'.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>From the attached log (scroll to the bottom...):
Preparing to unpack .../ksh_20210510-93u+m-1.0.0~beta.1-1_amd64.deb ...
Unpacking ksh (20210510-93u+m-1.0.0~beta.1-1) ...
dpkg: error processing archive
/var/cache/apt/archives/ksh_20210510-93u+m-1.0.0~beta.1-1_amd64.deb (--unpack):
trying to overwrite '/bin/ksh93', which is also in package ksh93u+m
1.0.0~beta.1-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/ksh_20210510-93u+m-1.0.0~beta.1-1_amd64.deb
The overwrite error is actually the other way around since ksh93u+m
in sid is newer than ksh in experimental.
Therefore please add
Breaks+Replaces: ksh (<< 20210511)
to ksh93u+m to ensure clean upgrades from whatever ksh version
was installed.
You also need to use an increasing version for
'dh_gencontrol -- -v...', otherwise subsequent (binary) uploads that
have a binary package with same version as already in the archive will
be rejected.
See the attached patch for my suggested solution.
You will have to file RM bugs against ftp.debian.org to get the obsolete
src:ksh package removed from sid and experimental.
cheers,
Andreas
diff -Nru ksh93u+m-1.0.0~beta.1/debian/control
ksh93u+m-1.0.0~beta.1/debian/control
--- ksh93u+m-1.0.0~beta.1/debian/control2021-09-05 15:14:36.0
+0200
+++ ksh93u+m-1.0.0~beta.1/debian/control2021-11-16 14:00:52.0
+0100
@@ -11,8 +11,8 @@
Package: ksh93u+m
Architecture: any
-Replaces: ksh (<= 2020.0.0+really93u+20120801-10)
-Breaks: ksh (<= 2020.0.0+really93u+20120801-10)
+Replaces: ksh (<< 20210511)
+Breaks: ksh (<< 20210511)
Depends: ${shlibs:Depends}, ${misc:Depends}
Suggests: binfmt-support
Description: AT&T KornShell
diff -Nru ksh93u+m-1.0.0~beta.1/debian/rules ksh93u+m-1.0.0~beta.1/debian/rules
--- ksh93u+m-1.0.0~beta.1/debian/rules 2021-09-05 15:14:36.0 +0200
+++ ksh93u+m-1.0.0~beta.1/debian/rules 2021-11-16 14:00:52.0 +0100
@@ -7,6 +7,7 @@
export TZ=GMT
include /usr/share/dpkg/buildflags.mk
+include /usr/share/dpkg/pkg-info.mk
export CCFLAGS+=$(shell dpkg-buildflags --get CFLAGS)
export CCFLAGS+=$(shell dpkg-buildflags --get CPPFLAGS)
@@ -34,8 +35,8 @@
dh_installchangelogs NEWS
override_dh_gencontrol:
- dh_gencontrol --package=ksh93u+m
- dh_gencontrol --package=ksh -- -v20210511
+ dh_gencontrol --package=ksh --
-v20210511+$(DEB_VERSION_UPSTREAM_REVISION)
+ dh_gencontrol --remaining-packages
clean:
dh_testdir
ksh93u+m=1.0.0~beta.1-1_ksh=20210510-93u+m-1.0.0~beta.1-1.log.gz
Description: application/gzip
Processed: affects 998140
Processing commands for cont...@bugs.debian.org:
> affects 998140 src:caffe src:auto-multiple-choice src:node-opencv
Bug #998140 {Done: Timo Röhling } [src:opencv] opencv: ABI
breakage causes autopkgtest failures
Bug #998141 {Done: Timo Röhling } [src:opencv] opencv: ABI
breakage causes autopkgtest failures
Bug #998142 {Done: Timo Röhling } [src:opencv] opencv: ABI
breakage causes autopkgtest failures
Added indication that 998140 affects src:caffe, src:auto-multiple-choice, and
src:node-opencv
Added indication that 998141 affects src:caffe, src:auto-multiple-choice, and
src:node-opencv
Added indication that 998142 affects src:caffe, src:auto-multiple-choice, and
src:node-opencv
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
998140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998140
998141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998141
998142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#999760: marked as done (opencv: libopencv-*4.5d: missing Breaks+Replaces: libopencv-*4.5)
Your message dated Tue, 16 Nov 2021 14:36:29 + with message-id and subject line Bug#999760: fixed in opencv 4.5.4+dfsg-3 has caused the Debian Bug report #999760, regarding opencv: libopencv-*4.5d: missing Breaks+Replaces: libopencv-*4.5 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.) -- 999760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: opencv Version: 4.5.4+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. This error may also be triggered by having a predecessor package from 'sid 'installed while installing the package from 'experimental'. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libopencv-core4.5d_4.5.4+dfsg-2_amd64.deb ... Unpacking libopencv-core4.5d:amd64 (4.5.4+dfsg-2) ... dpkg: error processing archive /var/cache/apt/archives/libopencv-core4.5d_4.5.4+dfsg-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libopencv_core.so.4.5.4', which is also in package libopencv-core4.5:amd64 4.5.4+dfsg-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../libopencv-flann4.5d_4.5.4+dfsg-2_amd64.deb ... Unpacking libopencv-flann4.5d:amd64 (4.5.4+dfsg-2) ... dpkg: error processing archive /var/cache/apt/archives/libopencv-flann4.5d_4.5.4+dfsg-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libopencv_flann.so.4.5.4', which is also in package libopencv-flann4.5:amd64 4.5.4+dfsg-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../libopencv-imgproc4.5d_4.5.4+dfsg-2_amd64.deb ... Unpacking libopencv-imgproc4.5d:amd64 (4.5.4+dfsg-2) ... dpkg: error processing archive /var/cache/apt/archives/libopencv-imgproc4.5d_4.5.4+dfsg-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libopencv_imgproc.so.4.5.4', which is also in package libopencv-imgproc4.5:amd64 4.5.4+dfsg-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../libopencv-features2d4.5d_4.5.4+dfsg-2_amd64.deb ... Unpacking libopencv-features2d4.5d:amd64 (4.5.4+dfsg-2) ... dpkg: error processing archive /var/cache/apt/archives/libopencv-features2d4.5d_4.5.4+dfsg-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libopencv_features2d.so.4.5.4', which is also in package libopencv-features2d4.5:amd64 4.5.4+dfsg-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../libopencv-calib3d4.5d_4.5.4+dfsg-2_amd64.deb ... Unpacking libopencv-calib3d4.5d:amd64 (4.5.4+dfsg-2) ... dpkg: error processing archive /var/cache/apt/archives/libopencv-calib3d4.5d_4.5.4+dfsg-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.5.4', which is also in package libopencv-calib3d4.5:amd64 4.5.4+dfsg-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libopencv-core4.5d_4.5.4+dfsg-2_amd64.deb /var/cache/apt/archives/libopencv-flann4.5d_4.5.4+dfsg-2_amd64.deb /var/cache/apt/archives/libopencv-imgproc4.5d_4.5.4+dfsg-2_amd64.deb /var/cache/apt/archives/libopencv-features2d4.5d_4.5.4+dfsg-2_amd64.deb /var/cache/apt/archives/libopencv-calib3d4.5d_4.5.4+dfsg-2_amd64.deb This seems to affect all libopencv-*4.5d packages. cheers, Andreas libopencv-core4.5=4.5.4+dfsg-1_libopencv-core4.5d=4.5.4+dfsg-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: opencv Source-Version: 4.5.4+dfsg-3 Done: Timo Röhling We believe that the bug you reported is fixed in the latest version of opencv, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Röhl
Bug#999619: Some debugging info - also about tcmalloc
Hi, the log messages are misleading at best, when reproducing in autopkgtest in a local VM I've found: $ sudo /usr/sbin/tgtd -f tgtd: iser_ib_init(3431) Failed to initialize RDMA; load kernel modules? tgtd: work_timer_start(146) use timer_fd based scheduler src/tcmalloc.cc:333] Attempt to free invalid pointer 0x55abdf028b00 Aborted It is only glusterfs, as this resolves the issue: $ sudo apt remove tgt-glusterfs $ sudo /usr/sbin/tgtd -f tgtd: iser_ib_init(3431) Failed to initialize RDMA; load kernel modules? tgtd: work_timer_start(146) use timer_fd based scheduler tgtd: bs_init(387) use signalfd notification This sounds very much like https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1950777 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999700 Reported the same to Ubuntu under https://bugs.launchpad.net/debian/+source/glusterfs/+bug/1951126 and hoping to find some time for it tomorrow. -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd
Bug#995781: [Debian-med-packaging] Bug#995781: python-sqlsoup autopkgtest fails with SQLAlchemy 1.4.23+ds1-2
On Sun, Nov 14, 2021, at 12:19 AM, Paul Wise wrote: > On Fri, 08 Oct 2021 16:51:06 -0400 Mike Bayer wrote: > > > SQLSoup's repository is currently at > > https://github.com/zzzeek/sqlsoup > > > > However it has not been maintained for many years and would not be > > expected to work with modern versions of SQLAlchemy. > > I suggest that you make this official by either mentioning that SQLSoup > is no longer maintained in the README.md, or using the "archived" > feature on GitHub, which marks the repository as read-only and adds a > banner about the repository no longer being maintained. I've done both as well as taken down the readthedocs page. > > https://docs.github.com/en/repositories/archiving-a-github-repository/archiving-repositories > > FTR, I've filed a bug upstream against Python plac, which is the only > other thing in Debian that uses SQLSoup (for its build-time tests). > > https://github.com/ialbert/plac/issues/62 > > -- > bye, > pabs > > https://wiki.debian.org/PaulWise > > > *Attachments:* > * signature.asc
Bug#997520: marked as pending in plank
Control: tag -1 pending Hello, Bug #997520 in plank 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/debian-mate-team/plank/-/commit/2acb02f37822a608e2e0ca7cd77b7bd515de9d5e debian/patches: Add 1001_fix-vala-doc-build.patch. Fix vala-doc generation. Recently, image file format has been changed from .png to .svg files. (Closes: #997520). (this message was generated automatically) -- Greetings https://bugs.debian.org/997520
Processed: Bug#997520 marked as pending in plank
Processing control commands: > tag -1 pending Bug #997520 [src:plank] plank: FTBFS: make[4]: *** No rule to make target 'vala-doc/plank/*.png', needed by 'all-am'. Stop. Added tag(s) pending. -- 997520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997520 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997520: marked as done (plank: FTBFS: make[4]: *** No rule to make target 'vala-doc/plank/*.png', needed by 'all-am'. Stop.)
Your message dated Tue, 16 Nov 2021 16:22:15 + with message-id and subject line Bug#997520: fixed in plank 0.11.89-4 has caused the Debian Bug report #997520, regarding plank: FTBFS: make[4]: *** No rule to make target 'vala-doc/plank/*.png', needed by 'all-am'. Stop. 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.) -- 997520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997520 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: plank Version: 0.11.89-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/docs' > /usr/bin/valadoc \ > -o vala-doc/ \ > --doclet=devhelp \ > --force --verbose --package-name plank --package-version 0.11.89 > --target-glib=2.40 --define HAVE_BARRIERS --define HAVE_DBUSMENU --define > HAVE_SYS_PRCTL_H --pkg gio-unix-2.0 --pkg gmodule-2.0 > --pkg gtk+-3.0 --pkg gdk-x11-3.0 >--pkg gdk-pixbuf-2.0 --pkg cairo > --pkg gee-0.8 --pkg libbamf3 > --pkg libwnck-3.0 --pkg posix > --pkg x11 --pkg xi --pkg xfixes --pkg Dbusmenu-0.4 --pkg > DbusmenuGtk3-0.4 --driver "`/usr/bin/valac --version`" --pkg plank-internal > --pkg compat --pkg config --vapidir=../lib --vapidir=../vapi \ > ../lib/DBusManager.vala ../lib/DockController.vala > ../lib/DockPreferences.vala ../lib/DockRenderer.vala ../lib/DragManager.vala > ../lib/HideManager.vala ../lib/PositionManager.vala ../lib/Version.vala > ../lib/DBus/Client.vala ../lib/DBus/Interfaces.vala > ../lib/Docklets/Docklet.vala ../lib/Docklets/DockletItem.vala > ../lib/Docklets/DockletManager.vala ../lib/Drawing/Color.vala > ../lib/Drawing/DrawingService.vala ../lib/Drawing/DockTheme.vala > ../lib/Drawing/Easing.vala ../lib/Drawing/Renderer.vala > ../lib/Drawing/Surface.vala ../lib/Drawing/SurfaceCache.vala > ../lib/Drawing/Theme.vala ../lib/Factories/AbstractMain.vala > ../lib/Factories/Factory.vala ../lib/Factories/ItemFactory.vala > ../lib/Items/ApplicationDockItem.vala > ../lib/Items/ApplicationDockItemProvider.vala > ../lib/Items/DefaultApplicationDockItemProvider.vala > ../lib/Items/DockContainer.vala ../lib/Items/DockElement.vala > ../lib/Items/DockItem.vala ../lib/Items/DockItemDrawValue.vala > ../lib/Items/DockItemProvider.vala ../lib/Items/DockItemPreferences.vala > ../lib/Items/Enums.vala ../lib/Items/FileDockItem.vala > ../lib/Items/PlaceholderDockItem.vala ../lib/Items/PlankDockItem.vala > ../lib/Items/TransientDockItem.vala ../lib/Services/Environment.vala > ../lib/Services/EnvironmentSettings.vala ../lib/Services/Logger.vala > ../lib/Services/Paths.vala ../lib/Services/Preferences.vala > ../lib/Services/Settings.vala ../lib/Services/System.vala > ../lib/Services/Unity.vala ../lib/Services/Worker.vala > ../lib/Widgets/CompositedWindow.vala ../lib/Widgets/DockWindow.vala > ../lib/Widgets/HoverWindow.vala ../lib/Widgets/PoofWindow.vala > ../lib/Widgets/PreferencesWindow.vala > ../lib/Widgets/TitledSeparatorMenuItem.vala > DockElement.vala:368.32-368.48: warning: `Gtk.ImageMenuItem' has been > deprecated since 3.10 > DockElement.vala:368.28-368.70: warning: `Gtk.ImageMenuItem' has been > deprecated since 3.10 > DockElement.vala:368.78-368.94: warning: `Gtk.ImageMenuItem' has been > deprecated since 3.10 > DockElement.vala:368.74-368.113: warning: `Gtk.ImageMenuItem' has been > deprecated since 3.10 > DockElement.vala:368.15-368.114: warning: `Gtk.ImageMenuItem' has been > deprecated since 3.10 > DockElement.vala:368.8-368.11: warning: `Gtk.ImageMenuItem' has been > deprecated since 3.10 > Settings.vala:100.35-100.52: warning: `GLib.Settings.list_keys' has been > deprecated since 2.46 > Settings.vala:58.35-58.52: warning: `GLib.Settings.list_keys' has been > deprecated since 2.46 > Theme.vala:111.16-111.42: warning: `Gtk.CssProvider.get_default' has been > deprecated since 3.24 > CompositedWindow.vala:43.4-43.18: warning: `Gtk.Widget.double_buffered' has > been deprecated since 3.14 > PositionManager.vala:137.22-137.48: warning: > `Gdk.Screen.get_monitor_workarea' has been deprecated since 3.22 > PositionManager.vala:115.12-115.37: warning: `Gdk.Screen.get_primary_monitor' > has been deprecated since 3.22 >
Processed: tagging 999750, found 993301 in 1.7.1-3.1, tagging 983224, tagging 983236, tagging 983253 ...
Processing commands for cont...@bugs.debian.org:
> tags 999750 + sid bookworm
Bug #999750 [src:lix] lix FTBFS with ldc 1.28.0
Added tag(s) sid and bookworm.
> found 993301 1.7.1-3.1
Bug #993301 [src:prototypejs] prototypejs: FTBFS
Marked as found in versions prototypejs/1.7.1-3.1.
> tags 983224 + sid bookworm
Bug #983224 [src:sosi2osm] sosi2osm: FTBFS with PROJ 8.0.0
Added tag(s) sid and bookworm.
> tags 983236 + sid bookworm
Bug #983236 {Done: Sebastiaan Couwenberg } [src:magics++]
magics++: FTBFS with PROJ 8.0.0
Added tag(s) bookworm and sid.
> tags 983253 + sid bookworm
Bug #983253 {Done: Adrian Bunk } [src:ncl] ncl: FTBFS with
PROJ 8.0.0
Added tag(s) bookworm and sid.
> tags 986770 + sid bookworm
Bug #986770 [shapetools] shapetools: FTBFS with glibc 2.32
Added tag(s) bookworm and sid.
> tags 998190 + sid bookworm
Bug #998190 [src:sagemath] sagemath: package new upstream version
Added tag(s) sid and bookworm.
> found 998723 3.5.0-2
Bug #998723 [libjs-fetch] node-whatwg-fetch conflicts libjs-fetch
Marked as found in versions libjs-fetch/3.5.0-2.
> tags 998411 + sid bookworm
Bug #998411 [src:hypre] hypre: shared libraries package must be renamed on
SONAME change (Policy 8.1)
Added tag(s) bookworm and sid.
> tags 979743 + sid bookworm
Bug #979743 [rungetty] rungetty: FTBFS with glibc 2.32
Added tag(s) sid and bookworm.
> tags 979448 + sid bookworm
Bug #979448 [alsamixergui] alsamixergui: FTBFS against glibc 2.32
Added tag(s) bookworm and sid.
> tags 999507 + sid bookworm
Bug #999507 [rust-tokio-signal] rust-tokio-signal, (build-)dependencies
unsatisfiable, abandoned upstream, should this package be removed.
Added tag(s) bookworm and sid.
> found 998854 1.4.2-1
Bug #998854 [python3-typed-ast] undefined symbol: _PyUnicode_DecodeUnicodeEscape
Marked as found in versions python3-typed-ast/1.4.2-1.
> tags 998854 + sid bookworm
Bug #998854 [python3-typed-ast] undefined symbol: _PyUnicode_DecodeUnicodeEscape
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
979448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979448
979743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979743
983224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983224
983236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983236
983253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983253
986770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986770
993301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993301
998190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998190
998411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998411
998723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998723
998854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998854
999507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999507
999750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999750
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#995781: Is sqlsoup really needed for epigrass? [m...@zzzcomputing.com: Bug#995781: Bug#995781: python-sqlsoup autopkgtest fails with SQLAlchemy 1.4.23+ds1-2]
Hi Flavio, thanks a lot for your really fast response. Its very helpful since we can now remove that orphaned package and remove some maintenance burden. Kind regards Andreas. Am Tue, Nov 16, 2021 at 01:27:47PM -0300 schrieb Flavio Coelho: > No, it's not. It's a left-over dependency. > I'll update the docs. > > thanks, > > > On Tue, Nov 16, 2021 at 1:07 PM Andreas Tille wrote: > > > Hi, > > > > it seems sqlsoup is not supported upstream any more. I see it mentioned in > > > >docs/source/install.rst > > > > but nowhere else in the code any more. Is it just a remaining in the docs > > and we can drop sqlsoup? > > > > Kind regards > > > > Andreas. > > > > - Weitergeleitete Nachricht von Mike Bayer > > - > > > > Date: Tue, 16 Nov 2021 10:41:43 -0500 > > From: Mike Bayer > > To: Paul Wise , 995...@bugs.debian.org > > Cc: Thomas Goirand > > Subject: Bug#995781: Bug#995781: python-sqlsoup autopkgtest fails with > > SQLAlchemy 1.4.23+ds1-2 > > X-Debian-PR-Message: followup 995781 > > X-Debian-PR-Package: src:python-sqlsoup > > X-Debian-PR-Keywords: sid bookworm upstream help > > X-Debian-PR-Source: python-sqlsoup > > > > > > > > On Sun, Nov 14, 2021, at 12:19 AM, Paul Wise wrote: > > > On Fri, 08 Oct 2021 16:51:06 -0400 Mike Bayer wrote: > > > > > > > SQLSoup's repository is currently at > > > > https://github.com/zzzeek/sqlsoup > > > > > > > > However it has not been maintained for many years and would not be > > > > expected to work with modern versions of SQLAlchemy. > > > > > > I suggest that you make this official by either mentioning that SQLSoup > > > is no longer maintained in the README.md, or using the "archived" > > > feature on GitHub, which marks the repository as read-only and adds a > > > banner about the repository no longer being maintained. > > > > I've done both as well as taken down the readthedocs page. > > > > > > > > > > > > > > > > > > https://docs.github.com/en/repositories/archiving-a-github-repository/archiving-repositories > > > > > > FTR, I've filed a bug upstream against Python plac, which is the only > > > other thing in Debian that uses SQLSoup (for its build-time tests). > > > > > > https://github.com/ialbert/plac/issues/62 > > > > > > -- > > > bye, > > > pabs > > > > > > https://wiki.debian.org/PaulWise > > > > > > > > > *Attachments:* > > > * signature.asc > > > > ___ > > Debian-med-packaging mailing list > > debian-med-packag...@alioth-lists.debian.net > > > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging > > > > > > - Ende weitergeleitete Nachricht - > > > > -- > > http://fam-tille.de > > -- http://fam-tille.de
Bug#998487: marked as done (glogic: FTBFS: configure.ac:12: error: AM_INIT_AUTOMAKE expanded multiple times)
Your message dated Tue, 16 Nov 2021 17:03:39 + with message-id and subject line Bug#998487: fixed in glogic 2.6-6 has caused the Debian Bug report #998487, regarding glogic: FTBFS: configure.ac:12: error: AM_INIT_AUTOMAKE expanded multiple times to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998487 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glogic Version: 2.6-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --with python3 >dh_update_autotools_config >dh_autoreconf > configure.ac:12: error: AM_INIT_AUTOMAKE expanded multiple times > /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... > configure.ac:3: the top level > /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... > configure.ac:12: the top level > autom4te: error: /usr/bin/m4 failed with exit status: 1 > aclocal: error: /usr/bin/autom4te failed with exit status: 1 > autoreconf: error: aclocal failed with exit status: 1 > dh_autoreconf: error: autoreconf -f -i returned exit code 1 > make: *** [debian/rules:4: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/glogic_2.6-5_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: glogic Source-Version: 2.6-6 Done: Håvard Flaget Aasen We believe that the bug you reported is fixed in the latest version of glogic, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Håvard Flaget Aasen (supplier of updated glogic 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: Tue, 16 Nov 2021 14:58:06 +0100 Source: glogic Architecture: source Version: 2.6-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Håvard Flaget Aasen Closes: 998487 Changes: glogic (2.6-6) unstable; urgency=medium . * QA upload. * Add gbp.conf * Patch: Remove duplicated line in configure.ac Closes: #998487 * Drop autopkgtest. * Update standards version to 4.6.0 Checksums-Sha1: c1e6c11d6f0fcb07593b1739e800e9f1558e688f 1851 glogic_2.6-6.dsc f182a2cf57d753772b72087cb569e2153824983b 5144 glogic_2.6-6.debian.tar.xz 9a4b12a1137a26962a44d470778ab0b38a65f14e 7599 glogic_2.6-6_source.buildinfo Checksums-Sha256: 870037f00155787b7ad79d3a1b797cca0c937d57f5ed7735379a00a456d63e39 1851 glogic_2.6-6.dsc 1885eabf3e833102b864b84bd41ded5f2020932ae4b453ef1d8987372a92c8fe 5144 glogic_2.6-6.debian.tar.xz 5ad489a4ecb8b1cf5aef4b3c027d64b4f285e3bf64b3852e697c41420461382e 7599 glogic_2.6-6_source.buildinfo Files: 64634d73d5d7bf3dc25c11af2bff0491 1851 electronics optional glogic_2.6-6.dsc 398dbc7d1e9b1a3e36a9aaf87a0ca371 5144 electronics optional glogic_2.6-6.debian.tar.xz a8f2ac7a57e46b62455cda795cf9a81d 7599 electronics optional glogic_2.6-6_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmGT32AACgkQweDZLphv fH4Fuw/9GzDnH+sa96huKyxuvtdH8H9mXN+VZqrZ+BDc7MsoV/ZR5+p8oZnC1zLr ag9E1tPcovG0NHwKb2zSR7GtdN1XZVfk4+2GaueuWAdEhhaMIeQXoLj1PmVg/BK6 iNLi+ENtdOFsnYGiU4nJRVgNivMmoWK4Vj9RVntpsPXO+F+JP1cDE2ffFGdgJaQ1 vZnBP997FcUFZZ/R48d96T4xlrQaw9vWZoN+zqTxafUOnNYBFHrhPwN9vw6H6AoH iEvcdQBmpLzg6ahF00o09EiiLcdGwFjqZMuan07JJUmV9eVl+8sQgfaQp1dUnGS6 3CJ6nJLiqOQiX8ua7jGa1aRNjW83b9V0a66a7GDJ0h2cTqHULHdlLXH3CCL3MkAO OJgmqkqA+P2CtQCMZ3mLZ3a/oyZ9Y/7yl1dXpCp0wF4WM198zLWWKfDfFFo/LIWW mbms
Bug#999773: ksh93u+m: missing Breaks+Replaces: ksh (<< 20210511)
On Tue, Nov 16, 2021 at 02:56:26PM +0100, Andreas Beckmann wrote: > Package: ksh93u+m > Version: 1.0.0~beta.1-1 > Severity: serious > Tags: patch > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package fails to upgrade from > 'sid' to 'experimental'. > It installed fine in 'sid', then the upgrade to 'experimental' fails > because it tries to overwrite other packages files without declaring a > Breaks+Replaces relation. > This error may also be triggered by having a predecessor package from > 'sid 'installed while installing the package from 'experimental'. Thanks for this observation and report. In this case, the version in experimental needs to be removed as that is no longer a valid upgrade path and has been superceded by the package transition to ksh93u+m. I will request the removal of the package in experimental to address this issue. Regards, Anuradha
Bug#994855: marked as done (zfs-dkms: Panic when receiving, fixed upstream)
Your message dated Wed, 17 Nov 2021 02:03:46 +0800 with message-id and subject line has caused the Debian Bug report #994855, regarding zfs-dkms: Panic when receiving, fixed upstream 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.) -- 994855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zfs-dkms Version: 2.0.3-9 Severity: grave Tags: patch upstream Justification: causes non-serious data loss With this latest version of the debian package, I've been getting panics receiving datasets. There's a patch already merged upstream. The errors are: VERIFY3(insert_inode_locked(ip) == 0) failed (-16 == 0) PANIC at zfs_znode.c:616:zfs_znode_alloc() The patch is at https://github.com/openzfs/zfs/commit/afa7b3484556d3ae610a34582ce5ebd2c3e27bba Please cherrypick this and add it soon. -- System Information: Debian Release: 11.0 APT prefers stable APT policy: (700, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-0.bpo.5-amd64 (SMP w/32 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages zfs-dkms depends on: ii debconf [debconf-2.0] 1.5.77 ii dkms 2.8.4-3 ii file 1:5.39-3 ii libc6-dev [libc-dev] 2.31-13 ii libpython3-stdlib 3.9.2-3 ii lsb-release11.1.0 ii perl 5.32.1-4 ii python3-distutils 3.9.2-1 Versions of packages zfs-dkms recommends: ii linux-libc-dev 5.10.46-4 ii zfs-zed 2.0.3-9 ii zfsutils-linux 2.0.3-9 Versions of packages zfs-dkms suggests: ii debhelper 13.3.4 -- debconf information excluded >From afa7b3484556d3ae610a34582ce5ebd2c3e27bba Mon Sep 17 00:00:00 2001 From: Paul Zuchowski <31706010+paulz...@users.noreply.github.com> Date: Fri, 11 Jun 2021 20:00:33 -0400 Subject: [PATCH] Do not hash unlinked inodes In zfs_znode_alloc we always hash inodes. If the znode is unlinked, we do not need to hash it. This fixes the problem where zfs_suspend_fs is doing zrele (iput) in an async fashion, and zfs_resume_fs unlinked drain processing will try to hash an inode that could still be hashed, resulting in a panic. Reviewed-by: Brian Behlendorf Reviewed-by: Alan Somers Signed-off-by: Paul Zuchowski Closes #9741 Closes #11223 Closes #11648 Closes #12210 --- module/os/linux/zfs/zfs_znode.c | 15 +++ 1 file changed, 11 insertions(+), 4 deletions(-) Index: zfs-linux-2.0.3/module/os/linux/zfs/zfs_znode.c === --- zfs-linux-2.0.3.orig/module/os/linux/zfs/zfs_znode.c +++ zfs-linux-2.0.3/module/os/linux/zfs/zfs_znode.c @@ -610,17 +610,24 @@ zfs_znode_alloc(zfsvfs_t *zfsvfs, dmu_bu * number is already hashed for this super block. This can never * happen because the inode numbers map 1:1 with the object numbers. * -* The one exception is rolling back a mounted file system, but in -* this case all the active inode are unhashed during the rollback. +* Exceptions include rolling back a mounted file system, either +* from the zfs rollback or zfs recv command. +* +* Active inodes are unhashed during the rollback, but since zrele +* can happen asynchronously, we can't guarantee they've been +* unhashed. This can cause hash collisions in unlinked drain +* processing so do not hash unlinked znodes. */ - VERIFY3S(insert_inode_locked(ip), ==, 0); + if (links > 0) + VERIFY3S(insert_inode_locked(ip), ==, 0); mutex_enter(&zfsvfs->z_znodes_lock); list_insert_tail(&zfsvfs->z_all_znodes, zp); zfsvfs->z_nr_znodes++; mutex_exit(&zfsvfs->z_znodes_lock); - unlock_new_inode(ip); + if (links > 0) + unlock_new_inode(ip); return (zp); error: >From afa7b3484556d3ae610a34582ce5ebd2c3e27bba Mon Sep 17 00:00:00 2001 From: Paul Zuchowski <31706010+paulz...@users.noreply.github.com> Date: Fri, 11 Jun 2021 20:00:33 -0400 Subject: [PATCH] Do not hash unlinked inodes In zfs_znode_alloc we always hash inodes. If the znode is unlinked, we do not need to hash it. This fixes the problem where zfs_suspend_fs is doing zrele (iput) in an async fashion, and zfs_resume_fs unlinked drain processing wi
Bug#999620: pktanon: autopkgtest regression on armhf
Hi Sascha, On 14-11-2021 11:03, Sascha Steinbiss wrote: I am puzzled. The recent upload only changed the watchfile and updated Standards-Version, compat level etc -- packaging things. Nothing touched the code or build rules. Well, but maybe your build dependencies have. Also, compat level isn't totally safe either in general (although the issue here doesn't obviously look like it). Also, I can't reproduce the bus error when running the offending command from the autopkgtest on a version I built on a porterbox: (sid_armhf-dchroot)satta@abel:~/pktanon-2~git20160407.0.2bde4f2+dfsg$ ../usr/bin/pktanon -c ../usr/share/doc/pktanon/examples/profiles/profile.xml profiles/sample.pcap ./out.pcap --- pktanon --- profile-based traffic anonymization --- initializing PktAnon, configuration = ../usr/share/doc/pktanon/examples/profiles/profile.xml unknown element: pktanon-config: 37 unknown element: anonymizations: 102 istream: opened file profiles/sample.pcap ostream: opened output file ./out.pcap initialized complete statistics for input file 'profiles/sample.pcap' processed packets: 9 errors in packets: 0 elapsed time: 639us Mpps: 0.0141 Our armhf host is very powerful, it has 160 cores and 255GB RAM. Maybe that makes it enough different from the porter box. (Albeit our other extreme host (ci-worker13; amd64) process the package fine, but that has *only* 48 cores and 256GB. I must admit that being unfamiliar with these architectures and not really having an idea of where to start, I am tempted to just remove armhf from the list of supported architectures and have the version with the broken autopkgtest removed from unstable. Do you probably know someone who might be more knowledgeable with such architecture-specific issues? We have porters for architecture specific support. However, I'm not totally convinced yet it's architecture specific. Is there anything I can try out for you on our armhf host to help debug the issue? Run the command with more debug options? Grab an output file from somewhere? I could try to run the test in testing with a rebuild of the package in testing, would that help? Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#995014: marked as done (linux/linux-signe-* break zfs-linux autopkgtest: None of the expected "capability" interfaces were detected)
Your message dated Tue, 16 Nov 2021 18:36:24 + with message-id and subject line Bug#995014: fixed in zfs-linux 2.0.6-2 has caused the Debian Bug report #995014, regarding linux/linux-signe-* break zfs-linux autopkgtest: None of the expected "capability" interfaces were detected 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.) -- 995014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995014 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: linux, zfs-linux Control: found -1 linux/5.14.6-2 Control: found -1 zfs-linux/2.0.3-9 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of linux ans linux-signed-* the autopkgtest of zfs-linux fails in testing when that autopkgtest is run with the binary packages of linux or the singed variants from unstable. It passes when run with only packages from testing. In tabular form: passfail linux from testing5.14.6-2 zfs-linux from testing2.0.3-9 all others from testingfrom testing I copied some of the output at the bottom of this report. I'm *suspecting* that the zfs-linux autopkgtest fails because the linux header are not in sync with the running kernel, but I'm by far not sure. Currently this regression is blocking the migration of linux and it's signed versions 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=linux https://ci.debian.net/data/autopkgtest/testing/amd64/z/zfs-linux/15487822/log.gz checking whether inode_owner_or_capable() exists... configure: error: *** None of the expected "capability" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.0.3-9 *** Compatible Kernels: 3.10 - 5.10 make: *** [debian/rules:230: override_dh_configure_modules_udeb_stamp] Error 1 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: zfs-linux Source-Version: 2.0.6-2 Done: Aron Xu We believe that the bug you reported is fixed in the latest version of zfs-linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aron Xu (supplier of updated zfs-linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 17 Nov 2021 01:55:16 +0800 Source: zfs-linux Architecture: source Version: 2.0.6-2 Distribution: unstable Urgency: medium Maintainer: Debian ZFS on Linux maintainers Changed-By: Aron Xu Closes: 995014 999663 Changes: zfs-linux (2.0.6-2) unstable; urgency=medium . * Add PPC get_user workaround from Ubuntu (Closes: #995014) * Fix FTBFS because of abigail upgrade (Closes: #999663) Checksums-Sha1: f2329851e02dff1ca18956cfa2606c04db3c86c5 3233 zfs-linux_2.0.6-2.dsc 292416043ac68e55d059b2478ba7ebf2904c0941 13192941 zfs-linux_2.0.6.orig.tar.gz de3889df02a64f7828143ed66c8d36e6a5739c8d 88940 zfs-linux_2.0.6-2.debian.tar.xz 9e485531f2724d27569f32b7b1031258e16eaa37 7106 zfs-linux_2.0.6-2_source.buildinfo Checksums-Sha256: f3dfd76e931f334dd7fffc99e2b8a698f21fd628579d52124de04955f426858b 3233 zfs-linux_2.0.6-2.dsc 44b22166b103022e3ca67cb713abdc991e274ed141b6a30568a1bd5c80b2aa95 13192941 zfs-linux_2.0.6.orig.tar.gz dc49d261900323f5bc8f03df95a1e3a87617b3b59ac87a70a152c4bd7898220b 88940 zfs-linux_2.0.6-2.debian.tar.xz 973494b599be5a164c34d77fd464fcaa50cc1b4f8e8d6b26a55033ba297fe240 7106 zfs-linux_2.0.6-2_source.buildinfo Files: b84e2469dd23eacabd044f8e7460cf29 3233 contri
Bug#999663: marked as done (zfs-linux: FTBFS with libabigail 2.0)
Your message dated Tue, 16 Nov 2021 18:36:24 +
with message-id
and subject line Bug#999663: fixed in zfs-linux 2.0.6-2
has caused the Debian Bug report #999663,
regarding zfs-linux: FTBFS with libabigail 2.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
999663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zfs-linux
Version: 2.0.6-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
zfs-linux recently started to FTBFS, I suspect this to be caused by the
upgrade of libabigail to 2.0:
debian/rules override_dh_auto_test
make[1]: Entering directory '/build/zfs-linux-2.0.6'
# Upstream provides an ABI guarantee that we validate here
/usr/bin/make checkabi
make[2]: Entering directory '/build/zfs-linux-2.0.6'
/usr/bin/make -C lib checkabi
make[3]: Entering directory '/build/zfs-linux-2.0.6/lib'
set -e ; for dir in libnvpair libuutil libzfs_core libzfs libzfsbootenv ; do \
/usr/bin/make -C $dir checkabi ; \
done
make[4]: Entering directory '/build/zfs-linux-2.0.6/lib/libnvpair'
for lib in libnvpair.la ; do \
abidiff --no-unreferenced-symbols \
--headers-dir1 ../../include \
--suppressions ${lib%.la}.suppr \
${lib%.la}.abi .libs/${lib%.la}.so ; \
done
abidiff: incompatible format version between the two input files:
'libnvpair.abi'
and
'.libs/libnvpair.so'
make[4]: *** [Makefile:1089: checkabi] Error 1
make[4]: Leaving directory '/build/zfs-linux-2.0.6/lib/libnvpair'
make[3]: *** [Makefile:964: checkabi] Error 2
make[3]: Leaving directory '/build/zfs-linux-2.0.6/lib'
make[2]: *** [Makefile:1502: checkabi] Error 2
make[2]: Leaving directory '/build/zfs-linux-2.0.6'
make[1]: *** [debian/rules:83: override_dh_auto_test] Error 2
make[1]: Leaving directory '/build/zfs-linux-2.0.6'
make: *** [debian/rules:34: binary] Error 2
Andreas
zfs-linux_2.0.6-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: zfs-linux
Source-Version: 2.0.6-2
Done: Aron Xu
We believe that the bug you reported is fixed in the latest version of
zfs-linux, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Aron Xu (supplier of updated zfs-linux package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 17 Nov 2021 01:55:16 +0800
Source: zfs-linux
Architecture: source
Version: 2.0.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian ZFS on Linux maintainers
Changed-By: Aron Xu
Closes: 995014 999663
Changes:
zfs-linux (2.0.6-2) unstable; urgency=medium
.
* Add PPC get_user workaround from Ubuntu (Closes: #995014)
* Fix FTBFS because of abigail upgrade (Closes: #999663)
Checksums-Sha1:
f2329851e02dff1ca18956cfa2606c04db3c86c5 3233 zfs-linux_2.0.6-2.dsc
292416043ac68e55d059b2478ba7ebf2904c0941 13192941 zfs-linux_2.0.6.orig.tar.gz
de3889df02a64f7828143ed66c8d36e6a5739c8d 88940 zfs-linux_2.0.6-2.debian.tar.xz
9e485531f2724d27569f32b7b1031258e16eaa37 7106
zfs-linux_2.0.6-2_source.buildinfo
Checksums-Sha256:
f3dfd76e931f334dd7fffc99e2b8a698f21fd628579d52124de04955f426858b 3233
zfs-linux_2.0.6-2.dsc
44b22166b103022e3ca67cb713abdc991e274ed141b6a30568a1bd5c80b2aa95 13192941
zfs-linux_2.0.6.orig.tar.gz
dc49d261900323f5bc8f03df95a1e3a87617b3b59ac87a70a152c4bd7898220b 88940
zfs-linux_2.0.6-2.debian.tar.xz
973494b599be5a164c34d77fd464fcaa50cc1b4f8e8d6b26a55033ba297fe240 7106
zfs-linux_2.0.6-2_source.buildinfo
Files:
b84e2469dd23eacabd044f8e7460cf29 3233 contrib/kernel optional
zfs-linux_2.0.6-2.dsc
c2b8640cb7aff6298fa4ac6d205e71dd 13192941 contrib/kernel optional
zfs-linux_2.0.6.orig.tar.gz
bc852d119a06a2c7a686c85057f8ed07 88940 contrib/kernel optional
zfs-linux_2.0.6-2.debian.tar.xz
41a0a2e2ca7d194289759dfb0532c471 7106 contrib/kernel optional
zfs-linux_2.0.6-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE+ecpf0kXAAxPjLtll/gMr2GMl1wFAmGT9NEACgkQl/gMr2GM
l1za+wf+Jtw9Brfk9g/9ZeqXMpCIDpp0RK/pjSOHnxEQGgz6n/5zaZC0qdrV
Bug#997517: marked as done (ignition-fuel-tools: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=--verbose ARGS\+=-j4 returned exit code 2)
Your message dated Tue, 16 Nov 2021 19:18:56 + with message-id and subject line Bug#997517: fixed in ignition-fuel-tools 4.1.0+dfsg-6 has caused the Debian Bug report #997517, regarding ignition-fuel-tools: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=--verbose ARGS\+=-j4 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 997517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997517 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ignition-fuel-tools Version: 4.1.0+dfsg-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>/obj-x86_64-linux-gnu' > Running tests... > /usr/bin/ctest --force-new-ctest-process --verbose -j4 > UpdateCTestConfiguration from > :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > Parse Config file:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > UpdateCTestConfiguration from > :/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > Parse Config file:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl > Test project /<>/obj-x86_64-linux-gnu > Constructing a list of tests > Done constructing a list of tests > Updating test list for fixtures > Added 0 tests to meet fixture requirements > Checking test dependency graph... > Checking test dependency graph end > test 1 > Start 1: UNIT_ClientConfig_TEST > > 1: Test command: > /<>/obj-x86_64-linux-gnu/bin/UNIT_ClientConfig_TEST > "--gtest_output=xml:/<>/obj-x86_64-linux-gnu/test_results/UNIT_ClientConfig_TEST.xml" > 1: Test timeout computed to be: 1500 > test 2 > Start 2: UNIT_JSONParser_TEST > > 2: Test command: > /<>/obj-x86_64-linux-gnu/bin/UNIT_JSONParser_TEST > "--gtest_output=xml:/<>/obj-x86_64-linux-gnu/test_results/UNIT_JSONParser_TEST.xml" > 2: Test timeout computed to be: 1500 > test 3 > Start 3: UNIT_LocalCache_TEST > > 3: Test command: > /<>/obj-x86_64-linux-gnu/bin/UNIT_LocalCache_TEST > "--gtest_output=xml:/<>/obj-x86_64-linux-gnu/test_results/UNIT_LocalCache_TEST.xml" > 3: Test timeout computed to be: 1500 > test 4 > Start 4: UNIT_ModelIdentifier_TEST > > 4: Test command: > /<>/obj-x86_64-linux-gnu/bin/UNIT_ModelIdentifier_TEST > "--gtest_output=xml:/<>/obj-x86_64-linux-gnu/test_results/UNIT_ModelIdentifier_TEST.xml" > 4: Test timeout computed to be: 1500 > 1: [==] Running 14 tests from 2 test suites. > 1: [--] Global test environment set-up. > 1: [--] 12 tests from ClientConfig > 1: [ RUN ] ClientConfig.InitiallyDefaultServers > 1: [ OK ] ClientConfig.InitiallyDefaultServers (0 ms) > 1: [ RUN ] ClientConfig.ServersCanBeAdded > 1: [ OK ] ClientConfig.ServersCanBeAdded (0 ms) > 1: [ RUN ] ClientConfig.CustomDefaultConfiguration > 1: [ OK ] ClientConfig.CustomDefaultConfiguration (0 ms) > 1: [ RUN ] ClientConfig.CustomConfiguration > 2: [==] Running 6 tests from 1 test suite. > 2: [--] Global test environment set-up. > 2: [--] 6 tests from JSONParser > 2: [ RUN ] JSONParser.ParseModels > 3: [==] Running 6 tests from 1 test suite. > 3: [--] Global test environment set-up. > 3: [--] 6 tests from LocalCache > 3: [ RUN ] LocalCache.AllModels > 1: [ OK ] ClientConfig.CustomConfiguration (0 ms) > 1: [ RUN ] ClientConfig.RepeatedServerConfiguration > 2: [ OK ] JSONParser.ParseModels (0 ms) > 2: [ RUN ] JSONParser.BuildModel > 2: [ OK ] JSONParser.BuildModel (0 ms) > 2: [ RUN ] JSONParser.ParseModel > 2: [ OK ] JSONParser.ParseModel (0 ms) > 2: [ RUN ] JSONParser.ParseWorlds > 2: [ OK ] JSONParser.ParseWorlds (0 ms) > 2: [ RUN ] JSONParser.BuildWorld > 2: [ OK ] JSONParser.BuildWorld (0 ms) > 2: [ RUN ] JSONParser.ParseWorld > 1: [ OK ] ClientConfig.RepeatedServerConfiguration (0 ms) > 1: [ RUN ] ClientConfig.NoServerUrlConfiguration > 1: [1;31m[Err] [ClientConfig.cc:348] [0m[1;31m[url] parameter is required > for a server[0m[1;31m[0m > 1: [ OK ] ClientConfig.NoServerUrlConfiguration (0 ms) > 1: [ RUN ] ClientConfig.EmptyServerUrlConfiguration > 1: [1;31m[Err] [ClientConfig.cc:348] [0m[1;31m[url] parameter is required > for a server[0m[1;31m[0m > 1: [ OK ] ClientConfig.EmptyServerUrlConfiguration (0 ms) > 1: [ RUN ] ClientConfig.NoCachePathConfiguration > 2: [ OK ]
Bug#998576: marked as pending in squeekboard
Control: tag -1 pending Hello, Bug #998576 in squeekboard reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/DebianOnMobile-team/squeekboard/-/commit/6f7fa64c07f4b6ebd22deaf311e54b98d901a9ee d/patches: add fix_meson_ftbfs (Closes: #998576) (this message was generated automatically) -- Greetings https://bugs.debian.org/998576
Processed: Bug#998576 marked as pending in squeekboard
Processing control commands: > tag -1 pending Bug #998576 [src:squeekboard] squeekboard: FTBFS: msgfmt: ../data/../po/LINGUAS does not exist Added tag(s) pending. -- 998576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998576 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998576: marked as done (squeekboard: FTBFS: msgfmt: ../data/../po/LINGUAS does not exist)
Your message dated Tue, 16 Nov 2021 19:49:38 + with message-id and subject line Bug#998576: fixed in squeekboard 1.14.0-3 has caused the Debian Bug report #998576, regarding squeekboard: FTBFS: msgfmt: ../data/../po/LINGUAS does not exist 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.) -- 998576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998576 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: squeekboard Version: 1.14.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > rm Cargo.lock > dh build-arch --builddirectory=_build --buildsystem=meson >dh_update_autotools_config -a -O--builddirectory=_build > -O--buildsystem=meson >dh_auto_configure -a -O--builddirectory=_build -O--buildsystem=meson > cd _build && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload > --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var > --libdir=lib/x86_64-linux-gnu > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/_build > Build type: native build > Project name: squeekboard > Project version: 1.14.0 > C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-10) > 11.2.0") > C linker for the host machine: cc ld.bfd 2.37 > Rust compiler for the host machine: rustc -C linker=cc (rustc 1.56.0) > Rust linker for the host machine: rustc -C linker=cc ld.bfd 2.37 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > ../meson.build:50: WARNING: Consider using the built-in werror option instead > of using "-Werror". > Message: > -- > squeekboard 1.14.0 > > -- > > Configuring Cargo.toml.base using configuration > Program cat found: YES (/bin/cat) > Program cargo found: YES (/usr/bin/cargo) > Program cargo.sh found: YES (/<>/cargo.sh) > Program cargo_build.py found: YES (/usr/bin/python3 > /<>/cargo_build.py) > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources) > Configuring sm.puri.Squeekboard.desktop.in using configuration > DEPRECATION: i18n.merge_file does not take any positional arguments. This > will become a hard error in the next Meson release. > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Run-time dependency wayland-protocols found: YES 1.23 > Program wayland-scanner found: YES (/usr/bin/wayland-scanner) > Program gdbus-codegen found: YES (/usr/bin/gdbus-codegen) > Configuring config.h using configuration > ../src/meson.build:7: WARNING: Got an empty configuration_data() object and > found no substitutions in the input file 'config.h.in'. If you want to copy a > file to the build dir, use the 'copy:' keyword argument added in 0.47.0 > Run-time dependency gio-2.0 found: YES 2.70.0 > Run-time dependency gio-unix-2.0 found: YES 2.70.0 > Run-time dependency gnome-desktop-3.0 found: YES 41.0 > Run-time dependency gtk+-3.0 found: YES 3.24.30 > Run-time dependency libfeedback-0.0 found: YES 0.0.0 > Run-time dependency wayland-client found: YES 1.19.0 > Run-time dependency xkbcommon found: YES 1.3.1 > Library m found: YES > Library rt found: YES > Library dl found: YES > Library pthread found: YES > Build targets in project: 11 > > squeekboard 1.14.0 > > User defined options > buildtype: plain > libdir : lib/x86_64-linux-gnu > localstatedir: /var > prefix : /usr > sysconfdir : /etc > wrap_mode: nodownload > > Found ninja-1.10.1 at /usr/bin/ninja >dh_auto_build -a -O--builddirectory=_build -O--buildsystem=meson > cd _build && LC_ALL=C.UTF-8 ninja -j4 -v > [1/58] /usr/bin/glib-compile-resources ../data/squeekboard.gresources.xml > --sourcedir ../data --c-name squeekboard --internal --generate --target > data/squeekboard-resources.h > xml-stripblanks preprocessing requested, but XMLLINT is not set, and xmllint > is not in PATH > [2/58] /usr/bin/glib-compile-resources ../data/squeekboard.gresources.xml > --sourcedir ../data --c-name squeekboard --internal --generate --target > data/squeekboard-resources.c --dependency-file data/squeekboard-resources.c.d > xml-stripblanks preprocessing requested, but XMLLINT is not set, and xmllint > is not in PATH > [3/58] /usr/bin/gdbus-codegen --c-generate-autocleanup all --body --output > src/sm.puri.OSK0.c /<>/data/dbus/sm.puri.OSK0.xml > [4/58] /usr/bin/gdbus-codegen --c-generate-a
Bug#999798: golang-github-alecthomas-chroma breaks golang-github-charmbracelet-glamour autopkgtest
Source: golang-github-alecthomas-chroma, golang-github-charmbracelet-glamour Control: found -1 golang-github-alecthomas-chroma/0.9.4-1 Control: found -1 golang-github-charmbracelet-glamour/0.3.0-2 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of golang-github-alecthomas-chroma the autopkgtest of golang-github-charmbracelet-glamour fails in testing when that autopkgtest is run with the binary packages of golang-github-alecthomas-chroma from unstable. It passes when run with only packages from testing. In tabular form: passfail golang-github-alecthomas-chroma from testing0.9.4-1 golang-github-charmbracelet-glamour from testing0.3.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 golang-github-alecthomas-chroma 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=golang-github-alecthomas-chroma https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-charmbracelet-glamour/16697724/log.gz --- FAIL: TestRenderHelpers (0.01s) FAIL FAILgithub.com/charmbracelet/glamour0.055s === RUN TestRenderer --- PASS: TestRenderer (0.02s) === RUN TestRendererIssues --- PASS: TestRendererIssues (0.02s) PASS ok github.com/charmbracelet/glamour/ansi 0.045s ? github.com/charmbracelet/glamour/examples/custom_renderer [no test files] ? github.com/charmbracelet/glamour/examples/helloworld[no test files] ? github.com/charmbracelet/glamour/internal/generate-style-json [no test files] FAIL dh_auto_test: error: cd _build && go test -vet=off -v -p 2 github.com/charmbracelet/glamour github.com/charmbracelet/glamour/ansi github.com/charmbracelet/glamour/examples/custom_renderer github.com/charmbracelet/glamour/examples/helloworld github.com/charmbracelet/glamour/internal/generate-style-json returned exit code 1 make: *** [debian/rules:6: build] Error 25 autopkgtest [16:15:07]: test dh-golang-autopkgtest OpenPGP_signature Description: OpenPGP digital signature
Processed: golang-github-alecthomas-chroma breaks golang-github-charmbracelet-glamour autopkgtest
Processing control commands: > found -1 golang-github-alecthomas-chroma/0.9.4-1 Bug #999798 [src:golang-github-alecthomas-chroma, src:golang-github-charmbracelet-glamour] golang-github-alecthomas-chroma breaks golang-github-charmbracelet-glamour autopkgtest Marked as found in versions golang-github-alecthomas-chroma/0.9.4-1. > found -1 golang-github-charmbracelet-glamour/0.3.0-2 Bug #999798 [src:golang-github-alecthomas-chroma, src:golang-github-charmbracelet-glamour] golang-github-alecthomas-chroma breaks golang-github-charmbracelet-glamour autopkgtest Marked as found in versions golang-github-charmbracelet-glamour/0.3.0-2. -- 999798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999799: cffi breaks cl-plus-ssl autopkgtest on armhf and i386: OMPILE-FILE-ERROR while compiling #
Source: cffi, cl-plus-ssl
Control: found -1 cffi/1:0.24.1-1
Control: found -1 cl-plus-ssl/20200609.gitff4634a-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of cffi the autopkgtest of cl-plus-ssl fails in
testing when that autopkgtest is run with the binary packages of cffi
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
cffi from testing1:0.24.1-1
cl-plus-sslfrom testing20200609.gitff4634a-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 cffi 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=cffi
https://ci.debian.net/data/autopkgtest/testing/armhf/c/cl-plus-ssl/16722626/log.gz
; file: /usr/share/common-lisp/source/cl-cffi/src/types.lisp
; in: DEFCTYPE :SIZE
; (CFFI:DEFCTYPE :SIZE)
; ; caught ERROR:
; (during macroexpansion of (DEFCTYPE :SIZE))
; Error while parsing arguments to DEFMACRO DEFCTYPE:
; too few elements in
; (:SIZE)
; to satisfy lambda list
; (NAME BASE-TYPE &OPTIONAL DOCUMENTATION):
; between 2 and 3 expected, but got 1
; processing (ERROR (QUOTE SB-INT:COMPILED-PROGRAM-ERROR) ...)
; processing (DEFCTYPE :SSIZE)
; file: /usr/share/common-lisp/source/cl-cffi/src/types.lisp
; in: DEFCTYPE :SSIZE
; (CFFI:DEFCTYPE :SSIZE)
; ; caught ERROR:
; (during macroexpansion of (DEFCTYPE :SSIZE))
; Error while parsing arguments to DEFMACRO DEFCTYPE:
; too few elements in
; (:SSIZE)
; to satisfy lambda list
; (NAME BASE-TYPE &OPTIONAL DOCUMENTATION):
; between 2 and 3 expected, but got 1
; processing (ERROR (QUOTE SB-INT:COMPILED-PROGRAM-ERROR) ...)
; processing (DEFCTYPE :PTRDIFF ...)
; file: /usr/share/common-lisp/source/cl-cffi/src/types.lisp
; in: DEFCTYPE :PTRDIFF
; (CFFI:DEFCTYPE :PTRDIFF :SSIZE)
; ; caught ERROR:
; (during macroexpansion of (DEFCTYPE :PTRDIFF ...))
; Unknown CFFI type :SSIZE
; processing (ERROR (QUOTE SB-INT:COMPILED-PROGRAM-ERROR) ...)
; processing (DEFCTYPE :OFFSET ...)
; wrote
/tmp/autopkgtest-lxc.w4ep9ku_/downtmp/autopkgtest_tmp/usr/share/common-lisp/source/cl-cffi/src/types-tmpBODYQO2B.fasl
; compilation finished in 0:00:00.460
Unhandled UIOP/LISP-BUILD:COMPILE-FILE-ERROR:
COMPILE-FILE-ERROR while compiling #
Backtrace for: #
0: (SB-DEBUG::DEBUGGER-DISABLED-HOOK
# # :QUIT T)
1: (SB-DEBUG::RUN-HOOK *INVOKE-DEBUGGER-HOOK*
#)
2: (INVOKE-DEBUGGER #)
3: (ERROR UIOP/LISP-BUILD:COMPILE-FILE-ERROR :CONTEXT-FORMAT
"~/asdf-action::format-action/" :CONTEXT-ARGUMENTS
((# . #"cffi" "src" "types">)))
4: (UIOP/LISP-BUILD:CHECK-LISP-COMPILE-RESULTS NIL T T
"~/asdf-action::format-action/" ((# .
#)))
5: ((SB-PCL::EMF ASDF/ACTION:PERFORM) # #argument> #
#)
6: ((LAMBDA NIL :IN ASDF/ACTION:CALL-WHILE-VISITING-ACTION))
7: ((:METHOD ASDF/ACTION:PERFORM :AROUND (ASDF/LISP-ACTION:COMPILE-OP
ASDF/LISP-ACTION:CL-SOURCE-FILE)) #
#) [fast-method]
8: ((:METHOD ASDF/ACTION:PERFORM-WITH-RESTARTS :AROUND (T T))
# #"src" "types">) [fast-method]
9: ((:METHOD ASDF/PLAN:PERFORM-PLAN (T)) #{4FD098D9}>) [fast-method]
10: ((FLET SB-C::WITH-IT :IN SB-C::%WITH-COMPILATION-UNIT))
11: ((:METHOD ASDF/PLAN:PERFORM-PLAN :AROUND (T))
#) [fast-method]
12: ((:METHOD ASDF/OPERATE:OPERATE (ASDF/OPERATION:OPERATION
ASDF/COMPONENT:COMPONENT)) #
# :PLAN-CLASS NIL :PLAN-OPTIONS NIL)
[fast-method]
13: ((SB-PCL::EMF ASDF/OPERATE:OPERATE) # #argument> # #)
14: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE))
15: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T))
# #)
[fast-method]
16: ((SB-PCL::EMF ASDF/OPERATE:OPERATE) # #argument> ASDF/LISP-ACTION:LOAD-OP "cl+ssl.test")
17: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE))
18: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T))
ASDF/LISP-ACTION:LOAD-OP "cl+ssl.test") [fast-method]
19: (ASDF/SESSION:CALL-WITH-ASDF-SESSION #ASDF/OPERATE:OPERATE) {4FD09775}> :OVERRIDE T :KEY NIL :OVERRIDE-CACHE T
:OVERRIDE-FORCING NIL)
20: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE))
21: (ASDF/SESSION:CALL-WITH-ASDF-SESSION #ASDF/OPERATE:OPERATE) {4FD09685}> :OVERRIDE NIL :KEY NIL :OVERRIDE-CACHE
NIL :OVERRIDE-FORCING NIL)
22: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T))
ASDF/LISP-ACTION:LOAD-OP "cl+ssl.test") [fast-method]
23: (ASDF/OPERATE:LOAD-SYSTEM "cl+ssl.test")
24: ((LAMBDA NIL :IN
"/tmp/autopkgtest-lxc.w4ep9ku_/downtmp/build.73k/src/debian/tests/runtests.lisp"))
25: (SB-INT:SIMPLE-EVAL-IN-LEXENV (LET ((UIOP/CONFIGU
Processed: cffi breaks cl-plus-ssl autopkgtest on armhf and i386: OMPILE-FILE-ERROR while compiling #
Processing control commands: > found -1 cffi/1:0.24.1-1 Bug #999799 [src:cffi, src:cl-plus-ssl] cffi breaks cl-plus-ssl autopkgtest on armhf and i386: OMPILE-FILE-ERROR while compiling # Marked as found in versions cffi/1:0.24.1-1. > found -1 cl-plus-ssl/20200609.gitff4634a-1 Bug #999799 [src:cffi, src:cl-plus-ssl] cffi breaks cl-plus-ssl autopkgtest on armhf and i386: OMPILE-FILE-ERROR while compiling # Marked as found in versions cl-plus-ssl/20200609.gitff4634a-1. -- 999799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999800: node-flatted: autopkgtest regression: Cannot find module '/tmp/autopkgtest-lxc.78cintn5/downtmp/build.nuC/src/cjs/index.js'
Source: node-flatted
Version: 3.2.2~ds-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of node-flatted the autopkgtest of node-flatted
fails in testing when that autopkgtest is run with the binary packages
of node-flatted from unstable. It passes when run with only packages
from testing. In tabular form:
passfail
node-flatted from testing3.2.2~ds-2
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=node-flatted
https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-flatted/16718609/log.gz
internal/modules/cjs/loader.js:406
throw e;
^
Error: Cannot find module
'/tmp/autopkgtest-lxc.78cintn5/downtmp/build.nuC/src/cjs/index.js'
at createEsmNotFoundErr (internal/modules/cjs/loader.js:842:15)
at finalizeEsmResolution (internal/modules/cjs/loader.js:835:15)
at trySelf (internal/modules/cjs/loader.js:400:12)
at Function.Module._resolveFilename
(internal/modules/cjs/loader.js:793:24)
at Function.Module._load (internal/modules/cjs/loader.js:667:27)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at [eval]:1:1
at Script.runInThisContext (vm.js:120:18)
at Object.runInThisContext (vm.js:309:38) {
code: 'MODULE_NOT_FOUND',
path: '/tmp/autopkgtest-lxc.78cintn5/downtmp/build.nuC/src/package.json'
}
autopkgtest [11:11:00]: test command1
OpenPGP_signature
Description: OpenPGP digital signature
Bug#997333: wifite: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: 'pyrit'
I did some investigation here and I believe this can be addressed by removing pyrit support from wifite. It should still work with tshark instead, as per the manpage. Cheers, -- Samuel Henrique
Processed: tagging 940275, tagging 997373, tagging 997064, tagging 984325, tagging 997381, tagging 996366 ...
Processing commands for cont...@bugs.debian.org:
> tags 940275 + experimental
Bug #940275 [php-cache-lite] FTBFS with recent PHPUnit (8)
Added tag(s) experimental.
> tags 997373 + experimental
Bug #997373 [src:praw] praw: FTBFS: AttributeError: 'Sphinx' object has no
attribute 'add_stylesheet'
Added tag(s) experimental.
> tags 997064 + experimental
Bug #997064 [src:emscripten] emscripten: FTBFS: BlockingIOError: [Errno 11]
write could not complete without blocking
Added tag(s) experimental.
> tags 984325 + experimental
Bug #984325 {Done: Laszlo Boszormenyi (GCS) } [src:rocksdb]
rocksdb: ftbfs with GCC-11
Added tag(s) experimental.
> tags 997381 + experimental
Bug #997381 [src:python-pgpy] python-pgpy: FTBFS: AttributeError: 'Sphinx'
object has no attribute 'add_stylesheet'
Added tag(s) experimental.
> tags 996366 + experimental
Bug #996366 [src:ruby-regexp-parser] ruby-regexp-parser: FTBFS with ruby3.0:
ERROR: Test "ruby3.0" failed: Failure/Error: (min..max).tap { |r|
r.define_singleton_method(:minmax) { [min, max] } }
Added tag(s) experimental.
> tags 984233 + experimental
Bug #984233 {Done: Alastair McKinstry } [src:mia] mia:
ftbfs with GCC-11
Added tag(s) experimental.
> tags 984267 + experimental
Bug #984267 [src:omniorb-dfsg] omnievents: ftbfs with GCC-11
Bug #984269 [src:omniorb-dfsg] omniorb-dfsg: ftbfs with GCC-11
Bug #984360 [src:omniorb-dfsg] tango: ftbfs with GCC-11
Added tag(s) experimental.
Added tag(s) experimental.
Added tag(s) experimental.
> tags 996108 + experimental
Bug #996108 [php-doctrine-bundle] Useless in Debian
Added tag(s) experimental.
> tags 984272 + experimental
Bug #984272 [src:open-vm-tools] open-vm-tools: ftbfs with GCC-11
Added tag(s) experimental.
> tags 997544 + experimental
Bug #997544 [src:git-lfs] git-lfs: FTBFS: dh_auto_test: error: cd
obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/git-lfs/git-lfs ...
returned exit code 1
Added tag(s) experimental.
> tags 997562 + experimental
Bug #997562 [src:golang-github-google-wire] golang-github-google-wire: FTBFS:
dh_auto_test: error: cd _build && go test -vet=off -v -p 4
github.com/google/wire github.com/google/wire/cmd/wire
github.com/google/wire/internal/wire returned exit code 1
Added tag(s) experimental.
> tags 997569 + experimental
Bug #997569 [src:golang-github-magiconair-properties]
golang-github-magiconair-properties: FTBFS: dh_auto_test: error: cd
obj-x86_64-linux-gnu && go test -vet=off -v -p 4
github.com/magiconair/properties github.com/magiconair/properties/assert
returned exit code 1
Added tag(s) experimental.
> tags 997780 + experimental
Bug #997780 {Done: David Prévot } [src:php-mockery]
php-mockery: FTBFS: There is a syntax error in your configuration file: invalid
syntax (conf.py, line 259)
Added tag(s) experimental.
> tags 984242 + experimental
Bug #984242 [src:mpich] mpich: ftbfs with GCC-11
Added tag(s) experimental.
> tags 941264 + experimental
Bug #941264 [php-cache-lite] phpunit breaks php-cache-lite autopkgtest: tries
to write to /usr/bin/.phpunit.result.cache
Added tag(s) experimental.
> tags 998140 - bookworm sid
Bug #998140 {Done: Timo Röhling } [src:opencv] opencv: ABI
breakage causes autopkgtest failures
Bug #998141 {Done: Timo Röhling } [src:opencv] opencv: ABI
breakage causes autopkgtest failures
Bug #998142 {Done: Timo Röhling } [src:opencv] opencv: ABI
breakage causes autopkgtest failures
Removed tag(s) bookworm and sid.
Removed tag(s) bookworm and sid.
Removed tag(s) sid and bookworm.
> found 998140 4.5.4+dfsg-1
Bug #998140 {Done: Timo Röhling } [src:opencv] opencv: ABI
breakage causes autopkgtest failures
Bug #998141 {Done: Timo Röhling } [src:opencv] opencv: ABI
breakage causes autopkgtest failures
Bug #998142 {Done: Timo Röhling } [src:opencv] opencv: ABI
breakage causes autopkgtest failures
Marked as found in versions opencv/4.5.4+dfsg-1.
Marked as found in versions opencv/4.5.4+dfsg-1.
Marked as found in versions opencv/4.5.4+dfsg-1.
> tags 997101 + experimental
Bug #997101 {Done: Joao Eriberto Mota Filho }
[src:gimp-texturize] gimp-texturize: FTBFS: type_traits:44:3: error: template
with C linkage
Added tag(s) experimental.
> tags 999721 + experimental
Bug #999721 [src:ruby-omniauth-openid-connect] ruby-omniauth-openid-connect:
FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed:
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in
activate_dependencies': Could not find 'omniauth' (~> 1.9) among 106 total
gem(s) (Gem::MissingSpecError)
Added tag(s) experimental.
> tags 996377 - sid bookworm
Bug #996377 [ruby-activesupport] ruby-rspec-rails: FTBFS with ruby3.0: ERROR:
Test "ruby3.0" failed: ArgumentError:
Removed tag(s) sid and bookworm.
> tags 996342 + experimental
Bug #996342 [src:ruby-omniauth-openid-connect] ruby-omniauth-openid-connect:
FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number
of arguments (given 2, expected 0..1)
Added tag(s) experimental.
> tags 998532 + ex
Bug#999800: [Pkg-javascript-devel] Bug#999800: node-flatted: autopkgtest regression: Cannot find module '/tmp/autopkgtest-lxc.78cintn5/downtmp/build.nuC/src/cjs/index.js'
Quoting Paul Gevers (2021-11-16 21:11:39)
> Source: node-flatted
> Version: 3.2.2~ds-2
> X-Debbugs-CC: debian...@lists.debian.org
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: regression
>
> Dear maintainer(s),
>
> With a recent upload of node-flatted the autopkgtest of node-flatted
> fails in testing when that autopkgtest is run with the binary packages
> of node-flatted from unstable. It passes when run with only packages
> from testing. In tabular form:
>
> passfail
> node-flatted from testing3.2.2~ds-2
> all others from testingfrom testing
>
> I copied some of the output at the bottom of this report.
>
> Currently this regression is blocking the migration to testing [1]. Can
> you please investigate the situation and fix it?
>
> More information about this bug and the reason for filing it can be found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
>
> Paul
>
> [1] https://qa.debian.org/excuses.php?package=node-flatted
>
> https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-flatted/16718609/log.gz
>
> internal/modules/cjs/loader.js:406
> throw e;
> ^
>
> Error: Cannot find module
> '/tmp/autopkgtest-lxc.78cintn5/downtmp/build.nuC/src/cjs/index.js'
> at createEsmNotFoundErr (internal/modules/cjs/loader.js:842:15)
> at finalizeEsmResolution (internal/modules/cjs/loader.js:835:15)
> at trySelf (internal/modules/cjs/loader.js:400:12)
> at Function.Module._resolveFilename
> (internal/modules/cjs/loader.js:793:24)
> at Function.Module._load (internal/modules/cjs/loader.js:667:27)
> at Module.require (internal/modules/cjs/loader.js:887:19)
> at require (internal/modules/cjs/helpers.js:74:18)
> at [eval]:1:1
> at Script.runInThisContext (vm.js:120:18)
> at Object.runInThisContext (vm.js:309:38) {
>code: 'MODULE_NOT_FOUND',
>path: '/tmp/autopkgtest-lxc.78cintn5/downtmp/build.nuC/src/package.json'
> }
> autopkgtest [11:11:00]: test command1
I don't understand why it fails, and could use some help.
When I log into a clean chroot, install the packages node-flatted and
nodejs, then the test command succeeds - i.e. this prints "0":
> node -e "require('flatted');"; echo $?
But when executed inside the (to me super complex) autopkgtest
framework, that same command apparently fails.
What am I missing?
- 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
Processed: Bug#997566 marked as pending in golang-github-prometheus-exporter-toolkit
Processing control commands: > tag -1 pending Bug #997566 [src:golang-github-prometheus-exporter-toolkit] golang-github-prometheus-exporter-toolkit: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/prometheus/exporter-toolkit/web github.com/prometheus/exporter-toolkit/web/kingpinflag returned exit code 1 Added tag(s) pending. -- 997566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997566 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997566: marked as pending in golang-github-prometheus-exporter-toolkit
Control: tag -1 pending Hello, Bug #997566 in golang-github-prometheus-exporter-toolkit reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/golang-github-prometheus-exporter-toolkit/-/commit/72776a7afd1ff89d24010cc6759bc63b07fb Fix test failures with new golang 1.17 Closes: #997566 (this message was generated automatically) -- Greetings https://bugs.debian.org/997566
Bug#993004: marked as done (yt: tests fail with h5py 3)
Your message dated Tue, 16 Nov 2021 21:49:10 + with message-id and subject line Bug#993004: fixed in yt 4.0.1-1 has caused the Debian Bug report #993004, regarding yt: tests fail with h5py 3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 993004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yt Version: 3.6.1-1 Severity: serious Justification: breaks yt tests fail with h5py 3, due to removal of the values property. if "dataset_units" in h5f: for unit_name in h5f["/dataset_units"]: current_unit = h5f["/dataset_units/%s" % unit_name] > value = current_unit.value E AttributeError: 'Dataset' object has no attribute 'value' yt has addressed it upstream, upgrade to yt 4 should fix it. --- End Message --- --- Begin Message --- Source: yt Source-Version: 4.0.1-1 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of yt, 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 993...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ole Streicher (supplier of updated yt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 Nov 2021 13:09:37 +0100 Source: yt Architecture: source Version: 4.0.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Team Changed-By: Ole Streicher Closes: 993004 Changes: yt (4.0.1-1) unstable; urgency=medium . * New upstream version 4.0.1. Closes: #993004 * Rediff patches * Push Standards-Version to 4.6.0. No changes needed * Add "Rules-Requires-Root: no" to d/control * Update build and test dependencies * Mark build dependencies that are required for testing only * Skip test_load_sample that requires remote data access * Move conftest.py to build dir before test * Update d/copyright * Don't install LICENSE and README files * Ignore potential dh_dwz failures with image_samplers.*.so * Use 32bit uword on i386 / 64bit on x86-64 * Remove *_nose.py and yt/frontends/gdf/tests/test_outputs.py * Explicitly cast np.argsort() result to target data type to fix FTBFS on 32 bit Checksums-Sha1: 5cb240c56c619f86276b39cf34eba30817296bac 2431 yt_4.0.1-1.dsc b0cd34757b8cc2a7e8b5ec1a5fdcd9bea29cd664 12588963 yt_4.0.1.orig.tar.gz 7071ef2b2523d335ba9527f9962971a2501f1073 10500 yt_4.0.1-1.debian.tar.xz Checksums-Sha256: 2a7142c10b2f0ade935c3e3022478afe4532607c87936526b393ee6dbe252982 2431 yt_4.0.1-1.dsc 6219cbf971871320a13679a57722c0363e50db5e6d4d64ea9d197461b2a7f70f 12588963 yt_4.0.1.orig.tar.gz e14bcd8663a70e30c6771b4d51a5b75c86c0ba6b57a6c36de285d28423f37bb2 10500 yt_4.0.1-1.debian.tar.xz Files: c72f3db3384d6ea907b3a8f6441390ac 2431 python optional yt_4.0.1-1.dsc 707ec8b228d465c62b97d86c0f8507b4 12588963 python optional yt_4.0.1.orig.tar.gz ab7d790f3fbe8298e68d2c957bbeeb7c 10500 python optional yt_4.0.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmGUIkQACgkQcRWv0HcQ 3PeKng//fY2nJCzjyDXQLTBRw3TjYaoJuNHvuPCUkW+39hDwRUQve1lKOGpLXC9L RSxKNNsEIROP7HWO8fK5pcmJzg2glX7V63oo6Sp5lVRqR5fvDsLT8MAQ8VMD5vxH lrf5apDaEkUFNgLQoSwBfCSc74/Qy5XybNhgsdJdC03xq1UMBncEOJ/MTF10qstV kfREKFETzHxXvIBjuuOJ0/hyufxGAehc+hUdYsEjWH+csVFNbwvnc5skbTJOb997 sfC1kkagrXnch98gQpE4r4tM/0DTPRKXij1HQ2xfCjWEJUTkBwf8mduqd9rl7hZ4 6Jmbe9RjJ/FlNolSSPqaMhCbu3y+Bzd35FvZRqCXgLSBfmluZI0m8c7hXgVyXqjI ks0eC4RkTufW/+jyyJsPmdtoO485a6oiq9wgGubcKuEOB1Qq5E7aTRBSLdea2teM TQ1Rg2ID4Nb4iBLu3Yqkht76sRbtzztrzRjsXemx6KpYbghbk7nUAZvRDv+CPmbQ XYRBysju33TR1/fYRg2YcHOIfep9UJG5xT2sbSWzbHEPy/Wdc1qHA2LarwOgcZCI I1HdH15rZLVQPW3yBgDQH8vBjRz4xX0d3lmiGVB6+x1+OnFTdnqs5LMvz8MhAlCk LiQs8OY7AzrfuYrSAZmvF4II103vYKhM7vsVaFSsoy/F6IDfInE= =mS7m -END PGP SIGNATURE End Message ---
Bug#997566: marked as done (golang-github-prometheus-exporter-toolkit: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/prometheus/exporter-toolkit/web github
Your message dated Tue, 16 Nov 2021 22:03:33 + with message-id and subject line Bug#997566: fixed in golang-github-prometheus-exporter-toolkit 0.7.0-1 has caused the Debian Bug report #997566, regarding golang-github-prometheus-exporter-toolkit: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/prometheus/exporter-toolkit/web github.com/prometheus/exporter-toolkit/web/kingpinflag returned exit code 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.) -- 997566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997566 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-prometheus-exporter-toolkit Version: 0.5.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package > golang-github-prometheus-exporter-toolkit > dpkg-buildpackage: info: source version 0.5.1-2 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Benjamin Drung > > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean --buildsystem=golang --with=golang >dh_auto_clean -O--buildsystem=golang >dh_autoreconf_clean -O--buildsystem=golang >dh_clean -O--buildsystem=golang > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building golang-github-prometheus-exporter-toolkit using > existing ./golang-github-prometheus-exporter-toolkit_0.5.1.orig.tar.gz > dpkg-source: info: building golang-github-prometheus-exporter-toolkit in > golang-github-prometheus-exporter-toolkit_0.5.1-2.debian.tar.xz > dpkg-source: info: building golang-github-prometheus-exporter-toolkit in > golang-github-prometheus-exporter-toolkit_0.5.1-2.dsc > debian/rules binary > dh binary --buildsystem=golang --with=golang >dh_update_autotools_config -O--buildsystem=golang >dh_autoreconf -O--buildsystem=golang >dh_auto_configure -O--buildsystem=golang >dh_auto_build -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 > github.com/prometheus/exporter-toolkit/web > github.com/prometheus/exporter-toolkit/web/kingpinflag > internal/unsafeheader > internal/goexperiment > internal/abi > internal/cpu > runtime/internal/atomic > runtime/internal/sys > runtime/internal/math > internal/race > sync/atomic > unicode > unicode/utf8 > internal/bytealg > container/list > internal/itoa > math/bits > crypto/internal/subtle > crypto/subtle > math > unicode/utf16 > vendor/golang.org/x/crypto/cryptobyte/asn1 > runtime > internal/nettrace > vendor/golang.org/x/crypto/internal/subtle > encoding > golang.org/x/sys/internal/unsafeheader > internal/reflectlite > sync > internal/testlog > internal/singleflight > math/rand > runtime/cgo > errors > sort > internal/oserror > io > syscall > strconv > bytes > hash > crypto/elliptic/internal/fiat > crypto > reflect > path > strings > time > internal/syscall/unix > internal/syscall/execenv > crypto/internal/randutil > bufio > crypto/hmac > context > internal/poll > io/fs > crypto/rc4 > vendor/golang.org/x/net/dns/dnsmessage > vendor/golang.org/x/crypto/hkdf > os > regexp/syntax > encoding/binary > internal/fmtsort > crypto/cipher > crypto/sha512 > crypto/ed25519/internal/edwards25519/field > fmt > crypto/aes > crypto/des > crypto/ed25519/internal/edwards25519 > crypto/md5 > crypto/sha1 > crypto/sha256 > math/big > encoding/hex > encoding/base64 > net > encoding/pem > net/url > path/filepath > vendor/golang.org/x/crypto/chacha20 > vendor/golang.org/x/crypto/poly1305 > io/ioutil > vendor/golang.org/x/sys/cpu > vendor/golang.org/x/crypto/curve25519 > vendor/golang.org/x/crypto/chacha20poly1305 > encoding/json > github.com/go-logfmt/logfmt > crypto/elliptic > encoding/asn1 > crypto/rand > crypto/ed25519 > vendor/golang.org/x/crypto/cryptobyte > crypto/rsa > crypto/dsa > crypto/x509/pkix > github.com/go-stack/stack > crypto/ecdsa > log > regexp > github.com/pkg/errors > github.com/jpillora/backoff > compress/flate > hash/crc32 > vendor/golang.org/x/text/transform > compress/gzip > github.com/go-kit/kit/log > vendor/golang.org/x/text/unicode/bidi > vendor/golang.org/x/text/unicode/norm > github.com/go-kit/kit/log/level > vendor/golang.org/x/net/http2/hpack
Bug#999800: [Pkg-javascript-devel] Bug#999800: Bug#999800: node-flatted: autopkgtest regression: Cannot find module '/tmp/autopkgtest-lxc.78cintn5/downtmp/build.nuC/src/cjs/index.js'
Control: tags -1 + moreinfo
Le 16/11/2021 à 23:05, Jonas Smedegaard a écrit :
> Quoting Paul Gevers (2021-11-16 21:11:39)
>> Source: node-flatted
>> Version: 3.2.2~ds-2
>> X-Debbugs-CC: debian...@lists.debian.org
>> Severity: serious
>> User: debian...@lists.debian.org
>> Usertags: regression
>>
>> Dear maintainer(s),
>>
>> With a recent upload of node-flatted the autopkgtest of node-flatted
>> fails in testing when that autopkgtest is run with the binary packages
>> of node-flatted from unstable. It passes when run with only packages
>> from testing. In tabular form:
>>
>> passfail
>> node-flatted from testing3.2.2~ds-2
>> all others from testingfrom testing
>>
>> I copied some of the output at the bottom of this report.
>>
>> Currently this regression is blocking the migration to testing [1]. Can
>> you please investigate the situation and fix it?
>>
>> More information about this bug and the reason for filing it can be found on
>> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
>>
>> Paul
>>
>> [1] https://qa.debian.org/excuses.php?package=node-flatted
>>
>> https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-flatted/16718609/log.gz
>>
>> internal/modules/cjs/loader.js:406
>> throw e;
>> ^
>>
>> Error: Cannot find module
>> '/tmp/autopkgtest-lxc.78cintn5/downtmp/build.nuC/src/cjs/index.js'
>> at createEsmNotFoundErr (internal/modules/cjs/loader.js:842:15)
>> at finalizeEsmResolution (internal/modules/cjs/loader.js:835:15)
>> at trySelf (internal/modules/cjs/loader.js:400:12)
>> at Function.Module._resolveFilename
>> (internal/modules/cjs/loader.js:793:24)
>> at Function.Module._load (internal/modules/cjs/loader.js:667:27)
>> at Module.require (internal/modules/cjs/loader.js:887:19)
>> at require (internal/modules/cjs/helpers.js:74:18)
>> at [eval]:1:1
>> at Script.runInThisContext (vm.js:120:18)
>> at Object.runInThisContext (vm.js:309:38) {
>>code: 'MODULE_NOT_FOUND',
>>path: '/tmp/autopkgtest-lxc.78cintn5/downtmp/build.nuC/src/package.json'
>> }
>> autopkgtest [11:11:00]: test command1
>
> I don't understand why it fails, and could use some help.
>
> When I log into a clean chroot, install the packages node-flatted and
> nodejs, then the test command succeeds - i.e. this prints "0":
>
>> node -e "require('flatted');"; echo $?
>
> But when executed inside the (to me super complex) autopkgtest
> framework, that same command apparently fails.
>
> What am I missing?
>
> - Jonas
Hi,
I'm unable to reproduce this failure using autopkgtest+schroot neither
autopkgtest+lxc
Cheers,
Yadd
Processed: Re: [Pkg-javascript-devel] Bug#999800: Bug#999800: node-flatted: autopkgtest regression: Cannot find module '/tmp/autopkgtest-lxc.78cintn5/downtmp/build.nuC/src/cjs/index.js'
Processing control commands: > tags -1 + moreinfo Bug #999800 [src:node-flatted] node-flatted: autopkgtest regression: Cannot find module '/tmp/autopkgtest-lxc.78cintn5/downtmp/build.nuC/src/cjs/index.js' Added tag(s) moreinfo. -- 999800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999800: [Pkg-javascript-devel] Bug#999800: Bug#999800: node-flatted: autopkgtest regression: Cannot find module '/tmp/autopkgtest-lxc.78cintn5/downtmp/build.nuC/src/cjs/index.js'
Control: tags -1 - moreinfo Le 16/11/2021 à 23:26, Yadd a écrit : > ... > Hi, > > I'm unable to reproduce this failure using autopkgtest+schroot neither > autopkgtest+lxc > > Cheers, > Yadd Sorry for the noise, there are 2 branches in salsa repo: debian/master and debian/latest
Processed: Re: [Pkg-javascript-devel] Bug#999800: Bug#999800: node-flatted: autopkgtest regression: Cannot find module '/tmp/autopkgtest-lxc.78cintn5/downtmp/build.nuC/src/cjs/index.js'
Processing control commands: > tags -1 - moreinfo Bug #999800 [src:node-flatted] node-flatted: autopkgtest regression: Cannot find module '/tmp/autopkgtest-lxc.78cintn5/downtmp/build.nuC/src/cjs/index.js' Removed tag(s) moreinfo. -- 999800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999800: marked as pending in node-flatted
Control: tag -1 pending Hello, Bug #999800 in node-flatted 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/js-team/node-flatted/-/commit/c8f6ae9171340323f9ba0b7a3cea1cf6bd3ddc0b Fix autopkgtest Closes: #999800 (this message was generated automatically) -- Greetings https://bugs.debian.org/999800
Processed: Bug#999800 marked as pending in node-flatted
Processing control commands: > tag -1 pending Bug #999800 [src:node-flatted] node-flatted: autopkgtest regression: Cannot find module '/tmp/autopkgtest-lxc.78cintn5/downtmp/build.nuC/src/cjs/index.js' Added tag(s) pending. -- 999800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999800: marked as done (node-flatted: autopkgtest regression: Cannot find module '/tmp/autopkgtest-lxc.78cintn5/downtmp/build.nuC/src/cjs/index.js')
Your message dated Tue, 16 Nov 2021 22:50:00 +
with message-id
and subject line Bug#999800: fixed in node-flatted 3.2.2~ds-3
has caused the Debian Bug report #999800,
regarding node-flatted: autopkgtest regression: Cannot find module
'/tmp/autopkgtest-lxc.78cintn5/downtmp/build.nuC/src/cjs/index.js'
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.)
--
999800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-flatted
Version: 3.2.2~ds-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of node-flatted the autopkgtest of node-flatted
fails in testing when that autopkgtest is run with the binary packages
of node-flatted from unstable. It passes when run with only packages
from testing. In tabular form:
passfail
node-flatted from testing3.2.2~ds-2
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=node-flatted
https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-flatted/16718609/log.gz
internal/modules/cjs/loader.js:406
throw e;
^
Error: Cannot find module
'/tmp/autopkgtest-lxc.78cintn5/downtmp/build.nuC/src/cjs/index.js'
at createEsmNotFoundErr (internal/modules/cjs/loader.js:842:15)
at finalizeEsmResolution (internal/modules/cjs/loader.js:835:15)
at trySelf (internal/modules/cjs/loader.js:400:12)
at Function.Module._resolveFilename
(internal/modules/cjs/loader.js:793:24)
at Function.Module._load (internal/modules/cjs/loader.js:667:27)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at [eval]:1:1
at Script.runInThisContext (vm.js:120:18)
at Object.runInThisContext (vm.js:309:38) {
code: 'MODULE_NOT_FOUND',
path: '/tmp/autopkgtest-lxc.78cintn5/downtmp/build.nuC/src/package.json'
}
autopkgtest [11:11:00]: test command1
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-flatted
Source-Version: 3.2.2~ds-3
Done: Yadd
We believe that the bug you reported is fixed in the latest version of
node-flatted, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yadd (supplier of updated node-flatted 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: Tue, 16 Nov 2021 23:34:54 +0100
Source: node-flatted
Architecture: source
Version: 3.2.2~ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Yadd
Closes: 999800
Changes:
node-flatted (3.2.2~ds-3) unstable; urgency=medium
.
* Team upload
* Fix autopkgtest (Closes: #999800)
Checksums-Sha1:
21a02e2548930a2ade07569d999bbd5301f10de5 2329 node-flatted_3.2.2~ds-3.dsc
23cee9c5fbb62468c5b66dfb7efddf1035b88105 5632
node-flatted_3.2.2~ds-3.debian.tar.xz
Checksums-Sha256:
7fc05ba451a76f82af08efbf83fe330de6227cc429a823e3e17c0afffb309314 2329
node-flatted_3.2.2~ds-3.dsc
7d28745274e110420cf3bcf253b1668c124235910cfeadec02cf8c8daf9f121a 5632
node-flatted_3.2.2~ds-3.debian.tar.xz
Files:
e68fc8b58054a9f50a5fa2e270a4b0b8 2329 javascript optional
node-flatted_3.2.2~ds-3.dsc
3acdccc1b55d01e1fea945633b55661b 5632 javascript optional
node-flatted_3.2.2~ds-3.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmGUMl4ACgkQ9tdMp8mZ
7unawg/+MTcI44UdUIuIqNOXrNTu/ShesSSgXYTGC9ub9e7ToUqc1w3B6Rlq3ug7
0BxDDdKJlRA4xmJU3Aa7t/TGB7Ivovs9WhvvGMnE94DrnasP0bQN+8XFj0mmTdA8
qgWwMIqiXCeLyFdun1Y2n/tLauTfgda2hwEgHiFTPX51qOfP541jjUKpc4EKmaeY
elfKjH0k2wbsyzhdf
Processed: tagging 995318, tagging 995359, tagging 982154, tagging 906496, tagging 880879, tagging 867261 ...
Processing commands for cont...@bugs.debian.org:
> tags 995318 + experimental
Bug #995318 [src:numpy] numpy: Does not build from source in current unstable
Added tag(s) experimental.
> tags 995359 + experimental
Bug #995359 [src:ruby-gitlab-labkit] ruby-gitlab-labkit: autopkgtest needs
update for new version of ruby-jaeger-client: Could not find 'jaeger-client'
(~> 0.10)
Added tag(s) experimental.
> tags 982154 + experimental bookworm
Bug #982154 {Done: Antoine Beaupré } [src:trocla] trocla
FTBFS: test failure
Added tag(s) bookworm and experimental.
> tags 906496 + bookworm
Bug #906496 [src:obexpushd] obexpushd: FTBFS in buster/sid (linux/irda.h: No
such file or directory)
Bug #906525 [src:obexpushd] obexpushd: FTBFS: src/net/irobex.c:9:10: fatal
error: linux/irda.h: No such file or directory
Added tag(s) bookworm.
Added tag(s) bookworm.
> tags 880879 + bookworm
Bug #880879 [src:haskell-dpkg] haskell-dpkg FTBFS: hlibrary.setup: parsing
output of pkg-config --modversion failed
Added tag(s) bookworm.
> tags 867261 + bookworm
Bug #867261 [src:tldp] tldp FTBFS with Python 3.6 as supported Python version
Added tag(s) bookworm.
> tags 844145 - sid stretch buster bullseye
Bug #844145 [src:elektra] elektra: FTBFS: kdberrors.h:489:0: error: invalid
storage class for function 'elektraSetErrorf8'
Removed tag(s) buster, sid, stretch, and bullseye.
> tags 840748 + bookworm
Bug #840748 [edb] edb: install script failed for emacs25 because of :indent
keyword
Added tag(s) bookworm.
> tags 941101 + bookworm
Bug #941101 [src:rdup] rdup: Uses functions deprecated in Nettle 3.5
Added tag(s) bookworm.
> tags 950999 - bullseye sid
Bug #950999 [src:libkiokudb-perl] libkiokudb-perl: FTBFS with recent YAML*
packages
Removed tag(s) sid and bullseye.
> tags 959193 + bookworm
Bug #959193 [src:libperl5i-perl] libperl5i-perl: Test failures with
Devel::Declare 0.006022-1
Added tag(s) bookworm.
> tags 945625 - bullseye sid
Bug #945625 [src:cicero] cicero: Python2 removal in sid/bullseye
Removed tag(s) bullseye and sid.
> tags 936777 + bookworm
Bug #936777 [src:k3d] k3d: Python2 removal in sid/bullseye
Added tag(s) bookworm.
> tags 936303 - bullseye sid
Bug #936303 [src:cinfony] cinfony: Python2 removal in sid/bullseye
Removed tag(s) sid and bullseye.
> tags 937266 + bookworm
Bug #937266 [src:pd-py] pd-py: Python2 removal in sid/bullseye
Added tag(s) bookworm.
> tags 964155 + bookworm
Bug #964155 [src:libtemplate-plugin-calendar-simple-perl]
libcalendar-simple-perl breaks libtemplate-plugin-calendar-simple-perl
autopkgtest: not ok 1 - correct output for Jan 1970
Added tag(s) bookworm.
> tags 964824 - bullseye sid
Bug #964824 [src:hdevtools] hdevtools: FTBFS with GHC 8.8
Removed tag(s) sid and bullseye.
> tags 936955 + bookworm
Bug #936955 [src:lizardfs] lizardfs: Python2 removal in sid/bullseye
Bug #966757 [src:lizardfs] lizardfs: Unversioned Python removal in sid/bullseye
Added tag(s) bookworm.
Added tag(s) bookworm.
> tags 937312 + bookworm
Bug #937312 [src:postnews] postnews: Python2 removal in sid/bullseye
Bug #966775 [src:postnews] postnews: Unversioned Python removal in sid/bullseye
Added tag(s) bookworm.
Added tag(s) bookworm.
> tags 938432 - bullseye sid
Bug #938432 [src:sandsifter] sandsifter: Python2 removal in sid/bullseye
Bug #966791 [src:sandsifter] sandsifter: Unversioned Python removal in
sid/bullseye
Removed tag(s) sid and bullseye.
Removed tag(s) sid and bullseye.
> tags 912485 + bookworm
Bug #912485 [src:childsplay] childsplay: Please migrate to python3-pygame
Added tag(s) bookworm.
> tags 936298 + bookworm
Bug #936298 [src:childsplay] childsplay: Python2 removal in sid/bullseye
Bug #966725 [src:childsplay] childsplay: Unversioned Python removal in
sid/bullseye
Added tag(s) bookworm.
Added tag(s) bookworm.
> tags 938351 - sid bullseye
Bug #938351 [src:renpy] renpy: Python2 removal in sid/bullseye
Removed tag(s) sid and bullseye.
> tags 967093 + bookworm
Bug #967093 [src:hothasktags] hothasktags: FTBFS: unsatisfiable
build-dependency: libghc-src-exts-dev (< 1.21) but 1.22.0-1 is to be installed
Added tag(s) bookworm.
> tags 964964 + bookworm
Bug #964964 [ruby-codemirror-rails] ruby-codemirror-rails: ftbfs with rails 6
in experimental and unmainatained.
Added tag(s) bookworm.
> tags 936503 - sid bullseye
Bug #936503 [src:falcon] falcon: Python2 removal in sid/bullseye
Removed tag(s) bullseye and sid.
> tags 943037 - sid bullseye
Bug #943037 [src:git-hub] git-hub: Python2 removal in sid/bullseye
Bug #966742 [src:git-hub] git-hub: Unversioned Python removal in sid/bullseye
Removed tag(s) sid and bullseye.
Removed tag(s) bullseye and sid.
> tags 789292 + bookworm
Bug #789292 [src:dmtcp] dmtcp: FTBFS with glibc-2.21 and gcc-5
Bug #808644 [src:dmtcp] dmtcp: FTBFS: error: conflicting types for
‘_real_sigvec’
Added tag(s) bookworm.
Added tag(s) bookworm.
> tags 972910 - bullseye sid
Bug #972910 [src:lasagne] lasagne ftbfs with python3.9
Removed tag(s) bullseye and sid.
> tags 966736 + bookworm
Bug #966736 [src:ge
Processed: reassign 996342 to src:ruby-faker, forcibly merging 996224 996342
Processing commands for cont...@bugs.debian.org:
> reassign 996342 src:ruby-faker 1.9.1-2
Bug #996342 [src:ruby-omniauth-openid-connect] ruby-omniauth-openid-connect:
FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number
of arguments (given 2, expected 0..1)
Bug reassigned from package 'src:ruby-omniauth-openid-connect' to
'src:ruby-faker'.
No longer marked as found in versions ruby-omniauth-openid-connect/0.4.0-2.
Ignoring request to alter fixed versions of bug #996342 to the same values
previously set
Bug #996342 [src:ruby-faker] ruby-omniauth-openid-connect: FTBFS with ruby3.0:
ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given
2, expected 0..1)
Marked as found in versions ruby-faker/1.9.1-2.
> forcemerge 996224 996342
Bug #996224 {Done: Daniel Leidert } [src:ruby-faker]
ruby-faker: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error:
test_ch_methods(TestZhLocale): ArgumentError: wrong number of arguments (given
2, expected 0..1)
Bug #996216 {Done: Daniel Leidert } [src:ruby-faker]
ruby-devise-two-factor: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
ArgumentError:
Bug #996216 {Done: Daniel Leidert } [src:ruby-faker]
ruby-devise-two-factor: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
ArgumentError:
Added tag(s) experimental.
Added tag(s) experimental.
Bug #996342 [src:ruby-faker] ruby-omniauth-openid-connect: FTBFS with ruby3.0:
ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given
2, expected 0..1)
998772 was blocked by: 996342
998772 was not blocking any bugs.
Removed blocking bug(s) of 998772: 996342
996157 was blocked by: 996224 996216
996157 was not blocking any bugs.
Added blocking bug(s) of 996157: 996342
Marked Bug as done
Marked as fixed in versions ruby-faker/1.9.1-3.
Merged 996216 996224 996342
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
996157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996157
996216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996216
996224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996224
996342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996342
998772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#996586: heimdal: CVE-2021-3671
Brian May writes: > * Patch breaks compilation on latest Heimdal release: https://github.com/heimdal/heimdal/issues/849 Upstream solution is use the git version :-( -- Brian May
Bug#999768: lintian: false report: adopted-extended-field XS-Autobuild
On Tue, 2021-11-16 at 13:11:26 +0100, Andreas Beckmann wrote: > Package: lintian > Version: 2.112.0 > Severity: serious > > Lintian now reports > > I: nvidia-graphics-drivers source: adopted-extended-field XS-Autobuild (in > section for source) [debian/control:26] > > but that field is not usable as Autobuild, dpkg/sid does not accept it: > > dpkg-gencontrol: warning: unknown information field 'Autobuild' in input data > in general section of control info file > dpkg-genchanges: warning: unknown information field 'Autobuild' in input data > in general section of control info file > dpkg-source: warning: unknown information field 'Autobuild' in input data in > general section of control info file The same with XS-Go-Import-Path, and I guess a bunch of other fields that are unknown to dpkg-dev. Regards, Guillem
Bug#997301: marked as done (python-librtmp: FTBFS: build-dependency not installable: python3-cffi-backend-dbg)
Your message dated Tue, 16 Nov 2021 18:59:14 -0500 with message-id and subject line Re: python-librtmp: FTBFS: build-dependency not installable: python3-cffi-backend-dbg has caused the Debian Bug report #997301, regarding python-librtmp: FTBFS: build-dependency not installable: python3-cffi-backend-dbg 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.) -- 997301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-librtmp Version: 0.3.0-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 9), dh-python, librtmp-dev, > python3-all-dev, python3-all-dbg, python3-cffi, python3-cffi-backend-dbg, > python3-setuptools, python3 (>= 3.4), build-essential, fakeroot > Filtered Build-Depends: debhelper (>= 9), dh-python, librtmp-dev, > python3-all-dev, python3-all-dbg, python3-cffi, python3-cffi-backend-dbg, > python3-setuptools, python3 (>= 3.4), build-essential, fakeroot > 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 [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [418 B] > Get:5 copy:/<>/apt_archive ./ Packages [503 B] > Fetched 1878 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: python3-cffi-backend-dbg but it > is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2021/10/23/python-librtmp_0.3.0-1.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Version: 0.3.0-1.2 This bug is fixed with latest upload. Thanks, Boyuan Yang On Sat, 23 Oct 2021 21:48:13 +0200 Lucas Nussbaum wrote: > Source: python-librtmp > Version: 0.3.0-1.1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > +- -+ > > | Install package build dependencies | > > +- -+ > > > > > > Setup apt archive > > - > > > > Merged Build-Depends: debhelper (>= 9), dh-python, librtmp-dev, python3- all-dev, python3-all-dbg, python3-cffi, python3-cffi-backend-dbg, python3- setuptools, python3 (>= 3.4), build-essential, fakeroot > > Filtered Build-Depends: debhelper (>= 9), dh-python, librtmp-dev, python3- all-dev, python3-all-dbg, python3-cffi, python3-cffi-backend-dbg, python3- setuptools, python3 (>= 3.4), build-essential, fakeroot > > 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 [957 B] > > Ign:3 copy:/<>/apt_archive .
Bug#996369: Info
This issue seems to be caused by rails. The issue is gone when using rails 6.1.4 from experimental. Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Processed: Bug#996369 marked as pending in ruby-responders
Processing control commands: > tag -1 pending Bug #996369 [src:ruby-responders] ruby-responders: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. Added tag(s) pending. -- 996369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996369: marked as pending in ruby-responders
Control: tag -1 pending Hello, Bug #996369 in ruby-responders reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-responders/-/commit/d57053b119b916a2a70bea683c3eda079eeeb706 Rails 6.1 will fix the FTBFS * d/control (Build-Depends): Require rails 6.1 to fix FTBFS (closes: #996369). (this message was generated automatically) -- Greetings https://bugs.debian.org/996369
Bug#996292: marked as pending in ruby-http
Control: tag -1 pending Hello, Bug #996292 in ruby-http reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-http/-/commit/b7f9249335163edf5252cab140f277dcbdc351ef Build-depend on ruby-webrick (Closes: #996292) (this message was generated automatically) -- Greetings https://bugs.debian.org/996292
Processed: Bug#996292 marked as pending in ruby-http
Processing control commands: > tag -1 pending Bug #996292 [src:ruby-http] ruby-http: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick Added tag(s) pending. -- 996292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996292 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995781: [Debian-med-packaging] Bug#995781: python-sqlsoup autopkgtest fails with SQLAlchemy 1.4.23+ds1-2
On Tue, 2021-11-16 at 10:41 -0500, Mike Bayer wrote: > I've done both as well as taken down the readthedocs page. Looks good, thanks for that. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#998572: marked as done (pytools: FTBFS: dh_sphinxdoc: error: debian/python-pytools-doc/usr/share/doc/python-pytools-doc/html/_static/clipboard.min.js is missing)
Your message dated Wed, 17 Nov 2021 01:45:21 +0100
with message-id
and subject line Re: pytools: FTBFS: dh_sphinxdoc: error:
debian/python-pytools-doc/usr/share/doc/python-pytools-doc/html/_static/clipboard.min.js
is missing
has caused the Debian Bug report #998572,
regarding pytools: FTBFS: dh_sphinxdoc: error:
debian/python-pytools-doc/usr/share/doc/python-pytools-doc/html/_static/clipboard.min.js
is missing
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.)
--
998572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytools
Version: 2021.2.8-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> Running Sphinx v4.2.0
> making output directory... done
> loading intersphinx inventory from
> /usr/share/doc/python3-doc/html/objects.inv...
> loading intersphinx inventory from
> /usr/share/doc/python-numpy-doc/html/objects.inv...
> loading intersphinx inventory from
> https://documen.tician.de/pymbolic/objects.inv...
> loading intersphinx inventory from
> https://documen.tician.de/loopy/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'https://documen.tician.de/pymbolic/objects.inv' not
> fetchable due to :
> HTTPSConnectionPool(host='documen.tician.de', port=443): Max retries exceeded
> with url: /pymbolic/objects.inv (Caused by ProxyError('Cannot connect to
> proxy.', NewConnectionError(' 0x7fbdd7f0ca30>: Failed to establish a new connection: [Errno 111] Connection
> refused')))
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'https://documen.tician.de/loopy/objects.inv' not
> fetchable due to :
> HTTPSConnectionPool(host='documen.tician.de', port=443): Max retries exceeded
> with url: /loopy/objects.inv (Caused by ProxyError('Cannot connect to
> proxy.', NewConnectionError(' 0x7fbdd7f0cd90>: Failed to establish a new connection: [Errno 111] Connection
> refused')))
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 8 source files that are out of date
> updating environment: [new config] 8 added, 0 changed, 0 removed
> reading sources... [ 12%] codegen
> reading sources... [ 25%] graph
> reading sources... [ 37%] index
> reading sources... [ 50%] misc
> reading sources... [ 62%] obj_array
> reading sources... [ 75%] persistent_dict
> reading sources... [ 87%] reference
> reading sources... [100%] tag
>
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [ 12%] codegen
> writing output... [ 25%] graph
> writing output... [ 37%] index
> writing output... [ 50%] misc
> writing output... [ 62%] obj_array
> writing output... [ 75%] persistent_dict
> writing output... [ 87%] reference
> writing output... [100%] tag
>
> generating indices... genindex py-modindex done
> writing additional pages... search done
> copying static files... done
> copying extra files... done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded, 2 warnings.
>
> The HTML pages are in _build/html.
> make[2]: Leaving directory '/<>/doc'
> dh_installdocs
> install -d debian/python3-pytools/usr/share/doc/python3-pytools
> install -d debian/.debhelper/generated/python3-pytools
> cp --reflink=auto -a ./README.rst
> debian/python3-pytools/usr/share/doc/python3-pytools
> chmod -R u\+rw,go=rX debian/python3-pytools/usr/share/doc
> dh_installdocs: warning: Cannot auto-detect main package for
> python-pytools-doc. If the default is wrong, please use --doc-main-package
> install -p -m0644 debian/README.Debian
> debian/python3-pytools/usr/share/doc/python3-pytools/README.Debian
> install -p -m0644 debian/copyright
> debian/python3-pytools/usr/share/doc/python3-pytools/copyright
> install -d debian/python-pytools-doc/usr/share/doc/python-pytools-doc
> install -d debian/.debhelper/generated/python-pytools-doc
> cd './doc/_build/html/..' && find 'html' \( -type f -or -type l \) -and
> ! -empty -print0 | LC_ALL=C sort -z | xargs -0 -I {} cp --reflink=auto
> --parents -dp {}
> /<>/debian/python-pytools-doc/usr/share/doc/python-pytools-doc
> chmod -R
Bug#998588: marked as done (pyopencl: FTBFS: dh_sphinxdoc: error: debian/python-pyopencl-doc/usr/share/doc/python-pyopencl-doc/html/_static/clipboard.min.js is missing)
Your message dated Wed, 17 Nov 2021 01:53:28 +0100
with message-id <0648328b-dbc2-cf27-3134-f8d332bd0...@debian.org>
and subject line Re: pyopencl: FTBFS: dh_sphinxdoc: error:
debian/python-pyopencl-doc/usr/share/doc/python-pyopencl-doc/html/_static/clipboard.min.js
is missing
has caused the Debian Bug report #998588,
regarding pyopencl: FTBFS: dh_sphinxdoc: error:
debian/python-pyopencl-doc/usr/share/doc/python-pyopencl-doc/html/_static/clipboard.min.js
is missing
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.)
--
998588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyopencl
Version: 2021.2.9-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- -s custom --test-args="PYTHONPATH={build_dir} cp -r
> {dir}/test {build_dir} && cd {build_dir}/test && {interpreter} -m pytest
> --verbosity=2 -k 'not test_event_set_callback' && rm -rf {build_dir}/test"
> pybuild --test --test-pytest -i python{version} -p 3.9 -s custom
> "--test-args=PYTHONPATH={build_dir} cp -r {dir}/test {build_dir} && cd
> {build_dir}/test && {interpreter} -m pytest --verbosity=2 -k 'not
> test_event_set_callback' && rm -rf {build_dir}/test"
> D: pybuild pybuild:569: version: 5.20211022.1
> D: pybuild pybuild:570: ['/usr/bin/pybuild', '--test', '--test-pytest', '-i',
> 'python{version}', '-p', '3.9', '-s', 'custom',
> "--test-args=PYTHONPATH={build_dir} cp -r {dir}/test {build_dir} && cd
> {build_dir}/test && {interpreter} -m pytest --verbosity=2 -k 'not
> test_event_set_callback' && rm -rf {build_dir}/test"]
> D: pybuild pybuild:36: cfg: Namespace(verbose=True, quiet=False,
> really_quiet=False, detect_only=False, clean_only=False,
> configure_only=False, build_only=False, install_only=False, test_only=True,
> list_systems=False, print_args=None, before_clean=None, clean_args=None,
> after_clean=None, before_configure=None, configure_args=None,
> after_configure=None, before_build=None, build_args=None, after_build=None,
> before_install=None, install_args=None, after_install=None, before_test=None,
> test_args="PYTHONPATH={build_dir} cp -r {dir}/test {build_dir} && cd
> {build_dir}/test && {interpreter} -m pytest --verbosity=2 -k 'not
> test_event_set_callback' && rm -rf {build_dir}/test", after_test=None,
> test_nose=False, test_nose2=False, test_pytest=True, test_tox=False,
> dir='/<>', destdir='debian/tmp', ext_destdir=None,
> ext_pattern='\\.so(\\.[^/]*)?$', ext_sub_pattern=None, ext_sub_repl=None,
> install_dir=None, name=None, system='custom', versions=['3.9'],
> interpreter=['python{version}'], disable=None, custom_tests=True)
> D: pybuild __init__:36: cannot initialize 'cmake' plugin
> Traceback (most recent call last):
> File "/usr/share/dh-python/dhpython/build/__init__.py", line 32, in
> module.BuildSystem.is_usable()
> File "/usr/share/dh-python/dhpython/build/base.py", line 122, in is_usable
> raise Exception("missing command: %s" % command)
> Exception: missing command: cmake
> D: pybuild tools:232: invoking: /usr/bin/dpkg-architecture
> D: pybuild pybuild:132: detected build system: custom (certainty: 99%)
> I: pybuild base:232: PYTHONPATH=/<>/.pybuild/cpython3_3.9/build
> cp -r /<>/test /<>/.pybuild/cpython3_3.9/build &&
> cd /<>/.pybuild/cpython3_3.9/build/test && python3.9 -m pytest
> --verbosity=2 -k 'not test_event_set_callback' && rm -rf
> /<>/.pybuild/cpython3_3.9/build/test
> D: pybuild tools:232: invoking:
> PYTHONPATH=/<>/.pybuild/cpython3_3.9/build cp -r
> /<>/test /<>/.pybuild/cpython3_3.9/build && cd
> /<>/.pybuild/cpython3_3.9/build/test && python3.9 -m pytest
> --verbosity=2 -k 'not test_event_set_callback' && rm -rf
> /<>/.pybuild/cpython3_3.9/build/test
> = test session starts
> ==
> platform linux -- Python 3.9.7, pytest-6.2.5, py-1.10.0, pluggy-0.13.0 --
> /usr/bin/python3.9
> cachedir: .pytest_cache
> rootdir: /<>, configfile: pytest.ini
> collecting ... collected 258 items / 1 deselected / 257 selected
>
> test_algorithm.py::test_elwise_kernel[ 'pthread-Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz' on 'Portable
> Computing Language'>>] PASSED [ 0%]
> test_algorithm.py::test_elwise_kernel_with_options[ 'Portable Computing Language'>>] PASSED [ 0%]
> test_algorithm.p
Bug#996292: marked as done (ruby-http: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick)
Your message dated Wed, 17 Nov 2021 01:04:02 +
with message-id
and subject line Bug#996292: fixed in ruby-http 4.4.1-5
has caused the Debian Bug report #996292,
regarding ruby-http: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot
load such file -- webrick
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.)
--
996292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-http
Version: 4.4.1-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-http was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> cannot load such file -- webrick
> #
> :85:in
> `require'
> #
> :85:in
> `require'
> # ./spec/support/dummy_server.rb:3:in `'
> #
> :85:in
> `require'
> #
> :85:in
> `require'
> # ./spec/lib/http_spec.rb:6:in `'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:2103:in
> `load'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:2103:in
> `load_file_handling_errors'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:1606:in
> `block in load_spec_files'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:1604:in
> `each'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:1604:in
> `load_spec_files'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:102:in
> `setup'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:86:in
> `run'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:71:in
> `run'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:45:in
> `invoke'
> # /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec:4:in
> `'
> Run options: include {:focus=>true}
>
> All examples were filtered out; ignoring {:focus=>true}
>
> Top 0 slowest examples (0 seconds, 0.0% of total time):
>
> Finished in 0.8 seconds (files took 0.7255 seconds to load)
> 0 examples, 0 failures, 2 errors occurred outside of examples
>
> Coverage report generated for RSpec to /<>/coverage. 652 / 1361
> LOC (47.91%) covered.
> [33m[Coveralls] Outside the CI environment, not sending data.[0m
> Stopped processing SimpleCov as a previous error not related to SimpleCov has
> been detected
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed:
Note that webrick has been removed from the standard library. It's
already been packaged and is currently in NEW, but this package now
needs an explicit dependency on it.
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-http/ruby-http_4.4.1-4+rebuild1633382951_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-http
Source-Version: 4.4.1-5
Done: Cédric Boutillier
We believe that the bug you reported is fixed in the latest version of
ruby-http, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Cédric Boutillier (supplier of updated ruby-http package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 17 Nov 2021 01:37:24 +0100
Source: ruby-http
Architecture: source
Version: 4.4.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Cédric Boutillier
Processed: tagging 998623, found 964138 in 2.9.0-1, notfound 964138 in 2.8.3-2, fixed 964138 in 2.8.3-2 ...
Processing commands for cont...@bugs.debian.org:
> tags 998623 + sid bookworm
Bug #998623 {Done: Stefano Rivera } [src:pysha3] pysha3:
FTBFS with dh-python 5.20211105 due to missing tox.ini
Added tag(s) sid and bookworm.
> found 964138 2.9.0-1
Bug #964138 [src:sec] src:sec: fails to migrate to testing for too long:
maintainer built arch:all binary
Marked as found in versions sec/2.9.0-1; no longer marked as fixed in versions
sec/2.9.0-1.
> notfound 964138 2.8.3-2
Bug #964138 [src:sec] src:sec: fails to migrate to testing for too long:
maintainer built arch:all binary
No longer marked as found in versions sec/2.8.3-2.
> fixed 964138 2.8.3-2
Bug #964138 [src:sec] src:sec: fails to migrate to testing for too long:
maintainer built arch:all binary
Marked as fixed in versions sec/2.8.3-2.
> fixed 964138 2.8.2-1.1
Bug #964138 [src:sec] src:sec: fails to migrate to testing for too long:
maintainer built arch:all binary
Marked as fixed in versions sec/2.8.2-1.1.
> tags 964138 - bullseye sid bookworm
Bug #964138 [src:sec] src:sec: fails to migrate to testing for too long:
maintainer built arch:all binary
Removed tag(s) bookworm, sid, and bullseye.
> tags 983229 + sid bookworm
Bug #983229 {Done: Olly Betts } [src:survex] survex: FTBFS
with PROJ 8.0.0
Added tag(s) bookworm and sid.
> tags 998317 + bookworm sid
Bug #998317 {Done: Christoph Berg } [gavodachs2-server]
PostgreSQL 14 transition
Added tag(s) bookworm and sid.
> found 998345 0.9.2-1
Bug #998345 {Done: Jonas Smedegaard }
[librust-quickcheck+env-logger-dev] librust-quickcheck+env-logger-dev:
uninstallable - depends on non-existing package librust-env-logger-0.7-dev
Marked as found in versions rust-quickcheck/0.9.2-1.
> found 996486 1.23-1
Bug #996486 {Done: Laszlo Boszormenyi (GCS) } [src:leveldb]
bitcoind: fails to start with undefined symbol: _ZTIN7leveldb6LoggerE
Bug #997927 {Done: Laszlo Boszormenyi (GCS) } [src:leveldb]
Please re-enable RTTI support in leveldb
Marked as found in versions leveldb/1.23-1.
Marked as found in versions leveldb/1.23-1.
> tags 983230 + sid bookworm
Bug #983230 {Done: Alastair McKinstry } [src:xygrib]
xygrib: FTBFS with PROJ 8.0.0
Added tag(s) bookworm and sid.
> found 998347 0.59.1-1
Bug #998347 {Done: Jonas Smedegaard }
[librust-bindgen+env-logger-dev] librust-bindgen+env-logger-dev: uninstallable
- depends on non-existing package librust-env-logger-0.7+default-dev
Marked as found in versions rust-bindgen/0.59.1-1.
> tags 947878 + sid bookworm
Bug #947878 [src:gnome-mime-data] gnome-mime-data: unmaintained upstream for
over a decade
Added tag(s) bookworm and sid.
> reassign 995346 src:ruby-fauxhai 7.4.0-1
Bug #995346 {Done: Lucas Kanashiro }
[src:ruby-chef-utils] ruby-chef-utils: depends on the Internet during build
Bug reassigned from package 'src:ruby-chef-utils' to 'src:ruby-fauxhai'.
No longer marked as found in versions ruby-chef-utils/16.12.3-2.
No longer marked as fixed in versions ruby-fauxhai/7.5.0-1.
Bug #995346 {Done: Lucas Kanashiro } [src:ruby-fauxhai]
ruby-chef-utils: depends on the Internet during build
Marked as found in versions ruby-fauxhai/7.4.0-1.
> fixed 995346 7.5.0-1
Bug #995346 {Done: Lucas Kanashiro } [src:ruby-fauxhai]
ruby-chef-utils: depends on the Internet during build
Marked as fixed in versions ruby-fauxhai/7.5.0-1.
> affects 995346 + src:ruby-chef-utils
Bug #995346 {Done: Lucas Kanashiro } [src:ruby-fauxhai]
ruby-chef-utils: depends on the Internet during build
Added indication that 995346 affects src:ruby-chef-utils
> notfixed 984364 3.34.0-1
Bug #984364 {Done: Simon McVittie } [src:template-glib]
template-glib: ftbfs with GCC-11
No longer marked as fixed in versions 3.34.0-1.
> fixed 998886 4.2.3+~9.2.2-1
Bug #998886 {Done: Yadd } [node-string-width,node-slice-ansi]
node-string-width,node-slice-ansi: both ship
/usr/share/nodejs/is-fullwidth-code-point/*
Bug #998911 {Done: Yadd } [node-string-width,node-slice-ansi]
node-string-width: file conflict with node-slice-ansi
There is no source info for the package 'node-slice-ansi' at version
'4.2.3+~9.2.2-1' with architecture ''
Marked as fixed in versions node-string-width/4.2.3+~9.2.2-1.
Marked as fixed in versions node-string-width/4.2.3+~9.2.2-1.
> fixed 993398 2:19.0.0~rc1-1
Bug #993398 {Done: Michal Arbet } [src:neutron]
neutron: CVE-2021-40085: Arbitrary dnsmasq reconfiguration via extra_dhcp_opts
Marked as fixed in versions neutron/2:19.0.0~rc1-1.
> fixed 990705 2:23.0.2-1
Bug #990705 {Done: Thomas Goirand } [nova-common] nova-common:
please depend on python3-q-text-as-data
Marked as fixed in versions nova/2:23.0.2-1.
> notfixed 997315 python3-sqlalchemy/1.4.23+ds1-5
Bug #997315 {Done: "Robin Jarry" } [src:buildbot] buildbot:
FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9
--system=custom "--test-args=PYTHONPATH=pkg:{destdir}/{install_dir}
PATH=\$PATH:{destdir}/usr/bin trial3 --reporter=text buildbot.test
buildbot_worker.test" returned exit code 13
The source python3-sqlalchemy and version
Bug#997541: marked as pending in oldsys-preseed
Control: tag -1 pending Hello, Bug #997541 in oldsys-preseed 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/installer-team/oldsys-preseed/-/commit/97f4187734afa4f1e7e98b9417f5f33ec5a481e2 tests/do-test: Switch to using "mktemp" instead of "tmpfile" (Closes: #997541) (this message was generated automatically) -- Greetings https://bugs.debian.org/997541
Processed: Bug#997541 marked as pending in oldsys-preseed
Processing control commands: > tag -1 pending Bug #997541 [src:oldsys-preseed] oldsys-preseed: FTBFS: Running test misc/hostname... ./do-test: line 17: tempfile: command not found Added tag(s) pending. -- 997541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998602: marked as done (matplotlib: FTBFS: dh_sphinxdoc: error: debian/python-matplotlib-doc/usr/share/doc/python-matplotlib-doc/html/_static/clipboard.min.js is missing)
Your message dated Wed, 17 Nov 2021 02:23:44 +0100 with message-id <6495c445-1841-f3dd-66ee-2ad98ed82...@debian.org> and subject line Re: matplotlib: FTBFS: dh_sphinxdoc: error: debian/python-matplotlib-doc/usr/share/doc/python-matplotlib-doc/html/_static/clipboard.min.js is missing has caused the Debian Bug report #998602, regarding matplotlib: FTBFS: dh_sphinxdoc: error: debian/python-matplotlib-doc/usr/share/doc/python-matplotlib-doc/html/_static/clipboard.min.js is missing 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.) -- 998602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: matplotlib Version: 3.3.4-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules binary > py3versions: no X-Python3-Version in control file, using supported versions > dh_testdir -i > dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel > dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel > dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel > dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel > dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel > dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel > dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel > dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel > dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel > dpkg-buildflags: warning: invalid flag in DEB_BUILD_OPTIONS: --no-parallel > dh_testroot -i > dh_prep > dh_install -p python-matplotlib-data > dh_install: warning: Compatibility levels before 10 are deprecated (level 7 > in use) > rm -fr > /<>/debian/python-matplotlib-data/usr/share/matplotlib/mpl-data/fonts/ttf/Vera*.ttf > rm -fr > /<>/debian/python-matplotlib-data/usr/share/matplotlib/mpl-data/fonts/ttf/*.TXT > rm -fr > /<>/debian/python-matplotlib-data/usr/share/matplotlib/mpl-data/fonts/ttf/local.conf > rm -fr > /<>/debian/python-matplotlib-data/usr/share/matplotlib/mpl-data/fonts/pdfcorefonts/readme.txt > chmod 644 > /<>/debian/python-matplotlib-data/usr/share/matplotlib/mpl-data/images/*.svg > dh_testdir -i > dh_testroot -i > dh_installchangelogs > dh_installchangelogs: warning: Compatibility levels before 10 are deprecated > (level 7 in use) > dh_installdocs -ppython-matplotlib-doc -i doc/build/html/ tutorials/ > dh_installdocs: warning: Compatibility levels before 10 are deprecated (level > 7 in use) > # remove pyc file from doc > dh_installexamples -ppython-matplotlib-doc -i examples/* > dh_installexamples: warning: Compatibility levels before 10 are deprecated > (level 7 in use) > dh_compress -i -Xexamples -Xexamples/data -Xpdf -X.js -X.py -Xobjects.inv > -X.html > dh_compress: warning: Compatibility levels before 10 are deprecated (level 7 > in use) > dh_compress: warning: Compatibility levels before 10 are deprecated (level 7 > in use) > dh_link -i > dh_sphinxdoc > dh_sphinxdoc: error: > debian/python-matplotlib-doc/usr/share/doc/python-matplotlib-doc/html/_static/clipboard.min.js > is missing > make: *** [debian/rules:163: binary-indep] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/matplotlib_3.3.4-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- On Thu, 4 Nov 2021 20:22:00 +0100 Lucas Nussbaum wrote: Source: matplotlib Version: 3.3.4-2 > dh_sphinxdoc: error: debian/python-matplotlib-doc/usr/share/doc/python-matplotlib-doc/html/_static/clipboard.min.js is missing Fixed in python3-sphinx-copybutton 0.4.0-2. Andreas--- End Message ---
Processed: Re: Bug#999760 closed by Debian FTP Masters (reply to Timo Röhling ) (Bug#999760: fixed in opencv 4.5.4+dfsg-3)
Processing control commands:
> found -1 4.5.4+dfsg-3
Bug #999760 {Done: Timo Röhling } [src:opencv] opencv:
libopencv-*4.5d: missing Breaks+Replaces: libopencv-*4.5
Marked as found in versions opencv/4.5.4+dfsg-3; no longer marked as fixed in
versions opencv/4.5.4+dfsg-3 and reopened.
--
999760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#999760: closed by Debian FTP Masters (reply to Timo Röhling ) (Bug#999760: fixed in opencv 4.5.4+dfsg-3)
Control: found -1 4.5.4+dfsg-3 This also affects the -jave and -jni packages: Preparing to unpack .../libopencv4.5d-jni_4.5.4+dfsg-3_amd64.deb ... Unpacking libopencv4.5d-jni (4.5.4+dfsg-3) ... dpkg: error processing archive /var/cache/apt/archives/libopencv4.5d-jni_4.5.4+dfsg-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/jni/libopencv_java454.so', which is also in package libopencv4.5-jni 4.5.4+dfsg-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../libopencv4.5d-java_4.5.4+dfsg-3_amd64.deb ... Unpacking libopencv4.5d-java (4.5.4+dfsg-3) ... dpkg: error processing archive /var/cache/apt/archives/libopencv4.5d-java_4.5.4+dfsg-3_amd64.deb (--unpack): trying to overwrite '/usr/share/java/opencv4/opencv-454.jar', which is also in package libopencv4.5-java 4.5.4+dfsg-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libopencv4.5d-jni_4.5.4+dfsg-3_amd64.deb /var/cache/apt/archives/libopencv4.5d-java_4.5.4+dfsg-3_amd64.deb Andreas
Bug#999813: util-linux: Upgrade from buster to bullseye fails because of util-linux
Package: util-linux Version: 2.36.1-8 Severity: critical Justification: breaks the whole system ear Maintainer, I was upgrading 'buster' to 'bullseye' using simple instructions here: https://linuxiac.com/upgrade-debian-10-buster-to-debian-11-bullseye/ Which has worked in every upgrade until the last one, on a different machine than the one I'm submitting this bug on. That machine requires a reinstall of the operating system from scratch. I have at least 20 years experience using debian, so this is certainly not an easy problem, and it may be a one-of-a-kind glitch due to random data corruption on disk. I cannot reproduce it, because the installation in question is no longer bootable, and I don't want to screw around with what I view as a lost cause. The system got into a state in which new software was not installable, but was needed to install upgrades. The culprit was the 'util-linux' package. This was an older, but up to date 'buster' installation, that had seen a lot of use. Of course user settings can be recovered from backups, but what a pain! I've got to say now that the debian team is second to none, absolutely top-notch, especially in the installer, which I've used several times over the past few weeks. The util-linux package failed to complete post-install scripts, which I took to mean the script is faulty. One thing I not able to do: delete the configuration files corresponding to util-linux, in /var/lib/dpkg/info. But I tried: $ dpkg -i --force-depends util-linux(full file name of deb found in /var/cache/apt/archives) Ended with failure of post install $ dpkg --configure --pending Repeatedly, got me a bit further in the upgrade, but the util-linux package ultimately led to further failure $ apt-get -f install Failed with a libcrypt perl error, installing liccrypt and libcrypt-dev using 'dpkg -i --force-depends' succeeded, but made no difference. Appstreamcli threw an error with 'symbol could not be found', or something like that, and the exact text of the message was found with: $ strings appstreamcli | grep So that went nowhere. I also checked LD_LIBRARY_PATH, and substituted several paths, but none fixed the problem. So, I set it to empty for the duration of my ordeal. Util-linux was half installed. Bsdmainutils may have also played a role, as it, along with at least 10 other packages had permanent errors from 'dpkg'. I tried to straighten the whole mess using 'dselect', which sometimes works, but it didn't this time. The upgrade succeeded through: $ apt-get upgrade --without-new-pkgs but failed with the final step: $ apt-get full-upgrade If there is anything else I could try, I'm still learning debian, so let me know! And, thank you for being active in the development of: 'The Worlds Reference Standard Computer Operating System'. Debian gets better each day, because of the efforts put forth by the developers. Currently, it is perhaps 'possible' to salvage the upgrade, but my preference would be to do a fresh install, and simply have the team notified to test util-linux, and see whether it is defective. Maybe something will be uncovered. The system info is relevant only in that I'm submitting the report on a machine running bullseye, and the machinbe in question was in the midst of an upgrade to bullseye. -- System Information: Debian Release: 11.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages util-linux depends on: ii libaudit1 1:3.0-2 ii libblkid1 2.36.1-8 ii libc6 2.31-13 ii libcap-ng0 0.7.9-2.2+b1 ii libcrypt1 1:4.4.18-4 ii libmount1 2.36.1-8 ii libpam0g 1.4.0-9 ii libselinux13.1-3 ii libsmartcols1 2.36.1-8 ii libsystemd0247.3-6 ii libtinfo6 6.2+20201114-2 ii libudev1 247.3-6 ii libuuid1 2.36.1-8 ii login 1:4.8.1-1 ii zlib1g 1:1.2.11.dfsg-2 util-linux recommends no packages. Versions of packages util-linux suggests: ii dosfstools 4.2-1 ii kbd 2.3.0-3 ii util-linux-locales 2.36.1-8 -- no debconf information
Processed: tagging 996346, severity of 996346 is important
Processing commands for cont...@bugs.debian.org: > tags 996346 + moreinfo unreproducible Bug #996346 [src:ruby-parallel] ruby-parallel: FTBFS with ruby3.0: ERROR: Test "ruby2.7" failed: Failure/Error: out.should == "0,1\nOK" Added tag(s) unreproducible and moreinfo. > # unreproducible - maybe just a flaky test? downgrading > severity 996346 important Bug #996346 [src:ruby-parallel] ruby-parallel: FTBFS with ruby3.0: ERROR: Test "ruby2.7" failed: Failure/Error: out.should == "0,1\nOK" Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 996346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998679:
Hi All, This bug has already been discussed and fixed in the mainline firefox packages (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998108). The discussion even includes a one-liner for hex-editing the binary to fix the freezing. Any reason why this fix cannot be backported to the firefox-esr package? Regards, Vlad
Bug#996586: marked as done (heimdal: CVE-2021-3671)
Your message dated Wed, 17 Nov 2021 04:48:33 + with message-id and subject line Bug#996586: fixed in heimdal 7.7.0+dfsg-3 has caused the Debian Bug report #996586, regarding heimdal: CVE-2021-3671 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.) -- 996586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: heimdal Version: 7.7.0+dfsg-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 7.5.0+dfsg-3 Hi, The following vulnerability was published for heimdal. CVE-2021-3671[0]: | A null pointer de-reference was found in the way samba kerberos server | handled missing sname in TGS-REQ (Ticket Granting Server - Request). | An authenticated user could use this flaw to crash the samba server. 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-2021-3671 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3671 [1] https://github.com/heimdal/heimdal/commit/04171147948d0a3636bc6374181926f0fb2ec83a [2] https://github.com/heimdal/heimdal/commit/773802aecfb4b6a73817fa522faeb55b2a7cdb2a Regards, Salvatore --- End Message --- --- Begin Message --- Source: heimdal Source-Version: 7.7.0+dfsg-3 Done: Brian May We believe that the bug you reported is fixed in the latest version of heimdal, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Brian May (supplier of updated heimdal package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 17 Nov 2021 12:12:45 +1100 Source: heimdal Architecture: source Version: 7.7.0+dfsg-3 Distribution: unstable Urgency: high Maintainer: Brian May Changed-By: Brian May Closes: 996586 Changes: heimdal (7.7.0+dfsg-3) unstable; urgency=high . * Fix CVE-2021-3671: A null pointer de-reference was found in the way samba kerberos server handled missing sname in TGS-REQ. Closes: #996586. * Fix autoconf 2.7 issues. Checksums-Sha1: c4d5fc13974baa269ed94af5ee624ec3cd192d97 3580 heimdal_7.7.0+dfsg-3.dsc 2b71fff4c2e4a4c8b2c6ab3e4f5dc40b26b6388f 5945252 heimdal_7.7.0+dfsg.orig.tar.xz 9588f0414db58fa45bebf6ade89b432951721d0d 129156 heimdal_7.7.0+dfsg-3.debian.tar.xz 31e694f184237e664cfc1026ba396bff9e228121 7613 heimdal_7.7.0+dfsg-3_source.buildinfo Checksums-Sha256: ca8d8b706816777d6d919cccdcb3190cf241c690b2f78de090411866d73ffcd7 3580 heimdal_7.7.0+dfsg-3.dsc 6822c9547188b753b6325047fda9255744e4ebbbe02bb0dade78c261061fefac 5945252 heimdal_7.7.0+dfsg.orig.tar.xz 4a11646bdaff58958c6796ebdb23b808aa52924712832de539a08c1731d56299 129156 heimdal_7.7.0+dfsg-3.debian.tar.xz 2068dd6a3fc5d62e28ed717c4b582023a61e1e695aef0983e96ccc482d3cb567 7613 heimdal_7.7.0+dfsg-3_source.buildinfo Files: e055ec1334069b8ad78270121457a72f 3580 net optional heimdal_7.7.0+dfsg-3.dsc 4400de10f7a569fe14ecb2641aea341b 5945252 net optional heimdal_7.7.0+dfsg.orig.tar.xz c8a8320753fd0d0b5ee0d9122fc0ca71 129156 net optional heimdal_7.7.0+dfsg-3.debian.tar.xz 9d6871450cbc1e335167a7521948136d 7613 net optional heimdal_7.7.0+dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEKpwfR8DOwu5vyB4TKpJZkldkSvoFAmGUg9YACgkQKpJZkldk SvrqMRAAiOObSd2Xh8M6eAyUlv+WT+DEeN+Cz/3MUBDK7f75k4glaDRp5w1al1kJ F5+3Ig8kPUuPpfX6CMcTcTMZB5nO222LEWk/4rqYY0aWjf99mBGrSFfUFXAPpKJ9 rTelhb9sNoWdh5e2nxWsdLN8SHc8+iKzxE1vdlBgsCzrSCZQ4m1QewTupRdrKaI3 2umsP7U8dTtAP+dv850qyXBIByLcW2QEOyKNA3JTps1yjm5D8pmn45Gg8mJ9m0L3 86lMlZyV8xfR13CqMSuzMyZD6NKyEL88MQkVcSNLies97IP0LvwkkuxMFPgwJXe/ n+s5G0hE0ltlLlFCtPvn60sCfy2IolgkElEsgu1JyJZeHXaVuRPw5w7DGjj3BA1e x3DtiuMXBZTnb58mips1DztxTR5eCxw8QHS85hgCo/s+Dgnjc5onSrEQWzT0ARWc eFGdlezj88A1mMPJN+3MJ5RNj04P8hhcJYuDx3LD7ogDjhXG8RhXHqg8fytmnPWU /bLd9HTNJOK33MJCWGin39YUqvVwJj4h2gsLe9PpJ94ok2bSQF11jjT4mrSiH1cR FxNZ/kdKe/9kLeCgdzh+n0H+5BMryeTYJ/wxnQ5FqkeK+S9OvJUbi9tk5bPoTOJ5 Ac5VhrfNa52uEw+AdpS+tyYW1F5CLLbCJZhS
Bug#999815: cryptsetup - build-depends on removed package.
Package: cryptsetup Version: 2:2.4.1-1 Severity: serious cryptsetup build-depends on libsepol1-dev which is no longer built by the libsepol source package. The package is completely gone from testing, in unstable it is still present as a cruft package, but is not usable for building cryptsetup because the current version of libselinux1-dev conflicts with it. I suspect (but have not tested) that you need to change your build-dependency to libsepol-dev.
Bug#999816: rpm - build-depends on removed package.
Package: rpm Version: 4.16.1.2+dfsg1-3 Tags: bookworm, sid Severity: serious rpm build-depends on libsepol1-dev which is no longer built by the libsepol source package. The package is completely gone from testing, in unstable it is still present as a cruft package, but is not usable for building cryptsetup because the current version of libselinux1-dev conflicts with it. I suspect (but have not tested) that you need to change your build-dependency to libsepol-dev.
Bug#999817: libstdc++-arm-none-eabi build-depends on removed package.
Package: libstdc++-arm-none-eabi Version: 13 Severity: serious x-debbugs-cc: kei...@debian.org libstdc++-arm-none-eabi build-depends on the gcc-arm-none-eabi-source binary package which is no longer built by the gcc-arm-none-eabi source package. It is still present in unstable as a cruft package but is completely gone from testing. Keith's comment when removing the package was "Why did this exist?", so I would guess that he did not check reverse build-dependencies.
Bug#999818: node-regenerate-unicode-properties build-depends on removed package.
Package: node-regenerate-unicode-properties Version: 8.2.0+ds-2 Severity: serious node-regenerate-unicode-properties build-depends on node-unicode-13.0.0 which is no longer built by the node-unicode-data source package. It is still present in unstable as a cruft package but is completely gone from testing. The package appears to have been replaced by node-unicode-14.0.0
Bug#999819: node-regexpu-core build-depends on removed package.
Package: node-regexpu-core Version: 4.7.1-3 Severity: serious node-regexpu-core build-depends on node-unicode-13.0.0 which is no longer built by the node-unicode-data source package. It is still present in unstable as a cruft package but is completely gone from testing. The package appears to have been replaced by node-unicode-14.0.0
Bug#999821: fftw: FBTFS: dh_install: error: missing files, aborting
Source: fftw Version: 2.1.5-5 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) fftw fails to build from source: |debian/rules override_dh_install-arch | make[1]: Entering directory '/<>' | mkdir -p /<>/debian/tmp-single/usr/share/doc/sfftw-dev/fortran | mkdir -p /<>/debian/tmp-double/usr/share/doc/fftw-dev/fortran | cp -a fortran/fftw_f77.i /<>/debian/tmp-single/usr/share/doc/sfftw-dev/fortran/ | cp -a fortran/fftw_f77.i /<>/debian/tmp-double/usr/share/doc/fftw-dev/fortran/ | dh_install --sourcedir=/<>/debian/tmp-single -p sfftw2 | dh_install: warning: Cannot find (any matches for) "usr/lib/lib*.so.*" (tried in /<>/debian/tmp-single, debian/tmp) | | dh_install: warning: sfftw2 missing files: usr/lib/lib*.so.* | dh_install: error: missing files, aborting | make[1]: *** [debian/rules:78: override_dh_install-arch] Error 25 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:14: binary-arch] Error 2 | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 The full build log can be found there: https://buildd.debian.org/fetch.php?pkg=fftw&arch=amd64&ver=2.1.5-5&stamp=1636562013&raw=0
Bug#999822: netopeer2: FBTFS: error: invalid use of undefined type ‘struct nc_reply_error’
Source: netopeer2
Version: 1.1.39-1+b1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
netopeer2 fails to build from source:
| | ^~
| [ 55%] Building C object
cli/CMakeFiles/netopeer2-cli.dir/linenoise/linenoise.c.o
| /<>/cli/commands.c:466:58: error: invalid use of undefined type
‘struct nc_reply_error’
| 466 | fprintf(output, "\tSID: %s\n",
error->err[i].sid);
| | ^~
| /<>/cli/commands.c:468:34: error: invalid use of undefined type
‘struct nc_reply_error’
| 468 | for (j = 0; j < error->err[i].attr_count; ++j) {
| | ^~
| /<>/cli/commands.c:469:69: error: invalid use of undefined type
‘struct nc_reply_error’
| 469 | fprintf(output, "\tbad-attr #%d: %s\n", j + 1,
error->err[i].attr[j]);
| | ^~
| cd /<>/obj-x86_64-linux-gnu/cli && /usr/bin/cc
-I/<>/obj-x86_64-linux-gnu
-I/<>/obj-x86_64-linux-gnu/cli -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time
-D_FORTIFY_SOURCE=2 -DHAVE_MKSTEMPS -Wall -Wextra -std=gnu99 -MD -MT
cli/CMakeFiles/netopeer2-cli.dir/linenoise/linenoise.c.o -MF
CMakeFiles/netopeer2-cli.dir/linenoise/linenoise.c.o.d -o
CMakeFiles/netopeer2-cli.dir/linenoise/linenoise.c.o -c
/<>/cli/linenoise/linenoise.c
| /<>/cli/commands.c:471:34: error: invalid use of undefined type
‘struct nc_reply_error’
| 471 | for (j = 0; j < error->err[i].elem_count; ++j) {
| | ^~
| /<>/cli/commands.c:472:69: error: invalid use of undefined type
‘struct nc_reply_error’
| 472 | fprintf(output, "\tbad-elem #%d: %s\n", j + 1,
error->err[i].elem[j]);
| | ^~
| /<>/cli/commands.c:474:34: error: invalid use of undefined type
‘struct nc_reply_error’
| 474 | for (j = 0; j < error->err[i].ns_count; ++j) {
| | ^~
| /<>/cli/commands.c:475:69: error: invalid use of undefined type
‘struct nc_reply_error’
| 475 | fprintf(output, "\tbad-ns #%d: %s\n", j + 1,
error->err[i].ns[j]);
| | ^~
| /<>/cli/commands.c:477:34: error: invalid use of undefined type
‘struct nc_reply_error’
| 477 | for (j = 0; j < error->err[i].other_count; ++j) {
| | ^~
| /<>/cli/commands.c:478:44: error: invalid use of undefined type
‘struct nc_reply_error’
| 478 | lyxml_print_mem(&str, error->err[i].other[j], 0);
| |^~
| /<>/cli/commands.c: In function ‘cmd_version’:
| /<>/cli/commands.c:2586:47: warning: macro "__DATE__" might
prevent reproducible builds [-Wdate-time]
| 2586 | fprintf(stdout, "Compile time: %s, %s\n", __DATE__, __TIME__);
| | ^~~~
| /<>/cli/commands.c:2586:57: warning: macro "__TIME__" might
prevent reproducible builds [-Wdate-time]
| 2586 | fprintf(stdout, "Compile time: %s, %s\n", __DATE__, __TIME__);
| | ^~~~
| /<>/cli/commands.c: In function ‘cmd_subscribe’:
| /<>/cli/commands.c:4522:25: warning: implicit declaration of
function ‘nc_time2datetime’ [-Wimplicit-function-declaration]
| 4522 | start = nc_time2datetime(t, NULL, NULL);
| | ^~~~
| /<>/cli/commands.c:4522:23: warning: assignment to ‘char *’ from
‘int’ makes pointer from integer without a cast [-Wint-conversion]
| 4522 | start = nc_time2datetime(t, NULL, NULL);
| | ^
| /<>/cli/commands.c:4524:22: warning: assignment to ‘char *’ from
‘int’ makes pointer from integer without a cast [-Wint-conversion]
| 4524 | stop = nc_time2datetime(t, NULL, NULL);
| | ^
| /<>/cli/commands.c:4602:47: warning: passing argument 2 of
‘nc_recv_notif_dispatch’ from incompatible pointer type
[-Wincompatible-pointer-types]
| 4602 | ret = nc_recv_notif_dispatch(session, cli_ntf_clb);
| | ^~~
| | |
| | void (*)(struct
nc_session *, const struct nc_notif *)
| In file included from /usr/include/nc_client.h:32,
| from /<>/cli/commands.c:32:
| /usr/include/libnetconf2/session_client.h:598:16: note: expected ‘void
(*)(struct nc_session *, const struct lyd_node *, const struct lyd_node *)’ but
argument is of type ‘void (*)(st
Bug#999823: liboqs: FBTFS: error: argument 1 of type ‘unsigned char[280]’ with mismatched bound [-Werror=array-parameter=]
Source: liboqs
Version: 0.7.0.15.g9be13d21+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
liboqs fails to build from source:
| /usr/bin/cc -I/<>/obj-aarch64-linux-gnu/include
-I/<>/src/kem/ntru/pqclean_ntruhrss701_clean
-I/<>/src/common/pqclean_shims -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-fvisibility=hidden -mcpu=native -Werror -Wall -Wextra -Wpedantic
-Wstrict-prototypes -Wshadow -Wformat=2 -Wfloat-equal -Wwrite-strings -O3
-fomit-frame-pointer -fdata-sections -ffunction-sections -Wl,--gc-sections
-std=gnu11 -MD -MT
src/kem/ntru/CMakeFiles/ntru_hrss701_clean.dir/pqclean_ntruhrss701_clean/pack3.c.o
-MF
src/kem/ntru/CMakeFiles/ntru_hrss701_clean.dir/pqclean_ntruhrss701_clean/pack3.c.o.d
-o
src/kem/ntru/CMakeFiles/ntru_hrss701_clean.dir/pqclean_ntruhrss701_clean/pack3.c.o
-c /<>/src/kem/ntru/pqclean_ntruhrss701_clean/pack3.c
| /<>/src/kem/ntru/pqclean_ntruhrss701_clean/pack3.c:3:62: error:
argument 1 of type ‘unsigned char[280]’ with mismatched bound
[-Werror=array-parameter=]
| 3 | void PQCLEAN_NTRUHRSS701_CLEAN_poly_S3_tobytes(unsigned char
msg[NTRU_OWCPA_MSGBYTES], const poly *a) {
| |
~~^~~~
| In file included from
/<>/src/kem/ntru/pqclean_ntruhrss701_clean/pack3.c:1:
| /<>/src/kem/ntru/pqclean_ntruhrss701_clean/poly.h:24:62: note:
previously declared as ‘unsigned char[140]’
|24 | void PQCLEAN_NTRUHRSS701_CLEAN_poly_S3_tobytes(unsigned char
msg[NTRU_PACK_TRINARY_BYTES], const poly *a);
| |
~~^~~~
| /<>/src/kem/ntru/pqclean_ntruhrss701_clean/pack3.c:17:79: error:
argument 2 of type ‘const unsigned char[280]’ with mismatched bound
[-Werror=array-parameter=]
|17 | void PQCLEAN_NTRUHRSS701_CLEAN_poly_S3_frombytes(poly *r, const
unsigned char msg[NTRU_OWCPA_MSGBYTES]) {
| |
^~~~
| In file included from
/<>/src/kem/ntru/pqclean_ntruhrss701_clean/pack3.c:1:
| /<>/src/kem/ntru/pqclean_ntruhrss701_clean/poly.h:25:79: note:
previously declared as ‘const unsigned char[140]’
|25 | void PQCLEAN_NTRUHRSS701_CLEAN_poly_S3_frombytes(poly *r, const
unsigned char msg[NTRU_PACK_TRINARY_BYTES]);
| |
^~~~
| cc1: all warnings being treated as errors
| [317/1032] /usr/bin/cc -I/<>/obj-aarch64-linux-gnu/include
-I/<>/src/kem/ntru/pqclean_ntruhrss701_clean
-I/<>/src/common/pqclean_shims -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-fvisibility=hidden -mcpu=native -Werror -Wall -Wextra -Wpedantic
-Wstrict-prototypes -Wshadow -Wformat=2 -Wfloat-equal -Wwrite-strings -O3
-fomit-frame-pointer -fdata-sections -ffunction-sections -Wl,--gc-sections
-std=gnu11 -MD -MT
src/kem/ntru/CMakeFiles/ntru_hrss701_clean.dir/pqclean_ntruhrss701_clean/owcpa.c.o
-MF
src/kem/ntru/CMakeFiles/ntru_hrss701_clean.dir/pqclean_ntruhrss701_clean/owcpa.c.o.d
-o
src/kem/ntru/CMakeFiles/ntru_hrss701_clean.dir/pqclean_ntruhrss701_clean/owcpa.c.o
-c /<>/src/kem/ntru/pqclean_ntruhrss701_clean/owcpa.c
| [318/1032] /usr/bin/cc -I/<>/obj-aarch64-linux-gnu/include
-I/<>/src/kem/kyber/pqcrystals-kyber_common_ref -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-fvisibility=hidden -mcpu=native -Werror -Wall -Wextra -Wpedantic
-Wstrict-prototypes -Wshadow -Wformat=2 -Wfloat-equal -Wwrite-strings -O3
-fomit-frame-pointer -fdata-sections -ffunction-sections -Wl,--gc-sections
-std=gnu11 -MD -MT
src/kem/kyber/CMakeFiles/kyber_common_ref.dir/pqcrystals-kyber_common_ref/aes256ctr.c.o
-MF
src/kem/kyber/CMakeFiles/kyber_common_ref.dir/pqcrystals-kyber_common_ref/aes256ctr.c.o.d
-o
src/kem/kyber/CMakeFiles/kyber_common_ref.dir/pqcrystals-kyber_common_ref/aes256ctr.c.o
-c /<>/src/kem/kyber/pqcrystals-kyber_common_ref/aes256ctr.c
| [319/1032] /usr/bin/cc -I/<>/obj-aarch64-linux-gnu/include
-I/<>/src/kem/kyber/pqcrystals-kyber_kyber512_ref
-I/<>/src/common/pqclean_shims -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-fvisibility=hidden -mcpu=native -Werror -Wall -Wextra -Wpedantic
-Wstrict-prototypes -Wshadow -Wformat=2 -Wfloat-equal -Wwrite-strings -O3
-fomit-frame-pointer -fdata-sections -ffunction-sections -Wl,--gc-sections
-DKYBER_K=2 -std=gnu11 -MD -MT
src/kem/kyber/CMakeFiles/kyber_512_ref.dir/pqcrystals-kyber_kyber512_ref/poly.c.o
-MF
src/kem/kyber/CMakeFiles/kyber_512_ref.dir/pqcrystals-kyber_kyber512_ref/poly.c.o.d
