Feed of "Codeberg" https://codeberg.org/Codeberg <p dir="auto">Codeberg is a non-profit, community-led effort that provides Git hosting and other services for free and open source projects.</p>
Sun, 07 Jun 2026 19:15:14 +0200 miversen33 commented on issue Codeberg/Community#1342 https://codeberg.org/Codeberg/Community/issues/1342#issuecomment-16770806 I can't see a way to delete a branch or repository <blockquote> <p dir="auto">Now you can delete it by Codeberge&#39;s UI, I think. I done it with branch &gt; click the <span class="emoji" aria-label="wastebasket" data-alias="wastebasket">🗑️</span> to delete the branch you want.</p> </blockquote>

Now you can delete it by Codeberge's UI, I think. I done it with branch > click the 🗑️ to delete the branch you want.

]]> miversen33 151509551: https://codeberg.org/Codeberg/Community/issues/1342#issuecomment-16770806
Sun, 07 Jun 2026 18:39:39 +0200 whitequark commented on issue Codeberg/Community#2370 https://codeberg.org/Codeberg/Community/issues/2370#issuecomment-16754030 Ask for advice/discussion: Documentation for Hugo websites on Codeberg Pages <p dir="auto">That depends on whether you are publishing via <code>pages</code> branch and webhook (<code>_git-pages-repository</code>) or via Forgejo Actions (<code>_git-pages-forge-allowlist</code>).</p> That depends on whether you are publishing via pages branch and webhook (_git-pages-repository) or via Forgejo Actions (_git-pages-forge-allowlist). ]]> whitequark 151414250: https://codeberg.org/Codeberg/Community/issues/2370#issuecomment-16754030 Sun, 07 Jun 2026 15:10:33 +0200 benjaoming commented on issue Codeberg/Community#1323 https://codeberg.org/Codeberg/Community/issues/1323#issuecomment-16748978 Migration from GitHub fails with Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction <p dir="auto">While failing 3 times, I noticed it always failed at the last step: Importing GitHub Pull Requests. <strong>After restarting and de-selecting Pull Requests, the migration succeeded</strong>. I was migrating <a href="https://github.com/django-money/django-money/" rel="nofollow">https://github.com/django-money/django-money/</a></p> While failing 3 times, I noticed it always failed at the last step: Importing GitHub Pull Requests. After restarting and de-selecting Pull Requests, the migration succeeded. I was migrating https://github.com/django-money/django-money/ ]]> benjaoming 151383089: https://codeberg.org/Codeberg/Community/issues/1323#issuecomment-16748978 Sun, 07 Jun 2026 13:52:53 +0200 benjaoming commented on issue Codeberg/Community#1323 https://codeberg.org/Codeberg/Community/issues/1323#issuecomment-16745009 Migration from GitHub fails with Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction <p dir="auto">Migrating now and hit the issue twice. Since the UI&#39;s recommendation is to <em>retry</em>, I&#39;m now retrying for the 3rd time but also decided to try searching for more help on the deadlock issue (update: 3rd time also failed <code>database deadlock occurred: Error 1205 (HY000): Lock wait timeout exceeded; try restarting transaction</code>)</p> <p dir="auto">I found this thread, and now I see that maybe I shouldn&#39;t try to do the migration on a Sunday at 12 UTC <span class="emoji" aria-label="thumbs up" data-alias="+1">👍</span></p> <p dir="auto">This made me wonder: Could Codeberg provide user guidance, for instance to avoid migrating issues+PRs on larger repos during busy hours? In this case, I was migrating a repo with ~300 issues. Since I just retried it, that would probably exacerbate performance issues?</p> <p dir="auto">Screenshot of where the message could be added?</p> <p dir="auto"><a href="/Codeberg/Community/attachments/2feee13b-e2ed-4dff-aed9-57d0c03c4fdb" target="_blank" rel="nofollow noopener"><img src="/Codeberg/Community/attachments/2feee13b-e2ed-4dff-aed9-57d0c03c4fdb" alt="image" loading="lazy"/></a></p> Migrating now and hit the issue twice. Since the UI's recommendation is to retry, I'm now retrying for the 3rd time but also decided to try searching for more help on the deadlock issue (update: 3rd time also failed database deadlock occurred: Error 1205 (HY000): Lock wait timeout exceeded; try restarting transaction)

I found this thread, and now I see that maybe I shouldn't try to do the migration on a Sunday at 12 UTC 👍

This made me wonder: Could Codeberg provide user guidance, for instance to avoid migrating issues+PRs on larger repos during busy hours? In this case, I was migrating a repo with ~300 issues. Since I just retried it, that would probably exacerbate performance issues?

Screenshot of where the message could be added?

image

]]> benjaoming 151379060: https://codeberg.org/Codeberg/Community/issues/1323#issuecomment-16745009 Sun, 07 Jun 2026 13:40:06 +0200 2904 commented on issue Codeberg/Community#2370 https://codeberg.org/Codeberg/Community/issues/2370#issuecomment-16742405 Ask for advice/discussion: Documentation for Hugo websites on Codeberg Pages <p dir="auto">Hi everyone!</p> Hi everyone! ]]> 2904 151374416: https://codeberg.org/Codeberg/Community/issues/2370#issuecomment-16742405 Sun, 07 Jun 2026 13:27:35 +0200 kada49 commented on issue Codeberg/Community#2732 https://codeberg.org/Codeberg/Community/issues/2732#issuecomment-16736600 Force-push and new commit on repo did not update pull request <p dir="auto">Correction: a ci-run is started, but the pr does not show that (<a href="https://codeberg.org/ziglang/zig/actions/runs/4322/jobs/0/attempt/1" rel="nofollow">https://codeberg.org/ziglang/zig/actions/runs/4322/jobs/0/attempt/1</a>)</p> Correction: a ci-run is started, but the pr does not show that (https://codeberg.org/ziglang/zig/actions/runs/4322/jobs/0/attempt/1) ]]> kada49 151300523: https://codeberg.org/Codeberg/Community/issues/2732#issuecomment-16736600 Sun, 07 Jun 2026 11:11:40 +0200 kada49 opened issue Codeberg/Community#2732 https://codeberg.org/Codeberg/Community/issues/2732 2732#Force-push on repo did not update pull request# Comment

