Re: Inactive packagers removed from the packager group

2024-05-16 Thread Tim Orling
On Thu, May 16, 2024 at 5:02 PM Kevin Fenzi  wrote:

> Hi all,
>
> Today, 2024-05-16, we have removed inactive packagers
> from the packager group.
>
> This is in accordance with the FESCo policy on inactive packagers:
> https://docs.fedoraproject.org/en-US/fesco/Policy_for_inactive_packagers/


I suspect I am not alone in asking “What is the list of inactive packagers
that this impacted?”

The list of affected packages is helpful; the list of inactive packagers
would have been extra helpful. I suppose it was earlier in the thread?


>
> If the removed user is 'main admin' for a package, this package
> will be orphaned. If there are co-maintainers for the package,
> one of them should take the role of 'main admin',
> by clicking "✋ Take" on
> `https://src.fedoraproject.org/rpms/`".
>
> Otherwise any packager may take the package while it's orphaned.
> After 6 weeks, the package will be retired.
> After another 8 weeks, a new review is needed to unretire it.
> see
> https://docs.fedoraproject.org/en-US/fesco/Policy_for_orphan_and_retired_packages/
> for more details.
>
> Note that removed packagers will currently still appear in packager
> groups on src.fedoraproject.org. We are working on a way to refresh that
> information.
>
> More details available in
> https://pagure.io/fedora-infrastructure/issue/11901
>
> Packages that have been orphaned are:
>
> flatpaks/ardour5
> flatpaks/dosbox
> flatpaks/filezilla
> flatpaks/gnome-books
> flatpaks/gnome-calendar
> flatpaks/gnome-maps
> flatpaks/gnome-music
> flatpaks/gnome-photos
> flatpaks/hydrapaper
> flatpaks/hydrogen
> flatpaks/jumpnbump
> flatpaks/prusa-slicer
> flatpaks/qtractor
> flatpaks/supertux
> flatpaks/xonotic
> modules/fleet-commander
> modules/pg-semver
> rpms/3Depict
> rpms/ansible-collection-community-rabbitmq
> rpms/apache-commons-net
> rpms/balsa
> rpms/BitchX
> rpms/bolt
> rpms/brightnessctl
> rpms/cgdb
> rpms/collectd
> rpms/connect-proxy
> rpms/container-exception-logger
> rpms/cutecw
> rpms/daggy
> rpms/dia-gnomeDIAicons
> rpms/dmidecode
> rpms/dnssec-nodes
> rpms/dnssec-system-tray
> rpms/dnssec-tools
> rpms/feedbackd
> rpms/fleet-commander-admin
> rpms/fleet-commander-client
> rpms/freeipa-desktop-profile
> rpms/gamemode
> rpms/gedit-latex
> rpms/gedit-plugins
> rpms/git-crypt
> rpms/gitg
> rpms/givaro
> rpms/gmrun
> rpms/gnome-shell-extension-gamemode
> rpms/gofer
> rpms/golang-github-client9-gospell
> rpms/golang-github-mitchellh-ps
> rpms/golang-github-remeh-sizedwaitgroup
> rpms/golang-github-xrash-smetrics
> rpms/gtranslator
> rpms/gtypist
> rpms/icewm
> rpms/inih
> rpms/kanotf-fonts
> rpms/koji-osbuild
> rpms/laf-plugin
> rpms/levien-museum-fonts
> rpms/libesmtp
> rpms/libgit2-glib
> rpms/libinjection
> rpms/libitl
> rpms/libvarlink
> rpms/linux-system-roles
> rpms/logserial
> rpms/lookup
> rpms/mathgl
> rpms/mmv
> rpms/mobile-broadband-provider-info
> rpms/mysql-mmm
> rpms/mythes-eo
> rpms/nik4
> rpms/nodejs-sprintf
> rpms/nodejs-strip-json-comments
> rpms/numactl
> rpms/nuntius
> rpms/oc-inject
> rpms/oomd
> rpms/osbuild
> rpms/pcmciautils
> rpms/pdns-recursor
> rpms/perl-Crypt-OpenSSL-AES
> rpms/perl-Crypt-OpenSSL-Bignum
> rpms/perl-Crypt-OpenSSL-DSA
> rpms/perl-Crypt-OpenSSL-PKCS10
> rpms/perl-Crypt-OpenSSL-Random
> rpms/perl-Crypt-OpenSSL-RSA
> rpms/perl-Crypt-OpenSSL-X509
> rpms/perl-Flickr-API
> rpms/perl-Flickr-Upload
> rpms/perl-Getopt-GUI-Long
> rpms/perl-Net-DNS-SEC
> rpms/perl-QWizard
> rpms/pidgin-guifications
> rpms/pisg
> rpms/Pound
> rpms/ppl
> rpms/pure-ftpd
> rpms/python-astor
> rpms/python-boolean.py
> rpms/python-ephyviewer
> rpms/python-fadvise
> rpms/python-flask-cache
> rpms/python-git-changelog
> rpms/python-glue
> rpms/python-glymur
> rpms/python-license-expression
> rpms/python-neatdend
> rpms/python-pooch
> rpms/python-pretend
> rpms/python-pyABF
> rpms/python-pyzabbix
> rpms/python-requre
> rpms/python-rfc3987
> rpms/python-satyr
> rpms/python-suds
> rpms/python-tzlocal
> rpms/python-varlink
> rpms/python-waitress
> rpms/python-whitenoise
> rpms/python-zbase32
> rpms/ren
> rpms/reportd
> rpms/reuse
> rpms/rubygem-daemons
> rpms/rust-xkbcommon
> rpms/sat4j
> rpms/satyr
> rpms/secvarctl
> rpms/shybrid
> rpms/spice-html5
> rpms/springlobby
> rpms/squeekboard
> rpms/ssmtp
> rpms/statsd
> rpms/sugar-colordeducto
> rpms/sugar-story
> rpms/sugar-xoeditor
> rpms/tcpxtract
> rpms/termy-server
> rpms/will-crash
> rpms/wofi
> rpms/wp-cli
> rpms/xarchiver
> rpms/xfburn
> rpms/xmlcopyeditor
> rpms/yank
> --
> ___
> devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
> To unsubscribe send an email to
> devel-announce-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:
> 

