[releng] Issue #7113: proposal to run bodhi updates pungi composes with
`--no-label`
by Dusty Mabe
dustymabe reported a new issue against the project: `releng` that you are following:
``
We have just started running bodhi updates via pungi (woo!!). One of the reasons the Atomic team has been helping drive this initiative is so that we can get better versioning of our ostrees output by fedora (via pungi).
When we started doing the runs we added a label to them of the form: `Update-20171025.1312`. Which translates into an ostree version of `27_Update.20171025.1312`. The atomic working group had previously got together and [decided](https://pagure.io/atomic-wg/issue/229) that a versioning scheme like `27.2017025.0` would be what we went with for better versioning for ostrees. This scheme was discussed with releng (including dennis) and also added as an RFE to pungi, which was implemented by @lsedlar in [PR](https://pagure.io/pungi/pull-request/592).
With the updates run we can get the desired version if we provide `--no-label` to pungi instead of actually giving it a label. This warrants the question: "what is the value of the label for an updates run?". Do we need it? What is it used for?
If we don't need it then I'd love to just use `--no-label`. If we do need it then we'll have to implement another smart versioning macro for ostrees in pungi.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7113
5 years, 5 months
[releng] Issue #7213: Tracker for packages tagged into atomic tags
by Dusty Mabe
dustymabe reported a new issue against the project: `releng` that you are following:
``
For background see: [new koji tags for atomic host](https://pagure.io/releng/issue/7100) ticket
This is a tracker for packages tagged into the`f27-atomic-host-installer` and `f27-atomic-host-overrides` tags.
Currently tagged packages:
[f27-atomic-host-installer]
-
[f27-atomic-host-overrides]
-
The description will get updated over time and the comments will serve as a changelog.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7213
5 years, 5 months
[releng] Issue #7208: Scratch builds from forked repos?
by Jose A. Rivera
jarrpa reported a new issue against the project: `releng` that you are following:
``
Hello!
I'm trying to do scratch builds from the following branch:
`https://src.fedoraproject.org/fork/jarrpa/container/glusterfs/branch/private-jarrpa`
With some help I managed to figure out the following command:
`koji-containerbuild --profile koji build --scratch f27-container-candidate git+https://src.fedoraproject.org/forks/jarrpa/container/glusterfs.git?#b...
But then I get the following error:
```
Created task: 23656542
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=23656542
Watching tasks (this may be safely interrupted)...
23656542 build (f27-container-candidate, /forks/jarrpa/container/glusterfs.git:bc698113adb8013df859a8c446b8547a5042fbdd): free
23656542 build (f27-container-candidate, /forks/jarrpa/container/glusterfs.git:bc698113adb8013df859a8c446b8547a5042fbdd): free -> FAILED: BuildError: src.fedoraproject.org:/forks/jarrpa/container/glusterfs.git is not in the list of allowed SCMs
0 free 0 open 0 done 1 failed
23656543 buildSRPMFromSCM (/forks/jarrpa/container/glusterfs.git:bc698113adb8013df859a8c446b8547a5042fbdd): FAILED: BuildError: src.fedoraproject.org:/forks/jarrpa/container/glusterfs.git is not in the list of allowed SCMs
23656542 build (f27-container-candidate, /forks/jarrpa/container/glusterfs.git:bc698113adb8013df859a8c446b8547a5042fbdd) failed
```
Is there any way to do scratch builds from forked repos? Otherwise, is there any way to create private/wip branched on the main repo that I can freely delete or do non-ff pushes to? I just want a repo I can use to do scratch builds using koji for development testing.
Thanks!
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7208
5 years, 5 months
[releng] Issue #7202: Add a machine readable product id to the installation
media buildstamp
by Martin Kolman
m4rtink reported a new issue against the project: `releng` that you are following:
``
The current situation
==================
At the moment the installation media buildstamp file has a field called "Product", which contains a human readable name of the product being installed.
The product name is used visually in multiple places in Anaconda (welcome screen, bootloader entries, etc.), but quite alarmingly, also as a kind of machine readable product identifier (base repo name, install class selection, etc.).
We have hit this issue yet again recently during an effort to merge back install classes for individual Fedora variants (Workstation, Server, etc.) to make install class maintenance easier & to make it possible to decommission the currently used per-variant product image packages.
Unfortunately we found out the "Product" field of every Fedora compose (rawhide/branched/GA) is, unlike on RHEL, always set to "Fedora", even if the compose & installation image itself is branded as Workstation/Server/etc. Also no other filed in the buildstamp has any information about about the variant at all.
Machine readable product id
========================
Rather than requesting the variant name to be appended to the Product field and possibly breaking all software that assumes it will always be just "Fedora" and nothing else, we would like to suggest a different solution, possibly fixing this issue once and for all.
Rather than misusing the old human readable field, let's add a new field designed to hold a separate machine readable product id. That way Anaconda and other tools will not have to parse a human readable filed to detect a variant, making things much more robust. Also adding and properly specifying a new field should be generally much safer than changing the content of an existing one.
Specifying the product id field name & value
=====================================
Looking at the current syntax, it looks like the field names are following a camel case convention (there is a BugURL and IsFinal field), so lets call the new field ProductId.
As for the machine readable product id value, I would suggest a few rules:
- no whitespace
- lower case ASCII letters, numbers and _ and - only
I suggest this because it's quite likely the machine readable product id might end up on the filesystem as a folder or file name, so the string should be safe for this use-case.
Example .buildstamp file with ProductId:
==================================
[Main]
Product=Fedora
ProductId=fedora_workstation
Version=Rawhide
IsFinal=False
UUID=201711300745.x86_64
[Compose]
Lorax=28.2-1
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7202
5 years, 5 months