| Summary: | repoman : '--include-arches' feature request | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Agostino Sarubbo <ago> |
| Component: | Repoman | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | Keywords: | InVCS |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 468524 | ||
| Attachments: | poc | ||
This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=9f14442ada82b5a076b1ea0093f0e9f133c10b47 This is fixed in 2.1.11.63 and 2.2.0_alpha174. |
Created attachment 345704 [details] poc This was already discussed on irc with Zac, here is the summary. When I/someone try to commit a package, sometimes there are repoman complains (mostly dependency.bad) that cause failures. In the most of the cases, if we are talking about a stabilization, the complain does not regard the arch in question, so is a pita get a failure every time and/or retry with --force. So, for example, if I'm committing for arm, have anything like: repoman commit --include-arches arm -m "Stable for arm" will catch only the problem that regards arm. Why --ignore-arches is not fine in this case: man repoman says: -i, --ignore-arches - Ignore arch-specific failures (where arch != host) Obviously I have not a gentoo-x86 repository for each machine/chroot, so if, for example, I'm doing the commit from an x86_64 machine and I'm trying to stabilize for x86, this option is not valid. Attached an example.