-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Previous stage rootfs not found #166
Comments
I had the same problem. My fix was to rename the latest folder in the 'work' directory to the current date. So the issue was probably caused by the script searching for a folder with the current date. I'm not sure, wether it is an intended behavior. |
Unfortunately the same problem is described in #176 |
See my comment in #176 about adding a stage2a |
As a newb to the project, the find-rootfs-by-date mechanism definitely bites you when working with your own stages (to keep future base merges clean) and it takes you multiple days to get something done. (Right now it always takes me at least a couple of days, and several iterations, since I'm still learning. Dozens of ways to fix it, just voting for some option. Even something as simple as adding an optional env var in the config for "IMG_BUILD_DATE" or similar to tell copy_previous where to look for rootfs. If that's something that would be accepted I can contribute that. |
A stupid workaround I use is something like "IMG_DATE=2017-03-02", which should work. |
D'oh. Didn't even read that bit of `build` to notice that. :)
…On Wed, Oct 24, 2018 at 6:41 AM XECDesign ***@***.***> wrote:
A stupid workaround I use is soemthing like "IMG_DATE=2017-03-02", which
should work.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#166 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABIQYtQZKIdch0OJB6quIFtekxRvSObDks5uoFHigaJpZM4Swx0B>
.
|
@XECDesign just hit the same stopper. Problem is that the
gives:
It should be noted that the |
One cannot skip an intermediary stage.
A possible solution is to move the line
PREV_ROOTFS_DIR="${ROOTFS_DIR}"
inside the
if [ ! -f SKIP ]
statementThe text was updated successfully, but these errors were encountered: