Seafile Client .deb packages on ubuntu and debian


In 6.1.7 we had to split out the Python libraries to separate packages python-ccnet and python-seafile. Previously, they were included in the lib* packages, but that was actually in violation of the Debian Policy.
But, as I said, this introduction of new binary packages causes their upload to require manual intervention, which increases the time it takes for them to be available.


installing python-ccnet fixes the ImportError, but now i get the same Error when i run seaf-cli start as when i was compiling 6.1.7:
Starting ccnet daemon ...
ccnet: symbol lookup error: /usr/lib/x86_64-linux-gnu/ undefined symbol: g_date_copy
CCNet daemon failed to start.


6.1.2. was never in the Debian repositories, so I think you’re talking about the PPA, right?
In Debian, there are no version upgrades of packages within a stable release. So new versions and new packages can only go to testing (until that becomes the new stable release) - that’s why backports was created.



that’s weird - I’m running testing and it works for me…
Could you send me the output of apt policy ccnet libglib2.0-0 on your system?


Installiert: 6.1.7-2
Installationskandidat: 6.1.7-2
*** 6.1.7-2 500
500 testing/main amd64 Packages
100 /var/lib/dpkg/status
6.0.4 500
500 stretch/main amd64 Packages
Installiert: 2.56.1-2
Installationskandidat: 2.56.1-2
*** 2.56.1-2 500
500 testing/main amd64 Packages
100 /var/lib/dpkg/status
2.48.0-1~bpo8+1 100
100 jessie-backports/main amd64 Packages


Ah, so you seem to have lots of other repositories enabled (e.g. “stretch” and “jessie-backports”).
What does lsb_release -a say?


No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux testing (buster)
Release: testing
Codename: buster

I have jessie-backports and seafile ppa but both aren’t used for this?


Do you maybe accidentally use some cruft that was leftover from your compilation?
Could you verify that

$ which ccnet

You could also maybe try reinstalling all of the packages:
apt install --reinstall ccnet libccnet0 libglib2.0-0 ?


I deleted the src folder completely and never got to the point of make install so there shoudn’t be anything left.

returns the same for me.

I did the reinstall, same error still.


true, i just setup a VM with a fresh debian testing and its working fine.
Meanwhile i removed every package from non-testing repos and deactivated them.
Then i did a apt install --reinstall on every package that gets installed on a fresh debian testing when you run apt install seafile-cli python-ccnet
Still same error…
Any help is greatly appreciated
EDIT: The files behind the symbolic link /usr/lib/x86_64-linux-gnu/> have the exact same date and size on my system and the VM


I have no idea ATM…


Holy cow i fixed it.
This is what i did:
I used ldd to check the shared libraries required by each program or shared object and found a difference to the fresh VM:
ldd -r /usr/lib/x86_64-linux-gnu/

returned […] => /lib/x86_64-linux-gnu/ […]
instead of /usr/lib/x86_64-linux-gnu/
so i went and checked in /lib and indeed there was an old version that didn’t have any package associated with it (check with dpkg -S) so i just deleted the old libraries. Now its working again.


Thanks for doing this. I am using the stretch-backports version for quite a while now and I really appreciate how easy the process of installing was!
Keep up the good work :slight_smile:


Hello again,


finally the latest version of the Seafile Client stack (6.1.8) is fully available in the official Debian and Ubuntu repositories. For users of the current stable version of Debian 9 “Stretch”, they are available via the official stretch-backports repository:

If you have any issues with those packages, please report the to the Debian or Ubuntu bug tracking systems using the reportbug tool.

Best wishes,
/cc @scheff


How did you solve the problem with qt5Linguisttools on Debian i686?


I don’t know what you’re referring to, but I didn’t do anything special about that.

You can see all the packaging stuff in


Seems you could ignore it and just build it.
Anyway, thanks.