I wanted to update a pr on for ziglang/zig, because it needed a rebase and did that. The pr: ziglang/zig#35470

Problem:
My repository (https://codeberg.org/kada49/zig/src/branch/array_hash_map_deprecation_rename) got updated, but the pr did not pick up the changes. I also added a new commit (empty because I didn't want to add unwanted changes) and still the pr did not update.

If you check the pr, no new actions/ci-runs were triggered, still shows up as conflicting and the code did not change. When clicking on the link, that should link to the repo where the changes come from, it shows the correct changes

]]> kada49 151291820: https://codeberg.org/Codeberg/Community/issues/2732 Sun, 07 Jun 2026 10:53:09 +0200 octylFractal created pull request Codeberg/Documentation#801 https://codeberg.org/Codeberg/Documentation/pulls/801 801#Change his/her & his to their in licensing.md# This is consistent with the rest of the document and is more inclusive. ]]> octylFractal 151164602: https://codeberg.org/Codeberg/Documentation/pulls/801 Sun, 07 Jun 2026 05:28:13 +0200 tad-lispy opened issue Codeberg/Community#2731 https://codeberg.org/Codeberg/Community/issues/2731 2731#SSH connection randomly dropped when using FIDO2 hardware key# Comment

Thank you for all your hard work. Codeberg is a delightful platform to use.

I'm trying to use FIDO2 hardware security key with a resident ECDSA key. With Codeberg it sometimes works, but about 80% of times I'm getting the following result.

$ ssh -T [email protected]
Confirm user presence for key ECDSA-SK SHA256:+CireGF53/LD+qzFZqWP76F/PlWvOrU5glqFQ9YtPaw
Enter PIN for ECDSA-SK key /home/tad/.ssh/id_ecdsa_sk_rk:
Confirm user presence for key ECDSA-SK SHA256:+CireGF53/LD+qzFZqWP76F/PlWvOrU5glqFQ9YtPaw
User presence confirmed
Connection closed by 217.197.84.140 port 22

I've tried

  • 3 different computers (two Linux laptops and a Mac),
  • two different hardware keys (same model),
  • different networks,
  • two different Codeberg accounts.

The same setup works flawlessly with other SSH servers, including GitHub. Other, file based keys work flawlessly with Codeberg, including a software ECDSA key.

So it seems that only the combination of my FIDO2 key and Codeberg that produces the problem. If I try 10 times, about twice it works. I don't see any other pattern. Sometimes it works the first time, sometimes after many trials.

My issue seems similar to #2297, but it's not predictable like in their case, and setting up SSH multiplexing does not solve it.

Below is a diff between successful and prematurely closed connection. The only difference that stands out to me is reply len (128 when okay, 127 when fails).

