| View previous topic :: View next topic |
| Author |
Message |
jankom
Guru
Joined: 30 Aug 2021
Posts: 329
Location: USA
|
 Posted: Mon Oct 16, 2023 12:42 pm Post subject: |
 |
|
sam wrote | Quote: | | can you try emerge --version and emerge --sync --debug |
| Code: | gellert@jgklinux ~ $ emerge --version
Portage 3.0.51 (python 3.11.5-final-0, default/linux/amd64/17.1, gcc-13, glibc-2.37-r7, 6.2.9-x86_64-linode160 x86_64)
gellert@jgklinux ~ $ su -c "emerge --sync --debug"
Password:
myaction sync
myopts {'--debug': True, '--regex-search-auto': 'y'}
[DEBUG] Using selector: EpollSelector
>>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'...
[DEBUG] Using selector: EpollSelector
* Using keys from /usr/share/openpgp-keys/gentoo-release.asc
* Refreshing keys via WKD ...[DEBUG] list_keys(): keyid: A13D0EF1914E7A72
[DEBUG] list_keys(): fingerprint: EF9538C9E8E64311A52CDEDFA13D0EF1914E7A72
[DEBUG] list_keys(): UID: repomirrorci@gentoo.org
[DEBUG] list_keys(): keyid: DB6B8C1F96D8BF6D
[DEBUG] list_keys(): fingerprint: DCD05B71EAB94199527F44ACDB6B8C1F96D8BF6D
[DEBUG] list_keys(): UID: infrastructure@gentoo.org
[DEBUG] list_keys(): ignoring UID without mail: b'Gentoo Portage Snapshot Signing Key (Automated Signing Key)'
[DEBUG] list_keys(): keyid: 9E6438C817072058
[DEBUG] list_keys(): fingerprint: D99EAC7379A850BCE47DA5F29E6438C817072058
[DEBUG] list_keys(): UID: releng@gentoo.org
[DEBUG] list_keys(): keyid: BB572E0E2D182910
[DEBUG] list_keys(): fingerprint: 13EBBDBEDE7A12775DFDB1BABB572E0E2D182910
[DEBUG] list_keys(): UID: releng@gentoo.org
[DEBUG] Starting new HTTPS connection (1): gentoo.org:443
|
Output of the first command in my home fitlet2 desktop: | Code: | janos@andraslinux ~ $ emerge --version
Portage 3.0.49 (python 3.11.5-final-0, default/linux/amd64/17.1/desktop, gcc-12, glibc-2.37-r3, 6.1.46-gentoofitlet2 x86_64)
janos@andraslinux ~ $ |
Apparently the remote linode server is more updated now, yet cannot do the sync.
Looks like the remote server is stuck at the https connection, As posted before the firwall is practically open, and port 443 is not forwarded.
jankom |
|
| Back to top |
|
 |
