I did a quick survey of the dependency state for opentofu 1.9.1.
Missing packages:
github.com/aliyun/alibaba-cloud-sdk-go v1.61.1501
github.com/aliyun/aliyun-tablestore-go-sdk v4.1.2+incompatible
github.com/hashicorp/aws-sdk-go-base/v2 v2.0.0-beta.43
github.com/hashicorp/consul/api v1.13.0
githu
> c++: fatal error: Killed signal terminated program cc1plus
The full build log is available from:
http://qa-logs.debian.net/2025/04/16/openvdb_10.0.1-2.3_testing-arm64.log
This doesn't looks like an FTBFS to me - more like the build machine ran out of
memory.
openvdb requires a serious amount
Core was generated by
`/build/reproducible-path/mariadb-11.8.1/builddir/sql/mariadbd
--defaults-group-suffix=.1
--defaults-file=/build/reproducible-path/mariadb-11.8.1/builddir/mysql-test/var/3/my.cnf
--log-output=file --core-file --loose-debug-sync-timeout=300'.
Program terminated with signal SIG
(sorry, this should have included a Cc... I added some additional analysis
below)
Also I am not to hot about hardcoding the list of archs where swtpm is
available in debian/control but do not see a better alternatives. - Any
ideas?
swtpm is a software TPM implementation[1] and shouldn't deman
Those all look like rounding errors (probably due to x87 excess
precision, since they only happen on i386). This suggests that the
appropriate response is either to ignore these tests on i386, or
possibly (the graph object output by gdf_to_nx has (x: float, y: float)
node keys, so rounding iss
This post suggests that it could be a packaging problem:
https://nocthoughts.com/2023/04/26/arch-linux-virt-manager-and-firewalld.html
In any case, the libvirt-daemon-driver-network package contains template
firewalld zone files in /usr/lib/firewalld/zones/ - it suffices to copy them to
/etc/fi
Hi Pranav,
I have started looking at this bug and was able to reproduce it. Continuing my
debug, will update further.
Thanks for testing!
I didn't see your message and continued to trace the problem via Qemu.
As far as I can see, it's two exporter modules that incorrectly format float32
valu
I commited a fix, but it's not uploaded yet.
I'm still working on another issue, will probably request a release when both
are ready.
I tested the build with Qemu on s390x and ppc64.
Both exhibit the same behavior as reported by buildd[1], which strongly
indicates this is an endianness issue.
Investigation is ongoing.
[1]
https://buildd.debian.org/status/fetch.php?pkg=trimesh&arch=s390x&ver=4.5.1-3&stamp=1739446909&raw=0
Source: trimesh
Version: 4.5.1-3
Severity: normal
X-Debbugs-Cc: debian-s...@lists.debian.org, onit...@gmail.com
User: debian-s...@lists.debian.org
Usertags: s390x
Several unit tests of trimesh are currently failing on s390x due to math
errors:
https://buildd.debian.org/status/fetch.php?pkg=trimesh
Package: python3-collada
Version: 0.7.2-1
Severity: normal
Tags: upstream
Forwarded: https://github.com/pycollada/pycollada/pull/148
X-Debbugs-Cc: onit...@gmail.com
pkg_resources is deprecated in setuptools:
https://setuptools.pypa.io/en/latest/pkg_resources.html
pycollada 0.7.2 still uses it, bu
Here's a patch that fixes both issues and more:
1. Fixes setup.py so the unit test data files are copied during the
installation stage. This makes the unit tests work again.
2. Removes unit tests from python3-collada package. I'm not sure why they were
included in the first place. Feel free to
FWIW: I think these bugs were all caused by setuptools v72 dropping
support for the "test" command, so dh-python has fallen back to
distutils / other test plugins.
If you're trying to figure out how to fix the bug, look at the
implementation of test_suite in setup.py to see what magic it does for
Upstream supports Python 3.13 in version 0.20, which is currently in
pre-release: https://github.com/beartype/beartype/releases/tag/v0.20.0rc0
This particular issue wasn't mentioned in
https://github.com/beartype/beartype/issues/387 - but the list there may not be
exhaustive.
On the other han
Hi Alexandre,
python3-pkg-resources is the runtime part of python3-setuptools,
it is also pulled in with python3-setuptools so it was
already installed before; but we are trying to do
an archive wide cleanup of extraneous python3-setuptools
runtime dependencies and see where it still really matt
Version: 0.0.291+dfsg1-4
During a rebuild of all packages in sid, your package failed to build
on amd64.
This issue would probably be fixed by an update to the latest upstream release.
But there's significant work to be done:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068248
Package: awscli
Version: 2.17.3-1
Severity: wishlist
X-Debbugs-Cc: onit...@gmail.com
Dear Maintainer,
AWS has recently (i.e. at re:Invent Dec 2024 or just before) released a number
of new features that aren't yet supported in aws-cli 2.17.
Please upgrade the package to the latest version.
Thank
You're welcome! Unfortunately we're blocked by upstream's new code
generation dependency: libkode has no license and is not
redistributable...so I contacted them and hope for a quick resolution.
It does now, but I assume you're already aware of that:
https://github.com/cornelius/libkode/blob/ma
If llvm-15 is supported since 11.1.0, can you consider doing at least this step?
llvm-15 is still in testing while llvm-14 no.
This will hopefully restore openvdb (and blender) in testing (until
llvm-15 also get out).
According to Sylvestre's statement and upstream's comments on their lack of
re
In this particular case, there was nothing to do on your side, that's why
Adrian reassigned
the bug, meaning "not really an issue for you".
The people who have routine in finding quickly whether this is true,
and who might already know what the problem is, are the people who
are having an overv
The following packages have unmet dependencies:
sbuild-build-depends-main-dummy : Depends: python3-skimage but it is not
installable
E: Unable to correct problems, you have held broken packages.
apt-get failed.
E: Package installation failed
Broken build dependencies are often FTBFS in a buil
Cura crashes upon startup.
The problem already got reported on community for cura 5.3 but is also present
in cura 5.0.0-3 :
https://community.ultimaker.com/topic/44538-cura-53-crashs-at-startup-linux/
This problem also got reported for RedHat :
https://bugzilla.redhat.com/show_bug.cgi?id=2252195
Hi,
That doesn't look like a related bug to me, and I didn't encounter it when I
prepared and tested the patch.
Maybe some other dependency changed in the meantime?
Anyway, this should be an easy fix, just add a #include near the top
of the failing unit test source.
I'll have a go, but it cou
Confirmation: The upstream PR fixes the compilation issue, after removing the
duplicate lines.
I combined it into a single patch and pushed it to the repo.
@hyperair: Feel free to release a new Debian version when you can.
Thanks!
This issue was fixed upstream a long time ago:
https://github.com/slic3r/Slic3r/pull/4974
Fedora had the same issue: https://bugzilla.redhat.com/show_bug.cgi?id=2259590
They added a quick&dirty fix to their build files:
https://src.fedoraproject.org/rpms/slic3r/pull-request/12#request_diff
I'
Package: azure-cli
Version: 2.63.0-1
Severity: important
X-Debbugs-Cc: onit...@gmail.com
Dear Maintainer,
Many commands produce errors in the Debian release of azure-cli.
While some operation do succeed, others consistently show a stack trace due to
a missing attribute.
$ az group create -l ea
Here's a new patch that should resolve the actual root of the problem[1].
Thanks to PyTom for the hint about the loader.
[1] https://docs.python.org/3/library/sys.html#sys.meta_pathcommit 2901314d05cf0ec29e35b3f8d7199927eaf8001e
Author: Gregor Riepl
Date: Fri Aug 9 00:36:08 2024
Here's a patch that (hopefully) fixes the deprecated APIs that were removed in
FFmpeg 7.--- a/module/ffmedia.c
+++ b/module/ffmedia.c
@@ -4,6 +4,7 @@
#include
#include
#include
+#include
#include
#include
@@ -71,7 +72,11 @@
}
+#if (LIBAVFORMAT_VERSION_MAJOR < 61)
static int rwo
Here's a quick patch that will at least make renpy work again for me.
I haven't done an exhaustive search for other relative .rpy->.py imports, only
fixed those that produce errors.
--- a/launcher/game/distribute.rpy
+++ b/launcher/game/distribute.rpy
@@ -35,7 +35,7 @@
import store.updater a
File "launcher/game/gui7.rpy", line 31, in
import gui7
ModuleNotFoundError: No module named 'gui7'
I'm getting the same error.
The files seem to be installed, but I'm not sure if the location is correct:
$ dpkg -L renpy | grep gui7
/usr/share/games/renpy/launcher/game/gui7
/usr/share/
Hi, and thanks for the report.
[... snipped ...]
2: if not self._mock_unsafe and (not self._mock_methods or name not in
self._mock_methods):
2: if name.startswith(('assert', 'assret', 'asert', 'aseert',
'assrt')) or name in _ATTRIB_DENY_LIST:
2: > raise Attrib
I think I've tracked down the issue.
UM/Qt/qml/UM/SimpleButton.qml references a UI element called "ColorImage".
This class exists in Qt, but it's private and was probably changed/removed in
Qt6.
However, there's also a ColorImage class in Uranium (Cura's UI toolkit), and I
suspect they actuall
Hi Ernesto,
Is there a short term workaround you can suggest? I tried searching for the error message in the
debian package sources, something like "Re-installing the plugin" or "plugin.*could
not be loaded" but couldn't find anything.
As a matter of fact, there is.
Simply delete the two plu
Some messages that may be relevant:
2024-06-25 09:12:27,979 - ERROR - [MainThread] UM.PluginRegistry._findPlugin
[730]: Exception: Import error loading module TrimeshReader
2024-06-25 09:12:27,980 - ERROR - [MainThread] UM.PluginRegistry._findPlugin
[730]: Traceback (most recent call last):
20
Hi myon,
- Packaging trimesh for 64-bit archs only
That wouldn't be a problem.
I pushed the latest trimesh release to Salsa, limited the Arch: field to all
Debian architectures that (I think) are 32bit, and fixed some issues.
There's a bunch of optional dependencies that aren't available i
Hi Ernesto,
Any time I open cura, I see two annoying popup messages:
...
- clicking the "Remove plugin" button in the popup
- attempting the "pip install trimesh" workaround
- clicking "Marketplace -> Installed", unchecking the two problematic plugins
...
None of these solutions appears to h
that leads here: https://github.com/aws/aws-cli/issues/7905
"cannot import name 'DEFAULT_CIPHERS' from 'urllib3.util.ssl_'"
https://github.com/boto/botocore/pull/2924/files
It's not mentioned in the changelog, but this commit was already included in
1.29.123:
https://github.com/boto/botocore/c
Hi Tobias,
I've prepared an NMU for slic3r-prusa (versioned as 2.7.4+dfsg-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Thank you, but could you explain where this patch is coming from?
+ set(OCCT_LIBS
+-TKXDESTEP
+-TKSTEP
+-TKSTEP209
If a fix for this can't be released on time, I'm requesting an exception for
llvm-15. Removing OpenVDB from Debian will affect Blender, which is is
relatively high-profile and should not just be axed for the sake if a pruning
operation.
You still have time, we aren't going to release the trix
Which LLVM versions are you planning to remove?
15, 16 soon. 17 later.
Would it be possible to keep at least LLVM 15 until upstream has
upgraded their code base?
Sounds very unlikely for the next Debian release.
If a fix for this can't be released on time, I'm requesting an exception
for l
As part of the effort to limit the number of llvm packages in the
archive, it would be great if you could upgrade to -17.
This package depends on 14.
Not possible at this time. Trying to build openvdb 10.0.1 against LLVM
17 results in the following error:
CMake Error at openvdb_ax/openvdb_ax
Hi Thomas,
I tried, in Sid, doing "import sendtry_sdk" and it worked without any
problem. So it's likely this was fixed in Eventlet 0.35.1.
The upstream bug is still open, and no fix for the missing epoll was
committed. It's also unlikely that this will ever happen, as the README
in the even
Hi,
I believe this issue can be addressed by my proposed fix for #1063986:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063986#12
Regards,
Gregor
Hi,
I think this issue can be fixed by pulling in the latest sentry-sdk
version (1.43 at this point) and applying the following patch:
diff --git a/debian/rules b/debian/rules
index 206ab22..27d6911 100755
--- a/debian/rules
+++ b/debian/rules
@@ -43,6 +43,7 @@ PYBUILD_TEST_ARGS_PYTEST7_IGNOR
Hi Timo,
This is not about Build-Depends, nor about the binary package Depends.
uranium has an explicit debian/tests/control file with "Depends: @",
which only installs the built package(s) and their dependencies. Up
until now, these dependencies included all supported Python
interpreters, be
Hi Timo,
your package has an autopkgtest regression due to changes in NumPy.
The python3-numpy package no longer depends on all supported Python
versions. You need to depend on python3-all if you want to run your
tests against all supported Python releases.
Can you elaborate why this dependenc
> The upstream bug has been closed because Prusa Slicer no longer has USB
control
> capabilities.
Are you sure this is related?
Your upstream bug[1] is still open last I checked.
Also, prusa-slicer 2.7.1+dfsg-1 still depends on libbgcode[2], so it
will still FTBFS on all big endian archs and b
Hi XTL,
Looks like my system offers an upgrade for prusa-slicer, which is being kept
back. The current/old version doesn't seem to appear available at all and the
only one offered is from sid.
That isn't reasonably installable either as it seems to replace or remove half
the system.
So, it look
The upstream bug has been closed because Prusa Slicer no longer has USB control
capabilities.
Are you sure this is related?
Your upstream bug[1] is still open last I checked.
Also, prusa-slicer 2.7.1+dfsg-1 still depends on libbgcode[2], so it
will still FTBFS on all big endian archs and block
Hi,
AttributeError: module 'pyglet.graphics' has no attribute 'vertex_list'
I suspect this may not be trivial to fix.
yagv depends on pyglet 1.x, which relies on the OpenGL fixed function
pipeline. Debian has switched to 2.x and no longer supports this. [1]
Unfortunately, it appears that u
Package: python3-samba
Version: 2:4.19.5+dfsg-1
Severity: normal
X-Debbugs-Cc: onit...@gmail.com
Dear Maintainer,
It looks like the python3-samba package installs some unit tests into
/usr/lib/python3/dist-packages/samba/tests
If this is the case, please exclude them from the package build. Ther
Package: adlibtracker2
Version: 2.4.24-2
Followup-For: Bug #1038016
X-Debbugs-Cc: onit...@gmail.com
I can confirm that the package builds and runs fine with libsdl1.2-compat-dev.
However, it seems to be broken in general, because no GUI is shown and the
adtrack2 process can only be ended with a S
Hi,
After upgrading mpv to 0.37.0, resuming the paused video by clicking the UI
"play" button nor pressing the space key works -> nothing happens. With mpv <=
0.36.0, resuming works normally.
The workaround is to move video forward/backward 10 seconds (left/right key)
first. After that, resumin
Source: libbgcode
Version: 0.0~git20231219.7aaf717-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Usertags: s390x
X-Debbugs-Cc: onit...@gmail.com
Dear Maintainer,
buildd reports failing unit tests on s390x and ppc64: [1] [2]
Example error:
1: Filters: "File transversal
Hi,
python3-core is importing python3-six for absolutely no reason
this package only work by luck for now because the
library got pulled-in by something else
(most likely python3-urllib2)
$ grep ' six' /usr/lib/python3/dist-packages/botocore -r | grep import
/usr/lib/python3/dist-packages/boto
Hi Graham,
sip4's autopkgtests fail with Python 3.12 [1]. I've copied what I
hope is the relevant part of the log below.
[1] https://ci.debian.net/packages/s/sip4/testing/amd64/
22s autopkgtest [20:09:51]: test autodep8-python3: [---
22s Testing with python3.12:
22s
22s b
(sorry for the very late response, I only noticed your message just now)
I did come to the conclusion that Werkzeug 2.3.x has some bigger changes
that will break most of the existing packages in some way. The main
differences to Werkzeug 3.x than isn't that big.
Ok, that makes sense!
Althoug
Hi Carsten,
I can see that 3.0.1 is currently in experimental, but it would be enough to
upgrade to the latest 2.x to fix this issue.
this makes not really sense to me. Flask 3.0.0 and Werkzeug 3.0.0 was
released on 09-30-2023, so almost three months before. Putting energy
into Flask 2.3.5 and
I don't see any other errors in the log except for the ast.Str
deprecation warnings, and they all come from python-werkezug and not
this package.
Reassiging the bug.
Upstream has already fixed this in in 2.3.5, by the way:
https://github.com/pallets/werkzeug/issues/2704
I can see that 3.0.1 is
It looks like this issue was already fixed upstream, or at least
partially. I reported a separate bug that also references the upstream
patch and gives some more context:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057630
While this is a relatively severe bug (uninitialized memory), it
Source: slic3r-prusa
Version: 2.6.1+dfsg-4.1
Severity: normal
Tags: patch upstream ftbfs
X-Debbugs-Cc: onit...@gmail.com
The PrusaSlicer currently fails to build on multiple architectures due to an
uninitialized field in GravityKernel.hpp .
This bug causes a unit test failure, but this doesn't alw
Gah, looks like some arch-dependent glitch. Which explains why it didn't
happen to either of us (we probably both used amd64 machines, I
definitely did) and then the failure did happen upon publishing.
Thanks for your help, I'll try to help get the next fix in once it's ready.
Ok, so I have a
Hi Aaron,
Simon is uploading the new packaging to the DELAYED/1 queue. It should
arrive in the archive on November 30.
If you are a maintainer of slic3r-prusa, you can review the new
packaging in the mean time and reject or fast-track it as you see fit.
Thanks a lot for this!
The NMU is bui
Here's the promised patch.
Also, I just found that this change was done in wxWidgets 3.2.4.
Upstream PR: https://github.com/wxWidgets/wxWidgets/pull/23309
It seems the wxWidgets developers actually recommend to move away from
wxArrayString and the like:
https://github.com/wxWidgets/wxWidgets/c
Source: slic3r-prusa
Version: 2.6.1+dfsg-4
Severity: serious
Tags: ftbfs patch
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: onit...@gmail.com
Hi,
During a recent upload, PrusaSlicer failed to build due to incompatible chanes
in wxWidgets 3.2.
Thes
Hi Dave,
Since it's just a warning, I wouldn't touch it. Stable updates are
possible, but need poking the stable release managers who have more
interesting problems to fix.
In that case, I recommend comparing the list of files and removing
what's not needed:
https://packages.debian.org/book
Hi Dave,
During boot, I get a warning about a missing username "ultimaker". As far as I
can tell this stems from the dbus configuration file packaged with python3-charon
(/usr/share/dbus-1/system.d/nl.ultimaker.charon.conf) (I don't think it's the systemd
configuration file that mentions the
Here's an updated version of the patch with hardcoded precision values
replaced with the epsilon constant used in other unit tests.
I also submitted the patch as a PR upstream:
https://github.com/prusa3d/PrusaSlicer/pull/11576From: Gregor Riepl
Date: Tue, 31 Oct 2023 19:37:00 +0100
Su
chose
the one that seems most appropriate to me for what slic3r does. I
believe there is no change in correctness, the results should be well
within acceptable limits.
Regards,
GregFrom: Gregor Riepl
Date: Tue, 31 Oct 2023 19:37:00 +0100
Subject: Catch2 v3 updates
Bug-Debian: https://bugs
Hi,
> fatal error: catch2/catch.hpp: No such file or directory
This is caused by significant changes in catch2 3.4.0.
Some other packages are affected by the same problem, which currently
blocks migration: https://qa.debian.org/excuses.php?package=catch2
I think this bug should be:
reassign
Package: packagekit
Version: 1.2.7-1
Severity: important
Tags: upstream
Forwarded: https://github.com/PackageKit/PackageKit/issues/656
X-Debbugs-Cc: onit...@gmail.com
The PackageKit daemon () crashes regularly with a SIGABRT due to a failed
assertion:
domain="PackageKit", file="../src/pk-transact
Package: platformio
Version: 4.3.4-3
Severity: grave
Justification: renders package unusable
Forwarded: https://github.com/platformio/platformio-core/issues/4075
X-Debbugs-Cc: onit...@gmail.com
Dear Maintainer,
The current version of PlatformIO in Debian no longer works with python3-click
due to
Hi Reinhard,
I've now worked on packaging 4.6.2, and it is currently available
in debian/experimental. Can you do me a favor? Please test it and let me
know whether
it fixes this issue.
Thanks, it looks very promising!
On a system without any storage.conf files, but with existing vfs
conta
As mentioned in the upstream bug report[1], the fix is actually in
containers/storage 1.48, included with podman 4.6 and not 4.5.
So, the bug can (hopefully) be fixed for good when this version is packaged.
It might also be helpful to include a what's new message, to make users
aware they need
Package: openjdk-17-jre
Version: 17.0.9~4ea-1
Severity: normal
X-Debbugs-Cc: onit...@gmail.com
The OpenJDK version in Debian includes the GTK+ theme, but the
SystemLookAndFeelClassName is set to the default Swing Metal theme.
Manually loading the GTK+ theme works, but this is very unportable and
s
Package: podman
Version: 4.5.1+ds1-2
Followup-For: Bug #1050993
X-Debbugs-Cc: onit...@gmail.com
Control: found -1
Thanks for upgrading the package, but it looks like the issue isn't fixed in
4.5 after all.
After upgrading and removing /etc/containers/storage.conf (to revert to default
behavior),
Package: podman
Version: 4.4.0+ds1-1
Severity: normal
Forwarded: https://github.com/containers/podman/issues/19811
X-Debbugs-Cc: onit...@gmail.com
The vfs storage driver in Podman has been the recommended upstream default up
until 4.4, but there isn't really a good reason to use it any more. The o
Package: firmware-amd-graphics
Version: 20230515-3
Tags: fixed-upstream, upstream
Followup-For: Bug #1042818
X-Debbugs-Cc: onit...@gmail.com
linux-firmware 20230804 has been released and contains the mentioned reverts
for amdgpu firmware.
This is not a permanent fix of the underlying problem, but
Package: firmware-amd-graphics
Version: 20230515-3
Followup-For: Bug #1043024
X-Debbugs-Cc: onit...@gmail.com
Can you post which firmware files are missing exactly?
dmesg should give you all the needed information.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT po
Here's a temporary workaround until the issue is fixed.
Either set the environment variable EVENTLET_NO_GREENDNS to "yes" before
launching applications that import eventlet, or put the following Python
code before loading the module:
import os
os.environ['EVENTLET_NO_GREENDNS'] = 'yes'
import
Package: firmware-amd-graphics
Version: 20230515-3
Severity: important
Tags: upstream
Forwarded: https://gitlab.freedesktop.org/drm/amd/-/issues/1887
X-Debbugs-Cc: onit...@gmail.com
Dear Maintainer,
The current AMDGPU firmware in Debian has compatibility issues with 6.3+
kernels.
These errors man
Package: mixxx
Version: 2.3.5+dfsg-1+b1
Severity: important
Followup-For: Bug #1039859
X-Debbugs-Cc: onit...@gmail.com
This issue does not occur for me on X.org.
While the rendering of album covers and the waveforms is suboptimal (lack of
interpolation, movement jitter, transparency issues at the
Package: python3-eventlet
Version: 0.33.1-4
Severity: important
Tags: upstream
Forwarded: https://github.com/eventlet/eventlet/issues/805
X-Debbugs-Cc: onit...@gmail.com
Control: affects -1 cura
Dear Maintainer,
The eventlet module has a known incompatibility with dnspython 0.24, that
causes it t
purelib: directory for site-specific, non-platform-specific files
(https://docs.python.org/3/library/sysconfig.html)
"site-specific" doesn't sound like packages should install anything
there.
"site-specific" may be meant from the perspective of the Python
interpreter, not the whole system, so
Source: uranium
Version: 5.0.0-2
Followup-For: Bug #1042157
X-Debbugs-Cc: onit...@gmail.com
This is caused by a change in cmake 3.27.
In 3.26.4-4, Python_SITELIB is /usr/lib/python3/dist-packages.
In 3.27.1-1, it's /usr/local/lib/python3.11/dist-packages
The documentation for 3.26 states:
> Inf
-- Installing:
/<>/debian/tmp/usr/local/lib/python3.11/dist-packages/UM
-- Installing:
/<>/debian/tmp/usr/local/lib/python3.11/dist-packages/UM/ColorImage.py
dh_install: warning: Cannot find (any matches for)
"usr/lib/python3/dist-packages/UM" (tried in ., debian/tmp)
dh_install: warning
Here's an excerpt of the failing tests:
test 21
Start 21: PolygonConnectorTest
21: Test command: cura-engine/obj-i686-linux-gnu/PolygonConnectorTest
21: Working Directory: cura-engine/tests/
21: Test timeout computed to be: 1500
5: [ OK ]
InfillTestcases/InfillTest.TestInfillSanity/
Source: cura-engine
Version: 5.0.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Usertags: i686
Forwarded: https://github.com/Ultimaker/CuraEngine/issues/1192
X-Debbugs-Cc: onit...@gmail.com
On i686, CuraEngine 5.x fails to build due
Upstream has fixed this via
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=5b429b870767e2107bcc7d5d849e04d6901b5912
Thanks for uploading the fix.
Unfortunately, it looks like the buildds are still choking on it:
https://buildd.debian.org/status/package.php?p=binutils-avr
#
I'm sorry Gregor, this is what happened, I mis-reported against 4.13. I hope
it wasn't too much of a time waste.
Fixing 5.0.0 should be sufficient. Thank you.
All right - I went ahead and marked the correct version.
It looks the next release is still on hold because of an old FPU
rounding i
thanks for collecting all the patches and putting them together.
There's still an issue on i386 left, and at least from looking at the
CI tests, it might have been caused by this fix:
https://salsa.debian.org/3dprinting-team/cura-engine/-/pipelines
Any ideas?
Very interesting!
I couldn't rep
> Could that please be disabled?
It's coming in version 8.
> a) It's a security risk. It's aboslutely unclear who controls these files
>(at least not debian).
I hear your concerns. These files are data that used to be shipped as part of
digikam and were later unbundled, which led to the d
The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.
This issue was due to a missing #include , and it was already
fixed upstream in an unrelated commit.
Hi Dan,
I tested the upstream CuraEngine commit and then realized that
refreshing it results in the same patch as yours, so I pushed your
version instead.
Now, I'm slightly confused about the version you reported this against.
According to the report, it affects 4.13, but the changes requirin
Package: azure-cli
Version: 2.50.0-2
Severity: important
Followup-For: Bug #1034797
X-Debbugs-Cc: onit...@gmail.com
With azure-cli 2.50.0-2, the keyvault feature is still broken, but it fails
with a different error now:
$ az keyvault secret show --vault-name myvault --name mykey
No module named '
Hi Dan,
Visible in both Sid and Ubuntu Mantic is the following autopkgtest error:
[ERROR] Trying to retrieve setting with no value given: 'adhesion_extruder_nr'
See the attached patch, which is just a trivial backport of
https://github.com/Ultimaker/CuraEngine/pull/1693
Thanks for that patch,
Hi myon,
I've tested the patch both on amd64 and i686 (in a chroot) and pushed it
to Salsa.
Could you upload cura-engine 5.0.0-4 when you have time?
Thank you very much!
Regards,
Gregor
This is actually a bug in the test and not CuraEngine.
In tests/InfillTest.cpp:104, they format a size_t as %lld instead of
%zu. %llu works as well, but it's not 100% correct with a 32-bit size_t.
Current upstream HEAD still has the bug, so I'm going to report it there
as well:
https://githu
Package: python3-charon
Version: 5.0.0-3
Severity: normal
Forwarded: https://github.com/Ultimaker/libCharon/issues/45
X-Debbugs-Cc: onit...@gmail.com
Upstream has reported that the metadata service is only relevant on Ultimaker
3D printers.
The service file installed in /lib/systemd/system/charon
Hi myon,
Cmake files check for matching architecture width now, mark package as Arch: any
* Cmake files check for matching architecture width now, mark package as
Arch: any. (The header files themselves do not change. Closes: #1040191)
* Drop M-A: foreign.
Thanks for the quick fix, but I'm
1 - 100 of 431 matches
Mail list logo
