- Package:
- febootstrap
- Source:
- supermin
- Submitter:
- Ritesh Raj Sarraf
- Date:
- 2023-04-26 09:00:27 UTC
- Severity:
- normal
I tried a febootstrap of Fedora 12 and it failed. The failure seems to be coming at the end, probably from fakeroot or febootstrap itself. Attached is the full log with the details. Regards, Ritesh
Hi,
I ran the commands (also tried with fedora-12 with same result):
mkdir fed10-64
febootstrap fedora-10 fed10-64 http://mirror/pub/fedora/linux/releases/10/Everything/x86_64/os
which seemed to go ok but than at the end it does this:
Failed:
filesystem.x86_64 0:2.4.19-1.fc10
Complete!
/usr/bin/fakeroot: line 1: 5294 Segmentation fault exit $RESULT
/usr/bin/fakeroot: line 1: 5295 Segmentation fault exit $RESULT
/usr/bin/fakeroot: line 1: 5296 Segmentation fault exit $RESULT
/usr/bin/fakeroot: line 1: 5297 Segmentation fault exit $RESULT
/usr/bin/fakeroot: line 1: 5298 Segmentation fault exit $RESULT
/usr/bin/fakeroot: line 1: 5299 Segmentation fault exit $RESULT
/usr/bin/fakeroot: line 1: 5300 Segmentation fault exit $RESULT
/usr/bin/fakeroot: line 1: 5301 Segmentation fault exit $RESULT
/usr/bin/fakeroot: line 1: 5302 Segmentation fault exit $RESULT
/usr/bin/fakeroot: line 1: 5303 Segmentation fault exit $RESULT
/usr/bin/fakeroot: line 1: 5304 Segmentation fault exit $RESULT
/usr/bin/fakeroot: line 1: 5305 Segmentation fault exit $RESULT
/usr/bin/fakeroot: line 1: 5306 Segmentation fault exit $RESULT
/usr/bin/fakeroot: line 1: 5307 Segmentation fault exit $RESULT
/usr/bin/fakeroot: line 1: 5308 Segmentation fault exit $RESULT
/usr/bin/fakeroot: line 1: 5309 Segmentation fault exit $RESULT
/usr/bin/fakeroot: line 1: 5310 Segmentation fault exit $RESULT
/usr/bin/fakeroot: line 1: 5311 Segmentation fault exit $RESULT
/usr/bin/fakeroot: line 1: 5312 Segmentation fault exit $RESULT
/usr/bin/febootstrap: line 246: 5313 Segmentation fault rm -rf "$target"/var/cache/yum/febootstrap
/usr/bin/febootstrap: line 246: 5314 Segmentation fault rm -rf "$target"/var/cache/yum/febootstrap-updates
/usr/bin/febootstrap: line 93: 5315 Segmentation fault rm -rf "$target"/var/cache/yum/febootstrap-updates
Cheers,
Erik
Which package is this? Segfaults are in any case caused by incompatibilities between glibc in the host and appliance. You have to only install an operating system which is compatible with the host OS. In Fedora we recommend only installing (eg) Fedora 12 on Fedora 12, because that way you know that glibc won't have problems. Rich.
Richard W.M. Jones wrote:
ii febootstrap 2.1-4 tool for bootstrapping a Fedora system (like Debian debootstrap)
I use debootstrap to install debian and ubuntu versions in chroots.
I have installed ubuntu 8.04 on debian testing and a bunch of other
combinations and never seen that before.
So why is febootstrap even made available to be installed under debian?
Erik
This is kind of old, I really need to update this to the latest version. It does in fact work, but not in all cases. Rich.
Richard W.M. Jones wrote: Thanks. I'll try again when the new version is available. Cheers, Erik
Hi, I'm using febootstrap since some week and indeed, I'm able to reproduce the bug. However, I disagree with the severity serious as it doesn't renders package unusable. After the segfault and the febootstrap cache removal failure, the boostrap is functional. You can chroot and use it as expected (note: you should cleanup the cache yourself if you want more space). Anyway, a new upstream release will be appreciated. If you don't mind, I could upload a NMU if needed. Cheers, Fathi
Hi, I'm using febootstrap since some week and indeed, I'm able to reproduce the bug. However, I disagree with the severity serious as it doesn't renders package unusable. After the segfault and the febootstrap cache removal failure, the boostrap is functional. You can chroot and use it as expected (note: you should cleanup the cache yourself if you want more space). Anyway, a new upstream release will be appreciated. If you don't mind, I could upload a NMU if needed. Cheers, Fathi
Yes please. The version in Debian is ancient. Rich.
Yes please. The version in Debian is ancient. Rich.
Hi, I have uploaded febootstrap 2.7-1 to Debian. Unfortunately, this version still segfault: Complete! /usr/bin/fakeroot: line 1: 17946 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17947 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17948 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17949 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17950 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17951 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17952 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17953 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17954 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17955 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17956 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17957 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17958 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17959 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17960 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17961 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17962 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17963 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17964 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17965 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17966 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17967 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17968 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17969 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17970 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17971 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17972 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17973 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17974 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17975 Segmentation fault exit $RESULT febootstrap-run: problem parsing the command line arguments febootstrap-run: problem parsing the command line arguments /usr/bin/febootstrap: line 93: 17980 Segmentation fault febootstrap-run "$target" -- rm -rf /var/cache/yum/febootstrap-updates IMHO, the bug should be downgraded to important. As I said in a previous mail: the boostrap is functional. You can chroot and use it as expected. Cheers, Fathi
Hi, I have uploaded febootstrap 2.7-1 to Debian. Unfortunately, this version still segfault: Complete! /usr/bin/fakeroot: line 1: 17946 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17947 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17948 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17949 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17950 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17951 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17952 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17953 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17954 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17955 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17956 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17957 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17958 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17959 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17960 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17961 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17962 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17963 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17964 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17965 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17966 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17967 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17968 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17969 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17970 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17971 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17972 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17973 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17974 Segmentation fault exit $RESULT /usr/bin/fakeroot: line 1: 17975 Segmentation fault exit $RESULT febootstrap-run: problem parsing the command line arguments febootstrap-run: problem parsing the command line arguments /usr/bin/febootstrap: line 93: 17980 Segmentation fault febootstrap-run "$target" -- rm -rf /var/cache/yum/febootstrap-updates IMHO, the bug should be downgraded to important. As I said in a previous mail: the boostrap is functional. You can chroot and use it as expected. Cheers, Fathi
These segfaults are almost certainly caused by glibc in the chroot not matching glibc outside the chroot. In practice when we do this in Fedora we ensure that the glibc versions are identical. This in turn may be caused because we aren't setting the correct LD_LIBRARY_PATH(s) up inside febootstrap, so that we're in effect mixing internal parts of the two different glibc versions. I haven't really had time to look into this in any detail. Rich.
These segfaults are almost certainly caused by glibc in the chroot not matching glibc outside the chroot. In practice when we do this in Fedora we ensure that the glibc versions are identical. This in turn may be caused because we aren't setting the correct LD_LIBRARY_PATH(s) up inside febootstrap, so that we're in effect mixing internal parts of the two different glibc versions. I haven't really had time to look into this in any detail. Rich.
Hello Fabo, I don't recollect now but there were issues with the half baked chroot environment. That was the justification for the severity.
Hi, [...] Do you get those segfaults as well if you run febootstrap with --no-clean? If it is just the clean which fails, I agree. At least in the original logfile, I do not see any other segfaults. Michael
Hi, [...] Do you get those segfaults as well if you run febootstrap with --no-clean? If it is just the clean which fails, I agree. At least in the original logfile, I do not see any other segfaults. Michael
Complete! /usr/bin/febootstrap: line 93: 15649 Segmentation fault [ "$clean" = "yes" ] You know my opinion on the severity of the bug. Ritesh, could you describe the issues ? The segfaults seems related to yum cache cleanup and it doesn't seems a big deal. Cheers, Fathi
Complete! /usr/bin/febootstrap: line 93: 15649 Segmentation fault [ "$clean" = "yes" ] You know my opinion on the severity of the bug. Ritesh, could you describe the issues ? The segfaults seems related to yum cache cleanup and it doesn't seems a big deal. Cheers, Fathi
severity 576250 normal thanks That clears that up. If there indeed is an issue, please bump the severity back again. Michael
severity 576250 normal thanks That clears that up. If there indeed is an issue, please bump the severity back again. Michael
I can't recollect the actual issues now. If you think it is yum, shouldn't this bug then be re-assigned ? Ritesh