Re: Need help with nut systemd scriptlets and multiple services and targets
On 4/6/23 17:56, Orion Poplawski wrote: The nut package has a number of different systemd units: /usr/lib/systemd/system/nut-driver-enumerator.path /usr/lib/systemd/system/nut-driver-enumerator.service '/usr/lib/systemd/system/nut-driver@.service' /usr/lib/systemd/system/nut-driver.target /usr/lib/systemd/system/nut-server.service /usr/lib/systemd/system/nut.target And I have a number of questions about how to handle them: * I think we want a preset to automatically enable and start nut-driver-enumerator.path. This monitors /etc/ups/ups.conf and runs nut-driver-enumerator.service when it does. It also has: [Install] WantedBy=nut.target Does that seem appropriate? Is is possible to start it immediately after install in %post? You don't want to start _anything_ until the user has done the rather extensive editing required in the config files to tell the package what hardware to look for and what to do. * What is a user expected to do to enable and start "nut"? It seems like: systemctl enable nut.target systemctl start nut.target The user needs to enable nut-driver-enumerator.service if there is any UPS hardware monitored by this system (i.e., not needed if this is a "secondary" system and some other "primary" system is actually monitoring the UPS). Then, running "systemctl enable nut.target" will start the package on the next boot. Include "--now", or run "systemctl start nut.target" to start it immediately. But all of that has to wait until the user has made the necessary edits in the config scripts in /etc/ups.conf and edited the /usr/bin/upssched-cmd script to set up any additional actions (e.g., notifications, etc) that are wanted. Would do the trick, but I don't think it's very intuitive - most users think in terms of service units I think. Overall, it's a pretty user-unfriendly package. Some things that used to "Just Work" back in the days of CentOS 6 need manual configuration now. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] python2 in epel8-next
I'm building python3.11-setuptools_scm-epel in epel8-next. It requires mercurial for the tests which requires: /usr/bin/python2 libpython2.7.so.1.0()(64bit) python(abi) = 2.7 python2 On my CS8 system this is satisfied by python2-2.7.18-12.module_el8+299+aa6e9afa.x86_64 from the python27 module. In the epel8-next build I end up with: python2 x86_64 2.7.17-1.el8 python2-for-tests x86_64 2.7.17-1.el8 python2-libs x86_64 2.7.17-1.el8 despite this message: DEBUG util.py:445: Enabling module streams: DEBUG util.py:445: mercurial 4.8 DEBUG util.py:445: python27 2.7 Which then emits a complaint when run: ERROR: Python 2 is disabled in RHEL8. - For guidance on porting to Python 3, see the Conservative Python3 Porting Guide: http://portingguide.readthedocs.io/ - If you need Python 2 at runtime: - Use the python27 module - If you do not have access to BZ#1533919: - Use the python27 module - If you need to use Python 2 only at RPM build time: - File a bug blocking BZ#1533919: https://bugzilla.redhat.com/show_bug.cgi?id=1533919 - Set the environment variable RHEL_ALLOW_PYTHON2_FOR_BUILD=1 (Note that if you do not file the bug as above, this workaround will break without warning in the future.) - If you need to use Python 2 only for tests: - File a bug blocking BZ#1533919: https://bugzilla.redhat.com/show_bug.cgi?id=1533919 (If your test tool does not have a Bugzilla component, feel free to use `python2`.) - Use /usr/bin/python2-for-tests instead of python2 to run your tests. (Note that if you do not file the bug as above, this workaround will break without warning in the future.) For details, see https://hurl.corp.redhat.com/rhel8-py2 Fatal Python error: Python 2 is disabled I can work around it by defining RHEL_ALLOW_PYTHON2_FOR_BUILD=1, but it seems like we really should be pulling in python2 from the module? -- Orion Poplawski he/him/his - surely the least important thing about me IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ smime.p7s Description: S/MIME Cryptographic Signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2183880] perl-Test-Compile-3.2.0 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2183880 --- Comment #3 from Fedora Update System --- FEDORA-2023-cd589e212e has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-cd589e212e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2183880 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2184624] perl-Test-Compile-3.2.2 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2184624 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System --- FEDORA-2023-cd589e212e has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-cd589e212e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2184624 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2182227] perl-Test-Compile-3.1.1 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2182227 --- Comment #4 from Fedora Update System --- FEDORA-2023-cd589e212e has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-cd589e212e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2182227 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2184492] perl-DBD-Pg-3.16.3 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2184492 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System --- FEDORA-2023-de5e19fd58 has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-de5e19fd58 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2184492 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Need help with nut systemd scriptlets and multiple services and targets
The nut package has a number of different systemd units: /usr/lib/systemd/system/nut-driver-enumerator.path /usr/lib/systemd/system/nut-driver-enumerator.service '/usr/lib/systemd/system/nut-driver@.service' /usr/lib/systemd/system/nut-driver.target /usr/lib/systemd/system/nut-server.service /usr/lib/systemd/system/nut.target And I have a number of questions about how to handle them: * I think we want a preset to automatically enable and start nut-driver-enumerator.path. This monitors /etc/ups/ups.conf and runs nut-driver-enumerator.service when it does. It also has: [Install] WantedBy=nut.target Does that seem appropriate? Is is possible to start it immediately after install in %post? * What is a user expected to do to enable and start "nut"? It seems like: systemctl enable nut.target systemctl start nut.target Would do the trick, but I don't think it's very intuitive - most users think in terms of service units I think. It also doesn't seem to work without nut-driver-enumerator.service having run to configure and start the nut-driver@UPS.service instance. Because starting nut.target does not appear to run nut-driver-enumerator.service, at least on EL8. * What systemd scriptlets should get called? Do we call them on target or path units as well? The packaging guidelines don't seem to mention those types specifically, but I do see them in various spec files. Thank you very much for any guidance. -- Orion Poplawski IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ smime.p7s Description: S/MIME Cryptographic Signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: HEADS UP: tesseract-5.3.0 landing in rawhide with soname bump
On 06.04.23 23:43, Adam Williamson wrote: On Thu, 2023-04-06 at 23:26 +0200, Sandro Mani wrote: On 06.04.23 22:37, Miro Hrončok wrote: On 23. 12. 22 16:00, Sandro Mani wrote: Hi I'll be landing tesseract 5.3.0 in rawhide, building it in the f38-build-side-61405 side tag, along with the following dependent packages: ffmpeg gimagereader mupdf opencv python-PyMuPDF qpdfview R-tesseract zathura-pdf-mupdf Thanks Sandro Hey Sandro, a new soname bump landed recently: https://src.fedoraproject.org/rpms/tesseract/c/cc010cab233fe1da5f614d7dc0afde3a5e2e8d2d?branch=rawhide Will you please also handle the rebuilds? E.g. https://bugzilla.redhat.com/show_bug.cgi?id=2185098 https://bugzilla.redhat.com/show_bug.cgi?id=2185090 https://bugzilla.redhat.com/show_bug.cgi?id=2185099 Apologies for this, evidently I failed somehow in my repoquery check. Will fix right away. To be clear, Sandro already was rebuilding dependencies, but just missed some. The tesseract build was done on a side tag and the update is https://bodhi.fedoraproject.org/updates/FEDORA-2023-3e0758623d . As of now it has only tesseract, ffmpeg and opencv builds, it needs the others from the list. Should now be okay. I had executed dnf repoquery --whatrequires libtesseract.so.5.3.0 rather than dnf repoquery --whatrequires libtesseract.so.5.3.0* ... ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: HEADS UP: tesseract-5.3.0 landing in rawhide with soname bump
On Thu, 2023-04-06 at 23:26 +0200, Sandro Mani wrote: > On 06.04.23 22:37, Miro Hrončok wrote: > > On 23. 12. 22 16:00, Sandro Mani wrote: > > > Hi > > > > > > I'll be landing tesseract 5.3.0 in rawhide, building it in the > > > f38-build-side-61405 side tag, along with the following dependent > > > packages: > > > > > > ffmpeg > > > gimagereader > > > mupdf > > > opencv > > > python-PyMuPDF > > > qpdfview > > > R-tesseract > > > zathura-pdf-mupdf > > > > > > Thanks > > > Sandro > > > > Hey Sandro, > > a new soname bump landed recently: > > https://src.fedoraproject.org/rpms/tesseract/c/cc010cab233fe1da5f614d7dc0afde3a5e2e8d2d?branch=rawhide > > > > Will you please also handle the rebuilds? > > > > E.g. > > https://bugzilla.redhat.com/show_bug.cgi?id=2185098 > > https://bugzilla.redhat.com/show_bug.cgi?id=2185090 > > https://bugzilla.redhat.com/show_bug.cgi?id=2185099 > > > Apologies for this, evidently I failed somehow in my repoquery check. > Will fix right away. To be clear, Sandro already was rebuilding dependencies, but just missed some. The tesseract build was done on a side tag and the update is https://bodhi.fedoraproject.org/updates/FEDORA-2023-3e0758623d . As of now it has only tesseract, ffmpeg and opencv builds, it needs the others from the list. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: HEADS UP: tesseract-5.3.0 landing in rawhide with soname bump
On 06.04.23 22:37, Miro Hrončok wrote: On 23. 12. 22 16:00, Sandro Mani wrote: Hi I'll be landing tesseract 5.3.0 in rawhide, building it in the f38-build-side-61405 side tag, along with the following dependent packages: ffmpeg gimagereader mupdf opencv python-PyMuPDF qpdfview R-tesseract zathura-pdf-mupdf Thanks Sandro Hey Sandro, a new soname bump landed recently: https://src.fedoraproject.org/rpms/tesseract/c/cc010cab233fe1da5f614d7dc0afde3a5e2e8d2d?branch=rawhide Will you please also handle the rebuilds? E.g. https://bugzilla.redhat.com/show_bug.cgi?id=2185098 https://bugzilla.redhat.com/show_bug.cgi?id=2185090 https://bugzilla.redhat.com/show_bug.cgi?id=2185099 Apologies for this, evidently I failed somehow in my repoquery check. Will fix right away. Sandro ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: HEADS UP: tesseract-5.3.0 landing in rawhide with soname bump
On 23. 12. 22 16:00, Sandro Mani wrote: Hi I'll be landing tesseract 5.3.0 in rawhide, building it in the f38-build-side-61405 side tag, along with the following dependent packages: ffmpeg gimagereader mupdf opencv python-PyMuPDF qpdfview R-tesseract zathura-pdf-mupdf Thanks Sandro Hey Sandro, a new soname bump landed recently: https://src.fedoraproject.org/rpms/tesseract/c/cc010cab233fe1da5f614d7dc0afde3a5e2e8d2d?branch=rawhide Will you please also handle the rebuilds? E.g. https://bugzilla.redhat.com/show_bug.cgi?id=2185098 https://bugzilla.redhat.com/show_bug.cgi?id=2185090 https://bugzilla.redhat.com/show_bug.cgi?id=2185099 -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2185089] New: perl-DynaLoader-Functions-0.004 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2185089 Bug ID: 2185089 Summary: perl-DynaLoader-Functions-0.004 is available Product: Fedora Version: rawhide Status: NEW Component: perl-DynaLoader-Functions Keywords: FutureFeature, Triaged Assignee: mspa...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: mspa...@redhat.com, p...@city-fan.org, perl-devel@lists.fedoraproject.org, ppi...@redhat.com Target Milestone: --- Classification: Fedora Releases retrieved: 0.004 Upstream release that is considered latest: 0.004 Current version/release in rawhide: 0.003-18.fc38 URL: http://search.cpan.org/dist/DynaLoader-Functions/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/2847/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-DynaLoader-Functions -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2185089 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Koji: Could the initial side tag repo be copied from parent (to avoid worflow delays)?
On Thu, Apr 06, 2023 at 08:21:36AM +0200, Miro Hrončok wrote: > Hello, > > When using custom side tags like this: > > $ fedpkg request-side-tag > $ fedpkg chain-build --target f38-build-side-... ... > > One of the obstacles is that the initial waitrepo for the job takes a lot of > time, (e.g. 10+ minutes). That is not comfortable for the package maintainer > -- it's faster to use buildroot overrides. > > I wonder if the initial createrepo could be skipped entirely by symlinking / > copying / using the already available repository from the base (parent) tag. > > That could make this workflow more attractive. The sidetag plugin code is in upstream koji. This sounds like a great RFE for koji then? I don't know why it's not done that way, there might be a reason or might be an oversight, but please file a RFE on it? :) Side note: I recall when normal newrepos took like 40-45min (and we had a lot less packages then), so 10min seems nice to me. But I agree if it could be made mostly instant that would be great for this case. kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Future of encryption in Fedora
There are a couple more disadvantages to using Discourse: * Several of the replies are lower-quality and are not contributing to the conversation. * There is no threading like we have with emails, so these replies are more disruptive and the discussion is less organized. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 38 Final Go/No-Go meeting next week
The Fedora Linux 38 Final Go/No-Go[1] meeting is scheduled for Thursday 13 April at 1700 UTC in #fedora-meeting. At this time, we will determine the status of the F38 Final for the 18 April early target date[2]. For more information about the Go/No-Go meeting, see the wiki[3]. [1] https://calendar.fedoraproject.org/meeting/10487/ [2] https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html [3] https://fedoraproject.org/wiki/Go_No_Go_Meeting -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] Fedora Linux 38 Final Go/No-Go meeting next week
The Fedora Linux 38 Final Go/No-Go[1] meeting is scheduled for Thursday 13 April at 1700 UTC in #fedora-meeting. At this time, we will determine the status of the F38 Final for the 18 April early target date[2]. For more information about the Go/No-Go meeting, see the wiki[3]. [1] https://calendar.fedoraproject.org/meeting/10487/ [2] https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html [3] https://fedoraproject.org/wiki/Go_No_Go_Meeting -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Future of encryption in Fedora
On Thu, Apr 6, 2023 at 12:32 PM Simo Sorce wrote: > On Mon, 2023-04-03 at 16:18 -0500, Michael Catanzaro wrote: > > On Mon, Apr 3 2023 at 01:41:48 PM -0700, Brian C. Lane > > wrote: > > > This seems like exactly the kind of discussion that belongs on the > > > devel > > > list, not on a website that I have to remember to visit for updates. > > > > There is a notification bell in the right sidebar. Click it. ;) > > > > Or we can simply ignore that discussion until it lands in devel with a > change proposal. > Discussing on the forum was a suggestion from zbyszek and I think he proposed it in the same spirit that I agreed to the proposal - as an experiment in trying to align technical discussions more closely with the overall direction of the Fedora project for communication. I think we can see both pros and cons in how it's gone - on the good side, people are involved that might not be involved otherwise, there's an easily accessible public record of the conversation that is more readable than even a good mailing list archive, and having richer markup available is genuinely useful. On the downside, spam limits on new posters have gotten in the way in some cases, and people have had some trouble figuring out how to use the quoting features, resulting in disconnected responses. Yes, there will eventually be change proposals, which will be discussed here (unless anything changes...) but I would strongly encourage people to get involved now in the discussion if they care about the topic - the more we can get things right early, the better. - Owen ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Future of encryption in Fedora
On Mon, 2023-04-03 at 16:18 -0500, Michael Catanzaro wrote: > On Mon, Apr 3 2023 at 01:41:48 PM -0700, Brian C. Lane > wrote: > > This seems like exactly the kind of discussion that belongs on the > > devel > > list, not on a website that I have to remember to visit for updates. > > There is a notification bell in the right sidebar. Click it. ;) > Or we can simply ignore that discussion until it lands in devel with a change proposal. -- Simo Sorce RHEL Crypto Team Red Hat, Inc ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Schedule for Thursday's FPC Meeting (2023-04-06 16:00 UTC)
On Wed, Apr 5, 2023 at 9:39 PM James Antill wrote: > > Following is the list of topics that will be discussed in the FPC > meeting Thursday at 2023-04-06 16:00 UTC in #fedora-meeting-1 on > irc.libera.chat. Can you add https://pagure.io/packaging-committee/pull-request/1255 if time permits? This blocks the implementation of the "Rpmautospec by Default" Change. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Linux 38 branched
V Fri, Feb 10, 2023 at 11:15:25AM +0100, Petr Pisar napsal(a): > V Thu, Feb 09, 2023 at 06:44:03PM +0100, Tomas Hrcka napsal(a): > > Two things to remember: > > > > 1. The modules will be built for a new platform:f39 > > Thanks for thinking of modules. I've actually started the rebuild and slowly > going through the 46 streams. > I finished rebuilding the modules: 37 done, 11 failed, 1 skipped. I reported all the build failures. For your information, here is the list (the #numbers are MBS build identifiers): Done: avocado:latest #15978 cri-o:1.22 #15980 cri-o:1.23 #15981 cri-o:1.24 #15983 ghc:8.10 #15985 avocado-vt:latest - depends on avocado:latest #15986 mysql:8.0 #16042 nextcloud:nextcloud-stable #15988 nextcloud:23 #15990 nextcloud:24 #16044 nginx:mainline #16051 nginx:1.20 #16059 perl-bootstrap:5.34 #16065 perl-bootstrap:5.36 #16091 perl:5.34 - depends on perl-bootstrap:5.34, #16081 perl:5.36 - depends on perl-bootstrap:5.36 #16104 perl-App-cpanminus:1.7045 - depends on perl:5.34, perl:5.36, perl-YAML:1.30 #16205, #16206 perl-Date-Manip:6.86 - depends on perl:5.34, perl:5.36 #16197, #16198 perl-DBD-MySQL:4.050 #16172, #16173 perl-DBD-Pg:3.15 - depends on postgresql:14 #16257, #16258 perl-DBD-SQLite:1.70 #16180, #16181 perl-DBI:1.643 #16132, #16133 perl-IO-Socket-SSL:2.074 - depends on perl:5.34, perl:5.36 #16147, #16148 perl-IO-stringy:2.113 #16155, #16156 perl-libwww-perl:6.62 - depends on perl:5.34, perl:5.36, perl-IO-Socket-SSL:2.074 #16222, #16223 perl-libwww-perl:6.67 - depends on perl:5.34, perl:5.36, perl-IO-Socket-SSL:2.074 #16214, #16215 perl-YAML:1.30 - depends on perl:5.34, perl:5.36, perl-YAML-bootstrap:1.30 #16164, #16165 perl-YAML-bootstrap:1.30 - depends on perl:5.34, perl:5.36 #16124, #16125 postgresql:12 #16134 postgresql:13 #16016 postgresql:14 #16247 https://bugzilla.redhat.com/show_bug.cgi?id=2170745 postgresql:15 #16140 ruby:3.1 #16076 sway:rolling #16031 swig:4.0 #16085 swig:4.1 #16108 varnish:6.0 #16117 Skipped: avocado-vt:82lts - depends on avocado:82lts Failed: avocado:82lts #15979, python-avocado-82.2-1 RPM build hangs https://bugzilla.redhat.com/show_bug.cgi?id=2183989 cri-o:1.25 #15984 https://bugzilla.redhat.com/show_bug.cgi?id=2168860 mariadb:10.5 #15987 https://bugzilla.redhat.com/show_bug.cgi?id=2169678 mariadb:10.6 #16041 https://bugzilla.redhat.com/show_bug.cgi?id=2169678 mariadb:10.7 #16054 https://bugzilla.redhat.com/show_bug.cgi?id=2169678 mariadb:10.8 #16066 https://bugzilla.redhat.com/show_bug.cgi?id=2169678 mariadb:10.9 #16075 https://bugzilla.redhat.com/show_bug.cgi?id=2169678 nodejs:16 #16060 https://bugzilla.redhat.com/show_bug.cgi?id=2119713 perl-CGI:4.54 - depends on perl:5.34, perl:5.36, perl-libwww-perl:6.67, MBS times out on a submission https://pagure.io/fm-orchestrator/issue/1759 perl-XML-Parser:2.46 - depends on perl:5.36, perl-libwww-perl:6.67, MBS times out on a submission https://pagure.io/fm-orchestrator/issue/1759 subversion:1.14 - depends on swig:4.0 #16113, subversion RPM tests fail https://bugzilla.redhat.com/show_bug.cgi?id=2170754 -- Petr signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[CANCELED] Reminder meeting : ELN SIG
Tomorrow is a holiday in many places. On Thu, Apr 6, 2023 at 8:00 AM wrote: > > Dear all, > > You are kindly invited to the meeting: >ELN SIG on 2023-04-07 from 12:00:00 to 13:00:00 US/Eastern >At fedora-meet...@irc.libera.chat > > The meeting will be about: > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 38 compose report: 20230406.n.0 changes
OLD: Fedora-38-20230405.n.0 NEW: Fedora-38-20230406.n.0 = SUMMARY = Added images:1 Dropped images: 0 Added packages: 0 Dropped packages:0 Upgraded packages: 0 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded packages: 0 B Size of downgraded packages: 0 B Size change of upgraded packages: 0 B Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Kinoite dvd-ostree ppc64le Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-38-20230406.n.0.iso = DROPPED IMAGES = = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = = DOWNGRADED PACKAGES = ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2184624] perl-Test-Compile-3.2.2 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2184624 --- Comment #2 from Fedora Update System --- FEDORA-2023-cd589e212e has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-cd589e212e -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2184624 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2184624] perl-Test-Compile-3.2.2 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2184624 Jitka Plesnikova changed: What|Removed |Added Doc Type|--- |If docs needed, set a value Status|NEW |MODIFIED Fixed In Version||perl-Test-Compile-3.2.2-2.f ||c39 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2184624 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Fedocal] Reminder meeting : ELN SIG
Dear all, You are kindly invited to the meeting: ELN SIG on 2023-04-07 from 12:00:00 to 13:00:00 US/Eastern At fedora-meet...@irc.libera.chat The meeting will be about: Source: https://calendar.fedoraproject.org//meeting/10449/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora rawhide compose report: 20230406.n.0 changes
OLD: Fedora-Rawhide-20230405.n.0 NEW: Fedora-Rawhide-20230406.n.0 = SUMMARY = Added images:1 Dropped images: 0 Added packages: 2 Dropped packages:1 Upgraded packages: 359 Downgraded packages: 0 Size of added packages: 4.28 MiB Size of dropped packages:133.27 KiB Size of upgraded packages: 6.22 GiB Size of downgraded packages: 0 B Size change of upgraded packages: -40.50 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Budgie live x86_64 Path: Spins/x86_64/iso/Fedora-Budgie-Live-x86_64-Rawhide-20230406.n.0.iso = DROPPED IMAGES = = ADDED PACKAGES = Package: rust-logging_timer_proc_macros-1.1.0-1.fc39 Summary: Proc-macro implementation for the logging_timer crate RPMs:rust-logging_timer_proc_macros+default-devel rust-logging_timer_proc_macros-devel Size:19.29 KiB Package: spirv-llvm15.0-translator-15.0.0-1.fc39 Summary: LLVM 15 to SPIRV Translator RPMs:spirv-llvm15.0-translator spirv-llvm15.0-translator-devel spirv-llvm15.0-translator-tools Size:4.26 MiB = DROPPED PACKAGES = Package: buildnumber-maven-plugin-1.3-24.fc38 Summary: Build Number Maven Plugin RPMs:buildnumber-maven-plugin buildnumber-maven-plugin-javadoc Size:133.27 KiB = UPGRADED PACKAGES = Package: NetworkManager-1:1.43.5-1.fc39 Old package: NetworkManager-1:1.43.4-1.fc39 Summary: Network connection manager and user applications RPMs: NetworkManager NetworkManager-adsl NetworkManager-bluetooth NetworkManager-cloud-setup NetworkManager-config-connectivity-fedora NetworkManager-config-server NetworkManager-dispatcher-routing-rules NetworkManager-initscripts-ifcfg-rh NetworkManager-initscripts-updown NetworkManager-libnm NetworkManager-libnm-devel NetworkManager-ovs NetworkManager-ppp NetworkManager-team NetworkManager-tui NetworkManager-wifi NetworkManager-wwan Size: 25.53 MiB Size change: 7.02 KiB Changelog: * Wed Apr 05 2023 Lubomir Rintel - 1:1.43.5-1 - Update to 1.43.5 release (development) Package: ags-3.6.0.47-1.fc39 Old package: ags-3.6.0.46-1.fc39 Summary: Engine for creating and running videogames of adventure (quest) genre RPMs: ags Size: 5.67 MiB Size change: 1.68 KiB Changelog: * Tue Apr 04 2023 Dominik Mierzejewski - 3.6.0.47-1 - update to 3.6.0.47 stable release (#2183747) Package: akonadi-calendar-tools-23.03.90-1.fc39 Old package: akonadi-calendar-tools-23.03.80-1.fc39 Summary: Akonadi Calendar Tools RPMs: akonadi-calendar-tools Size: 925.05 KiB Size change: -123 B Changelog: * Fri Mar 31 2023 Marc Deop i Argem?? - 23.03.90-1 - 23.03.90 Package: akonadi-import-wizard-23.03.90-1.fc39 Old package: akonadi-import-wizard-23.03.80-1.fc39 Summary: Akonadi Import Wizard RPMs: akonadi-import-wizard akonadi-import-wizard-devel Size: 2.34 MiB Size change: 87 B Changelog: * Fri Mar 31 2023 Marc Deop i Argem?? - 23.03.90-1 - 23.03.90 Package: akonadiconsole-23.03.90-1.fc39 Old package: akonadiconsole-23.03.80-1.fc39 Summary: Akonadi developer tool RPMs: akonadiconsole Size: 1.49 MiB Size change: 23.92 KiB Changelog: * Fri Mar 31 2023 Marc Deop i Argem?? - 23.03.90-1 - 23.03.90 Package: akregator-23.03.90-1.fc39 Old package: akregator-23.03.80-1.fc39 Summary: Feed Reader RPMs: akregator akregator-libs Size: 5.83 MiB Size change: -6 B Changelog: * Fri Mar 31 2023 Marc Deop i Argem?? - 23.03.90-1 - 23.03.90 Package: alligator-23.03.90-1.fc39 Old package: alligator-23.03.80-1.fc39 Summary: Kirigami-based RSS reader RPMs: alligator Size: 635.67 KiB Size change: 200 B Changelog: * Fri Mar 31 2023 Marc Deop i Argem?? - 23.03.90-1 - 23.03.90 Package: analitza-23.03.90-1.fc39 Old package: analitza-23.03.80-1.fc39 Summary: Library of mathematical features RPMs: analitza analitza-devel Size: 3.02 MiB Size change: 742 B Changelog: * Fri Mar 31 2023 Marc Deop i Argem?? - 23.03.90-1 - 23.03.90 Package: angelfish-23.03.90-1.fc39 Old package: angelfish-23.03.80-1.fc39 Summary: Plasma Mobile minimal web browser RPMs: angelfish Size: 710.75 KiB Size change: 2.84 KiB Changelog: * Fri Mar 31 2023 Marc Deop i Argem?? - 23.03.90-1 - 23.03.90 Package: ansible-freeipa-1.10.0-1.fc39 Old package: ansible-freeipa-1.9.2-1.fc38 Summary: Roles and playbooks to deploy FreeIPA servers, replicas and clients RPMs: ansible-freeipa ansible-freeipa-tests Size: 549.06 KiB Size change: 10.04 KiB Changelog: * Fri Mar 10 2023 Rafael Jeffman - 1.9.2-2 - Migrate to SPDX license * Wed Apr 05 2023 Thomas Woerner - 1.10.0-1 - Update to version 1.10.0 https://github.com/freeipa/ansible-freeipa/releases/tag/v1.10.0 Highlights: - ipagroup: Allow multiple group management
[Bug 2184492] perl-DBD-Pg-3.16.3 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2184492 --- Comment #2 from Fedora Update System --- FEDORA-2023-de5e19fd58 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-de5e19fd58 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2184492 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2184492] perl-DBD-Pg-3.16.3 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2184492 Jitka Plesnikova changed: What|Removed |Added Fixed In Version||perl-DBD-Pg-3.16.3-1.fc39 Doc Type|--- |If docs needed, set a value Status|NEW |MODIFIED -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2184492 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: redhat-lsb-core
On Tue, 2023-04-04 at 10:19 -0400, Steven A. Falco wrote: > On 4/4/23 09:56 AM, Neal Gompa wrote: > > On Tue, Apr 4, 2023 at 9:49 AM Steven A. Falco > > wrote: > > > > > > On 4/4/23 05:58 AM, ser...@serjux.com wrote: > > > > On 2023-04-03 21:13, Steven A. Falco wrote: > > > > > I'm confused by the Requires for redhat-lsb-core. > > > > > > > > > > According to "dnf repoquery --requires redhat-lsb-core" there > > > > > is no > > > > > requirement for esmtp. But according to "dnf repoquery -- > > > > > whatrequires > > > > > esmtp", redhat-lsb-core does require esmtp. > > > > > > > > > > Perhaps there is some sort of transitive requirement that the > > > > > above > > > > > commands don't show, but the curious thing is that I have > > > > > redhat-lsb-core installed on my F37 machine, and that didn't > > > > > pull in > > > > > esmtp. > > > > > > > > Please open a bug report , I'm reviewing redhat-lsb [1] , this > > > > package is so old that still called redhat ... > > > > Anyone suggest another name ? > > > I'm happy to write a bug. Do you prefer something along the > > > lines of "Split lsb_release into a subpackage" or perhaps "Split > > > redhat-lsb-core into finer-grained subpackages"? > > > > > > For me, having an lsb_release subpackage would be best, because > > > that is all I need for KiCad. But I'll also pursue Neal's > > > comment about changing wxWidgets to get the info another way. > > > > > > > The distro command from python3-distro may also help if you *must* > > use > > a command-line tool. > > > > But reading the file directly would be better. > > I've created a bug [2] requesting that wxGTK use a file from os- > release rather than lsb_release. > > > Worst case scenario, I could bring over a port of SUSE's > > lsb_release > > package that uses os-release for its data into Fedora[1]. > > That is a very interesting approach that could potentially help other > customers of the information. > > Steve > > > [1]: > > https://copr.fedorainfracloud.org/coprs/ngompa/lsb_release-shim-el9/ > > [2] https://bugzilla.redhat.com/show_bug.cgi?id=2184391 Hi, Sorry for delay ... I'm planing bring redhat-lsb to epel9 soon , because will avoid many confusions . lsb_release-shim-el9 and https://github.com/thkukuk/lsb-release_os-release is very interesting for me, I will check Basically we need or should provide /usr/bin/lsb_release which gives information of the system like [1] , all the rest is meta packages and meta information that I think we don't need and in others cases are completely obsolete, but have a tool which identify the operating system in a standard way, I think is still valid . [1] lsb_release -a LSB Version::core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1- noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1- amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1- noarch:trialuse-4.1-amd64:trialuse-4.1-noarch Distributor ID: Fedora Description:Fedora release 37 (Thirty Seven) Release:37 Codename: ThirtySeven -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Koji: Could the initial side tag repo be copied from parent (to avoid worflow delays)?
Hello, When using custom side tags like this: $ fedpkg request-side-tag $ fedpkg chain-build --target f38-build-side-... ... One of the obstacles is that the initial waitrepo for the job takes a lot of time, (e.g. 10+ minutes). That is not comfortable for the package maintainer -- it's faster to use buildroot overrides. I wonder if the initial createrepo could be skipped entirely by symlinking / copying / using the already available repository from the base (parent) tag. That could make this workflow more attractive. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
