Project

General

Profile

Actions

tickets #165710

open

Can't push to my fork of a repo

Added by Akatama 3 months ago. Updated 24 days ago.

Status:
New
Priority:
Normal
Assignee:
Category:
Pagure
Target version:
-
Start date:
2024-08-23
Due date:
2024-08-29 (about 3 months late)
% Done:

0%

Estimated time:

Description

Hey everyone,
I've been helping out the openSUSE Cloud group for a few months now, and I recently created some configuration files that I need to update on the kiwi-descriptions repo.

I created that fork last Saturday, and since then I have had the below error message. As a result, I cannot even push to my own fork, or really do anything with it. I even tried to delete it at one point but even clicking the delete button doesn't do anything.

The permissions on this repository are being updated. This may take a while. During this time, you or some of the project's contributors may not be able to push to this repository.

My fork is here: https://code.opensuse.org/fork/Akatama/project/kiwi-descriptions

I think it is mostly likely a permissions issue. I have already messaged the person is in charge of maintaining the kiwi-descriptions repo and I am waiting to hear from him.
In the meantime it was suggested to me that I create an issue here to see if this issue can be fixed.

If you have any other questions for me, please don't hesitate to ask!


Related issues 2 (1 open1 closed)

Related to openSUSE admin - tickets #166451: code.opensuse.org pagure errorNew2024-09-06

Actions
Has duplicate openSUSE admin - tickets #168478: Code.o.o needs an update?Closed2024-10-18

Actions
Actions #1

Updated by crameleon 3 months ago

  • Tracker changed from communication to tickets
  • Assignee set to Pharaoh_Atem
  • Private changed from Yes to No
Actions #2

Updated by Pharaoh_Atem 3 months ago

Unfortunately, this is known. It's caused by a bug in Leap's pygit2: https://bugzilla.opensuse.org/show_bug.cgi?id=1229570

Actions #3

Updated by crameleon 3 months ago

Actions #4

Updated by Akatama 2 months ago

Are there any updates on this bug? I understand from the bug that Pharaoh_Atem posted from Bugzilla that an ECO will be required to update pygit2 in order to fix this bug. Are there any plans to do that?

I hope I am not being too pushy here - in my particular case I seem to have found a workaround (although last I heard there was some kind of error accepting my PR, which I hope is not caused by this same issue. I am waiting for the maintainer to take another look now that I have made some changes). I do have some concern that other users of Pagure might be affected now or in the future which could make things difficult in terms of contributing.

Actions #5

Updated by crameleon about 1 month ago

Actions #6

Updated by sfalken@cloverleaf-linux.org about 1 month ago

I just linkpac'd in the following packages from Factory to openSUSE:infrastructure:pagure, that should fix this issue on code.o.o, if somebody wants to update it.

libgit2
python-cffi
-cryptography
-setuptools-rust
-pyOpenSSL
-pygit2

Actions #7

Updated by crameleon about 1 month ago ยท Edited

We already tried linking cffi from Factory and devel projects. Your link by itself does not help, it builds for Python 3.11. If you remove the sle15_pythons macro it will try to build for 3.6 but fail.
We also tried to switch the whole Pagure stack to 3.11 (see the tons of packages openSUSE:infrastructure:pagure) but eventually gave up after a long dependency chain (we resolved most of the dependencies, but there was some issue with Pagure itself at 3.11, so we suspect it would not work on Tumbleweed either).

Actions #8

Updated by sfalken@cloverleaf-linux.org about 1 month ago

Let me see what happens with Tumbleweed, I'll report back.

Actions #9

Updated by Pharaoh_Atem 24 days ago

I have, for the time being, downgraded python-pygit2 to the version shipped in Leap 15.5 and versionlocked it:

pharaoh_atem@pagure01:~> sudo zypper in --oldpackage ./python3-pygit2-1.7.0-bp155.2.14.x86_64.rpm 
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following package is going to be downgraded:
  python3-pygit2

1 package to downgrade.

Package download size:   177.8 KiB

Package install size change:
              |     856.6 KiB  required by packages that will be installed
  -214.2 KiB  |  -    1.0 MiB  released by packages that will be removed

Backend:  classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y): y
Retrieving: python3-pygit2-1.7.0-bp155.2.14.x86_64 (Plain RPM files cache)                                                                                                                                                (1/1), 177.8 KiB    

Checking for file conflicts: ...........................................................................................................................................................................................................[done]
(1/1) Installing: python3-pygit2-1.7.0-bp155.2.14.x86_64 ...............................................................................................................................................................................[done]
There are running programs which still use files and libraries deleted or updated by recent upgrades. They should be restarted to benefit from the latest updates. Run 'zypper ps -s' to list these programs.

pharaoh_atem@pagure01:~> sudo zypper addlock python3-pygit2
Specified lock has been successfully added.

We still need to make adjustments to the pagure packaging in Factory to allow us to optionally override the default Python it is built with.

Actions

Also available in: Atom PDF