Hi,
I’m creating a setup where I have RT3 frontend running on Debian Sid,
and the Postgres DB running on a different machine that has Debian
Stable.
I’ve run into a snag, where I’m trying to use the rt-setup-database to
populate postgres.
Of course rt-setup-database is expecting some perl modules that don’t
exist on my stable machine.
I’ve managed to workaround this by pinning the machine to testing, and
apt-getting the required perl libraries:
i.e.
liblocale-maketext-fuzzy-perl
liblocale-maketext-lexicon-perl
liblocale-maketext-perl
and copying the specific RT modules over:
/usr/share/perl5/RT.pm
/usr/share/perl5/RT/I18N.pm
This was working well until I hit this one:
Can’t locate Encode/compat.pm in @INC
I can’t find this module anywhere in debian packages.
I’m left with two choices:
a) manually install Encode::compat from CPAN
b) Find a way of populating the database with out needing to use
rt-setup-database.
Has anyone else tried this sort of thing, or am I on my own?
Help?
TIA
jamie
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Can’t locate Encode/compat.pm in @INC
That says to me that you’re running on perl 5.6, which is explicitly
unsupported. But if you need to run on 5.6.1, you’ll need
Encode::compat. If you upgrade to perl 5.8, the dependency will go
away.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)
iD8DBQFAOTYjQaM/s3DrrJARAml4AJ9lmDfrWR1LkmZ2q2WxOLFvXn4NXwCgvqSy
3rckshyzQh4OOGxUYisd6Ug=
=JbRr
-----END PGP SIGNATURE-----
Hi Jesse,
I realise this.
I can’t find a Debian package that has Encode::compat
The only reason I really need perl for what I’m doing on this machine is
to populate the db. (right?)
If I can find a way to a) populate the db without using
rt-setup-database or b) solve the non-existence of Encode::compat in
debian then I think my problem will be solved…
BTW I do have the DB running on another machine. Can we do interesting
things with pg_dumpall?
jamieOn Mon, 2004-02-23 at 12:07, Jesse Vincent wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Can’t locate Encode/compat.pm in @INC
That says to me that you’re running on perl 5.6, which is explicitly
unsupported. But if you need to run on 5.6.1, you’ll need
Encode::compat. If you upgrade to perl 5.8, the dependency will go
away.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)
iD8DBQFAOTYjQaM/s3DrrJARAml4AJ9lmDfrWR1LkmZ2q2WxOLFvXn4NXwCgvqSy
3rckshyzQh4OOGxUYisd6Ug=
=JbRr
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Jesse,
The only reason I really need perl for what I’m doing on this machine
is
to populate the db. (right?)
Oh, you’re running RT on a different box? Populate the database from
the remote box.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)
iD8DBQFAOTqpQaM/s3DrrJARAiqDAKCoTTkbeuOZQU28witpwuTMiI+ujgCfYKhk
C38mS3UbDzjO3NXtCPf5a2E=
=mG5A
-----END PGP SIGNATURE-----
Hmm. Good Idea. Change around the existing RT_SiteConfig.pm to
temporarily repoint at the new db.
thanks! - that should fix it.
jamieOn Mon, 2004-02-23 at 12:26, Jesse Vincent wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Feb 22, 2004, at 6:18 PM, Jamie Baddeley wrote:
Hi Jesse,
The only reason I really need perl for what I’m doing on this machine
is
to populate the db. (right?)
Oh, you’re running RT on a different box? Populate the database from
the remote box.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)
iD8DBQFAOTqpQaM/s3DrrJARAiqDAKCoTTkbeuOZQU28witpwuTMiI+ujgCfYKhk
C38mS3UbDzjO3NXtCPf5a2E=
=mG5A
-----END PGP SIGNATURE-----
Jamie Baddeley, Mon, Feb 23, 2004 at 12:18:59PM +1300:
I realise this.
I can’t find a Debian package that has Encode::compat
Did you try `dh-make-perl --cpan Encode::compat’ ? That’s the preferred
way to make debs from perl modules that aren’t yet packaged.
[OT] Do the RT developers have a target distribution/platform, or do they
just try to always use the latest version of everything? Sorry if this
is a FAQ.
g