Should I file it as a bug for deja-dup then?
Thanks
Martin

On Fri, Jan 25, 2013 at 6:33 PM, Michael Terry
<[email protected]>wrote:

> Ah good point about Deja Dup forcing it.
>
> Can't merely log it, since in 0.6.21, the new style bindings became
> mandatory when using --gio.  So duplicity is rightly failing to do what
> it was asked to do.  Falling back to non-gio is not necessarily good
> behavior.
>
> -mt
>
> On 01/25/2013 12:21 PM, Martin Jinoch wrote:
> > this command line is constructed by deja-dup, so I can not modify it
> > easily. I "solved" it by commenting out the "use_gio" method in
> > commandline.py
> >
> > But still, wouldn't that make sense to just log warning instead of
> halting
> > in this case?
> >
> > Martin
> >
> >
> > On Fri, Jan 25, 2013 at 5:49 PM, Martin Jinoch
> > <[email protected]>wrote:
> >
> >> Public bug reported:
> >>
> >> Description:    Ubuntu 10.04.4 LTS
> >> Release:        10.04
> >>
> >> duplicity:
> >>   Installed: 0.6.21-0ubuntu0ppa21~lucid1
> >>   Candidate: 0.6.21-0ubuntu0ppa21~lucid1
> >>   Version table:
> >>  *** 0.6.21-0ubuntu0ppa21~lucid1 0
> >>         500
> http://ppa.launchpad.net/duplicity-team/ppa/ubuntu/lucid/main Packages
> >>         100 /var/lib/dpkg/status
> >>      0.6.08b-0ubuntu2.1 0
> >>         500 http://cz.archive.ubuntu.com/ubuntu/ lucid-updates/universe
> >> Packages
> >>         500 http://ubuntu.inode.at/ubuntu/ lucid-updates/universe
> Packages
> >>      0.6.08b-0ubuntu2 0
> >>         500 http://cz.archive.ubuntu.com/ubuntu/ lucid/universe
> Packages
> >>         500 http://ubuntu.inode.at/ubuntu/ lucid/universe Packages
> >>
> >>
> >> On Ubuntu 10.04 when I try to run duplicity
> (0.6.21-0ubuntu0ppa21~lucid1)
> >> with command line such as:
> >> duplicity collection-status --exclude=/media/BACKUP/dejadup
> >>  --exclude=/tmp --exclude=** --gio file:///media/BACKUP/dejadup
> >> --verbosity=9 --archive-dir=/home/jyyna/.cache/deja-dup
> >> --log-file=/tmp/deja-dup-UJ8JRW
> >>
> >> it stops with error message:
> >> Unable to load gio backend: No module named gi.repository
> >>
> >> previous version (duplicity 0.6.08) worked fine (it logs just warning,
> >> that giobackend is not found, but it works then)
> >>
> >> seems to be caused by a changed way  of loading giobackend that is no
> >> longer loaded in backends.py (it is in 0.6.08) but in commandline.py
> >> where in parse_cmd_line_options it "throws" ImportError and stops.
> >>
> >> ** Affects: duplicity (Ubuntu)
> >>      Importance: Undecided
> >>          Status: New
> >>
> >> --
> >> You received this bug notification because you are subscribed to the bug
> >> report.
> >> https://bugs.launchpad.net/bugs/1105252
> >>
> >> Title:
> >>   duplicity refuses to start when --gio command line parameter is used
> >>
> >> Status in “duplicity” package in Ubuntu:
> >>   New
> >>
> >> Bug description:
> >>   Description:  Ubuntu 10.04.4 LTS
> >>   Release:      10.04
> >>
> >>   duplicity:
> >>     Installed: 0.6.21-0ubuntu0ppa21~lucid1
> >>     Candidate: 0.6.21-0ubuntu0ppa21~lucid1
> >>     Version table:
> >>    *** 0.6.21-0ubuntu0ppa21~lucid1 0
> >>           500
> http://ppa.launchpad.net/duplicity-team/ppa/ubuntu/lucid/main Packages
> >>           100 /var/lib/dpkg/status
> >>        0.6.08b-0ubuntu2.1 0
> >>           500 http://cz.archive.ubuntu.com/ubuntu/lucid-updates/universe
> >> Packages
> >>           500 http://ubuntu.inode.at/ubuntu/ lucid-updates/universe
> >> Packages
> >>        0.6.08b-0ubuntu2 0
> >>           500 http://cz.archive.ubuntu.com/ubuntu/ lucid/universe
> Packages
> >>           500 http://ubuntu.inode.at/ubuntu/ lucid/universe Packages
> >>
> >>
> >>   On Ubuntu 10.04 when I try to run duplicity
> >> (0.6.21-0ubuntu0ppa21~lucid1) with command line such as:
> >>   duplicity collection-status --exclude=/media/BACKUP/dejadup
> >>  --exclude=/tmp --exclude=** --gio file:///media/BACKUP/dejadup
> >> --verbosity=9 --archive-dir=/home/jyyna/.cache/deja-dup
> >> --log-file=/tmp/deja-dup-UJ8JRW
> >>
> >>   it stops with error message:
> >>   Unable to load gio backend: No module named gi.repository
> >>
> >>   previous version (duplicity 0.6.08) worked fine (it logs just warning,
> >>   that giobackend is not found, but it works then)
> >>
> >>   seems to be caused by a changed way  of loading giobackend that is no
> >>   longer loaded in backends.py (it is in 0.6.08) but in commandline.py
> >>   where in parse_cmd_line_options it "throws" ImportError and stops.
> >>
> >> To manage notifications about this bug go to:
> >>
> >>
> https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1105252/+subscriptions
> >>
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1105252
>
> Title:
>   duplicity refuses to start when --gio command line parameter is used
>
> Status in “duplicity” package in Ubuntu:
>   Won't Fix
>
> Bug description:
>   Description:  Ubuntu 10.04.4 LTS
>   Release:      10.04
>
>   duplicity:
>     Installed: 0.6.21-0ubuntu0ppa21~lucid1
>     Candidate: 0.6.21-0ubuntu0ppa21~lucid1
>     Version table:
>    *** 0.6.21-0ubuntu0ppa21~lucid1 0
>           500 http://ppa.launchpad.net/duplicity-team/ppa/ubuntu/lucid/main 
> Packages
>           100 /var/lib/dpkg/status
>        0.6.08b-0ubuntu2.1 0
>           500 http://cz.archive.ubuntu.com/ubuntu/ lucid-updates/universe
> Packages
>           500 http://ubuntu.inode.at/ubuntu/ lucid-updates/universe
> Packages
>        0.6.08b-0ubuntu2 0
>           500 http://cz.archive.ubuntu.com/ubuntu/ lucid/universe Packages
>           500 http://ubuntu.inode.at/ubuntu/ lucid/universe Packages
>
>
>   On Ubuntu 10.04 when I try to run duplicity
> (0.6.21-0ubuntu0ppa21~lucid1) with command line such as:
>   duplicity collection-status --exclude=/media/BACKUP/dejadup
>  --exclude=/tmp --exclude=** --gio file:///media/BACKUP/dejadup
> --verbosity=9 --archive-dir=/home/jyyna/.cache/deja-dup
> --log-file=/tmp/deja-dup-UJ8JRW
>
>   it stops with error message:
>   Unable to load gio backend: No module named gi.repository
>
>   previous version (duplicity 0.6.08) worked fine (it logs just warning,
>   that giobackend is not found, but it works then)
>
>   seems to be caused by a changed way  of loading giobackend that is no
>   longer loaded in backends.py (it is in 0.6.08) but in commandline.py
>   where in parse_cmd_line_options it "throws" ImportError and stops.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1105252/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1105252

Title:
  duplicity refuses to start when --gio command line parameter is used

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1105252/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to