#591 Do not auto-request EPEL x.y modules
Merged 18 days ago by onosek. Opened a month ago by carlwgeorge.
carlwgeorge/fedpkg epel_minor_no_module_request  into  master

file modified
+1 -1
@@ -46,7 +46,7 @@ 

                            get_release_branches, get_stream_branches, is_epel,

                            new_pagure_issue, sl_list_to_dict, verify_sls)

  

- RELEASE_BRANCH_REGEX = r'^(f\d+|el\d+|eln|epel\d+)$'

+ RELEASE_BRANCH_REGEX = r'^(f\d+|el\d+|eln|epel\d+|epel\d+\.\d+)$'

  LOCAL_PACKAGE_CONFIG = 'package.cfg'

  

  BODHI_TEMPLATE = """\

After the EPEL 10.0 mass branching, we discovered that running fedpkg request-branch epel10.0 would file SCM requests for:

  • New Branch "epel10.0" for "rpms/<name>"
  • New Repo for "modules/<name>"
  • New Branch "epel10.0" for "modules/<name>"

The second two are invalid and unwanted. Thankfully Fabio Valentini (@decathorpe) noticed that this was similar to what was happening for ELN a while back, an pointed me to RELEASE_BRANCH_REGEX. This adjust that regex to also accept EPEL minor version branches.

Related: #564

Signed-off-by: Carl George carlwgeorge@gmail.com

rebased onto ffe8211

a month ago

As a followup, we should probably remove the whole auto_module code.

Pull-Request has been merged by onosek

18 days ago

Thanks for the change.

As a followup, we should probably remove the whole auto_module code.

@churchyard, just the auto_module code, or even the whole module functionality?
https://fedoraproject.org/wiki/Changes/RetireModularity
https://pagure.io/fedpkg/issue/595

Metadata