help with repackaging pdf-stapler for python3

[Globe Trotter]

Hi,
I am tryingto repackage pdf-stapler with python3. 

My updated SPEC file is:

https://paste.centos.org/view/b7477290

This SPEC file builds the binary using 

rpmbuld -bb pdf-stapler.spec

fine, and the binary even installs. From what I can test, it seems to work.

However, when I try to use:
rpmbuild -ba pdf-stapler.spec
I get the following. I am not very familiar with the intricacies of packaging (sorry) but
this is the first time such an error has shown up for me. Any suggestions? 

Many thanks in advance.

$ rpmbuild -ba pdf-stapler.spec 
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.as88BY
+ umask 022
+ cd /home/aarem/rpmbuild/BUILD
+ cd /home/aarem/rpmbuild/BUILD
+ rm -rf stapler-1.0.0
+ /usr/bin/bzip2 -dc /home/aarem/rpmbuild/SOURCES/stapler-1.0.0.tar.bz2
+ /usr/bin/tar -xof -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd stapler-1.0.0
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ sed -i 's|"PyPDF2>=1.24"||' setup.py
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.9D7r1f
+ umask 022
+ cd /home/aarem/rpmbuild/BUILD
+ cd stapler-1.0.0
+ CFLAGS='-O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2
-Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection'
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,now
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld'
+ /usr/bin/python3 setup.py build '--executable=/usr/bin/python3 -s'
/usr/lib/python3.7/site-packages/setuptools/dist.py:475: UserWarning: Normalizing
'1.0.0-rc1' to '1.0.0rc1'
  normalized_version,
running build
running build_py
creating build
creating build/lib
creating build/lib/staplelib
copying staplelib/stapler.py -> build/lib/staplelib
copying staplelib/commands.py -> build/lib/staplelib
copying staplelib/__init__.py -> build/lib/staplelib
copying staplelib/iohelper.py -> build/lib/staplelib
copying staplelib/tests.py -> build/lib/staplelib
running egg_info
creating stapler.egg-info
writing stapler.egg-info/PKG-INFO
writing dependency_links to stapler.egg-info/dependency_links.txt
writing entry points to stapler.egg-info/entry_points.txt
writing requirements to stapler.egg-info/requires.txt
writing top-level names to stapler.egg-info/top_level.txt
writing manifest file 'stapler.egg-info/SOURCES.txt'
reading manifest file 'stapler.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'stapler.egg-info/SOURCES.txt'
creating build/lib/staplelib/testfiles
copying staplelib/testfiles/1page.pdf -> build/lib/staplelib/testfiles
copying staplelib/testfiles/5page.pdf -> build/lib/staplelib/testfiles
+ exit 0
Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.KFKATx
+ umask 022
+ cd /home/aarem/rpmbuild/BUILD
+ '[' /home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64 '!='
/ ']'
+ rm -rf /home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64
++ dirname /home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64
+ mkdir -p /home/aarem/rpmbuild/BUILDROOT
+ mkdir /home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64
+ cd stapler-1.0.0
+ CFLAGS='-O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2
-Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection'
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed  -Wl,-z,now
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld'
+ /usr/bin/python3 setup.py install -O1 --skip-build --root
/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64
/usr/lib/python3.7/site-packages/setuptools/dist.py:475: UserWarning: Normalizing
'1.0.0-rc1' to '1.0.0rc1'
  normalized_version,