--- connection-closed.txt	2026-06-06 23:21:54.734549458 +0200
+++ connection-ok.txt	2026-06-06 23:22:21.942884723 +0200
@@ -1,183 +1,323 @@
 $ ssh -i /home/tad/.ssh/id_ecdsa_sk_rk [email protected] -o IdentitiesOnly=yes -o IdentityAgent=none -vvvv
 debug1: OpenSSH_10.3p1, OpenSSL 3.6.2 7 Apr 2026
 debug3: Running on Linux 7.0.10 #1-NixOS SMP PREEMPT_DYNAMIC Sat May 23 11:09:44 UTC 2026 x86_64
 debug3: Started with: /run/current-system/sw/bin/ssh -i /home/tad/.ssh/id_ecdsa_sk_rk [email protected] -o IdentitiesOnly=yes -o IdentityAgent=none -vvvv
 debug1: Reading configuration data /home/tad/.ssh/config
 debug1: /home/tad/.ssh/config line 8: Applying options for codeberg.org
 debug1: Reading configuration data /etc/ssh/ssh_config
 debug1: /etc/ssh/ssh_config line 2: Applying options for *
 debug3: /etc/ssh/ssh_config line 5: Including file /nix/store/a8avqfxd649rfgfpqldja6v38ljb8fj5-systemd-260.1/lib/systemd/ssh_config.d/20-systemd-ssh-proxy.conf depth 0
 debug1: Reading configuration data /nix/store/a8avqfxd649rfgfpqldja6v38ljb8fj5-systemd-260.1/lib/systemd/ssh_config.d/20-systemd-ssh-proxy.conf
 debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/tad/.ssh/known_hosts'
 debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/tad/.ssh/known_hosts2'
 debug1: auto-mux: Trying existing master at '/home/tad/.ssh/sockets/[email protected]'
 debug1: Control socket "/home/tad/.ssh/sockets/[email protected]" does not exist
 debug2: resolving "codeberg.org" port 22
 debug3: resolve_host: lookup codeberg.org:22
 debug3: channel_clear_timeouts: clearing
 debug3: ssh_connect_direct: entering
 debug1: Connecting to codeberg.org [217.197.84.140] port 22.
 debug3: set_sock_tos: set socket 3 IP_TOS 0xb8
 debug1: Connection established.
 debug1: loaded pubkey from /home/tad/.ssh/id_ecdsa_sk_rk: ECDSA-SK SHA256:+CireGF53/LD+qzFZqWP76F/PlWvOrU5glqFQ9YtPaw
 debug1: identity file /home/tad/.ssh/id_ecdsa_sk_rk type 6
 debug1: no identity pubkey loaded from /home/tad/.ssh/id_ecdsa_sk_rk
 debug1: loaded pubkey from /home/tad/.ssh/id_ecdsa_sk_rk: ECDSA-SK SHA256:+CireGF53/LD+qzFZqWP76F/PlWvOrU5glqFQ9YtPaw
 debug1: identity file /home/tad/.ssh/id_ecdsa_sk_rk type 6
 debug1: no identity pubkey loaded from /home/tad/.ssh/id_ecdsa_sk_rk
 debug1: Local version string SSH-2.0-OpenSSH_10.3
 debug1: Remote protocol version 2.0, remote software version OpenSSH_10.0p2 Debian-7+deb13u4
 debug1: compat_banner: match: OpenSSH_10.0p2 Debian-7+deb13u4 pat OpenSSH* compat 0x04000000
 debug2: fd 3 setting O_NONBLOCK
 debug1: Authenticating to codeberg.org:22 as 'git'
 debug3: record_hostkey: found key type ED25519 in file /home/tad/.ssh/known_hosts:203
 debug3: record_hostkey: found key type RSA in file /home/tad/.ssh/known_hosts:204
 debug3: record_hostkey: found key type ECDSA in file /home/tad/.ssh/known_hosts:205
 debug3: load_hostkeys_file: loaded 3 keys from codeberg.org
 debug1: load_hostkeys: fopen /home/tad/.ssh/known_hosts2: No such file or directory
 debug3: order_hostkeyalgs: have matching best-preference key type [email protected], using HostkeyAlgorithms verbatim
 debug3: send packet: type 20
 debug1: SSH2_MSG_KEXINIT sent
 debug3: receive packet: type 20
 debug1: SSH2_MSG_KEXINIT received
 debug2: local client KEXINIT proposal
 debug2: KEX algorithms: mlkem768x25519-sha256,sntrup761x25519-sha512,[email protected],curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c,[email protected]
 debug2: host key algorithms: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected],[email protected],rsa-sha2-512,rsa-sha2-256
 debug2: ciphers ctos: [email protected],[email protected],[email protected],aes128-ctr,aes192-ctr,aes256-ctr
 debug2: ciphers stoc: [email protected],[email protected],[email protected],aes128-ctr,aes192-ctr,aes256-ctr
 debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
 debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
 debug2: compression ctos: none,[email protected]
 debug2: compression stoc: none,[email protected]
 debug2: languages ctos:
 debug2: languages stoc:
 debug2: first_kex_follows 0
 debug2: reserved 0
 debug2: peer server KEXINIT proposal
 debug2: KEX algorithms: mlkem768x25519-sha256,sntrup761x25519-sha512,[email protected],curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,ext-info-s,[email protected]
 debug2: host key algorithms: rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519
 debug2: ciphers ctos: [email protected],[email protected],[email protected],aes128-ctr,aes192-ctr,aes256-ctr
 debug2: ciphers stoc: [email protected],[email protected],[email protected],aes128-ctr,aes192-ctr,aes256-ctr
 debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
 debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
 debug2: compression ctos: none,[email protected]
 debug2: compression stoc: none,[email protected]
 debug2: languages ctos:
 debug2: languages stoc:
 debug2: first_kex_follows 0
 debug2: reserved 0
 debug3: kex_choose_conf: will use strict KEX ordering
 debug1: kex: algorithm: mlkem768x25519-sha256
 debug1: kex: host key algorithm: ssh-ed25519
 debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: none
 debug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: none
 debug3: send packet: type 30
 debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
 debug3: receive packet: type 31
 debug1: SSH2_MSG_KEX_ECDH_REPLY received
 debug1: Server host key: ssh-ed25519 SHA256:mIlxA9k46MmM6qdJOdMnAQpzGxF4WIVVL+fj+wZbw0g
 debug3: record_hostkey: found key type ED25519 in file /home/tad/.ssh/known_hosts:203
 debug3: record_hostkey: found key type RSA in file /home/tad/.ssh/known_hosts:204
 debug3: record_hostkey: found key type ECDSA in file /home/tad/.ssh/known_hosts:205
 debug3: load_hostkeys_file: loaded 3 keys from codeberg.org
 debug1: load_hostkeys: fopen /home/tad/.ssh/known_hosts2: No such file or directory
 debug1: Host 'codeberg.org' is known and matches the ED25519 host key.
 debug1: Found key in /home/tad/.ssh/known_hosts:203
 debug3: send packet: type 21
 debug1: ssh_packet_send2_wrapped: resetting send seqnr 3
 debug2: ssh_set_newkeys: mode 1
 debug1: rekey out after 134217728 blocks
 debug1: SSH2_MSG_NEWKEYS sent
 debug1: Sending SSH2_MSG_EXT_INFO
 debug3: send packet: type 7
 debug1: expecting SSH2_MSG_NEWKEYS
 debug3: receive packet: type 21
 debug1: ssh_packet_read_poll2: resetting read seqnr 3
 debug1: SSH2_MSG_NEWKEYS received
 debug2: ssh_set_newkeys: mode 0
 debug1: rekey in after 134217728 blocks
 debug2: KEX algorithms: mlkem768x25519-sha256,sntrup761x25519-sha512,[email protected],curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c,[email protected]
 debug2: host key algorithms: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected],[email protected],rsa-sha2-512,rsa-sha2-256
 debug2: ciphers ctos: [email protected],[email protected],[email protected],aes128-ctr,aes192-ctr,aes256-ctr
 debug2: ciphers stoc: [email protected],[email protected],[email protected],aes128-ctr,aes192-ctr,aes256-ctr
 debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
 debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
 debug2: compression ctos: none,[email protected]
 debug2: compression stoc: none,[email protected]
 debug2: languages ctos:
 debug2: languages stoc:
 debug2: first_kex_follows 0
 debug2: reserved 0
 debug3: send packet: type 5
 debug3: receive packet: type 7
 debug1: SSH2_MSG_EXT_INFO received
 debug3: kex_input_ext_info: extension server-sig-algs
 debug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected],rsa-sha2-512,rsa-sha2-256>
 debug3: kex_input_ext_info: extension [email protected]
 debug1: kex_ext_info_check_ver: [email protected]=<0>
 debug3: kex_input_ext_info: extension [email protected]
 debug1: kex_ext_info_check_ver: [email protected]=<0>
 debug3: receive packet: type 6
 debug2: service_accept: ssh-userauth
 debug1: SSH2_MSG_SERVICE_ACCEPT received
 debug3: send packet: type 50
 debug3: receive packet: type 7
 debug1: SSH2_MSG_EXT_INFO received
 debug3: kex_input_ext_info: extension server-sig-algs
 debug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected],rsa-sha2-512,rsa-sha2-256>
 debug3: receive packet: type 51
 debug1: Authentications that can continue: publickey
 debug3: start over, passed a different list publickey
 debug3: preferred publickey
 debug3: authmethod_lookup publickey
 debug3: remaining preferred:
 debug3: authmethod_is_enabled publickey
 debug1: Next authentication method: publickey
 debug1: Will attempt key: /home/tad/.ssh/id_ecdsa_sk_rk ECDSA-SK SHA256:+CireGF53/LD+qzFZqWP76F/PlWvOrU5glqFQ9YtPaw explicit authenticator
 debug1: Will attempt key: /home/tad/.ssh/id_ecdsa_sk_rk ECDSA-SK SHA256:+CireGF53/LD+qzFZqWP76F/PlWvOrU5glqFQ9YtPaw explicit authenticator
 debug2: pubkey_prepare: done
 debug1: Offering public key: /home/tad/.ssh/id_ecdsa_sk_rk ECDSA-SK SHA256:+CireGF53/LD+qzFZqWP76F/PlWvOrU5glqFQ9YtPaw explicit authenticator
 debug3: send packet: type 50
 debug2: we sent a publickey packet, wait for reply
 debug3: receive packet: type 60
 debug1: Server accepts key: /home/tad/.ssh/id_ecdsa_sk_rk ECDSA-SK SHA256:+CireGF53/LD+qzFZqWP76F/PlWvOrU5glqFQ9YtPaw explicit authenticator
 debug3: sign_and_send_pubkey: using [email protected] with ECDSA-SK SHA256:+CireGF53/LD+qzFZqWP76F/PlWvOrU5glqFQ9YtPaw
 debug3: sign_and_send_pubkey: signing using [email protected] SHA256:+CireGF53/LD+qzFZqWP76F/PlWvOrU5glqFQ9YtPaw
 Confirm user presence for key ECDSA-SK SHA256:+CireGF53/LD+qzFZqWP76F/PlWvOrU5glqFQ9YtPaw
