* [gentoo-guru] Dev branch failing pkgcheck scan
@ 2022-04-15 13:06 Philippe Chaintreuil
2022-04-15 13:22 ` [gentoo-guru] " 1over137
0 siblings, 1 reply; 4+ messages in thread
From: Philippe Chaintreuil @ 2022-04-15 13:06 UTC (permalink / raw
To: gentoo-guru, Shaoyu Tseng
I'm getting an exception out of pkgcheck scan this morning.
What's our protocol for issues like this? Rollback the change
immediately? Or reach out and see if the commiter can fix it?
============================================================================
peep@kant ~/git/guru $ pkgcheck scan --net
pkgcheck scan: error: Traceback (most recent call last):
File "/usr/lib/python3.9/site-packages/pkgcore/ebuild/atom.py", line
261, in __init__
sf(self, "_cpv", cpv.CPV(self.cpvstr, versioned=bool(self.op)))
File "/usr/lib/python3.9/site-packages/pkgcore/ebuild/cpv.py", line
317, in __init__
raise InvalidCPV(cpvstr, f"invalid version '{pkg_chunks[-1]}'")
pkgcore.ebuild.errors.InvalidCPV: app-misc/vocabsieve-.4: invalid
version '.4'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/lib/python3.9/site-packages/pkgcheck/pipeline.py", line
227, in _run
self._queue_work(sync_pipes, work_q)
File "/usr/lib/python3.9/site-packages/pkgcheck/pipeline.py", line
172, in _queue_work
for restrict in unversioned_source.itermatch(restriction):
File "/usr/lib/python3.9/site-packages/pkgcheck/sources.py", line
378, in itermatch
for pkg in super().itermatch(restrict, **kwargs):
File "/usr/lib/python3.9/site-packages/pkgcheck/sources.py", line
247, in itermatch
yield from super().itermatch(restrict, raw_pkg_cls=RawCPV, **kwargs)
File
"/usr/lib/python3.9/site-packages/pkgcore/repository/prototype.py", line
298, in _internal_match
for pkg in self._internal_gen_candidates(candidates, **kwargs):
File
"/usr/lib/python3.9/site-packages/pkgcore/repository/prototype.py", line
295, in _internal_gen_candidates
yield from sorter(pkg_filter(pkgs))
File "/usr/lib/python3.9/site-packages/pkgcheck/packages.py", line
41, in __lt__
return self.versioned_atom < other.versioned_atom
File "/usr/lib/python3.9/site-packages/pkgcheck/packages.py", line
33, in versioned_atom
return atom.atom(f'={self}')
File "/usr/lib/python3.9/site-packages/snakeoil/caching.py", line
115, in __call__
instance = super(WeakInstMeta, cls).__call__(*a, **kw)
File "/usr/lib/python3.9/site-packages/pkgcore/ebuild/atom.py", line
263, in __init__
raise errors.MalformedAtom(orig_atom) from e
pkgcore.ebuild.errors.MalformedAtom: invalid package atom:
'=app-misc/vocabsieve-.4'
Sandboxed process killed by signal: Broken pipe
Sandboxed process killed by signal: Broken pipe
Sandboxed process killed by signal: Broken pipe
============================================================================
My git bisect say this is the first bad commit:
============================================================================
318009746930e0b83ed39e6b74968f2a44720b1c is the first bad commit
commit 318009746930e0b83ed39e6b74968f2a44720b1c
Author: Shaoyu Tseng <1over137@anche.no>
Date: Fri Apr 15 06:25:21 2022 -0400
app-misc/vocabsieve: move from app-misc/ssmtool
Signed-off-by: Shaoyu Tseng <1over137@anche.no>
app-misc/ssmtool/Manifest | 1 -
app-misc/ssmtool/metadata.xml | 12 ----------
app-misc/ssmtool/ssmtool-0.6.4.ebuild | 35
----------------------------
app-misc/vocabsieve/Manifest | 1 +
app-misc/vocabsieve/metadata.xml | 12 ++++++++++
app-misc/vocabsieve/ssmtool-0.6.4.ebuild | 35
++++++++++++++++++++++++++++
app-misc/vocabsieve/vocabsieve-0.7.0.ebuild | 36
+++++++++++++++++++++++++++++
profiles/updates/2Q-2022 | 1 +
8 files changed, 85 insertions(+), 48 deletions(-)
delete mode 100644 app-misc/ssmtool/Manifest
delete mode 100644 app-misc/ssmtool/metadata.xml
delete mode 100644 app-misc/ssmtool/ssmtool-0.6.4.ebuild
create mode 100644 app-misc/vocabsieve/Manifest
create mode 100644 app-misc/vocabsieve/metadata.xml
create mode 100644 app-misc/vocabsieve/ssmtool-0.6.4.ebuild
create mode 100644 app-misc/vocabsieve/vocabsieve-0.7.0.ebuild
create mode 100644 profiles/updates/2Q-2022
============================================================================
For ease of reference:
https://github.com/gentoo/guru/commit/318009746930e0b83ed39e6b74968f2a44720b1c
Thanks.
-- Philippe Chaintreuil
^ permalink raw reply [flat|nested] 4+ messages in thread
* [gentoo-guru] Re: Dev branch failing pkgcheck scan
2022-04-15 13:06 [gentoo-guru] Dev branch failing pkgcheck scan Philippe Chaintreuil
@ 2022-04-15 13:22 ` 1over137
2022-04-15 13:28 ` Philippe Chaintreuil
0 siblings, 1 reply; 4+ messages in thread
From: 1over137 @ 2022-04-15 13:22 UTC (permalink / raw
To: Philippe Chaintreuil, gentoo-guru
Sorry, I think I failed to remove the old ebuild, causing this error.
Simply removing the old ebuild in the folder (ssmtool-0.6.4.ebuild)
would fix it. How do I fix it? Do I simply make a new commit?
Shaoyu Tseng
On Fri, 2022-04-15 at 09:06 -0400, Philippe Chaintreuil wrote:
> I'm getting an exception out of pkgcheck scan this morning.
>
> What's our protocol for issues like this? Rollback the change
> immediately? Or reach out and see if the commiter can fix it?
>
> =====================================================================
> =======
> peep@kant ~/git/guru $ pkgcheck scan --net
> pkgcheck scan: error: Traceback (most recent call last):
> File "/usr/lib/python3.9/site-packages/pkgcore/ebuild/atom.py",
> line
> 261, in __init__
> sf(self, "_cpv", cpv.CPV(self.cpvstr, versioned=bool(self.op)))
> File "/usr/lib/python3.9/site-packages/pkgcore/ebuild/cpv.py",
> line
> 317, in __init__
> raise InvalidCPV(cpvstr, f"invalid version '{pkg_chunks[-1]}'")
> pkgcore.ebuild.errors.InvalidCPV: app-misc/vocabsieve-.4: invalid
> version '.4'
>
> The above exception was the direct cause of the following exception:
>
> Traceback (most recent call last):
> File "/usr/lib/python3.9/site-packages/pkgcheck/pipeline.py", line
> 227, in _run
> self._queue_work(sync_pipes, work_q)
> File "/usr/lib/python3.9/site-packages/pkgcheck/pipeline.py", line
> 172, in _queue_work
> for restrict in unversioned_source.itermatch(restriction):
> File "/usr/lib/python3.9/site-packages/pkgcheck/sources.py", line
> 378, in itermatch
> for pkg in super().itermatch(restrict, **kwargs):
> File "/usr/lib/python3.9/site-packages/pkgcheck/sources.py", line
> 247, in itermatch
> yield from super().itermatch(restrict, raw_pkg_cls=RawCPV,
> **kwargs)
> File
> "/usr/lib/python3.9/site-packages/pkgcore/repository/prototype.py",
> line
> 298, in _internal_match
> for pkg in self._internal_gen_candidates(candidates, **kwargs):
> File
> "/usr/lib/python3.9/site-packages/pkgcore/repository/prototype.py",
> line
> 295, in _internal_gen_candidates
> yield from sorter(pkg_filter(pkgs))
> File "/usr/lib/python3.9/site-packages/pkgcheck/packages.py", line
> 41, in __lt__
> return self.versioned_atom < other.versioned_atom
> File "/usr/lib/python3.9/site-packages/pkgcheck/packages.py", line
> 33, in versioned_atom
> return atom.atom(f'={self}')
> File "/usr/lib/python3.9/site-packages/snakeoil/caching.py", line
> 115, in __call__
> instance = super(WeakInstMeta, cls).__call__(*a, **kw)
> File "/usr/lib/python3.9/site-packages/pkgcore/ebuild/atom.py",
> line
> 263, in __init__
> raise errors.MalformedAtom(orig_atom) from e
> pkgcore.ebuild.errors.MalformedAtom: invalid package atom:
> '=app-misc/vocabsieve-.4'
> Sandboxed process killed by signal: Broken pipe
> Sandboxed process killed by signal: Broken pipe
> Sandboxed process killed by signal: Broken pipe
> =====================================================================
> =======
>
> My git bisect say this is the first bad commit:
>
> =====================================================================
> =======
> 318009746930e0b83ed39e6b74968f2a44720b1c is the first bad commit
> commit 318009746930e0b83ed39e6b74968f2a44720b1c
> Author: Shaoyu Tseng <1over137@anche.no>
> Date: Fri Apr 15 06:25:21 2022 -0400
>
> app-misc/vocabsieve: move from app-misc/ssmtool
>
> Signed-off-by: Shaoyu Tseng <1over137@anche.no>
>
> app-misc/ssmtool/Manifest | 1 -
> app-misc/ssmtool/metadata.xml | 12 ----------
> app-misc/ssmtool/ssmtool-0.6.4.ebuild | 35
> ----------------------------
> app-misc/vocabsieve/Manifest | 1 +
> app-misc/vocabsieve/metadata.xml | 12 ++++++++++
> app-misc/vocabsieve/ssmtool-0.6.4.ebuild | 35
> ++++++++++++++++++++++++++++
> app-misc/vocabsieve/vocabsieve-0.7.0.ebuild | 36
> +++++++++++++++++++++++++++++
> profiles/updates/2Q-2022 | 1 +
> 8 files changed, 85 insertions(+), 48 deletions(-)
> delete mode 100644 app-misc/ssmtool/Manifest
> delete mode 100644 app-misc/ssmtool/metadata.xml
> delete mode 100644 app-misc/ssmtool/ssmtool-0.6.4.ebuild
> create mode 100644 app-misc/vocabsieve/Manifest
> create mode 100644 app-misc/vocabsieve/metadata.xml
> create mode 100644 app-misc/vocabsieve/ssmtool-0.6.4.ebuild
> create mode 100644 app-misc/vocabsieve/vocabsieve-0.7.0.ebuild
> create mode 100644 profiles/updates/2Q-2022
> =====================================================================
> =======
>
> For ease of reference:
> https://github.com/gentoo/guru/commit/318009746930e0b83ed39e6b74968f2a44720b1c
>
> Thanks.
>
> -- Philippe Chaintreuil
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-guru] Re: Dev branch failing pkgcheck scan
2022-04-15 13:22 ` [gentoo-guru] " 1over137
@ 2022-04-15 13:28 ` Philippe Chaintreuil
2022-04-15 14:21 ` Andrew Ammerlaan
0 siblings, 1 reply; 4+ messages in thread
From: Philippe Chaintreuil @ 2022-04-15 13:28 UTC (permalink / raw
To: gentoo-guru, 1over137
On 4/15/2022 9:22 AM, 1over137 wrote:
> Sorry, I think I failed to remove the old ebuild, causing this error.
> Simply removing the old ebuild in the folder (ssmtool-0.6.4.ebuild)
> would fix it. How do I fix it? Do I simply make a new commit?
I can confirm, deleting app-misc/vocabsieve/ssmtool-0.6.4.ebuild makes
pkgcheck happy.
I'm new here, so I'm not authoritative by any stretch of the
imagination, but I'd say just submit a new commit that removes the file.
Thanks for the quick response!
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-guru] Re: Dev branch failing pkgcheck scan
2022-04-15 13:28 ` Philippe Chaintreuil
@ 2022-04-15 14:21 ` Andrew Ammerlaan
0 siblings, 0 replies; 4+ messages in thread
From: Andrew Ammerlaan @ 2022-04-15 14:21 UTC (permalink / raw
To: gentoo-guru
On 15/04/2022 15:28, Philippe Chaintreuil wrote:
> On 4/15/2022 9:22 AM, 1over137 wrote:
>> Sorry, I think I failed to remove the old ebuild, causing this error.
>> Simply removing the old ebuild in the folder (ssmtool-0.6.4.ebuild)
>> would fix it. How do I fix it? Do I simply make a new commit?
>
> I can confirm, deleting app-misc/vocabsieve/ssmtool-0.6.4.ebuild makes
> pkgcheck happy.
>
> I'm new here, so I'm not authoritative by any stretch of the
> imagination, but I'd say just submit a new commit that removes the file.
Yes this would indeed be the best approach
>
> Thanks for the quick response!
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2024-11-24 22:47 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-04-15 13:06 [gentoo-guru] Dev branch failing pkgcheck scan Philippe Chaintreuil
2022-04-15 13:22 ` [gentoo-guru] " 1over137
2022-04-15 13:28 ` Philippe Chaintreuil
2022-04-15 14:21 ` Andrew Ammerlaan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox