No i cannot install labraw20 without broken my distro.
libraw19 is a part of Ubuntu 20.04 and many packages depends of this.
I cannot install libraw19 and libraw20 in same time.

But why libraw20 instead of libraw19 ?

The solution was posted here:
www.indilib.org/forum/ccds-dslrs/7562-in....html?start=12#58620

HTH

The solution doesn't work for me. See my comment later in that thread. FWIW removing libraw19 worked on my Ubuntu 20.04 RPi4 but reinstalling kstars etc doesn't work because there still are dependencies on libraw19. That is for the nightly builds by the way.


Wouter

This definitely should be possible (it is on my openSUSE Tumbleweed). That is why the version is in the package name. The only thing you cannot install simultaneously is the development packages. So if installing one removes the other, it is (IMO) a packaging bug....

I think, the problem is libraw20.
libraw19 don't break any libraries.
libraw20, yes:

libraw19:
--\ Dépend (6)
--- libc6 (>= 2.29)
--- libgcc1 (>= 1:3.0)
--- libgomp1 (>= 6)
--- libjpeg8 (>= 8c)
--- liblcms2-2 (>= 2.2+git20110628)
--- libstdc++6 (>= 5.2)
--\ Casse (1)
--- libraw19 (!= 0.19.6~202002010816~ubuntu20.04.1)
--\ Remplace (1)
--- libraw19 (< 0.19.6~202002010816~ubuntu20.04.1)
--- Paquets dépendants de libraw19 (23)


libraw20:
--\ Dépend (6)
--- libc6 (>= 2.29)
--- libgcc-s1 (>= 3.0)
--- libgomp1 (>= 6)
--- libjpeg8 (>= 8c)
--- liblcms2-2 (>= 2.2+git20110628)
--- libstdc++6 (>= 5.2)
--\ Est en conflit avec (2)
--- libraw19 (NON SATISFAIT(E))
--- libraw19
--\ Remplace (2)
--- libraw19
--- libraw19

If I read it correct, it's not breaking anything, it just has rule in the package to replace each other. Which, as I mentioned, would be a packaging error(?).

Yes, but many applications (krita, gthumb, siril...) uses libraw19, not libraw20

Which is why it is a bad idea to force the removal of libraw19 when installing libraw20. From which repo is the libraw20? I'd file a bug report...

If you know your way around you can try to force installation without execution/enforcement of dependencies, or manually extract the libs from a downloaded package and place them in /usr/lib{,64} or /usr/local/lib{,64} (+ run ldconfig). No guides for that from my side though, I'm not fluent in apt/dpkg....

I'm Linux sysadmin and i know what force an install is bad
A day or another the system will be broken.

As far as I can tell libraw20 comes from the INDI PPA.

It sure does

I carried out a --force-conflicts install of libraw20.

So now apt is broken but theoretically I could install kstars-bleeding et al manually. Removing libraw20 restores apt functionality to normal.

At any rate, libraw19 and libraw20 do not have any conflicting files, which I was able to confirm with 'dpkg-query -L'.

It comes down to the fact that libraw20's control file has 'Conflicts' and 'Replaces' entries against libraw19, while the latter has no such entries against any prior versions of libraw.

So would there be any harm in just deleting those entries in libraw20's control file to allow installation to proceed?

IIRC, I added Conflicts and Replaces because there were indeed conflicts, maybe in the development files I don't exactly remember. I'd be more than happy to make it install alongside libraw19 if someone figures out a way for them to live happily togeather.