Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 156885 - Firebird 1.5.3 is considered unsafe on AMD64 by upstream
Summary: Firebird 1.5.3 is considered unsafe on AMD64 by upstream
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: AMD64 Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-02 02:28 UTC by Michael Weissenbacher
Modified: 2007-02-10 01:16 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Weissenbacher 2006-12-02 02:28:55 UTC
The subject says it all. Upstream developers suggest to switch to 2.0 on AMD64 because 1.5.x has unsolved bugs on AMD64. Has the gentoo team made special patches for it or was is marked stable by mistake?

Quoting a mail to firebird-devel from Dmitry Yemanov <dimitr@users.sourceforge.net> 2006-07-17 15:54:
64-bit builds of v1.5 are not recommended for production use. There are 
known bugs there.
Comment 1 Simon Stelling (RETIRED) gentoo-dev 2007-02-02 14:12:43 UTC
It was marked stable because we didn't find any problems during testing, but if upstream says it's better not to use it, this belongs into testing. Also, the firebird USE flag is masked now.

Thanks for telling us.
Comment 2 William L. Thomson Jr. (RETIRED) gentoo-dev 2007-02-09 21:26:11 UTC
I question the upstream thread that statement came from. Since it's referring to compiling/building issues of 1.5.3. Not specific issues, vulnerabilities, or anything that would justify the un-stabilization. I have posted to upstream user ml, referencing both this bug, and the upstream ml thread that the statement came from.

I think we should have further confirmation or proof, rather than to just go on hear say. Even if it's from a dev on the project. If their are known issues, there should be some bugs documenting it. And/or if they are vulnerabilities, some sort of official announcement or warning. If there were issues with 1.5.3 on amd64, why would upstream still be shipping binaries. Without a warning saying not for production use or etc.

I believe the quoted statement was taken out of context, and we have un-stabilized a package less a valid or justifiable reason.

Granted at this time, they have released both 2.0.x and 1.5.4 so we should likely see about packaging both of those. If there were issues with 1.5.3, they likely have been addressed with 1.5.4.
Comment 3 William L. Thomson Jr. (RETIRED) gentoo-dev 2007-02-09 21:27:56 UTC
Link to upstream thread the comment came from.
https://sourceforge.net/mailarchive/message.php?msg_id=31319650

In the future if statements are to be quoted/provided. A link to where those statements/comments came from should be provided. That way one can do their own research and read the context of the quoted statement/comment. Thanks
Comment 4 Michael Weissenbacher 2007-02-10 00:38:29 UTC
Here is the link to the original message that made me suspect AMD64 builds of firebird 1.5.x:
http://tech.groups.yahoo.com/group/firebird-support/message/75550

The official solution suggested by the firebird team is to use 32-bit images on AMD64, which the gentoo AMD64 build clearly isn't.
Comment 5 Michael Weissenbacher 2007-02-10 00:41:43 UTC
Another message suggesting problems with AMD64:
http://tech.groups.yahoo.com/group/firebird-support/message/67547

Upstream DOES NOT provide 64bit binary builds of firebird 1.5.x:
http://www.firebirdsql.org/index.php?op=files&id=engine_154