Re: perl-MooX-Role-Parameterized orphaned
* Christian Walde [11/10/2024 12:05] : > > What do you mean it doesn't represent a problem? Just that. You are free to license your Perl distributions under whatever license you wish to use. This is a good thing. The only issue I had at one point was that I couldn't update perl-MooX-Role-Parameterized because one of its dependencies was not in Fedora (this is bug #2256220, FTR). This ceased to be an issue when I orphaned the package. > If it weren't a problem for you, as per fedora policies, then you > wouldn't have needed to take any action. You taking action is physical > proof that it presents a problem. By that logic, having Throwable-SugarFactory licensed under a Fedora-approved license would be twice as problematic as it being under a non-Fedora-approved one since that would have required me to do two actions: 1) submit perl-Throwable-SugarFactory as a package in Fedora 2) update perl-MooX-Role-Parameterized, adding perl-Throwable-SugarFactory in its dependencies > Just tell me what license i can replace it with so it's acceptable for your > policies. The list of accepted licenses is here: https://docs.fedoraproject.org/en-US/legal/allowed-licenses/#_allowed_licenses Any license on that list will do. I suppose you could craft your own license and ask Fedora Legal to consider it for inclusion in that list. Please, don't do this. Nothing can justify the amount of work this will require. You can also give the user of your distributions the choice of several licenses. FTR, most Perl packages are licensed under the same license as Perl itself. That is "GPL-1.0-or-later OR Artistic-1.0-Perl" in the list. That said, MooX-Role-Parameterized is licensed under the MIT license. Note that putting your distributions under a Fedora-approved license is not a garentee that they will end up packaged. Again, I suspect you are trying to solve a problem that does not exist. That said, if I can help in any way I can, feel free to ask. Emmanuel -- ___ 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: perl-MooX-Role-Parameterized orphaned
* Christian Walde [11/10/2024 08:26] : > > I am the maintainer of Throwable-SugarFactory. Hello, Christian. > Having been linked this i get to learn that people are now > experiencing consequences because of choices i made in good faith, > without me having been approached in good faith or even AT ALL, and > without any hint within this message of how i could even redress this. FTR, I toyed with the idea of contacting Tiago Peczenyj, the author of MooX-Role-Parameterized, asking if the module could stop depending on MooX::BuildClass but finally decided that: a) that would suggest your use of the CC0 license represents a problem, which isn't the case b) it was more trouble than it was worth > Please provide instructions on how to both maintain the spirit of my > choice and whatever requirements you may have in order to resolve > this. I'm not sure there's anything to resolve, really. Emmanuel -- ___ 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
perl-MooX-Role-Parameterized orphaned
Hello, all. I have just orphaned perl-MooX-Role-Parameterized. Newer versions of the application depend on the Perl module MooX::BuildClass. This module is part of the Throwable-SugarFactory distribution and licensed under CC0. This license is allowed in Fedora for content but not for code. Emmanuel -- ___ 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: Looking for user Lhirlimann
* Peter Boy [16/09/2024 10:04] : > > Does someone know WIKI user >>lhirlimann<< and how to get in contact? > I would like to talk about some of his/her contributions. His RHBZ email is ludo...@hirlimann.net . Emmanuel -- ___ 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: *****SPAM***** Enabling GOPROXY and GOSUMDB in Fedora
* Chris Suszynski [11/07/2024 11:16] : > > What's the reason for treating Go differently than other languages? > Fedora does not patch out calls to sites like npmjs.com, pypi.org, > rubygems.org or repo.maven.apache.org, doesn't it? Actually, we do. https://src.fedoraproject.org/rpms/perl-Dancer2/c/990a6540412546f8ea8cc35ad79c31cd46b06b6a?branch=rawhide Emmanuel -- ___ 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: [Node.js] Stepping down as Node.js Maintainer in Fedora
* Jan Staněk [24/06/2024 03:06] : > > > Right now I see no way on Pagure to request ownership/co-maintenance > (maybe I'm just blind). Anyway, feel free to add me to maintainers > and/or transfer the ownership. Unless things have changed, Pagure does not allow transfer of ownership. Once Stephen has orphaned the packages, you (and every other packager) will be able to claim ownership of the individuel packages via a button in the interface. Regards, Emmanuel -- ___ 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: Unresponsive packagers: suanand and vponcova
* Sundeep Anand [07/05/2024 05:50] : > > (not sure how to update email at bugzilla.redhat.com) Go to https://bugzilla.redhat.com/userprefs.cgi?tab=account and fill in the 'New email address' field. Emmanuel -- ___ 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: convert everything to rpmautospec?
* Zbigniew Jędrzejewski-Szmek [08/04/2024 09:02] : > > Well, you and Kevin see "salami tactics" (whatever that may be), FTR, I have no idea what "salami tactics" is. > while I see normal engineering practice: some new idea is hatched, > it's implemented and used narrowly, them it's applied by default > and more widely, and possibly at the end previous methods are > deprecated. This sounds acceptable but is not at all how these changes are proposed. An proposal is made, stating explicity that it will be opt-in or target a subset of the target audience and never even suggesting that the scope might one day be expanded. It is accepted based on that premise and, after a while, changes are made to make the change default or opt-out, leaving the people who would not have accepted it had they known they would be forced to use it with no recourse. This is unfriendly (thus violating one of Fedora's core principles) at best and deceitful at worst. > The alternative would be to have "grand plans" where we decide that > some technology will be used by default and mandatory before we deploy > it widely and get feedback. Another alternative would be not lie to the target audience by initially claiming that the change is opt-in. Yet another alternative would be to not go back on this claim. > I think that if you think this through, you'll realize that the > "salami tactic" is quite reasonable. I don't but wish to thank you for the condescending tone nonetheless. Emmanuel -- ___ 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: convert everything to rpmautospec?
* Zbigniew Jędrzejewski-Szmek [07/04/2024 15:56] : > > On Sun, Apr 07, 2024 at 05:47:57PM +0200, Emmanuel Seyman wrote: > > > > This doesn't solve the problem you have so that's a no-go as well. > > In what way doesn't it solve the problem? In your original post, you stated "When working with other packages, I'll forget to update the Relase and/or %changelog." This will not go away if packages are allowed to opt-out. > The opt-out with 'norpmautospec' would solve 1 and 2. I've noticed a trend in proposed changes in the way Fedora works. They start off as as things packagers will not have to use if they do not want to and, over time, become default/forced (Matrix vs IRC, Discourse, ...). Perhaps it's time to discuss imposing financial and/or legal penalties when the opt-in nature of the change goes away. Emmanuel -- ___ 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: convert everything to rpmautospec?
* Zbigniew Jędrzejewski-Szmek [07/04/2024 15:35] : > > OK, so if there was an opt-out, [...] This doesn't solve the problem you have so that's a no-go as well. Emmanuel -- ___ 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: [Pierre-Yves Chibon] Unresponsive packagers: nknazeko
* Vit Mojzis [11/02/2024 22:44] : > >Do I understand correctly that she just needs > to create a new BZ account using the email address in FAS? I suspect changing the email linked to her existing BZ account to match the one in FAS will suffice. Emmanuel -- ___ 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
License change for perl-Net-DHCP
Hello, all. The license tag on perl-Net-DHCP has been corrected from: GPL+ or Artistic to MIT Regards, Emmanuel -- ___ 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: The new Change discussion process is painful
* Vít Ondruch [14/09/2023 10:50] : > > Apart from documentation, where this was announced? On Discourse? Because I > don't remember any email about this change. https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/Z2T5WKUTHNLS2SVCVAWNYYRIBK3NGF32/ Emmanuel ___ 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: SIG proposal: Multimedia SIG
* Philip Wyett [19/06/2023 22:20] : > > Private mailing list? No part of this project should have private anything > IMHO. Bug reports can explain security flaws and lead to exploits. They can also contain confidentiel information. I would suggest a private ml dedicated to bugs and a public one for everything else, IMHO. Emmanuel ___ 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: Place to write something up
* Todd Zullinger [03/05/2023 23:33] : > > > Kind of a random thing, but... I would like to write up how to use GRUB2 > > to do BIOS-PXE+UEFI-PXE+UEFI-HTTP boot. I asked for the Fedora packages > > to include the needed PXE bit, and it does now (thanks!), so I feel I > > owe a good explanation on how to use it. :) Note that we have related pages in the Server SIG documentation, some of which hasn't been written yet. https://docs.stg.fedoraproject.org/en-US/fedora-server/administration/dnsmasq/ https://docs.stg.fedoraproject.org/en-US/fedora-server/administration/dnsmasq-pxe-boot/ https://docs.stg.fedoraproject.org/en-US/fedora-server/administration/tftp/ Emmanuel ___ 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: It’s time to transform the Fedora devel list into something new
* Kevin P. Fleming [21/04/2023 10:03] : > > lots of people say "I decide > what to read based on what I see in my email client", but when the subject > of the emails doesn't reflect their contents, that's a losing proposition. I agree there's a huge lack of netiquette in Fedora's mailing lists, with wholesale quoting, top-posting, subjects not being updated, etc but changing mediums seems far more expensive than asking people to post emails that are easier to read. Emmanuel ___ 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: It’s time to transform the Fedora devel list into something new
* Fulko Hew [20/04/2023 21:18] : > > Can you say the same for Discourse? I've tried using Fedora Discussions and its email notifications (both the text and html versions) leave a lot to be desired. So much so that I never actually go on to read the discussions. Emmanuel ___ 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: Looking to orphan perl-Net-TELNET
* Stephen Smoogen [14/04/2023 12:20] : > > I would like someone else to take over this package and will either add > someone or orphan this in the coming 2 weeks. I will gladly take it (fas name: eseyman). Emmanuel ___ 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: Orphaned packages looking for new maintainers
* Miro Hrončok [19/12/2022 16:43] : > > perl-Mail-Procmailorphan 0 weeks ago Taken. Emmanuel ___ 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: Review Request: ImageMagick7
* Neal Gompa [04/12/2022 22:26] : > > Smooge challenged me earlier in this conversation to provide patches > and effort, and I'm doing just that. Thank you for doing this, btw. Over the weekend, this became a discussion where none of the participants seemed to be listening to the others and it became somewhat painful to read. It's nice to see something constructive come out of it. Emmanuel ___ 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: Orphaned packages looking for new maintainers
* Chuck Anderson [05/12/2022 13:06] : > > Would you lke to take perl-Term-ShellUI as well? It is a dependency > of kpcli which requires perl-File-KeePass. Otherwise I'm happy to > take it. Taken as well. Co-maintainers are welcome. Emmanuel ___ 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: Orphaned packages looking for new maintainers
* Miro Hrončok [05/12/2022 12:36] : > > perl-App-PFT orphan 1 weeks ago > perl-File-KeePass cra, echevemaster, orphan, 0 weeks ago > xavierb > perl-HTTP-Server-Simple-Authenorphan 1 weeks ago > perl-Library-CallNumber-LCorphan 1 weeks ago > perl-PFT orphan 1 weeks ago > perl-Pod-PseudoPodorphan 1 weeks ago > perl-Pod-PseudoPod-LaTeX orphan 1 weeks ago > perl-Proc-PID-Fileorphan 1 weeks ago > perl-WWW-xkcd orphan 0 weeks ago I have taken the above packages. Emmanuel ___ 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: Orphaned packages looking for new maintainers
* Miro Hrončok [26/09/2022 11:27] : > > perl-PatchReader orphan 1 weeks ago I have taken this since Bugzilla requires it, last time I checked. Emmanuel ___ 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: Retiring the pcre package from Fedora
* Lukas Javorsky [22/07/2022 14:24] : > > perl-HTML-Template-Pro I'll build against pcre2 in the coming days (probably this weekend). Emmanuel ___ 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: Non Responsive maintainer
* Ivan Chavero [04/07/2022 15:09] : > > I've been trying to contact the current nextcloud package maintainer > because there's a blocker bug [1]. Folks, when you're asking us if anyone knows how to contact the maintainer of a given package, you might want to consider actually giving us his name (both real and FAS). Emmanuel ___ 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: Maintainer Change
* Steve Dickson [19/05/2022 14:21] : > > How is this done these days? The package is first orphaned then claimed by the new maintainer. https://docs.fedoraproject.org/en-US/package-maintainers/Package_Orphaning_Process/#claiming_ownership_of_an_orphaned_package Emmanuel ___ 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: The future of FMN (Fedora Messaging Notifications)
* Aurelien Bompard [14/05/2022 09:39] : > > Please check it out if you're interested, it has an analysis of the existing > system and requirements for the next. > And the best time for feedback is now, before the work actually starts :-) One thing I've always wanted is to be able to have a daily/weekly/monthly email summary of all my notifications instead of getting one email for each notification. Emmanuel ___ 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: Do we have any policy for disabling inactive users
* Stephen Snow [16/02/2022 11:21] : > > Perhaps the automation should do > just that, demote primary packager (from owner to co-maintainer) if > inactive for over a year and promote the main supporter for the year to > be the owner from co-maintainer. Can you define "main supporter"? Emmanuel ___ 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: Orphaned packages looking for new maintainers
* Jens-Ulrik Petersen [08/02/2022 17:21] : > > Anyone interested in keeping 'ikiwiki' and 'perl-Text-Markdown' around? perl-Text-Markdown has a BR on perl-HTML-Tidy but doesn't do anything with it. I'll submit a PR to remove it (and improve other things in that spec file). Emmanuel ___ 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
Orphaning perl-MouseX-App-Cmd and perl-HTML-Tidy
Hello, folks. I've just orphaned two packages, perl-MouseX-App-Cmd and perl-HTML-Tidy. perl-MouseX-App-Cmd has been FTBFS for some time and there is no upstream to speak of. perl-HTML-Tidy's upstream has also stopped work on it. https://src.fedoraproject.org/rpms/perl-MouseX-App-Cmd https://src.fedoraproject.org/rpms/perl-HTML-Tidy Emmanuel ___ 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: mock, %{buildroot}, fc35
* Alain Vigne [02/02/2022 16:07] :
>
> Can someone explain to me why my .srpm [1]
> is not building in mock ?
This fails with the following message:
RPM build errors:
error: File not found:
/builddir/build/BUILDROOT/libfungw-1.2.0-1.fc36.x86_64/usr/lib64/libfungw_mujs.*
error: File not found:
/builddir/build/BUILDROOT/libfungw-1.2.0-1.fc36.x86_64/usr/lib/puplug/fungw_mujs.*
File not found:
/builddir/build/BUILDROOT/libfungw-1.2.0-1.fc36.x86_64/usr/lib64/libfungw_mujs.*
File not found:
/builddir/build/BUILDROOT/libfungw-1.2.0-1.fc36.x86_64/usr/lib/puplug/fungw_mujs.*
This is because the spec file contains the following stanza:
%files-n %{libmujs}
%{_libdir}/%{name}_mujs.*
%{_usr}/lib/puplug/%{srcname}_mujs.*
but the instructions of the %install part of the spec don't result in
these files being created. So the creation of the rpm fails.
Emmanuel
___
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: I quit packaging
* Volker Fröhlich [12/12/2021 23:03] : > > All of my packages are up for grabs. For the curious, volter maintains the following packages: * cptutils * dans-gdal-scripts * e00compr * esniper * freexl * gdal * grass * libgeotiff * librasterlite2 * libspatialite * mingw-polyclipping * polyclipping * pyshp * python-OWSLib * python-phyghtmap * python-Rtree * qextserialport * qgis * readosm * routino * saga * snmptt * spatialindex * spatialite-tools * xerces-c * zabbix Emmanuel ___ 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: Question for election candidates: do you support allowing Fedora src-git repositories to be hosted on a proprietary software git forge?
* Michel Alexandre Salim [30/11/2021 15:22] : > > At the risk of straying off-topic, an approach I really like (which is > in the spirit of Git being distributed) is to use an open source forge > primarily, with GitHub only as backup. How do people using this setup prevent people from submitting PR and issues to the Github mirror where they cannot be applied/fixed? Emmanuel ___ 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: OpenLDAP 2.5 (System-Wide Change proposal)
* Ben Cotton [19/10/2021 12:08] : > > == Benefit to Fedora == > Brings a stable and up-to-date version of OpenLDAP according to > upsteam release. OpenLDAP 2.4 will be out of support as soon as > OpenLDAP 2.6 is released which is planned for this year. Fedora will > be prepared for such a step. Since this was written, the OpenLDAP Project has released OpenLDAP 2.6: https://lists.openldap.org/hyperkitty/list/openldap-annou...@openldap.org/thread/IHS5V46H6NFNFUERMC6AWMPHTWRVNLFA/ Emmanuel ___ 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: Fedora 💔 Java: The Death of Two SIGs
* Peter Boy [29/09/2021 23:29] : > > Any ideas to get it started to fly? The first step should be to empty the group in FAS and remove its bugzilla account from component ownership in Bugzilla (I happen to think that this is not a good idea in general but it's even worse when the group has no active members). The second step should be to document the current state of affairs in the wiki along with the steps that someone would need to go through to revive the group for another try. We could the point anyone who wants to contribute to that page and get out of their way while they fix things. As an aside, I'm somewhat surprised that the only commit on the Java SIG's main wiki page in nearly 4 years is one that simply fixes a spelling mistake. This doesn't jive with the amount of discussion we've had on this list nor does it match the amount of work that people claim to have done on the stack in recent times. I would encourage people who want to restart the SIG to reach out to other distributions and enquire as to how they handle their Java stack. While I'm as much into Fedora exceptionalism as any other packager, I'm certain that other distributions have the same problems packaging Java that we do. At worst, doing this would give us insight into how the stack can be kept in working condition and, at best, we could gain new contributers. On that topic, I've just read an interview of Nicolas Lécureuil, the president of the Mageia board, in which he says that Mageia's Java stack is based on Fedora's and that he interacts with Fedora's Java team (leading me to wonder who exactly he is interacting with given Fabio's description of the SIG's activity in the opening mail of this thread). Emmanuel ___ 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: perl-Data-Properties License change
* Emmanuel Seyman [25/07/2021 22:42] : > > > Sometime over the coming week, I'm going to update the > perl-Data-Properties package from the current 0.02 to 1.05. > Among other changes, the license changes from ASL 2.0 to the Perl > license (GPL+ or Artistic). Upstream has re-released 0.02 with the version number 1.06 so, in a few days, the changes in the 1.05 version (including the license change) will be reverted. Sorry for the noise, folks. Emmanuel ___ 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: New RPM submission (dovecot-fts-xapian)
* Ankur Sinha [20/08/2021 12:27] : > > I totally understand the point of the system we have in place, but I do > see how it doesn't quite address the case of upstream developers or > individuals who'd just like to maintain their few packages. To be fair, the system does address the case of the upstream developers: it is recommended that they co-maintain the packages of their software but leave ownership of the packages to experienced packagers. This has been explained to Joan a number of times. > So, here, I'd rather have Joan, who is the developer and has been > actively engaging with the community to get the package included > (including going through the review), and so who I'd trust to look after > their package, on the team than not. The small issue I have is that, while Joan claims to want to become a packager in the mails he sends to the devel list@, he a) is very secretive about what steps he has taken to seek out a sponsor and b) has said in the review bug that he has no intentions of following the guidelines. Let's hope this dichotomy gets resolved sooner than later. Emmanuel ___ 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: The Death of Java (packages)
* Stephen Snow [11/08/2021 12:08] : > > > > Even tried the review route, which is also beset with arbitrary > > > obstacles. > > > Wasn't able to download the build via the link provided. ??? Building a package with mock will create the build in /var/lib/mock/... No download should be required. Emmanuel ___ 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: The Death of Java (packages)
* Stephen Snow [11/08/2021 11:37] : > > I feel the frustration you are expressing, and would like to help, nut > apparently I don't meet the Fedora Packaging standards. I'm curious as to what happened... > Even tried the review route, which is also beset with arbitrary obstacles. Again, what happened? Can you point us to those reviews? > I will keep trying because that is in my nature, but making joining the > packaging group(s) a bit more open would go a long way to garnering more > packagers IMO. What changes to the process would you like to see made? Emmanuel ___ 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
perl-Data-Properties License change
Hello, folks. Sometime over the coming week, I'm going to update the perl-Data-Properties package from the current 0.02 to 1.05. Among other changes, the license changes from ASL 2.0 to the Perl license (GPL+ or Artistic). Please holler if this creates a problem for you. Regards, Emmanuel ___ 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: Why so long for EPEL-8?
* Björn Persson [19/07/2021 13:05] : > > but if I could be notified > about updates of certain packages I'm interested in, then I could > choose to test those if I'm not too busy at the time. I don't know a > convenient way to do that, so I end up installing updates when they > show up in the updates repository. There are a number of options that I can see: 1) Bodhi has an RSS feed that you can apply filters to. I'm not sure if you can select packages you want to follow, though. 2) You can sign up as co-maintainer of the package on the EPEL branches. This will give you email notifications on pretty much anything that happens on those branches. 3) Bugzilla generates RSS feeds for virtually any list. You can follow bug activity via those. Emmanuel ___ 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: New RPM submission
* Joan Moreau via devel [26/06/2021 19:36] : > > What is next ? The answer is the same one you were given two months ago. You need to seek out a sponsor: https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group Emmanuel ___ 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: New RPM submission
* Joan Moreau via devel [01/05/2021 09:21] : > > 1 - Those who have a great piece of software, simply willing to make it > available to the large public. In such case, there should be only quality > barrier of the package + rules of duration (i.e. added packages are not kept > in Fedora if not maintained for instance once a year) I suspect having packages being removed after a year is going to make for a poor user experience. If an upstream author wants his software in Fedora, I would recommend one of two solutions: a) use a COPR repository and publish instructions on enabling the repo b) find an existing maintainer to do the heavy lifting and sign on as a co-maintainer to deal with upstream-related issues. The primary maintainer will then only have to deal with Fedora-related issues. Emmanuel ___ 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: New RPM submission
* Joan Moreau via devel [30/04/2021 14:16] : > > 1 - How to get to the "packager" group ou forum or else ? We use FAS (https://accounts.fedoraproject.org/user/eseyman/) to manage Fedora developer accounts. FAS has the notion of groups, one of which is the packager group (https://accounts.fedoraproject.org/group/packager/). People can added in this group once they are sponsored in by somebody with "sponsor" status. > 2 - What does it mean to "block the FE-NEEDSPONSOR [1] tracking bug" ? Bugzilla bugs can block and depend on other bugs. To block on the FE-NEEDSPONSOR bug means to block on bug #177841 (which has the alias FE-NEEDSPONSOR) > So far, I have https://bugzilla.redhat.com/show_bug.cgi?id=1953340 This bug blocks FE-NEEDSPONSOR so there is noting more to do on this front. Emmanuel ___ 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: New RPM submission
* Joan Moreau [27/04/2021 20:51] :
>
> Hi Emmanuel
>
> I am trying my best to foloow the process but I get nowhere
>
> Now I get a "koji" error ("AuthError: unable to obtain a session")
That looks like a recurring kerberos issue.
https://pagure.io/koji/issue/2063
https://pagure.io/releng/issue/7522
You probably want to contact releng to help solve this.
> I tried "fedpkg request-repo --exception dovecot-fts-xapian" -> Lead some
> error ("fedpkg request-repo --exception dovecot-fts-xapian")
Why is this package exempt from the review process?
> I filed a "bug" on redhat :
> https://bugzilla.redhat.com/show_bug.cgi?id=1953340
>
> And now, how to get things moving ?
You need to seek out a sponsor:
https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group
> Isnt' there just a repo where to push the RPM ? (similar to Arch)
There is COPR but I suspect this is reserved to Fedora packagers so you
will still need to be sponsored.
https://fedoraproject.org/wiki/Category:Copr
Emmanuel
___
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: The Death of Java (packages)
* Fabio Valentini [26/04/2021 21:19] : > > I am not using any of > them, I don't like Java or any other languages targeting the JVM, and > don't get me started on the horrid Java ecosystem. Thank you for all the work you've done, Fabio. Emmanuel ___ 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: New RPM submission
* Joan Moreau via devel [24/04/2021 18:49] : > > It looks overwhelmingly complicated. Out of curiosity, which part of the process looks complicated. Perhaps we can simplify it. Emmanuel ___ 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: WARNING: The script foo is installed $HOME/.local/bin which is not on PATH
* Sérgio Basto [18/04/2021 12:57] : > > Hi, > > $HOME/.local/bin which is not on PATH , $HOME/bin is in PATH, am I > missing something ? /etc/skel/.bashrc has contained the following: # User specific environment if ! [[ "$PATH" =~ "$HOME/.local/bin:$HOME/bin:" ]] then PATH="$HOME/.local/bin:$HOME/bin:$PATH" fi export PATH for years and years now. If $HOME/.local/bin is not in your path, something is wrong with your configuration. Emmanuel ___ 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
Orphaning perl-re-engine-RE2
Hello, folks. I've just orphaned the perl-re-engine-RE2 package. If someone wishes to take it up, it's yours. Be warned that the package has an open bug in Bugzilla: Bug #1922811 (perl-re-engine-RE2-0.14 is available) Regards, Emmanuel ___ 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: Summary/Minutes from today's FESCo Meeting (2020-11-11)
* Matthew Miller [19/11/2020 17:13] : > > Some packagers in Fedora do not have time to maintain the build dependencies > for the packages that they are actually interested in and have time to > build. I suspect that these packages are maintained only to the point where they can build (and thus be used as buildreqs) but their maintainer also doesn't want them to be updated without making sure that the update will not break the package they are really interested in. > However, I'm not stuck on that one and it's probably not useful to stay > stuck on it if there's not enough support to do it. So, let's find a > different solution. What exactly do you want to do with this list of lightly-maintained packages? Is this something you want to present to end-users? Is this a list we should show to people tempted to become packagers? Do we want to generate auto-replies to bugs filed in Bugzilla? Should SIGs keep a lookout for security fixes to apply? I suspect we'll only be able to determine the best approach if we know what problem you're trying to solve. Emmanuel ___ 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
Re: Summary/Minutes from today's FESCo Meeting (2020-11-11)
* Kevin Kofler via devel [13/11/2020 00:52] : > > The one that keeps getting brought up is Tomcat, but I can tell you from my > personal experience that the Fedora Tomcat package has always been working > just fine (not only as a build dependency, but for its intended use as a web > application server: I use it to locally test Java web applications). I suspect this isn't sufficient a test to determine if a package is well maintained or not. At a minimum, you also need to look at CVEs for which fixes have not being pushed. Emmanuel ___ 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
Re: Lightly-maintained packages (was: Summary/Minutes from today's FESCo Meeting (2020-11-11))
* Miroslav Suchý [11/11/2020 18:05] : > > We already have "lightly-maintained packages" - it is called Copr projects. > Do we need something in between? The issue here is discoverabilty. If $PACKAGE is in a separate repository, be it a 'lightly-maintained' repo or a copr, how do we go about communicating to users wanting to install it that they need to activate that repository and that the software they download from it may or may not work? Emmanuel ___ 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
EPEL8 Branch Request: perl-Data-GUID
Hello, all. Ralf Corsepius has requested that someone give Paul Howarth and Jitka Plesnikova collaborator rights in bug #1870755 . Their FAS usernames are pghmcfc and jplesnik respectively. Is there someone on the list who can do this? Regards, Emmanuel ___ 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
perl-Unicode-MapUTF8 license change: GPL+ or Artistic -> MIT
Hello, all. With version 1.12, the author of the Perl Unicode::MapUTF8 module has relicensed it under the MIT license. In pratice, the first package to contain the relicensed module is perl-Unicode-MapUTF8-1.14-1.fc34 with the license field only being updated in perl-Unicode-MapUTF8-1.14-2.fc34 . Emmanuel ___ 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
Re: The Future of the Java Stack (also regarding ELN and RHEL)
* Fabio Valentini [09/09/2020 00:19] : > > Can we please increase the bus / lottery > factor (= 1) for Java package maintenance in fedora? I know that at least one distribution bases its Java stack on Fedora's. Perhaps someonce could contact their maintainers and encourage them to contribute to their upstream? Emmanuel ___ 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
Re: Lua 5.4.0
* Tom Callaway [30/06/2020 18:00] : > > lua-event seems to be broken because of broken deps unrelated to Lua > 5.4: nothing provides perl(:MODULE_COMPAT_5.30.1) needed by > perl-Monotone-1.1-34.fc32.x86_64, so I left it alone. FTR, We've moved on to Perl 5.32.x so monotone needs to be rebuild against that so that we get a new perl-Monotone package. Emmanuel ___ 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
Re: Regarding behaviour of Gnome and Fedora members
* Ty Young [12/06/2020 07:13] : > > > Some of the comments mentioned in my article took place on this mailing > list. Would it not be appropriate to post it here as a result? No, I don't think so. >Where on > Fedora's mailing lists should I post it to? I don't think this would be considered on topic for any of Fedora's lists that I know of thus I would refrain from posting to any of them. Emmanuel ___ 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
Re: Regarding behaviour of Gnome and Fedora members
* Ty Young [12/06/2020 05:50] : > > So, could anything be done about any of this? I would propose that we keep discussions not related to the development of Fedora off the devel@ mailing-list. Emmanuel ___ 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
Re: F30 security update submitted for stable "marked obsolete" instead of being pushed
* Artur Iwicki [27/05/2020 06:25] : > > While I understand the mechanism, I think that this needs to be communicated > more clearly. I've been a packager for close to 3 years now and I admit until > I read this e-mail I wasn't quite sure whether "no updates after EOL" meant > "you can't submit stuff to bodhi", or whether it meant "the updates repo is > frozen solid, whatever didn't make it in, well shucks". (As we can see, it's > the latter.) The Fedora 29 EOL message[1] was a bit more explicit: "At that time, all open Bugzilla bugs will be closed and no more package updates will be published." Emmanuel [1] https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org/message/VUK3CJ5LO4ROUH3JTCDVHYAVVYAOCU62/ ___ 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
Non-responsive maintainer check for avesh
Hello, Anybody knows how to contact Avesh Agarwal (fas:avesh) ? I have a bug filed in Bugzilla that has not seen any action for 6+ months now. BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1748553 Emmanuel ___ 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
Re: CPE Git Forge Decision
* Clement Verna [01/04/2020 15:04] : > > What does NIH stands for ? Not invented here (see https://en.wikipedia.org/wiki/Not_invented_here for the gory details) Emmanuel ___ 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
Re: Orphaned packages looking for new maintainers
* Scott Talbert [30/03/2020 14:38] : > > Because the maintainer (normunds) was non-responsive. I don't see any > commits from you?? Sorry, I was looking at perl-Data-Validate-Type, not at perl-Data-Validate-Domain. I've taken the package. Emmanuel ___ 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
Re: Orphaned packages looking for new maintainers
* Miro Hrončok [30/03/2020 20:24] : > > perl-Data-Validate-Domain orphan 1 weeks ago I've maintained this package for years now. Why is it considered it orphaned? Emmanuel ___ 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
Re: Nvidia binary drivers fail to install on Fedora 32
* Vitaly Zaitsev via devel [30/03/2020 12:42] : > > This is absolutely impossible. No proprietary software are allowed. I believe OP means that NVidia must provide a third-party repo for Fedora. Emmanuel ___ 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
Re: Bugzilla signal/noise ratio
* Daniel Pocock [20/03/2020 13:22] : > > > Over how many bugs and what time period were the requests generated? > > More than a year This is the core of your problem. Not responding to outstanding requests in a timely manner is a sure way to get more reminders. I suspect responding to these in a timely manner (i.e. within a week) will cut down the amount of bugzilla mail you receive. > The bug alone is enough I feel you've proved the opposite: filing bugs alone isn't sufficient and, apparently, neither is sending out periodic reminders by mail. Perhaps we need to be more agressive in encouraging people to find co-maintainers that can help them do their work. Emmanuel ___ 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
Re: Bugzilla signal/noise ratio
Hi, Daniel. * Daniel Pocock [20/03/2020 12:38] : > > - there were over 100 "outstanding requests" emails in my inbox Over how many bugs and what time period were the requests generated? > - there are numerous bugs about builds failing, FTBFS These bugs are signal and not noise. Not only are they signal but I consider them to be relatively important. Emmanuel ___ 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
Re: Ideas for better development processes when maintaining hundreds of packages
* Remi Collet [29/01/2020 15:18] : > > And I really prefer to see stabilization of our current tools and > infrastructure before breaking it again. Same here, to be honest. I'm far more held up in my work by the infrastructure breaking up from under me than the absence of any of the suggestions from this thread. Emmanuel ___ 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
Re: Orphaned ldapvi
* Matěj Cepl [30/01/2020 14:54] : > > https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_an_Orphaned_Package Done! Emmanuel ___ 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
Re: Orphaned ldapvi
* Matěj Cepl [30/01/2020 11:43] : > > If anybody wants it, let me know. I will gladly take it (fas user: eseyman). Emmanuel ___ 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
Re: Ideas for better development processes when maintaining hundreds of packages
* Stephen John Smoogen [28/01/2020 13:08] : > > You are assuming that maintainers actually check to see if a version > fixes an issue already. If a packager has 100's or 1000's of > packages.. there is no way they will have done so except on a 1 in a > million case set. I think if are going to aim that a packager can > 'maintain' hundreds or thousands of packages that we also assume that > this security is not going to be checked by the maintainer. I really don't think I'm *that* special a case so I'ld prefer you check that this is actually true rather than assume something wrong. Emmanuel ___ 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
Re: Java Dev Group and Fedora Quality
* Bill Chatfield via devel [26/01/2020 22:33] : > > I don't know if the problem is dnf or a library, but it is a serious problem. There are several issues here: - Different servers will transmit repository metadata at different speeds and you need to factor these out when trying to find bottleneck in the client-side code. - dnf handles more stuff than apt. For instance, perl packages have virtual provides in the form of 'perl($MODULE)' for every perl module in the package. This allows users to install a given module without caring what package it is in. Last I checked, apt had no equivalent. Emmanuel ___ 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
Re: Java Dev Group and Fedora Quality
* Bill Chatfield via devel [25/01/2020 23:23] : > > I'd be willing to work on that if I can figure out how to recreate the group. > Can you point me in the right direction? SIGs are rather informal and none of them have a joining procedure that I know of. That said, this was already discussed on the list in November. https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/5HLSAPTEZLH24Y3GPF5NJEKULYJ64PUU/ You should subscribe to the mailing list, introduce yourself and request any commit rights you feel you need. Once that's done, you can start making commits/pull requests and doing reviews of package submissions (formal or informal). Updating the wiki page and welcoming new members would be a huge plus. Emmanuel ___ 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
Re: Java Dev Group and Fedora Quality
* Bill Chatfield via devel [25/01/2020 22:06] : > > I'm trying to find out what's going on with Java in Fedora. Fedora 31 was > released with a broken Eclipse. I subscribe to the java-devel mailing list > but there is no traffic there. As has been discussed time and time again on this mailing list, the last member of the Java SIG left it at the end of 2018, leaving the group empty. https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/YFUXS7ZX6UDEMEKJWONKFMVDTSBABZID/ > If I go to "Join a Group" and click on "J" there is simply nothing there... There are several FAS groups with 'java' in their name but non that start with the letter 'J'. I'm not sure why you would expect this to be the case... Emmanuel ___ 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
Re: Old changelog entries removal
* Daniel P. Berrangé [03/10/2019 14:47] :
>
> FWIW, my approach is to purge all changelog entries older than 2 years
> the first time I touch a package in January each year. Is there any value
> in having guidelines to encourage some policy in this area, so maintainer
> approach it in a consistent way ?
FTR, this is done automatically by this snippet in redhat-rpm-config:
# Automatically trim changelog entries after 2 years
%_changelog_trimtime%{lua:print(os.time() - 2 * 365 * 86400)}
https://bugzilla.redhat.com/show_bug.cgi?id=1722806
Emmanuel
___
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
Re: Defining the future of the packager workflow in Fedora
* Matthew Miller [02/10/2019 13:33] : > >And there _are_ real tracking and review benefits to > having everything go through that workflow. > > Do you have an alternative proposal? I'm fine with the workflow we have now. Small and drive-by contributions can by contributed via pull requests while core contributers (can) commit directly to master if they so wish. Emmanuel ___ 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
Re: Defining the future of the packager workflow in Fedora
* Pierre-Yves Chibon [26/09/2019 16:07] : > > When we work on upstream projects, I think it's pretty standard now to always > go > via PRs, even for your own branch. FWIW, this workflow makes sense for one that has a community but it sounds very strange to do this on a project on which you are the only developer. > Is it a tooling issue? The biggest issue I have with this workflow is that I don't know of any means through which I can merge a PR using only git and/or fedpkg. Emmanuel ___ 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
Re: gstreamer-plugins-base revival
* Tom Callaway [22/08/2019 09:04] : > > I don't really want to own it, but I have dependent packages, so if no one > else does, I will claim it. Since this one is back, I'm planning to unretire perl-GStreamer and perl-GStreamer-Interfaces, which depended on this. Emmanuel ___ 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
Re: Fedora 31 Beta Release Announcement
* Kevin Kofler [19/09/2019 16:12] : > > That could have been prevented by policy, but deliberately was not, because > the people behind Modularity had exactly this (moving random packages to > module-only) as their hidden agenda. I'm quite certain that forbidding people to move to module-only would mean that we would not only not have a Java stack in Fedora but also no Java module too. You can argue that that's a good thing. Mikolaj wouldn't have gotten half the abuse he got for being the last remaining member of the Java SIG and we wouldn't have crazy conspiracies accussing people of moving packages to module-only because $REASON but having a Java module is better than not having one. Emmanuel ___ 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
Re: Fedora 31 Beta Release Announcement
* John M. Harris, Jr. [17/09/2019 21:27] : > > I can provide a link to the vendor's website when I get home. I'm interested in this. Emmanuel ___ 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
Re: Fedora 31 System-Wide Change proposal (late): No i686 Repositories
* vvs vvs [10/09/2019 21:07] : > > I suppose that SIG is a much formal entity than just a bunch of > individuals performing some non-regular activities. The PHP SIG is barely more than one person, the Perl SIG has no regular meeting and the mailing list activity is not representative of the work being done but thoses SIGS still do the work necessary to keep their stack in the distribution. > If that really was that simple then just subscribing to that list > would be enough to get support for x86 architecture and we wouldn't > be here. I think you're confusing cause and effect, here. We look at Bugzilla stats and mailing-lists activity because it's (supposed to be) indicative of the work being done. It's a by-product, not the final outcome. Subscribing to a mailing-list (and even posting to it) isn't going to improve the packages in the distribution by itself. Emmanuel ___ 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
Re: Fedora 31 System-Wide Change proposal (late): No i686 Repositories
* vvs vvs [10/09/2019 11:41] : > > And the primary reason why that SIG initiative never worked is that the > project didn't put any significant efforts to make that happen. I'm going to disagree with you here. Back in 2017, we went through a very long discussion which lead to the creation of the x86 SIG. The discussion on the mailing list started off at a reasonable rate and then slowed to a stop because it couldn't keep its momentum going. So the fault with the SIG not working really lies with the people who wanted to keep x86_32 going not being able/willing to do the work necessary, not all the other Fedora developers. > Either we can be a low activity grass-roots enthusiasts and find our > own ways to contribute packages, e.g. COPR might be useful. This is pretty much the definition of a SIG. Emmanuel ___ 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
Re: No longer supporting mailing lists:
* Pierre-Yves Chibon [26/08/2019 09:44] : > > Our recommended solution is to find someone that would maintain the mailman3 > stack for us. Does this have to be mailman3 or can it be a different mailing list manager? Emmanuel ___ 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
Re: Over 500 orphaned packages seeking new maintainers
* Christopher [30/07/2019 13:20] : > > Is there anything special one must do to "Join" the Java SIG? I would > like to join. SIGs are rather informal and none of them have a joining procedure that I know of. You should subscribe to the mailing list, introduce yourself and request any commit rights you feel you need. Once that's done, you can start making pull requests and doing reviews of package submissions (formal or informal). Emmanuel ___ 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
Re: Orphaned packages looking for new maintainers (75 to be retired)
* Kevin Fenzi [26/07/2019 09:25] : > > That said, we could: > * make a bugzilla user for every package named > 'packagename-ow...@fedoraproject.org' > * assign bugs for that package to that user (no ccs) Please don't do this. The best feature the system we currently use has is accountability. It's immediately obvious who the person most responsible for fixing the bug is at any given point and that's very much a good thing. Emmanuel ___ 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
Re: Discussion around app retirements and categorizations by the CPE team
* Nicolas Mailhot via devel [23/07/2019 11:51] : > > That is not true. Search the list archive for Michael Zhang’s questions on > how to get Open Liberty in Fedora. About 4 months later, can anyone do a dnf > install open liberty, pointing to a Fedora repo? No but that's probably because he got several comments on his review request and hasn't replied to them (his last comment on the bug[1] was in February). Emmanu ___ 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
Re: Fedora 32 System-Wide Change proposal: x86-64 micro-architecture update
* Josh Boyer [22/07/2019 15:56] : > > Would it be possible to include some basic instructions or a script > for people to run on their systems to see if they are AVX2 compliant? > That would help them assess the impact. you can find your cpu model by running the command: $ grep 'model name' /proc/cpuinfo From there, it's a simple lookup on http://www.cpu-world.com to see what features it has. Emmanuel ___ 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
Re: Discussion around app retirements and categorizations by the CPE team
* Peter Robinson [17/07/2019 14:07] : > > It would be useful to have the CPE mission linked to directly, it's > mentioned a number of times in the post but I don't see a direct way > to get to it. It's in the first link on that page: https://communityblog.fedoraproject.org/outcome-of-the-cpes-teams-face-to-face/ Emmanuel ___ 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
Re: Discussion around app retirements and categorizations by the CPE team
My initial reaction is that the lists of applications in categories 1 and 2 are very short. My second reaction is that this page doesn't sell me that I should use Python in any business-critical software... Is release-monitoring.org also maintained by the CPE? It's being broken for ages and I feel it's a shame it doesn't get more love. Emmanuel ___ 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
Re: Inconsistent dnf provides result
* Georg Sauthoff [01/06/2019 19:40] : > > But what about the `dnf provides` output? > > It looks like something is going wrong in the process that generates the > file-index. Should I open a bug for this, as well? And where? Wow, that git history is messy... Please file a bug against the package arguing that the %ghost directive seems to be abused in this case (it really should be used for log (and maybe configuration files) not shipped with the package but linked to it. I'll argue that having an rpm provide ghosted files is correct behaviour. Emmanuel ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Orphaning elasticsearch
* Luis Enrique Bazán De León [14/04/2019 08:22] : > > I can work on it I've transferred the package to you, Luis. Good luck with it! Emmanuel ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Orphaning elasticsearch
Hi, folks. A while back, I realized that I was the main admin for the elasticsearch package. Given that I'm not using elasticsearch these days (I signed up for co-maintainership because I maintain the perl bindings for ES) and with the upcoming retiring of most of the Java stack in Fedora, I just don't have the cycles to deal with this and I've decided to orphan the package. If any one of you wants to step up and become main admin, speak up in the coming days and we'll make it happen. Emmanuel ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: [Fwd: Orphaned packages to be retired (Java packages in 2 weeks)]
* Sérgio Basto [19/03/2019 00:03] : > > I though it was just one person which decide orphan his 259 packages Mikolaj is the last actif member of the Java SIG. Emmanuel ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Orphaned packages to be retired (Java packages in 3 weeks)
* Richard W.M. Jones [15/03/2019 20:23] : > > These are very important packages. What do we have to do here? I'm going to repeat this until it sinks in... If you (this is the generic you, not you specifically) want these packages to be in the distribution, you need to step up and ask for maintainership of said packages or incite people who are interested in maintaining Java packages to do so. > Is Java being dropped from the distro? Yes, that's what we were warned about months ago. Emmanuel ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Orphaned packages to be retired (Java packages in 3 weeks)
* Hans de Goede [13/03/2019 08:51] : > > A solution for this needs to be found and be in place *before* dropping > these packages not the otherway around. We've known the solution for months, now. If you (this is the generic you, not you specifically) want these packages to be in the distribution, you need to step up and ask for maintainership of said packages. It's that simple, folks. Emmanuel ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Ditch RPM in favor of DPKG
* Dridi Boukelmoune [19/02/2019 11:03] : > > Three of those packages are heavy on Perl code, and I'm not a Perl > Monk. I tried to CC perl-sig as per the guidelines [1] (also tried with > the mailing list address) but bugzilla replied kindly: > > CC: perl-sig did not match anything The Perl SIG's mailing list address is perl-de...@lists.fedoraproject.org . This is a valid account in Bugzilla and should work. Emmanuel ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Orphaned packages that will be retired (and everything will most likely burn)
* Hans de Goede [15/02/2019 12:09] : > > And automatic scripts really just should hand it over to the first > co-maintainer > in the list. This inspires two observations (which I'm sure you already know). * There's no such thing as "the first co-maintainer" There are co-maintainers and they all have equal standing. Picking one to give the package to is going to require one of: 1) asking them to figure it out amongst themselves 2) something based on /dev/random 3) running 'git shortlog -s | sort -nr' and going down the list * It's more polite to ask first Making someone the maintainer should probably require his informed consent. A co-maintainer might exist for the sole case of maintaing (perl|python|php) bindings of a given application. In this case, making them the point of contract will probably not yield the results you're looking for. Emmanuel ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages
* Fabio Valentini [13/02/2019 13:58] : > > It's fine for now, since the ant hasn't been retired from the master > branch - yet. > Once that happens, it will not be available from the regular repos, > but only from the modular repos. The issue here is that, if we have someone who can maintain ant, I see no incentive for him/her to doing this under the Stewardship SIG you're proposing rather than the Java SIG which already exists. Emmanuel ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Proposal: Stewardship Group / SIG for taking care of otherwise "module-only" packages
* Ron Yorston [13/02/2019 08:45] : > > What causes a package to move? I guess it doesn't just happen > spontaneously, so presumably it's a choice the maintainer makes. It isn't really a move per se. A regular package can be copied into a module. If the package is then orphaned/retired, it ceases to be a regular package but stays part of a module. > If so, why would they do that? Why would they *not* want their package > to be available as a regular package? It seems counterproductive for > them to downgrade their package to this second-class status. The goal, IIUC (and I'm not at sure that I do), is to for each module to be able to have its own lifecycle, seperate from the lifecycle of the distribution. Emmanuel ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Orphaned packages that will be retired (and everything will most likely burn)
* Tom Hughes [12/02/2019 09:15] : > > So basically the module squad have managed to ensure that everything > that relies on ant to build is going to have to modularise or else be > forced out of the distribution then... Once more with feeling: if you want ant as a package, all that is needed to make that happen is for you to step up and maintain it. This has nothing to do with modularisation. Emmanuel ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Retiring perl-perlmenu
* Emmanuel Seyman [29/01/2019 00:35] : > > I maintain perl-perlmenu in Fedora and I will be retiring it at the end > of the week unless someone offers to maintain it instead. Tha package has been retired. Emmanuel ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
