| 2013-02-10 05:07:09 |
Mechanical snail |
bug |
|
|
added bug |
| 2013-02-10 05:08:06 |
Mechanical snail |
description |
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
What we think 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). |
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). |
|
| 2013-02-10 05:10:25 |
Mechanical snail |
bug task added |
|
launchpad |
|
| 2013-02-10 05:16:20 |
Launchpad Janitor |
ubuntu: status |
New |
Confirmed |
|
| 2013-02-10 05:23:44 |
Andrew King |
bug |
|
|
added subscriber Andrew King |
| 2013-02-10 16:28:54 |
J Phani Mahesh |
bug |
|
|
added subscriber J Phani Mahesh |
| 2013-02-11 07:40:37 |
William Grant |
ubuntu: status |
Confirmed |
Invalid |
|
| 2013-02-11 07:40:40 |
William Grant |
launchpad: status |
New |
Invalid |
|
| 2013-02-15 05:45:34 |
Mechanical snail |
description |
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). |
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, http://chat.stackexchange.com/rooms/201/conversation/more-bug-discussion
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). |
|
