A few questions about rpmdev-bumpspec tool
by Qiyu Yan
Hello all,
I have some problem with rpmdev-bumpspec recently.
In the latest version of rpmdevtools, rpmdev-bumpspec has changed to
use time+date in the changelog it generates[1], while the packaging
guidelines have not been updated accordingly[2], should the guideline
be updated to the rpmdev-bumpspec change?
I am packaging fcitx5 using forge macros, and upstream have never
tagged a version, in this case, I am packaging like this [3] (The
snapshot dates and git short commit hashesin changelog is manually
added). With this spec file, I noticed that when I try to use
rpmdev-bumpspec to generate a changelog, it will give things like this
[4].
You can see that, in case of using forge, rpmdev-bumpspec can't
include either snapshot dates nor git short commit hashes, will this
be fine (and we can ignore the warning from rpmlint when ran on the
built packages, and start the review process) or I should always
manually include snapshot dates and git commit hashes in the
changelog. Or I should wait for this change [5] to be done and ignore
all changelog things? (and submit for review then?)
Thanks.
[1]: https://pagure.io/rpmdevtools/c/d205ad9cfc4b7123acd573e028f8c4521ec79300
[2]: https://docs.fedoraproject.org/en-US/packaging-guidelines/#changelogs
[3]: https://github.com/karuboniru/fcitx5-fedora/blob/master/fcitx5/fcitx5.spec
[4]: https://github.com/karuboniru/fcitx5-fedora/blob/972fd2e2e84e6ca136a9c5f4...
[5]: https://fedoraproject.org/wiki/Changes/Patches_in_Forge_macros_-_Auto_mac...
------
And the snapshot dates generated on my machine and copr can be
different, I think this is related to time zone (I am in UTC+8), I
don't think it is a bug, but I hope this will be improved.
--
Best regards,
Qiyu Yan
3 years, 8 months
Fedora 33, can't access NAS
by Andreas Tunek
I made a fresh install with Fedora Workstation 33 today and everything
seems to be working except for one problem. I can see my NAS in Files, but
I can't connect to it. It looks exactly the same as F32 where everything
works as expected.
Does anyone have any pointers on how to debug this, or should I just file a
bug for Files?
Best regards
Andreas
3 years, 8 months
The Fedora wiki system sucks
by Richard Shaw
So I wanted to document a ham radio related howto, so I decided that I
would make it an extension of the Amateur Radio SIG wiki, and I've got an
incomplete version created:
https://fedoraproject.org/wiki/AmateurRadio/Howto/Pat
How can a wiki not have some kind of <code> tag?
Most other systems in Fedora support markdown, and I would be a fan of
that.
Thanks,
Richard
3 years, 8 months
Schedule for Wednesday's FESCo Meeting (2020-08-12)
by Miro Hrončok
Following is the list of topics that will be discussed in the
FESCo meeting Wednesday at 14:00UTC in #fedora-meeting-2 on
irc.freenode.net.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2020-08-12 14:00 UTC'
Links to all issues to be discussed can be found at:
https://pagure.io/fesco/report/meeting_agenda
= Discussed and Voted in the Ticket =
F34 System-Wide Change: NSS CK_GCM_PARAMS change
https://pagure.io/fesco/issue/2400
APPROVED (+4,0,-0)
Update 3rd party repo policy
https://pagure.io/fesco/issue/2416
APPROVED (+3,0,-0)
F33 Self-Contained Change: DXVK as default wined3d backend on VK capable hardware
https://pagure.io/fesco/issue/2456
APPROVED (+8,0,-0)
F33 Self-Contained Change: Reserve resources for active users (Workstation)
https://pagure.io/fesco/issue/2457
APPROVED (+9,0,-0)
F33 Self-Contained Change: Ruby on Rails 6.0
https://pagure.io/fesco/issue/2458
APPROVED (+9,0,-0)
F33 Self-Contained Change: X.org Utility Deaggregation
https://pagure.io/fesco/issue/2459
APPROVED (+9,0,-0)
= Open Floor =
For more complete details, please visit each individual
issue. The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda
If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.
3 years, 8 months
Highlights from the latest Copr release
by Pavel Raiskup
Hello.
On Aug 12 2020, a new Copr release landed production. Here is the list
of visible changes:
- Project karma implemented; Logged-in users can give
thumbs-up/thumbs-down to the existing copr projects. This is just
another way to give feedback about a particular Copr project quality.
This is merely subjective. We do not give you guidance what "thumbs
up/down" means. When it is good for you - for whatever reason - give it
thumbs up. It may be just feedback for the maintainer or other users.
Or we may automatically select and group high-quality projects in the
future - and e.g. revive the idea of the Playground [1]. The options
are open. We would like to hear your feedback about this feature!
- Copr newly provides a build-time macro %buildtag. Its format is
`.copr<BUILD_ID>` and is useable for auto-incrementing the package's NVR
in subsequent builds. It may be used in spec file like:
Release: 1%{?dist}%{?buildtag}
It could be useful as good-enough alternative for the Release
auto-bumping proposal. See the fedora devel discussion [2] for more
info. This is not any kind of encouragement to use it. We added it
there to easy testing your ideas about the automatic filling of the
Release tag.
- The /status page has a new "Starting" tab [3] which shows all the binary
builds where the worker process is already started, but appropriate
builder VM is not yet assigned to it (issue/1429).
- Group avatars (user-icons assigned to an e-mail) were fixed to
really use the groups' emails, not the administrators' (issue/1419).
- Command-line interface for the project package listing was significantly
optimized, and should now be faster than the web-UI on large projects
(issue/757).
- All the background jobs have now a lower priority than normal jobs.
Previously, background source builds were still prioritized over normal
builds. This should be the last step towards a fair build scheduler.
- Support for a new command 'copr-cli list-builds <project>' was added.
It lists each build on a separate line, as a tab-separated list of
<BUILD_ID> <PACKAGE_NAME> <BUILD_STATUS> items.
Related copr client Fedora/EPEL updates:
F32 - https://bodhi.fedoraproject.org/updates/FEDORA-2020-ce81a9539d
F31 - https://bodhi.fedoraproject.org/updates/FEDORA-2020-76bfc383c3
EPEL8 - https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-4c313586d8
EPEL7 - https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-6a77e31d06
EPEL6 - https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-78e089fe70
Should you have any related issues, please report them to us as usual.
[1] https://fedoraproject.org/wiki/Playground
[2] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
[3] https://copr.fedorainfracloud.org/status/starting/
Happy building!
Copr Team
3 years, 8 months