Bug#969622: gnome-shell-extension-log-out-button: fails to load: TypeError: System._createActionButton is not a function
Package: gnome-shell-extension-log-out-button Version: 1.0.8-1 Severity: serious The "Log Out Button" GNOME shell extension fails to load with GNOME 3.36. When I click the "Show Errors" link in the GNOME shell Looking Glass (type lg into the run dialog, click on Extensions) I see this: TypeError: System._createActionButton is not a function -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-3-amd64 (SMP w/4 CPU threads) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-shell-extension-log-out-button depends on: ii gnome-shell 3.36.5-1 gnome-shell-extension-log-out-button recommends no packages. gnome-shell-extension-log-out-button suggests no packages. -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#969623: gnome-shell-extension-show-ip: load fails: ReferenceError: None is not defined
Package: gnome-shell-extension-show-ip Version: 8-6 Severity: serious I noticed that this extension now fails to load with this error: ReferenceError: None is not defined -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-3-amd64 (SMP w/4 CPU threads) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-shell-extension-show-ip depends on: ii gnome-shell 3.36.5-1 ii gnome-shell-extension-prefs 3.36.5-1 gnome-shell-extension-show-ip recommends no packages. gnome-shell-extension-show-ip suggests no packages. -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed (with 1 error): Re: gnome-shell-extension-weather: fails to load: TypeError: this.actor.reparent is not a function
Processing control commands: > retitle -1 gnome-shell-extension-weather: fails to load: TypeError: > this.actor.reparent is not a function Bug #969273 [gnome-shell-extension-weather] gnome-shell-extension-weather: Error loading the extension. Changed Bug title to 'gnome-shell-extension-weather: fails to load: TypeError: this.actor.reparent is not a function' from 'gnome-shell-extension-weather: Error loading the extension.'. > severity -1 serious Bug #969273 [gnome-shell-extension-weather] gnome-shell-extension-weather: fails to load: TypeError: this.actor.reparent is not a function Severity set to 'serious' from 'important' > usertags -1 + bittenby Unknown command or malformed arguments to command. -- 969273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969621: propellor: Propellor fails to find location of built propellor binary
Package: propellor Version: 5.10.2-2 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, While trying to test propellor on a Debian Testing system, I discovered my changes were not taking effect. Eventually I discovered that the haskell build system was writing the new binary into ./dist- newstyle/build/x86_64-linux/ghc-8.8.3/propellor-5.10.2/x/propellor/build/propellor/propellor While Bootstrap.hs was assuing the binary would be built in dist/build/propellor-config/propellor-config See https://propellor.branchable.com/forum/Bootstrapping_with_Cabal_on_Archlinux_fails/ Which also includes a report from someone else about Propellor not working on Debian Testing. There appear to be patches in 5.11, but they're spread out over several commits, and I'm not sure which ones to pull. I tried to just build 5.11, but export CABAL=./Setup breaks the build, the makefile assumes ./Setup sdist -o - will output a compressed stream, but the Setup file built in an unstable schroot doesn't support that feature. Thanks Diane -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'oldstable-debug'), (500, 'testing'), (500, 'stable'), (110, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-3-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages propellor depends on: ii cabal-install 3.0.0.0-3 ii ghc [libghc-transformers-dev] 8.8.3-3 ii git1:2.28.0-1 ii libc6 2.30-4 ii libffi73.3-4 ii libghc-ansi-terminal-dev 0.10.3-1 ii libghc-async-dev 2.2.2-2 ii libghc-exceptions-dev 0.10.4-1 ii libghc-hashable-dev1.3.0.0-2 ii libghc-hslogger-dev1.3.1.0-1 ii libghc-ifelse-dev 0.85-16 pn libghc-mtl-dev ii libghc-network-dev 3.1.1.1-1 ii libghc-propellor-dev 5.10.2-2 ii libghc-split-dev 0.2.3.4-1 pn libghc-text-dev ii libghc-type-errors-dev 0.2.0.0-3 ii libghc-unix-compat-dev 0.5.2-2 ii libgmp10 2:6.2.0+dfsg-6 propellor recommends no packages. propellor suggests no packages. -- no debconf information
Processed: bug 943032 is forwarded to https://github.com/mnauw/git-remote-hg/issues/34
Processing commands for cont...@bugs.debian.org: > forwarded 943032 https://github.com/mnauw/git-remote-hg/issues/34 Bug #943032 [src:git-remote-hg] git-remote-hg: Python2 removal in sid/bullseye Set Bug forwarded-to-address to 'https://github.com/mnauw/git-remote-hg/issues/34'. > thanks Stopping processing here. Please contact me if you need assistance. -- 943032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969608: ncbi-blast+: regressions on armhf
Steve Langasek writes: > I have reproduced the ncbi-blast+ autopkgtest failure on abel.debian.org, > confirming this is not a problem specific to the Debian build. Thanks for the report. I have a solid idea for a patch that should help here (and on 32-bit architectures in general), and will test it out when I get a chance, probably tomorrow or Monday. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#969559: Info received (Bug#969559: curl segmentation fauls on any https URL)
I have checked my pkcs11 device and it is functioning properly, but curl still crashes. Fortunately I can just use 'wget' until this is fixed. -- Bruce Momjian https://momjian.us EnterpriseDB https://enterprisedb.com The usefulness of a cup is in its emptiness, Bruce Lee
Bug#969616: rust-tui builds 5 uninstallable packages
Source: rust-tui Version: 0.8.0-2 Severity: grave User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu groovy The rust-tui source package builds 5 different binary packages all of which has unsatisfiable dependencies, as reported by britney: librust-tui+crossterm-dev/amd64 has unsatisfiable dependency librust-tui+curses-dev/amd64 has unsatisfiable dependency librust-tui+easycurses-dev/amd64 has unsatisfiable dependency librust-tui+pancurses-dev/amd64 has unsatisfiable dependency librust-tui+rustbox-dev/amd64 has unsatisfiable dependency None of rust-crossterm, rust-easycurses, rust-pancurses, or rust-rustbox appear anywhere in Debian, including in the NEW queue. We should not have uninstallable packages in the archive. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#969103: [Pkg-emacsen-addons] Bug#969103: seq.el: requesting an update to the version in GNU ELPA
Hello, On Fri 04 Sep 2020 at 11:57AM GMT, Stefan Kangas wrote: > Lev Lamberov writes: > >> I've applied your patch to seq from the ELPA git repository and tested >> it both in GNU Emacs 24 and GNU Emacs 25 from the Debian archive >> (stretch release). Here is the output: > > Thanks for testing! > > I've now pushed the patch to the GNU ELPA repository. Please allow for > at least 24 hours for the new package to get automatically uploaded on > elpa.gnu.org. Thanks for your help with this. Debian has been updated. -- Sean Whitton signature.asc Description: PGP signature
Processed: Re: Bug#937665: Waiting for Python 2-depending reverse dependencies
Processing control commands: > unblock -1 by 933750 Bug #937665 [src:python-coverage] python-coverage: Python2 removal in sid/bullseye 937665 was blocked by: 938009 938407 936340 937609 937159 938300 938011 937989 936335 937157 936745 938244 943014 936296 938278 936473 937516 938676 937580 937666 938102 937232 936120 938408 933750 939481 936560 936585 937823 937725 937718 937665 was blocking: 937695 938168 967200 Removed blocking bug(s) of 937665: 933750 > tags -1 + pending Bug #937665 [src:python-coverage] python-coverage: Python2 removal in sid/bullseye Ignoring request to alter tags of bug #937665 to the same tags previously set > outlook -1 0 Outlook replaced with message bug 937665 message 80 -- 937665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937665: Waiting for Python 2-depending reverse dependencies
Control: unblock -1 by 933750 Control: tags -1 + pending Control: outlook -1 0 We will ignore the remaining reverse-dependencies. This release will break those reverse-dependencies, but they have already lost other Python dependencies which drop Python 2 support. On 17-Aug-2020, Jann Haber wrote: > paleomix was removed from testing in May for not supporting Python > 3. Since then, the following b-ds of paleomix have already been > dropped: python-nose, python-flexmock, python-pysam and > python-setproctitle - so it is already impossible to be build from > source in sid. That convinces me, then. I will remove that block on this bug report, and proceed with the Coverage 5.1 packaging. Thanks for investigating and documenting what you found. -- \ “I bought some batteries, but they weren't included; so I had | `\to buy them again.” —Steven Wright | _o__) | Ben Finney signature.asc Description: PGP signature
Bug#969615: rust-unicode-script has unsatisfiable dependency on non-existent rust-harfbuzz-sys
Source: rust-unicode-script Version: 0.3.0-2 Severity: grave User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu groovy The librust-unicode-script+harfbuzz-dev package is uninstallable because it depends on librust-harfbuzz-sy-0.3+default-dev, which does not exist anywhere in Debian, including in the NEW queue. We should not have uninstallable packages in the archive. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#969103: [Pkg-emacsen-addons] Bug#969103: elpa-flycheck: causes leak in GNU Emacs 27.1
Hello Lev, Thanks for the report and testing. New version uploaded. -- Sean Whitton signature.asc Description: PGP signature
Processed: closing 966835
Processing commands for cont...@bugs.debian.org: > close 966835 0.19.1-1 Bug #966835 [src:haskell-shake] haskell-shake needs source upload for new haddock interface The source 'haskell-shake' and version '0.19.1-1' do not appear to match any binary packages Marked as fixed in versions haskell-shake/0.19.1-1. Bug #966835 [src:haskell-shake] haskell-shake needs source upload for new haddock interface Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 966835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969609: rust-zstd: unbuildable, uninstallable, depends on non-existent rust-zstd-safe
Source: rust-zstd Version: 0.5.1-1 Severity: grave The rust-zstd package has both a dependency and a build-dependency on librust-zstd-safe-2.0.3+experimental-dev, which does not exist anywhere in Debian. Presumably it would be built by a rust-zstd-safe package, but no such package exists, including in the Debian NEW queue. The binaries of rust-zstd that are in Debian were clearly not built on the autobuilders, and all other architectures besides amd64 are unable to build this package. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#957685: marked as done (pipewire: ftbfs with GCC-10)
Your message dated Sat, 05 Sep 2020 22:00:13 +
with message-id
and subject line Bug#957685: fixed in pipewire 0.3.10-1
has caused the Debian Bug report #957685,
regarding pipewire: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
957685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pipewire
Version: 0.2.7-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/pipewire_0.2.7-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.
To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html
[...]
Configuring pipewire-cli.1.xml using configuration
Configuring pipewire-monitor.1.xml using configuration
Program pw-uninstalled.sh found: YES (/<>/pw-uninstalled.sh)
Build targets in project: 54
WARNING: Project specifies a minimum meson_version '>= 0.47.0' but uses
features which were added in newer versions:
* 0.50.0: {'install arg in configure_file'}
Option buildtype is: plain [default: debugoptimized]
Found ninja-1.10.0 at /usr/bin/ninja
make[1]: Leaving directory '/<>'
dh_auto_build
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v
[1/170] cc -Ispa/plugins/alsa/b6cb841@@spa-alsa@sha -Ispa/plugins/alsa
-I../spa/plugins/alsa -Ispa/include -I../spa/include -fdiagnostics-color=always
-pipe -D_FILE_OFFSET_BITS=64 -std=gnu99 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MQ
'spa/plugins/alsa/b6cb841@@spa-alsa@sha/alsa.c.o' -MF
'spa/plugins/alsa/b6cb841@@spa-alsa@sha/alsa.c.o.d' -o
'spa/plugins/alsa/b6cb841@@spa-alsa@sha/alsa.c.o' -c ../spa/plugins/alsa/alsa.c
[2/170] cc -Ispa/plugins/alsa/b6cb841@@spa-alsa@sha -Ispa/plugins/alsa
-I../spa/plugins/alsa -Ispa/include -I../spa/include -fdiagnostics-color=always
-pipe -D_FILE_OFFSET_BITS=64 -std=gnu99 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MQ
'spa/plugins/alsa/b6cb841@@spa-alsa@sha/alsa-monitor.c.o' -MF
'spa/plugins/alsa/b6cb841@@spa-alsa@sha/alsa-monitor.c.o.d' -o
'spa/plugins/alsa/b6cb841@@spa-alsa@sha/alsa-monitor.c.o' -c
../spa/plugins/alsa/alsa-monitor.c
[3/170] cc -Ispa/plugins/alsa/b6cb841@@spa-alsa@sha -Ispa/plugins/alsa
-I../spa/plugins/alsa -Ispa/include -I../spa/include -fdiagnostics-color=always
-pipe -D_FILE_OFFSET_BITS=64 -std=gnu99 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MQ
'spa/plugins/alsa/b6cb841@@spa-alsa@sha/alsa-sink.c.o' -MF
'spa/plugins/alsa/b6cb841@@spa-alsa@sha/alsa-sink.c.o.d' -o
'spa/plugins/alsa/b6cb841@@spa-alsa@sha/alsa-sink.c.o' -c
../spa/plugins/alsa/alsa-sink.c
[4/170] cc -Ispa/plugins/alsa/b6cb841@@spa-alsa@sha -Ispa/plugins/alsa
-I../spa/plugins/alsa -Ispa/include -I../spa/include -fdiagnostics-color=always
-pipe -D_FILE_OFFSET_BITS=64 -std=gnu99 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MQ
'spa/plugins/alsa/b6cb841@@spa-alsa@sha/alsa-source.c.o' -MF
'spa/plugins/alsa/b6cb841@@spa-alsa@sha/alsa-source.c.o.d' -o
'spa/plugins/alsa/b6cb841@@spa-alsa@sha/alsa-source.c.o' -c
../spa/plugins/alsa/alsa-source.c
[5/170] cc -Ispa/plugins/audiomixer/55b85d2@@spa-audiomixer@sha
-Ispa/plugins/audiomixer -I../spa/plugins/audiomixer -Ispa/include
-I../spa/include -fdiagnostics-color=always
Bug#969608: ncbi-blast+: regressions on armhf
Source: ncbi-blast+ Version: 2.10.0-1 Severity: grave User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu groovy Dear maintainers, It appears that ncbi-blast+ 2.10 has regressed on armhf, and is significantly broken. In Ubuntu, all of the autopkgtests triggered by ncbi-blast+ have regressed on this arch, including those of ncbi-blast+ itself: https://autopkgtest.ubuntu.com/packages/n/ncbi-blast+/groovy/armhf https://autopkgtest.ubuntu.com/packages/k/kaptive/groovy/armhf https://autopkgtest.ubuntu.com/packages/r/ruby-crb-blast/groovy/armhf I have reproduced the ncbi-blast+ autopkgtest failure on abel.debian.org, confirming this is not a problem specific to the Debian build. In addition, the python-pyani reverse-dependency fails to build on armhf in both Debian and Ubuntu (the current Debian package was built on the autobuilders against the previous version of ncbi-blast+, but I've reproduced this failure as well in unstable on abel): https://launchpad.net/ubuntu/+source/python-pyani/0.2.10-2/+build/19218920 I think this rises to the level of a grave bug, since armhf is a release architecture and the binaries for this architecture appear to be largely unusable. Either the armhf binaries should be removed or they should be made to work on armhf. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Processed: closing 959555
Processing commands for cont...@bugs.debian.org: > close 959555 Bug #959555 [src:zope.interface] zope.interface: FTBFS: ImportError: cannot import name 'Feature' from 'setuptools' (/usr/lib/python3/dist-packages/setuptools/__init__.py) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 959555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959555 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 959555 in 5.1.0-1
Processing commands for cont...@bugs.debian.org: > fixed 959555 5.1.0-1 Bug #959555 [src:zope.interface] zope.interface: FTBFS: ImportError: cannot import name 'Feature' from 'setuptools' (/usr/lib/python3/dist-packages/setuptools/__init__.py) Marked as fixed in versions zope.interface/5.1.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 959555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959555 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961584: lxc-stop fails with exit code 1
Le mercredi 03 juin 2020 à 10:57:13+0200, Inaki Malerba a écrit :
> El 2/6/20 a las 20:07, Pierre-Elliott Bécue escribió:
> > Could you remove the --quiet bit to see if lxc-stop gives us a bit more
> > intel?
> >
> > If possible, have your testbed call lxc-stop --kill --logpriority trace
> > --logfile /dev/stdout --name ${NAME}, so we can have the most expressive
> > output. But if it's an error, removing the quiet bit could be enough.
> >
> > Thanks.
> >
>
> The POC I attached on a previous email it's not using debci, so you can
> modify the lxc-stop call.
>
> After enabling trace log level, the output is the following:
>
> > Starting LXC network bridge: :Starting LXC autoboot containers: :
> > lxc-stop autopkgtest-stable-amd64 20200603085059.718 TRACEcommands -
> > commands.c:lxc_cmd_rsp_recv:123 - Command "get_init_pid" received response
> > lxc-stop autopkgtest-stable-amd64 20200603085059.718 DEBUGcommands -
> > commands.c:lxc_cmd_rsp_recv:156 - Response data length for command
> > "get_init_pid" is 0
> > lxc-stop autopkgtest-stable-amd64 20200603085059.718 TRACEcommands -
> > commands.c:lxc_cmd:293 - Opened new command socket connection fd 4 for
> > command "get_init_pid"
> > lxc-stop autopkgtest-stable-amd64 20200603085059.719 TRACEcommands -
> > commands.c:lxc_cmd_rsp_recv:123 - Command "get_state" received response
> > lxc-stop autopkgtest-stable-amd64 20200603085059.719 DEBUGcommands -
> > commands.c:lxc_cmd_rsp_recv:156 - Response data length for command
> > "get_state" is 0
> > lxc-stop autopkgtest-stable-amd64 20200603085059.719 TRACEcommands -
> > commands.c:lxc_cmd:293 - Opened new command socket connection fd 4 for
> > command "get_state"
> > lxc-stop autopkgtest-stable-amd64 20200603085059.719 DEBUGcommands -
> > commands.c:lxc_cmd_get_state:656 - Container "autopkgtest-stable-amd64" is
> > in "RUNNING" state
> > lxc-stop autopkgtest-stable-amd64 20200603085059.719 TRACEcommands -
> > commands.c:lxc_cmd_rsp_recv:123 - Command "stop" received response
> > lxc-stop autopkgtest-stable-amd64 20200603085059.719 DEBUGcommands -
> > commands.c:lxc_cmd_rsp_recv:156 - Response data length for command "stop"
> > is 0
> > lxc-stop autopkgtest-stable-amd64 20200603085059.719 TRACEcommands -
> > commands.c:lxc_cmd:293 - Opened new command socket connection fd 4 for
> > command "stop"
> > lxc-stop autopkgtest-stable-amd64 20200603085059.720 ERRORcommands -
> > commands.c:lxc_cmd_stop:707 - No such file or directory - Failed to stop
> > container "autopkgtest-stable-amd64"
> > lxc-stop: autopkgtest-stable-amd64: commands.c: lxc_cmd_stop: 707 No such
> > file or directory - Failed to stop container "autopkgtest-stable-amd64"
LXC's devs told me that 4.0.4 should solve it. I'm uploading this
release now. Please don't hesitate to tell me if it helps.
--
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.
signature.asc
Description: PGP signature
Bug#964973: mesa-opencl-icd: Applications using OpenCL crash with : CommandLine Error: Option 'polly' registered more than once!
Package: libreoffice Version: 1:7.0.1-1 Followup-For: Bug #964973 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello! I just got a hit by this bugs while trying to start LibreOffice: #954849 does not start: LLVM ERROR: inconsistency in registered CommandLine options #964973 mesa-opencl-icd: Applications using OpenCL crash with : CommandLine Error: Option 'polly' registered more than once! #965178 opencl support is broken: LLVM ERROR: inconsistency in registered CommandLine option #965310 hwloc: lstopo crash with: CommandLine Error: Option 'polly' registered more than once! It is not possible to start LibreOffice anymore! Also it removes completly my working OpenOffice v4.1.7 installation! :( Not so nice. - -- Yours sincerely Joerg Schiermeier - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-3-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.utf-8, LC_CTYPE=de_DE.utf-8 (charmap=UTF-8), LANGUAGE=de:en_GB Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libreoffice depends on: ii libreoffice-base1:7.0.1-1 ii libreoffice-calc1:7.0.1-1 ii libreoffice-core1:7.0.1-1 ii libreoffice-draw1:7.0.1-1 ii libreoffice-impress 1:7.0.1-1 ii libreoffice-math1:7.0.1-1 ii libreoffice-report-builder-bin 1:7.0.1-1 ii libreoffice-writer 1:7.0.1-1 ii python3-uno 1:7.0.1-1 Versions of packages libreoffice recommends: pn fonts-crosextra-caladea pn fonts-crosextra-carlito pn fonts-dejavu pn fonts-liberation pn fonts-liberation2 pn fonts-linuxlibertine pn fonts-noto-core pn fonts-noto-extra pn fonts-noto-mono pn fonts-noto-ui-core pn fonts-sil-gentium-basic ii libreoffice-java-common 1:7.0.1-1 ii libreoffice-nlpsolver 0.9+LibO7.0.1-1 ii libreoffice-report-builder 1:7.0.1-1 ii libreoffice-script-provider-bsh 1:7.0.1-1 ii libreoffice-script-provider-js 1:7.0.1-1 ii libreoffice-script-provider-python 1:7.0.1-1 ii libreoffice-sdbc-mysql 1:7.0.1-1 ii libreoffice-sdbc-postgresql 1:7.0.1-1 ii libreoffice-wiki-publisher 1.2.0+LibO7.0.1-1 Versions of packages libreoffice suggests: ii cups-bsd 2.3.3-3 pn default-jre | java8-runtime | jre pn firefox-esr | thunderbird | firefox pn ghostscript pn gnupg pn gpa pn gstreamer1.0-libav pn gstreamer1.0-plugins-bad pn gstreamer1.0-plugins-base pn gstreamer1.0-plugins-good pn gstreamer1.0-plugins-ugly pn hunspell-dictionary pn hyphen-hyphenation-patterns pn imagemagick | graphicsmagick-imagemagick-compat pn libgl1 pn libofficebean-java ii libreoffice-help-de [libreoffice-help]1:7.0.1-1 ii libreoffice-help-en-gb [libreoffice-help] 1:7.0.1-1 ii libreoffice-help-es [libreoffice-help]1:7.0.1-1 ii libreoffice-help-nl [libreoffice-help]1:7.0.1-1 ii libreoffice-l10n-de [libreoffice-l10n]1:7.0.1-1 ii libreoffice-l10n-en-gb [libreoffice-l10n] 1:7.0.1-1 ii libreoffice-l10n-es [libreoffice-l10n]1:7.0.1-1 ii libreoffice-l10n-nl [libreoffice-l10n]1:7.0.1-1 ii libreoffice-librelogo 1:7.0.1-1 ii libreoffice-lightproof-en [libreoffice-grammarcheck] 0.4.3+1.6-2 ii libreoffice-plasma1:7.0.1-1 pn libsane pn libxrender1 pn myspell-dictionary pn mythes-thesaurus pn openclipart2-libreoffice | openclipart-libreoffice pn pstoedit pn unixodbc Versions of packages libreoffice-core depends on: pn fontconfig ii fonts-opensymbol2:102.11+LibO7.0.1-1 pn libboost-locale1.71.0
Processed: src:minimap2: fails to migrate to testing for too long: FTBFS on multiple arches
Processing control commands: > close -1 2.17+dfsg-11 Bug #969596 [src:minimap2] src:minimap2: fails to migrate to testing for too long: FTBFS on multiple arches Marked as fixed in versions minimap2/2.17+dfsg-11. Bug #969596 [src:minimap2] src:minimap2: fails to migrate to testing for too long: FTBFS on multiple arches Marked Bug as done -- 969596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969596: src:minimap2: fails to migrate to testing for too long: FTBFS on multiple arches
Source: minimap2 Version: 2.17+dfsg-9 Severity: serious Control: close -1 2.17+dfsg-11 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:minimap2 in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=minimap2 signature.asc Description: OpenPGP digital signature
Bug#969534: marked as done (ffc autopkg test failure)
Your message dated Sat, 05 Sep 2020 16:50:51 + with message-id and subject line Bug#969534: fixed in ffc 2019.2.0~git20200123.6b621eb-3 has caused the Debian Bug report #969534, regarding ffc autopkg test failure to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 969534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ffc Version: 2019.2.0~git20200123.6b621eb-2 Severity: serious Tags: sid bullseye seen in unstable: autopkgtest [10:34:13]: test test-ffc: [--- running install running bdist_egg running egg_info creating fenics_ffc_factory.egg-info writing fenics_ffc_factory.egg-info/PKG-INFO writing dependency_links to fenics_ffc_factory.egg-info/dependency_links.txt writing top-level names to fenics_ffc_factory.egg-info/top_level.txt writing manifest file 'fenics_ffc_factory.egg-info/SOURCES.txt' reading manifest file 'fenics_ffc_factory.egg-info/SOURCES.txt' writing manifest file 'fenics_ffc_factory.egg-info/SOURCES.txt' installing library code to build/bdist.linux-x86_64/egg running install_lib running build_ext creating tmp x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.8 -c /tmp/tmpsyqpzq35.cpp -o tmp/tmpsyqpzq35.o -std=c++14 x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.8 -c /tmp/tmpxavabf_a.cpp -o tmp/tmpxavabf_a.o -fvisibility=default building 'ffc_factory' extension creating build creating build/temp.linux-x86_64-3.8 x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/lib/python3/dist-packages/ffc/backends/ufc -I/usr/lib/python3/dist-packages/pybind11/include -I/usr/lib/python3/dist-packages/pybind11/include -I/usr/include/python3.8 -c interface.cpp -o build/temp.linux-x86_64-3.8/interface.o -DVERSION_INFO="0.0.1" -std=c++14 -fvisibility=default x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/lib/python3/dist-packages/ffc/backends/ufc -I/usr/lib/python3/dist-packages/pybind11/include -I/usr/lib/python3/dist-packages/pybind11/include -I/usr/include/python3.8 -c dofmap.cpp -o build/temp.linux-x86_64-3.8/dofmap.o -DVERSION_INFO="0.0.1" -std=c++14 -fvisibility=default x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/lib/python3/dist-packages/ffc/backends/ufc -I/usr/lib/python3/dist-packages/pybind11/include -I/usr/lib/python3/dist-packages/pybind11/include -I/usr/include/python3.8 -c finite_element.cpp -o build/temp.linux-x86_64-3.8/finite_element.o -DVERSION_INFO="0.0.1" -std=c++14 -fvisibility=default x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/lib/python3/dist-packages/ffc/backends/ufc -I/usr/lib/python3/dist-packages/pybind11/include -I/usr/lib/python3/dist-packages/pybind11/include -I/usr/include/python3.8 -c finite_element_bindings.cpp -o build/temp.linux-x86_64-3.8/finite_element_bindings.o -DVERSION_INFO="0.0.1" -std=c++14 -fvisibility=default creating build/lib.linux-x86_64-3.8 x86_64-linux-gnu-g++ -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro -g -fwrapv -O2 -Wl,-z,relro -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-3.8/interface.o build/temp.linux-x86_64-3.8/dofmap.o
Bug#969548: marked as done (setuptools breaks ffc autopkgtest: No module named 'ffc_factory')
Your message dated Sat, 05 Sep 2020 16:50:51 + with message-id and subject line Bug#969534: fixed in ffc 2019.2.0~git20200123.6b621eb-3 has caused the Debian Bug report #969534, regarding setuptools breaks ffc autopkgtest: No module named 'ffc_factory' 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.) -- 969534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: setuptools, ffc Control: found -1 setuptools/49.3.1-2 Control: found -1 ffc/2019.2.0~git20200123.6b621eb-2 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of setuptools the autopkgtest of ffc fails in testing when that autopkgtest is run with the binary packages of setuptools from unstable. It passes when run with only packages from testing. In tabular form: passfail setuptools from testing49.3.1-2 ffcfrom testing2019.2.0~git20200123.6b621eb-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 setuptools 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=setuptools https://ci.debian.net/data/autopkgtest/testing/amd64/f/ffc/6909276/log.gz ERRORS _ ERROR collecting ufc/finite_element/test_evaluate.py _ ImportError while importing test module '/tmp/autopkgtest-lxc.cxd5j8yt/downtmp/build.Ndr/src/test/unit/ufc/finite_element/test_evaluate.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: unit/ufc/finite_element/test_evaluate.py:25: in import ffc_factory E ModuleNotFoundError: No module named 'ffc_factory' !!! Interrupted: 1 errors during collection === 1 error in 1.40 seconds autopkgtest [10:34:49]: test test-ffc: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: ffc Source-Version: 2019.2.0~git20200123.6b621eb-3 Done: Drew Parsons We believe that the bug you reported is fixed in the latest version of ffc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated ffc 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: Sun, 06 Sep 2020 00:21:29 +0800 Source: ffc Architecture: source Version: 2019.2.0~git20200123.6b621eb-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Drew Parsons Closes: 969534 Changes: ffc (2019.2.0~git20200123.6b621eb-3) unstable; urgency=medium . * setuptools is deprecated for installation to non-system dirs, instead use pip to build and locally install ffc_factory for tests. Closes: #969534. - allow stderr in tests (pip sends log messages to stderr) * debhelper compatibility level 13 Checksums-Sha1: b1ac0028b8dec4150ec0e503d2c70596f8898e68 2278 ffc_2019.2.0~git20200123.6b621eb-3.dsc 5ef9f362d2626457e4f3f83959dfe3566d4c4994 9712 ffc_2019.2.0~git20200123.6b621eb-3.debian.tar.xz Checksums-Sha256: 2503ad89b60db403622702edde513335452d6abdf89bb55d378dcd67b8d1829e 2278 ffc_2019.2.0~git20200123.6b621eb-3.dsc 0388c1881e76cb2cb6ffa3d78f7d81982c3e54bac6e5ba5453b8394a03897593 9712 ffc_2019.2.0~git20200123.6b621eb-3.debian.tar.xz Files: 11858c95e4d6a832b42b9d7899852a6b 2278 python optional ffc_2019.2.0~git20200123.6b621eb-3.dsc 1eab850a65b383edeebc54c643445955 9712
Bug#969592: sane-backends: FTBFS: +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25
Source: sane-backends Version: 1.0.27-3.2 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) sane-backends FTBFS on armel and armhf: | @@ -7204,7 +7151,7 @@ | sanei_pp_outb_addr@Base 1.0.25 | sanei_pp_outb_ctrl@Base 1.0.25 | sanei_pp_outb_data@Base 1.0.25 | - sanei_pp_outb_epp@Base 1.0.25 | +#MISSING: 1.0.27# sanei_pp_outb_epp@Base 1.0.25 | sanei_pp_release@Base 1.0.25 | sanei_pp_set_datadir@Base 1.0.25 | sanei_pp_setmode@Base 1.0.25 | dh_makeshlibs: error: failing due to earlier errors | make[1]: *** [debian/rules:139: override_dh_makeshlibs-arch] Error 25 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:25: binary-arch] Error 2 See https://buildd.debian.org/status/fetch.php?pkg=sane-backends=armel=1.0.27-3.2%2Bb2=1599315993=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#966353: FTBFS: guile segfaults when run to collect docs
On Mon, Jul 27, 2020 at 09:09:45PM +1000, Stuart Prescott wrote: >... > guile segfaults as soon as it is started (with or without docs on stdin). > The backtrace is as follows in case the problem jumps out. > > /build/lilypond-jv5Dao/lilypond-2.20.0/guile18/libguile/.libs$ > LD_LIBRARY_PATH=. gdb ./guile > Reading symbols from ./guile... > (gdb) r > Starting program: > /build/lilypond-jv5Dao/lilypond-2.20.0/guile18/libguile/.libs/guile > > Program received signal SIGSEGV, Segmentation fault. > scm_mark_locations (x=0x7fffe948, n=18446744073709551562) at gc-mark.c:435 > 435 SCM obj = * (SCM *) [m]; >... lilypond started to FTBFS when libgc 8 entered unstable. > regards > Stuart cu Adrian
Bug#969570: marked as done (ulfius: FTBFS on s390x)
Your message dated Sat, 5 Sep 2020 17:54:00 +0200
with message-id <0abc14f9-6e93-17c6-cce0-17f0656d4...@debian.org>
and subject line Re: Bug#969570: ulfius: FTBFS on s390x
has caused the Debian Bug report #969570,
regarding ulfius: FTBFS on s390x
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.)
--
969570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ulfius
Version: 2.6.9-1
Severity: serious
Hello, your package FTBFS on s390x. Please have a look if possible
gmake[4]: Leaving directory '/<>/build'
gmake[3]: Leaving directory '/<>/build'
Start 1: core
1/4 Test #1: core . Passed0.08 sec
Start 2: u_map
2/4 Test #2: u_map Passed0.02 sec
Start 3: framework
3/4 Test #3: framework ***Failed0.65 sec
Running suite(s): Ulfius framework function tests
86%: Checks: 15, Failures: 2, Errors: 0
/<>/test/framework.c:630:P:test_ulfius_framework:test_ulfius_simple_endpoint:0:
Passed
/<>/test/framework.c:767:P:test_ulfius_framework:test_ulfius_net_type_endpoint:0:
Passed
/<>/test/framework.c:845:P:test_ulfius_framework:test_ulfius_endpoint_parameters:0:
Passed
/<>/test/framework.c:896:P:test_ulfius_framework:test_ulfius_endpoint_injection:0:
Passed
/<>/test/framework.c:971:P:test_ulfius_framework:test_ulfius_endpoint_multiple:0:
Passed
/<>/test/framework.c:994:P:test_ulfius_framework:test_ulfius_endpoint_stream:0:
Passed
/<>/test/framework.c:1024:P:test_ulfius_framework:test_ulfius_utf8_not_ignored:0:
Passed
/<>/test/framework.c:1056:P:test_ulfius_framework:test_ulfius_utf8_ignored:0:
Passed
/<>/test/framework.c:1083:P:test_ulfius_framework:test_ulfius_endpoint_callback_position:0:
Passed
/<>/test/framework.c:1115:P:test_ulfius_framework:test_ulfius_MHD_set_response_with_other_free:0:
Passed
/<>/test/framework.c:1145:F:test_ulfius_framework:test_ulfius_send_smtp:0:
Assertion 'ulfius_send_smtp_email("localhost", 2525, 0, 0, ((void *)0), ((void
*)0), "from", "to", "cc", "bcc", "subject", "mail body") == 0' failed:
ulfius_send_smtp_email("localhost", 2525, 0, 0, ((void *)0), ((void *)0),
"from", "to", "cc", "bcc", "subject", "mail body") == 5, 0 == 0
/<>/test/framework.c:1169:F:test_ulfius_framework:test_ulfius_send_rich_smtp:0:
Assertion 'ulfius_send_smtp_rich_email("localhost", 2526, 0, 0, ((void *)0),
((void *)0), "from", "to", "cc", "bcc", "text/ulfius; charset=utf-42",
"subject", "mail body") == 0' failed: ulfius_send_smtp_rich_email("localhost",
2526, 0, 0, ((void *)0), ((void *)0), "from", "to", "cc", "bcc", "text/ulfius;
charset=utf-42", "subject", "mail body") == 5, 0 == 0
/<>/test/framework.c:1208:P:test_ulfius_framework:test_ulfius_follow_redirect:0:
Passed
/<>/test/framework.c:1230:P:test_ulfius_framework:test_ulfius_server_ca_trust:0:
Passed
/<>/test/framework.c:1306:P:test_ulfius_framework:test_ulfius_client_certificate:0:
Passed
Start 4: websocket
4/4 Test #4: websocket Passed3.04 sec
75% tests passed, 1 tests failed out of 4
Total Test time (real) = 3.78 sec
The following tests FAILED:
3 - framework (Failed)
Errors while running CTest
make[2]: *** [Makefile:118: test] Error 8
make[2]: Leaving directory '/<>/build'
make[1]: *** [debian/rules:29: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:11: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
thanks
G.
--- End Message ---
--- Begin Message ---
Hello,
On Sat, 5 Sep 2020 08:17:49 -0400 Nicolas Mora wrote:
> Hello,
>
> Le 20-09-05 à 03 h 42, Gianfranco Costamagna a écrit :>
> > Hello, your package FTBFS on s390x. Please have a look if possible
> >
> [...]
> > Start 3: framework
> > 3/4 Test #3: framework ***Failed0.65 sec
> > Running suite(s): Ulfius framework function tests
> > 86%: Checks: 15, Failures: 2, Errors: 0
> [...]
> > /<>/test/framework.c:1145:F:test_ulfius_framework:test_ulfius_send_smtp:0:
> > Assertion 'ulfius_send_smtp_email("localhost", 2525, 0, 0, ((void *)0),
> > ((void *)0), "from", "to", "cc", "bcc", "subject", "mail body") == 0'
> > failed: ulfius_send_smtp_email("localhost", 2525, 0, 0, ((void *)0), ((void
> > *)0), "from", "to", "cc", "bcc", "subject", "mail body") == 5, 0 == 0
> > /<>/test/framework.c:1169:F:test_ulfius_framework:test_ulfius_send_rich_smtp:0:
> > Assertion 'ulfius_send_smtp_rich_email("localhost", 2526, 0, 0, ((void
> >
Bug#969559: curl segmentation fauls on any https URL
On Sat, Sep 5, 2020 at 03:50:20PM +0200, Bernhard Übelacker wrote:
> Dear Maintainer,
> I tried to reproduce this fault, but did not get a segfault.
>
> However, I think the backtrace points to these lines:
>
> (gdb) bt
> #0 0x7769dbce in int_ctx_new () at ../crypto/evp/pmeth_lib.c:160
> #1 0x7769dcfa in EVP_PKEY_CTX_new () at
> ../crypto/evp/pmeth_lib.c:245
> #2 0x77698d44 in do_sigver_init () at ../crypto/evp/m_sigver.c:29
> #3 0x77698eab in EVP_DigestVerifyInit () at
> ../crypto/evp/m_sigver.c:97
> #4 0x775bc7d2 in ASN1_item_verify () at
> ../crypto/asn1/a_verify.c:148
> #5 0x77722490 in X509_verify () at ../crypto/x509/x_all.c:26
> ...
>
>
> https://sources.debian.org/src/openssl/1.1.1d-0+deb10u3/crypto/evp/pmeth_lib.c/#L160
>
> 159 if (pmeth->init) {
> 160 if (pmeth->init(ret) <= 0) {
> 161 ret->pmeth = NULL;
>
> As there is a check for pmeth->init being non-null, I guess
> it contains for some reason an invalid pointer.
>
>
> @Bruce Momjian,
> maybe you could install the following debug symbols packages
> `curl-dbgsym libcurl4-dbgsym libssl1.1-dbgsym` from the dbgsym
> repository described here:
>
> https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols
>
> Then run a new gdb session and when the segfault appears
> please run these commands in gdb:
> print pmeth->init
> bt full 5
Sure, here it is:
(gdb) run https://google.com
Starting program: /usr/bin/curl https://google.com
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x76730700 (LWP 30481)]
[Thread 0x76730700 (LWP 30481) exited]
Thread 1 "curl" received signal SIGSEGV, Segmentation fault.
0x77679bce in int_ctx_new (pkey=pkey@entry=0x556035a0,
e=0x555bd8d0, e@entry=0x0, id=, id@entry=-1) at
../crypto/evp/pmeth_lib.c:160
160 ../crypto/evp/pmeth_lib.c: No such file or directory.
(gdb) print pmeth->init
$1 = (int (*)(EVP_PKEY_CTX *)) 0xf0e0d0c0b0a0908
(gdb) bt full 5
#0 0x77679bce in int_ctx_new (pkey=pkey@entry=0x556035a0,
e=0x555bd8d0, e@entry=0x0, id=, id@entry=-1) at
../crypto/evp/pmeth_lib.c:160
ret = 0x55609810
pmeth = 0x555eaaf0
#1 0x77679cfa in EVP_PKEY_CTX_new
(pkey=pkey@entry=0x556035a0, e=e@entry=0x0) at ../crypto/evp/pmeth_lib.c:245
No locals.
#2 0x77674d44 in do_sigver_init (ctx=ctx@entry=0x556034c0,
pctx=pctx@entry=0x0, type=type@entry=0x777b1fc0 , e=e@entry=0x0,
pkey=pkey@entry=0x556035a0, ver=ver@entry=1)
at ../crypto/evp/m_sigver.c:29
No locals.
#3 0x77674eab in EVP_DigestVerifyInit
(ctx=ctx@entry=0x556034c0, pctx=pctx@entry=0x0,
type=type@entry=0x777b1fc0 , e=e@entry=0x0,
pkey=pkey@entry=0x556035a0)
at ../crypto/evp/m_sigver.c:97
No locals.
#4 0x775987d2 in ASN1_item_verify (it=0x777c3e80
, a=a@entry=0x555ff698,
signature=signature@entry=0x555ff6a8, asn=asn@entry=0x555ff610,
pkey=0x556035a0)
at ../crypto/asn1/a_verify.c:148
type = 0x777b1fc0
ctx = 0x556034c0
buf_in = 0x0
ret = -1
inl = 0
mdnid = 672
pknid = 6
inll = 0
(More stack frames follow...)
I also got this output:
gdb) print *pmeth
$8 = {pkey_id = 50462976, flags = 117835012, init = 0xf0e0d0c0b0a0908,
copy = 0x1716151413121110, cleanup = 0x1f1e1d1c1b1a1918, paramgen_init =
0x98c476a19fc273a5, paramgen = 0x9cc072a593ce7fa9,
keygen_init = 0xdabe4402cda85116, keygen = 0xdeba4006c1a45d1a,
sign_init = 0x681bf10ff0df87ae, sign = 0x6715fc03fbd58ea6, verify_init =
0x924fa56f48f1e16d, verify = 0x8d51b87353ebf875,
verify_recover_init = 0x1799a7c97f8256c6, verify_recover =
0x8b59d56cec4c296f, signctx_init = 0xe7754752753ae23d, signctx =
0x39cf0754b49ebf27, verifyctx_init = 0x48097bc25f90dc0b,
verifyctx = 0x2f1c87c1a44552ad, encrypt_init = 0x87d3b21760a6f545,
encrypt = 0xa820a64334d0d30, decrypt_init = 0x54feb4be1cf7cf7c, decrypt =
0xdfa761d2f0bbe613, derive_init = 0x7929a8e7fefa1af0,
derive = 0x40e6afb34a64a5d7, ctrl = 0x2500f59b71fe4125, ctrl_str =
0xa1c725ad5bb1388, digestsign = 0xe04ff2a999665a4e, digestverify =
0xeacdf8cdaa2b577e, check = 0xe97909bfcc79fc24,
public_check = 0x36de686d3cc21a37, param_check = 0xd, digest_custom =
0x7758ac80 }
(gdb) print pmeth->init[0]
Cannot access memory at address 0xf0e0d0c0b0a0908
(gdb) print *(pmeth->init)
Cannot access memory at address
Bug#969260: openfjx: FTBFS (gstreamer)
Hi Chris! On Sat, Sep 05, 2020 at 05:43:17AM +, Chris Knadle wrote: > Chris Knadle: > > For what it's worth, I used a clean cowbuilder sid chroot that was fully > > upgraded to build openjfx 11.0.7+0-4 and the package built fine. The build > > log > > is about 808kB -- I'll send it to the bug report if desired. Offhand I'm not > > sure what's going on either. It's probably wishful thinking that the > > cowbuilder > > build log will be comparable to the buildd build logs, but I'll have a look. > > Okay, I've compared the cowbuilder logs and the buildd logs and there are a > number of differences, and to me it looks like buildd might be using gcc-10 > where my cowbuilder build may not be. The buildd logs show many warning/error > lines of variables "first defined here" and that's indicative of a gcc-10 > problem, along with many other errors and warnings that the cowbuilder build > didn't show. > > I was given some hints about this in bug #957546: > >Common build failures are new warnings resulting in build failures with >-Werror turned on, or new/dropped symbols in Debian symbols files. >For other C/C++ related build failures see the porting guide at >http://gcc.gnu.org/gcc-10/porting_to.html Thank you for taking a look at this. I suspect that you're on to something with gcc-10, but if that's the case, I'm worried about my entire build toolchain with respect to gcc-10 bugs. Just to be sure, I created a fresh chroot with: sudo sbuild-createchroot sid /path/to/chroot And the package still builds correctly for me, and "gcc -v" in that chroot shows gcc 10.2: $ schroot -c sid-amd64-sbuild -u root (sid-amd64-sbuild)root@lark:~# gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/10/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 10.2.0-6' --with-bugurl=file:///usr/share/doc/gcc-10/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-10 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-10-OZNiN5/gcc-10-10.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-10-OZNiN5/gcc-10-10.2.0/debian/tmp-gcn/usr,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 10.2.0 (Debian 10.2.0-6) So I'm confused about what's different on the buildd system. I will keep poking at it. Cheers, tony
Bug#957813: marked as pending in slimevolley
Control: tag -1 pending Hello, Bug #957813 in slimevolley reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/games-team/slimevolley/-/commit/b01d76ea37e5a14a59bb416efbe03e7322b85090 Fix FTBFS with GCC 10 Closes: #957813 (this message was generated automatically) -- Greetings https://bugs.debian.org/957813
Processed: Bug#957813 marked as pending in slimevolley
Processing control commands: > tag -1 pending Bug #957813 [src:slimevolley] slimevolley: ftbfs with GCC-10 Added tag(s) pending. -- 957813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957813 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969534: ffc autopkg test failure
Source: ffc Followup-For: Bug #969534 Control: forwarded -1 https://github.com/pypa/setuptools/issues/2295 Looks like setuptools is now deprecated upstream. "python3 setup.py install --prefix " no longer installs an importable module (site.py is no longer installed) setuptools upstream recommends using pip instead to install packages from source to non-system directories, see upstream issue #2295.
Processed: Re: ffc autopkg test failure
Processing control commands: > forwarded -1 https://github.com/pypa/setuptools/issues/2295 Bug #969534 [src:ffc] ffc autopkg test failure Bug #969548 [src:ffc] setuptools breaks ffc autopkgtest: No module named 'ffc_factory' Set Bug forwarded-to-address to 'https://github.com/pypa/setuptools/issues/2295'. Set Bug forwarded-to-address to 'https://github.com/pypa/setuptools/issues/2295'. -- 969534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969534 969548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969548 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967198: marked as done (pecomato: Unversioned Python removal in sid/bullseye)
Your message dated Sat, 05 Sep 2020 15:21:39 + with message-id and subject line Bug#967198: fixed in pecomato 0.0.15-11 has caused the Debian Bug report #967198, regarding pecomato: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pecomato Version: 0.0.15-10 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: pecomato Source-Version: 0.0.15-11 Done: Ricardo Mones We believe that the bug you reported is fixed in the latest version of pecomato, 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 967...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ricardo Mones (supplier of updated pecomato 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: Sat, 05 Sep 2020 15:06:05 +0200 Source: pecomato Architecture: source Version: 0.0.15-11 Distribution: unstable Urgency: high Maintainer: Ricardo Mones Changed-By: Ricardo Mones Closes: 937268 967198 Changes: pecomato (0.0.15-11) unstable; urgency=high . * Use packaged instead of embedded obsolete tools (Closes: #967198, #937268) * Bump Standards-Version to 4.5.0 * Bump compat level to 13 * Simplify rules thanks compat level 13 * Add Rules-Requires-Root field * Raised urgency because of RC bug #967198 Checksums-Sha1: 6fb1e315e8f997e27073bf21d1569f141fd4e087 1870 pecomato_0.0.15-11.dsc 6b216ad8b4574a4086a4672497ea6ecd75013b96 6284 pecomato_0.0.15-11.debian.tar.xz cc5bcc6e5418527923771d2eae59efd420322030 8961 pecomato_0.0.15-11_amd64.buildinfo Checksums-Sha256: 87d54d6f9a27f115c9b5a3975319af1840dcf784fde64d067419b3b6caee7cfd 1870 pecomato_0.0.15-11.dsc 17802ddd1686e1f202b70a72c720aaad703687bab7d8a82663fc497b38168636 6284 pecomato_0.0.15-11.debian.tar.xz bef9c5ff16e5554f41032beb515f8844af8b2cf98f9bc2f9cf45f8432c27320f 8961 pecomato_0.0.15-11_amd64.buildinfo Files: 65b72432095bb4d708f82fc34c56681b 1870 utils optional pecomato_0.0.15-11.dsc 20a7412b8bbc03e75dfb2aa1ff2c2665 6284 utils optional pecomato_0.0.15-11.debian.tar.xz 3d489b82bb5888302d52d295c91d9765 8961 utils optional pecomato_0.0.15-11_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEQ7w2SxbfDCBevXWSHw8KiN5bzKYFAl9TpiUACgkQHw8KiN5b zKa4Pw//dGNG6WDihNQiiNcV28dXjyhZK7DLWhNX5+qWZt7lecbfymjb4BlD5OfD eiM59HF/Z5Ke7iji1684D974vBc97p6WtWdEeERkscoNW2Xcsqrc+L9AtRL55+IP 3rntiTuFPTmiPiJiMcxxdYGMl9QBKn6i7KOyH7OxQy6nxli4bpq9K56rHl+mCrMX 0QjxKxyBp2OFLVBzb8qsfOFInBC3uwsmfxMUYYmvfLIstoH4EXeeoplvmWrYpjXJ +5rvn6cppaMW0dQjdccx0alMQf+cfZ4UgRqf83E/oi96SVAupPNxG0hKXz7Q2QMd uo6qRFkepVlyBd+BlVG+HD1U3jmgN4VwEkA6CuPaLoyGxjqP8n9JeaUyix0OYwlb +hxnlSCo/J3mn1KcfUB7jrkPXOXAMhKVe1/tVAZmSTWj836Df5NYCzMxQ5kGhTtk vJVKIsfwVKPwmfNOKdlv3Wr1lLFOq3hkK8WnmHY2cZBE5vqOwHBKh0SgZtCCr7sm DqpOLqsSCmgwZ7zJMjR5Dh+rtmTIgc2PfrYyB3Do+EYf5BQE41Udfmal09HK+SGz o8M7zi4z/9LCXzid28AtATYqzWiKfuHivyVgVwR41WDzVtlPKlWX18i5d7bfTHh4 /Rm1a4s9H+SPFySxa4NL8pXxhPXBZkJ1QbPrsOQ2EtZXFnm3r8w= =q0mR -END PGP
Bug#969569: marked as done (Gnome-builder: build-depends on package that is not in testing.)
Your message dated Sat, 05 Sep 2020 15:19:13 + with message-id and subject line Bug#969569: fixed in gnome-builder 3.36.1-1 has caused the Debian Bug report #969569, regarding Gnome-builder: build-depends on package that is not in testing. 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.) -- 969569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969569 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-builder Version: 3.36.0-3 Severity: serious Tags: patch The gnome-builder source package build-depends on libenchant-dev (source package enchant) which was recently removed from testing (see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956881 ). However the gnome-builder binary package depends on libenchant-2-2 (source package enchant-2) Reading though the changelog it seems that gnome-builder switched from enchant to enchant-2 in version 3.34.1-2 but the build-dependency was not updated accordingly. The package built successfully because libenchant-2-dev was pulled in indirectly. I did a test build with the build-dependency changed from libenchant-dev to libenchant-2-dev and it was successful. Please update your build-dependency. --- End Message --- --- Begin Message --- Source: gnome-builder Source-Version: 3.36.1-1 Done: Simon McVittie We believe that the bug you reported is fixed in the latest version of gnome-builder, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated gnome-builder 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: Sat, 05 Sep 2020 15:01:42 +0100 Source: gnome-builder Architecture: source Version: 3.36.1-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Simon McVittie Closes: 922640 969569 Changes: gnome-builder (3.36.1-1) unstable; urgency=medium . * Team upload * New upstream release - Among other fixes, there is an updated German translation (Closes: #922640) * d/p/meson-Add-generated-lsp-enum-header-to-lsp-sources.patch: Drop patch, applied upstream * Add post-release fixes from upstream 3.36 branch, up to 3.36.1-9-gb99463102 * d/control.in: Switch build-dependency from enchant to enchant-2. Thanks to peter green (Closes: #969569) Checksums-Sha1: 5fa577cb6b8bcbc57de1dc64692c60d3d6b2c5d1 3240 gnome-builder_3.36.1-1.dsc d6fae1269c011339d34c28600ae3f5c07427f52c 12026976 gnome-builder_3.36.1.orig.tar.xz bf1098a920c33647034575b23a7e0ff8b7bf06c8 28892 gnome-builder_3.36.1-1.debian.tar.xz e05e14e4f57d591d6861cba44e0d54d7f901f3c7 19041 gnome-builder_3.36.1-1_source.buildinfo Checksums-Sha256: 504fb3b1f260ae551d261fef5e91429380e78a03466e37b8a0b7e552d51ad34d 3240 gnome-builder_3.36.1-1.dsc 22ab39f3c974e9b3f37c9c0b1879a0045b79dc86a670936743595d2f4babfb9e 12026976 gnome-builder_3.36.1.orig.tar.xz c9ed749bbe6d5dd44be35e16c02e30f939646b86b24799f9e9212dc4c1f64166 28892 gnome-builder_3.36.1-1.debian.tar.xz 9d6957f16b51a69651fb0c360c97d697db1cbac8b950cb35b0f311eae345d99a 19041 gnome-builder_3.36.1-1_source.buildinfo Files: bb267dd33008b69042c47497a85af3a5 3240 editors optional gnome-builder_3.36.1-1.dsc 6004c30ebe74aedc0d5610d23647e373 12026976 editors optional gnome-builder_3.36.1.orig.tar.xz a0b8e2bc759882f8b83efa63b84e441d 28892 editors optional gnome-builder_3.36.1-1.debian.tar.xz 6e3e46de7e232f02590f8a0f5d097139 19041 editors optional gnome-builder_3.36.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAl9TpkUQHHNtY3ZAZGVi aWFuLm9yZwAKCRDgWuFHj4FMT30CD/9fi638MfD93bQkfZD6lAZMauEK63nlyMfK TbPnftiS9zN+NieVPNcCV5PbLF/FVb26n4H/fGRQi38Sq41u0fOGD+5Ka4jbEzYl OJZ7T/k8xlF4qQXZKi43fNFAVyFoFvfCTrmFSrUvnkXPQHv41BVVqZZ/gn6Rry9L KNX/6OhQ15NxYTupCithqxjVUpttdz4hPCujR6DVcwzf3R/vK5epm0QGp7zNjxWb 1q/rU/aKptPwRjUmmX+gNJ1hBzB8SEf8aeaqvA1ktM3Asultijwf5yWPtOQesel8 h1vGQY1k/g/2mTRWEID8hfswmMj05HJwdYkC8Ez0ssbKfkih84g0yMe68kiS1uSI cbAFVf5wiNcjUsDgmxzEimtGj4akxNexsXjx9lNKQuqI0oFfBfDJx6Cy5P5PShM3
Bug#957271: gfpoken: ftbfs with GCC-10
Hi, the GCC 10 build error is easily fixed with the attached patch. But the build also fails while generating artwork via a Gimp script (art/mktiles): > Starting extension: 'extension-script-fu' > No batch interpreter specified, using the default 'plug-in-script-fu-eval'. > Welcome to TinyScheme, Version 1.40 > Copyright (c) Dimitrios Souflis > > ts> It then just hangs in this tinyscheme "shell". Unfortunately I don't know enough about Gimp scripting to fix that. Kind regards, Reiner --- a/common.h +++ b/common.h @@ -19,7 +19,7 @@ */ /* Variable Declarations */ -int gamestatus; +extern int gamestatus; extern unsigned int dragbuf[DrNum]; /* Draggable buffer for list on right */ extern unsigned int bufsize, originalbuf; /* Number of items in buffer */ extern pos buttonx, buttony; /* Location of button press, in tiles. */ signature.asc Description: PGP signature
Bug#969579: marked as done (ruby-oj: ftbfs on armel, armhf and mipsel - Failure: CustomJuice#test_float_parse_fast [/<>/test/test_custom.rb:129]: Expected: "12.12345678901235" Actual: "1
Your message dated Sat, 05 Sep 2020 14:53:20 + with message-id and subject line Bug#969579: fixed in ruby-oj 3.10.13-2 has caused the Debian Bug report #969579, regarding ruby-oj: ftbfs on armel, armhf and mipsel - Failure: CustomJuice#test_float_parse_fast [/<>/test/test_custom.rb:129]: Expected: "12.12345678901235" Actual: "12.12345678901234" 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.) -- 969579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ruby-oj Version: 3.10.13-1 Severity: serious Control: forwarded -1 https://github.com/ohler55/oj/issues/610 Failed to build on official buildd with error 1) Failure: CustomJuice#test_float_parse_fast [/<>/test/test_custom.rb:129]: Expected: "12.12345678901235" Actual: "12.12345678901234" 482 runs, 8980 assertions, 1 failures, 0 errors, 0 skips Full log https://buildd.debian.org/status/fetch.php?pkg=ruby-oj=mipsel=3.10.13-1=1598615251=0 --- End Message --- --- Begin Message --- Source: ruby-oj Source-Version: 3.10.13-2 Done: Pirate Praveen We believe that the bug you reported is fixed in the latest version of ruby-oj, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated ruby-oj 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: Sat, 05 Sep 2020 19:53:14 +0530 Source: ruby-oj Architecture: source Version: 3.10.13-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Pirate Praveen Closes: 969579 Changes: ruby-oj (3.10.13-2) unstable; urgency=medium . * Team upload. * Cherry pick commit from upstream develop branch to fix test failure (Closes: #969579) Checksums-Sha1: 7d88b9d24861460470f6e64a39b0ff7f1e9798e7 2001 ruby-oj_3.10.13-2.dsc 2a27ec57ff499116a0d571d254052d0f5e82390f 5696 ruby-oj_3.10.13-2.debian.tar.xz 45e893b2b5190402b021c584bb3b0f97de2aa443 8729 ruby-oj_3.10.13-2_amd64.buildinfo Checksums-Sha256: e35440bb4de3307eed852af1a306566c0faad13266eb937cf84c251ce6c12e8f 2001 ruby-oj_3.10.13-2.dsc 99082d872ed0928b93ff549a3c7801d358aea3f7bbbfe9338ad2d242fd42ba89 5696 ruby-oj_3.10.13-2.debian.tar.xz 6a72ea6f092992bf9f0622ee78b69f4a7caa5afed2fa4d58f2c760d7448ed178 8729 ruby-oj_3.10.13-2_amd64.buildinfo Files: 0c82e16cfd08e1a353a89abe9461993a 2001 ruby optional ruby-oj_3.10.13-2.dsc 513c9579bb0f030cda521cfac40da52c 5696 ruby optional ruby-oj_3.10.13-2.debian.tar.xz 18fa63810072cdc3661eeff2e05c499b 8729 ruby optional ruby-oj_3.10.13-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0whj4mAg5UP0cZqDj1PgGTspS3UFAl9ToEwACgkQj1PgGTsp S3VWsA/8DHdIWXuQvFJkCAW3o6XXRsYOuHfNZEEAmTZyknYkOR8QsDQkBIYlT5qu VlKgXjfKerEn2v/rXywiAywtL98E/my4DG1uzcW2hP5lubvkVEzOO47bQP053nEW kvwyEwMBNp7rwEsZtbMUyZitZjJKVPY9rw2BPOKqkPOg2QJxOKHGDxABw0Rq7cgt nSc1J0bAOjrtg442uEo5/UI66vIpRWcVSrnLbBiom4ZmiKXKVeJOdUP0RZpLpeAi kaPnhdrKrTK96mizlykVhLKc/cky/Bp4RzuuJ2hufgqysHnOPmtzRERWKO0aZDC1 bsNO/Yit3HxaVX0NE7S9eU1P5ir8N5ZlS1iifgcOY0JnRlcID3aCNopa0owMTdPz wPBwQyZ9q1Yu7+LaA99a5iH796Lgn/+NC0VxVpjypBDd352H5/7PzahRcC7YI208 jGPSbpeASvSKeuW1kBdqiREyKzZCwd3Qwh3gnEpu5EWlzU04rXKEwWGv3oNMpPdO MMUKGQQZKFtfLT0HwBVD17E4blATYbM59FJiVRsjHM/RKw0FYBsv060LWEXm+PMY VHvEltxMy9Jv+eUC6fCb7ExAN2/0SreTVvdKXkW8KcuX5J7xmB9VB3kgNhpoeEGK P+1c6vp7hEP686RhiENiU/dF6ZYeNgBUMyBZuEK9M+F3aiyhEGY= =MbGO -END PGP SIGNATURE End Message ---
Processed: Re: [Pkg-sass-devel] Bug#953415: Processed: gitlab upstream forwarded this to libsass upstream
Processing control commands: > retitle -1 libsass: performance regression from v3.5.2 to v3.6.4 Bug #953415 [libsass] regression in libsass Bug #956205 [libsass] regression in libsass Changed Bug title to 'libsass: performance regression from v3.5.2 to v3.6.4' from 'regression in libsass'. Changed Bug title to 'libsass: performance regression from v3.5.2 to v3.6.4' from 'regression in libsass'. > severity -1 important Bug #953415 [libsass] libsass: performance regression from v3.5.2 to v3.6.4 Bug #956205 [libsass] libsass: performance regression from v3.5.2 to v3.6.4 Severity set to 'important' from 'serious' Severity set to 'important' from 'serious' -- 953415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953415 956205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953415: [Pkg-sass-devel] Bug#953415: Processed: gitlab upstream forwarded this to libsass upstream
Control: retitle -1 libsass: performance regression from v3.5.2 to v3.6.4 Control: severity -1 important Quoting Pirate Praveen (2020-09-05 10:13:38) > Control: forwarded -1 https://github.com/sass/libsass/issues/3125 > Control: retitle -1 regression in libsass > Control: severity -1 serious > > On Wed, 26 Aug 2020 16:24:34 +0200 > Jonas Smedegaard wrote: > > When reassigning to another package, then please re-examine > > severity, and clarify the issue in the context of the package > > reassigned to - including retitle of the issue as needed. > > Retitled now. It completely breaks gitlab installation caused by a > memory leak (libsass just hangs) and hence serious. Thanks. Please note that package name is listed first with colon. I have now updated tite, with a bit more detail than just "regression". > > I fail to recognize that "Problem installing 12.8.8-6" is an issue > > of libsass at all, I do not understand what issue is "Top-level > > selectors may not contain the parent selector "&"", and I see > > references only to upstream of _gitlab_ but none for the upstream > > of _libsass_. > > The gitlab upstream issue linked has links to libsass upstream issue. > Now changed forwarded entry to libsass issue. Thanks. Lowered severity: libsass has usecases where this regression is not release critical. - 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#969569 marked as pending in gnome-builder
Processing control commands: > tag -1 pending Bug #969569 [gnome-builder] Gnome-builder: build-depends on package that is not in testing. Added tag(s) pending. -- 969569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969569 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969559: curl segmentation fauls on any https URL
Dear Maintainer,
I tried to reproduce this fault, but did not get a segfault.
However, I think the backtrace points to these lines:
(gdb) bt
#0 0x7769dbce in int_ctx_new () at ../crypto/evp/pmeth_lib.c:160
#1 0x7769dcfa in EVP_PKEY_CTX_new () at
../crypto/evp/pmeth_lib.c:245
#2 0x77698d44 in do_sigver_init () at ../crypto/evp/m_sigver.c:29
#3 0x77698eab in EVP_DigestVerifyInit () at
../crypto/evp/m_sigver.c:97
#4 0x775bc7d2 in ASN1_item_verify () at
../crypto/asn1/a_verify.c:148
#5 0x77722490 in X509_verify () at ../crypto/x509/x_all.c:26
...
https://sources.debian.org/src/openssl/1.1.1d-0+deb10u3/crypto/evp/pmeth_lib.c/#L160
159 if (pmeth->init) {
160 if (pmeth->init(ret) <= 0) {
161 ret->pmeth = NULL;
As there is a check for pmeth->init being non-null, I guess
it contains for some reason an invalid pointer.
@Bruce Momjian,
maybe you could install the following debug symbols packages
`curl-dbgsym libcurl4-dbgsym libssl1.1-dbgsym` from the dbgsym
repository described here:
https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols
Then run a new gdb session and when the segfault appears
please run these commands in gdb:
print pmeth->init
bt full 5
Kind regards,
Bernhard
# Buster/stable amd64 qemu VM
apt update
apt dist-upgrade
apt install systemd-coredump curl gdb
curl https://google.com
dpkg -l curl libc6 libcurl4 zlib1g libssl1.1
ii curl7.64.0-4+deb10u1 amd64command line tool for
transferring data with URL syntax
ii libc6:amd64 2.28-10 amd64GNU C Library: Shared
libraries
ii libcurl4:amd64 7.64.0-4+deb10u1 amd64easy-to-use client-side URL
transfer library (OpenSSL flavour)
ii libssl1.1:amd64 1.1.1d-0+deb10u3 amd64Secure Sockets Layer toolkit
- shared libraries
ii zlib1g:amd641:1.2.11.dfsg-1 amd64compression library - runtime
benutzer@debian:~$ curl https://google.com
301 Moved
301 Moved
The document has moved
https://www.google.com/;>here.
gdb -q --args curl https://google.com
b ASN1_item_verify
y
run
disassemble ASN1_item_verify
b EVP_DigestVerifyInit
cont
...
generate-core-file /tmp/core
(gdb) bt
#0 0x7769dbce in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.1.1
#1 0x77698d44 in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.1.1
#2 0x775bc7d2 in ASN1_item_verify () from
/lib/x86_64-linux-gnu/libcrypto.so.1.1
#3 0x7771cfb4 in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.1.1
#4 0x7771edd6 in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.1.1
#5 0x7771f416 in X509_verify_cert () from
/lib/x86_64-linux-gnu/libcrypto.so.1.1
#6 0x7782fb88 in ?? () from /lib/x86_64-linux-gnu/libssl.so.1.1
#7 0x778510f3 in ?? () from /lib/x86_64-linux-gnu/libssl.so.1.1
#8 0x778536c5 in ?? () from /lib/x86_64-linux-gnu/libssl.so.1.1
#9 0x7784d143 in ?? () from /lib/x86_64-linux-gnu/libssl.so.1.1
#10 0x77838f34 in SSL_do_handshake () from
/lib/x86_64-linux-gnu/libssl.so.1.1
#11 0x77fa3240 in ?? () from /lib/x86_64-linux-gnu/libcurl.so.4
#12 0x77fa53f0 in ?? () from /lib/x86_64-linux-gnu/libcurl.so.4
#13 0x77fa61da in ?? () from /lib/x86_64-linux-gnu/libcurl.so.4
#14 0x77f4d462 in ?? () from /lib/x86_64-linux-gnu/libcurl.so.4
#15 0x77f6f6fe in ?? () from /lib/x86_64-linux-gnu/libcurl.so.4
#16 0x77f70aa9 in curl_multi_perform () from
/lib/x86_64-linux-gnu/libcurl.so.4
#17 0x77f67642 in curl_easy_perform () from
/lib/x86_64-linux-gnu/libcurl.so.4
#18 0x55569f30 in ?? ()
#19 0x5556b42a in ?? ()
#20 0xd8c4 in ?? ()
#21 0x77b5c09b in __libc_start_main (main=0xd770, argc=2,
argv=0x7fffe608, init=, fini=,
rtld_fini=, stack_end=0x7fffe5f8)
at ../csu/libc-start.c:308
#22 0xd9da in ?? ()
apt install curl-dbgsym libcurl4-dbgsym libssl1.1-dbgsym
gdb -q /usr/bin/curl --core /tmp/core
set width 0
set pagination off
(gdb) bt
#0 0x7769dbce in int_ctx_new (pkey=pkey@entry=0x55601a10,
e=e@entry=0x0, id=, id@entry=-1) at ../crypto/evp/pmeth_lib.c:160
#1 0x7769dcfa in EVP_PKEY_CTX_new (pkey=pkey@entry=0x55601a10,
e=e@entry=0x0) at ../crypto/evp/pmeth_lib.c:245
#2 0x77698d44 in do_sigver_init (ctx=ctx@entry=0x55601930,
pctx=pctx@entry=0x0, type=type@entry=0x777d5fc0 , e=e@entry=0x0,
pkey=pkey@entry=0x55601a10, ver=ver@entry=1) at ../crypto/evp/m_sigver.c:29
#3 0x77698eab in EVP_DigestVerifyInit (ctx=ctx@entry=0x55601930,
pctx=pctx@entry=0x0, type=type@entry=0x777d5fc0 , e=e@entry=0x0,
pkey=pkey@entry=0x55601a10) at ../crypto/evp/m_sigver.c:97
#4 0x775bc7d2 in ASN1_item_verify (it=0x777e7e80 ,
a=a@entry=0x555fda18, signature=signature@entry=0x555fda28,
Bug#969569: marked as pending in gnome-builder
Control: tag -1 pending Hello, Bug #969569 in gnome-builder reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/gnome-builder/-/commit/55ae5219639a74edaf409d0886741ef6e6f648fd d/control.in: Switch build-dependency from enchant to enchant-2 Closes: #969569 Thanks: peter green (this message was generated automatically) -- Greetings https://bugs.debian.org/969569
Bug#969315: marked as done (pytsk FTBFS with sleuthkit 4.9.0)
Your message dated Sat, 05 Sep 2020 13:18:34 +
with message-id
and subject line Bug#969315: fixed in pytsk 20200117-2
has caused the Debian Bug report #969315,
regarding pytsk FTBFS with sleuthkit 4.9.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.)
--
969315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969315
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytsk
Version: 20190507-1.1
Severity: serious
Tags: patch ftbfs
https://buildd.debian.org/status/package.php?p=pytsk=sid
...
dh_auto_test -a -O--buildsystem=pybuild
I: pybuild base:217: cd /<>/.pybuild/cpython3_3.8/build; python3.8
-m unittest discover -v
tests.test_lib (unittest.loader._FailedTest) ... ERROR
==
ERROR: tests.test_lib (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: tests.test_lib
Traceback (most recent call last):
File "/usr/lib/python3.8/unittest/loader.py", line 436, in _find_test_path
module = self._get_module_from_name(name)
File "/usr/lib/python3.8/unittest/loader.py", line 377, in
_get_module_from_name
__import__(name)
File "/<>/.pybuild/cpython3_3.8/build/tests/test_lib.py", line
5, in
import pytsk3
ImportError:
/<>/.pybuild/cpython3_3.8/build/pytsk3.cpython-38-x86_64-linux-gnu.so:
undefined symbol: libvmdk_handle_read_buffer_at_offset
--
Ran 1 test in 0.000s
FAILED (errors=1)
E: pybuild pybuild:352: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.8/build; python3.8 -m unittest discover -v
dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit
code 13
make: *** [debian/rules:8: build-arch] Error 25
Fix:
---
pytsk-20200117/debian/patches/0001-Link-system-tsk-statically-talloc-dynamically-instea.patch
2020-08-28 00:27:28.0 +0300
+++
pytsk-20200117/debian/patches/0001-Link-system-tsk-statically-talloc-dynamically-instea.patch
2020-08-31 12:36:28.0 +0300
@@ -80,7 +80,7 @@
+"libraries": [ "talloc" ],
+"extra_link_args": [
+ "-Wl,-Bstatic", "-ltsk", "-Wl,-Bdynamic",
-+ "-lafflib", "-lewf", "-lstdc++", "-lz",
++ "-lafflib", "-lewf", "-lstdc++", "-lz", "-lvmdk", "-lvhdi",
+]}
# The sources to build.
--- End Message ---
--- Begin Message ---
Source: pytsk
Source-Version: 20200117-2
Done: Samuel Henrique
We believe that the bug you reported is fixed in the latest version of
pytsk, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 969...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Samuel Henrique (supplier of updated pytsk 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: Sat, 05 Sep 2020 14:01:33 +0100
Source: pytsk
Architecture: source
Version: 20200117-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools
Changed-By: Samuel Henrique
Closes: 969315
Changes:
pytsk (20200117-2) unstable; urgency=medium
.
* Team upload
* Bump DH to 13
* Add new Build-Dependeds libvhdi-dev and libvmdk-dev (closes: #969315)
* d/t/autopkgtest-pkg-python.conf: Create file to describe correct
import_name
Checksums-Sha1:
36550a5ddb5b1d31326eca72d54018d530d40ffd 2062 pytsk_20200117-2.dsc
02fcb051f3f49fb87100c8d09ca20a340256e01f 5224 pytsk_20200117-2.debian.tar.xz
712654168ac0051744303d7270a80b93eb8ef569 7754 pytsk_20200117-2_amd64.buildinfo
Checksums-Sha256:
cc3707a031ca37d2a3394d6e59b4bf28a02392972c6148ca9e035f0cb0d83f36 2062
pytsk_20200117-2.dsc
61466722e59ee18db11af557c85be26a3e66fda77f8a48107629ea8749e5 5224
pytsk_20200117-2.debian.tar.xz
4f304dfd87f0b468f700eb0ecf4e894ef6c6210313f0a1dcbc08d22c9b95f139 7754
pytsk_20200117-2_amd64.buildinfo
Files:
a50e5e396ae36556d6ed09ea306bb921 2062 python optional pytsk_20200117-2.dsc
3918a388129cd43dc98b7f6c0b9dedb7 5224 python optional
pytsk_20200117-2.debian.tar.xz
f05326fce52e133e2a68222afa9ad67e 7754 python optional
Bug#969315: marked as pending in pytsk
Control: tag -1 pending Hello, Bug #969315 in pytsk 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/pkg-security-team/pytsk/-/commit/08f5882bdc9fd5c130d71b6b925d5ef68ad3d2ca Add new Build-Dependeds libvhdi-dev and libvmdk-dev (closes: #969315) (this message was generated automatically) -- Greetings https://bugs.debian.org/969315
Processed: Bug#969315 marked as pending in pytsk
Processing control commands: > tag -1 pending Bug #969315 [src:pytsk] pytsk FTBFS with sleuthkit 4.9.0 Added tag(s) pending. -- 969315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969315 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969570: ulfius: FTBFS on s390x
Hello,
Le 20-09-05 à 03 h 42, Gianfranco Costamagna a écrit :>
> Hello, your package FTBFS on s390x. Please have a look if possible
>
[...]
> Start 3: framework
> 3/4 Test #3: framework ***Failed0.65 sec
> Running suite(s): Ulfius framework function tests
> 86%: Checks: 15, Failures: 2, Errors: 0
[...]
> /<>/test/framework.c:1145:F:test_ulfius_framework:test_ulfius_send_smtp:0:
> Assertion 'ulfius_send_smtp_email("localhost", 2525, 0, 0, ((void *)0),
> ((void *)0), "from", "to", "cc", "bcc", "subject", "mail body") == 0' failed:
> ulfius_send_smtp_email("localhost", 2525, 0, 0, ((void *)0), ((void *)0),
> "from", "to", "cc", "bcc", "subject", "mail body") == 5, 0 == 0
> /<>/test/framework.c:1169:F:test_ulfius_framework:test_ulfius_send_rich_smtp:0:
> Assertion 'ulfius_send_smtp_rich_email("localhost", 2526, 0, 0, ((void *)0),
> ((void *)0), "from", "to", "cc", "bcc", "text/ulfius; charset=utf-42",
> "subject", "mail body") == 0' failed:
> ulfius_send_smtp_rich_email("localhost", 2526, 0, 0, ((void *)0), ((void
> *)0), "from", "to", "cc", "bcc", "text/ulfius; charset=utf-42", "subject",
> "mail body") == 5, 0 == 0
This is weird, there were no changes in this part of the library between
2.6.8 and 2.6.9, and in the previous version the build had no problem [1]
The failing tests are using TCP ports 2525 and 2526 for SMTP tests.
Is it possible that those ports were not available during the build,
leading to test fails? Maybe because another process is using them or
some other reason?
/Nicolas
[1] -
https://buildd.debian.org/status/fetch.php?pkg=ulfius=s390x=2.6.8-1=1594468505=0
Bug#969537: marked as done (elpa-pdf-tools-server: broken when compiled against libpoppler102)
Your message dated Sat, 05 Sep 2020 12:18:27 + with message-id and subject line Bug#969537: fixed in emacs-pdf-tools 1.0~20200512-1 has caused the Debian Bug report #969537, regarding elpa-pdf-tools-server: broken when compiled against libpoppler102 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.) -- 969537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969537 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: elpa-pdf-tools-server Version: 0.90-3+b2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Here's a script to reproduce the segfault (path needs adjusting, must be absolute). I suspect any pdf will be the same, but I will attach the pdf in question. I say grave because this is the first command sent by the emacs package elpa-pdf-tools to verify the server is working. /usr/bin/epdfinfo < wt8.pdf Description: Adobe PDF document --- End Message --- --- Begin Message --- Source: emacs-pdf-tools Source-Version: 1.0~20200512-1 Done: David Bremner We believe that the bug you reported is fixed in the latest version of emacs-pdf-tools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Bremner (supplier of updated emacs-pdf-tools 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: Sat, 05 Sep 2020 08:52:01 -0300 Source: emacs-pdf-tools Architecture: source Version: 1.0~20200512-1 Distribution: experimental Urgency: medium Maintainer: Debian Emacs addons team Changed-By: David Bremner Closes: 969462 969537 Changes: emacs-pdf-tools (1.0~20200512-1) experimental; urgency=medium . * Team upload * New upstream snapshot. Bug fix: "annotation editing broken with emacs 27.1" (Closes: #969462). * Drop patch fix-for-new-libsynctex; equivalent is upstream now. * Add versioned depends on libpoppler-glib8 (Closes: #969537). Checksums-Sha1: 40e7a199c4f3b3a4c46f72ee862eb14f8c1c1ab2 2362 emacs-pdf-tools_1.0~20200512-1.dsc 6b3c3964e0c4ca75cde6b40d69bcb472e053a6cb 399120 emacs-pdf-tools_1.0~20200512.orig.tar.xz bdcd893eb0ffd2585eede387f07d37209e813e87 5184 emacs-pdf-tools_1.0~20200512-1.debian.tar.xz Checksums-Sha256: cdf44ae71edd486f496f37b346efcf40ee4ebc4c82e1baa825b3863270614bb7 2362 emacs-pdf-tools_1.0~20200512-1.dsc 15cd0872029fdcbbdba3e6e51b0148a279f0567f15acd7420aef791b2fd1ae81 399120 emacs-pdf-tools_1.0~20200512.orig.tar.xz 81e7bf7405269eeec5cd65f944761acdba15650b5af2f6776bb91dd5366d2643 5184 emacs-pdf-tools_1.0~20200512-1.debian.tar.xz Files: 94bbd485ed70dd007dfd2677c095fcae 2362 text optional emacs-pdf-tools_1.0~20200512-1.dsc 0ca3b29c7bbada1a7380790bfac2a8ce 399120 text optional emacs-pdf-tools_1.0~20200512.orig.tar.xz 2ebcc3c92539bc2fb0bc367bfc25c23e 5184 text optional emacs-pdf-tools_1.0~20200512-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl9TfZIACgkQA0U5G1Wq FSHdQQ//T/QFDL1uL2IitTyljxS460ZXW8SDOGqz16PiPiryLIiRRoaV2SRifVap qkzicRDnUdqtBYm0HLRT0UaldMV7xbV1iMMJGCa1LPhhKiwhtCxzoXv2O95iGvK9 Yoxa6Bq+mmpnEkZpGe9vxHUR6j/BFGnaZlNSJ7uea9cNDStTYgbJ+lwillQ16W3+ Rd3Su2AbEWhY47kB12sIny4xzGOoxdciQ7N9TJzwRLTTsuJyqtMs+NEAh+ScpxRL NIWe5gPBqjDi1OD0U5hDBEm+52yS+kIAq9xjEj68PU8dhv3DJzr3mhDik3iIneck 7x2tSLX8XnMYyetDDxmZdOS2KGAIo4y1qQMPxsKVVPgarSdcJKaTfGnlX5AUowzo CckqqbFoDRWwdhz4g9nlKwY25y0Zpje3ZpThMsCuPDNa1wc+ceiSbPDuLPsbSaoI gor1SRkRUT1CbM7iyn1HKiExKD5Do7+2vBnosO/SvJ88SGHEQLD0Wr6oIYW0igBY 2taDbeFAvSLmee61PVZws+qzRINE/D04jL3A8K4I7Znk3xCfkRGaUgNyhVRHekuB wG5DvWerQDrjxitCz9gLUXfYAUG2iI42f+rrBBmeeRS+UZovZsmfALx56JDzBuuc IAHA0wIg+SZoBDKlJ0BoS0dAfIBra4f3o2JpcRcT9V5JNaRF1OA= =R9nq -END PGP SIGNATURE End Message ---
Processed: tagging 958622
Processing commands for cont...@bugs.debian.org: > tags 958622 + pending Bug #958622 [src:tor] tor: Build-Depends on deprecated dh-systemd which is going away Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 958622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958622 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952085: marked as done (ruby-invisible-captcha: FTBFS: ERROR: Test "ruby2.5" failed: LoadError:)
Your message dated Sat, 05 Sep 2020 11:50:24 + with message-id and subject line Bug#952085: fixed in ruby-invisible-captcha 0.12.2-3 has caused the Debian Bug report #952085, regarding ruby-invisible-captcha: FTBFS: ERROR: Test "ruby2.5" failed: LoadError: 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.) -- 952085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-invisible-captcha Version: 0.12.2-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > LoadError: > cannot load such file -- rspec/rails > # > /usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in > `require' > # ./spec/spec_helper.rb:4:in `' > No examples found. > No examples found. > > > Finished in 0.3 seconds (files took 0.69733 seconds to load) > 0 examples, 0 failures, 1 error occurred outside of examples > > Finished in 0.3 seconds (files took 0.69733 seconds to load) > 0 examples, 0 failures, 1 error occurred outside of examples > > > /usr/bin/ruby2.5 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby2.5" failed: The full build log is available from: http://qa-logs.debian.net/2020/02/22/ruby-invisible-captcha_0.12.2-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! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: ruby-invisible-captcha Source-Version: 0.12.2-3 Done: Pirate Praveen We believe that the bug you reported is fixed in the latest version of ruby-invisible-captcha, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated ruby-invisible-captcha package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 05 Sep 2020 16:39:29 +0530 Source: ruby-invisible-captcha Architecture: source Version: 0.12.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Pirate Praveen Closes: 952085 Changes: ruby-invisible-captcha (0.12.2-3) unstable; urgency=medium . * Team upload . [ Daniel Leidert ] * d/control (Standards-Version): Bump to 4.5.0. (Depends): Remove interpreter. * Refresh patches and add DEP3 headers . [ Pirate Praveen ] * Use rails 6 and rspec-rails 4 for tests * Update autopkgtest fix patch for rails 6.0 as well (Closes: #952085) * Bump Standards-Version to 4.5.0 (no changes needed) * Tag patches that need not be forwarded * Remove gemfiles/rails_6.0.gemfile.lock in clean Checksums-Sha1: bddcdf42df5e9786268fa280734617deb67d649b 2240 ruby-invisible-captcha_0.12.2-3.dsc 1fac5c4e32adc50ebc9adab5daa467fab850beb4 3828 ruby-invisible-captcha_0.12.2-3.debian.tar.xz f6cef47778c8615d048c26592fc41b0353721292 10575 ruby-invisible-captcha_0.12.2-3_amd64.buildinfo Checksums-Sha256: 1160f82d2ada04271f8bd9a26200dc52b1ea7bf6615baafd0006daea4fde28dc 2240 ruby-invisible-captcha_0.12.2-3.dsc
Processed: ruby-oj: ftbfs on armel, armhf and mipsel - Failure: CustomJuice#test_float_parse_fast [/<>/test/test_custom.rb:129]: Expected: "12.12345678901235" Actual: "12.12345678901234"
Processing control commands: > forwarded -1 https://github.com/ohler55/oj/issues/610 Bug #969579 [ruby-oj] ruby-oj: ftbfs on armel, armhf and mipsel - Failure: CustomJuice#test_float_parse_fast [/<>/test/test_custom.rb:129]: Expected: "12.12345678901235" Actual: "12.12345678901234" Set Bug forwarded-to-address to 'https://github.com/ohler55/oj/issues/610'. -- 969579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969578: rakudo 2020.08.2-1 breaks perl6-* modules
Package: rakudo
Version: 2020.08.2-1
Severity: serious
Justification: breaks other packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Today's update of rakudo+nqp+moarvm left a big mess, after trying
several things and purging everything perl6 related an reinstalling
it looks like:
rakudo+nqp+moarvm can be upgraded or newly installed, but the
handling of the perl6-* modules fails:
Setting up perl6-zef (0.8.5-2) ...
===SORRY!=== Error while compiling /usr/share/perl6/tools/install-dist.p6
Could not find CompUnit::Repository::Staging in:
inst#/root/.raku
inst#/usr/share/perl6/site
inst#/usr/share/perl6/vendor
inst#/usr/share/perl6/core
ap#
nqp#
perl5#
at /usr/share/perl6/tools/install-dist.p6:35
"perl6 /usr/share/perl6/tools/install-dist.p6
--from=/usr/share/perl6/debian-sources/perl6-zef --to=/tmp/BfKrXArDh7/build
--for=vendor" unexpectedly returned exit value 1 at
/usr/share/perl5/IPC/System/Simple.pm line 578.
IPC::System::Simple::_check_exit("perl6
/usr/share/perl6/tools/install-dist.p6 --from=/usr/shar"..., 1,
ARRAY(0x55c01200c838)) called at /usr/share/perl5/IPC/System/Simple.pm line 550
IPC::System::Simple::_process_child_error(256, "perl6
/usr/share/perl6/tools/install-dist.p6 --from=/usr/shar"...,
ARRAY(0x55c01200c838)) called at /usr/share/perl5/IPC/System/Simple.pm line 190
IPC::System::Simple::run("perl6 /usr/share/perl6/tools/install-dist.p6
--from=/usr/shar"...) called at (eval 29) line 12
eval {...} called at (eval 29) line 11
Fatal::__ANON__("perl6 /usr/share/perl6/tools/install-dist.p6
--from=/usr/shar"...) called at /usr/share/perl6/rakudo-helper.pl line 47
main::install("perl6-zef") called at /usr/share/perl6/rakudo-helper.pl
line 151
at /usr/share/perl6/rakudo-helper.pl line 47
/usr/share/perl6/tools/install-dist.p6 is in rakudo, and I think
CompUnit::Repository::Staging
should be in rakudo as well but is not there or is not found.
Cheers,
gregor
- -- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500,
'oldoldstable'), (500, 'experimental'), (500, 'testing'), (500, 'stable'),
(500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages rakudo depends on:
ii libc6 2.31-3
ii libgraph-perl 1:0.9704-1
ii libipc-system-simple-perl 1.30-1
ii libpath-tiny-perl 0.114-1
ii moarvm 2020.08+dfsg-1
ii nqp2020.08.2+dfsg-1
rakudo recommends no packages.
Versions of packages rakudo suggests:
ii valgrind 1:3.16.1-1
- -- no debconf information
-BEGIN PGP SIGNATURE-
iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl9TcytfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbxsA//avg3MbDHB4HQ6EkAyM7Ku3PsGVbVkM+BLozouUDflFi3BHPmBIKzkebb
spq51cegneA5DIe2EeaBFzMjPJAuB4EeaDn9DW4A75mJePCmSUir3UE94KwN8JEY
u2ottAmxgDVvV8rhCu99fuwdY3gLC0uEGmG49npcKR03iOZtcUFwwjeKyQ7hEnFr
uQYgaGj7n2WgzLu9/ULLUWbBpEYA2CuSEJLKGdbH3Fj/wj9UcycOtsTPOXTa5JKI
/T2LUd+0jWw6aSix2cDaY0xs1Y1H9YddOZx1sd7dV8Tv3GV7R/qom65sh9pHsglC
IMdqdig2PUvO+Qrt6HSak+v3hJfHnkSp8d+mRbq+y7t/CGh3Swu4UJvw57+9ljz2
PZq5CHIatDRA63ESLUqWpEbwiyvZwbddUyfhaaTHRpYEDgUAzKC8kRqkVQdkQz8F
jjEnYNKPRtLtQ2okliE30Drvj9qec9pemWirWqLLO7C37ggBMN0vj0kPWIgrlFds
BLuYz9EMOI69UZ3wd1cykI9NNFJjq1bxnYxa9t1T7uSPEDzVkYYlnQFrcLIsVLXB
RuzBlE2xzSjFit6F+MU5Vq/AGVK6SLka45zh4YxjYKu4qKtxfQowQAYex7I17Mtm
nfW4H4nJoSZ70dHflPfMq4zlPsMLJkEtpQFrap/0ywc4R4sp6uE=
=abg/
-END PGP SIGNATURE-
Bug#969579: ruby-oj: ftbfs on armel, armhf and mipsel - Failure: CustomJuice#test_float_parse_fast [/<>/test/test_custom.rb:129]: Expected: "12.12345678901235" Actual: "12.12345678901234
Package: ruby-oj Version: 3.10.13-1 Severity: serious Control: forwarded -1 https://github.com/ohler55/oj/issues/610 Failed to build on official buildd with error 1) Failure: CustomJuice#test_float_parse_fast [/<>/test/test_custom.rb:129]: Expected: "12.12345678901235" Actual: "12.12345678901234" 482 runs, 8980 assertions, 1 failures, 0 errors, 0 skips Full log https://buildd.debian.org/status/fetch.php?pkg=ruby-oj=mipsel=3.10.13-1=1598615251=0
Bug#969577: caml-crush: FTBFS with GCC 10: multiple definition of `my_arch'
Source: caml-crush Version: 1.0.9-1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) caml-crush fails to build with GCC 10: | gcc -Wl,-z,relro,-z,now -shared -Wl,-soname,libp11clienttcpssl.so -fPIC -o libp11client"".so pkcs11_rpc_xdr.o pkcs11_rpc_clnt.o modwrap_"".o modwrap_crpc.o modwrap_crpc_ssl.o -lpthread -lssl -Wl,-z,relro; | /usr/bin/ld: modwrap_crpc.o:(.bss+0xa8): multiple definition of `my_arch'; modwrap_.o:(.bss+0xa8): first defined here | /usr/bin/ld: modwrap_crpc.o:(.bss+0xb0): multiple definition of `peer_arch'; modwrap_.o:(.bss+0xb0): first defined here | /usr/bin/ld: modwrap_crpc.o:(.bss+0x8): multiple definition of `is_Blocking'; modwrap_.o:(.bss+0x0): first defined here | /usr/bin/ld: modwrap_crpc.o:(.bss+0x20): multiple definition of `mutex'; modwrap_.o:(.bss+0x20): first defined here | /usr/bin/ld: modwrap_crpc.o:(.bss+0x60): multiple definition of `linkedlist_mutex'; modwrap_.o:(.bss+0x60): first defined here | /usr/bin/ld: modwrap_crpc.o:(.bss+0x88): multiple definition of `op_type'; modwrap_.o:(.bss+0x88): first defined here | /usr/bin/ld: modwrap_crpc.o:(.bss+0x90): multiple definition of `request_data'; modwrap_.o:(.bss+0x90): first defined here | /usr/bin/ld: modwrap_crpc.o:(.bss+0x98): multiple definition of `ssl'; modwrap_.o:(.bss+0x98): first defined here | /usr/bin/ld: modwrap_crpc.o:(.bss+0xa0): multiple definition of `ctx'; modwrap_.o:(.bss+0xa0): first defined here | /usr/bin/ld: modwrap_crpc_ssl.o:(.bss+0x98): multiple definition of `ssl'; modwrap_.o:(.bss+0x98): first defined here | /usr/bin/ld: modwrap_crpc_ssl.o:(.bss+0xa0): multiple definition of `ctx'; modwrap_.o:(.bss+0xa0): first defined here | /usr/bin/ld: modwrap_crpc_ssl.o:(.bss+0x18): multiple definition of `is_Blocking'; modwrap_.o:(.bss+0x0): first defined here | /usr/bin/ld: modwrap_crpc_ssl.o:(.bss+0x20): multiple definition of `mutex'; modwrap_.o:(.bss+0x20): first defined here | /usr/bin/ld: modwrap_crpc_ssl.o:(.bss+0x60): multiple definition of `linkedlist_mutex'; modwrap_.o:(.bss+0x60): first defined here | /usr/bin/ld: modwrap_crpc_ssl.o:(.bss+0x88): multiple definition of `op_type'; modwrap_.o:(.bss+0x88): first defined here | /usr/bin/ld: modwrap_crpc_ssl.o:(.bss+0x90): multiple definition of `request_data'; modwrap_.o:(.bss+0x90): first defined here | /usr/bin/ld: modwrap_crpc_ssl.o:(.bss+0xa8): multiple definition of `my_arch'; modwrap_.o:(.bss+0xa8): first defined here | /usr/bin/ld: modwrap_crpc_ssl.o:(.bss+0xb0): multiple definition of `peer_arch'; modwrap_.o:(.bss+0xb0): first defined here | collect2: error: ld returned 1 exit status | make[3]: *** [Makefile:39: crpc] Error 1 | make[3]: Leaving directory '/<>/build-SERVER/src/client-lib' | make[2]: *** [Makefile:19: client] Error 2 | make[2]: Leaving directory '/<>/build-SERVER' | dh_auto_build: error: cd build-SERVER && make -j1 CUSTOM_SONAME=libp11clienttcpssl.so returned exit code 2 | make[1]: *** [debian/rules:45: override_dh_auto_build-SERVER] Error 25 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:53: build] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#967186: marked as done (ogmrip: Unversioned Python removal in sid/bullseye)
Your message dated Sat, 5 Sep 2020 11:52:36 +0200 with message-id <20200905095236.ga663...@ramacher.at> and subject line Re: Bug#967186: ogmrip: Unversioned Python removal in sid/bullseye has caused the Debian Bug report #967186, regarding ogmrip: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967186 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ogmrip Version: 1.0.1-3 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- On 2020-08-04 09:28:48 +, Matthias Klose wrote: > Package: src:ogmrip > Version: 1.0.1-3 > Severity: serious > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2unversioned > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the distribution, as discussed in > https://lists.debian.org/debian-python/2019/07/msg00080.html > > We will keep some Python2 package as discussed in > https://lists.debian.org/debian-python/2020/07/msg00039.html > but removing the unversioned python packages python-minimal, python, > python-dev, python-dbg, python-doc. > > Your package either build-depends, depends on one of those packages. > Please either convert these packages to Python3, or if that is not > possible, replaces the dependencies on the unversioned Python > packages with one of the python2 dependencies (python2, python2-dev, > python2-dbg, python2-doc). > > Please check for dependencies, build dependencies AND autopkg tests. > > If there are questions, please refer to the wiki page for the removal: > https://wiki.debian.org/Python/2Removal, or ask for help on IRC > #debian-python, or the debian-pyt...@lists.debian.org mailing list. ogmrip does not depend or build-depend on anything Pythonish, hence I'm closing this bug. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message ---
Bug#967211: marked as done (swami: Unversioned Python removal in sid/bullseye)
Your message dated Sat, 5 Sep 2020 11:53:15 +0200 with message-id <20200905095315.gb663...@ramacher.at> and subject line Re: Bug#967211: swami: Unversioned Python removal in sid/bullseye has caused the Debian Bug report #967211, regarding swami: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967211 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:swami Version: 2.2.1-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- On 2020-09-03 22:47:56 +0200, Dennis Braun wrote: > Hi Matthias, > > it looks for me that this bug is false positive, because swami has no > python dependency and py-compile from the root dir is not in use. Closing -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message ---
Bug#966020: marked as done (jekyll: ftbfs with ruby-kramdown 2.x in experimental)
Your message dated Sat, 05 Sep 2020 09:33:29 +
with message-id
and subject line Bug#966020: fixed in jekyll 3.9.0+dfsg-1
has caused the Debian Bug report #966020,
regarding jekyll: ftbfs with ruby-kramdown 2.x in experimental
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.)
--
966020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966020
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jekyll
Version: 3.8.6+dfsg-3
Severity: important
┌──┐
│ Checking Rubygems dependency resolution on ruby2.7 │
└──┘
GEM_PATH=/<>/debian/jekyll/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0
ruby2.7 -e gem\ \"jekyll\"
/usr/lib/ruby/2.7.0/rubygems/dependency.rb:313:in `to_specs': Could not
find 'kramdown' (~> 1.14) - did find: [kramdown-2.3.0]
(Gem::MissingSpecVersionError)
Checked in
'GEM_PATH=/<>/debian/jekyll/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0',
execute `gem env` for more information
from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1402:in `block in
activate_dependencies'
from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in `each'
from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in
`activate_dependencies'
from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1373:in `activate'
from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in `block
in gem'
from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in
`synchronize'
from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in `gem'
Full log
https://people.debian.org/~praveen/ruby-kramdown2-meta-build/buildlogs/jekyll.log
Seems not many breaking changes and relaxing dependency may be enough
(major one is required minimum version of ruby is 2.3)
https://github.com/gettalong/kramdown/blob/master/doc/news/release_2_0_0.page
This version include a fix for CVE so getting this to unstable soon
would be nice.
--- End Message ---
--- Begin Message ---
Source: jekyll
Source-Version: 3.9.0+dfsg-1
Done: Pirate Praveen
We believe that the bug you reported is fixed in the latest version of
jekyll, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 966...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pirate Praveen (supplier of updated jekyll 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: Sat, 05 Sep 2020 14:19:21 +0530
Source: jekyll
Architecture: source
Version: 3.9.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Pirate Praveen
Closes: 961194 966020
Changes:
jekyll (3.9.0+dfsg-1) unstable; urgency=medium
.
* Team Upload
.
[ Debian Janitor ]
* Wrap long lines in changelog entries: 1.5.1-1.
* Set field Upstream-Contact in debian/copyright.
* Remove obsolete fields Contact, Name from debian/upstream/metadata
(already present in machine-readable debian/copyright).
.
[ Daniel Leidert ]
* d/control (Build-Depends): Add ruby-coderay and ruby-yajl. Remove unused
ruby-toml.
(Depends): Replace most dependencies by ${ruby:Depends} except for those
not listed in the gemspec but rather the Gemfile.
(Suggests): Add jekyll-theme-minima, ruby-jekyll-avatar, and
ruby-jekyll-mentions.
(Description): Add a paragraph how to find the plugins.
* d/ruby-tests.rake: Use gem2deb. Enable tag, convertible, plugin, and site
tests. Enable coffeescript tests based on AUTOPKGTEST_TEST_COFFEESCRIPT
environment variable. Enable the new command test based on the
AUTOPKGTEST_TEST_NEW_COMMAND environment
Processed: Re: [Pkg-sass-devel] Processed: gitlab upstream forwarded this to libsass upstream
Processing control commands: > forwarded -1 https://github.com/sass/libsass/issues/3125 Bug #953415 [libsass] gitlab: Top-level selectors may not contain the parent selector "&" Bug #956205 [libsass] gitlab: Problem installing 12.8.8-6 Changed Bug forwarded-to-address to 'https://github.com/sass/libsass/issues/3125' from 'https://gitlab.com/gitlab-org/gitlab/-/merge_requests/29187'. Changed Bug forwarded-to-address to 'https://github.com/sass/libsass/issues/3125' from 'https://gitlab.com/gitlab-org/gitlab/-/merge_requests/29187'. > retitle -1 regression in libsass Bug #953415 [libsass] gitlab: Top-level selectors may not contain the parent selector "&" Bug #956205 [libsass] gitlab: Problem installing 12.8.8-6 Changed Bug title to 'regression in libsass' from 'gitlab: Top-level selectors may not contain the parent selector "&"'. Changed Bug title to 'regression in libsass' from 'gitlab: Problem installing 12.8.8-6'. > severity -1 serious Bug #953415 [libsass] regression in libsass Bug #956205 [libsass] regression in libsass Severity set to 'serious' from 'minor' Severity set to 'serious' from 'minor' -- 953415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953415 956205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956205 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959571: marked as pending in audacity
Control: tag -1 pending Hello, Bug #959571 in audacity reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/multimedia-team/audacity/-/commit/ec4ff31207413cd59935cf1f06e7bd3f53e09ea0 Bump cmake requirement Closes: #959571 (this message was generated automatically) -- Greetings https://bugs.debian.org/959571
Processed: Bug#959571 marked as pending in audacity
Processing control commands: > tag -1 pending Bug #959571 [src:ruby-psych] ruby-psych: FTBFS: LoadError: no such file to load -- psych Added tag(s) pending. -- 959571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969570: ulfius: FTBFS on s390x
Source: ulfius
Version: 2.6.9-1
Severity: serious
Hello, your package FTBFS on s390x. Please have a look if possible
gmake[4]: Leaving directory '/<>/build'
gmake[3]: Leaving directory '/<>/build'
Start 1: core
1/4 Test #1: core . Passed0.08 sec
Start 2: u_map
2/4 Test #2: u_map Passed0.02 sec
Start 3: framework
3/4 Test #3: framework ***Failed0.65 sec
Running suite(s): Ulfius framework function tests
86%: Checks: 15, Failures: 2, Errors: 0
/<>/test/framework.c:630:P:test_ulfius_framework:test_ulfius_simple_endpoint:0:
Passed
/<>/test/framework.c:767:P:test_ulfius_framework:test_ulfius_net_type_endpoint:0:
Passed
/<>/test/framework.c:845:P:test_ulfius_framework:test_ulfius_endpoint_parameters:0:
Passed
/<>/test/framework.c:896:P:test_ulfius_framework:test_ulfius_endpoint_injection:0:
Passed
/<>/test/framework.c:971:P:test_ulfius_framework:test_ulfius_endpoint_multiple:0:
Passed
/<>/test/framework.c:994:P:test_ulfius_framework:test_ulfius_endpoint_stream:0:
Passed
/<>/test/framework.c:1024:P:test_ulfius_framework:test_ulfius_utf8_not_ignored:0:
Passed
/<>/test/framework.c:1056:P:test_ulfius_framework:test_ulfius_utf8_ignored:0:
Passed
/<>/test/framework.c:1083:P:test_ulfius_framework:test_ulfius_endpoint_callback_position:0:
Passed
/<>/test/framework.c:1115:P:test_ulfius_framework:test_ulfius_MHD_set_response_with_other_free:0:
Passed
/<>/test/framework.c:1145:F:test_ulfius_framework:test_ulfius_send_smtp:0:
Assertion 'ulfius_send_smtp_email("localhost", 2525, 0, 0, ((void *)0), ((void
*)0), "from", "to", "cc", "bcc", "subject", "mail body") == 0' failed:
ulfius_send_smtp_email("localhost", 2525, 0, 0, ((void *)0), ((void *)0),
"from", "to", "cc", "bcc", "subject", "mail body") == 5, 0 == 0
/<>/test/framework.c:1169:F:test_ulfius_framework:test_ulfius_send_rich_smtp:0:
Assertion 'ulfius_send_smtp_rich_email("localhost", 2526, 0, 0, ((void *)0),
((void *)0), "from", "to", "cc", "bcc", "text/ulfius; charset=utf-42",
"subject", "mail body") == 0' failed: ulfius_send_smtp_rich_email("localhost",
2526, 0, 0, ((void *)0), ((void *)0), "from", "to", "cc", "bcc", "text/ulfius;
charset=utf-42", "subject", "mail body") == 5, 0 == 0
/<>/test/framework.c:1208:P:test_ulfius_framework:test_ulfius_follow_redirect:0:
Passed
/<>/test/framework.c:1230:P:test_ulfius_framework:test_ulfius_server_ca_trust:0:
Passed
/<>/test/framework.c:1306:P:test_ulfius_framework:test_ulfius_client_certificate:0:
Passed
Start 4: websocket
4/4 Test #4: websocket Passed3.04 sec
75% tests passed, 1 tests failed out of 4
Total Test time (real) = 3.78 sec
The following tests FAILED:
3 - framework (Failed)
Errors while running CTest
make[2]: *** [Makefile:118: test] Error 8
make[2]: Leaving directory '/<>/build'
make[1]: *** [debian/rules:29: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:11: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
thanks
G.
Bug#969569: Gnome-builder: build-depends on package that is not in testing.
Package: gnome-builder Version: 3.36.0-3 Severity: serious Tags: patch The gnome-builder source package build-depends on libenchant-dev (source package enchant) which was recently removed from testing (see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956881 ). However the gnome-builder binary package depends on libenchant-2-2 (source package enchant-2) Reading though the changelog it seems that gnome-builder switched from enchant to enchant-2 in version 3.34.1-2 but the build-dependency was not updated accordingly. The package built successfully because libenchant-2-dev was pulled in indirectly. I did a test build with the build-dependency changed from libenchant-dev to libenchant-2-dev and it was successful. Please update your build-dependency.
