#6100: create bsd-style checksum files for CHECKSUM files
-----------------------------+------------------------
Reporter: till | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 21 Final | Component: koji
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
Create the files like https://getfedora.org/en/static/checksums/Fedora-
Workstation-21-x86_64-CHECKSUM
using "--tag", this adds an tag that shows which digest algorithm was
used:
{{{
$ sha256sum --tag /dev/null
SHA256 (/dev/null) =
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
}}}
This still allows to verify the files as usual.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6100>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#6112: Migrate koji to well-known CA certificate
-----------------------------+------------------------
Reporter: till | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 21 Final | Component: koji
Keywords: | Blocked By:
Blocking: 6111 |
-----------------------------+------------------------
Depends on:
https://fedorahosted.org/koji/ticket/312
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6112>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#6132: Create Fedora 22 Beta test compose (TC) and release candidate (RC)
----------------------------+------------------------
Reporter: adamwill | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 22 Beta | Component: koji
Keywords: | Blocked By:
Blocking: |
----------------------------+------------------------
It's Beta time! In fact, for the record, Beta TC1 was already composed by
releng without a request:
https://dl.fedoraproject.org/pub/alt/stage/22_Beta_TC1/
We're now requesting Beta TC2, as there's a new anaconda build we'll want
to test. So please compose Beta TC2 from current F22 stable plus:
*
[https://admin.fedoraproject.org/updates/FEDORA-2015-3846/anaconda-22.20.4-1…
,python-blivet-1.0.3-1.fc22 anaconda-22.20.4-1.fc22,python-
blivet-1.0.3-1.fc22]
Thanks!
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6132>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#6118: Please create a f22-gnome side tag
-----------------------------+------------------------
Reporter: kalev | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 22 Alpha | Component: koji
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
Hi,
Please create a new f22-gnome side tag and build target. We'll be building
GNOME 3.15.91 early next week and this would help ensure it doesn't cause
instabilities in F22 proper while we're preparing the update.
Thanks,
Kalev
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6118>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#6035: read cloud image size from spin-kickstarts git repo instead of hardcoding
in the script
-----------------------------+------------------------
Reporter: mattdm | Owner: rel-eng@…
Type: enhancement | Status: new
Milestone: Fedora 21 Final | Component: koji
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
Currently, the cloud image size is hardcoded at 3GB in
https://git.fedorahosted.org/cgit/releng/tree/scripts/build-cloud-
images#n39
This is apparently too small for current Atomic, and may actually be
_bigger_ than we want for Cloud Base. We want to fix the size problem in
Atomic, though, and don't want to keep hassling with tickets to rel-eng to
change the scripts.
Instead, please make this read from the spin-kickstarts file -- either a
config file in spin-kickstarts (e.g. fedora-cloud-atomic.ks.cfg) or from
the kickstart file itself (a special comment? i'm not sure that'll survive
the kickstart smashing).
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6035>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#6020: If Workstation tree is being dropped, please do same with Cloud
----------------------------+------------------------
Reporter: mattdm | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 21 Beta | Component: koji
Keywords: | Blocked By:
Blocking: |
----------------------------+------------------------
Based on yesterday's FESCo meeting, the plan is for Fedora Workstation
composes to be refactored such that there is not a separate Workstation
tree, but that top-level directory on the mirrors will just contain the
live ISOs in various architectures.
I still think just rm'ing the netinst images from those trees is the
lowest-impact workaround, but if this is what we are doing, Cloud should
match because the exact same situation applies.
So, please drop everything but the Images subdirectory from the Cloud
tree.
Thank you!
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6020>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#5984: Adding metadata to the Fedora Workstation Live CD
----------------------------+------------------------
Reporter: rhughes | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 21 Beta | Component: koji
Keywords: | Blocked By:
Blocking: |
----------------------------+------------------------
Hi Dennis, and other rel-eng dudes!
I've hit somewhat of a roadblock with this:
http://blogs.gnome.org/hughsie/2014/08/29/putting-packagekit-metadata-on-
the-fedora-livecd/
Basically, I need access to the post-mash (i.e. fedora, fedora-updates)
from the compose server. This allows us to put the old metadata on the
Fedora LiveCD so we don't have to wait the few minutes after install to be
able to search for and install new applications.
I totally agree we don't want unfettered internet access, or even access
to the mirror network, as I'm happy doing something like this in the
fedora-live-workstation.ks file:
%post --nochroot
DESTDIR=$INSTALL_ROOT $INSTALL_ROOT/usr/libexec/packagekit-direct refresh
--rewrite-baseurl fedora=http://some.local.ip.address/f21 --rewrite-
baseurl updates=http://some.local.ip.address/f21-updates
On the assumption that some.local.ip.address is available from inside the
LiveCD builder and gives us access to the mash'ed *metadata* only (I don't
need packages, and it can even be a few days old with no penalty).
The alternative is that I ship the fedora and updates metadata in the
PackageKit rpm file, which means doing a -0.01 day release of the RPM for
the Live media, which makes everything so very fragile.
Other ideas of course welcome. Thanks!
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5984>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#5894: git branches for SCL packages
-----------------------------+------------------------
Reporter: mmaslano | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 21 Alpha | Component: git
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
I would prefer SCL packages in branches of the main package (eg ruby). We
used the same approach in some internal projects and it worked well with
koji, composes, everything...
I suggest name of branches:
scl-f21
scl-f22
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5894>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#5805: add index.asc files for cloud images for virt-builder
----------------------------+------------------------
Reporter: mattdm | Owner: rel-eng@…
Type: enhancement | Status: new
Milestone: Fedora 20 Beta | Component: other
Keywords: | Blocked By:
Blocking: |
----------------------------+------------------------
Please add a GPG-signed 'index.asc' file to the Fedora 20 Images/
directory describing cloud images for virt-builder and other tools.
The format is documented at http://libguestfs.org/virt-builder.1.html
#creating-your-own-templates, and there's actually a Fedora example there.
Thanks!
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5805>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
#5883: New Cloud Images Process
-----------------------------+------------------------
Reporter: red | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 20 Final | Component: git
Keywords: | Blocked By:
Blocking: |
-----------------------------+------------------------
The cloud kickstart file has been moved to the spin-kickstarts Git by rel-
eng. When this happened, it seems there was no discussion regarding the
future process to create cloud images and the Spins Process doesn't seem
appropriate.
Therefore, the Cloud SIG would like to know what the intended process
should look like to give new contributors access to the cloud image
kickstart files and how to make sure new images (i.e. products) are
created from new kickstart files if necessary.
For now, mattdm (probably already has) and I need access from the Cloud
SIG but more will follow soon as we get ready to work on new products.
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5883>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project