@@ -193,25 +193,25 @@ write_archive_info() {
193
193
}
194
194
195
195
patch_osbuild () {
196
+ return # we have no patches right now
196
197
# # Add a few patches that either haven't made it into a release or
197
198
# # that will be obsoleted with other work that will be done soon.
198
199
199
200
# # To make it easier to apply patches we'll move around the osbuild
200
201
# # code on the system first:
201
- rmdir /usr/lib/osbuild/osbuild
202
- mv /usr/lib/python3.13/site-packages/osbuild /usr/lib/osbuild/
203
- mkdir /usr/lib/osbuild/tools
204
- mv /usr/bin/osbuild-mpp /usr/lib/osbuild/tools/
202
+ # rmdir /usr/lib/osbuild/osbuild
203
+ # mv /usr/lib/python3.13/site-packages/osbuild /usr/lib/osbuild/
204
+ # mkdir /usr/lib/osbuild/tools
205
+ # mv /usr/bin/osbuild-mpp /usr/lib/osbuild/tools/
205
206
206
207
# # Now all the software is under the /usr/lib/osbuild dir and we can patch
207
208
# cat foo.patch | patch -d /usr/lib/osbuild -p1
208
- patch -d /usr/lib/osbuild -p1 < /usr/lib/coreos-assembler/0001-live-artifacts-read-os-name-from-usr-lib-os-release.patch
209
-
209
+ #
210
210
# # And then move the files back; supermin appliance creation will need it back
211
211
# # in the places delivered by the RPM.
212
- mv /usr/lib/osbuild/tools/osbuild-mpp /usr/bin/osbuild-mpp
213
- mv /usr/lib/osbuild/osbuild /usr/lib/python3.13/site-packages/osbuild
214
- mkdir -p /usr/lib/osbuild/osbuild
212
+ # mv /usr/lib/osbuild/tools/osbuild-mpp /usr/bin/osbuild-mpp
213
+ # mv /usr/lib/osbuild/osbuild /usr/lib/python3.13/site-packages/osbuild
214
+ # mkdir -p /usr/lib/osbuild/osbuild
215
215
}
216
216
217
217
if [ $# -ne 0 ]; then
0 commit comments