This looks of it could be the same issue as bug 1021938, which is due to a
regression in libical version 3.0.15.
--
David Jarvie
KAlarm author, KDE developer
Confirmed, the two patches work for me too (AMD Ryzen Embedded V1605B with
Radeon Vega Gfx).
Kernel rebuilt and now boots like a charm and works without further issues.
Thanks to all of you!!
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 1022025 + pending
Bug #1022025 [src:linux] Can't enable amdgpu driver in
linux-image-5.10.0-19-amd64
Bug #1
Hi,
I have the same issue, 5.10.0-18 works, 5.10.0-19 crashes the system
after disk decryption.
AMD Ryzen 7 5700U
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir IOMMU
00:01.0 Host bridge: Advanced Micro Devi
Processing commands for cont...@bugs.debian.org:
> block 1019353 with 1022152 1020446
Bug #1019353 [release.debian.org] transition: perl 5.36
1019353 was blocked by: 1022133 1022150 1021324 1016761 1022124 1022132
1019353 was blocking: 1022003
Added blocking bug(s) of 1019353: 1020446 and 1022152
Processing commands for cont...@bugs.debian.org:
> block 1019353 with 1022124
Bug #1019353 [release.debian.org] transition: perl 5.36
1019353 was blocked by: 1021324 1016761 1022133 1022150 1022132
1019353 was blocking: 1022003
Added blocking bug(s) of 1019353: 1022124
> thanks
Stopping processing
Control: forcemerge -1 1022150
On Thu, Oct 20, 2022 at 09:14:57PM +0300, Niko Tyni wrote:
> Source: libdevel-bt-perl
> Version: 0.06-5
> Severity: serious
> Tags: ftbfs
> Control: block 1019353 with -1
>
> This package failed to build against Perl 5.36.
>
> https://buildd.debian.org/status/pac
Processing control commands:
> forcemerge -1 1022150
Bug #1022133 [src:libdevel-bt-perl] libdevel-bt-perl: FTBFS on armel: t/basic.t
failure
Bug #1022150 [src:libdevel-bt-perl] libdevel-bt-perl FTBFS on armel
1019353 was blocked by: 1021324 1022133 1016761 1022132
1019353 was blocking: 1022003
Ad
Your message dated Fri, 21 Oct 2022 00:09:35 -0500
with message-id
and subject line ruby-image-science: FTBFS: ERROR: Test "ruby3.0" failed:
:85:in
`require': cannot load such file -- image_science (LoadError)
has caused the Debian Bug report #1011692,
regarding ruby-image-science: FTBFS: ERROR:
Source: postgresql-14
Version: 14.5-2
Severity: serious
Tags: ftbfs
bunk@coccia:~$ cat
/srv/ftp-master.debian.org/queue/reject/postgresql-14_14.5-2+b1_amd64-buildd.changes.reason
Version check failed:
Your upload included the binary package libecpg-compat3, version 14.5-2+b1, for
amd64,
however
Package: python3-pip
Version: 20.3.4-4+deb11u1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: fabquennevi...@gmail.com
Dear Maintainer,
I was trying to install spotipy with:
pip3 install spotipy
and I got a wall of errors:
--- Logging error ---
Traceback (most recent cal
Source: libdevel-bt-perl
Version: 0.06-5
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=libdevel-bt-perl&arch=armel
...
dh_auto_test -a
make -j8 test TEST_VERBOSE=1
make[1]: Entering directory '/<>'
"/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -
Sorry, I made a mistake when trying to send the link to the closed bug
[1]. You can find the right link below.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976350
Regards,
David.
Hi,
I adjusted the affected versions in the BTS, but I couldn't find any
patch for it. The reference to buffer overflows seem related to
CVE-2020-27818, so I wonder whether it is a duplicate or not.
If it is, it was already closed in [1].
[1] CVE-2020-27818
Regards,
David
Package: ktimetracker
Version: 4:5.0.1-3
Severity: grave
KDE Frameworks: Version 5.98.0
Qt: Version 5.15.4 (built against 5.15.4)
Running on: Xfce v: 4.16.1
ktimetracker loses all session history/times data on shutdown/quit.
Worse, when I tried to manually reload the icv file using the 'open'
Processing commands for cont...@bugs.debian.org:
> severity 1013533 important
Bug #1013533 [src:os-autoinst] os-autoinst: FTBFS: make[1]: ***
[debian/rules:25: override_dh_auto_test] Error 1
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you ne
Package: src:linux
Version: 5.10.149-1
Followup-For: Bug #1022051
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Maintainer,
* What led up to the situation?
Normal kernal package upgrade and reboot.
* What exactly did you do (or not do) that was effective (or
ineffective)?
5.10
On Thursday, 20 October 2022 22:10:27 CEST Salvatore Bonaccorso wrote:
> So there are two patches who need to be reverted:
>
> https://lore.kernel.org/stable/20221020153857.565160-1-alexander.deuc...@amd.com/
> https://lore.kernel.org/stable/20221020153857.565160-2-alexander.deuc...@amd.com/
http
Your message dated Thu, 20 Oct 2022 23:35:38 +
with message-id
and subject line Bug#1022140: fixed in loggerhead 2.0.1+bzr541+ds-1
has caused the Debian Bug report #1022140,
regarding loggerhead: autopkgtest regression: No module named 'pygments'
to be marked as done.
This means that you clai
On Thursday, October 20 2022, I wrote:
> Control: tags -1 + patch
>
> On Thursday, October 20 2022, I wrote:
>
>> This can be easily solved by listing python3-pygments in the d/t/control
>> file.
>
> The following patch fixes the issue for me.
Better version of the patch, closing the related bugs
Processing control commands:
> tags -1 + patch
Bug #1022140 [src:loggerhead] loggerhead: autopkgtest regression: No module
named 'pygments'
Added tag(s) patch.
--
1022140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022140
Debian Bug Tracking System
Contact ow...@bugs.debian.org with pro
Control: tags -1 + patch
On Thursday, October 20 2022, I wrote:
> This can be easily solved by listing python3-pygments in the d/t/control
> file.
The following patch fixes the issue for me.
Thanks,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted
Source: loggerhead
Version: 2.0.0-2
Severity: serious
Hi,
Ubuntu's loggerhead package is experiencing an autopkgtest failure due
to a missing test dependency:
--8<---cut here---start->8---
==
Processing commands for cont...@bugs.debian.org:
> severity 1022137 serious
Bug #1022137 [wike] wike: Wike does not run due to missing python3-requests
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1022137: htt
Your message dated Thu, 20 Oct 2022 20:42:38 +
with message-id
and subject line Bug#1009677: fixed in python-django 2:2.2.28-1~deb11u1
has caused the Debian Bug report #1009677,
regarding python-django: CVE-2022-28346
to be marked as done.
This means that you claim that the problem has been d
Your message dated Thu, 20 Oct 2022 20:42:38 +
with message-id
and subject line Bug#1004752: fixed in python-django 2:2.2.28-1~deb11u1
has caused the Debian Bug report #1004752,
regarding python-django: CVE-2022-22818 CVE-2022-23833
to be marked as done.
This means that you claim that the pro
I also applied this patch and it appears to work well.
--
Keep well,
Chris
<><
Your message dated Thu, 20 Oct 2022 20:34:21 +
with message-id
and subject line Bug#1021928: fixed in libksba 1.5.0-3+deb11u1
has caused the Debian Bug report #1021928,
regarding libksba8: CVE-2022-3515 - remote code execution in libksba before
1.6.2
to be marked as done.
This means that you
Your message dated Thu, 20 Oct 2022 20:34:20 +
with message-id
and subject line Bug#1015860: fixed in bcel 6.5.0-1+deb11u1
has caused the Debian Bug report #1015860,
regarding libxalan2-java: CVE-2022-34169
to be marked as done.
This means that you claim that the problem has been dealt with.
Hi all,
On Thu, Oct 20, 2022 at 07:41:51PM +, Doublychargedhiggs wrote:
> Did the same as Dan, i.e built the kernel (apt-get install source) with the
> upstream proposed patch
> 0001-drm-amdgpu-fix-sdma-doorbell-init-ordering-on-APUs.patch
> using the mentioned test-patches script. The kernel
Processing commands for cont...@bugs.debian.org:
> severity 1013158 serious
Bug #1013158 [facet-analyser] facet-analyser: vtk[6,7] removal
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1013158: https://bugs.debian.org/c
Processing commands for cont...@bugs.debian.org:
> severity 1013157 serious
Bug #1013157 [nifti2dicom] nifti2dicom: vtk[6,7] removal
Ignoring request to change severity of Bug 1013157 to the same value.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1013157: http
Processing commands for cont...@bugs.debian.org:
> severity 1016599 serious
Bug #1016599 [src:mayavi2] mayavi2: vtk[6,7] removal
Ignoring request to change severity of Bug 1016599 to the same value.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1016599: https://
Processing commands for cont...@bugs.debian.org:
> severity 1013156 serious
Bug #1013156 [gdcm] gdcm: vtk[6,7] removal
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1013156: https://bugs.debian.org/cgi-bin/bugreport.cgi
Processing commands for cont...@bugs.debian.org:
> severity 1013153 serious
Bug #1013153 [camitk] camitk: vtk[6,7] removal
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1013153: https://bugs.debian.org/cgi-bin/bugreport
Processing commands for cont...@bugs.debian.org:
> severity 1013152 serious
Bug #1013152 [itksnap] itksnap: vtk[6,7] removal
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1013152: https://bugs.debian.org/cgi-bin/bugrepo
On Thursday, 20 October 2022 19:53:22 CEST Dan Coleman wrote:
> > Apparently "test-patches" does not build a 'headers-common' package and
> > therefor installing the headers failed which in turn made DKMS fail.
>
> That seems like less-than-ideal behavior for test-patches.
> Is that a bug that wo
Did the same as Dan, i.e built the kernel (apt-get install source) with the
upstream proposed patch
0001-drm-amdgpu-fix-sdma-doorbell-init-ordering-on-APUs.patch
using the mentioned test-patches script. The kernel really builds, is even
installable, but then hangs
as before at boot, as Dan report
Dear maintainer,
I can confirm this bug too. Processor is an AMD Ryzen 5 5600G with
Radeon Graphics. It doesn't boot (at least not in ~10min) and displays
only the mentioned "flip_done timed out" messages.
5.10.0-18-amd64 works normally.
Best regards,
Andreas
Your message dated Thu, 20 Oct 2022 23:24:59 +0500
with message-id <87a65q4akk.fsf@localhost>
and subject line
has caused the Debian Bug report #1022094,
regarding elpa-pcre2el fails to install
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not th
Your message dated Thu, 20 Oct 2022 18:16:45 +
with message-id
and subject line Bug#1021861: fixed in virglrenderer 0.10.3-2
has caused the Debian Bug report #1021861,
regarding virglrenderer FTBFS on armel
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing control commands:
> block 1019353 with -1
Bug #1019353 [release.debian.org] transition: perl 5.36
1019353 was blocked by: 1022132 1016761 1021324
1019353 was blocking: 1022003
Added blocking bug(s) of 1019353: 1022133
--
1019353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=10193
Source: libdevel-bt-perl
Version: 0.06-5
Severity: serious
Tags: ftbfs
Control: block 1019353 with -1
This package failed to build against Perl 5.36.
https://buildd.debian.org/status/package.php?p=libdevel-bt-perl
# Failed test 'perl backtrace for SIGABRT'
# at t/basic.t line 26.
#
Processing control commands:
> block 1019353 with -1
Bug #1019353 [release.debian.org] transition: perl 5.36
1019353 was blocked by: 1016761 1021324
1019353 was blocking: 1022003
Added blocking bug(s) of 1019353: 1022132
--
1019353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019353
10221
Source: gnumeric
Version: 1.12.53-1
Severity: serious
Tags: ftbfs
Control: block 1019353 with -1
This package currently fails to build on the ppc64el architecture.
https://buildd.debian.org/status/logs.php?pkg=gnumeric&arch=ppc64el
I'm guessing the long double change (#1016388) in 1.12.53-1 bro
Hi Diederik,
Great news! I'm glad I did it correctly.
On 10/20/22 11:32 AM, Diederik de Haas wrote:
> Hi Dan,
>
> On Thursday, 20 October 2022 17:26:42 CEST Dan Coleman wrote:
>> Yeah, I tried to apply it, but I had that same problem where I managed to
>> compile the .debs, but got a bunch of err
I can confirm this same exact problem on a machine of mine.
CPU: AMD FX-8350
GPU: AMD R9 270X (Southern Islands Family)
5.10.0-19 fails to boot, while 5.10.0-18 does.
Best regards.
--
inasprecali
Can confirm this issue with a AMD Ryzen 3 2200G Processor with Vega 8
Graphics on a AsRock DeskMini A300.
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:golang-v2ray-core
> # 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.debi
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:firebird3.0
> # 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
On Thu, Oct 20, 2022 at 08:09:15PM +0300, программист некто wrote:
># fsck.f2fs -f /dev/sda1
>didn't report any errors.
OK, that's good to know.
>I can continue testing - rebuild without patches in turn, to reveal patch
>which break f2fs support.
If you're happy to do that, then that would be e
# fsck.f2fs -f /dev/sda1
didn't report any errors.
I can continue testing - rebuild without patches in turn, to reveal patch which
break f2fs support.
19.10.2022, 13:47, "Steve McIntyre" :
> OK, so the patches from upstream have broken f2fs support for
> you. Looking at the patches, I'm not seei
Your message dated Thu, 20 Oct 2022 17:06:39 +
with message-id
and subject line Bug#1021538: fixed in freeglut 3.2.2-1~exp2
has caused the Debian Bug report #1021538,
regarding libglut-dev: missing Breaks+Replaces: freeglut3-dev (<< 3.2.2)
to be marked as done.
This means that you claim that
On Thursday, 20 October 2022 17:36:33 CEST Christoph Zechner wrote:
> I hope this helps, if there's something additional I could contribute,
> please let me know!
It's probably best to participate in the upstream issue here:
https://gitlab.freedesktop.org/drm/amd/-/issues/2216
signature.asc
Descr
Hi Dan,
On Thursday, 20 October 2022 17:26:42 CEST Dan Coleman wrote:
> Yeah, I tried to apply it, but I had that same problem where I managed to
> compile the .debs, but got a bunch of errors installing them with a black
> screen at the end of the test. I use DKMS for nvidia and openrazer, and
>
On Thu, 20 Oct 2022 16:42:35 +0200 Diederik de Haas
wrote:
On Thursday, 20 October 2022 16:34:47 CEST Diederik de Haas wrote:
> On Thursday, 20 October 2022 14:44:34 CEST Dan Coleman wrote:
> > Looks like there's some attention upstream.
> >
> > https://gitlab.freedesktop.org/drm/amd/-/issues/2
Yeah, I tried to apply it, but I had that same problem where I managed to
compile the .debs, but got a bunch of errors installing them with a black
screen at the end of the test. I use DKMS for nvidia and openrazer, and that's
been posing problems, which you'll see below. In addition, there are
Source: libdbd-oracle-perl
Version: 1.80-3
Severity: serious
Tags: ftbfs
libdbd-oracle-perl cannot be built on the buildds,
and it needs binaries uploaded for the perl 5.36 transition.
Your message dated Thu, 20 Oct 2022 15:05:14 +
with message-id
and subject line Bug#1021988: fixed in mate-tweak 22.10.0-2
has caused the Debian Bug report #1021988,
regarding mate-tweak: overly generic python module name:
/usr/lib/python3/dist-packages/setup.py
to be marked as done.
This me
On Thu, Oct 20, 2022 at 04:17:18PM +0200, Santiago Ruano Rincón wrote:
> El 20/10/22 a las 11:30, Debian Bug Tracking System escribió:
> > Processing commands for cont...@bugs.debian.org:
> >
> > > tags 1019724 + ftbfs
> > Bug #1019724 [grep] warning: stray \ before - causes autopkgtest failure
>
Processing commands for cont...@bugs.debian.org:
> severity 1022025 serious
Bug #1022025 [src:linux] Can't enable amdgpu driver in
linux-image-5.10.0-19-amd64
Bug #1022042 [src:linux] linux-image-amd64: linux-image-5.10.0-19-amd64 fails
to boot on machines with AMD integrated graphics
Bug #10220
Your message dated Thu, 20 Oct 2022 14:45:20 +
with message-id
and subject line Bug#1021174: fixed in unrar-free 1:0.0.2-1
has caused the Debian Bug report #1021174,
regarding unrar-free: non-source file in Debian tests
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> reassign 1022070 src:linux
Bug #1022070 [linux-image-5.10.0-19-amd64] Booting semi-hangs with
'drm_atomic_helper_wait_for_flip_done' errors and alike
Warning: Unknown package 'linux-image-5.10.0-19-amd64'
Bug reassigned from package 'linux-image-
El 20/10/22 a las 11:30, Debian Bug Tracking System escribió:
> Processing commands for cont...@bugs.debian.org:
>
> > tags 1019724 + ftbfs
> Bug #1019724 [grep] warning: stray \ before - causes autopkgtest failure
> Added tag(s) ftbfs.
Could you please clarify why it FTBFS? The warnings are pres
... and of course I managed to make a typo.
It should be Kernel: 5.10.0-19-amd64 x86_64 as in the original report.
Apologies for the noise.
Peter
Van: Debian Bug Tracking System
Verzonden: donderdag 20 oktober 2022 14:12
Aan: Kroon P C, Peter
Onderwerp: B
Processing commands for cont...@bugs.debian.org:
> close 1022115
Bug #1022115 [src:0ad] 0ad: fails to build from the source
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1022115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022115
Debian
Control: notfound -1 0.0.26-1
On Thu, 20 Oct 2022, at 13:30, Andrej Shadura wrote:
>> SIGKILL while compiling C++ looks like the OOM-killer to me: 0ad contains
>> a bundled copy of mozjs, which is a large and compile-time-memory-hungry
>> C++ project. How large a machine did you use to build it?
Hi,
On Thu, 20 Oct 2022, at 13:26, Simon McVittie wrote:
> On Thu, 20 Oct 2022 at 11:32:52 +0100, Andrej Shadura wrote:
>> > g++: fatal error: Killed signal terminated program cc1plus
> ...
>> make[5]: *** Deleting file 'Unified_cpp_js_src_jit4.o'
>
> SIGKILL while compiling C++ looks like t
Processing control commands:
> notfound -1 0.0.26-1
Bug #1022115 [src:0ad] 0ad: fails to build from the source
No longer marked as found in versions 0ad/0.0.26-1.
--
1022115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with p
On Thu, 20 Oct 2022 at 11:32:52 +0100, Andrej Shadura wrote:
> > g++: fatal error: Killed signal terminated program cc1plus
...
> make[5]: *** Deleting file 'Unified_cpp_js_src_jit4.o'
SIGKILL while compiling C++ looks like the OOM-killer to me: 0ad contains
a bundled copy of mozjs, which is
Your message dated Thu, 20 Oct 2022 12:21:01 +
with message-id
and subject line Bug#1019485: fixed in virglrenderer 0.10.3-1.1
has caused the Debian Bug report #1019485,
regarding libvirglrenderer-dev must depend on packages required for its
pkg-config file
to be marked as done.
This means t
Your message dated Thu, 20 Oct 2022 12:21:01 +
with message-id
and subject line Bug#1021861: fixed in virglrenderer 0.10.3-1.1
has caused the Debian Bug report #1021861,
regarding virglrenderer FTBFS on armel
to be marked as done.
This means that you claim that the problem has been dealt with
Hi all,
I'm encountering the same issue on the following hardware:
Kernel: 5.10.0-18-amd64 x86_64
bits: 64
Distro: Debian GNU/Linux 11 (bullseye)
Machine type: Mini-pc
System: ASUSTeK
product: MINIPC PN50
UEFI: ASUSTeK
CPU Info: Quad Core AMD Ryzen 3 4300U with Radeon Graphics [MCP]
spee
Your message dated Thu, 20 Oct 2022 12:41:25 +0100
with message-id
and subject line Re: gdm3 - Login fails and returns to login or blank screen
has caused the Debian Bug report #1010088,
regarding gdm3 - Login fails and returns to login or blank screen
to be marked as done.
This means that you cl
Ok. This package appears to lack some love. Bugs are never closed
(I just closed a few bugreports which were fixed years ago), migration
status apparently is never checked, bugs actually are not watched/handled
(these 2 bugs are here for quite some time already). I pinged the maintainer
but he did
Processing commands for cont...@bugs.debian.org:
> tags 1019724 + ftbfs
Bug #1019724 [grep] warning: stray \ before - causes autopkgtest failure
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1019724: https://bugs.debian.org/cgi-bin/bugreport.
Processing commands for cont...@bugs.debian.org:
> affects 1019724 src:kbuild
Bug #1019724 [grep] warning: stray \ before - causes autopkgtest failure
Added indication that 1019724 affects src:kbuild
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1019724: https:/
On Sun, 24 Apr 2022 04:23:21 +0100 Philip Wyett
wrote:
> Package: gdm3
> Version: 42.0-1
> Severity: serious
> Tags: bookworm sid
>
> Login fails and returns to login or a blank screen.
>
> Platform is VM with virtio graphics.
Could you share your VM settings?
sudo virsh dumpxml
Kind regard
Source: 0ad
Version: 0.0.26-1
Severity: serious
Tags: ftbfs
Dear Maintainer,
While rebuilding your package, it failed to build from
the source at the build stage due to the following error:
...
| ^~~
/<>/libraries/source/spidermonkey/mozjs-78.6.0/js/src/jit/MCallOp
Your message dated Thu, 20 Oct 2022 10:31:11 +
with message-id
and subject line Bug#1020108: fixed in quilt 0.66-2.2
has caused the Debian Bug report #1020108,
regarding quilt: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8
--verbose" VERBOSE=1 returned exit code 2
to be marke
Your message dated Thu, 20 Oct 2022 10:24:56 +
with message-id
and subject line Bug#1022101: fixed in lomiri-gallery-app
2.10.9~git20221009.1317376-3
has caused the Debian Bug report #1022101,
regarding lomiri-gallery-app{,-common} depend on non-existing
qml-module-lomiri-thumbnailer0.1
to b
Your message dated Thu, 20 Oct 2022 09:49:33 +
with message-id
and subject line Bug#1018134: fixed in chatty 0.7.0~rc0-1
has caused the Debian Bug report #1018134,
regarding chatty: Fails to build with evolution-data-server 3.45
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 20 Oct 2022 09:49:33 +
with message-id
and subject line Bug#1020063: fixed in chatty 0.7.0~rc0-1
has caused the Debian Bug report #1020063,
regarding chatty: FTBFS: e-data-server-util.h:261:50: error: unknown type name
‘SoupURIComponent’
to be marked as done.
This mea
Hi Ileana,
are you aware of the bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020436
Bill posted a suggestion how to fix this test there yesterday.
Best wishes,
Tobias
On 10/19/22 14:44, Ileana Dumitrescu wrote:
> Hi Julien,
>
> I applied pari.patch to fix the compile issues with new u
Source: rust-linux-raw-sys
Version: 0.0.46-1
Severity: serious
Usertags: uploaders
rust-linux-raw-sys 0.0.46-1 introduced an invalid Uploaders field,
that is missing the name for the uploader .
$ apt-cache showsrc rust-linux-raw-sys | grep -E '^$|^Version|^Uploaders'
Version: 0.0.46-1
Up
Hi,
Emilio Pozuelo Monfort wrote:
> I don't see why we should preemptively remove firefox from architectures for
> a build issue that may or may not happen 3 years from now. If it happens and
> we can't fix/workaround it, then we can discontinue FF security updates
> there. But until then, I think
Hi,
Prusa Slicer 2.5.0+dfsg-2 still SIGSEGV's during startup on Bookworm
with some sid.
A local rebuild does also runs into Segfault. However, it also reports
that it is unable to init glew.
I'm quite sure it is a different issue, but the result is quite the
same. So i was unsure if I should
87 matches
Mail list logo
