[releng] Issue #8294: coreos-pool and coreos-release koji tags request for
FCOS
by Sinny Kumari
sinnykumari reported a new issue against the project: `releng` that you are following:
``
** Describe the issue**
Fedora CoreOS will have [various streams](https://github.com/coreos/fedora-coreos-tracker/blob/master/stre.... All streams will use packages which are built in Fedora koji. Mechanical streams will use packages available in Fedora repos from tags f$(release), f$(release)-updates, f$(release)-updates-testing. Development and production streams will get built from packages available under koji tag `coreos-pool`. Packages which make it to production will also get tagged to `coreos-release` tag.
These tags will ensure that (1) packages are not automatically garbage collected (2) stream builds are reproducible (up to the GC retention policy we agree upon), and (3) packages are added to the pool (and thus into the production streams) in a controlled manner.
To build FCOS for different streams we need:
- coreos-pool and coreos-release koji tags created (include arches aarch64, ppc64le, x86_64)
- Permission to add packages to requested tags (ACLs for bgilbert, dustymabe, jlebon and sinnykumari, until we have bot setup done)
- Tag builds needs to be signed
- Generate dist repo for requested tags with option `--non-latest` to koji dist-repo (to perform build with desired NVRA)
**Question**
As we have streams like next-devel and testing-devel, packages will be from multiple Fedora releases in coreos-pool and coreos-release tags. Since we will be using signed packages, does koji dist-repo allows to specify multiple keys for generating dist repos? This question is because, in [infra ansible tag2distrepo](https://infrastructure.fedoraproject.org/cgit/ansible.git/t..., so far single key has been used.
** When do you need this? (YYYY/MM/DD) **
ASAP
** When is this no longer needed or useful? (YYYY/MM/DD) **
Always needed
** If we cannot complete your request, what is the impact? **
we won't be able to build FCOS for different streams
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8294
4 years, 1 month
[releng] Issue #8275: Fedora 31 FTBFS and all Fails to install tracker
bugzillas
by Miro Hrončok
churchyard reported a new issue against the project: `releng` that you are following:
``
According to the [new policy about FTBFS and FTI (Fails to install) packages](https://pagure.io/fesco/issue/2109), please create the following new tracker bugzillas:
* Fedora 31 Fails to build from source - F31FTBFS
* Fedora 31 Fails to install - F31FailsToInstall
* Fedora 30 Fails to install - F30FailsToInstall
* Fedora 29 Fails to install - F29FailsToInstall
* Fedora 28 Fails to install - F28FailsToInstall
About the aliases: I suggested F31FTI, but @till [had a good point](https://pagure.io/fesco/issue/2109#comment-561765) that F30_fails_to_install (or similar) might be easier for others. I ultimately leave that decision to releng, but I guess we usually stick to CamelCase, so I went with F30FailsToInstall
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8275
4 years, 2 months
[releng] Issue #8143: 12 packages have no git directory on pkgs02,
but are active in pdc.
by Kevin Fenzi
kevin reported a new issue against the project: `releng` that you are following:
``
These packages do not have git repos on pkgs02, but are active in pdc:
```
ERROR: /srv/git/repositories/rpms/R-gnomeGUI.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/actdiag.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/compat-ImageMagick6.9.3.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/gnome-cpufreq-applet.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/kf5-textwidgets.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/nwdiag.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/python-elementtree.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/repsurgeon.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/seqdiag.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/tetex-beamer.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/tetex-pgf.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/tetex-xcolor.git does not appear to be a directory
```
so, likely they should be marked eol in pdc and blocked in koji?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8143
4 years, 2 months