Hello,
There was a bug in liburdfdom-dev that caused ros-robot-model to FTBFS
on arm architectures. This has been fixed in liburdfdom-dev
1.0.0-2. Please give back ros-robot-model on armel and armhf.
gb ros-robot-model_1.12.3-2 . armel armhf
Thanks.
signature.asc
Description: PGP signature
Hi,
There was a bug in ros-ros-comm that caused ros-bond-core and
ros-nodelet-core to FTBFS on mips64el. This has been fixed in
ros-ros-comm 1.12.6-1. Please give back ros-bond-core and
ros-nodelet-core on mips64el.
gb ros-bond-core_1.7.18-2 . mips64el
gp ros-nodelet-core_1.9.7-2 . mips64el
Than
Hello,
There was a bug in librosconsole-dev that caused ros-actionlib,
ros-bond-core and ros-geometry-experimental to FTBFS on sh4. This has
been fixed in librosconsole-dev 1.12.6-1. Please add a dependency wait
for it.
dw ros-actionlib_1.11.7-1 . sh4 . -m 'librosconsole-dev (>=1.12.6-1)'
dw
Hello,
There seems to have been a hiccup on the buildd that caused fdroidcl to
FTBFS on mips. I've tried it on the porterbox where it worked. Please
give back fdroidcl on mips.
gb fdroidcl_0.3.1-3 . mips
Thanks.
signature.asc
Description: PGP signature
Hello,
There was a bug in librosconsole-dev 1.12.2 that caused
ros-rosconsole-bridge to FTBFS on sh4. This has been fixed in
librosconsole-dev 1.12.6. Please give back librosconsole-dev on sh4.
gb ros-rosconsole-bridge_0.4.4-1 . sh4
Thanks.
Jochen
signature.asc
Description: PGP signature
Hi,
the build of ros-bond-core failed due to inactivity. As the package build fine
before, and even the same version in experimental, I suspect a hiccup of the
buildd, so please try it again.
gb ros-bond-core_1.8.1-2 . m68k
Thanks!
signature.asc
Description: PGP signature
Dear release team,
there was an update in catkin that caused ros-common-msgs to generate
different cmake macros. This has not been picked up on amd64 due to
transitioning through new and being build before that change.
Please give back ros-common-msgs on amd64:
gb ros-common-msgs_1.12.6-3 .
Hello,
There was a bug in libopenni0 that caused python-pcl to FTBFS on all
armhf architectures. This has been fixed in libopenni0 1.5.4.0+dfsg-2.
Please give back libopenni0 on armhf.
gb python-pcl_0.3.0~rc1+dfsg-4 . armhf
Thanks.
signature.asc
Description: PGP signature
Hello,
There was a bug in libassimp4 that caused kido to FTBFS on armhf
(#911484). This has been fixed in libassimp4 4.1.0~dfsg-5. Please give
back kido on armhf. Note that libassimp4 4.1.0~dfsg-5 not build yet, so
add a dep-wait.
dw kido_0.1.0+dfsg-6 . armhf . -m 'libassimp4 (>= 4.1.0~dfsg
Hello,
There was a change in libclass-loader-dev that caused ros-ros-comm to FTBFS on
amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el s390x hppa
sh4. Please give it back:
gb ros-ros-comm_1.14.3+ds1-5+b1 . amd64 arm64 armel armhf i386 mips mips64el
mipsel ppc64el s390x hppa sh4
Tha
Hello,
There was a change in libclass-loader-dev that caused a number of ros- to FTBFS.
Please give back:
gb ros-image-common_1.11.13-3+b2 . amd64 arm64 armel armhf i386 mips mips64el
mipsel ppc64el
gb ros-urdf_1.13.1-1+b2 . amd64 arm64 armel armhf i386 mips mips64el mipsel
ppc64el s390x
gb ro
Source: containerd
Version: 1.6.20~ds1-1
Severity: important
X-Debbugs-Cc: debian-wb-team@lists.debian.org
Usertags: unshare
Hi,
containerd uses sysctl during the build which fails as a normal user:
=== RUN TestLinuxSandboxContainerSpec
sandbox_run_linux_test.go:241: TestCase "spec should
Source: golang-github-kardianos-service
Version: 1.2.0-2
Severity: important
X-Debbugs-Cc: debian-wb-team@lists.debian.org
Usertags: unshare
Hi,
golang-github-kardianos-service fails to build when it can't detect the
OS platform:
=== RUN TestPlatformName
name_test.go:15: Platform is unix-s
Source: kel-agent
Version: 0.4.6-2
Severity: important
X-Debbugs-Cc: debian-wb-team@lists.debian.org
Usertags: unshare
Hi,
kel-agent hard codes to skip a test when build inside schroot:
https://sources.debian.org/src/kel-agent/0.4.6-2/integration/suite_test.go/#L27
But the test also fails in ot
Source: runc
Version: 1.1.12+ds1-2
Severity: important
X-Debbugs-Cc: debian-wb-team@lists.debian.org
Usertags: unshare
Hi,
runc tries to write cgroups files during the build which fails as a
normal user:
=== RUN TestDevicesSetAllow
--- FAIL: TestDevicesSetAllow (0.00s)
panic: runtime error: in
Hi Reinhard,
* Reinhard Tartler [2024-06-10 22:26]:
Are you sure that the test is actually executing a sysctl(2) command?
Looking at the code, it seems to me that this is code is assembling a
runtime spec that the CRI implementation will then carry out.
Forthermore, the output above indicates t
16 matches
Mail list logo