[users] perl-Encode error

[Khusro Jaleel]

Hi,

I am trying to install the package 'perl-Encode' from rpmforge on a
CentOS machine with EPEL also enabled. I am using the priorities plugin
so Base, EPEL and RPMForge all have different priorities, however I get
the following error from yum. Any ideas as to how to fix this appreciated

Thanks,


=====================================================================================

Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
* addons: mirror.sov.uk.goscomb.net
* base: mirror.sov.uk.goscomb.net
* epel: mirror01.th.ifl.net
* extras: mirror.ox.ac.uk
* rpmforge: apt.sw.be
* updates: mirror.ox.ac.uk
3559 packages excluded due to repository priority protections
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package perl-Encode.x86_64 0:2.39-1.el5.rf set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

============================================================================================================================================
Package Arch
Version Repository Size
============================================================================================================================================
Installing:
perl-Encode x86_64
2.39-1.el5.rf rpmforge 3.0 M

Transaction Summary
============================================================================================================================================
Install 1 Package(s)
Upgrade 0 Package(s)

Total size: 3.0 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test


Transaction Check Error:
file /usr/bin/enc2xs from install of perl-Encode-2.39-1.el5.rf.x86_64
conflicts with file from package perl-5.8.8-32.el5_5.2.x86_64
file /usr/bin/piconv from install of perl-Encode-2.39-1.el5.rf.x86_64
conflicts with file from package perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man1/enc2xs.1.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man1/piconv.1.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Alias.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::CJKConstants.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::CN::HZ.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Config.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Encoder.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Encoding.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Guess.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::JP::H2Z.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::JP::JIS7.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::KR::2022_KR.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::MIME::Header.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::PerlIO.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Supported.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Unicode::UTF7.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/encoding.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64

Error Summary
-------------
=====================================================================================

[Yury V. Zaytsev]

Post by Khusro Jaleel
file /usr/bin/enc2xs from install of perl-Encode-2.39-1.el5.rf.x86_64
conflicts with file from package perl-5.8.8-32.el5_5.2.x86_64
file /usr/bin/piconv from install of perl-Encode-2.39-1.el5.rf.x86_64

