[releng] Issue #7275: provide casync index and object storage files for
images on getfedora.org
by Basti Endres
sedrubal reported a new issue against the project: `releng` that you are following:
``
[casync](https://github.com/systemd/casync) is like a new and better rsync for directory trees, binary files and system images. It can speed up downloads if the user already has a similar image on his local machine.
For example if a user already has fedora 26 and he wants to download fedora 27 he can use fedora 26 as local seed and download only differences using casync. The same applies if he has fedora workstation and he wants to download fedora server.
It was great if you provide a `.caibx` index file for each image and a (global) `.castr` object storage on the fedora ftp mirrors.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7275
4 years, 6 months
[releng] Issue #7300: Deny push / Implement git hook for unescaped macro in
%changelog
by Igor Gnatenko
ignatenkobrain reported a new issue against the project: `releng` that you are following:
``
```python
#!/usr/bin/python3
import re
import sys
replace = False
out = []
with open(sys.argv[1], "r"):
for l in open(sys.argv[1], "r"):
out.append(l)
if l.startswith("%changelog"):
replace = True
continue
if not replace:
continue
if l.startswith("%"):
replace = False
continue
if l.startswith("*"):
# XXX: HACK
continue
out[-1] = re.sub(r"([^%])%([^% \n\d])", r"\1%%\2", l)
with open(sys.argv[1], "w") as f:
f.writelines(out)
```
This is something I've been using for automatic fix myself. I think we should either prohibit pushing this or have git-hook which would fix it automatically.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7300
4 years, 6 months
[releng] Issue #7878: Please make pm_request available (and working) in koji
by Nicolas Mailhot
nim reported a new issue against the project: `releng` that you are following:
``
So the Go (golang) ecosystem is a morass of fast-changing software, with massive code reuse, and components that get created/forked/renamed/deprecated at a fast pace. This is similar to other "modern" language ecosystems such as javascript.
This has led to mass-generation of Go spec files in Fedora from code analysis tools (and has prevented any form of official Fedora Go packaging guidelines).
However, generating specs outside rpm leads to specs that rot at a fast pace. No one really understands or audits the generated code, and as soon as you need to adapt it due to some upstream quirk you lose the ability to regenerate it cleanly.
And you can not ignore golang or javascript, the first is used by pretty much any container-oriented software, the other by pretty much anything that needs to present a web ui.
Therefore I've been trying for a year to put back the generation logic within rpm macros, so it's centralized, audited and and controlled by Fedora, and the generation logic is cleanly separated from human adaptations in the corresponding spec files.
For build requires, that means computing the code needs in %prep and getting mock to install the corresponding packages. The approach agreed on with FPC members and upstream mock was to use the pm_request mock plug-in and the corresponding logic written by the Java sig in javapackages.
https://github.com/rpm-software-management/mock/issues/160
Unfortunately the Java SIG code was too imbricated with Java specific things to be reusable so I ended up writing a separate mock pm request client
https://github.com/nim-nim/mock-install
https://copr.fedorainfracloud.org/coprs/nim/mock-install/
https://bugzilla.redhat.com/show_bug.cgi?id=1629371
And now I find out pm_request is not available in koji and copr (don't know it it was before and has been removed since, or if it was never enabled because the java sig built its stuff elsewhere)
Anyway:
1. please enable pm_request in koji
2. please make sure that it works
https://github.com/rpm-software-management/mock/issues/218
How to test:
1. take a mock install binary from
https://copr.fedorainfracloud.org/coprs/nim/mock-install/
2. use any spec you like that calls mock-install <package-name> from %prep
See also
https://pagure.io/koji/issue/1133
https://bugzilla.redhat.com/show_bug.cgi?id=1641187
https://bugzilla.redhat.com/show_bug.cgi?id=1641191
https://bugzilla.redhat.com/show_bug.cgi?id=1629371
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7878
4 years, 6 months
[releng] Issue #7848: fedpkg retire on modules doesn't remove them from
anywhere
by Igor Gnatenko
ignatenkobrain reported a new issue against the project: `releng` that you are following:
``
## Describe the issue
I've ran `fedpkg retire` on `stratis/master`, but module didn't disappear neither from f29 nor from rawhide.
It would be nice if it would be removed since it is unsupported ;)
## When do you need this? (YYYY/MM/DD)
Ideally before F29 final freeze because then it would be shipped to users.
## When is this no longer needed or useful? (YYYY/MM/DD)
I think it will be useful always.
## If we cannot complete your request, what is the impact?
Unsupported RPMs will be shipped to users.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7848
4 years, 6 months
[releng] Issue #7641: Create a Fedora Container release in bodhi stg
by Clement Verna
cverna reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
In order to test container updates in bodhi stg. We need to have a bodhi release available for f28 containers.
This will also requires koji tags to be created.
* When do you need this? (YYYY/MM/DD)
when possible
* When is this no longer needed or useful? (YYYY/MM/DD)
* If we cannot complete your request, what is the impact?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7641
4 years, 6 months
[releng] Issue #7827: Split modules-for-flatpaks into separate compose/repos
by Colin Walters
walters reported a new issue against the project: `releng` that you are following:
``
This should probably block Fedora 29 releases (at least classic systems), otherwise it's going to bite people:
```
# podman run --rm -ti registry.fedoraproject.org/fedora:29 bash
[root@2fc48260492d /]# yum module enable eog:master
...
Enabling module streams:
eog master
...
[root@2fc48260492d /]# yum -y install bubblewrap
...
Installed:
bubblewrap-0.3.0-2.module_2123+73a9ef6f.x86_64
....
[root@2fc48260492d /]# rpm -ql bubblewrap |grep /app
/app/bin/bwrap
...
```
This is just totally broken - this RPM should only be used to generate flatpaks *server side*.
Anyone who ends up installing flatpak-targeted app RPMs on the client side is highly likely to end up with a broken system.
https://github.com/projectatomic/rpm-ostree/issues/1542
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7827
4 years, 7 months
[releng] Issue #7922: Build Fedora 29 Python Classroom Lab
by Miro Hrončok
churchyard reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
The Fedora 29 Python Classroom Lab was not built (it FTBFS and I failed to notice that).
The FTBFS fix was pushed to rawhide and F29, rawhide builds, so should F29.
Please rebuild it, so we can "release" it.
The list should be:
https://fedoraproject.org/wiki/Changes/PythonClassroomLab#Scope
* When do you need this? (YYYY/MM/DD)
No real deadline, sooner the better.
* When is this no longer needed or useful? (YYYY/MM/DD)
Fedora 29 EOL.
* If we cannot complete your request, what is the impact?
No Fedora 29 Python Classroom Lab :(
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7922
4 years, 7 months