[EPEL-devel] Re: [new / help wanted] fence-agents-epel package

[Alex Talaran]

wouldnt think make split packages vs all the agents just in the -epel 
package as i originally submitted? im fine either way just not clear.
do i need to make other changes or does the rest seem ok since i am not 
tied to requiring man pages?

On 2022-08-25 08:29, Troy Dawson wrote:
> For the names, the source rpm needs to have the -epel suffice 
> (fence-agents-epel) but then all the "missing" packages have the same 
> name they would have if they were in RHEL or Fedora.  So in this case 
> they would be
>
> fence-agents-pve
> fence-agents-raritan
> fence-agents-rcd-serial
> fence-agents-virsh
>
> If you look at my attachment in my previous email I have them set that way.
> Troy
>
> On Wed, Aug 24, 2022 at 3:38 PM Alex Talaran <[e-mail] 
> > wrote:
> i dont need them but wasnt sure if required for epel to keep things
> complete and similar to the base package. how did you want me to change
> the names? i left it the same as in the original spec file, and named
> this one -epel after previous discussion on list
>
> On 2022-08-24 17:13, Troy Dawson wrote:
>  > I'm sure having all the fence agents in one package is nice for
> you, but
>  > if someone has both Fedora and RHEL based machines, they would
>  > appreciate the packages having the same naming conventions.
>  > This is looking pretty good.
>  > I'll do some poking about for the man pages.  How badly do you
> want the
>  > man pages?
>  >
>  > Troy
>  >
>  >
>  > On Tue, Aug 23, 2022 at 6:40 AM Alex Talaran <[e-mail]
> <mailto:[e-mail]>
>  > <mailto:[e-mail] <mailto:[e-mail]>>> wrote:
>  >
>  >     attached a new spec using 4.10 which should match el9
> (desired distro
>  >     version) as you noted.
>  >     srpm and rpm still seem to build fine without man pages,
> still not sure
>  >     how to generate them.
>  >
>  >     On 2022-08-08 17:22, Troy Dawson wrote:
>  >      > Hi Alex,
>  >      > I've been looking into this some.
>  >      >
>  >      > What distribution do you want this for?
>  >      > I haven't seen anywhere in your emails saying if this is
> for RHEL
>  >     8 or
>  >      > RHEL 9?
>  >      > The spec file you have attached is for fence-agents-4.11,
> which
>  >     is only
>  >      > in Fedora, so that doesn't let me know either.
>  >      >
>  >      > The major problem is that the fence-agents-pve version has to
>  >     match the
>  >      > fence-agents that is in your version of RHEL.
>  >      > So for RHEL8 (or compatible) it needs to be version
> 4.2.1.  For
>  >     RHEL 9
>  >      > it needs to be 4.10.0
>  >      >
>  >      > We need to start with the correct version of fence-agents and
>  >     work from
>  >      > there.
>  >      >
>  >      > Troy
>  >      >
>  >      > On Wed, Jul 27, 2022 at 10:03 AM Alex Talaran
> <[e-mail] <mailto:[e-mail]>
>  >     <mailto:[e-mail] <mailto:[e-mail]>>
>  >      > <mailto:[e-mail] <mailto:[e-mail]>
> <mailto:[e-mail] <mailto:[e-mail]>>>> wrote:
>  >      >
>  >      >     i was able to get this built and installable if anyone
> wants
>  >     to help
>  >      >     test or maintain it.
>  >      >     an issue exists with the man pages not being built
> still but
>  >     im not
>  >      >     sure
>  >      >     how the makefile target works for these so they are
> excluded
>  >     for now.
>  >      >
>  >      >     maybe some other small tweaks are still needed too
> since its
>  >     just a
>  >      >     (first for me) stripped down and modified upstream
> spec file.
>  >      >
>  >      >     On 2022-07-20 08:47, Andrew C Aitchison wrote:
>  >      >      > On Wed, 20 Jul 2022, Alex Talaran wrote:
>  >      >      >
>  >      >      >> i ended up with the same error with that change.
>  >      >      >
>  >      >      > I am sorry my suggestion did not help.
>  >      >      > I don't have a Red Hat compatible machine newer
> that RHEL6
>  >      >      > (I moved to Ubuntu for work-related reasons)
>  >      >      > so I am unable to test things myself.
>  >      >      >
>  >      >      >> is it possible its getting confused because the
> dirname
>  >     in the
>  >      >     tarball
>  >      >      >> is different than the package name and looking in the
>  >     wrong spot?
>  >      >      >
>  >      >      > The -n fence-agents-%{version} in
>  >      >      >      %prep
>  >      >      >      %setup -q -n fence-agents-%{version}
>  >      >      > is supposed to resolve that, but that setup line might
>  >     need tweaking
>  >      >      > to match the contents of the tarball.
>  >      >      >
>  >      >      > It is old and may be somewhat dated, but my bible for
>  >     rewriting
>  >      >     .spec
>  >      >      > files was the book
>  >      >      >     Maximum RPM - Taking the Red Hat Package Manager to
>  >     the Limit
>  >      >      > a version of which is available at
>  >      >      > http://ftp.rpm.org/max-rpm/index.html
> <http://ftp.rpm.org/max-rpm/index.html>
>  >     <http://ftp.rpm.org/max-rpm/index.html
> <http://ftp.rpm.org/max-rpm/index.html>>
>  >      >     <http://ftp.rpm.org/max-rpm/index.html
> <http://ftp.rpm.org/max-rpm/index.html>
>  >     <http://ftp.rpm.org/max-rpm/index.html
> <http://ftp.rpm.org/max-rpm/index.html>>>
>  >      >      >
>  >      >      >> On 2022-07-19 23:32, Andrew C Aitchison wrote:
>  >      >      >>> On Tue, 19 Jul 2022, Alex Talaran wrote:
>  >      >      >>>
>  >      >      >>>> per a previous thread i took a shot at cleaning
> up the
>  >      >     fence-agents
>  >      >      >>>> rpm to only include the missing agents and make
> a new
>  >     package.
>  >      >     i am
>  >      >      >>>> having some issues with the source url and
> getting it to
>  >      >     build. the
>  >      >      >>>> srpm is ok, but when i try to rebuild it into a
> proper
>  >     rpm i
>  >      >     get the
>  >      >      >>>> following (output truncated):
>  >      >      >>>>
>  >      >      >>>> ---
>  >      >      >>>> + py39_byte_compile /usr/bin/python3
>  >      >      >>>>
>  >      >
>  >     
>   /builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence
>  >      >      >>>> + python_binary='env PYTHONHASHSEED=0
> /usr/bin/python3'
>  >      >      >>>> +
>  >      >      >>>>
>  >      >
>  >     
>   bytecode_compilation_path=/builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence
>  >      >      >>>> + env PYTHONHASHSEED=0 /usr/bin/python3 -s -B -m
>  >     compileall -o
>  >      >     0 -o
>  >      >      >>>> 1 -s
>  >      >   
>   /builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64
>  >      >      >>>> -p /
>  >      >      >>>>
>  >      >
>  >     
>   /builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence
>  >      >      >>>> Listing
>  >      >      >>>>
>  >      >
>  >     
>   '/builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence'...
>  >      >      >>>> Can't list
>  >      >      >>>>
>  >      >
>  >     
>   '/builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence'
>  >      >      >>>> + chmod 0755
>  >      >      >>>>
>  >      >
>  >     
>   /builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence/fence_pve.py /builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence/fence_raritan.py /builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence/fence_rcd_serial.py /builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence/fence_virsh.py
>  >      >      >>>> chmod: cannot access
>  >      >      >>>>
>  >      >
>  >     
>   '/builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence/fence_pve.py': No such file or directory
>  >      >      >>>> chmod: cannot access
>  >      >      >>>>
>  >      >
>  >     
>   '/builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence/fence_raritan.py': No such file or directory
>  >      >      >>>> chmod: cannot access
>  >      >      >>>>
>  >      >
>  >     
>   '/builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence/fence_rcd_serial.py': No such file or directory
>  >      >      >>>> chmod: cannot access
>  >      >      >>>>
>  >      >
>  >     
>   '/builddir/build/BUILDROOT/fence-agents-epel-4.11.0-1.el9.x86_64/usr/share/fence/fence_virsh.py': No such file or directory
>  >      >      >>>> error: Bad exit status from /var/tmp/rpm-tmp.S10L6D
>  >     (%install)
>  >      >      >>>> ---
>  >      >      >>>>
>  >      >      >>>> i even tried to comment out the bytecompile
> lines but
>  >     got the
>  >      >     same
>  >      >      >>>> error.
>  >      >      >>>>
>  >      >      >>>> is it possible to get some help sorting this out? i
>  >     have attached
>  >      >      >>>> the WIP spec file.
>  >      >      >>>> thank you.
>  >      >      >>>
>  >      >      >>> I would try replacing
>  >      >      >>>      mkdir -p %{buildroot}/%{_datadir}/
>  >      >      >>> with
>  >      >      >>>      mkdir -p %{buildroot}/%{_datadir}/fence
>  >      >      >>>
>  >      >      >>
>  >      >      > _______________________________________________
>  >      >     epel-devel mailing list --
> [e-mail]
> <mailto:[e-mail]>
>  >     <mailto:[e-mail]
> <mailto:[e-mail]>>
>  >      >     <mailto:[e-mail]
> <mailto:[e-mail]>
>  >     <mailto:[e-mail]
> <mailto:[e-mail]>>>
>  >      >     To unsubscribe send an email to
>  >      > [e-mail]
> <mailto:[e-mail]>
>  >     <mailto:[e-mail]
> <mailto:[e-mail]>>
>  >      >     <mailto:[e-mail]
> <mailto:[e-mail]>
>  >     <mailto:[e-mail]
> <mailto:[e-mail]>>>
>  >      >     Fedora Code of Conduct:
>  >      >
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> <https://docs.fedoraproject.org/en-US/project/code-of-conduct/>
>  >   
>   <https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> <https://docs.fedoraproject.org/en-US/project/code-of-conduct/>>
>  >      >
>  >     
>   <https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> <https://docs.fedoraproject.org/en-US/project/code-of-conduct/>
>  >   
>   <https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> <https://docs.fedoraproject.org/en-US/project/code-of-conduct/>>>
>  >      >     List Guidelines:
>  >      > https://fedoraproject.org/wiki/Mailing_list_guidelines
> <https://fedoraproject.org/wiki/Mailing_list_guidelines>
>  >     <https://fedoraproject.org/wiki/Mailing_list_guidelines
> <https://fedoraproject.org/wiki/Mailing_list_guidelines>>
>  >      >   
>   <https://fedoraproject.org/wiki/Mailing_list_guidelines
> <https://fedoraproject.org/wiki/Mailing_list_guidelines>
>  >     <https://fedoraproject.org/wiki/Mailing_list_guidelines
> <https://fedoraproject.org/wiki/Mailing_list_guidelines>>>
>  >      >     List Archives:
>  >      >
>  >
> https://lists.fedoraproject.org/archives/list/[e-mail] <https://lists.fedoraproject.org/archives/list/[e-mail]> <https://lists.fedoraproject.org/archives/list/[e-mail] <https://lists.fedoraproject.org/archives/list/[e-mail]>> <https://lists.fedoraproject.org/archives/list/[e-mail] <https://lists.fedoraproject.org/archives/list/[e-mail]> <https://lists.fedoraproject.org/archives/list/[e-mail] <https://lists.fedoraproject.org/archives/list/[e-mail]>>>
>  >      >     Do not reply to spam on the list, report it:
>  >      > https://pagure.io/fedora-infrastructure
> <https://pagure.io/fedora-infrastructure>
>  >     <https://pagure.io/fedora-infrastructure
> <https://pagure.io/fedora-infrastructure>>
>  >      >     <https://pagure.io/fedora-infrastructure
> <https://pagure.io/fedora-infrastructure>
>  >     <https://pagure.io/fedora-infrastructure
> <https://pagure.io/fedora-infrastructure>>>
>  >      >
>  >      >
>  >      > _______________________________________________
>  >      > epel-devel mailing list --
> [e-mail]
> <mailto:[e-mail]>
>  >     <mailto:[e-mail]
> <mailto:[e-mail]>>
>  >      > To unsubscribe send an email to
>  > [e-mail]
> <mailto:[e-mail]>
>  >     <mailto:[e-mail]
> <mailto:[e-mail]>>
>  >      > Fedora Code of Conduct:
>  > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> <https://docs.fedoraproject.org/en-US/project/code-of-conduct/>
>  >   
>   <https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> <https://docs.fedoraproject.org/en-US/project/code-of-conduct/>>
>  >      > List Guidelines:
>  > https://fedoraproject.org/wiki/Mailing_list_guidelines
> <https://fedoraproject.org/wiki/Mailing_list_guidelines>
>  >     <https://fedoraproject.org/wiki/Mailing_list_guidelines
> <https://fedoraproject.org/wiki/Mailing_list_guidelines>>
>  >      > List Archives:
>  >
> https://lists.fedoraproject.org/archives/list/[e-mail] <https://lists.fedoraproject.org/archives/list/[e-mail]> <https://lists.fedoraproject.org/archives/list/[e-mail] <https://lists.fedoraproject.org/archives/list/[e-mail]>>
>  >      > Do not reply to spam, report it:
>  > https://pagure.io/fedora-infrastructure/new_issue
> <https://pagure.io/fedora-infrastructure/new_issue>
>  >     <https://pagure.io/fedora-infrastructure/new_issue
> <https://pagure.io/fedora-infrastructure/new_issue>>
>  >