Re: Self Introduction: Yunmei Li
Hi, I have built Milvus package on Copr and reviewed it with Fedora-review. I fixed these items that are flagged as fail,but there are some items that are flagged as manual review needed. I am looking___ 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: Self Introduction: Yunmei Li
On 2/23/22 6:42 AM, Yunmei LI wrote: Hi, Thanks for your help! I reworked the Milvus package for EPEL8 based on the comments I received, and updated theSpec URL and SRPMURL on Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2055596 <https://bugzilla.redhat.com/show_bug.cgi?id=2055596> I am really lookingforward to someone reviewingMilvus package at the earliest convenience. Not a review, but does it build on Copr[1] or Koji[2] ? It may be helpful to check the Go SIG recommendations[3],[4]. You may also find OpenBuildService helpful[5]. [1] https://copr.fedorainfracloud.org/ [2] https://koji.fedoraproject.org/koji/ [3] https://fedoraproject.org/wiki/SIGs/Go [4] https://fedoraproject.org/wiki/PackagingDrafts/Go [5] https://openbuildservice.org/ Thanks, Yunmei Li From: "Ben Beasley"<mailto:c...@musicinmybrain.net>> Date: Mon, Feb 21, 2022, 22:11 Subject: Re: Self Introduction: Yunmei Li To: mailto:devel@lists.fedoraproject.org>> All current versions of *Fedora* have CMake 3.20 or later, so you shouldn’t have any problems there. When packaging for EPEL, you rely on the package versions that were released with the corresponding version of Red Hat Enterprise Linux. RHEL aims to provide long-term stability, so these mostly get bugfix releases and security backports rather than significant updates over the life of the distribution. This is largely the same update philosophy as individual Fedora releases, but with a lifecycle on the order of a decade rather than a year. Since RHEL 7.0 was released in 2014, most of the packages you can use when building for EPEL7 are based on pretty old upstream versions. In most cases, if the dependency versions in a particular release of RHEL don’t meet your needs, it means that it is not practical to build your package for the corresponding version of EPEL. There are a few exceptions—for example, you can get a newer compiler toolchain by using one of the devtoolset releases, e.g. [1]. If you can package for EPEL7 successfully, but only by doing things that don’t meet Fedora/EPEL guidelines (bundling dependencies without satisfying the conditions in [2], packaging your own newer-but-not-parallel-installable version of cmake to build with), then you might still be able to offer a package for EL7 distributions via COPR[3]. You might find that EPEL8 or EPEL9 are still viable targets. You also might find that the epel-devel mailing list is a helpful place to ask questions. – Ben [1] https://src.fedoraproject.org/rpms/sleef/blob/epel7/f/sleef.spec [2] https://docs.fedoraproject.org/en-US/packaging-guidelines/#bundling [3] https://docs.pagure.org/copr.copr/user_documentation.html#faq ___ 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: Self Introduction: Yunmei Li
Hi, Thanks for your help! I reworked the Milvus package for EPEL8 based on the comments I received, and updated the Spec URL and SRPM URL on Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=20555___ 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: Self Introduction: Yunmei Li
All current versions of *Fedora* have CMake 3.20 or later, so you shouldn’t have any problems there. When packaging for EPEL, you rely on the package versions that were released with the corresponding version of Red Hat Enterprise Linux. RHEL aims to provide long-term stability, so these mostly get bugfix releases and security backports rather than significant updates over the life of the distribution. This is largely the same update philosophy as individual Fedora releases, but with a lifecycle on the order of a decade rather than a year. Since RHEL 7.0 was released in 2014, most of the packages you can use when building for EPEL7 are based on pretty old upstream versions. In most cases, if the dependency versions in a particular release of RHEL don’t meet your needs, it means that it is not practical to build your package for the corresponding version of EPEL. There are a few exceptions—for example, you can get a newer compiler toolchain by using one of the devtoolset releases, e.g. [1]. If you can package for EPEL7 successfully, but only by doing things that don’t meet Fedora/EPEL guidelines (bundling dependencies without satisfying the conditions in [2], packaging your own newer-but-not-parallel-installable version of cmake to build with), then you might still be able to offer a package for EL7 distributions via COPR[3]. You might find that EPEL8 or EPEL9 are still viable targets. You also might find that the epel-devel mailing list is a helpful place to ask questions. – Ben [1] https://src.fedoraproject.org/rpms/sleef/blob/epel7/f/sleef.spec [2] https://docs.fedoraproject.org/en-US/packaging-guidelines/#bundling [3] https://docs.pagure.org/copr.copr/user_documentation.html#faq On 2/20/22 22:16, Yunmei LI wrote: Hi, Thanks for your suggestion, and I will rework my package based on your comments. A question by the way: I built an epel package on CentOS7, my package will depend on cmake 3.18 when it is building, but the latest version of cmake in Fedora is 3.17 (boost and openblas as well). What should I do if the software version in Fedora does not meet my needs？ Kind Regards, Yunmei Li From: "Felix Schwarz" Date: Fri, Feb 18, 2022, 17:02 Subject: Re: Self Introduction: Yunmei Li To: "Development discussions related to Fedora" Am 18.02.22 um 07:40 schrieb Yunmei LI: > We are looking to contribute Milvus to the fedora community to help more users with their AI applications. > I have already filled out a Milvus package review request in bugzilla: > https://bugzilla.redhat.com/show_bug.cgi?id=2055596 Welcome to Fedora. I'm always glad if companies help maintaining their software in Fedora (or other distros) :-) One just a little hint for your package: I think you'll have to rework this a bit. For example a Fedora package must not not depend on "epel-release" or "centos-release-scl-rh" (this is also true for EPEL packages). BuildRequiring "wget" seems strange. I guess the build process tries to download something from the internet which is also forbidden in Fedora. You MUST include all sources in your package or use packages already included in Fedora. I see that you list OpenBLAS, cmake, go, boost and tbb in your sources. You should remove all of these from your package and use only the packages already included in Fedora. This might be a bit of work especially for somewhat complex packages but it ensures that Fedora can provide some level of quality. So again, thank you for your contribution. It's a good start and I'm pretty sure that streamlining your software to match Fedora's processes will also help your upstream quality. Felix ___ 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 todevel-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
Re: Self Introduction: Yunmei Li
Hi, Thanks for your suggestion, and I will rework my package based on your comments. A question by the way: I built an epel package on CentOS7, my package will depend on cmake 3.18 when it is building___ 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: Self Introduction: Yunmei Li
Am 18.02.22 um 07:40 schrieb Yunmei LI: We are looking to contribute Milvus to the fedora community to help more users with their AI applications. I have already filled out a Milvus package review request in bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2055596 Welcome to Fedora. I'm always glad if companies help maintaining their software in Fedora (or other distros) :-) One just a little hint for your package: I think you'll have to rework this a bit. For example a Fedora package must not not depend on "epel-release" or "centos-release-scl-rh" (this is also true for EPEL packages). BuildRequiring "wget" seems strange. I guess the build process tries to download something from the internet which is also forbidden in Fedora. You MUST include all sources in your package or use packages already included in Fedora. I see that you list OpenBLAS, cmake, go, boost and tbb in your sources. You should remove all of these from your package and use only the packages already included in Fedora. This might be a bit of work especially for somewhat complex packages but it ensures that Fedora can provide some level of quality. So again, thank you for your contribution. It's a good start and I'm pretty sure that streamlining your software to match Fedora's processes will also help your upstream quality. Felix ___ 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
Self Introduction: Yunmei Li
Hi All: I am Yunmei Li and I am working at Zilliz as a DevOps engineer. I am an active contributor to the Milvus Vector Database project. Zilliz is an open-source software company dedicated to unstruc___ 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
