Upgraded 3 batches and I noticed that there are so many reloads as there are accounts in the ownCloud

W dniu 18.12.2013 13:20, Thomas Müller pisze:
Hey,

thanks a lot for notifying us about this is.
We are aware of this issue and we are about to prepare a fix.

There will be a 5.0.14a arriving soon.

Thanks,

Thomas

https://github.com/owncloud/apps/issues/1564

Am Mittwoch, den 18.12.2013 um 13:15 schrieb Daniel Wunderlich:
Hello everybody,

thanks for the 5.0.14 upgrade. Can't wait not to have to redownload all
files again. ;o)

I just added the new repository for oC 4 in my owncloud.list (Ubuntu
12.04-Server) and did apt-get update and apt-get upgrade. After
rebooting the server and accessing oC with Firefox, the upgrade message
appeared. After a while, I only got the 'Maintaince mode on'-message. I
set 'maintenance' => false at config.php, but now I get the following
message:

Failed to upgrade "search_lucene". Exception="Failed to update database
structure (MDB2 Error: constraint violation, _doQuery: [Error message:
Could not execute statement] [Last executed query: ALTER TABLE
`oc_lucene_status` ADD PRIMARY KEY (`fileid`)] [Native code: 1062]
[Native message: Duplicate entry '3' for key 'PRIMARY'] )"

Following this mailing list for a long time now, I've seen problems with
lucene several times. Strange ...

I just opened a bug report [1] concerning this behaviour.

Regards,
Daniel

[1] https://github.com/owncloud/core/issues/6484
_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud

_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud


--
Cyryl Sochacki

Wiem że świat nie spodziewa się po nas wiele. Wystarczy, że odpowiesz sobie na 
bardzo ważne pytanie: co lubię w życiu robić, a potem zacznij to robić.

_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud

Reply via email to