Hi

On Wed, 31 Aug 2022 at 09:23, Kwankyu Lee <ekwan...@gmail.com> wrote:

> Perhaps need to update trac server ssh keys stored in github?
>

This is quite likely. Who has access, where is this done?

Regards,
Jan




>
> On Wednesday, August 31, 2022 at 4:10:34 PM UTC+9 emanuel.c...@gmail.com
> wrote:
>
>> And an attempt to fetch a ticket also failed for related reasons :
>>
>> charpent@zen-book-flip:/usr/local/sage-9$ git trac checkout 34457
>> Loading ticket #34457...
>>
>> Traceback (most recent call last):
>>   File
>> "/home/charpent/Dev/git-trac-command/git_trac/digest_transport.py", line
>> 106, in single_request
>>     return self.parse_response(response)
>>   File "/usr/lib/python3.10/xmlrpc/client.py", line 1354, in
>> parse_response
>>     return u.close()
>>   File "/usr/lib/python3.10/xmlrpc/client.py", line 668, in close
>>     raise Fault(**self._stack[0])
>> xmlrpc.client.Fault: <Fault 1: "'Error updating the gitolite-admin
>> repository: Host key verification failed.\nfatal: Could not read from
>> remote repository.\n\nPlease make sure you have the correct access
>> rights\nand the repository exists.\n; you may have to manually clean up or
>> re-clone the repository' while executing 'ticket.changeLog()'">
>>
>> During handling of the above exception, another exception occurred:
>>
>>
>> Traceback (most recent call last):
>>   File "/usr/local/bin/git-trac", line 17, in <module>
>>     cmdline.launch()
>>   File "/home/charpent/Dev/git-trac-command/git_trac/cmdline.py", line
>> 239, in launch
>>     app.checkout(args.ticket_or_branch, args.branch_name)
>>   File "/home/charpent/Dev/git-trac-command/git_trac/app.py", line 118,
>> in checkout
>>     self._checkout_ticket(int(ticket_or_branch), branch_name)
>>   File "/home/charpent/Dev/git-trac-command/git_trac/app.py", line 125,
>> in _checkout_ticket
>>     ticket = self.trac.load(ticket_number)
>>   File "/home/charpent/Dev/git-trac-command/git_trac/trac_server.py",
>> line 133, in load
>>     ticket = TracTicket(ticket_number, self.anonymous_proxy)
>>   File "/home/charpent/Dev/git-trac-command/git_trac/trac_ticket.py",
>> line 155, in TracTicket
>>     change_log = server_proxy.ticket.changeLog(ticket_number)
>>   File "/usr/lib/python3.10/xmlrpc/client.py", line 1122, in __call__
>>     return self.__send(self.__name, args)
>>   File "/usr/lib/python3.10/xmlrpc/client.py", line 1464, in __request
>>     response = self.__transport.request(
>>   File "/usr/lib/python3.10/xmlrpc/client.py", line 1166, in request
>>     return self.single_request(host, handler, request_body, verbose)
>>   File
>> "/home/charpent/Dev/git-trac-command/git_trac/digest_transport.py", line
>> 108, in single_request
>>     raise TracInternalError(e)
>> git_trac.trac_error.TracInternalError: <Fault 1: "'Error updating the
>> gitolite-admin repository: Host key verification failed.\nfatal: Could not
>> read from remote repository.\n\nPlease make sure you have the correct
>> access rights\nand the repository exists.\n; you may have to manually clean
>> up or re-clone the repository' while executing 'ticket.changeLog()'">
>>
>> Of note : I could create a new ticket (the one I was trying to fetch)
>> yesterday afternoon. This might be a problem distinct from the one due to
>> the key change (this week-end, IIUIC).
>> Le mercredi 31 août 2022 à 09:04:43 UTC+2, Emmanuel Charpentier a écrit :
>>
>>> The Web site is still unreachable.
>>>
>>> Le mercredi 31 août 2022 à 09:02:53 UTC+2, Emmanuel Charpentier a écrit :
>>>
>>>> Ditto from Git via SSH :
>>>>
>>>> ```charpent@zen-book-flip:/usr/local/sage-9$ git fetch
>>>> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>>>> @    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
>>>> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>>>> IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
>>>> Someone could be eavesdropping on you right now (man-in-the-middle
>>>> attack)!
>>>> It is also possible that a host key has just been changed.
>>>> The fingerprint for the ECDSA key sent by the remote host is
>>>> SHA256:29lzUeszegCYCnVMOJ+Ts/IlCwojLuf03NnVoLlONEs.
>>>> Please contact your system administrator.
>>>> Add correct host key in /home/charpent/.ssh/known_hosts to get rid of
>>>> this message.
>>>> Offending ECDSA key in /home/charpent/.ssh/known_hosts:14
>>>>   remove with:
>>>>   ssh-keygen -f "/home/charpent/.ssh/known_hosts" -R "trac.sagemath.org
>>>> "
>>>> Host key for trac.sagemath.org has changed and you have requested
>>>> strict checking.
>>>> Host key verification failed.
>>>> fatal: Impossible de lire le dépôt distant.
>>>>
>>>> Veuillez vérifier que vous avez les droits d'accès
>>>> et que le dépôt existe.
>>>> ```
>>>>
>>>> Removing the old SSH key cleared git access.
>>>>
>>>>
>>>> Le mercredi 31 août 2022 à 08:45:29 UTC+2, Emmanuel Charpentier a
>>>> écrit :
>>>>
>>>>> This morning (Aug 31, 2022, 8:43), any attempt to reach `
>>>>> trac.sagemath.org` ends up displayong a Python trace :
>>>>>
>>>>> ```
>>>>> Traceback (most recent call last): File
>>>>> "/usr/local/lib/python2.7/dist-packages/trac/web/api.py", line 602, in
>>>>> send_error data, 'text/html') File
>>>>> "/usr/local/lib/python2.7/dist-packages/trac/web/chrome.py", line 1104, in
>>>>> render_template template = self.load_template(filename, method=method) 
>>>>> File
>>>>> "/usr/local/lib/python2.7/dist-packages/trac/web/chrome.py", line 1053, in
>>>>> load_template self.get_all_templates_dirs(), auto_reload=self.auto_reload,
>>>>> File "/usr/local/lib/python2.7/dist-packages/trac/web/chrome.py", line 
>>>>> 758,
>>>>> in get_all_templates_dirs for provider in self.template_providers: File
>>>>> "/usr/local/lib/python2.7/dist-packages/trac/core.py", line 82, in
>>>>> extensions components = [component.compmgr[cls] for cls in classes] File
>>>>> "/usr/local/lib/python2.7/dist-packages/trac/core.py", line 208, in
>>>>> __getitem__ component = cls(self) File
>>>>> "/usr/local/lib/python2.7/dist-packages/trac/core.py", line 144, in
>>>>> __call__ self.__init__() File
>>>>> "/usr/local/lib/python2.7/dist-packages/sage_trac/sshkeys.py", line 195, 
>>>>> in
>>>>> __init__ self._init_gitolite_admin() File
>>>>> "/usr/local/lib/python2.7/dist-packages/sage_trac/sshkeys.py", line 66, in
>>>>> wrapper ret = inner_wrapper(self, *args, **kwargs) File
>>>>> "/usr/local/lib/python2.7/dist-packages/fasteners/lock.py", line 302, in
>>>>> wrapper return f(self, *args, **kwargs) File
>>>>> "/usr/local/lib/python2.7/dist-packages/sage_trac/sshkeys.py", line 52, in
>>>>> inner_method return method(self, *args, **kwargs) File
>>>>> "/usr/local/lib/python2.7/dist-packages/sage_trac/sshkeys.py", line 226, 
>>>>> in
>>>>> _init_gitolite_admin self._update_gitolite_admin() File
>>>>> "/usr/local/lib/python2.7/dist-packages/sage_trac/sshkeys.py", line 287, 
>>>>> in
>>>>> _update_gitolite_admin 'repository'.format(out)) TracError: Error updating
>>>>> the gitolite-admin repository: Host key verification failed. fatal: Could
>>>>> not read from remote repository. Please make sure you have the correct
>>>>> access rights and the repository exists. ; you may have to manually clean
>>>>> up or re-clone the repository
>>>>> ```
>>>>>
>>>>> Any idea ?
>>>>>
>>>>> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/72e04322-519c-4e1b-a217-bd002a8b85acn%40googlegroups.com
> <https://groups.google.com/d/msgid/sage-devel/72e04322-519c-4e1b-a217-bd002a8b85acn%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
  .~.
  /V\     Jan Groenewald
 /( )\    www.aims.ac.za
 ^^-^^

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAg%3Dp_0jEupd%3Dqi974T6fjJDh4hXM_ZYV37fR1fJL1x68%3DE1eA%40mail.gmail.com.

Reply via email to