perl-Unix-Statgrab license correction

2023-03-12 Thread Tim Orling
perl-Unix-Statgrab-0.112-18.fc39 will correct the license from
(LGPL-2.1-or-later) to
(LGPL-2.1-or-later AND (GPL-1.0-or-later OR Artistic-1.0-Perl))

https://rt.cpan.org/Ticket/Display.html?id=125519
___
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: Self Introduction: Dorinda Bassey

2022-01-18 Thread Tim Orling
On Tue, Jan 18, 2022 at 4:49 AM Felipe Borges  wrote:

> On Tue, Jan 18, 2022 at 1:21 PM Dorinda Bassey  wrote:
> >
> > Hi Everyone,
> >
> > My name is Dorinda and I am an Associate software Engineer at Red Hat,
> > I'm passionate about software development, contributing to the growth of
> communities and I have
> > some experience contributing to FOSS projects.
> > I am interested in becoming a package maintainer.
> > I learnt how to create RPM packages and build with mock and copr,
> > My plan so far is to maintain gpuvis and gpu-trace packages(yet to
> submit).
> > I'm also open to maintaining some more in the future.
>
> Welcome to the Fedora Project!
>

Nice to see a “new” familiar face. Welcome, Dorinda.

>
> >
> > Thanks,
> >
> > Dorinda.
> >
> > ___
> > 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
>
___
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


Retired perl-File-Find-Rule-Age

2021-08-04 Thread Tim Orling
This package has not seen any attention upstream for 7 years and keeps
having random FTBFS due to the tests. As nothing depends on this and I no
longer need it in my own workflow, let us send it out to pasture.

https://bugzilla.redhat.com/show_bug.cgi?id=1399506
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Retired perl-File-Find-Rule-Age

2021-08-04 Thread Tim Orling
This package has not seen any attention upstream for 7 years and keeps
having random FTBFS due to the tests. As nothing depends on this and I no
longer need it in my own workflow, let us send it out to pasture.

https://bugzilla.redhat.com/show_bug.cgi?id=1399506
___
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


[EPEL-devel] Re: fop for epel 8

2020-04-01 Thread Tim Orling
 <https://bugzilla.redhat.com/show_bug.cgi?id=1819818>

On Wed, Apr 1, 2020 at 6:21 AM Troy Dawson  wrote:

> Packages in the EPEL-8 repository are volunteered by Fedora packagers
> via requests by interested users.
> If a package you are looking for is not there, please look at
> https://bugzilla.redhat.com and see if a request has been opened for
> your package to be built in EPEL-8.
> If it hasn't please open a new ticket.
> Some packages may not be able to built in EPEL-8 due to missing deps
> which need to be added.
> ---
> That is the official way to get packages into EPEL 8.
> Looks like the owner has already started work on it, but it's still
> good to get a bugzilla if there isn't one.  I tend to prioritize what
> packages I do based on if they have a bugzilla or not.
>
> To be clear, I am a Fedora packager and have supported multiple packages
in epel-6. So my first inclination was not to file a bug for someone else
to do the work. But agreed that the process should be followed.

https://bugzilla.redhat.com/show_bug.cgi?id=1819818


> On Tue, Mar 31, 2020 at 9:41 PM Tim Orling  wrote:
> >
> > Naively cloning f30 branch and performing a local build:
> >
> > ant is available as module
> >
> > No match for apache-commons, avalon-framework, batik, fontbox,
> javapackages-local, junit, qdox, servlet, xmlgraphics-commons, xmlunit
> >
> > I guess there's some work to do...
> > ___
> > epel-devel mailing list -- epel-de...@lists.fedoraproject.org
> > To unsubscribe send an email to epel-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/epel-de...@lists.fedoraproject.org
> ___
> epel-devel mailing list -- epel-de...@lists.fedoraproject.org
> To unsubscribe send an email to epel-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/epel-de...@lists.fedoraproject.org
>
___
epel-devel mailing list -- epel-de...@lists.fedoraproject.org
To unsubscribe send an email to epel-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/epel-de...@lists.fedoraproject.org


[EPEL-devel] Re: fop for epel 8

2020-03-31 Thread Tim Orling
Naively cloning f30 branch and performing a local build:

ant is available as module

No match for apache-commons, avalon-framework, batik, fontbox, 
javapackages-local, junit, qdox, servlet, xmlgraphics-commons, xmlunit

I guess there's some work to do...
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org


[EPEL-devel] fop for epel 8

2020-03-31 Thread Tim Orling
I'd like to package fop for epel-8, but not sure how to do that (haven't
done epel in the new era). There are epel8 and epel8-playground branches
but they look like incomplete modularity support.

Is normal rpm packaging for fop a fool's errand for epel8?

Can one of the admins add me as a contributor so I can package rpm/module
for epel8?

Regards,
Tim
fas: ttorling
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org


Re: Creation of a perl-packagers-sig group

2020-03-13 Thread Tim Orling
On Fri, Mar 13, 2020 at 4:39 PM Emmanuel Seyman  wrote:

> * Emmanuel Seyman [12/03/2020 21:03] :
> >
> > perl-sig is a pseudo-user, not a group and it is next to impossible to
> convert
> > a pseudo-user into a group.
>
> Typing that sentence out made me wonder why we have so few notifications
> going
> to the list these days. Today, I decided to look at the perl-sig account
> and
> realized that it watches just 33 packages instead of the 2400+ packages it
> was
> watching at one point or the 3000+ packages it should be watching right
> now.
>
> Once I calm down, I will open a ticket to get this fixed.
>

