Also look at https://fedoraproject.org/wiki/Join_the_package_collection_maintainers сб, 10 апр. 2021 г., 14:22 Peter Oliver <mavit(a)mavit.org.uk&gt;: > Welcome! Start at > https://fedoraproject.org/wiki/Package_Review_Process > _______________________________________________ > devel mailing list -- devel(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave(a)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(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)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

When I launch the "koji" comand, build fails because it does not find g++ (see : https://kojipkgs.fedoraproject.org//work/tasks/9140/66659140/build.log ) However, I put gcc-c++ in the BuildRequires line (see : https://github.com/grosjo/fts-xapian/blob/master/PACKAGES/RPM/fts-xapian.... )

Same status :(

> you probably sent the same srpm No, it is a new one , re-generated > just fine, I did make a few changes to the spec file. with a correct > changelag entry it should pass review What changes are you suggesting ?

On Sun, Apr 25, 2021 at 8:48 AM Richard Shaw <hobbes1069(a)gmail.com&gt; wrote: On Sun, Apr 25, 2021 at 8:36 AM Joan Moreau via devel <devel(a)lists.fedoraproject.org&gt; wrote: When I launch the "koji" comand, build fails because it does not find g++ (see : https://kojipkgs.fedoraproject.org//work/tasks/9140/66659140/build.log ) However, I put gcc-c++ in the BuildRequires line (see : https://github.com/grosjo/fts-xapian/blob/master/PACKAGES/RPM/fts-xapian.... ) Just a drive by look at it but try changing: ./configure --with-dovecot=/usr/lib64/dovecot to: %configure --with-dovecot=/usr/lib64/dovecot

Thanks, Richard _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)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

* 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(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)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

* 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(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)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

在 2021-04-29星期四的 13:25 +0100，Joan Moreau via devel写道： > Thank you > Concretely, how to "find a sponsor" ? FYI: https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)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

Isn´t there a muh more systemic (and simpler) process to push a RPM in the distribution ?

在 2021-04-29星期四的 13:25 +0100，Joan Moreau via devel写道： > Thank you > Concretely, how to "find a sponsor" ? FYI: https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)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

1 - How to get to the "packager" group ou forum or else ?

2 - What does it mean to "block the FE-NEEDSPONSOR [1] tracking bug" ?

So far, I have https://bugzilla.redhat.com/show_bug.cgi?id=1953340

Il 30/04/21 15:16, Joan Moreau via devel ha scritto: Thanks but I am really scratching my head to try to understand all this: 1 - How to get to the "packager" group ou forum or else ? 2 - What does it mean to "block the FE-NEEDSPONSOR <https://bugzilla.redhat.com/show_bug.cgi?id=FE-NEEDSPONSOR> tracking bug" ? So far, I have https://bugzilla.redhat.com/show_bug.cgi?id=1953340 Any help very welcome Thanks JM Short answer: wait for someone to review your package submission, meanwhile you can do some informal reviews as described here [1] to show some sponsor you actually comprehend Fedora Packaging Guidelines [2]. Becoming a Fedora packager and being allowed to push software in Fedora official repositories require following specific rules and standards. Just like getting a driver license, you're required to study the rules and to show you know how to do things. You cannot just jump in a car and start driving (at least, not in Italy). BTW from a quick look at your specfile, the changelog doesn't seem to be in the prescribed format.

Mattia [1] https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_gro... [2] https://docs.fedoraproject.org/en-US/packaging-guidelines/ _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)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

