On Fri, 7 Apr 2017 21:24:55 -0600 Kevin Fenzi kevin@scrye.com wrote:
On 04/06/2017 09:24 AM, Petr Kovar wrote:
On Wed, 5 Apr 2017 10:07:39 -0600 Kevin Fenzi kevin@scrye.com wrote:
On 03/06/2017 05:17 AM, Petr Kovar wrote:
I'm afraid we don't have the same Publican web site data in https://pagure.io /docs-fp-o/ that used to be in https://git.fedorahosted.org/cgit/docs/web.git/log/ (which is no longer available).
Unless we get the data back from the old web.git repo, we won't be able to publish any new Publican content to http://docs.fedoraproject.org/, as documented in http://fedoraproject.org/wiki/Publishing_a_document_with_Publican.
I can get the data back if you like. We still have it available.
Thank you. I think we should get the data back just in case the new publishing platform is not ready in time for the Fedora 26 GA release. Actually, we might need to cover beta, as well?
Does anyone object to this?
I guess we should set up a temporary web.git repo in pagure and update the publish scripts for http://docs.fedoraproject.org/ accordingly.
ok. If someone does this, please let me know so I can change the pull location in infrastructure.
Can you push the backup data to a new repo on pagure? Or, do we need to set up a new repo first?
I created and pushed the git info to:
https://pagure.io/fedora-docs-web/
I've made a few folks admins, hopefully they can add anyone else that needs it or I can do so if asked.
I have switched infrastructure to pull from and publish this content now, so changes there should take effect.
Let me know if there's anything else to do on this now...
Thank you, Kevin. It turns out I'm unable to test the new repo with my old Fedora 18 + publican 2 setup since pagure.io no longer allows for connections with the dated ssh version shipped in F18...
pk