[Bug 1792997] vim fails to build in Fedora rawhide: could not
configure perl: cc1: fatal error: inaccessible plugin file plugin/annobin.so
expanded from short plugin name annobin: No such file or directory
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1792997
Petr Pisar <ppisar(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |caillon+fedoraproject@gmail
| |.com, iarnell(a)gmail.com,
| |jplesnik(a)redhat.com,
| |kasal(a)ucw.cz,
| |mmaslano(a)redhat.com,
| |perl-devel(a)lists.fedoraproj
| |ect.org,
| |psabata(a)redhat.com,
| |rhughes(a)redhat.com,
| |sandmann(a)redhat.com,
| |tcallawa(a)redhat.com
Component|vim |perl
Assignee|karsten(a)redhat.com |jplesnik(a)redhat.com
Summary|vim fails to build in |vim fails to build in
|Fedora rawhide: could not |Fedora rawhide: could not
|configure perl |configure perl: cc1: fatal
| |error: inaccessible plugin
| |file plugin/annobin.so
| |expanded from short plugin
| |name annobin: No such file
| |or directory
--- Comment #2 from Petr Pisar <ppisar(a)redhat.com> ---
I confirm that current rpm-build CFLAGS do not lost
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 option. It seems they also
removed a dependency on (annobin if gcc) from redhat-rpm-config. Thus when
building against Perl, Perl adds that build option, but no annobin plugin is
found on the system.
I will rebuild perl. That should fix it.
--
You are receiving this mail because:
You are on the CC list for the bug.
4 years, 4 months
[Bug 1792689] New: perl-IO-Tty-1.14 is available
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1792689
Bug ID: 1792689
Summary: perl-IO-Tty-1.14 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-IO-Tty
Keywords: FutureFeature, Triaged
Assignee: tcallawa(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: jose.p.oliveira.oss(a)gmail.com, paul(a)city-fan.org,
perl-devel(a)lists.fedoraproject.org, steve(a)silug.org,
tcallawa(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 1.14
Current version/release in rawhide: 1.12-16.fc31
URL: http://search.cpan.org/dist/IO-Tty/
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/7281/
--
You are receiving this mail because:
You are on the CC list for the bug.
4 years, 4 months
[Bug 1792078] New: perl-TimeDate-2.31 is available
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1792078
Bug ID: 1792078
Summary: perl-TimeDate-2.31 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-TimeDate
Keywords: FutureFeature, Triaged
Assignee: jplesnik(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: caillon+fedoraproject(a)gmail.com, caolanm(a)redhat.com,
john.j5live(a)gmail.com, jplesnik(a)redhat.com,
kasal(a)ucw.cz, perl-devel(a)lists.fedoraproject.org,
rhughes(a)redhat.com, rstrode(a)redhat.com,
sandmann(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 2.31
Current version/release in rawhide: 2.30-19.fc32
URL: http://search.cpan.org/dist/TimeDate/
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/3463/
--
You are receiving this mail because:
You are on the CC list for the bug.
4 years, 4 months