-
Notifications
You must be signed in to change notification settings - Fork 32
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
Kiwi export not comaptible with SUSEStudio #1301
Comments
Hi, thx for the report. The reason for this is that SUSE Studio expects a But even when I move everything to a source directory and compress it with tar.gz the import fails with "Invalid sequence in interleave Invalid sequence in interleave Element image failed to validate content". I will look into it. |
The issue seems to be related to Studio, I will forward the issue. |
We adapted the Studio import like stated in this Fate: https://fate.suse.com/318388 |
Sorry, this page is not public to openSUSE users, and it is not on openFATE. |
The kiwi configuration exchange format is:
But I have tried compressing our export and uploading it to Susestudio and had an issue which is currently looked at. I will let you know as soon as there are some news. |
Hey, to give you a heads up, we are still working on this. We have improved our Kiwi export and there is already a Studio development version which can import at least the packages. |
Is this still an issue? We will support the Kiwi standard export format which should resolve any remaining problems. #2190 |
Yes, still an issue. KIWI from studio behaves different than on OBS than on local build. Machinery I haven't tried. But just taking the sources from lets say Studio and drop it to OBS does not work.... |
Morning all,
I heard on the oSC 2015 about machinery and its ability to create a Kiwi-Export, which can be used as the basis for an Studio-Build. However, import to Studio fails with the error message:
could not find 'Source' directory
Not sure where the source of the problem is, but in the Studio Forum nobody could help.
The text was updated successfully, but these errors were encountered: