To go further, the files needed to do the repository definition RPM are
attached to this message. Put the OTRS RPM in a dir on your WWW server.. Fix
your WWW server configuration to make that directory available via the WWW
server
Then, edit the .repo files attached to reflect the URL of that dir (the
baseurl= line is the critical one, although the one in the spec file should
match) and run rpmbuild on the spec file. Put the resulting RPM somewhere on
the WWW site (the same dir as the OTRS RPM is fine) and run ‘createrepo’ in
that directory.
You can then have people do ‘rpm –Uvh
http://whereveryouputit.otrs.com/otrs-stable-repo.x.noarch.rpm’. That will
install the repository and integrate it into yum.
Then ‘yum listrepo’ to check that it installed correctly. Then ‘yum install
otrs-rpm-name’ and watch the fun.
From: otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] On Behalf Of Michiel
Beijen
Sent: Tuesday, November 27, 2012 1:55 PM
To: User questions and discussions about OTRS.
Subject: Re: [otrs] RPM repo (was: FW: OTRS 3.2 beta – statement from Manuel
Hecht, Vice President Global Software Development)
Hi David,
Thanks for the suggestion - I appreciate your concern. Better packaging has
been long on our wish list but the list is long and the amount of hours in a
day is not.
Anyway, to be able to pull this off the upgrade process for patch level updates
should be fool proof and should not require manual actions. Currently, it would
still require manual reinstallation of packages via the OTRS package manager in
case you are using ITSM, for instance. This should be taken care of by the RPM.
That is totally fixable.
And we should create different repositories for the different minor revisions,
so if you would like to upgrade from OTRS 3.1 to 3.2 you could do that by
changing your package repository and running yum upgrade plus any post install
actions, and if you would not change the repo you will keep on receiving 3.1.x
updates.
One other topic is that we currently do not ship with an SELinux profile, which
forces people to set selinux to permissive.
Would there be any RHEL syadmin that can help with the SElinux profile?
Would there be people interested in testing such an RPM repo?
--
Mike.
Op 27 nov. 2012 16:35 schreef David Boyes
dbo...@sinenomine.netmailto:dbo...@sinenomine.net het volgende:
A suggestion:
Something that would be really helpful if you’d like to encourage beta testing:
a network-accessible repository (either yum or apt, preferably both) that can
be added to a system, and then used to install, eg a repository definition file
that can be retrieved with wget, and then being able to do ‘yum update; yum
install otrs’. This is enterprise software, and the “download a RPM and
figure out how to bolt it into the various install systems” is a real PITA.
At least for the RPM variants, you just need to take the dir that contains the
RPM and run ‘createrepo’ on it. It’s a little more work for Debian based
systems, but IMHO it would REALLY help the uptake on beta testing. It’s also
becoming a hallmark of a serious enterprise application to operate this way.
Feed: OTRS Community Blog
Posted on: Monday, November 26, 2012 6:54 AM
Author: Mike
Subject: OTRS 3.2 beta – statement from Manuel Hecht, Vice President Global
Software Development
On 30th October, we have released beta 1 of OTRS 3.2. Today we have released
the third
betahttp://www.otrs.com/en/open-source/community-news/releases-notes/release-notes-otrs-help-desk-320-beta3/,
together with beta’s of our ITSM modules. After some more beta releases we’ll
finally release the stable release on January 29th, 2013.
One of the new features Shawn already showed in an earlier blog post
http://blog.otrs.org/2012/10/29/something-is-brewing-on-the-horizon/ is the
all-new Customer Information Center. One other feature we’ll write more about
in the upcoming weeks is the new Process Management features, with a nice GUI
where you can design interfaces and actions.
Apart from that, we have the usual smaller and bigger performance- and UI
improvements.
Below a video statement from Manuel Hecht, our Vice President Global Software
Development, who talks about the new OTRS 3.2 release and more.
Please try out the
betahttp://www.otrs.com/en/open-source/community-news/releases-notes/release-notes-otrs-help-desk-320-beta3/
now. We recommend that you do not use this software in production yet,
although we are ‘dogfooding’ ourselves and have upgraded our internal portal to
3.2.x recently. But installing it on a test environment is absolutely something
you could consider, and plan your move to 3.2 accordingly. Obviously, OTRS
Group can support you with
upgradinghttp://www.otrs.com/en/solutions/services/ if you want, just contact
us to discuss. And if you are an existing customer with a Professional or
Enterprise subscriptionhttp://www.otrs.com/en/solutions/subscriptions/, we’ll
perform your
