TPA issueshttps://gitlab.torproject.org/groups/tpo/tpa/-/issues2020-06-13T16:40:41Zhttps://gitlab.torproject.org/tpo/tpa/schleuder/-/issues/40000Gitlab Migration Milestone2020-06-13T16:40:41ZTracGitlab Migration MilestoneWe're creating this ticket as a part of the Trac-to-Gitlab migration, so that each project's numbering for new tickets will start with 40001.We're creating this ticket as a part of the Trac-to-Gitlab migration, so that each project's numbering for new tickets will start with 40001.https://gitlab.torproject.org/tpo/tpa/team/-/issues/40000Gitlab Migration Milestone2020-06-13T17:04:28ZTracGitlab Migration MilestoneWe're creating this ticket as a part of the Trac-to-Gitlab migration, so that each project's numbering for new tickets will start with 40001.We're creating this ticket as a part of the Trac-to-Gitlab migration, so that each project's numbering for new tickets will start with 40001.https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/14Create list of Trac usernames with email addresses2020-06-16T18:46:51ZAlexander Færøyahf@torproject.orgCreate list of Trac usernames with email addressesSince we migrated /some/ users from Trac to Gitlab, it would be useful for us to have a list of each Trac user that have an email attached to their user. We can use this when people write to gitlab-admin@torproject.org and want access to...Since we migrated /some/ users from Trac to Gitlab, it would be useful for us to have a list of each Trac user that have an email attached to their user. We can use this when people write to gitlab-admin@torproject.org and want access to their old Trac accounts on Gitlab. Otherwise, we might end up handing out the accounts to the wrong people and that would be sad.anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/17delete /tpa hierarchy2020-06-16T19:32:08Zanarcatdelete /tpa hierarchyit seems like the `/tpa` hierarchy overlaps with the `/tpo/tpa` project where issues have been imported. i think the group and its subprojects should be deleted, but i'm not confident enough I won't be destroying anything to do it myself...it seems like the `/tpa` hierarchy overlaps with the `/tpo/tpa` project where issues have been imported. i think the group and its subprojects should be deleted, but i'm not confident enough I won't be destroying anything to do it myself.
it looks like https://gitlab.torproject.org/tpa/unattended_upgrades is the only project with any actual content, which is the unattended_upgrades puppet module repo hiro created a while back.
so i'm going to /assign @hiro here and hope she finds the time to review this and approve! :)anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/gitlab-lobby/-/issues/2Test test2020-06-16T21:47:44ZAlexander Færøyahf@torproject.orgTest testSummary
Test testSummary
Test testAlexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.orghttps://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/2zwiebelbot doesn't talk with the new gitlab server2020-06-17T14:01:08Zanarcatzwiebelbot doesn't talk with the new gitlab serverthis works:
```
09:51:56 <anarcat> gitlabtpo:tpo/tpa/gitlab#1
09:51:57 -zwiebelbot:#tpo-admin- gitlabtpo:tpo/tpa/gitlab#1: legacy issues are writable and should not be - https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/1
```
but t...this works:
```
09:51:56 <anarcat> gitlabtpo:tpo/tpa/gitlab#1
09:51:57 -zwiebelbot:#tpo-admin- gitlabtpo:tpo/tpa/gitlab#1: legacy issues are writable and should not be - https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/1
```
but this doesn't:
```
09:50:34 <anarcat> tpo/tpa/gitlab#1
```
... while it should.
it also seems like #NNN still talks to Trac while it should be talking to `legacy#NNN` instead.weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/22Archive legacy/trac2020-06-17T14:03:46ZAlexander Færøy (admin)Archive legacy/tracThe archive feature of Gitlab essentially makes a project read-only. We should do this to prevent accidents where people alter tickets in there.The archive feature of Gitlab essentially makes a project read-only. We should do this to prevent accidents where people alter tickets in there.Alexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.orghttps://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/1legacy issues are writable and should not be2020-06-17T14:03:47Zanarcatlegacy issues are writable and should not bea message from alex:
> A usability issue we have right now: It is possible to comment on
> tickets in legacy/trac, but you shouldn't.
>
> Look for the "Closed (Moved)" part of the ticket, and you can go to the
> *actual* ticket that you...a message from alex:
> A usability issue we have right now: It is possible to comment on
> tickets in legacy/trac, but you shouldn't.
>
> Look for the "Closed (Moved)" part of the ticket, and you can go to the
> *actual* ticket that you should be editing/commenting on.
>
> Yes, we are looking at a way to make it impossible to update legacy/trac
> tickets without some special permissions, to avoid this.
>
> General rule of thumb: If you need to do anything on Gitlab that is not
> looking at historical content, avoid legacy/trac. If you can't avoid it,
> it means we need to extract some more data from it and you should
> contact the Gitlab admins :-)
>
> Happy hacking!
>
> All the best,
> Alex.Alexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.orghttps://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/13Update Trac frontpage to say we are moved to Gitlab2020-06-17T15:33:49ZAlexander Færøyahf@torproject.orgUpdate Trac frontpage to say we are moved to GitlabWe should add a note on trac.torproject.org on our move to Gitlab.We should add a note on trac.torproject.org on our move to Gitlab.anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/7Send tpo/* ticket updates to IRC2020-06-17T20:13:13ZAlexander Færøyahf@torproject.orgSend tpo/* ticket updates to IRCWe should make sure that ticket updates are send to our IRC channel in `#tor-bots` on OFTC.We should make sure that ticket updates are send to our IRC channel in `#tor-bots` on OFTC.anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/30Uploading files on the "Designs" tab does not work2020-06-22T15:51:16ZAntonelaantonela@torproject.orgUploading files on the "Designs" tab does not workSome repos like [tor-browser](https://gitlab.torproject.org/tpo/applications/tor-browser) have a `designs` tab to upload files. That is awesome!
I've tried to upload files, and it is not working, seems like the file gets uploaded (becau...Some repos like [tor-browser](https://gitlab.torproject.org/tpo/applications/tor-browser) have a `designs` tab to upload files. That is awesome!
I've tried to upload files, and it is not working, seems like the file gets uploaded (because something loads) but it doesn't show in the issue. Could someone try to reproduce my error?Alexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.orghttps://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/33Update warning messages of the mirror repositories at GitHub2020-06-22T16:39:52ZBarkin SimsekUpdate warning messages of the mirror repositories at GitHubCurrently, the mirror repositories at the GitHub (https://github.com/torproject/) have the following warning messages in their description fields:
`unofficial git repo -- report bugs/issues/pull requests on https://trac.torproject.org/...Currently, the mirror repositories at the GitHub (https://github.com/torproject/) have the following warning messages in their description fields:
`unofficial git repo -- report bugs/issues/pull requests on https://trac.torproject.org/ --`
They need to be updated to something like:
`unofficial git repo -- report bugs/issues/pull requests on https://gitlab.torproject.org/ --`Gabagaba@torproject.orgGabagaba@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40010sbws would use gitlab git as the canonical repo2020-06-22T19:52:07Zjugasbws would use gitlab git as the canonical repoAccording to what @ahf, @gk and i talked today, we would like to use the gitlab git as the canonical repo and then we can remove the git repo at git.tpoAccording to what @ahf, @gk and i talked today, we would like to use the gitlab git as the canonical repo and then we can remove the git repo at git.tpohttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40015moly should be upgraded to buster(Debian 10) or retired2020-06-23T09:46:38Zweasel (Peter Palfrader)moly should be upgraded to buster(Debian 10) or retiredhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40014hetzner-nbg1-01 should be upgraded to buster(Debian 10) or retired2020-06-23T15:36:02Zweasel (Peter Palfrader)hetzner-nbg1-01 should be upgraded to buster(Debian 10) or retiredhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40018vineale should be upgraded to buster(Debian 10) or retired2020-06-23T16:05:03Zweasel (Peter Palfrader)vineale should be upgraded to buster(Debian 10) or retiredhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40011corsicum should be upgraded to buster/Debian 102020-06-23T19:29:02Zweasel (Peter Palfrader)corsicum should be upgraded to buster/Debian 10weasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/tpo/tpa/team/-/issues/40019scw-arm-par-01 should be upgraded to buster(Debian 10) or retired2020-06-23T19:32:59Zweasel (Peter Palfrader)scw-arm-par-01 should be upgraded to buster(Debian 10) or retiredweasel (Peter Palfrader)weasel (Peter Palfrader)https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/27block /webhook/ on irc bot2020-06-23T20:27:06Zanarcatblock /webhook/ on irc botthe irc bot has /webhook/ wide open to the world right now, and without a password. block the /webhook/ route in nginx and restrict it to the gitlab host.the irc bot has /webhook/ wide open to the world right now, and without a password. block the /webhook/ route in nginx and restrict it to the gitlab host.anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40020Please refresh sysrqb's pgp key2020-06-24T14:52:17ZMatthew FinkelPlease refresh sysrqb's pgp key```
$ gpg2 -k CE1782624600EE98764C6D9CCB8FC772D1AA1D30
pub rsa4096/0xCB8FC772D1AA1D30 2014-06-26 [SC] [expires: 2020-12-20]
Key fingerprint = CE17 8262 4600 EE98 764C 6D9C CB8F C772 D1AA 1D30
uid [ unknown] Mat...```
$ gpg2 -k CE1782624600EE98764C6D9CCB8FC772D1AA1D30
pub rsa4096/0xCB8FC772D1AA1D30 2014-06-26 [SC] [expires: 2020-12-20]
Key fingerprint = CE17 8262 4600 EE98 764C 6D9C CB8F C772 D1AA 1D30
uid [ unknown] Matthew Finkel <sysrqb@torproject.org>
uid [ unknown] Matthew Finkel <Matthew.Finkel@gmail.com>
uid [ unknown] Matthew Finkel <sysrqb@protonmail.com>
uid [ unknown] Matthew Finkel <sysrqb@riseup.net>
sub rsa2048/0x0282E4E0C8F56C94 2020-06-23 [S] [expires: 2020-12-20]
sub rsa2048/0x44ADFA83E76BD9F5 2020-06-23 [E] [expires: 2020-12-20]
sub rsa2048/0xCA1E0E95A87E21A2 2020-06-23 [A] [expires: 2020-12-20]
```
[CE1782624600EE98764C6D9CCB8FC772D1AA1D30](/uploads/43e2879bc78397b19fb560f2b967e485/CE1782624600EE98764C6D9CCB8FC772D1AA1D30)
Thanks.anarcatanarcat