[releng] Issue #7763: define and implement retention policy for nightly
composes
by Dan Horák
sharkcz reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
Right now we have only last 14 days of the nightly composes. Which makes it impossible to compare current compose with an old one to see what changed (mainly functionally). The polocy could be time based (like keep 1 compose per week for 4 weeks preceding the 14 days, then keep 1 per month, until previous GA). Or it can be based on the openqa testing and keep composes "nominated for further testing". Or something else.
One of the reason for this request is https://bugzilla.redhat.com/show_bug.cgi?id=1623547 where I'm almost sure I had a F-29 nightly compose behaving sanely on s390x in the past, but have nothing I could compare with the current state.
* When do you need this? (YYYY/MM/DD)
soon
* When is this no longer needed or useful? (YYYY/MM/DD)
never
* If we cannot complete your request, what is the impact?
Difficult to find out what changed (functionally) in the composes as the previous compose is the GA compose of the last release. AFAIK it's almost impossible to recreate an old compose from a given date on demand.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7763
4 years, 6 months
[releng] Issue #7802: Several EPEL7 package conflicts with RHEL/CentOS 7.5
by Eli Young
elyscape reported a new issue against the project: `releng` that you are following:
``
#### Describe the issue
The releases of RHEL and CentOS 7.5 (and likely earlier versions) brought with them new packages that were previously provided by EPEL7. Some of these are still present in EPEL, potentially causing conflicts. Particularly problematic are various packages that are provided in EPEL as python2-* and provided in upstream as python-*. While fully-overlapping names are suboptimal, these partially-overlapping names that provide the same actual package leads to issues like [certbot #6314][certbot] and [RHBZ #1578071][bugzilla].
I have attached 4 files containing lists of problematic packages:
filename|description|impact if unresolved
-|-|-
base-and-updates-full.txt|EPEL7 packages also in upstream base or updates|moderate
base-and-updates-partial.txt|EPEL7 packages also in upstream base or updates as python-*|significant
extras-full.txt|EPEL7 packages also in upstream extras|moderate
extras-partial.txt|EPEL78 packages also in upstream extras as python-*|significant
#### When do you need this? (YYYY/MM/DD)
No specific date, but sooner is better.
#### When is this no longer needed or useful? (YYYY/MM/DD)
N/A
#### If we cannot complete your request, what is the impact?
EPEL-provided packages with full name overlap may potentially override upstream packages. EPEL-provided packages with partial name overlap may cause issues like [certbot #6314][certbot] and [RHBZ #1578071][bugzilla].
<!!image>
<!!image>
<!!image>
<!!image>
[certbot]: https://github.com/certbot/certbot/issues/6314
[bugzilla]: https://bugzilla.redhat.com/show_bug.cgi?id=1578071
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7802
4 years, 6 months
[releng] Issue #7738: fedpkg build - Connection aborted.
by Vít Ondruch
vondruch reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
The fedpkg connection with server fails during build almost every time:
~~~
$ fedpkg scratch-build --srpm
/usr/lib/python3.7/site-packages/fedora/client/bodhi.py:48: DeprecationWarning: fedora.client.bodhi has been deprecated. Please use bodhi.client.bindings instead.
DeprecationWarning)
/usr/lib/python3.7/site-packages/fedpkg/__init__.py:235: DeprecationWarning: dist() and linux_distribution() functions are deprecated in Python 3.5
runtime_os, runtime_version, _ = platform.linux_distribution()
Zapsáno: /home/vondruch/fedora-scm/own/ruby/ruby-2.5.1-99.fc30.src.rpm
/usr/lib/python3.7/site-packages/koji/__init__.py:1704: DeprecationWarning: This method will be removed in future versions. Use 'parser.read_file()' instead.
config.readfp(f)
[====================================] 100% 00:00:03 10.90 MiB 3.16 MiB/sec
Building ruby-2.5.1-99.fc30.src.rpm for rawhide
Created task: 29377062
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=29377062
Watching tasks (this may be safely interrupted)...
Could not execute scratch_build: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
~~~
This happens already for some time and it is quite annoying.
~~~
$ rpm -q fedpkg
fedpkg-1.35-1.fc30.noarch
~~~
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7738
4 years, 6 months
[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, 7 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, 7 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, 7 months