Have you actually talked to @orion in https://bugzilla.redhat.com/show_bug.cgi?id=1765877 ?

@churchyard I will be talking to him about this, but there's still the fundamental problem that these requests shouldn't have been granted.

https://pagure.io/releng/issue/8844

I've responded in the bug. FWIW I don't see any point in deleting these branches, they are the standard epel8 branches.

@orion Normally when I add support for epel8, I want it to be possible to fast-forward merge from Fedora branches. The problem is that by default, releng creates a branch and stacks a commit on top that breaks my workflow to add package.cfg.

I usually create epel8 branches myself instead, which allows me to avoid that.

I'd use the package.cfg if it worked as I wanted it to... https://pagure.io/fedpkg/issue/352

So please, can someone delete the branches or at least reset it so I can cleanly merge Fedora branches?

We are not allowing removing of branches anymore. But I will discuss about this ticket in our next releng meeting on Wed 16:00 UTC if we can do anything about this.

Sorry about the trouble.

@mohanboddu At the very minimum, dropping the commit that makes it so I can't fast-forward merge would make me happy...

From RelEng meeting on Feb 12 2020:

We will close the tickets and ask people to take it to fesco for a process to remove branches

Please file a ticket with fesco to get a process established to remove branches.

Sorry for the trouble.

FESCo has approved branch deletion for branches that have never been used for a build (as it is in this case). Can this be done now?

From our meeting today:

#info mboddu will remove the branches in pdc first and then try deleting the branches in pkgs02.phx2.fp.o directly from the dist-git repo

I will try that later today.

FESCo has approved branch deletion for branches that have never been used for a build (as it is in this case). Can this be done now?

Sorry for the bureaucracy here, but in the ticket, they are talking about accidental branches, not release branches. Also, as per their ref verification, epel8 is not removable as it created from master.

Can you request a special exception in your case?

Again, sorry about all this bureaucracy.

FYI - https://pagure.io/fesco/issue/2387

What's the status here? It would be really nice to get buildbot into EPEL8. Thanks.

I'd like to have the epel8 branch reset to remove the package.cfg commit, so that master can be fast-forwarded into it. And then I'd like to have epel8-playground entirely deleted.

@orion If you can get all of Buildbot's dependencies into EPEL8, I'm happy to grant you collaborator access for the epel8 branch once this is done.

@ngompa All the deps are in EPEL8 now (have been for a while). Why remove epel8-playground?

@orion There are definitely missing dependencies for EPEL 8:

Finish: rpmbuild buildbot-2.8.3-2.fc34.src.rpm
Finish: build phase for buildbot-2.8.3-2.fc34.src.rpm
INFO: Done(buildbot-2.8.3-2.fc34.src.rpm) Config(epel-8-x86_64) 4 minutes 42 seconds
INFO: Results and/or logs in: /var/lib/mock/epel-8-x86_64/result
INFO: Installing built packages
INFO: installing package(s): /var/lib/mock/epel-8-x86_64/result/buildbot-2.8.3-2.el8.noarch.rpm /var/lib/mock/epel-8-x86_64/result/buildbot-master-2.8.3-2.el8.noarch.rpm /var/lib/mock/epel-8-x86_64/result/buildbot-worker-2.8.3-2.el8.noarch.rpm /var/lib/mock/epel-8-x86_64/result/buildbot-www-2.8.3-2.el8.noarch.rpm
No matches found for the following disable plugin patterns: local, spacewalk
CentOS-8 - Base                                  16 kB/s | 3.9 kB     00:00
CentOS-8 - AppStream                             13 kB/s | 4.3 kB     00:00
CentOS-8 - PowerTools                            17 kB/s | 4.3 kB     00:00
CentOS-8 - Extras                               4.8 kB/s | 1.5 kB     00:00
epel                                            8.0 kB/s | 4.7 kB     00:00
epel                                            9.0 MB/s | 7.9 MB     00:00
Error:
 Problem 1: conflicting requests
  - nothing provides python3.6dist(cairocffi) needed by buildbot-www-2.8.3-2.el8.noarch
  - nothing provides python3.6dist(cairosvg) needed by buildbot-www-2.8.3-2.el8.noarch
  - nothing provides python3.6dist(klein) needed by buildbot-www-2.8.3-2.el8.noarch
 Problem 2: package buildbot-2.8.3-2.el8.noarch requires buildbot-www = 2.8.3, but none of the providers can be installed
  - conflicting requests
  - nothing provides python3.6dist(cairocffi) needed by buildbot-www-2.8.3-2.el8.noarch
  - nothing provides python3.6dist(cairosvg) needed by buildbot-www-2.8.3-2.el8.noarch
  - nothing provides python3.6dist(klein) needed by buildbot-www-2.8.3-2.el8.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
WARNING: Failed install built packages
Finish: run

This should be fixed now.

Thanks!