Summary/Minutes from today's FPC Meeting (2021-03-18 16:00 - 16:20 UTC)
by James Antill
======================
#fedora-meeting-2: fpc
======================
Meeting started by geppetto at 16:01:09 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-2/2021-03-18/fpc.2021-03...
.
Meeting summary
---------------
* Roll Call (geppetto, 16:01:09)
* Open Floor (geppetto, 16:07:57)
* ACTION: Eighth_Doctor will fix versioning ;) (geppetto, 16:17:45)
Meeting ended at 16:20:15 UTC.
Action Items
------------
* Eighth_Doctor will fix versioning ;)
Action Items, by person
-----------------------
* Eighth_Doctor
* Eighth_Doctor will fix versioning ;)
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* geppetto (33)
* Eighth_Doctor (29)
* mhroncok (17)
* zodbot (14)
* decathorpe (5)
* nirik (2)
* pingou (1)
* carlwgeorge (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
3 years, 1 month
Excluding tests with %gocheck -r not working
by Bryce Torcello
Hello all,
I'm still fairly new to packaging and I was packaging a golang library when one of it's tests relies on networking so I'd like to skip it. The Fedora packaging guidelines https://docs.fedoraproject.org/en-US/packaging-guidelines/Golang/#_runnin... suggests the `-r <regexp>` flag would help me do this, however I've not been able to get it to work.
I've tried `%gocheck -r get_gcs_test.go`, `%gocheck -r get_gcs_test.*`, `%gocheck -r ./get_gcs_test.go`, as well as adding double quotes around the filename, but none of these seem to have any effect on excluding the test. Am I using this flag incorrectly or is there a bug with this flag?
I looked at a number of other golang packages and I wasn't able to find any other uses of the `-r` flag. Only noting uses of the `-d <directory>` flag, which does seem to work in my case but excludes other tests which I do not want to exclude.
--
Bryce Torcello
https://procupti.me
3 years, 1 month
Macronize %package -n python3-foo?
by Miro Hrončok
Hello Pythonistas.
I find myself cop-pasting this boring snippet each time I create a Python
package (using the old macros or the new):
%package -n python3-foo
Summary: %{summary}
%description -n python3-foo %_description
And using one of those in %files:
%files -n python3-foo
%files -n python3-foo -f %{pyproject_files}
I wonder whether it makes sense to macronize this.
For example:
Name: python-foo
...
%global _description %{expand:
This is the description for both SRPM and the python3-foo package.}
%description %_description
%py3_package %_description
...
%py3_files
...
Or maybe even (if possible):
Name: python-foo
...
%py3_package_with_description
This is the description for both SRPM and the python3-foo package.
...
%py3_files
...
Both macros would figure the package name by replacing the python- prefix from
%{name} with python3-.
Pros: No more copy-paste-edit \o/
Cons: The more is hidden from the reader behind automagic macros, the less
obvious is the spec file to somebody who tries to read or modify it :(
What is your opinion?
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
3 years, 1 month
I cannot use %ifarch on a noarch package?
by Miro Hrončok
Hello.
I wanted to ship the following snippet in python-hypothesis:
--------------------------------------------------
%check
%pytest -v -n auto \
-k "not test_registered_from_entrypoint" \
--ignore tests/codemods \
--ignore tests/dpcontracts \
--ignore tests/redis \
%ifarch s390x
-k "not test_data_frames_with_timestamp_columns"
%endif
--------------------------------------------------
However, for some reason, the s390x part was not present on s390x. I've been
banging my head on the desk for some time trying to figure out why it doesn't
wok and apparently, it is because the package is noarch.
I've got around the problem by using:
%if "%{_arch}" == "s390x"
-k "not test_data_frames_with_timestamp_columns"
%endif
Is that how it is supposed to work?
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
3 years, 1 month
Fedora Update Policy
by Brad Bell
I have a package that runs all it's automated tests during the `%check phase` of the build process.
I am not sure what I should specify, for this case, during the `fedpkg updae` command ?
It seems that my updates have gotten stuck, with the options I have tried.
For example, see `20210000.3-3.fc33` on
http://rpms.remirepo.net/rpmphp/zoom.php?rpm=cppad
How can I move this version to `base` for fedora-33 ?
3 years, 1 month
