288401 – www-client/seamonkey-2.0_beta2: dependency for sqlite not up-to-date

Bug 288401 - www-client/seamonkey-2.0_beta2: dependency for sqlite not up-to-date

Summary: www-client/seamonkey-2.0_beta2: dependency for sqlite not up-to-date

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Mozilla Gentoo Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2009-10-10 09:35 UTC by Arend Freije
Modified:	2009-10-12 05:15 UTC (History)
CC List:	0 users

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

Attachments
The log file of the configuration step (config.log,35.45 KB, text/plain) 2009-10-10 09:36 UTC, Arend Freije	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Arend Freije 2009-10-10 09:35:10 UTC

While trying to emerge the new seamonkey beta2, the configuration failed.
                                                                                                             

Reproducible: Always

Steps to Reproduce:
1. emerge sqlite 3.6.6.2 (was installed as dependency for another package)
2. emerge =www-client/seamonkey-2.0_beta2

Actual Results:  
checking for sqlite3 >= 3.6.10... Requested 'sqlite3 >= 3.6.10' but version of SQLite is 3.6.6.2                                                               
configure: error: Library requirements (sqlite3 >= 3.6.10) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them.       


Expected Results:  
Before seamonkey is compiled, sqlite should have been upgraded to 3.6.10 or better.

Workaround: upgrade sqlite manually

Comment 1 Arend Freije 2009-10-10 09:36:08 UTC

Created attachment 206632 [details]
The log file of the configuration step

Comment 2 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev

2009-10-12 05:15:28 UTC

This bug was fixed while bumping seamonkey to version 2.0_rc1. Thanks for reporting :)