Get Sponsored for my package
Hi, all I saw https://fedoraproject.org/wiki/Join_the_package_collection_maintainers and I have submit my review requst to bugzilla. https://bugzilla.redhat.com/show_bug.cgi?id=1882871 Can anyone help me review it. What should I do next to get sponsored into package group? Thanks! -- Ruki Wang war...@gmail.com https://github.com/waruqi https://twitter.com/waruqi ___ 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
Re: build rpm from spec file fails on fedora-eln-armhfp
Ok, Thanks! Pavel Raiskup 于2020年10月6日周二 下午3:24写道： > On Tuesday, October 6, 2020 5:24:09 AM CEST Ruki Wang wrote: > > Thanks, but now all fedora-eln-* failed. > > > > https://copr.fedorainfracloud.org/coprs/waruqi/xmake/build/1695687/ > > > > warning: > /var/lib/mock/fedora-eln-x86_64-1601952807.335959/root/var/cache/dnf/eln-78c0f68aeb10b59c/packages/krb5-libs-1.18.2-24.eln104.x86_64.rpm: > > Header V4 RSA/SHA256 Signature, key ID 45719a39: NOKEY > > Fedora ELN - Developmental modular packages for 1.6 MB/s | 1.6 kB > 00:00 > > GPG key at > file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-rawhide-primary > > (0x9570FF31) is already installed > > The GPG keys listed for the "Fedora ELN - Developmental modular > > packages for the next Enterprise Linux release" repository are already > > installed but they are not correct for this package. > > Check that the correct key URLs are configured for this repository.. > > Failing package is: krb5-libs-1.18.2-24.eln104.x86_64 > > GPG Keys are configured as: > > > file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-rawhide-primary > > Public key for redhat-rpm-config-175-1.eln104.noarch.rpm is not > > installed. Failing package is: redhat-rpm-config-175-1.eln104.noarch > > GPG Keys are configured as: > > > file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-rawhide-primary > > Public key for rpm-4.16.0-2.eln104.x86_64.rpm is not installed. > > Failing package is: rpm-4.16.0-2.eln104.x86_64 > > GPG Keys are configured as: > > > file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-rawhide-primary > > Public key for rpm-build-4.16.0-2.eln104.x86_64.rpm is not installed. > > Failing package is: rpm-build-4.16.0-2.eln104.x86_64 > > GPG Keys are configured as: > > > file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-rawhide-primary > > Public key for rpm-build-libs-4.16.0-2.eln104.x86_64.rpm is not > > installed. Failing package is: rpm-build-libs-4.16.0-2.eln104.x86_64 > > GPG Keys are configured as: > > > file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-rawhide-primary > > Public key for rpm-libs-4.16.0-2.eln104.x86_64.rpm is not installed. > > Failing package is: rpm-libs-4.16.0-2.eln104.x86_64 > > GPG Keys are configured as: > > > file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-rawhide-primary > > Error: GPG check FAILED > > The ELN repo is not mirrored ATM (see discussion [1]), so it is likely > we'll see > some temporary issues like that. Copr/Mock can not do anything sane about > this. > Please re-try the build. > > [1] > https://github.com/rpm-software-management/mock/issues/614#issuecomment-671405333 > > Pavel > > On Monday, October 5, 2020 9:41:44 AM CEST Pavel Raiskup wrote: > > On Monday, October 5, 2020 9:23:14 AM CEST Florian Weimer wrote: > > > * Ruki Wang: > > > > > > > Errors during downloading metadata for repository 'eln': > > > > - Status code: 404 for > https://odcs.fedoraproject.org/composes/production/latest-Fedora-ELN/compose/Everything/armhfp/os/repodata/repomd.xml > (IP: 67.219.144.68) > > > > > > Looks like COPR is still trying to build ELN on armhfp, but it's not > > > longer available. > > > > > > I believe there is a checkbox in the COPR web UI you can untick, but > > > eventually, this has to be adjusted by the COPR administrators. > > > > Thanks for the reminder. The chroot has just been deactivated in Copr. > > > > Pavel > > > > > Thanks, > > > Florian > > > -- > > > Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, > > > Commercial register: Amtsgericht Muenchen, HRB 153243, > > > Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, > Michael O'Neill > > > ___ > > > 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 > > > > > > > > > > > ___ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org >
Re: build rpm from spec file fails on fedora-eln-armhfp
My spec file:
https://download.copr.fedorainfracloud.org/results/waruqi/xmake/fedora-eln-armhfp/01693870-xmake/xmake.spec
Ruki Wang 于2020年10月5日周一 上午8:50写道：
> Hi all,
>
> I'm building rpm from spec file on copr and doing some tests.
>
> But It always failed on fedora-eln-armhfp.
>
> I don’t know if it’s the spec or dnf.
>
> https://copr.fedorainfracloud.org/coprs/waruqi/xmake/build/1693870/
>
> https://download.copr.fedorainfracloud.org/results/waruqi/xmake/fedora-eln-armhfp/01693870-xmake/builder-live.log.gz
>
> Fedora ELN - Developmental modular packages for 721 B/s | 284 B 00:00
> Errors during downloading metadata for repository 'eln':
> - Status code: 404 for
> https://odcs.fedoraproject.org/composes/production/latest-Fedora-ELN/compose/Everything/armhfp/os/repodata/repomd.xml
> (IP: 67.219.144.68)
> Error: Failed to download metadata for repo 'eln': Cannot download
> repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
> INFO: chroot_scan: 3 files copied to
> /var/lib/copr-rpmbuild/results/chroot_scan
> INFO:
> /var/lib/mock/fedora-eln-armv7hl-1601776907.784619/root/var/log/dnf.rpm.log
> /var/lib/mock/fedora-eln-armv7hl-1601776907.784619/root/var/log/dnf.librepo.log
> /var/lib/mock/fedora-eln-armv7hl-1601776907.784619/root/var/log/dnf.log
> ERROR: Exception(/tmp/copr-rpmbuild-rb6vsdi2/xmake.spec)
> Config(fedora-eln-armv7hl) 0 minutes 23 seconds
> INFO: Results and/or logs in: /var/lib/copr-rpmbuild/results
> INFO: Cleaning up build root ('cleanup_on_failure=True')
>
>
> Can you help me?
>
> Thanks!
>
> --
>
> Ruki Wang
> war...@gmail.com
> https://github.com/waruqi
> https://twitter.com/waruqi
>
>
--
Ruki Wang
war...@gmail.com
https://github.com/waruqi
https://twitter.com/waruqi
___
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
build rpm from spec file fails on fedora-eln-armhfp
Hi all,
I'm building rpm from spec file on copr and doing some tests.
But It always failed on fedora-eln-armhfp.
I don’t know if it’s the spec or dnf.
https://copr.fedorainfracloud.org/coprs/waruqi/xmake/build/1693870/
https://download.copr.fedorainfracloud.org/results/waruqi/xmake/fedora-eln-armhfp/01693870-xmake/builder-live.log.gz
Fedora ELN - Developmental modular packages for 721 B/s | 284 B 00:00
Errors during downloading metadata for repository 'eln':
- Status code: 404 for
https://odcs.fedoraproject.org/composes/production/latest-Fedora-ELN/compose/Everything/armhfp/os/repodata/repomd.xml
(IP: 67.219.144.68)
Error: Failed to download metadata for repo 'eln': Cannot download
repomd.xml: Cannot download repodata/repomd.xml: All mirrors were
tried
INFO: chroot_scan: 3 files copied to /var/lib/copr-rpmbuild/results/chroot_scan
INFO:
/var/lib/mock/fedora-eln-armv7hl-1601776907.784619/root/var/log/dnf.rpm.log
/var/lib/mock/fedora-eln-armv7hl-1601776907.784619/root/var/log/dnf.librepo.log
/var/lib/mock/fedora-eln-armv7hl-1601776907.784619/root/var/log/dnf.log
ERROR: Exception(/tmp/copr-rpmbuild-rb6vsdi2/xmake.spec)
Config(fedora-eln-armv7hl) 0 minutes 23 seconds
INFO: Results and/or logs in: /var/lib/copr-rpmbuild/results
INFO: Cleaning up build root ('cleanup_on_failure=True')
Can you help me?
Thanks!
--
Ruki Wang
war...@gmail.com
https://github.com/waruqi
https://twitter.com/waruqi
___
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
Re: %set_build_flags problem in rpm spec file
It works fine, Thanks!
Neal Gompa 于2020年10月3日周六 下午10:55写道：
> On Sat, Oct 3, 2020 at 10:18 AM Vitaly Zaitsev via devel
> wrote:
> >
> > On 03.10.2020 15:47, Ruki Wang wrote:
> > > I try `%?set_build_flags` and it works fine.
> >
> > No, it will not. This command will just force RPM to ignore errors. No
> > actual build flags will be forwarded.
> >
> > You need to create separate SPEC files for Fedora and openSUSE.
> >
>
> That's not even close to true. The solution is quite simple for
> handling openSUSE Leap.
>
> Instead of "%set_build_flags" or "%?set_build_flags", do the following:
>
> %if 0%{?suse_version} && 0%{?suse_version} < 1550
> export CFLAGS="%{optflags}"
> export CXXFLAGS="%{optflags}"
> %else
> %set_build_flags
> %endif
>
>
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
> ___
> 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
>
--
Ruki Wang
war...@gmail.com
https://github.com/waruqi
https://twitter.com/waruqi
___
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
Re: %set_build_flags problem in rpm spec file
ok, I will try it. Thanks! : )
在 2020年10月3日星期六，Neal Gompa 写道：
> On Sat, Oct 3, 2020 at 10:18 AM Vitaly Zaitsev via devel
> wrote:
> >
> > On 03.10.2020 15:47, Ruki Wang wrote:
> > > I try `%?set_build_flags` and it works fine.
> >
> > No, it will not. This command will just force RPM to ignore errors. No
> > actual build flags will be forwarded.
> >
> > You need to create separate SPEC files for Fedora and openSUSE.
> >
>
> That's not even close to true. The solution is quite simple for
> handling openSUSE Leap.
>
> Instead of "%set_build_flags" or "%?set_build_flags", do the following:
>
> %if 0%{?suse_version} && 0%{?suse_version} < 1550
> export CFLAGS="%{optflags}"
> export CXXFLAGS="%{optflags}"
> %else
> %set_build_flags
> %endif
>
>
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
> ___
> 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
>
--
Ruki Wang
war...@gmail.com
https://github.com/waruqi
https://twitter.com/waruqi
___
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
Re: %set_build_flags problem in rpm spec file
I try `%?set_build_flags` and it works fine. Thanks! Miro Hrončok 于2020年10月3日周六 下午2:45写道： > On 03. 10. 20 5:04, Ruki Wang wrote: > > Hi, every one. > > > > I am making rpm spec and doing tests on copr. > > > > But on opensuse-leap-15.1-*, %set_build_flags still causes some problems. > > > > > > + %set_build_flags > > /var/tmp/rpm-tmp.9RYL8i: line 32: fg: no job control > > error: Bad exit status from /var/tmp/rpm-tmp.9RYL8i (%build) > > Bad exit status from /var/tmp/rpm-tmp.9RYL8i (%build) > > > > > > Links: > > > > https://copr.fedorainfracloud.org/coprs/waruqi/xmake/build/1693007/ > > > https://download.copr.fedorainfracloud.org/results/waruqi/xmake/opensuse-leap-15.2-x86_64/01693007-xmake/builder-live.log.gz > > < > https://download.copr.fedorainfracloud.org/results/waruqi/xmake/opensuse-leap-15.2-x86_64/01693007-xmake/builder-live.log.gz > > > > > > Buzilla: > > https://bugzilla.redhat.com/show_bug.cgi?id=1882871 > > > > Does anyone know the reason for this? Thanks! > > <https://bugzilla.redhat.com/show_bug.cgi?id=1882871> > > Yes. The reason is openSUSE and Fedora are different. and they don't have > our macro. > > A quick "make it build" action would be to add ?: > > %?set_build_flags > > However, the openSUSE build might not have the proper flags. > > -- > Miro Hrončok > -- > Phone: +420777974800 > IRC: mhroncok > ___ > 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 > -- Ruki Wang war...@gmail.com https://github.com/waruqi https://twitter.com/waruqi ___ 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
Re: %set_build_flags problem in rpm spec file
Got it, thanks! Neal Gompa 于2020年10月3日周六 下午8:07写道： > On Sat, Oct 3, 2020 at 2:45 AM Miro Hrončok wrote: > > > > On 03. 10. 20 5:04, Ruki Wang wrote: > > > Hi, every one. > > > > > > I am making rpm spec and doing tests on copr. > > > > > > But on opensuse-leap-15.1-*, %set_build_flags still causes some > problems. > > > > > > > > > + %set_build_flags > > > /var/tmp/rpm-tmp.9RYL8i: line 32: fg: no job control > > > error: Bad exit status from /var/tmp/rpm-tmp.9RYL8i (%build) > > > Bad exit status from /var/tmp/rpm-tmp.9RYL8i (%build) > > > > > > > > > Links: > > > > > > https://copr.fedorainfracloud.org/coprs/waruqi/xmake/build/1693007/ > > > > https://download.copr.fedorainfracloud.org/results/waruqi/xmake/opensuse-leap-15.2-x86_64/01693007-xmake/builder-live.log.gz > > > < > https://download.copr.fedorainfracloud.org/results/waruqi/xmake/opensuse-leap-15.2-x86_64/01693007-xmake/builder-live.log.gz > > > > > > > > Buzilla: > > > https://bugzilla.redhat.com/show_bug.cgi?id=1882871 > > > > > > Does anyone know the reason for this? Thanks! > > > <https://bugzilla.redhat.com/show_bug.cgi?id=1882871> > > > > Yes. The reason is openSUSE and Fedora are different. and they don't > have our macro. > > > > A quick "make it build" action would be to add ?: > > > > %?set_build_flags > > > > However, the openSUSE build might not have the proper flags. > > > > It's because %set_build_flags was introduced in RPM 4.15, and openSUSE > Leap 15.x uses RPM 4.14. Moreover, openSUSE Leap 15.1 predates the > introduction of the macro even upstream. It was not backported into > openSUSE Leap 15.2 either, so the macro just doesn't exist in openSUSE > Leap yet. > > The macro was backported to RHEL 8 during its development, so it > exists there despite it using RPM 4.14 as well. > > > > > -- > 真実はいつも一つ！/ Always, there's only one truth! > ___ > 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 > -- Ruki Wang war...@gmail.com https://github.com/waruqi https://twitter.com/waruqi ___ 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
%set_build_flags problem in rpm spec file
Hi, every one. I am making rpm spec and doing tests on copr. But on opensuse-leap-15.1-*, %set_build_flags still causes some problems. + %set_build_flags /var/tmp/rpm-tmp.9RYL8i: line 32: fg: no job control error: Bad exit status from /var/tmp/rpm-tmp.9RYL8i (%build) Bad exit status from /var/tmp/rpm-tmp.9RYL8i (%build) Links: https://copr.fedorainfracloud.org/coprs/waruqi/xmake/build/1693007/ https://download.copr.fedorainfracloud.org/results/waruqi/xmake/opensuse-leap-15.2-x86_64/01693007-xmake/builder-live.log.gz <https://download.copr.fedorainfracloud.org/results/waruqi/xmake/opensuse-leap-15.2-x86_64/01693007-xmake/builder-live.log.gz> Buzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1882871 Does anyone know the reason for this? Thanks! <https://bugzilla.redhat.com/show_bug.cgi?id=1882871> -- Ruki Wang war...@gmail.com https://github.com/waruqi https://twitter.com/waruqi ___ 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
Re: Self Introduction: Ruki Wang
Oh, It's great! I saw the QQ group. : ) Thanks! Robin Lee 于2020年9月25日周五 下午4:35写道： > On Fri, Sep 25, 2020 at 11:33 AM Ruki Wang wrote: > > > > > > Hi, all! > > > > I'm Ruki Wang, a full stack developer from China. I'm creator of @tboox > and @xmake-io Open Source Groups. My Github: https://github.com/waruqi > > > > I am developing xmake now. > > > > it's a lightweight cross-platform build utility based on Lua. > > > > It uses xmake.lua to maintain project builds. Compared with > makefile/CMakeLists.txt, the configuration syntax is more concise and > intuitive. It is very friendly to novices and can quickly get started in a > short time. Let users focus more on actual project development. > > > > It can compile the project directly like Make/Ninja, or generate project > files like CMake/Meson, and it also has a built-in package management > system to help users solve the integrated use of C/C++ dependent libraries. > > > > I have made it into an rpm package and uploaded it to the copr > repository. https://copr.fedorainfracloud.org/coprs/waruqi/xmake/ > > > > I know, now I can install it with the following command. > > > > sudo dnf copr enable waruqi/xmake > > sudo dnf install xmake > > > > > > But what I want to know is how should I do next to submit my package to > fedora's official repository? > > So that I can directly execute the following command to install the > package I uploaded. > > > > sudo dnf install xmake > > > > > > Thanks! > Welcome! > > You can get in touch with local user group from [1]. > And I am one of the packagers from China. Feel free to contact me > personally. > > [1] https://fedoraproject.org/wiki/FZUGCommunicate > > - robin > > > > -- > > > > Ruki Wang > > war...@gmail.com > > https://github.com/waruqi > > https://twitter.com/waruqi > > > > ___ > > 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 > ___ > 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 > -- Ruki Wang war...@gmail.com https://github.com/waruqi https://twitter.com/waruqi ___ 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
Re: Self Introduction: Ruki Wang
Hi, Vit Thank you very much for your reply, I will look at these documents. Thanks! Vít Ondruch 于2020年9月25日周五 下午4:13写道： > Hello and welcome! > > All information necessary to become Fedora packager should be available on > this page: > > https://fedoraproject.org/wiki/Join_the_package_collection_maintainers > > There is also Fedora Join SIG, which can help you with onboarding: > > https://docs.fedoraproject.org/en-US/fedora-join/index.html > > > Vít > > > Dne 25. 09. 20 v 5:32 Ruki Wang napsal(a): > > > Hi, all! > > I'm Ruki Wang, a full stack developer from China. I'm creator of @tboox > <https://github.com/tboox> and @xmake-io <https://github.com/xmake-io> Open > Source Groups. My Github: https://github.com/waruqi > > I am developing xmake <https://github.com/xmake-io/xmake> now. > > it's a lightweight cross-platform build utility based on Lua. > > It uses xmake.lua to maintain project builds. Compared with > makefile/CMakeLists.txt, the configuration syntax is more concise and > intuitive. It is very friendly to novices and can quickly get started in a > short time. Let users focus more on actual project development. > > It can compile the project directly like Make/Ninja, or generate project > files like CMake/Meson, and it also has a built-in package management > system to help users solve the integrated use of C/C++ dependent libraries. > > I have made it into an rpm package and uploaded it to the copr repository. > https://copr.fedorainfracloud.org/coprs/waruqi/xmake/ > > I know, now I can install it with the following command. > > sudo dnf copr enable waruqi/xmakesudo dnf install xmake > > > But what I want to know is how should I do next to submit my package to > fedora's official repository? > So that I can directly execute the following command to install the > package I uploaded. > > sudo dnf install xmake > > > Thanks! > > -- > > Ruki Wang > war...@gmail.com > https://github.com/waruqi > https://twitter.com/waruqi > > > ___ > 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 > > ___ > 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 > -- Ruki Wang war...@gmail.com https://github.com/waruqi https://twitter.com/waruqi ___ 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
Self Introduction: Ruki Wang
Hi, all! I'm Ruki Wang, a full stack developer from China. I'm creator of @tboox <https://github.com/tboox> and @xmake-io <https://github.com/xmake-io> Open Source Groups. My Github: https://github.com/waruqi I am developing xmake <https://github.com/xmake-io/xmake> now. it's a lightweight cross-platform build utility based on Lua. It uses xmake.lua to maintain project builds. Compared with makefile/CMakeLists.txt, the configuration syntax is more concise and intuitive. It is very friendly to novices and can quickly get started in a short time. Let users focus more on actual project development. It can compile the project directly like Make/Ninja, or generate project files like CMake/Meson, and it also has a built-in package management system to help users solve the integrated use of C/C++ dependent libraries. I have made it into an rpm package and uploaded it to the copr repository. https://copr.fedorainfracloud.org/coprs/waruqi/xmake/ I know, now I can install it with the following command. sudo dnf copr enable waruqi/xmakesudo dnf install xmake But what I want to know is how should I do next to submit my package to fedora's official repository? So that I can directly execute the following command to install the package I uploaded. sudo dnf install xmake Thanks! -- Ruki Wang war...@gmail.com https://github.com/waruqi https://twitter.com/waruqi ___ 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
