| Summary: | dev-haskell/pandoc-citeproc-0.3.1 stabilization request | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Andrew Savchenko <bircoph> |
| Component: | [OLD] Keywording and Stabilization | Assignee: | Gentoo's Haskell Language team <haskell> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | pacho |
| Priority: | Normal | Keywords: | STABLEREQ |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 550390, 550392, 550420 | ||
| Bug Blocks: | 546258 | ||
|
Description
Andrew Savchenko
2015-04-11 10:49:29 UTC
@haskell, ping here I'll have to select version, and file stabilization request for dependencies myself in few weeks if no action from your side. (In reply to Andrew Savchenko from comment #1) > @haskell, ping here > > I'll have to select version, and file stabilization request for dependencies > myself in few weeks if no action from your side. I would go ahead ;) OK, I waited long enough indeed. I just CC'ed arches on stabilization requests for the leafs of the dependency tree. OK, thanks. Also, to save time you can CC arches in all parent bugs as soon as all of them have the needed arches CCed ;) It's only a suggestion of course :) Hm, I always though it is forbidden to CC arches on packages with not all dependencies stabilized. It was somewhere on the quizzes. https://devmanual.gentoo.org/keywording/index.html ``The package must not have any non-arch dependencies.'' Looks like manual should be updated (or maybe I'm misunderstanding something). But you can CC them if the arches are already CCed in needed bugs and, then, arch teams can go through all the dep tree and stabilize in order. Otherwise you will be blocked by last arch on every step (and that can take *months* per step as some arches take really a long time to do it) @Pacho OK, thanks for explanation. Arch teams, please stabilize =dev-haskell/pandoc-citeproc-0.3.1. amd64 stable x86 stable |