Ugh. That is disheartening.
Thank you for checking!


> Emmanuel
> ___
> perl-devel mailing list -- perl-devel@lists.fedoraproject.org
> To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
>
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org


[EPEL-devel] Re: EPEL: Python 3.4 will be EOL in March 2019

2018-08-24 Thread Tim Orling
On Fri, Aug 24, 2018 at 3:04 PM Kevin Fenzi  wrote:

> On 08/21/2018 11:06 AM, Miro Hrončok wrote:
> >>
> >> I'd start untangling the deps and getting the following in:
> >>
> >>   * six (looking at that one now)
> >
> > https://src.fedoraproject.org/rpms/python3-six/pull-request/1


Merged.

> 
> >
> >>   * pytest
> >>   * Cython
> >>   * PyYAML
> >>   * pip
> >>   * attrs
> >>   * requests
> >>   * mock
>
> Yeah, I'd love to see us move this forward and get everything on 3.6...
>
> Unfortunately I don't have a lot of time, but I can review/merge PR's
> and do builds and such.
>
> Perhaps we could setup a wiki page or someplace to coordinate?
>
> kevin
>
>
> ___
> epel-devel mailing list -- epel-devel@lists.fedoraproject.org
> To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org/message/5SQ7QYAI4QPGREKY7ZM2MJP5BEMYUIKN/
>
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org/message/IGFFM7T7IT773RBZWUPOS2YQJVGKQHEA/


Re: [atomic-devel] Starting a Container SIG

2018-07-25 Thread Tim Orling
On Wed, Jul 25, 2018 at 2:42 PM Dusty Mabe  wrote:

>
>
> On 07/25/2018 01:09 PM, Clement Verna wrote:
> >
> > Please Reply if you're interested with helping out making the
> > Container story great in Fedora. If there is a good response, I will
> > create a Container SIG wiki page, and I guess we can ask for
> > container-devel mailing list for SIG discussions.
>
> Unfortunately I can't sign up to do a bunch of work but I would like to
> join
> and help represent Fedora CoreOS and related interests in the SIG.
>

Also not sure how much I can sign up for, but I have a significant amount
of container development and usage on Fedora at work and play.

FAS:ttorling

>
> Dusty
> ___
> 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/QPTYH5DDCPYUCUCBZGGNOATXYHO5O2HG/
>
___
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/OJDLS772CXLGX6VK2X3C7VPVUJKFXLB6/


Re: Your package doesn't build with Python 3.7

2018-07-07 Thread Tim Orling
https://kojipkgs.fedoraproject.org/repos/rawhide/latest/x86_64/

See:
https://copr.fedorainfracloud.org/coprs/ttorling/pystatgrab/

(I didn’t try to build any other architectures on copr)
On Sat, Jul 7, 2018 at 10:06 AM Sergio  wrote:

> What you add to rawhide repos ? We still haven't composes of rawhide with
> python 3.7 . Please and thanks
>
> Sent from my Android
> Em 06/07/2018 9:55 da tarde, Tim Orling  escreveu:
>
> Fixed pystatgrab.
> python3.7 on copr worked fine for me, with your suggestion of adding the
> rawhide repo
>
> On Mon, Jul 2, 2018 at 12:38 AM, Miro Hrončok  wrote:
>
> On 2.7.2018 02:54, Sérgio Basto wrote:
>
> On Mon, 2018-07-02 at 01:37 +0200, Miro Hrončok wrote:
>
> On 2.7.2018 01:20, Sérgio Basto wrote:
>
> Hmm I was under the impression that PyString_AsString does not
> exist
> in Python3
> and you'll have to use PyUnicode_AsEncodedString. Was it actually
> compiling with
> previous versions of Python3?
>
>
> I was testing disable python2 [1], to see what happen but copr
> rawhide
> still have python 3.6 !
> How I enable python-3.7 on copr ?
>
>
> You can add a repo in copr settings:
>
> https://kojipkgs.fedoraproject.org/repos/f29-python/938830/$basearch
>
>
> Unfortunately failed [1]
>
> Thanks
>
> [1]
> https://copr.fedorainfracloud.org/coprs/sergiomb/opencv/build/772874/
> https://copr-be.cloud.fedoraproject.org/results/sergiomb/opencv/fedora-
> rawhide-x86_64/00772874-opencv/root.log
>
> DEBUG util.py:489:  BUILDSTDERR: Error:
> DEBUG util.py:489:  BUILDSTDERR:  Problem: package
> gdb-headless-8.1.50.20180629-26.fc29.x86_64 requires 
> libpython3.6m.so.1.0()(64bit),
> but none of the providers can be installed
> DEBUG util.py:489:  BUILDSTDERR:   - cannot install both
> python3-libs-3.7.0-1.fc29.x86_64 and python3-libs-3.6.5-4.fc29.x86_64
> DEBUG util.py:489:  BUILDSTDERR:   - cannot install both
> python3-libs-3.6.5-4.fc29.x86_64 and python3-libs-3.7.0-1.fc29.x86_64
> DEBUG util.py:489:  BUILDSTDERR:   - cannot install the best update
> candidate for package python3-libs-3.6.5-4.fc29.x86_64
> DEBUG util.py:489:  BUILDSTDERR:   - cannot install the best update
> candidate for package gdb-headless-8.1.50.20180629-26.fc29.x86_64
> DEBUG util.py:491:  (try to add '--allowerasing' to command line to
> replace conflicting packages or '--skip-broken' to skip uninstallable
> packages)
>
>
> In that case, sorry, no idea how to use 3.7 in copr. I've asked releng to
> merge the side tag today anyway. https://pagure.io/releng/issue/7564
>
> --
> 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://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/DMWCEHQIOTWJ2MXWY2T4YFBHUT263CFS/
>
>
>
___
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/ZZPTR2V4OCON7ECCVQC3Y7TRPRSO4N6B/


