On Tue, Nov 18, 2014 at 08:46:54AM -0800, Brian C. Lane wrote:
> This kind of information doesn't belong in livecd-creator. You can pass
> it a volume id. Koji knows (or should know) what it is building, it
> should construct the correct name and pass it. The default in
> livecd-creator is just a default and is used to match up the isolinux
> config with the image for booting, which is working just fine.
> Also, can we stop with the quick fixes? They live forever, so let's do
> this the right way.
Agree in general, but a) sometimes, that's where we are, and b) as I
understand it, the F22 plan is to use imagefactory and/or
livemedia-creator rather than livecd creator, so it really is
Fedora Project Leader
Fixing buildsys CC
On 11/15/2014 01:29 PM, Cole Robinson wrote:
> Hi all,
> The ISO volume ID for the Fedora 21 workstation livecd is
> 'Fedora-Live-Workstation-x86_64-2', which doesn't actually say 21 in it, and
> libosinfo can't use it to detect the fedora version for boxes/virt-manager.
> Koji is responsible for generating the volume ID, and there's a bug filed:
> I also sent a (untested) koji patch to buildsys list:
> However neither have received a response, so I'm reaching out here.
> If this isn't fixed before F21 GA, we are stuck with the crappy volume ID
> forever and tools that are depending on it are in a tough spot. Is there any
> process to escalate this and get the fix deployed to infrastructure? (FWIW
> I've just proposed the bug as a freeze exception, but presumably it will take
> more coordination that that)
Hi. Attached are a couple of enhancements to rpkg. The first adds a
--runas option. This allows you to run Koji commands as a different
user, if the Koji hub has been configured to allow you to do so. This
is useful for automation that launches builds on behalf of other users.
The other patch fixes support for password authentication (it has
never worked correctly) and cleans up Koji session creation, so all
relevant config options are passed through to the new session. This
should improve compatibility between the Koji cli and rpkg. Let me know
if there are any questions.
Sites could specify a path in the user's home directory for the
kojiconfig attribute (e.g. ~/.koji/config-cbs). This is a one-line
change to run os.expanduser() on that path so that file doesn't get
skipped when loading the koji session attributes.
bstinson(a)ksu.edu | IRC: bstinson | Bitbucket/Twitter: bstinsonmhk