I can confirm the issue has been solved.

I have no clue why it does not work for you, but here is plan B!

Plan B 1 - open a terminal on the server 2 - go to ../files/libri/bibliotecadicalibre 3 - type: nano convert.sh (or any other name you like) 4 - copy this into the nano editor

#!/bin/bash rm -f metadata.dbv4 sqlite3 metadata.db .dump > metadata.dump sqlite3 metadata.dbv4 < metadata.dump rm -f metadata.dump echo "done ....."

save with <ctrl>x and yes 5 - make executable: chmod +x convert.sh 6 - run this executable: ./convert.sh 7 - there should be a metadata.dbv4 file in the calibre directory. Is there? 8 - got cops in a browser. 9 - report back

I run COPS on a couple of Centos servers, one v7 and v8. As noted by Althor84, when I upgraded my local version of Calibre to 5.6, and copied the dataset out to the servers, COPS stopped working on Centos 7 but not on Centos 8. The issue is indeed the old sqlite3.7.17 whereas Centos 8 runs sqlite3.26.0. You can test which versions of sqlite3 will open the Calibre 5.x database from the command line with:

sqlite3.x.x /path/to/metadata.db then: sqlite> .tables

This will list out the tables if it can open the db but zilch if it cannot.

As marioscube notes, there is not an obvious Centos supported upgrade for the sqlite3 component. It seems to play a central role in the management of the OS and is tightly integrated. If you just drop a different version of sqlite3 into /usr/bin then "bad things may happen".

However, I did find a post in a Reddit discussion from a user who had similar problems with Ruby on Rails who gave instructions for using a fedora packages from the Fedora Project. Namely:

wget https://kojipkgs.fedoraproject.org//packages/sqlite/3.8.11/1.fc21/x86_64/sqlite-devel-3.8.11-1.fc21.x86_64.rpm wget https://kojipkgs.fedoraproject.org//packages/sqlite/3.8.11/1.fc21/x86_64/sqlite-3.8.11-1.fc21.x86_64.rpm sudo yum install sqlite-3.8.11-1.fc21.x86_64.rpm sqlite-devel-3.8.11-1.fc21.x86_64.rpm

check the sqlite3 version with: sqlite3 --version.

I tried this out in a VM of Centos 7. It seemed to work fine with no complaints. The sqlite3 version checked out as as 3.8.11. Running info.php on the local Apache server (PHP was 7.4.14) gave a pdo_sqlite = 3.8.11 as well as sqlite3 = 3.8.11. COPS now works fine on the 5.6 database. The server itself appears to be running normally, updates are processed as you might expect. I had initially thought that PHP would pick up its sqlite from its extension module but that does not seem to be the case.

There may be other rpm packages which incorporate later versions of sqlite3 but v3.8.11 seems to work with the new Calibre db.

I'm searching my disks for a batch file I made that you could run, but I can't find it.........

I will try again this evening.

777 and the same for all the sub, the files Only metadata_db_prefs_backup.json have 755

What are the "Permessi" of folder../files/libri/bibliotecadicalibre/. ?

same as before

Yes, more or less five times switching the calibre folder up and down... I'll retry again now

Il giorno ven 22 gen 2021 alle ore 16:42 marioscube < notifications@github.com> ha scritto:

That is ok. The size of metadata.dump seems a bit small though.....

You have tried to delete metadata.dump and metadata.dbv4 and then tried it again

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/seblucas/cops/issues/499#issuecomment-765494590, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACD7SDKQTWGRD3FH7AZMFHLS3GMFNANCNFSM4WGETGXA .

That is ok. The size of metadata.dump seems a bit small though.....

You have tried to delete metadata.dump and metadata.dbv4 and then tried it again

I don't know if this matters but the sizes of metadata.db and metadata.dump are different The first one is 405.504.

Yes...

The image does not work, but I believe you. Size of metadata.dump is > 0?

I will test again with my antique setup.

So, what can u say about that?

Hello!

