Summary: | dev-libs/libffi-3.4.2-r1, dev-libs/libffi-compat-3.3-r2: stabilisation | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sam James <sam> |
Component: | Stabilization | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | arthurzam |
Priority: | Normal | Keywords: | CC-ARCHES |
Version: | unspecified | Flags: | nattka:
sanity-check+
|
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=801109 https://bugs.gentoo.org/show_bug.cgi?id=804660 |
||
Whiteboard: | |||
Package list: |
dev-libs/libffi-3.4.2-r1
dev-libs/libffi-compat-3.3-r2 amd64 x86
|
Runtime testing required: | --- |
Bug Depends on: | 811462 | ||
Bug Blocks: | 832824 |
Description
Sam James
2021-09-19 00:49:10 UTC
I see that the whiteboard holds "Don't proceed yet!", but this was set on 2021-09-19, meaning ~8 month ago. Currently this bug blocks not small Java stabalereq tree, so I think this bug doesn't hold low priority. I want to ask the current state of the bug. Can we have some more information, a deadline, or somwthing so we can at least know when to expect things. (In reply to Arthur Zamarin from comment #1) > I see that the whiteboard holds "Don't proceed yet!", but this was set on > 2021-09-19, meaning ~8 month ago. > > Currently this bug blocks not small Java stabalereq tree, so I think this > bug doesn't hold low priority. > > I want to ask the current state of the bug. Can we have some more > information, a deadline, or somwthing so we can at least know when to expect > things. It was/is stuck because enough people (all people, ideally) need to have completed the "failure to preserve libraries" news item steps. We could do a janky preserve step like we do in glibc for crypt, but I'm not sure. ppc done arm64 done ppc64 stable sparc done amd64 done arm done x86 done hppa done all arches done |