running install
running install_lib
creating /home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr
creating /home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr/lib
creating /home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr/lib/python3.7
creating
/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr/lib/python3.7/site-packages
creating
/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr/lib/python3.7/site-packages/staplelib
copying build/lib/staplelib/stapler.py ->
/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr/lib/python3.7/site-packages/staplelib
creating
/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr/lib/python3.7/site-packages/staplelib/testfiles
copying build/lib/staplelib/testfiles/5page.pdf ->
/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr/lib/python3.7/site-packages/staplelib/testfiles
copying build/lib/staplelib/testfiles/1page.pdf ->
/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr/lib/python3.7/site-packages/staplelib/testfiles
copying build/lib/staplelib/commands.py ->
/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr/lib/python3.7/site-packages/staplelib
copying build/lib/staplelib/__init__.py ->
/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr/lib/python3.7/site-packages/staplelib
copying build/lib/staplelib/iohelper.py ->
/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr/lib/python3.7/site-packages/staplelib
copying build/lib/staplelib/tests.py ->
/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr/lib/python3.7/site-packages/staplelib
byte-compiling
/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr/lib/python3.7/site-packages/staplelib/stapler.py
to stapler.cpython-37.pyc
byte-compiling
/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr/lib/python3.7/site-packages/staplelib/commands.py
to commands.cpython-37.pyc
byte-compiling
/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr/lib/python3.7/site-packages/staplelib/__init__.py
to __init__.cpython-37.pyc
byte-compiling
/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr/lib/python3.7/site-packages/staplelib/iohelper.py
to iohelper.cpython-37.pyc
byte-compiling
/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr/lib/python3.7/site-packages/staplelib/tests.py
to tests.cpython-37.pyc
writing byte-compilation script '/tmp/tmp37pd80wk.py'
/usr/bin/python3 /tmp/tmp37pd80wk.py
removing /tmp/tmp37pd80wk.py
running install_egg_info
running egg_info
writing stapler.egg-info/PKG-INFO
writing dependency_links to stapler.egg-info/dependency_links.txt
writing entry points to stapler.egg-info/entry_points.txt
writing requirements to stapler.egg-info/requires.txt
writing top-level names to stapler.egg-info/top_level.txt
reading manifest file 'stapler.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'stapler.egg-info/SOURCES.txt'
Copying stapler.egg-info to
/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr/lib/python3.7/site-packages/stapler-1.0.0rc1-py3.7.egg-info
running install_scripts
Installing stapler script to
/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr/bin
Installing pdf-stapler script to
/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr/bin
+ mv /home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64//usr/bin/stapler
/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64//usr/bin/pdf-stapler
+ /usr/lib/rpm/find-debuginfo.sh -j8 --strict-build-id -m -i --build-id-seed 1.0.0-1.fc30
--unique-debug-suffix -1.0.0-1.fc30.x86_64 --unique-debug-src-base
pdf-stapler-1.0.0-1.fc30.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000
--dwz-max-die-limit 110000000 -S debugsourcefiles.list
/home/aarem/rpmbuild/BUILD/stapler-1.0.0
find: 'debug': No such file or directory
+ '[' noarch = noarch ']'
+ case "${QA_CHECK_RPATHS:-}" in
+ /usr/lib/rpm/check-buildroot
+ /usr/lib/rpm/redhat/brp-ldconfig
+ /usr/lib/rpm/brp-compress
+ /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip
+ /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1 0
Bytecompiling .py files below
/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-1.fc30.x86_64/usr/lib/python3.7 using
/usr/bin/python3.7
+ /usr/lib/rpm/brp-python-hardlink
+ /usr/lib/rpm/redhat/brp-mangle-shebangs
Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.WqoCMQ
+ umask 022
+ cd /home/aarem/rpmbuild/BUILD
+ cd stapler-1.0.0
+ /usr/bin/python3 setup.py test
/usr/lib/python3.7/site-packages/setuptools/dist.py:475: UserWarning: Normalizing
'1.0.0-rc1' to '1.0.0rc1'
  normalized_version,
running test
running egg_info
writing stapler.egg-info/PKG-INFO
writing dependency_links to stapler.egg-info/dependency_links.txt
writing entry points to stapler.egg-info/entry_points.txt
writing requirements to stapler.egg-info/requires.txt
writing top-level names to stapler.egg-info/top_level.txt
reading manifest file 'stapler.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'stapler.egg-info/SOURCES.txt'
running build_ext
test_cat (staplelib.tests.TestStapler)
Make sure files are properly concatenated. ... ok
test_del_one_page (staplelib.tests.TestStapler)
Test del command for inverse select of one page. ... ok
test_del_range (staplelib.tests.TestStapler)
Test del command for inverse select multiple pages. ... ok
test_output_file_already_exists (staplelib.tests.TestStapler)
Test zip. ... ok
test_sel_one_page (staplelib.tests.TestStapler)
Test select of a one page from a PDF file. ... ok
test_sel_range (staplelib.tests.TestStapler)
Test select of more pages from a PDF file. ... ok
test_split (staplelib.tests.TestStapler)
Make sure a file is properly split into pages. ... ok
test_zip (staplelib.tests.TestStapler)
Test zip. ... ok

