https://bugzilla.redhat.com/show_bug.cgi?id=1638994
Mattia Verga changed:
What|Removed |Added
Status|POST|CLOSED
Resolution|---
https://bugzilla.redhat.com/show_bug.cgi?id=1638994
--- Comment #21 from Jonathan Wakely ---
Or you should depend on the %{version}-%release} of *boost* not the %{release}
of your package. The %{release} of your package should be independent of the
boost one.
--
You are receiving this mail be
https://bugzilla.redhat.com/show_bug.cgi?id=1638994
--- Comment #20 from Jonathan Wakely ---
That seems right to me. You should not have to rebuild boost-python3 for every
change to boost (and vice versa).
A change to the RHEL boost-1.53.0 package *might* require a rebuild for
boost-python3 bu
https://bugzilla.redhat.com/show_bug.cgi?id=1638994
--- Comment #19 from Andrea ---
ok, i had to relax the dependencies over boost-devel then ( version and not
version-release ), hope this is not an issue
thanks
Andrea
--
You are receiving this mail because:
You are on the CC list for the bu
https://bugzilla.redhat.com/show_bug.cgi?id=1638994
--- Comment #17 from Andrea ---
sorry to bother..but i made a stupid mistake..
i first build the package in EPEL7 without making the changes with discussed
(adding static packages and remove not needed patches) and i forgot to run it
as scrat
https://bugzilla.redhat.com/show_bug.cgi?id=1638994
--- Comment #18 from Robert-André Mauchin ---
You can't. You need to bump the Release tag with your changes and build it
again. There is no undo button for this.
--
You are receiving this mail because:
You are on the CC list for the bug.
You
https://bugzilla.redhat.com/show_bug.cgi?id=1638994
--- Comment #16 from Gwyn Ciesla ---
(fedscm-admin): The Pagure repository was created at
https://src.fedoraproject.org/rpms/boost-python3
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified a
https://bugzilla.redhat.com/show_bug.cgi?id=1638994
--- Comment #15 from Andrea ---
Hi Jonathan
thanks for your comments, i'm going to drop the not needed lib and patches.
Regarding the missing static, OpenMPI and MPICH packages, i have to admit that
i decided to package only what i need for m
https://bugzilla.redhat.com/show_bug.cgi?id=1638994
--- Comment #14 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #13)
> This EPEL package doesn't provide Did you decide not to provide Python3
Oops, I lost a word there. That was meant to say:
This EPEL package doesn't pro
https://bugzilla.redhat.com/show_bug.cgi?id=1638994
--- Comment #13 from Jonathan Wakely ---
In RHEL there are subpackages which include Python2 modules for OpenMPI and
MPICH:
%files openmpi-python
%defattr(-, root, root, -)
%doc LICENSE_1_0.txt
%{_libdir}/openmpi/lib/libboost_mpi_python*.so.%
https://bugzilla.redhat.com/show_bug.cgi?id=1638994
--- Comment #12 from Jonathan Wakely ---
> Source2: libboost_thread-mt.so
This can be dropped, it's only needed for the boost-thread subpackage in the
main RHEL boost package.
Most of the patches can be dropped as they aren't relevant to Bo
https://bugzilla.redhat.com/show_bug.cgi?id=1638994
--- Comment #11 from Jonathan Wakely ---
(In reply to Igor Gnatenko from comment #9)
> why isn't it called python3-boost? ;)
Please, let's not start this again! Somebody changed the boost-python3 packages
in Fedora to be python3-boost and I h
https://bugzilla.redhat.com/show_bug.cgi?id=1638994
--- Comment #10 from Andrea ---
Hi Igor,
i used the name of the package already available in F28, should i move to the
new naming convention also in EPEL7
thanks
Andrea
--
You are receiving this mail because:
You are on the CC list for the b
https://bugzilla.redhat.com/show_bug.cgi?id=1638994
Igor Gnatenko changed:
What|Removed |Added
CC||i.gnatenko.br...@gmail.com
--- Commen
https://bugzilla.redhat.com/show_bug.cgi?id=1638994
--- Comment #8 from Andrea ---
thanks a lot for your help!
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
__
https://bugzilla.redhat.com/show_bug.cgi?id=1638994
--- Comment #7 from Robert-André Mauchin ---
If you have trouble rebuilding your SRPM, just use this where you have your
SPEC and sources:
rpmbuild --define "python3_pkgversion 34" --define "_sourcedir $PWD" --define
"_srcrpmdir $PWD" --targe
https://bugzilla.redhat.com/show_bug.cgi?id=1638994
Robert-André Mauchin changed:
What|Removed |Added
Status|NEW |POST
Assignee|nob...@f
17 matches
Mail list logo