[users] Re: problem with amavisd after perl-* update

Dag Wieers dag at wieers.com
Thu Nov 22 18:07:08 CET 2007


On Thu, 22 Nov 2007, John Thomas wrote:

> Dag Wieers said the following on 11/20/2007 01:17 AM:
> > On Mon, 19 Nov 2007, John Thomas wrote:
> >
> > > Dag Wieers said the following on 11/18/2007 12:41 PM:
> > > > > > Install the perl-File-Temp 0.18.
> > > > > That doesn't really work out, at least not on RHEL 5:
> > > > >
> > > > > Transaction Check Error:
> > > > >   file /usr/share/man/man3/File::Temp.3pm.gz from install of
> > > > >   perl-File-Temp-0.18-1.el5.rf conflicts with file from package
> > > > >   perl-5.8.8-10.el5_0.2
> > > > >   file /usr/share/man/man3/File::Temp.3pm.gz from install of
> > > > >   perl-File-Temp-0.18-1.el5.rf conflicts with file from package
> > > > >   perl-5.8.8-10.el5_0.2
> > > > Then locking to a specific version of the module is probably best :-(
> > > Sorry, what does "locking to a specific version of the module" mean?
> >
> > Not installing a newer one. apt has something like pinning, I believe yum
> > has something similar ? But the best thing you can do for production
> > systems, is create your own custom repository with packages that have been
> > tested.
>
> I am still confused with this.  My description below is terse, but it is
> merely brevity first, humility second, to save your time.
>
> 1. "yum install perl-File-Temp" does not work, as mentioned above.
> 2. "yum update" breaks amavisd-new because of 1, as mentioned in thread.
> 3. Presumably, all new and existing users cannot use amavisd-new.
>
> It seems a possible (not tested by me) solution is to somehow get
> perl-file-temp installed via the --nodocs option (source:
> http://www.mail-archive.com/openpkg-dev@openpkg.org/msg18151.html )
>
> Should rpmforge:  (a) modify perl-file-temp so that it has "nodocs", (b) back
> out latest upgrades so that perl-file-temp is not needed by amavisd-new, or
> (c) something else so that rpmforge fixes a known problem?

We cannot install a perl module that Red Hat has put in the perl package
because the default perl include path that Red Hat uses prefers their
own modules over the vendor or site installed modules.

This problem goes back to RH7 and possible much earlier. I cannot find a
reference from the previous century, but I did found there bugzilla
entries:

	https://bugzilla.redhat.com/show_bug.cgi?id=124443

The only thing that you can do now is downgrade manually. With apt you can
do:

	apt-cache policy perl-MIME-tools
	apt-get install perl-MIME-tools=5.420

And you should also disable using RPMforge for production systems because
we cannot prevent a problem like this from happening. Cherry-pick and
maintain you own repository of packages for production systems after you
have tested any combination of packages you want to use.

Kind regards,
-- 
--   dag wieers,  dag at wieers.com,  http://dag.wieers.com/   --
[Any errors in spelling, tact or fact are transmission errors]



More information about the users mailing list