----------------------------------------------------------------------
Ran 8 tests in 0.580s

OK
+ exit 0
error: Bad file: /home/aarem/rpmbuild/SOURCES/1.0.0.tar.bz2: No such file or directory


RPM build errors:
    Bad file: /home/aarem/rpmbuild/SOURCES/1.0.0.tar.bz2: No such file or directory

[José Abílio Matos]

On Thursday, 26 December 2019 16.07.01 WET Globe Trotter via devel wrote:
>  Hi,
>  
>  I am tryingto repackage pdf-stapler with python3.
>  
>  My updated SPEC file is:
>  
>  https://paste.centos.org/view/b7477290
>  
>  This SPEC file builds the binary using 
Something weird in your spec file is that it has two source files:

Source0:        https://pypi.python.org/packages/source/s/stapler/stapler-%
{version}.tar.bz2
Source1:        https://github.com/hellerbarde/stapler/archive/stapler=%
{version}.tar.bz2

The second looks an error, notice the equal sign after the name. And if it is 
supposed to be the same then why are there two locations? This seems the 
likely cause of your problem.

-- 
José Abílio

[Globe Trotter]

   On Thursday, December 26, 2019, 10:34:12 AM CST, José Abílio Matos
<jamatos(a)fc.up.pt&gt; wrote: 

>  Something weird in your spec file is that it has two source files:
>  Source0:       
> https://pypi.python.org/packages/source/s/stapler/stapler-% 
{version}.tar.bz2
>  Source1:       
> https://github.com/hellerbarde/stapler/archive/stapler=% 
{version}.tar.bz2

>  The second looks an error, notice the equal sign after the name. And
> if it is  supposed to be the same then why are there two locations? This seems the likely
> cause of your problem. 
Thanks! That must have been it. The package compiles.
However, I have a problem: the issue is that Source0 does not have the latest tar.bz2
while Source1 does not call it 1.0.0 though the release notes say so (there).
So, I put in a Source2: which contains the local tar.bz2 that I have. There is no error in
the compilation but fedpkg build seems to have an error that I do not seem to get:
aarem's pdf-stapler-1.0.0-1.fc32 failed to build
    http://koji.fedoraproject.org/koji/buildinfo?buildID=1424956

And here is the spec file:

$ fpaste  pdf-stapler.spec
Uploading (4.7KiB)...
https://paste.centos.org/view/c2c3d4bf


Any help would be greatly and very gratefully appreciated!
Many thanks!

[Alexander Ploumistos]

Hello,

On Fri, Dec 27, 2019 at 7:44 AM Globe Trotter via devel
<devel(a)lists.fedoraproject.org&gt; wrote:
>  However, I have a problem: the issue is that Source0 does not have the latest tar.bz2
> while Source1 does not call it 1.0.0 though the release notes say so (there). 
You should have just one SourceX tag for each tarball. Since all three
of your links essentially point to the same thing and the actual
upstream is on github, keep only the URL to the source package you are
using. In your case, you are using a git snapshot, so you should be
following the relevant guidelines[0, 1], which if I'm interpreting
correctly, should result in something like this:

%global commit 875325103234b4a3ed96a4a5167ff78c291edbff
%global shortcommit %(c=%{commit}; echo ${c:0:7})
%global commitdate 20191215

Name:           pdf-stapler
Version:        1.0.0
Release:        0.1.%{commitdate}git%{shortcommit}%{?dist}
Summary:        Tool for manipulating PDF documents from the command line
License:        BSD
URL:            https://github.com/hellerbarde/stapler
Source0:      
https://github.com/hellerbarde/stapler/archive/%{commit}/%{name}-%{shortc...