-debug3: start_helper: started pid=87786
-debug3: ssh_msg_send: type 5 len 535
+debug3: start_helper: started pid=88110
 debug1: start_helper: starting /nix/store/mpzrhvrkdzkajhgay1dngqpf062vb1iq-openssh-10.3p1/libexec/ssh-sk-helper
+debug3: ssh_msg_send: type 5 len 535
 debug3: ssh_msg_send: done
 debug3: ssh_msg_recv entering
 debug1: process_sign: ready to sign with key ECDSA-SK, provider internal: msg len 326, compat 0x4000000
 debug1: sshsk_sign: provider "internal", key ECDSA-SK, flags 0x25
 debug1: sk_probe: 1 device(s) detected
 debug1: sk_probe: selecting sk by touch
 debug1: check_sk_options: option uv is unknown
 debug1: ssh_sk_sign: check_sk_options uv
 debug1: sshsk_sign: sk_sign failed with code -3
 debug1: ssh-sk-helper: Signing failed: incorrect passphrase supplied to decrypt private key
 debug1: main: reply len 8
 debug3: ssh_msg_send: type 5 len 8
 debug3: ssh_msg_send: done
 debug1: client_converse: helper returned error -43
-debug3: reap_helper: pid=87786
+debug3: reap_helper: pid=88110
 debug1: identity_sign: sshkey_sign: incorrect passphrase supplied to decrypt private key
 Enter PIN for ECDSA-SK key /home/tad/.ssh/id_ecdsa_sk_rk:
 Confirm user presence for key ECDSA-SK SHA256:+CireGF53/LD+qzFZqWP76F/PlWvOrU5glqFQ9YtPaw
-debug3: start_helper: started pid=87803
+debug3: start_helper: started pid=88117
 debug1: start_helper: starting /nix/store/mpzrhvrkdzkajhgay1dngqpf062vb1iq-openssh-10.3p1/libexec/ssh-sk-helper
 debug3: ssh_msg_send: type 5 len 557
 debug3: ssh_msg_send: done
 debug3: ssh_msg_recv entering
 debug1: process_sign: ready to sign with key ECDSA-SK, provider internal: msg len 326, compat 0x4000000
 debug1: sshsk_sign: provider "internal", key ECDSA-SK, flags 0x25 with-pin
 debug1: sk_probe: 1 device(s) detected
 debug1: sk_probe: selecting sk by touch
-debug1: main: reply len 127
-debug3: ssh_msg_send: type 5 len 127
+debug1: main: reply len 128
+debug3: ssh_msg_send: type 5 len 128
 debug3: ssh_msg_send: done
-debug3: reap_helper: pid=87803
+debug3: reap_helper: pid=88117
 User presence confirmed
 debug3: send packet: type 50
