[releng] Issue #6784: Remove all modular targets
by Jan Kaluža
jkaluza reported a new issue against the project: `releng` that you are following:
``
I have decided it is time to stop generating module-* targets, because they seem to block kojira for everyone. Please remove all of them. We will deploy new MBS which will delete the old targets itself as a temporary workaround and will work on target-free module builds.
List of current modular targets:
```
module-003655f6e917d46d
module-003655f6e917d46d-repo
module-01314d11adc2edd8
module-01314d11adc2edd8-repo
module-02edadb91222d988
module-02edadb91222d988-repo
module-0350cd630e51dcd8
module-0350cd630e51dcd8-repo
module-038aa19b4479899a
module-038aa19b4479899a-repo
module-04ba8aadb85a3b51
module-04ba8aadb85a3b51-repo
module-08a8a83ad4085d77
module-08a8a83ad4085d77-repo
module-12063ee83fe7c429
module-12063ee83fe7c429-repo
module-13844958cede3dd4
module-13844958cede3dd4-repo
module-13fc84733fc24a83
module-13fc84733fc24a83-repo
module-1541a1e6551d698e
module-1541a1e6551d698e-repo
module-155db5d0318508a6
module-155db5d0318508a6-repo
module-1882447d52d24b1d
module-1882447d52d24b1d-repo
module-1d46c435c4aef954
module-1d46c435c4aef954-repo
module-2118aef6f7c86cbb
module-2118aef6f7c86cbb-repo
module-2477d6fe25d4e7e6
module-2477d6fe25d4e7e6-repo
module-26d1d0e8e127dc9b
module-26d1d0e8e127dc9b-repo
module-27a562bdf010e715
module-27a562bdf010e715-repo
module-2a19f989aac43f63
module-2a19f989aac43f63-repo
module-2d9a181196718cb5
module-2d9a181196718cb5-repo
module-30a4ce43463f9699
module-30a4ce43463f9699-repo
module-339d95008d28791f
module-339d95008d28791f-repo
module-36520305ab338610
module-36520305ab338610-repo
module-40210d5641c092ac
module-40210d5641c092ac-repo
module-442783f2d9863ee7
module-442783f2d9863ee7-repo
module-445c3a105c96d318
module-445c3a105c96d318-repo
module-463a9bb84bd6e612
module-463a9bb84bd6e612-repo
module-477f222eeca25183
module-477f222eeca25183-repo
module-49b6a32c81ed403f
module-49b6a32c81ed403f-repo
module-51836d81a4b4e352
module-51836d81a4b4e352-repo
module-5349e6f27dd56498
module-5349e6f27dd56498-repo
module-540183c0d82d738c
module-540183c0d82d738c-repo
module-55cce33f0564d90f
module-55cce33f0564d90f-repo
module-56749e46e190eb78
module-56749e46e190eb78-repo
module-5817566b23a52976
module-5817566b23a52976-repo
module-59eb54adf38547b0
module-59eb54adf38547b0-repo
module-5a0a295c9673c2a1
module-5a0a295c9673c2a1-repo
module-5a3e7d9106e8caf6
module-5a3e7d9106e8caf6-repo
module-5ccf9229944793fc
module-5ccf9229944793fc-repo
module-5d197e359fd3ea1d
module-5d197e359fd3ea1d-repo
module-5ec2482a0578dd84
module-5ec2482a0578dd84-repo
module-644e28a84a5e07ea
module-644e28a84a5e07ea-repo
module-650750374f6f664a
module-650750374f6f664a-repo
module-6a7ea52fa6b4952b
module-6a7ea52fa6b4952b-repo
module-6bbec18e68532c1d
module-6bbec18e68532c1d-repo
module-711f2547ffcd33ca
module-711f2547ffcd33ca-repo
module-7571a4830b16a549
module-7571a4830b16a549-repo
module-789f6b1cacf90faf
module-789f6b1cacf90faf-repo
module-7dd1649ba5398d7e
module-7dd1649ba5398d7e-repo
module-7e01f122edf0cdba
module-7e01f122edf0cdba-repo
module-897eb46f0686f084
module-897eb46f0686f084-repo
module-8bd3baaaacf62f31
module-8bd3baaaacf62f31-repo
module-8bd6de8fb095683f
module-8bd6de8fb095683f-repo
module-8d32d6e2f476fd85
module-8d32d6e2f476fd85-repo
module-9037e4d97333eb6b
module-9037e4d97333eb6b-repo
module-a01042a9a6030e84
module-a01042a9a6030e84-repo
module-a5e0e53d82b96134
module-a5e0e53d82b96134-repo
module-a61012b0b920a6ac
module-a61012b0b920a6ac-repo
module-ae0742b768dc7582
module-ae0742b768dc7582-repo
module-b73c43a36a16878c
module-b73c43a36a16878c-repo
module-b9fb731f5a6e39bb
module-b9fb731f5a6e39bb-repo
module-base-runtime-master-20170315150159
module-base-runtime-master-20170315150159-repo
module-bd74f0614604ab95
module-bd74f0614604ab95-repo
module-c5b45d25f0b8991b
module-c5b45d25f0b8991b-repo
module-c633663f7262c802
module-c633663f7262c802-repo
module-ca722b8e5d8d534a
module-ca722b8e5d8d534a-repo
module-cc0ad6f057e9d246
module-cc0ad6f057e9d246-repo
module-d0c17f83179972c2
module-d0c17f83179972c2-repo
module-d3117eb86595d4ed
module-d3117eb86595d4ed-repo
module-d335f63e21c55c9f
module-d335f63e21c55c9f-repo
module-d6f9903bb0ade6d8
module-d6f9903bb0ade6d8-repo
module-da0b9d8e3505401d
module-da0b9d8e3505401d-repo
module-dd8e3681a1241519
module-dd8e3681a1241519-repo
module-deab6c376e7c6032
module-deab6c376e7c6032-repo
module-debugging-tools-master-20170405115403
module-debugging-tools-master-20170405115403-repo
module-e4722fec27030fba
module-e4722fec27030fba-repo
module-e67c1e728d6aa7be
module-e67c1e728d6aa7be-repo
module-ec3ca856b46ad31d
module-ec3ca856b46ad31d-repo
module-f0f7e44f3c6cccab
module-f0f7e44f3c6cccab-repo
module-f3990dd9e9002418
module-f3990dd9e9002418-repo
module-f95d27190d259bae
module-f95d27190d259bae-repo
module-fa0f971c0b6df0ff
module-fa0f971c0b6df0ff-repo
module-fb5b7ce091a46d7f
module-fb5b7ce091a46d7f-repo
module-fcd86adc7a9c7e0a
module-fcd86adc7a9c7e0a-repo
module-ff792745ded5256d
module-ff792745ded5256d-repo
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6784
6 years, 11 months
[release] pungi 4.1.15,
by Lubomír Sedlář
Hello everyone,
a new version of Pungi is available! The 4.1.14 build is ready to be
used. There are updates for F26 and F25 in Bodhi waiting to be pushed
to updates-testing.
Biggest changes are:
* More debug information is printed when depsolving. We now store the
exact requires which cause dependencies to be pulled in. The process
is also made more deterministic by processing dependencies sorted.
* A lock is used when koji runroot command is executed to avoid race
conditions with kerberos authentication.
* Support for SHA512 is added into most places (everywhere except for
inside `.treeinfo`).
* The yum.comps python module is no longer used and is replaced with
libcomps (for Python 3 compatibility).
* Automatically generating versions for artifacts is made more
explicit. It now allows generating version for use with ostree.
* Configuration for images is simplified: all repos for an image can
be configured with a single option. A pull request for configuration
is provided at [0].
Better error reporting:
* when config mentions non-existing git branch
* when variant has no input packages or groups
* when variant includes non-existing comps group
Fixes for modular compose:
* compatible arches are expanded when gathering packages from modules
* avoid race condition where multiple threads accessed the same
temporary directory
* write a list of RPMs into modulemd metadata
[0] https://pagure.io/pungi-fedora/pull-request/224
Refer to the documentation [1] for details on what configuration
options are available.
[1] https://docs.pagure.org/pungi/index.html
If you encounter problems or need general help, stop by #fedora-releng
IRC channel or file issues in Pagure.
Happy composing!
Lubomír
6 years, 11 months
Knowledge Query: Release End-of-Life
by Robert Marshall
I am updating the End-of-Life SOP documentation.
The following are open questions on the Work-in-Progress (WIP) pull request.
For context, check the PR here and look for TODO tags:
https://pagure.io/releng/pull-request/6734
- How do we toggle the flag in PKGDB to make builds EOL?
- Are there any "Docs" tasks required for End-of-Life?
- Cloud Tasks
- What do we need to do with 'fedimg'
- Cloud Images are apparently off limits for archiving, do we have any
business logic or rules that we could present to eventually remove some?
- "Remove Unsupported EC2 Images" links to the which which just points to
the Fedora Cloud page. Where do we need to remove these images from?
- Archiving From/To Locations
- does the "Archiving the Release" section make sense in terms of locations
re-hardlinking from A to B?
- Is anything missing from this list of items to archive?
- Yes/No - Torrents are just deleted at End-of-Life; seemed legit to me.
- Verifications
- How much verification of archival is enough?
- Is there any work that is outside rel-eng that should be documented?
- Consider Before Running
- what is the bullet point 'ot' in this context?
- Esoteric Questions
- Is anything missing here that would be a requirement of moving a release
into End-of-Life?
Thank you,
--Rob
Robert Marshall
Software Engineer , RHCSA
Red Hat
rmarshall(a)redhat.com
6 years, 12 months
[releng] Issue #6767: Creating a Pagure repo/project for "PkgDB related
tickets"
by Matt Prahl
mprahl reported a new issue against the project: `releng` that you are following:
``
Hello,
As you may have read from the following thread, Factory 2.0 and the Fedora community is in the process of replacing PkgDB: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedora...
Part of PkgDB's functionality is its ticketing queue for new package requests, branch requests, and unretiring packages. It was decided that we would use Pagure tickets to replace this functionality. In this scenario, users would use a CLI tool that formatted requests and posted JSON in the ticket body in Pagure. Tooling would then process those tickets.
This ticket is not about how or why we are doing this, but simply, what would you like the name of this repo to be? Once you decide that, please create it. If we don't get a consensus on this, we will just create something like https://pagure.io/repo-requests/.
Thank you.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6767
7 years
