Control: tag -1 pending
Hello,
Bug #1066634 in crack 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:
Processing control commands:
> tag -1 pending
Bug #1066634 [src:crack] crack: FTBFS: rules.c:477:18: error: implicit
declaration of function ‘elcid_pwsize’ [-Werror=implicit-function-declaration]
Added tag(s) pending.
--
1066634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066634
Debian
Your message dated Mon, 27 May 2024 04:34:01 +
with message-id
and subject line Bug#1061077: fixed in golang-github-gookit-color 1.5.4-3
has caused the Debian Bug report #1061077,
regarding golang-github-gookit-color: FTBFS in ubuntu due to unknown TERM env
to be marked as done.
This means
Processing control commands:
> tag -1 pending
Bug #1061077 [src:golang-github-gookit-color] golang-github-gookit-color: FTBFS
in ubuntu due to unknown TERM env
Added tag(s) pending.
--
1061077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061077
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #1061077 in golang-github-gookit-color 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 Mon, 27 May 2024 00:39:40 +
with message-id
and subject line Bug#1071338: fixed in python-numpysane 0.41-1
has caused the Debian Bug report #1071338,
regarding python-numpysane: FTBFS: test/testlib_pywrap_GENERATED.c:24:10: fatal
error: numpy/arrayobject.h: No such file or
Processing control commands:
> tag -1 pending
Bug #1071873 [src:debian-installer] debian-installer: FTBFS: unsatisfiable
build-dependencies
Added tag(s) pending.
--
1071873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071873
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 pending
Hello,
Bug #1071873 in debian-installer 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:
Source: netctl
Version: 1.28-1
Severity: serious
Justification: FHS violation
Rebuilding your package in current unstable leads to .service files
being installed into /:
-rw-r--r-- root/root 512 2023-08-06 22:20 ./netctl-auto@.service
-rw-r--r-- root/root 445 2023-08-06 22:20
Source: jupyterhub
Version: 3.0.0+ds1-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: z...@debian.org
Your package currently fails to build, see below and the attached build
log:
PYTHONPATH=debian/jupyterhub/usr/lib/python3.11/dist-packages help2man
--output=jupyterhub-singleuser.1
Your message dated Sun, 26 May 2024 23:06:53 +
with message-id
and subject line Bug#1071115: fixed in mpich 4.2.0-6
has caused the Debian Bug report #1071115,
regarding libmpich-dev: unhandled symlink to directory conversion:
/usr/lib/x86_64-linux-gnu/mpich/include ->
Am 24.05.24 um 21:23 schrieb Ross Gammon:
Hi Tobias,
There are no blockers other than real life getting in the way. I did
start working on 5.2.0 in the experimental branch on Salsa. From memory,
there was a problem with fuzzy patches, and the tedious checking of
copyrights still to do. But I
Your message dated Sun, 26 May 2024 21:34:26 +
with message-id
and subject line Bug#1071470: fixed in slic3r-prusa 2.7.4+dfsg-1.1
has caused the Debian Bug report #1071470,
regarding src:slic3r-prusa: FTBFS with opencasacade 7.8.1
to be marked as done.
This means that you claim that the
Hello Bastian,
thanks for taking care and fixing this speedily.
However, I am wondering whether there was a particular need to speed up
fixing this bug that I might have missed and that might need to have
been added to the bug for further consideration / clarification.
After all I, as the
Hello,
I realized this bug prevents shaderc from migrating to testing.
Please have a look on my MR
(https://salsa.debian.org/xorg-team/vulkan/glslang/-/merge_requests/6),
which (among other things) fixes this bug.
Thanks,
Philippe.
Hi,
On Sun, May 26, 2024 at 10:39 PM Marcel Partap wrote:
> I'm not sure whether this is a purely local issue but it's
>
> tmux: /lib/x86_64-linux-gnu/libtinfo.so.6: version
> `NCURSES6_TINFO_6.4.current'
> not found (required by tmux)
Has to be a local issue... Are you 100% sure that this
Package: tmux
Version: 3.4-5
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: mpar...@gmx.net
I'm not sure whether this is a purely local issue but it's
tmux: /lib/x86_64-linux-gnu/libtinfo.so.6: version `NCURSES6_TINFO_6.4.current'
not found (required by tmux)
tmux:
Source: dh-make
Version: 2.202302
Severity: serious
Justification: Multiarch false promises
X-Debbugs-Cc: debian-cr...@lists.debian.org, hel...@subdivi.de,
chris.obb...@collabora.com
Dear dh-make maintainers,
This bug is related to #1040542 and to commit d411b19 on Salsa[1].
[1]
Your message dated Sun, 26 May 2024 19:49:05 +
with message-id
and subject line Bug#1071643: fixed in horizon-eda 2.6.0-2.1
has caused the Debian Bug report #1071643,
regarding horizon-eda: Missing build dependency on cppzmq-dev
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> tags 1063754 - moreinfo
Bug #1063754 [src:linux] fat-modules: SD corruption upon opening file on Linux
desktop
Removed tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1063754:
On 2024-05-26 12:44, Santiago Vila wrote:
To track that, what does `lscpu` report on your failing system?
(the thread,core,socket lines are probably the relevant ones)
It's an AWS machine of type m6a.large. These are the most relevant
specs.
Thread(s) per core: 2
Core(s) per
Processing control commands:
> tags -1 + moreinfo unreproducible
Bug #1071378 [src:linux] linux-image-6.7.12-686-pae: Crash during early boot
Added tag(s) moreinfo and unreproducible.
--
1071378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071378
Debian Bug Tracking System
Contact
Control: tags -1 + moreinfo unreproducible
Hi Jörn,
On Sat, May 18, 2024 at 09:37:03AM +0200, Jörn Heusipp wrote:
> Package: src:linux
> Version: 6.7.12-1
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: osm...@problemloesungsmaschine.de
>
> Hello Debian kernel team!
Processing control commands:
> clone -1 -2
Bug #1063571 [libpcre3] libpcre3: move libraries to /usr (DEP17)
Bug 1063571 cloned as bug 1071970
> retitle -2 pcre3 should not be part of trixie
Bug #1071970 [libpcre3] libpcre3: move libraries to /usr (DEP17)
Changed Bug title to 'pcre3 should not be
Processing commands for cont...@bugs.debian.org:
> notfound 1058895 2.0.30+ds1-1
Bug #1058895 [python3-sqlalchemy] python 3.12 slices are hashable, affects one
area of Row for 1.4 only
Ignoring request to alter found versions of bug #1058895 to the same values
previously set
> thanks
Stopping
Your message dated Sun, 26 May 2024 17:33:01 +
with message-id
and subject line Bug#1070838: fixed in xine-lib-1.2 1.2.13+hg20230710-2.1
has caused the Debian Bug report #1070838,
regarding xine-lib-1.2 FTBFS with glibc 2.38
to be marked as done.
This means that you claim that the problem
Your message dated Sun, 26 May 2024 17:20:08 +
with message-id
and subject line Bug#1071321: fixed in libdumbnet 1.18.0-1.1
has caused the Debian Bug report #1071321,
regarding libdumbnet: FTBFS: dpkg-gensymbols: error: some symbols or patterns
disappeared in the symbols file
to be marked as
I am uploading a NMU to fix this. Please find the debdiff attached.diff -Nru libdumbnet-1.18.0/debian/changelog libdumbnet-1.18.0/debian/changelog
--- libdumbnet-1.18.0/debian/changelog 2024-03-10 12:11:12.0 +
+++ libdumbnet-1.18.0/debian/changelog 2024-05-26 16:35:47.0
Processing commands for cont...@bugs.debian.org:
> notfound 1058895 2.0.30+ds1-1
Bug #1058895 [python3-sqlalchemy] python 3.12 slices are hashable, affects one
area of Row for 1.4 only
There is no source info for the package 'python3-sqlalchemy' at version
'2.0.30+ds1-1' with architecture ''
On Sun, May 26, 2024 at 06:12:50PM +0200, Marc Haber wrote:
> I am not too fond about the suggested patch since it breaks atop on
> systems with 32bit time_t,
It does not: promoting the time_t to a long long on all architectures before
passing it as an argument to the format string is portable to
Control: tags 1066575 + patch
Control: tags 1066575 + pending
Dear maintainer,
I've prepared an NMU for kakasi (versioned as 2.3.6-4.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. https://info.comodo.priv.at -- Debian Developer
Processing control commands:
> tags 1066575 + patch
Bug #1066575 [src:kakasi] kakasi: FTBFS: configure: error: can not use EUC-JP
or UTF-8 encoding on iconv
Added tag(s) patch.
> tags 1066575 + pending
Bug #1066575 [src:kakasi] kakasi: FTBFS: configure: error: can not use EUC-JP
or UTF-8
Processing control commands:
> tags -1 confirmed
Bug #1069859 [atop] atop: Fix atop for 64-bit time_t on arm
Added tag(s) confirmed.
> forwarded -1 https://github.com/Atoptool/atop/issues/306
Bug #1069859 [atop] atop: Fix atop for 64-bit time_t on arm
Set Bug forwarded-to-address to
Control: tags -1 confirmed
Control: forwarded -1 https://github.com/Atoptool/atop/issues/306
thanks
thanks for spotting and debugging this.
On Thu, Apr 25, 2024 at 02:16:33PM -0700, Steve Langasek wrote:
> Although atop currently builds successfully on armhf and armel, it is broken
> at runtime
Processing commands for cont...@bugs.debian.org:
> notfound 1058895 2.0.30-1
Bug #1058895 [python3-sqlalchemy] python 3.12 slices are hashable, affects one
area of Row for 1.4 only
There is no source info for the package 'python3-sqlalchemy' at version
'2.0.30-1' with architecture ''
Unable to
Source: libdata-fake-perl
Version: 0.006-1
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source
Forwarded: https://github.com/dagolden/Data-Fake/issues/15
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
t/dates.t fails on i386, looks like time_t 32 bit issues (via
Your message dated Sun, 26 May 2024 14:43:55 +
with message-id
and subject line Bug#1058265: fixed in sqlalchemy 2.0.30+ds1-1
has caused the Debian Bug report #1058265,
regarding python-flask-marshmallow: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12
Your message dated Sun, 26 May 2024 14:43:55 +
with message-id
and subject line Bug#1058102: fixed in sqlalchemy 2.0.30+ds1-1
has caused the Debian Bug report #1058102,
regarding flask-sqlalchemy: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11"
Your message dated Sun, 26 May 2024 14:43:55 +
with message-id
and subject line Bug#1057443: fixed in sqlalchemy 2.0.30+ds1-1
has caused the Debian Bug report #1057443,
regarding sqlalchemy ftbfs with Python 3.12 (segfault during tests)
to be marked as done.
This means that you claim that
Your message dated Sun, 26 May 2024 14:43:55 +
with message-id
and subject line Bug#1057443: fixed in sqlalchemy 2.0.30+ds1-1
has caused the Debian Bug report #1057443,
regarding sqlalchemy ftbfs with Python 3.12
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 26 May 2024 13:49:42 +
with message-id
and subject line Bug#1071362: fixed in rpy2 3.5.16-2
has caused the Debian Bug report #1071362,
regarding rpy2: FTBFS: rpy2/tests/rinterface/test_embedded_r.py s...Fatal
Python error: Segmentation fault
to be marked as done.
Your message dated Sun, 26 May 2024 13:34:50 +
with message-id
and subject line Bug#1071328: fixed in lomiri-indicator-network 1.0.2-5
has caused the Debian Bug report #1071328,
regarding lomiri-indicator-network: FTBFS: unit-tests failed
to be marked as done.
This means that you claim that
We are still having the open issue of rpy2 now segfaulting on the embedding
tests which reproduces on my plain vanilla amd64 setup -- so I commented that
test out too.
Laurent: Any idea why R 4.4.0 and rpy2 do not get along on embedding?
Cheers, Dirk
--
dirk.eddelbuettel.com | @eddelbuettel
Processing commands for cont...@bugs.debian.org:
> found 1070295 cgroupfs-mount/1.4
Bug #1070295 [cgroupfs-mount] cgroupfs-mount: Fails to upgrade or remove if
elogind is running: "umount: /sys/fs/cgroup/elogind: target is busy."
Marked as found in versions cgroupfs-mount/1.4.
> thanks
Stopping
Control: tag -1 pending
Hello,
Bug #1071328 in lomiri-indicator-network 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:
Processing control commands:
> tag -1 pending
Bug #1071328 [src:lomiri-indicator-network] lomiri-indicator-network: FTBFS:
unit-tests failed
Added tag(s) pending.
--
1071328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
On 25 May 2024 at 12:35, Bo YU wrote:
| Hi,
| On Sat, May 18, 2024 at 06:41:53AM -0500, Dirk Eddelbuettel wrote:
| >
| >On 17 May 2024 at 23:05, Santiago Vila wrote:
| >| Dirk Eddelbuettel wrote:
| >| > Is there a chance this could be spurious?
| >|
| >| Unlikely because it also happens here:
|
Hi Jonathan and Lucas,
I solved the problem in the new release (0.24.5.26).
I tested it with these commands:
git clone https://salsa.debian.org/debian/trash-cli.git
cd trash-cli
git remote add upstream https://github.com/andreafrancia/trash-cli
git fetch upstream
git merge 0.24.5.26
debuild -b
Your message dated Sun, 26 May 2024 11:49:37 +
with message-id
and subject line Bug#1071947: fixed in compiz 2:0.8.18-6
has caused the Debian Bug report #1071947,
regarding compiz crashes after upgrading libxml2 to 2.12.7+dfsg-2
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> tags 1071947 + pending
Bug #1071947 [compiz] compiz crashes after upgrading libxml2 to 2.12.7+dfsg-2
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1071947:
Processing control commands:
> found -1 3.5.1+dfsg1-4
Bug #1071949 [src:freerdp3] freerdp3: FTBFS on armhf (dh_auto_test
--builddirectory=debian/testtmp will fail)
Marked as found in versions freerdp3/3.5.1+dfsg1-4.
--
1071949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071949
Debian
In such bug I proposed to run mpi with true and skip
the tests if it fails.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057556#34
Maybe a similar idea would work here as well.
We can try that. As you suggested in the other bug, it might be quirk of
openmpi we're facing.
openmpi
Processing control commands:
> reassign -1 libmmap-allocator
Bug #1069451 [src:iitii] iitii: FTBFS on armhf:
Control: reassign -1 libmmap-allocator
Control: found -1 0.4.0+git20200122.adbfbe1-1
Control: fixed -1 0.4.0+git20200122.adbfbe1-2
Control: close -1
This is due to mmap not being compiled with t64 flags.
Should be fixed after added cppflags and verified that iitii compiles
in armhf chroot.
Best,
Package: compiz
Version: 2:0.8.18-5.2
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
After upgrading libxml2 to 2.12.7+dfsg-2, compiz failed to start.
* What exactly did you do (or not do) that was effective (or
Control: block -1 by 1071902
Quoting Matthias Geiger (2024-05-26 11:20:09)
> I will look into updating concurrent-queue to 2.5.0 then.
Please also see https://bugs.debian.org/1071902
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website:
Processing control commands:
> block -1 by 1071902
Bug #1069575 [src:rust-async-process] FTBFS in experimental
1069575 was blocked by: 1071902 1071900
1069575 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1069575 to the same blocks
previously set
--
1069575:
On 2024-05-25 18:31, Santiago Vila wrote:
El 25/5/24 a las 16:42, Drew Parsons escribió:
adios4dolfinx is building cleanly in reproducibility builds.
Perhaps the problem was a temporary glitch on your test system?
No, this is unlikely to be a temporary glitch:
...
My system has 2 CPUs,
Hello everyone,
On Sun, May 26, 2024 at 10:54:21AM +0200, Christoph Biedl wrote:
> Étienne Mollier wrote...
> > If that helps, the symbols strlcat and strlcpy have been added
> > to the glibc 2.38, so I believe it should be safe to remove the
> > following symbols without soname bump:
>
> Just
Processing control commands:
> reassign -1 python3-ipywidgets
Bug #1071893 [src:sagetex] sagetex: FTBFS: unsatisfiable build-dependencies
Bug reassigned from package 'src:sagetex' to 'python3-ipywidgets'.
No longer marked as found in versions sagetex/3.6.1+ds-1.
Ignoring request to alter fixed
Control: reassign -1 python3-ipywidgets
Control: found -1 8.1.1-5
Control: affects -1 src:sagetex
On 25.05.2024 19:22, Santiago Vila wrote:
Hello,
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this
On Sat, 25 May 2024 20:27:28 +0200 Jonas Smedegaard wrote:
> Control: block -1 by 1071900
>
> Quoting Jonas Smedegaard (2024-05-25 20:13:12)
> > Ahh, you are talking about *async-channel* v2.3.0. Please consider in
> > future to mention crate name, both in email subject and in content, to
> >
Christoph Biedl wrote...
> (and why does the BTS¹ not show Étienne's
> message?).
Never mind, just a race condition.
signature.asc
Description: PGP signature
Étienne Mollier wrote...
> If that helps, the symbols strlcat and strlcpy have been added
> to the glibc 2.38, so I believe it should be safe to remove the
> following symbols without soname bump:
Just came here to say the same (and why does the BTS¹ not show Étienne's
message?). There might be
Your message dated Sun, 26 May 2024 08:24:22 +
with message-id
and subject line Bug#1070459: fixed in psortb 3.0.6+dfsg-4
has caused the Debian Bug report #1070459,
regarding psortb: FTBFS: binding.c:52:13: error: implicit declaration of
function ‘free’
to be marked as done.
This means that
Your message dated Sun, 26 May 2024 08:24:08 +
with message-id
and subject line Bug#1071082: fixed in plm 2.9.2-1.1
has caused the Debian Bug report #1071082,
regarding FTBFS against jgit/6.7.0-1 in unstable
to be marked as done.
This means that you claim that the problem has been dealt
Hi Florian,
Florian Ernst, on 2024-05-18:
> # yeah, confirmed via sbuild, and I will further investigate the next chance
> I get
If that helps, the symbols strlcat and strlcpy have been added
to the glibc 2.38, so I believe it should be safe to remove the
following symbols without soname bump:
67 matches
Mail list logo