(The actual source URL is this one:
https://github.com/hellerbarde/stapler/archive/875325103234b4a3ed96a4a516...
)


>  So, I put in a Source2: which contains the local tar.bz2 that I have.
> There is no error in the compilation but fedpkg build seems to have an error that I do not
> seem to get:
>
>  aarem's pdf-stapler-1.0.0-1.fc32 failed to build
>      http://koji.fedoraproject.org/koji/buildinfo?buildID=1424956 
It appears that the tests defined in the %check section download some
files over the internet and since koji does not allow internet access,
the test suite is failing. I did not check what is defined in the test
suite, but your options are to disable checks, include the test files
as separate sources or package them as new packages (going through the
review process), depending on their nature.


0. https://fedoraproject.org/wiki/Packaging:SourceURL
1. https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/

[Globe Trotter]

 Thank you!

Here is my updated spec file:
$ fpaste pdf-stapler.spec
Uploading (4.8KiB)...
https://paste.centos.org/view/6ddc6eec

However, I can not change the directory to a stapler directory. I get the following
error:
+ cd stapler-1.0.0
/var/tmp/rpm-tmp.2ZnEy2: line 38: cd: stapler-1.0.0: No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.2ZnEy2 (%prep)

Thanks again for your help!




    On Friday, December 27, 2019, 3:08:05 AM CST, Alexander Ploumistos
<alex.ploumistos(a)gmail.com&gt; wrote:  
 
 Hello,

On Fri, Dec 27, 2019 at 7:44 AM Globe Trotter via devel
<devel(a)lists.fedoraproject.org&gt; wrote:
>  However, I have a problem: the issue is that Source0 does not have the latest tar.bz2
> while Source1 does not call it 1.0.0 though the release notes say so (there). 
You should have just one SourceX tag for each tarball. Since all three
of your links essentially point to the same thing and the actual
upstream is on github, keep only the URL to the source package you are
using. In your case, you are using a git snapshot, so you should be
following the relevant guidelines[0, 1], which if I'm interpreting
correctly, should result in something like this:

%global commit 875325103234b4a3ed96a4a5167ff78c291edbff
%global shortcommit %(c=%{commit}; echo ${c:0:7})
%global commitdate 20191215

Name:          pdf-stapler
Version:        1.0.0
Release:        0.1.%{commitdate}git%{shortcommit}%{?dist}
Summary:        Tool for manipulating PDF documents from the command line
License:        BSD
URL:            https://github.com/hellerbarde/stapler
Source0:     
https://github.com/hellerbarde/stapler/archive/%{commit}/%{name}-%{shortc...

(The actual source URL is this one:
https://github.com/hellerbarde/stapler/archive/875325103234b4a3ed96a4a516...
)


>  So, I put in a Source2: which contains the local tar.bz2 that I have.
> There is no error in the compilation but fedpkg build seems to have an error that I do not
> seem to get:
>
>  aarem's pdf-stapler-1.0.0-1.fc32 failed to build
>     http://koji.fedoraproject.org/koji/buildinfo?buildID=1424956 
It appears that the tests defined in the %check section download some
files over the internet and since koji does not allow internet access,
the test suite is failing. I did not check what is defined in the test
suite, but your options are to disable checks, include the test files
as separate sources or package them as new packages (going through the
review process), depending on their nature.


0. https://fedoraproject.org/wiki/Packaging:SourceURL
1. https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)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/[e-mail]

[José Abílio Matos]

On Friday, 27 December 2019 14.50.16 WET Globe Trotter via devel wrote:
>  Thank you!
>  
>  
>  Here is my updated spec file:
>  
>  $ fpaste pdf-stapler.spec
>  Uploading (4.8KiB)...
>  https://paste.centos.org/view/6ddc6eec
>  
>  However, I can not change the directory to a stapler directory. I get the
>  following error:
>  
>  + cd stapler-1.0.0
>  /var/tmp/rpm-tmp.2ZnEy2: line 38: cd: stapler-1.0.0: No such file or
>  directory error: Bad exit status from /var/tmp/rpm-tmp.2ZnEy2 (%prep)
>  
>  Thanks again for your help! 
In lines 43-44 you have:

