| Summary: | app-portage/gemato: keywordreq | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Michał Górny <mgorny> |
| Component: | Keywording | Assignee: | Michał Górny <mgorny> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | dev-portage, prefix |
| Priority: | Normal | Flags: | nattka:
sanity-check-
|
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: |
app-portage/gemato-12.0
dev-python/bz2file-0.98
dev-python/backports-lzma-0.0.10
sys-apps/portage-2.3.24-r1
|
Runtime testing required: | No |
| Bug Depends on: | 634818, 634936 | ||
| Bug Blocks: | |||
|
Description
Michał Górny
2017-11-25 10:01:04 UTC
Target keywords: everywhere where Portage runs. An automated check of this bug failed - repoman reported dependency errors (51 lines truncated):
> dependency.bad app-portage/gemato/gemato-4.ebuild: DEPEND: ~alpha(default/linux/alpha/13.0) ['dev-python/bz2file[python_targets_python2_7(-)?,-python_single_target_python2_7(-)]', 'dev-python/backports-lzma[python_targets_python2_7(-)?,-python_single_target_python2_7(-)]']
> dependency.bad app-portage/gemato/gemato-4.ebuild: RDEPEND: ~alpha(default/linux/alpha/13.0) ['dev-python/bz2file[python_targets_python2_7(-)?,-python_single_target_python2_7(-)]', 'dev-python/backports-lzma[python_targets_python2_7(-)?,-python_single_target_python2_7(-)]']
> dependency.bad app-portage/gemato/gemato-4.ebuild: DEPEND: ~alpha(default/linux/alpha/13.0/desktop) ['dev-python/bz2file[python_targets_python2_7(-)?,-python_single_target_python2_7(-)]', 'dev-python/backports-lzma[python_targets_python2_7(-)?,-python_single_target_python2_7(-)]']
As for the two dependencies, feel free to either keyword them or mask USE={bzip2,lzma} on gemato.
An automated check of this bug failed - repoman reported dependency errors (1 lines truncated):
> dependency.bad app-portage/gemato/gemato-4.ebuild: DEPEND: ~arm(default/linux/arm/13.0) ['dev-python/pysha3[python_targets_python2_7(-)?,-python_single_target_python2_7(-),python_targets_python3_4(-)?,-python_single_target_python3_4(-),python_targets_python3_5(-)?,-python_single_target_python3_5(-)]']
> dependency.bad app-portage/gemato/gemato-4.ebuild: RDEPEND: ~arm(default/linux/arm/13.0) ['dev-python/pysha3[python_targets_python2_7(-)?,-python_single_target_python2_7(-),python_targets_python3_4(-)?,-python_single_target_python3_4(-),python_targets_python3_5(-)?,-python_single_target_python3_5(-)]']
> dependency.bad app-portage/gemato/gemato-4.ebuild: DEPEND: ~hppa(default/linux/hppa/13.0) ['dev-python/pysha3[python_targets_python2_7(-)?,-python_single_target_python2_7(-),python_targets_python3_4(-)?,-python_single_target_python3_4(-),python_targets_python3_5(-)?,-python_single_target_python3_5(-)]']
is this going to be a portage/repoman dependency? Most likely yes, since it provides very flexible API for partial verification. An automated check of this bug succeeded - the previous repoman errors are now resolved. ~ppc/~ppc64 keyworded ~ia64 keyworded ~sparc keyworded (thanks to Rolf Eike Beer) ~hppa keyworded ~arm64 added ~arm added (included portage 2.3.21) An automated check of this bug failed - the following atoms are unknown: sys-apps/portage-2.3.21 app-portage/gemato-10.3 Please verify the atom list. An automated check of this bug failed - repoman reported dependency errors: I want to add ~mips, but repoman has issues: RepoMan scours the neighborhood... metadata.bad [fatal] 1 app-portage/gemato/metadata.xml: unused local USE-description: 'portage-postsync' I thought the USE flag to control this was 'rsync-verify', except that flag isn't defined in metadata.xml. I have that USE disabled on my x86_64 for expediency at the moment, but it apparently still tried to run a verify and threw a traceback when it couldn't find gemato. So which USE is the correct USE to control the use of gemato? The NEWS blurb suggests I will want to disable this on my MIPS machines due to slow I/O. (In reply to Joshua Kinard from comment #17) > I want to add ~mips, but repoman has issues: > RepoMan scours the neighborhood... > metadata.bad [fatal] 1 > app-portage/gemato/metadata.xml: unused local USE-description: > 'portage-postsync' Fixed. > > I thought the USE flag to control this was 'rsync-verify', except that flag > isn't defined in metadata.xml. I have that USE disabled on my x86_64 for > expediency at the moment, but it apparently still tried to run a verify and > threw a traceback when it couldn't find gemato. So which USE is the correct > USE to control the use of gemato? The NEWS blurb suggests I will want to > disable this on my MIPS machines due to slow I/O. It's on sys-apps/portage. (In reply to Michał Górny from comment #18) > (In reply to Joshua Kinard from comment #17) > > I want to add ~mips, but repoman has issues: > > RepoMan scours the neighborhood... > > metadata.bad [fatal] 1 > > app-portage/gemato/metadata.xml: unused local USE-description: > > 'portage-postsync' > > Fixed. > > > > > I thought the USE flag to control this was 'rsync-verify', except that flag > > isn't defined in metadata.xml. I have that USE disabled on my x86_64 for > > expediency at the moment, but it apparently still tried to run a verify and > > threw a traceback when it couldn't find gemato. So which USE is the correct > > USE to control the use of gemato? The NEWS blurb suggests I will want to > > disable this on my MIPS machines due to slow I/O. > > It's on sys-apps/portage. ~mips is added to gemato, bz2file, and backports-lzma. I haven't tested gemato yet on one of my MIPS systems. Should be interesting to time the I/O on slower hardware. An automated check of this bug succeeded - the previous repoman errors are now resolved. ~x64-cygwin keyworded, though not a portage dep in Prefix yet. ~amd64-fbsd done The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2434e14beeba9febfd2e2aab00e276376f715792 commit 2434e14beeba9febfd2e2aab00e276376f715792 Author: Mart Raudsepp <leio@gentoo.org> AuthorDate: 2018-03-06 13:11:03 +0000 Commit: Mart Raudsepp <leio@gentoo.org> CommitDate: 2018-03-06 18:12:19 +0000 sys-apps/portage-2.3.24-r1: re-add ~arm64 Keyword was removed without a re-keywording bug. Or more exactly, it was added to package list after the previous package list was already done, and a re-CC was forgotten. Bug: https://bugs.gentoo.org/638776 Package-Manager: Portage-2.3.19, Repoman-2.3.6 sys-apps/portage/portage-2.3.24-r1.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)} added ~alpha What to do when the verification falls over on the checking of the cert's. In my case I now do not get a sync completed,please reset back to prior system,until this gemato thingy is actually working,or dump the idea. A frustrated user. (In reply to Geoff Madden from comment #25) > What to do when the verification falls over on the checking of the cert's. > In my case I now do not get a sync completed,please reset back to prior > system, In the future there will be one or more of these options available: 1) on-demand verification 2) rollback 2) repository quarantine > until this gemato thingy is actually working,or dump the idea. > A frustrated user. If you're experiencing bug 647696 or bug 648586, then please leave a comment there if you have some information to add. If your issue different from those, then please file a new bug and make it block bug 650144. Note that portage-2.3.28 has retry support for the key refresh, see bug 649276. s390 was done ~m68k and ~sh done *-fbsd is gone. Unable to check for sanity:
> no match for package: app-portage/gemato-12.0
Unable to check for sanity:
> no match for package: dev-python/pysha3-1.0.2
|