| lubot | [telegram] <lynorian> is ssh for pushing things to the manual on phab down or will I just be able to push to gittea soon? | 01:26 |
|---|---|---|
| === guiverc2 is now known as guiverc | ||
| arraybolt3[m] | @lynorian: I don't know how the manual development process used to work - did the manual automatically update when you'd make a change to the repo, or did it have to be manually moved over to manual.lubuntu.me? | 01:54 |
| arraybolt3[m] | Actually I don't know enough about how all of Git works to actually know any answers here so... | 01:55 |
| arraybolt3[m] | s/Git/Lubuntu Git/ | 01:55 |
| lubot | [telegram] <lynorian> I am pretty it is a cron job that builds it from the repo source every hour but not exactly sure myself | 01:58 |
| tsimonq2 | teward: lynorian needs access to GiTea please ^^^^^^^ | 06:27 |
| arraybolt3[m] | o/ | 15:05 |
| arraybolt3[m] | Alright so I didn't get back until today, but I am back now and am going to start working on writing the setup-gitea script. | 15:06 |
| lubot_ | [telegram] <teward001> tsimonq2: 30min wait time | 15:11 |
| lubot_ | [telegram] <teward001> lots of dayjob crap | 15:11 |
| arraybolt3[m] | I see that GitPython is in maintenance mode, which gives me cause for concern, so I'm cutting it out of the loop in the setup-gitea script and just using calls to os.chdir() and custom-written functions that simply call git directly. If this isn't acceptable, I should probably know soon-ish. | 15:26 |
| tsimonq2 | <arraybolt3[m]> "I see that GitPython is in..." <- Read it more carefully, maintenance mode is scaring you off ;) | 15:42 |
| arraybolt3[m] | Well... I can use it, but after seeing how other projects in Maintenance Mode have gotten treated... Also the thing where he advertises gitoxide is a bit worrying, when he talks about where some things are deeply flawed and broken beyond repair. | 15:43 |
| arraybolt3[m] | Maybe this is just my fear of causing catastrophic messes in Git surfacing again :P | 15:44 |
| arraybolt3[m] | And I am assuming this guy's maintenance mode is the same as other people's maintenance mode, which may be false. | 15:46 |
| teward | tsimonq2: i require lynorian's email address | 15:46 |
| arraybolt3[m] | teward: ...can't you get that out of the manual Git repo? | 15:47 |
| teward | i'm lazy :p | 15:47 |
| teward | and doing a lot of Day Job stuff | 15:47 |
| * arraybolt3[m] find is | 15:47 | |
| arraybolt3[m] | *it | 15:47 |
| arraybolt3[m] | (Email found, teward now has it) | 15:52 |
| teward | and i sent lynorian an email with the password that it was created with as it's a temporary pw | 15:52 |
| arraybolt3[m] | The way you shallow clone a repo is with `git clone --depth=1 <repoURI>`, right? | 15:52 |
| teward | now i'mma go consume mass quantities of coffee | 15:52 |
| arraybolt3[m] | Because if so, shallow cloning on Phab is busted. Yet another reason to deprecate it I guess, though. | 15:52 |
| arraybolt3[m] | teward: Mmm, that sounds like a good idea in just a bit here. | 15:53 |
| * genii joins teward | 15:53 | |
| arraybolt3 | So this is a bit awkward. Gitea doesn't have any API feature for changing a repository's default branch. Here's hoping the trick with changing the remote HEAD works. | 15:59 |
| arraybolt3 | Ah, looks like "git push --mirror" will do the trick. Time to do some experimenting in a test repo. | 16:01 |
| arraybolt3 | actually... that could cause real chaos... hmm... how do I do this then? | 16:03 |
| arraybolt3 | It dawns on me, if I use git clone --mirror, then git push --mirror won't be a problem. | 16:09 |
| arraybolt3 | OK, I need a break, be back later. | 16:09 |
| arraybolt3[m] | OK so this is frustrating. It doesn't look like there's any way for me to set the remote default branch. | 18:47 |
| arraybolt3[m] | Even git push --mirror isn't doing the trick. | 18:48 |
| arraybolt3[m] | I can change the default branch locally using git remote set-head, but there's no way for me to push that to Gitea. | 18:49 |
| arraybolt3[m] | Soooo... from what I'm seeing, I think we're sunk. Gitea doesn't have the API functionality needed to change a default branch without the Web UI, and Git doesn't have any good workarounds to make it happen. And I even saw a feature request for this on Gitea's GitHub, which seems to have only been half implemented (the request asked for something related to both protected branches and default branches, only the bit about protected | 18:55 |
| arraybolt3[m] | branches was ever implemented that I can see) and then closed. | 18:55 |
| arraybolt3[m] | Currently in #gitea to see if anyone else knows what to do here. | 18:58 |
| arraybolt3[m] | OK so apparently I can't read. The API can, in fact, change the default branch. | 19:01 |
| arraybolt3[m] | Simon Quigley: Alright, finished script for your critique whenever you're ready: | 19:24 |
| * arraybolt3[m] sent a code block: https://libera.ems.host/_matrix/media/v3/download/libera.chat/565711bc08297de371707969f51f283a7af05bb2 | 19:24 | |
| arraybolt3[m] | I was going to undo my work porting away from GitPython but it dawned on me doing it this way makes GitPython unnecessary, which makes our thing a bit more portable (this only depends on Requests and Python builtins, nothing more), and also avoids the use of pip for installing GitPython which may slightly increase our security so that no one has to risk typo-ing GitPython and accidentally installing a malicious repo. | 19:26 |
| arraybolt3[m] | * I was going to undo my work porting away from GitPython but it dawned on me that getting rid of GitPython makes our thing a bit more portable (this only depends on Requests and Python builtins, nothing more), and also avoids the use of pip for installing GitPython which may slightly increase our security so that no one has to risk typo-ing GitPython and accidentally installing a malicious repo. | 19:26 |
| arraybolt3[m] | * I was going to undo my work porting away from GitPython but it dawned on me that getting rid of GitPython makes our thing a bit more portable (this only depends on Requests and Python builtins, nothing more), and also avoids the use of pip for installing GitPython which may slightly increase our security by making it so that no one has to risk typo-ing the install command for GitPython and accidentally installing a malicious | 19:27 |
| arraybolt3[m] | repo. | 19:27 |
| arraybolt3[m] | * ```... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/466f048d3b1471f76d847c4f760d6beeae4d84bf>) | 19:28 |
| tsimonq2 | Today's been one of those days where I'm running on 2 hours of sleep but have no choice but to run through it | 19:34 |
| tsimonq2 | I'll code review once I get some sleep - it'll be more pleasant that way :P | 19:34 |
| arraybolt3[m] | No problem. I'll carefully debug the thing to make sure it's safe, then shout for no one to change anything on Gitea and kick off the final change. | 19:35 |
| tsimonq2 | <arraybolt3[m]> "I was going to undo my work..." <- Attack vector could be changing $PATH tho? | 19:35 |
| arraybolt3[m] | LOL if something can change $PATH on your local machine, you have much worse things to worry about than an install command typo. | 19:36 |
| tsimonq2 | Fair enough lmao | 19:37 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!