On Fri, 30 Apr 2021 at 12:26, Mattia Verga via devel <
devel(a)lists.fedoraproject.org> 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).
--
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...