backintime-qt fails to start

[00rob00]

Traceback (most recent call last):
File "/usr/share/backintime/qt/app.py", line 35, in
import qttools
File "/usr/share/backintime/qt/qttools.py", line 47, in
import snapshots
File "/usr/share/backintime/common/snapshots.py", line 34, in
import config
File "/usr/share/backintime/common/config.py", line 32, in
import tools
File "/usr/share/backintime/common/tools.py", line 1802, in
class OrderedSet(collections.MutableSet):
AttributeError: module 'collections' has no attribute 'MutableSet

It stopped working 1st April 2022. There was an update to python3 that day on my distribution, Devuan, python3 (3.9.8-1) to 3.10.4-1 if that is relevant

Thanks
rob

[candardo]

It's a know bug related to python 3.10 and fixed in the newest version. Read the first comment on #1232

[00rob00]

Thanks

[joolz]

Thank you all for trying to pick up the BiT code. A question about priorities: since upgrading to ubuntu 22.04 BiT (as you probably know) wil not even startup due to ubuntu upgrading to python3.10.

As I understand, the fix in BiT is quite simple, is there a chance that it could be picked up and released first? At the moment I can't make backups and if this situation remains I will start using some alternative, and probably not come back to BiT.

I don't want to do this, BiT functionality is really nice, but if it doesn't even start, wel ... Also, all BiT users upgrading to ubuntu 22.04 will have the same issue, and the same decision to make.

And once again thanks for your work on this!

[candardo]

Bit 1.3.2 landed in debiaa so I guess it will be fixed in Ubuntu too soon.

[cfc-librarian]

BIT 1.3.2 is only on (unstable) Debian Sid. The current Debian 11 Bullseye is on 1.2.1.3 and the older Debian 10 Buster is on 1.1.24.0-1. Not sure how long it takes or what the process is for it to move from unstable to stable Debian.

[gsker]

@joolz I'm waiting for it to hit my repos too, but for now the "fix" for me was one line.
So if you are not backing up because of it you should just make the change manually.
https://github.com/bit-team/backintime/pull/1174/files
In common/tools.py change line 1805 (or thereabouts) from
class OrderedSet(collections.MutableSet):
to
class OrderedSet(collections.abc.MutableSet):

I'm just responding to you saying you are not backing up -- but if your only point was that it needs to hit the repos, then I apologize for any offense.
(also -- that's all I had to do -- your mileage may vary.)

[joolz]

@gsker this works for me too, thank you very much! Of course this needs to end up in the repos but for now at least I can backup again.

Makes me wonder... When a new release comes out (Ubuntu in this case), ideally there would be some automated build process that does at least a quick smoke test to see if all the applications in the repos will run. Then again if I think of how much software is in the repos, with all their interrelated dependencies, that would be quite a task. Probably not feasable.

[jdrch]

@gsker Thanks for your reply on #1259. I hadn't realized backintime has its own repo now. I'll add it and update to the latest version. Hopefully that fixes things.

[emtiu]

@gsker Thanks for your reply on #1259. I hadn't realized backintime has its own repo now. I'll add it and update to the latest version. Hopefully that fixes things.

Ideally, this shouldn't be necessary, but at the moment, it's the best available fix. We're working to get the project back on track, and hopefully have a working version included with distributions in the near future. Thanks for your patience :)

[AlexSchr]

As far as I understand
https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/1976164
the packages in Ubuntu 22.04 LTS have been updated, so that back in time now starts successfully. Can anybody confirm that?

[joolz]

Works for me on 22.04, thanks!

[jdrch]

As far as I understand https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/1976164 the packages in Ubuntu 22.04 LTS have been updated, so that back in time now starts successfully. Can anybody confirm that?

I haven't seen the cron error that prompted me to come here in the 1st place since I applied the repo addition fix, so I assume all is well on this end too. Thanks!

[emtiu]

Cool! It would be best to have the current release 1.3.2 in Ubuntu, but having this patch committed is also good. Closing the issue.