Perhaps we could improve the wiki page on Joining** to make it more clear what the process is like? I read through the guidelines and the Joining page a couple times, and only near the end does it state that Joining is more about, well, joining as a person than publishing a package. I believe it then recommendeds Copr around that point for simple publishing. Maybe we could ask Docs and some newer joiners to do a little review of the wiki for Joining and see if we can rewrite and modernize? On Fri., Apr. 30, 2021, 10:43 a.m. Stephen John Smoogen, <smooge(a)gmail.com&gt; wrote: > > > On Fri, 30 Apr 2021 at 12:26, Mattia Verga via devel < > devel(a)lists.fedoraproject.org&gt; wrote: > >> Il 30/04/21 15:16, Joan Moreau via devel ha scritto: >> >> Thanks but I am really scratching my head to try to understand all this: >> >> 1 - How to get to the "packager" group ou forum or else ? >> >> 2 - What does it mean to "block the FE-NEEDSPONSOR >> <https://bugzilla.redhat.com/show_bug.cgi?id=FE-NEEDSPONSOR> tracking >> bug" ? >> >> So far, I have https://bugzilla.redhat.com/show_bug.cgi?id=1953340 >> >> Any help very welcome >> >> Thanks >> >> JM >> >> Short answer: wait for someone to review your package submission, >> meanwhile you can do some informal reviews as described here [1] to show >> some sponsor you actually comprehend Fedora Packaging Guidelines [2]. >> >> Becoming a Fedora packager and being allowed to push software in Fedora >> official repositories require following specific rules and standards. Just >> like getting a driver license, you're required to study the rules and to >> show you know how to do things. You cannot just jump in a car and start >> driving (at least, not in Italy). >> >> BTW from a quick look at your specfile, the changelog doesn't seem to be >> in the prescribed format. >> > > So going from this long list of posts, I think the core problem is that > new people do not have a good idea of what it means to have a package in > Fedora Linux. > > Fedora Linux is built around the idea that it is a total operating > system, which means that the packages should be integrated with each other. > This means that the packages in it have some knowledge of how the rest of > the operating system works so that they a) do not interfere with each other > and b) are able to ask for and use resources properly from other systems. > Over the ~30 years of Linux operating systems a lot of corner cases and > other complexities have been discovered which are boiled down in each > operating system's "packaging rules". Because Fedora Linux releases every 6 > months, there are additional complexities which are needed to allow for > someone else to 'take over a package' that require 'prescribed formats and > rules of the road'. Finally because each application in a 'total operating > system' can affect the security of many different computers, there needs to > be a certain amount of trust between people on who the packager is, why > they are doing something, and what they know. > > This means that becoming a Fedora Packager requires some training > (usually done by oneself) and it requires commitment for working through > the process of becoming a packager. Similar processes are needed to add > packages in Debian and some other Linux distributions also. > > It is a lot of work, and it is probably something we should be more > upfront with (we mainly forget because most of us 'joined the club' years > ago). > > > > >> Mattia >> >> [1] >> https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_gro... >> [2] https://docs.fedoraproject.org/en-US/packaging-guidelines/ >> _______________________________________________ >> devel mailing list -- devel(a)lists.fedoraproject.org >> To unsubscribe send an email to devel-leave(a)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 >> > > > -- > Stephen J Smoogen. > I've seen things you people wouldn't believe. Flame wars in > sci.astro.orion. I have seen SPAM filters overload because of Godwin's Law. > All those moments will be lost in time... like posts on BBS... > _______________________________________________ > devel mailing list -- devel(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave(a)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 >

Bryce Carson kirjoitti 1.5.2021 klo 3.21: For what it's worth, I'm trying to join and have a package included and there are definitely some areas I would like to improve. Should we make a thread on their mailing list? On Fri., Apr. 30, 2021, 5:50 p.m. Bryce Carson, <bryce.a.carson(a)gmail.com&gt; wrote: Perhaps we could improve the wiki page on Joining** to make it more clear what the process is like? I read through the guidelines and the Joining page a couple times, and only near the end does it state that Joining is more about, well, joining as a person than publishing a package. I believe it then recommendeds Copr around that point for simple publishing. Maybe we could ask Docs and some newer joiners to do a little review of the wiki for Joining and see if we can rewrite and modernize?

Il 01/05/21 10:21, Joan Moreau via devel ha scritto: > > For instance, personally, I am not using Fedora at all (Arch fan ;) ) > but just willing to make my piece of software available widely for > those interested. I am happy to maintain the package in the long run, > but will not get involve to much into Fedora project except my small > piece of software contribution. > > That's absolutely fine, but in my opinion the wiki should clarify one thing: a certain amount of involvement in Fedora should be taken into account if one wants to become a packager. I don't think it's not entirely clear that by publishing a package in Fedora repositories implies 1) maintain the package updated, 2) maintain the specfile in line with future Packaging Guidelines changes and 3) get in touch with the community to handle possible bugs filed by other users which install your package. There must be a section that clearly states that if the scope is "I made this piece of software and I'll fire through Fedora repositories, then goodbye", or "I use this software, I'll push into Fedora repositories and never touch it again until this version is fine for me" there are other means to achieve that. That's the reason for having the "sponsorship barrier" at joining time, that, I know very well, it's quite scaring if you're not English mother tongue. Anyway, after a successful review of a package, one could get in touch with some sponsors by filing a ticket in the appropriate page [1] and some nice folk will help them to enter the packager group. Mattia [1] https://pagure.io/packager-sponsors/ _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)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