Re: Your package doesn't build with Python 3.7

2018-07-06 Thread Tim Orling
Fixed pystatgrab.
python3.7 on copr worked fine for me, with your suggestion of adding the
rawhide repo

On Mon, Jul 2, 2018 at 12:38 AM, Miro Hrončok  wrote:

> On 2.7.2018 02:54, Sérgio Basto wrote:
>
>> On Mon, 2018-07-02 at 01:37 +0200, Miro Hrončok wrote:
>>
>>> On 2.7.2018 01:20, Sérgio Basto wrote:
>>>
 Hmm I was under the impression that PyString_AsString does not
> exist
> in Python3
> and you'll have to use PyUnicode_AsEncodedString. Was it actually
> compiling with
> previous versions of Python3?
>

 I was testing disable python2 [1], to see what happen but copr
 rawhide
 still have python 3.6 !
 How I enable python-3.7 on copr ?

>>>
>>> You can add a repo in copr settings:
>>>
>>> https://kojipkgs.fedoraproject.org/repos/f29-python/938830/$basearch
>>>
>>
>> Unfortunately failed [1]
>>
>> Thanks
>>
>> [1]
>> https://copr.fedorainfracloud.org/coprs/sergiomb/opencv/build/772874/
>> https://copr-be.cloud.fedoraproject.org/results/sergiomb/opencv/fedora-
>> rawhide-x86_64/00772874-opencv/root.log
>>
>> DEBUG util.py:489:  BUILDSTDERR: Error:
>> DEBUG util.py:489:  BUILDSTDERR:  Problem: package
>> gdb-headless-8.1.50.20180629-26.fc29.x86_64 requires
>> libpython3.6m.so.1.0()(64bit), but none of the providers can be installed
>> DEBUG util.py:489:  BUILDSTDERR:   - cannot install both
>> python3-libs-3.7.0-1.fc29.x86_64 and python3-libs-3.6.5-4.fc29.x86_64
>> DEBUG util.py:489:  BUILDSTDERR:   - cannot install both
>> python3-libs-3.6.5-4.fc29.x86_64 and python3-libs-3.7.0-1.fc29.x86_64
>> DEBUG util.py:489:  BUILDSTDERR:   - cannot install the best update
>> candidate for package python3-libs-3.6.5-4.fc29.x86_64
>> DEBUG util.py:489:  BUILDSTDERR:   - cannot install the best update
>> candidate for package gdb-headless-8.1.50.20180629-26.fc29.x86_64
>> DEBUG util.py:491:  (try to add '--allowerasing' to command line to
>> replace conflicting packages or '--skip-broken' to skip uninstallable
>> packages)
>>
>
> In that case, sorry, no idea how to use 3.7 in copr. I've asked releng to
> merge the side tag today anyway. https://pagure.io/releng/issue/7564
>
> --
> 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://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.or
> g/archives/list/devel@lists.fedoraproject.org/message/DMWCEH
> QIOTWJ2MXWY2T4YFBHUT263CFS/
>
___
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/7FJYG34EPA5GRZUSDJNEOWZL7UYM5WAG/


Re: Your package requires Python 3.6, rebuild it!

2018-07-06 Thread Tim Orling
Fixed pystatgrab

On Thu, Jul 5, 2018 at 4:10 AM, Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:

> On Wed, Jul 04, 2018 at 09:58:15PM +0200, Miro Hrončok wrote:
> > On 4.7.2018 21:51, Sérgio Basto wrote:
> > >since 2018-07-02 14:28 [1] we don't have compose this mean build root
> > >on copr aren't update , and we can't test it
> >
> > Try adding
> > http://kojipkgs.fedoraproject.org/repos/rawhide/latest/x86_64/ as a
> > repo to copr. there should be no more problems like iwth the
> > f29-python side tag, where packages had newer versions in rawhide
> > still depending on 3.6.
>
> Alternatively, build in mock:
> $ fedpkg srpm && mock --enablerepo=local whatever.src.pm
>
> (Repo 'local' pulls directly from koji.)
>
> Zbyszek
> ___
> 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/DXWIO4CIKCKXT2PREKXWCOKDZIWXH4T7/
>
___
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/EV6US2EGVJEAK77BKRXX3LQYCJOOYZFL/


Re: [ACTION NEEDED] Missing BuildRequires: gcc/gcc-c++

2018-03-06 Thread Tim Orling
On Tue, Mar 6, 2018 at 7:08 AM, Jan Rybar  wrote:

