-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ROOTFS_DIR '/tmp/rear..' is broken, chroot bash test failed #29
Comments
More information about this issue is in the original report at SF#3431201 |
We are waiting for feedback from the original reporter in order to get this ball rolling again... @schlomo: Is there a possibility to get in contact with the reporter using private email ? |
I just went over the SF bug again. I would say close it and wait if it pops up again. I hope that we will have some Ubuntu 64bit as part of our regular test setup. Who knows, maybe he upgraded his system from something older and that caused his /lib dirs to be different. Also, I think that now we have even smarter /lib cloning code so maybe it already fixed it for this user. (I don't know this user and don't have private contact) |
Alright, closing this issue because we lack feedback about a recent and relevant release. If this is still an issue, please re-open this issue. |
Hi, I ran into the same issue:
I ran into this error with Debian/Ubuntu Package from opensuse build service with Version 1.12 and tried the newer 1.13 Release as tar.gz (purged any debian package before). My local.conf:
running on system: Ubuntu 11.10 The bug did'nt show up on rear version 1.10 I used before; but this version didn't allow me to restore the system (as stated in some other bugreport) so I tried to upgrade. root@icinga:~# chroot /tmp/rear.2SahWSVBl6Oualf/rootfs/ where /tmp/rear.2SahWSVBl6Oualf/rootfs/bin/bash is existing and executable I tried also to chroot into a rear-rootfs I copied from a debian system to the ubuntu-box, that worked for fine me. Kind regards |
Hi,
I assume there is a cleaner way to include this into rear (maybe some rule especially for Ubuntu 11.10 so that rear works out of the box. reagards Jan |
@jpeschke What version did you try ? We made an important change in the master branch that should have fixed the issue you see. And so we would like to know if that effectively fixes your issue as well. I would appreciate if you could test the version in the master branch. This is also the first release that can be used without requiring to install it, so you can simply do a |
I tried this version https://github.com/downloads/rear/rear/rear-1.13.0.tar.gz |
I can confirm, that the masterbranch fixed any issue I had with stable versions on Ubuntu 11.10; thanks a lot. |
Ok, good to hear! Closing this again. |
Reported by sid23 as SF#3431201 on 2011-10-31 06:22:17 PDT
Original report
Linux rl01 3.0.0-12-server #20-Ubuntu SMP Fri Oct 7 16:36:30 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
ReaR V1.11.0 in a VM with Ubuntu 11.10 (Supervisor is Ubuntu 11.04 and KVM)
local.conf:
The text was updated successfully, but these errors were encountered: