backintime fails on IPv6 (easy to fix!)

Bug #1361634 reported by Gilles Schintgen on 2014-08-26
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Back In Time
Fix Released

Bug Description

backintime fails when using an IPv6-only backup destination over ssh. When I confirm my configuration settings, backintime validates the proposed configuration. If the ssh-host is not IPv4-reachable, the ping check in will fail with some error message shown to the user. Simply commenting out the call to self.check_ping_host in pre_mount_check "fixes" this issue and everything works perfectly fine over IPv6!
(Of course, the real fix is to modify the ping check, but this shouldn't take more than a few lines.)

I'm using 1.0.34 as provided by Ubuntu 14.04.

Germar (germar) wrote :

'Easy to fix' is relative ;-) I don't have working IPv6 to test.
If you don't mind it would be great if you could test the Alpha version for 1.1 from my ppa:germar/bit-testing where I tried to fix this.

Changed in backintime:
status: New → In Progress
assignee: nobody → Germar (germar)
importance: Undecided → Medium
milestone: none → 1.1.0
Gilles Schintgen (shigi) wrote :

No more ping error with your ppa :-)

Germar (germar) wrote :

Great! Thanks for testing.

Changed in backintime:
status: In Progress → Fix Committed
Germar (germar) on 2015-01-15
Changed in backintime:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers