First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 183919
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Python Gentoo Team <python@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: William L. Thomson Jr. (RETIRED) <wltjr@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 183919 depends on: Show dependency tree
Bug 183919 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-07-02 02:37 0000
I broke kinterbasedb 3.1 by updating Firebird and removing the previous version
that was stable. Although same version remains in ~arch. The newer version in
the same slot is stable now. I tried lessening the deps of 3.1, but it would
not compile. There were some other QA is general issues with 3.2 that Ali
Polatel (hawking) addressed. Many thanks there for the help.

Beyond that 3.2 is almost a year old now, an 3.1 is even older than that. Being
as how Firebird < 2.x has a security issue, and 3.1 fails to compile against
>=2.x. I think we have adequate justification for a rush stabilization of 3.2.
It's been in tree for a long time now, before current modifications. Should not
introduce more breakage than there is now, and once stabilized 3.1 can be
removed.

Very sorry for the breakage. Firebird stuff is all kinda a mess and trying to
clean it up. Starting with Firebird itself, and trickling down to stuff like
this accidentally broken. :)

------- Comment #1 From Christian Faulhammer 2007-07-02 23:36:14 0000 -------
x86 stable and closing

First Last Prev Next    No search results available      Search page      Enter new bug