Re: EPEL8: neofetch package request

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thank you for letting us know.

The need to inform epel-devel of adding a package is only if the
package is a "Limited Arch" package.  Since your package is a noarch
package, and thus will be available for all arches, you do not need to
inform us, nor wait for our approval.
Please proceed with the packaging guidelines and request the branch.

On Fri, Jan 3, 2020 at 7:34 AM Kees de Jong <kees.dejong+dev@xxxxxxxxxx> wrote:
>
> Hi,
>
>
> I got the request to package `neofetch` for EPEL8 [1]. It's already in
> Fedora for quite some time [2]. I have the intention to grant this
> request. According to the EPEL packaging guidelines I need to inform
> you first of this intention [3]. The package should work fine. If there
> are no objections then I'll go through the packaging guidelines and
> request a branch for EPEL8.
>
>
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1786483
> [2]
> https://src.fedoraproject.org/rpms/neofetch/blob/master/f/neofetch.spec
> [3] https://fedoraproject.org/wiki/EPEL:Packaging
>
>
>
> --
> Met vriendelijke groet,
> Kees de Jong
>
> De informatie opgenomen in deze e-mail kan vertrouwelijk zijn en is
> uitsluitend bestemd voor de geadresseerde(n). Indien u deze e-mail
> onterecht ontvangt, wordt u verzocht de inhoud niet te gebruiken en de
> afzender direct te informeren door de e-mail te retourneren. Aan deze
> e-mail inclusief de bijlagen kunnen geen rechten ontleend worden,
> tenzij schriftelijk anders wordt overeengekomen.
> --
> The information contained in this e-mail may be confidential and is
> intended to be exclusively for the addressee(s). Should you receive
> this e-mail unintentionally, please do not use the contents herein and
> notify the sender immediately by return e-mail. This e-mail including
> the attachments are not legally binding, unless otherwise agreed upon
> in writing.
> --
> OpenPGP fingerprint: 0x0E45C98AB51428E6
> _______________________________________________
> epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux