I can confirm this on 32bit fully updated 8.10 as well.
After some more testing, I can confirm this is a gcc bug because it is
the -O2 flag which causes the problem. Without that, it is fine.
I have attached the source code to the test to this bug report. Compile
like so:
$ gcc -o bar1 -O2
Really, all that's needed is this part, which basically occurs on line
222 of the above bar.c:
void main() {
int i = 0;
for (i = 1; 0 i; i *= 2) {
if (0)
return;
}
return;
}
As you can see, the loop is designed to end
For the record, re-running autoconf on the given project's files
(archfs), updated the configure script so that it no longer writes the
test in this way. The test then passes appropriately with Ubuntu 8.10.
I'll file a bug against the archfs project to update their configure
script.
--
mktime
Oh, I see. I'll try to remember to only set it for the rdiff-backup
line and not the rdiff-backup (Ubuntu) line.
If you want to backport the fix to your package, here's the patch:
http://lists.nongnu.org/archive/html/rdiff-backup-commits/2009-03/msg00023.html
I can't say when the next release of
Argh, typo. That's what I get for hand-moving patches out of my local
tree. :-( Thanks so much for testing!!
In the patch, change:
assert len(Globals.connection) == len(rpaths) + 1
to
assert len(Globals.connections) == len(rpaths) + 1
(connection - connections)
--
jaunty rdiff-backup
Acknowledging as bug in rdiff-backup. This bug only affects the --test-
server option, and is an unintended consequence of a bug fix in 1.2.6.
I'll get working on a fix.
--
jaunty rdiff-backup can't use --test-server with a rdiff-backup --server
--restrict command-locked remote side
Fixed in CVS. Will be included in next rdiff-backup releases, 1.2.8 and
1.3.4.
** Changed in: rdiff-backup (Ubuntu)
Status: Confirmed = Fix Committed
--
jaunty rdiff-backup can't use --test-server with a rdiff-backup --server
--restrict command-locked remote side
whoops, I meant 1.2.9 there. sorry for the spam.
--
jaunty rdiff-backup can't use --test-server with a rdiff-backup --server
--restrict command-locked remote side
https://bugs.launchpad.net/bugs/349072
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Rdiff-backup 1.2.8 and 1.3.3 have been released.
** Changed in: rdiff-backup (Ubuntu)
Status: Fix Committed = Fix Released
--
rdiff-backup crashed with IOError in __init__()
https://bugs.launchpad.net/bugs/329722
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi Sarah,
I might be able to spin a new release on Monday.
--
rdiff-backup crashed with IOError in __init__()
https://bugs.launchpad.net/bugs/329722
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Yup, that's why. It looks like you did your first few backups as 'hew'
and then all subsequent backups as root.
The code to check for this situation examines the ownership of the
'char_to_quote' file, which is the first file that rdiff-backup attempts
to access. Since that file is owned by 'hew'
Fix committed to CVS. Will be included in next releases: 1.2.8 and
1.3.3.
** Changed in: rdiff-backup (Ubuntu)
Status: New = Fix Committed
--
rdiff-backup crashed with IOError in __init__()
https://bugs.launchpad.net/bugs/329722
You received this bug notification because you are a member
Well that's good -- at least rdiff-backup isn't failing to make a
directory which the shell can easily create. :-)
Actually, I think you might be able to avoid this problem entirely if you set
the right options in your shell. A search for ntfs-3g invalid or incomplete
multibyte or wide
Wait a sec ... the version you are running already has code in it to
check this situation. I just ran the same scenario and got an
appropriate error message (not a traceback). The permissions on your
rdiff-backup-data are not what I expect.
What are the permissions?
$ ls -la
Hmm, yes. The previous fix only applied to files which generate the
Invalid or incomplete multibyte or wide character error.
Unfortunately, with a directory, it isn't clear what to do. Should
rdiff-backup skip the entire directory since it can't create it on the
destination? (Analogous to what it
Hew,
The traceback shows:
IOError: [Errno 13] Permission denied: '/media/terabyte/rdiff-backup
/rdiff-backup-
data/mirror_metadata.2009-02-15T03:00:24+11:00.snapshot.gz'
Were you not running rdiff-backup as the user who runs the backups? What
are the permissions on that file, and the
This issue is definitely fixed in rdiff-backup 1.2.5. The error is no
longer fatal and the user will be informed about the problem.
** Changed in: rdiff-backup (Ubuntu)
Status: Incomplete = Fix Released
--
rdiff-backup crashed with OSError in rename()
** Changed in: rdiff-backup (Ubuntu)
Status: Fix Committed = Fix Released
--
rdiff-backup crashed with IOError in reval()
https://bugs.launchpad.net/bugs/284506
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Looking at this bug again, I realized that it was fixed Jan 10, 2006 and
released in rdiff-backup 1.1.6.
** Changed in: rdiff-backup (Ubuntu)
Status: Incomplete = Fix Released
--
Problem with keep, backup to samba share
https://bugs.launchpad.net/bugs/109981
You received this bug
A warning message is printed, which the user must have disregarded, or
was not displayed by a GUI (was Keep used?). The warning message has
been present since the first version, and was improved in versions
0.12.7 and 0.13.4.
Rdiff-backup permits this because 1) it succeeds on some platforms (I
I have updated CVS so that a connection dropped message is reported if
this error happens again. The stack trace will no longer be printed.
** Changed in: rdiff-backup (Ubuntu)
Status: Confirmed = Fix Committed
--
rdiff-backup crashed with OSError in setdata()
** Changed in: rdiff-backup (Ubuntu)
Status: Invalid = Fix Committed
--
rdiff-backup crashed with IOError in reval()
https://bugs.launchpad.net/bugs/284506
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Changed in: rdiff-backup (Ubuntu)
Status: Confirmed = Fix Released
--
[apport] rdiff-backup crashed with IOError in log_to_term()
https://bugs.launchpad.net/bugs/119992
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: rdiff-backup (Ubuntu)
Status: Confirmed = Fix Released
--
[apport] rdiff-backup crashed with IOError in log_to_term()
https://bugs.launchpad.net/bugs/107053
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This traceback is due to insufficient permissions to access the rdiff-
backup destination. I have added a fix to CVS which will give the user a
nicer error message if this happens in the future (a traceback will no
longer be generated).
The fix will be part of rdiff-backup 1.2.3 and subsequent
This traceback is due to insufficient permissions to access the rdiff-
backup destination. I have added a fix to CVS which will give the user a
nicer error message if this happens in the future (a traceback will no
longer be generated).
The fix will be part of rdiff-backup 1.2.3 and subsequent
** Changed in: rdiff-backup (Ubuntu)
Status: New = Fix Released
--
Crashes on cron job
https://bugs.launchpad.net/bugs/117983
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: rdiff-backup (Ubuntu)
Status: New = Fix Released
--
rdiff-backup crashed with OSError in setdata()
https://bugs.launchpad.net/bugs/227918
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Given that Jakob was using a non-standard version, I am marking this bug
as invalid. Many people use --remove-older-than without trouble ... this
traceback indicates that there was a bug in the Python code (not due to
the backup repository). I assume it was due to Jakob's modifications.
**
** Changed in: rdiff-backup (Ubuntu)
Status: Incomplete = Fix Released
--
rdiff-backup throws traceback output
https://bugs.launchpad.net/bugs/158431
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This is a bug. Rdiff-backup should print something helpful when:
OSError: [Errno 107] Transport endpoint is not connected:
'/home/username/.gvfs'
happens. Although, the real fault is that gvfs failed.
** Changed in: rdiff-backup (Ubuntu)
Status: Incomplete = Confirmed
--
rdiff-backup
Correct.
Rdiff-backup only guarantees compatibility between stable releases, eg:
1.2.0, 1.2.1, and 1.2.2 are compatible together and 1.0.5, 1.0.4, 1.0.3,
etc.. The development series, 1.1.x, came with no backwards-compatible
guarantees.
Ubuntu was shipping development releases, and can either
** Changed in: rdiff-backup (Ubuntu)
Status: Incomplete = In Progress
--
rdiff-backup --list-increments does not distinguish between error conditions
https://bugs.launchpad.net/bugs/128244
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
33 matches
Mail list logo
