Public bug reported:
I'm presently configuring anew Nssbackup under a fresh Karmic,
remembering what worked previously under an updated one.
Present Nssbackup is reported as 0.2-0~rc8 by package manager, and as
0.2-0 RC7 by it's Help>About
But there is more confusing and embarassing:
Opening the gui I see 2 active combos
1/ Compression choice: actve and empty
2/ Split size: active displaying illimited.
I select 4Go, in order ton save on a FAT32 USB key, I save the config, and
Backup now: I receive an error message: "at the time, slitting is not
compatible with compressing
So I select none in the compression combo, see that the split combo
turns inactive and empty, save the configuration and Backup now
I receive an error message, duly reported in the log:
Sauvegarde impossible : tar: Suppression de « / » au début des noms des membres
gzip: stdout: File too large
tar: /media/KINGSTON/2010-02-01_12.09.21.598292.portable-leleu.inc/files.tar.gz
: la fonction write a échoué: Relais brisé (pipe)
tar: Erreur non récupérable : arrêt du traitement
It's clear taht I did not succeed to the the 4 Go limitation....
** Affects: nssbackup
Importance: Undecided
Status: New
--
some oddities
https://bugs.launchpad.net/bugs/515449
You received this bug notification because you are a member of NSsbackup
team, which is subscribed to NSsbackup.
_______________________________________________
Mailing list: https://launchpad.net/~nssbackup-team
Post to : nssbackup-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nssbackup-team
More help : https://help.launchpad.net/ListHelp