-Connection closed by 217.197.84.140 port 22
+debug3: receive packet: type 52
+Authenticated to codeberg.org ([217.197.84.140]:22) using "publickey".
+debug1: setting up multiplex master socket
+debug3: muxserver_listen: temporary control path /home/tad/.ssh/sockets/[email protected]
+debug2: fd 4 setting O_NONBLOCK
+debug3: fd 4 is O_NONBLOCK
+debug3: fd 4 is O_NONBLOCK
+debug1: channel 0: new mux listener [/home/tad/.ssh/sockets/[email protected]] (inactive timeout: 0)
+debug3: muxserver_listen: mux listener channel 0 fd 4
+debug1: control_persist_detach: backgrounding master process
+debug2: control_persist_detach: background process is 88122
+debug2: fd 4 setting O_NONBLOCK
+debug1: forking to background
+debug1: Entering interactive session.
+debug1: pledge: id
+debug3: client_repledge: enter
+debug2: set_control_persist_exit_time: schedule exit in 600 seconds
+debug1: multiplexing control connection
+debug2: fd 5 setting O_NONBLOCK
+debug3: fd 5 is O_NONBLOCK
+debug1: channel 1: new mux-control [mux-control] (inactive timeout: 0)
+debug3: channel_post_mux_listener: new mux channel 1 fd 5
+debug3: mux_master_read_cb: channel 1: hello sent
+debug3: receive packet: type 80
+debug1: client_input_global_request: rtype [email protected] want_reply 0
+debug3: client_input_hostkeys: received RSA key SHA256:6QQmYi4ppFS4/+zSZ5S4IU+4sa6rwvQ4PbhCtPEBekQ
+debug3: client_input_hostkeys: received ECDSA key SHA256:T9FYDEHELhVkulEKKwge5aVhVTbqCW0MIRwAfpARs/E
+debug3: client_input_hostkeys: received ED25519 key SHA256:mIlxA9k46MmM6qdJOdMnAQpzGxF4WIVVL+fj+wZbw0g
+debug1: client_input_hostkeys: searching /home/tad/.ssh/known_hosts for codeberg.org / (none)
+debug3: hostkeys_foreach: reading file "/home/tad/.ssh/known_hosts"
+debug3: hostkeys_find: found ssh-ed25519 key at /home/tad/.ssh/known_hosts:203
+debug3: hostkeys_find: found ssh-rsa key at /home/tad/.ssh/known_hosts:204
+debug3: hostkeys_find: found ecdsa-sha2-nistp256 key at /home/tad/.ssh/known_hosts:205
+debug1: client_input_hostkeys: searching /home/tad/.ssh/known_hosts2 for codeberg.org / (none)
+debug1: client_input_hostkeys: hostkeys file /home/tad/.ssh/known_hosts2 does not exist
+debug3: client_input_hostkeys: 3 server keys: 0 new, 3 retained, 0 incomplete match. 0 to remove
+debug1: client_input_hostkeys: no new or deprecated keys from server
+debug3: client_repledge: enter
+debug3: receive packet: type 4
+debug1: Remote: /usr/local/bin/forgejo --config /etc/forgejo/conf/app.ini keys -u %u -t %t -k %k:2: key options: command
+debug3: receive packet: type 4
+debug1: Remote: /usr/local/bin/forgejo --config /etc/forgejo/conf/app.ini keys -u %u -t %t -k %k:2: key options: command
+debug2: set_control_persist_exit_time: cancel scheduled exit
+debug3: mux_master_read_cb: channel 1 packet type 0x00000001 len 4
+debug2: mux_master_process_hello: channel 1 client version 4
+debug2: mux_client_hello_exchange: master version 4
+debug1: Received 'info' extension
+debug3: mux_client_forwards: request forwardings: 0 local, 0 remote
+debug3: mux_client_request_session: entering
+debug3: mux_client_request_alive: entering
+debug3: mux_master_read_cb: channel 1 packet type 0x10000004 len 4
+debug2: mux_master_process_alive_check: channel 1: alive check
+debug3: mux_client_request_alive: done pid = 88124
+debug3: mux_master_read_cb: channel 1 packet type 0x10000002 len 49
+debug3: mux_client_request_session: session request sent
+debug2: mux_master_process_new_session: channel 1: request tty 1, X 0, agent 0, subsys 0, term "tmux-256color", cmd "", env 0
+debug3: mux_master_process_new_session: got fds stdin 6, stdout 7, stderr 8
+debug1: channel 2: new session [client-session] (inactive timeout: 0)
+debug2: mux_master_process_new_session: channel_new: 2 linked to control channel 1
+debug2: channel 2: send open
+debug3: send packet: type 90
+debug2: client_loop: session QoS is now interactive
+debug2: fd 3 setting TCP_NODELAY
+debug3: set_sock_tos: set socket 3 IP_TOS 0xb8
+debug3: receive packet: type 91
+debug2: channel_input_open_confirmation: channel 2: callback start
+debug2: client_session2_setup: id 2
+debug2: channel 2: request pty-req confirm 1
+debug3: send packet: type 98
+debug2: channel 2: request shell confirm 1
+debug3: send packet: type 98
+debug3: client_repledge: enter
+debug3: mux_session_confirm: sending success reply
+debug2: channel_input_open_confirmation: channel 2: callback done
+debug2: channel 2: open confirm rwindow 0 rmax 32768
+debug1: mux_client_request_session: master session id: 2
+debug3: receive packet: type 100
+debug2: channel_input_status_confirm: type 100 id 2
+debug3: client_status_confirm: channel 2: mux request: PTY allocation
+debug3: mux_tty_alloc_failed: channel 2: TTY alloc failed
+debug2: channel 2: rcvd adjust 2097152
+debug3: receive packet: type 99
+debug2: channel_input_status_confirm: type 99 id 2
+debug2: shell request accepted on channel 2
+PTY allocation request failed
+debug2: channel 2: written 31 to efd 8
+debug3: receive packet: type 96
+debug2: channel 2: rcvd eof
+debug2: channel 2: output open -> drain
+debug3: receive packet: type 98
+debug1: client_input_channel_req: channel 2 rtype exit-status reply 0
+debug3: mux_exit_message: channel 2: exit message, exitval 0
+debug3: receive packet: type 98
+debug1: client_input_channel_req: channel 2 rtype [email protected] reply 0
+debug2: channel 2: rcvd eow
+debug2: chan_shutdown_read: channel 2: (i0 o1 sock -1 wfd 6 efd 8 [write])
+debug2: channel 2: input open -> closed
+debug3: receive packet: type 97
+debug2: channel 2: rcvd close
+debug3: channel 2: will not send data after close
+Hi there, tad-lispy! You've successfully authenticated with the key named K9, but Forgejo does not provide shell access.
+If this is unexpected, please log in with password and setup Forgejo under another user.
+debug3: channel 2: will not send data after close
+debug2: channel 2: obuf empty
+debug2: chan_shutdown_write: channel 2: (i3 o1 sock -1 wfd 7 efd 8 [write])
+debug2: channel 2: output drain -> closed
+debug2: channel 2: send_close2
+debug2: channel 2: send close for remote id 0
+debug3: send packet: type 97
+debug2: channel 2: is dead
+debug2: channel 2: gc: notify user
+debug3: mux_master_session_cleanup_cb: entering for channel 2
+debug2: channel 1: rcvd close
+debug2: channel 1: output open -> drain
+debug2: chan_shutdown_read: channel 1: (i0 o1 sock 5 wfd 5 efd -1 [closed])
+debug2: channel 1: input open -> closed
+debug2: channel 2: gc: user detached
+debug2: channel 2: is dead
+debug2: channel 2: garbage collecting
+debug1: channel 2: free: client-session, nchannels 3
+debug3: channel 2: status: The following connections are open:
+  #1 mux-control (t16 [mux-control] nr0 m0 i3/0 o1/0 e[closed]/0 fd 5/5/-1 sock 5 cc -1 nc0 io 0x01/0x00 I)
+  #2 client-session (t4 [session] r0 nm0 i3/0 o3/0 e[write]/0 fd -1/-1/8 sock -1 cc -1 nc0 io 0x00/0x00 RTI)
+
+debug2: channel 1: obuf empty
+debug2: chan_shutdown_write: channel 1: (i3 o1 sock 5 wfd 5 efd -1 [closed])
+debug2: channel 1: output drain -> closed
+debug2: channel 1: is dead (local)
+debug2: channel 1: gc: notify user
+debug3: mux_master_control_cleanup_cb: entering for channel 1
+debug2: channel 1: gc: user detached
+debug2: channel 1: is dead (local)
+debug2: channel 1: garbage collecting
+debug1: channel 1: free: mux-control, nchannels 2
+debug3: mux_client_read_packet_timeout: read header failed: Broken pipe
+debug2: Received exit status from master 0
+debug3: channel 1: status: The following connections are open:
+  #1 mux-control (t16 [mux-control] nr0 nm0 i3/0 o3/0 e[closed]/0 fd 5/5/-1 sock 5 cc -1 nc0 io 0x00/0x00 I)
+
+Shared connection to codeberg.org closed.
+debug2: set_control_persist_exit_time: schedule exit in 600 seconds

Please let me know if I can provide any more useful information.

]]> tad-lispy 151073879: https://codeberg.org/Codeberg/Community/issues/2731 Sun, 07 Jun 2026 00:02:50 +0200 DontBlameMe opened issue Codeberg/Community#2730 https://codeberg.org/Codeberg/Community/issues/2730 2730#HEAD.lock present & repo taking unnecessary space# Comment

Hey. I have two problems:

  • I have managed to lock up my repository (with a HEAD.lock present) ._. I am so sorry and have no idea why 😭
    its at https://codeberg.org/DontBlameMe/project_templates and tells me: The database representation of this repository is out of synchronization. If this warning is still shown after pushing a commit to this repository contact the administrator.
  • My other repo (Wallpapers, found at https://codeberg.org/DontBlameMe/Wallpapers) has 1.2gib in size, because old things havent been garbage collected yet (at least thats my assumption?). I previously had these wallpapers unarchived and force-pushed to get rid of it. Is this also something an admin needs to start manually? When cloning it I have a total disk usage of 293mb - which I think would be okay - or is this overall something that should not be hosted here?

Thank you so much for your time :)

]]> DontBlameMe 151006613: https://codeberg.org/Codeberg/Community/issues/2730 Sat, 06 Jun 2026 21:20:15 +0200 chr_56 opened issue Codeberg/Community#2729 https://codeberg.org/Codeberg/Community/issues/2729 2729#Repository `PhonographPlus/Phonograph_Plus` was file locked (HEAD.lock)# Comment

It seems that repository PhonographPlus/Phonograph_Plus got a file write lock in git. (forgejo service process died once?)

This is what I see on pushing

remote: error: cannot lock ref 'HEAD': Unable to create '/mnt/ceph-cluster/git/gitea-repositories/phonographplus/phonograph_plus.git/./HEAD.lock': File exists.        
remote: 
remote: Another git process seems to be running in this repository, e.g.        
remote: an editor opened by 'git commit'. Please make sure all processes        
remote: are terminated then try again. If it still fails, a git process        
remote: may have crashed in this repository earlier:        
remote: remove the file manually to continue.

The Web UI says:

The database representation of this repository is out of synchronization. If this warning is still shown after pushing a commit to this repository contact the administrator.
]]> chr_56 150844478: https://codeberg.org/Codeberg/Community/issues/2729 Sat, 06 Jun 2026 15:34:53 +0200 ede1998 commented on issue Codeberg/Community#2726 https://codeberg.org/Codeberg/Community/issues/2726#issuecomment-16669076 Consistent 500 error on compare link when logged out <p dir="auto">Thanks for this issue. Gave me the workaround I needed:</p> Thanks for this issue. Gave me the workaround I needed: ]]> ede1998 150742853: https://codeberg.org/Codeberg/Community/issues/2726#issuecomment-16669076 Sat, 06 Jun 2026 11:27:35 +0200 mrichling closed issue Codeberg/Community#2717 https://codeberg.org/Codeberg/Community/issues/2717#issuecomment-16640270 Erbeten der Freischaltung der Pages-Funktion mrichling 150503432: https://codeberg.org/Codeberg/Community/issues/2717#issuecomment-16640270 Fri, 05 Jun 2026 22:40:48 +0200 mrichling commented on issue Codeberg/Community#2717 https://codeberg.org/Codeberg/Community/issues/2717#issuecomment-16640267 Erbeten der Freischaltung der Pages-Funktion <p dir="auto">Fehlalarm, die Seite läuft einwandfrei unter der Pages-Adresse. Das Problem lag an meiner lokalen Konfiguration und nicht an der Plattform selbst. Ich schließe das Issue hiermit.</p> Fehlalarm, die Seite läuft einwandfrei unter der Pages-Adresse. Das Problem lag an meiner lokalen Konfiguration und nicht an der Plattform selbst. Ich schließe das Issue hiermit. ]]> mrichling 150503426: https://codeberg.org/Codeberg/Community/issues/2717#issuecomment-16640267 Fri, 05 Jun 2026 22:40:48 +0200 abekonge opened issue Codeberg/Community#2727 https://codeberg.org/Codeberg/Community/issues/2727 2727#Downloading release tar.gz with cURL does not work# Comment

