Messaggio originale
Da: Andrea Pappacoda
Inviato il: 3 maggio 2024 07:39:59 CEST
A: Stuart Prescott
Oggetto: Re: Bug#1069357: cpp-httplib: FTBFS on arm64: dh_auto_test: error: cd
obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8
MESON_TESTTHREADS=4
Processing commands for cont...@bugs.debian.org:
> tag 1069843 + pending
Bug #1069843 [src:zarr] zarr: FTBFS: failing tests
Added tag(s) pending.
> thansk
Unknown command or malformed arguments to command.
> --
Stopping processing here.
Please contact me if you need assistance.
--
1069843:
Source: bibledit
Version: 5.1.002-1
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: teusbensc...@debian.org
Dear Maintainer,
The version of upstream code, included in this package,
has broken javascript.
This cripples some parts of the program, in particular
Source: bibledit-cloud
Version: 5.1.005-1
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: teusbensc...@debian.org
Dear Maintainer,
The uptream version, included in this package,
has partially broken javascript.
This cripples some parts of the Bible editors.
Processing control commands:
> tags -1 +moreinfo
Bug #1070266 [release.debian.org] nmu: chromium_124.0.6367.118-1
Added tag(s) moreinfo.
--
1070266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Fri, 3 May 2024 07:26:19 +0200
with message-id
and subject line Re: Bug#1070266: nmu: chromium_124.0.6367.118-1
has caused the Debian Bug report #1070266,
regarding nmu: chromium_124.0.6367.118-1
to be marked as done.
This means that you claim that the problem has been dealt
Control: tags -1 +moreinfo
On Fri, May 3, 2024 at 12:57 AM Andres Salomon wrote:
> Snappy 1.2.0-1 was uploaded with broken symbols (see
> https://bugs.debian.org/1070217). This is fixed in snappy 1.2.0-2, but
> chromium in sid had already built against the broken version of snappy.
Nope, the
Hi Andrea
Gentle ping on this bug - there are a few packages lined up for
autoremoval and/or can't migrate due to this bug.
Looking at the test suite, there seems to be three tests (all within
SSLClientServerTest) that now hang on multiple architectures. I don't
think this is simply a
On Thu, 2 May 2024 19:05:22 +0300 Jussi Pakkanen wrote:
>
> Along the way I found other bugs, such as bindgen not working at all
> out of the box. I filed
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070241 for that.
>
> All in all this is getting into very deep Debian toolchain magic, of
Source: rust-sequoia-octopus-librnp
Version: 1.8.1-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
User: debian-...@lists.debian.org
Usertags: time-t
rust-sequoia-octopus-librnp FTBFS on armel/armhf due to the t64
transition:
Processing commands for cont...@bugs.debian.org:
> found 1068209 8.9
Bug #1068209 {Done: Nicolas Boulenguez } [dh-ada-library]
libgtkada: FTBFS on all: dh_ada_library: error:
debian/tmp/usr/lib/x86_64-linux-gnu/ada/adalib/gtkada/*.ali are missing
Marked as found in versions dh-ada-library/8.9.
Package: riseup-vpn
Version: 0.21.11+ds1-5+b1
Severity: grave
When attempting to run the bookworm riseup-vpn package, it fails to
connect to riseup's servers and gives the following output:
2024/05/01 18:21:23 Error fetching eip v3
json:https://api.black.riseup.net/3/config/eip-service.json
Update:
- python3-levenshtein is now fixed in unstable
- python-levenshtein can't migrate because of a long chain that gets
back to #1069357 (cpp-httplib: FTBFS on arm64).
--
Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/
Your message dated Fri, 3 May 2024 00:16:13 +0100
with message-id <8b493f77-cdac-44d7-81d9-319d8d9b0...@debian.org>
and subject line Re: librust-prost-build-dev: FTBFS
has caused the Debian Bug report #1069195,
regarding librust-prost-build-dev: FTBFS
to be marked as done.
This means that you
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: binnmu
Severity: serious
Hello,
Snappy 1.2.0-1 was uploaded with broken symbols (see
https://bugs.debian.org/1070217). This is fixed in snappy 1.2.0-2, but
chromium in sid had already built against the broken
Your message dated Thu, 2 May 2024 23:37:12 +0200
with message-id
and subject line Re: mediastreamer2: NMU diff for 64-bit time_t transition
has caused the Debian Bug report #1064170,
regarding mediastreamer2: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim
02.05.2024 23:36, Michael Biebl wrote:
Control: reopen -1
Control: found -1 2:4.19.6+dfsg-3
On Thu, 2 May 2024 11:58:59 -0700 "Leo L. Schwab" wrote:
Did you fix this one, too?
---
Performing actions...
Setting up python3-samba (2:4.19.6+dfsg-2) ...
File
Processing commands for cont...@bugs.debian.org:
> severity 1070236 serious
Bug #1070236 [python3-samba] python3-samba: SyntaxError during configuration
phase of package on upgrade
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need
Your message dated Thu, 02 May 2024 20:36:04 +
with message-id
and subject line Bug#1070246: fixed in libayatana-appindicator 0.5.93+really-1
has caused the Debian Bug report #1070246,
regarding libayatana-appindicator version of Debian package does not match the
upstream version
to be
My apologies. I cut and pasted the wrong bug number. However, thank you
for the patch. I have included it in the upcoming 23.6.2 release in
Debian. I have also incorporated this patch upstream.
--
Tim Theisen (he, him, his)
Release Manager
HTCondor & Open Science Grid
Center for High
Processing control commands:
> tags 1064516 + patch
Bug #1064516 [src:ruby-rack] ruby-rack: CVE-2024-26141 CVE-2024-25126
CVE-2024-26146
Added tag(s) patch.
> tags 1064516 + pending
Bug #1064516 [src:ruby-rack] ruby-rack: CVE-2024-26141 CVE-2024-25126
CVE-2024-26146
Added tag(s) pending.
--
Control: tags 1064516 + patch
Control: tags 1064516 + pending
Dear maintainer,
I've prepared an NMU for ruby-rack (versioned as 2.2.7-1.1) and uploaded
it to DELAYED/2. Please feel free to tell me if I should cancel it.
cu
Adrian
diffstat for ruby-rack-2.2.7 ruby-rack-2.2.7
changelog
Package: susv4
Version: 7.20180621
Followup-For: Bug #968415
X-Debbugs-Cc: mlukow...@sdf.org
--- debian/susv4.postinst.orig 2024-05-02 15:56:25.243665232 -0400
+++ debian/susv4.postinst 2024-05-02 15:56:34.133076612 -0400
@@ -8,7 +8,7 @@
wget -P $TEMPDIR
Package: susv4
Version: 7.20180621
Followup-For: Bug #968415
X-Debbugs-Cc: mlukow...@sdf.org
Dear Maintainer,
--- debian/susv4/DEBIAN/postinst.orig 2024-05-02 15:49:52.972725058 -0400
+++ debian/susv4/DEBIAN/postinst2024-05-02 15:50:01.506839488 -0400
@@ -8,7 +8,7 @@
wget -P $TEMPDIR
Hej,
Am Donnerstag, 2. Mai 2024, 15:24:07 CEST schrieb Helmut Grohne:
> Source: ktp-text-ui
> Version: 22.12.3-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in
> the past)
>
> ktp-text-ui fails to build from source in unstable on amd64.
Your message dated Thu, 02 May 2024 19:12:17 +
with message-id
and subject line Bug#1065956: fixed in mtd-utils 1:2.2.0-2
has caused the Debian Bug report #1065956,
regarding mtd-utils: FTBFS on arm{el,hf}: FAIL mtdlib_test (exit status: 17)
to be marked as done.
This means that you claim
Source: libcxx-serial
Version: 1.2.1-5
Severity: serious
Justification: nocheck ftbfs is rc since trixie
Tags: ftbfs trixie sid
libcxx-serial fails to build from source when enabling the nocheck build
profile. I think the relevant part is:
| -- catkin 0.8.10
| -- BUILD_SHARED_LIBS is on
| CMake
Source: ktp-text-ui
Version: 22.12.3-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
ktp-text-ui fails to build from source in unstable on amd64. The
relevant log probably is:
| [ 76%] Linking CXX executable ktp-text-ui
| cd
Your message dated Thu, 2 May 2024 13:40:28 -0500
with message-id <0a5dbd46-f97b-466e-beba-880208495...@cs.wisc.edu>
and subject line Re: htcondor: preemption not working if NEGOTIATOR_INTERVAL is
set
has caused the Debian Bug report #1067661,
regarding condor: unable to install condor on armhf
Your message dated Thu, 02 May 2024 18:37:22 +
with message-id
and subject line Bug#1069350: fixed in netavark 1.4.0-4.1
has caused the Debian Bug report #1069350,
regarding netavark: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo
build returned exit code 101
to be marked as done.
Your message dated Thu, 02 May 2024 18:04:25 +
with message-id
and subject line Bug#1067299: fixed in ada-reference-manual
1:2020.1commit85143dcb-5
has caused the Debian Bug report #1067299,
regarding ada-reference-manual: FTBFS: debian/rules:31:
/usr/share/ada/debian_packaging.mk: No such
Processing commands for cont...@bugs.debian.org:
> merge 1070247 1070250
Bug #1070247 [src:telepathy-glib] telepathy-glib: Fails to build with glib 2.80
Bug #1070250 [src:telepathy-glib] telepathy-glib: Fails to build with glib 2.80
Merged 1070247 1070250
>
End of message, stopping processing
Package: sublime-music
Version: 0.12.0-1
Severity: critical
Forwarded: https://github.com/sublime-music/sublime-music/issues/462
Using libmpv2 0.38, the playback is broken an results in the following trace:
Traceback (most recent call last):
File
Source: telepathy-glib
Severity: serious
Version: 0.24.2-0.3
Tags: ftbfs upstream
X-Debbugs-CC: bi...@debian.org
Please cherry-pick the glib commit from
https://gitlab.freedesktop.org/telepathy/telepathy-glib/-/commits/master
to fix the build with glib 2.80 (currently in experimental but will be
Thanks. This is a duplicate (https://bugs.debian.org/1070217), but I'm
leaving it open to ensure that chromium doesn't accidentally migrate to
trixie while built against a broken libsnappy. And as a reminder that
we'll probably need a binNMU once snappy is fixed, unless upstream has a
new
Your message dated Thu, 02 May 2024 17:52:34 +
with message-id
and subject line Bug#1070217: fixed in snappy 1.2.0-2
has caused the Debian Bug report #1070217,
regarding dependency: libsnappy1v5: After update from 1.1.10-1+b1 to 1.2.0-1
symbol lookup error
to be marked as done.
This means
Your message dated Thu, 02 May 2024 17:52:34 +
with message-id
and subject line Bug#1070217: fixed in snappy 1.2.0-2
has caused the Debian Bug report #1070217,
regarding chromium: Symbol lookup error with libsnappy1v5>=1.2.0
to be marked as done.
This means that you claim that the problem
Source: telepathy-glib
Severity: serious
Version: 0.24.2-0.3
Tags: ftbfs upstream
X-Debbugs-CC: bi...@debian.org
Please cherry-pick the glib commit from
https://gitlab.freedesktop.org/telepathy/telepathy-glib/-/commits/master
to fix the build with glib 2.80 (currently in experimental but will be
Source: libayatana-appindicator
Severity: serious
Version: 0.5.92-1
Version: 0.5.93-1
The package of libayatana-appindicator on Debian is not building from the
right orig tarball as indicated on the package version.
Both package versions on Debian 12 and testing (versions 0.5.92-1 and
On Thu, 2 May 2024 at 01:48, Shmerl wrote:
> > Ubuntu fixed it with this patch:
> > https://launchpadlibrarian.net/715235929/meson_1.3.2-1_1.3.2-1ubuntu1.diff.gz
> >
>
> Can this fix be added to Debian? Meson has been stuck without
> moving to testing for a very long time and now it seems to be
Package: wsclean
Version: 3.4-1+b2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: offri...@gmail.com
Dear Maintainer,
There is something wrong with the packaging of WSClean; running WSClean fails
with the following error:
wsclean: error while loading shared libraries:
Your message dated Thu, 02 May 2024 15:04:45 +
with message-id
and subject line Bug#1068209: fixed in dh-ada-library 9.4
has caused the Debian Bug report #1068209,
regarding libgtkada: FTBFS on all: dh_ada_library: error:
debian/tmp/usr/lib/x86_64-linux-gnu/ada/adalib/gtkada/*.ali are
Work-around for affected users:
Download and install
libsnappy1v5_1.1.10-1+b1_amd64.deb
from
https://snapshot.debian.org/archive/debian/20240210T223313Z/pool/main/s/snappy/
Temporary protection:
% cat /etc/apt/preferences.d/libsnappy
Explanation: Debian#1070217: chromium: Symbol lookup
Hi,
On Thu, May 02, 2024 at 03:55:53PM +0200, Guido Günther wrote:
> Hi,
> On Wed, May 01, 2024 at 12:27:41PM +0200, Guido Günther wrote:
> > Package: gcovr
> > Version: 7.2-1
> > Severity: grave
> >
> > Hi,
> > invoking gcovr 7.2 in an empty directory fails like
> >
> > $ gcovr
> >
Hi,
On Wed, May 01, 2024 at 12:27:41PM +0200, Guido Günther wrote:
> Package: gcovr
> Version: 7.2-1
> Severity: grave
>
> Hi,
> invoking gcovr 7.2 in an empty directory fails like
>
> $ gcovr
> --
>
Processing commands for cont...@bugs.debian.org:
> reassign 1068209 dh-ada-library
Bug #1068209 [src:libgtkada] libgtkada: FTBFS on all: dh_ada_library: error:
debian/tmp/usr/lib/x86_64-linux-gnu/ada/adalib/gtkada/*.ali are missing
Bug reassigned from package 'src:libgtkada' to 'dh-ada-library'.
Your message dated Thu, 02 May 2024 12:50:47 +
with message-id
and subject line Bug#1070053: fixed in prometheus-process-exporter 0.8.2-1
has caused the Debian Bug report #1070053,
regarding prometheus-process-exporter: FTBFS: cannot use status.UIDs[1]
(variable of type uint64) as string
Same issue with nextcloud (package nextcloud-desktop):
$ nextcloud
nextcloud: symbol lookup error:
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5: undefined symbol:
_ZN6snappy11RawCompressEPKcmPcPm
(Touching bug to reset AUTORM countdown.)
signature.asc
Description: This is a digitally signed message part
Processing commands for cont...@bugs.debian.org:
> affects 1070217 chromium
Bug #1070217 [libsnappy1v5] chromium: Symbol lookup error with
libsnappy1v5>=1.2.0
Bug #1070228 [libsnappy1v5] dependency: libsnappy1v5: After update from
1.1.10-1+b1 to 1.2.0-1 symbol lookup error
Added indication that
Your message dated Thu, 2 May 2024 11:30:36 +0200
with message-id <1f540de6-e4f6-5b97-e7f3-e3a75d2e6...@debian.org>
and subject line Re: libosmo-sccp: FTBFS on armhf: build-dependency not
installable: libosmo-netif-dev (>= 1.2.0)
has caused the Debian Bug report #1069504,
regarding libosmo-sccp:
Processing commands for cont...@bugs.debian.org:
> severity 1070228 serious
Bug #1070228 [libsnappy1v5] dependency: libsnappy1v5: After update from
1.1.10-1+b1 to 1.2.0-1 symbol lookup error
Bug #1070217 [libsnappy1v5] chromium: Symbol lookup error with
libsnappy1v5>=1.2.0
Severity set to
Processing control commands:
> reassign -1 libsnappy1v5
Bug #1070228 [libqt5webenginecore5] dependency: libsnappy1v5: After update from
1.1.10-1+b1 to 1.2.0-1 symbol lookup error
Bug reassigned from package 'libqt5webenginecore5' to 'libsnappy1v5'.
No longer marked as found in versions
looks like it was an abi change upstream
https://github.com/google/snappy/commit/
766d24c95e345d4d06bfd3cc5787c2da3e025fab#diff-
ec7058c429b88797a43d7c3ef3a244980e46f8219844cd2550eaf4bcdc36e961
without an accompanying soname change.
It doesn't look like something where the abi can't easily be
Package: chromium
Version: 124.0.6367.78-1
Severity: grave
The current package in debian unstable fails to start with the following
missing symbol:
$ chromium
grep: warning: stray \ before -
/usr/lib/chromium/chromium: symbol lookup error: /usr/lib/chromium/chromium:
undefined symbol:
Your message dated Thu, 02 May 2024 08:49:20 +
with message-id
and subject line Bug#1061874: fixed in colpack 1.0.10-8
has caused the Debian Bug report #1061874,
regarding colpack: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> reassign 1070217 libsnappy1v5 1.2.0-1
Bug #1070217 [snappy] chromium: Symbol lookup error with libsnappy1v5>=1.2.0
Bug reassigned from package 'snappy' to 'libsnappy1v5'.
No longer marked as found in versions 1.2.0-1.
Ignoring request to alter
Processing commands for cont...@bugs.debian.org:
> found 1070217 1.2.0-1
Bug #1070217 [snappy] chromium: Symbol lookup error with libsnappy1v5>=1.2.0
There is no source info for the package 'snappy' at version '1.2.0-1' with
architecture ''
Unable to make a source version for version '1.2.0-1'
Your message dated Thu, 02 May 2024 07:51:20 +
with message-id
and subject line Bug#1070116: fixed in python-zeep 4.2.1-3
has caused the Debian Bug report #1070116,
regarding python-zeep: Build-depends on NBS libraries libxmlsec1 and
libxmlsec1-openssl
to be marked as done.
This means that
On Tue, 30 Apr 2024 20:07:07 -0400 Boyuan Yang wrote:
I've prepared an NMU for sniproxy (versioned as 0.6.1+git20240321-0.1)
and uploaded it to DELAYED/14. Please feel free to tell me if I
sniproxy is orphaned, so you should rather do an undelayed QA upload
(instead of a NMU) and update the
Your message dated Thu, 02 May 2024 07:04:29 +
with message-id <66333afd217bc_54c94c...@godard.mail>
and subject line Bug#1070116 fixed in python-zeep
has caused the Debian Bug report #1070116,
regarding python-zeep: Build-depends on NBS libraries libxmlsec1 and
libxmlsec1-openssl
to be
Processing control commands:
> tag -1 pending
Bug #1070116 {Done: Mathias Behrle } [src:python-zeep]
python-zeep: Build-depends on NBS libraries libxmlsec1 and libxmlsec1-openssl
Added tag(s) pending.
--
1070116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070116
Debian Bug Tracking
Control: tag -1 pending
Hello,
Bug #1070116 in python-zeep 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:
Your message dated Thu, 02 May 2024 06:38:19 +
with message-id
and subject line Bug#1042251: fixed in python-omegaconf 2.3.0-1
has caused the Debian Bug report #1042251,
regarding python-omegaconf: FTBFS: E ModuleNotFoundError: No module named
'attr'
to be marked as done.
This means that
64 matches
Mail list logo
