Summary: | app-misc/tpconfig-3.1.3-r2 stable request | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pacho Ramos <pacho> |
Component: | Stabilization | 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 WONTFIX | ||
Severity: | normal | Keywords: | STABLEREQ |
Priority: | Normal | Flags: | stable-bot:
sanity-check+
|
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: |
app-misc/tpconfig-3.1.3-r2
|
Runtime testing required: | --- |
Description
Pacho Ramos
2019-01-27 10:03:21 UTC
does not make sense is not even stable on amd64 Do you refer that changes are too few to be stabilized? In that case, should we simply mark the ebuild stable to remove the newer revision and copy it to the current -r1? I mean, to keep only one ebuild we could: 1. Copy -r2 to -r1 (and also stabilize on amd64 finally). 2. Simply stabilize -r2 (without even involving x86 as it will work still) I will also look into updating EAPI by the way |