Fedora-Cloud-33-20211112.0 compose check report
No missing expected images. Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-33-2021.0): ID: 1062800 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/1062800 ID: 1062809 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1062809 Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: libnsl.so.2.0.1 updated to libnsl.so.3.0.0 without coordination, broke rawhide
Yeah someone should push that to a side package... ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 55 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-f005e1b879 debmirror-2.35-1.el7 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-39d32447db openssl11-1.1.1k-1.el7 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-05dd12001e rpki-client-7.5-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing copr-cli-1.97-1.el7 cscppc-2.1.1-1.el7 csmock-3.1.0-1.el7 python-copr-1.114-1.el7 python-yara-4.1.3-2.el7 wordpress-5.1.11-1.el7 yara-4.1.3-1.el7 Details about builds: copr-cli-1.97-1.el7 (FEDORA-EPEL-2021-e74efdc371) Command line interface for COPR Update Information: copr-cli - More detailed "Request is not in JSON format" error - APIv3 /monitor route python-copr - Depend on setuptools for the pkg_resources - APIv3 /monitor route ChangeLog: * Wed Nov 10 2021 Silvie Chlupova 1.97-1 - More detailed "Request is not in JSON format" error - APIv3 /monitor route cscppc-2.1.1-1.el7 (FEDORA-EPEL-2021-1b387a86a0) A compiler wrapper that runs cppcheck in background Update Information: - update to latest upstream release ChangeLog: * Thu Nov 11 2021 Kamil Dudka 2.1.1-1 - update to latest upstream release csmock-3.1.0-1.el7 (FEDORA-EPEL-2021-1b387a86a0) A mock wrapper for Static Analysis tools Update Information: - update to latest upstream release ChangeLog: * Thu Nov 11 2021 Kamil Dudka 3.1.0-1 - update to latest upstream release python-copr-1.114-1.el7 (FEDORA-EPEL-2021-e74efdc371) Python interface for Copr Update Information: copr-cli - More detailed "Request is not in JSON format" error - APIv3 /monitor route python-copr - Depend on setuptools for the pkg_resources - APIv3 /monitor route ChangeLog: * Wed Nov 10 2021 Silvie Chlupova 1.114-1 - Depend on setuptools for the pkg_resources - APIv3 /monitor route python-yara-4.1.3-2.el7 (FEDORA-EPEL-2021-1a59ba90e8) Python binding for the YARA pattern matching tool Update Information: update to bugfix release ChangeLog: * Wed Nov 10 2021 Michal Ambroz - 4.1.3-2 - rebuild due to koji hickup * Wed Nov 10 2021 Michal Ambroz - 4.1.3-1 - bump the python-yara as well to 4.1.3 * Fri Jul 23 2021 Fedora Release Engineering - 4.1.0-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild * Fri Jun 4 2021 Python Maint - 4.1.0-2 - Rebuilt for Python 3.10 References: [ 1 ] Bug #1963945 - yara-4.1.3 is available https://bugzilla.redhat.com/show_bug.cgi?id=1963945 [ 2 ] Bug #1997121 - python-yara-4.1.3 is available https://bugzilla.redhat.com/show_bug.cgi?id=1997121 wordpress-5.1.11-1.el7 (FEDORA-EPEL-2021-6d0e7309d6) Blog tool and publishing platform Update Information: WordPress 5.1.11 Security Release ChangeLog: * Thu Nov 11 2021 Remi Collet - 5.1.11-1 - WordPress 5.1.11 Security Release
Re: Action required: Account system IRC pointer reset
> > I wonder, which mailing list was your original / first message (the > > announcement, I think?) in this thread sent to? Is there a mailing > > list archive link for it? > > Because I seem to be missing the actual announcement mail with all > > the > > details from my mail inbox, only subsequent responses are here. > > It went to annou...@lists.fedoraproject.org, but I guess I should > have > also sent it to devel-announce? mattdm has suggested that we need > something like a 'contributor-announce' for things like this. > > https://lists.fedoraproject.org/archives/list/annou...@lists.fedoraproject.org/thread/DK2DYBB3JZW4J3KUYREEEC42Z4D3IPP2/ > > kevin Thanks for clearing that up! I had the same thought. -- Maxwell G (@gotmax23) Pronouns: He/Him/His PGP Key Fingerprint: f57c76e5a238fe0a628e2ecef79e4e25e8c661f8 gotmax@e.email signature.asc Description: This is a digitally signed message part ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2022551] New: perl-HTTP-Message-6.35 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2022551 Bug ID: 2022551 Summary: perl-HTTP-Message-6.35 is available Product: Fedora Version: rawhide Status: NEW Component: perl-HTTP-Message Keywords: FutureFeature, Triaged Assignee: mspa...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: mspa...@redhat.com, perl-devel@lists.fedoraproject.org, ppi...@redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 6.35 Current version/release in rawhide: 6.33-2.fc35 URL: http://search.cpan.org/dist/HTTP-Message/ 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://fedoraproject.org/wiki/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/2977/ -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2022551 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] KDE Status in EPEL8
The qt5 libraries in RHEL 8.5 are at a higher version than they were in RHEL 8.4. This is causing RHEL 8 machines that have the KDE Plasma Desktop unable to do an update due to qt5 version dependencies. A rebuild of the KDE Plasma Desktop in EPEL8 is currently underway. It usually takes 3-4 days for all the packages to be rebuilt, as long as the builders co-operate. We expect the packages to be in epel8-testing by Monday, November 15. Thank you for your patience. Troy Dawson ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
License change: jacktrip
Hi, I'm working on updating jacktrip from 1.3.0 to 1.4.1. License changes: MIT -> MIT and GPLv3 and LGPLv3. Regards, -- Iñaki Úcar ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2022402] Please branch and build an epel8 for perl-Net-Telnet
https://bugzilla.redhat.com/show_bug.cgi?id=2022402 Carl George 鸞 changed: What|Removed |Added Blocks||1766676 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1766676 [Bug 1766676] Smokeping in EPEL8 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2022402 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2022400] Please branch and build an epel8 for perl-Config-Grammar
https://bugzilla.redhat.com/show_bug.cgi?id=2022400 Carl George 鸞 changed: What|Removed |Added Blocks||1766676 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1766676 [Bug 1766676] Smokeping in EPEL8 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2022400 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Package FFMPEG with royalty free codes (AV1, THEORA, VPX, OGG, OPUS, SPEEX, ...) for Fedora
Vitaly Zaitsev via devel wrote: > On 10/11/2021 16:33, Lyes Saadi wrote: >> I could even imagine someone creating a repo (not in COPR hopefully, due >> to legal issues) replacing in proprietary apps like Discord (or Slack >> which happens to be relevant to other discussions here) the bundled >> electron with Fedora's making things like Desktop sharing (not sure if >> it requires more changes) and Wayland working natively, packaged in a >> convenient RPM, a bit like what is currently available in the AUR. > > Proprietary apps don't allow patching of their code. Recently discussed > in #flatpak:matrix.org. You would not actually be patching the proprietary code, but the bundled Electron. Considering that essential parts of libchromiumcontent (the Blink code derived from WebKit, itself derived from KHTML) are under the LGPL, the proprietary applications are actually *required* to allow you to replace the LGPL library with a modified and/or updated version. If they attempt to sue you for it, *they* are violating the LGPL license of WebKit. (You will probably also be able to find some KDE developers whose LGPLed KHTML code ended up in Blink and who may be more willing to cooperate with you in the case of a lawsuit than Google or Apple.) Kevin Kofler ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Action required: Account system IRC pointer reset
On Thu, Nov 11, 2021 at 08:04:34PM +0100, Fabio Valentini wrote: > On Wed, Nov 10, 2021 at 8:41 PM Kevin Fenzi wrote: > > > > On Wed, Nov 10, 2021 at 08:40:32AM -0500, Stephen Gallagher wrote: > > > On Tue, Nov 9, 2021 at 5:36 PM Kevin Fenzi wrote: > > > > > > > > Greetings everyone. > > > > > > > > As you know, we migrated a while back from freenode.net to libera.chat > > > > for our IRC networks, > > > > and we also migrated to a new account system. After these moves, we > > > > would like to clear any > > > > IRC information that could be no longer correct and allow users to > > > > update their accounts > > > > with the correct information. > > > > > > > > The old Fedora account system had a ‘irc nick’ field. The new Fedora > > > > account system has > > > > a ‘Chat nicknames’ section. In that section you can put IRC nick(s) or > > > > Matrix Ids. > > > > If you do not qualify them, they are assumed to be for the libera.chat > > > > (IRC) and fedora.im (matrix) networks. > > > > > > > > Groups in both the old and new account system have a details section > > > > often containing links to mailing list and irc channel. > > > > > > > > On 2021-11-10 we are going to remove from the account system all users > > > > ‘Chat nicknames’ values > > > > and adjust all groups irc channel links from freenode.net to > > > > libera.chat. Users are encouraged > > > > to login after this time and enter their current and correct Chat > > > > nicknames. > > > > > > > > > > Will an additional announcement be going out once this change has been > > > applied, so we know when to update our nicks? > > > > Yes. This change is applied. Please update at your leasure. > > I wonder, which mailing list was your original / first message (the > announcement, I think?) in this thread sent to? Is there a mailing > list archive link for it? > Because I seem to be missing the actual announcement mail with all the > details from my mail inbox, only subsequent responses are here. It went to annou...@lists.fedoraproject.org, but I guess I should have also sent it to devel-announce? mattdm has suggested that we need something like a 'contributor-announce' for things like this. https://lists.fedoraproject.org/archives/list/annou...@lists.fedoraproject.org/thread/DK2DYBB3JZW4J3KUYREEEC42Z4D3IPP2/ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Action required: Account system IRC pointer reset
On Wed, Nov 10, 2021 at 8:41 PM Kevin Fenzi wrote: > > On Wed, Nov 10, 2021 at 08:40:32AM -0500, Stephen Gallagher wrote: > > On Tue, Nov 9, 2021 at 5:36 PM Kevin Fenzi wrote: > > > > > > Greetings everyone. > > > > > > As you know, we migrated a while back from freenode.net to libera.chat > > > for our IRC networks, > > > and we also migrated to a new account system. After these moves, we would > > > like to clear any > > > IRC information that could be no longer correct and allow users to update > > > their accounts > > > with the correct information. > > > > > > The old Fedora account system had a ‘irc nick’ field. The new Fedora > > > account system has > > > a ‘Chat nicknames’ section. In that section you can put IRC nick(s) or > > > Matrix Ids. > > > If you do not qualify them, they are assumed to be for the libera.chat > > > (IRC) and fedora.im (matrix) networks. > > > > > > Groups in both the old and new account system have a details section > > > often containing links to mailing list and irc channel. > > > > > > On 2021-11-10 we are going to remove from the account system all users > > > ‘Chat nicknames’ values > > > and adjust all groups irc channel links from freenode.net to libera.chat. > > > Users are encouraged > > > to login after this time and enter their current and correct Chat > > > nicknames. > > > > > > > Will an additional announcement be going out once this change has been > > applied, so we know when to update our nicks? > > Yes. This change is applied. Please update at your leasure. I wonder, which mailing list was your original / first message (the announcement, I think?) in this thread sent to? Is there a mailing list archive link for it? Because I seem to be missing the actual announcement mail with all the details from my mail inbox, only subsequent responses are here. Fabio ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Change: Package information on ELF objects (System-Wide Change proposal)
On Thu, Nov 11, 2021 at 07:02:10PM +0100, Florian Weimer wrote: > * Lennart Poettering: > > > And I think that's a *good* thing: JSON might not be perfect — because > > nothing is —, but it's certainly one of the better designed generic > > data formats around, and it's complexity is absolutely managable. > > Number handling in JSON is underspecified, and some variants (including > the original one) are not exactly easy to implement. I assume you > simply don't use numbers in the data? Not really, it's just strings so far. Even versions are not numbers, because of dots and letters. I can imagine we could maybe use integers for something in the future (epochs? compat versions?), but those would be small numbers, so nothing that could cause problems. Zbyszek ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Change: Package information on ELF objects (System-Wide Change proposal)
* Lennart Poettering: > And I think that's a *good* thing: JSON might not be perfect — because > nothing is —, but it's certainly one of the better designed generic > data formats around, and it's complexity is absolutely managable. Number handling in JSON is underspecified, and some variants (including the original one) are not exactly easy to implement. I assume you simply don't use numbers in the data? Thanks, Florian ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2022468] New: perl-IO-Async-0.800 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2022468 Bug ID: 2022468 Summary: perl-IO-Async-0.800 is available Product: Fedora Version: rawhide Status: NEW Component: perl-IO-Async Keywords: FutureFeature, Triaged Assignee: emman...@seyman.fr Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: emman...@seyman.fr, kwiz...@gmail.com, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Latest upstream release: 0.800 Current version/release in rawhide: 0.79-1.fc35 URL: http://search.cpan.org/dist/IO-Async 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://fedoraproject.org/wiki/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/7999/ -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2022468 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Change: Package information on ELF objects (System-Wide Change proposal)
On Di, 09.11.21 10:14, Fedora Development ML (devel@lists.fedoraproject.org) wrote: > On 08/11/2021 22:24, Lennart Poettering wrote: > > And I think that's a*good* thing: JSON might not be perfect — because > > nothing is —, but it's certainly one of the better designed generic > > data formats around, and it's complexity is absolutely managable. > > What about YAML? Complexity is a scale. YAML is certainly more complex than JSON, given it's a true superset of it. One generally should prefer the simplest format – as long as it provides the requirements we have here. The requirements we have in mind are fulfilled by both YAML and JSON (i.e. self-descriptiveness, extensibility, well understood, with established parsers and so on). But there's no requirement we have in mind that would be fulfilled by YAML but not by JSON as well. Hence JSON it is, and YAML is not. Lennart -- Lennart Poettering, Berlin ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Bodhi critpath package updates now gated on openQA results
On Tue, 2021-05-18 at 08:26 -0500, Michael Catanzaro wrote: > You reported my complaints as: > https://github.com/fedora-infra/bodhi/issues/4219. Thanks! > > I'm going to go ahead and ask that the gating be turned off until it's > fixed. If it doesn't display accurate test results, it's not even close > to being ready yet. Good gating is good, but bad gating is worse than > no gating. Hey again folks! It's been a while, but I wanted to note that Bodhi 5.7.1 with all my changes related to this and other issues that came up to do with update gating is now deployed in production. I checked and so far it *seems* like everything is working. The status ping-pong on update creation doesn't happen, and status is being correctly updated in response to new results. I hope you'll find it better now. Please let me know if you see any problems. Note that openQA update tests are currently failing unpredictably due to https://pagure.io/fedora-infrastructure/issue/9234 ; I'm re-firing them as I notice them, and I will take a look at the tests and see if there's anything I can do to try and mitigate the problem (fiddle with the retries or something). -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha 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 on the list, report it: https://pagure.io/fedora-infrastructure
python-absl-py 1.0.0 coming to Rawhide with a license change
In one week (2021-11-18), or slightly later, I will merge and build https://src.fedoraproject.org/rpms/python-absl-py/pull-request/1, updating python-absl-py to 1.0.0 in Rawhide. In this release, upstream drops support for obsolete Python versions (<3.6). This means the “absl.third_party.unittest3_backport” code is no longer needed and has been removed. This is technically a breaking API change—thus this advance notice—but I do not expect it to affect anyone in practice. Furthermore, the license changes from “ASL 2.0 and Python” to “ASL 2.0”, since the unittest3_backport code was the Python-licensed part of the package. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
License for “jo” simplified to “GPLv2”
I have simplified the License for the “jo” package from “GPLv2+ and MIT and Public Domain” to the effective license “GPLv2+”. A spec file comment explains: # The entire source is GPLv2+, except json.c and json.h, which are MIT, # and base64.c and base64.h, which are Public Domain. Since these files # are only used as sources for an executable with an effective license # of GPLv2+, the overall package license remains GPLv2+. The MIT-licensed files json.* are a slightly forked version of the copylib ccan-json, and are properly handled under the bundling guidelines. The public-domain files base64.* look like a copylib too, but I was never able to identify anywhere from which it might have been copied. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2022443] New: perl-PDL-2.061 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2022443 Bug ID: 2022443 Summary: perl-PDL-2.061 is available Product: Fedora Version: rawhide Status: NEW Component: perl-PDL Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: caillon+fedoraproj...@gmail.com, jakub.jedel...@gmail.com, jples...@redhat.com, ka...@ucw.cz, lkund...@v3.sk, perl-devel@lists.fedoraproject.org, rhug...@redhat.com, rstr...@redhat.com, sandm...@redhat.com, tjczep...@gmail.com Target Milestone: --- Classification: Fedora Latest upstream release: 2.061 Current version/release in rawhide: 2.57.0-1.fc36 URL: http://search.cpan.org/dist/PDL/ 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://fedoraproject.org/wiki/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/3205/ -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2022443 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2022402] Please branch and build an epel8 for perl-Net-Telnet
https://bugzilla.redhat.com/show_bug.cgi?id=2022402 --- Comment #2 from Stephen John Smoogen --- my punishment for starting a good deed for a third party :). -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2022402 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Package FFMPEG with royalty free codes (AV1, THEORA, VPX, OGG, OPUS, SPEEX, ...) for Fedora
On Thursday, November 11, 2021 11:28:42 AM CET Vitaly Zaitsev via devel wrote: > On 11/11/2021 11:08, Andreas Schneider wrote: > > > I'm packaging Signal-Desktop completely built from source. > > > https://build.opensuse.org/package/view_file/network:im:signal/signal-deskto > p/prepare_vendor.sh?expand=1 > Does this script simply download assets from npm using the "yarn > install" command? Does it look like it only calls 'yarn install' and does nothing else? Maybe look through the "echo" commands to see what it does. Are you looking for the `echo ">> Cleanup object files"` section? ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2022402] Please branch and build an epel8 for perl-Net-Telnet
https://bugzilla.redhat.com/show_bug.cgi?id=2022402 Robin Lee changed: What|Removed |Added Assignee|robinlee.s...@gmail.com |smo...@redhat.com --- Comment #1 from Robin Lee --- I give main admin to you. I don't actually use this package any more. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2022402 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2022402] New: Please branch and build an epel8 for perl-Net-Telnet
https://bugzilla.redhat.com/show_bug.cgi?id=2022402 Bug ID: 2022402 Summary: Please branch and build an epel8 for perl-Net-Telnet Product: Fedora Version: rawhide Status: NEW Component: perl-Net-Telnet Assignee: robinlee.s...@gmail.com Reporter: smo...@redhat.com QA Contact: extras...@fedoraproject.org CC: perl-devel@lists.fedoraproject.org, robinlee.s...@gmail.com Target Milestone: --- Classification: Fedora Description of problem: Version-Release number of selected component (if applicable): Please branch and build perl-Net-Telnet in epel8. If you do not wish to maintain perl-Net-Telnet in epel8, or do not think you will be able to do this in a timely manner, I would be happy to be a co-maintainer of the package. I have tested a build and perl-Net-Telnet-3.05-2.fc35.src.rpm currently builds clean in EPEL8 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2022402 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2022400] New: Please branch and build an epel8 for perl-Config-Grammar
https://bugzilla.redhat.com/show_bug.cgi?id=2022400 Bug ID: 2022400 Summary: Please branch and build an epel8 for perl-Config-Grammar Product: Fedora EPEL Version: epel8 Status: NEW Component: perl-Config-Grammar Assignee: shelt...@fedoraproject.org Reporter: smo...@redhat.com QA Contact: extras...@fedoraproject.org CC: fed...@mickweiss.com, jper...@centos.org, perl-devel@lists.fedoraproject.org, shelt...@fedoraproject.org, terje...@phys.ntnu.no Target Milestone: --- Classification: Fedora Description of problem: Please branch and build perl-Config-Grammar in epel8. If you do not wish to maintain perl-Config-Grammar in epel8, or do not think you will be able to do this in a timely manner, I would be happy to be a co-maintainer of the package. [I have tested that the package will build in EPEL-8 and it currently builds in mock without errors.] -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2022400 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
libnsl.so.2.0.1 updated to libnsl.so.3.0.0 without coordination, broke rawhide
Hello, Since this update: https://src.fedoraproject.org/rpms/libnsl2/c/d2e2fab5e3ab07228a34f35ab8ec1954581153d0?branch=rawhide Nothing in rawhide builds, because Python and hence dnf is not installable: Error: Problem 1: package python3-dnf-4.10.0-1.fc36.noarch requires python3-libdnf, but none of the providers can be installed - package python3-dnf-4.10.0-1.fc36.noarch requires python3-libdnf >= 0.65.0, but none of the providers can be installed - package dnf-4.10.0-1.fc36.noarch requires python3-dnf = 4.10.0-1.fc36, but none of the providers can be installed - package python3-libdnf-0.65.0-1.fc36.ppc64le requires libpython3.10.so.1.0()(64bit), but none of the providers can be installed - conflicting requests - nothing provides libnsl.so.2()(64bit) needed by python3-libs-3.10.0-3.fc36.ppc64le - nothing provides libnsl.so.2(LIBNSL_1.0)(64bit) needed by python3-libs-3.10.0-3.fc36.ppc64le Problem 2: package python3-dnf-plugins-core-4.0.24-1.fc36.noarch requires python3-hawkey >= 0.46.1, but none of the providers can be installed - package dnf-plugins-core-4.0.24-1.fc36.noarch requires python3-dnf-plugins-core = 4.0.24-1.fc36, but none of the providers can be installed - package python3-hawkey-0.65.0-1.fc36.ppc64le requires libpython3.10.so.1.0()(64bit), but none of the providers can be installed - conflicting requests - nothing provides libnsl.so.2()(64bit) needed by python3-libs-3.10.0-3.fc36.ppc64le - nothing provides libnsl.so.2(LIBNSL_1.0)(64bit) needed by python3-libs-3.10.0-3.fc36.ppc64le (try to add '--skip-broken' to skip uninstallable packages) Additionally, the following packages (and everything that depends on them) will fail to install: $ repoquery -q --repo=rawhide --whatrequires 'libnsl.so.2()(64bit)' autofs-1:5.1.8-1.fc36.x86_64 exim-0:4.95-1.fc36.x86_64 exim-mon-0:4.95-1.fc36.x86_64 libnsl2-devel-0:1.3.0-4.fc35.x86_64 nss_nis-0:3.1-9.fc35.x86_64 pam-0:1.5.2-6.fc36.x86_64 postfix-2:3.6.2-6.fc36.x86_64 python2.7-0:2.7.18-15.fc36.x86_64 python3-debug-0:3.10.0-2.fc36.x86_64 python3-libs-0:3.10.0-2.fc36.x86_64 python3.11-0:3.11.0~a1-1.fc36.x86_64 python3.6-0:3.6.15-2.fc36.x86_64 python3.7-0:3.7.12-2.fc36.x86_64 python3.8-0:3.8.12-2.fc36.x86_64 python3.9-0:3.9.8-1.fc36.x86_64 rwall-0:0.17-60.fc35.x86_64 rwall-server-0:0.17-60.fc35.x86_64 sendmail-0:8.17.1-2.fc36.x86_64 slapi-nis-0:0.56.7-2.fc35.x86_64 tcp_wrappers-0:7.6-98.fc35.x86_64 tcp_wrappers-libs-0:7.6-98.fc35.x86_64 yp-tools-0:4.2.3-10.fc35.x86_64 ypbind-3:2.7.2-5.fc35.x86_64 ypserv-0:4.2-1.fc36.x86_64 I've requested the package to be untagged: https://pagure.io/releng/issue/10380 This change needs to be coordinated. -- 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Action required: Account system IRC pointer reset
On 11/11/2021 14:48, Dominik 'Rathann' Mierzejewski wrote: But SSO is not working. It opens a browser window to log in via id.fedoraproject.org, but then the nheko window shows an error: "Failed to setup encryption keys. Server response: One time key signed_curve25519:CA already exists." Please report this issue to upstream: https://github.com/Nheko-Reborn/nheko/issues -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2019189] Upgrade perl-Config-Model to 2.145
https://bugzilla.redhat.com/show_bug.cgi?id=2019189 Jitka Plesnikova changed: What|Removed |Added Assignee|david.hanneq...@gmail.com |jples...@redhat.com Fixed In Version||perl-Config-Model-2.145-1.f ||c36 Resolution|--- |RAWHIDE Status|NEW |CLOSED Last Closed||2021-11-11 14:45:11 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2019189 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Change: ELN-Extras (System-Wide Change proposal)
On Thu, Nov 11, 2021 at 9:31 AM Miro Hrončok wrote: > > On 11. 11. 21 15:24, Ben Cotton wrote: > > anyone > > who wants to have a package appear in ELN-Extras will need to add it > > to the content set. > > I have some questions: > > 1) How does anyone add a package to the ELN-Extras content set? They will need to submit a merge request against https://github.com/minimization/content-resolver-input > 2) Who exactly is "anyone"? E.g. can non-packager users do this? > 3) Are there any rules or guidelines for including new packages? Suppose an > user wants to add everything, would that be allowed? The format for the content set additions includes a requirement to specify the maintainer for the content. If one person wants to add every package... they become responsible for maintaining every package in ELN. Realistically, all MRs against the content set will be reviewed by the ELN SIG for suitability. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Change: ELN-Extras (System-Wide Change proposal)
On 11. 11. 21 15:24, Ben Cotton wrote: anyone who wants to have a package appear in ELN-Extras will need to add it to the content set. I have some questions: 1) How does anyone add a package to the ELN-Extras content set? 2) Who exactly is "anyone"? E.g. can non-packager users do this? 3) Are there any rules or guidelines for including new packages? Suppose an user wants to add everything, would that be allowed? -- 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 on the list, report it: https://pagure.io/fedora-infrastructure
F36 Change: ELN-Extras (System-Wide Change proposal)
https://fedoraproject.org/wiki/Changes/ELN-Extras == Summary == ELN-extras will be a new build target and compose similar in behavior to ELN, but closer to EPEL in function. It will be a place to prepare and maintain packages that may be desired for EPEL N+1 while RHEL N+1 is still being incubated in ELN. == Owner == * Owner: [[User:Sgallagh| Stephen Gallagher]] * SIG: ELN SIG == Detailed Description == This will essentially be an extension of Fedora ELN, with the primary difference being that the content in ELN-Extras will be defined by the Fedora/EPEL community, while ELN's content is largely decided upon by Red Hat management. This will offer users the opportunity to make sure their applications will work on upcoming releases of RHEL as well as providing a bootstrapping mechanism for EPEL. It will be far easier and quicker to get a compose of EPEL N+1 out the door if the initial packages have already been built for ELN-Extras. == Benefit to Fedora == This Change will enable application developers to keep up with impending changes in RHEL even before CentOS Stream becomes available for that release. Additionally, it provides a bootstrapping mechanism for EPEL, which will mean a much shorter gap between the launch of a new RHEL major release and the availability of the EPEL repositories. == Scope == * Proposal owners: High-level tasks 1. Create the tags and targets in Koji (see the release engineering ticket below). 2. Add support to Content Resolver for addon repositories [DONE] 3. Update the DistroBuildSync configuration to support building for ELN-Extras. 4. Configure ODCS to produce an ELN-Extras variant compose. * Other developers: Aside from the release engineering tasks, anyone who wants to have a package appear in ELN-Extras will need to add it to the content set. This is not mandatory for any packager and we can ship the ELN-Extras repository empty if we so choose. * Release engineering: [https://pagure.io/releng/issues #10378] * Policies and guidelines: N/A (not needed for this Change) Documentation on how to add packages to the ELN-Extras content set and how to consume its compose will be written as part of this Change. * Trademark approval: N/A (not needed for this Change) * Alignment with Objectives: Not specifically aligned with the currently-active Objectives. Loosely related to the previous Minimization Objective. == Upgrade/compatibility impact == N/A, this will be an entirely new compose and thus has nothing from which to upgrade. == How To Test == No specific testing is required for this Change, though any general OS and software management testing would be most welcome. == User Experience == Fedora will make available a new add-on repository for ELN, maintained by the Fedora Community. == Dependencies == This should be self-contained from a dependency perspective. The groundwork was already laid by ELN. == Contingency Plan == * Contingency mechanism: We will not ship/advertise the existence of the ELN-Extras repository. * Contingency deadline: Final freeze * Blocks release? No == Documentation == Documentation will be written as part of this Change. -- 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 on the list, report it: https://pagure.io/fedora-infrastructure
F36 Change: ELN-Extras (System-Wide Change proposal)
https://fedoraproject.org/wiki/Changes/ELN-Extras == Summary == ELN-extras will be a new build target and compose similar in behavior to ELN, but closer to EPEL in function. It will be a place to prepare and maintain packages that may be desired for EPEL N+1 while RHEL N+1 is still being incubated in ELN. == Owner == * Owner: [[User:Sgallagh| Stephen Gallagher]] * SIG: ELN SIG == Detailed Description == This will essentially be an extension of Fedora ELN, with the primary difference being that the content in ELN-Extras will be defined by the Fedora/EPEL community, while ELN's content is largely decided upon by Red Hat management. This will offer users the opportunity to make sure their applications will work on upcoming releases of RHEL as well as providing a bootstrapping mechanism for EPEL. It will be far easier and quicker to get a compose of EPEL N+1 out the door if the initial packages have already been built for ELN-Extras. == Benefit to Fedora == This Change will enable application developers to keep up with impending changes in RHEL even before CentOS Stream becomes available for that release. Additionally, it provides a bootstrapping mechanism for EPEL, which will mean a much shorter gap between the launch of a new RHEL major release and the availability of the EPEL repositories. == Scope == * Proposal owners: High-level tasks 1. Create the tags and targets in Koji (see the release engineering ticket below). 2. Add support to Content Resolver for addon repositories [DONE] 3. Update the DistroBuildSync configuration to support building for ELN-Extras. 4. Configure ODCS to produce an ELN-Extras variant compose. * Other developers: Aside from the release engineering tasks, anyone who wants to have a package appear in ELN-Extras will need to add it to the content set. This is not mandatory for any packager and we can ship the ELN-Extras repository empty if we so choose. * Release engineering: [https://pagure.io/releng/issues #10378] * Policies and guidelines: N/A (not needed for this Change) Documentation on how to add packages to the ELN-Extras content set and how to consume its compose will be written as part of this Change. * Trademark approval: N/A (not needed for this Change) * Alignment with Objectives: Not specifically aligned with the currently-active Objectives. Loosely related to the previous Minimization Objective. == Upgrade/compatibility impact == N/A, this will be an entirely new compose and thus has nothing from which to upgrade. == How To Test == No specific testing is required for this Change, though any general OS and software management testing would be most welcome. == User Experience == Fedora will make available a new add-on repository for ELN, maintained by the Fedora Community. == Dependencies == This should be self-contained from a dependency perspective. The groundwork was already laid by ELN. == Contingency Plan == * Contingency mechanism: We will not ship/advertise the existence of the ELN-Extras repository. * Contingency deadline: Final freeze * Blocks release? No == Documentation == Documentation will be written as part of this 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: spec file error (updated)
Vitaly replied in this thread as well with other spec file changes you
need to make to align with current packaging guidelines. For
reference:
https://docs.fedoraproject.org/en-US/packaging-guidelines/
Other replies below...
On Wed, Nov 10, 2021 at 09:48:24PM +, Globe Trotter via devel wrote:
My apologies, i spoke too soon.
I updated Makefile.in to be:
install: gbuffy
./mkinstalldirs $(DESTDIR)$(bindir)
$(INSTALL) gbuffy $(DESTDIR)$(bindir)
Here is my updated spec file:
%define ver 0.2.8
%define rel 1%{?dist}
Summary: multiple mailbox buffy for GTK+
Name: gbuffy
Version: %ver
Release: %rel
License: GPL
The License value needs to match a license abbreviation from this page:
https://fedoraproject.org/wiki/Licensing:Main?rd=Licensing#SoftwareLicenses
For more information, see:
https://docs.fedoraproject.org/en-US/packaging-guidelines/LicensingGuidelines/
You may combine multiple short license names using the "and" and "or"
keywords. The packaging guidelines explain this in more detail.
Group: Applications/Communications
Source0: ~/C.libs/linux/%{name}-%{version}.tar.bz2
Source1: http://www.fiction.net/blong/programs/gbuffy/gbuffy-%{ver}.tar.gz
I don't understand what Source0 is here. Source0 should be the
upstream source archive. Then you should add a Patch0 patch that
makes the change to Makefile.in. The %autosetup macro in %prep will
apply that patch after unpacking Source0.
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-%(%{__id_u} -n)
URL: http://www.fiction.net/blong/programs/gbuffy
BuildRequires: libPropList
%description
GBuffy is a GTK+ multiple mailbox "biff" program. It is conceptually
based on XBuffy by Bill Pemberton, but is a complete rewrite from
scratch.
GBuffy will poll multiple mailboxes for new mail. It will list the
number of new messages in each mailbox you configure. It will also
highlight the mailboxes which have new mail.
GBuffy is currently capable of watching MBOX, MMDF, Maildir and MH
Folders. This version also supports IMAP4rev1 and NNTP with XOVER
mailboxes.
%prep
%setup -q
%configure
%make_build
%install
%make_install
%files
%defattr(-,root,root,-)
%doc CHANGES README
%license LICENSE
%{_bindir}/%{name}
%clean
However, I still have some problems:
...
+ cd gbuffy-0.2.8
+ /usr/bin/make install
DESTDIR=/home/rpmbuild/BUILDROOT/gbuffy-0.2.8-1.fc35.x86_64
'INSTALL=/usr/bin/install -p'
./mkinstalldirs /home/rpmbuild/BUILDROOT/gbuffy-0.2.8-1.fc35.x86_64/usr/bin
make: ./mkinstalldirs: Permission denied
make: *** [Makefile:50: install] Error 127
error: Bad exit status from /var/tmp/rpm-tmp.QLLNwm (%install)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.QLLNwm (%install)
Is there something I did not do correctly?
Many thanks!
___
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 on the list, report it:
https://pagure.io/fedora-infrastructure
--
David Cantrell
Red Hat, Inc. | Boston, MA | EST5EDT
___
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 on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Action required: Account system IRC pointer reset
On Thursday, 11 November 2021 at 09:21, Vitaly Zaitsev via devel wrote: > On 10/11/2021 23:09, Dominik 'Rathann' Mierzejewski wrote: > > ... and support encrypted chats, I forgot to add. > > nheko support E2EE. But SSO is not working. It opens a browser window to log in via id.fedoraproject.org, but then the nheko window shows an error: "Failed to setup encryption keys. Server response: One time key signed_curve25519:CA already exists." Deleting ~/.cache/nheko and .config/nheko doesn't help. Regards, Dominik -- Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2019189] Upgrade perl-Config-Model to 2.145
https://bugzilla.redhat.com/show_bug.cgi?id=2019189 Jitka Plesnikova changed: What|Removed |Added Summary|Upgrade perl-Config-Model |Upgrade perl-Config-Model |to 2.143|to 2.145 --- Comment #1 from Jitka Plesnikova --- Latest Fedora delivers 2.142 version. Upstream released 2.145. When you have free time, please upgrade it. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2019189 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2005973] perl-Crypt-OpenSSL-PKCS10: FTBFS with OpenSSL 3.0 .0 in Fedora Rawhide
https://bugzilla.redhat.com/show_bug.cgi?id=2005973 Petr Pisar changed: What|Removed |Added CC||sah...@redhat.com --- Comment #1 from Petr Pisar --- *** Bug 2021948 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2005973 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2021948] perl-Crypt-OpenSSL-PKCS10: FTBFS with OpenSSL 3.0.0
https://bugzilla.redhat.com/show_bug.cgi?id=2021948 Petr Pisar changed: What|Removed |Added Resolution|--- |DUPLICATE CC||ppi...@redhat.com Status|NEW |CLOSED Last Closed||2021-11-11 11:38:45 --- Comment #1 from Petr Pisar --- *** This bug has been marked as a duplicate of bug 2005973 *** -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2021948 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2005979] perl-Crypt-OpenSSL-RSA: FTBFS with OpenSSL 3.0.0 in Fedora Rawhide
https://bugzilla.redhat.com/show_bug.cgi?id=2005979 Petr Pisar changed: What|Removed |Added CC||sah...@redhat.com --- Comment #1 from Petr Pisar --- *** Bug 2021945 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2005979 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2021945] perl-Crypt-OpenSSL-RSA: FTBFS with OpenSSL 3.0.0
https://bugzilla.redhat.com/show_bug.cgi?id=2021945 Petr Pisar changed: What|Removed |Added CC||ppi...@redhat.com Status|NEW |CLOSED Resolution|--- |DUPLICATE Last Closed||2021-11-11 11:37:44 --- Comment #1 from Petr Pisar --- *** This bug has been marked as a duplicate of bug 2005979 *** -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2021945 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2007247] perl-Crypt-SSLeay-0.72-32.fc36 FTBFS with OpenSSL 3: SSLeay.so: undefined symbol: SSLv3_client_method
https://bugzilla.redhat.com/show_bug.cgi?id=2007247 Petr Pisar changed: What|Removed |Added CC||sah...@redhat.com --- Comment #1 from Petr Pisar --- *** Bug 2021942 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2007247 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2021942] perl-Crypt-SSLeay: FTBFS with OpenSSL 3.0.0
https://bugzilla.redhat.com/show_bug.cgi?id=2021942 Petr Pisar changed: What|Removed |Added Resolution|--- |DUPLICATE CC||ppi...@redhat.com Status|NEW |CLOSED Last Closed||2021-11-11 11:36:20 --- Comment #1 from Petr Pisar --- *** This bug has been marked as a duplicate of bug 2007247 *** -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2021942 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
CPE Weekly Update – Week of November 08th – 12nd
Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/). If you wish to read this in form of a blog post, check the post on Fedora community blog: https://communityblog.fedoraproject.org/cpe-weekly-update-week-of-november-08th-12nd/ # Highlights of the week ## Infrastructure & Release Engineering Goal of this Initiative --- Purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work. It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.). The ARC (which is a subset of the team) investigates possible initiatives that CPE might take on. Update -- ### Fedora Infra * Out of freeze, merged a bunch of post freeze work, more to come * Dnssec records finally fully updated away from sha-1 * Ibiblio hosts ipv6 all moved off old net/block * Attempted to move s390x builders to new mainframe, but hit issues, going to try again next week. * Fedora koji upgraded to latest upstream ### CentOS Infra including CentOS CI * Business as usual ### Release Engineering * Epel 9 next is in bodhi * New side tag for f35-kde * Business as usual ## CentOS Stream Goal of this Initiative --- This initiative is working on CentOS Stream/Emerging RHEL to make this new distribution a reality. The goal of this initiative is to prepare the ecosystem for the new CentOS Stream. Updates --- * We’ve updated RHEL 9 branching images in Dev Guide * Working on documentation and tidying up docs locations on the compose reporting work showing the diffs between RHEL/c8s/c9s composes * Package additions from RHEL appstream coming through to be added to CentOS Stream repos * Content resolver logic has been reviewed and re-written to accommodate a new buildroot functionality and working through adding package placeholders ## CentOS Duffy CI Goal of this Initiative --- Duffy is a system within CentOS CI Infra which allows tenants to provision and access bare metal resources of multiple architectures for the purposes of CI testing. We need to add the ability to checkout VMs in CentOS CI in Duffy. We have OpenNebula hypervisor available, and have started developing playbooks which can be used to create VMs using the OpenNebula API, but due to the current state of how Duffy is deployed, we are blocked with new dev work to add the VM checkout functionality. Updates --- * Finished Work In Progress from last week * Logging * Database model * Configuration Framework * Tests started working successfully on Python 3.10, by magic! Test against Python 3.6 ~ 3.10 in CI. * Work In Progress * API endpoints for all the things * Planning delegating to bare metal and OpenNebula (VMs) ## FCOS OpenShift migration Goal of this Initiative --- Move current Fedora CoreOS pipeline from the centos-ci OCP4 cluster to the newly deployed fedora infra OCP4 cluster. Updates --- * New Openshift role sysadmin-openshift to handle installation/configuration of OCP 4 tasks * Added oc client for ocp4 to the batcave01 PR * Pushed changes to allow connections from batcave01 to the ocp4 cluster, follow on ticket opened with RH IT to open ports in firewall also. ## EPEL Goal of this initiative --- Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL). EPEL packages are usually based on their Fedora counterparts and will never conflict with or replace packages in the base Enterprise Linux distributions. EPEL uses much of the same infrastructure as Fedora, including buildsystem, bugzilla instance, updates manager, mirror manager and more. Updates --- * Fedora s390x builder migration was not successful, had to be rolled back and rescheduled, so epel9-next is still blocked * Epel9-next has been added to bodhi, allowing us to test the push pipeline with noarch packages (epel-release and epel-rpm-macros) * Additional ancillary work in mock-core-configs, bodhi, and fedpkg Kindest regards, CPE Team ___ 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
Re: Package FFMPEG with royalty free codes (AV1, THEORA, VPX, OGG, OPUS, SPEEX, ...) for Fedora
On Thu, 2021-11-11 at 11:08 +0100, Andreas Schneider wrote: > On Wednesday, November 10, 2021 11:27:32 AM CET Vitaly Zaitsev via > devel > wrote: > > On 10/11/2021 09:44, Andreas Schneider wrote: > > > > > I'm sorry, but didn't we talk about electron and you're pointing > > > to > > > vscode? > > > > My previous message was: > > > > > > > Electron core packaging is a quite trivial task (Arch Linux and > > > Debian have already done this), but what about Electron > > > applications > > > (VS Code for example)? > > > > By the way, which Electron app do you want to package? > > I'm packaging Signal-Desktop completely built from source. > > https://build.opensuse.org/package/show/network:im:signal/ https://build.opensuse.org/project/show/network:im:signal https://build.opensuse.org/package/view_file/network:im:signal/signal-desktop/prepare_vendor.sh -- 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Package FFMPEG with royalty free codes (AV1, THEORA, VPX, OGG, OPUS, SPEEX, ...) for Fedora
On 11/11/2021 11:08, Andreas Schneider wrote: I'm packaging Signal-Desktop completely built from source. https://build.opensuse.org/package/view_file/network:im:signal/signal-desktop/prepare_vendor.sh?expand=1 Does this script simply download assets from npm using the "yarn install" command? -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Package FFMPEG with royalty free codes (AV1, THEORA, VPX, OGG, OPUS, SPEEX, ...) for Fedora
I wonder what is Slack's TOS? Maybe with their approval, a COPR could be maintained without any issue? COPR can't be used for building non-free software: https://docs.pagure.org/copr.copr/user_documentation.html#what-i-can-build-in-copr Indeed, forgot about that when writing my e-mail ^^'! I guess someone volunteering to properly package it in RPM Fusion could do it (if they got Slack's approval), since Slack seems to be no longer willing to ship it themselves. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Package FFMPEG with royalty free codes (AV1, THEORA, VPX, OGG, OPUS, SPEEX, ...) for Fedora
On Wednesday, November 10, 2021 3:39:42 PM CET Vitaly Zaitsev via devel wrote: > > Keep mislead people and twisting things if this helps you with packaging > > electron apps on Fedora. > > I think it will be very difficult or even impossible to build Electron > apps completely from sources without using pre-built assets from npm (or > parsing and downloading content from yarn.lock). It is a pain, but doable. I have it working for Signal-Desktop. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Package FFMPEG with royalty free codes (AV1, THEORA, VPX, OGG, OPUS, SPEEX, ...) for Fedora
On Wednesday, November 10, 2021 11:27:32 AM CET Vitaly Zaitsev via devel wrote: > On 10/11/2021 09:44, Andreas Schneider wrote: > > > I'm sorry, but didn't we talk about electron and you're pointing to > > vscode? > > My previous message was: > > > > Electron core packaging is a quite trivial task (Arch Linux and > > Debian have already done this), but what about Electron applications > > (VS Code for example)? > > By the way, which Electron app do you want to package? I'm packaging Signal-Desktop completely built from source. https://build.opensuse.org/package/show/network:im:signal/ ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Cloud-34-20211111.0 compose check report
No missing expected images. Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-34-20211109.0): ID: 1061027 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/1061027 ID: 1061036 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1061036 Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Rawhide-20211111.n.0 compose check report
No missing expected images. Compose FAILS proposed Rawhide gating check! 3 of 43 required tests failed, 1 result missing openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 24/206 (x86_64), 14/141 (aarch64) New failures (same test not failed in Fedora-Rawhide-20211109.n.0): ID: 1060578 Test: x86_64 Server-dvd-iso install_btrfs_preserve_home URL: https://openqa.fedoraproject.org/tests/1060578 ID: 1060582 Test: x86_64 Server-dvd-iso install_btrfs_preserve_home_uefi@uefi URL: https://openqa.fedoraproject.org/tests/1060582 ID: 1060590 Test: x86_64 Server-dvd-iso install_resize_lvm URL: https://openqa.fedoraproject.org/tests/1060590 ID: 1060595 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller **GATING** URL: https://openqa.fedoraproject.org/tests/1060595 ID: 1060605 Test: x86_64 Server-dvd-iso realmd_join_sssd **GATING** URL: https://openqa.fedoraproject.org/tests/1060605 ID: 1060615 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart **GATING** URL: https://openqa.fedoraproject.org/tests/1060615 ID: 1060621 Test: x86_64 Server-dvd-iso realmd_join_cockpit URL: https://openqa.fedoraproject.org/tests/1060621 ID: 1060630 Test: x86_64 Workstation-live-iso desktop_login URL: https://openqa.fedoraproject.org/tests/1060630 ID: 1060641 Test: x86_64 Workstation-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/1060641 ID: 1060647 Test: x86_64 Workstation-live-iso evince URL: https://openqa.fedoraproject.org/tests/1060647 ID: 1060648 Test: x86_64 Workstation-live-iso gedit URL: https://openqa.fedoraproject.org/tests/1060648 ID: 1060651 Test: x86_64 KDE-live-iso desktop_notifications_live URL: https://openqa.fedoraproject.org/tests/1060651 ID: 1060669 Test: x86_64 KDE-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/1060669 ID: 1060678 Test: x86_64 Silverblue-dvd_ostree-iso evince URL: https://openqa.fedoraproject.org/tests/1060678 ID: 1060679 Test: x86_64 Silverblue-dvd_ostree-iso gedit URL: https://openqa.fedoraproject.org/tests/1060679 ID: 1060743 Test: aarch64 Server-dvd-iso realmd_join_cockpit@uefi URL: https://openqa.fedoraproject.org/tests/1060743 ID: 1060773 Test: aarch64 Workstation-raw_xz-raw.xz evince@uefi URL: https://openqa.fedoraproject.org/tests/1060773 ID: 1060809 Test: x86_64 universal install_european_language URL: https://openqa.fedoraproject.org/tests/1060809 ID: 1060810 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/1060810 ID: 1060816 Test: x86_64 universal install_arabic_language URL: https://openqa.fedoraproject.org/tests/1060816 ID: 1060825 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/1060825 ID: 1060860 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/1060860 ID: 1060915 Test: aarch64 Server-dvd-iso install_resize_lvm@uefi URL: https://openqa.fedoraproject.org/tests/1060915 Old failures (same test failed in Fedora-Rawhide-20211109.n.0): ID: 1060649 Test: x86_64 Workstation-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/1060649 ID: 1060660 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/1060660 ID: 1060668 Test: x86_64 KDE-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/1060668 ID: 1060705 Test: aarch64 Server-dvd-iso install_btrfs_preserve_home@uefi URL: https://openqa.fedoraproject.org/tests/1060705 ID: 1060707 Test: aarch64 Server-dvd-iso install_btrfs_preserve_home_uefi@uefi URL: https://openqa.fedoraproject.org/tests/1060707 ID: 1060724 Test: aarch64 Server-dvd-iso support_server@uefi URL: https://openqa.fedoraproject.org/tests/1060724 ID: 1060739 Test: aarch64 Server-dvd-iso install_repository_nfs_graphical@uefi URL: https://openqa.fedoraproject.org/tests/1060739 ID: 1060775 Test: aarch64 Workstation-raw_xz-raw.xz gedit@uefi URL: https://openqa.fedoraproject.org/tests/1060775 ID: 1060829 Test: x86_64 universal install_iscsi URL: https://openqa.fedoraproject.org/tests/1060829 ID: 1060873 Test: aarch64 universal install_arabic_language@uefi URL: https://openqa.fedoraproject.org/tests/1060873 ID: 1060880 Test: aarch64 universal install_european_language@uefi URL: https://openqa.fedoraproject.org/tests/1060880 ID: 1060881 Test: aarch64 universal install_iscsi@uefi URL: https://openqa.fedoraproject.org/tests/1060881 ID: 1060884 Test: aarch64 universal install_asian_language@uefi URL: https://openqa.fedoraproject.org/tests/1060884 ID: 1060893 Test: aarch64 universal upgrade_server_domain_controller@uefi URL: https://openqa.fedoraproject.org/tests/1060893 ID: 1060911 Test: aarch64 universal upgrade_realmd_client@uefi URL: https://openqa.fedoraproject.org/tests/1060911
Re: spec file error
Am Donnerstag, dem 11.11.2021 um 09:27 +0100 schrieb Vitaly Zaitsev via
devel:
> On 10/11/2021 21:15, Globe Trotter via devel wrote:
> > Version: %ver
> > Release: %rel
>
> You shouldn't use macroses here, because this behavior can break
> release
> bumps from different bots or proven-packager scripts.
I agree with you, that at least the macro for the package version should
be dropped. For the package release it is permittable to use
`baserelease` as a macro, as that is useable for `rpmdev-bumpspec`:
```
%global baserelease 1
Version: X.Y.Z
Release: %{baserelease}%{?dist}
```
Anyways, macros in the spec file must be defined using the expanded at
definition time `%global`, if there is no reasonable justification to
use the lazy-expanding `%define`.
signature.asc
Description: This is a digitally signed message part
___
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 on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Python RPM dependency generators and LegacyVersion, time to error?
On 04. 11. 21 12:49, Miro Hrončok wrote: Hello Pythonistas. After some recent improvements in the Python RPM dependency generators, a regression was discovered [0]. Turns out the error happened when the upstream metadata contained a requirement with a PEP 440 [1] incompatible version. A fix is pending and only one package in Fedora was affected. [...] tl;dr: - there might be cases where legacy versions are needed - but in most cases, they should be avoided Hence, I propose we do the following in Rawhide: We turn LegacyVersions to failures, but we provide a stop-gap measure, such as (%global python_dependency_allow_legacy_version_provides 1 / %global python_dependency_allow_legacy_version_requires 1 ) for packages that need to override this. When pypa/packaging actually drops LegacyVersion, this stop-gap measure will no longer work. I suggest removing LegacyVersion support without replacement. I think neither creating nor using "python_dependency_allow_legacy_version_requires" would be worth the extra work. All the uses of it that we've seen were mistakes, and since upstream tools are removing support for it, the stop-gap is just delaying the inevitable. If we find an actual use case for it, it can always be added. ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-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/python-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Cloud-35-20211111.0 compose check report
No missing expected images. Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-35-2020.0): ID: 1060944 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/1060944 ID: 1060953 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1060953 Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Package FFMPEG with royalty free codes (AV1, THEORA, VPX, OGG, OPUS, SPEEX, ...) for Fedora
On 10/11/2021 18:04, Lyes Saadi wrote: I wonder what is Slack's TOS? Maybe with their approval, a COPR could be maintained without any issue? COPR can't be used for building non-free software: https://docs.pagure.org/copr.copr/user_documentation.html#what-i-can-build-in-copr -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: spec file error
On 10/11/2021 21:15, Globe Trotter via devel wrote:
Version: %ver
Release: %rel
You shouldn't use macroses here, because this behavior can break release
bumps from different bots or proven-packager scripts.
Group: Applications/Communications
Legacy. Must be removed.
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-%(%{__id_u} -n)
Must be removed.
%setup -q
Can be replaced with %autosetup.
%{?ldconfig_scriptlets}
No longer used. Can be removed.
%defattr(-,root,root,-)
Legacy. Must be removed.
%clean
rm -rf %{buildroot}
Not allowed by modern Fedora guidelines. Must be removed.
--
Sincerely,
Vitaly Zaitsev (vit...@easycoding.org)
___
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 on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Action required: Account system IRC pointer reset
On 10/11/2021 23:09, Dominik 'Rathann' Mierzejewski wrote: ... and support encrypted chats, I forgot to add. nheko support E2EE. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
