Status report?
What's left to do before the next version of glibc can be uploaded?
I ask for the obvious reason (it's preventing migration of, um, everything
into etch), and because it's not obvious what needs to be done.
Of the RC bugs:
#181494 is pre-existing
#324455: fix appears to be in the repo and ready to upload
#324450: fix appears to be in the repo and ready to upload
#317082 is "moreinfo". Has a decision been made on how to fix this?
If not, frankly it should be downgraded to "important", because it only
hurts biarch -- meaning it isn't actually a blocker for any single
subarchitecture -- and that's not nearly as bad as holding up
every package on every single arch.
Is there a problem which is not listed in the RC bugs?
--
Nathanael Nerode <neroden@twcny.rr.com>
[Insert famous quote here]
Reply to: