https://bugzilla.redhat.com/show_bug.cgi?id=2256207

            Bug ID: 2256207
           Summary: perl-Apache-Htpasswd: please enable builds for EPEL8
                    and EPEL9
           Product: Fedora EPEL
           Version: epel9
          Hardware: All
                OS: Linux
            Status: NEW
         Component: perl-Apache-Htpasswd
          Severity: low
          Assignee: xav...@bachelot.org
          Reporter: p...@bieringer.de
        QA Contact: extras...@fedoraproject.org
                CC: perl-devel@lists.fedoraproject.org,
                    xav...@bachelot.org
  Target Milestone: ---
    Classification: Fedora



Description of problem:
currently it's only available for EPEL7, but looks like a build on EPEL8 works
without issues using SRPM from EPEL7:

https://koji.fedoraproject.org/koji/taskinfo?taskID=111008111

rebuild of EPEL7 on EPEL9 results in a problem
https://koji.fedoraproject.org/koji/taskinfo?taskID=111008336
RPM build errors:
    File must begin with "/": %{perl_vendorlib}/*

but rebuild of F39 on EPEL9 works without any issue:
https://koji.fedoraproject.org/koji/taskinfo?taskID=111008715

=> can one please activate build for EPEL8+9, in case of lack of manpower feel
free to add me as co-maintainer.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2256207

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202256207%23c0
--
_______________________________________________
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to