[3dprinter-general] Bug#1066948: Bug#1066948: prusa-slicer: No installable version on trixie

Gregor Riepl onitake at gmail.com
Sat Mar 16 11:32:19 GMT 2024


> 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 looks like prusa-slicer is not availble and that effectively means
> trixie can not do 3d printing. Which has worked so far and works as long as I
> keep the old package that I luckily have on one machine.
> This seems like a situation that should never happen IMO.

Sorry about this situation, but these things *do* happen from time to 
time. There's a large number of transitions going on right now, and 
slicer depends on several of the affected packages. That delays migration.

Unfortunately, we also had to deal with fallout from some of updated 
dependencies recently (catch2 and wxwidgets come to mind), which blocked 
automigration and caused autoremoval from trixie in December.

If you look at the package tracker[1], you can (somewhat) see what's 
going on.

There's also the issue that libbgcode (a dependency of slicer) is broken 
on all big-endian architectures, which still seems to unsolved. This 
blocks automigration, because s390x is a big-endian release architecture.
Related bug: [2]
There might still be something fishy going here.
@hyperair Do you think the situation will resolve itself, or do we need 
to exclude s390x from the Architectures in slic3r-prusa/debian/control ?


[1] https://tracker.debian.org/pkg/slic3r-prusa
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062014

More information about the 3dprinter-general mailing list