Summary: | guile-gtk crash when trying to install gwave package | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jordi Alcántara <jordi.alcantara> |
Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | agriffis |
Priority: | High | ||
Version: | 2005.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 107840 | ||
Bug Blocks: |
Description
Jordi Alcántara
2005-06-11 02:47:38 UTC
No metadata.xml, this package needs a maitainer... Can you test if the same occurs with =1.2.0.41? Just bumped it in the tree. ACCEPT_KEYWORDS="~x86" emerge =guile-gtk-1.2.0.41 whith ACCEPT_KEYWORDS="~x86" emerge =guile-gtk-1.2.0.41 compiles cleanly Mass reassign of bugs on orphaned packages to appropriate assignee. Works for me, as comment #3. Is there any good reason to keep a broken version as "stable" and a workable one as "unstable"? Rick: This is a valid question. As a policy, we keep ebuild versions in the testing branch for about a month to ensure they are not broken. Please consider that the current stable version may be broken only for one specific application (the one you are interested in), while the testing version might be a lot more broken (we do not know until it is tested for some time). Therefore, we do not rush versions into the stable branch simply because they fix one bug; we wait some time to allow testing to make sure the new version does work correctly. guile-gtk has now been bumped to stable on x86. Other arches are to follow. This should solve your problem. |