%prep
%setup -q -n stapler-%{version}

the last line should be:
%setup -q -n stapler

as you said the directory name does not have the version in it. :-)
-- 
José Abílio

[Globe Trotter]

 Thanks!

    On Friday, December 27, 2019, 9:32:29 AM CST, José Abílio Matos
<jamatos(a)fc.up.pt&gt; wrote: 

>  in lines 43-44 you have: 
 
>  %prep
>  %setup -q -n stapler-%{version} 
>  the last line should be:
>  %setup -q -n stapler 
as you said the directory name does not have the version in it. :-)

I tried: 

%setup -q -n  stapler-%{commit}

mv: cannot stat
'/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-0.1.20191215git8753251.fc31.x86_64//usr/bin/stapler-875325103234b4a3ed96a4a5167ff78c291edbff':
No such file or directoryerror: Bad exit status from /var/tmp/rpm-tmp.dbb8Yr (%install)


Sorry, I am still lost. Here is my updated spec file.

https://paste.centos.org/view/a2d17d1a

[Rodger Etz]

What happens when you try this?

%setup -q -n pdf-stapler

Do not append anything after pdf-stapler

BR,

Brownsen

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, 27. December 2019 17:04, Globe Trotter via devel
<devel(a)lists.fedoraproject.org&gt; wrote:

>  Thanks!
>
>  On Friday, December 27, 2019, 9:32:29 AM CST, José Abílio Matos <jamatos(a)fc.up.pt&gt;
> wrote:
>
> > in lines 43-44 you have:
>
> > %prep
> > %setup -q -n stapler-%{version}
>
> > the last line should be:
> > %setup -q -n stapler
>
>  as you said the directory name does not have the version in it. :-)
>
>  I tried:
>
>  %setup -q -n  stapler-%{commit}
>  mv: cannot stat
> '/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-0.1.20191215git8753251.fc31.x86_64//usr/bin/stapler-875325103234b4a3ed96a4a5167ff78c291edbff':
> No such file or directory
>  error: Bad exit status from /var/tmp/rpm-tmp.dbb8Yr (%install)
>
>  Sorry, I am still lost. Here is my updated spec file.
>
>  https://paste.centos.org/view/a2d17d1a

[Alexander Ploumistos]

Hello again,

Replace the mv line you have in your spec file with this:
rm %{buildroot}%{_bindir}/stapler

Also, do you really need to declare PKG-INFO as documentation? It's
included with the egg metadata. If you remove it from your %files
section, the package builds fine. If you are intent on keeping it
declared, you will have to copy it to your buildroot (I think).

On Fri, Dec 27, 2019 at 5:04 PM Globe Trotter via devel
<devel(a)lists.fedoraproject.org&gt; wrote:
>
> Thanks!
>
> On Friday, December 27, 2019, 9:32:29 AM CST, José Abílio Matos
<jamatos(a)fc.up.pt&gt; wrote:
>
>
> > in lines 43-44 you have:
>
> > %prep
> > %setup -q -n stapler-%{version}
>
> > the last line should be:
> > %setup -q -n stapler
>
> as you said the directory name does not have the version in it. :-)
>
>
> I tried:
>
> %setup -q -n  stapler-%{commit}
>
> mv: cannot stat
'/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-0.1.20191215git8753251.fc31.x86_64//usr/bin/stapler-875325103234b4a3ed96a4a5167ff78c291edbff':
No such file or directory
> error: Bad exit status from /var/tmp/rpm-tmp.dbb8Yr (%install)
>
>
> Sorry, I am still lost. Here is my updated spec file.
>
>
> https://paste.centos.org/view/a2d17d1a
>
>
>
>
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)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/[e-mail]

[Globe Trotter]

 Thanks! This seems to compile again, but I can't tell what happened with koji:
