Re: Packaging software for LulzBot Taz-6 3D printer

[Bob Mauchin]

On Sat, 19 Aug 2023, 19:30 W. Michael Petullo,  wrote:

> I am trying to package the software necessary to operate the LulzBot
> Taz-6 3D printer. This seems to have been supported in previous versions
> of Fedora [1], so I am trying to take ownership of retired packages.
> Some of the dependencies should be broadly useful, like the arduino
> package. I could use help with two things: (1) package reviewing and
> (2) help with two of the packages.
>
> The following are available for review now:
>
> jakarta-commons-httpclient:
> https://bugzilla.redhat.com/show_bug.cgi?id=2232859
> jmdns: https://bugzilla.redhat.com/show_bug.cgi?id=2232860
> jsemver: https://bugzilla.redhat.com/show_bug.cgi?id=2232861
> python-uranium-lulzbot:
> https://bugzilla.redhat.com/show_bug.cgi?id=2232862
> libarcus-lulzbot
> :
> https://bugzilla.redhat.com/show_bug.cgi?id=2232864
> CuraEngine-lulzbot
> :
> https://bugzilla.redhat.com/show_bug.cgi?id=2232865
> cura-lulzbot
> :
> https://bugzilla.redhat.com/show_bug.cgi?id=2232866
>
> The dependencies led me to create a COPR repository to aid in the review
> process:
>
> [copr:copr.fedorainfracloud.org:mikep:lulzbot]
> name=Copr repo for lulzbot owned by mikep
> baseurl=
> https://download.copr.fedorainfracloud.org/results/mikep/lulzbot/fedora-$releasever-$basearch/
> type=rpm-md
> 
> skip_if_unavailable=True
> gpgcheck=1
> gpgkey=
> https://download.copr.fedorainfracloud.org/results/mikep/lulzbot/pubkey.gpg
> repo_gpgcheck=0
> 
> enabled=1
> enabled_metadata=1
>
> I could use help with two of the packages: arduino and
> lulzbot-marlin-firmware.
>
> To get the arduino package to build and install, I had to remove some
> dependencies. First, arduino-builder is deprecated. Does someone know
> Arduino enough to know if I need to replace this with arduino-cli?
> (And how?) Second, I removed the dependency on asm2, which I found used
> deprecated RPM macros such as %add_to_maven_depmap. Could someone take a
> look at that retired package and suggest how to modernize it towards the
> newer macros?
>
> The lulzbot-marlin-firmware does not build. The build fails with:
>
>
> /usr/lib/gcc/arm-none-eabi/12.2.0/../../../../arm-none-eabi/bin/ld: cannot
> find
> ../ArduinoAddons/arduino-1.8.5/packages/ultimachine/hardware/sam/1.6.9-b/variants/archim/libsam_sam3x8e_gcc_rel.a:
> No such file or directory
>
> Does anyone know where libsam_sam3x8e_gcc_rel.a is supposed to come
> from?
>
> [1] https://lulzbot.com/learn/cura-lulzbot-edition-installation-fedora
>
> --
> Mike
>
> :wq
>


I don't have time to check today because family reunion in middle of
nowhere, but from what I could see this morning, could you :

- convert to SPDX
- use autorelease/autochangelog
- bump each package to the latest version

For libarcus-lulzbot, use the gitlab repohttps://
gitlab.com/lulzbot3d/cura-le/libarcus
Same for uranium: https://gitlab.com/lulzbot3d/cura-le/uranium

Etc for the other lulzbot projects

And thus grab the sources from there.

Cheers,

Robert-André
___
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: RPM packaging help

[Bob Mauchin]

On Sun, 13 Aug 2023, 21:39 Maxwell G,  wrote:

> Hi Robert-André and Andrew,
>
>
> On Sun Aug 13, 2023 at 11:23 +0200, Robert-André Mauchin wrote:
> > On 8/10/23 15:43, Andrew Heath wrote:
> > > All,
> > > My name is Andrew, and I have been working with the Fedora Infra team
> and we are trying to
> > > create some RPMs for some projects that we are working on, one of the
> RPMs we need to create
> > > is for the Ansible receptor[1 ].
> I have a copy of the
> > > spec file from downstream Red Hat that gives some guidance but where
> its a mix of python and
> > > go-lang I was wondering if I could have some guidance from more
> experienced packers on how
> > > to package up the application correctly so that we can get the package
> in use for the Fedora
> > > Infra.
> > >
> > > Links:
> > > [1]: https://github.com/ansible/receptor <
> https://github.com/ansible/receptor>
> > >
> > > --
> > > Sincerely,
> > > Andrew Heath
> > > aheath1...@gmail.com 
> > >
> >
> > Ok, let's roll, you will end up with a Frankstein SPEC, be warned. Here
> is the process:
>
> This is great. Thanks! Here are some notes:
>
> > License:Apache-2.0 AND ISC AND MIT AND BSD-3-Clause AND
> BSD-2-Clause
>
> What did you use to generate that list of licenses?
>
>
>
>

What I've mentioned on Matrix this weekend or last night, the wrapper
around the deps.devs I coded Saturday, and subsequent script I added to the
new tools repo I added to Go-sig on Pagure.

https://github.com/eclipseo/pydepsdev
https://pagure.io/GoSIG/tools