sam_
Developer
Joined: 14 Aug 2020
Posts: 1721
|
| Posted: Mon Oct 16, 2023 12:55 pm Post subject: |
|
|
Thanks. That's better but I was hoping for a bit more info from the debug output. It hangs at that '[DEBUG] Starting new HTTPS connection (1): gentoo.org:443' line? 
Which gemato version is this? If it's not 20.5, could you try get that?
As a hack, instead, you could try the bit at the top of https://github.com/projg2/gemato/issues/7? You will have to manually edit the file at /usr/lib/python3.11/site-packages/gemato/openpgp.py.
(I've now filed https://github.com/projg2/gemato/issues/33 too.) |
|
| Back to top |
|
|
jankom
Guru
Joined: 30 Aug 2021
Posts: 329
Location: USA
|
| Posted: Mon Oct 16, 2023 1:12 pm Post subject: |
|
|
Thanks, but additional info B4 replying re gemato.
Output of "emerge --sync --debug" right now from my fitlet2 home desktop: | Code: | andraslinux /home/janos # emerge --sync --debug
myaction sync
myopts {'--debug': True, '--regex-search-auto': 'y'}
>>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'...
* Using keys from /usr/share/openpgp-keys/gentoo-release.asc
* Refreshing keys via WKD ... [ ok ]
>>> Starting rsync with rsync://[2a00:1828:a00d:ffff::6]/gentoo-portage...
... |
Command proceeded immediately, and then I interrupted the syncing.
Interestingly, the linode remote server [DEBUG] talks about EpolSelector, etc.
Could this be the culpriq?
jankom |
|
| Back to top |
|
|
sam_
Developer
Joined: 14 Aug 2020
Posts: 1721
|
| Posted: Mon Oct 16, 2023 1:21 pm Post subject: |
|
|
| Good point - but it's just because one of the Portages is older and I improved the debug support in newer versions, so ignore that bit (red herring). |
|
| Back to top |
|
|
jankom
Guru
Joined: 30 Aug 2021
Posts: 329
Location: USA
|
| Posted: Mon Oct 16, 2023 1:29 pm Post subject: |
|
|
sam wrote: | Quote: | | Which gemato version is this? |
Is this my gemato version? | Code: | gellert@jgklinux ~ $ emerge -p gemato
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 1.29 s.
[ebuild R ] app-portage/gemato-20.5
gellert@jgklinux ~ $ |
Is this my gemato version?
jankom |
|
| Back to top |
|
|
sam_
Developer
Joined: 14 Aug 2020
Posts: 1721
|
| Posted: Mon Oct 16, 2023 1:30 pm Post subject: |
|
|
yes!
OK, that means unfortunately we need to do that manual hack I mentioned with editing the file, then try sync, then read the file in /tmp it makes. |
|
| Back to top |
|
|
jankom
Guru
Joined: 30 Aug 2021
Posts: 329
Location: USA
|
| Posted: Mon Oct 16, 2023 1:39 pm Post subject: |
|
|
sam wrote: | Quote: | | As a hack, instead, you could try |
Sorry, I looked at those links but I'm not that experienced with patching, hacking. I can try to learn and play with it, but not as yet now. Thanks for your efforts tryng to help.
I have to go now, but will return to this forum sometimes later today.
jankom |
|
| Back to top |
|
|
jankom
Guru
Joined: 30 Aug 2021
Posts: 329
Location: USA
|
| Posted: Mon Oct 16, 2023 9:02 pm Post subject: hacking openpgp.py file |
|
|
@sam
I need some guidance. the Whissi posting looks like a patch. What exactly do I need to edit in the openpgp.py file (line 196 does noe seem to fit)?
Do I need to add the following quoted lines before line containing "honor user..."? | Quote: | +# enable logging
+verbose
+debug 4096
+debug-level 4096
+debug-all
+log-file /tmp/gemato-dirmngr.log
+
|
I copied the original openpgp.py as openpgp.py.g just to make sure I can recover it.
This is part of my learning experience - jankom |
|
| Back to top |
|
|
jankom
Guru
Joined: 30 Aug 2021
Posts: 329
Location: USA
|
| Posted: Mon Oct 16, 2023 9:39 pm Post subject: Additional info on openpgp.py |
|
|
I compared the openpgp.py files of my home fitlet desktop and the linode remote server, and found some differences. Probably a red herring - but I try to keep both machines updated the same time, so that they would be the same except Profile 3 and 1.
Here is the difference, has to do with logging: | Code: | janos@andraslinux ~/tmp $ diff openpgp.py openpgp.py.linode
51a52,53
> LOGGER = logging.getLogger(__name__)
>
468c470
< logging.warning(
---
> LOGGER.warning(
477,478c479,480
< logging.debug(f'GNUPGHOME left for debug purposes: '
< f'{self._home}')
---
> LOGGER.debug(f'GNUPGHOME left for debug purposes: '
> f'{self._home}')
525c527
< logging.debug(
---
> LOGGER.debug(
|
and so on.
Just another tidbit of information if it may help...
jankom |
|
| Back to top |
|
|
jankom
Guru
Joined: 30 Aug 2021
Posts: 329
Location: USA
|
| Posted: Tue Oct 17, 2023 1:50 pm Post subject: Update py hacking |
|
|
I did the gemato openpgp.py hacking and here is the partial output of a log file: | Code: | ...
2023-10-17 13:35:01 gpg-agent[22018] DBG: chan_10 <- OPTION agent-awareness=2.1.0
2023-10-17 13:35:01 gpg-agent[22018] DBG: chan_10 -> OK
2023-10-17 13:35:01 gpg-agent[22018] DBG: chan_10 <- HAVEKEY 456F3286FADED7113707077C6914559D3C570166
2023-10-17 13:35:01 gpg-agent[22018] DBG: chan_10 -> ERR 67108881 No secret key <GPG Agent>
2023-10-17 13:35:01 gpg-agent[22018] DBG: chan_10 <- HAVEKEY ED3DB8E852B3CBEFEE9E639985B827385C040F08
2023-10-17 13:35:01 gpg-agent[22018] DBG: chan_10 -> ERR 67108881 No secret key <GPG Agent>
2023-10-17 13:35:01 gpg-agent[22018] DBG: chan_10 <- HAVEKEY E7A39208C790BD427D8991F6F0B9BEC02599C7F8
2023-10-17 13:35:01 gpg-agent[22018] DBG: chan_10 -> ERR 67108881 No secret key <GPG Agent>
2023-10-17 13:35:01 gpg-agent[22018] DBG: chan_10 <- HAVEKEY 97F78819EDC085335AC22F6E5CB293AD31A315ED
2023-10-17 13:35:01 gpg-agent[22018] DBG: chan_10 -> ERR 67108881 No secret key <GPG Agent>
2023-10-17 13:35:01 gpg-agent[22018] DBG: chan_10 <- [eof]
2023-10-17 13:35:05 gpg-agent[22018] DBG: agent_cache_housekeeping |
Is the problem the missing secret key? How to fix that?
Note: This log file excerpt is from /tmp/gpg-agent.log, not the hack defined /tmp/gemato-dirmgr.log which is not there.
jankom |
|
| Back to top |
|
|
jankom
Guru
Joined: 30 Aug 2021
Posts: 329
Location: USA
|
| Posted: Tue Oct 24, 2023 10:14 pm Post subject: Solved |
|
|
Finally I gave up, and rebuilt the virtual server. Presently I'm working on restoring it from backups, but the core system works and eix-sync completes. Apparently the install image deployed by linode (Akamai) is 154 days old, so emerging apache failed. This is why I decided to do (and test with the new installation) an eix-sync.
The root cause was probably something with keys. I chose the "easy" solution of rebuilding the entire system.
Nevertheless, this was a good learning experience. Thank you all for suggestions and helping me with this problem.
jankom |
|
| Back to top |
|
|
|
Portage & Programming
