Skip to content
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

Closed
coogor opened this issue Sep 7, 2015 · 8 comments
Closed

Kiwi export not comaptible with SUSEStudio #1301

coogor opened this issue Sep 7, 2015 · 8 comments

Comments

@coogor
Copy link

coogor commented Sep 7, 2015

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.

@thardeck
Copy link
Member

Hi, thx for the report. The reason for this is that SUSE Studio expects a source directory in the tarball, where the configuration and the root directory is stored inside.

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.

@thardeck
Copy link
Member

The issue seems to be related to Studio, I will forward the issue.

@ChrisBr
Copy link

ChrisBr commented Mar 4, 2016

We adapted the Studio import like stated in this Fate: https://fate.suse.com/318388
Not sure how the machinery export looks like, however, we stick now to structure stated in this fate...

@coogor
Copy link
Author

coogor commented Mar 5, 2016

Sorry, this page is not public to openSUSE users, and it is not on openFATE.
Did you align both projects somehow?

@thardeck
Copy link
Member

thardeck commented Mar 7, 2016

The kiwi configuration exchange format is:

  • a tar ball compressed with xz.
  • it contains a "config.xml" at top level. This is a required file.
  • further optional files, like image.sh, config.sh and alike are packaged as well on top level
  • all layered files are inside of the directory called "root/" inside of this archive
  • the file name suffix of this archive should be .kiwi.txz

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.

@thardeck
Copy link
Member

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.

@cornelius
Copy link
Contributor

Is this still an issue?

We will support the Kiwi standard export format which should resolve any remaining problems. #2190

@coogor
Copy link
Author

coogor commented Oct 28, 2016

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....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants