Re: python3 rpm macros not available without python3-devel installed

[Robin Lee]

The main issue is failing to use a macro defined with %__python3 to specify
the version of a requirement.

The recipe is sth like this:

%global py3_ver %(echo `%{__python3} -c "import sys;
sys.stdout.write(sys.version[:3])"`)

...

Requires:   python(abi) = %{py3_ver}

On Wed, Sep 15, 2010 at 10:32 PM, David Malcolm  wrote:

> I suspect I haven't had enough coffee yet, but I don't see the problem
> here.  Why not simply add "python3-devel" as a build requirement as
> Ignacio says?
>
> If a build requirement isn't installed, it's acceptable for a build to
> fail: it's a violation of a precondition.
>
> On Wed, 2010-09-15 at 19:35 +0800, Robin Lee wrote:
> > You should build this package in a clean root like a mock environment.
> > If you have python3-devel already installed and then run rpmbuild
> > --rebuild, you will not see the issue.
> >
> > On Wed, Sep 15, 2010 at 7:25 PM, Robin Lee 
> > wrote:
> > For a more concrete example:
> > https://bugzilla.redhat.com/show_bug.cgi?id=567348
> > I want to set the python(abi) requirement of the subpackage at
> > buildtime. So, I want to set it like this:
> > Requires: python(abi) = %{py3_ver}
> >
> > But when build it, it will fail with the following output:
> > $ rpmbuild -bp dreampie.spec
> > Building target platforms: i686
> > Building for target i686
> > sh: python3: command not found
> > sh: python3: command not found
> > sh: python3: command not found
> > error: line 46: Version required: Requires:   python(abi) =
> >
> > Even though python3-devel has been added as BR.
> >
> >
> >
> > On Wed, Sep 15, 2010 at 7:06 PM, Ignacio Vazquez-Abrams
> >  wrote:
> >
> > On Wed, 2010-09-15 at 18:22 +0800, Robin Lee wrote:
> > > python3 rpm macros not available without
> > python3-devel installed.
> > > 'rpmbuild --viewrc' will show you.
> > >
> > > So if you use the python3 macros to define another
> > macro and you have
> > > no python3-devel installed, you must fail.
> > >
> > > So, how to define, for example, a %py3_ver macro for
> > the major version
> > > of Python3? Must yum be used?
> > >
> > > Robin
> >
> >
> > Adding a "BuildRequires: python3-devel" should be
> > enough to pull them
> > in.
> >
> > --
> > Ignacio Vazquez-Abrams 
>
>
>
> ___
> python-devel mailing list
> python-de...@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/python-devel
>
___
python-devel mailing list
python-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/python-devel

Re: python3 rpm macros not available without python3-devel installed

[Robin Lee]

Oh, sorry. I may have chosen a bad email subject.

This failed scratch build shows what was happening:
https://koji.fedoraproject.org/koji/taskinfo?taskID=2468876

On Wed, Sep 15, 2010 at 11:07 PM, Robin Lee  wrote:

> The main issue is failing to use a macro defined with %__python3 to specify
> the version of a requirement.
>
> The recipe is sth like this:
>
> %global py3_ver %(echo `%{__python3} -c "import sys;
>
> sys.stdout.write(sys.version[:3])"`)
>
> ...
>
>
> Requires:   python(abi) = %{py3_ver}
>
> On Wed, Sep 15, 2010 at 10:32 PM, David Malcolm wrote:
>
>> I suspect I haven't had enough coffee yet, but I don't see the problem
>> here.  Why not simply add "python3-devel" as a build requirement as
>> Ignacio says?
>>
>> If a build requirement isn't installed, it's acceptable for a build to
>> fail: it's a violation of a precondition.
>>
>> On Wed, 2010-09-15 at 19:35 +0800, Robin Lee wrote:
>> > You should build this package in a clean root like a mock environment.
>> > If you have python3-devel already installed and then run rpmbuild
>> > --rebuild, you will not see the issue.
>> >
>> > On Wed, Sep 15, 2010 at 7:25 PM, Robin Lee 
>> > wrote:
>> > For a more concrete example:
>> > https://bugzilla.redhat.com/show_bug.cgi?id=567348
>> > I want to set the python(abi) requirement of the subpackage at
>> > buildtime. So, I want to set it like this:
>> > Requires: python(abi) = %{py3_ver}
>> >
>> > But when build it, it will fail with the following output:
>> > $ rpmbuild -bp dreampie.spec
>> > Building target platforms: i686
>> > Building for target i686
>> > sh: python3: command not found
>> > sh: python3: command not found
>> > sh: python3: command not found
>> > error: line 46: Version required: Requires:   python(abi) =
>> >
>> > Even though python3-devel has been added as BR.
>> >
>> >
>> >
>> > On Wed, Sep 15, 2010 at 7:06 PM, Ignacio Vazquez-Abrams
>> >  wrote:
>> >
>> > On Wed, 2010-09-15 at 18:22 +0800, Robin Lee wrote:
>> > > python3 rpm macros not available without
>> > python3-devel installed.
>> > > 'rpmbuild --viewrc' will show you.
>> > >
>> > > So if you use the python3 macros to define another
>> > macro and you have
>> > > no python3-devel installed, you must fail.
>> > >
>> > > So, how to define, for example, a %py3_ver macro for
>> > the major version
>> > > of Python3? Must yum be used?
>> > >
>> > > Robin
>> >
>> >
>> > Adding a "BuildRequires: python3-devel" should be
>> > enough to pull them
>> > in.
>> >
>> > --
>> > Ignacio Vazquez-Abrams 
>>
>>
>>
>> ___
>> python-devel mailing list
>> python-de...@lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/python-devel
>>
>
>
___
python-devel mailing list
python-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/python-devel

Re: orphan most of my packages

[Robin Lee]

python-alsa is taken by 'cheeselee'

On Sun, Oct 10, 2010 at 10:13 PM, Andy Shevchenko  wrote:

> Hello,
>
> I have no more time to support the following packages in the Fedora.
>
> jack-audio-connection-kit -- The Jack Audio Connection Kit
>
> klamav -- Clam Anti-Virus on the KDE Desktop
>
> man-pages-uk -- Ukrainian man pages from the Linux Documentation Project
>
> python-alsa -- Python binding for the ALSA library
>
> qstat -- Real-time Game Server Status for FPS game servers
>
> uniconvertor -- Universal vector graphics translator
>
>
> --
> With Best Regards,
> Andy Shevchenko
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
>
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: orphan most of my packages

[Robin Lee]

OK! I will look into them.


Robin

On Mon, Oct 18, 2010 at 3:44 AM, Andy Shevchenko
wrote:

> In the attachment a few patches which were not included in the Fedora
> yet. I don't remember for which version they are and what usefulness
> of them, but just in case I send them to you.
>
> On Sun, Oct 10, 2010 at 7:29 PM, Robin Lee 
> wrote:
> > python-alsa is taken by 'cheeselee'
> >
> > On Sun, Oct 10, 2010 at 10:13 PM, Andy Shevchenko
> >  wrote:
> >>
> >> Hello,
> >>
> >> I have no more time to support the following packages in the Fedora.
> >>
> >> jack-audio-connection-kit -- The Jack Audio Connection Kit
> >>
> >> klamav -- Clam Anti-Virus on the KDE Desktop
> >>
> >> man-pages-uk -- Ukrainian man pages from the Linux Documentation Project
> >>
> >> python-alsa -- Python binding for the ALSA library
> >>
> >> qstat -- Real-time Game Server Status for FPS game servers
> >>
> >> uniconvertor -- Universal vector graphics translator
> >>
> >>
> >> --
> >> With Best Regards,
> >> Andy Shevchenko
> >> --
> >> devel mailing list
> >> devel@lists.fedoraproject.org
> >> https://admin.fedoraproject.org/mailman/listinfo/devel
> >
> >
> > --
> > devel mailing list
> > devel@lists.fedoraproject.org
> > https://admin.fedoraproject.org/mailman/listinfo/devel
> >
>
>
>
> --
> With Best Regards,
> Andy Shevchenko
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
>
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: orphan most of my packages

[Robin Lee]

Did you send the patches upstream?

Robin

On Mon, Oct 18, 2010 at 3:44 AM, Andy Shevchenko
wrote:

> In the attachment a few patches which were not included in the Fedora
> yet. I don't remember for which version they are and what usefulness
> of them, but just in case I send them to you.
>
> On Sun, Oct 10, 2010 at 7:29 PM, Robin Lee 
> wrote:
> > python-alsa is taken by 'cheeselee'
> >
> > On Sun, Oct 10, 2010 at 10:13 PM, Andy Shevchenko
> >  wrote:
> >>
> >> Hello,
> >>
> >> I have no more time to support the following packages in the Fedora.
> >>
> >> jack-audio-connection-kit -- The Jack Audio Connection Kit
> >>
> >> klamav -- Clam Anti-Virus on the KDE Desktop
> >>
> >> man-pages-uk -- Ukrainian man pages from the Linux Documentation Project
> >>
> >> python-alsa -- Python binding for the ALSA library
> >>
> >> qstat -- Real-time Game Server Status for FPS game servers
> >>
> >> uniconvertor -- Universal vector graphics translator
> >>
> >>
> >> --
> >> With Best Regards,
> >> Andy Shevchenko
> >> --
> >> devel mailing list
> >> devel@lists.fedoraproject.org
> >> https://admin.fedoraproject.org/mailman/listinfo/devel
> >
> >
> > --
> > devel mailing list
> > devel@lists.fedoraproject.org
> > https://admin.fedoraproject.org/mailman/listinfo/devel
> >
>
>
>
> --
> With Best Regards,
> Andy Shevchenko
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
>
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

python-nltk ownership changed

[Robin Lee]

python-nltk ownership is passed from 'salimma' to 'cheeselee'.

Cheers.


Robin 'cheese' Lee
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: how to include a .so file in my python rpm

[Robin Lee]

Just remove the line 'BuildArch:  noarch' from your specfile?

On Wed, Jan 26, 2011 at 9:59 PM, Erik Blankinship wrote:

> In my python application, I need to include a .so binary I built of a
> custom gstreamer plugin.  My python application works fine with this plugin
> when launching from the command line.
>
> Now that I am packaging my python application into a fedora rpm, I need to
> compile the plugin as part of the packaging process?
>
> I ask because when I try to include the .so file in %files and part of the
> manifest, I get this error from rpmbuild:
>
> "arch dependent binaries in noarch package"
>
> Could someone point me to an example of how to create a spec file which
> shows how to include "nested" c code so as to avoid this error and
> successfully build my rpm?
>
> Thanks much.  Erik
>
> ___
> python-devel mailing list
> python-de...@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/python-devel
>
___
python-devel mailing list
python-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/python-devel

Re: scriplet issues installing deps in f23 mock

[Robin Lee]

I met the exact same problem.


-robin

On Wed, Sep 30, 2015 at 6:17 AM, Cole Robinson  wrote:

> I'm hitting scriplet errors when trying to build f23 qemu in mock on an up
> to
> date f23 host. Example:
>
> $ mock --root fedora-23-x86_64 --init
> ...
> $ mock --root fedora-23-x86_64 --rebuild qemu-2.4.0-4.fc23.src.rpm
> ...
>
> Transaction Summary
>
> 
> Install  48 Packages (+596 Dependent packages)
>
> Total size: 396 M
> Installed size: 1.1 G
> Downloading packages:
> Running transaction check
> Running transaction test
> Transaction test succeeded
> Running transaction (shutdown inhibited)
> error: %prein(texlive-base-4:2014-13.20140525_r34255.fc23.noarch) scriptlet
> failed, exit status 126
> Error in PREIN scriptlet in rpm package
> 4:texlive-base-2014-13.20140525_r34255.fc23.noarch
>   Installing : 2:libpng-1.6.17-2.fc23.x86_64
> 2/644
> error: texlive-base-4:2014-13.20140525_r34255.fc23.noarch: install failed
> warning: %post(libpng-2:1.6.17-2.fc23.x86_64) scriptlet failed, exit
> status 126
> Non-fatal POSTIN scriptlet failure in rpm package
> 2:libpng-1.6.17-2.fc23.x86_64
>   Installing : freetype-2.6.0-3.fc23.x86_64
>  3/644
> warning: %post(freetype-2.6.0-3.fc23.x86_64) scriptlet failed, exit status
> 126
> Non-fatal POSTIN scriptlet failure in rpm package
> freetype-2.6.0-3.fc23.x86_64
>   Installing : xorg-x11-proto-devel-7.7-16.fc23.noarch
> ...
>
>
> With many cascading failures after that.
>
> However if I invoke mock and request installing all the deps manually,
> everything works:
>
> $ mock --root fedora-23-x86_64 --init
> ...
> $ mock --root fedora-23-x86_64 --install SDL2-devel zlib-devel which
> chrpath
> gnutls-devel cyrus-sasl-devel libtool libaio-devel rsync pciutils-devel
> pulseaudio-libs-devel libiscsi-devel ncurses-devel libattr-devel
> usbredir-devel gperftools-devel texinfo perl-podlators spice-protocol
> spice-server-devel libseccomp-devel libcurl-devel ceph-devel systemtap
> systemtap-sdt-devel nss-devel xfsprogs-devel libjpeg-devel libpng-devel
> libuuid-devel bluez-libs-devel brlapi-devel libfdt-devel libcap-devel
> pixman-devel glusterfs-devel glusterfs-api-devel libusbx-devel
> libssh2-devel
> gtk3-devel vte3-devel gettext librdmacm-devel qemu-sanity-check-nodeps
> kernel
> iasl xen-devel numactl-devel bzip2-devel texi2html
> ...
>
> Transaction Summary
>
> 
> Install  48 Packages (+596 Dependent packages)
>
> Total size: 396 M
> Installed size: 1.1 G
> Downloading packages:
> Running transaction check
> Running transaction test
> Transaction test succeeded
> Running transaction (shutdown inhibited)
>   Installing : 4:texlive-base-2014-13.20140525_r34255.fc23.noarch
>  1/644
>   Installing : 2:libpng-1.6.17-2.fc23.x86_64
> 2/644
>   Installing : freetype-2.6.0-3.fc23.x86_64
>  3/644
>   Installing : xorg-x11-proto-devel-7.7-16.fc23.noarch
> 4/644
>   Installing : 4:texlive-kpathsea-lib-2014-13.20140525_r34255.fc23.x8
>  5/644
> ...
>
>
> Complete output of the working command:
> https://paste.fedoraproject.org/272899/14435647/
> Complete output of the failing command:
> http://paste.fedoraproject.org/272900/44356490
>
> Anyone know what the issue is, or where to go from here?
>
> Thanks,
> Cole
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

vmpk 0.6.0 license changed to 'GPLv3+'

[Robin Lee]

vmpk 0.6.0 license changed from 'GPLv3+ and (LGPLv2 with exception or
GPLv3)' to 'GPLv3+'.

Cheers
-robin
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

License of python-nltk-3.0.0 specified to 'ASL 2.0 and GPLv2+ with exceptions'

[Robin Lee]

License of python-nltk-3.0.0 specified from 'ASL 2.0' to 'ASL 2.0 and
GPLv2+ with exceptions'.

-robin
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: libvpx got soname bump and no one noticed?

[Robin Lee]

Marcin:

You should update rpmfusion-free-relase. And run 'dnf downgrade
ffmpeg-libs'.

There is no 'branched' repos in RPMFusion. And before f22 is released, you
are actually using the 'rawhide' repos of RPMFusion. But After f22
released, RPMFusion f22 repos is then finally branched and the yum repo
configs are updated in new version of rpmfusion-free-release. So, if you
run a global 'dnf upgrade' before upgrade rpmfusion-free-release, you will
pull in some 'rawhide' packages from RPMFusion.

-roibn

On Thu, May 28, 2015 at 4:39 AM, Marcin Juszkiewicz  wrote:

> F22 got released so I upgraded my machine from F22 to rawhide. But as
> usual it meant rebuilding rpmfusion packages (as they do not support
> rawhide).
>
> All went quite good. Except installing:
>
> Error: package ffmpeg-libs-2.6.2-3.fc23.x86_64 requires
> libvpx.so.2()(64bit), but none of the providers can be installed.
>
> Why's that?
>
> libvpx 1.4.0 bumped libvpx.so.1 -> libvpx.so.2 and I did not found any
> mail about it on fedora-devel ML (maybe such mails are not required, no
> idea - many such were sent). Most of rawhide is built against libvpx 1.3.0
> so old soname is required.
>
> Simple 'dnf remove "libvpx.so.1()(64bit)"' on my rawhide shows 512
> packages including wine, kde, gstreamer plugins and lot of other stuff.
>
> How to solve it? I am afraid that answer would be "wait 2 months, we will
> slowly solve it by new uploads" ;(
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: libvpx got soname bump and no one noticed?

[Robin Lee]

Marcin:

Oh. You said you upgraed to Rawhide. But you seems not actually using
Rawhide repos.

-robin

On Thu, May 28, 2015 at 1:28 PM, Robin Lee 
wrote:

> Marcin:
>
> You should update rpmfusion-free-relase. And run 'dnf downgrade
> ffmpeg-libs'.
>
> There is no 'branched' repos in RPMFusion. And before f22 is released, you
> are actually using the 'rawhide' repos of RPMFusion. But After f22
> released, RPMFusion f22 repos is then finally branched and the yum repo
> configs are updated in new version of rpmfusion-free-release. So, if you
> run a global 'dnf upgrade' before upgrade rpmfusion-free-release, you will
> pull in some 'rawhide' packages from RPMFusion.
>
> -roibn
>
> On Thu, May 28, 2015 at 4:39 AM, Marcin Juszkiewicz <
> mjuszkiew...@redhat.com> wrote:
>
>> F22 got released so I upgraded my machine from F22 to rawhide. But as
>> usual it meant rebuilding rpmfusion packages (as they do not support
>> rawhide).
>>
>> All went quite good. Except installing:
>>
>> Error: package ffmpeg-libs-2.6.2-3.fc23.x86_64 requires
>> libvpx.so.2()(64bit), but none of the providers can be installed.
>>
>> Why's that?
>>
>> libvpx 1.4.0 bumped libvpx.so.1 -> libvpx.so.2 and I did not found any
>> mail about it on fedora-devel ML (maybe such mails are not required, no
>> idea - many such were sent). Most of rawhide is built against libvpx 1.3.0
>> so old soname is required.
>>
>> Simple 'dnf remove "libvpx.so.1()(64bit)"' on my rawhide shows 512
>> packages including wine, kde, gstreamer plugins and lot of other stuff.
>>
>> How to solve it? I am afraid that answer would be "wait 2 months, we will
>> slowly solve it by new uploads" ;(
>> --
>> devel mailing list
>> devel@lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/devel
>> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>
>
>
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Self Introduction: Qiyu Yan

[Robin Lee]

On Thursday, June 11, 2020, Qiyu Yan  wrote:
> I am Qiyu Yan, mail: yanqiy...@gmail.com, a 5-yesr Fedora user and a
undergraduate student in Physics.
>
> I started doing packaging because I want to setup development environment
for my lab's computers, the software I first packaged is geant4 on copr
http://copr.fedorainfracloud.org/coprs/yanqiyu/geant4/
>
> By improving the package forked from someone else, I started to know how
to do packaging. (geant4 is a complexed software, I need more time to
package it well)
>
> But I am not trying to join devel to bring geant4 to official repository
here:
>
> I want to make an open-source anti-censorship proxy software [Trojan](
https://github.com/trojan-gfw/trojan) [GPL-3.0 license] available to
Fedora's official repositories. Will that be  possible? (Its named as
trojan but it is a proxy, which pretends to be a TLS server which makes it
possible to bypass China, or any other government's censorship)
>
> Fedora's official repositories already have a python3-shadowsocks with
similar functions, but that project is likely to be out of maintenance. I
think having a new one will be great.
>
> I have made it to be able to build on [koji](
https://koji.fedoraproject.org/koji/taskinfo?taskID=45580956) what to do
next to carry on?
>
> And I want to add more proxy software, such as [V2ray](
https://github.com/v2ray/v2ray-core) and [Shadowsocks-libev](
https://github.com/shadowsocks/shadowsocks-libev) later.
>
> Why I want to build those proxies into fedora's official repository? That
is because downloading those software from GitHub or COPR will be extremely
slow, but if them can enter official repository, they will be mirrored into
China, which will make it easier to install for Chinese users.
>
> And they are not a Chinese only software, they are also useful when you
don't want someone else to know if you are using a proxy, wireguard or
IPSec just do encryption but not confuse possible attackers.
>

Welcome!
You can follow this guide[0] and submit your first review request.

[0] https://fedoraproject.org/wiki/Join_the_package_collection_maintainers

___
> 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

How to create a bodhi update from f32-kde tag?

[Robin Lee]

Hi,

I rebuilt some packages to the f32-kde tag for Qt 5.14.2. And after the new
qt package being pushed to stable, I want to create an update for my packages.

But bodhi request failed:
$ bodhi updates new --type bugfix --notes 'Deepin rebuilds for Qt
5.14.2' --request testing --autotime --autokarma --suggest logout
--user cheeselee
deepin-kwin-0.1.0-7.fc32,deepin-qt-dbus-factory-5.0.1-5.fc32,dtkwidget-2.1.1-5.fc32,deepin-qt5integration-5.0.0-5.fc32,deepin-launcher-5.0.0-5.fc32,deepin-file-manager-5.0.0-7.fc32,deepin-editor-1.2.9.1-5.fc32

Cannot find release associated with build: deepin-kwin-0.1.0-7.fc32,
tags: ['f32-kde']

So, which is the proper way to create to the update?

-robin
___
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: How to create a bodhi update from f32-kde tag?

[Robin Lee]

On Mon, Jun 15, 2020 at 2:59 PM Kalev Lember  wrote:
>
> On 6/15/20 03:55, Robin Lee wrote:
> > Hi,
> >
> > I rebuilt some packages to the f32-kde tag for Qt 5.14.2. And after the new
> > qt package being pushed to stable, I want to create an update for my 
> > packages.
> >
> > But bodhi request failed:
> > $ bodhi updates new --type bugfix --notes 'Deepin rebuilds for Qt
> > 5.14.2' --request testing --autotime --autokarma --suggest logout
> > --user cheeselee
> > deepin-kwin-0.1.0-7.fc32,deepin-qt-dbus-factory-5.0.1-5.fc32,dtkwidget-2.1.1-5.fc32,deepin-qt5integration-5.0.0-5.fc32,deepin-launcher-5.0.0-5.fc32,deepin-file-manager-5.0.0-7.fc32,deepin-editor-1.2.9.1-5.fc32
> >
> > Cannot find release associated with build: deepin-kwin-0.1.0-7.fc32,
> > tags: ['f32-kde']
> >
> > So, which is the proper way to create to the update?
>
> Hi Robin,
>
> You need to tag them over to the regular updates-candidate tag first before 
> submitting the bodhi update:
>
> $ koji tag-build f32-updates-candidate deepin-kwin-0.1.0-7.fc32 
> deepin-qt-dbus-factory-5.0.1-5.fc32 dtkwidget-2.1.1-5.fc32 
> deepin-qt5integration-5.0.0-5.fc32 deepin-launcher-5.0.0-5.fc32 
> deepin-file-manager-5.0.0-7.fc32 deepin-editor-1.2.9.1-5.fc32

Thanks! New update is created.

>
> --
> Kalev
> ___
> 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

Re: Self Introduction: Christopher Meng

[Robin Lee]

你好, Meng!
I am a packager from China. I will go to Beijing next week. We can make
friends and study packaging.

robin

On Wed, Jun 27, 2012 at 3:50 PM, Christopher Meng wrote:

> I'm a senior high school student from Beijing,China.I love many
> things,especially Linux.
> I'm also an ambassador of Fedora Project APAC,now I want to
> co-maintain some packages.
> Hope I can learn somethings at here.
> Greetings to everyone!
>
> --
>
> Best Regards,
> Christopher Meng--'Cicku'
>
> Ambassador/Contributor of Fedora Project and Contributor of GNU.
> Blog:http://cicku.me
> Twitter:@cickumqt
> Hope you can visit and leave some comments.
> More Contact info see here:http://about.me/cicku
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Review swap for a simple Perl module required by Shutter update

[Robin Lee]

Hi.

The link is : 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=832353perl-Net-Dropbox-API

I can review a package in C/C++, Perl or Python.


robin
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

stardict-3.0.5-1 license revised from 'GPLv3' to 'GPLv3+ and GPLv2+ and CPL'

[Robin Lee]

stardict-3.0.5-1 license revised from 'GPLv3' to 'GPLv3+ and GPLv2+ and CPL'

-robin
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: [ACTION REQUIRED][FINAL NOTICE] Retiring packages for Fedora 21 v4

[Robin Lee]

I would like to take this one:
espresso-aborphan, chitlesh

FAS ID: cheeselee

-robin


On Thu, Jul 3, 2014 at 3:48 AM, Till Maas  wrote:

> On Wed, Jul 02, 2014 at 06:49:23PM +0800, Christopher Meng wrote:
> > I'd like to take these 3:
> >
> > bitbakeixs
> > guile-lib  laxathom
> > rats   smilner, rmonk
>
> changed.
>
> Regards
> Till
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

python-shadowsocks license changed

[Robin Lee]

python-shadowsocks 2.8.2 license changed from 'MIT' to 'ASL 2.0'

-robin
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Self Introduction: Jianhong

[Robin Lee]

Hi Yin,

Welcome to Fedora. And it would be great if you can join the Chinese
mailing list[1].

[1] https://admin.fedoraproject.org/mailman/listinfo/chinese

-robin

On Mon, Nov 9, 2015 at 12:40 PM, 尹剑虹  wrote:

> Hi all
>
> I am glad to join the Fedora Project, and going to be the sponsor of
> package mod_rivet.
> My given name is Jianhong, I used to be a programmer for 7 years, and I
> have been a QE more than 2 years in Redhat China R&D Branch.
>
> Specialties:
>   Languages: C Bash Tcl Perl  HTML CSS Javascript
>   Platforms: Linux FreeBSD Windows
>   Databases: Sqlite
>
> I like Tcl very much, I think it's simple and powerful.
>  That's one of the reason that I want push mod_rivet in Fedora.
>
> Github: github.com/tcler
>
> Jianhong
>
>
>
>
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

global and global-ctags license tags revised

[Robin Lee]

License tag of global changed from 'GPLv2+ and BSD' to 'GPLv3+ and LGPLv2+
and BSD and GPLv2+ and MIT'

License tag of global-ctags changed from 'GPLv2+ and BSD' to 'GPLv3+'

-robin
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Self Introduction: Yang JiaXun

[Robin Lee]

Hi Yang,

Welcome to Fedora. And it would be great if you can join the Chinese
mailing list[1].

[1] https://admin.fedoraproject.org/mailman/listinfo/chinese

-robin

On Sat, Nov 21, 2015 at 10:57 PM, 杨嘉勋  wrote:

> https://fedoraproject.org/wiki/User:Flygoat
>
>  I'm a middle school in HangZhou ,China . I studied Visual Basic in 2009 ,C++ 
> in 2012 ,and I'm studing Python Now. I've got CYLE English Level'Flyers' 
> (Same as KET) year ago.
>   I've been using Fedora since release 17.
>   I love aviation .In my free time I usually go to the airport and watch  
> aiecrafts takeoff and lands.
>
>
> 杨嘉勋 Send By Office365-Outlook For Business
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Shutter license changed to GPLv3+

[Robin Lee]

Shutter license changed to GPLv3+
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Calling for the packager of fping

[Robin Lee]

Hi, Meng.

If you would like to help, you can go through [1] to take over the package
ownership.

[1]
https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers
cheers,
robin
On Thu, Aug 23, 2012 at 4:53 PM, Christopher Meng wrote:

> Hey all,
>
> I wonder if maintainer of fping is available or not.I took a look at the
> spec file and see that since f12 rebuild nobody has updated the package.
>
> But I can't say nobody is its maintainer,so I want to find that guy.
>
> Thanks.
>
> --
>
>
> *Yours sincerely,*
> *Christopher Meng*
>
> Ambassador/Contributor of Fedora Project and many others.
> http://cicku.me
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
>
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Calling for the packager of fping

[Robin Lee]

Then you may file a bug against the EPEL branch to ask the maintainer to
make an upgrade.

On Thu, Aug 23, 2012 at 9:03 PM, Christopher Meng wrote:

> Sorry I forgot that I mean the 'fping' is the package in EPEL, not Fedora,
> sorry!
>
> --
>
>
> *Yours sincerely,*
> *Christopher Meng*
>
> Ambassador/Contributor of Fedora Project and many others.
> http://cicku.me
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
>
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

'newpackager' is not in FAS, or How to co-maintain a package before getting sponsored

[Robin Lee]

Hi, all

I want to follow the route [1] to bring up a new packager. But when I try
to approve commit privilege for him, pkgdb says:
"... must be in one of these groups: ('cvsadmin', 'packager',
'provenpackager', 'newpackager') to hold the commit acl"

I think he should join the 'newpackager' FAS group first, but the group is
not existing in FAS.

Or candidate packager would not get commit privilege until actually
sponsored?


[1]
https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Become_a_co-maintainer

Cheers,
robin
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: 'newpackager' is not in FAS, or How to co-maintain a package before getting sponsored

[Robin Lee]

On Sat, Sep 29, 2012 at 12:02 PM, Jason L Tibbitts III wrote:

> >>>>> "RL" == Robin Lee  writes:
>
> RL> Hi, all I want to follow the route [1] to bring up a new
> RL> packager.
>
> Then why not follow the procedure you referenced?  It tells you what to
> do, which involves opening a ticket in the appropriate trac instance.
>
>  - J<

It is just the beginning at this moment. The candidate packager is still
learning RPM packaging  and below level that can be sponsored.

I just thought that the 'newpackager' is the group for such kind of new
contributors. People in this group can have access to limited group of
packages and cannot own any package. But, after all, the group is not
existing.

So, that means new willing contributors can only co-maintain the package by
sending patches and filing bugs, instead of having direct commit privilege
to the Git repo?


robin
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: 'newpackager' is not in FAS, or How to co-maintain a package before getting sponsored

[Robin Lee]

On Sat, Sep 29, 2012 at 1:32 PM, Toshio Kuratomi  wrote:

> On Sat, Sep 29, 2012 at 12:24:40PM +0800, Robin Lee wrote:
> > On Sat, Sep 29, 2012 at 12:02 PM, Jason L Tibbitts III <
> ti...@math.uh.edu>
> > wrote:
> >
> > >>>>> "RL" == Robin Lee  writes:
> >
> > RL> Hi, all I want to follow the route [1] to bring up a new
> > RL> packager.
> >
> > Then why not follow the procedure you referenced?  It tells you what
> to
> > do, which involves opening a ticket in the appropriate trac instance.
> >
> >  - J<
> >
> > It is just the beginning at this moment. The candidate packager is still
> > learning RPM packaging  and below level that can be sponsored.
> >
> > I just thought that the 'newpackager' is the group for such kind of new
> > contributors. People in this group can have access to limited group of
> packages
> > and cannot own any package. But, after all, the group is not existing.
> >
> > So, that means new willing contributors can only co-maintain the package
> by
> > sending patches and filing bugs, instead of having direct commit
> privilege to
> > the Git repo?
> >
> Not at all.
>
> If you are willing to mentor the new packager, then they can be sponsored
> into the packager group.
>
> If you are not a sponsor yourself, you open a ticket in fesco's trac
> stating
> who you'd like to have sponosred and that you will be mentoring them as
> they
> comaintain which package with you.
>
> -Toshio
>
At this moment I don't approve him to be sponsored.
So at this moment, can he only send patches to me to co-maintain the
package? Can he have git commit privilege to that single package?

robin
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: 'newpackager' is not in FAS, or How to co-maintain a package before getting sponsored

[Robin Lee]

On Sat, Sep 29, 2012 at 2:56 PM, Toshio Kuratomi  wrote:

> On Sat, Sep 29, 2012 at 02:00:36PM +0800, Robin Lee wrote:
> > On Sat, Sep 29, 2012 at 1:32 PM, Toshio Kuratomi 
> wrote:
> >
> > On Sat, Sep 29, 2012 at 12:24:40PM +0800, Robin Lee wrote:
> > > On Sat, Sep 29, 2012 at 12:02 PM, Jason L Tibbitts III <
> ti...@math.uh.edu
> > >
> >     > wrote:
> > >
> > > >>>>> "RL" == Robin Lee  writes:
> > >
> > > RL> Hi, all I want to follow the route [1] to bring up a new
> > > RL> packager.
> > >
> > > Then why not follow the procedure you referenced?  It tells
> you what
> > to
> > > do, which involves opening a ticket in the appropriate trac
> instance.
> > >
> > >  - J<
> > >
> > > It is just the beginning at this moment. The candidate packager is
> still
> > > learning RPM packaging  and below level that can be sponsored.
> > >
> > > I just thought that the 'newpackager' is the group for such kind
> of new
> > > contributors. People in this group can have access to limited
> group of
> > packages
> > > and cannot own any package. But, after all, the group is not
> existing.
> > >
> > > So, that means new willing contributors can only co-maintain the
> package
> > by
> > > sending patches and filing bugs, instead of having direct commit
> > privilege to
> > > the Git repo?
> > >
> > Not at all.
> >
> > If you are willing to mentor the new packager, then they can be
> sponsored
> > into the packager group.
> >
> > If you are not a sponsor yourself, you open a ticket in fesco's trac
> > stating
> > who you'd like to have sponosred and that you will be mentoring them
> as
> > they
> > comaintain which package with you.
> >
> > -Toshio
> >
> > At this moment I don't approve him to be sponsored.
> > So at this moment, can he only send patches to me to co-maintain the
> package?
> >
> If you're unwilling to mentor him, then that is correct.
>
OK. I am willing, but he is newbie and may give up a moment later.

>
> > Can he have git commit privilege to that single package?
> >
> People in the packager group only have commit privileges to the packages
> that they own or have been granted the commit acl on.  So if he is in
> packager and only has commit acls on that single package then that's all
> that he'll have access to.
>
> -Toshio
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
>
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

perl-Net-ARP-1.0.8 license change

[Robin Lee]

perl-Net-ARP-1.0.8 license is changed from 'GPL+ or Artistic' to 'GPLv2'.

-robin
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: orphaning of packages

[Robin Lee]

On Fri, Aug 16, 2013 at 12:19 PM, Dennis Gilmore  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi all,
>
> Jima has not been able to make enough time for Fedora lately and asked
> me to orphan and announce the packages he maintains.
>
> alsa-oss
> aoetools
> banner
>
banner taken.


> bwm-ng
> clusterssh
> conserver
> graphviz
> libdnet
> libstatgrab
> miau
> ngrep
> perl-X11-Protocol
> rblcheck
> scanssh
> vblade
>
> feel free to pick them up
>
> Dennis
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.19 (GNU/Linux)
>
> iEYEARECAAYFAlINqGoACgkQkSxm47BaWffvnwCeON8fhdQ2m7gO1oUMXy6GiF3B
> 5LEAoMGWAeAHgit/h2YU2NrkPX98RYKm
> =EFde
> -END PGP SIGNATURE-
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

fcitx-unikey-0.2.2 license tag corrected from GPLv2+ to GPLv3+

[Robin Lee]

The previous version 0.1.1 is already under GPLv3+.

-robin
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: [RFC] Easiest making kernel rpms from upstream git

[Robin Lee]

On Wed, Aug 28, 2013 at 9:53 PM, Igor Gnatenko
wrote:

> Today I've wrote article w/ many notes about bisecting kernel [0], but
> I've used make bzImage, make install and the same commands bypassing RPM
> and I have IMHO good idea to write utility, that will be build rpm w/o/
> Fedora patches, changelogs, etc. simple rpms w/ one command.
>
'make binrpm-pkg'
should be the simplest way to make kernel rpm. But you may need to copy the
scriptlets following the Fedora/RHEL 'kernel' rpm to
scripts/package/mkspec, so the output rpm from 'make binrpm-pkg' can be
installed without manual intervene.

-robin

>
> We will use "utilityname `git rev-parse HEAD` f19" instead of "make
> bzImage && make modules" and "yum install ./rpms/*.rpm" instead of "make
> install && make modules_install".
>
> This software should increase the effectiveness, simplify the build test
> kernels, simplify to work w/ installed kernels (e.g. remove). Also we
> can easy provide rpms to bugreport for testing regressions, etc.
>
> I see alike software at bubuntu wiki [1].
>
> Would anyone besides me find this useful enough for me to keep working
> on it?
>
> [0]https://fedoraproject.org/wiki/User:Ignatenkobrain/Kernel/Bisection
> [1]
> https://wiki.ubuntu.com/Kernel/KernelBisection#Build_Upstream_Test_Kernel
>
> --
> Igor Gnatenko
> Fedora release 19 (Schrödinger’s Cat)
> Linux 3.10.7-200.fc19.x86_64
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

cherrytree-0.30.5 license changed from GPLv2+ to GPLv3+

[Robin Lee]

Hi,

cherrytree-0.30.5 license changed from GPLv2+ to GPLv3+

-robin
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: boost141 and stability of Boost API?

[Robin Lee]

Upstream Tracker is a convenient place for checking API/ABI changes:
For Boost: http://upstream-tracker.org/versions/boost.html

-robin


On Sun, Sep 29, 2013 at 11:44 AM, Dave Johansen wrote:

> I just noticed that the boost141 package had been previously available in
> Fedora, but it has since been removed (
> https://fedorahosted.org/rel-eng/ticket/5291 ). I'm not familiar with the
> recent changes in Boost, but is the API stable enough to support a package
> to build on EL 5/6 and Fedora?
> Thanks,
> Dave
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

perl-File-Next 1.12 license corrected to 'Artistic 2.0'

[Robin Lee]

Upstream has mis-matched licensing in Makefile.PL and in the source code. I
corrected the License in specfile following the source code.

robin
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

lonote-2.2.1 license changed from 'GPLv3 and ASL 2.0' to 'ASL 2.0'

[Robin Lee]

lonote-2.2.1 license has changed from 'GPLv3 and ASL 2.0' to 'ASL 2.0'.

Cheers
-robin
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: quotatool

[Robin Lee]

Hi,

You can send a mail to the maintainer directly. You can find his/her Email
address[1] in RPM changelog.

[1] * Tue Sep 29 2009 Xia Shing Zee  1.4.11-8

robin


On Tue, Jan 1, 2013 at 2:46 PM, Christopher Meng  wrote:

> Hi,
>
> I just want to find the reason of orphaned quotatool.
>
> Anyone can help me?
>
> Thanks.
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
>
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: cpio: Digest mismatch

[Robin Lee]

On Thu, Feb 23, 2017 at 12:32 PM,  wrote:

> Hi Guys,
> I have a source file of 6 GB and i try to create an RPM using the spec
> file.
> After creating the RPMS , i installed on the machines. But i am not able
> to do the command :
> "rpm -ivh LINSEE_xilinx-sdk_v20164-2016.4-1.src.rpm"
> It throws an error as below :
>
> [root@euca-10-254-169-180 SRPMS]# rpm -ivh LINSEE_xilinx-sdk_v20164-2016.
> 4-1.src.rpm
>1:LINSEE_xilinx-sdk_v2016###
> [100%]
> error: unpacking of archive failed on file 
> /root/rpmbuild/SOURCES/xilinx-sdk.tar.gz;58ae56bb:
> cpio: Digest mismatch
> error: LINSEE_xilinx-sdk_v20164-2016.4-1.src.rpm cannot be installed
>
> I split the RPM into 3 packages , Is there any way how i can split the
> source file using spec file.
> Kindly help me here.
>
You should build the src rpm with this rpmbuild option: --define
"_source_filedigest_algorithm md5".
Then you can install the src rpm on CentOS5 or earlier versions.

> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Self Introduction: Stephen Kitt

[Robin Lee]

On Fri, Feb 24, 2017 at 1:48 AM, Stephen Kitt  wrote:

> Hi everyone,
>
> As part of the "join the package collection maintainers" process, I'd like
> to
> introduce myself — I've just submitted my first review request
> (https://bugzilla.redhat.com/show_bug.cgi?id=1426333).
>
> I'm a long-standing free software user and packager, in the Debian world
> (https://qa.debian.org/developer.php?login=skitt). My packaging interests
> cover a wide spectrum, from games and emulators to toolchains and random
> interesting pieces of software. Some of you might have seen me at Devconf
> where I gave a presentation contrasting the processes for joining Debian
> and
> Fedora as a packaging contributor
> (https://www.youtube.com/watch?v=pGQFZPA6r8w). I work for Red Hat but
> packaging isn't a big part of my day job (although the request above is
> submitted using my @redhat.com account — it's for OpenDaylight, which is
> what
> I work on).
>
> I'm looking forward to adding some interesting software to Fedora!
>
> Regards,
>
> Stephen
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
Welcome!

-robin
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Self Introduction: Jeffrey Lau

[Robin Lee]

On Fri, Mar 3, 2017 at 9:48 AM, Jeffrey Lau  wrote:

> Hi fellow Fedora devs,
>
> My name is Jeffrey Lau, and I'm from Hong Kong.
> I started using Fedora since Core 2, and have been a fan since then.
> I also enjoy tinkering my Bash prompts ... O_o
> After all these years, I am happy to finally have something that I could
> contribute back to the project --- there are some software that I'd like to
> use under Fedora's ecosystem which hasn't been packaged yet, so I'd like to
> tackle that.  I hope this is the right place to do self introduction :-p
>  The wikis are *really* detailed so I hope I haven't misread anything.
>
> Looking forward to working with you guys and contributing to the project
> that I love.  Long live Fedora!
>
> P.S. My FAS handle is jeffreylauribose , if it's of any use here.
>
> P.P.S. will be submitting a Package Review request soon ...! :-D
>
> Cheers,
> Jeffrey
>
> Software Engineer
>
> Ribose, Inc.
> T: +852 3976 3976 <+852%203976%203976>
>
> +=+
> This message may contain confidential and/or privileged
> information.  If you are not the addressee or authorized to
> receive this for the addressee, you must not use, copy,
> disclose or take any action based on this message or any
> information herein.  If you have received this message in
> error, please advise the sender immediately by reply e-mail
> and delete this message.  Thank you for your cooperation.
> +=+
>
>
>

>
>
>
>
>
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
> Welcome, Jeffrey!
I am a packager at Guangzhou City.
Feel free to contact me personally if you have any question about packaging.

-robin
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Self Introduction: Junwei Fang

[Robin Lee]

On Mon, Jul 17, 2017 at 3:01 PM, 方俊伟  wrote:

> Dear,
>Hello, everybody. My name is Junwei Fang, a developer of C++. I am
> from China
> I worked for a little company, my work is about VoIP. I use fedora
> workstation as my default OS,
> i worked with gnome desktop for more than 5 years. I hope to join fedora
> project and I'm a newer,
> I'm seeking for a sponsor, Could you help me?
>
>
>
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
> Hi, 俊伟

If you want to join Fedora project as a packager, you can follow the steps
in [1].

And you can join the Chinese list[2].

And you can contact me personally if you have any question about packaging.

[1]: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
[2]: https://lists.fedoraproject.org/admin/lists/chinese.lists.
fedoraproject.org/

-robin
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Large number of packages to be orphaned on Feb 26

[Robin Lee]

On Mon, Feb 22, 2016 at 2:59 PM, Petr Šabata  wrote:

> On Fri, Feb 19, 2016 at 01:09:22PM -0500, Josh Boyer wrote:
> > rpms/dmenu -- Generic menu for X ( master f23 f22 epel7 el6 )
>
> I'll take this one, finally.
> P
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
>
> rpms/blktap -- Blktap Userspace Tools + Library ( master f23 f22 )
rpms/nbd -- Network Block Device user-space tools (TCP version) (
master f23 f22 epel7 )

I am happy to take these two.
FAS id: cheeselee

-robin
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: rpm: %patch needs --fuzz

[Robin Lee]

On Wed, May 4, 2016 at 9:22 PM, Neal Becker  wrote:

> In an rpm .spec I need a patch with more fuzz
>
> %patch macro
>
> doesn't seem to accept --fuzz=xxx
>
> What's a good solution?
> --
> devel mailing list
> devel@lists.fedoraproject.org
> http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
>
You can redefine %_default_patch_fuzz before any %patchN.

-robin
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Offering help for audio related packages, seeking sponsor

[Robin Lee]

On Tue, Oct 18, 2016 at 5:31 PM, Guido Aulisi 
wrote:

> Hi,
> I recently posted 2 review requests and a sponsor request for 2 audio
> related packages, https://bugzilla.redhat.com/show_bug.cgi?id=1373641
> and https://bugzilla.redhat.com/show_bug.cgi?id=1374510 and I am
> seeking for a sponsor.
> I also noticed that some audio related packages (lilv, suil, serd,
> sord) are old, new versions have been released by upstream, and I am
> offering help to update these packages as well, maybe as a
> co-maintainer.
>
> Best regards.
> Guido AUlisi
>
Hi, Guido!

I maintain some drumstick based packages: vmpk, kmetronome, kmid2 and
drumstick itself.
All of them welcome co-maintainer.

> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Qt 5.14.2 coming to rawhide

[Robin Lee]

On Sun, Apr 5, 2020 at 6:58 AM Rex Dieter  wrote:
>
> FYI, Started work on importing Qt 5.14.2 into rawhide today, with work-in-
> progress being done in side tag f33-build-side-21031
>
> I figure it'll take at least a few days to get the core bits and all
> dependencies rebuilt.  Will provide status updates as warranted.
>
> -- Rex
I built deepin-qt5integration-5.0.0-5.fc33 in the side tag.
But when I build deepin-file-manager, the new build of deepin-qt5integration
is not found.
What should I do to fix this?

-robin
> ___
> 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

Re: Qt 5.14.2 coming to rawhide

[Robin Lee]

On Wed, Apr 8, 2020 at 12:24 PM Kevin Fenzi  wrote:
>
> On Wed, Apr 08, 2020 at 10:45:40AM +0800, Robin Lee wrote:
> > On Sun, Apr 5, 2020 at 6:58 AM Rex Dieter  wrote:
> > >
> > > FYI, Started work on importing Qt 5.14.2 into rawhide today, with work-in-
> > > progress being done in side tag f33-build-side-21031
> > >
> > > I figure it'll take at least a few days to get the core bits and all
> > > dependencies rebuilt.  Will provide status updates as warranted.
> > >
> > > -- Rex
> > I built deepin-qt5integration-5.0.0-5.fc33 in the side tag.
> > But when I build deepin-file-manager, the new build of deepin-qt5integration
> > is not found.
> > What should I do to fix this?
>
> It doesn't look to me like thats the cause of the failed build?
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=43111751
>
> ...
> ./shutil/dsqlitehandle.h:29:8: error: redefinition of 'struct 
> std::hash'
>29 | struct hash
>   |^
> In file included from /usr/include/qt5/QtCore/qlist.h:47,
>  from /usr/include/qt5/QtCore/qurl.h:47,
>  from /usr/include/qt5/QtCore/QUrl:1,
>  from ./interfaces/durl.h:28,
>  from tag/tagmanager.h:15,
>  from tag/tagmanager.cpp:7:
> /usr/include/qt5/QtCore/qhashfunctions.h:180:16: note: previous definition of 
> 'struct std::hash'
>   180 | struct hash< QT_PREPEND_NAMESPACE(Class) > {\
>   |^~~
> /usr/include/qt5/QtCore/qhashfunctions.h:200:5: note: in expansion of macro 
> 'QT_SPECIALIZE_STD_HASH_TO_CALL_QHASH'
>   200 | QT_SPECIALIZE_STD_HASH_TO_CALL_QHASH(Class, const argument_type &)
>   | ^~~~
> /usr/include/qt5/QtCore/qhashfunctions.h:204:1: note: in expansion of macro 
> 'QT_SPECIALIZE_STD_HASH_TO_CALL_QHASH_BY_CREF'
>   204 | QT_SPECIALIZE_STD_HASH_TO_CALL_QHASH_BY_CREF(QString)
>   | ^~~~
> make[1]: *** [Makefile:3680: tagmanager.o] Error 1
> ...
>
> kevin
Sorry! I checked a wrong task for log.
Now deepin-file-manager is also fixed. New build is
deepin-file-manager-5.0.0-7.fc33

> ___
> 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

Re: RFC: Feature macros (aka USE flags)

[Robin Lee]

On Mon, Apr 27, 2020 at 7:21 PM Petr Šabata  wrote:
>
> Based on the recent discussions around %fedora/%rhel macros and ELN,
> and %bcond generally being confusing to work with, I came up with a
> distribution-wide feature that defines generic feature keywords and
> associated helper macros that packages can check in build-time
> conditionals.
>
> The key advantage here is the defaults are defined by the buildroot,
> not the package. The package is just a building block.
>
> I'd like some input to improve this and unless this turns out to be a
> really bad idea, I intend to submit it as a change proposal. Even
> though the more packages use it the more beneficial it gets, it's, of
> course, perfectly optional.
>
> Details in the gist:
> https://gist.github.com/contyk/0f0585c57976ca18a293b3566408
Should the use flags be automatically recorded in Provides of binary packages?
Package A "Provides: A(+feature)"
Then package B may 'Requires: A(+feature)"

That semantics is implemented in Gentoo.
>
> Cheers,
> P
> ___
> 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

Re: Self Introduction: Jude Lee / judescripts

[Robin Lee]

On Tue, Apr 28, 2020 at 11:43 AM Jude Lee  wrote:
>
> Hi! my name is Jude and I am a fullstack / architect (github.com/judescripts 
> | linkedin.com/in/leejude).
>
> This is first time joining a fedora group and I've been wanting to become a 
> part of the open source project community for awhile now.
> I've mostly worked with debian based distros and some arch linux, but after 
> giving a go at fedora I fell in love.
> Would like to contribute more in the best way I can through this group and 
> hoping to learn and grow in this community and become a valuable contributor.
>
> Nice to meet you all and looking forward to getting to know the community 
> more :)
>
> Best,
>
> Jude
Welcome! It's a good idea to start with the packages that you actually use.
> ___
> 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

Re: Fedora 32 System-Wide Change proposal: Use update-alternatives for /usr/bin/cc and /usr/bin/c++

[Robin Lee]

On Fri, Dec 20, 2019 at 5:44 AM Ben Cotton  wrote:
>
> https://fedoraproject.org/wiki/Changes/Use-Update-Alternatives-For-usr-bin-cc
>
> == Summary ==
> Modify the gcc package so that the /usr/bin/cc and /usr/bin/c++
> symlinks are managed by update-alternatives.
>
> == Owner ==
> * Name: [[User:tstellar| Tom Stellard]]
> * Email: 
>
> == Detailed Description ==
> The gcc package currently installs symlinks to /usr/bin/cc and
> /usr/bin/c++ which point to /usr/bin/gcc and /usr/bin/g++
> respectively.  For this change, the gcc package will be modified so
> that update-alternatives creates and manages these symlinks.
>
> In addition to modifying the gcc package, the clang package will be
> modified so that /usr/bin/clang and /usr/bin/clang++ can be used as
> alternatives for /usr/bin/cc and /usr/bin/c++.  The clang alternatives
> will have a lower priority than the gcc alternatives, so that by
> default, gcc will provide the /usr/bin/cc and /usr/bin/c++
> implementations.
>
> The clang package currently has a run-time dependency on gcc, so this
> ensures that gcc will always provide the default implementation,
> because it's impossible to install clang without gcc.
>
> The only way users will be able to change the /usr/bin/cc or
> /usr/bin/c++ implementations will be by explicitly using the
> update-alternatives tool.
>
> == Benefit to Fedora ==
> Many build systems default to using /usr/bin/cc and /usr/bin/c++ as
> the default C/C++ compilers.  Being able to easily swap out these
> implementation will provide a lot of flexibility within Fedora for
> doing things like:
>
> * Setting up alternative buildroots for testing.
> * Installing a gcc wrapper script to /usr/bin/cc to help migrate
> packages to new compiler flags or to capture statistics about compiler
> usage.
> * Letting users experiment easily with alternate compilers.
> * Easily switch between system gcc and a development version of gcc.
>
> == Scope ==
> * Proposal owners: The proposal owner will implement the necessary
> changes in the gcc and clang packages.
>
> * Other developers: The gcc maintainers will be responsible for
> reviewing and approving changes to the gcc package.
>
> * Release engineering: (a check of an impact with Release Engineering is 
> needed)
> * Policies and guidelines: No policies or guidelines will need to be
> updated as a result of this change.
> * Trademark approval: N/A (not needed for this Change)
>
>
> == Upgrade/compatibility impact ==
> This change should not impact upgradeability.
>
> == How To Test ==
> CI tests will be added to the gcc package to ensure that /usr/bin/cc
> and /usr/bin/c++ still point to /usr/bin/gcc and /usr/bin/g++ when
> installed.  There will also be a CI test added to the clang package to
> ensure that /usr/bin/gcc and /usr/bin/g++ remain the default when
> clang is installed.
>
> == User Experience ==
> This change will give users a much better way to experiment using
> other compilers for their own development.  They will be able to
> easily switch between different compilers without having to modify
> their projects build system or make non-standard changes to their
> Fedora system.
>
> == Dependencies ==
> This change has no other dependencies besides the changes to the gcc
> and clang packages.
>
> == Contingency Plan ==
> * Contingency mechanism: (What to do?  Who will do it?) Proposal Owner
> will revert changes made to gcc and clang packages and rebuild.
> * Contingency deadline: If the changes are not complete by 2 weeks
> before the mass rebuild, then we will consider postponing to the next
> Fedora release and back out any changes that were made.
> * Blocks release? No
> * Blocks product? None
>
> == Documentation ==
> Release notes will be added for this change.
>
> == Release Notes ==
> The user /usr/bin/cc and /usr/bin/c++ symlinks are now managed by
> update-alternatives.  If you would like to change these symlinks to
> point to another compiler, like clang, for example, you can use these
> commands:
>
> `update-alternatives --set cc /usr/bin/clang`
>
> `update-alternatives --set c++ /usr/bin/clang++`
>
> --
> Ben Cotton
> He / Him / His
> Fedora Program Manager
> Red Hat
> TZ=America/Indiana/Indianapolis
> ___
> 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
Alternatives for 'cpp' are needed, too. Clang has 'clang-cpp'.
___
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://fedora

Re: Orphaned package "solfege"

[Robin Lee]

On Mon, Jul 29, 2019 at 2:32 AM Christian Krause  wrote:
>
> Hi,
>
> I have orphaned the package "solfege" (a small music education tool to learn 
> to hear intervals, rhythms, ...).
>
> It does not build anymore [1] and there is no upstream activity since a few 
> years.
>
> Last stable version (3.22.2) is from 2013 [2]
> Last unstable version (3.23.4) is from 2016 [3]
> Last git commit corresponds with the 3.23.4 release [4]
>
> For python3, version 3.23.4 would be required. However, even this version 
> does not compile since autoconf does not use pkg-config for Python.h and so 
> the path used in recent Fedora releases (e.g. /usr/include/python3.7m) is not 
> found.
>
> Personally I would retire it from Fedora, but I orphaned it first just in 
> case someone wants to pick it up. If not, it will get automatically retired 
> due to the open FTBFS bug.
>
> Best regards,
> Christian
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1639699
> [2] http://ftp.gnu.org/gnu/solfege/
> [3] https://sourceforge.net/projects/solfege/files/solfege-unstable/
> [4] http://git.savannah.gnu.org/cgit/solfege.git
It would be nice if solfege can be packaged as flatpak.
> ___
> 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

Proper way to keep service enabled when updated from sysv to systemd?

[Robin Lee]

Hi,

I packaged xe-guest-utilities with a systemd service for Fedora.

But there is an upstream rpm package that include the same service as
a sysv one. And the
service is enabled with the 'Default-Start' info in the init script
after '/sbin/chkconfig --del xe-linux-distribution'.

And when people update the package from upstream one to the Fedora
one. Since the service changed to a systemd one. The service is then
disabled by default without regard to the sysv service.

That surprises end users. So the new package should make it compatible
in the scriptlets.
But which is the proper way?

Best Regards
-robin
___
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: Proper way to keep service enabled when updated from sysv to systemd?

[Robin Lee]

On Tue, Aug 13, 2019 at 10:37 PM Zbigniew Jędrzejewski-Szmek
 wrote:
>
> On Tue, Aug 13, 2019 at 06:02:42PM +0800, Robin Lee wrote:
> > Hi,
> >
> > I packaged xe-guest-utilities with a systemd service for Fedora.
> >
> > But there is an upstream rpm package that include the same service as
> > a sysv one. And the
> > service is enabled with the 'Default-Start' info in the init script
> > after '/sbin/chkconfig --del xe-linux-distribution'.
> >
> > And when people update the package from upstream one to the Fedora
> > one. Since the service changed to a systemd one. The service is then
> > disabled by default without regard to the sysv service.
> >
> > That surprises end users. So the new package should make it compatible
> > in the scriptlets.
> > But which is the proper way?
>
> You can add a %trigger script. Something like this, completely untested:
> %triggerun xe-linux-distribution < …old…version+1…
> if test -e /etc/rc.d/rc3.d/Snn-…; then
># enable systemd service based on old status
>systemctl enable xe-linux-distribution.service
> fi

Thanks for your tips!

I now use such version:

%triggerun -- %{name}
if /bin/ls /etc/rc3.d/S*%{service_name} >/dev/null 2>&1; then
# Re-enable the service if it was enabled in sysv mode
/usr/bin/systemctl enable %{service_name} >dev/null 2>&1||:
/bin/rm /etc/rc3.d/S*%{service_name} >/dev/null 2>&1||:
/usr/bin/systemctl try-restart %{service_name} >dev/null 2>&1||:
fi

>
> Please note that for new packages, the general guidelines apply
> (https://docs.fedoraproject.org/en-US/packaging-guidelines/DefaultServices/)
> and services should be managed through presets. But keeping enablement
> state on upgrade is outside of the guidelines and a nice thing to do.
>
> Zbyszek
> ___
> 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

Re: Help needed to fix FTBFS (gcc-10 caused failures)

[Robin Lee]

On Sun, Feb 23, 2020 at 11:50 PM Mukundan Ragavan  wrote:
>
> Hi all,
>
> I have two packages that fail to build from source. As far as I can tell
> from the build logs, they are gcc-10 failures. The typical "extern"
> solution does not work me (or, I am not adding 'extern' at the correct
> places).
>
> Can someone give me pointers for fixing this FTBFS? Here are the links
> containing the build logs -
>
> xfce4-panel:
> https://bugzilla.redhat.com/show_bug.cgi?id=1800267
>
> xfce4-sensors-plugin:
> https://bugzilla.redhat.com/show_bug.cgi?id=1800268
I have figured out patches for both issues. Let's talk in bugzilla and upstream.

-robin
>
> Direct koji links no longer show the build logs and hence
>
> Thanks!
>
> ___
> 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

Re: Self Introduction: ChillyBot

[Robin Lee]

On Wed, Feb 27, 2019 at 2:42 AM absolutezero  wrote:
>
> Hello everyone!
>
> My name is Chilly. I am looking to bring back Snort IDS into the Fedora 
> Project and maintain it for at least several years. I am relatively new to 
> packaging but have been using Fedora for many years now as my daily driver. 
> Doing my best to follow to guide according to 
> https://fedoraproject.org/wiki/Join_the_package_collection_maintainers and am 
> excited to contribute. I work as a Linux Sysadmin and infosec/privacy 
> consultant.
Grad to hear that!
>
> GPG Fingerprint: 0977E14243A7B76741A6E049076FD2093766DC98
>
> Any question or comments feel free to contact me directly :)
>
> Best wishes,
>
> Chilly
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> 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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Donate 1 minute of your time to test upgrades from F29 to F30

[Robin Lee]

On Thu, Feb 28, 2019 at 5:23 PM Miroslav Suchý  wrote:
>
> Do you want to make Fedora 30 better? Please spend 1 minute of your time and 
> try to run:
>
>   sudo dnf --releasever=30 --setopt=module_platform_id=platform:f30 
> --enablerepo=updates-testing distro-sync
>
> If you get this prompt:
>
>   ...
>   Total download size: XXX M
>   Is this ok [y/N]:
>
> you can answer N and nothing happens, no need to test the real upgrade. 
> Upgrades will be fine for you.
>
> But very likely you get some dependency problem now. In that case please 
> report it against appropriate package.
Tested on Fedora 28:

 Problem 1: problem with installed package python2-pungi-4.1.32-3.fc28.noarch
  - python2-pungi-4.1.32-3.fc28.noarch does not belong to a
distupgrade repository
  - nothing provides python2.7dist(dict.sorted) needed by
python2-pungi-4.1.33-2.fc30.noarch
 ...
 Problem 3: package python-cephfs-1:12.2.10-1.fc28.x86_64 requires
libcephfs2 = 1:12.2.10-1.fc28, but none of the providers can be
installed
  - libcephfs2-1:12.2.10-1.fc28.x86_64 does not belong to a
distupgrade repository
  - problem with installed package python-cephfs-1:12.2.10-1.fc28.x86_64
 Problem 4: package python-rados-1:12.2.10-1.fc28.x86_64 requires
librados2 = 1:12.2.10-1.fc28, but none of the providers can be
installed
  - librados2-1:12.2.10-1.fc28.x86_64 does not belong to a distupgrade
repository
  - problem with installed package python-rados-1:12.2.10-1.fc28.x86_64
 Problem 5: package python-rbd-1:12.2.10-1.fc28.x86_64 requires
librbd1 = 1:12.2.10-1.fc28, but none of the providers can be installed
  - librbd1-1:12.2.10-1.fc28.x86_64 does not belong to a distupgrade repository
  - problem with installed package python-rbd-1:12.2.10-1.fc28.x86_64
 Problem 6: package python-rgw-1:12.2.10-1.fc28.x86_64 requires
librgw2 = 1:12.2.10-1.fc28, but none of the providers can be installed
  - librgw2-1:12.2.10-1.fc28.x86_64 does not belong to a distupgrade repository
  - problem with installed package python-rgw-1:12.2.10-1.fc28.x86_64
 ...
 Problem 8: package python2-pylint-1.7.5-1.fc28.noarch requires
python2-isort, but none of the providers can be installed
  - python2-isort-4.3.4-2.fc28.noarch does not belong to a distupgrade
repository
  - problem with installed package python2-pylint-1.7.5-1.fc28.noarch
 Problem 9: package python2-rpkg-1.57-6.fc28.noarch requires
rpkg-common = 1.57-6.fc28, but none of the providers can be installed
  - rpkg-common-1.57-6.fc28.noarch does not belong to a distupgrade repository
  - problem with installed package python2-rpkg-1.57-6.fc28.noarch
 Problem 10: package python3-PyXB-1.2.6-2.fc28.noarch requires
python(abi) = 3.6, but none of the providers can be installed
  - python3-3.6.8-2.fc28.x86_64 does not belong to a distupgrade repository
  - problem with installed package python3-PyXB-1.2.6-2.fc28.noarch
 ...
 Problem 13: problem with installed package pungi-legacy-4.1.32-3.fc28.noarch
  - package pungi-legacy-4.1.33-2.fc30.noarch requires python2-pungi =
4.1.33-2.fc30, but none of the providers can be installed
  - pungi-legacy-4.1.32-3.fc28.noarch does not belong to a distupgrade
repository
  - nothing provides python2.7dist(dict.sorted) needed by
python2-pungi-4.1.33-2.fc30.noarch
 Problem 14: package dnf-yum-4.1.0-1.fc30.noarch conflicts with yum
provided by yum-3.4.3-521.fc30.noarch
  - problem with installed package yum-3.4.3-517.fc28.noarch
  - problem with installed package dnf-yum-2.7.5-12.fc28.noarch
  - yum-3.4.3-517.fc28.noarch does not belong to a distupgrade repository
  - dnf-yum-2.7.5-12.fc28.noarch does not belong to a distupgrade repository
>
> Thank you
>
> Miroslav
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> 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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

package built but not tagged into Rawhide in Koji

[Robin Lee]

Hi,

I have a package built on 10 Mar. Build is
deepin-qt-dbus-factory-1.1.0-1.fc31[1].
The package is already available in public repo. But I just found it
is not tagged
into rawhide, queried with 'koji latest-build rawhide deepin-qt-dbus-factory'.

I never met this case. What should I do?

[1] https://koji.fedoraproject.org/koji/buildinfo?buildID=1216408

-robin
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: New Go Packaging Guidelines landed in rawhide (koji) today

[Robin Lee]

On Sat, Jun 8, 2019 at 10:35 PM Nicolas Mailhot via devel
 wrote:
>
> Hi,
>
> Fedora’s new Go packaging macros landed in rawhide (koji) today.
>
> The corresponding Fedora Go packaging conventions are therefore
> EFFECTIVE for new rawhide builds. For the first time in Fedora’s
> history, we will be able to perform Go package builds conforming to an
> approved Fedora Packaging Guideline.
>
> Packaging documentation:
> https://eclipseo.fedorapeople.org/guidelines/packaging-guidelines/Golang/
> and approval: https://pagure.io/packaging-committee/issue/382
> The go-rpm-templates package provides more complete info.
>
> F31 change page:
> https://fedoraproject.org/wiki/Changes/Adopt_new_Go_Packaging_Guidelines
> and approval: https://pagure.io/fesco/issue/2120
>
> While the guidelines will feel familiar to anyone who created a Fedora
> Go packages in the last two years, they DO include a backwards-
> incompatible change. Making GOPATH manipulation robust required moving
> the corresponding logic to %prep with a new %goprep macro.
>
> Therefore, existing specs are expected to fail without the addition of
> the %goprep call.
>
> This is of course not the end of the road, just a key step.
>
> It opens the way to a mass cleanup and refresh of the Fedora Go stack.
> https://pagure.io/packaging-committee/issue/901
>
> A preview of this refresh is available here:
> https://copr.fedorainfracloud.org/coprs/eclipseo/golang-ng/builds/
>
> Enormous thanks to
> – Robert-André Mauchin (eclipseo) for the gigantic work done reviewing
> updating and cleaning-up all those packages, and to
> – Elliott Sales de Andrade (Qulogic), that picked up maintenance of
> golist and fixed many of its long-standing bugs and limitations.
>
> Many thanks to the mock, rpm and redhat-rpm-config maintainers,
> that integrated the changes, we built upon (Igor Gnatenko, Florian
> Festi, Miroslav Suchý, Panu Matilainen)
>
> The macro set supports Go DynamicBuildRequires
> https://fedoraproject.org/wiki/Changes/DynamicBuildRequires
>
> They will be usable in mock as soon as rpm 4.15 lands
> https://fedoraproject.org/wiki/Changes/RPM-4.15
>
> Use in koji or copr will have to wait for the corresponding refresh
> buldsystem-side. So this part of the change is a technology preview for
> now.
>
> Best regards,
>
> --
> Nicolas Mailhot
What should I do at this moment as a packager that maintaining some Go packages?
Should I fix my packages and build against f31-go in Koji?
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> 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

iniparser SONAME bump in rawhide

[Robin Lee]

iniparser SONAME version bump from 0 to 1 since 4.1.

All packages depends on iniparser should be rebuilt:
- cava
- spindown
- ubridge

robin
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Call for participation: Fedora Flatpaks

[Robin Lee]

On Fri, Sep 7, 2018 at 9:53 AM Owen Taylor  wrote:
>
> I'd like to invite Fedora contributors to start creating Flatpaks of 
> graphical applications in Fedora. We're still working on putting the final 
> pieces into place to have a complete story from end to end, but it's 
> definitely close enough to get started.
>
> If you maintain a graphical application, please try creating a Flatpak of it. 
> Your experience will vary - some applications are quite easy, but if your 
> application, for example:
>
>  * Uses qt5-qtwebengine
>  * Uses many KDE libraries
>  * Uses many Perl or Python packages
>  * Uses texlive
>
> etc, then you may want to wait - we will eventually be creating shared builds 
> to make bundling these easier. Also, if your application has a system 
> service, installs a polkit policy, or otherwise is not self-contained, then 
> it's not a good candidate for a Flatpak.
>
> Or you can pick one of 280+ applications that have been identfied as easy to 
> Flatpak:
>
>https://fedoraproject.org/wiki/Flatpak:Easy
>
> and assist out the application package maintainer by creating a Flatpak of 
> that.
>
> An introduction, draft tutorial and other documentation can be found at:
>
>   https://fishsoup.net/misc/fedora-docs-flatpak/flatpak/
>
> (The plan is to integrate this into docs.fedoraproject.org. For now, the 
> documentation source
> is at: https://github.com/owtaylor/fedora-docs-flatpak)
>
> For help, please ask on #fedora-workstation on Freenode, or mail 
> desk...@lists.fedoraproject.org.
>
> Owen
What does it mean for 'Fedora' Flatpaks?
- Flatpaks that run on a Fedora runtime? Then, what's the benifit to
use Fedora runtime instead of freedesktop ones?
- Flatpaks that maintained by Fedora community? Then, why not
encourage people to contribute to Flathub directly?
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> 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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Call for participation: Fedora Flatpaks

[Robin Lee]

On Fri, Sep 7, 2018 at 5:15 PM Owen Taylor  wrote:
>
> On Fri, Sep 7, 2018 at 2:52 AM, Robin Lee  wrote:
>>
>> What does it mean for 'Fedora' Flatpaks?
>> - Flatpaks that run on a Fedora runtime? Then, what's the benifit to
>> use Fedora runtime instead of freedesktop ones?
>> - Flatpaks that maintained by Fedora community? Then, why not
>> encourage people to contribute to Flathub directly?
>
>
> What is meant here is "a runtime and Flatpaks built out of the Fedora RPMs on 
> Fedora infrastructure".
Great! This summary let me get the point.
>
> Some advantages this has over building and using Flatpaks on Flathub:
>
>  - In most cases, it's easier to create a Flatpak from an existing RPM rather 
> than creating a flatpak-builder manifest from scratch.
>  - We're able to reuse the Fedora updates infrastructure and automate 
> rebuilding and releasing Flatpaks and the runtime for security or other bug 
> fixes
>  - Applications with complicated build dependencies are easier to handle. Any 
> RPM in Fedora can be used as a build-time dependency. Only run-time 
> dependencies that aren't already in the runtime need to be rebuilt and 
> bundled, and even there it's a mostly automatic process.
>
> (On the other hand, for an upstream application developer who knows nothing 
> about RPMs and specfiles and so forth, and just wants to create a Flatpak of 
> their application, flatpak-builder and Flathub is likely more attractive than 
> creating a Flatpak via Fedora packaging.)
>
> It's not exclusive - you can use Flatpaks from Flathub and from this effort 
> together - even on a non-Fedora system. And, of course, you can contribute to 
> both Fedora and Flathub!
>
> Owen
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> 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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Porting Fedora for the LoongArch architecture.

[Robin Lee]

On Tue, Jan 10, 2023 at 11:13 PM 孙海勇  wrote:
>
> Hi everyone,
>
> I am Sun Haiyong, from China. I want to port Fedora for the LoongArch
> architecture.
> LoongArch is a RISC ISA released by Loongson Technology Corporation Limited,
> and has supported a series of (Binutils, GCC, Linux, Glibc, LLVM, QEMU,
> etc.)
> core open source projects.
>
> Currently, there are many linux distributions that can run on LoongArch
> machines,
> they are OpenEuler, OpenAnolis, UOS, Kylin.
>
> I am good at cross-compiling operating systems and often build Linux systems
> using something like LFS or CLFS.
>
> I have built Linux distributions using rpm package management from scratch
> several times since 2015 (some systems are not publicly available):
>
> 1 Fedora 21, 28, 32 based on MIPS64EL architecture;
> 2 CentOS 7 based on MIPS64EL architecture;
> 3 CentOS 7 based on Power8 architecture;
> 4 CentOS 8.3 based on LoongArch architecture;
> 5 OpenEuler 2109 based on LoongArch architecture.
>
> And I have published a book on porting Fedora systems to new architectures.
>
> I want to add LoongArch to the official Fedora support architecture, and
> I've
> been doing so for some time, here's some of what I've done so far：
>
> To verify the feasibility of building a LoongArch architecture branch for
> Fedora, I have used the software version from the rawhide git repository,
> and have now compiled a large number of base packages and built a temporary
> repository that can be accessed at https://mirrors.wsyu.edu.cn/fedora/
>
> I have compiled and generated more than 45,000 installable rpm files (of
> course there are a lot of perl, Python, rust and texlive files), and the
> number is still expanding, the scope of the package is enough to build a
> LiveCD system, for which I have built LXDE, MATE, WorkStation ( Gnome3) of
> the LiveCD and the installation of the ISO, you can get in the following
> address: https://github.com/fedora-remix-loongarch/releases-info
>
> Of course, there are still a lot of problems with LoongArch's Fedora system,
> for example, some software is not yet fully supported by the upstream
> community, but I believe the power of the community can gradually improve
> them, so I am sending out an email here to get more people to support this
> new LoongArch architecture.
>
> I have recruited some developers who are interested in this and they are：
>
> Wu Xiaotian
> Chen Huacai
> Shi Pujin
> Si Yanteng
> Chen Feiyang
>
> Of course, there are many other users who are interested in Fedora systems.
>
> I'm currently a newbie in the Fedora community, so I need help from
> community
> developers, and would like someone to guide me on what to do next, such as
> what would be a better time to submit necessary patches to packages in the
> Fedora repository, how to develop in a collaborative manner, what other
> systems to be used for management, etc. In short, any information would be
> useful. Could I get help here? :)
>
> Again, thanks for reading this email.

Hi, 海勇 and other LoongArch contributors!

I am a long-term Chinese Fedora packager. I also got interested in
LoongArch recently
and started to create some PRs[1][2] related to LoongArch.

Please feel free to reach out to me personally. I hope I can help you
from the Fedora side.

[1] https://src.fedoraproject.org/rpms/cross-binutils/pull-request/2
[2] https://src.fedoraproject.org/rpms/cross-gcc/pull-request/3
-robin
>
> Best Regards
> Sun Haiyong
> ___
> 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, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Porting Fedora for the LoongArch architecture.

[Robin Lee]

On Wed, Jan 11, 2023 at 4:34 PM Zbigniew Jędrzejewski-Szmek
 wrote:
>
> On Tue, Jan 10, 2023 at 11:12:22PM +0800, 孙海勇 wrote:
> > Hi everyone,
> >
> > I am Sun Haiyong, from China. I want to port Fedora for the LoongArch
> > architecture.
>
> Cool!
>
> What is the status of qemu support?
QEMU support is fully upstreamed. Qemu[1] in F38/Rawhide already built
loongarch64 sub-packages.
EDK2 support is also upstreamed but Fedora does not catch up. We can
download edk2-loongarch64-code.fd from here[2]

[1] https://koji.fedoraproject.org/koji/buildinfo?buildID=2102503
[2] 
https://github.com/loongson/Firmware/blob/b5cbb26048ab3000e76df9ebae72a2a3ecfb77fe/LoongArchVirtMachine/edk2-loongarch64-code.fd
-robin


>
> Zbyszek
> ___
> 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, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Do we have alternatives to alternatives?

[Robin Lee]

On Mon, Jan 16, 2023 at 7:34 PM Petr Menšík  wrote:
>
> Hi!
>
> I heard (read) objections to any alternatives macros usage often. But
> unless I am mistaken, we do not have any user (enough) friendly way to
> support similar functionality tools with just minor differences.
>
> I thought about it recently and I think we have similar issue solved by
> systemd-sysusers macros. Unless I am mistaken, they work fine even on
> rpm-ostree distributions. They have some similarities with alternatives
> %post scriptlets:
>
> those scriptlets more define values for some other tools than they need
> immediate reaction. Original %pre scriptlets adding users had to be
> executed during install and never outside. systemd-sysusers solves it
> fine by calling a common tool and data configuration file. It makes it
> possible to configure all users at a time or just the user from given
> config.
>
> I think similar approach could work with alternatives. Instead of
> defining the alternative name by alternatives --install command, we
> could move link name, path and priority to simple configuration snippet.
> Then process that definition either per-package (for classic rpm %post)
> or after-install (for rpm-ostree based distributions). The result should
> be the same, just time of execution may differ. It would require
> modification of alternatives to read instructions also from config file,
> not only from command line parameters.
>
> It might be naive, but wouldn't such modification allow to solve
> alternatives sufficiently also for ostree based installations? Is there
> a reason why this would not work? Of course it would add extra config
> file per package using alternatives. Unless I am mistaken, we do not
> have full featured replacement for current alternatives. Other than not
> having alternatives at all. I doubt dnf swap approach is more
> user-friendly, especially because it cannot be done by PackageKit GUI tools.
>
> Is there a reason, why my idea cannot work? Is there an unsolved problem
> it could not solve? Have something similar been considered already?
>
> Best Regards,
> Petr
>
> --
> Petr Menšík
> Software Engineer, RHEL
> Red Hat, https://www.redhat.com/
> PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
In the great blueprint of image-based system[1], system should boot
with an empty /etc filesystem.

But I found Fedora still has two requirements on the /etc filesystem.

The first one is /etc/alternatives. So I also hope we can change to
another mechanism that
satisfies the need for image-based system.

The other is the need for /etc/ld.so.*.

[1] https://0pointer.net/blog/fitting-everything-together.html

-robin
> ___
> 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, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Poco soname bump landing in rawhide/f38

[Robin Lee]

Poco 1.12.4 build with a soname bump is completed by massive rebuild.

-robin
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: questions about requesting new package into official Fedora repository?

[Robin Lee]

On Tue, Feb 21, 2023 at 11:14 AM Felix Wang  wrote:
>
> If I want to packaging a new package into Fedora repository, I did a koji 
> scratch build, which it failed on some architecture. Is there a minimum  
> architecture requirement, which builds successfully on some architecture 
> (like x86_64?), in order to adopt the new package?

https://docs.fedoraproject.org/en-US/packaging-guidelines/#_architecture_support
-robin
> ___
> 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, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Orphaned Zim

[Robin Lee]

I've orphaned the Zim package. It fails to build with Python 3.12 in Rawhide.

Users can move to the flatpak on Flathub, which is also packaged by me.

-robin
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Orphaned plenty of packages

[Robin Lee]

Sorry, since changes in day-job and lack of time for working on
Fedora, I orphaned plenty of packages:

* buildstream
* csmith
* drumstick
* drumstick0
* kmetronome
* nsnake
* nudoku
* qstardict
* qterm
* sonivox
* texworks
* vmpk

-robin
--
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Poco soname bump in rawhide/f37

[Robin Lee]

Poco 1.12.2 landed in rawhide/f37 with a soname bump.

-robin
___
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

fcitx-qt5 license changed to 'GPLv2+ and BSD'

[Robin Lee]

fcitx-qt5 1.2.1 license changed from 'GPLv2+ and LGPLv2+' to 'GPLv2+ and
BSD'.

-robin
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Deepin Desktop Environment v20 coming to Rawhide with packages license changed

[Robin Lee]

* Upstream original release notes:
https://www.deepin.org/en/2020/09/11/deepin-20-innovation-is-ongoing/
* Versions of packages are actually sychronised with Arch Linux, not
directly with Deepin upstream.
* There are new packages released upstream but not packaged in Fedora.
We lack human power.
* The packages have been built with Qt 5.15.2
* Packit is deployed to maintain rpm packing stuff. And major number
of the specfiles has been merged upstream.
* dtkcore and dtkwidget license is changing to LGPLv3+
* dtkcore, dtkwidget and dtkwm so name versions bump to 5.

-robin
___
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

[Robin Lee]

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

Re: Self-introduction: yecheng

[Robin Lee]

On Tue, Aug 1, 2017 at 9:45 PM, Cheng Ye  wrote:

> I'm an inexperienced high school student interested in poping some
> packages off the package maintainer wishlist (and hopefully learn to read
> others source codes more efficiently) during this summer vacation.
>
> This is the bugzilla page of my first review request:
> https://bugzilla.redhat.com/show_bug.cgi?id=1476434
> Thanks for Iwicki Artur's corrections  and sorry for the frequent rebuilds
> and URL changes.
> By the way, if possible, please help to put a test-result-inprogress sign
> beside bstring package on package maintainer wishlist (
> https://fedoraproject.org/wiki/Package_maintainers_wishlist?rd=
> PackageMaintainers/WishList)  and fill the status field with bug#1476434.
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
Welcome, Cheng Ye!

Currently we have a small team to work on importing deepin[1] packages to
Fedora[2].
I wonder if you would like to help.

Feel free to contact me personally.

[1] https://www.deepin.org/
[2] https://fedoraproject.org/wiki/SIGs/DeepinDE
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: review swap

[Robin Lee]

On Fri, Aug 18, 2017 at 6:32 AM, Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:

> I'm looking for a reviewer for
>
> Bug 1478231 – Review Request: conda - Cross-platform, Python-agnostic
> binary package manager
> https://bugzilla.redhat.com/1478231

Taken.
You helped a lot to deepin packaging.

-robin

>
>
> I can review stuff in return.
>
> Zbyszek
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: hiredis soname bump

[Robin Lee]

On Tue, Jan 18, 2022 at 9:53 AM Kevin Fenzi  wrote:
>
> On Mon, Jan 17, 2022 at 10:44:57AM +1100, Nathan Scott wrote:
> > On Mon, Jan 17, 2022 at 10:35 AM Iñaki Ucar  wrote:
> > > On Mon, 17 Jan 2022 at 00:21, Nathan Scott  wrote:
> > > > On Mon, Jan 17, 2022 at 7:05 AM Kevin Fenzi  wrote:
> > > > >
> > > > > Greetings.
> > > > >
> > > > > We currently have hiredis-0.13.3-16 in rawhide, I'd like to upgrade to
> > > > > 1.0.2, which includes a soname bump.
> > > >
> > > > I think upstream may have reverted this change FWIW ...
> > > > https://github.com/redis/hiredis/issues/990
> > >
> > > This refers to the incorrect SONAME bump in 1.0.1 with respect to
> > > 1.0.0. But as Kevin said, we still have 0.13.3 in Fedora, so...
> >
> > Aha - right you are, thanks for the correction.
>
> ok, so I made the sidetag (f36-build-side-49618) and rebuilt things,
> but of course now there's 4 more erroring packages (I guess due to gcc12?).
> Any help welcomed. :)
>
> (bccing maintainers)
>
> gearmand
> https://koji.fedoraproject.org/koji/taskinfo?taskID=81386050
> ...
> ./gear_config.h:35:25: error: conversion from 'int' to 'const std::string' 
> {aka 'const std::__cxx11::basic_string'} is ambiguous
Fixed build in the side tag.
>
> sems
> https://koji.fedoraproject.org/koji/taskinfo?taskID=81386117
> ...
> /builddir/build/BUILD/sems-baad4717fdb3c02a63eb4869f31ec33ff8ec1fed/core/tests/fct.h:267:12:
>  error: '__builtin_strncpy' specified bound 256 equals destination size 
> [-Werror=stringop-truncation]
>
> seqan3
> https://koji.fedoraproject.org/koji/taskinfo?taskID=81386062
> /builddir/build/BUILD/seqan3-3.1.0/include/seqan3/utility/concept/exposition_only/core_language.hpp:67:5:
>  error: testing if a concept-id is a valid expression; add 'requires' to 
> check satisfaction [-Werror=missing-requires]
>67 | std::convertible_to= v1), bool>;
>
> suircata
> https://koji.fedoraproject.org/koji/taskinfo?taskID=81386008
>Compiling suricata v6.0.4 (/builddir/build/BUILD/suricata-6.0.4/rust)
> /usr/lib/librustc_driver-f074454651f889f4.so(+0x4d3083)[0xf3c95083]
> linux-gate.so.1(__kernel_sigreturn+0x0)[0xf7f9a570]
> /usr/lib/libLLVM-13.so(+0xf564fe)[0xee3684fe]
> /usr/lib/libLLVM-13.so(+0xf586ae)[0xee36a6ae]
> /usr/lib/libLLVM-13.so(+0x104900f)[0xee45b00f]
> /usr/lib/libLLVM-13.so(_ZN4llvm18ScheduleDAGSDNodes12EmitScheduleERNS_26MachineInstrBundleIteratorINS_12MachineInstrELb0EEE+0x382)[0xee45a1a2]
> /usr/lib/libLLVM-13.so(_ZN4llvm16SelectionDAGISel17CodeGenAndEmitDAGEv+0xa2a)[0xee532fca]
> /usr/lib/libLLVM-13.so(_ZN4llvm16SelectionDAGISel16SelectBasicBlockENS_14ilist_iteratorINS_12ilist_detail12node_optionsINS_11InstructionELb0ELb0EvEELb0ELb1EEES6_Rb+0x303)[0xee532543]
> /usr/lib/libLLVM-13.so(_ZN4llvm16SelectionDAGISel20SelectAllBasicBlocksERKNS_8FunctionE+0x2204)[0xee531d14]
> /usr/lib/libLLVM-13.so(_ZN4llvm16SelectionDAGISel20runOnMachineFunctionERNS_15MachineFunctionE+0xc22)[0xee52e932]
> /usr/lib/libLLVM-13.so(+0x37b98e1)[0xf0bcb8e1]
> /usr/lib/libLLVM-13.so(_ZN4llvm19MachineFunctionPass13runOnFunctionERNS_8FunctionE+0x14b)[0xedfddd0b]
> /usr/lib/libLLVM-13.so(_ZN4llvm13FPPassManager13runOnFunctionERNS_8FunctionE+0x598)[0xedd407d8]
> /usr/lib/libLLVM-13.so(_ZN4llvm13FPPassManager11runOnModuleERNS_6ModuleE+0x48)[0xedd48148]
> /usr/lib/libLLVM-13.so(_ZN4llvm6legacy15PassManagerImpl3runERNS_6ModuleE+0x43b)[0xedd40fdb]
> /usr/lib/libLLVM-13.so(_ZN4llvm6legacy11PassManager3runERNS_6ModuleE+0x2b)[0xedd484fb]
> /usr/lib/librustc_driver-f074454651f889f4.so(+0x5702ed)[0xf3d322ed]
> /usr/lib/librustc_driver-f074454651f889f4.so(+0x8752aa)[0xf40372aa]
> /usr/lib/librustc_driver-f074454651f889f4.so(+0x87aefe)[0xf403cefe]
> /usr/lib/librustc_driver-f074454651f889f4.so(+0x893167)[0xf4055167]
> /usr/lib/librustc_driver-f074454651f889f4.so(+0x88c6e4)[0xf404e6e4]
> /usr/lib/librustc_driver-f074454651f889f4.so(+0x7a91a3)[0xf3f6b1a3]
> /usr/lib/librustc_driver-f074454651f889f4.so(+0x820c27)[0xf3fe2c27]
> /usr/lib/libstd-1c430345c3146024.so(rust_metadata_std_6938c2bdeba667b5+0x9d37b)[0xf36d537b]
> /usr/lib/libc.so.6(+0x8baf1)[0xf34d9af1]
> /usr/lib/libc.so.6(+0x1118cc)[0xf355f8cc]
> error: could not compile `suricata`
>
> kevin
___
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: Orphaning poco

[Robin Lee]

On Fri, Oct 8, 2021 at 2:49 AM Scott Talbert  wrote:
>
> I'm orphaning poco: https://src.fedoraproject.org/rpms/poco
>
> I'm not sure why I picked it up originally - I don't use it.  It currently
> FTBFS in rawhide due to OpenSSL 3.0 (and can't be fixed easily by going
> back to OpenSSL 1.1 because one of its other BR's requires OpenSSL 3.0).
>
> Nothing in Fedora depends on it but there is one RPMFusion dependency I
> believe (vdr-plex).  It's not technically an orphaning as there is a
> comaintainer, but that comaintainer hasn't done anything in several years.

I take it. It is a great library and I use it even in my day job.
>
> Scott
> ___
> 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 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: F36 Change: ostree native containers / CoreOS layering (System-Wide Change proposal)

[Robin Lee]

On Wed, Nov 24, 2021 at 1:20 AM Ben Cotton  wrote:
>
> https://fedoraproject.org/wiki/Changes/OstreeNativeContainer
>
> == Summary ==
>
> Enhance the (rpm-)ostree stack to natively support OCI/Docker
> containers as a transport and delivery mechanism for operating system
> content.
>
> This is the basis of
> https://github.com/coreos/enhancements/blob/main/os/coreos-layering.md
>
>
> == Owner ==
> * Name: [[User:walters| Colin Walters]]
> * Email: walt...@verbum.org
>
>
> == Detailed Description ==
>
> Having the Fedora ecosystem (from users to release engineering)
> maintain tooling that operates on all three of "container images",
> RPMs, and OSTree updates is a maintenance burden.
>
> This proposes that:
>
> * The ostree stack is enhanced to support
> encapsulating/unencapsulating ostree commits as OCI/Docker images
> (DONE)
> * rpm-ostree is updated to consume this, while still supporting all
> its current features (e.g. per-machine package layering) (DONE)
> * We ship e.g. `quay.io/fedora/coreos:stable` and
> `quay.io/fedora/silverblue:36` etc.
> * We support '''deriving''' new user custom images from these images
> * We enhance this tooling to
> [https://github.com/ostreedev/ostree-rs-ext/issues/69 support
> chunking]
>
> For more details, please see:
>
> * [https://github.com/coreos/enhancements/blob/main/os/coreos-layering.md
> CoreOS layering enhancement]
> * [https://coreos.github.io/rpm-ostree/container/ rpm-ostree container docs]
This is a great enhancement for the OSTree world. People can use Docker hub
or quay.io as an OSTree hub to maintain different ostree-based Linux
distributions for users to rebase and try.

This function is unrelated to 'rpm' but unfortunately provided by 'rpm-ostree'.
Maybe we should provide another standalone tool so non-rpm/dnf-based
distributions can be easier to deploy.

-robin
___
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

[Robin Lee]

On Wed, Jun 6, 2018 at 12:48 PM, Feather Lin  wrote:
> Hello Jerry,
> Thank you! (謝謝！） Yes the 歡迎光臨 is mean welcome the people.
Welcome!
Feel free to check out the methods to contact the 中文 user group.[1]

[1] https://fedoraproject.org/wiki/Zh

-robin 李瑞彬
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/ASYNZJW6TGIU4GIUYWKCJPIBEWF6GZHK/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/HP2D4PY7NUYYWFAYLEN2MZLFL5D6NTSY/

Re: Self Introduction: Kairui Song

[Robin Lee]

On Fri, Jul 13, 2018 at 2:33 AM, Kairui Song  wrote:
> Hi all,
>
> I'm working on submitting a package, it's my first package. So I want to
> give a brief self-introduction here.
>
> My name is Kairui Song, I'm a software engineer at Red Hat, have been a Red
> Hat employee for two years, and start working on kdump / kexec and related
> components recently. Have been a Linux user/fan/enthusiast for about 4 years
> since college, started with customizing and optimize my smartphone's kernel.
> Besides this, I also have some experience working as a full-stack developer,
> and I enjoy learning and try all kinds of new things and tech stacks. I have
> a personal website, feel free to visit if you have any interest
> , there you can find my Github and some other social
> accounts.
>
> I'm seeking a sponsor for my package review request: (already approved)
> . I'm working with
> kexec-tools' package maintainer on splitting out a subpackage, please help
> if any sponsor is reading this, thank you!
Welcome!
Let's get in touch in the 中文 user group.[1]

[1] https://fedoraproject.org/wiki/Zh

-robin 李瑞彬
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/YR5WDDFVKKXO6ZJH72RXK3HNBBPHLOZ3/
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/FZBCN7Q5GC5B2FTJQGJVOXWZ2TEX3L5G/

Re: tool to order packages by build dependencies (rpmbuild-order)

[Robin Lee]

On Thu, Jul 26, 2018 at 1:21 PM Jens-Ulrik Petersen  wrote:
>
> Hi,
>
> This is an early announcement about a tool called 'rpmbuild-order' I made to 
> sort RPM-based packages in build dependency order. I am not sure if such a 
> tool exists already?  Certainly some tools like `mockchain` can already order 
> builds in this way, but I don't know of such a standalone utility.
>
> https://github.com/juhp/rpmbuild-order
>
> It works by reading the BRs in spec files of the packages you want to build, 
> generating a graph of their interdependencies internally, from which it 
> outputs the packages in a build dependency order. If you have a complete 
> family of packages checked out, it can also output the dependencies or 
> reverse dependency of any of the packages.
>
> You can try it from my copr repo:
> https://copr.fedorainfracloud.org/coprs/petersen/rpmbuild-order
>
> Let me know if you if it works for you or you find any problems.
> I have tested it lightly a set of about 400 packages. There are probably 
> optimization that could be made.  I feel it would be good to do mass-rebuilds 
> for example in dependency order perhaps.
>
> Also, I am planning to add this package to Fedora: before doing that I am 
> open to suggestions for alternative names for the tool - I couldn't really 
> think of a better one..
>
> Cheers, Jens
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/ECWHXZHDJ5UEPTLRHGYYGN65EW7Y6GRU/

I use a tool with similar function named Planex[1]

[1] https://github.com/xenserver/planex

-robin
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/QCX6C33POZMAHXQSBVWUOVWLUR2NVRHJ/

Re: bootstrapping without .spec modification

[Robin Lee]

On Fri, Jan 29, 2021 at 7:33 PM Zbigniew Jędrzejewski-Szmek
 wrote:
>
> Hello fellow packagers!
>
> The subject of bootstrapping came up on fedora-devel recently.
> I had the following idea, about which I would love to hear some feedback:
>
> == Problem:
> building packages with bootstrap currently involves doing *two*
> patches to the spec file: first to add '%global _without_bootstrap 1',
> then comes a rebuild, second to remove the macro, and then comes
> another rebuild.
>
> == Partial solution
> Let's have an rpm that provides a single file that sets the macro for us:
> $ rpm -qpl noarch/rpm-with-bootstrap-0-1.fc34.noarch.rpm
> /usr/lib/rpm/macros.d/macros.rpm-with-bootstrap
> $ cat rpm-macros-bootstrap/macros.rpm-with-bootstrap
> # Enable %%with_bootstrap for all builds
> %_with_bootstrap 1

For my experience, a boolean bootstrap macro is not enough
for bootstrapping the whole Feodra distribution. Especially for
cross-bootstrapping Fedora to a new architecture.

We may need a few bootstrap stages.
For each stage we can define different value for an rpm macro.
For example:
%define _bootstrap_stage 1
%define _bootstrap_stage 2


And the %_bootstrap or %bootstrap macro may have been used
by different packages for different semantics.
It is better to use a brand new macro for distribution bootstrap.

-robin

>
> Then we can do the following:
> $ rpmdev-bumpspec 'Do rebuild w/ bootstrap'
> $ mock -i rpm-with-bootstrap
> $ fedpkg mockbuild
> $ rpmdev-bumpspec 'Do rebuild w/o bootstrap'
> $ mock -i rpm-without-bootstrap [3]
> $ fedpkg mockbuild
> Voilà!
>
> The same pattern should work with side-tags in koji.
>
> I prepared a poc implementation in [1] which builds
> rpm-{with,without}-{bootstrap,tests,lto}, and a test package [2] which
> prints the values of %with_bootstrap, %with_tests, %with_lto.
>
> == Full solution
> If we have automatic version bumps, this would become even simpler:
> $ mock -i rpm-with-bootstrap
> $ fedpkg mockbuild
> $ mock --dnf-cmd remove rpm-with-bootstrap
> $ fedpkg mockbuild
>
> My idea would be to submit [1] for package-review so that it's
> generally available.
>
> Note that this works if the package we're building uses
>   %bcond_with bootstrap
> or
>   %bcond_without bootstrap
> I picked %{with bootstrap}, %{with lto}, %{with tests} as
> generally-useful settings. I think it is worth standarizing the names
> like this, and at least %{with bootstrap} and %{with tests} could be
> added to packaging guidelines.
>
> [1] https://pagure.io/rpm-macros-bootstrap
> [2] https://pagure.io/rpm-macros-test
> [3] rpm-without-bootstrap has Conflicts:rpm-with-bootstrap, so installing
> one forces the other out. Alternatively, rpm-with-bootstrap may just
> be uninstalled.
>
> Zbyszek
> ___
> 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

Re: opam (was: Re: Orphaned packages looking for new maintainers)

[Robin Lee]

On Wed, May 19, 2021 at 4:29 AM Richard W.M. Jones  wrote:
>
> (I've added a few opam devs to CC)
>
> On Tue, May 18, 2021 at 10:14:41PM +0200, Miro Hrončok wrote:
> > opam  orphan   1 weeks 
> > ago
>
> I didn't notice that opam had been orphaned.  This package is the tool
> used for source packaging of OCaml packages under $HOME
> (https://opam.ocaml.org/).
>
> I don't especially like language-specific tools for managing packages,
> because of the usual problems that have been widely discussed
> elsewhere and it's not profitable to rehash them again.  This is my
> personal view.
>
> The question is if we want to keep this in Fedora or not?  ie. As an
> official Fedora package versus something that opam maintainers would
> provide themselves as a download.

I would like to take opam for Fedora. People who need this package would
be easier to install it. Just like pip for Python and cpanm for Perl,
which are available in Fedora.
People just use the package as it is. They don't urge a full
integration with Fedora-shipped
Ocaml packages.

And there is a use case in the XAPI community and the Citrix company
that a huge opam
repo is packaged in a single RPM[1]. They don't ship individual RPM
per Ocaml package.
They also package opam as an RPM[2]. So, It won't be hard to also
maintain the opam RPM in
Fedora.

[1] https://github.com/xcp-ng-rpms/xs-opam-repo
[2] https://github.com/xcp-ng-rpms/opam

- robin
>
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-builder quickly builds VMs from scratch
> http://libguestfs.org/virt-builder.1.html
> ___
> 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 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

Poco FTBFS fix and soname bump

[Robin Lee]

Poco upstream finally committed OpenSSL 3 in the next release branch.
And Carl George helped to finish rawhide/f36 builds with a snapshot
source.

There is also a soname bump. Poco bumps soname at every release.

After all, nothing else in Fedora depends on Poco.

-robin
___
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: Ma Zheng

[Robin Lee]

On Tue, Jul 27, 2021 at 10:29 PM Ma, Zheng  wrote:
>
> Hi all,
>
> This is Zheng, newly coming to Fedora community :)
>
> I’m now working on the rpm packaging things, hoping to contribute a package 
> soon!
Welcome! Hope for your first package!

- robin
>
>
>
> Zheng
>
>
>
> ___
> 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 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