Il 01/05/21 10:21, Joan Moreau via devel ha scritto: > For instance, personally, I am not using Fedora at all (Arch fan ;) ) > but just willing to make my piece of software available widely for > those interested. I am happy to maintain the package in the long run, > but will not get involve to much into Fedora project except my small > piece of software contribution. > > That's absolutely fine, but in my opinion the wiki should clarify one thing: a certain amount of involvement in Fedora should be taken into account if one wants to become a packager. I don't think it's not entirely clear that by publishing a package in Fedora repositories implies 1) maintain the package updated, 2) maintain the specfile in line with future Packaging Guidelines changes and 3) get in touch with the community to handle possible bugs filed by other users which install your package. There must be a section that clearly states that if the scope is "I made this piece of software and I'll fire through Fedora repositories, then goodbye", or "I use this software, I'll push into Fedora repositories and never touch it again until this version is fine for me" there are other means to achieve that. That's the reason for having the "sponsorship barrier" at joining time, that, I know very well, it's quite scaring if you're not English mother tongue. Anyway, after a successful review of a package, one could get in touch with some sponsors by filing a ticket in the appropriate page [1] and some nice folk will help them to enter the packager group. Mattia [1] https://pagure.io/packager-sponsors/ _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)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

On Mon, May 03, 2021 at 11:11:23AM +0200, Vít Ondruch wrote: > Just FTR, if anybody has some specific proposal but don't feel > empowered to update the wiki, I think it is still good idea to make > a copy of the wiki page in their personal space and add the > suggestions on top of that page. This way, the specific proposal can > be shared with wider audience for a review, until it is deemed > acceptable. > > E.g. in the old days when packaging guidelines were kept in wiki, I > used to have drafts like this [1, 2] in my personal space where it > is obvious what I am proposing and what is the difference to > original. With the new system, you can fork https://pagure.io/packaging-committee/blob/master/f/guidelines/modules/RO... and similarly get the differences, and even submit pull requests which can be commented on.

On Mon, May 03, 2021 at 04:29:54PM +0200, Vít Ondruch wrote: > Right, but this sub- thread it about > https://fedoraproject.org/wiki/Join_the_package_collection_maintainers Ah, sorry. I got lost. :) But now that you mention it, I'd like to see that migrated to the new docs system too. -- Matthew Miller <mattdm(a)fedoraproject.org&gt; Fedora Project Leader _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)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

Could you comment on the status of repository package-maintainer-docs at pagure.io [1]? It looks like it is intended to be that migration, I wanted to contribute and started with a tiny pull request (to be followed by more substantial ones), but there has been no reaction from you or other admins.

Thank you the explanation. If you hand the repository over to me, I can see that material from the wiki is migrated there and the repository published at docs.fp.o Engineering Teams [1] as "Package Maintainers" ( or is it officially "Fedora Package Maintainers"?). And that tooling is updated to Antora for sure.

On 01.05.2021 10:21, Joan Moreau via devel wrote: > For instance, personally, I am not using Fedora at all (Arch fan ;) ) > but just willing to make my piece of software available widely for > those interested. I am happy to maintain the package in the long run, > but will not get involve to much into Fedora project except my small > piece of software contribution. You can use COPR for your software then. No join barrier at all.

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)

Hello How can I move forward on this ? Thank you

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.