> done: procps-ng, psmisc, psacct
>
>
> On 02/18/2018 06:09 PM, Igor Gnatenko wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> Over this weekend I've performed scratch-mass-rebuild without having gcc
>> and
>> gcc-c++ in buildroot of all Fedora packages, many of which failed due to
>> random
>> reasons and I grepped all logs for some common errors found by analyzing
>> hundreds of build logs.
>>
>> Guidelines: https://fedoraproject.org/wiki/Packaging:C_and_C%2B%2B#Build
>> Require
>> s_and_Requies
>>
>> The grep output is located here:
>> https://ignatenkobrain.fedorapeople.org/gcc-removal.txt
>>
>> Some packages might be missed due to short koji outage, broken
>> dependencies and
>> so on, but majority of real failures is below.
>>
>> If you fixed package(s), found false positive, found missing packages in
>> list
>> or anything else -- please let me know.
>>
>> Note to packages which use CMake buildsystem. When you have project(xxx)
>> in
>> CMakeLists.txt it checks both for C and CXX compilers. So you might
>> encounter
>> packages where you have BuildRequires: gcc and it fails on CXX compiler
>> (even
>> you think you don't need it). Solution for this is to send patch to
>> upstream
>> switching to something like project(xxx C), or if problem is opposite to
>> project(xxx CXX).
>>
>> List of packages and respective maintainers:
>> https://ignatenkobrain.fedorapeople.org/gcc-removal-pkgs.txt
>>
>>
Forgot to email the list, but I took care of bwm-ng (which was FTBFS as
well) and pystatgrab. For the others next to my name I am not a primary or
even secondary maintainer, so I am a little bit hesitant to make the
changes.

I do wonder if libstatgrab needs the fix or the fact that it depends on
autotools has already indirectly taken care of it such that it is not on
your list? Happy to add it if needed/wanted/desired.

FAS: ttorling

- -- - -Igor Gnatenko
>> -BEGIN PGP SIGNATURE-
>>
>> iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAlqJs1QACgkQaVcUvRu8
>> X0xxkRAAj56QZYSxzDXiMyvM9eLdVS0Qrt9jiNa66rasIbDVciTym7WQoV2CXxM+
>> ZxaOCYU8eyxOhE1rx36KITJ7SgU6ugLu2dVZlG/QR8vH3RTqJPV/GWhM/WUAgaon
>> f/SPwTIMk31qvEuKwlqLgNH1rwpRH2NfWVelZChwi1zXOglMvIHakV7sSedYy2i9
>> bmVvf/1ylj/NbaI6FaLUqg81UQhUulD8RYeZi1cyxSpit/4aysP7ixCb4MLizmwH
>> uNUO0y//xxL0hMSShmfTlsPXowU+NpkzV+lFQ/k2X4KcCZWMabfCt69TdyTbYlj5
>> ai8oFGNI94Tv6rrzR/Rirfl/eODtdaaeNqyg/MBze6hYpS2w2oezOEmdYvlpJ7Xo
>> z0fN/vIus1SeeyIKWo4KYHZYRX6g2nTCUeGYJqvCIRVxS9UJsy45C/HlnIWTtedn
>> Dyp9O/0aSDhY+ErPQi64+HloZrY7p+KsCzPNc9HdzLbhnfM5IUn2TmO+qHngBSlY
>> zGNfpOsBmmllSuBftWDfiayh8C9sBUpGT9693iyQYXPIwjZkQSHAclDZa7naN3Oy
>> NKQaqVOsDmgDDP9xVOyr/Aue3jQk/8QHraM5DgO05L6lXHwdm+rjIdbb7CU2rFF7
>> Gl14+kSFP7yufRQiS6Gt96eN4ePxSuD7XjiT/9GicztDXypNeX8=
>> =KRiO
>> -END PGP SIGNATURE-
>> ___
>> devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
>> To unsubscribe send an email to devel-announce-le...@lists.fed
>> oraproject.org
>> ___
>> 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
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org


[EPEL-devel] Re: Updating pytest in EPEL6

2016-12-05 Thread Tim Orling
I am in favor of the update.

On Mon, Dec 5, 2016 at 2:23 PM, Orion Poplawski  wrote:

> Does anyone have any opinions about updating pytest to 2.4.2 in EPEL6?
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1400254
>
> --
> Orion Poplawski
> Technical Manager 303-415-9701 x222
> NWRA, Boulder/CoRA Office FAX: 303-415-9702
> 3380 Mitchell Lane   or...@nwra.com
> Boulder, CO 80301   http://www.nwra.com
> ___
> epel-devel mailing list -- epel-devel@lists.fedoraproject.org
> To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
>
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org


[EPEL-devel] python34 in testing for EPEL6

2016-10-21 Thread Tim Orling
I came across a need for python34 in CentOS 6.8 and decided to go ahead and 
package it for EL6 (SCLs were already available). I have also packaged a number 
of other python3 modules, which are also in testing. If you are interested, 
please take a moment to review:

https://bodhi.fedoraproject.org/users/ttorling

Any testing and karma is much appreciated.

--Tim (Intel)

P.S. A big Thank You to orionp for the original python34 patch and for 
answering many questions during the process.
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org


Re: dotnet on Fedora

2016-10-14 Thread Tim Orling
FYI,

I'm quite involved with upstream IronPython [0] and plan to eventually
package IronPython [1] (and ironpython3 [2] when it is ready) for Fedora.
Also, come join us if you are interested [3].

Cheers.
Tim "moto-timo"
FAS: ttorling

[0]: http://ironpython.net
[1]:
https://github.com/IronLanguages/main/tree/ipy-2.7-maint/Languages/IronPython
[2]: https://github.com/IronLanguages/ironpython3
[3]: https://gitter.im/IronLanguages/main


On Fri, Oct 14, 2016 at 11:08 AM, Radka Janekova 
wrote:

> Yes and no, it will evolve... there will be info about dotnet itself which
> has nothing to do witht he sig... a bit too exhausted to explain today (im
> after surgery that went wrong) but you can leave questions or suggestions
> here or catch me on irc tomorrow.
>
>
>
>
> Best regards,
> Radka
>
> --
> *Radka Janeková*
> *radka.ja...@redhat.com *
>
>
> On Fri, Oct 14, 2016 at 7:27 PM, Miro Hrončok  wrote:
>
>> On 14.10.2016 18:50, Radka Janekova wrote:
>>
>>> Hello there,
>>>
>>> I'd like to introduce new SIG to you, i'm RHs dotnet person and when i
>>> noticed that Fedora lacks any dotnet presence I felt like I need to
>>> change that =)
>>>
>>> Feel free to join up, team up, discuss C# stuffs and eventually I hope
>>> that we can get into crafting reliable packages!
>>>
>>> Wiki: https://fedoraproject.org/wiki/DotNet
>>> 
>>>
>>
>> Shouldn't that be https://fedoraproject.org/wiki/SIGs/DotNet ?
>>
>> List: https://lists.fedoraproject.org/admin/lists/dotnet-sig.lists
>>> .fedoraproject.org
>>> >> s.fedoraproject.org>
>>> IRC: #fedora-dotnet
>>>
>>> Taking it slowly though, please don't expect miracles yet :]
>>>
>>> Best regards,
>>> Radka
>>>
>>> 
>>> *Radka Janeková*
>>> *radka.ja...@redhat.com *
>>>
>>>
>>>
>>> ___
>>> devel mailing list -- devel@lists.fedoraproject.org
>>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>>>
>>>
>> --
>> 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
>>
>
>
> ___
> 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: [POC-change] Fedora packages point of contact updates