https://koji.fedoraproject.org/koji/taskinfo?taskID=39956986
Sorry, I am very lost. My earleir spec file was fine with the python2 version.
Any further suggestion/help? Here is the updated spec file:
$ fpaste pdf-stapler.spec
Uploading (5.0KiB)...
https://paste.centos.org/view/3a4fe4d6






    On Friday, December 27, 2019, 6:26:37 PM EST, Alexander Ploumistos
<alex.ploumistos(a)gmail.com&gt; wrote:  
 
 Hello again,

Replace the mv line you have in your spec file with this:
rm %{buildroot}%{_bindir}/stapler

Also, do you really need to declare PKG-INFO as documentation? It's
included with the egg metadata. If you remove it from your %files
section, the package builds fine. If you are intent on keeping it
declared, you will have to copy it to your buildroot (I think).

On Fri, Dec 27, 2019 at 5:04 PM Globe Trotter via devel
<devel(a)lists.fedoraproject.org&gt; wrote:
>  Thanks!
>
>  On Friday, December 27, 2019, 9:32:29 AM CST, José Abílio Matos <jamatos(a)fc.up.pt&gt;
> wrote:
>
>
>  > in lines 43-44 you have:
>
>  > %prep
>  > %setup -q -n stapler-%{version}
>
>  > the last line should be:
>  > %setup -q -n stapler
>
>  as you said the directory name does not have the version in it. :-)
>
>
>  I tried:
>
>  %setup -q -n  stapler-%{commit}
>
>  mv: cannot stat
> '/home/aarem/rpmbuild/BUILDROOT/pdf-stapler-1.0.0-0.1.20191215git8753251.fc31.x86_64//usr/bin/stapler-875325103234b4a3ed96a4a5167ff78c291edbff':
> No such file or directory
>  error: Bad exit status from /var/tmp/rpm-tmp.dbb8Yr (%install)
>
>
>  Sorry, I am still lost. Here is my updated spec file.
>
>
>  https://paste.centos.org/view/a2d17d1a
>
>
>
>
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)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/[e-mail]
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)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/[e-mail]

[Alexander Ploumistos]

On Sat, Dec 28, 2019 at 7:35 AM Globe Trotter via devel
<devel(a)lists.fedoraproject.org&gt; wrote:
>  Thanks! This seems to compile again, but I can't tell what happened with koji:
>
>  https://koji.fedoraproject.org/koji/taskinfo?taskID=39956986 
Besides koji misbehaving in general in the last few days, you have
uploaded an older source rpm (or you gave the link to the wrong koji
task).

[Alexander Ploumistos]

On Sat, Dec 28, 2019 at 7:35 AM Globe Trotter via devel
<devel(a)lists.fedoraproject.org&gt; wrote:
>  Any further suggestion/help? Here is the updated spec file:
>
>  $ fpaste pdf-stapler.spec
>  Uploading (5.0KiB)...
>  https://paste.centos.org/view/3a4fe4d6
>  
Oh, there's also a problem with your changelog entries, the last three
have 1.0.0-1 as the version. Since there hasn't been a successful koji
build yet, change them to
1.0.0-0.2.20191215git8753251
1.0.0-0.1.20191215git8753251
etc.

The egg metadata state that the current version is a 1.0.0 release
candidate, so the 0.x versioning is correct.

[Globe Trotter]

 Thanks! There was an issue with koji and me. Now the update has been built and submitted
for testing. Should I fix the egg issue? How.Thanks!

    On Saturday, December 28, 2019, 3:34:30 AM EST, Alexander Ploumistos
<alex.ploumistos(a)gmail.com&gt; wrote:  
 
 On Sat, Dec 28, 2019 at 7:35 AM Globe Trotter via devel
<devel(a)lists.fedoraproject.org&gt; wrote:
>  Any further suggestion/help? Here is the updated spec file:
>
>  $ fpaste pdf-stapler.spec
>  Uploading (5.0KiB)...
>  https://paste.centos.org/view/3a4fe4d6
>  
Oh, there's also a problem with your changelog entries, the last three
have 1.0.0-1 as the version. Since there hasn't been a successful koji
build yet, change them to
1.0.0-0.2.20191215git8753251
1.0.0-0.1.20191215git8753251
etc.

