Mantis - libmysqlclient15
Viewing Issue Advanced Details
4120 packaging major always 2010-01-07 23:47 2011-08-29 17:49
maciej  
maciej  
normal  
closed  
fixed  
none    
none  
0004120: libmysqlclient_r.so.15 missing
ld.so.1: bacula-dir: fatal: libmysqlclient_r.so.15: open failed: No such file or directory
Issue History
2010-01-07 23:47 maciej New Issue
2010-01-10 11:05 maciej Note Added: 0007201
2010-01-10 11:05 maciej Assigned To => maciej
2010-01-10 11:05 maciej Status new => feedback
2010-01-11 16:48 maciej Note Added: 0007209
2010-01-12 18:31 maciej Note Added: 0007211
2010-01-12 18:31 maciej Status feedback => assigned
2010-02-17 10:04 maciej Note Added: 0007459
2011-08-29 17:48 maciej Note Added: 0009246
2011-08-29 17:49 maciej Status assigned => closed
2011-08-29 17:49 maciej Resolution open => fixed

Notes
(0007201)
maciej   
2010-01-10 11:05   
Updated packages are in testing.

http://mirror.opencsw.org/testing.html [^]
(0007209)
maciej   
2010-01-11 16:48   
I haven't got a response from the original issue reporter, but I've smoke-tested the updated packages myself. They have been sent for release.

* mysql5client: revision upgrade
 - from: 2009.12.22
 - to: 2010.01.08
 + mysql5client-5.0.87,REV=2010.01.08-SunOS5.8-i386-CSW.pkg.gz
 + mysql5client-5.0.87,REV=2010.01.08-SunOS5.8-sparc-CSW.pkg.gz
* mysql5: revision upgrade
 - from: 2010.01.03
 - to: 2010.01.08
 + mysql5rt-5.0.87,REV=2010.01.08-SunOS5.8-i386-CSW.pkg.gz
 + mysql5rt-5.0.87,REV=2010.01.08-SunOS5.8-sparc-CSW.pkg.gz
 + mysql5-5.0.87,REV=2010.01.08-SunOS5.8-i386-CSW.pkg.gz
 + mysql5-5.0.87,REV=2010.01.08-SunOS5.8-sparc-CSW.pkg.gz
(0007211)
maciej   
2010-01-12 18:31   
The updated package has been released. I'll keep this issue open until I implement a unit test to catch this problem in the future.
(0007459)
maciej   
2010-02-17 10:04   
http://sourceforge.net/apps/trac/gar/ticket/18 [^] is a ticket on which this bug depends: once there are assertions, I'll add an assertion about libmysqlclient_r.so.15
(0009246)
maciej   
2011-08-29 17:48   
The new shared library packaging scheme will detect this issue if it ever occurs in the future. If a shared library went missing, there would be a suddenly empty package which would trigger a checkpkg error.