Public bug reported:

There is an issue where old package versions are getting released for
newer Ubuntu releases without properly updating the shared-library
references. This causes regressions where a package that worked in
previous versions starts to fail with an error like:

photoprint: error while loading shared libraries: libgutenprint.so.2:
cannot open shared object file: No such file or directory

The underlying issue seems to cause reappearing bugs like bug #260849,
where the photoprint package refers to libgutenprint.so.2 (the file in
current Ubuntu releases is libgutenprint.so.3).

This was discussed in Ask Ubuntu chat:
http://chat.stackexchange.com/rooms/201/conversation/bug-1120870

What we guess is happening is that when a new Ubuntu release appears,
binary packages with no source changes are copied unmodified into the
newer Ubuntu repository. It apparently does not check that the package
still works, or specifically that needed shared libraries still exist.
What should happen is that the package gets rebuilt when needed (simply
rebuilding the package gets it to work again:
http://chat.stackexchange.com/transcript/message/8047931#8047931).

** Affects: launchpad
     Importance: Undecided
         Status: New

** Affects: ubuntu
     Importance: Undecided
         Status: New


** Tags: metabug packaging regression-release

** Description changed:

  There is an issue where old package versions are getting released for
  newer Ubuntu releases without properly updating the shared-library
  references. This causes regressions where a package that worked in
  previous versions starts to fail with an error like:
  
  photoprint: error while loading shared libraries: libgutenprint.so.2:
  cannot open shared object file: No such file or directory
  
  The underlying issue seems to cause reappearing bugs like bug #260849,
  where the photoprint package refers to libgutenprint.so.2 (the file in
  current Ubuntu releases is libgutenprint.so.3).
  
- This was discussed in Ask Ubuntu chat, starting at:
- http://chat.stackexchange.com/transcript/message/8047662#8047662
+ This was discussed in Ask Ubuntu chat:
+ http://chat.stackexchange.com/rooms/201/conversation/bug-1120870
  
- What we think is happening is that when a new Ubuntu release appears,
+ What we guess is happening is that when a new Ubuntu release appears,
  binary packages with no source changes are copied unmodified into the
  newer Ubuntu repository. It apparently does not check that the package
  still works, or specifically that needed shared libraries still exist.
  What should happen is that the package gets rebuilt when needed (simply
  rebuilding the package gets it to work again:
  http://chat.stackexchange.com/transcript/message/8047931#8047931).

** Also affects: launchpad
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1120870

Title:
  Bit rot breaking shared library references in packages not rebuilt in
  new Ubuntu releases

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1120870/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to