3 Apr
2015
3 Apr
'15
1 p.m.
Hi
This is brilliant and just what I needed. Thank you very much!
Kind regards,
Mahomed
-----Original Message-----
From: users [mailto:users-bounces@xwiki.org] On Behalf Of Marius Dumitru Florea
Sent: 03 April 2015 11:37
To: XWiki Users
Subject: Re: [xwiki-users] Advice on upgrade and testing
On Wed, Apr 1, 2015 at 12:50 PM, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
On Wed, Apr 1, 2015 at 11:35 AM, Mahomed Hussein
<Mahomed(a)custodiandc.com> wrote:
Hi
I wonder if anyone could be kind enough to provide me with some advice and pointers. I’ve
noticed that XWiki runs its distribution upgrade wizard automatically when a new version
is detected, but even though I pressed “Later” it still went ahead and upgraded. Or at
least it appeared to have upgraded part of the system as the core version at the bottom
showed 6.4.3 when the extensions etc. were still for 6.4.2. We started with 6.4.2
(installed using apt-get on Ubuntu 14.04). So, to summarise my questions:
· How do I stop Xwiki from automatically upgrading. I just want it to notify me
then I can plan the upgrade
You are mixing two different things. The upgrade wizard is only about
part of XWiki (the standard wiki pages) and it's been triggered
because you upgraded the WAR probably using apt-get upgrade. If you
don't want XWiki to be upgraded by apt-get you need to look at apt-get
configuration.
As far as I know you can indicate a list of packages
to
not be taken into account automatically by apt-get upgrade.
I successfully 'blocked' upgrades for XWiki by creating the file
/etc/apt/preferences.d/xwiki
with this content:
Package: xwiki-*
Pin: version 6.2.7
Pin-Priority: 1001
See https://help.ubuntu.com/community/PinningHowto
Hope this helps,
Marius
· How do you perform a controlled upgrade and test (I appreciate that this is a
rather in-depth question)? What I need to be able to do is to do an upgrade and then be
able to fairly easily test that the new version doesn’t break any of our documents or
functionality that we depend on. Would the only way to do this be to keep a list of my
changes and check them with every upgrade?
The safest for this is usually to have a test server which is a clone
of the production server on which you do the upgrade and test it
before doing it on the production server.
Thanks in advance for your time and help.
Kind regards,
Mahomed Hussein
Senior NOC Engineer
P.S. We are finalists for Data Centre Colocation Supplier of the year, please help us to
win and VOTE<http://www.dcsawards.com/voting.php> for us
here<http://www.dcsawards.com/voting.php>
Tel: +44 (0)1622 230382
| Email: Mahomed(a)CustodianDC.com
| Web: www.CustodianDC.com<http://www.CustodianDC.com>
| Info: info.CustodianDC.com<http://info.CustodianDC.com>
[Custodian Data Centres]<http://www.CustodianDC.com>
[ISO 27001 IS:567248]
Click to VOTE<http://www.dcsawards.com/voting.php> for Custodian! [DCS Awards
Finalist]
[Like us on Facebook!][Follow us on Twitter][See us on YouTube!]
[Link to us!][Google Plus!]
Click here to view our email
disclaimer<http://www.custodiandc.com/disclaimer.txt>
Registered Office: Maidstone TV Studios, Vinters Park, Maidstone, Kent ME14 5NZ. Company
Number: 07878023
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
--
Thomas Mortagne
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users