Re: Update 1.5 to 1.6

I'm finally following this up, trying to import the SVN repository into 
a bazaar (bzr) one on launchpad.net. In the process, I notice that the 
svn:externals point to the old svn.bitflux.ch domain rather than the 
Liip one.

The problem occurs here:

svn co --non-interactive \
   https://svn.bitflux.ch/repos/public/fluxcms/trunk

> svn: OPTIONS of 'https://svn.bitflux.ch/repos/public/fluxcms/trunk': Server certificate verification failed: certificate issued for a different hostname, issuer is not trusted (https://svn.bitflux.ch)

Looks like pointing to the old domain name causes problems because the 
SSL certificate is for *.liip.ch, not *.bitflux.ch.

best regards,
adam


Christian Stocker wrote:
> Hi
> 
> 
> 
> On 4.8.2008 21:25 Uhr, Adam Lindsay wrote:
>  > Pardon my threadjacking, but where's 1.6?
> 
> There's no officially released 1.6 yet, it's on our near future todo list.
> 
> The plan is to release 1.6 ASAP (the next few weeks) and then switch to 
> a so called stable trunk policy, so that trunk is always usuable und 
> developement happens on branches. We still try to put official releases 
> out, but you know our track record :)
> 
> With the stable trunk policy, one can at least be somehow sure, that the 
> trunk is not getting the latest untested whizz and breaks totally your 
> app :)
> 
> The further near term plan (after 1.6 is released) is to improve some of 
> the not-so-good usability issues in Flux CMS, there's a long list of 
> little issues.
> 
> And then we try to decide what's Flux 2.0 will gonna be like, we haven't 
> decided yet, but some ideas are floating around
> 
>  > Somewhat related, is this still the SVN repository of interest? (and not
>  > public/fluxcms?)
>  > https://svn.liip.ch/repos/public/fluxcms_demo/
> 
> https://svn.liip.ch/repos/public/fluxcms_demo
> 
> is the site-specific code, while
> https://svn.liip.ch/repos/public/fluxcms
> is the cms specific code. The latter is automatically included (with 
> svn:externals) from the demo. This allows to seperate cms-code from your 
> local installation code (like themes, specific plugins, etc)
> 
> HTH
> 
> chregu
> 
>  >
>  > adam
>  >
>  > Achim Hut wrote:
>  >> Hi List
>  >>
>  >>
>  >> I want to update a Flux CMS Version: 1.5.0-dev/r8230
>  >>
>  >> to
>  >>
>  >> 1.6.0
>  >>
>  >>
>  >> My question is how to update without data-loss. I can't find any readme
>  >> with update instructions or any hints on the website.
>  >>
>  >> Achim
>  >>
> 
-- 
bitflux-cms mailing list
[email protected]
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms