-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Control: severity -1 important
On Tue, 2024-03-26 at 12:25 +0100, Matthias Klose wrote:
> Package: src:ifuse
> Version: 1.1.4~git20181007.3b00243-1
> Severity: serious
> Tags: sid trixie ftbfs patch
>
> ifuse ftbfs from source, not finding the libp
Processing control commands:
> severity -1 important
Bug #1067755 [src:ifuse] ifuse ftbfs from source, not finding the libplist
configuration
Severity set to 'important' from 'serious'
--
1067755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067755
Debian Bug Tracking System
Contact ow...
On 4 April 2024 02:52:29 CEST, David Landry wrote:
>Good evening,
>
>The bug involving compiling/installing nvidia-kernel-dkms is still present.
>The result of the bug is that following a reboot after the erroneous
>installation noted below, my display drivers get completely disabled,
>includin
Your message dated Thu, 04 Apr 2024 05:34:40 +
with message-id
and subject line Bug#1067055: fixed in openmpi 4.1.6-8
has caused the Debian Bug report #1067055,
regarding openmpi: error: implicit declaration of function
'OPAL_THREAD_ADD_FETCH64'
to be marked as done.
This means that you clai
Your message dated Thu, 4 Apr 2024 06:48:42 +0200
with message-id
and subject line [ftpmas...@ftp-master.debian.org: Accepted nodejs
18.20.1+dfsg-1 (source) into unstable]
has caused the Debian Bug report #1068347,
regarding nodejs: CVE-2024-27983 CVE-2024-27982
to be marked as done.
This means
Source: nodejs
Source-Version: 18.20.1+dfsg-1
- Forwarded message from Debian FTP Masters
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 03 Apr 2024 16:50:38 +0200
Source: nodejs
Architecture: source
Version: 18.20.1+dfsg-1
Distribution: unstable
Urgency: medi
Processing commands for cont...@bugs.debian.org:
> found 1068347 18.19.1+dfsg-3
Bug #1068347 [src:nodejs] nodejs: CVE-2024-27983 CVE-2024-27982
Marked as found in versions nodejs/18.19.1+dfsg-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1068347: https://bugs
Processing control commands:
> tags -1 patch
Bug #1066239 [src:gnome-system-tools] gnome-system-tools: FTBFS:
shares-tool.c:113:17: error: implicit declaration of function ‘table_add_share’
[-Werror=implicit-function-declaration]
Added tag(s) patch.
--
1066239: https://bugs.debian.org/cgi-bin/
Your message dated Thu, 04 Apr 2024 03:04:25 +
with message-id
and subject line Bug#1033316: fixed in ruby-moneta 1.6.0-1
has caused the Debian Bug report #1033316,
regarding Autopkgtest is flaky
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Package: gnome-system-tools
Followup-For: Bug #1066239
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch
Dear Maintainer,
Would it be possible tot consider the attached patch as a solution to this
issue.
In Ubuntu, the attached patch was applie
Your message dated Thu, 04 Apr 2024 02:49:21 +
with message-id
and subject line Bug#1064813: fixed in fprintd 1.94.3-1
has caused the Debian Bug report #1064813,
regarding fprintd: FTBFS: (fprintd:160601): fprintd-WARNING **: 06:35:58.406:
Could not open "/etc/fprintd.conf": No such file or d
Hi, Paul,
> If you believe your package is unable to migrate to testing due to
> issues beyond your control, don't hesitate to contact the Release Team.The
> excuses shows peony blocked by qtbase-opensource-src which it's beyond my
> contorl,and the peony and peony-extensions will been auto rem
Processing commands for cont...@bugs.debian.org:
> tags 1068347 + upstream
Bug #1068347 [src:nodejs] nodejs: CVE-2024-27983 CVE-2024-27982
Added tag(s) upstream.
> tags 1068346 + upstream
Bug #1068346 [src:node-express] node-express: CVE-2024-29041
Added tag(s) upstream.
> thanks
Stopping processi
On Thu, 2 Nov 2023 23:05:28 +0100 at46 wrote:
> I had the same problem and it took me quite some time to find that
> fluidsynth was the root cause of this. Fluidsynth was installed as
new
> dependency from lutris 0.5.14 and blocked my sound device each
~second
> boot.
>
> @Patrick I could chec
Good evening,
The bug involving compiling/installing nvidia-kernel-dkms is still present. The
result of the bug is that following a reboot after the erroneous installation
noted below, my display drivers get completely disabled, including nouveau,
resulting in my external display not functionin
Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that t
Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that t
Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that t
Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that t
Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that t
Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that t
Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that t
Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that t
Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that t
Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that t
Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that t
Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that t
Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that t
Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that t
Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that t
Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id
and subject line Bug#1064096: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1064096,
regarding gir-rust-code-generator FTBFS with librust-toml-dev 0.8
to be marked as done.
This means that you claim t
Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id
and subject line Bug#1067256: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1067256,
regarding gir-rust-code-generator: update for time_t changes
to be marked as done.
This means that you claim that t
Your message dated Thu, 04 Apr 2024 00:22:17 +
with message-id
and subject line Bug#1064766: fixed in gir-rust-code-generator 0.18.3-2
has caused the Debian Bug report #1064766,
regarding gir-rust-code-generator: FTBFS: failed to select a version for the
requirement `toml = "^0.7"`; candidate
Processing commands for cont...@bugs.debian.org:
> reassign 1067256 src:gir-rust-code-generator
Bug #1067256 [src:rust-atk-sys] rust-atk-sys: FTBFS: make[1]: ***
[debian/rules:16: execute_before_dh_auto_build] Error 101
Bug reassigned from package 'src:rust-atk-sys' to 'src:gir-rust-code-generato
Processing commands for cont...@bugs.debian.org:
> severity 1050429 important
Bug #1050429 [musl-tools] musl: unusable on mipsel, mips64el:
mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me
Hi ZenWorker,Am 03.04.2024 um 15:51 schrieb ZenWalker :Package: snapshot.debian.orgSeverity: graveDebian is tracking issues related to the xz backdoor additionally at https://salsa.debian.org/ftp-team/xz-2024-incident/. I made Bastian aware of your perfect catch and this is now also https://salsa.
On 2024-04-03 23:46:43 +0200, Andrea Bolognani wrote:
> On Tue, Apr 02, 2024 at 12:02:53AM +0200, Sebastian Ramacher wrote:
> > On 2024-04-01 23:39:37 +0200, Andrea Bolognani wrote:
> > > The problem with it, and the reason why a manual dependency is used
> > > in that case, is that ${shlib:Depends
Processing control commands:
> tags 1064708 + patch
Bug #1064708 [src:pygame] pygame: FTBFS: AssertionError: "No video mode" does
not match "Parameter 'surface' is invalid"
Ignoring request to alter tags of bug #1064708 to the same tags previously set
> tags 1064708 + pending
Bug #1064708 [src:py
Control: tags 1064708 + patch
Control: tags 1064708 + pending
Dear maintainer,
I've prepared an NMU for pygame (versioned as 2.5.2-1.2) and
uploaded it.
Regards.
diff -Nru pygame-2.5.2/debian/changelog pygame-2.5.2/debian/changelog
--- pygame-2.5.2/debian/changelog 2024-01-10 06:32:39.00
Processing control commands:
> affects -1 src:pandas
Bug #1068349 [python3-nbconvert,python3-lxml] nbsphinx/nbconvert broken by lxml
5.2: lxml.html.clean
Added indication that 1068349 affects src:pandas
> affects -1 python3-nbsphinx
Bug #1068349 [python3-nbconvert,python3-lxml] nbsphinx/nbconvert
Dear Maintainers,
Would it be possible to consider a merge request[1] that addresses this issue?
Best Regards,
Vladimir.
[1] https://salsa.debian.org/debian/gimp-plugin-registry/-/merge_requests/2
This appears to be another manifestation of the incompatibility with
python3.12 reported in #1059647. I'm not going to mark it as a
duplicate in the BTS since the process of getting there is so different,
but I believe the fix will be the same. Upstream has reworked the build
process to allow use
Your message dated Wed, 03 Apr 2024 22:06:52 +
with message-id
and subject line Bug#976564: fixed in golang-github-linuxkit-virtsock
0.0~git20220523.1a23e78+ds-1
has caused the Debian Bug report #976564,
regarding golang-github-linuxkit-virtsock: FTBFS:
src/github.com/linuxkit/virtsock/pkg/h
Your message dated Wed, 03 Apr 2024 22:06:52 +
with message-id
and subject line Bug#976564: fixed in golang-github-linuxkit-virtsock
0.0~git20220523.1a23e78+ds-1
has caused the Debian Bug report #976564,
regarding golang-github-linuxkit-virtsock: FTBFS: dh_auto_build: error: cd
obj-aarch64-l
tags 1059647 +upstream
thanks
Upstream reports in https://github.com/scikit-fmm/scikit-fmm/issues/78
that this issue is fixed on a development branch, and will be merged and
released as soon as a test suite issue gets resolved.
Bdale
signature.asc
Description: PGP signature
Your message dated Wed, 03 Apr 2024 23:44:51 +0200
with message-id
and subject line Re: Bug#1067308 python-meshplex: FTBFS: dh_auto_test: error:
has caused the Debian Bug report #1067308,
regarding python-meshplex: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.
Your message dated Wed, 03 Apr 2024 21:54:02 +
with message-id
and subject line Bug#1067010: fixed in squashfuse 0.5.2-0.1
has caused the Debian Bug report #1067010,
regarding libsquashfuse-dev: Incompatible pointer types on 32-bit architectures
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> tags 1066248 +pending
Bug #1066248 [src:librnd] librnd: FTBFS:
../src/librnd/plugins/hid_lesstif/main.c:261:25: error: implicit declaration of
function ‘lesstif_attr_sub_update_hidlib’
[-Werror=implicit-function-declaration]
Added tag(s) pendin
tags 1066248 +pending
tags 1049315 +pending
thanks
Last night I successfully completed a test build of librnd from upstream
svn trunk that resolves all open Debian bugs. The next upstream release
is still expected on 10 April, and I plan to update the Debian librnd
package immediately after that
On Tue, Apr 02, 2024 at 12:02:53AM +0200, Sebastian Ramacher wrote:
> On 2024-04-01 23:39:37 +0200, Andrea Bolognani wrote:
> > The problem with it, and the reason why a manual dependency is used
> > in that case, is that ${shlib:Depends} will not pick it up, since
> > it's dlopen()ed rather than l
Source: nodejs
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerabilities were published for nodejs.
CVE-2024-27983[0]:
https://nodejs.org/en/blog/vulnerability/april-2024-security-releases/
CVE-2024-27982[1]:
https://nodejs.org/en/blog/vulnerability
Your message dated Wed, 03 Apr 2024 20:46:19 +
with message-id
and subject line Bug#1066392: fixed in gtk2-engines-murrine 0.98.2-4
has caused the Debian Bug report #1066392,
regarding gtk2-engines-murrine: FTBFS: ./src/murrine_style.c:133:30: error:
implicit declaration of function ‘murrine_
This is already fixed in unstable, waiting for pacemaker to migrate.
I noticed one package affected by this issue, prettytable, has
switched to a fork, pytest-lazy-fixtures (note the s at the end of the
name).
Would someone like to package this for Debian to fix several packages
failing to build?
https://github.com/dev-petrov/pytest-lazy-fixtures
Thank you,
Jerem
Processing commands for cont...@bugs.debian.org:
> tags 1067547 + fixed-upstream
Bug #1067547 [src:wmweather+] FTBFS: "vsnprintf is so broken we can't
compensate. Sorry."
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1067547: https:
Processing commands for cont...@bugs.debian.org:
> affects 1063957 src:prettytable
Bug #1063957 [src:python-pytest-lazy-fixture] python-pytest-lazy-fixture:
autopkgtest regression with pytest 8
Bug #1063973 [src:python-pytest-lazy-fixture] python-marshmallow-sqlalchemy:
autopkgtest regression wi
This is actually https://bugs.debian.org/1063957
prettytable has worked around this for the 3.10.0 release by switching
to a fork, python-pytest-lazy-fixtures, which is not yet packaged in
Debian.
Thank you,
Jeremy Bícha
Am Wed, 03 Apr 2024 20:46:29 +0200
schrieb Simon Chopin :
> I just uploaded the attached debdiff to Ubuntu to both fix the FTBFS and
> start the t64 transition for this package, based on the following
> comment:
Are you able to test this for the dev snapshot of mpg123 before I do
the next releas
Processing commands for cont...@bugs.debian.org:
> notfound 1017729 5.4.2-2
Bug #1017729 [cinnamon-l10n] cinnamon-l10n: Upgrading to 5.4.2-2 breaks cinnamon
No longer marked as found in versions cinnamon-translations/5.4.2-2.
> found 1017729 6.0.2-2
Bug #1017729 [cinnamon-l10n] cinnamon-l10n: Upgr
Control: tag -1 pending
Hello,
Bug #1066255 in asciijump reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/games-team/asciijump/-/commit/b6196ae4e5b323fc6377affca
Processing control commands:
> tag -1 pending
Bug #1066255 [src:asciijump] asciijump: FTBFS: scrclient.c:76:19: error:
implicit declaration of function ‘strtol’; did you mean ‘strtok’?
[-Werror=implicit-function-declaration]
Added tag(s) pending.
--
1066255: https://bugs.debian.org/cgi-bin/bug
tags 1067547 + fixed-upstream
thanks
Hi Adrian,
> >...
> > > debdiffs contain only changes to debian/
> >
> > The bookworm/bullseye debdiffs looks good, please upload to
> > security-master, thanks!
>
> both are now uploaded.
DSA has been released, thanks!
> > Note that both need -sa, but dak needs some special attention when
>
Processing control commands:
> tags -1 ftbfs patch
Bug #1067562 [src:mpg123] FTBFS: missing symbols on 32-bit architectures
Added tag(s) patch.
--
1067562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> tags 1068223 + ftbfs
Bug #1068223 [cyrus-imapd] cyrus-imapd - FTBFS on 32-bit non-i386 architectures
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1068223: https://bugs.debian.org/cgi-bin/bug
Source: mpg123
Followup-For: Bug #1067562
X-Debbugs-Cc: scho...@ubuntu.com
Control: tags -1 ftbfs patch
Hi,
I just uploaded the attached debdiff to Ubuntu to both fix the FTBFS and
start the t64 transition for this package, based on the following
comment:
> the non-suffixed functions now work wi
On Wed, 13 Mar 2024 13:03:27 +0100 Lucas Nussbaum wrote:
Source: libast
Version: 0.7-9.1
During a rebuild of all packages in sid, your package failed to build
on amd64.
> snprintf.c:45:22: error: unknown type name ‘size_t’
>45 | vsnprintf(char *str, size_t count, const char *fmt, va_li
Your message dated Wed, 3 Apr 2024 19:20:55 +0100
with message-id
and subject line Re: Bug#1061493: consolekit: install PAM module and udev files
into /usr
has caused the Debian Bug report #1061493,
regarding consolekit: install PAM module and udev files into /usr
to be marked as done.
This mean
Your message dated Wed, 03 Apr 2024 17:50:28 +
with message-id
and subject line Bug#1066942: fixed in xmrig 6.21.2+dfsg-2
has caused the Debian Bug report #1066942,
regarding xmrig: FTBFS on armhf: cc: error: unrecognized command-line option
‘-maes’
to be marked as done.
This means that you
Your message dated Wed, 03 Apr 2024 17:34:04 +
with message-id
and subject line Bug#1066437: fixed in libast 0.7-10
has caused the Debian Bug report #1066437,
regarding libast: FTBFS: snprintf.c:45:22: error: unknown type name ‘size_t’
to be marked as done.
This means that you claim that the
Your message dated Wed, 03 Apr 2024 17:34:21 +
with message-id
and subject line Bug#1057442: fixed in onboard 1.4.1-6
has caused the Debian Bug report #1057442,
regarding onboard ftbfs with Python 3.12
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
I could not reproduce the issue on an armhf porterbox, which is
concerning. I have just uploaded a new release that just tells cmake to
force an ARMv7 build if DEB_HOST_ARCH is armhf. It also includes a handy
patch that makes the build log give a couple clues so I can track down
why my machine
Your message dated Wed, 03 Apr 2024 17:19:17 +
with message-id
and subject line Bug#1067326: fixed in mkdocstrings 0.24.2-1
has caused the Debian Bug report #1067326,
regarding mkdocstrings: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned ex
Followup-For: Bug #1067311
There seem to be two problems leading to this bug:
1.)
- jupyter-nbextension-jupyter-js-widgets is no longer built from
src:ipywidgets since -3
- it is not provided by any other package
- it ships /etc/jupyter/nbconfig/notebook.d/jupyter-js-widgets.json (and
nothing
Processing control commands:
> tag -1 pending
Bug #1057442 [src:onboard] onboard ftbfs with Python 3.12
Added tag(s) pending.
--
1057442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1057442 in onboard reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/debian-mate-team/onboard/-/commit/e1c683eda8f7e548ad486d7
Control: severity -1 normal
On 2024-04-03 11:29 +0200, Alejandro Colomar wrote:
> Hi,
>
> On Tue, Apr 02, 2024 at 08:58:32PM +0200, Aurelien Jarno wrote:
>> Thanks, that sounds great that we can finally get rid out of those in
>> the debian package.
>>
>> >$ git diff --stat b06cd070f..128a3ae
Processing control commands:
> severity -1 normal
Bug #1068188 [glibc-doc] pthread_cond_init.3.gz: conflict with manpages-dev
6.7-1
Severity set to 'normal' from 'serious'
--
1068188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068188
Debian Bug Tracking System
Contact ow...@bugs.debian.
Your message dated Wed, 03 Apr 2024 15:36:07 +
with message-id
and subject line Bug#1068158: fixed in python-escript 5.6-7
has caused the Debian Bug report #1068158,
regarding python-escript: FTBFS: RuntimeError: We do not current support
different different dpkg-buildflags for C vs C++:
to b
Your message dated Wed, 03 Apr 2024 15:36:07 +
with message-id
and subject line Bug#1067385: fixed in python-escript 5.6-7
has caused the Debian Bug report #1067385,
regarding python-escript: FTBFS: unsatisfiable build-dependencies (purely
virtual?): libocct-data-exchange-7.6 (>= 7.6.3+dfsg1)
Followup-For: Bug #1053169
Migration is currently blocked behind the t64 transition.
Andreas
On 3/4/24 8:26 PM, Guido Günther wrote:
Thanks for checking! Please always make sure you check for inhibitors
(`gnome-session-inhibit -l`, `systemd-inhibit -l`) to make sure nothing
left a suspend/sleep inhibitor blocking this.
I noticed it happening for a few days and across multiple reboots
Processing commands for cont...@bugs.debian.org:
> forwarded 1068158 https://bugs.launchpad.net/escript-finley/+bug/2060138
Bug #1068158 [src:python-escript] python-escript: FTBFS: RuntimeError: We do
not current support different different dpkg-buildflags for C vs C++:
Set Bug forwarded-to-addre
Hi Praveen,
On Wed, Apr 03, 2024 at 05:58:41PM +0530, Praveen Arimbrathodiyil via
Debian-on-mobile-maintainers wrote:
> On Tue, 2 Apr 2024 08:04:12 -0400 =?UTF-8?Q?Jeremy_B=C3=ADcha?=
> wrote:
> > On Tue, Apr 2, 2024 at 8:03 AM Jeremy Bícha
> > wrote:
> > >
> > > On Tue, Apr 2, 2024 at 5:31 AM
Processing control commands:
> severity -1 serious
Bug #1017729 [cinnamon-l10n] cinnamon-l10n: Upgrading to 5.4.2-2 breaks cinnamon
Severity set to 'serious' from 'important'
--
1017729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017729
Debian Bug Tracking System
Contact ow...@bugs.debia
It seems that the maes flag is automatically added if the ARM_TARGET
CMake var is not set, which happens in cmake/cpu.cmake. The first thing
I saw when I opened that file looked promising:
if (CMAKE_SIZEOF_VOID_P EQUAL 8)
set(XMRIG_64_BIT ON)
add_definitions(-DXMRIG_64_BIT)
Package: snapshot.debian.org
Severity: grave
On 02/04/2024 21:29, Sebastian Ramacher wrote:
To be honest, I don't see these two changes (changing mpi-defaults to
mpich on 32 bit; breaking 32 bit build of openmpi) to be ready. It'd be
preferable to reinstate a 32-bit compatible pmix and fix openmpi on 32
bit until the time_t transition is d
Processing control commands:
> found -1 2.15.00-1
Bug #1068327 [src:flexc++] flexc++: FTBFS on armel, armhf (Segmentation fault)
Marked as found in versions flexc++/2.15.00-1.
--
1068327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068327
Debian Bug Tracking System
Contact ow...@bugs.debi
Source: flexc++
Severity: serious
Tags: ftbfs
Control: found -1 2.15.00-1
X-Debbugs-Cc: ken...@xdump.org
Dear Maintainer,
flexc++ fails to build on armel, armhf.
FYI:
https://buildd.debian.org/status/fetch.php?pkg=flexc%2B%2B&arch=armel&ver=2.15.00-1&stamp=1712127698&raw=0
https://buildd.debian
On 02/04/2024 21:29, Sebastian Ramacher wrote:
OpenMPI 5 drops 32-bit support, but otherwise does not change the API/ABI.
So it is technically not a transition, but breaks 32-bit builds.
Doesn't make it better. This is not the time to do that without tests
builds and bugs filed.
The soluti
Source: bisonc++
Severity: serious
Tags: ftbfs
Control: found -1 6.08.00-1
X-Debbugs-Cc: ken...@xdump.org
Dear Maintainer,
bisonc++ fails to build on armel, armhf.
FYI:
https://buildd.debian.org/status/fetch.php?pkg=bisonc%2B%2B&arch=armel&ver=6.08.00-1&stamp=1712127818&raw=0
https://buildd.deb
Processing control commands:
> found -1 6.08.00-1
Bug #1068325 [src:bisonc++] bisonc++: FTBFS on armel, armhf
(override_dh_auto_clean Segmentation fault)
Marked as found in versions bisonc++/6.08.00-1.
--
1068325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068325
Debian Bug Tracking Sys
Processing commands for cont...@bugs.debian.org:
> tags 1066831 + upstream fixed-upstream pending
Bug #1066831 [nbd-client] nbd-server: Crash on -C /dev/null or -C /missing/file
Added tag(s) pending, fixed-upstream, and upstream.
> thanks
Stopping processing here.
Please contact me if you need as
On Sun, 31 Mar 2024 18:41:02 -0700, Russ Allbery wrote:
> In theory, one could delete the pieces of the module that try to do things
> that no one should really be doing from Perl and the rest of it remains
> somewhat useful, but given that upstream has archived the project, I would
> go ahead and
Your message dated Wed, 3 Apr 2024 17:58:41 +0530
with message-id <1ff6ab18-3191-4001-a48b-90632ec59...@onenetbeyond.org>
and subject line Re: Bug#1068230: automatic suspend regression with
gnome-settings-daemon 46
has caused the Debian Bug report #1068230,
regarding automatic suspend regression w
On Tue, 2 Apr 2024 08:04:12 -0400 =?UTF-8?Q?Jeremy_B=C3=ADcha?=
wrote:
On Tue, Apr 2, 2024 at 8:03 AM Jeremy Bícha wrote:
>
> On Tue, Apr 2, 2024 at 5:31 AM Pirate Praveen
wrote:
> > Recently automatic suspend stopped working. I think this was after gnome
settings daemon 46 was available. So
Your message dated Wed, 03 Apr 2024 12:20:44 +
with message-id
and subject line Bug#1067288: fixed in pulseaudio 16.1+dfsg1-5
has caused the Debian Bug report #1067288,
regarding pulseaudio: FTBFS cpu-volume-test fails
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 03 Apr 2024 12:21:06 +
with message-id
and subject line Bug#1066604: fixed in trickle 1.07-13
has caused the Debian Bug report #1066604,
regarding trickle: FTBFS: configure: error: Couldn't figure out how to access
libc
to be marked as done.
This means that you claim
Your message dated Wed, 03 Apr 2024 12:19:41 +
with message-id
and subject line Bug#1065767: fixed in libopendbx 1.4.6-17
has caused the Debian Bug report #1065767,
regarding libopendbx: FTBFS: mssql_basic.c:324:21: error: implicit declaration
of function ‘dbpoll’ [-Werror=implicit-function-d
1 - 100 of 116 matches
Mail list logo