> > %if %{with bundled}
> > Provides:   bundled(golang(github.com/ansible/receptor) = 1.4.1
> > Provides:   bundled(golang(github.com/creack/pty) = 1.1.18
> > Provides:   bundled(golang(github.com/davecgh/go-spew) = 1.1.1
> > Provides:   bundled(golang(github.com/emicklei/go-restful/v3) =
> 3.10.2
> > Provides:   bundled(golang(github.com/fortytw2/leaktest) = 1.3.0
> > Provides:   bundled(golang(github.com/fsnotify/fsnotify) = 1.6.0
> > Provides:   bundled(golang(github.com/ghjm/cmdline) = 0.1.2
> > Provides:   bundled(golang(github.com/go-logr/logr) = 1.2.4
> > Provides:   bundled(golang(github.com/go-openapi/jsonpointer) =
> 0.19.6
> > Provides:   bundled(golang(github.com/go-openapi/jsonreference) =
> 0.20.2
> > Provides:   bundled(golang(github.com/go-openapi/swag) = 0.22.3
> > Provides:   bundled(golang(github.com/go-task/slim-sprig) =
> 0.0.0-20230315git52ccab3
> > Provides:   bundled(golang(github.com/gogo/protobuf) = 1.3.2
> > Provides:   bundled(golang(github.com/golang-jwt/jwt/v4) = 4.5.0
> > Provides:   bundled(golang(github.com/golang/mock) = 1.6.0
> > Provides:   bundled(golang(github.com/golang/protobuf) = 1.5.3
> > Provides:   bundled(golang(github.com/google/gnostic) = 0.6.9
> > Provides:   bundled(golang(github.com/google/go-cmp) = 0.5.9
> > Provides:   bundled(golang(github.com/google/gofuzz) = 1.2.0
> > Provides:   bundled(golang(github.com/google/pprof) =
> 0.0.0-20230502git255e3b9
> > Provides:   bundled(golang(github.com/google/shlex) =
> 0.0.0-20191202gite7afc7f
> > Provides:   bundled(golang(github.com/google/uuid) = 1.3.0
> > Provides:   bundled(golang(github.com/gorilla/websocket) = 1.5.0
> > Provides:   bundled(golang(github.com/imdario/mergo) = 0.3.15
> > Provides:   bundled(golang(github.com/josharian/intern) = 1.0.0
> > Provides:   bundled(golang(github.com/json-iterator/go) = 1.1.12
> > Provides:   bundled(golang(github.com/jupp0r/go-priority-queue) =
> 0.0.0-20160601gitab10738
> > Provides:   bundled(golang(github.com/mailru/easyjson) = 0.7.7
> > Provides:   bundled(golang(github.com/minio/highwayhash) = 1.0.2
> > Provides:   bundled(golang(github.com/moby/spdystream) = 0.2.0
> > Provides:   bundled(golang(github.com/modern-go/concurrent) =
> 0.0.0-20180306gitbacd9c7
> > Provides:   bundled(golang(github.com/modern-go/reflect2) = 1.0.2
> > Provides:   bundled(golang(github.com/munnerz/goautoneg) =
> 0.0.0-20191010gita7dc8b6
> > Provides:   bundled(golang(github.com/onsi/ginkgo/v2) = 2.9.4
> > Provides:   bundled(golang(github.com/pbnjay/memory) =
> 0.0.0-20210728git7b4eea6
> > Provides:   bundled(golang(github.com/pmezard/go-difflib) = 1.0.0
> > Provides:   bundled(golang(github.com/prep/socketpair) =
> 0.0.0-20171228gitc2c6a7f
> > Provides:   bundled(golang(github.com/quic-go/qtls-go1-19) = 0.3.2
> > Provides:   bundled(golang(github.com/quic-go/qtls-go1-20) = 0.2.2
> > Provides:   bundled(golang(github.com/quic-go/quic-go) = 0.34.0
> > Provides:   bundled(golang(github.com/rogpeppe/go-internal) = 1.10.0
> > Provides:   bundled(golang(github.com/songgao/water) =
> 0.0.0-20200317git2b4b6d7
> > Provides:   bundled(golang(github.com/spf13/pflag) = 1.0.5
> > Provides:   bundled(golang(github.com/stretchr/testify) = 1.8.1
> > Provides:   

Re: Disabling rawhide builds during branching

[Bob Mauchin]

On Mon, 7 Aug 2023, 23:19 Tomas Hrcka,  wrote:

> Hi All,
>
> Fedora Linux 39 is going to be branched from rawhide on 2023-08-08 at
> 10:30 UTC
> as per the previous discussion[1] we are going to disable new koji
> builds for the duration of this event.
>
> All builds that will be running at that time for the rawhide will be
> canceled and can be resubmitted by maintainers after the branching.
>
> All rawhide updates that are in a pending state for rawhide will be
> unpushed.
>
> Once Fedora Linux 39 is branched we will re enable builds in koji.
>
> 1 -
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E/#GWY4TIDIP65HA2V33F2ROU2MJLKMRZ7E
> ___
> 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



Hello,

Around how much time will it take?

Thanks,


Robert-André

>
>
___
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: Orphaned packages looking for new maintainers

[Bob Mauchin]

Hi,


I'm working on the Go situation due to my non responsive situation.

I'm currently assessing what is needed by our binaries packages and will
take packages needed that have been orphaned. The reminder will be thus
retired.

Some package are probably FTBFS and I will need time to get them back to a
working condition, hopefully before the deadline.

Wishing you all a great day,

Robert-André Mauchin

Fas: eclipseo



>
___
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: Non-responsive maintainer check for eclipseo

[Bob Mauchin]

I'm here just very busy with work and being tired, I ll try to work on
stuff this weekend.

On Wed, Mar 15, 2023, 18:23 Mark E. Fuller  wrote:

> Thanks for the suggestion, but I do not use Twitter and don't want to
> create an account.
>
>
> On March 15, 2023 5:13:43 PM GMT+02:00, Fabio Valentini <
> decatho...@gmail.com> wrote:
>
>> On Wed, Mar 15, 2023 at 4:04 PM Mark E. Fuller  
>> wrote:
>>
>>>
>>>  Hi,
>>>  This is a non-responsive maintainer check for eclipseo.
>>>  I am trying to contact him as the owner of
>>>  golang-github-masterminds-semver[0].
>>>  There is one other open non-responsive maintainer check, filed ~2 weeks
>>>  ago[1].
>>>  Does anyone know how to contact eclipseo?
>>>
>>
>> I haven't had luck with getting responses to bugs or emails either ...
>> Maybe reaching out on twitter could work? https://twitter.com/eclipseo10
>>
>> Fabio
>> --
>> 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
>
___
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: Orphaned a lot of (mostly) Go packages owned by @fpokorny

[Bob Mauchin]

On Wed, 23 Nov 2022, 12:21 Miro Hrončok,  wrote:

> Hello.
>
> Based on my conversation with Fridolín Pokorný @fpokorny, I've removed
> them
> from their Fedora packages.
>
> They left Red Hat and are no longer interested in maintaining Fedora
> packages.
>
> Co-maintainers BCC'ed.
>
> fpokorny is main admin of rpms/consul
>rpms/consul co-maintainers: @jchaloup
>fpokorny is no longer the main admin of rpms/consul
> fpokorny has a bugzilla override on rpms/consul
>fpokorny has no longer a bugzilla overrides on rpms/consul
> fpokorny is maintainer of rpms/docker-machine
>fpokorny is no longer maintaining rpms/docker-machine
>fpokorny is no longer watching rpms/docker-machine
> fpokorny is maintainer of rpms/docker-swarm
>fpokorny is no longer maintaining rpms/docker-swarm
>fpokorny is no longer watching rpms/docker-swarm
> fpokorny is watching rpms/gawk
>fpokorny is no longer watching rpms/gawk
> fpokorny is maintainer of rpms/go-compilers
>fpokorny is no longer maintaining rpms/go-compilers
>fpokorny is no longer watching rpms/go-compilers
> fpokorny is main admin of rpms/golang-bitbucket-kardianos-osext
>rpms/golang-bitbucket-kardianos-osext co-maintainers: @jchaloup,
> @maxamillion, @tdawson, @vbatts
>fpokorny is no longer the main admin of
> rpms/golang-bitbucket-kardianos-osext
> fpokorny is main admin of rpms/golang-bitbucket-ww-goautoneg
>rpms/golang-bitbucket-ww-goautoneg co-maintainers: @jchaloup
>fpokorny is no longer the main admin of
> rpms/golang-bitbucket-ww-goautoneg
> fpokorny is watching rpms/golang-github-10gen-openssl
>fpokorny is no longer watching rpms/golang-github-10gen-openssl
> fpokorny is main admin of rpms/golang-github-AdRoll-goamz
>rpms/golang-github-AdRoll-goamz co-maintainers: @jchaloup
>fpokorny is no longer the main admin of rpms/golang-github-AdRoll-goamz
> fpokorny is main admin of rpms/golang-github-Azure-azure-sdk-for-go
>rpms/golang-github-Azure-azure-sdk-for-go co-maintainers: @jchaloup
>fpokorny is no longer the main admin of
> rpms/golang-github-Azure-azure-sdk-for-go
> fpokorny is main admin of rpms/golang-github-BurntSushi-toml
>rpms/golang-github-BurntSushi-toml co-maintainers: @jchaloup
>fpokorny is no longer the main admin of
> rpms/golang-github-BurntSushi-toml
> fpokorny is main admin of rpms/golang-github-DATA-DOG-go-sqlmock
>rpms/golang-github-DATA-DOG-go-sqlmock co-maintainers: @jchaloup
>fpokorny is no longer the main admin of
> rpms/golang-github-DATA-DOG-go-sqlmock
> fpokorny is maintainer of rpms/golang-github-DataDog-datadog-go
>fpokorny is no longer maintaining rpms/golang-github-DataDog-datadog-go
>fpokorny is no longer watching rpms/golang-github-DataDog-datadog-go
> fpokorny is main admin of rpms/golang-github-MakeNowJust-heredoc
>rpms/golang-github-MakeNowJust-heredoc co-maintainers: @jchaloup
>fpokorny is no longer the main admin of
> rpms/golang-github-MakeNowJust-heredoc
> fpokorny is main admin of rpms/golang-github-RangelReale-osin
>rpms/golang-github-RangelReale-osin co-maintainers: @jchaloup
>fpokorny is no longer the main admin of
> rpms/golang-github-RangelReale-osin
> fpokorny is main admin of rpms/golang-github-RangelReale-osincli
>rpms/golang-github-RangelReale-osincli co-maintainers: @jchaloup
>fpokorny is no longer the main admin of
> rpms/golang-github-RangelReale-osincli
> fpokorny is main admin of rpms/golang-github-SeanDolphin-bqschema
>rpms/golang-github-SeanDolphin-bqschema co-maintainers: @jchaloup
>fpokorny is no longer the main admin of
> rpms/golang-github-SeanDolphin-bqschema
> fpokorny is main admin of rpms/golang-github-Sirupsen-logrus
>rpms/golang-github-Sirupsen-logrus co-maintainers: @jchaloup
>fpokorny is no longer the main admin of
> rpms/golang-github-Sirupsen-logrus
> fpokorny is main admin of rpms/golang-github-abbot-go-http-auth
>rpms/golang-github-abbot-go-http-auth co-maintainers: @jchaloup
>fpokorny is no longer the main admin of
> rpms/golang-github-abbot-go-http-auth
> fpokorny is main admin of rpms/golang-github-agl-ed25519
>rpms/golang-github-agl-ed25519 co-maintainers: @jchaloup
>fpokorny is no longer the main admin of rpms/golang-github-agl-ed25519
> fpokorny is main admin of rpms/golang-github-appc-spec
>rpms/golang-github-appc-spec co-maintainers: @jchaloup
>fpokorny is no longer the main admin of rpms/golang-github-appc-spec
> fpokorny is main admin of rpms/golang-github-armon-circbuf
>rpms/golang-github-armon-circbuf co-maintainers: @jchaloup
>fpokorny is no longer the main admin of rpms/golang-github-armon-circbuf
> fpokorny is main admin of rpms/golang-github-armon-go-metrics
>rpms/golang-github-armon-go-metrics co-maintainers: @jchaloup
>fpokorny is no longer the main admin of
> rpms/golang-github-armon-go-metrics
> fpokorny is main admin of rpms/golang-github-armon-go-radix
>rpms/golang-github-armon-go-radix 

Re: EPEL-9 terrible updates (dav1d, libavif...)

[Bob Mauchin]

On Thu, 17 Nov 2022, 10:09 Remi Collet,  wrote:

> It looks like EPEL-9 is managed like rawhide.
>
>
> 1/ dav1d 1.0.0 update (also in F37)
>
> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-40bb8ce9c5
>
> This introduce a soname change breaking lot of stuff
> including libavif (from EPEL) and packages in RPMFusion
>
> 2/ libavif 0.11.1 update (only in Rawhide)
>
> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-385df27ee1
>
> This fix the issue with libdav1d, but introduce another soname bump
>
>
> This is a real nightmare.
>
> ** Please, manage EPEL-9 like a "stable" branch. **
>
> soname change should be avoid,
> if not possible (security exception ?) should be properly managed
> and, at least, announced
>
>
> /me is disappointed
>
>
> Remi
>
>
>

Those are my packages but I don't recall authoring such changes? I remember
considering David 1.0.0 for EPEL9 but didn't do so because of the
dependency nightmare.

Best regards,

Robert-André
___
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: SPDX - How to handle MIT and BSD

[Bob Mauchin]

On Tue, Nov 15, 2022, 12:24 Miro Hrončok  wrote:

> On 14. 11. 22 20:53, Miroslav Suchý wrote:
> > 1) You can use https://github.com/spdx/spdx-license-diff and use it to
> identify
> > your license. This is a Chrome and Firefox plugin and allows you to
> select the
> > text; and in the context menu, you can choose to identify the license.
> It will
> > print, e.g., that it matches 60% of the MIT-feh license and highlight
> the
> > difference. Or...
>
> Do we have a command line tool for this? Does licensecheck support SPDX
> identifiers?
>
> (I find the use of browser extension for this very weird. I have the
> LICENSE
> file unpackaged with the sources on my machine, I am not browsing it on
> the web.)
>
> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue



I package askalono-cli which can detect license texts and outputs an SPDX
identifier:  https://github.com/jpeddicord/askalono

We use it in go2rpm.

Best regards,

Robert-André

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

Do we need a change proposal for this?

[Bob Mauchin]

Hello everyone,

So, I and some Go fellows would like to drop i686 from Go supported arches
(not for go itself but the libraries and binaries we build with it).

Since technically Fedora isn't proposing the i686 variant to download
anymore, does it make sense to need a change proposal? No-one would
technically be impacted, except us who wouldn't have to deal with int
overflows.

If possible we'd like to kick this into action before our mass rebuild.

Best regards,

Robert-André
___
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: [HEADS UP] Sphinx 5 and docutils 0.18.1 coming to Rawhide on July 11th

[Bob Mauchin]

On Thu, 30 Jun 2022, 17:35 Karolina Surma,  wrote:

> Hello packagers,
>
> The new major version of the popular documentation framework Sphinx has
> been recently released[0]. It brings many changes, among which there is
> support of docutils 0.18.1. We aim to update both packages together in
> Fedora Rawhide on **July 11th**.
>
> Common issues and mitigation
>
> - `None` is no longer accepted as value of `language` in conf.py
> Solution: Use `language = 'en'` instead.
>
> - Build/ tests fail with: `AttributeError: 'path' object has no
> attribute 'text'`
> Solution: use `path.read_text()` instead
>
>
>
> Full list of known affected packages
>
> eclipseo   python-graphviz python-h2 python-priority


Hello,

If we fix the common issues in Rawhide, will these fixes work on Fedora 36
with older Sphinx/docutils?

Best regards,

Robert-André
___
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: Can we start changing License to SPDX now?

[Bob Mauchin]

On Wed, 29 Jun 2022, 09:48 Zbigniew Jędrzejewski-Szmek, 
wrote:

> On Wed, Jun 29, 2022 at 08:54:37AM +0200, Petr Pisar wrote:
> > > #2799 F38 Change proposal: SPDX License Phase 1
> > > APPROVED (+5,0,-0)
> >
> > Do I understand it correctly that we can change License tags in our spec
> files
> > to SPDX syntax right now?
> >
> > Or should we wait until updating
> >  to SPDX
> > identifiers?
>
> That's my understanding. The plan is to not treat the wiki as the
> authoritative source, but instead to generate a Docs page from a table
> in fedora-license-data.rpm. If the license is listed in
> /usr/share/fedora-license-data/licenses/fedora-licenses.json as
> approved:yes,
> then this should be enough. The plan is to rework the wiki too, but that'll
> likely take more time.
>
> 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 on the list, report it:
> https://pagure.io/fedora-infrastructure


Weren't there a proposal for a macro allowing to use both Spottags and SPDX
so we could merge --ff-only to the old branches? Not being able to do that
is a PITA.

Have a great day everyone!

Robert-André

>
>
___
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: F37 proposal: Golang 1.19 (System-Wide Change proposal)

[Bob Mauchin]

On Sat, 25 Jun 2022, 16:46 Benjamin Beasley, 
wrote:

> I imagine I could answer this myself by looking carefully at the history
> of the golang package, but what happens if you end up doing the mass
> rebuild with a pre-release version? Would you need to do a second mass
> rebuild with the final version between the beta and final freezes?
>
> The Beta Freeze is currently scheduled for 2022-08-23, and Go 1.19 final
> is scheduled for sometime in August, so getting the mass rebuild done with
> the final version before the beta freeze might be tight or it might be just
> fine.
>
The beta mass rebuild allows us to detect problems early and sometimes even
escalading to the Go team for an incorrect behaviour. They are generally
responsive at that stage.

>
>
___
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: debug_package when using go_generate_buildrequires

[Bob Mauchin]

On Mon, 20 Dec 2021, 14:09 Panu Matilainen,  wrote:

> On 12/20/21 01:39, Robert-André Mauchin wrote:
> > On 12/6/21 12:42, Mikel Olasagasti wrote:
> >> Hi all,
> >>
> >> I was updating some golang specs I've and switching them to use
> >> go_generate_buildrequires.
> >>
> >> I realized that some specs that are using it fail to build if `%global
> >> debug_package %{nil}` is not set. Same spec with all BuildRequires
> >> defined works just fine.
> >>
> >> Example:
> >>
> >> - Full spec (go2rpm):
> >>
> https://mikel.olasagasti.info/tmp/fedora/golang-github-alecaivazis-survey-2.spec
> >>
> >> - go_generate_buildrequires spec:
> >>
> https://raw.githubusercontent.com/mikelolasagasti/github-cli/main/golang-github-alecaivazis-survey-2.spec
> >>
> >>
> >> - Full spec build:
> >> https://koji.fedoraproject.org/koji/taskinfo?taskID=79642572
> >> - go_generate_buildrequires build:
> >> https://koji.fedoraproject.org/koji/taskinfo?taskID=79642147
> >>
> >> Is this expected?
> >> Is adding `%global debug_package %{nil}` correct or good practice for
> >> this scenario?
> >>
> >> Kind regards,
> >> Mikel Olasagasti (mikelo2)
> >
> > Hello,
> >
> > Yes this is an issue I have noticed but I don't know where/what causes
> it.
> >
> > I know that if we have a %build section it will cause the debug info to
> > be looked for. It does it too with %generate_buildrequires and I think
> > it shouldn't, but I don't know if this is a behavior triggered by rpm
> > itself or is it triggered somewhere else during the build process?
> >
> > CC Panu and Devel to weigh in.
> >
> > In the meantime, as long as you don't have a %build section and thus do
> > not produce a binaries, you can use %global debug_package %{nil}
>
> Having to disable debug packages practically always indicates a bug in
> the package - either packaging, upstream or both.
>
> Typical causes for "error: Empty %files file
> <...>/debugsourcefiles.list" are missing debug info in the build (eg -g
> flag of gcc) and building outside the designated build directory.
> Unfortunately diagnosing these from rpm isn't easy.
>
> "%global debug_package %{nil}" is always a workaround and never a fix.
>
>  - Panu -
>
> >
> > Best regards,
> >
> > Robert-André
> >


Yes I know, but not in this case as go libraries are noarch.
The problem that when we add the %generate_buildrequires section, it
triggers the detection of the debug info. Without it, the detection of
debug info is skipped so the package builds normally. I don't know what is
the expected behavior.
___
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: The case of LTO when produced enlarged binaries

[Bob Mauchin]

On Mon, Aug 31, 2020, 05:32 Jeff Law  wrote:

> On Sun, 2020-08-30 at 14:42 +0200, Igor Raits wrote:
> > On Sun, 2020-08-30 at 12:37 +0100, Tomasz Kłoczko wrote:
> > > On Fri, 24 Jul 2020 at 21:31, Igor Raits <
> > > ignatenkobr...@fedoraproject.org>
> > > wrote:
> > > [..]
> > >
> > > > Well, I tell what I see :)
> > > >
> > > > Compiling kitty with settings below produces this big
> > > > /usr/lib64/kitty/kitty/fast_data_types.so:
> > > >
> > > > * Without any LTO-related flags: 4.52 MB
> > > > * With -flto: 4.30 MB
> > > > * With -flto -ffat-lto-objects: 4.79 MB
> > > >
> > > > Well, I did not run compilation multiple times but don't think it
> > > > will
> > > > change much.
> > > >
> > >
> > > Comparing the size of the executable files does not make any sense.
> > > You should use the "size" command.
> >
> > Well, I'd use `size` command if I would care what section of a file
> > takes what size. In this case, I don't really care which section it is.
> >
> > All I care is that with -ffat-lto-objects, binary becomes bigger.
> Given this isn't a correctness issue, I haven't prioritized it.
>
> A quick look tells me all the difference is in the symbol table -- ie, the
> code,
> data and bss sections are the same size, but the symbol table is
> significantly
> larger.  And AFAICT it's all debug symbols.
>
> In fact, it doesn't look like the debug info was stripped at all:
>
> [law@localhost kitty]$ objdump -h fast_data_types.so
>
> fast_data_types.so: file format elf64-x86-64
> [ ... ]
>  26 .debug_aranges 01e0      000e2b64
> 2**0
>   CONTENTS, READONLY, DEBUGGING, OCTETS
>  27 .debug_info   000e60c7      000e2d44
> 2**0
>   CONTENTS, READONLY, DEBUGGING, OCTETS
>  28 .debug_abbrev 7543      001c8e0b
> 2**0
>   CONTENTS, READONLY, DEBUGGING, OCTETS
>  29 .debug_line   0007644f      001d034e
> 2**0
>   CONTENTS, READONLY, DEBUGGING, OCTETS
>  30 .debug_str0005cab8      0024679d
> 2**0
>   CONTENTS, READONLY, DEBUGGING, OCTETS
>  31 .debug_loc000d6477      002a3255
> 2**0
>   CONTENTS, READONLY, DEBUGGING, OCTETS
>  32 .debug_ranges 0003a000      003796cc
> 2**0
>   CONTENTS, READONLY, DEBUGGING, OCTETS
>  33 .debug_macro  0002b64f      003b36cc
> 2**0
>   CONTENTS, READONLY, DEBUGGING, OCTETS
>
>
> So someone needs to figure out why debug symbols aren't being stripped.  I
> manually stripped the bits in kitty and after doing so the sizes of the
> resultant
> DSOs are the same (as I'd expect them to be) across the two builds.
>
> jeff
>
Is the file permission 0755? This is often a permission problem I encounter
while reviewing.

>
___
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 me bring AVIF to Fedora

[Bob Mauchin]

On Mon, Jul 20, 2020, 21:59 Andy Mender  wrote:

> On Sun, 19 Jul 2020 at 23:15, Robert-André Mauchin 
> wrote:
>
>> Hello,
>>
>> I'd like some help to review:
>>  - libavif: https://bugzilla.redhat.com/show_bug.cgi?id=1858419
>>
>>  - qt-avif-image-plugin:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1858639
>>
>> I can swap with anything.
>>
>>
> Took libavif. Will give it a spin tomorrow after work :).
>
> ~Andy
>

Thanks a lot Andy!

>
___
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-review broken?

[Bob Mauchin]

On Wed, Aug 28, 2019, 15:12 Richard Shaw  wrote:

> While I'm trying to use it for a review on RPM Fusion I don't think the
> error is related...
>
> Just running fedora-review without any arguments produces this in the log:
>
> Traceback (most recent call last):
>   File "/usr/lib/python3.7/site-packages/FedoraReview/review_helper.py",
> line 236, in run
> self._do_run(outfile)
>   File "/usr/lib/python3.7/site-packages/FedoraReview/review_helper.py",
> line 197, in _do_run
> Settings.init()
>   File "/usr/lib/python3.7/site-packages/FedoraReview/settings.py", line
> 417, in init
> args = parser.parse_args()
>   File "/usr/lib64/python3.7/argparse.py", line 1749, in parse_args
> args, argv = self.parse_known_args(args, namespace)
>   File "/usr/lib64/python3.7/argparse.py", line 1781, in parse_known_args
> namespace, args = self._parse_known_args(args, namespace)
>   File "/usr/lib64/python3.7/argparse.py", line 1987, in _parse_known_args
> start_index = consume_optional(start_index)
>   File "/usr/lib64/python3.7/argparse.py", line 1927, in consume_optional
> take_action(action, args, option_string)
>   File "/usr/lib64/python3.7/argparse.py", line 1855, in take_action
> action(self, namespace, argument_values, option_string)
>   File "/usr/lib64/python3.7/argparse.py", line 1038, in __call__
> parser.exit()
>   File "/usr/lib64/python3.7/argparse.py", line 2488, in exit
> _sys.exit(status)
> SystemExit: 0
>
> When I try to do the review I get:
>
> Traceback (most recent call last):
>   File "/usr/lib/python3.7/site-packages/FedoraReview/review_helper.py",
> line 236, in run
> self._do_run(outfile)
>   File "/usr/lib/python3.7/site-packages/FedoraReview/review_helper.py",
> line 226, in _do_run
> self._do_report(outfile)
>   File "/usr/lib/python3.7/site-packages/FedoraReview/review_helper.py",
> line 99, in _do_report
> self._run_checks(self.bug.spec_file, self.bug.srpm_file, outfile)
>   File "/usr/lib/python3.7/site-packages/FedoraReview/review_helper.py",
> line 117, in _run_checks
> self.checks.run_checks(output=output, writedown=not Settings.no_report)
>   File "/usr/lib/python3.7/site-packages/FedoraReview/checks.py", line
> 382, in run_checks
> run_check(name)
>   File "/usr/lib/python3.7/site-packages/FedoraReview/checks.py", line
> 357, in run_check
> check.run()
>   File
> "/usr/lib/python3.7/site-packages/FedoraReview/plugins/generic_build.py",
> line 203, in run
> Mock.build(self.srpm.filename)
>   File "/usr/lib/python3.7/site-packages/FedoraReview/mock.py", line 457,
> in build
> self.builddir_cleanup()
>   File "/usr/lib/python3.7/site-packages/FedoraReview/mock.py", line 584,
> in builddir_cleanup
> paths = glob(os.path.join(self.get_builddir("BUILD"), "*"))
>   File "/usr/lib/python3.7/site-packages/FedoraReview/mock.py", line 360,
> in get_builddir
> p = self._get_dir(os.path.join("root", self._topdir[1:]))
>   File "/usr/lib/python3.7/site-packages/FedoraReview/mock.py", line 201,
> in _get_dir
> self._get_root()
>   File "/usr/lib/python3.7/site-packages/FedoraReview/mock.py", line 186,
> in _get_root
> config = compile(content[0], path, "exec")
> IndexError: list index out of range
>
> Thanks,
> Richard
> ___
> 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
>

>

What's the mock config file you are using? From the error it seems it's
missing config_opts['root']
___
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: [HEADS UP] Unannounced soname bump of qrencode

[Bob Mauchin]

On Wed, Jun 26, 2019, 00:21 Fabio Valentini  wrote:

> On Tue, Jun 25, 2019 at 11:21 PM Miro Hrončok  wrote:
> >
> > qrencode was bumped from 3.4.4 to 4.0.2.
> >
> > It has a bumped soname from libqrencode.so.3 to libqrencode.so.4.
>
> This might be a good time to remind people that globbing out shared
> libraries like this:
> https://src.fedoraproject.org/rpms/qrencode/blob/master/f/qrencode.spec#_63
>
> is even strongly discouraged by the current Packaging Guidelines:
>
> https://docs.fedoraproject.org/en-US/packaging-guidelines/#_listing_shared_library_files
>
> - to help prevent packagers from accidentally bumping SONAMEs without
> noticing it.
>
> Fabio
>

At least this is enforced for any new package, I make sure of it. But for
existing ones, we can maybe grep .so* to fix them.
___
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: PSA: builds using forge macros with tags broken on rawhide

[Bob Mauchin]

On Wed, 24 Oct 2018, 09:46 Nicolas Mailhot, 
wrote:

> Le mercredi 24 octobre 2018 à 08:42 +0200, Nicolas Mailhot a écrit :
> > Le mercredi 24 octobre 2018 à 00:52 +0200, Robert-André Mauchin a
> > écrit :
> > > On mardi 23 octobre 2018 23:47:05 CEST you wrote:
> > > > On mardi 23 octobre 2018 22:43:16 CEST Nicolas Mailhot wrote:
> > > > > Anyway, since no one answers when I list the possible fixes and
> > > > > ask to
> > > > > choose between them, I fixed the Fedora spec files myself.
> > > > >
> > > > > Feel free to reintroduce %gosetup calls if you really want them,
> > > > > once
> > > > > the %gosetup implementation has been fixed.
> > > >
> > > > Thanks for doing but you messed up the bumping of all the
> > > > %changelog
> > > > entries.
> > >
> > > Used this Fish script to fix my SPEC:
> > >
> >
> > This does not need any fixing, it may not be the changelog format
> > you're
> > used to, but it's one of the changelog styles rpm understands, which
> > is
> > used by packages in Fedora, and which was documented at one point in
> > guidelines (no idea where the corresponding paragraph is today with
> > the
> > doc.fedoraproject changes)
>
> Concretely the
>
> *   
> - version-release
> - changes
>
> format is a tad more flexible and allows publishing several fixes in a
> row without duplicating date lines
>
> *   
> - version-release
> - changes
> - version-release
> -
> changes
>
> and so on
>
> And, our infra does not care if a changelog uses mixed style or not,
> since mass rebuilds will drop changelog entries in a single format in
> all Fedora specs, so you have many mixed style changelogs in the
> distribution today.
>
> (of course it's your specs, you can rewrite changelog entries any way
> that makes you feel better)
>
> Regards,
>
> --
> Nicolas Mailhot
>

I'm talking about dropping the git hash from the release part of the entry.

>
___
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: Orphaned Packages in rawhide (2018-08-27)

[Bob Mauchin]

On Tue, 28 Aug 2018, 00:04 Till Maas,  wrote:

> The following packages are orphaned or depend on an orphaned package
> and will be retired, soon, unless someone adopts them. If you know for
> sure that
> the package should be retired, please do so now with a proper reason:
> https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
>
> Note: If you received this mail directly you (co)maintain one of the
> affected
> packages or a package that depends on one. Please adopt the affected
> package or
> adjust your depending package to avoid broken dependencies, otherwise your
> package will be retired when the affected package gets retired.
>
>   Package(co)maintainers  Status
> Change
> ===
> dnscrypt-proxy comzeradd, eclipseo, orphan5 weeks ago
>

Can someone reassign dnscrypt-proxy to me, eclipseo, I have updated the
project recently and I follow upstream closely. What's the procedure to
adopt it?

Best regards,

Robert-André

>
___
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: Nonresponsive maintainer: Björn Esser (besser82)

[Bob Mauchin]

On Fri, Aug 17, 2018, 12:53 Leigh Scott 
wrote:

> Besser82 hasn't answered  any of my emails for months.
>

I saw him back in May for a couple of reviews, maybe he's in holidays.

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

Re: Introduction/looking for a sponsorship

[Bob Mauchin]

Le 7 août 2017 04:04, "Matthew Miller"  a écrit :


Do the individual source files contain license information? Or is it
otherwise documented? See
https://fedoraproject.org/wiki/Packaging:LicensingGuidelines#License_Text
for guidance on this.


It is absolutely not documented anywhere, that's why I'm trying  to contact
the developer.

https://fedoraproject.org/wiki/Packaging:Conflicts#Binary_Name_Conflicts

Does this package exist in other distros? Doing what they do is usually
a good choice. Most ideally, you convince the upstream to switch to a
compatible name.


I've got the idea for the name from Arch, but Arch packages the Debian
rename under this name. Arch also packages this rename but chose to name it
perl-rename.
It's doubtful upstream would agree on a name change, they're the first
result on CPAN for "rename" and the package has not been touched for years.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Introduction/looking for a sponsorship

[Bob Mauchin]

I intend to package it for Fedora but I have no license file. I have
contacted the developer awhile ago and I'm still waiting for an answer.
It's based on a Larry Wall script under Perl license so there should not be
any issue.
Also I don't know if it's compatible with the guidelines but I renamed the
package: the original binary is named rename but was conflicting with GNU
rename so I patched the source to add a "p" prefix. I remember reading in
the guidelines that prefixing is an option in case of conflict but I'm not
sure it is the approved way.

Best regards,

Robert-André

Le 7 août 2017 01:42, "Ben Rosser"  a écrit :

> On Mon, Jul 31, 2017 at 5:56 AM, Robert-André Mauchin
>  wrote:
> > Hello,
> >
> > My name is Robert-André and I'm looking to become a packager for Fedora.
> [...]
> >
> > So if you like my work so far, please consider sponsoring me for the
> packaging team o/
> >
> > Thank you.
> >
> > Robert-André
> > FAS username: eclipseo
>
> Welcome to Fedora!
>
> This is interesting timing; a few days ago I found myself looking for
> the Perl version of "rename" and installed your copr repository for
> the script (https://copr.fedorainfracloud.org/coprs/eclipseo/prename/).
>
> If you are interested in submitting prename to the review queue in
> addition to your other packages, I would be happy to take the review.
>
> I see you've already been sponsored, which is great!
>
> Ben Rosser
> ___
> 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: Orphaned Packages in rawhide (2017-08-06)

[Bob Mauchin]

python-jira should not depend on python-tlslite as this dependency has been
removed upstream since August of 2016. (
https://github.com/pycontribs/jira/commit/1ab6709ea83f08ee0d2793331baf95c2d8b4fb3b
)

Best regards,

Robert-André

Le 6 août 2017 02:02,  a écrit :

> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know for
> sure
> that the package should be retired, please do so now with a proper reason:
> https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
>
> Note: If you received this mail directly you (co)maintain one of the
> affected
> packages or a package that depends on one. Please adopt the affected
> package or
> retire your depending package to avoid broken dependencies, otherwise your
> package will be retired when the affected package gets retired.
>
>  Package  (co)maintainersStatus Change
> ==
> apvlvorphan  0 weeks ago
> frepple  orphan, jdetaeye, salimma   1 weeks ago
> herbstluftwm orphan, cicku   0 weeks ago
> modem-manager-guiorphan, mariobl 4 weeks ago
> python-tlslite   orphan  0 weeks ago
> rubygem-haml-rails   orphan  2 weeks ago
> xsettingsd   orphan, pcarrier0 weeks ago
>
> The following packages require above mentioned packages:
> Depending on: python-tlslite (1), status change: 2017-08-02 (0 weeks ago)
> python-jira (maintained by: ralph)
> python2-jira-1.0.7-2.fc27.noarch requires python2-tlslite
> = 0.4.9-5.fc27
> python3-jira-1.0.7-2.fc27.noarch requires python3-tlslite
> = 0.4.9-5.fc27
>
> Affected (co)maintainers
> cicku: herbstluftwm
> jdetaeye: frepple
> mariobl: modem-manager-gui
> pcarrier: xsettingsd
> ralph: python-tlslite
> salimma: frepple
>
> Orphans (7): apvlv frepple herbstluftwm modem-manager-gui
> python-tlslite rubygem-haml-rails xsettingsd
>
>
> Orphans (dependend on) (1): python-tlslite
>
>
> Orphans (rawhide) for at least 6 weeks (dependend on) (0):
>
>
> Orphans  (rawhide)(not depended on) (6): apvlv frepple herbstluftwm
> modem-manager-gui rubygem-haml-rails xsettingsd
>
>
> Orphans (rawhide) for at least 6 weeks (not dependend on) (0):
>
>
> Depending packages (rawhide) (1): python-jira
>
>
> Packages depending on packages orphaned (rawhide) for more than 6
> weeks (0):
>
> --
> The script creating this output is run and developed by Fedora
> Release Engineering. Please report issues at its pagure instance:
> https://pagure.io/releng/
> The sources of this script can be found at:
> https://pagure.io/releng/blob/master/f/scripts/find_unblocked_orphans.py
> ___
> 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

Introduction/looking for a sponsor

[Bob Mauchin]

Hello,

My name is Robert-André and I'm looking to become a packager for Fedora.

I'm 33 years-old Frenchman. I first tried GNU/Linux in the late 90
with Debian and what was
then Mandrake. Back then with no Internet, I remember It was tough to
get set up and find
help. After a Windows period, I got back to Linux in 2005 with
Ubuntu's Hoary Hedgehog
release. It was simple, almost everything worked out of the box, and I
could work without
having to « look under the hood » to make it work.

Following what I thought was questionable relations between Ubuntu and
upstreams, and their
choices to reinvent the wheel, i decided look for alternative
distributions. First Debian which
was close to what I've been using, and then Fedora. I had some
reservation about Fedora
because last time I had tried one (Fedora 16, Verne), the package
manager was quite slow
compared to apt-get. And this meant a lot to relearn. But I was
quickly conquered by its simplicity
and its « freshness ». And then dnf came around, it was fast and easy
to use, and I haven't left
Fedora since then.

Thanks to the French fedora-fr wiki which explains step-by-step how to
make your own package,
 I've recently started to package my own things using the COPR service:
https://copr.fedorainfracloud.org/coprs/eclipseo/
And now I'm looking to get them into Fedora. I've learned Fedora
Packaging Guidelines, and how
to use the various tool like rpmbuild, fedpkg, mock, Koji…

Here's a few of the projects I want to include:
 - rclone: https://bugzilla.redhat.com/show_bug.cgi?id=1473314 This Go
app allows you to sync your
files among different Cloud services. I had to unbundled it so it
spawned a dozen of new packages
to build (see the dependencies).
 - qdirstat: https://bugzilla.redhat.com/show_bug.cgi?id=1476201 It's
an app that allow you to track
how your disk space is used, like k4dirstart, but written in Qt5.
 - libva-intel-hydrid-driver
https://bugzilla.redhat.com/show_bug.cgi?id=1475962 This driver
enables
video hardware acceleration for VP9 decoding on Skylake/Kabylake
platforms. (dependency cmrt:
https://bugzilla.redhat.com/show_bug.cgi?id=1475961)

Since I proposed my packages, I've also started to do other reviews:
 - libcbor: https://bugzilla.redhat.com/show_bug.cgi?id=1474694
 - clustersos: https://bugzilla.redhat.com/show_bug.cgi?id=1476438
 - danmaQ: https://bugzilla.redhat.com/show_bug.cgi?id=1471806
 - xfce4-statusnotifier-plugin:
https://bugzilla.redhat.com/show_bug.cgi?id=1476489
 - libsemigroups: https://bugzilla.redhat.com/show_bug.cgi?id=1476085
 - tpm2-abrmd: https://bugzilla.redhat.com/show_bug.cgi?id=1475228

So if you like my work so far, please consider sponsoring me for the
packaging team o/

Thank you.

Robert-André

===
FAS username: eclipseo
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org