Spec URL: http://www.fateyev.com/RPMS/Fedora22/perl-Sereal.spec
SRPM URL: http://www.fateyev.com/RPMS/Fedora22/perl-Sereal-3.014-1.fc24.src.rpm
Description: Sereal is an efficient, compact-output, binary and feature-rich serialization protocol. The Perl encoder is implemented as the Sereal::Encoder module, the Perl decoder correspondingly as Sereal::Decoder. They are distributed separately to allow for safe upgrading without downtime.
(Hint: Upgrade the decoder everywhere first, then the encoder.)
Fedora Account System Username: dfateyev
Koji scratch build:
In the future also planned for epel7.
This is already in Fedora.
*** This bug has been marked as a duplicate of bug 1267198 ***
Sorry, the same issue as with RHBZ #1305266.
Could you provide epel7 branch with the package (supporting perl-Sereal-Encoder, perl-Sereal-Decoder, etc. packages there, too), or you aren't interested and I should request epel7 branch by myself?
The same response as in bug 1305266 :)
I'm not much interested in EPEL. I saw you had already asked for the branches and I forwarded them to relengs to create the branches for you.
Don't forget the two Sereal packages requires themselves for tests. You will have to insert %perl_boostrap macro definition into one of them, then build them and then remove the definition and rebuild the package again.
OK. Thanks for the details on bootstrap.
"perl-Sereal" package epel7 provision and update progress.
perl-Sereal-3.003-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-b62e983e59
perl-Sereal-3.003-1.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-b62e983e59
perl-Sereal-3.003-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.