Topic: Bugzilla 3.0.3 Perl Mod Install help needed for Email::MIME

[pauljclarke]

Hi,

I have a working copy of Bugzilla 2.22.2 on my SME7.3 box and am looking at making a HowTo for downloading and installing / upgrading to 3.0.3 (and then 3.1.x later)

All is good so far however I need the perl Module Email:MIME:Modifier... which I'm pointed towards doing the following:

Code: [Select]

perl -MCPAN -e 'install "Email::MIME::Modifier"'
However this is not installing without force? see below tail of output - please can anyone help?

Code: [Select]

Test Summary Report
-------------------
t/content_id.t  (Wstat: 65280 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 15 tests but ran 1.
t/ct_attrs.t    (Wstat: 65280 Tests: 3 Failed: 2)
  Failed tests:  1-2
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 10 tests but ran 3.
t/disposition.t (Wstat: 65280 Tests: 2 Failed: 2)
  Failed tests:  1-2
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 7 tests but ran 2.
t/encoding.t    (Wstat: 65280 Tests: 2 Failed: 2)
  Failed tests:  1-2
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 14 tests but ran 2.
t/parts.t       (Wstat: 65280 Tests: 2 Failed: 2)
  Failed tests:  1-2
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 22 tests but ran 2.
Files=7, Tests=11,  0 wallclock secs ( 0.03 usr  0.01 sys +  0.29 cusr  0.08 csys =  0.41 CPU)
Result: FAIL
Failed 5/7 test programs. 9/11 subtests failed.
make: *** [test_dynamic] Error 255
  /usr/bin/make test -- NOT OK
Running make install
  make test had returned bad status, won't install without force


[Marco Hess]

Code: [Select]

perl -MCPAN -e 'install "Email::MIME::Modifier"'
Why don't you look for that package as an rpm?

The quick look with google found:

Code: [Select]

ftp://fr.rpmfind.net/linux/dag/redhat/el4/en/i386/dag/RPMS/perl-Email-MIME-Modifier-1.441-2.el4.rf.noarch.rpm
I personally try to stay away from CPAN if I need to install something in a production server as it tend to ínstall/update much more than you are looking for and I am always afraid it breaks other applications through these upgrades. It's verbosity I also find confusing and it tends to hide some of its actions.

Marco

[pfloor]

Most perl modules can be found in the Dag repo.  Set up like this:

db yum_repositories set dag repository \
Name 'Dag - EL4' \
BaseURL 'http://apt.sw.be/redhat/el4/en/$basearch/dag' \
EnableGroups no \
GPGCheck yes \
GPGKey http://dag.wieers.com/packages/RPM-GPG-KEY.dag.txt \
Visible no \
Exclude freetype,htop,iptraf,rsync,syslinux \
status disabled

expand-template /etc/yum.conf

You *might* have to install the gpg key for dag (can't remember, it's been a long time since I set mine up).

rpm --import http://dag.wieers.com/packages/RPM-GPG-KEY.dag.txt

Then install required perl module:

yum --enablerepo=dag install perl-Email-MIME-Modifier

WARNING NOTE: Do not enable this repo by default (eg: status enabled) as it will pull in all kinds of unwanted updates and possibly render your server unusable.

[cactus]

Most perl modules can be found in the Dag repo.  Set up like this:

Please refer to the wiki for configuration instructions as the configuration template might change sometime, the wiki will always have the latest entries, which is hard to maintain in the forums: http://wiki.contribs.org/Dag

[pfloor]

Please refer to the wiki for configuration instructions as the configuration template might change sometime, the wiki will always have the latest entries, which is hard to maintain in the forums: http://wiki.contribs.org/Dag

Agreed, BUT...

That page has no warnings about making sure that repo is disabled by default.  This little footnote "Warning"  is essential (especially on the dag repo) and needs to be added to the page that you directly linked to.

[brianr]

.. and the page is locked so it cannot be edited.  there is already a correction under the "discussion" tab.

I have created a bug entry for it.

http://bugs.contribs.org/show_bug.cgi?id=4260

[cactus]

.. and the page is locked so it cannot be edited.  there is already a correction under the "discussion" tab.

I have created a bug entry for it.

http://bugs.contribs.org/show_bug.cgi?id=4260

I disagree, the pages list the configuration instructions only and should not be used in other purposes actually than to be included in setup instructions using the Repository template, that is the way I designed them.

The FAQ states that you should not enable other repositories than the ones listed there. I do not understand why users change the configuration settings as we suggest them like this to them for a reason.

[pfloor]

I disagree, the pages list the configuration instructions only and should not be used in other purposes actually than to be included in setup instructions using the Repository template, that is the way I designed them.

The FAQ states that you should not enable other repositories than the ones listed there.

And that's why you should never post a link directly to that particular page, it skips the FAQ and lacks the appropriate warning.

I do not understand why users change the configuration settings as we suggest them like this to them for a reason.

Really now, I can't believe you are actually saying this. <Please Note smiley here!

[pauljclarke]

FYI - above comments all worked ok, added Repo and yum'ed it in, thats people.