Hi,
perl-Language-Expr FTBFS in rawhide and F20 (since F20 was rawhide). There is some crazy stuff in Perl itself that prevents perl-Regexp-Grammars to work properly and perl-Language-Expr cannot work without proper perl-Regexp-Grammars.
This leads to perl-Language-Expr in F20 being from F19 and having unresolved dependencies on perl(:MODULE_COMPAT_5.16.2).
* It makes mess when updating F19 to F20 * It emails me on daily basic * I cannot fix it
However, new version of upstream Language::Expr is out, that disables tests, while still not being functional. I would like to update perl-Language-Expr in F20 and rawhide. That would lead to:
* No more mess * No more email for me * Nonfunctional package in Fedora
While I believe that nonfunctional package is a bad think, I believe that anything is better than the situation now.
Any thoughts?
Links:
https://bugzilla.redhat.com/show_bug.cgi?id=992666 perl-Language-Expr: FTBFS in rawhide
https://bugzilla.redhat.com/show_bug.cgi?id=997835 perl-Language-Expr-0.23 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1009919 perl-5.18: Regexp::Grammars does not work due to bug in perl
On Wed, May 14, 2014 at 01:08:51PM +0200, Miro Hrončok wrote:
Hi,
perl-Language-Expr FTBFS in rawhide and F20 (since F20 was rawhide). There is some crazy stuff in Perl itself that prevents perl-Regexp-Grammars to work properly and perl-Language-Expr cannot work without proper perl-Regexp-Grammars.
This leads to perl-Language-Expr in F20 being from F19 and having unresolved dependencies on perl(:MODULE_COMPAT_5.16.2).
- It makes mess when updating F19 to F20
- It emails me on daily basic
- I cannot fix it
However, new version of upstream Language::Expr is out, that disables tests, while still not being functional. I would like to update perl-Language-Expr in F20 and rawhide. That would lead to:
- No more mess
- No more email for me
- Nonfunctional package in Fedora
While I believe that nonfunctional package is a bad think, I believe that anything is better than the situation now.
Any thoughts?
It sounds like this would just hide the issues from you. If it's nonfunctional, why not retire perl-Language-Expr instead?
-Toshio
Links:
https://bugzilla.redhat.com/show_bug.cgi?id=992666 perl-Language-Expr: FTBFS in rawhide
https://bugzilla.redhat.com/show_bug.cgi?id=997835 perl-Language-Expr-0.23 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1009919 perl-5.18: Regexp::Grammars does not work due to bug in perl
Dne 14.5.2014 16:38, Toshio Kuratomi napsal(a):
It sounds like this would just hide the issues from you. If it's nonfunctional, why not retire perl-Language-Expr instead?
1) Retiring the package would not solve the F19 to F20 update issue 2) The bug in Perl is supposed to be fixed in near future, however I'm not quite sure when
On Wed, May 14, 2014 at 05:43:14PM +0200, Miro Hrončok wrote:
Dne 14.5.2014 16:38, Toshio Kuratomi napsal(a):
It sounds like this would just hide the issues from you. If it's nonfunctional, why not retire perl-Language-Expr instead?
- Retiring the package would not solve the F19 to F20 update issue
- The bug in Perl is supposed to be fixed in near future, however I'm
not quite sure when
But you say it's been non-functional in Fedora 20 since before release? If you think it'll be fixed soon, maybe a half measure would be to have the perl package Obsolete perl-Language-Expr to get it off the user's systems but don't retire it yet. If you don't think that it will be fixed soon (for instance, there's no commitment by anyone that they are working on the issue) then it's likely you do want to retire the package on rawhide in addition to throwing in the Obsoletes. The package is just a re-review away from being brought back when the problems are fixed.
We really don't want to be shipping packages that are irretrievably broken to users. And shipping another package that has no purpose to hide the fact that the first package is broken to the package maintainer just doesn't seem right. Really the system is emailing you because as package maintainer you're supposed to fix the software. If you can't then we likely don't want the software in Fedora until the issue can be resolved. :-(
-Toshio
packaging@lists.fedoraproject.org