Bug#1022927: marked as done (libghc-aeson-dev depends on non-existing libghc-semialign-dev-1.2.0.1-ebc3a)
Your message dated Fri, 28 Oct 2022 09:02:20 +0300 with message-id <20221028060220.6b7dfkdxzvkee...@iliastsi.net> and subject line Re: Bug#1022927: libghc-aeson-dev depends on non-existing libghc-semialign-dev-1.2.0.1-ebc3a has caused the Debian Bug report #1022927, regarding libghc-aeson-dev depends on non-existing libghc-semialign-dev-1.2.0.1-ebc3a 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.) -- 1022927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libghc-aeson-dev Version: 2.0.3.0-1+b4 Severity: serious Hi, libghc-aeson-dev on amd64c depends on libghc-semialign-dev-1.2.0.1-ebc3a which does not exist in the archive. The situation is the same on other arches with a different hash of libghc-semialign-dev-1.2.0.1. -Ralf. --- End Message --- --- Begin Message --- Version: 2.0.3.0-1+b5 Hi Ralf, On Thu, Oct 27, 2022 at 09:52PM, Ralf Treinen wrote: > libghc-aeson-dev on amd64c depends on libghc-semialign-dev-1.2.0.1-ebc3a > which does not exist in the archive. The situation is the same on other > arches with a different hash of libghc-semialign-dev-1.2.0.1. We are currently under transition[1] for Haskell in unstable and some of the packages may be uninstallable. We are rebuilding them as we speak. libghc-aeson-dev on amd64 is now at version 2.0.3.0-1+b5, which is installable again. [1] https://release.debian.org/transitions/html/haskell.html Best, -- Ilias--- End Message ---
Bug#1022282: staden-io-lib: FTBFS: ./data/9827_rand3.cram.fai: No such file or directory
Dear Bernhard, > A short term solution might be the patch in [7] which makes > the build and tests succeed without "implicit declarations". Thanks a lot for your explicit explanation and the helpful patch. I've just uploaded your patch Andreas. -- http://fam-tille.de
Processed: limit source to linux, tagging 1022848
Processing commands for cont...@bugs.debian.org: > limit source linux Limiting to bugs with field 'source' containing at least one of 'linux' Limit currently set to 'source':'linux' > tags 1022848 + pending Bug #1022848 [src:linux] 6.0.5 fixes critical btrfs bug in 6.0.3, affecting space cache v1 filesystems Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1022848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1022848: linux: 6.0.5 fixes critical btrfs bug
Processing control commands: > severity -1 serious Bug #1022848 [src:linux] 6.0.5 fixes critical btrfs bug in 6.0.3, affecting space cache v1 filesystems Severity set to 'serious' from 'important' -- 1022848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022806: linux-image-5.10.0-19-amd64: amggpu unbootable problem persists
Oland [Radeon HD 8570 / R5 430 OEM R7 240/340 Radeon 520 OEM] vendor: Dell driver: radeon v: kernel arch: GCN-1 pcie: speed: 2.5 GT/s lanes: 8 ports: active: DP-1,DVI-I-1 empty: none bus-ID: 01:00.0 chip-ID: 1002:6611 Same failure as in my previous comment #45 about GCN2. In Bullseye in both PCs, workaround is to omit 'plymouth.enable=0 radeon.si_support=1' from linu line in Grub, which absent installation of radeon DDX, forces use of modesetting DIX instead of amdgpu DDX, which was working just fine until linux-image-5.10.0-19-amd64 was installed. The resulting change in display output names requires the xrandr script locating all the displays to be rewritten. On this one I've not as yet attempted installation of backport kernel. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Bug#1022400: marked as done (nuitka: FTBFS: make[1]: python2: No such file or directory)
Your message dated Fri, 28 Oct 2022 03:05:09 +
with message-id
and subject line Bug#1022400: fixed in nuitka 1.1.7+ds-1
has caused the Debian Bug report #1022400,
regarding nuitka: FTBFS: make[1]: python2: No such file or directory
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.)
--
1022400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nuitka
Version: 1.0.6+ds-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> /bin/sh: 1: [: Illegal number: n/a
> python2 -c 'from nuitka.utils.Rest import createPDF; createPDF("README.rst");
> createPDF("Developer_Manual.rst")'
> make[1]: pyversions: No such file or directory
> make[1]: python2: No such file or directory
> make[1]: *** [debian/rules:39: override_dh_auto_build] Error 127
The full build log is available from:
http://qa-logs.debian.net/2022/10/23/nuitka_1.0.6+ds-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221023&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: nuitka
Source-Version: 1.1.7+ds-1
Done: Kay Hayen
We believe that the bug you reported is fixed in the latest version of
nuitka, 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 1022...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Kay Hayen (supplier of updated nuitka package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 26 Oct 2022 14:46:14 +0200
Source: nuitka
Architecture: source
Version: 1.1.7+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Kay Hayen
Changed-By: Kay Hayen
Closes: 1022400
Changes:
nuitka (1.1.7+ds-1) unstable; urgency=medium
.
* New upstream hotfix release.
.
* Handle Debian sid change in release number (Closes: #1022400)
Checksums-Sha1:
03de72690272ab149b5bf9698c9e37302860473b 2558 nuitka_1.1.7+ds-1.dsc
d507268da57c37c1c3f766e1c09a7fd48c3fc6c5 1658811 nuitka_1.1.7+ds.orig.tar.gz
fc17a101ae3cf812c57061017917965edbe9cef5 13304 nuitka_1.1.7+ds-1.debian.tar.xz
d64012530d460927cb72684a3e339bd472283736 9694 nuitka_1.1.7+ds-1_amd64.buildinfo
Checksums-Sha256:
834823a23979dba97e1847586cfe6b68b6773757c093e9e172815f292ad3bdd0 2558
nuitka_1.1.7+ds-1.dsc
db09cac17bc4fdc5abb0c906a7baf3fe219e6c0a799edff13682a85619bd485e 1658811
nuitka_1.1.7+ds.orig.tar.gz
9cda55600327b3717702e9928424a4e266100c4c99efe71b99572213fb46b57e 13304
nuitka_1.1.7+ds-1.debian.tar.xz
4c5783b2e54f533692e209b493fc90fef5e605747bcdc84c7ce96d7c7fbc3552 9694
nuitka_1.1.7+ds-1_amd64.buildinfo
Files:
d59edb97ec81e073e57df6b4255d4934 2558 python optional nuitka_1.1.7+ds-1.dsc
fbe2f9cbabbfcd5dcbcb4acbfa3e0eda 1658811 python optional
nuitka_1.1.7+ds.orig.tar.gz
a2c8929403b101ce1a42efe5695cd61a 13304 python optional
nuitka_1.1.7+ds-1.debian.tar.xz
1e4db96f754ef3fdd527138b8941cf40 9694 python optional
nuitka_1.1.7+ds-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEExbkF8OjZ/ZZo/zZvot4jUGLaM/oFAmNbQcMACgkQot4jUGLa
M/rlEBAAqLYHvpxrtS6RJbBWw5ZGEcWgsSA4QHwaiL9W6x7Vj9iER4XuPZbYLjFB
uFTO/Kc397LjYz2NM37OY6wa4uCLpBlX2aWFx1PG7i9StYjidAFGkCbWU+G7s+te
CSoAXi5qfzteohuwVTrEyaZhnk/aoi34EYAKLMWysYeSpvMLxfBbEHO3E9RmAeXb
m+thGZrWqhioAt
Bug#1022806: linux-image-5.10.0-19-amd64: amggpu unbootable problem persists
5.10.149-2 produced no improvement for my A10-7850K Radeon R7. 5.19.0-0.deb11.2-amd64 solves the problem for me, which is no surprise given Bookworm has been working fine on same PC using its latest 5.19 kernel. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Bug#1022025: Fwd: Bug#1022051: Acknowledgement (linux-image-5.10.0-19-amd64: no boot possible)
On Sun, 23 Oct 2022 10:12:17 +0200 Michael Becker wrote: > 5.10.149-2 solved the problem 5.10.149-2 was no help with A10-7850K Radeon R7. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Bug#664396: vsdump: Helping to update to packaging format 3.0
Raising severity to serious as dpatch is now removed from sid, which makes the package FTBFS. -Ralf.
Processed: reassign 664396 to src:vsdump
Processing commands for cont...@bugs.debian.org: > reassign 664396 src:vsdump Bug #664396 [vsdump] [PATCH] vsdump: Helping to update to packaging format 3.0 Bug reassigned from package 'vsdump' to 'src:vsdump'. Ignoring request to alter found versions of bug #664396 to the same values previously set Ignoring request to alter fixed versions of bug #664396 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 664396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664396 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 664396 is serious
Processing commands for cont...@bugs.debian.org: > severity 664396 serious Bug #664396 [vsdump] [PATCH] vsdump: Helping to update to packaging format 3.0 Severity set to 'serious' from 'wishlist' > thanks Stopping processing here. Please contact me if you need assistance. -- 664396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664396 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013009: marked as done (openjfx: ftbfs with GCC-12)
Your message dated Fri, 28 Oct 2022 00:21:33 + with message-id and subject line Bug#1013009: fixed in openjfx 11.0.11+0-1.1 has caused the Debian Bug report #1013009, regarding openjfx: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1013009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:openjfx Version: 11.0.11+1-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/openjfx_11.0.11+1-1_unstable_gcc12.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':web:compileNativeLinux'. at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:100) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:70) at org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51) at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:62) at org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54) at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:60) at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:97) at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:87) at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:52) at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52) at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54) at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43) at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34) at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.run(DefaultTaskGraphExecuter.java:248) at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336) at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328) at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199) at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110) at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:241) at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.
Bug#1004638: marked as done (openjfx: FTBFS with ffmpeg 5.0)
Your message dated Fri, 28 Oct 2022 00:21:33 +
with message-id
and subject line Bug#1004638: fixed in openjfx 11.0.11+0-1.1
has caused the Debian Bug report #1004638,
regarding openjfx: FTBFS with ffmpeg 5.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.)
--
1004638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjfx
Version: 11.0.11+0-1
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0
openjfx FTBFS with ffmpeg 5.0 (available in experimental):
| gcc -fPIC -Wformat -Wextra -Wformat-security -fstack-protector
-Werror=implicit-function-declaration -Werror=trampolines -fbuiltin
-DHAVE_STDINT_H -DLINUX -DGST_DISABLE_LOADSAVE -DGSTREAMER_LITE
-ffunction-sections -fdata-sections -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-ffile-prefix-map=/<>/modules/javafx.media/src/main/native/gstreamer/projects/linux/avplugin=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall -msse2
-I../../../plugins -I../../../plugins/av -I../../../gstreamer-lite/gstreamer
-I../../../gstreamer-lite/gstreamer/libs -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/x86_64-linux-gnu -c
../../../plugins/av/videodecoder.c -o
/<>/modules/javafx.media/build/native/linux/Release/obj/plugins/avplugin/av/videodecoder.o
| In file included from /usr/include/glib-2.0/glib/gthread.h:32,
| from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
| from /usr/include/glib-2.0/glib.h:32,
| from ../../../gstreamer-lite/gstreamer/gst/gst.h:27,
| from ../../../plugins/av/decoder.h:29,
| from ../../../plugins/av/decoder.c:26:
| ../../../plugins/av/decoder.c: In function ‘basedecoder_get_type’:
| /usr/include/glib-2.0/glib/gatomic.h:113:5: warning: argument 2 of
‘__atomic_load’ discards ‘volatile’ qualifier [-Wincompatible-pointer-types]
| 113 | __atomic_load (gapg_temp_atomic, &gapg_temp_newval,
__ATOMIC_SEQ_CST); \
| | ^
| /usr/include/glib-2.0/glib/gthread.h:260:7: note: in expansion of macro
‘g_atomic_pointer_get’
| 260 | (!g_atomic_pointer_get (location) && \
| | ^~~~
| ../../../plugins/av/decoder.c:58:9: note: in expansion of macro
‘g_once_init_enter’
|58 | if (g_once_init_enter (&gonce_data))
| | ^
| ../../../plugins/av/decoder.c:64:16: warning: cast between incompatible
function types from ‘void (*)(void *)’ to ‘void (*)(void *, void *)’
[-Wcast-function-type]
|64 |(GClassInitFunc) basedecoder_class_intern_init,
| |^
| ../../../plugins/av/decoder.c:66:16: warning: cast between incompatible
function types from ‘void (*)(BaseDecoder *)’ {aka ‘void (*)(struct
_BaseDecoder *)’} to ‘void (*)(GTypeInstance *, void *)’ {aka ‘void (*)(struct
_GTypeInstance *, void *)’} [-Wcast-function-type]
|66 |(GInstanceInitFunc) basedecoder_init,
| |^
| ../../../plugins/av/decoder.c: In function ‘basedecoder_init’:
| ../../../plugins/av/decoder.c:73:43: warning: unused parameter ‘self’
[-Wunused-parameter]
|73 | static void basedecoder_init(BaseDecoder *self)
| | ~^~~~
| ../../../plugins/av/decoder.c: In function ‘basedecoder_class_init’:
| ../../../plugins/av/decoder.c:79:5: error: implicit declaration of function
‘avcodec_register_all’ [-Werror=implicit-function-declaration]
|79 | avcodec_register_all();
| | ^~~~
| ../../../plugins/av/decoder.c: In function ‘basedecoder_open_decoder’:
| ../../../plugins/av/decoder.c:112:20: warning: assignment discards ‘const’
qualifier from pointer target type [-Wdiscarded-qualifiers]
| 112 | decoder->codec = avcodec_find_decoder(id);
| |^
| ../../../plugins/av/decoder.c: In function ‘basedecoder_set_codec_data’:
| ../../../plugins/av/decoder.c:169:17: warning: ‘g_memdup’ is deprecated: Use
'g_memdup2' instead [-Wdeprecated-declarations]
| 169 | decoder->codec_data = g_memdup(info.data, info.size);
| | ^~~
| In file included from /usr/include/glib-2.0/glib.h:82,
| from ../../../gstreamer-lite/gstreamer/gst/gst.h:27,
| from ../../../plugins/av/decoder.h:29,
| from ../../../plugins/av/decoder.c:26:
| /usr/include/glib-2.0/glib/gstrfuncs.h:25
Bug#1022934: libpappsomspp: FTBFS on i386
Source: libpappsomspp Version: 0.8.55-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=libpappsomspp&arch=i386&ver=0.8.55-1%2Bb1&stamp=1666460310&raw=0 term_listb.size= 8 MOD:00397 mass=57.021463721083 MOD:00429 mass=28.031300128964 MOD:00382 mass=-20.026214748524 MOD:00234 mass=305.068156389475 MOD:00838 mass=3.018830236677 A 71.037113785565 R 156.10025652 C 103.009184959665 D 115.026943024685 E 129.042593089167 F 147.068413914529 G 57.021463721083 H 137.058911859647 I 113.084063979011 K 128.094963016052 L 113.084063979011 M 131.040485088629 N 114.042927442166 P 97.052763850047 Q 128.058577506648 R 156.10025652 S 87.032028405125 T 101.047678469607 V 99.068413914529 W 186.07931295157 Y 163.063328534089 U 168.964198469607 O 255.158291550141 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 0% 0% 10% 20% ..:: Test 1 OK ::.. ..:: second test, new calibration parameters ::.. ..:: Test 2 OK ::.. === test cases: 32 | 31 passed | 1 failed assertions: 345 | 343 passed | 2 failed 94% tests passed, 1 tests failed out of 18 Total Test time (real) = 3.47 sec The following tests FAILED: 1 - catch2-only-tests (Failed) Errors while running CTest make[2]: *** [Makefile:94: test] Error 8 Cheers -- Sebastian Ramacher
Bug#1004638: openjfx: diff for NMU version 11.0.11+0-1.1
[Note that mails to nnn...@bug.debian.org does not reach the submitter.] On 2022-10-26 18:33:39 +0200, Emmanuel Bourg wrote: > Le 26/10/2022 à 01:27, Sebastian Ramacher a écrit : > > > Dear maintainer, > > > > I've prepared an NMU for openjfx (versioned as 11.0.11+0-1.1) and > > uploaded it to DELAYED/2. Please feel free to tell me if I > > should delay it longer. > > Hi Sebastian, > > Thank you for the update, but could you send a PR on Salsa instead of > uploading NMUs please? As there is no bookworm branch (or something similar) available, I cannot create a PR on salsa. You can take the changes from https://salsa.debian.org/sramacher/openjfx/-/tree/bookworm Cheers -- Sebastian Ramacher
Bug#937049: mini-buildd: Python2 removal in sid/bullseye
Am Fri, Aug 30, 2019 at 07:26:40AM + schrieb Matthias Klose: > Package: src:mini-buildd > Version: 1.0.41 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the distribution, as discussed in > https://lists.debian.org/debian-python/2019/07/msg00080.html How close is the 2.x branch in experimental from being a replacement? python2 will be dropped in bookworm and also removed from the archive. Cheers, Moritz
Bug#1022931: Should viewmol be removed?
Source: viewmol Version: 2.4.1-26 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 (which will soon be removed) - Dead upstream - Dropped from testing for over two years If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Bug#1022932: Should fbpanel be removed?
Source: fbpanel Version: 7.0-4.3 Severity: serious Your package came up as a candidate for removal from Debian: - Depends on Python 2, which will soon be removed - Last maintainer upload five years ago - Dead upstream If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Processed: closing 1022288
Processing commands for cont...@bugs.debian.org: > close 1022288 Bug #1022288 [src:rust-fd-lock] rust-fd-lock: FTBFS: unsatisfiable build-dependencies: librust-io-lifetimes-0.7+async-std-dev, librust-io-lifetimes-0.7+fs-err-dev, librust-io-lifetimes-0.7+mio-dev, librust-io-lifetimes-0.7+os-pipe-dev, librust-io-lifetimes-0.7+socket2-dev, librust-io-lifetimes-0.7+tokio-dev, librust-io-lifetimes-0.7-dev, librust-rustc-std-workspace-alloc-1+default-dev Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1022288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022288 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022806: linux-image-5.10.0-19-amd64: amggpu unbootable problem persists
On woensdag 26 oktober 2022 12:43:02 CEST Alexis Huxley wrote: > Following other reports of post-grub kernel hangs on systems with > amdgpu, I waited for new release of linux-image-5.10.0-19-amd64, > which came quickly, but it did not solve the problem for me. > > Symptoms are: grub loads kernel and a few seconds into the > scrolling messages from the kernel the system hangs. The screen > is blank. The system is not accessible over the network. AFAICT, which may be incorrect, the issue is slightly different from the other related bug report (#1022042) in that here it is a system which does not boot. The other problem that is fixed, is where the system does boot, but the graphics don't work correctly. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022042#105 is where Andreas Wirooks (See also https://gitlab.freedesktop.org/drm/amd/-/issues/ 2216#note_1601632) reported on that/this issue and in msg 110 'inasprecali' reported the same issue (AFAICT). See also the msgs that follow, which may give hints as to where the non-boot issue may come from. It _may_ also be related to older chipset variants. HTH, Diederik signature.asc Description: This is a digitally signed message part.
Bug#1022806: linux-image-5.10.0-19-amd64: amggpu unbootable problem persists
Hi All, > Would you be able to start own kenel builds, confirming it does not > happen with 5.10.140 upstream but with 5.10.149, and isolate the > breaking change? > > (Are you able to boot the kernel from bullseye-backports?) I will try to do this, but owing to my schedule, it will be only Tuesday before I can try. If you did the kernel building and sent me download links then I can test them, which is obviously a lot less work for me, but a lot more for you. Otherwise I'll let you know how I get on next week. Sorry to have submitted tbe report and then immediatey not be available to do the followup. Regards, Alexis
Bug#1022806: linux-image-5.10.0-19-amd64: amggpu unbootable problem persists
Hi Alexis, [Cc'ing Alex Deucher who addressed the previous regressions as well] On Wed, Oct 26, 2022 at 12:43:02PM +0200, Alexis Huxley wrote: > Package: src:linux > Version: 5.10.149-2 > Severity: serious > Justification: 1022025, 1022051, 1022062, 1022070, 1022097, 1022147 marked > serious so this marked serious too > > Dear Maintainer, > > Following other reports of post-grub kernel hangs on systems with > amdgpu, I waited for new release of linux-image-5.10.0-19-amd64, > which came quickly, but it did not solve the problem for me. > > Symptoms are: grub loads kernel and a few seconds into the > scrolling messages from the kernel the system hangs. The screen > is blank. The system is not accessible over the network. > > I reverted to linux-image-5.10.0-18-amd64 and all is okay again. > > The crash happens pretty early on: I believe X has not yet tried > to start. Both /var/log/syslog and /var/log/messages contain > no entries pertaining to the hanging boot (only messages from > where the earlier shutdown of 18 and the later start of 18). > > Output from lscpu is below. > > Automatically included output (e.g. kernel version) pertains > to linux-image-5.10.0-18-amd64, as I am unable to boot > linux-image-5.10.0-19-amd64. I don't remove it in case it contains > other pertinent information. > > I'm happy to test with other kernels or provide any requested > files/output. Would you be able to start own kenel builds, confirming it does not happen with 5.10.140 upstream but with 5.10.149, and isolate the breaking change? (Are you able to boot the kernel from bullseye-backports?) Regards, Salvatore
Bug#1022927: libghc-aeson-dev depends on non-existing libghc-semialign-dev-1.2.0.1-ebc3a
Package: libghc-aeson-dev Version: 2.0.3.0-1+b4 Severity: serious Hi, libghc-aeson-dev on amd64c depends on libghc-semialign-dev-1.2.0.1-ebc3a which does not exist in the archive. The situation is the same on other arches with a different hash of libghc-semialign-dev-1.2.0.1. -Ralf.
Bug#1021674: marked as done (src:kpcli: fails to migrate to testing for too long: uploader built arch:all binary)
Your message dated Thu, 27 Oct 2022 19:49:59 + with message-id and subject line Bug#1021674: fixed in kpcli 3.8.1-1.1 has caused the Debian Bug report #1021674, regarding src:kpcli: fails to migrate to testing for too long: uploader built arch:all binary 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.) -- 1021674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021674 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kpcli Version: 3.7-1 Severity: serious Control: close -1 3.8.1-1 Tags: sid bookworm pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:kpcli has been trying to migrate for 61 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 bookworm, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=kpcli OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: kpcli Source-Version: 3.8.1-1.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of kpcli, 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 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated kpcli package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 12 Oct 2022 20:33:17 +0200 Source: kpcli Architecture: source Version: 3.8.1-1.1 Distribution: unstable Urgency: medium Maintainer: Arno Töll Changed-By: Paul Gevers Closes: 1021674 Changes: kpcli (3.8.1-1.1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #1021674) Checksums-Sha1: 025148d1cc66f07afc36fb49b64ccc6befd3fc5d 1616 kpcli_3.8.1-1.1.dsc ca5b47171359ec22ad96356209754d5a5c7b8e53 3384 kpcli_3.8.1-1.1.debian.tar.xz Checksums-Sha256: 8748054a4fbbb3fc166890f00d65fb87d3a64850813b714bbe4348d6d9dee3b5 1616 kpcli_3.8.1-1.1.dsc 82d6fc4de70a39ff9a3d9d85b0a374560eb996cc40c5c7f1f4932e72b133f59d 3384 kpcli_3.8.1-1.1.debian.tar.xz Files: 744f8d68e9718089554f309bbc15a9c0 1616 utils optional kpcli_3.8.1-1.1.dsc 6f4f6c08eccce56812aa6319bf98f457 3384 utils optional kpcli_3.8.1-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmNHC7EACgkQnFyZ6wW9 dQokeAgAjj+28bZExHlRAZatTu0tNdiLnOXiovCYeTVZoH7XsEsZzPtQhfPLWzTl 9LmOLOOQCtbM8afuWkpegTHAdRU/HUwf6j2xte5umttrlOMQcndyvwkFzcSWcoPI 4L2bO9o9hvNeSbqmIfQg6CJCN7Ol4cG4cYtNm3awny1p9OKIalIC1m7HRTsF+A3m MqDjpsBl/x2HvzA6aBEvnoxV1vz9KbT90k5gea7TqmWvRj+25GBDMx4VF2dwLRjN usmLoI5pbDz4iTlFDzzF5VcAQYl0tLWYfZJKrwWk12QpBtj6dWsIi25txbSiYBS6 5vIQa5o7p9DPfA8CIZUpgx17C0Tgug== =hImL -END PGP SIGNATURE End Message ---
Processed: Re: Bug#1020087: guile-ssh: FTBFS: dh_auto_test: error: cd debian/build/guile-3.0 && make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2
Processing control commands: > forwarded 1020087 https://github.com/artyom-poptsov/guile-ssh/issues/34 Bug #1020087 [src:guile-ssh] guile-ssh: FTBFS: dh_auto_test: error: cd debian/build/guile-3.0 && make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2 Set Bug forwarded-to-address to 'https://github.com/artyom-poptsov/guile-ssh/issues/34'. -- 1020087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020087: guile-ssh: FTBFS: dh_auto_test: error: cd debian/build/guile-3.0 && make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2
Control: forwarded 1020087 https://github.com/artyom-poptsov/guile-ssh/issues/34 On 2022-09-18, Lucas Nussbaum wrote: >> make[5]: Entering directory '/<>/debian/build/guile-3.0/tests' >> PASS: log.scm >> FAIL: server.scm >> PASS: session.scm >> FAIL: client-server.scm >> PASS: popen.scm >> PASS: shell.scm >> PASS: server-client.scm >> PASS: sssh-ssshd.scm >> FAIL: key.scm >> PASS: tunnel.scm >> PASS: dist.scm >> >>Guile-SSH 0.13.1: tests/test-suite.log >> >> >> # TOTAL: 11 >> # PASS: 8 >> # SKIP: 0 >> # XFAIL: 0 >> # FAIL: 3 >> # XPASS: 0 >> # ERROR: 0 I believe this is due to the new libssh 0.10.x version introduced middle of september 2022 and compatibility issues in guile-ssh's test suite. I've confirmed the issue on guile-ssh 0.13.x, 0.15.x and 0.16.x locally, and the reproducible builds tests also confirm this rough timing: https://tests.reproducible-builds.org/debian/history/amd64/guile-ssh.html Forwarded the bug upstream. live well, vagrant signature.asc Description: PGP signature
Bug#1022806: Bug#1022025: fixed in linux 5.10.149-2
Hi, On Thu, Oct 27, 2022 at 07:12:43PM +, inasprecali wrote: > On Thu, 27 Oct 2022 21:01:15 +0200 Salvatore Bonaccorso > wrote: > > Can you please fill a new bug for your issue, which would still > > be > > present in the 5.10.149-2 release? There are two users which > > report > > that they still have problems with the amdgpu driver still in > > 5.10.149-2. > > I think bug 1022806 is a recent one referring to 5.10.149-2 > specifically, which is about this same issue. I don't think there > is a need to report yet another bug about it. Yes this is indeed enough. Regards, Salvatore
Bug#1022025: fixed in linux 5.10.149-2
On Thu, 27 Oct 2022 21:01:15 +0200 Salvatore Bonaccorso wrote: > Can you please fill a new bug for your issue, which would still > be > present in the 5.10.149-2 release? There are two users which > report > that they still have problems with the amdgpu driver still in > 5.10.149-2. I think bug 1022806 is a recent one referring to 5.10.149-2 specifically, which is about this same issue. I don't think there is a need to report yet another bug about it. Best regards. -- inasprecali
Bug#1022025: fixed in linux 5.10.149-2
Hi On Thu, Oct 27, 2022 at 05:21:32PM +, inasprecali wrote: > On Thu, 27 Oct 2022 06:17:10 + Debian FTP Masters > wrote: > > Source: linux > > Source-Version: 5.10.149-2 > > Done: Salvatore Bonaccorso > > > > We believe that the bug you reported is fixed in the latest > version of > > linux, which is due to be installed in the Debian FTP archive. > > I'm sorry, but your belief seems to be mistaken, since we have > multiple reports o 5.10.149-2 still not booting with the amdgpu > driver. Can you please fill a new bug for your issue, which would still be present in the 5.10.149-2 release? There are two users which report that they still have problems with the amdgpu driver still in 5.10.149-2. Thanks already, let's folloup there with some questions. Regards, Salvatore
Processed: Re: Bug#1022848: linux: 6.0.5 fixes critical btrfs bug
Processing control commands: > severity -1 important Bug #1022848 [src:linux] 6.0.5 fixes critical btrfs bug in 6.0.3, affecting space cache v1 filesystems Severity set to 'important' from 'critical' -- 1022848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022848: linux: 6.0.5 fixes critical btrfs bug
Control: severity -1 important Hi, On Wed, Oct 26, 2022 at 10:23:35PM +0200, Christoph Anton Mitterer wrote: > Source: linux > Version: 5.19.6-1 > Severity: critical > Justification: breaks the whole system > > > Hi. > > 6.0.3 introduced a commit that causes (permanent) CPU soft lockups > for some people with btrfs filesystems, effectively breaking the > system, e.g. when booting. According to your references there is the workaround of mounting with clear_cache,space_cache=v2 and convert the filesystem. What would one prevent doing so? I'm downgrading the severity to important as it does not make the kernel unbootable or unstable on common hardware or all systems that a flavour is supposed to support. While I agree it is important to fix, this issue should not block the migration of the current kernel to address CVE-2022-2602. I will work next on importing the newer 6.0.y versions which include a fix for this issue as well. Regards, Salvatore
Processed: tagging 1022848
Processing commands for cont...@bugs.debian.org: > tags 1022848 + upstream Bug #1022848 [src:linux] 6.0.5 fixes critical btrfs bug in 6.0.3, affecting space cache v1 filesystems Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1022848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022322: marked as done (lugaru: FTBFS: gamegl.hpp:48:10: fatal error: GL/glu.h: No such file or directory)
Your message dated Thu, 27 Oct 2022 17:49:49 + with message-id and subject line Bug#1022322: fixed in lugaru 1.2-6 has caused the Debian Bug report #1022322, regarding lugaru: FTBFS: gamegl.hpp:48:10: fatal error: GL/glu.h: No such file or directory 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.) -- 1022322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022322 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lugaru Version: 1.2-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/c++ -DBinIO_STDINT_HEADER="" > -DDATA_DIR=\"/usr/share/games/lugaru\" -DPLATFORM_LINUX=1 -DPLATFORM_UNIX=1 > -I/usr/include/AL -I/usr/include/SDL2 -I/<>/Source -Wall -Wextra > -Wno-parentheses -pedantic --std=gnu++11 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -MD -MT > CMakeFiles/lugaru.dir/Source/Devtools/ConsoleCmds.cpp.o -MF > CMakeFiles/lugaru.dir/Source/Devtools/ConsoleCmds.cpp.o.d -o > CMakeFiles/lugaru.dir/Source/Devtools/ConsoleCmds.cpp.o -c > /<>/Source/Devtools/ConsoleCmds.cpp > In file included from /<>/Source/Math/XYZ.hpp:24, > from /<>/Source/Audio/openal_wrapper.hpp:24, > from /<>/Source/Audio/openal_wrapper.cpp:21: > /<>/Source/Graphic/gamegl.hpp:48:10: fatal error: GL/glu.h: No > such file or directory >48 | #include > | ^~ > compilation terminated. > In file included from /<>/Source/Math/XYZ.hpp:24, > from /<>/Source/Animation/Animation.hpp:23, > from /<>/Source/Animation/Skeleton.hpp:24, > from /<>/Source/Game.hpp:24, > from /<>/Source/main.cpp:21: > /<>/Source/Graphic/gamegl.hpp:48:10: fatal error: GL/glu.h: No > such file or directory >48 | #include > | ^~ > In file included from /<>/Source/Math/XYZ.hpp:24, > from /<>/Source/Animation/Animation.hpp:23, > from /<>/Source/Animation/Skeleton.hpp:24, > from /<>/Source/Game.hpp:24, > from /<>/Source/Devtools/ConsoleCmds.cpp:23: > /<>/Source/Graphic/gamegl.hpp:48:10: fatal error: GL/glu.h: No > such file or directory >48 | #include > | ^~ > compilation terminated. > compilation terminated. > In file included from /<>/Source/Math/XYZ.hpp:24, > from /<>/Source/Animation/Animation.hpp:23, > from /<>/Source/Animation/Animation.cpp:20: > /<>/Source/Graphic/gamegl.hpp:48:10: fatal error: GL/glu.h: No > such file or directory >48 | #include > | ^~ > In file included from /<>/Source/Math/XYZ.hpp:24, > from /<>/Source/Animation/Joint.hpp:24, > from /<>/Source/Animation/Muscle.hpp:24, > from /<>/Source/Animation/Muscle.cpp:21: > /<>/Source/Graphic/gamegl.hpp:48:10: fatal error: GL/glu.h: No > such file or directory >48 | #include > | ^~ > compilation terminated. > compilation terminated. > In file included from /<>/Source/Math/XYZ.hpp:24, > from /<>/Source/Animation/Animation.hpp:23, > from /<>/Source/Animation/Skeleton.hpp:24, > from /<>/Source/Animation/Skeleton.cpp:21: > /<>/Source/Graphic/gamegl.hpp:48:10: fatal error: GL/glu.h: No > such file or directory >48 | #include > | ^~ > compilation terminated. > In file included from /<>/Source/Math/XYZ.hpp:24, > from /<>/Source/Audio/Sounds.hpp:23, > from /<>/Source/Audio/Sounds.cpp:20: > /<>/Source/Graphic/gamegl.hpp:48:10: fatal error: GL/glu.h: No > such file or directory >48 | #include > | ^~ > In file included from /<>/Source/Math/XYZ.hpp:24, > from /<>/Source/Animation/Joint.hpp:24, > from /<>/Source/Animation/Joint.cpp:21: > /<>/Source/Graphic/gamegl.hpp:48:10: fatal error: GL/glu.h: No > such file or directory >48 | #include > | ^~ > compilation terminated. > compilation terminated. > make[3]: *** [CMakeFiles/lugaru.dir/build.make:149: > CMakeFiles/lugaru.dir/Source/Audio/openal_wrapper.cpp.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/10/23/lugaru_1.2-5_unstable.log
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> unarchive 983090
Bug #983090 {Done: Chris Lamb } [python-django]
python-django: CVE-2021-23336
Unarchived Bug 983090
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
983090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983090
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> unarchive 969367
Bug #969367 {Done: Chris Lamb } [python-django]
python-django: CVE-2020-24583 CVE-2020-24584
Unarchived Bug 969367
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
969367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> unarchive 981562
Bug #981562 {Done: Chris Lamb } [python-django]
python-django: CVE-2021-3281
Unarchived Bug 981562
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
981562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#957123: marked as done (dballe: ftbfs with GCC-10)
Your message dated Thu, 27 Oct 2022 18:00:11 + with message-id and subject line Bug#957123: fixed in dballe 9.3-1 has caused the Debian Bug report #957123, regarding dballe: 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.) -- 957123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:dballe Version: 8.6-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/dballe_8.6-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 [...] libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -DTABLE_DIR=\"/usr/share/wreport\" -I.. -I.. -I/usr/include/lua5.1 -I/usr/include/postgresql -I/usr/include/mariadb -I/usr/include/mariadb/.. -Werror -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -c db/v7/export.cc -o db/v7/libdballe_la-export.o >/dev/null 2>&1 libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -DTABLE_DIR=\"/usr/share/wreport\" -I.. -I.. -I/usr/include/lua5.1 -I/usr/include/postgresql -I/usr/include/mariadb -I/usr/include/mariadb/.. -Werror -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -c db/summary-access.cc -o db/libdballe_la-summary-access.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -DTABLE_DIR=\"/usr/share/wreport\" -I.. -I.. -I/usr/include/lua5.1 -I/usr/include/postgresql -I/usr/include/mariadb -I/usr/include/mariadb/.. -Werror -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o db/libdballe_la-explorer.lo `test -f 'db/explorer.cc' || echo './'`db/explorer.cc libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -DTABLE_DIR=\"/usr/share/wreport\" -I.. -I.. -I/usr/include/lua5.1 -I/usr/include/postgresql -I/usr/include/mariadb -I/usr/include/mariadb/.. -Werror -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -c db/explorer.cc -fPIC -DPIC -o db/.libs/libdballe_la-explorer.o /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -DTABLE_DIR=\"/usr/share/wreport\" -I.. -I.. -I/usr/include/lua5.1 -I/usr/include/postgresql -I/usr/include/mariadb -I/usr/include/mariadb/.. -Werror -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o sql/libdballe_la-postgresql.lo `test -f 'sql/postgresql.cc' || echo './'`sql/postgresql.cc libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -DTABLE_DIR=\"/usr/share/wreport\" -I.. -I.. -I/usr/include/lua5.1 -I/usr/include/postgresql -I/usr/include/mariadb -I/usr/include/mariadb/.. -Werror -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -c sql/postgresql.cc -fPIC -DPIC -o sql/.libs/libdballe_la-postgresql.o /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -DTABLE_DIR=\"/usr/share/wreport\" -I.. -I.. -I/usr/include/lua5.1 -I/usr/include/postgresql -I/usr/include/mariadb -I/usr/include/mariadb/.. -Werror -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o sql/libdballe_la-mysql.lo `test -f
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> unarchive 1014541
Bug #1014541 {Done: Salvatore Bonaccorso } [python-django]
python-django: CVE-2022-34265
Unarchived Bug 1014541
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1014541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:llvm-toolchain-15
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:llvm-toolchain-15 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1022169 (http://bugs.debian.org/1022169) > # Bug title: llvm-toolchain-15: FTBFS on mips*el: static assertion failed: > struct_kernel_stat_sz == sizeof(stat) > # * https://github.com/llvm/llvm-project/issues/57521 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1022169 + fixed-upstream Bug #1022169 [src:llvm-toolchain-15] llvm-toolchain-15: FTBFS on mips*el: static assertion failed: struct_kernel_stat_sz == sizeof(stat) Added tag(s) fixed-upstream. > usertags 1022169 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1022169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022169 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022025: fixed in linux 5.10.149-2
On Thu, 27 Oct 2022 06:17:10 + Debian FTP Masters wrote: > Source: linux > Source-Version: 5.10.149-2 > Done: Salvatore Bonaccorso > > We believe that the bug you reported is fixed in the latest version of > linux, which is due to be installed in the Debian FTP archive. I'm sorry, but your belief seems to be mistaken, since we have multiple reports o 5.10.149-2 still not booting with the amdgpu driver. Best regards. -- inasprecali
Bug#1021478: marked as done (mmdebstrap - Enables first boot experience via machine-id)
Your message dated Thu, 27 Oct 2022 16:21:35 + with message-id and subject line Bug#1021478: fixed in mmdebstrap 1.2.2-1 has caused the Debian Bug report #1021478, regarding mmdebstrap - Enables first boot experience via machine-id 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.) -- 1021478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mmdebstrap Version: 1.2.1-2 Severity: serious mmdebstrap writed "uninitialized" to /etc/machine-id. This triggers first boot semantic[1], so makes the boot wait for input. Please write an empty file if you are not equipped to handle first boot questions. Bastian [1]: https://www.freedesktop.org/software/systemd/man/machine-id.html -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (700, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.19.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mmdebstrap depends on: ii apt 2.5.3 ii perl 5.34.0-5 ii python3 3.10.6-1 Versions of packages mmdebstrap recommends: pn arch-test pn fakechroot ii fakeroot 1.29-1 ii gpg 2.2.39-1 pn libdistro-info-perl ii libdpkg-perl 1.21.9 ii mount2.38.1-1 pn uidmap Versions of packages mmdebstrap suggests: ii apt [apt-transport-https] 2.5.3 pn apt-transport-tor ii apt-utils 2.5.3 pn binfmt-support ii ca-certificates20211016 pn debootstrap ii distro-info-data 0.54 ii dpkg-dev 1.21.9 pn genext2fs pn perl-doc pn proot pn qemu-user pn qemu-user-static pn squashfs-tools-ng --- End Message --- --- Begin Message --- Source: mmdebstrap Source-Version: 1.2.2-1 Done: Johannes Schauer Marin Rodrigues We believe that the bug you reported is fixed in the latest version of mmdebstrap, 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 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Johannes Schauer Marin Rodrigues (supplier of updated mmdebstrap package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 27 Oct 2022 17:50:11 +0200 Source: mmdebstrap Architecture: source Version: 1.2.2-1 Distribution: unstable Urgency: medium Maintainer: Johannes Schauer Marin Rodrigues Changed-By: Johannes Schauer Marin Rodrigues Closes: 1021478 Changes: mmdebstrap (1.2.2-1) unstable; urgency=medium . * new upstream release * write an empty /etc/machine-id instead of writing 'uninitialized' (Closes: #1021478) Checksums-Sha1: 98ba367141456ec15d46d810e2dd39f68b1ea9dd 2329 mmdebstrap_1.2.2-1.dsc 30466427a3d249c35bb08ff2df9e1cbc761a0345 128660 mmdebstrap_1.2.2.orig.tar.gz ab569eeb2ef5837305d9ac7305c35e0af40dbef9 11264 mmdebstrap_1.2.2-1.debian.tar.xz Checksums-Sha256: e1c1b678f67fda401536fe67623e42aad7039838001e70c121a3d1c78489665f 2329 mmdebstrap_1.2.2-1.dsc 85e302fa0fadb55bbffa89276bfbbfde2f3059582bdd3fd25b0fdc50be9395ba 128660 mmdebstrap_1.2.2.orig.tar.gz abb5f72f3b23e494b2a6cfdd1bffc3b40dafb2e1b74b3e4ac71a24face22ca02 11264 mmdebstrap_1.2.2-1.debian.tar.xz Files: e417e2efaa4cac7bd642f50a57e68028 2329 admin optional mmdebstrap_1.2.2-1.dsc 1f3e2766fd13e3aa99d495b35c79d098 128660 admin optional mmdebstrap_1.2.2.orig.tar.gz 9320eb9ba486ca823f6ab5a65ac52a74 11264 admin optional mmdebstrap_1.2.2-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAmNaq8kACgkQ8sulx4+9 g+EdnQ//bF9O0w2Hkg46v+ykmadgRDC4idSHDFPnKfMLq1065Ol551paBkPVsnEG voO+8q7cx5RHHWh31dBLSsHk3lwxI68VVdrn0nK6EWKGb5nWNdao+5SIbPC89xMz wL1w0GFY/HlOP0mpdI3XnbBkSfH6PhAUadEDlburhn4t9/cmneJgfUbR7KoTCT2K By+565g0ezJjjnuz2aR4BfNS24g5o4S
Bug#1022920: Removal notice: obsolete
Source: haskell-thyme Version: 0.3.5.5-5 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS * Seems unmaintained; Last upload more than 7 years ago * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias
Bug#1022918: Removal notice: obsolete
Source: haskell-text-format Version: 0.3.2-4 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS * Seems unmaintained; Last upload more than 3 years ago * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias
Bug#1022914: Removal notice: obsolete
Source: haskell-test-framework-th Version: 0.2.4-12 Severity: serious I intend to remove this package: * It has no rev dependencies * Seems unmaintained; Last upload more than 10 years ago * It's not part of the latest Stackage LTS * Depends on deprecated software (see #1022040) If you believe we should keep this package in Debian, please close this bug report. -- Ilias
Bug#1022913: Removal notice: obsolete
Source: haskell-test-framework-th-prime Version: 0.0.10-4 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS * Seems unmaintained; Last upload more than 5 years ago * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias
Bug#1022896: marked as done (rust-rusty-pool: autopkgtest failure)
Your message dated Thu, 27 Oct 2022 14:55:00 + with message-id and subject line Bug#1022896: fixed in rust-rusty-pool 0.7.0-3 has caused the Debian Bug report #1022896, regarding rust-rusty-pool: autopkgtest 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.) -- 1022896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-rusty-pool Version: 0.7.0-2 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-rusty-pool/27568708/log.gz ... autopkgtest [03:39:50]: test librust-rusty-pool+default-dev:default: /usr/share/cargo/bin/cargo-auto-test rusty_pool 0.7.0 --all-targets autopkgtest [03:39:50]: test librust-rusty-pool+default-dev:default: [--- crate directory not found: /usr/share/cargo/registry/rusty_pool-0.7.0 autopkgtest [03:39:50]: test librust-rusty-pool+default-dev:default: ---] autopkgtest [03:39:51]: test librust-rusty-pool+default-dev:default: - - - - - - - - - - results - - - - - - - - - - librust-rusty-pool+default-dev:default FAIL non-zero exit status 1 autopkgtest [03:39:51]: summary rust-rusty-pool:@FAIL non-zero exit status 1 --- End Message --- --- Begin Message --- Source: rust-rusty-pool Source-Version: 0.7.0-3 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of rust-rusty-pool, 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 1022...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated rust-rusty-pool package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 27 Oct 2022 15:45:58 +0200 Source: rust-rusty-pool Architecture: source Version: 0.7.0-3 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Closes: 1022896 Changes: rust-rusty-pool (0.7.0-3) unstable; urgency=medium . * fix set X-Cargo-Crate: rusty_pool; closes: bug#1022896, thanks to Adrian Bunk * temporarily set RUST_BACKTRACE=full to aid in debugging bug#1022895 Checksums-Sha1: ea9ea4fa5654bc055c2e73aaa6c6d41bae80685b 2376 rust-rusty-pool_0.7.0-3.dsc 5ab629d7ca3a5da36b783fa248bb5b74ce27fbf4 10076 rust-rusty-pool_0.7.0-3.debian.tar.xz 62c39f0b8dab4e4c73d8db6646db45b9398638e3 8546 rust-rusty-pool_0.7.0-3_amd64.buildinfo Checksums-Sha256: 267cf598cda725e448b49b9fc6ef07ed147a7abc74467c2c52e681269d16b525 2376 rust-rusty-pool_0.7.0-3.dsc 173744cb8f756865c667459affa38ed8360ded31a3b25ec2da317f13fda33060 10076 rust-rusty-pool_0.7.0-3.debian.tar.xz 564b618a1b244b67971892b2d94860c2e57ee1bc5486eae2203f67a6c5fa261e 8546 rust-rusty-pool_0.7.0-3_amd64.buildinfo Files: 82f0e707df3aae13cf60c2ce07754e1f 2376 rust optional rust-rusty-pool_0.7.0-3.dsc 08a2459823c853ef736dc87e85599320 10076 rust optional rust-rusty-pool_0.7.0-3.debian.tar.xz 073e705ca522c063f06c50ed48d3566d 8546 rust optional rust-rusty-pool_0.7.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmNajSIACgkQLHwxRsGg ASGLNRAAjpc5vrJF4oiCKeXAIq0VqccU8F01n3fxfsMNsfvg8I+r1OYCiXYyBP4B BRXsdNDZC515DRDb8w3xrS1lsir0ipLyqucNDSgrsH+/sXhf2cYRFpXlmB5JONl/ Dq7b01oMEurgjuzNKGJcwrQQC3ASzVMmUgPYCNMvkUcVdSEOCb0hszIx/x3AQ77z 0yH3/DvrKNX4YmEY3IEKLxjrhKwleQB5/upM5VphRmtVsGEqkn4Yrdl5tv1CrnC+ l2xAgmXZOTePTrzkIGZdlGzfuqJjuHYJ83CQmwKnOflaq2vRMe6CA93BDn2Lo9Ct FuyRB6qOMViZQsW7Q/S8eOb7YHh9nDS0Ptv9WV9hAqNek2UkzgKhGfO6mQD3+aC8 oWvt2RWekaq11tWezaq0ZKX07UAgk/l98BPkv8bKMPrbcp/5X6bLKWySzRxn/Y/E mY/k5NLaXcENC6D+y883w9x6ca5OqFHyL3uAcjpDEQWjknu2j5tdS/md9ONz/ZTW yQ59xgURuKFmMVuF0HPl9dCnSmyaSCVvwsT74hvUDH1XsjDkUtKYKeh1GbmL2n27 2Vca1UKQkZkqltXtrLUz4eRoxIR7WXiAQM30WUiyZ5Wm9RoMTDr3LZz7EFJG51ur 26+fXjlLK34wGcPsCHxYgr1jOJcuGmGv103PyQGIE7qqPdbeHIU= =tXZr -END PGP SIGNATURE End Message ---
Bug#1022910: Removal notice: obsolete
Source: haskell-regex-compat-tdfa Version: 0.95.1.4-8 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS * Seems unmaintained; Last upload more than 9 years ago * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias
Processed: merging 1022908 1022909
Processing commands for cont...@bugs.debian.org: > merge 1022908 1022909 Bug #1022908 [src:haskell-pipes-aeson] Removal notice: obsolete Bug #1022909 [src:haskell-pipes-aeson] Removal notice: obsolete Merged 1022908 1022909 > thanks Stopping processing here. Please contact me if you need assistance. -- 1022908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022908 1022909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022909: Removal notice: obsolete
Source: haskell-pipes-aeson Version: 0.4.1.8-4 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS * Seems unmaintained; Last upload more than 8 years ago * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias
Bug#1022908: Removal notice: obsolete
Source: haskell-pipes-aeson Version: 0.4.1.8-4 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS * Seems unmaintained; Last upload more than 5 years ago * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias
Bug#1021658: marked as done (latexml: AutoPKG test suite fails since latest upload of TLive)
Your message dated Thu, 27 Oct 2022 14:41:16 + with message-id and subject line Bug#1021658: fixed in latexml 0.8.6-5 has caused the Debian Bug report #1021658, regarding latexml: AutoPKG test suite fails since latest upload of TLive 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.) -- 1021658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: latexml Version: 0.8.6-4 Severity: important Dear Maintainer, This is just for the records: since the latest upload of texlive-base/texlive-lang/texlive-extra snapshot the latexml test suite fails to run. The issue is known in upstream. Hilmar -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.19.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages latexml depends on: ii imagemagick-6.q16 [imagemagick] 8:6.9.11.60+dfsg-1.3+b3 ii libarchive-zip-perl 1.68-1 ii libfile-which-perl 1.27-1 pn libimage-magick-perl pn libimage-size-perl ii libio-string-perl1.08-3.1 pn libjson-xs-perl ii libparse-recdescent-perl 1.967015+dfsg-3 pn libpod-parser-perl ii libtext-unidecode-perl 1.30-2 ii liburi-perl 5.14-1 pn libuuid-tiny-perl ii libwww-perl 6.67-1 ii libxml-libxml-perl 2.0207+dfsg+really+2.0134-1 ii libxml-libxslt-perl 2.002000-1 ii libxml2 2.9.14+dfsg-1+b1 ii libxslt1.1 1.1.35-1 ii perl 5.34.0-5 ii tex-common 6.17 ii texlive-latex-base 2022.20220923-1 latexml recommends no packages. latexml suggests no packages. -- sigmentation fault signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: latexml Source-Version: 0.8.6-5 Done: Hilmar Preusse We believe that the bug you reported is fixed in the latest version of latexml, 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 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilmar Preusse (supplier of updated latexml package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 27 Oct 2022 15:17:25 +0200 Source: latexml Architecture: source Version: 0.8.6-5 Distribution: unstable Urgency: medium Maintainer: Debian TeX Task Force Changed-By: Hilmar Preusse Closes: 1021658 Changes: latexml (0.8.6-5) unstable; urgency=medium . * Add patch from upstream to fix incompatibility to latest TeX Live checkout. (Closes: #1021658) Checksums-Sha1: d251545ac4b522d719ebcbabb9ad0718bdee3126 2758 latexml_0.8.6-5.dsc 02cb399b49d5bcdcf7976578231240532f4315cf 14488 latexml_0.8.6-5.debian.tar.xz 49a83dbe49451bb4b480d9a03c8cc87c936b3890 8713 latexml_0.8.6-5_source.buildinfo Checksums-Sha256: baffba203b841a09d23a6f8d4d33ce0cf2753f891bcf9be295535aa95548e807 2758 latexml_0.8.6-5.dsc 6564a6810d9dd9dcd2957beebe83cb0cb1276317ca0be0d98199d62d0dc5 14488 latexml_0.8.6-5.debian.tar.xz b3a3449512ed8ebf4d86b3254848a20587094ea68f80c83959324ba069ab1b5a 8713 latexml_0.8.6-5_source.buildinfo Files: 665170073f94246fa003d7b5ecf5d2a3 2758 tex optional latexml_0.8.6-5.dsc f27169a5a71ef0cc61ddf48b602fd830 14488 tex optional latexml_0.8.6-5.debian.tar.xz 9f0969addf65967f86d6a1a7db261a16 8713 tex optional latexml_0.8.6-5_source.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEaXGmC/nkbIhxf16kxiZYRqvgLIsFAmNahUVfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDY5 NzFBNjBCRjlFNDZDODg3MTdGNUVBNEM2MjY1ODQ2QUJFMDJDOEIACgkQxiZYRqvg LIsPCw/+OAkdshiuZMwHLuhmSAhQUqNJrxJc5XfaAkFXxmZmm4J3mnY8yFamKP3r HxciVqEdsg5CQre+AUOz/3kCTCmUmpsUteV2BwBO7Zt/jl5ggxGNBAQ3DXLCg
Processed: bug 1022896 is forwarded to https://github.com/robinfriedli/rusty_pool/issues/9
Processing commands for cont...@bugs.debian.org: > forwarded 1022896 https://github.com/robinfriedli/rusty_pool/issues/9 Bug #1022896 [src:rust-rusty-pool] rust-rusty-pool: autopkgtest failure Set Bug forwarded-to-address to 'https://github.com/robinfriedli/rusty_pool/issues/9'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1022896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1022896 is not forwarded
Processing commands for cont...@bugs.debian.org: > notforwarded 1022896 Bug #1022896 [src:rust-rusty-pool] rust-rusty-pool: autopkgtest failure Unset Bug forwarded-to-address > thanks Stopping processing here. Please contact me if you need assistance. -- 1022896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022906: Removal notice: obsolete
Source: haskell-monad-unlift Version: 0.2.0-6 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS * It's not part of the latest Stackage LTS * Deprecated in favor of unliftio-core, unliftio, rio If you believe we should keep this package in Debian, please close this bug report. -- Ilias
Bug#1022905: Removal notice: obsolete
Source: haskell-maths Version: 0.4.9-2 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS * Seems unmaintained; Last upload more than 4 years ago * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias
Bug#1022282: staden-io-lib: FTBFS: ./data/9827_rand3.cram.fai: No such file or directory
Dear Maintainer,
the original staden-io-lib seems to be built with
libhtscodecs2 in version 1.2.2-1 [1].
The rebuild seems to be using libhtscodecs2 in version 1.3.0-4.
Unfortunately htscodecs upstream integrated this commit [3],
which renamed e.g. function encode_names to tok3_encode_names.
It added a compatibility function encode_names, but does not
declare it in the header file.
Therefore in the build of staden-io-lib the function encode_names
is implicitly declared - therefore seems to default to
a return type of int [4] - and therefore the returned pointer
gets truncated to the lower 4 bytes [5].
This get through unnoticed until the pointer is freed and
produces a segfault there [6].
I guess the right thing would be to have the short function name
in the header file of htscodecs, therefore solve this issue for
other packages using htscodecs.
A short term solution might be the patch in [7] which makes
the build and tests succeed without "implicit declarations".
Kind regards,
Bernhard
[1]
https://buildd.debian.org/status/fetch.php?pkg=staden-io-lib&arch=amd64&ver=1.14.14%2Bdfsg-1%2Bb1&stamp=1663567926&raw=0
[2] https://tracker.debian.org/pkg/htscodecs
[3]
https://github.com/jkbonfield/htscodecs/commit/6211b208d2bd21e93f3f62c0cd0d8c43546f98b5
[4]
cram_io.c: In function ‘cram_compress_by_method’:
cram_io.c:2420:23: warning: implicit declaration of function
‘encode_names’; did you mean ‘tok3_encode_names’?
[-Wimplicit-function-declaration]
2420 | uint8_t *cp = encode_names(in, in_size, lev, strat,
&out_len, NULL);
| ^~~~
| tok3_encode_names
cram_io.c:2420:23: warning: initialization of ‘uint8_t *’ {aka ‘unsigned
char *’} from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
[5]
(rr) bt
#0 tok3_encode_names (blk=, len=, level=,
use_arith=, out_len=, last_start_p=) at
./htscodecs/tokenise_name3.c:1540
#1 0x7f281aa34454 in cram_compress_by_method (s=s@entry=0x55e9af757e50, in=0x7f281000e930
"s0", in_size=9, out_size=out_size@entry=0x7f2819611730, method=method@entry=TOK3,
level=, strat=0, content_id=) at ./io_lib/cram_io.c:2420
#2 0x7f281aa38ebe in cram_compress_block (fd=fd@entry=0x55e9af71f930,
s=s@entry=0x55e9af757e50, b=0x55e9af758830, metrics=0x55e9af731f50,
method=65794, level=level@entry=5) at ./io_lib/cram_io.c:2562
#3 0x7f281aa22d75 in cram_compress_slice (s=0x55e9af757e50, c=, fd=0x55e9af71f930) at ./io_lib/cram_encode.c:951
#4 cram_encode_slice (fd=fd@entry=0x55e9af71f930,
c=c@entry=0x55e9af73c270, h=h@entry=0x55e9af73c520, s=0x55e9af757e50) at
./io_lib/cram_encode.c:1219
#5 0x7f281aa27881 in cram_encode_container (fd=,
c=) at ./io_lib/cram_encode.c:2119
#6 0x7f281aa33fb0 in cram_flush_thread (arg=0x55e9af4d0500) at
./io_lib/cram_io.c:4328
#7 0x7f281aa44272 in t_pool_worker (arg=0x55e9af737460) at
./io_lib/thread_pool.c:434
#8 0x7f281a68784a in start_thread (arg=) at
./nptl/pthread_create.c:442
#9 0x7f281a70a530 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:100
(rr) print out
$6 = (uint8_t *) 0x7f2810010320 "\t"
(rr) finish
Run till exit from #0 tok3_encode_names (blk=, len=,
level=, use_arith=, out_len=,
last_start_p=) at ./htscodecs/tokenise_name3.c:1540
0x7f281aa34454 in cram_compress_by_method (s=s@entry=0x55e9af757e50, in=0x7f281000e930
"s0", in_size=9, out_size=out_size@entry=0x7f2819611730, method=method@entry=TOK3,
level=, strat=0, content_id=) at ./io_lib/cram_io.c:2420
2420uint8_t *cp = encode_names(in, in_size, lev, strat,
&out_len, NULL);
Value returned is $8 = (uint8_t *) 0x7f2810010320 "\t"
(rr) stepi
2421*out_size = out_len;
(rr) print cp
$7 = (uint8_t *) 0x10010320
(rr) list
2416int out_len;
2417int lev = level;
2418if (method == NAME_TOK3 && lev > 3)
2419lev = 3;
2420uint8_t *cp = encode_names(in, in_size, lev, strat,
&out_len, NULL);
2421*out_size = out_len;
2422return (char *)cp;
2423}
2424
2425case RAW:
[6]
Thread 2 received signal SIGSEGV, Segmentation fault.
0x7f281a69788a in __GI___libc_free (mem=0x10010320) at
./malloc/malloc.c:3363
3363./malloc/malloc.c: Datei oder Verzeichnis nicht gefunden.
(rr) bt
#0 0x7f281a69788a in __GI___libc_free (mem=0x10010320) at
./malloc/malloc.c:3363
#1 0x7f281aa39238 in cram_compress_block (fd=fd@entry=0x55e9af71f930,
s=s@entry=0x55e9af757e50, b=0x55e9af758830, metrics=0x55e9af731f50,
method=65794, level=level@entry=5) at ./io_lib/cram_io.c:2575
#2 0x7f281aa22d75 in cram_compress_slice (s=0x55e9af757e50, c=, fd=0x55e9af71f930) at ./io_lib/cram_encode.c:951
#3 cram_encode_slice (fd=fd@entry=0x55e9af71f930,
c=c@entry=0x55e9af7
Bug#1022901: Removal notice: obsolete
Source: haskell-ghc-mtl Version: 1.2.1.0-10 Severity: serious I intend to remove this package: * It has no rev dependencies * The current version FTBFS * Seems unmaintained; Last upload more than 7 years ago * It's not part of the latest Stackage LTS If you believe we should keep this package in Debian, please close this bug report. -- Ilias
Bug#1022896: rust-rusty-pool: autopkgtest failure
Source: rust-rusty-pool Version: 0.7.0-2 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-rusty-pool/27568708/log.gz ... autopkgtest [03:39:50]: test librust-rusty-pool+default-dev:default: /usr/share/cargo/bin/cargo-auto-test rusty_pool 0.7.0 --all-targets autopkgtest [03:39:50]: test librust-rusty-pool+default-dev:default: [--- crate directory not found: /usr/share/cargo/registry/rusty_pool-0.7.0 autopkgtest [03:39:50]: test librust-rusty-pool+default-dev:default: ---] autopkgtest [03:39:51]: test librust-rusty-pool+default-dev:default: - - - - - - - - - - results - - - - - - - - - - librust-rusty-pool+default-dev:default FAIL non-zero exit status 1 autopkgtest [03:39:51]: summary rust-rusty-pool:@FAIL non-zero exit status 1
Bug#1022893: golang-github-etcd-io-gofail: binary-any FTBFS
Source: golang-github-etcd-io-gofail Version: 0.0.0+git.2022.09.25.d0d2a96a6e-3 Severity: serious Tags: ftbfs X-Debbugs-Cc: Thomas Goirand https://buildd.debian.org/status/logs.php?pkg=golang-github-etcd-io-gofail&ver=0.0.0%2Bgit.2022.09.25.d0d2a96a6e-3 ... debian/rules override_dh_install make[1]: Entering directory '/<>' dh_install rm /<>/debian/golang-github-etcd-io-gofail-dev/usr/share/gocode/src/go.etcd.io/gofail/.gitignore rm: cannot remove '/<>/debian/golang-github-etcd-io-gofail-dev/usr/share/gocode/src/go.etcd.io/gofail/.gitignore': No such file or directory make[1]: *** [debian/rules:15: override_dh_install] Error 1
Bug#982095: marked as done (haskell-yesod-bin: autopkgtest failure)
Your message dated Thu, 27 Oct 2022 12:05:42 + with message-id and subject line Bug#982095: fixed in haskell-yesod-bin 1.6.2.2-1 has caused the Debian Bug report #982095, regarding haskell-yesod-bin: autopkgtest 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.) -- 982095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-yesod-bin Version: 1.6.0.6-1 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/h/haskell-yesod-bin/10268587/log.gz ... autopkgtest [19:49:32]: test scaffold: [--- The init command has been removed. Please use 'stack new ' instead where the available templates can be found by running 'stack templates'. For a Yesod based application you should probably choose one of the pre-canned Yesod templates. autopkgtest [19:49:33]: test scaffold: ---] scaffold FAIL non-zero exit status 1 autopkgtest [19:49:33]: test scaffold: - - - - - - - - - - results - - - - - - - - - - autopkgtest [19:49:33]: summary scaffold FAIL non-zero exit status 1 --- End Message --- --- Begin Message --- Source: haskell-yesod-bin Source-Version: 1.6.2.2-1 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-yesod-bin, 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 982...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated haskell-yesod-bin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 27 Oct 2022 14:44:02 +0300 Source: haskell-yesod-bin Architecture: source Version: 1.6.2.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Ilias Tsitsimpis Closes: 982095 Changes: haskell-yesod-bin (1.6.2.2-1) unstable; urgency=medium . * New upstream release * Remove autopkgtest since the 'yesod test' command has been deprecated (Closes: #982095) Checksums-Sha1: ebbfad7a246e4776003fd87382ef643a10d7071c 2969 haskell-yesod-bin_1.6.2.2-1.dsc b00745dc79b0e0ffb834bc84da9addd3a3f7d610 22752 haskell-yesod-bin_1.6.2.2.orig.tar.gz 066f1e9bf6e9cf083226680e27949c4cb2b46f49 4044 haskell-yesod-bin_1.6.2.2-1.debian.tar.xz ae89e2a982a2d935abd50a9f1c8b2c3cba3a5fa0 12982 haskell-yesod-bin_1.6.2.2-1_amd64.buildinfo Checksums-Sha256: 49441baded9879d4f1658d4dc35855b1d639fc7e3f3fc9ee75ad2e248ba2457d 2969 haskell-yesod-bin_1.6.2.2-1.dsc 7953aab9517acad598b01b3944f95c4f95e1e7e979ba27cc46bc2c26f9c976a1 22752 haskell-yesod-bin_1.6.2.2.orig.tar.gz 4730929c82cb182335abdedda64f21c99a85ddce6ac0e495378602dff04358da 4044 haskell-yesod-bin_1.6.2.2-1.debian.tar.xz 8e9002aff4307b8cc157bfff1a3e633f789ea73a1234de8ac31f43aeeb846398 12982 haskell-yesod-bin_1.6.2.2-1_amd64.buildinfo Files: d13a2def48a002343a3a081bf6511d89 2969 haskell optional haskell-yesod-bin_1.6.2.2-1.dsc 27386279fcbe1a341a8c4dc36ee72d28 22752 haskell optional haskell-yesod-bin_1.6.2.2.orig.tar.gz 6f6d7ece049718be1de5a126be32976d 4044 haskell optional haskell-yesod-bin_1.6.2.2-1.debian.tar.xz 13e6a52d27f6ed68f75b725af21c03e6 12982 haskell optional haskell-yesod-bin_1.6.2.2-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAmNacO4UHGlsaWFzdHNp QGRlYmlhbi5vcmcACgkQ16hngMxkQDxR7A//TpcW/qgQEKoEwdRlJo9rBXC0E9Cr cM/I3bnXH5HiPbg65aUYaqd+qH2nHXYbxUH6ksO2kmXULj0Zcj/yA9LqXgY9prX7 mvhrHuxyVHr45xcXJhTEW+ABrOvP0OWY8hqndU4rnh76nZ9XwveqowwtPX5xIEtV lodhibsmtQshw0iuEtqo48C9z5ojckHiSLTrjiqwNVfmKDX1cdMwZe+xEQ8WH0Yy XrnTSEBVjh8i8FOROK31bI5mBRFB611drFzrk0fDPuwpHN51Jd+drI/JejwBmfqA 3G+C+8EcFu0w1/FoaIT8u8n9pb+JbswKdANT2xy3bpI7WDcxf2SSPQZhsEJ9BkZT TEPbLudEk+K0kRAEeppxAnOV1g5prnENoi942cpbMKEYP93RLkV/VZFncO6xGCU6 1bUtpZNSudty/7HCcgSg5xvF3xn0tAnU+unWXKTB9lxIKX4HDezDHLEtl2QO3ijg wKWgnDIY3xCnqniPwiUoMGDA8Ec2hL7MXWgvK4ZABpb8OHc7GbwIwpY/5Ok/K+xG TMK+kyrG4NloUQb07BirtffwceMaZXvtCRS4qpNKwtZ8PxQ+W8NcZpcqlJ4zVzFD O2hftJoyeBT8mgQ0mN+IIOm2vXIBEmfJhVy7hUJWi3um04+d59xNiv+Y7yVh/iqw ZJxhzZkZLwBh+F8= =Zwvy -END PGP SIGNATURE End
Processed: tagging 1021936, tagging 1016190
Processing commands for cont...@bugs.debian.org:
> tags 1021936 - sid
Bug #1021936 [src:kopanocore] kopanocore: fix all arch ftbfs("error:
‘unique_ptr’ in namespace ‘std’ does not name a template type")
Removed tag(s) sid.
> tags 1016190 + sid bookworm
Bug #1016190 [src:sanitizer] ship sanitizer with bookworm?
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1016190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016190
1021936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: notfound 924233 in 2.9.4-4, notfixed 998073 in 0.4.12-1, notfound 1004427 in 1:8.7p1-1 ...
Processing commands for cont...@bugs.debian.org:
> # unconfuse the BTS
> notfound 924233 2.9.4-4
Bug #924233 {Done: Andrej Shadura } [obs-server]
obs-server: fails to purge: delgroup: `obsservicerun' still has `obsrun' as
their primary group!
No longer marked as found in versions open-build-service/2.9.4-4.
> notfixed 998073 0.4.12-1
Bug #998073 [wireplumber] wireplumber: fails to automatically switch to
headphones when connected
No longer marked as fixed in versions 0.4.12-1.
> notfound 1004427 1:8.7p1-1
Bug #1004427 {Done: Colin Watson } [openssh-server]
openssh-server: Connection reset when trying to establish a connection on armhf
No longer marked as found in versions openssh/1:8.7p1-1.
> notfixed 1008997 2.4.1op1-2
Bug #1008997 {Done: Thorsten Alteholz } [cups] cups:
impossible to print on hp envy 5536 from sid
No longer marked as fixed in versions 2.4.1op1-2.
> found 1009636 2.0.0-1
Bug #1009636 [src:ruby-devise-two-factor] ruby-devise-two-factor:
CVE-2021-43177 - possible reuse of OTP due to incomplete fix for CVE-2015-7225
Marked as found in versions ruby-devise-two-factor/2.0.0-1.
> notfound 1009636 4.0.2-1
Bug #1009636 [src:ruby-devise-two-factor] ruby-devise-two-factor:
CVE-2021-43177 - possible reuse of OTP due to incomplete fix for CVE-2015-7225
No longer marked as found in versions ruby-devise-two-factor/4.0.2-1.
> notfixed 1018785 1:0.4.1-4
Bug #1018785 {Done: Torquil Macdonald Sørensen }
[python3-dolfinx-real] Problem with python3-dolfinx-real or libfftw3_mpi.so.3
No longer marked as fixed in versions 1:0.4.1-4.
> notfixed 1020863 4.4.4-1
Bug #1020863 {Done: Boyuan Yang <073p...@gmail.com>}
[src:python-flask-jwt-extended] python-flask-jwt-extended: Source-only upload
needed
No longer marked as fixed in versions 4.4.4-1.
> fixed 1020863 4.4.4-2
Bug #1020863 {Done: Boyuan Yang <073p...@gmail.com>}
[src:python-flask-jwt-extended] python-flask-jwt-extended: Source-only upload
needed
Marked as fixed in versions python-flask-jwt-extended/4.4.4-2.
> reopen 983913
Bug #983913 {Done: Debian FTP Masters }
[puppet-master,puppet-master-passenger] puppet-master,puppet-master-passenger:
depends on unavailable puppet-server
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 5.5.22-4+rm.
> fixed 979887 2021.08-1
Bug #979887 {Done: Antonio Terceiro } [lava] lava:
node-uglify is deprecated in favor of uglifyjs
There is no source info for the package 'lava' at version '2021.08-1' with
architecture ''
Unable to make a source version for version '2021.08-1'
Marked as fixed in versions 2021.08-1.
> notfixed 979887 2022.01.3-3
Bug #979887 {Done: Antonio Terceiro } [lava] lava:
node-uglify is deprecated in favor of uglifyjs
No longer marked as fixed in versions lava/2022.01.3-3.
> notfound 979887 2022.01.3-3
Bug #979887 {Done: Antonio Terceiro } [lava] lava:
node-uglify is deprecated in favor of uglifyjs
No longer marked as found in versions lava/2022.01.3-3.
> tags 979887 + sid bookworm
Bug #979887 {Done: Antonio Terceiro } [lava] lava:
node-uglify is deprecated in favor of uglifyjs
Added tag(s) sid and bookworm.
> found 979887 2021.01-1
Bug #979887 {Done: Antonio Terceiro } [lava] lava:
node-uglify is deprecated in favor of uglifyjs
There is no source info for the package 'lava' at version '2021.01-1' with
architecture ''
Unable to make a source version for version '2021.01-1'
Marked as found in versions 2021.01-1.
> reassign 1002548 indi-fli 1.5-1
Bug #1002548 {Done: Thorsten Alteholz } [libfli2,indi-fli]
libfli2,indi-fli: both ship /lib/udev/rules.d/99-fli.rules
Bug reassigned from package 'libfli2,indi-fli' to 'indi-fli'.
No longer marked as found in versions indi-fli/1.5-1.
No longer marked as fixed in versions libfli/2.0-2, indi-fli/1.5-2, and
libfi/2.0-2.
Bug #1002548 {Done: Thorsten Alteholz } [indi-fli]
libfli2,indi-fli: both ship /lib/udev/rules.d/99-fli.rules
Marked as found in versions indi-fli/1.5-1.
> fixed 1002548 1.5-2
Bug #1002548 {Done: Thorsten Alteholz } [indi-fli]
libfli2,indi-fli: both ship /lib/udev/rules.d/99-fli.rules
Marked as fixed in versions indi-fli/1.5-2.
> affects 1002548 + libfli2
Bug #1002548 {Done: Thorsten Alteholz } [indi-fli]
libfli2,indi-fli: both ship /lib/udev/rules.d/99-fli.rules
Added indication that 1002548 affects libfli2
> reassign 1020504 src:linux 5.19.6-1
Bug #1020504 {Done: Salvatore Bonaccorso }
[linux-image-5.19.0-1-amd64] Bug on Debian 11 Bullseye - Kernel 5.19.6-amd64
dont run with Nvidia drivers
Warning: Unknown package 'linux-image-5.19.0-1-amd64'
Bug reassigned from package 'linux-image-5.19.0-1-amd64' to 'src:linux'.
No longer marked as found in versions linux-signed-amd64/5.19.6+1.
Ignoring request to alter fixed versions of bug #1020504 to the same values
previously set
Bug #1020504 {Done: Salvatore Bonaccorso } [src:linux] Bug
on Debian 11 Bullseye - Kernel 5.19.6-amd64 dont run with
Bug#1022881: swt4-gtk FTBFS due to default encoding
Source: swt4-gtk Version: 4.17.0-1 Severity: serious Tags: ftbfs patch Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: vignesh.ra...@collabora.com Dear Maintainer, swt4-gtk fails to build with the below error, https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/swt4-gtk.html copy.translationfiles: [javac] Compiling 436 source files to /build/swt4-gtk-4.17.0/bundles/org.eclipse.swt/temp.folder/@dot.bin [javac] /build/swt4-gtk-4.17.0/bundles/org.eclipse.swt/temp.folder/@dot.src/org/eclipse/swt/layout/FillLayout.java:13: error: unmappable character (0xC3) for encoding US-ASCII [javac] * Christoph L??ubrich - Bug 513185 [javac] ^ [javac] /build/swt4-gtk-4.17.0/bundles/org.eclipse.swt/temp.folder/@dot.src/org/eclipse/swt/layout/FillLayout.java:13: error: unmappable character (0xA4) for encoding US-ASCII [javac] * Christoph L??ubrich - Bug 513185 [javac]^ [javac] 2 errors BUILD FAILED /build/swt4-gtk-4.17.0/bundles/org.eclipse.swt/buildFragment.xml:88: The following error occurred while executing this line: /build/swt4-gtk-4.17.0/bundles/org.eclipse.swt/buildFragment.xml:61: Compile failed; see the compiler error output for details. The default encoding is US-ASCII. Some packages contain characters that cannot be displayed with the default encoding and thus will cause build failures. Set encoding to UTF-8 to fix this error. I'm attaching a patch which includes the fix. Please could you review it. Thank you. Regards, Vignesh -- System Information: Debian Release: 11.1 APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (500, 'stable-updates'), (500, 'stable-security') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled >From f1e41f5ba6d1430aba3d8ca7927cff299f489934 Mon Sep 17 00:00:00 2001 From: Vignesh Raman Date: Wed, 26 Oct 2022 12:30:33 +0530 Subject: [PATCH] Set encoding to UTF-8 swt4-gtk fails to build with the below error, copy.translationfiles: [javac] Compiling 436 source files to /build/swt4-gtk-4.17.0/bundles/org.eclipse.swt/temp.folder/@dot.bin [javac] /build/swt4-gtk-4.17.0/bundles/org.eclipse.swt/temp.folder/@dot.src/org/eclipse/swt/layout/FillLayout.java:13: error: unmappable character (0xC3) for encoding US-ASCII [javac] * Christoph L??ubrich - Bug 513185 [javac] ^ [javac] /build/swt4-gtk-4.17.0/bundles/org.eclipse.swt/temp.folder/@dot.src/org/eclipse/swt/layout/FillLayout.java:13: error: unmappable character (0xA4) for encoding US-ASCII [javac] * Christoph L??ubrich - Bug 513185 [javac]^ [javac] 2 errors BUILD FAILED /build/swt4-gtk-4.17.0/bundles/org.eclipse.swt/buildFragment.xml:88: The following error occurred while executing this line: /build/swt4-gtk-4.17.0/bundles/org.eclipse.swt/buildFragment.xml:61: Compile failed; see the compiler error output for details. The default encoding is US-ASCII. Some packages contain characters that cannot be displayed with the default encoding and thus will cause build failures. Set encoding to UTF-8 to fix this error. Signed-off-by: Vignesh Raman --- debian/rules | 1 + 1 file changed, 1 insertion(+) diff --git a/debian/rules b/debian/rules index 803ce85..9bb459a 100755 --- a/debian/rules +++ b/debian/rules @@ -15,6 +15,7 @@ DEB_DH_MAKESHLIBS_ARGS_ALL := -Xjni AWT_LIB_DIR := $(JAVA_ARCH) export AWT_LIB_PATH=/usr/lib/jvm/default-java/jre/lib/$(AWT_LIB_DIR) +export JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF8 MAKE_ARGS=-C bundles/org.eclipse.swt/Eclipse\ SWT\ PI/gtk/library -I../../../Eclipse\ SWT/common/library/ -f make_linux.mak -- 2.30.2
Processed: Re: Bug#1021067: Removal notice: obsolete
Processing control commands: > clone -1 -2 Bug #1021067 [src:haskell-crypto-numbers] Removal notice: obsolete Bug 1021067 cloned as bug 1022878 > reassign -2 ftp.debian.org Bug #1022878 [src:haskell-crypto-numbers] Removal notice: obsolete Bug reassigned from package 'src:haskell-crypto-numbers' to 'ftp.debian.org'. No longer marked as found in versions haskell-crypto-numbers/0.2.7-10. Ignoring request to alter fixed versions of bug #1022878 to the same values previously set > retitle -2 RM: haskell-crypto-numbers -- ROM; obsolete Bug #1022878 [ftp.debian.org] Removal notice: obsolete Changed Bug title to 'RM: haskell-crypto-numbers -- ROM; obsolete' from 'Removal notice: obsolete'. > severity -2 normal Bug #1022878 [ftp.debian.org] RM: haskell-crypto-numbers -- ROM; obsolete Severity set to 'normal' from 'serious' -- 1021067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021067 1022878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022878 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021067: Removal notice: obsolete
Control: clone -1 -2 Control: reassign -2 ftp.debian.org Control: retitle -2 RM: haskell-crypto-numbers -- ROM; obsolete Control: severity -2 normal Dear FTP masters, please remove haskell-crypto-numbers from unstable. -- Ilias
Processed: Re: Bug#1021068: Removal notice: obsolete
Processing control commands: > clone -1 -2 Bug #1021068 [src:haskell-crypto-pubkey] Removal notice: obsolete Bug 1021068 cloned as bug 1022876 > reassign -2 ftp.debian.org Bug #1022876 [src:haskell-crypto-pubkey] Removal notice: obsolete Bug reassigned from package 'src:haskell-crypto-pubkey' to 'ftp.debian.org'. No longer marked as found in versions haskell-crypto-pubkey/0.2.8-10. Ignoring request to alter fixed versions of bug #1022876 to the same values previously set > retitle -2 RM: haskell-crypto-pubkey -- ROM; obsolete Bug #1022876 [ftp.debian.org] Removal notice: obsolete Changed Bug title to 'RM: haskell-crypto-pubkey -- ROM; obsolete' from 'Removal notice: obsolete'. > severity -2 normal Bug #1022876 [ftp.debian.org] RM: haskell-crypto-pubkey -- ROM; obsolete Severity set to 'normal' from 'serious' -- 1021068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021068 1022876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022876 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1021068: Removal notice: obsolete
Control: clone -1 -2 Control: reassign -2 ftp.debian.org Control: retitle -2 RM: haskell-crypto-pubkey -- ROM; obsolete Control: severity -2 normal Dear FTP masters, please remove haskell-crypto-pubkey from unstable. -- Ilias
Bug#1019808: marked as pending in openbabel
Control: tag -1 pending Hello, Bug #1019808 in openbabel 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/debichem-team/openbabel/-/commit/9a875ec27408d6d399f0e69b20fd8f019eed646e Transition to wxwidgets3.2 (Closes: #1019808) (this message was generated automatically) -- Greetings https://bugs.debian.org/1019808
Processed: Bug#1019808 marked as pending in openbabel
Processing control commands: > tag -1 pending Bug #1019808 [src:openbabel] openbabel: Please transition to wxwidgets3.2 Added tag(s) pending. -- 1019808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019808 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022362: marked as done (debos: FTBFS: make[1]: *** [debian/rules:17: override_dh_auto_build] Error 25)
Your message dated Thu, 27 Oct 2022 08:36:08 + with message-id and subject line Bug#1022362: fixed in debos 1.1.1-1 has caused the Debian Bug report #1022362, regarding debos: FTBFS: make[1]: *** [debian/rules:17: override_dh_auto_build] Error 25 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.) -- 1022362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022362 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: debos Version: 1.0.0+git20210707.c66a48d-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build > cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 > github.com/go-debos/debos github.com/go-debos/debos/actions > github.com/go-debos/debos/cmd/debos > src/github.com/go-debos/fakemachine/decompressors.go:7:2: cannot find package > "github.com/klauspost/compress/zstd" in any of: > /usr/lib/go-1.19/src/github.com/klauspost/compress/zstd (from $GOROOT) > > /<>/obj-x86_64-linux-gnu/src/github.com/klauspost/compress/zstd > (from $GOPATH) > src/github.com/go-debos/fakemachine/decompressors.go:8:2: cannot find package > "github.com/ulikunitz/xz" in any of: > /usr/lib/go-1.19/src/github.com/ulikunitz/xz (from $GOROOT) > /<>/obj-x86_64-linux-gnu/src/github.com/ulikunitz/xz (from > $GOPATH) > dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 > github.com/go-debos/debos github.com/go-debos/debos/actions > github.com/go-debos/debos/cmd/debos returned exit code 1 > make[1]: *** [debian/rules:17: override_dh_auto_build] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/10/23/debos_1.0.0+git20210707.c66a48d-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221023&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: debos Source-Version: 1.1.1-1 Done: Christopher Obbard We believe that the bug you reported is fixed in the latest version of debos, 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 1022...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christopher Obbard (supplier of updated debos package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 27 Oct 2022 08:52:37 +0100 Source: debos Architecture: source Version: 1.1.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Christopher Obbard Closes: 989145 1008762 1020288 1020691 1020917 1022362 Changes: debos (1.1.1-1) unstable; urgency=medium . * New upstream release (Closes: #1020917) * Add myself to list of uploaders * Point d/watch at tagged releases * Add systemd-resolved to Recommends (Closes: #1020288, #1020691) * Add user-mode-linux & libslirp-helper to Suggests * Fix grammatical mistakes in package Description * Don't require fakemachine for autopkgtests (Closes: #989145) * Bump Standards-Version to 4.6.1 * Bump build dependency on golang-github-go-debos-fakemachine-dev - Fakemachine now works with kernel >=5.13 (Closes: #1008762) - Fakemachine lib package now depends on required libs (Closes: #1022362) * Don't include duplicate Build-Depends from fakemachine Che
Bug#1022095: marked as done (electrum: Replace the sourceless minified JavaScript files)
Your message dated Thu, 27 Oct 2022 10:34:44 +0200 with message-id and subject line Re: Upstream discussion has caused the Debian Bug report #1022095, regarding electrum: Replace the sourceless minified JavaScript files 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.) -- 1022095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: electrum Version: 4.0.9-1 Severity: serious Tags: upstream Justification: Policy 4.16 Lintian reports three minified JavaScript files that do not have source: electrum/www/jquery-3.4.1.min.js electrum/www/jquery-ui.min.js electrum/www/qrcode.js --- End Message --- --- Begin Message --- Version: 4.3.2+dfsg1-1--- End Message ---
