[Bug 483772] New: SVK fails because it cannot find Time/Progress.pm
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: SVK fails because it cannot find Time/Progress.pm
https://bugzilla.redhat.com/show_bug.cgi?id=483772
Summary: SVK fails because it cannot find Time/Progress.pm
Product: Fedora
Version: 10
Platform: All
OS/Version: Linux
Status: NEW
Severity: urgent
Priority: low
Component: perl-SVK
AssignedTo: ianburrell(a)gmail.com
ReportedBy: warlord(a)mit.edu
QAContact: extras-qa(a)fedoraproject.org
CC: ianburrell(a)gmail.com,
fedora-perl-devel-list(a)redhat.com
Classification: Fedora
Description of problem:
I just upgraded Fedora 10 yesterday and this morning I noticed that SVK isn't
working anymore. When I try to sync I get:
Can't locate Time/Progress.pm in @INC (@INC contains:
/usr/lib/perl5/5.10.0/i386-linux-thread-multi /usr/lib/perl5/5.10.0
/usr/local/lib/perl5/site_perl/5.10.0/i386-linux-thread-multi
/usr/local/lib/perl5/site_perl/5.10.0
/usr/lib/perl5/vendor_perl/5.10.0/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.10.0 /usr/lib/perl5/vendor_perl
/usr/local/lib/perl5/site_perl .) at
/usr/lib/perl5/vendor_perl/5.10.0/SVK/Notify.pm line 214.
Version-Release number of selected component (if applicable):
perl-SVK-2.2.1-1.fc10.noarch
How reproducible:
Seems to happen every time I try to use "svk sync".
Some other svk operations seem to work okay.
Steps to Reproduce:
1. yum update (as of 2009-02-03 10:20am US/EST)
2. svk sync <depotpath>
3.
Actual results:
See above
Expected results:
It should sync.
Additional info:
I cannot find Time/Progress.pm in a package.. And indeed the perl-SVK RPM
doesn't depend on perl(Time/Progress.pm) for some odd reason... Probably
because the "require Time/Progress.pm" is within a subroutine instead of
global?
But this bug makes SVK practically useless.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
13 years, 1 month
[Bug 620410] New: perl-Devel-Cycle - Request for EL-6 branch
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: perl-Devel-Cycle - Request for EL-6 branch
https://bugzilla.redhat.com/show_bug.cgi?id=620410
Summary: perl-Devel-Cycle - Request for EL-6 branch
Product: Fedora EPEL
Version: el6
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: perl-Devel-Cycle
AssignedTo: rob.myers(a)gtri.gatech.edu
ReportedBy: paul(a)city-fan.org
QAContact: extras-qa(a)fedoraproject.org
CC: rob.myers(a)gtri.gatech.edu,
fedora-perl-devel-list(a)redhat.com
Classification: Fedora
perl-Devel-Cycle is included in EL-6 optional packages, but not on all
architectures (e.g. it is missing from ppc64), which is a problem when building
packages that depend on it in EPEL-6.
Please could we have an EPEL EL-6 branch built using the RHEL-6 SRPM to provide
it for the other arches. I (pghmcfc) am willing to (co)maintain.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
13 years, 1 month
[Bug 671389] New: perl-RPM2 cannot be compile against rpm-4.9.0
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: perl-RPM2 cannot be compile against rpm-4.9.0
https://bugzilla.redhat.com/show_bug.cgi?id=671389
Summary: perl-RPM2 cannot be compile against rpm-4.9.0
Product: Fedora
Version: rawhide
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: perl-RPM2
AssignedTo: mmaslano(a)redhat.com
ReportedBy: ppisar(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: fedora-perl-devel-list(a)redhat.com,
mmaslano(a)redhat.com, lkundrak(a)v3.sk
Classification: Fedora
rpm-4.9.0_beta1 Changelog:
- Since rpm 4.1 times, callers are supposed to use the rpmtsFooDB()
variants instead of the lower-level rpmdb functions, and mixing
them is not safe. Enforce the use of ts-level versions by making
rpmdbLink(), rpmdbOpen(), rpmdbInit(), rpmdbClose(),
rpmdbSync(), rpmdbVerify() and rpmdbRebuild() internal-only.
Thus perl-RPM2 cannot be linked at run-time:
Can't load 'blib/arch/auto/RPM2/RPM2.so' for module RPM2:
blib/arch/auto/RPM2/RPM2.so: undefined symbol: rpmdbOpen at
/usr/lib64/perl5/DynaLoader.pm line 200.
perl-RPM2 uses the old low level function only.
Should we drop this package in favor of (not yet packaged) RPM4?
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
13 years, 1 month
[Bug 691451] New: Rebuild required to work correctly with perl 5.012003.
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Rebuild required to work correctly with perl 5.012003.
https://bugzilla.redhat.com/show_bug.cgi?id=691451
Summary: Rebuild required to work correctly with perl 5.012003.
Product: Fedora
Version: 14
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: unspecified
Priority: unspecified
Component: perl-Devel-Cover
AssignedTo: tcallawa(a)redhat.com
ReportedBy: berrange(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: tcallawa(a)redhat.com, fedora-perl-devel-list(a)redhat.com
Classification: Fedora
Story Points: ---
Description of problem:
Any attempt to use perl-Devel-Cover in fully updated Fedora 14, results in a
warning printed
This version of Devel::Cover was built with Perl version 5.012000.
It is now being run with Perl version 5.012003.
Attempting to make adjustments, but you may find that some of your modules do
not have coverage data collected. You may need to alter the +-inc, +-ignore
and +-select options.
At the very least, this is obscuring real problems with doing coverage testing
of unit tests, but is also causing potentially incorrect results.
A simple rebuild of the RPM should solve it.
Version-Release number of selected component (if applicable):
perl-5.12.3-141.fc14.x86_64
perl-Devel-Cover-0.66-1.fc14.x86_64
How reproducible:
Always
Steps to Reproduce:
1.$ perl -MDevel::Cover -e ''
2.
3.
Actual results:
This version of Devel::Cover was built with Perl version 5.012000.
It is now being run with Perl version 5.012003.
Attempting to make adjustments, but you may find that some of your modules do
not have coverage data collected. You may need to alter the +-inc, +-ignore
and +-select options.
Expected results:
No warning about incompatible versions
Additional info:
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
13 years, 1 month