Hi, After installing gcc-4.0-base, libwxgtk2.4-1, linux-sound-base, discover1-data, libdiscover1, and discover1 and upgrading alsa-utils from 1.0.6-4 to 1.0.9a-4, libgcc1 from 1:4.0.0-11 to 1:4.0.1-6, libstdc++6 from 3.4.3-5 to 4.0.1-6, audacity from 1.2.3-1 to 1.2.3-2, libsndfile1-dev from 1.0.10-2 to 1.0.11-1, alsa-base from 1.0.6a-11 to 1.0.9b-4 and libasound2 from 1.0.8-3 to 1.0.9-3, I ran rdiff-backup again.
It worked. Thanks, Kingsley On 09/05/05 13:01, dean gaudet wrote: > On Mon, 5 Sep 2005, Kingsley G. Morse Jr. wrote: > > > Hi, > > > > What may have caused the following stack traces, > > and how might they be fixed? > > > > They seemed to happen at about the same time as > > upgrading several Debian linux packages. > > the upgrade was happening while rdiff-backup was running? did you get new > python2.3 packages? (istr there was a security fix in at least deb > unstable python 2.3 this week...) > > signal 15 is SIGTERM... sounds suspiciously like something tried to kill > your rdiff-backup... does this happen every time? > > -dean _______________________________________________ rdiff-backup-users mailing list at [email protected] http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
