Mailing List Archive

On Thu, 2010-03-11 at 08:49 +0100, Alessandro De Zorzi wrote:
> Hi all, I am new in this list!
>
> After postgres upgrade (from 8.0 to 8.3) and davical upgrade,
> frontend show to me:
>
> "Database schema needs upgrading. Current: 1.2.2, Desired: 1.2.7"
>
> so I do these commands
>
> # su - postgres
>
> postgres at mail:~$ /usr/share/davical/dba/update-davical-database
>
> The database is version 8.3 currently at revision 1.2.2.
> Applying patch 1.2.3.sql ... failed. Attempting next alternative.
> Applying patch 1.2.5.sql ... succeeded.
> Applying patch 1.2.6.sql ... succeeded.
> Applying patch 1.2.7.sql ... succeeded.
> Successfully applied 3 patches.
> Supported locales updated.
> Updated view: dav_principal.sql applied.
> CalDAV functions updated.
> RRULE functions updated.
> WARNING: no privileges were granted for "dav_id_seq"
> Database permissions updated.
>
>
> I do not understand why 1.2.3.sql ... failed and if 1.2.3a and 1.2.4 not
> really needed ?!?
>
> On client (I use iceowl) one calendar show all appointment as "Busy".
>
> Should I apply 1.2.3a and 1.2.4 manually?

No. The system worked as intended :-)

If you are seeing all appointments as 'Busy' then you are accessing that
calendar as a user who only has the read-free-busy privilege to do so.
You should go to the user who owns the calendar and grant more
privileges to the user who is accessing it.

What happened historically was that when I screwed up with version
0.9.6.1 and 0.9.6.2 in that the davical.sql file specified them as
version 1.2.2 when in reality they were version 1.2.4 so if you
installed from that version it was set wrong.

The problem is cleaned up by the 1.2.3.sql file detecting this and
setting the version correctly to 1.2.4, and then promptly failing to
apply itself. The upgrade script then looks at the current database
version and sees that it now needs to apply the patch for 1.2.5 :-)

Very observant of you to notice though - I'm sure you're not the only
person who's had those lines scroll by on the screen!

Regards,
Andrew.

------------------------------------------------------------------------
andrew (AT) morphoss (DOT) com +64(272)DEBIAN
Your boss climbed the corporate ladder, wrong by wrong.
------------------------------------------------------------------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.morphoss.com/pipermail/davical-users/attachments/20100312/632c6b07/attachment.pgp>
-------------- next part --------------

Andrew McMillan ha scritto:
>
>> Should I apply 1.2.3a and 1.2.4 manually?
>>
>
> No. The system worked as intended :-)
>
> If you are seeing all appointments as 'Busy' then you are accessing that
> calendar as a user who only has the read-free-busy privilege to do so.
> You should go to the user who owns the calendar and grant more
> privileges to the user who is accessing it.
>
done, all works fine! thanks so much!

Alessandro