×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Libraw19 and libraw20 conflict in 1.8.6?

  • Posts: 2
  • Thank you received: 0
Worked for me. Installed it from a modified deb, apt keeps wanting to update it from the one in the ppa but it won't as long as the conflict is still there.
3 years 7 months ago #58801

Please Log in or Create an account to join the conversation.

  • Posts: 1009
  • Thank you received: 133

Yes, the devel files will conflict. The usual way is to split this in two parts, one with only the libs (i.e., libraw19, libraw20 containing libraw.so.XX and libraw_r.so.XX), and one, unversioned, with the devel files (headers, unversioned .so link), libraw-dev. Those will conflict, and there it is fine to replace the earlier version, as one usually wants to compile against the latest version. But normal users probably wouldn't install the devel part anyhow...
3 years 7 months ago #58805

Please Log in or Create an account to join the conversation.

The development package is actually required to build KStars in the PPA, hence this conundrum.
3 years 7 months ago #58807

Please Log in or Create an account to join the conversation.

  • Posts: 1009
  • Thank you received: 133
Sure, but the dependencies should only be that libraw-dev (version 20) requires libraw20 and replaces libraw-dev (version <=19). libraw20 however should not replace earlier versions, so that you can keep different versions of the library in parallel (which is the idea behind using librawXX instead of just libraw).
3 years 7 months ago #58810

Please Log in or Create an account to join the conversation.

The debian files are located here: git.launchpad.net/~mutlaqja/+git/packaging/tree/libraw

If you can get BOTH libraw20 and libraw-dev to install gracefully alongside libraw19, please post the necessary patch so I can apply it.
3 years 7 months ago #58811

Please Log in or Create an account to join the conversation.

  • Posts: 1009
  • Thank you received: 133
As Aurneth suggests, it seems it is only the two lines
Conflicts: libraw19
Replaces: libraw19
in the control file (section libraw20) that should just be deleted. But I have no Debian system (and only guess this from similarities to the SPEC files of rpm)
3 years 7 months ago #58816

Please Log in or Create an account to join the conversation.

  • Posts: 6
  • Thank you received: 0

Also, it would appear, gimp, shotwell and my own :(

James
3 years 7 months ago #58881

Please Log in or Create an account to join the conversation.

  • Posts: 6
  • Thank you received: 0
Meanwhile, is there a way to install the previous releases of indi-full and kstars-bleeding to avoid this problem?

James
3 years 7 months ago #58882

Please Log in or Create an account to join the conversation.

  • Posts: 216
  • Thank you received: 120
@knro I'm not sure how to build the packages using this source, but here's a patch that SHOULD work.
diff --git a/libraw/control b/libraw/control
index 429991c..e836b8d 100644
--- a/libraw/control
+++ b/libraw/control
@@ -17,8 +17,6 @@ Architecture: any
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends},
          ${misc:Depends}
-Conflicts: libraw19
-Replaces: libraw19
 Multi-Arch: same
 Description: raw image decoder library
  LibRaw is a library for reading RAW files obtained from digital photo cameras

This still leaves libraw-dev depending on libraw20, but allows libraw19 and libraw20 to be installed side-by-side.
3 years 7 months ago #58891

Please Log in or Create an account to join the conversation.

and what happens when the user install libraw-dev ?
3 years 7 months ago #58919

Please Log in or Create an account to join the conversation.

  • Posts: 1009
  • Thank you received: 133
The old version of the dev package will be removed. So you cannot compile against libraw19 anymore.
If libraw20 is not (yet) installed, it will be installed as dependency. But as there is no longer a conflict it will not remove libraw19 (which for the package system is a completely different package). In contrast, the libraw-dev is an update to the 'same' package.
Also, if someone had installed the first libraw20 versions (with or without the -dev), which had removed libraw19, after updating to the updated version without the Conflicts/Replaces nothing would prevent them from installing libraw19 again.
The only issue could be if libraw19 has a conflict against higher versions, but I strongly doubt that.
3 years 7 months ago #58921

Please Log in or Create an account to join the conversation.

  • Posts: 216
  • Thank you received: 120
I just tested a local install by manually removing the Replaces and Conflicts lines in the libraw20 deb available on the stable ppa. I was able to install both libraw19 and libraw20 along side libraw-dev (0.20).
sudo apt list --installed | grep libraw
 
libraw-dev/focal,now 0.20.0~202008211452~ubuntu20.04.1 amd64 [installed]
libraw1394-11/focal,now 2.1.2-1 amd64 [installed]
libraw19/focal,now 0.19.6~202002010816~ubuntu20.04.1 amd64 [installed]
libraw20/now 0.20.0~202008211452~ubuntu20.04.1 amd64 [installed,upgradable to: 0.20.0~202008211452~ubuntu20.04.1]
3 years 7 months ago #58922

Please Log in or Create an account to join the conversation.

Time to create page: 1.291 seconds