Non-responsive maintainer mkulik
Hi all, mkulik is the main admin of pg_auto_failover component, and I can't reach him. So I would like to start the process of moving the main admin role to me(I am an admin now but the default assignee is mkulik due to the main admin role). Here is the mandatory BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2238708 -Filip- ___ 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: Request repo only with EPEL banch
Thanks Petr, I expected such an approach, but my ticket was closed twice with: The Bugzilla bug is for "Fedora EPEL" but the requested branch is "rawhide" So I changed BZ from epel to Fedora. And I hope now it will work. -Filip- pá 4. 2. 2022 v 12:50 odesílatel Petr Pisar napsal: > V Fri, Feb 04, 2022 at 09:02:57AM +0100, Filip Janus napsal(a): > > I have an issue with requesting repo only with epel8 branch. fedpkg > > request-repo doesn`t > > support any option related to branch name by default it sends the request > > for new repo with rawhide branch. I also tried to request branch epel8 > for > > non-existing repo, but it failed as expected. > > > Working procedure is to ask for the new repository, then ask for epel8 > branch, > then retire rawhide branch. > > -- Petr > ___ > 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 > ___ 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
Request repo only with EPEL banch
Hi everyone, I have an issue with requesting repo only with epel8 branch. fedpkg request-repo doesn`t support any option related to branch name by default it sends the request for new repo with rawhide branch. I also tried to request branch epel8 for non-existing repo, but it failed as expected. I`ve already asked it in the ticket[1] but it was again closed by automatization without response. [1] https://pagure.io/releng/fedora-scm-requests/issue/41693 Thanks -Filip- ___ 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: Naming convention
> Shouldn't it be autoconf2.71, assuming that it is for autoconf 2.71? Yes, but in the case of autoconf2.71, I am wondering how to deal with an update since this package should be the latest version. Creating package autoconf2.72 in the future doesn't make sense to me. My thought was to use autoconf2.7 and in case of a new release update this package. Another option could be autoconf2.7.x. Thanks Filip čt 23. 9. 2021 v 13:48 odesílatel Florian Weimer napsal: > * Dominik Mierzejewski: > > > On Thursday, 23 September 2021 at 09:52, Filip Janus wrote: > >> Hi all, > >> I am wondering about the right name for Autoconf compact package. I > need to > >> add the latest release of autoconf into EPEL so I need a package with a > >> different name. Currently, there are in fedora autoconf, autoconf213, > and > >> autoconf268. The latest version is 2.71 so I have few options in my > mind: > >> > >>- compat-autoconf > >>- compat-autoconf27 > >>- autoconf27 > >> > >> What do you think? > > > > The last one is almost the currently recommended convention. The correct > > name would be "autoconf2.7": > > > https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/#multiple > > Shouldn't it be autoconf2.71, assuming that it is for autoconf 2.71? > > Thanks, > Florian > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ 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
Naming convention
Hi all, I am wondering about the right name for Autoconf compact package. I need to add the latest release of autoconf into EPEL so I need a package with a different name. Currently, there are in fedora autoconf, autoconf213, and autoconf268. The latest version is 2.71 so I have few options in my mind: - compat-autoconf - compat-autoconf27 - autoconf27 What do you think? -Filip- ___ 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
Effort to remove libdb
Hi all, as you maybe know the BerkeleyDB 6.x has a more restrictive license than the previous versions (AGPLv3 vs. LGPLv2), and due to that many projects cannot use it. Few years ago there was an effort to reduce the number of dependent packages on BerkeleyDB(libdb). And nowadays situation seems to be almost the same. Here is the link with packages dependent on libdb[1] from previous effort, which is truthful for nowadays situation. As a member of the database team which is responsible for libdb, I would like to know your opinions on this problem, because many components have many specific cases where is libdb used. Nowadays we would like to remove libdb from Fedora as soon as possible, in the best case from Fedora 33. But I am afraid, that it isn't real. I have discussed this issue with my colleagues and we propose an approach. We found that the biggest problem would occur in updating components from versions that support libdb to versions without this support. Here could arise problems of inconsistency. Our approach assumes to convert old libdb databases to other supported database format in each package related to this libdb issue. Result would be Fedora without libdb. I know that this approach probably isn't perfect. Therefore I would like to ask for Your opinions, suggestions and every problem clarification. Thank you very much for any help. I welcome every opinion. [1] https://fedoraproject.org/w/index.php?title=User:Pkubat/Draft_-_Removing_BerkeleyDB_from_Fedora&rd=User%3AJstanek%2FDraft_-_Removing_BerkeleyDB_from_Fedora Fiip Januš - Red Hat Associate Developer Engineer - Databases Team ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