Honeslt y , process is so complicated Now, I am again getting errors about "unaotirzed url" How to make things happens intesaod of all thisnightmare ? Thank you On Wed, 2021-06-23 at 19:58 +0200, Arthur Bols wrote: > On 23/06/2021 19:34, Joan Moreau via devel wrote: > > Hello > > > > How can I move forward on this ? > > > > Thank you > Hi Joan, > > Could you elaborate please? > > As Emmanuel said, you have two options: > > 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. > > Arthur > _______________________________________________ > devel mailing list -- devel(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave(a)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(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)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

The process is complicated for multiple reasons: 1. There are a lot of steps to deal with corner cases which have come up over the years which need to be dealt with. 2. There are some steps to make sure that the package is going to be maintained versus just dropped and forgotten as a lot of packages have been. 3. There are a lot of warts/headaches/problems which have been there but people who have packaged for 20 years no longer see (or in a Stockholm syndrome feel they NEED to be there.) In packaging software there are a set of steps you need to ask yourself: 1. Why are you wanting to do this task? 2. What do you expect to get out of this? 3. How committed are you to continually packaging this software? 4. What does this software bring to a complete operating system? 5. Why this operating system?

The first three questions are mostly about personal motivations but it is something that I see people not answering and then burning themselves out on finding out how complicated packaging is. Packaging up software is a long term commitment. It is saying 'I think this software is useful and will be maintained for years at a time.' If the software is more of a short term project or you really don't think that you (or others) want to keep fixing/maintaining it for years.. then the software doesn't really need to be in a distribution but in some sort of PPA or COPR. The fourth and fifth are to deal with marketing the software. Just having it in a distribution isn't going to get it to be used. [In most distribution early years, they don't take this part seriously and then end up with hundreds or thousands of ghost packages which end up being a pain. A distribution then starts adding more 'does anyone need this really???' type roadblocks which may go into overkill. Or it may be that putting it in the operating system is going to be a headache the entire time because the way the operating system deals with the language set is more work than you care for. For Fedora/RHEL, programs written in newer languages like Java, Go, Rust are going to have a lot of rules which seem completely antithetical to how the language is set up elsewhere. Getting software written in these is going to need a LOT of extra work which requires even more dedication. [I am not saying that they shouldn't be done, but it is more like the 'packaging game' is set to Instadeath/Torment X mode. On Sat, 26 Jun 2021 at 06:38, Joan Moreau via devel <devel(a)lists.fedoraproject.org&gt; wrote: > Honeslt y , process is so complicated > > Now, I am again getting errors about "unaotirzed url" > > How to make things happens intesaod of all thisnightmare ? > > Thank you > > > > On Wed, 2021-06-23 at 19:58 +0200, Arthur Bols wrote: > > On 23/06/2021 19:34, Joan Moreau via devel wrote: > > Hello > > How can I move forward on this ? > > Thank you > > Hi Joan, > > Could you elaborate please? > > As Emmanuel said, you have two options: > > 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. > > > Arthur > _______________________________________________ > devel mailing list -- devel(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave(a)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(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave(a)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

Hello How can I move forward on this ? Thank you On April 27, 2021 21:51:53 Joan Moreau via devel <devel(a)lists.fedoraproject.org&gt; wrote: > 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") > I tried "fedpkg request-repo --exception dovecot-fts-xapian" -> Lead some > error ("fedpkg request-repo --exception dovecot-fts-xapian") > I filed a "bug" on redhat : https://bugzilla.redhat.com/show_bug.cgi?id=1953340 > > And now, how to get things moving ? > Isnt' there just a repo where to push the RPM ? (similar to Arch) > thank you so much > > > > On 2021-04-25 15:51, Emmanuel Seyman wrote: >> * 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(a)lists.fedoraproject.org >> To unsubscribe send an email to devel-leave(a)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(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave(a)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

What is next ?

* 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(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)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

In practical terms, how to get a "sponsor" ? On 2021-06-29 11:13, Sérgio Basto wrote: > On Sat, 2021-06-26 at 22:34 +0200, Emmanuel Seyman wrote: > > * 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 > > > > https://fedoraproject.org/wiki/Join_the_package_collection_maintainers > https://fedoraproject.org/wiki/Package_maintenance_guide > > > > Emmanuel > > _______________________________________________ > > devel mailing list -- devel(a)lists.fedoraproject.org > > To unsubscribe send an email to devel-leave(a)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

Il 02/07/21 22:29, Joan Moreau via devel ha scritto: > In practical terms, how to get a "sponsor" ? Open a ticket in https://pagure.io/packager-sponsors/issues and ask there for guidance. Mattia _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)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

Il 03/07/21 16:58, Joan Moreau via devel ha scritto: > > Thanks to you and @eclipseo > > This has already been a full nightmare to create the SRPM file, and > now it seems that I again need to an additional nightmare to "prove > myself" > > The package is already in Deb and archlinux (*). Isn't it enough to > push it to Fedora ? > > Thanks > > > (*) > > https://packages.debian.org/bullseye/dovecot-fts-xapian > <https://packages.debian.org/bullseye/dovecot-fts-xapian> > > https://archlinux.org/packages/?q=dovecot-fts-xapian > <https://archlinux.org/packages/?q=dovecot-fts-xapian> > > The SRPM file may be fine, but the packager may not. What we are trying to make you understand is that to be admitted as Fedora packager you must prove your reliability. Posting comments such as: "I don't really plan to 'show my worth' but just willing to maintain this small and usefull package" or refusing to read and follow guidelines, keeping posting complaints here don't really make a good impression. Mattia _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)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

but now, honestly, I don't really know what to do.

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.

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.

So, if we can do anything to make it easier for developers to just maintain their one or two tools for the Fedora community, that'll be good.

On Sat, Aug 21, 2021 11:31:32 +0200, Vitaly Zaitsev via devel wrote: On 21/08/2021 10:57, Ankur Sinha wrote: So, if we can do anything to make it easier for developers to just maintain their one or two tools for the Fedora community, that'll be good. And we will get a lot of low-quality packages with bundled a lot of libraries, ignoring Fedora build flags, guidelines, etc. Look at Flathub for example.

Il 02/07/21 22:29, Joan Moreau via devel ha scritto: > In practical terms, how to get a "sponsor" ? Open a ticket in https://pagure.io/packager-sponsors/issues and ask there for guidance. Mattia _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)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