(Assigning to you as you did, at least!, the last upload)
Currently, the pureos-meta package is here:
https://github.com/purism/pureos-meta
Please could you move it to https://code.puri.sm/pureos/pureos-meta ?
Thanks :)
(Assigning to you as you did, at least!, the last upload)
Currently, the pureos-meta package is here:
https://github.com/purism/pureos-meta
Please could you move it to https://code.puri.sm/pureos/pureos-meta ?
Thanks :)
At the moment, this is not easily possible without setting up some kind of merge with Github or redirection, as a couple of tools pull data from the repository and have it hardcoded.
I want to have the repository and everything else moved rather soon though, and at the same time split the "PureOS" group at Gogs into pureos-packages and pureos proper, so all the infrastructure pieces can live there as well and we have a separate place for packages (for easier permission control, clear scope and less potential for name conflicts).
If we are moving to Gitlab or $something_else though, I will wait for that to happen first (because if we need to adjust our Git repo URLs, it's better to only do it once) - that's why I didn't pursue these plans so far.
@todd Why did you reassign the task?
It is still valid, even if Chris can now commit to the repo (which I though he could...), but moving it will need quite a lot more changes to not break things - that's the reason why all infrastructure components are still on Github, especially since Gogs was very unreliable initially and we couldn't risk these repositories to go down.
I reassigned probably out of confusion of the task, I thought it was blocking on assignment of a user to proceed under lamby's tasks, but maybe this is under your tasks. So it can be assigned wherever appropriate.
Ok, in that case I claim this task again - this is really not blocking anything at all, in a way it's more a cosmetic/consistency change. I had it on my todo list anyway, so having this bug makes sense.
Thanks, although I mildly disagree that it's just cosmetic change given that it requires separate access with yet another set of credentials and ACL to maintain etc. etc etc.
Yeah, for us it is a change needed for consistency and ease of development, but for our users it doesn't matter at all and thereby is more of a cosmetic change (I should have been clearer on what I meant ^^).