[releng] Issue #8506: Fedora 32 side tag for Python 3.8
by Miro Hrončok
churchyard reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
I'd kindly like to request a **Fedora 32** side tag in koji for Python 3.8 rebuilds. See https://pagure.io/releng/issue/8092
Preferred tag/target name: f32-python
Parent: f32-build
```
$ koji add-tag f32-python --parent=f32-build --arches='armv7hl i686 x86_64 aarch64 ppc64 ppc64le s390x'
$ koji add-target f32-python f32-python
```
* When do you need this? (2019/08/14) - right after branching
* When is this no longer needed or useful? (2020/01/29)
* If we cannot complete your request, what is the impact?
We would not be able to rebuild Python 3.8 for Fedora 32.
Thanks.
Se also https://pagure.io/releng/issue/8320
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8506
4 years, 8 months
[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, 8 months
[releng] Issue #8435: Side tag for Golang new macros
by Robert-André Mauchin
eclipseo reported a new issue against the project: `releng` that you are following:
``
I'd kindly like to request a Fedora 31 side tag in koji for Golang rebuilds. See https://fedoraproject.org/wiki/Changes/Adopt_new_Go_Packaging_Guidelines
* For which release?
F31
* Name of the side tag? (Generally fxx-pkg)
Preferred tag/target name: f31-go or f31-golang
Parent: f31-build
$ koji add-tag f31-go --parent=f31-go --arches='armv7hl i686 x86_64 aarch64 ppc64 ppc64le s390x'
$ koji add-target f31-go f31-go
* Number of builds that are expected in the side tag?
Around 1120. Exhaustive list: https://copr.fedorainfracloud.org/coprs/eclipseo/golang-ng/
* When do you need this?
This week would be good.
* How long do you need the side tag?
Until 2019-07-24
* If we cannot complete your request, what is the impact?
We would not be able to rebuild the Golang stack with the new macros.
* Any extra information?
I never used a side tag before so I'd also like some pointer or howto to properly make use of it.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8435
4 years, 8 months