The egg metadata state that the current version is a 1.0.0 release
candidate, so the 0.x versioning is correct.
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)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/[e-mail]

[Alexander Ploumistos]

You are welcome. Sorry for the HTML, I am away from home.

On Sat, Dec 28, 2019, 15:12 Globe Trotter via devel <
devel(a)lists.fedoraproject.org&gt; wrote:

>  Thanks! There was an issue with koji and me. Now the update has been
> built
>  and submitted for testing. Should I fix the egg issue? How.
>  Thanks!
>  
I am not sure there is an "egg issue", but that's something you should
check with our python gurus. I remember that there is a section on
packaging egg stuff in our Packaging guidelines, you can search for that
page and see if you're adhering to it.

Best regards,
Alex

[Globe Trotter]

 Sorry, no problem.I was referring to the following:
"The egg metadata state that the current version is a 1.0.0 release candidate, so the
0.x versioning is correct."
But I guess that it is perhaps fine now. 

Thanks!



    On Saturday, December 28, 2019, 9:31:47 AM EST, Alexander Ploumistos
<alex.ploumistos(a)gmail.com&gt; wrote:  
 
 You are welcome. Sorry for the HTML, I am away from home.

On Sat, Dec 28, 2019, 15:12 Globe Trotter via devel <devel(a)lists.fedoraproject.org&gt;
wrote:

 Thanks! There was an issue with koji and me. Now the update has been built and submitted
for testing. Should I fix the egg issue? How.Thanks!


I am not sure there is an "egg issue", but that's something you should check
with our python gurus. I remember that there is a section on packaging egg stuff in our
Packaging guidelines, you can search for that page and see if you're adhering to it.
Best regards,Alex
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)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/[e-mail]

[Globe Trotter]

 I got the following:
https://bodhi.fedoraproject.org/updates/FEDORA-2019-2b1eed3d9d
Failed to talk to greenwave. How do I go about fixing it?

Thanks!

    On Saturday, December 28, 2019, 9:31:47 AM EST, Alexander Ploumistos
<alex.ploumistos(a)gmail.com&gt; wrote:  
 
 You are welcome. Sorry for the HTML, I am away from home.

On Sat, Dec 28, 2019, 15:12 Globe Trotter via devel <devel(a)lists.fedoraproject.org&gt;
wrote:

 Thanks! There was an issue with koji and me. Now the update has been built and submitted
for testing. Should I fix the egg issue? How.Thanks!


I am not sure there is an "egg issue", but that's something you should check
with our python gurus. I remember that there is a section on packaging egg stuff in our
Packaging guidelines, you can search for that page and see if you're adhering to it.
Best regards,Alex
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)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/[e-mail]

[Kevin Fenzi]

On Sun, Dec 29, 2019 at 02:45:20PM +0000, Globe Trotter via devel wrote:
>   I got the following:
>  https://bodhi.fedoraproject.org/updates/FEDORA-2019-2b1eed3d9d
>  Failed to talk to greenwave. How do I go about fixing it? 
Nothing to do on your end, something was not working right in the stack
of things that greenwave needs. I've restarted things and it appears
working now.

kevin

[Globe Trotter]

 Thanks, I will ignore it then.

    On Sunday, December 29, 2019, 9:14:54 AM CST, Kevin Fenzi <kevin(a)scrye.com&gt;
wrote:  
 
 On Sun, Dec 29, 2019 at 02:45:20PM +0000, Globe Trotter via devel wrote:
>   I got the following:
>  https://bodhi.fedoraproject.org/updates/FEDORA-2019-2b1eed3d9d
>  Failed to talk to greenwave. How do I go about fixing it? 
Nothing to do on your end, something was not working right in the stack
of things that greenwave needs. I've restarted things and it appears
working now.

kevin
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)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/[e-mail]