2016-10-14 Thread Tim Orling
Looking at the upstream [0], it says "An obsolete library. Don't use it in
new projects."


So we should probably decide what to do with it. I would be willing to pick
it up, but since it won't see any new development according to upstream, we
should "do the right thing".

[0]: https://github.com/algernon/libmongo-client

On Fri, Oct 14, 2016 at 12:26 PM, Till Maas  wrote:

> On Mon, Oct 03, 2016 at 10:00:09AM +, nob...@fedoraproject.org wrote:
> > Change in package status over the last 168 hours
> > 
>
> > libmongo-client [f23, master, epel7, f24] was orphaned by kevin
> >  Alternative C driver for MongoDB
> >  https://admin.fedoraproject.org/pkgdb/package/libmongo-client
>
> 3306 packages depend on this via rsyslog (and perl) or syslog-ng. Are
> there plans to drop support for mongodb in the logging daemons or is
> there someone willing to adopt libmongo-client?
>
> Kind regards
> Till
> ___
> 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: Python SIG on-boarding issue

2016-09-13 Thread Tim Orling
On Tue, Sep 13, 2016 at 10:36 AM, Miro Hrončok  wrote:

> On 13.9.2016 19:27, Dhanesh Bhalchandra Sabane wrote:
>
>> Aloha Python-SIG!
>> I was wondering whether it is a good time to make the new pages official.
>> Also, I would like to know whether the idea of splitting the SIG into two
>> FAS groups is acceptable so that we can start taking necessary actions.
>>
> Yes and yes.


+1

>
> CommOps is currently working on the Python SIG On-Boarding ticket [1] and
>>> one of the tasks
>>> we have identified is re-writing the Python SIG wiki page to make it more
>>> beginner-friendly. I was assigned with this particular task which is now
>>> complete [2] [3].
>>>  We received some feedback from mhroncok today during the CommOps
>>> meeting and following
>>> points were discussed:
>>>
>>> 1. Splitting Python SIG in two FAS groups:
>>> 1.1 *python-sig* for newcomers and interested members who hang out and
>>> help with Python on
>>> Fedora
>>> 1.2 *python-packagers* for proven members of the community / packagers
>>> who will also
>>> receive security-related bugs. Promising members from *python-sig* group
>>> can be promoted
>>> to *python-packagers* given that they have contributed to the package's
>>> git.
>>>
>>>
This will make the intent much clearer :)
___
python-devel mailing list
python-devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/python-devel@lists.fedoraproject.org


Re: [Python-SIG] Self-Introduction: Tim Orling

2016-07-14 Thread Tim Orling
Hi Petr,

It is precisely the security information that I am seeking access to. My
job depends on it.

I have already done everything in [0]. In some cases more than once. And we
are talking over the period of many months. So let me ask this in return:
what is the process once someone has done everything in [0]? The only place
that I can have any dialog is this mailing list or #fedora-python.
Application to the FAS group is a one time, one way thing. Application to
the python-sig mailing list is a one way thing. A human on the other end
must make some action to move the process forward.

Out of frustration, I emailed tomspur recently, as he is listed as the main
contact for python-sig group in FAS. Other than a response from him, I have
not heard anything else. I can understand that it is summer and people have
holidays and it has not been that long yet.

But I must reiterate that this process has been going on for months from my
side. Fedora already has a problem of perception of being too Red Hat
insider in some circles. My observation has been that Red Hat employees
have been gently reminded on #fedora-python that they need to apply to
python-sig. I am assuming they have been successful. Meanwhile, I wait for
action on the part of a member of python-sig.

That action could be as simple as, "we don't know you, could you please
submit a python package for review so we can start to get to know you?".
But that still requires action on the part of a member of python-sig.

I can tell you that the response from the perl-sig community was much more
inviting.

Cheers.

--Tim (Intel Open Source Technology Center)

On Thu, Jul 14, 2016 at 4:44 AM, Petr Viktorin <pvikt...@redhat.com> wrote:

