Opened 2 years ago
Closed 2 months ago
#2822 closed task (fixed)
Upgrade tracsvn to bullseye
Reported by: | robe | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | Sysadmin Contract 2024-III (strk) |
Component: | SysAdmin | Keywords: | gitea, trac, svn |
Cc: |
Description
Tracsvn is currently at debian buster which is now oldoldstable.
Need to upgrade this to at least bullseye. Bookworm the next stable is in RC phase.
Change History (18)
comment:1 by , 23 months ago
Milestone: | Sysadmin Contract 2022-II → Sysadmin Contract 2023-I |
---|
comment:2 by , 13 months ago
Doing this should also give us Gitea support for the Agit workflow, allowing us to create pull requests directly via git push
: https://github.com/go-gitea/gitea/issues/27579#issuecomment-1765074621
comment:3 by , 13 months ago
Keywords: | gitea trac svn added |
---|
comment:4 by , 11 months ago
Milestone: | Sysadmin Contract 2023-I → Sysadmin Contract 2024-I |
---|
Moving my prior still open items to the next proposed Milestone
follow-up: 6 comment:5 by , 5 months ago
Bookworm is current stable, for the record, so we should probably go there (Debian 12)
comment:6 by , 5 months ago
Replying to strk:
Bookworm is current stable, for the record, so we should probably go there (Debian 12)
As I recall you can't skip versions, so you need to go to bullseye first and if we have to go there anyway we might as well confirm things still work before venturing to bookworm.
comment:7 by , 3 months ago
For the record: upgrade to Bookworm will give us access to Trac-1.6 via backports, see #3238
comment:8 by , 3 months ago
Yah but I think it's safer to upgrade to bullseye first and then bookworm. I'm not sure skipping upgrades is even allowed in debian. Maybe but it's not in ubuntu and I assume for good reason.
comment:10 by , 3 months ago
Upgrade went bad, I've done:
- apt update && apt upgrade
- edit /etc/apt/sources.list and /etc/apt/sources.list.d/* replacing buster with bullseyes
- apt upgrade && apt dist-upgrade
Current status, after all of the above: systemctl status
fails after 1m30s of trying, with message Failed to reload daemon: Transport endpoint is not connected
comment:11 by , 3 months ago
Purging acpi packages fixed the issue. Please test if dev.gitea.osgeo.org and dev.trac.osgeo.org work (we don't have staging svn ?)
comment:12 by , 3 months ago
We are also now running Trac-1.6 in staging https://dev.trac.osgeo.org
comment:13 by , 3 months ago
Milestone: | Sysadmin Contract 2024-I → Sysadmin Contract 2024-III (strk) |
---|
comment:14 by , 3 months ago
dev.gitea.osgeo.org my two-factor still works.
doing git clone via http works -
but git clone via ssh is failing:
git clone ssh://git@dev.git.osgeo.org:3022/postgis/postgis.git postgis-ssh
gives me 3022 connection timed out. I recall it worked last time I tried it maybe you reset the port or something.
comment:15 by , 3 months ago
Regina do you remember what did you do to fix network ? I'm also experiencing slow transfers
comment:16 by , 3 months ago
Connecting to port 3022 works from the osgeo4 host but not from the outside (where it times out).
The host proxy seems fine:
devices: proxyssh3022: connect: tcp:127.0.0.1:22 listen: tcp:140.211.15.32:3022 type: proxy
comment:17 by , 3 months ago
Found the problem: firewall on osgeo4 was not having port 3022 open. Opening that fixed the ssh clone issue. Fixed with https://git.osgeo.org/gitea/sac/ansible-deployment/commit/3f1f8cc3f00f27490414d7cf2849cfd744da77c9
comment:18 by , 2 months ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Tracsvn is now upgraded to bullseye
pushing to next milestone since my contract funds have been used.