[rt-users] Possible to downgrade DB from 3.8 to 3.6?

[Darin Perusich]

The OpenSuSE build service has a lot of good information about using the
Build Service for packaging perl modules, see
http://en.opensuse.org/openSUSE:Packaging_Perl and
http://old-en.opensuse.org/Packaging/Perl. The can easily be adopted for
building locally.

All the perl packages needed for a default RT installation are available
in the perl development language repo,
http://download.opensuse.org/repositories/devel:/languages:/perl/. I ran
into missing packages for RTIR but was able to build rpms for them using
the above information. Additionally, I imported them into my personal
repository with the goal of having them included in the perl repo but
ran into a couple minor issues which I haven't had time to address. This
are build service glitches I'm not sure how to overcome and have nothing
to do with the packages themselves.

--
Darin Perusich
Email: Darin.Perusich at ctg.com
Office: 716-888-3690
Cell: 716-807-4589


> -----Original Message-----
> From: rt-users-bounces at lists.bestpractical.com [mailto:rt-users-
> bounces at lists.bestpractical.com] On Behalf Of John Arends
> Sent: Monday, December 13, 2010 7:14 PM
> To: rt-users at lists.bestpractical.com
> Subject: Re: [rt-users] Possible to downgrade DB from 3.8 to 3.6?
> 
> 
> On Dec 13, 2010, at 6:06 PM, Gary Greene wrote:
> 
> > On 13/12/10 9:43 AM, "John Arends" <jarends at illinois.edu> wrote:
> >> CPAN makes me cranky, but trying to package all the perl modules as
> RPMs
> >> makes me crankier. It's like wrapping one packaging system around
> >> another one, and fighting with both of them.
> >>
> >
> > This is why I use cpan2rpm every time.
> >
> >> The reality is, every time RHEL updates perl, RT will break. I
solve
> >> this by having an identical test system. I apply the updates, see
> what
> >> breaks, and then reinstall the perl modules in question using CPAN.
> >
> > This ALSO can be avoided, if you know how to package your cpan2rpm
> packages
> > in site instead of vendor locations. This allows that NONE of the
> issues
> > that are endemic of RHEL's busted Perl packaging to cause long term
> > headaches for me.
> 
> 
> Do you know of a guide that explains how to do this?
The information transmitted is intended only for the person or entity to which
it is addressed and may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of any action
in reliance upon, this information by persons or entities other than the
intended recipient is prohibited. If you are not the intended recipient of this 
message, please contact the sender and delete this material from this computer.