> Hello Tim! Welcome to python-devel, and sorry for us being so quiet.
>
> Is there anything in particular you're pinging about?
>
> If want to access the python-sig FAS group, note that an introduction here
> is just a part of the process [0]. However, that list is mostly used to get
> notifications about bugs in various Python packages (so it might not be for
> you), and it gets security-related information (so not everyone who applies
> is accepted, but I don't know the details there). For general discussions
> there is this list, so you can already participate.
>
>
> [0] https://fedoraproject.org/wiki/SIGs/Python#Python_SIG_FAS_group
>
> On 07/11/2016 10:41 PM, Tim Orling wrote:
>
>> Ping. Again.
>>
>> On Thu, May 12, 2016 at 9:32 PM, Tim Orling <ticot...@gmail.com
>> <mailto:ticot...@gmail.com>> wrote:
>>
>> Ping.
>>
>> On Fri, Apr 29, 2016 at 6:56 AM, Tim Orling <ticot...@gmail.com
>> <mailto:ticot...@gmail.com>> wrote:
>>
>> Greetings,
>>
>> I recently became a co-maintainer for pystatgrab [1] and am a
>> contributor to upstream [2]. I am a co-founder and co-maintainer
>> of the meta-python [3] and meta-maker [4] layers for
>> OpenEmbedded. I am also a contributor to IronPython [5] and
>> RobotFramework [6].
>>
>> In my professional life, I work for the Intel Open Technology
>> Center on the Yocto Project, which depends heavily on Python for
>> its tools and infrastructure.
>>
>> [1]
>> https://admin.fedoraproject.org/pkgdb/package/rpms/pystatgrab/
>> [2] https://github.com/i-scream/pystatgrab/graphs/contributors
>> [3]
>> https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/
>> [4]
>> https://layers.openembedded.org/layerindex/branch/master/layer/meta-maker/
>> [5] https://github.com/orgs/IronLanguages/people
>> [6]
>> https://github.com/robotframework/robotframework/graphs/contributors
>>
>
>
>
> --
> Petr Viktorin
>
>
___
python-devel mailing list
python-devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/python-devel@lists.fedoraproject.org


Re: Injecting perl-devel and perl-generators build-requires

2016-06-23 Thread Tim Orling
Thank you for doing all this work, Petr. I, for one, really appreciate it.
I hope others feel the same (whether or not they agree with the Built Root
change itself).


Cheers.

--Tim

On Thu, Jun 23, 2016 at 6:09 AM, Petr Pisar  wrote:

> Hello,
>
> per Build Root Without Perl Fedora 25 change
> , I'm
> ready to
> implement the most visible part of this change.
>
> I'm going to inject perl-devel and perl-generators build-requires into
> Fedora
> specification files tomorrow. That's necessary not to break building the
> packages when Perl will have been removed from the build root.
>
> There are 3292 packages that should build-require perl-generators,
> there are 491 packages that should build-require perl-devel.
> Some of them already contain the dependency.
> There are 3129 packages that miss one of them and they will be edited.
>
> The edit will consist of one commit with this commit message:
>
> Mandatory Perl build-requires added <
> https://fedoraproject.org/wiki/Changes/Build_Root_Without_Perl>
>
> The commit will add:
>
> BuildRequires: perl-devel
>
> or
> BuildRequires: perl-generators
>
> or both into a spec file. There will be no revision bump, no RPM changelog
> entry, no rebuild in the Koji.
>
> I expect pulling the source repositories, commiting the changes and pushing
> them back to the dist-git will take at least 2 hours. Package maintainers
> and
> people with watch-commit role will receive an e-mail notification about the
> commit as usually.
>
> Thank you for your understanding.
>
> -- Petr
>
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
>
>
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org


Re: Schedule for Friday's FESCo Meeting (2016-04-15)

2016-04-15 Thread Tim Orling


> On Apr 14, 2016, at 4:16 PM, Kevin Fenzi  wrote:
> 
> Following is the list of topics that will be discussed in the FESCo
> meeting Friday at 17:00UTC in #fedora-meeting on irc.freenode.net.
> 
> To convert UTC to your local time, take a look at
>  http://fedoraproject.org/wiki/UTCHowto
> 
> or run:
>  date -d '2016-04-15 17:00 UTC'
> 
> Links to all tickets below can be found at: 
> https://fedorahosted.org/fesco/report/9
> 
> = Followups =
> 
> #topic #1444 Updates deliverables
> .fesco 1444
> https://fedorahosted.org/fesco/ticket/1444
> 
> = New business =
> 
> #topic #1556 Review of release blocking deliverables for F24
> .fesco 1556
> https://fedorahosted.org/fesco/ticket/1556
You of course meant:
https://fedorahosted.org/fesco/ticket/1566

> 
> #topic #1567 Change process - proposal of two new milestones
> .fesco 1567
> https://fedorahosted.org/fesco/ticket/1567
> 
> = Open Floor = 
> 
> For more complete details, please visit each individual ticket.  The
> report of the agenda items can be found at
> https://fedorahosted.org/fesco/report/9
> 
> If you would like to add something to this agenda, you can reply to
> this e-mail, file a new ticket at https://fedorahosted.org/fesco,
> e-mail me directly, or bring it up at the end of the meeting, during
> the open floor topic. Note that added topics may be deferred until
> the following meeting.
> --
> devel mailing list
> devel@lists.fedoraproject.org
> http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org


Re: Removing perl from build root

2016-03-31 Thread Tim Orling
+1

Since I care about embedded and containers, having a smaller minimal build
root is high on my list.

As a perl module maintainer, I don't mind adding a few lines to my spec
files to achieve this. Especially since you are updating the guidelines to
provide clear guidance.


--Tim (Intel)

On Thu, Mar 31, 2016 at 6:43 AM, Paul Howarth  wrote:

> On 31/03/16 14:10, Petr Pisar wrote:
>
>> Fedora's minimal build root contains perl. There is a reasonable request
>>  to
>> remove the perl in order to minimize the build root. (The x86_64 F25 build
>> root occupies 527 MB now, 20 MB of that are perl packages.)
>>
>> The reason why perl is there is the rpm-build package. The Requires
>> dependency
>> tree looks like:
>>
>> rpm-build
>>  perl-generators
>>  perl(:MODULE_COMPAT_5.22.1)
>>  perl(Fedora::VSP)
>>  perl
>>  perl-macros
>>  system-rpm-config   (a Provide)
>>  redhat-rpm-config
>>  perl-srpm-macros
>>
>> While perl-srpm-macros's presence is intended, perl-generators' presence
>> is
>> unwanted.
>>
>> On technical level, the reason is the rpm-build binary package requires
>> perl-generators explicitely. It's there for backward compatibility. Simply
>> removing the dependency removes perl from minimal build root.
>>
>> But the compatibility is important. Without perl-generators in a build
>> root no
>> Perl dependencies are generated into binary packages. To fix it, every
>> Perl
>> package must build-require perl-generators.
>>
>
> Might it not be easier to use the newly-allowed boolean dependencies, e.g.
> in rpm-build something like this:
>
> Requires: (perl-generators if perl-libs)
>
> Paul.
> --
> Fedora Extras Perl SIG
> http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
> perl-devel mailing list
> perl-devel@lists.fedoraproject.org
>
> http://lists.fedoraproject.org/admin/lists/perl-devel@lists.fedoraproject.org
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/perl-devel@lists.fedoraproject.org

pystatgrab: license change GPLv2+ -> LGPLv2+

2016-03-26 Thread Tim Orling
Heads up that v0.6 coming to Rawhide has a license change from GPLv2+ to
LGPLv2+.

See
https://github.com/i-scream/pystatgrab/commit/c88af8cd35712e4fec035637f4c8314b27eec3d4

Regards,

--Tim Orling (Intel)
FAS: ttorling
irc: moto-timo
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org


Re: A big package giveaway

2016-03-10 Thread Tim Orling
On Thu, Mar 10, 2016 at 2:18 AM, Petr Šabata  wrote:

> On Tue, Mar 08, 2016 at 12:43:50PM +0100, Petr Šabata wrote:
> > Dear Perl hackers,
> >
> > due to a shift in my work responsibilities, I'm giving away a
> > large number of my packages.  If you're interested in any of
> > them, let me know and I'll pass them to you.  See the list at
> > the end of this mail.
> >
> > I'm going to orphan what's left & post to devel@ on Friday.
> >
> > Thank you,
> > Petr
>
> Updated again.
>

I hope the "shift" is good and welcome one for you Petr!

As these are both directly related to my other packages and my end use, I
am happy to take them.


> perl-Log-Any -- Bringing loggers and listeners together ( master f24 f23
> f22 epel7 el6 el5 )
>


> 
>


> perl-Unix-Statgrab -- Perl extension for collecting information about the
> machine ( master f24 f23 f22 el6 el5 )
>


> 
>
> P
>

I'll take a deeper look at the list over the weekend, just in case.

Regards,

--Tim ( FAS ttorling )
aka moto-timo on IRC
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/perl-devel@lists.fedoraproject.org

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

2016-02-19 Thread Tim Orling
I am also interested in maintaining or co-maintaining:
rpms/bitbake -- Build tool executing tasks and managing metadata (
master f23 f22 )

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


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

2016-02-19 Thread Tim Orling
I have an interest in either taking over or co-maintaining:
rpms/bwm-ng -- Bandwidth Monitor NG ( master f23 f22 epel7 el6 )
rpms/libstatgrab -- A library that provides cross platform access to
statistics of the system ( master f23 f22 epel7 el6 )

I'll have to digest the rest of the list to see if there are more.

Regards,
Tim
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org


koji task vs. build

2015-07-17 Thread Tim Orling
I would like to build a package on koji to make available for a bodhi
override, but -- since I am not yet sponsored -- I suspect that I do not
have the proper permissions?

All my koji builds seem to be tasks...

Otherwise, I am missing something in the syntax and have not found the
right example/documentation.

Regards,

ttorling
-- 
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: Introduction, Seeking Sponsor

2015-04-28 Thread Tim Orling
On Mon, Apr 27, 2015 at 7:27 AM, Petr Šabata con...@redhat.com wrote:

 On Thu, Apr 02, 2015 at 08:09:07PM -0700, Tim Orling wrote:
  Hello perl-devel,
 
  I have been an active user since Redhat 6.
 
  I am currently co-maintainer of meta-python layer for OpenEmbedded and
  frequent contributor to the meta-perl layer.
 
  I have built many RPMs in the past, but this will be my first entrance
 into
  the world of contributors.
 
  In an effort to use https://github.com/rehsack/Packager-Utils I find
 that I
  need additional perl modules in Fedora. My builds of perl-MooX-Log-Any
 and
  perl-Alien-Packages (generated by cpanspec) pass on koji. (user:
 ttorling)
 
  Please consider sponsoring me as a collaborator/packager and member of
 the
  group.
 
  --Tim

 Hey Tim,

 apologies for the late reply; I somehow missed this email.

 It's great news you'd like to contribute.  Go ahead and submit
 your packages for review [0].  I'll gladly help you polish the
 rough bits and possibly sponsor you.

 While still a useful tool, packages generated by cpanspec are
 far from perfect and still need some attention.  To get an
 idea what a modern perl package looks like, browse the git
 repositories or check out some recent perl package reviews.

 Anyway, do submit your packages and we'll see how it goes :)

 Cheers,
 Petr

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

 --
 Fedora Extras Perl SIG
 http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
 perl-devel mailing list
 perl-devel@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/perl-devel


Petr,

Thank you for responding. Work is currently being a four letter word, so I
am quite busy. In the coming weeks I will submit my packages per the
guidelines.

I assume I should be targeting F23.

Regards,

Tim
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel

Introduction, Seeking Sponsor

2015-04-02 Thread Tim Orling
Hello perl-devel,

I have been an active user since Redhat 6.

I am currently co-maintainer of meta-python layer for OpenEmbedded and
frequent contributor to the meta-perl layer.

I have built many RPMs in the past, but this will be my first entrance into
the world of contributors.

In an effort to use https://github.com/rehsack/Packager-Utils I find that I
need additional perl modules in Fedora. My builds of perl-MooX-Log-Any and
perl-Alien-Packages (generated by cpanspec) pass on koji. (user: ttorling)

Please consider sponsoring me as a collaborator/packager and member of the
group.

--Tim
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel