How do I find out which FAI classes were used to build a
certain image? Reply-To:
Hi,
to reproduce a bug, I would like to build a local grml image as similiar as possible to grml64-full.2017.05.iso.
How do I find out which FAI classes were used to build the image to give the exact same list to grml-live's -c option? Is that information inside the ISO and/or accessible from the booted grml?
Greetings Marc
* Marc Haber [Thu Aug 31, 2017 at 03:56:48PM +0200]:
to reproduce a bug, I would like to build a local grml image as similiar as possible to grml64-full.2017.05.iso.
How do I find out which FAI classes were used to build the image to give the exact same list to grml-live's -c option? Is that information inside the ISO and/or accessible from the booted grml?
The best we currently have are the build logs, e.g. https://jenkins.grml.org/job/grml64-full_Release/32/console has the details for the grml64-full.2017.05 ISO. So it was generated using the following classes:
DEBORPHAN,GRMLBASE,GRML_FULL,RELEASE,AMD64,IGNORE,SNAPSHOT
This raises an interesting issue, it might be nice to include such build information inside the ISO itself by default.
What about something like:
% jo build_date="$(TZ=UTC date +%s)" grml_live_classes=DEBORPHAN,GRMLBASE,GRML_FULL,RELEASE,AMD64,IGNORE,SNAPSHOT grml_live_version=0.30.2 build_tool=grml-live debian_release=stretch grml_live_options="-F -V -A" architecture=amd64 grml_version=build2065 debian_release=autobuild-build2065 grml_name=grml64-full_sid build_host="jenkins.grml.org" | jq -S '.' { "architecture": "amd64", "build_date": 1504206859, "build_host": "jenkins.grml.org", "build_tool": "grml-live", "debian_release": "autobuild-build2065", "grml_live_classes": "DEBORPHAN,GRMLBASE,GRML_FULL,RELEASE,AMD64,IGNORE,SNAPSHOT", "grml_live_options": "-F -V -A", "grml_live_version": "0.30.2", "grml_name": "grml64-full_sid", "grml_version": "build2065" }
put into /GRML/buildinfo.json or so on the ISO?
regards, -mika-
On Thu, Aug 31, 2017 at 09:16:38PM +0200, Michael Prokop wrote:
- Marc Haber [Thu Aug 31, 2017 at 03:56:48PM +0200]:
to reproduce a bug, I would like to build a local grml image as similiar as possible to grml64-full.2017.05.iso.
How do I find out which FAI classes were used to build the image to give the exact same list to grml-live's -c option? Is that information inside the ISO and/or accessible from the booted grml?
The best we currently have are the build logs, e.g. https://jenkins.grml.org/job/grml64-full_Release/32/console has the details for the grml64-full.2017.05 ISO. So it was generated using the following classes:
DEBORPHAN,GRMLBASE,GRML_FULL,RELEASE,AMD64,IGNORE,SNAPSHOT
Thanks, that will help.
This raises an interesting issue, it might be nice to include such build information inside the ISO itself by default.
Yes, I opened grml-live #44 about that.
What about something like:
% jo build_date="$(TZ=UTC date +%s)" grml_live_classes=DEBORPHAN,GRMLBASE,GRML_FULL,RELEASE,AMD64,IGNORE,SNAPSHOT grml_live_version=0.30.2 build_tool=grml-live debian_release=stretch grml_live_options="-F -V -A" architecture=amd64 grml_version=build2065 debian_release=autobuild-build2065 grml_name=grml64-full_sid build_host="jenkins.grml.org" | jq -S '.' { "architecture": "amd64", "build_date": 1504206859, "build_host": "jenkins.grml.org", "build_tool": "grml-live", "debian_release": "autobuild-build2065", "grml_live_classes": "DEBORPHAN,GRMLBASE,GRML_FULL,RELEASE,AMD64,IGNORE,SNAPSHOT", "grml_live_options": "-F -V -A", "grml_live_version": "0.30.2", "grml_name": "grml64-full_sid", "grml_version": "build2065" }
put into /GRML/buildinfo.json or so on the ISO?
Looks nearly perfect. A personal preference might be that I'd prefer a human-readable date as build_data and the snapshot, if it's important in the first place, the epoch timestamp in another variable.
And probably the suite is missing.
Greetings Marc
* Marc Haber [Sun Sep 03, 2017 at 06:37:42PM +0200]:
On Thu, Aug 31, 2017 at 09:16:38PM +0200, Michael Prokop wrote:
What about something like:
% jo build_date="$(TZ=UTC date +%s)" grml_live_classes=DEBORPHAN,GRMLBASE,GRML_FULL,RELEASE,AMD64,IGNORE,SNAPSHOT grml_live_version=0.30.2 build_tool=grml-live debian_release=stretch grml_live_options="-F -V -A" architecture=amd64 grml_version=build2065 debian_release=autobuild-build2065 grml_name=grml64-full_sid build_host="jenkins.grml.org" | jq -S '.' { "architecture": "amd64", "build_date": 1504206859, "build_host": "jenkins.grml.org", "build_tool": "grml-live", "debian_release": "autobuild-build2065", "grml_live_classes": "DEBORPHAN,GRMLBASE,GRML_FULL,RELEASE,AMD64,IGNORE,SNAPSHOT", "grml_live_options": "-F -V -A", "grml_live_version": "0.30.2", "grml_name": "grml64-full_sid", "grml_version": "build2065" }
put into /GRML/buildinfo.json or so on the ISO?
Looks nearly perfect. A personal preference might be that I'd prefer a human-readable date as build_data and the snapshot, if it's important in the first place, the epoch timestamp in another variable.
What do you mean with "snapshot" here? Can you please provide a full example of what you'd like to have?
And probably the suite is missing.
I think I just used the wrong argument for debian_release in my example. :)
regards, -mika-
On Wed, Sep 06, 2017 at 09:06:33AM +0200, Michael Prokop wrote:
- Marc Haber [Sun Sep 03, 2017 at 06:37:42PM +0200]:
On Thu, Aug 31, 2017 at 09:16:38PM +0200, Michael Prokop wrote:
What about something like:
% jo build_date="$(TZ=UTC date +%s)" grml_live_classes=DEBORPHAN,GRMLBASE,GRML_FULL,RELEASE,AMD64,IGNORE,SNAPSHOT grml_live_version=0.30.2 build_tool=grml-live debian_release=stretch grml_live_options="-F -V -A" architecture=amd64 grml_version=build2065 debian_release=autobuild-build2065 grml_name=grml64-full_sid build_host="jenkins.grml.org" | jq -S '.' { "architecture": "amd64", "build_date": 1504206859, "build_host": "jenkins.grml.org", "build_tool": "grml-live", "debian_release": "autobuild-build2065", "grml_live_classes": "DEBORPHAN,GRMLBASE,GRML_FULL,RELEASE,AMD64,IGNORE,SNAPSHOT", "grml_live_options": "-F -V -A", "grml_live_version": "0.30.2", "grml_name": "grml64-full_sid", "grml_version": "build2065" }
put into /GRML/buildinfo.json or so on the ISO?
Looks nearly perfect. A personal preference might be that I'd prefer a human-readable date as build_data and the snapshot, if it's important in the first place, the epoch timestamp in another variable.
What do you mean with "snapshot" here? Can you please provide a full example of what you'd like to have?
I must have been drunk[1] when I wrote that, i mean "build_date", and strike "and the snapshot" for the sentence to make sense.
And probably the suite is missing.
I think I just used the wrong argument for debian_release in my example. :)
Hehe ;-)
Greetings Marc
[1] or the Editor used wrong, I am currently migrating to vim after using an emacs clone for 20 years, with significant collateral damage
participants (2)
-
Marc Haber -
Michael Prokop