n3_7 (-pypy3) -python3_6 -python3_8 (-python3_9)" 0 KiB
> =====
>
> OK, so I emerged gemato, and a whole bunch of its dependencies, but
> that doesn't help...
It looks like I went about things exactly the wrong way. gemato
should not be emerged directly. USE=&qu
343.63K bytes/sec
> total size is 178.09M speedup is 3.42
> !!! Unable to verify: gemato-14.5+ is required
>
> Action: sync for repo: gentoo, returned code = 127
>
>
> [d531][root][~] emerge -pv --changed-use --deep --update @world
> * Last emerge --sync was 32d 14h 23m 2
Hello all,
I just synced my system after a long delay, and I want to emerge
firefox. I got this, first, I think, for something called gemato:
The following REQUIRED_USE flag constraints are unsatisfied:
any-of ( python_targets_python3_10 python_targets_python3_11
>=app-portage/gemato-14.5[python_targets_pypy3(-)?,python_targets_python3_10(-)?,python_targets_python3_11(-)?]"
have been masked.
!!! One of the following masked packages is required to complete your
request:
- app-portage/gemato-::gentoo (masked by: EAPI 8)
- app-portage/gemato-20.4::g
with my machine
update?
# emerge --oneshot sys-apps/portage
* IMPORTANT: 15 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
Calculating dependencies... done!
!!! All ebuilds that could satisfy
">=app-portage/gemato-14.5[python_targe
Hi Bill,
On Sat, 07 Jul 2018 07:40:00 +0800
Bill Kenworthy wrote:
I still have this error and Ive tried a number of things including:
gemato create -p ebuild -K /usr/share/openpgp-keys/gentoo-release.asc
/usr/portage/
next emerge --sync error-ed on a lot of private manifest files
ems.
>
> Calculating dependencies... done!
>
> !!! All ebuilds that could satisfy
> ">=app-portage/gemato-14.5[python_targets_pypy3(-)?,python_targets_python3_10(-)?,python_targets_python3_11(-)?]"
> have been masked.
> !!! One of the following masked packages
: No public key' error when running
rsync.
For me, using the keys from package:
app-crypt/openpgp-keys-gentoo-release-20180703 [1]
and running gemato with those:
# gemato verify -K /tmp/gentoo-release.asc.20180703 /usr/portage/
solves the issue. Afterwards I was able to update (pulls and install
On 07/07/18 09:42, Floyd Anderson wrote:
> Hi Bill,
>
> On Sat, 07 Jul 2018 07:40:00 +0800
> Bill Kenworthy wrote:
>>
>> I still have this error and Ive tried a number of things including:
>>
>> gemato create -p ebuild -K /usr/share/openpgp-keys/gentoo-rel
ingly, I already have app-crypt/openpgp-keys-gentoo-release
> > installed,
> > but still get 'gpg: Can't check signature: No public key' error when running
> > rsync.
>
> For me, using the keys from package:
>
> app-crypt/openpgp-keys-gentoo-release-20180703 [1]
>
ease-20180706
[20180703] USE="{-test%}"
[ebuild R] dev-python/setuptools-36.7.2
PYTHON_TARGETS="python3_6* -python3_5*"
[ebuild R] dev-python/certifi-2018.4.16
PYTHON_TARGETS="python3_6* -python3_5* (-python3_7)"
[ebuild U *] app-por
On 06/07/18 00:06, Floyd Anderson wrote:
> On Wed, 04 Jul 2018 22:57:05 -0400
> John Covici wrote:
>>
>> I got the following when running your command:
>> gemato verify -K /tmp/gentoo-release.asc.20180703 /usr/portage/
>> INFO:root:Refreshing keys from keyserver.
up is 3.42
!!! Unable to verify: gemato-14.5+ is required
Action: sync for repo: gentoo, returned code = 127
[d531][root][~] emerge -pv --changed-use --deep --update @world
* Last emerge --sync was 32d 14h 23m 26s ago.
These are the packages that would be merged, in order:
Calculating dependenci
It looks like we may have a "documentation bug" on our hands.
According to
https://www.gentoo.org/support/news-items/2018-01-30-portage-rsync-verification.html
> If you wish to disable it, you can disable the 'rsync-verify' USE
> flag on sys-apps/portage or set 'sync-rsync-verify-metamanifest
solution was to install app-portage/gemato-14.0. Of course, all
older versions of gemato aren't in portage anymore, so that can't be the
issue.
Does anyone have any suggestions on how to fix this issue?
Thanks in advance
Stefano
On Wed, 04 Jul 2018 22:57:05 -0400
John Covici wrote:
I got the following when running your command:
gemato verify -K /tmp/gentoo-release.asc.20180703 /usr/portage/
INFO:root:Refreshing keys from keyserver...
INFO:root:Keys refreshed.
To be more specific, I wasn't interested in verifying
On 2023-06-09, Daniel Pielmeier wrote:
> If it is only about gemato then temporary disable the rsync-verify flag
> which pulls it in.
>
> # USE="-rsync-verify" emerge sys-apps/portage
The problem I ran into is that you never know how many issues there
are standing i
[1.25.10-r1] PYTHON_TARGETS="python3_8* python3_9* (-python3_10)"
[ebuild U ] dev-python/requests-2.26.0 [2.24.0-r1]
PYTHON_TARGETS="python3_8* python3_9* (-python3_10)"
[ebuild U ] app-portage/gemato-16.2 [15.2]
PYTHON_TARGETS="python3_8* python3_9* (-python3_
gt;
> The interesting thing is that the conflict refers to the exact same
> piece of code: certifi-2018.4.16:0/0::gentoo is scheduled for merge but
> it is already installed. So what's wrong with it?
I would sort out the portage- situation first. That depends on
gemato- which may
Thanks for the answer. I'd heard of this attack and read this [1] article on
gentoo.org. From what I understand, it said that in theory there shouldn't be
problems when syncing because "The gemato tool used to verify the Gentoo
ebuild repository uses WKD by default. During normal operation it shou
change(s). The --autounmask-backtrack=y
* option can be used to force further backtracking, but there is no
* guarantee that it will produce a solution.
!!! All ebuilds that could satisfy
">=app-portage/gemato-14[python_targets_pypy3(-)?,python_targets_python3_6(-)?,python_targets_python
:
[...]
[nomerge ] app-portage/gemato-16.2::gentoo USE="gpg -test -tools"
PYTHON_TARGETS="python3_8* (-pypy3) -python3_6 -python3_7* -python3_9"
[nomerge ] dev-python/requests-2.24.0-r1::gentoo USE="ssl -socks5
-test" PYTHON_TARGETS="python3_8* (-pypy3
-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_pypy3(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]
> required by (app-portage/gemato-16.2:0/0::gentoo, ebuild scheduled for
> merge)
On 09/06/2023 21:16, Grant Edwards wrote:
On 2023-06-09, Daniel Pielmeier wrote:
If it is only about gemato then temporary disable the rsync-verify flag
which pulls it in.
# USE="-rsync-verify" emerge sys-apps/portage
The problem I ran into is that you never know how m
On 2023-06-12, Wol wrote:
> On 09/06/2023 21:16, Grant Edwards wrote:
>> On 2023-06-09, Daniel Pielmeier wrote:
>>
>>> If it is only about gemato then temporary disable the rsync-verify flag
>>> which pulls it in.
>>>
>>> # USE="-rsync-
>>> emerge (6 of 11) sys-devel/llvm-15.0.7-r3 to /
> 1686582174: >>> emerge (7 of 11) app-portage/gemato-20.4 to /
> 1686582180: >>> emerge (8 of 11) media-libs/gstreamer-1.20.5 to /
> 1686582206: >>> emerge (9 of 11) dev-db/unixODBC-2.3.11 t
On Tue, Jun 13, 2023 at 10:38 AM Grant Edwards
wrote:
> On 2023-06-12, Wol wrote:
> > On 09/06/2023 21:16, Grant Edwards wrote:
> >> On 2023-06-09, Daniel Pielmeier wrote:
> >>
> >>> If it is only about gemato then temporary disable
user would switch to git anyway.
At that time also the gkeys project was very active, and git was
(besides webrsync) the only expected way to get checksums for the
full tree. In particular, rsync was inherently insecure.
The situation has changed meanwhile on both sides: gkeys was
apparently practical
oisonin
> > g->
> can-break-some-openpgp-implementations/
>
> > Aside:
> > I have already switched my personal gpg configuration to use the new
> > isolated keyserver.
>
> Thanks for the answer. I'd heard of this attack and read this [1] article on
> gentoo.o
o /
> > 1686579507: >>> emerge (5 of 11) net-print/cups-2.4.4 to /
> > 1686579541: >>> emerge (6 of 11) sys-devel/llvm-15.0.7-r3 to /
> > 1686582174: >>> emerge (7 of 11) app-portage/gemato-20.4 to /
> > 1686582180: >>> emerg
et_jython2_7(-),-python_single_target_pypy(-),-python_single_target_pypy3(-),-python_single_target_python3_7(-),python_single_target_python3_6(+)]
required by (net-misc/streamlink-1.1.1:0/0::gentoo, installed)
USE="-doc -test" ABI_X86="(64)" PYTHON_SINGLE_TARGET="python3_6
-python2_7 -python
.10 [2.2.4] USE="ssl%*"
[ebuild N ] app-portage/gemato-14.1 USE="blake2 bzip2 gpg -lzma -sha3
{-test} -tools" PYTHON_TARGETS="python2_7 python3_6 (-pypy) -python3_5
(-python3_7)"
[ebuild U ~] sys-apps/portage-2.3.67 [2.3.13-r1] USE="rsync-verify%*
penpgp-keys-gentoo-release-20180706
>[20180703] USE="{-test%}"
>
> [ebuild R] dev-python/setuptools-36.7.2
>PYTHON_TARGETS="python3_6* -python3_5*"
>
> [ebuild R] dev-python/certifi-2018.4.16
> PYTHON_TARGETS="python3_6* -python3_5*
equired by "app-portage/gemato-::gentoo" [ebuild])//
//(dependency required by
"sys-apps/portage-2.3.66-r1::gentoo[-build,rsync-verify]" [ebuil//
//(dependency required by "portage" [argument])//
//For more information, see the MASKED PACKAGES section
> > > Aside:
> > > I have already switched my personal gpg configuration to use the new
> > > isolated keyserver.
> >
> > Thanks for the answer. I'd heard of this attack and read this [1] article
> > on gentoo.org. From what I understand, it said that
7(-)?,python_targets_python3_8(-)?,python_targets_python3_9(-)?,-python_single_target_pypy3(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-),-python_single_target_python3_8(-),-python_single_target_python3_9(-)]
required by (app-portage/gemato-16.2:0/0::gentoo, ebuild scheduled for
merge) USE=&
gman.org.uk>
> >wrote:>
> >> On 09/06/2023 21:16, Grant Edwards wrote:
> >>
> >>> On 2023-06-09, Daniel Pielmeier
> >>> bil...@gentoo.org<mailto:bil...@gentoo.org> wrote:
>>>
> >>>
> >>>
> >>>> I
06-09, Daniel Pielmeier bil...@gentoo.org<mailto:bil...@gentoo.org>
>>> wrote:
>>>
>>>> If it is only about gemato then temporary disable the rsync-verify flag
>>>> which pulls it in.
>>>>
>>>> # USE="-rsync-verify" emerge s
verification
because the public key was not available without app-crypt/openpgp-keys-
gentoo-release first being updated to the latest 20180703 version.
A poster on another thread has provided advice on using gemato to verify the
gentoo keys, but I don't know or understand the process gemato
py%) (-python3_4%) (-python3_5%)" 839 KiB
[ebuild U ] dev-python/certifi-2019.11.28::gentoo [2018.4.16::gentoo]
PYTHON_TARGETS="python2_7 python3_7* (-pypy3) -python3_6* (-python3_8) (-pypy%)
(-python3_4%) (-python3_5%)" 153 KiB
[ebuild U ] app-portage/gemato-14.3::gent
TARGETS="python2_7 python3_6* (-pypy) (-pypy3) -python3_5* (-python3_7)
(-python3_4%)" 147 KiB
[ebuild U ] app-crypt/gnupg-2.2.10::gentoo [2.2.4::gentoo] USE="bzip2 ldap
nls readline smartcard ssl%* usb -doc (-selinux) -tofu -tools -wks-server
(-gnutls%*)" 6504 KiB
[ebuild
; > >
> > > > https://www.bleepingcomputer.com/news/security/public-certificate-pois
> > > > on
> > > > in
> > > > g->
> > >
> > > can-break-some-openpgp-implementations/
> > >
> > > > Aside:
> &g
mmand line?
e.g:
sudo emerge -av =sys-apps/portage-2.3.89-r3
=app-portage/gemato-14.3 =dev-python/setuptools-44.1.0
dev-python/certifi-2019.11.28
Maybe. The issue is to first understand (for each slot conflict) what
is pulling in each of the conflicting versions. The newer version is
prob
=sys-apps/portage-2.3.89-r3
=app-portage/gemato-14.3 =dev-python/setuptools-44.1.0
dev-python/certifi-2019.11.28
On 05/16/20 18:16, Jack wrote:
On 2020.05.16 11:56, n952162 wrote:
Okay, I'm blocked here, at the very beginning:
sys-apps/portage:0
(sys-apps/portage-*2.3.89-r3:0*/0::gent
quot;
[ebuild U ] dev-python/requests-2.25.1-r1 [2.21.0-r1] USE="-test%"
PYTHON_TARGETS="python3_8%* -python3_9%"
[ebuild U ~] app-crypt/gnupg-2.2.27 [2.2.20] USE="-scd-shared-access%"
[ebuild U ] app-portage/gemato-16.2 [14.3] PYTHON_TARGET
merge (3 of 11) dev-python/fonttools-4.39.4 to /
1686579500: >>> emerge (4 of 11) dev-python/weasyprint-59.0 to /
1686579507: >>> emerge (5 of 11) net-print/cups-2.4.4 to /
1686579541: >>> emerge (6 of 11) sys-devel/llvm-15.0.7-r3 to /
1686582174: &
>
> The current version of portage supports EAPI '6'. You must upgrade to a
> newer version of portage before EAPI masked packages can be installed.
> (dependency required by "app-portage/gemato-::gentoo" [ebuild])
> (dependency required by
> "sys-apps/portage-2.
urity/public-certificate-po
> > > > > is
> > > > > on
> > > > > in
> > > > > g->
> > > >
> > > > can-break-some-openpgp-implementations/
> > > >
> > > > > Aside:
> > > > >
equire
python 3.7.
# emerge -cpv python:3.7
Calculating dependencies... done!
dev-lang/python-3.7.9 pulled in by:
app-office/gnumeric-1.12.47 requires dev-lang/python:3.7
app-office/libreoffice-6.4.7.2 requires dev-lang/python:3.7[threads(+),xml]
app-portage/gemato-16.2 requires dev-l
s... done!
> dev-lang/python-2.7.18 pulled in by:
> app-doc/gimp-help-2.8.2 requires >=dev-lang/python-2.7.5-r2:2.7
> app-office/scribus-1.5.5-r1 requires >=dev-lang/python-2.7.5-r2:2.7
> app-portage/gemato-14.3 requires
> >=dev-lang/python-2.7.5-r2:2.7[threads(+
python:2.7
Calculating dependencies... done!
dev-lang/python-2.7.18 pulled in by:
app-doc/gimp-help-2.8.2 requires >=dev-lang/python-2.7.5-r2:2.7
app-office/scribus-1.5.5-r1 requires >=dev-lang/python-2.7.5-r2:2.7
app-portage/gemato-14.3 requires
>=dev-lang/python-2.7.5-r2:2.
ired by
(dev-python/pyparsing-2.4.7-r1:0/0::gentoo, installed) USE="userland_GNU -examples"
ABI_X86="(64)" PYTHON_TARGETS="python3_8 python3_9 (-pypy3) -python3_10"
>=dev-lang/python-exec-2:2/2=[python_targets_python3_8(-),python_targets_python3_9(-)] required by
(
ed in by
>
> >=dev-lang/python-exec-2:2/2=[python_targets_python3_8(-),python_targets_python3_9(-)]
> required by (dev-python/pyparsing-2.4.7-r1:0/0::gentoo, installed)
> USE="userland_GNU -examples" ABI_X86="(64)" PYTHON_TARGETS="python3_8
> python3_9 (
] dev-python/cryptography-3.2.1::gentoo [2.9::gentoo]
USE="-idna -libressl -test" PYTHON_TARGETS="python3_6 python3_8*
(-pypy3) -python3_7* -python3_9 (-python2_7%*)" 529 KiB
[ebuild R ] media-libs/lv2-1.18.0::gentoo USE="-doc -plugins"
ABI_X86="(64) -32 (-x32
-python -qt5 (-selinux) -systemd -test"
ABI_X86="(64) -32 (-x32)" PYTHON_TARGETS="python3_7 python3_8*
-python3_6" 0 KiB
[ebuild U ] media-libs/gegl-0.4.24:0.4::gentoo [0.4.22:0.4::gentoo]
USE="cairo -debug -ffmpeg -introspection -lcms -lensfun -openexr
(-x32)" PYTHON_TARGETS="python3_7 python3_8*
-python3_6" 0 KiB
[ebuild U ] media-libs/gegl-0.4.24:0.4::gentoo [0.4.22:0.4::gentoo]
USE="cairo -debug -ffmpeg -introspection -lcms -lensfun -openexr -pdf
-raw -sdl -svg -test -tiff -umfpack -v4l -vala -webp" 4822 KiB
[ebuild
ntry-1.1.0-r2
app-crypt/rhash-1.3.6-r1
app-dicts/aspell-en-2018.04.16.0
app-editors/emacs-26.3-r1
app-emacs/emacs-common-gentoo-1.6-r3
app-emacs/emacs-daemon-0.22
app-eselect/eselect-ctags-1.18
app-eselect/eselect-emacs-1.18
app-eselect/eselect-fontconfig-1.1-r1
app-eselect/eselect-java-0.4.0
app-es
quot; 0 KiB
> [ebuild N ] app-arch/lz4-1.9.2:0/r132::gentoo USE="-static-libs"
> ABI_X86="(64) -32 (-x32)" 0 KiB
> [ebuild U ] dev-libs/libksba-1.4.0::gentoo [1.3.5-r1::gentoo]
> USE="-static-libs" 0 KiB
> [ebuild U ] app-crypt
59 matches
Mail list logo
