Re: Fedora 34 Change: GitRepos-master-to-main (Self-Contained Change)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Good morning,

20/12/9 23:24(e)an, Kevin Fenzi igorleak idatzi zuen:
On Wed, Dec 09, 2020 at 08:02:45AM +0100, Julen Landa Alustiza wrote:


20/12/4 20:42(e)an, Kevin Fenzi igorleak idatzi zuen:
On Fri, Dec 04, 2020 at 12:45:03AM +0100, Miro Hrončok wrote:
On 12/3/20 4:39 PM, Petr Šabata wrote:
On Thu, Dec 3, 2020 at 4:34 PM Pierre-Yves Chibon<pingou@xxxxxxxxxxxx>  wrote:
On Thu, Dec 03, 2020 at 04:16:56PM +0100, Petr Šabata wrote:
Since I don't see those on the list, does this impact

* rpkg (fedpkg)?
Wrapper to git, should not be impacted. The only thing I could think of was:
when we fedpkg clone an empty git repo, have fedpkg do the "git branch -M main"
directly. That being said, I'm not 100% sure when we creating a project on
dist-git today we create them empty.

Optionally, they can be empty.

    $ fedpkg request-repo ... --no-initial-commit

This could be anoying if someone then pushes as master branch back up,
but I guess we can take those on a case by case basis.
This change proposal should cover changing pagure-dist-git's rules so that
should be impossible.

Indeed, we can add that.

Indeed we'll need to be able to opt-in to the new naming on some repos while
the rest keeps the old one, so we could temporary need to disable the
hardcoded rules and rely on upstream protected branches feature or something
similar at least during the transition.

I'm not sure what you mean here. Someone pushing while we are changing
the repos?

I thought there were some rpms namespace repos on phase 0, but that's not true, so nevermind. We can just modify dist-git for full rpms namespace :)


src.fp.o has strict rules to avoid to push some tags, this transition must
keep those stricts rules in place while transitioning imo

Yep. And add master. Will update the change.

kevin


_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux