You need to logout and login for the changes on account.fedoraproject.org to be reflected.

no joke you think I haven't already tried

it doesn't make the menu appear to add the ssh key as if by magic

and the git urls are always indicated in https and not in ssh

and it indicates that you have to add an ssh key while the menu that allows you to do so does not exist

good after a second disconnection

now it says

Only members of the packager group(s) can clone via ssh

but I am on a fork so we must be able to have access to the fork in ssh

and yet it is still only in https

we can not modify anything in https

we can only modify the files already present

no way to add a new file at this level also it is necessary to correct those

because on all the other git we can directly add files from the web interface and there again it is not proposed

LANG=en git clone ssh://git@src.fedoraproject.org/forks/goddabrouquita8280/rpms/Pound.git
Cloning into 'Pound'...
ssh: connect to host src.fedoraproject.org port 22: Connection timed out
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

I would like to be able to do this to propose that this package be put back on the repositories

because the version that was deleted is 2.7 which is indeed obsolete

https://src.fedoraproject.org/rpms/Pound/blob/rawhide/f/dead.package

Pound fails to build from source: https://bugzilla.redhat.com/show_bug.cgi?id=1674583

based on Pound 2.7 to old source

https://src.fedoraproject.org/rpms/Pound/blob/f30/f/Pound.spec

except the deleveling of this program has continued but it has been moved to github

currently we have 4.13 in stable version 4.14 in development

https://github.com/graygnuorg/pound

src rpm used for el9 work on fedora

http://www.invoca.ch/pub/packages/pound/RPMS/ils-9/SRPMS/pound-4.13-1.el9.src.rpm

so we should be able to do this

git clone ssh://git@src.fedoraproject.org/forks/goddabrouquita8280/rpms/Pound.git
cd Pound
wget http://www.invoca.ch/pub/packages/pound/RPMS/ils-9/SRPMS/pound-4.13-1.el9.src.rpm
rpm2cpio pound-4.13-1.el9.src.rpm | cpio -idmv
rm -f pound-4.13-1.el9.src.rpm
rm -f pound-4.13.tar.gz
echo "SHA512 (pound-4.13.tar.gz) = 0a9f8612c4f894abcaac569d8f673cd39ea8cab21e2dfcd2968f1f79796a5c15af7d3e7fdae9b0e9dfe86f40c90bd466d20db85500dc05975aa6d65108cf26a1" > sources
git add --all *
git commit -a -m "Update Pound 4.13"
git push origin main

after send pull request for update Pound 4.13 on the official fedora repository

I recommend you to use fedpkg when working with packages and not plain git. The fedpkg tool could be found in fedora-packager package.

I'm also not sure if ssh is allowed when you are not part of packagers group.

I'm also not sure if ssh is allowed when you are not part of packagers group.

It does not, you need to git clone and push via http

Yes, see: https://fedoraproject.org/wiki/Infrastructure/HTTPS-commits

except that we can't push by https and therefore we can't send modifications

while it is our own fork any git allows it since it does not modify the original project

so not allowing ssh on our own fork is an error

and this error prevents us from being able to participate in the codes

as for your fedora packager tool I never use them

for the following reason this tool is only available on fedora

but I work with several linux distributions

which means that I am not always only on fedora
there are also people who are windows or mac etc

so using a distribution-specific tool to participate in your code is not a good idea

you should only use multi-distribution tools

git is a good choice but fork access must always be writable with git in ssh

this is the case on pagure but not on src.fedoraproject.org

this problem is only on src.fedoraproject.org

except certain packages are present only on src.fedoraproject.org and are not present on pagure and vice versa

the tools used are similar, they are probably on the same cms but not in the same version

or not the same permissions

it would therefore be necessary to correct these and allow git write access in ssh on src.fedoraproject.org as is the case on pagure

As I said earlier you need to be a Fedora packager to have ssh access to our distribution git. You can still push using https, it will ask you for username and password during push. But you will be able to push only to our own forks as the access to actual packages is allowed only to maintainers. Then you can open PR from your fork to actual package and ask maintainer to merge it.

We don't have any package on pagure.io, everything packaged in Fedora is hosted on src.fedoraproject.org. Pagure is our public git forge we provide for community.

doing a push on git in https is totally impossible and those even sending your login in http authentication

this is a security protection that has existed for years to prevent unauthorized modifications pushes are authorized only and exclusively in ssh

so instead of insisting by inviting people to do things that are not feasible and which have been prohibited for security measures, be sure to correct the problem and authorize pushes in ssh on private forks thank you

it's not complicated it takes 2 minutes to modify the settings since yesterday you should have already done it

instead of insisting on telling people to do things that are not feasible

in addition you allow yourself to close the insue when it is not even resolved we closed an insue that if it was resolved moreover it is the one who opens the insue who must close it and not another person

We don't want everybody to be able to push to packages in dist-git, this is why it's limited only for packagers.

We will not enable this for users who are not in packager group. If you want to have ssh access ask for co-maintainership of the package you care about.