[Helmut Grohne]
> since the last upload, libx52pro0 contains both
> /lib/udev/rules.d/99-x52pro.rules and
> /usr/lib/udev/rules.d/99-x52pro.rule.
Ah, thanks for letting me know. Sorry I failed to discovered this
during testing. I will keep the issue with dh_install
vs. dh_installudev in mind for
Commit
https://github.com/performancecopilot/pcp/commit/bf6c6f5ed69eeadfe697958b1c060fd947923058
resolves this issue by moving the PCP pmcheck command out of /usr/bin.
Processing commands for cont...@bugs.debian.org:
> forwarded 1071017 https://github.com/exeldro/obs-source-copy/issues/10
Bug #1071017 [obs-source-copy] FTBFS: source-copy.cpp:615:31: error: ‘void
obs_sceneitem_get_info(const obs_sceneitem_t*, obs_transform_info*)’ is
deprecated [-Werror=depreca
Package: obs-source-copy
Version: 0.2.2-5
Severity: serious
Tags: upstream
Justification: FTBFS
When rebuilding the source code, we got:
/usr/bin/c++ -DHAVE_OBSCONFIG_H -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG
-DQT_WIDGETS_LIB -Dsource_copy_EXPORTS
-I/PKGS/obs-source-copy/1/obs-source-copy-0.2.
Processing commands for cont...@bugs.debian.org:
> # debdiff between 4 and 5 does not show the fix, so it's not fixed in version
> 5
> notfixed 1031439 5
Bug #1031439 [src:gcc-sh-elf] gcc-sh-elf: FTBFS: make[6]: *** No rule to make
target '../libsframe/libsframe.la', needed by 'libbfd.la'. Stop
Processing commands for cont...@bugs.debian.org:
> found 1031439 8
Bug #1031439 {Done: John Scott } [src:gcc-sh-elf]
gcc-sh-elf: FTBFS: make[6]: *** No rule to make target
'../libsframe/libsframe.la', needed by 'libbfd.la'. Stop.
Marked as found in versions gcc-sh-elf/8 and reopened.
> tags 103
found 1031439 8
tags 1031439 + patch
tags 1031439 - fixed
thanks
Hi.
For some reason, version 8 does not include the fix that was
applied in version 4.1 to fix this bug. As a result, the
current version still has the bug (see attach).
I'm including the patch (taken from the diff between 4 and 4
Hi Bernd,
thanks for your report.
This looks like #1029939 (https://bugs.debian.org/1029939) in shaderc.
supertuxkart 1.4+dfsg-4, which uses the shaderc package instead of a
bundled copy, has migrated to testing before shaderc 2023.8-1, which
fixes the linking problem.
Can you please try upgradin
Hi Bastian,
I've intentionally snipped much of your reply as I think we two agree on
many of the aspects.
On Sun, May 12, 2024 at 07:35:09PM +0200, Bastian Blank wrote:
> > 1. API expectation of *-$arch-cross packages
>
> I asked exactly that in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bu
El 7/5/24 a las 19:43, Uecker, Martin escribió:
Yes, if you do not mind to do the work, please update bullseye.
That would be much appreciated.
Hi. The uploads for bart and bart-cuda have been accepted for
bullseye-proposed-updates.
So I pushed the pending changes to salsa.
One thing I didn't
Processing control commands:
> tag -1 pending
Bug #1069528 [src:mingw-w64] mingw-w64: FTBFS on armhf: _wstat.c:68:1: error:
conflicting types for ‘wstat’; have ‘int(const wchar_t *, struct _stati64 *)’
{aka ‘int(const short unsigned int *, struct _stati64 *)’}
Added tag(s) pending.
--
1069528:
Control: tag -1 pending
Hello,
Bug #1069528 in mingw-w64 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/mingw-w64-team/mingw-w64/-/commit/90fb8e2afd9656aaf25dc
Processing control commands:
> affects -1 + libpoppler-cpp0v5
Bug #1071009 [libpoppler-cpp0t64] libpoppler-cpp0t64 has an undeclared file
conflict
Added indication that 1071009 affects libpoppler-cpp0v5
--
1071009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071009
Debian Bug Tracking Sy
Processing control commands:
> affects -1 + pmtools
Bug #1071010 [pcp] pcp has an undeclared file conflict on /usr/bin/pmcheck
Added indication that 1071010 affects pmtools
--
1071010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071010
Debian Bug Tracking System
Contact ow...@bugs.debian.
Package: pcp
Version: 6.2.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + pmtools
pcp has an undeclared file conflict. This may result in an unpack error
from dpkg.
The file /usr/bin/pmcheck is contained in the packages
* pcp/6.2.1-1 as present
Package: libx52pro0
Version: 0.1.1-3
Severity: serious
Justification: policy 10.1
Tags: patch
X-Debbugs-Cc: Petter Reinholdtsen
Hi,
since the last upload, libx52pro0 contains both
/lib/udev/rules.d/99-x52pro.rules and
/usr/lib/udev/rules.d/99-x52pro.rule. Doing so violates Debian policy
section
Package: libpoppler-cpp0t64
Version: 24.02.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libpoppler-cpp0v5
libpoppler-cpp0t64 has an undeclared file conflict. This may result in
an unpack error from dpkg.
The files
* /usr/lib/x86_64-linux-gnu
Processing control commands:
> affects -1 + pycrc
Bug #1071007 [sherlock] sherlock has an undeclared file conflict on
/usr/lib/python3/dist-packages/__init__.py
Added indication that 1071007 affects pycrc
--
1071007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071007
Debian Bug Tracking
Package: sherlock
Version: 0.14.3+git20240511.b83f5be-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + pycrc
sherlock has an undeclared file conflict. This may result in an unpack
error from dpkg.
The file /usr/lib/python3/dist-packages/__init__.py
Processing control commands:
> affects -1 + vc-dev
Bug #1071006 [conky-cli,conky-std,conky-all] conky-all, conky-cli and conky-std
have an undeclared file conflict
Added indication that 1071006 affects vc-dev
--
1071006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071006
Debian Bug Track
Package: conky-cli,conky-std,conky-all
Version: 1.21.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + vc-dev
conky-all, conky-cli and conky-std have an undeclared file conflict.
This may result in an unpack error from dpkg.
The files
* /usr/lib/
Processing control commands:
> affects -1 + rustc rustc-mozilla rustc-web
Bug #1071005 [rust-llvm] rust-llvm has an undeclared file conflict
Added indication that 1071005 affects rustc, rustc-mozilla, and rustc-web
--
1071005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071005
Debian Bug
Package: rust-llvm
Version: 1.71.1+dfsg1-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + rustc rustc-mozilla rustc-web
rust-llvm has an undeclared file conflict. This may result in an unpack
error from dpkg.
The files
* /usr/bin/rust-clang
Bastian Germann dixit:
>> Do you have a link?
>
> No. It is not a public address.
Ah, yes, that is unfortunate. I used to be subscribed and have no
idea why I’m not, but I re-subscribed (though have not yet seen any
traffic in the last couple of days).
>> What did upstream say?
>
> No upstream r
Your message dated Sun, 12 May 2024 19:47:31 +
with message-id
and subject line Bug#1026061: fixed in bart 0.6.00-3+deb11u1
has caused the Debian Bug report #1026061,
regarding bart: FTBFS randomly in bullseye (failing test)
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 12 May 2024 19:47:31 +
with message-id
and subject line Bug#1070757: fixed in bart-cuda 0.6.00-1+deb11u1
has caused the Debian Bug report #1070757,
regarding bart-cuda: FTBFS in bullseye: failing tests
to be marked as done.
This means that you claim that the problem ha
Source: audit
Version: 1:3.1.2-2
Severity: serious
Control: close -1 1:3.1.2-2.1
X-Debbugs-CC: vor...@debian.org
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1070327
Dear maintainer(s),
The Release Team considers packages that are out-o
Processing control commands:
> close -1 1:3.1.2-2.1
Bug #1071003 [src:audit] src:audit: fails to migrate to testing for too long:
piuparts regression
Marked as fixed in versions audit/1:3.1.2-2.1.
Bug #1071003 [src:audit] src:audit: fails to migrate to testing for too long:
piuparts regression
M
Processing commands for cont...@bugs.debian.org:
> severity 1069480 wishlist
Bug #1069480 [src:bochs] bochs: FTBFS on armhf: build-dependency not
installable: gcc-i686-linux-gnu
Severity set to 'wishlist' from 'serious'
> tags 1069480 + wontfix
Bug #1069480 [src:bochs] bochs: FTBFS on armhf: buil
Package: ruby-mysql2
Version: 0.5.5-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-powe...@lists.debian.org
Hi,
https://buildd.debian.org/status/fetch.php?pkg=ruby-mysql2&arch=ppc64el&ver=0.5.5-2&stamp=1715331286
Your message dated Sun, 12 May 2024 19:19:11 +
with message-id
and subject line Bug#1070713: fixed in how-can-i-help 19
has caused the Debian Bug report #1070713,
regarding how-can-i-help: undefined local variable or method autorm_header_done
to be marked as done.
This means that you claim th
close 1065662 8.1.2-2
thanks
Processing commands for cont...@bugs.debian.org:
> close 1065662 8.1.2-2
Bug #1065662 [src:ipywidgets] FTBFS: error: aborting due to unexpected upstream
changes
The source 'ipywidgets' and version '8.1.2-2' do not appear to match any binary
packages
Marked as fixed in versions ipywidgets/8.1.2-2
Your message dated Sun, 12 May 2024 19:04:57 +
with message-id
and subject line Bug#1070256: fixed in libcxx-serial 1.2.1-6
has caused the Debian Bug report #1070256,
regarding libcxx-serial FTBFS with the nocheck build profile
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> forwarded 1069074
> https://github.com/totalopenstation/totalopenstation/issues/173
Bug #1069074 [src:totalopenstation] totalopenstation: FTBFS: failing tests
Ignoring request to change the forwarded-to-address of bug#1069074 to the same
value
>
On Sat, Apr 13, 2024 at 01:59:28AM +0300, Peter Pentchev wrote:
>...
> I will probably upload a new ucspi-tcp version in a couple of days.
Any update on this?
> G'luck,
> Peter
Thanks
Adrian
Processing commands for cont...@bugs.debian.org:
> # ssl certificate expired again
> notfixed 1036255 1.12.0-2+deb12u1
Bug #1036255 {Done: Santiago Vila }
[src:python3-onelogin-saml2] python3-onelogin-saml2: FTBFS in bookworm and
above: AssertionError: "Invalid issuer in the Logout Request" does
Processing commands for cont...@bugs.debian.org:
> severity 1067954 important
Bug #1067954 [src:openmesh] openmesh: FTBFS on armel,armhf
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1067954: https://bugs.debian.org/cgi
Processing commands for cont...@bugs.debian.org:
> unarchive 1036255
Bug #1036255 {Done: Santiago Vila }
[src:python3-onelogin-saml2] python3-onelogin-saml2: FTBFS in bookworm and
above: AssertionError: "Invalid issuer in the Logout Request" does not match
"Could not validate timestamp: expired
Processing commands for cont...@bugs.debian.org:
> tags 1058436 + bookworm
Bug #1058436 [src:py-rnp] py-rnp: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) bookworm.
> thanks
Stopping processing here.
Please contact m
On Sun, May 12, 2024 at 01:53:33PM +0200, Helmut Grohne wrote:
> 2+3+6+7. linux-libc-dev could be split into linux-libc-dev-common
>arch:all m-a:foreign and the symlink farms could be kept in
>linux-libc-dev:any m-a:same retaining the size reduction.
This would not actually work. linux-li
Your message dated Sun, 12 May 2024 17:55:21 +
with message-id
and subject line Bug#1070795: fixed in xfsprogs 6.7.0-3
has caused the Debian Bug report #1070795,
regarding xfsprogs-udeb: the udeb is empty (size 904 bytes) so does not contain
mkfs.xfs
to be marked as done.
This means that you
Hi Helmut
On Sun, May 12, 2024 at 01:53:33PM +0200, Helmut Grohne wrote:
> > Care to just share what you actually found? Where is it broken and how
> > to see this?
> > Because this whole thing started with "it is broken, but I won't tell
> > you where or what or how".
> Quite clearly, this is no
Your message dated Sun, 12 May 2024 17:21:46 +
with message-id
and subject line Bug#1070912: fixed in libuv1 1.48.0-3
has caused the Debian Bug report #1070912,
regarding libuv1: latest upload reverts 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:
> # this is happening in bullseye and bookworm
> found 1052942 1.21.0-1.1
Bug #1052942 {Done: Mark Hindley } [src:insserv] Upstream
testsuite fails to produce deterministic results
Marked as found in versions insserv/1.21.0-1.1.
> found 1052942 1.2
Processing commands for cont...@bugs.debian.org:
> unarchive 1052942
Bug #1052942 {Done: Mark Hindley } [src:insserv] Upstream
testsuite fails to produce deterministic results
Unarchived Bug 1052942
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1052942: https:/
Processing control commands:
> close -1 20240408-1
Bug #1070995 [src:eclib] src:eclib: fails to migrate to testing for too long:
FTBFS on arm 32 bits
Marked as fixed in versions eclib/20240408-1.
Bug #1070995 [src:eclib] src:eclib: fails to migrate to testing for too long:
FTBFS on arm 32 bits
M
Source: eclib
Version: 20231212-1
Severity: serious
Control: close -1 20240408-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1069515
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unst
Source: praat
Version: 6.4.05+dfsg-1
Severity: serious
Tags: sid trixie ftbfs
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 30 days as having a Release Cr
Processing control commands:
> close -1 4.0.0.1-1
Bug #1070993 [src:ukui-power-manager] src:ukui-power-manager: fails to migrate
to testing for too long: unresolved RC bug
Marked as fixed in versions ukui-power-manager/4.0.0.1-1.
Bug #1070993 [src:ukui-power-manager] src:ukui-power-manager: fails
Source: ukui-power-manager
Version: 3.1.1-1
Severity: serious
Control: close -1 4.0.0.1-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1070426
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
Your message dated Sun, 12 May 2024 16:31:46 +
with message-id
and subject line Bug#1070898: fixed in slurm-wlm 23.11.6-1
has caused the Debian Bug report #1070898,
regarding slurm-wlm: FTBFS: dpkg-gensymbols: error: some symbols or patterns
disappeared in the symbols file: see diff output be
Processing control commands:
> tags -1 +patch +pending
Bug #1070838 [src:xine-lib-1.2] xine-lib-1.2 FTBFS with glibc 2.38
Added tag(s) patch.
Bug #1070838 [src:xine-lib-1.2] xine-lib-1.2 FTBFS with glibc 2.38
Added tag(s) pending.
--
1070838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=10
Control: tags -1 +patch +pending
Dear maintainer,
I've prepared an NMU for xine-lib-1.2 (versioned as 1.2.13+hg20230710-2.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru xine-lib-1.2-1.2.13+hg20230710/debian/changelog
xine-lib-1.
Source: ruby-parslet
Version: 1.8.2-4
Severity: serious
Control: close -1 2.0.0-1
Tags: sid trixie
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 30 days a
Processing control commands:
> close -1 2.0.0-1
Bug #1070989 [src:ruby-parslet] src:ruby-parslet: fails to migrate to testing
for too long: triggers autopkgtest issues
Marked as fixed in versions ruby-parslet/2.0.0-1.
Bug #1070989 [src:ruby-parslet] src:ruby-parslet: fails to migrate to testing
Processing control commands:
> close -1 2024.2.0+dfsg-1
Bug #1070988 [src:q2-feature-table] src:q2-feature-table: fails to migrate to
testing for too long: autopkgtest regression
Marked as fixed in versions q2-feature-table/2024.2.0+dfsg-1.
Bug #1070988 [src:q2-feature-table] src:q2-feature-table
Source: q2-feature-table
Version: 2023.9.0+dfsg-1
Severity: serious
Control: close -1 2024.2.0+dfsg-1
Tags: sid trixie
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
Processing control commands:
> close -1 0.6.0-3
Bug #1070987 [src:tiktoken] src:tiktoken: fails to migrate to testing for too
long: autopkgtest regression
Marked as fixed in versions tiktoken/0.6.0-3.
Bug #1070987 [src:tiktoken] src:tiktoken: fails to migrate to testing for too
long: autopkgtest
Source: tiktoken
Version: 0.4.0-2
Severity: serious
Control: close -1 0.6.0-3
Tags: sid trixie
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 30 days as ha
Good morning,
This bug has been her over 6 months now. Is there some sort of issue? I want to
check in because this bug is a fairly straightforward fix, or so it seems.
Seems well overdue that this be resloved and the package returned to testing...
Am 04.05.24 um 03:33 schrieb Thorsten Glaser:
Hi Bastian,
I have already informed upstream about it.
did you do that on a mailing list?
I have reported to felix-dietl...@fefe.de.
Do you have a link?
No. It is not a public address.
What did upstream say?
No upstream response up to no
Package: supertuxkart
Version: 1.4+dfsg-4
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: b...@zockertown.de
Dear Maintainer,
Trying to start supertuxkart from console brings this as answer, after last
full-upgrade
supertuxkart: symbol lookup error: /lib/x86_64-linux-gnu/l
Your message dated Sun, 12 May 2024 12:34:51 +
with message-id
and subject line Bug#1070909: fixed in llvm-toolchain-18 1:18.1.5-3
has caused the Debian Bug report #1070909,
regarding llvm-toolchain-18: FTBFS on riscv64: dh_install: warning:
llvm-18-linker-tools missing files: usr/lib/llvm-18
Your message dated Sun, 12 May 2024 12:34:51 +
with message-id
and subject line Bug#1070811: fixed in llvm-toolchain-18 1:18.1.5-3
has caused the Debian Bug report #1070811,
regarding llvm-toolchain-18: FTBFS on armel:
cxa_guard.cpp:(.text.unlikely.__cxa_guard_acquire+0x28): undefined referen
Your message dated Sun, 12 May 2024 12:18:07 +
with message-id
and subject line Bug#1063264: Removed package(s) from unstable
has caused the Debian Bug report #1042244,
regarding python-future: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11 returned exit c
Hi,
In this mail, I'll try to summarize my state of knowledge on this
matter while noting that I don't see the full picture.
On Fri, Mar 29, 2024 at 11:17:55AM +0100, Bastian Blank wrote:
> On Thu, Mar 21, 2024 at 08:48:01PM +0100, Helmut Grohne wrote:
> > I was recently working on gcc builds and
Processing control commands:
> close -1 0.5.2-2
Bug #1070982 [src:click] src:click: fails to migrate to testing for too long:
autopkgtest regression on !amd64
Marked as fixed in versions click/0.5.2-2.
Bug #1070982 [src:click] src:click: fails to migrate to testing for too long:
autopkgtest regr
Source: click
Version: 0.5.0-10
Severity: serious
Control: close -1 0.5.2-2
Tags: sid trixie
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 30 days as havi
Control: tags -1 + confirmed upstream
Control: forwarded -1 https://gitlab.com/german.tischler/libmaus2/-/issues/40
In the end, I could reproduce the test failures affecting
libmaus2 on amdahl and informed upstream. We'll see how things
go.
Have a nice day, :)
--
.''`. Étienne Mollier
: :
Processing control commands:
> tags -1 + confirmed upstream
Bug #1069691 [src:libmaus2] libmaus2: FTBFS on arm64: what():
AutoArray failed to allocate
1398102 elements (11184816 bytes)
Added tag(s) upstream and confirmed.
> forwarded -1 https://gitlab.com/german.tischler/libmaus2/-/issues/40
Source: libamplsolver
Version: 0~20190702-2
Severity: serious
Tags: patch upstream ftbfs
Justification: fails to build from source (but built successfully in the past)
User: debian-ri...@lists.debian.org
Usertags: riscv64
Dear maintainer,
libamplsolver fails to build from source on a few architec
Hi Santiago,
thanks for the report. This seems to be due to git 1:2.30.2-1+deb11u1 as
it works with the version before (1:2.30.2-1). Give that it is a
security fix and a testing only problem that could worked around easily,
I would leave this as is.
Cheers Jochen
* Santiago Vila [2024-05-1
Package: puddletag
Version: 2.3.0-1
Severity: grave
Tags: patch
Justification: renders package unusable
Dear Maintainer,
The new version of python3-pyparsing will prevent puddletag from running.
See https://github.com/puddletag/puddletag/issues/884
However, it can be fixed by adding "ParserEle
Processing commands for cont...@bugs.debian.org:
> owner 1070950 sanv...@debian.org
Bug #1070950 {Done: Santiago Vila } [src:pysph] pysph:
FTBFS in bullseye
Owner recorded as sanv...@debian.org.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1070950: https://bug
owner 1070950 sanv...@debian.org
thanks
El 12/5/24 a las 8:36, Santiago Vila escribió:
Another option is that I simply change NPROCS to 1 as you point out,
verify that it works, including machines with a single cpu, and do the
proposed-updates upload (but in this case the mystery of mpi would
re
Processing control commands:
> tags -1 pending
Bug #1068363 [src:autopkgtest] autopkgtest: test_copy_timeout fails on tmpfs
Added tag(s) pending.
--
1068363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 pending
Hi,
On 06-04-2024 9:58 p.m., Paul Gevers wrote:
Anyways, it looks like we could just lower the timeout to 1 second and
hope were fine for some time to come.
No. 1 second is *too short* for the PodmanRunner.test_copy_timeout test
on salsa. So I'll just disable the tes
78 matches
Mail list logo