Sounds like more than a man conflict that we can ignore :-(

File a bug at RH to repackage it as a separate entity?

[Steve Huff]

Post by Yury V. Zaytsev

Post by Khusro Jaleel
file /usr/bin/enc2xs from install of perl-Encode-2.39-1.el5.rf.x86_64
conflicts with file from package perl-5.8.8-32.el5_5.2.x86_64
file /usr/bin/piconv from install of perl-Encode-2.39-1.el5.rf.x86_64

Sounds like more than a man conflict that we can ignore :-(
File a bug at RH to repackage it as a separate entity?

no, that's not the case; it looks like Encode 2.12 is part of Perl 5.8.8 core, and unfortunately, RH is technically doing the right thing by packaging Encode as part of the perl-5.8.8 RPM.

for our part, it means that perl-Encode needs an rfx tag, since if Khusro forces an install of perl-Encode-2.39, then he's breaking his existing perl package, and he should be aware of it.

Khusro, why are you trying to install a newer Encode than provided? do you specifically need a version later than 2.12? why?

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
PGP 8477B706 (A92A 1F7E 6D76 16A0 BFF9 E61D AD54 0251 8477 B706)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.repoforge.org/pipermail/users/attachments/20101213/334392ff/attachment.bin

[Khusro Jaleel]

Post by Steve Huff
for our part, it means that perl-Encode needs an rfx tag, since if Khusro forces an install of perl-Encode-2.39, then he's breaking his existing perl package, and he should be aware of it.
Khusro, why are you trying to install a newer Encode than provided? do you specifically need a version later than 2.12? why?

I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(

So does this mean that in this case, I can only really install the
latest version of RT by satisfying all the dependencies using CPAN?
There is no other way to do it is there? I don't have the option of
using RT 3.6 that EPEL packages because I'm trying to migrate an
existing 3.8 system to a CentOS box.

Thanks,
Khusro

[Steve Huff]

So does this mean that in this case, I can only really install the latest version of RT by satisfying all the dependencies using CPAN? There is no other way to do it is there? I don't have the option of using RT 3.6 that EPEL packages because I'm trying to migrate an existing 3.8 system to a CentOS box.

no; it means that if you need newer versions of core Perl modules (which it sounds like you do), then you need to break your perl-5.8.8 package a bit. the good news is that RPMforge Perl modules install into the vendor_perl branch, so they shouldn't be clobbering the actual .pm files, but you will have to install with rpm --excludedocs to get past the man page conflicts (or with --force if you want the update man pages).

RT is indeed difficult to install under RHEL, especially recent versions; honestly, if you can, you may want to wait until CentOS 6 is out.

installing from CPAN is a bad idea; don't do that.

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
PGP 8477B706 (A92A 1F7E 6D76 16A0 BFF9 E61D AD54 0251 8477 B706)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.repoforge.org/pipermail/users/attachments/20101213/d11b2485/attachment.bin

[Khusro Jaleel]

Post by Steve Huff
RT is indeed difficult to install under RHEL, especially recent versions; honestly, if you can, you may want to wait until CentOS 6 is out.

Unfortunately I can't wait too long, but what is special about CentOS 6
in regards to my specific problem?

Post by Steve Huff
installing from CPAN is a bad idea; don't do that.

In terms of Redhat specific advice, I have been told to:

1. Never mix packages and CPAN, use only one or the other
2. RT people say: Why would you trust some third-party packages? Compile
it yourself!
3. Redhat people say: never use CPAN, only use packages, however it
appears they are slightly broken in this case.

What do real people do to install RT on CentOS? It seems they all ignore
the first advice and just mix CPAN and packages (see [1] and [2]). I
guess there is no other way to really do it. Oh, and they ALL turn OFF
SELinux straight away which is another thing you are NOT supposed to do.

[1] - http://requesttracker.wikia.com/wiki/CentOS5InstallPlusSome
[2] - http://www.ptitov.net/2008/07/request-tracker-installation-o.html

[Steve Huff]

What do real people do to install RT on CentOS? It seems they all ignore the first advice and just mix CPAN and packages (see [1] and [2]).

at my day job we install RT entirely via RPMs, clobbering upstream packages where necessary.

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
PGP 8477B706 (A92A 1F7E 6D76 16A0 BFF9 E61D AD54 0251 8477 B706)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.repoforge.org/pipermail/users/attachments/20101213/eccc5c23/attachment.bin

[William J. Horka]

Post by Steve Huff
at my day job we install RT entirely via RPMs, clobbering upstream packages where necessary.

It's true. If you want to look at our spec file, it's in
http://mirror.hmdc.harvard.edu/HMDC-RT/el5/SRPMS/rt-3.8.8-1.HMDC.RHEL5.src.rpm
.

Please do note that this build has been customized for our environment,
so I wouldn't recommend using it as-is, but it can provide you with a
starting point for packaging RT.

Basically, to gather the list of requirements, all I did was unpack the
RT source, do a ./configure, and then run "make testdeps" through sed:

make testdeps |grep -v "Can't locate" \
|sed -r -e '/^SOME DEPENDENCIES WERE MISSING/,$d' \
-e 's/ \.\.\.found$//' -e 's/ \.\.\.MISSING$//' \
-e '/^[A-Za-z]/s/^/### /' \
-e 's/^[[:space:]]([^[:space:]]+)/perl(\1)/' >alldeps.txt

After building that into an RPM and enabling the RPMforge repo, yum was
able to resolve all but 6 dependencies for RT 3.8.8.

Four of the dependency packages will not install cleanly on RHEL/CentOS5
via yum due to the fact that they conflict with files owned by the
upstream perl package. They must be downloaded manually and installed
with --force. They will also need to be reinstalled after each
subsequent update to the upstream perl package.
perl-File-Temp
perl-Sys-Syslog
perl-Encode
perl-CGI

Two of the dependency packages will not install due to dependency
resolution issues. They must be downloaded and installed manually, but
updates can occur normally:
perl-FCGI
perl-Any-Moose

e.g.
# yumdownloader perl-File-Temp perl-Sys-Syslog \
perl-Encode perl-CGI perl-FCGI perl-Any-Moose
# rpm -Uvh --force perl-File-Temp-*.rpm perl-Sys-Syslog-*.rpm \
perl-Encode-*.rpm perl-CGI-*.rpm perl-FCGI-*.rpm \
perl-Any-Moose-*.rpm

All of the above can be found in RPMforge.

Regards,
-Bill

[William J. Horka]

Post by Steve Huff
at my day job we install RT entirely via RPMs, clobbering upstream packages where necessary.

It's true. If you want to look at our spec file, it's in
http://mirror.hmdc.harvard.edu/HMDC-RT/el5/SRPMS/rt-3.8.8-1.HMDC.RHEL5.src.rpm
.

Please do note that this build has been customized for our environment,
so I wouldn't recommend using it as-is, but it can provide you with a
starting point for packaging RT.

Basically, to gather the list of requirements, all I did was unpack the
RT source, do a ./configure, and then run "make testdeps" through sed:

make testdeps |grep -v "Can't locate" \
|sed -r -e '/^SOME DEPENDENCIES WERE MISSING/,$d' \
-e 's/ \.\.\.found$//' -e 's/ \.\.\.MISSING$//' \
-e '/^[A-Za-z]/s/^/### /' \
-e 's/^[[:space:]]([^[:space:]]+)/perl(\1)/' >alldeps.txt

After building that into an RPM and enabling the RPMforge repo, yum was
able to resolve all but 6 dependencies for RT 3.8.8.

Four of the dependency packages will not install cleanly on RHEL/CentOS5
via yum due to the fact that they conflict with files owned by the
upstream perl package. They must be downloaded manually and installed
with --force. They will also need to be reinstalled after each
subsequent update to the upstream perl package.
perl-File-Temp
perl-Sys-Syslog
perl-Encode
perl-CGI

Two of the dependency packages will not install due to dependency
resolution issues. They must be downloaded and installed manually, but
updates can occur normally:
perl-FCGI
perl-Any-Moose

e.g.
# yumdownloader perl-File-Temp perl-Sys-Syslog \
perl-Encode perl-CGI perl-FCGI perl-Any-Moose
# rpm -Uvh --force perl-File-Temp-*.rpm perl-Sys-Syslog-*.rpm \
perl-Encode-*.rpm perl-CGI-*.rpm perl-FCGI-*.rpm \
perl-Any-Moose-*.rpm

All of the above can be found in RPMforge.

Regards,
-Bill

[William J. Horka]

Post by Steve Huff
at my day job we install RT entirely via RPMs, clobbering upstream packages where necessary.

It's true. If you want to look at our spec file, it's in
http://mirror.hmdc.harvard.edu/HMDC-RT/el5/SRPMS/rt-3.8.8-1.HMDC.RHEL5.src.rpm
.

Please do note that this build has been customized for our environment,
so I wouldn't recommend using it as-is, but it can provide you with a
starting point for packaging RT.

Basically, to gather the list of requirements, all I did was unpack the
RT source, do a ./configure, and then run "make testdeps" through sed:

make testdeps |grep -v "Can't locate" \
|sed -r -e '/^SOME DEPENDENCIES WERE MISSING/,$d' \
-e 's/ \.\.\.found$//' -e 's/ \.\.\.MISSING$//' \
-e '/^[A-Za-z]/s/^/### /' \
-e 's/^[[:space:]]([^[:space:]]+)/perl(\1)/' >alldeps.txt

After building that into an RPM and enabling the RPMforge repo, yum was
able to resolve all but 6 dependencies for RT 3.8.8.

Four of the dependency packages will not install cleanly on RHEL/CentOS5
via yum due to the fact that they conflict with files owned by the
upstream perl package. They must be downloaded manually and installed
with --force. They will also need to be reinstalled after each
subsequent update to the upstream perl package.
perl-File-Temp
perl-Sys-Syslog
perl-Encode
perl-CGI

Two of the dependency packages will not install due to dependency
resolution issues. They must be downloaded and installed manually, but
updates can occur normally:
perl-FCGI
perl-Any-Moose

e.g.
# yumdownloader perl-File-Temp perl-Sys-Syslog \
perl-Encode perl-CGI perl-FCGI perl-Any-Moose
# rpm -Uvh --force perl-File-Temp-*.rpm perl-Sys-Syslog-*.rpm \
perl-Encode-*.rpm perl-CGI-*.rpm perl-FCGI-*.rpm \
perl-Any-Moose-*.rpm

All of the above can be found in RPMforge.

Regards,
-Bill

[William J. Horka]

Post by Steve Huff
at my day job we install RT entirely via RPMs, clobbering upstream packages where necessary.

It's true. If you want to look at our spec file, it's in
http://mirror.hmdc.harvard.edu/HMDC-RT/el5/SRPMS/rt-3.8.8-1.HMDC.RHEL5.src.rpm
.

Please do note that this build has been customized for our environment,
so I wouldn't recommend using it as-is, but it can provide you with a
starting point for packaging RT.

Basically, to gather the list of requirements, all I did was unpack the
RT source, do a ./configure, and then run "make testdeps" through sed:

make testdeps |grep -v "Can't locate" \
|sed -r -e '/^SOME DEPENDENCIES WERE MISSING/,$d' \
-e 's/ \.\.\.found$//' -e 's/ \.\.\.MISSING$//' \
-e '/^[A-Za-z]/s/^/### /' \
-e 's/^[[:space:]]([^[:space:]]+)/perl(\1)/' >alldeps.txt

After building that into an RPM and enabling the RPMforge repo, yum was
able to resolve all but 6 dependencies for RT 3.8.8.

Four of the dependency packages will not install cleanly on RHEL/CentOS5
via yum due to the fact that they conflict with files owned by the
upstream perl package. They must be downloaded manually and installed
with --force. They will also need to be reinstalled after each
subsequent update to the upstream perl package.
perl-File-Temp
perl-Sys-Syslog
perl-Encode
perl-CGI

Two of the dependency packages will not install due to dependency
resolution issues. They must be downloaded and installed manually, but
updates can occur normally:
perl-FCGI
perl-Any-Moose

e.g.
# yumdownloader perl-File-Temp perl-Sys-Syslog \
perl-Encode perl-CGI perl-FCGI perl-Any-Moose
# rpm -Uvh --force perl-File-Temp-*.rpm perl-Sys-Syslog-*.rpm \
perl-Encode-*.rpm perl-CGI-*.rpm perl-FCGI-*.rpm \
perl-Any-Moose-*.rpm

All of the above can be found in RPMforge.

Regards,
-Bill

[William J. Horka]

Post by Steve Huff
at my day job we install RT entirely via RPMs, clobbering upstream packages where necessary.

It's true. If you want to look at our spec file, it's in
http://mirror.hmdc.harvard.edu/HMDC-RT/el5/SRPMS/rt-3.8.8-1.HMDC.RHEL5.src.rpm
.

Please do note that this build has been customized for our environment,
so I wouldn't recommend using it as-is, but it can provide you with a
starting point for packaging RT.

Basically, to gather the list of requirements, all I did was unpack the
RT source, do a ./configure, and then run "make testdeps" through sed:

make testdeps |grep -v "Can't locate" \
|sed -r -e '/^SOME DEPENDENCIES WERE MISSING/,$d' \
-e 's/ \.\.\.found$//' -e 's/ \.\.\.MISSING$//' \
-e '/^[A-Za-z]/s/^/### /' \
-e 's/^[[:space:]]([^[:space:]]+)/perl(\1)/' >alldeps.txt

After building that into an RPM and enabling the RPMforge repo, yum was
able to resolve all but 6 dependencies for RT 3.8.8.

Four of the dependency packages will not install cleanly on RHEL/CentOS5
via yum due to the fact that they conflict with files owned by the
upstream perl package. They must be downloaded manually and installed
with --force. They will also need to be reinstalled after each
subsequent update to the upstream perl package.
perl-File-Temp
perl-Sys-Syslog
perl-Encode
perl-CGI

Two of the dependency packages will not install due to dependency
resolution issues. They must be downloaded and installed manually, but
updates can occur normally:
perl-FCGI
perl-Any-Moose

e.g.
# yumdownloader perl-File-Temp perl-Sys-Syslog \
perl-Encode perl-CGI perl-FCGI perl-Any-Moose
# rpm -Uvh --force perl-File-Temp-*.rpm perl-Sys-Syslog-*.rpm \
perl-Encode-*.rpm perl-CGI-*.rpm perl-FCGI-*.rpm \
perl-Any-Moose-*.rpm

All of the above can be found in RPMforge.

Regards,
-Bill

[Steve Huff]

What do real people do to install RT on CentOS? It seems they all ignore the first advice and just mix CPAN and packages (see [1] and [2]).

at my day job we install RT entirely via RPMs, clobbering upstream packages where necessary.

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
PGP 8477B706 (A92A 1F7E 6D76 16A0 BFF9 E61D AD54 0251 8477 B706)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.repoforge.org/pipermail/users/attachments/20101213/eccc5c23/attachment-0001.bin

[Steve Huff]

What do real people do to install RT on CentOS? It seems they all ignore the first advice and just mix CPAN and packages (see [1] and [2]).

at my day job we install RT entirely via RPMs, clobbering upstream packages where necessary.

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
PGP 8477B706 (A92A 1F7E 6D76 16A0 BFF9 E61D AD54 0251 8477 B706)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.repoforge.org/pipermail/users/attachments/20101213/eccc5c23/attachment-0002.bin

[Steve Huff]

What do real people do to install RT on CentOS? It seems they all ignore the first advice and just mix CPAN and packages (see [1] and [2]).

at my day job we install RT entirely via RPMs, clobbering upstream packages where necessary.

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
PGP 8477B706 (A92A 1F7E 6D76 16A0 BFF9 E61D AD54 0251 8477 B706)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.repoforge.org/pipermail/users/attachments/20101213/eccc5c23/attachment-0003.bin

[Steve Huff]

What do real people do to install RT on CentOS? It seems they all ignore the first advice and just mix CPAN and packages (see [1] and [2]).

at my day job we install RT entirely via RPMs, clobbering upstream packages where necessary.

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
PGP 8477B706 (A92A 1F7E 6D76 16A0 BFF9 E61D AD54 0251 8477 B706)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
URL: <http://lists.repoforge.org/pipermail/users/attachments/20101213/eccc5c23/attachment.sig>

[Khusro Jaleel]

Post by Steve Huff
RT is indeed difficult to install under RHEL, especially recent versions; honestly, if you can, you may want to wait until CentOS 6 is out.

Unfortunately I can't wait too long, but what is special about CentOS 6
in regards to my specific problem?

Post by Steve Huff
installing from CPAN is a bad idea; don't do that.

In terms of Redhat specific advice, I have been told to:

1. Never mix packages and CPAN, use only one or the other
2. RT people say: Why would you trust some third-party packages? Compile
it yourself!
3. Redhat people say: never use CPAN, only use packages, however it
appears they are slightly broken in this case.

What do real people do to install RT on CentOS? It seems they all ignore
the first advice and just mix CPAN and packages (see [1] and [2]). I
guess there is no other way to really do it. Oh, and they ALL turn OFF
SELinux straight away which is another thing you are NOT supposed to do.

[1] - http://requesttracker.wikia.com/wiki/CentOS5InstallPlusSome
[2] - http://www.ptitov.net/2008/07/request-tracker-installation-o.html

[Khusro Jaleel]

Post by Steve Huff
RT is indeed difficult to install under RHEL, especially recent versions; honestly, if you can, you may want to wait until CentOS 6 is out.

Unfortunately I can't wait too long, but what is special about CentOS 6
in regards to my specific problem?

Post by Steve Huff
installing from CPAN is a bad idea; don't do that.

In terms of Redhat specific advice, I have been told to:

1. Never mix packages and CPAN, use only one or the other
2. RT people say: Why would you trust some third-party packages? Compile
it yourself!
3. Redhat people say: never use CPAN, only use packages, however it
appears they are slightly broken in this case.

What do real people do to install RT on CentOS? It seems they all ignore
the first advice and just mix CPAN and packages (see [1] and [2]). I
guess there is no other way to really do it. Oh, and they ALL turn OFF
SELinux straight away which is another thing you are NOT supposed to do.

[1] - http://requesttracker.wikia.com/wiki/CentOS5InstallPlusSome
[2] - http://www.ptitov.net/2008/07/request-tracker-installation-o.html

[Khusro Jaleel]

Post by Steve Huff
RT is indeed difficult to install under RHEL, especially recent versions; honestly, if you can, you may want to wait until CentOS 6 is out.

Unfortunately I can't wait too long, but what is special about CentOS 6
in regards to my specific problem?

Post by Steve Huff
installing from CPAN is a bad idea; don't do that.

In terms of Redhat specific advice, I have been told to:

1. Never mix packages and CPAN, use only one or the other
2. RT people say: Why would you trust some third-party packages? Compile
it yourself!
3. Redhat people say: never use CPAN, only use packages, however it
appears they are slightly broken in this case.

What do real people do to install RT on CentOS? It seems they all ignore
the first advice and just mix CPAN and packages (see [1] and [2]). I
guess there is no other way to really do it. Oh, and they ALL turn OFF
SELinux straight away which is another thing you are NOT supposed to do.

[1] - http://requesttracker.wikia.com/wiki/CentOS5InstallPlusSome
[2] - http://www.ptitov.net/2008/07/request-tracker-installation-o.html

[Khusro Jaleel]

Post by Steve Huff
RT is indeed difficult to install under RHEL, especially recent versions; honestly, if you can, you may want to wait until CentOS 6 is out.

Unfortunately I can't wait too long, but what is special about CentOS 6
in regards to my specific problem?

Post by Steve Huff
installing from CPAN is a bad idea; don't do that.

In terms of Redhat specific advice, I have been told to:

1. Never mix packages and CPAN, use only one or the other
2. RT people say: Why would you trust some third-party packages? Compile
it yourself!
3. Redhat people say: never use CPAN, only use packages, however it
appears they are slightly broken in this case.

What do real people do to install RT on CentOS? It seems they all ignore
the first advice and just mix CPAN and packages (see [1] and [2]). I
guess there is no other way to really do it. Oh, and they ALL turn OFF
SELinux straight away which is another thing you are NOT supposed to do.

[1] - http://requesttracker.wikia.com/wiki/CentOS5InstallPlusSome
[2] - http://www.ptitov.net/2008/07/request-tracker-installation-o.html

[Dave Miller]

Post by Steve Huff

So does this mean that in this case, I can only really install the latest version of RT by satisfying all the dependencies using CPAN? There is no other way to do it is there? I don't have the option of using RT 3.6 that EPEL packages because I'm trying to migrate an existing 3.8 system to a CentOS box.

no; it means that if you need newer versions of core Perl modules (which it sounds like you do), then you need to break your perl-5.8.8 package a bit. the good news is that RPMforge Perl modules install into the vendor_perl branch, so they shouldn't be clobbering the actual .pm files, but you will have to install with rpm --excludedocs to get past the man page conflicts (or with --force if you want the update man pages).

Wouldn't it make sense to build the RPM with the bin files and man pages
set to install into /usr/local or somesuch? That way it wouldn't
conflict with the core packages and would still put the new files first
in the PATH and MANPATH.

[Dave Miller]

Post by Steve Huff

So does this mean that in this case, I can only really install the latest version of RT by satisfying all the dependencies using CPAN? There is no other way to do it is there? I don't have the option of using RT 3.6 that EPEL packages because I'm trying to migrate an existing 3.8 system to a CentOS box.

no; it means that if you need newer versions of core Perl modules (which it sounds like you do), then you need to break your perl-5.8.8 package a bit. the good news is that RPMforge Perl modules install into the vendor_perl branch, so they shouldn't be clobbering the actual .pm files, but you will have to install with rpm --excludedocs to get past the man page conflicts (or with --force if you want the update man pages).

Wouldn't it make sense to build the RPM with the bin files and man pages
set to install into /usr/local or somesuch? That way it wouldn't
conflict with the core packages and would still put the new files first
in the PATH and MANPATH.

[Dave Miller]

Post by Steve Huff

So does this mean that in this case, I can only really install the latest version of RT by satisfying all the dependencies using CPAN? There is no other way to do it is there? I don't have the option of using RT 3.6 that EPEL packages because I'm trying to migrate an existing 3.8 system to a CentOS box.

no; it means that if you need newer versions of core Perl modules (which it sounds like you do), then you need to break your perl-5.8.8 package a bit. the good news is that RPMforge Perl modules install into the vendor_perl branch, so they shouldn't be clobbering the actual .pm files, but you will have to install with rpm --excludedocs to get past the man page conflicts (or with --force if you want the update man pages).

Wouldn't it make sense to build the RPM with the bin files and man pages
set to install into /usr/local or somesuch? That way it wouldn't
conflict with the core packages and would still put the new files first
in the PATH and MANPATH.

[Dave Miller]

Post by Steve Huff

So does this mean that in this case, I can only really install the latest version of RT by satisfying all the dependencies using CPAN? There is no other way to do it is there? I don't have the option of using RT 3.6 that EPEL packages because I'm trying to migrate an existing 3.8 system to a CentOS box.

no; it means that if you need newer versions of core Perl modules (which it sounds like you do), then you need to break your perl-5.8.8 package a bit. the good news is that RPMforge Perl modules install into the vendor_perl branch, so they shouldn't be clobbering the actual .pm files, but you will have to install with rpm --excludedocs to get past the man page conflicts (or with --force if you want the update man pages).

Wouldn't it make sense to build the RPM with the bin files and man pages
set to install into /usr/local or somesuch? That way it wouldn't
conflict with the core packages and would still put the new files first
in the PATH and MANPATH.

[Dave Miller]

Post by Steve Huff

So does this mean that in this case, I can only really install the latest version of RT by satisfying all the dependencies using CPAN? There is no other way to do it is there? I don't have the option of using RT 3.6 that EPEL packages because I'm trying to migrate an existing 3.8 system to a CentOS box.

no; it means that if you need newer versions of core Perl modules (which it sounds like you do), then you need to break your perl-5.8.8 package a bit. the good news is that RPMforge Perl modules install into the vendor_perl branch, so they shouldn't be clobbering the actual .pm files, but you will have to install with rpm --excludedocs to get past the man page conflicts (or with --force if you want the update man pages).

Wouldn't it make sense to build the RPM with the bin files and man pages
set to install into /usr/local or somesuch? That way it wouldn't
conflict with the core packages and would still put the new files first
in the PATH and MANPATH.

[Scott Robbins]

Post by Khusro Jaleel
I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(
So does this mean that in this case, I can only really install the
latest version of RT by satisfying all the dependencies using CPAN?
There is no other way to do it is there? I don't have the option of
using RT 3.6 that EPEL packages because I'm trying to migrate an
existing 3.8 system to a CentOS box.

RT is a pain to install on CentOS. I never found a way that avoided
CPAN entirely, but was able to get a great deal of it from rpmforge.

You can see my page at
http://home.roadrunner.com/~computertaijutsu/rt3.html

I don't know if any of it will help you.

I was using an older version, but that's exactly what I had to do,
migrate it.

Hopefully, you're familiar with migrating it. The gotcha I ran into was
that I had to change the newer machine's default sendmail

DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl


to

dnl DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl

Another gotcha was that I had to cpoy /opt/rt3/bin/rt3-mailgate to
/etc/smrsh amdn make sure the permissions were 755 owner root, group rt.

But to answer your original question, I wasn't able to avoid CPAN.

[Edward Prendergast]

Post by Scott Robbins

Post by Khusro Jaleel
I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(

But to answer your original question, I wasn't able to avoid CPAN.

I've found using perl's local::lib can significantly reduce the pain of
using CPAN when you absolutely have to. If you set it up properly you
can use CPAN without messing with the perl of the system, the RPM DB or
any other stuff.

************
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorised. If you are not the intended recipient, any action taken or
omitted to be taken in reliance on it, any form of reproduction,
dissemination, copying, disclosure, modification, distribution and/or
publication of this E-mail message is strictly prohibited and may be
unlawful. If you have received this E-mail message in error, please notify
us immediately. Please also destroy and delete the message from your
computer.
************

[Khusro Jaleel]

Post by Edward Prendergast

Post by Scott Robbins

Post by Khusro Jaleel
I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(

But to answer your original question, I wasn't able to avoid CPAN.

I've found using perl's local::lib can significantly reduce the pain
of using CPAN when you absolutely have to. If you set it up properly
you can use CPAN without messing with the perl of the system, the RPM
DB or any other stuff.

Can you please elaborate a little bit on this technique and how you used
it? Did you specify something in /opt for installing all the CPAN stuff?

[Khusro Jaleel]

Post by Edward Prendergast

Post by Scott Robbins

Post by Khusro Jaleel
I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(

But to answer your original question, I wasn't able to avoid CPAN.

I've found using perl's local::lib can significantly reduce the pain
of using CPAN when you absolutely have to. If you set it up properly
you can use CPAN without messing with the perl of the system, the RPM
DB or any other stuff.

Can you please elaborate a little bit on this technique and how you used
it? Did you specify something in /opt for installing all the CPAN stuff?

[Khusro Jaleel]

Post by Edward Prendergast

Post by Scott Robbins

Post by Khusro Jaleel
I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(

But to answer your original question, I wasn't able to avoid CPAN.

I've found using perl's local::lib can significantly reduce the pain
of using CPAN when you absolutely have to. If you set it up properly
you can use CPAN without messing with the perl of the system, the RPM
DB or any other stuff.

Can you please elaborate a little bit on this technique and how you used
it? Did you specify something in /opt for installing all the CPAN stuff?

[Khusro Jaleel]

Post by Edward Prendergast

Post by Scott Robbins

Post by Khusro Jaleel
I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(

But to answer your original question, I wasn't able to avoid CPAN.

I've found using perl's local::lib can significantly reduce the pain
of using CPAN when you absolutely have to. If you set it up properly
you can use CPAN without messing with the perl of the system, the RPM
DB or any other stuff.

Can you please elaborate a little bit on this technique and how you used
it? Did you specify something in /opt for installing all the CPAN stuff?

[Khusro Jaleel]

Post by Edward Prendergast

Post by Scott Robbins

Post by Khusro Jaleel
I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(

But to answer your original question, I wasn't able to avoid CPAN.

I've found using perl's local::lib can significantly reduce the pain
of using CPAN when you absolutely have to. If you set it up properly
you can use CPAN without messing with the perl of the system, the RPM
DB or any other stuff.

Can you please elaborate a little bit on this technique and how you used
it? Did you specify something in /opt for installing all the CPAN stuff?

[Khusro Jaleel]

Post by Scott Robbins

Post by Khusro Jaleel
I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(
So does this mean that in this case, I can only really install the
latest version of RT by satisfying all the dependencies using CPAN?
There is no other way to do it is there? I don't have the option of
using RT 3.6 that EPEL packages because I'm trying to migrate an
existing 3.8 system to a CentOS box.

RT is a pain to install on CentOS. I never found a way that avoided
CPAN entirely, but was able to get a great deal of it from rpmforge.
You can see my page at
http://home.roadrunner.com/~computertaijutsu/rt3.html
I don't know if any of it will help you.
I was using an older version, but that's exactly what I had to do,
migrate it.
Hopefully, you're familiar with migrating it. The gotcha I ran into was
that I had to change the newer machine's default sendmail
DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl
to
dnl DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl
Another gotcha was that I had to cpoy /opt/rt3/bin/rt3-mailgate to
/etc/smrsh amdn make sure the permissions were 755 owner root, group rt.
But to answer your original question, I wasn't able to avoid CPAN.

Thank you very much, Scott. This is a nice addition to the ones I have
found so far. I will go through it as well. If I have any questions I'll
ask.

[Edward Prendergast]

Post by Scott Robbins

Post by Khusro Jaleel
I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(

But to answer your original question, I wasn't able to avoid CPAN.

I've found using perl's local::lib can significantly reduce the pain of
using CPAN when you absolutely have to. If you set it up properly you
can use CPAN without messing with the perl of the system, the RPM DB or
any other stuff.

************
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorised. If you are not the intended recipient, any action taken or
omitted to be taken in reliance on it, any form of reproduction,
dissemination, copying, disclosure, modification, distribution and/or
publication of this E-mail message is strictly prohibited and may be
unlawful. If you have received this E-mail message in error, please notify
us immediately. Please also destroy and delete the message from your
computer.
************

[Khusro Jaleel]

Post by Scott Robbins

Post by Khusro Jaleel
I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(
So does this mean that in this case, I can only really install the
latest version of RT by satisfying all the dependencies using CPAN?
There is no other way to do it is there? I don't have the option of
using RT 3.6 that EPEL packages because I'm trying to migrate an
existing 3.8 system to a CentOS box.

RT is a pain to install on CentOS. I never found a way that avoided
CPAN entirely, but was able to get a great deal of it from rpmforge.
You can see my page at
http://home.roadrunner.com/~computertaijutsu/rt3.html
I don't know if any of it will help you.
I was using an older version, but that's exactly what I had to do,
migrate it.
Hopefully, you're familiar with migrating it. The gotcha I ran into was
that I had to change the newer machine's default sendmail
DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl
to
dnl DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl
Another gotcha was that I had to cpoy /opt/rt3/bin/rt3-mailgate to
/etc/smrsh amdn make sure the permissions were 755 owner root, group rt.
But to answer your original question, I wasn't able to avoid CPAN.

Thank you very much, Scott. This is a nice addition to the ones I have
found so far. I will go through it as well. If I have any questions I'll
ask.

[Edward Prendergast]

Post by Scott Robbins

Post by Khusro Jaleel
I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(

But to answer your original question, I wasn't able to avoid CPAN.

I've found using perl's local::lib can significantly reduce the pain of
using CPAN when you absolutely have to. If you set it up properly you
can use CPAN without messing with the perl of the system, the RPM DB or
any other stuff.

************
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorised. If you are not the intended recipient, any action taken or
omitted to be taken in reliance on it, any form of reproduction,
dissemination, copying, disclosure, modification, distribution and/or
publication of this E-mail message is strictly prohibited and may be
unlawful. If you have received this E-mail message in error, please notify
us immediately. Please also destroy and delete the message from your
computer.
************

[Khusro Jaleel]

Post by Scott Robbins

Post by Khusro Jaleel
I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(
So does this mean that in this case, I can only really install the
latest version of RT by satisfying all the dependencies using CPAN?
There is no other way to do it is there? I don't have the option of
using RT 3.6 that EPEL packages because I'm trying to migrate an
existing 3.8 system to a CentOS box.

RT is a pain to install on CentOS. I never found a way that avoided
CPAN entirely, but was able to get a great deal of it from rpmforge.
You can see my page at
http://home.roadrunner.com/~computertaijutsu/rt3.html
I don't know if any of it will help you.
I was using an older version, but that's exactly what I had to do,
migrate it.
Hopefully, you're familiar with migrating it. The gotcha I ran into was
that I had to change the newer machine's default sendmail
DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl
to
dnl DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl
Another gotcha was that I had to cpoy /opt/rt3/bin/rt3-mailgate to
/etc/smrsh amdn make sure the permissions were 755 owner root, group rt.
But to answer your original question, I wasn't able to avoid CPAN.

Thank you very much, Scott. This is a nice addition to the ones I have
found so far. I will go through it as well. If I have any questions I'll
ask.

[Edward Prendergast]

Post by Scott Robbins

Post by Khusro Jaleel
I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(

But to answer your original question, I wasn't able to avoid CPAN.

I've found using perl's local::lib can significantly reduce the pain of
using CPAN when you absolutely have to. If you set it up properly you
can use CPAN without messing with the perl of the system, the RPM DB or
any other stuff.

************
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorised. If you are not the intended recipient, any action taken or
omitted to be taken in reliance on it, any form of reproduction,
dissemination, copying, disclosure, modification, distribution and/or
publication of this E-mail message is strictly prohibited and may be
unlawful. If you have received this E-mail message in error, please notify
us immediately. Please also destroy and delete the message from your
computer.
************

[Khusro Jaleel]

Post by Scott Robbins

Post by Khusro Jaleel
I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(
So does this mean that in this case, I can only really install the
latest version of RT by satisfying all the dependencies using CPAN?
There is no other way to do it is there? I don't have the option of
using RT 3.6 that EPEL packages because I'm trying to migrate an
existing 3.8 system to a CentOS box.

RT is a pain to install on CentOS. I never found a way that avoided
CPAN entirely, but was able to get a great deal of it from rpmforge.
You can see my page at
http://home.roadrunner.com/~computertaijutsu/rt3.html
I don't know if any of it will help you.
I was using an older version, but that's exactly what I had to do,
migrate it.
Hopefully, you're familiar with migrating it. The gotcha I ran into was
that I had to change the newer machine's default sendmail
DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl
to
dnl DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl
Another gotcha was that I had to cpoy /opt/rt3/bin/rt3-mailgate to
/etc/smrsh amdn make sure the permissions were 755 owner root, group rt.
But to answer your original question, I wasn't able to avoid CPAN.

Thank you very much, Scott. This is a nice addition to the ones I have
found so far. I will go through it as well. If I have any questions I'll
ask.

[Edward Prendergast]

Post by Scott Robbins

Post by Khusro Jaleel
I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(

But to answer your original question, I wasn't able to avoid CPAN.

I've found using perl's local::lib can significantly reduce the pain of
using CPAN when you absolutely have to. If you set it up properly you
can use CPAN without messing with the perl of the system, the RPM DB or
any other stuff.

************
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorised. If you are not the intended recipient, any action taken or
omitted to be taken in reliance on it, any form of reproduction,
dissemination, copying, disclosure, modification, distribution and/or
publication of this E-mail message is strictly prohibited and may be
unlawful. If you have received this E-mail message in error, please notify
us immediately. Please also destroy and delete the message from your
computer.
************

[Khusro Jaleel]

Post by Scott Robbins

Post by Khusro Jaleel
I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(
So does this mean that in this case, I can only really install the
latest version of RT by satisfying all the dependencies using CPAN?
There is no other way to do it is there? I don't have the option of
using RT 3.6 that EPEL packages because I'm trying to migrate an
existing 3.8 system to a CentOS box.

RT is a pain to install on CentOS. I never found a way that avoided
CPAN entirely, but was able to get a great deal of it from rpmforge.
You can see my page at
http://home.roadrunner.com/~computertaijutsu/rt3.html
I don't know if any of it will help you.
I was using an older version, but that's exactly what I had to do,
migrate it.
Hopefully, you're familiar with migrating it. The gotcha I ran into was
that I had to change the newer machine's default sendmail
DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl
to
dnl DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl
Another gotcha was that I had to cpoy /opt/rt3/bin/rt3-mailgate to
/etc/smrsh amdn make sure the permissions were 755 owner root, group rt.
But to answer your original question, I wasn't able to avoid CPAN.

Thank you very much, Scott. This is a nice addition to the ones I have
found so far. I will go through it as well. If I have any questions I'll
ask.

[Steve Huff]

So does this mean that in this case, I can only really install the latest version of RT by satisfying all the dependencies using CPAN? There is no other way to do it is there? I don't have the option of using RT 3.6 that EPEL packages because I'm trying to migrate an existing 3.8 system to a CentOS box.

no; it means that if you need newer versions of core Perl modules (which it sounds like you do), then you need to break your perl-5.8.8 package a bit. the good news is that RPMforge Perl modules install into the vendor_perl branch, so they shouldn't be clobbering the actual .pm files, but you will have to install with rpm --excludedocs to get past the man page conflicts (or with --force if you want the update man pages).

RT is indeed difficult to install under RHEL, especially recent versions; honestly, if you can, you may want to wait until CentOS 6 is out.

installing from CPAN is a bad idea; don't do that.

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
PGP 8477B706 (A92A 1F7E 6D76 16A0 BFF9 E61D AD54 0251 8477 B706)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.repoforge.org/pipermail/users/attachments/20101213/d11b2485/attachment-0001.bin

[Scott Robbins]

Post by Khusro Jaleel
I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(
So does this mean that in this case, I can only really install the
latest version of RT by satisfying all the dependencies using CPAN?
There is no other way to do it is there? I don't have the option of
using RT 3.6 that EPEL packages because I'm trying to migrate an
existing 3.8 system to a CentOS box.

RT is a pain to install on CentOS. I never found a way that avoided
CPAN entirely, but was able to get a great deal of it from rpmforge.

You can see my page at
http://home.roadrunner.com/~computertaijutsu/rt3.html

I don't know if any of it will help you.

I was using an older version, but that's exactly what I had to do,
migrate it.

Hopefully, you're familiar with migrating it. The gotcha I ran into was
that I had to change the newer machine's default sendmail

DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl


to

dnl DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl

Another gotcha was that I had to cpoy /opt/rt3/bin/rt3-mailgate to
/etc/smrsh amdn make sure the permissions were 755 owner root, group rt.

But to answer your original question, I wasn't able to avoid CPAN.

[Steve Huff]

So does this mean that in this case, I can only really install the latest version of RT by satisfying all the dependencies using CPAN? There is no other way to do it is there? I don't have the option of using RT 3.6 that EPEL packages because I'm trying to migrate an existing 3.8 system to a CentOS box.

no; it means that if you need newer versions of core Perl modules (which it sounds like you do), then you need to break your perl-5.8.8 package a bit. the good news is that RPMforge Perl modules install into the vendor_perl branch, so they shouldn't be clobbering the actual .pm files, but you will have to install with rpm --excludedocs to get past the man page conflicts (or with --force if you want the update man pages).

RT is indeed difficult to install under RHEL, especially recent versions; honestly, if you can, you may want to wait until CentOS 6 is out.

installing from CPAN is a bad idea; don't do that.

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
PGP 8477B706 (A92A 1F7E 6D76 16A0 BFF9 E61D AD54 0251 8477 B706)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.repoforge.org/pipermail/users/attachments/20101213/d11b2485/attachment-0002.bin

[Scott Robbins]

Post by Khusro Jaleel
I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(
So does this mean that in this case, I can only really install the
latest version of RT by satisfying all the dependencies using CPAN?
There is no other way to do it is there? I don't have the option of
using RT 3.6 that EPEL packages because I'm trying to migrate an
existing 3.8 system to a CentOS box.

RT is a pain to install on CentOS. I never found a way that avoided
CPAN entirely, but was able to get a great deal of it from rpmforge.

You can see my page at
http://home.roadrunner.com/~computertaijutsu/rt3.html

I don't know if any of it will help you.

I was using an older version, but that's exactly what I had to do,
migrate it.

Hopefully, you're familiar with migrating it. The gotcha I ran into was
that I had to change the newer machine's default sendmail

DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl


to

dnl DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl

Another gotcha was that I had to cpoy /opt/rt3/bin/rt3-mailgate to
/etc/smrsh amdn make sure the permissions were 755 owner root, group rt.

But to answer your original question, I wasn't able to avoid CPAN.

[Steve Huff]

So does this mean that in this case, I can only really install the latest version of RT by satisfying all the dependencies using CPAN? There is no other way to do it is there? I don't have the option of using RT 3.6 that EPEL packages because I'm trying to migrate an existing 3.8 system to a CentOS box.

no; it means that if you need newer versions of core Perl modules (which it sounds like you do), then you need to break your perl-5.8.8 package a bit. the good news is that RPMforge Perl modules install into the vendor_perl branch, so they shouldn't be clobbering the actual .pm files, but you will have to install with rpm --excludedocs to get past the man page conflicts (or with --force if you want the update man pages).

RT is indeed difficult to install under RHEL, especially recent versions; honestly, if you can, you may want to wait until CentOS 6 is out.

installing from CPAN is a bad idea; don't do that.

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
PGP 8477B706 (A92A 1F7E 6D76 16A0 BFF9 E61D AD54 0251 8477 B706)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.repoforge.org/pipermail/users/attachments/20101213/d11b2485/attachment-0003.bin

[Scott Robbins]

Post by Khusro Jaleel
I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(
So does this mean that in this case, I can only really install the
latest version of RT by satisfying all the dependencies using CPAN?
There is no other way to do it is there? I don't have the option of
using RT 3.6 that EPEL packages because I'm trying to migrate an
existing 3.8 system to a CentOS box.

RT is a pain to install on CentOS. I never found a way that avoided
CPAN entirely, but was able to get a great deal of it from rpmforge.

You can see my page at
http://home.roadrunner.com/~computertaijutsu/rt3.html

I don't know if any of it will help you.

I was using an older version, but that's exactly what I had to do,
migrate it.

Hopefully, you're familiar with migrating it. The gotcha I ran into was
that I had to change the newer machine's default sendmail

DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl


to

dnl DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl

Another gotcha was that I had to cpoy /opt/rt3/bin/rt3-mailgate to
/etc/smrsh amdn make sure the permissions were 755 owner root, group rt.

But to answer your original question, I wasn't able to avoid CPAN.

[Steve Huff]

So does this mean that in this case, I can only really install the latest version of RT by satisfying all the dependencies using CPAN? There is no other way to do it is there? I don't have the option of using RT 3.6 that EPEL packages because I'm trying to migrate an existing 3.8 system to a CentOS box.

no; it means that if you need newer versions of core Perl modules (which it sounds like you do), then you need to break your perl-5.8.8 package a bit. the good news is that RPMforge Perl modules install into the vendor_perl branch, so they shouldn't be clobbering the actual .pm files, but you will have to install with rpm --excludedocs to get past the man page conflicts (or with --force if you want the update man pages).

RT is indeed difficult to install under RHEL, especially recent versions; honestly, if you can, you may want to wait until CentOS 6 is out.

installing from CPAN is a bad idea; don't do that.

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
PGP 8477B706 (A92A 1F7E 6D76 16A0 BFF9 E61D AD54 0251 8477 B706)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
URL: <http://lists.repoforge.org/pipermail/users/attachments/20101213/d11b2485/attachment.sig>

[Scott Robbins]

Post by Khusro Jaleel
I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(
So does this mean that in this case, I can only really install the
latest version of RT by satisfying all the dependencies using CPAN?
There is no other way to do it is there? I don't have the option of
using RT 3.6 that EPEL packages because I'm trying to migrate an
existing 3.8 system to a CentOS box.

RT is a pain to install on CentOS. I never found a way that avoided
CPAN entirely, but was able to get a great deal of it from rpmforge.

You can see my page at
http://home.roadrunner.com/~computertaijutsu/rt3.html

I don't know if any of it will help you.

I was using an older version, but that's exactly what I had to do,
migrate it.

Hopefully, you're familiar with migrating it. The gotcha I ran into was
that I had to change the newer machine's default sendmail

DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl


to

dnl DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl

Another gotcha was that I had to cpoy /opt/rt3/bin/rt3-mailgate to
/etc/smrsh amdn make sure the permissions were 755 owner root, group rt.

But to answer your original question, I wasn't able to avoid CPAN.

[Khusro Jaleel]

Post by Steve Huff
for our part, it means that perl-Encode needs an rfx tag, since if Khusro forces an install of perl-Encode-2.39, then he's breaking his existing perl package, and he should be aware of it.
Khusro, why are you trying to install a newer Encode than provided? do you specifically need a version later than 2.12? why?

I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(

So does this mean that in this case, I can only really install the
latest version of RT by satisfying all the dependencies using CPAN?
There is no other way to do it is there? I don't have the option of
using RT 3.6 that EPEL packages because I'm trying to migrate an
existing 3.8 system to a CentOS box.

Thanks,
Khusro

[Khusro Jaleel]

Post by Steve Huff
for our part, it means that perl-Encode needs an rfx tag, since if Khusro forces an install of perl-Encode-2.39, then he's breaking his existing perl package, and he should be aware of it.
Khusro, why are you trying to install a newer Encode than provided? do you specifically need a version later than 2.12? why?

I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(

So does this mean that in this case, I can only really install the
latest version of RT by satisfying all the dependencies using CPAN?
There is no other way to do it is there? I don't have the option of
using RT 3.6 that EPEL packages because I'm trying to migrate an
existing 3.8 system to a CentOS box.

Thanks,
Khusro

[Khusro Jaleel]

Post by Steve Huff
for our part, it means that perl-Encode needs an rfx tag, since if Khusro forces an install of perl-Encode-2.39, then he's breaking his existing perl package, and he should be aware of it.
Khusro, why are you trying to install a newer Encode than provided? do you specifically need a version later than 2.12? why?

I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(

So does this mean that in this case, I can only really install the
latest version of RT by satisfying all the dependencies using CPAN?
There is no other way to do it is there? I don't have the option of
using RT 3.6 that EPEL packages because I'm trying to migrate an
existing 3.8 system to a CentOS box.

Thanks,
Khusro

[Khusro Jaleel]

Post by Steve Huff
for our part, it means that perl-Encode needs an rfx tag, since if Khusro forces an install of perl-Encode-2.39, then he's breaking his existing perl package, and he should be aware of it.
Khusro, why are you trying to install a newer Encode than provided? do you specifically need a version later than 2.12? why?

I'm trying to install RT and apparently it needs a newer version of
Encode, as well as a huge bunch of other Perl things :-(

So does this mean that in this case, I can only really install the
latest version of RT by satisfying all the dependencies using CPAN?
There is no other way to do it is there? I don't have the option of
using RT 3.6 that EPEL packages because I'm trying to migrate an
existing 3.8 system to a CentOS box.

Thanks,
Khusro

[Steve Huff]

Post by Yury V. Zaytsev

Post by Khusro Jaleel
file /usr/bin/enc2xs from install of perl-Encode-2.39-1.el5.rf.x86_64
conflicts with file from package perl-5.8.8-32.el5_5.2.x86_64
file /usr/bin/piconv from install of perl-Encode-2.39-1.el5.rf.x86_64

Sounds like more than a man conflict that we can ignore :-(
File a bug at RH to repackage it as a separate entity?

no, that's not the case; it looks like Encode 2.12 is part of Perl 5.8.8 core, and unfortunately, RH is technically doing the right thing by packaging Encode as part of the perl-5.8.8 RPM.

for our part, it means that perl-Encode needs an rfx tag, since if Khusro forces an install of perl-Encode-2.39, then he's breaking his existing perl package, and he should be aware of it.

Khusro, why are you trying to install a newer Encode than provided? do you specifically need a version later than 2.12? why?

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
PGP 8477B706 (A92A 1F7E 6D76 16A0 BFF9 E61D AD54 0251 8477 B706)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.repoforge.org/pipermail/users/attachments/20101213/334392ff/attachment-0001.bin

[Steve Huff]

Post by Yury V. Zaytsev

Post by Khusro Jaleel
file /usr/bin/enc2xs from install of perl-Encode-2.39-1.el5.rf.x86_64
conflicts with file from package perl-5.8.8-32.el5_5.2.x86_64
file /usr/bin/piconv from install of perl-Encode-2.39-1.el5.rf.x86_64

Sounds like more than a man conflict that we can ignore :-(
File a bug at RH to repackage it as a separate entity?

no, that's not the case; it looks like Encode 2.12 is part of Perl 5.8.8 core, and unfortunately, RH is technically doing the right thing by packaging Encode as part of the perl-5.8.8 RPM.

for our part, it means that perl-Encode needs an rfx tag, since if Khusro forces an install of perl-Encode-2.39, then he's breaking his existing perl package, and he should be aware of it.

Khusro, why are you trying to install a newer Encode than provided? do you specifically need a version later than 2.12? why?

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
PGP 8477B706 (A92A 1F7E 6D76 16A0 BFF9 E61D AD54 0251 8477 B706)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.repoforge.org/pipermail/users/attachments/20101213/334392ff/attachment-0002.bin

[Steve Huff]

Post by Yury V. Zaytsev

Post by Khusro Jaleel
file /usr/bin/enc2xs from install of perl-Encode-2.39-1.el5.rf.x86_64
conflicts with file from package perl-5.8.8-32.el5_5.2.x86_64
file /usr/bin/piconv from install of perl-Encode-2.39-1.el5.rf.x86_64

Sounds like more than a man conflict that we can ignore :-(
File a bug at RH to repackage it as a separate entity?

no, that's not the case; it looks like Encode 2.12 is part of Perl 5.8.8 core, and unfortunately, RH is technically doing the right thing by packaging Encode as part of the perl-5.8.8 RPM.

for our part, it means that perl-Encode needs an rfx tag, since if Khusro forces an install of perl-Encode-2.39, then he's breaking his existing perl package, and he should be aware of it.

Khusro, why are you trying to install a newer Encode than provided? do you specifically need a version later than 2.12? why?

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
PGP 8477B706 (A92A 1F7E 6D76 16A0 BFF9 E61D AD54 0251 8477 B706)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://lists.repoforge.org/pipermail/users/attachments/20101213/334392ff/attachment-0003.bin

[Steve Huff]

Post by Yury V. Zaytsev

Post by Khusro Jaleel
file /usr/bin/enc2xs from install of perl-Encode-2.39-1.el5.rf.x86_64
conflicts with file from package perl-5.8.8-32.el5_5.2.x86_64
file /usr/bin/piconv from install of perl-Encode-2.39-1.el5.rf.x86_64

Sounds like more than a man conflict that we can ignore :-(
File a bug at RH to repackage it as a separate entity?

no, that's not the case; it looks like Encode 2.12 is part of Perl 5.8.8 core, and unfortunately, RH is technically doing the right thing by packaging Encode as part of the perl-5.8.8 RPM.

for our part, it means that perl-Encode needs an rfx tag, since if Khusro forces an install of perl-Encode-2.39, then he's breaking his existing perl package, and he should be aware of it.

Khusro, why are you trying to install a newer Encode than provided? do you specifically need a version later than 2.12? why?

-steve

--
If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
PGP 8477B706 (A92A 1F7E 6D76 16A0 BFF9 E61D AD54 0251 8477 B706)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
URL: <http://lists.repoforge.org/pipermail/users/attachments/20101213/334392ff/attachment.sig>

[Khusro Jaleel]

Hi,

I am trying to install the package 'perl-Encode' from rpmforge on a
CentOS machine with EPEL also enabled. I am using the priorities plugin
so Base, EPEL and RPMForge all have different priorities, however I get
the following error from yum. Any ideas as to how to fix this appreciated

Thanks,


=====================================================================================

Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
* addons: mirror.sov.uk.goscomb.net
* base: mirror.sov.uk.goscomb.net
* epel: mirror01.th.ifl.net
* extras: mirror.ox.ac.uk
* rpmforge: apt.sw.be
* updates: mirror.ox.ac.uk
3559 packages excluded due to repository priority protections
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package perl-Encode.x86_64 0:2.39-1.el5.rf set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

============================================================================================================================================
Package Arch
Version Repository Size
============================================================================================================================================
Installing:
perl-Encode x86_64
2.39-1.el5.rf rpmforge 3.0 M

Transaction Summary
============================================================================================================================================
Install 1 Package(s)
Upgrade 0 Package(s)

Total size: 3.0 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test


Transaction Check Error:
file /usr/bin/enc2xs from install of perl-Encode-2.39-1.el5.rf.x86_64
conflicts with file from package perl-5.8.8-32.el5_5.2.x86_64
file /usr/bin/piconv from install of perl-Encode-2.39-1.el5.rf.x86_64
conflicts with file from package perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man1/enc2xs.1.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man1/piconv.1.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Alias.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::CJKConstants.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::CN::HZ.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Config.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Encoder.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Encoding.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Guess.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::JP::H2Z.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::JP::JIS7.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::KR::2022_KR.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::MIME::Header.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::PerlIO.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Supported.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Unicode::UTF7.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/encoding.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64

Error Summary
-------------
=====================================================================================

[Yury V. Zaytsev]

Post by Khusro Jaleel
file /usr/bin/enc2xs from install of perl-Encode-2.39-1.el5.rf.x86_64
conflicts with file from package perl-5.8.8-32.el5_5.2.x86_64
file /usr/bin/piconv from install of perl-Encode-2.39-1.el5.rf.x86_64

Sounds like more than a man conflict that we can ignore :-(

File a bug at RH to repackage it as a separate entity?

[Khusro Jaleel]

Hi,

I am trying to install the package 'perl-Encode' from rpmforge on a
CentOS machine with EPEL also enabled. I am using the priorities plugin
so Base, EPEL and RPMForge all have different priorities, however I get
the following error from yum. Any ideas as to how to fix this appreciated

Thanks,


=====================================================================================

Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
* addons: mirror.sov.uk.goscomb.net
* base: mirror.sov.uk.goscomb.net
* epel: mirror01.th.ifl.net
* extras: mirror.ox.ac.uk
* rpmforge: apt.sw.be
* updates: mirror.ox.ac.uk
3559 packages excluded due to repository priority protections
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package perl-Encode.x86_64 0:2.39-1.el5.rf set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

============================================================================================================================================
Package Arch
Version Repository Size
============================================================================================================================================
Installing:
perl-Encode x86_64
2.39-1.el5.rf rpmforge 3.0 M

Transaction Summary
============================================================================================================================================
Install 1 Package(s)
Upgrade 0 Package(s)

Total size: 3.0 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test


Transaction Check Error:
file /usr/bin/enc2xs from install of perl-Encode-2.39-1.el5.rf.x86_64
conflicts with file from package perl-5.8.8-32.el5_5.2.x86_64
file /usr/bin/piconv from install of perl-Encode-2.39-1.el5.rf.x86_64
conflicts with file from package perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man1/enc2xs.1.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man1/piconv.1.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Alias.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::CJKConstants.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::CN::HZ.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Config.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Encoder.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Encoding.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Guess.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::JP::H2Z.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::JP::JIS7.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::KR::2022_KR.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::MIME::Header.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::PerlIO.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Supported.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Unicode::UTF7.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/encoding.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64

Error Summary
-------------
=====================================================================================

[Yury V. Zaytsev]

Post by Khusro Jaleel
file /usr/bin/enc2xs from install of perl-Encode-2.39-1.el5.rf.x86_64
conflicts with file from package perl-5.8.8-32.el5_5.2.x86_64
file /usr/bin/piconv from install of perl-Encode-2.39-1.el5.rf.x86_64

Sounds like more than a man conflict that we can ignore :-(

File a bug at RH to repackage it as a separate entity?

[Khusro Jaleel]

Hi,

I am trying to install the package 'perl-Encode' from rpmforge on a
CentOS machine with EPEL also enabled. I am using the priorities plugin
so Base, EPEL and RPMForge all have different priorities, however I get
the following error from yum. Any ideas as to how to fix this appreciated

Thanks,


=====================================================================================

Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
* addons: mirror.sov.uk.goscomb.net
* base: mirror.sov.uk.goscomb.net
* epel: mirror01.th.ifl.net
* extras: mirror.ox.ac.uk
* rpmforge: apt.sw.be
* updates: mirror.ox.ac.uk
3559 packages excluded due to repository priority protections
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package perl-Encode.x86_64 0:2.39-1.el5.rf set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

============================================================================================================================================
Package Arch
Version Repository Size
============================================================================================================================================
Installing:
perl-Encode x86_64
2.39-1.el5.rf rpmforge 3.0 M

Transaction Summary
============================================================================================================================================
Install 1 Package(s)
Upgrade 0 Package(s)

Total size: 3.0 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test


Transaction Check Error:
file /usr/bin/enc2xs from install of perl-Encode-2.39-1.el5.rf.x86_64
conflicts with file from package perl-5.8.8-32.el5_5.2.x86_64
file /usr/bin/piconv from install of perl-Encode-2.39-1.el5.rf.x86_64
conflicts with file from package perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man1/enc2xs.1.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man1/piconv.1.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Alias.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::CJKConstants.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::CN::HZ.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Config.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Encoder.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Encoding.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Guess.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::JP::H2Z.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::JP::JIS7.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::KR::2022_KR.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::MIME::Header.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::PerlIO.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Supported.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Unicode::UTF7.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/encoding.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64

Error Summary
-------------
=====================================================================================

[Yury V. Zaytsev]

Post by Khusro Jaleel
file /usr/bin/enc2xs from install of perl-Encode-2.39-1.el5.rf.x86_64
conflicts with file from package perl-5.8.8-32.el5_5.2.x86_64
file /usr/bin/piconv from install of perl-Encode-2.39-1.el5.rf.x86_64

Sounds like more than a man conflict that we can ignore :-(

File a bug at RH to repackage it as a separate entity?

[Khusro Jaleel]

Hi,

I am trying to install the package 'perl-Encode' from rpmforge on a
CentOS machine with EPEL also enabled. I am using the priorities plugin
so Base, EPEL and RPMForge all have different priorities, however I get
the following error from yum. Any ideas as to how to fix this appreciated

Thanks,


=====================================================================================

Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
* addons: mirror.sov.uk.goscomb.net
* base: mirror.sov.uk.goscomb.net
* epel: mirror01.th.ifl.net
* extras: mirror.ox.ac.uk
* rpmforge: apt.sw.be
* updates: mirror.ox.ac.uk
3559 packages excluded due to repository priority protections
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package perl-Encode.x86_64 0:2.39-1.el5.rf set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

============================================================================================================================================
Package Arch
Version Repository Size
============================================================================================================================================
Installing:
perl-Encode x86_64
2.39-1.el5.rf rpmforge 3.0 M

Transaction Summary
============================================================================================================================================
Install 1 Package(s)
Upgrade 0 Package(s)

Total size: 3.0 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test


Transaction Check Error:
file /usr/bin/enc2xs from install of perl-Encode-2.39-1.el5.rf.x86_64
conflicts with file from package perl-5.8.8-32.el5_5.2.x86_64
file /usr/bin/piconv from install of perl-Encode-2.39-1.el5.rf.x86_64
conflicts with file from package perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man1/enc2xs.1.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man1/piconv.1.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Alias.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::CJKConstants.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::CN::HZ.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Config.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Encoder.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Encoding.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Guess.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::JP::H2Z.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::JP::JIS7.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::KR::2022_KR.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::MIME::Header.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::PerlIO.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Supported.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/Encode::Unicode::UTF7.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64
file /usr/share/man/man3/encoding.3pm.gz from install of
perl-Encode-2.39-1.el5.rf.x86_64 conflicts with file from package
perl-5.8.8-32.el5_5.2.x86_64

Error Summary
-------------
=====================================================================================

[Yury V. Zaytsev]

Post by Khusro Jaleel
file /usr/bin/enc2xs from install of perl-Encode-2.39-1.el5.rf.x86_64
conflicts with file from package perl-5.8.8-32.el5_5.2.x86_64
file /usr/bin/piconv from install of perl-Encode-2.39-1.el5.rf.x86_64

Sounds like more than a man conflict that we can ignore :-(

File a bug at RH to repackage it as a separate entity?