We use cURL for install of Lichen-markdown: https://codeberg.org/ukrudt.net/lichen-markdown

But when trying to download the latest release with cURL:

curl https://codeberg.org/ukrudt.net/lichen-markdown/archive/v1.5.0.tar.gz --output test.tar.gz

we get a html page with 500 or 504.

While going to the same url with a browser works just fine.

]]> abekonge 150454469: https://codeberg.org/Codeberg/Community/issues/2727 Fri, 05 Jun 2026 20:56:23 +0200 alexjyong commented on issue Codeberg/Community#2634 https://codeberg.org/Codeberg/Community/issues/2634#issuecomment-16632647 Codespaces: can we please revisit #272? <p dir="auto">I&#39;m all for this. Codespaces is super useful with Github, and I&#39;d love to see something like Codeberg have it.</p> I'm all for this. Codespaces is super useful with Github, and I'd love to see something like Codeberg have it. ]]> alexjyong 150434318: https://codeberg.org/Codeberg/Community/issues/2634#issuecomment-16632647 Fri, 05 Jun 2026 20:25:05 +0200 kaeru commented on issue Codeberg/Community#2596 https://codeberg.org/Codeberg/Community/issues/2596#issuecomment-16624538 500/504 server error creating issues/PR, commenting etc. <p dir="auto"><a href="/Gusted" class="mention" rel="nofollow">@Gusted</a> wrote in <a href="https://codeberg.org/Codeberg/Community/issues/2596#issuecomment-15800714" class="ref-issue" rel="nofollow">#2596 (comment)</a>:</p> @Gusted wrote in #2596 (comment): ]]> kaeru 150349385: https://codeberg.org/Codeberg/Community/issues/2596#issuecomment-16624538 Fri, 05 Jun 2026 17:45:55 +0200 evrix commented on issue Codeberg/Community#2718 https://codeberg.org/Codeberg/Community/issues/2718#issuecomment-16624469 stuck on stale lock file <p dir="auto">Thanks!</p> Thanks! ]]> evrix 150348098: https://codeberg.org/Codeberg/Community/issues/2718#issuecomment-16624469 Fri, 05 Jun 2026 17:43:05 +0200 kcbanner opened issue Codeberg/Community#2726 https://codeberg.org/Codeberg/Community/issues/2726 2726#Consistent 500 error on compare link when logged out# Comment

When logged out, this link consistently gives a 500 server error: https://codeberg.org/ziglang/zig/compare/master...kcbanner/zig:coff_linker_wip

When logged in, I don't see the problem.

I noticed one difference, when I get a 200, the x-server-name header is s_forgejo_main, when it 500s (when logged out), it is s_forgejo_secondary_aburayama. Perhaps something is broken on that specific server?

Thanks!

]]> kcbanner 150293123: https://codeberg.org/Codeberg/Community/issues/2726 Fri, 05 Jun 2026 16:04:51 +0200 MarcMichel opened issue Codeberg/Community#2725 https://codeberg.org/Codeberg/Community/issues/2725 2725#Stale HEAD.lock prevents pushing to default branch — MarcMichel/Augmea# Hello Codeberg team,

Pushes to the default branch main of https://codeberg.org/MarcMichel/Augmea are rejected server-side with:

remote: error: cannot lock ref 'HEAD': Unable to create '/mnt/ceph-cluster/git/gitea-repositories/marcmichel/augmea.git/./HEAD.lock': File exists.
 ! [remote rejected] main -> main (failed to update ref)

This looks like a stale HEAD.lock left by a crashed server-side git process. Evidence it is not client-side:

  • Pushing to non-default branches works (fix/email-brevo-2026-06-03, wip/consolidation-disque-2026-06-03 pushed fine on 2026-06-03).
  • Only updates to main (touching HEAD) are rejected; the very first attempt already reported File exists, so the lock pre-existed the push.
  • Merging via the web UI fails with the same error, so the server itself can no longer write HEAD.

Could you please remove the stale lock file /mnt/ceph-cluster/git/gitea-repositories/marcmichel/augmea.git/HEAD.lock (and check other stale *.lock files, e.g. refs/heads/main.lock)?

Account: MarcMichel. Thank you!

]]> MarcMichel 150269348: https://codeberg.org/Codeberg/Community/issues/2725 Fri, 05 Jun 2026 15:17:07 +0200 momar commented on pull request Codeberg/org#1247 https://codeberg.org/Codeberg/org/pulls/1247#issuecomment-16610843 WIP: Bylaws: Add fee waiver clause <p dir="auto">We&#39;ve just discussed this and decided to replace the fee reduction with the fee waiver (German version only right now!), and reduce the obstacles to waiving fees - it is now possible to waive fees just for financial issues or just for good contributions, as well as for other reasons as well that can be decided by the executive board. Further details &amp; constraints can of course be later decided &amp; written down in the Compendium as well to make the decision process more transparent.</p> <p dir="auto">As a decision text for the assembly, we&#39;d then of course need to include what happens with reduced fee memberships; I&#39;d suggest the following here:</p> <blockquote> <p dir="auto">Der Codeberg e. V. beschließt, wie in PR 1247 (<a href="https://codeberg.org/Codeberg/org/pulls/1247" class="ref-issue" rel="nofollow">#1247</a>) festgeschrieben, den § 2 der Beitragsordnung (Ermäßigung) durch die Option der Beitragsbefreiung zu ersetzen. Alle Mitglieder, die bisher eine Ermäßigung erhalten, werden stattdessen für mindestens ein Jahr nach der neuen Regelung vom Beitrag befreit.</p> </blockquote> <hr/> <blockquote> <p dir="auto">Codeberg e. V. decides, as set forth in PR 1247 (<a href="https://codeberg.org/Codeberg/org/pulls/1247" class="ref-issue" rel="nofollow">#1247</a>), to replace Section 2 of the Membership Fee Regulations (Reductions) with the option of a membership fee waiver. All members who have previously received a reduction will instead be exempt from membership fees for at least one year under the new regulation.</p> </blockquote> We've just discussed this and decided to replace the fee reduction with the fee waiver (German version only right now!), and reduce the obstacles to waiving fees - it is now possible to waive fees just for financial issues or just for good contributions, as well as for other reasons as well that can be decided by the executive board. Further details & constraints can of course be later decided & written down in the Compendium as well to make the decision process more transparent.

