FS#4880 - Sylpheed v2.2.4 broken after upgrade to current

Attached to Project: Arch Linux
Opened by Anonymous Submitter - Monday, 26 June 2006, 22:10 GMT
Last edited by Tobias Kieslich (tobias) - Tuesday, 27 June 2006, 14:13 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To dorphell (dorphell)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Overnight upgraded to the recent "testing" version of current. Sylpheed is now not working. If I run it at a command line, I get the following error message :

$ sylpheed
sylpheed: error while loading shared libraries: libssl.so.0.9.7: cannot open shared object file: No such file or directory

It seems that Sylpheed hasn't been upgraded to use the newer version of openssl.

Here is the package version I have installed :

$ pacman -Q -s sylpheed
local/sylpheed 2.2.4-2
A GTK+ based, lightweight, and fast email client

I've marked it as a critical as sylpheed is now broken, which seems to me to be a critical error for the package.
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 28 June 2006, 18:31 GMT
Reason for closing:  Fixed
Comment by Igor (furester) - Tuesday, 27 June 2006, 06:54 GMT
the same aerror appears to cause the same problem to other packages like e17genmenu
Comment by arjan timmerman (blaasvis) - Tuesday, 27 June 2006, 08:50 GMT
why do you think this is critical?
i won't mess up you system or data.
Comment by Anonymous Submitter - Tuesday, 27 June 2006, 09:10 GMT
"why do you think this is critical?
i won't mess up you system or data"

Sure it won't mess up my data, but when I can't run the application that allows me to see my data (in this case my emails), my system less less to me, which "messes" up using it to read email :-) My system is less useful to me today than it was yesterday, and all I did was a simple package upgrade.

It would seem to me that the definition of the word critical is "won't work at all", and there isn't any easy work around. I think that is what has happened here. It's a "show stopper" type bug for the package.
Comment by arjan timmerman (blaasvis) - Tuesday, 27 June 2006, 10:16 GMT
yeah it is a showstopper, so it is something severity high and probably priority high but not critical.
Comment by Anonymous Submitter - Tuesday, 27 June 2006, 20:44 GMT
'yeah it is a showstopper, so it is something severity high and probably priority high but not critical.'

It's occured to me that the bug is critical or severity high depends on your point of view. When I'm filling out the bug report, I'm thinking about the specific package I've found a bug in, and if the package itself doesn't work at all, then it is a critical bug (to the package), which is why I marked it critical. OTOH, I can see that if you guys are dealing with all the bug reports at a higher level, which I suppose would mean that you're looking at the bug's impact to the "system" overall, then it isn't a critical bug, but it is a high severity one.

I don't know if it is worth worrying about, however maybe there would be a way or some value in somehow reflecting this difference in point of view e.g. somehow separate and record the severity level to the package from the severity to the system. It would be useful for me to still see my bug report listed as critical, yet not have people concerned that there is a system wide impact because it is marked critical from their point of view.

Loading...