According to https://github.com/jorgebucaran/fisher/issues/651, fisher doesn't allow top-level *.fish files anymore. So I just move top-level *.fish files to functions/*.fish I think omf install agnoster && omf theme agnoster would be fine even after merging this PR.

Hi @kosukemori!

I'm quite reluctant to merge it as it does not concern Oh-my-fish, but during my (short) testing it does not brake anything, so I'll merge it in the hope that it does not break for anybody else.

Hello, thanks to your nice fish theme! I found installation issue with fisher. This PR fixes it:

Fisher 4.2.0 and later doesn't accept *.fish in top level directory anymore.

This PR moves fish_prompt.fish to functions/.

See: https://github.com/jorgebucaran/fisher/issues/651 Ref: https://github.com/oh-my-fish/theme-agnoster/pull/53

+1

+1

Yes. There is

[image: Immagine 2021-01-22 141748.png]

Il giorno ven 22 gen 2021 alle ore 08:24 marioscube < notifications@github.com> ha scritto:

Is there a metadata.dump file in ../cops/tmp/ ?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/seblucas/cops/issues/499#issuecomment-765193781, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACD7SDKL4SJ6KZ6T3YH3673S3ER2LANCNFSM4WGETGXA .

I wish I read more solution-oriented messages in this thread.

We have. The problem isn't that the certificate is expired, the problem is that nobody is available to handle it in a timely manner, or to even answer bug reports about it.

We've also said that either new people need to be introduced (which so far hasn't happened and I don't see any one stepping up, but I also haven't seen anyone ask where prospective candidates would see it - that might help), and I have mentioned that the old people could also come back, either fully or at least to keep the project in maintenance mode by answering issues (even if it's just either "not a bug in oh-my-fish, please look $here" or "yup, please send patches") and merging PRs.

If none of that happens, I maintain that formally winding down the project would be, on the whole, preferable to having it around as a zombie that keeps being recommended to people who then end up asking here and not getting an answer.

Also given the nature of OMF it needs active maintenance at least on the package front - #800 requires an actual change in the OMF repo even tho nothing in OMF changed, simply because the linked package disappeared.

I know this is difficult for you, and please don't assume this is easy for me to write. It's just that I don't think the current situation is good for the users.

I have installed ocean theme today. Then, I tried to install lolfish theme, theme successfully installing but not applying.

Environment report

Oh My Fish version:   7
OS type:              Linux
Fish version:         fish, version 3.1.2
Git version:          git version 2.29.2
Git core.autocrlf:    no
Warning: fish_prompt.fish is overridden.
  fish_config command persists the prompt to ~/.config/fish/functions/fish_prompt.fish
  That file takes precedence over Oh My Fish's themes. Remove the file to fix it:
  rm ~/.config/fish/functions/fish_prompt.fish

Checking for a sane environment...
If everything you use Oh My Fish for is working fine, please don't worry and just ignore the warnings. Thanks!

I am using Fedora, Gnome on Wayland, in gnome-terminal.

Edit: I ran this command, but anything not changed:

rm ~/.config/fish/functions/fish_prompt.fish

I have installed ocean theme today. Then, I tried to install lolfish theme, theme successfully installing but not applying.

Environment report

Oh My Fish version:   7
OS type:              Linux
Fish version:         fish, version 3.1.2
Git version:          git version 2.29.2
Git core.autocrlf:    no
Warning: fish_prompt.fish is overridden.
  fish_config command persists the prompt to ~/.config/fish/functions/fish_prompt.fish
  That file takes precedence over Oh My Fish's themes. Remove the file to fix it:
  rm ~/.config/fish/functions/fish_prompt.fish

Checking for a sane environment...
If everything you use Oh My Fish for is working fine, please don't worry and just ignore the warnings. Thanks!

I am using Fedora, Gnome on Wayland, in gnome-terminal.

Edit: I ran this command, but anything not changed:

rm ~/.config/fish/functions/fish_prompt.fish