As a decision text for the assembly, we'd then of course need to include what happens with reduced fee memberships; I'd suggest the following here:

Der Codeberg e. V. beschließt, wie in PR 1247 (#1247) festgeschrieben, den § 2 der Beitragsordnung (Ermäßigung) durch die Option der Beitragsbefreiung zu ersetzen. Alle Mitglieder, die bisher eine Ermäßigung erhalten, werden stattdessen für mindestens ein Jahr nach der neuen Regelung vom Beitrag befreit.

Codeberg e. V. decides, as set forth in PR 1247 (#1247), to replace Section 2 of the Membership Fee Regulations (Reductions) with the option of a membership fee waiver. All members who have previously received a reduction will instead be exempt from membership fees for at least one year under the new regulation.

]]> momar 150250964: https://codeberg.org/Codeberg/org/pulls/1247#issuecomment-16610843 Fri, 05 Jun 2026 14:44:34 +0200 laumann commented on issue Codeberg/Community#2596 https://codeberg.org/Codeberg/Community/issues/2596#issuecomment-16602983 500/504 server error creating issues/PR, commenting etc. <p dir="auto">From Gentoo&#39;s CI perspective: It&#39;s working well the majority of the time, we sometimes see a 504 but they&#39;re not that frequent. Mostly it&#39;s this error we see in the logs (fetching the list of open PRs):</p> <pre class="code-block"><code class="chroma language-text display">requests.exceptions.HTTPError: 504 Server Error: Gateway Time-out for url: https://codeberg.org/api/v1/repos/gentoo/gentoo/pulls?limit=100&amp;state=open </code></pre> From Gentoo's CI perspective: It's working well the majority of the time, we sometimes see a 504 but they're not that frequent. Mostly it's this error we see in the logs (fetching the list of open PRs): 
requests.exceptions.HTTPError: 504 Server Error: Gateway Time-out for url: https://codeberg.org/api/v1/repos/gentoo/gentoo/pulls?limit=100&state=open
]]> laumann 150159071: https://codeberg.org/Codeberg/Community/issues/2596#issuecomment-16602983 Fri, 05 Jun 2026 11:25:07 +0200 Gusted closed issue Codeberg/Community#2719 https://codeberg.org/Codeberg/Community/issues/2719#issuecomment-16582778 main ref points at an object upload-pack reports as "not our ref" after the recent outage Gusted 149984957: https://codeberg.org/Codeberg/Community/issues/2719#issuecomment-16582778 Fri, 05 Jun 2026 02:25:14 +0200 Gusted commented on issue Codeberg/Community#2719 https://codeberg.org/Codeberg/Community/issues/2719#issuecomment-16582775 main ref points at an object upload-pack reports as "not our ref" after the recent outage <p dir="auto">Hi,</p> Hi, ]]> Gusted 149984951: https://codeberg.org/Codeberg/Community/issues/2719#issuecomment-16582775 Fri, 05 Jun 2026 02:25:14 +0200 Gusted closed issue Codeberg/Community#2718 https://codeberg.org/Codeberg/Community/issues/2718#issuecomment-16582733 stuck on stale lock file Gusted 149984078: https://codeberg.org/Codeberg/Community/issues/2718#issuecomment-16582733 Fri, 05 Jun 2026 02:20:25 +0200 Gusted commented on issue Codeberg/Community#2718 https://codeberg.org/Codeberg/Community/issues/2718#issuecomment-16582730 stuck on stale lock file <p dir="auto"><a href="/evrix" class="mention" rel="nofollow">@evrix</a> your case is fixed.</p> @evrix your case is fixed. ]]> Gusted 149984072: https://codeberg.org/Codeberg/Community/issues/2718#issuecomment-16582730 Fri, 05 Jun 2026 02:20:25 +0200 Gusted closed issue Codeberg/Community#2720 https://codeberg.org/Codeberg/Community/issues/2720#issuecomment-16582727 Stale HEAD.lock prevents pushing to default branch — MarcMichel/Augmea Gusted 149983745: https://codeberg.org/Codeberg/Community/issues/2720#issuecomment-16582727 Fri, 05 Jun 2026 02:20:15 +0200 Gusted commented on issue Codeberg/Community#2720 https://codeberg.org/Codeberg/Community/issues/2720#issuecomment-16582724 Stale HEAD.lock prevents pushing to default branch — MarcMichel/Augmea <p dir="auto">Fixed.</p> Fixed. ]]> Gusted 149983739: https://codeberg.org/Codeberg/Community/issues/2720#issuecomment-16582724 Fri, 05 Jun 2026 02:20:14 +0200 Gusted closed issue Codeberg/Community#2723 https://codeberg.org/Codeberg/Community/issues/2723#issuecomment-16582583 Cannot push to server-side locked branch: Unable to create /mnt/ceph-cluster/git/gitea-repositories Gusted 149981039: https://codeberg.org/Codeberg/Community/issues/2723#issuecomment-16582583 Fri, 05 Jun 2026 02:15:27 +0200 Gusted commented on issue Codeberg/Community#2723 https://codeberg.org/Codeberg/Community/issues/2723#issuecomment-16582580 Cannot push to server-side locked branch: Unable to create /mnt/ceph-cluster/git/gitea-repositories <p dir="auto">Fixed.</p> Fixed. ]]> Gusted 149981033: https://codeberg.org/Codeberg/Community/issues/2723#issuecomment-16582580 Fri, 05 Jun 2026 02:15:27 +0200