Univention Bugzilla – Bug 42483
Initialize updater/identify from ISO image metadata
Last modified: 2016-10-13 11:44:14 CEST
It should be possible to initialize the updater/identity variable through ISO image metadata. That allows us to identify images without re-building an image. The command line tool exiv2 can change the metadata for example.
(In reply to Stefan Gohmann from comment #0) > It should be possible to initialize the updater/identity variable through > ISO image metadata. That allows us to identify images without re-building an > image. It's called "ISO-9660 Primary Volume Descriptor", described in <http://wiki.osdev.org/ISO_9660#The_Primary_Volume_Descriptor>. You can use 'isoinfo -d' to show part of the information, but for example the time stamps are missing: | $ isoinfo -f -i /var/univention/buildsystem2/isotests/ucs_4.1-3-latest-amd64.iso -d | System id: | Volume id: UCS 4.1-3 amd64 1 | Volume set id: | Publisher id: UNIVENTION GMBH | Data preparer id: XORRISO-1.2.2 2012.04.02.133001, LIBISOBURN-1.2.2, LIBISOFS-1.2.2, LIBBURN-1.2.2 | Application id: UNIVENTION CORPORATE SERVER | Copyright File id: | Abstract File id: | Bibliographic File id: Basically you can use "dd" to poke the right bytes, as the structure is at a fixed position inside the ISO file. > The command line tool exiv2 can change the metadata for example. exiv2 is for JPEG images, NOT for ISO-9660 files!
DVD with test errata: ucs_4.1-3-20161010-191822-dvd-amd64.iso univention-system-setup (9.0.4-48) Advisory: univention-system-setup.yaml
OK: updater/identify is "UCS ($METADATA)" if iso metadata is set. OK: does not get overwritten by updater appliance hook, if UCRv is set during installer OK: DVD installation OK: usb stick installation OK: yaml OK: Changes merged to ucs 4.2
<http://errata.software-univention.de/ucs/4.1/292.html>