Red Hat Bugzilla – Bug 226048
Merge Review: libtheora
Last modified: 2016-12-20 06:58:14 EST
Fedora Merge Review: libtheora
Initial Owner: firstname.lastname@example.org
Almost ready for approval (see Maybe and Bad section)
- Package name matches upstream
- Spec file name matches base package name
- License matches actual license, included in %doc, is FLOSS
- Spec written in American English, is legible
- Source matches upstream
- Package builds fine on all supported architectures
- Build requirements complete
- ldconfig called properly
- directory ownerships OK
- files listing: no duplicates
- file permissions OK
- Inter-dependencies OK
- Why --enable-static=yes ?
E: libtheora invalid-version 1.0alpha7
according to the Naming Guidelines, the 'alpha' part should be
part of the release tag
W: libtheora-devel summary-ended-with-dot
E: theora-tools binary-or-shlib-defines-rpath
No documentation for libtheora-devel and theora-tools, but that's fine
- Source URL not provided. Also, use .tar.bz2 instead of .tar.gz?
All the Bads and Maybes seem to be fixed in the current rawhide package, except
for the version. The only way to fix it that I can see would be to add an epoch,
since rpm considers 1.0alpha > 1.0. Is this worth an epoch ?
Introducing an Epoch should be delayed as long as it makes sense. The next
upstream version might for example be "1.1" instead of "1.0" which would mean an
Epoch introduced today would have had only negative effects.
I guess we'll have to wait until a stable version is out (hopefully it won't be
Closing this bug, since in this case it's a review of an existing package and
there's no owner set
I would like to request early branching for F-10 of libtheora
Package Change Request
Package Name: libtheora
New Branches: F-9
(In reply to comment #3)
Re-opening the review.
> Introducing an Epoch should be delayed as long as it makes sense.
We do need to fix this now. See: https://bugzilla.redhat.com/478651
Mass reassigning all merge reviews to their component. For more details, see this FESCO ticket:
If you don't know what merge reviews are about, please see:
How to handle this bug is left to the discretion of the package maintainer.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.
(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)
More information and reason for this action is here:
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.