feat: Include the EIB elemental fix temporary for 3.4 #319
Reference in New Issue
Block a user
Delete Branch "eib-elemental-fix-3.4"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Backport of #323
Temporarily carry https://github.com/suse-edge/edge-image-builder/pull/810 until it's included in an EIB release
@@ -0,0 +1,24 @@From 643bcd634310909d01e1365cf5f3aaac98f25414 Mon Sep 17 00:00:00 2001From: e-minguez <e.minguez@gmail.com>Should we move this to @suse.com?
Done
I think we want to update the EIB image tag as well
@@ -19,3 +19,3 @@Name: edge-image-builderVersion: 1.3.0Release: 0Release: 1This field is automatically managed by OBS on source change, so please keep it to 0 to make it less confusing
ACK
I'm confused now :D Do you want me to bump it to 1.3.0-something? IIRC the BuildTag is 1.3.0-%RELEASE%, shall I just change %RELEASE% by something else?
Also, do you happen to know why it is failing on the patch process? I basically did the same I did before for python-pyhelm3 here https://src.opensuse.org/suse-edge/Factory/src/branch/main/python-pyhelm3/0001-icon-metadata-allow-fileurl.patch but I'm not sure about the directory structure here (I'm confused by the vendor.tar.gz I guess)
It will get published as
1.3.0-somethingas expected, but it will also override the1.3.0tag (not sure we want that).I think you got confused in the file path in the patch, in python there is almost always a first level directory that is the name of the package (as in your example with
pyhelm3), not here, so your path shouldn't include theedge-image-builder-1.3.0partI don't think we want to override that tag. What should I do then? Keep 1.3.0 and 0 or override them somehow?
I think I send it without that folder, let me send it again to see the error message again.
Yep, it failed as:
Any ideas on why? or how can I replicate it locally? where is the vendor.tar.gz coming from? and the eib-1.3.0.tar file? Upstream releases are .tar.gz 😅
They come from the source services, you should be able to replicate by doing an
osc buildin the directory, you may have to indicate some metadata in.oscdirectory so that it knows the dependencies and so on, so here is what those should look like:But from a quick look, in the
%prepsection, the%autosetupmay just miss a-p1argumentI agree I think we're missing the
-p1- I pushed #321 to prove but it seems OBS is downSo I checked by downloading the srpm from https://build.opensuse.org/projects/isv:SUSE:Edge:3.4/packages/edge-image-builder/repositories/standard/binaries
Then you can use
rpm2cpioto extract the tarball, unpack it and patch which shows the-p1works:Sent the
-p1addition. Thanks folks!Bumped version to 1.3.0.1 to avoid overriding the current 1.3.0 one.