python3-porting-vfad
LOGS
14:30:05 <potty> #startmeeting
14:30:06 <zodbot> Meeting started Sat Nov 14 14:30:05 2015 UTC.  The chair is potty. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:30:06 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:30:10 <mstuchli> rodrigc: Yup, that's the idea
14:30:19 <mstuchli> threebean: I guess we may as well :)
14:30:26 <potty> #topic Python 3 Porting FAD
14:30:40 <potty> Welcome pythonistas!
14:30:40 <mstuchli> So createrepo_c will need a python3 subpackage
14:30:41 <rodrigc> do you guys know about this web site: https://caniusepython3.com/
14:31:11 <frafra> mstuchli: ok! thank you ;)
14:31:50 <patxi> A site to help you transition to Py3,not bad.
14:32:09 <rodrigc> :q
14:32:12 <MSK61> Hello everyone.
14:32:24 <mstuchli> MSK61: Hey there :)
14:32:39 <MSK61> I have good knowledge about python 2(but none about python 3), and I'd like to contribute to the porting efforts.
14:33:03 <potty> Welcome MSK61
14:33:25 <mstuchli> MSK61: Have you seen http://synfo.github.io/2015/10/14/Python3-Porting-Database/ ?
14:33:43 <MSK61> I've checked tagia https://tree.taiga.io/project/synfo-fedora-python-3-porting/kanban but it looks empty for me.
14:33:47 <rodrigc> This lists packages not yet Python3: https://python3wos.appspot.com/
14:34:00 <potty> mstuchli: what time is it over there?
14:34:06 <mstuchli> 15:34 :)
14:34:21 <potty> rodrigc: use the portingdb app please
14:34:26 <Ivoz> AFAIK pyinvoke is considered by maintainer as worthy successor to Fabric for python 3, at least for local scripting
14:34:29 <dperson> Hello, I'm mainly a sys admin, but have done some small scripts in python, is there a shallow end to pick a package / script from?
14:34:35 <mstuchli> The pycon sprint will start tomorrow ~10am
14:35:15 <mstuchli> MSK61: Yes, the taiga won't be used in the end, sorry for the confusion :)
14:35:16 <rodrigc> potty: I cloned it from github, I can't figure out which yaml file to update
14:35:23 <mstuchli> dperson: Take a look at http://synfo.github.io/2015/10/14/Python3-Porting-Database/
14:35:32 <mstuchli> dperson: And see if you can pick something from the portingdb :)
14:35:40 <mstuchli> rodrigc: What do you need to do again?
14:36:03 <dperson> @mstuchli thank you
14:36:04 <patxi> Using git huh.
14:36:35 <mstuchli> patxi: yup
14:36:55 <rodrigc> mstuchli: update info about python fabric and m2crypto
14:37:59 <rodrigc> ]% python3 -m portingdb --datadir data/ load
14:37:59 <rodrigc> Traceback (most recent call last):
14:37:59 <rodrigc> File "/usr/local/lib/python3.5/runpy.py", line 170, in _run_module_as_main
14:37:59 <rodrigc> "__main__", mod_spec)
14:37:59 <rodrigc> File "/usr/local/lib/python3.5/runpy.py", line 85, in _run_code
14:37:59 <rodrigc> exec(code, run_globals)
14:37:59 <rodrigc> File "/usr/home/rodrigc/portingdb/portingdb/__main__.py", line 3, in <module>
14:38:00 <Ivoz> bitprophet *might* reconsider updating fabric for python 3 these days, since paramiko is now 3+ comp., but moreso he wants to let it die in favour of newer stuff (e.g his own `invoke`, or things like ansible)
14:38:00 <rodrigc> main()
14:38:00 <rodrigc> File "/usr/home/rodrigc/portingdb/portingdb/cli.py", line 17, in main
14:38:01 <rodrigc> return cli(obj={})
14:38:01 <rodrigc> File "/usr/home/rodrigc/astrenv/lib/python3.5/site-packages/click/core.py", line 700, in __call__
14:38:02 <rodrigc> return self.main(*args, **kwargs)
14:38:02 <rodrigc> File "/usr/home/rodrigc/astrenv/lib/python3.5/site-packages/click/core.py", line 655, in main
14:38:03 <rodrigc> raise RuntimeError('Click will abort further execution '
14:38:08 <frafra> wow, please use fpaste :)
14:38:17 <rodrigc> Ivoz: no, he refused
14:38:27 <Ivoz> rodrigc, recently? :)
14:38:31 <rodrigc> Ivoz: https://github.com/fabric/fabric/issues/1378
14:38:51 <mstuchli> rodrigc: Does this help? https://github.com/fedora-python/portingdb/pull/18
14:39:11 <Ivoz> oh hmm, maybe I'm behind times on that
14:39:30 <rodrigc> Ivoz: he has been claiming to be working on a rewrite of Fabric for the past 2 years which will be Python 3, but the code is nowhere in sight
14:39:53 <rodrigc> mstuchli: Can you help me with the error I got?
14:40:04 <rodrigc> how do I configure the encoding?
14:40:33 <mstuchli> rodrigc: I don't think I go the entire thing, could you put it on pastebin
14:40:56 <Ivoz> rodrigc, I thought pyinvoke was supported to be like 3/5ths of the rewrite... but I hadn't heard of his idea for actual "Fabric 2.0" before, just that he wanted to transition it off to other stuff
14:41:25 <rodrigc> Ivoz: it's all vaporware
14:41:36 <Ivoz> pyinvoke isn't
14:41:45 <Ivoz> works fine
14:41:57 <Ivoz> pip uses it now
14:42:26 <patxi> Just learned how to create my user wiki page in fedora now...got my head spinning trying to figure that out when I wanted to be a translator.
14:44:05 <rodrigc> Ivoz: the pyinvoke web page says it is pre-1.0 and subject to change
14:44:22 <rodrigc> Ivoz: meanwhile, I have tons of scripts that use Fabric, and many other people do to as well
14:44:39 <rkuska> Anyone is having problem with python-click?
14:44:41 <Ivoz> I've been following invoke, it's getting very close to stable now
14:45:01 <rodrigc> mstuchli: http://pastebin.com/B4fJhQZz
14:45:08 <michel_slm> should we try and keep the yaml files in the portingdb git sorted?
14:45:31 <rodrigc> Ivoz: well that's nice, but if people are using Fabric now, and are asking for a Python 3 version, and someone even ported it
14:45:45 <rodrigc> Ivoz: it's annoying that upstream is rejecting the port
14:46:06 <rkuska> rodrigc: try define LANG=en_GB.utf8 LC_ALL=en_GB.utf8
14:46:37 <rodrigc> rhuska: can I use a US locale?
14:47:18 <rkuska> rodrigc: sure
14:47:54 <rkuska> rodrigc: just make sure it is in correct format, because when python3 fails to recognize the correct encode format it fall back to ASCII as encoding
14:48:07 <rodrigc> rkuska: I tried this: env LANG=en_US.utf8 LC_ALL=en_US.utf8 python3 -m portingdb --datadir data/ load
14:48:13 <rodrigc> rkuska: and that failed
14:49:26 <rodrigc> env LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 python3 -m portingdb --datadir data/ load
14:49:28 <rodrigc> that worked
14:49:34 <rodrigc> ok, now I am getting a different error
14:49:50 <rodrigc> ImportError: No module named 'pysqlite2'
14:50:10 <rkuska> rodrigc: so install pysqlite2 now :-)
14:50:15 <potty> Missing dependencies
14:50:35 <rodrigc> that needs to go in requirements.txt, I am installing everything in a virtualenv
14:50:49 <potty> Yup rodrigc
14:51:28 <rodrigc> there is no pysqlite2 package
14:52:05 <rodrigc> ok I tried to pip install pysqlite
14:52:07 <rodrigc> and got this:
14:52:08 <rodrigc> Complete output from command python setup.py egg_info:
14:52:08 <rodrigc> pysqlite is not supported on Python 3. When using Python 3, use the sqlite3 module from the standard library.
14:52:18 <rodrigc> WTF
14:52:59 <mstuchli> rodrigc: Could you post the entire ImportError exception? I don't think portingdb requires pysqlite2
14:55:19 <rodrigc> mstuchli: http://pastebin.com/ygwVzKck
14:59:15 <rodrigc> can I skip running this application?  I'm wasting time on it, and want to focus my time on actually porting code to Python 3
15:00:10 <mstuchli> rodrigc: Running it is definitely not necessary
15:00:20 <mstuchli> rodrigc: But I *think* that's a system problem, not portingdb
15:00:23 <mstuchli> What distro do you use?
15:00:41 <rodrigc> I'm running my FreeBSD laptop, running Python 3.5
15:00:50 <rodrigc> I installed everything in a virtualenv via pip
15:02:07 <patxi> i'm off my mum gets mad after i'm more than 20 mins on the laptop!
15:02:29 <rodrigc> oh if I remember, I think in FreeBSD ports, they don't compile sqlite into the default Python by default
15:02:32 <patxi> GL porting all of that, huge step for the py devs.
15:02:39 <mstuchli> patxi: Hah, tell her you're doing good work! ;)
15:02:43 <fale> hi :) I've read on the Magazine that today there is a FAD to port py2 packages to py3 at 8pm... but there is no indication of the TimeZone
15:02:56 <rodrigc> and the way that SQLAlchemy works is, if it doesn't find sqlite3 module, it tries to load pysqlite2
15:03:07 <mstuchli> fale: It's ongoing! :)
15:03:17 <frafra> hi fale ;)
15:03:22 <fale> frafra: hi :)
15:03:32 <mstuchli> fale: Take a look at http://synfo.github.io/2015/10/14/Python3-Porting-Database/
15:03:39 <fale> mstuchli: awesome :) thanks
15:04:53 <potty> fale no matter timezone. The FAD is all saturday and sunday
15:05:20 <fale> potty: the Magazine indication is wrong, then ;)
15:05:38 <potty> It is ok
15:05:40 <potty> Welcome
15:05:46 <patxi> mstuchli:If only you knew my age you would lol so hard. I don't know what she thinks a job in software engineering and It actually is.
15:06:40 <fale> any suggestion on a package to start with?
15:07:15 <patxi> fale: scroll up someone posted the list of the packages
15:07:51 <fale> patxi: the list is pretty long, I've seen... I just pick one randmly?
15:08:23 <patxi> fale: yeah download the source code and start working
15:10:18 <fale> patxi: thanks :)
15:20:23 <fujimotos> Is there any order to the list in "data/upstream.yaml"? Currently, the list just seems unordered.
15:21:05 <frafra> fujimotos: I think you can just append your text
15:21:48 <fujimotos> frafra: Ok, I'll do that. thanks.
15:22:57 <frafra> yw
15:26:12 <Grahhhh> Good morning all.
15:27:01 <MSK61> Do I have to be on the latest fedora 23? I'm currently on fedora 22.
15:27:32 <frafra> MSK61: I don't think it's necessary
15:27:38 <Grahhhh> michel_slm: In the portingdb code, there's a data/fedora-update.yaml file.  You can add notes like upstream being against it there.
15:28:06 <Grahhhh> michel_slm: If there's an alternative, you can make the status blocked and put an alternative to port dependent packages to.
15:28:56 <michel_slm> Grahhhh: thanks. marking it in upstream.yaml per some discussion in portingdb's github
15:29:12 <threebean> mstuchli: want to add the portingdb app github activity to fedmsg?  https://apps.fedoraproject.org/github2fedmsg/
15:29:46 <mayorga> Hi folks! I'm Eduardo Mayorga from Nicaragua. I am a Fedora packager and sponsor. I'm looking forward to give a helping hand in the Porting to Python 3 FAD.
15:29:54 <rodrigc> does Fedora use a lot of Python for it's own scripts?  I remember stuff like anaconda
15:30:28 <threebean> rodrigc: sure does.  all over the place.
15:30:40 <mstuchli> threebean: That would be super cool. Not sure how we'd use it right now tho
15:30:55 <rodrigc> threebean: are all those internal scripts python3 in fedora23?
15:31:20 <mstuchli> mayorga: Hey there! :) Please read http://synfo.github.io/2015/10/14/Python3-Porting-Database/ and let us know if you have any questions :)
15:31:42 <threebean> mstuchli: that github2fedmsg webapp should be self-service to turn it on (but you need admin rights on the github repo)
15:31:52 <michaeleekk> pyliblzma, why not set to dropped? I saw the status suggesting to use stdlib or python-backports-lzma
15:31:53 <threebean> mstuchli: we could graph activity afterwards for a nice blog post :p
15:32:14 <threebean> michaeleekk: sounds like a good idea.  can you set it to dropped?
15:32:24 <michaeleekk> no prob ;)
15:32:27 <threebean> ty!
15:33:23 <mstuchli> threebean: Huh, that's an idea! I'll look into doing that
15:33:32 <Grahhhh> MSK61: Yes you can -- if you want to do some programming, you'll probably need to learn some python3.  If you're just interested in helping out, we also want to figure out what upstreams currently support python3 where our packages' do not (so that packagers know where they can simply update to a new version of upstream).  And if you know rpm packagin, you can update to those new upstream versions and create python3 versions of the packages.
15:33:47 <mstuchli> threebean: You have a link or somthing I can follow to enable it?
15:34:09 <threebean> https://apps.fedoraproject.org/github2fedmsg/
15:34:11 <threebean> mstuchli: ^^
15:35:24 <mstuchli> threebean: Aww, shoot, do I really need to give the app access to all my org's repos?
15:35:46 <threebean> :/ I think it only needs read and webhook access.
15:35:57 <threebean> but you can control which ones are enabled.  it doesn't turn them all on by default.
15:36:26 <mstuchli> I have some private code I can't share, I'll try to figure out how to disable it
15:36:37 * threebean nods
15:37:06 <potty> threebean: got that in mind
15:38:39 <mstuchli> threebean: Could you do it yourself, if I set you as an admin?
15:39:05 <potty> mayorga: hola
15:39:59 <mayorga> potty: We have fitoria in #fedora-ni, but he is still unable to join this channel.
15:41:12 <echevemaster> Hi everyone, just to inform I'm attending to the FAD of today, I'm willing to help in any package that be needed
15:42:06 <rodrigc> mstuchli: OK, I fixed the sqlite3 problem on my side and got portingdb to run
15:42:13 <mstuchli> rodrigc: Cool :)
15:42:40 <mstuchli> echevemaster: Hey there :) Please read http://synfo.github.io/2015/10/14/Python3-Porting-Database/ and let us know if you have any questions
15:42:52 <fitoria> o/
15:43:02 <tomspur> OT: Do you know of arm ressources to test/debug a current scipy failure?
15:43:12 <rodrigc> ok according to portingdb it lists m2crypto as dropped
15:43:47 <echevemaster> got it mstuchli
15:44:01 <rodrigc> how are you getting the information about packages which are done?
15:44:33 <rodrigc> there are other web apps which poll information about Python 3 packages directly from PyPI
15:44:55 <fitoria> I’m in now :)
15:44:58 <fitoria> where can I start?
15:46:04 <rodrigc> fitoria: Hey there :) Please read http://synfo.github.io/2015/10/14/Python3-Porting-Database/ and let us know if you have any
15:46:04 <rodrigc> +questions
15:46:14 <fitoria> go ti
15:46:16 <fitoria> it*
15:47:44 <potty> Bienvenidos! fitoria mayorga echevemaster
15:49:01 <abadger1999> rodrigc: The done status is when the package in the fedora developmet branch (what we call rawhide) has a python3 subpackage
15:49:24 <abadger1999> rodrigc: (with some checks that the python3 subpackage doesn't depend on python2 due to packaging errors)
15:49:46 <tonet666p> hi guys
15:49:50 <rodrigc> abadger1999: so it is not enough to have the package in PyPI?
15:50:02 <abadger1999> rodrigc: The app currently doesn't tie into any other services to get upstream status -- any information about that is being done manually as people notice things like that.
15:50:03 <tonet666p> i'm near to my home
15:50:08 <abadger1999> rodrigc: correct.
15:50:26 <rodrigc> abadger1999: well that's probably OK for now
15:50:30 <abadger1999> rodrigc: But if it is ported to python3 and available on pypi we want to know that/do something about that as well.
15:51:09 <abadger1999> rodrigc: some people here are more fedora packagers than python developers and creating the fedora package is something they can do if upstream has already ported the code.
15:52:00 <rodrigc> abadger1999: well maybe the portingdb can have another state
15:52:09 <potty> Hey abadger1999 sup!
15:52:20 <rodrigc> abadger1999: "available" or "ported upstream"
15:53:01 <abadger1999> Speaking of.. if anyone here wants to work on packaging rather than python coding, let me know.  I can point you at a list of packages that probably just need a little bit of spec file fixing.
15:53:42 <rodrigc> abadger1999: https://caniusepython3.com/ and https://python3wos.appspot.com/ poll the info about Python 3 readiness from PyPI
15:53:47 <abadger1999> mstuchli: ^ rodrigc has a feature request.  Not sure if we have something like that already?
15:53:59 <abadger1999> (or something that could be expanded to that)
15:54:10 <tonet666p> .fas tonet666p
15:54:10 <zodbot> tonet666p: tonet666p 'Tonet Pascualet Jallo Colquehuanca' <tonet666p@gmail.com>
15:54:21 <abadger1999> potty: buenos dias!
15:54:55 <tonet666p> hola a todos | hi to everyone
15:55:40 <mstuchli> abadger1999: Hmmm, I wonder how they figure out if a project supports Python 3 or not
15:56:35 <abadger1999> IIRC, at least the appspot one that rodrigc linked to has open source code -- I believe it scans the metadata at pypi to determine it.
15:57:34 <mstuchli> abadger1999: That's not very reliable though
15:57:54 <abadger1999> <nod>  Probably more false negatives than false positives though.
15:58:12 <rodrigc> why does portingdb have a README *and* a README.md file?
15:58:18 <mstuchli> Perhaps, I'll talk to encukou about adding that feature
15:58:31 <abadger1999> So it would be helpful for getting an initial list of upstream packages that packagers just need to update.
15:59:36 <abadger1999> threebean: We are porting createrepo to python3, correct?
15:59:50 * abadger1999 will look at breaking the pyliblzma dependency if so.
15:59:51 <mstuchli> I would note that if someone wants to take a look into doing that as part of the FAD most def go ahead, it looks interesting :)
16:00:05 <mstuchli> abadger1999: createrepo_c, right, not createrepo
16:00:14 <potty> Yes
16:00:49 <abadger1999> mstuchli: Hmm. okay,  I have avoided delving into the C extenstion world so far.
16:03:35 <rodrigc> so in fedora23, are all the internal fedora scripts which use python now python3 scripts?
16:03:44 <abadger1999> rodrigc: nope, not yet.
16:03:47 <mstuchli> abadger1999: I'm just going by what threebean said, I think createrepo is... deprecated, in this sense
16:03:53 <abadger1999> mstuchli: k.
16:04:08 <rodrigc> so what did fedora23 do with respect to python3?
16:04:11 <abadger1999> I'll look for some other low hanging fruit for now.
16:04:36 <abadger1999> rodrigc: we got python2 off of the workstation install (the most popular version of Fedora)
16:05:02 <rodrigc> but how could you do that if the fedora python scripts are not python3?
16:05:13 <abadger1999> rodrigc: which means that the packages that went into a default install of workstation are all python3 now.
16:05:33 <abadger1999> rodrigc: Maybe I'm misunderstanding "internal" -- I take that to mean things that are used to build the distro.
16:05:43 <potty> abadger1999 +1
16:05:47 <rodrigc> well building the distro is one
16:06:07 <abadger1999> rodrigc: There are still a lot of python2 scripts and applications in that set.
16:06:17 <rodrigc> but I was referring more to python scripts which are part of a base fedora distribution
16:06:30 <rodrigc> such as the installer, or any management tools
16:06:33 <abadger1999> rodrigc: ah -- yes, those should be ported to python3 at this point.
16:06:40 <rodrigc> ok
16:06:47 <rodrigc> that's a huge milestone
16:06:55 <abadger1999> rodrigc: One thing that I'd love to see is the Fedora Server install also being completely python3.
16:07:16 <abadger1999> So that might be one thing to take a look at where the dependencies lead.
16:07:25 <rodrigc> yes, when Fedora Server is python3 that will be a bigger one
16:07:33 <abadger1999> sgallagh: If you're around this weekend, I wonder if you know those off the top of your head.
16:07:41 <rodrigc> Fedora is considered the more "serious" distro
16:08:20 <mstuchli> abadger1999: Samba, FreeIPA, those are too big for this FAD thought, and they are being worked on separately
16:08:22 <abadger1999> sgallagh: Or know of a list of the packages in Server that we can query.
16:08:27 <abadger1999> <nod>
16:08:51 <potty> mstuchli: perhaps in another FAD?
16:09:51 <potty> With people knowing the work flow of this FAD, next related FADs would be easier to manage
16:10:50 <abadger1999> potty: maybe... they'll both need participation from the upstreams of those projects.
16:10:50 <mstuchli> abadger1999: https://gist.github.com/sYnfo/fede3641ce603ca59b33 these should be the problematic on server
16:11:02 <mstuchli> abadger1999: Exactly, those are some pretty big fish
16:11:08 <abadger1999> potty: freeipa we'll need to know what they plan on replcing python-paste with.
16:11:21 <abadger1999> (since last I heard isn't pporting to python3)
16:11:30 <mstuchli> If someone is interested in XFCE, take a loot at exo
16:11:37 <mstuchli> We don;t think it should depend on Python 2
16:12:08 <potty> abadger1999: i see
16:12:32 <abadger1999> samba it looks like upstream is working on it but I suppose we could help out if they're stalled somewhere.
16:12:42 <abadger1999> mstuchli: thanks for the list!
16:14:50 <mstuchli> I gotta go for now, have fun!
16:14:57 <abadger1999> are we pushing updates to spec files to add python3 subpackages and building in rawhide or just opening bugzillas for hte maintainers?
16:14:59 <rodrigc> >I filed this issue against portingdb: https://github.com/fedora-python/portingdb/issues/23 Need to report if Python package has Python3 version available in PyPI
16:15:17 <abadger1999> rodrigc: okay.  Thanks!
16:16:20 <abadger1999> threebean: Should we mark the turboGears stack as dropped?  TurboGears2 stack is okay, upstream though?  (If so, I don't know which packages are common to both)
16:16:57 <echevemaster> I think we should push updates in rawhide abadger1999,
16:17:10 <abadger1999> echevemaster: okay.
16:18:03 <rodrigc> sorry to keep talking about portingdb
16:18:18 <rodrigc> but a comment at the top of each yaml file would be helpful
16:19:37 <rodrigc> which one do I modify to indicate I am working on m2crypto?
16:19:42 <rodrigc> fedora-update.yaml?
16:20:33 <abadger1999> <nod>  Probably should file a bug for that too -- the portingdb author isn't here presently so we're not necessarily the best ones to fix it.
16:20:45 <rodrigc> lol
16:20:45 <abadger1999> mstuchli: ^ Question about where to mark that one of us is working on porting.
16:22:25 <rodrigc> abadger1999: https://github.com/fedora-python/portingdb/issues/25
16:23:16 <fitoria> I’m going to start working on boom
16:23:23 <rodrigc> I'm going to take a guess and say that fedora-update.yaml is for dealing with fedora packaging
16:23:42 <fitoria> Should I mark it on upstream.yaml?
16:23:42 <rodrigc> and upstream.yaml is for the upstream code on PyPI
16:23:48 <fitoria> great
16:23:51 <fitoria> going for it
16:24:10 <rodrigc> but don't take anything I say about portingdb as true, I am just guessing
16:24:22 <fitoria> lol
16:25:03 <rodrigc> fedora-update.yaml is alphabetically sorted
16:25:06 <rodrigc> upstream.yaml is not
16:25:09 <rodrigc> ??
16:25:14 <condor> Good morning good folk ... I brought the Starbucks!
16:26:13 <abadger1999> rodrigc: If you'd like to correct that, I will merge your pull request.
16:26:26 <rodrigc> lol, ok
16:26:44 <abadger1999> I think (except for he json file which is updated via a script) they should all be alphabetized.
16:27:43 <fitoria> I’ve created this PR https://github.com/fedora-python/portingdb/pull/26
16:28:15 <potty> lol condor
16:28:52 <rodrigc> did anyone answer my question about why portingdb has a README *and* README.md file?
16:29:04 <abadger1999> fitoria: Cool.  I'll get to merging it shortly :-)
16:30:15 <abadger1999> rodrigc: One's a symlink -- my guess is encukou wrote a README and then noticed that github would format it if it was named with .md as a file extension.
16:30:31 <abadger1999> rodrigc: don't know if he has a reason for keeping the un-suffixed file around.
16:31:17 <rodrigc> abadger1999: Oops, didn't notice it was a symlink!!
16:31:50 <condor> lol potty
16:31:52 <abadger1999> :-)
16:38:24 <frafra> ok, I'm slowly understanding how it works :)
16:38:45 <frafra> that's a good way to learn many things about packaging
16:40:21 <potty> This event helps in many ways
16:40:31 <frafra> I agree
16:40:37 <abadger1999> tomspur: I'm looking at python-daemon for the python3 porting FAD -- upstream claims support for python3 in the new 2.0.6 version.
16:40:52 <barracks510> I develop an upstream program with bindings in python2 using swig. What's the best way to add a python3 binding?
16:41:03 <abadger1999> tomspur: Do you want me to open a bug report with my changes to the spec file or just push it to rawhide and you'll look at it there?
16:41:27 <abadger1999> barracks510: I'm not intimately familiar with swig but I know that it supports building python3 bindings as well.
16:42:28 <barracks510> abadger1999: Would that be preferable over a setup.py modification?
16:43:00 <condor> ok, I'm logged into github, and following along.  Just watching and learning stuff.
16:43:10 <mayorga> I have an eye on https://titanpad.com/S3r8qX7OQJ. Please update it so packagers can find packages to work on.
16:43:11 <abadger1999> barracks510: http://www.swig.org/Doc1.3/Python.html#Python_python3support
16:44:49 <rodrigc> abadger1999: https://github.com/fedora-python/portingdb/pull/27
16:46:04 <abadger1999> rodrigc: Cool.  Would you be willing to update (there's merge conflicts)  I promise I won't merge any other pull requests until you do so.
16:46:22 <rodrigc> abadger1999: ok wait
16:46:23 <potty> mayorga is right. Update the Etherpad indicating what are you currently working
16:46:36 <potty> So we avoid double efforts
16:47:48 <tomspur> abadger1999: Feel free to build it in rawhide
16:48:01 <abadger1999> tomspur: Cool.  Thanks!
16:48:56 <tomspur> abadger1999: Do you know of arm resources for packager? I try to track down a scipy bug currently...
16:49:11 <tomspur> I cannot connect to https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers
16:50:21 <iamgregb> Hi , I am porting a small package right now as a test....if that works out..how do I start making it official?
16:50:39 <abadger1999> tomspur: I don't -- I know peter robinson and dgilmore were spearheading the overall effort... since the arm test machines are hosted by infrastructure, might be that anyone in #fedora-admin can help get them back up and running.
16:50:49 <rodrigc> abadger1999: don't modify this file, I am 10 commits behind
16:50:56 <abadger1999> rodrigc: k :-)
16:50:56 <rodrigc> abadger1999: let me catch up
16:51:15 <tomspur> abadger1999: thanks
16:51:59 <abadger1999> iamgregb: We'll need to push the changes to upstream.
16:52:25 <tonet666p> wich is the list of packages for migrate to python 3?
16:53:04 <abadger1999> iamgregb: We could either track the progress of your patch getting merged upstream in the portingdb app or bugzilla (or both).... mstuchli, threebean, what do you think about iamgregb's question?
16:53:19 <abadger1999> tonet666p: the portingdb app has the overall picture for fedora.
16:53:21 <tomspur> abadger1999: Hmm... I think there was an old issue with python-daemon and (iirc!) minimock and one version of the one doesn't work with the other...
16:53:44 <abadger1999> tonet666p: http://portingdb-encukou.rhcloud.com/
16:53:45 <tomspur> So I don't know if python-daemon with this version can be used with python3. Maybe kushal knows more about that....
16:53:59 <tonet666p> ty abadger1999
16:54:04 <abadger1999> tomspur: k.  I'm doing a scratch build now to see.
16:54:09 <iamgregb> abadger1999: Doest upstream refer to where the package originates from or...
16:54:41 <abadger1999> tonet666p: If you're interested in packaging rather than porting of upstream code, I have a smaller list of packages that need help in that area too.
16:54:55 <abadger1999> iamgregb: yes.
16:55:09 <tonet666p> abadger1999, send me that list please
16:55:39 <abadger1999> iamgregb: So most of hte time we try not to diverge too much from upstream in the fedora packages.   So what we want is to port code, submit it to the upstream author/project, have them merge it, and then pull the new version in the next fedora package.
16:55:56 <abadger1999> iamgregb: that way we don't have to maintain our own patchset for forever.
16:56:19 <iamgregb> sounds reasonable
16:56:28 <abadger1999> tonet666p: https://github.com/fedora-python/portingdb/issues/9#issuecomment-153654009  there's a list of packages in that comment
16:56:45 <abadger1999> tonet666p: they all have python3 subpackages but something is wrong with them.
16:58:06 <frafra> libraries: subpackage (2 rpm: one for py2 one for py3); app: switch to py3; app for py2 only: use /usr/bin/python2; am I correct?
16:58:13 <frafra> I'm a bit confused
16:58:18 <tonet666p> abadger1999, reading...
16:58:57 <abadger1999> tonet666p: You could look at python-jsonpointer if you want something to start on that's reasonably easy.
16:59:13 <tonet666p> ok
16:59:15 <abadger1999> tonet666p: It's from the list and I had looked at it earlier but not started rewriting hte spec file.
17:00:21 <abadger1999> frafra: Yes,  for legacy reasons, the main package (named something like python-pypiname) can contian the python2 library.  Or the python2 library can be in its own subpackage.
17:00:39 <abadger1999> frafra: the python3 library is in its own subpackage.
17:01:14 <abadger1999> frafra: For almost all apps, you wnat to switch it to use /usr/bin/python3 in rawhide.
17:01:54 <tonet666p> wait a moment, i still have fedora 22, i necesary f23 for this work?
17:01:59 <potty> No
17:02:15 <abadger1999> frafra: if the app only can be run on python2, chances are any python library that ships with  the app also only runs on python2 so there's nothing we can do for creating a python3 package here... but we can work on adding python3 support upstream.
17:03:08 <abadger1999> frafra: ah -- my "almost all" in regards to app -- that's assuming you can get the code to work with python3 of course :-)
17:03:54 <abadger1999> tonet666p: Most packages I can do all the work on whatever fedora I have installed (i'm on f21 right now).
17:04:10 <abadger1999> tonet666p: some you can't build htem on older fedora because the python3 versions of its dependencies aren't there.
17:04:12 <frafra> abadger1999: thank you :)
17:04:40 <mstuchli> abadger1999: porters.yaml is for that
17:04:56 <abadger1999> tonet666p: You can use the test machine resources to have something to test on: https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers
17:05:17 <abadger1999> tonet666p: I've been using rawhide-test.scrye.com a lot for those sorts of packages.
17:05:41 <abadger1999> mstuchli: k
17:06:02 <abadger1999> thanks!
17:06:06 <MSK61> I've noticed that the last commit in portingdb, cabd81961c9d7b5f00ea525d290117176cb16dce, which merges pull request #22, causes the database creation to fail.
17:06:27 <MSK61> I've verified that just one commit before, it was working fine.
17:06:35 <abadger1999> MSK61: k.  I'll take a look.
17:08:29 <logavanc> Holy cow it got busy in here!
17:09:30 <logavanc> Is this https://tree.taiga.io/project/synfo-fedora-python-3-porting/ page going to be used?
17:10:07 <chandankumar> abadger1999: Hello
17:10:09 <abadger1999> logavanc: It was decided that it was superfluous.  Use the titanpad page and the portingdb instead.
17:10:13 <abadger1999> chandankumar: Greetings
17:10:34 <abadger1999> logavanc: https://titanpad.com/S3r8qX7OQJ  http://portingdb-encukou.rhcloud.com/
17:10:35 <potty> abadger1999 +1
17:10:36 <threebean> mstuchli: if you made me an admin, that would probably work :)
17:10:40 <chandankumar> abadger1999: I had applied the patch and created a new build for python-os-testr https://bugzilla.redhat.com/show_bug.cgi?id=1279704
17:10:45 <chandankumar> abadger1999: ++
17:10:53 <threebean> abadger1999: on createrepo, yeah.  i was thinking of dropping createrepo, and instead just focusing on porting createrepo_c
17:11:08 <abadger1999> threebean: Okay, thanks for the info!
17:11:15 <threebean> abadger1999: not clear how hard that will be yet.  I figured out how to get it to compile against python3, but the extension still needs some work.  I left notes in the app! :D
17:12:02 <mstuchli> threebean: done
17:12:35 <MSK61> portingdb creation failure log: http://pastebin.com/99bLXWWf
17:12:50 <abadger1999> chandankumar: Excellent, thanks!
17:13:01 <abadger1999> MSK61: yep, I have a fix ready.
17:13:28 <abadger1999> Just waiting on rodrigc to resubmit his sorted list PR to commit it.
17:13:56 <abadger1999> (The portingb only understands links of type bug: I think.  So other links go in the notes section.)
17:14:13 <rodrigc> abadger1999: try now
17:14:34 <threebean> abadger1999: fwiw, I think it also understands links of type 'repo'
17:15:01 <abadger1999> rodrigc: Thanks!
17:15:09 <abadger1999> threebean: nice, I'll try that out.
17:17:25 <rodrigc> abadger1999: oops
17:17:30 <rodrigc> abadger1999: now I am getting this
17:17:31 <rodrigc> aml.composer.ComposerError: found undefined alias 'obnam'
17:17:32 <rodrigc> in "/usr/home/rodrigc/portingdb/data/upstream.yaml", line 27, column 10
17:17:38 <abadger1999> :-(
17:18:46 <abadger1999> Very odd... looks like the same syntax.
17:19:01 <abadger1999> But it also looks like maybe it should have been $obnam; ?
17:19:24 <threebean> mstuchli: all done!  :)
17:21:11 <abadger1999> hmm... alright maybe & is when you define it...
17:21:14 * abadger1999 looking further
17:22:05 <abadger1999> oh... maybe it's being defined after it's being referenced now...
17:24:28 <condor> Must butt in, I must bounce,  be back perhaps by 17:30 utc, having reviewed this irc log and the links provided here in.  Guess I call myself as want to packager.  lol all!
17:24:49 <abadger1999> michel_slm, mstuchli: Should we be marking packages as dropped that are active upstream but upstream is just not ready to port yet?
17:25:12 <abadger1999> michel_slm, mstuchli: especially if there isn't an alternative module out there?
17:26:56 <rodrigc> abadger1999: this application is not designed well.  if people need to manually edit yaml files like this, that is no good
17:27:59 <mstuchli> abadger1999: If they are not outright against porting, than perhaps keep it idle and add a note
17:28:06 <rodrigc> it would be easier to just have a wiki, or a Google doc spreadsheet
17:28:40 <abadger1999> rodrigc: heh, yeah, but I imagine the author probably wanted to spend more time porting code than to making the app perfect.. a matter of where a volunteer wants to spend their time.
17:28:54 <abadger1999> rodrigc: we had tried a wiki in the past--- it definitely didn't work as well as this.
17:29:19 <zodbot> potty: Error: Can't start another meeting, one is in progress.
17:29:19 <abadger1999> rodrigc: there's a good deal of automation (determining the dependencies and determining what packages are already ported).
17:29:46 <abadger1999> rodrigc: the problem is that not all of the information is automatically collected, thus the app needing some manner of manual entry.
17:34:04 <potty> /me going to lunch. After that will start my coding/packaging effort.
17:34:08 <rodrigc> now I'm getting this:
17:34:11 <rodrigc> qlite3.IntegrityError: CHECK constraint failed: links
17:34:28 <rodrigc> sqlalchemy.exc.IntegrityError: (sqlite3.IntegrityError) CHECK constraint failed: links [SQL: 'INSERT INTO links (collection_package_id, url, type) VALUES (?, ?, ?)'] [parameters: ((28, 'https://git.fedorahosted.org/cgit/freeipa.git', 'repo'), (29, 'https://github.com/pyldap/pyldap', 'repo'), (42, 'https://github.com/rpm-software-management/createrepo_c/issues/41', 'bug'), (35, 'https://bugs.launchpad.net/rapid/+bug/1074028', 'bug
17:34:48 <joe> hi
17:35:23 <joe> just read the magazine article
17:37:09 <abadger1999> rodrigc: hmmm... that should be fixed in my latest merge.
17:37:42 <MSK61> rodrigc: I think this's similar to my symptom here http://pastebin.com/99bLXWWf.
17:38:39 <rodrigc> MSK61: yeah
17:38:57 <abadger1999> MSK61: yours should be fixed too... unless I merged to the wrong branch or something.
17:39:38 <abadger1999> Yeah, should be fixed by this commit: https://github.com/fedora-python/portingdb/commit/54fe81f6a607732f092f02f98c56e565d8c8a2b3
17:40:40 <rodrigc> abadger1999: OK, I updated with your latest changes and it works
17:41:27 <rodrigc> oh
17:42:13 <rodrigc> status: released
17:42:13 <rodrigc> links:
17:42:13 <rodrigc> repo: https://github.com/coleifer/peewee
17:42:13 <rodrigc> travis-ci: https://travis-ci.org/coleifer/peewee
17:42:25 <rodrigc> so having travis-ci in the links section was causing the integrity error
17:42:36 <rodrigc> so links has a fixed schema
17:45:21 <fujimotos> Oh I don't notice that "links" has a schema. I'll fix this.
17:46:04 <tonet666p> abadger1999, python-jsonpointer already has python 3 support
17:46:44 <abadger1999> tonet666p: Yep, it does but it has a problem.
17:47:19 <tonet666p> i understand the problem is in python 2
17:48:00 <abadger1999> tonet666p: If you check repoquery -q --requires python-jsonpointer and repoquery-q --requires python3-jsonpointer you'll see that one of those is dragging in the wrong version of python.
17:48:06 <tonet666p> also, the upstream released a new version
17:48:42 <rodrigc> fujimotos: are you the author of portingdb?
17:49:18 * abadger1999 refreshes his memory of what needs to happen in jsonpointer...
17:50:01 <rodrigc> ok now that portingdb works for me, back to one of my earlier questions
17:50:21 <rodrigc> who decided that m2crypto is "dropped"?
17:50:38 <abadger1999> tonet666p: okay so what it needs is for the script that is in python-jsonppointer to be moved to python3-jsonpointer.
17:50:39 <rodrigc> I've been submitting Python3 patches upstream, and the maintainer has been slowly taking them
17:50:41 <fujimotos> rodrigc: No, I'm not the author.
17:52:04 <abadger1999> tonet666p: the rationale there is: (1) the script can be run with either python2 or python3 and it won't make any difference to the end user.  (2) we should be providing the script running with python3 not python2 in fedora 23 and above.
17:52:33 <abadger1999> (3) the python-jsonpointer package shouldn't require python3 and vice versa for the python3-jsonpointer pakcage.
17:53:20 <abadger1999> tonet666p: So for that one we should just need to move the script over.
17:53:46 <hasys> Hi all. Do you have some useful articles about migration from python 2 to python 3?
17:54:25 <abadger1999> Others on that list should be similar but may have slight differences -- they might currently be built against python2 rather than python3.  The script might do different things under py2 and py3 so we need to ship two versions, etc.
17:54:50 <abadger1999> hasys: in what context?  In terms of porting upstream code?  Or in terms of migrating rpm spec files?
17:55:24 <abadger1999> hasys: for the upstream question, this is the best guide I've found: http://python3porting.com/noconv.html
17:55:57 <abadger1999> rodrigc: Not sure -- I could trawl the git history... If upstream is taking patches now then we can update the data to say that.
18:00:40 <hasys> abadger1999: I'd like to port some apps to python3 for example Anki. So it is interesting for me how to start. What I have to do to port Anki app to python 3 for fedora and others distributives
18:01:52 <abadger1999> rodrigc: Looks like it was added directly by the portingdb author here: https://github.com/fedora-python/portingdb/commit/9ded408c31c2775c04b5dbc219994186c1b9095c
18:03:41 <abadger1999> rodrigc: I can change it from dropped to something else if you and upstream are working on it...  not sure what hte best status is... I guess I'd move it back to idle and add a link to a commit/Pr/mailing list post showing that work is starting to happen upstream?
18:03:52 <abadger1999> (If you could dig up one of those links for me).
18:04:11 <abadger1999> hasys: Cool.  So yeah. python3porting.com is where I'd go first to find information.
18:04:39 <abadger1999> hasys: There's also this page on the python wiki that has some useful information: https://wiki.python.org/moin/PortingToPy3k
18:05:40 <abadger1999> hasys: we've had good luck using python-mechanize to get started on making code run under both py2.6+ and python3.... still needs manual work afterwards usually but it gets you started.
18:05:44 <rodrigc> I can add links to README.md if it helps.  There are a bunch I have been using for Python3 porting
18:06:11 <abadger1999> rodrigc: not sure -- maybe add it to the titanpad for now.
18:06:57 <abadger1999> I don't know how much the portingdb author wants to make the app repo a repository for general py3 porting info versus how to run and contribute to the app.
18:07:10 <abadger1999> titanpad link: https://titanpad.com/S3r8qX7OQJ
18:07:46 <hasys> abadger1999: thank you. And can I ask you do you know which repository use fedora team for anki?
18:08:58 <abadger1999> hasys: If someone starts work on porting here, we'll contribute it back to upstream directly.  (if you're on github, then probably as a PR.  If you have some other mailing list or bug tracker than maybe there).
18:09:25 <abadger1999> hasys: We have our own repos -- but those are for packaging of the upstream code into rpms rather than for directly working on the code.
18:10:28 <abadger1999> hasys: That packaging repository is here: http://pkgs.fedoraproject.org/cgit/anki.git/tree/
18:11:29 <MSK61> Is this FAD intended for packages of software requireing small effort for migration to python 3? I'm thinking of picking up anjuta, but it seems it's going to take some good effort till it gets migrated.
18:12:13 <MSK61> I'll probably need to consult their developers on the way.
18:12:35 <abadger1999> MSK61: that's fine -- it's one part excuse to focus effort on porting and a second part, having other people around to ask questions of.
18:12:35 <hasys> abadger1999: I see, thank you. I am asking because official github repo not looks like really alive project https://github.com/dae/anki . So I am not sure is it worth to do this work?..
18:12:51 <abadger1999> hasys: It may not be worthwhile.
18:14:40 <abadger1999> hasys: Probably should talk to upstream about whether they would be interested in patches to port and if they'll make a new release when the port is completed.
18:16:48 <zbyszek> Hi! How's the FAD going?
18:16:56 <zbyszek> I'll try python-argcomplete
18:17:47 <zbyszek> Oh, argcomplete is already done.
18:20:04 <abadger1999> zbyszek: Looks like argcomplete is ported but hte rpm packaging needs to be fixed.
18:20:17 <fitoria> BOOM package done on my github https://github.com/fitoria/boom/tree/python3
18:20:25 <fitoria> I’m sending the PR
18:20:50 <abadger1999> zbyszek: up to you whether you're interested in the coding side of things or the packaging side of things :-)
18:21:03 <potty> Good job
18:21:46 <abadger1999> fitoria: yay!  Either let me know the link to the PR or put in a portingdb PR and I'll get it merged to the data set there.
18:21:49 <zbyszek> abadger1999: can you explain what is wrong with the rpm packaging? python3-argcomplete installs just fine...
18:21:59 <fitoria> https://github.com/tarekziade/boom/pull/52
18:22:02 <fitoria> there is the link
18:22:04 <abadger1999> zbyszek: http://portingdb-encukou.rhcloud.com/pkg/python-argcomplete/
18:22:08 <fitoria> we’re going for lunch :D
18:22:25 <abadger1999> zbyszek: The python-argcomplete package depends on /usr/bin/python3
18:22:45 <potty> fitoria saludos!
18:22:58 <abadger1999> zbyszek: that probably means that the package is creating a script in /usr/bin/* and that script is using python3 in its shebang line.
18:23:08 <zbyszek> Ah, interesting. I should be able to fix that.
18:23:12 <abadger1999> zbyszek: the proper thing to do is to move the script to the python3-argcomplete package.
18:23:34 <abadger1999> zbyszek: Cool.  let me know if it's a different reason that's happening and you need some help.
18:24:11 <zbyszek> abadger1999: yes, that's the reason. /usr/bin/register-python-argcomplete has #!/usr/bin/python3.
18:29:07 <threebean> fitoria: nice work :)  I left a question in your boom PR
18:31:07 <frafra> ok! I think that I've done my first spec migration for a py3 app... I'm quite slow, I know :) https://frafra.fedorapeople.org/spec/autotrash.spec
18:33:54 <frafra> now let's try a real porting of a py2-only lib :)
18:37:38 * decause clocks in
18:37:54 <frafra> 2to3 was enough in this simple case; should I send the patch upstream? every url is down and the code is not maintained
18:38:55 <abadger1999> :-(
18:39:14 <abadger1999> frafra: I guess submit a bugzilla report to the maintainer.
18:40:06 <abadger1999> frafra: I suppose we're sorta giving hte fedora packager a choice... you either have to support this on your own or retire the package....
18:40:37 <circ-user-ZZhEp> Hellooo
18:40:47 <threebean> circ-user-ZZhEp: hi josh :)
18:40:58 <abadger1999> eventually supporting on their own would mean accepting and maintaining the python3 patch because that's where fedora is moving.
18:41:04 <circ-user-ZZhEp> Hi bean :o)
18:41:20 <potty> On a similar case I forked the project and worked on the fork
18:41:47 <abadger1999> heh, so we're also still seeing packages that haven't been rebuilt since python3 in fedora was updated to python-3.5 :-(
18:41:48 <threebean> circ-user-ZZhEp: we have a list of packages we're working from here http://portingdb-encukou.rhcloud.com/
18:42:31 <threebean> circ-user-ZZhEp, decause: and there is info on how to update it here -> http://synfo.github.io/2015/10/14/Python3-Porting-Database/
18:43:20 <abadger1999> python3-pycurl.... i wonder if you are just a rebuild...
18:47:06 * abadger1999 sees a rabbit hole and backs away slowly...
18:49:13 <potty> Lol
18:49:30 <potty> Careful with traps abadger1999
18:49:36 <abadger1999> tonet666p, zbyszek: If you guys need any help (or someone to merge your spec file changes) let me know.  Those are usually changes I don't have any problem using provenpackager to merge to rawhide and rebuild for.
18:50:32 <rodrigc> is anyone from Pycon CZ here?
18:51:15 <frafra> abadger1999: thank you
18:51:28 <abadger1999> frafra: no problem :-)
18:51:47 <rodrigc> what is titanpad?
18:51:52 <abadger1999> rodrigc: what we heard earlier from mstuchli was that pyco nCZwould start tomorrow (for them)
18:51:57 <abadger1999> rodrigc: https://titanpad.com/S3r8qX7OQJ
18:52:07 <abadger1999> rodrigc: just an etherpad instance that we can use to coordinate this a bit.
18:52:22 <abadger1999> errr...
18:52:41 <abadger1999> rodrigc: correction on pycon cz... that they'd show up here tomorrow...
18:52:51 <abadger1999> I guess they're all out having fun without us right now ;-)
18:58:39 <potty> Indeed
18:58:42 <potty> They are resting
18:58:52 <potty> Tomorrow they will do the sprint
18:59:22 <potty> Where are you from rodrigc ?
19:01:54 <frafra> abadger1999: should I update fedora-update.yaml or upstream.yaml in this case? which status should I use?
19:02:35 <abadger1999> frafra: for the PR you submitted?  I already updated the upstream.yaml... not sure if that's the right place but I figure they'll correct me if I'm wrong.
19:03:07 <abadger1999> frafra: My thought is that once it's merged upstream, it can be moved to fedora-update.yaml to show that fedora needs to do the work now.
19:03:20 <abadger1999> (or maybe they'll rearhitect the app to not have both files ;-)
19:04:39 <frafra> abadger1999: I mean this new one (python-printr) - https://bugzilla.redhat.com/show_bug.cgi?id=1282069
19:08:01 <frafra> it's an upstream problem (it's not maintained), but the problem will probably be handled inside Fedora
19:08:05 <frafra> (I suppose)
19:08:52 <abadger1999> frafra: yeah -- I guess add it to upstream.yaml... I would leave status as idle (default) for now, link to the bugzilla and add a note explaining that upstream is dead and fedora maintainer has not yet decided whether to drop support.
19:09:16 <frafra> ok, thank you
19:09:18 <frafra> :)
19:16:07 <condor> Hi, I've question, looking at the list of packages to port how can we detirmine the packages that count on in, or is such a  search possible?
19:17:25 <abadger1999> condor: that should be further down in the list...
19:17:52 <abadger1999> condor: actually. inline
19:18:41 <abadger1999> condor: If you look for python-twisted on the page for example: http://portingdb-encukou.rhcloud.com/
19:18:55 <abadger1999> condor: you'll see that it is needed for a whole lot of packages.
19:19:39 <condor> right click copy link location ... give me a few minutes to catch up :)
19:19:40 <abadger1999> condor: if, on the other hand, you have a package and want to see what blocks it,  go down further and see if it's in the Blocked packages list.
19:20:23 <abadger1999> The individual package page also has the information in the left hand side bar: http://portingdb-encukou.rhcloud.com/pkg/python-twisted/
19:20:31 <condor> abadger19999: second case have a package and want to see what blocks  was my original thought
19:20:39 <abadger1999> cool.
19:21:26 <abadger1999> condor: <nod>  So if I was looking into buildbot, I'd go to this page: http://portingdb-encukou.rhcloud.com/pkg/buildbot/  and see that python-twisted and python-migrate were blocking it.
19:21:40 <SDyroff> Hey, I would like to help porting something. It seams that a lot of the packaged django packages support python 3
19:22:37 <abadger1999> SDyroff: Cool.  You can look here for lists of packages and their status in fedora: http://portingdb-encukou.rhcloud.com/
19:23:27 <abadger1999> SDyroff: If upstream already has support for python3 then it should be just a matter of changing the packaging of the fedora package to fix it.  If upstream hasn't ported yet, then we have to port the code and submit it upstream.
19:24:15 <SDyroff> abadger1999: I have already found some easy packages, that only needs spec changes, should these packages be marked in portingdb, or should i just work on the specs and mark them when they are done?
19:27:47 <sayan> abadger1999, Hi
19:28:10 <threebean> damnedfacts: hi!
19:28:12 <abadger1999> sayan: greetings :-)
19:28:14 <damnedfacts> hello!
19:28:28 <decause> fedmsg-python++
19:28:30 <threebean> damnedfacts: here's the list of all the packages we're looking at http://portingdb-encukou.rhcloud.com/
19:28:43 <sayan> abadger1999, I wrote ported the spec file for python-retask but saw this link now http://synfo.github.io/2015/10/14/Python3-Porting-Database/
19:28:55 <threebean> damnedfacts: and here's a blog post with info on how to update that app http://synfo.github.io/2015/10/14/Python3-Porting-Database/
19:28:59 <abadger1999> SDyroff: I'd just do them and then mark them after they're done.
19:29:01 <decause> damnedfacts++
19:29:09 <damnedfacts> threebean: thanks!
19:29:27 <abadger1999> SDyroff: But it's probably how much you think you can get done in a reasonable time :-)
19:29:48 <sayan> abadger1999, but in upstream.yaml, I see it's in progress
19:29:53 <abadger1999> SDyroff: If you won't get all of them done hten it's good to let other people know what's required.
19:30:48 <SDyroff> abadger1999: Ok, I start then working on the specs and will mark those I am not able to finish :)
19:31:32 <abadger1999> sayan: I don't see any markings for retask in the portingdb so I think it's fair game:http://portingdb-encukou.rhcloud.com/pkg/python-retask/
19:31:36 <abadger1999> Sdrexcellent.
19:31:48 <abadger1999> SDyroff:  Excellent
19:31:59 <Rupe> abadger1999, sayan: actually, I'm working on it
19:32:08 <Rupe> just submitted a PR to claim it ;);)
19:32:45 <fedmsg-python> 15github.push -- abadger pushed 3 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/97c60acb6e1d...22fc307fc065
19:32:46 <fedmsg-python> 15github.pull_request.closed -- abadger closed pull request #33 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/33
19:33:08 <fedmsg-python> 15github.pull_request.closed -- abadger closed pull request #34 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/34
19:33:09 <fedmsg-python> 15github.push -- abadger pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/22fc307fc065...a3e7694901a7
19:33:27 <abadger1999> Cool
19:34:51 <abadger1999> Rupe, sayan: You might want to work together if sayan has the spec file updated and Rupe you're just starting on it.
19:35:57 <Rupe> abadger1999, sayan: all of the unit tests just passed under 3.4, so I think we're good actually
19:36:05 <sayan> Rupe, yeah, made some other changes too other than porting :)
19:37:02 <condor> abadger1999: I'm chewing on this...
19:37:05 <fedmsg-python> 15github.fork -- DamnedFacts forked fedora-python/portingdb 10https://github.com/DamnedFacts/portingdb
19:37:20 <Rupe> sayan: gotcha, you want to claim it in the upstream.yaml?
19:38:08 <sayan> Rupe, ok, I'll then send a PR to the portingdb repo
19:38:24 <sayan> abadger1999, can you add both the links to IRC channel topic?
19:38:40 <Rupe> sayan++
19:39:09 <threebean> yay!
19:39:43 <abadger1999> potty: Can you have zodbot change the channel topic ^
19:40:11 <abadger1999> potty: You could also make some more of us chairs of the meeting so we can tell zodbot what to do too.
19:41:01 <fedmsg-python> 15github.push -- ralph pushed 1 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/a3e7694901a7...0803383f42bd
19:47:11 <fedmsg-python> 15github.fork -- sayanchowdhury forked fedora-python/portingdb 10https://github.com/sayanchowdhury/portingdb
19:48:10 <fitoria> Should packages marked as idle ported?
19:48:11 <fitoria> or not?
19:48:18 <fedmsg-python> 15github.fork -- fale forked fedora-python/portingdb 10https://github.com/Fale/portingdb
19:48:24 <fitoria> I’m thinking in porting https://github.com/google/python-atfork
19:49:39 <zbyszek> OK, python-argcomplete is built in rawhide. I rebuilt barman and abrt with new Requires.
19:49:48 <zbyszek> Should I check python-argcomplete off somewhere?
19:49:48 <fedmsg-python> 15github.pull_request.opened -- sayanchowdhury opened pull request #35 on fedora-python/portingdb: python-retask updated 10https://github.com/fedora-python/portingdb/pull/35
19:50:42 <fedmsg-python> 15github.pull_request.opened -- fale opened pull request #36 on fedora-python/portingdb: Notify rb_libtorrent status 10https://github.com/fedora-python/portingdb/pull/36
19:52:44 <fedmsg-python> 15github.fork -- keszybz forked fedora-python/portingdb 10https://github.com/keszybz/portingdb
19:53:21 <fedmsg-python> 15github.pull_request.opened -- keszybz opened pull request #38 on fedora-python/portingdb: Mark argcomplete as done 10https://github.com/fedora-python/portingdb/pull/38
19:53:22 <fedmsg-python> 15github.pull_request.opened -- fitoria opened pull request #37 on fedora-python/portingdb: Marking python-atfork as in progress 10https://github.com/fedora-python/portingdb/pull/37
19:54:30 <SigmaWP> do I really have to use my IRC nickname for fedora? my IRC account is tied only to Wikipedia and I like to keep Wikipedia separate from the rest of my life :\
19:55:08 <condor> abadger1999: for buildbot python-twisted-conch, python-twisted-mail, & python-twisted-work examined and possibly modified replacing any mention of python with pyton3
19:55:10 <pingou> SigmaWP: why would you have to?
19:55:47 <abadger1999> fitoria: Yes, I think idle is the main place that we're going to be working.
19:56:02 <condor> abadger19999: but I'm not going to dnf download --source ...,  I need to get clone ?  and the inform upstream developer of any changes needed?
19:56:14 <SigmaWP> I was suggested to create a fedora account, sign the contributor agreement, and list my irc nickname on my account profile
19:56:26 <abadger1999> zbyszek: shouldn't need to -- once it hits the master mirror someone will regenerate the information from the yum repository and then it should be noted automatically.
19:56:29 <condor> abadger1999: sorry `git clone '
19:56:48 <fedmsg-python> 15github.fork -- fabaff forked fedora-python/portingdb 10https://github.com/fabaff/portingdb
19:57:26 <zbyszek> abadger1999: OK, thanks. I'll withdraw my PR for portingdb then.
19:57:34 <abadger1999> zbyszek: note -- I have some changes that I'd make to that package -- let me pastebin them.
19:58:46 <abadger1999> zbyszek: http://fpaste.org/290549/53105914/
19:59:18 <fedmsg-python> 15github.issue.comment -- keszybz commented on issue #38 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/38#issuecomment-156742525
19:59:19 <fedmsg-python> 15github.pull_request.closed -- keszybz closed pull request #38 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/38
20:00:33 <randomuser> yay, more IRC channels!
20:00:48 <abadger1999> zbyszek: We don't need to put a Provides on the script... rpm can find file deps without it;  better to make the script that's installed be the one that's used in the %files section rather than sed'ing hte script to change the shebang because some packages might have enough code in the script that the code will be different.
20:01:33 <abadger1999> zbyszek: -- I see that I made a mistake.
20:01:37 <abadger1999> :-)
20:01:59 <abadger1999> zbyszek: I'll make sure I don't include that when I commit this.
20:01:59 <fedmsg-python> 15github.pull_request.opened -- fabaff opened pull request #39 on fedora-python/portingdb: add pysysbot 10https://github.com/fedora-python/portingdb/pull/39
20:02:16 <zbyszek> abadger1999: I thought that adding an explicit Provides:/file/name avoids the need to download the full list of files. An optimization measure.
20:02:49 <abadger1999> zbyszek: nope -- with yum, there's a list of common directories that it keeps in the primary metadata (bindir is in there).
20:03:04 <zbyszek> Ah, OK.
20:03:15 <abadger1999> zbyszek: With dnf, it downloads the entire filelist information everytime. It doesn't have an optimization there :-(
20:04:11 <zbyszek> There are epel branches... I think the maintaner might want to build w/o python3.
20:04:53 <abadger1999> <nod>
20:05:45 <abadger1999> That should still work with my changes (minus the %files section change... that one I didn't see what you were doing at first)
20:06:33 <zbyszek> So, you want register-python-argcomplete to use python2 or python3?
20:06:40 <abadger1999> ... I also see I didn't reference what I was talking about when I said I made a mistake above.... I need to learn to type.
20:08:02 <abadger1999> zbyszek: http://fpaste.org/290552/53163514/  how's that look?
20:08:36 <zbyszek> So, you want register-python-argcomplete to use python2 or python3?
20:08:41 <potty> #chair abadger1999
20:08:41 <zodbot> Current chairs: abadger1999 potty
20:08:42 <abadger1999> zbyszek: python3 in fedora, python2 in epel, I think.
20:08:50 <potty> #chair threebean
20:08:50 <zodbot> Current chairs: abadger1999 potty threebean
20:09:07 <potty> Done abadger1999
20:09:11 <zbyszek> And if you build it with those changes, do you have the right she-bang line?
20:09:13 <abadger1999> potty: thanks
20:09:20 <abadger1999> zbyszek: yep.
20:09:26 <potty> u welcome
20:09:38 <abadger1999> zbyszek: although I usually make it explicit by moving hte files around ...
20:10:12 <abadger1999> zbyszek: I think distutils and setuptools do oppoiste things regarding overwriting with the latest vs preserving the file if it is already present.
20:11:58 <zbyszek> abadger1999: OK, then it looks fine.
20:11:59 <abadger1999> zbyszek: I usually do something like this: http://pkgs.fedoraproject.org/cgit/python-reno.git/tree/python-reno.spec#n102  so that there's no ambiguity.
20:12:05 <abadger1999> cool.
20:12:27 <fedmsg-python> 15github.pull_request.opened -- rupe120 opened pull request #40 on fedora-python/portingdb: claiming python-django-registration 10https://github.com/fedora-python/portingdb/pull/40
20:12:59 <zbyszek> Yeah, I rebuilt locally and it seems good.
20:14:40 <abadger1999> Cool.
20:15:41 <threebean> potty: thanks! :)
20:16:13 <threebean> #meetingname python3-porting-vfad
20:16:13 <zodbot> The meeting name has been set to 'python3-porting-vfad'
20:16:33 <SDyroff> abadger1999: I have my first package ported, should create a bug for the maintainer, to review the changes
20:16:35 <decause> #chairs
20:16:50 <threebean> SDyroff: that sounds like a good plan :)
20:17:07 <threebean> SDyroff: and then link to that bug from the portingdb data/fedora-updates.yml file. with an 'in-progress' status.
20:17:24 <abadger1999> #topic Python3 porting FAD in progress | Package status: http://portingdb-encukou.rhcloud.com/ | Porting notes: https://titanpad.com/S3r8qX7OQJ
20:17:49 <fedmsg-python> 15github.pull_request.opened -- frafra opened pull request #41 on fedora-python/portingdb: python-flask-debugtoolbar added 10https://github.com/fedora-python/portingdb/pull/41
20:17:58 <potty> Good
20:18:20 <fitoria> PR for python atfork https://github.com/google/python-atfork/pull/1 I’m going to update the portingdb right now
20:18:21 <abadger1999> I thought zodbot would update the topic but perhaps he doesn't have permissions :-(
20:19:04 <abadger1999> SDyroff: How big are the changes?
20:19:40 <fedmsg-python> 15github.pull_request.synchronize -- fitoria synchronized pull request #37 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/37
20:19:47 <abadger1999> SDyroff: I can look -- if they're things like zbyszek's changes to python-argcomplete I think it's okay to push it to rawhide and build.
20:19:48 <potty> abadger1999 actually when i started the meeting tried to change topic and does not worked
20:20:16 <SDyroff> abadger1999: I think it is best to let the maintainer look over it. The translation thing seems a bit ugly
20:20:23 <abadger1999> potty: k.  I guess we'll need to figure out who has op in here.
20:20:59 <abadger1999> SDyroff: k.  Works for me -- we should put a note into the portingdb too then so that we can do something if the fedora maintainer doesn't get around to it for a while.
20:22:57 <fedmsg-python> 15github.pull_request.closed -- abadger closed pull request #35 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/35
20:22:58 <fedmsg-python> 15github.push -- abadger pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/0803383f42bd...b604742ccb1d
20:24:16 <fedmsg-python> 15github.pull_request.opened -- decause opened pull request #42 on fedora-python/portingdb: tweepy confirmed python3 ready (and tox-tested) upstream by @decause 10https://github.com/fedora-python/portingdb/pull/42
20:24:50 <condor> Gosh I got a build error on python-twisted! An empty egg file?
20:26:04 <fedmsg-python> 15github.issue.comment -- abadger commented on issue #41 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/41#issuecomment-156743970
20:26:12 <dperson> I 'futurize'd the byobu python scripts to be compatible with python 3.x, tested them with both versions, and submitted a pull request. Assuming that it's accepted, the she-bang line is '#!/usr/bin/env python' and it's not likely to be changed. The scripts will however be python 3.x ready. I'm not sure exactly how this should be handled...
20:27:04 <abadger1999> dperson: is it installed via distutils or setuptools?
20:27:45 <abadger1999> dperson: those usually transform shebang lines of scripts correctly.  If not.. in hte spec file you can sed the shebang lines appropriately.
20:28:25 <abadger1999> (If the scripts are actually shebang lines in the modules rather than in things in %{_bindir} then we'd have to do the sed thing too)
20:28:33 <dperson> @abadger1999 thank you that makes sense
20:29:19 <fedmsg-python> 15github.pull_request.synchronize -- frafra synchronized pull request #41 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/41
20:30:05 <dperson> I'll add myself to the 'working on byobu' and submit a pull, once the byobu pull is accepted, I'll update the spec file
20:30:12 <threebean> this is crazy :)
20:30:38 <fedmsg-python> 15github.fork -- dperson forked fedora-python/portingdb 10https://github.com/dperson/portingdb
20:30:39 <fedmsg-python> 15github.issue.comment -- frafra commented on issue #41 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/41#issuecomment-156744189
20:30:55 <fedmsg-python> 15github.pull_request.closed -- abadger closed pull request #41 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/41
20:30:56 <fedmsg-python> 15github.push -- abadger pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/b604742ccb1d...375587fd3ddb
20:31:13 <fedmsg-python> 15github.pull_request.closed -- abadger closed pull request #42 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/42
20:31:15 <fedmsg-python> 15github.push -- abadger pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/375587fd3ddb...ac8c34983e06
20:31:53 <fedmsg-python> 15github.fork -- ampotty forked fedora-python/portingdb 10https://github.com/ampotty/portingdb
20:32:35 <zbyszek> abadger1999: http://paste.fedoraproject.org/290559/75331271
20:32:46 <fedmsg-python> 15github.pull_request.opened -- DamnedFacts opened pull request #43 on fedora-python/portingdb: Regarding python-sexy 10https://github.com/fedora-python/portingdb/pull/43
20:34:12 <fitoria> Hey guys, I’m starting to port https://pypi.python.org/pypi/pyprintr
20:34:39 <potty> I will work with python-daap
20:35:01 <abadger1999> zbyszek: Looks good!  +1
20:36:17 <zbyszek> abadger1999: thx. Building now.
20:38:06 <fedmsg-python> 15github.pull_request.synchronize -- rupe120 synchronized pull request #40 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/40
20:41:18 <fedmsg-python> 15github.pull_request.closed -- abadger closed pull request #43 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/43
20:44:09 <fedmsg-python> 15github.push -- abadger pushed 1 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/974a8cf6ed04...5854bbdcb218
20:44:46 <fedmsg-python> 15github.issue.comment -- abadger commented on issue #36 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/36#issuecomment-156744967
20:44:48 <fedmsg-python> 15github.pull_request.closed -- abadger closed pull request #36 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/36
20:45:06 <fedmsg-python> 15github.pull_request.opened -- sdyroff opened pull request #44 on fedora-python/portingdb: Add information about python-flask-admin 10https://github.com/fedora-python/portingdb/pull/44
20:45:22 <frafra> fale: hi! :D
20:46:17 <fedmsg-python> 15github.pull_request.opened -- dperson opened pull request #45 on fedora-python/portingdb: Add work on 'byobu' to fedora-update.yaml 10https://github.com/fedora-python/portingdb/pull/45
20:47:46 <michaeleekk> I saw the package lunatic-python has a better alternative which supports python3 already, which is called Lupa. Should I mark lunatic-python as dropped then?
20:48:25 <michaeleekk> And add Lupa to upstream?
20:48:50 <fedmsg-python> 15github.pull_request.opened -- sayanchowdhury opened pull request #46 on fedora-python/portingdb: update note for python-retask in fedora-update.yaml 10https://github.com/fedora-python/portingdb/pull/46
20:49:15 <frafra> upstream.yaml: These are out of order because they define an alias that is used later in the file
20:49:45 <frafra> (I saw some non ordered parts at the end)
20:50:13 <condor> https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
20:51:47 <frafra> ops, sorry
20:52:31 <abadger1999> michaeleekk: Is Lupa packaged for Fedora?
20:52:36 <fitoria> pyprintr ported and bug updated https://bugzilla.redhat.com/show_bug.cgi?id=1282069
20:52:46 <abadger1999> fitoria: nice work!
20:52:46 <frafra> ok I didn't pushed the wrong commit, good :)
20:53:06 <frafra> fitoria: good!
20:53:27 <michaeleekk> abadger1999: seems not yet
20:53:44 <abadger1999> michaeleekk: if it is then I probably would... if it is not then I'd open a bug report in bugzilla for the lunatic maintainer to consider doing that.
20:54:04 <abadger1999> michaeleekk: and update the portingdb to reference the bgu report until we know what the maintainer wants to do.
20:54:19 <abadger1999> #chair mstuchli
20:54:19 <zodbot> Current chairs: abadger1999 mstuchli potty threebean
20:55:22 <fedmsg-python> 15github.pull_request.opened -- frafra opened pull request #47 on fedora-python/portingdb: youtube-dl: bugzilla bug added 10https://github.com/fedora-python/portingdb/pull/47
20:55:45 <SDyroff> Hey, what about tools that do not really have a useful library, should they be python3 only?
20:55:46 <abadger1999> okay, pycurl rebuilt for python-3.5... but I'm still far down the rabbit hole of python3.5 rebuilds (working through the testtools chain)
20:55:49 <michaeleekk> abadger1999: according to this github readme, https://github.com/bastibe/lunatic-python, it seems the maintainer is not quite active. So Lupa, https://github.com/scoder/lupa, seems to be a separated project now
20:55:54 <abadger1999> SDyroff: in general yes.
20:56:11 <abadger1999> michaeleekk: cool.  I was meaning the fedora maintainer.
20:56:51 <michaeleekk> abadger1999: oh! okay~
20:57:57 <abadger1999> michaeleekk: that way they can choose to block python-lunatik and start maintaining python-Lupa... otherwise we'd have to find a new maintainer to get lupa packaged.
20:58:29 <michaeleekk> abadger1999: understood ;)
21:01:47 <fedmsg-python> 15github.pull_request.closed -- abadger closed pull request #44 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/44
21:02:16 <fedmsg-python> 15github.pull_request.closed -- abadger closed pull request #45 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/45
21:02:16 <fedmsg-python> 15github.push -- abadger pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/b7738cbaacff...72bbb0066c60
21:02:42 <fedmsg-python> 15github.push -- abadger pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/72bbb0066c60...3c95865fa119
21:02:43 <fedmsg-python> 15github.pull_request.closed -- abadger closed pull request #46 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/46
21:03:06 <fedmsg-python> 15github.pull_request.closed -- abadger closed pull request #47 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/47
21:03:07 <fedmsg-python> 15github.push -- abadger pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/3c95865fa119...8e15e51d89b4
21:03:17 <frafra> wow
21:05:24 <blackfile> .fas blackfile
21:05:25 <zodbot> blackfile: blackfile 'Luis Manuel Segundo' <luis@blackfile.net>
21:08:15 <potty> Welcome
21:08:48 <fedmsg-python> 15github.pull_request.synchronize -- rupe120 synchronized pull request #40 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/40
21:10:12 <fedmsg-python> 15github.push -- abadger pushed 3 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/8e15e51d89b4...84e4ebae82fa
21:10:21 <fitoria> Rupe: btw django-regsitration is going to make a new release
21:10:40 <fitoria> or did  a few days… let me check
21:10:41 <fitoria> one sec
21:10:58 <fedmsg-python> 15github.issue.comment -- abadger commented on issue #37 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/37#issuecomment-156746187
21:10:59 <Rupe> fitoria: everything passed, I was just going to set it has released
21:10:59 <fedmsg-python> 15github.pull_request.closed -- abadger closed pull request #37 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/37
21:11:19 <fitoria> aaa this is django-registration-redux
21:11:39 <fedmsg-python> 15github.pull_request.opened -- michaeleekk opened pull request #48 on fedora-python/portingdb: update lunatic-python status 10https://github.com/fedora-python/portingdb/pull/48
21:12:17 <abadger1999> Rupe: Your rebase of  https://github.com/fedora-python/portingdb/pull/40  has a .orig file -- should that just be deleted?  (I'll merge and do that if so)
21:12:19 <fitoria> https://twitter.com/ubernostrum/status/665001542919962624
21:12:40 <Rupe> fitoria: ya, sorry working on
21:12:46 <Rupe> it
21:14:21 <fedmsg-python> 15github.pull_request.synchronize -- rupe120 synchronized pull request #40 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/40
21:14:34 <abadger1999> Rupe: thanks!
21:14:39 <fedmsg-python> 15github.push -- abadger pushed 6 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/84e4ebae82fa...5909c04d64aa
21:14:40 <fedmsg-python> 15github.pull_request.closed -- abadger closed pull request #40 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/40
21:15:11 <fedmsg-python> 15github.pull_request.closed -- abadger closed pull request #48 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/48
21:15:12 <fedmsg-python> 15github.push -- abadger pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/5909c04d64aa...7d05cdd6a214
21:15:17 <fedmsg-python> 15github.push -- ralph pushed 1 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/7d05cdd6a214...4e867bd91507
21:16:08 <fedmsg-python> 15github.fork -- fitoria forked fedora-python/portingdb 10https://github.com/fitoria/portingdb
21:17:06 <fedmsg-python> 15github.push -- abadger pushed 1 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/4e867bd91507...838b11f320b8
21:17:37 <fedmsg-python> 15github.issue.comment -- abadger commented on issue #39 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/39#issuecomment-156746485
21:17:38 <fedmsg-python> 15github.pull_request.closed -- abadger closed pull request #39 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/39
21:20:32 <fedmsg-python> 15github.pull_request.opened -- fitoria opened pull request #49 on fedora-python/portingdb: updating status of python-printr 10https://github.com/fedora-python/portingdb/pull/49
21:21:22 <fedmsg-python> 15github.push -- abadger pushed 1 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/838b11f320b8...5287af6ea4ba
21:22:57 <fedmsg-python> 15github.create -- abadger created a new branch "pr/49" at fedora-python/portingdb 10https://github.com/fedora-python/portingdb
21:22:58 <fedmsg-python> 15github.push -- abadger pushed 1 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/commit/251f2abd08e7
21:23:14 <fedmsg-python> 15github.push -- abadger pushed 1 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/5287af6ea4ba...251f2abd08e7
21:23:23 <fedmsg-python> 15github.delete -- abadger deleted the "pr/49" branch at fedora-python/portingdb 10https://github.com/fedora-python/portingdb
21:23:24 <fedmsg-python> 15github.push -- abadger pushed 0 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/251f2abd08e7...000000000000
21:23:43 <fedmsg-python> 15github.issue.comment -- abadger commented on issue #49 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/49#issuecomment-156746964
21:23:44 <fedmsg-python> 15github.pull_request.closed -- abadger closed pull request #49 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/49
21:25:01 <potty> abadger1999
21:25:08 <abadger1999> hehe
21:25:11 <potty> I am working with python-di
21:25:18 <abadger1999> k
21:25:32 <potty> I ported it to Python 3 but how do I make the pull request there
21:25:44 <potty> It is on Fedora Git
21:26:35 * abadger1999 looking
21:28:27 <abadger1999> potty: okay, is it a big/intrusive patch or relatively straightforward?
21:28:38 <abadger1999> potty: If it's straightforward I can merge it to rawhide.
21:29:00 <potty> It is straightforward
21:29:01 <abadger1999> potty: otherwise best to open a bugzilla for it and attach the patch so that the maintainer can look at it.
21:29:08 <potty> O well
21:29:11 <abadger1999> potty: Cool... git commit, then git format-patch -1
21:29:21 <abadger1999> and then let me have the patch to apply.
21:29:30 <abadger1999> (Unless you're a provenpackager)
21:32:10 <potty> I am no provenpackager
21:32:16 <potty> Let me pass you the patch
21:32:43 <potty> abadger1999 through email?
21:33:01 <abadger1999> potty: pastebin is probably quickest.
21:33:31 <potty> Kk
21:33:43 <fedmsg-python> 15github.pull_request.opened -- sdyroff opened pull request #50 on fedora-python/portingdb: Updated wiki2beamer 10https://github.com/fedora-python/portingdb/pull/50
21:34:44 * decause dives back in
21:35:02 <abadger1999> SDyroff: Hey re: 50, is that the one that you wanted to run by the maintainer?
21:35:25 <SDyroff> abadger1999: no, that is my own package
21:35:29 <potty> abadger1999: here you go http://paste.fedoraproject.org/290569/
21:35:50 <abadger1999> SDyroff: if so, a link to the bugzilla that asks the maintainer for feedback would be great to add.
21:36:57 <SDyroff> abadger1999: added a link in 44
21:37:42 <fedmsg-python> 15github.pull_request.opened -- rupe120 opened pull request #51 on fedora-python/portingdb: working on python-django-extra-form-fields 10https://github.com/fedora-python/portingdb/pull/51
21:38:59 <abadger1999> SDyroff: okay, We don't need to enter it into the portingdb manually then, the next time the yum repo is updated we'll be able to sync the information automatically into the database.
21:39:17 <michaeleekk> potty: why not just remove the `if hasattr(func, "func_globals")` in the patch?
21:39:25 <SDyroff> abadger1999: Ok, sorry, didn't know of that
21:39:32 <abadger1999> No worries :-)
21:39:57 <SigmaWP> I just made an account and signed the contributor agreement
21:40:02 <SigmaWP> How do I proceed with the Python stuff?
21:40:10 <fedmsg-python> 15github.pull_request.closed -- sdyroff closed pull request #50 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/50
21:40:40 <fedmsg-python> 15github.issue.comment -- sdyroff commented on issue #50 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/50#issuecomment-156748057
21:40:50 <abadger1999> potty: ah -- I misunderstood.  That's changes to the upstream code base.  So we want to submit that upstream.
21:41:07 <potty> abadger1999: aja
21:41:26 <abadger1999> potty: I think this is the upstream source repo: https://github.com/lukasbuenger/python-di/
21:41:32 <abadger1999> So a pull reqeust there.
21:41:47 <abadger1999> potty: then we can link to the upstream pull request in the portingdb.
21:41:47 <potty> thanks
21:41:51 <abadger1999> de nada.
21:42:23 <abadger1999> SigmaWP: Pick a packge off of the posrtingdb app and see what it would take to port it.
21:42:44 <SigmaWP> Hmm
21:43:38 <abadger1999> SigmaWP: Some of them are there because the packaging doesn't include a python3 subpackage.  If you want to do rpm packaging work, I can help get you started with those or you can just send us PRs to the portingdb to update that information with upstream's status.
21:43:46 <abadger1999> SigmaWP: others require upstream porting.
21:44:34 <abadger1999> SigmaWP: So we have the list with dependency information which lets you select a high value package, but the work will really be porting code, submitting an upstream PR and then we'll wait for the change to trickle down into Fedora.
21:44:59 <fedmsg-python> 15github.pull_request.opened -- fitoria opened pull request #52 on fedora-python/portingdb: Adding info on python progressbar 10https://github.com/fedora-python/portingdb/pull/52
21:46:44 <fedmsg-python> 15github.issue.comment -- encukou commented on issue #23 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/issues/23#issuecomment-156748299
21:46:47 <abadger1999> Rupe, fitoria: note -- we're trying to keep that file in alphabetical order.
21:47:13 <Rupe> abadger1999: my bad, will do
21:47:20 <abadger1999> Cool.  thanks!
21:47:37 <potty> abadger1999: the link you sent me is different from the one specified on the package spec
21:47:46 <abadger1999> potty: hmm...
21:47:50 * abadger1999 checks out hte package spec
21:47:52 <potty> it is already functional with Python 3, but then the issue is on the package spec
21:48:05 <potty> abadger1999: https://apps.fedoraproject.org/packages/python-di/sources/spec/
21:50:03 <fedmsg-python> 15github.issue.comment -- encukou commented on issue #15 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/issues/15#issuecomment-156748439
21:50:22 <abadger1999> potty: okay... hmm... Yeah, it looks like fedorapeople is where we should submit upstream requests.
21:50:35 <fedmsg-python> 15github.pull_request.synchronize -- rupe120 synchronized pull request #51 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/51
21:50:54 <Rupe> abadger1999: fixed
21:51:28 <fedmsg-python> 15github.pull_request.closed -- abadger closed pull request #51 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/51
21:51:29 <fedmsg-python> 15github.push -- abadger pushed 3 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/251f2abd08e7...c8a6f73087a5
21:53:01 <abadger1999> Rupe: thanks!
21:53:39 <fedmsg-python> 15github.push -- ralph pushed 1 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/c8a6f73087a5...18b2c17fc615
21:54:26 <fedmsg-python> 15github.issue.comment -- rodrigc commented on issue #23 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/issues/23#issuecomment-156748618
21:54:39 <abadger1999> potty: I guess bugzilla.redhat.com is probably the best place.
21:54:54 <abadger1999> potty: the package maintainer seems to be the same as the upstream author so they should see it there.
21:56:14 <abadger1999> potty: if the patch you showed me earlier isn't needed and we just need to update the spec file I probably would be okay merging that.
21:56:19 * randomuser painfully extricates himself from the rabbit hole of openstack-related python packages
21:56:25 <abadger1999> (using provenpackager)
21:58:05 <threebean> Rupe: https://github.com/mitsuhiko/python-modernize
21:59:55 <potty> abadger1999: let me create a patch for the spec
22:00:50 <SigmaWP> How do I makr that I'm working on a package?
22:02:36 <fedmsg-python> 15github.push -- ralph pushed 1 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/18b2c17fc615...c36bacfdf19c
22:03:01 <threebean> SigmaWP: check out this blog post http://synfo.github.io/2015/10/14/Python3-Porting-Database/
22:03:32 <threebean> SigmaWP: short answer - there's that portingdb webapp.  fork it on github and add yourself to one or more data files and submit a pull request :)
22:03:39 <SigmaWP> ah
22:03:51 <threebean> abadger1999: just submitted a patch for python-mpd on rhbz btw :)
22:04:04 <fedmsg-python> 15github.fork -- Riamse forked fedora-python/portingdb 10https://github.com/Riamse/portingdb
22:10:13 <fedmsg-python> 15github.pull_request.opened -- rodrigc opened pull request #53 on fedora-python/portingdb: Put in alphabetical order 10https://github.com/fedora-python/portingdb/pull/53
22:10:54 <MSK61> SigmaWP: You can also record the package you're working on here https://titanpad.com/S3r8qX7OQJ.
22:11:09 <fedmsg-python> 15github.pull_request.synchronize -- fitoria synchronized pull request #52 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/52
22:11:26 <fedmsg-python> 15github.push -- ralph pushed 1 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/c36bacfdf19c...721cfabf6f6d
22:11:44 <fedmsg-python> 15github.pull_request.opened -- Riamse opened pull request #54 on fedora-python/portingdb: Doing stuff 10https://github.com/fedora-python/portingdb/pull/54
22:12:41 <SigmaWP> MSK61: Thanks
22:12:56 <SigmaWP> MSK61: Also, how many things do we need to port to get the badge? I have a bunch of midterms to study for >_>
22:13:49 <decause> randomuser++
22:13:49 <zodbot> decause: Karma for immanetize changed to 2 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
22:13:55 <threebean> SigmaWP: ha :D  I dunno.
22:16:04 <potty> abadger1999++
22:16:04 <zodbot> potty: Karma for toshio changed to 2 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
22:17:22 <frafra> abadger1999++
22:17:22 <zodbot> frafra: Karma for toshio changed to 3 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
22:17:54 <potty> :)
22:17:57 <potty> frafra+
22:17:59 <potty> frafra++
22:17:59 <zodbot> potty: Karma for frafra changed to 1 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
22:18:07 <potty> welcome :)
22:18:13 <threebean> SigmaWP: I bet 1 would do it.  also, don't fail your midterms!
22:18:26 <SigmaWP> thanks man
22:18:33 <threebean> SigmaWP: :)
22:18:36 <frafra> uh, thank you :)
22:18:42 <decause> SigmaWP: :)
22:18:43 <threebean> here's a graph of the portingdb activity!  https://apps.fedoraproject.org/datagrepper/charts/line?category=github&contains=portingdb&delta=28000
22:18:47 <decause> threebean++
22:18:47 <threebean> decause: ^^
22:18:51 <threebean> .tiny https://apps.fedoraproject.org/datagrepper/charts/line?category=github&contains=portingdb&delta=28000
22:18:52 <zodbot> threebean: http://tinyurl.com/phn2ku4
22:19:16 <frafra> potty++
22:19:16 <zodbot> frafra: Karma for potty changed to 1 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
22:19:26 <potty> threebean: great graph!
22:19:40 <frafra> mstuchli++
22:19:40 <zodbot> frafra: Karma for mstuchli changed to 2 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
22:19:52 <frafra> fitoria++
22:19:53 <zodbot> frafra: Karma for fitoria changed to 1 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
22:19:56 <frafra> voilà
22:20:31 <potty> fitoria++
22:20:31 <zodbot> potty: Karma for fitoria changed to 2 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
22:20:58 <fitoria> yei karma karma :) what can I do with it? :)
22:21:49 <frafra> fitoria: eat imaginary cookies :D
22:22:49 <abadger1999> https://badges.fedoraproject.org/badge/macaron-cookie-i
22:23:50 <potty> fitoria: it is a way to say thanks to the people
22:24:01 <fitoria> great :)
22:24:06 <potty> for example i thank you for coming to the event and do a good job :)
22:24:11 <frafra> ...with imaginary cookies :D
22:24:16 <potty> to give a cookie
22:24:23 <potty> just the fas_account++
22:25:36 <fedmsg-python> 15github.issue.comment -- encukou commented on issue #15 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/issues/15#issuecomment-156751363
22:26:46 <fedmsg-python> 15github.push -- ralph pushed 1 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/721cfabf6f6d...065decf7b2ec
22:26:57 <fedmsg-python> 15github.pull_request.opened -- rupe120 opened pull request #55 on fedora-python/portingdb: updated python-django-extra-form-fields status 10https://github.com/fedora-python/portingdb/pull/55
22:27:55 <fedmsg-python> 15github.issue.comment -- ralph commented on issue #15 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/issues/15#issuecomment-156751462
22:28:22 <fedmsg-python> 15github.issue.comment -- ralph commented on issue #55 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/55#issuecomment-156751483
22:28:24 <fedmsg-python> 15github.pull_request.closed -- ralph closed pull request #55 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/55
22:28:28 <fedmsg-python> 15github.push -- ralph pushed 3 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/065decf7b2ec...3b15665d616b
22:28:29 <fedmsg-python> 15github.pull_request.synchronize -- fitoria synchronized pull request #52 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/52
22:31:47 <fedmsg-python> 15github.issue.opened -- encukou opened issue #56 on fedora-python/portingdb: Get "in-progress" statuses for Fedora from Bugzilla 10https://github.com/fedora-python/portingdb/issues/56
22:33:00 <abadger1999> Hmm... I just tried running the dnf plugin to update the fedora.json file from the repository... Didn't seem to work right as it didn't capture the /usr/bin/python2 and /usr/bin/python3 dependencies.
22:33:14 <fedmsg-python> 15github.push -- encukou pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/3b15665d616b...e593871695fa
22:34:50 <fedmsg-python> 15github.push -- encukou pushed 1 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/e593871695fa...fce942fcf659
22:35:16 <fedmsg-python> 15github.push -- abadger pushed 8 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/fce942fcf659...7be7e5b6da69
22:35:16 <fedmsg-python> 15github.pull_request.closed -- abadger closed pull request #52 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/52
22:35:36 <fedmsg-python> 15github.pull_request.closed -- abadger closed pull request #53 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/53
22:35:37 <fedmsg-python> 15github.push -- abadger pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/7be7e5b6da69...8e933a895057
22:37:34 <fedmsg-python> 15github.issue.comment -- encukou commented on issue #54 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/54#issuecomment-156752195
22:38:35 <fedmsg-python> 15github.push -- ralph pushed 1 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/8e933a895057...581ba43284fc
22:40:18 <fedmsg-python> 15github.push -- encukou pushed 1 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/581ba43284fc...ed1c8c7bd324
22:43:30 <tonet666p> abadger1999, i found the solution (late because i'm begginer)
22:43:41 <abadger1999> cool.
22:43:44 <tonet666p> what's the next step?
22:43:52 <abadger1999> tonet666p: this is just a change to the spc file right?
22:44:11 <tonet666p> abadger1999, just the position of some lines
22:44:11 <abadger1999> tonet666p: *spec file
22:44:14 <abadger1999> <nod>
22:44:29 <abadger1999> tonet666p: okay, if you make me a patch I can apply it (since I'm i nthe provenpackager group)
22:44:37 <mayorga> fitoria++
22:44:37 <zodbot> mayorga: Karma for fitoria changed to 3 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
22:45:00 <mayorga> frafra++
22:45:01 <zodbot> mayorga: Karma for frafra changed to 2 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
22:45:17 <fedmsg-python> 15github.issue.comment -- encukou commented on issue #25 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/issues/25#issuecomment-156752508
22:46:17 <abadger1999> tonet666p: if you're working from a git checkout, you should be able to git commit your changes and then ; git format-patch -1 to generate a patch.
22:46:34 <fedmsg-python> 15github.issue.assigned -- encukou assigned issue #4 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/issues/4
22:47:59 <tonet666p> abadger1999, challenge accepted
22:48:23 <abadger1999> :-)
22:49:04 <fedmsg-python> 15github.issue.comment -- encukou commented on issue #25 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/issues/25#issuecomment-156752644
22:49:05 <fedmsg-python> 15github.issue.closed -- encukou closed issue #25 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/issues/25
22:51:45 <fedmsg-python> 15github.push -- ralph pushed 1 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/ed1c8c7bd324...5bad2c85342a
22:54:10 <abadger1999> potty: Were you going to get me a patch as well?
22:54:21 <potty> sorry abadger1999 got distracted
22:54:42 <abadger1999> non problem.  I just didn't want to forget about it if I promised you I'd look at merging it ;-)
22:54:49 <potty> i know
22:55:07 * potty have my first baby-girl a week and a day ago
22:55:23 <fedmsg-python> 15github.pull_request.opened -- fitoria opened pull request #57 on fedora-python/portingdb: Adds information for django-annoying, django-avatar, django-celery 10https://github.com/fedora-python/portingdb/pull/57
22:55:48 <decause> potty++
22:55:48 <zodbot> decause: Karma for potty changed to 2 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
22:55:53 <decause> super congrats!
22:56:02 <potty> decause: thank you very much
22:56:07 <fedmsg-python> 15github.pull_request.opened -- fabaff opened pull request #58 on fedora-python/portingdb: python-instant done 10https://github.com/fedora-python/portingdb/pull/58
22:56:30 <mstuchli> PyCon just ended and it's midnight here, I just looked at the portingdb commits and you guys are crazy awesome
22:56:57 <mayorga> :-)
22:57:01 <mstuchli> *PyCon talks :)
22:58:30 <threebean> talks_ending_at_midnight++
22:59:10 <mstuchli> A party was included :P
22:59:24 <threebean> ha!  good :P
23:00:40 <potty> awesome!
23:00:49 <SigmaWP> wait a second
23:00:56 <SigmaWP> if the dependencies for a project are marked as "dropped"
23:00:57 <fedmsg-python> 15github.push -- encukou pushed 1 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/5bad2c85342a...be49c78c54d6
23:01:05 <SigmaWP> does that mean that the project needs to be moved to python 2?
23:02:01 <frafra> :):)
23:02:23 <threebean> SigmaWP: if the deps are marked as dropped, then... something needs to happen :p
23:02:30 <SigmaWP> but
23:02:33 <SigmaWP> what does "dropped" mean
23:02:36 <SigmaWP> are we able to pick it up
23:02:47 <threebean> SigmaWP: either that package gets dropped too, or it gets ported to to use some new equivalent dep that itself is py3 compatible
23:02:55 <SigmaWP> oh
23:03:04 <threebean> SigmaWP: which package are you looking at?
23:03:09 <SigmaWP> do we still get the parselmouth badge if we mark something as dropped?
23:03:25 <SigmaWP> the package depends on pygobject2 and pygtk2 and python
23:03:33 * threebean cannot speak for the Parselmouth Overlords
23:03:41 <SigmaWP> aahh
23:03:57 <threebean> SigmaWP: can you link me to the package in the portingdb app?
23:04:12 <SigmaWP> https://portingdb-encukou.rhcloud.com/pkg/keybinder/
23:04:52 <threebean> ah ha!  so if you click on the pygtk2 and pygobject2 links
23:05:01 * potty is looking at Harry Potter and the Chamber of Secrets
23:05:13 <threebean> there's a note on both of them that says that dependant packages should be ported to use 'python-gobject' instead
23:05:25 <SigmaWP> aha
23:05:30 <threebean> SigmaWP: so, that's what would need to be done for keybinder to be ready for py3.
23:05:35 <SigmaWP> yay
23:05:41 <threebean> :)
23:06:29 <fedmsg-python> 15github.issue.comment -- encukou commented on issue #57 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/57#issuecomment-156754916
23:06:34 <fedmsg-python> 15github.pull_request.closed -- encukou closed pull request #57 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/57
23:06:35 <fedmsg-python> 15github.push -- encukou pushed 3 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/be49c78c54d6...d28eaec12b5c
23:06:55 <SigmaWP> threebean: so this implies that i have to mess with the .spec files?
23:08:03 <abadger1999> SigmaWP: probably code first and then once upstream has taken the changes, someone will update the .spec file.
23:08:07 <mstuchli> SigmaWP: The badge is about the effort, not necessarily the size of the achievements :)
23:08:37 <abadger1999> SigmaWP: There's probably a considerable amount of upstream porting to port from pygtk2 to python-gobject.
23:08:46 <fedmsg-python> 15github.pull_request.synchronize -- Riamse synchronized pull request #54 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/54
23:09:21 <fedmsg-python> 15github.issue.comment -- Riamse commented on issue #54 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/54#issuecomment-156755792
23:09:55 <SigmaWP> mmm
23:10:07 <tonet666p> abadger1999, i need commit the changes to this repo http://pkgs.fedoraproject.org/cgit/python-jsonpointer.git/ , right?
23:10:16 <abadger1999> tonet666p: correct
23:10:24 <tonet666p> ok
23:10:46 <abadger1999> tonet666p: Are you a fedora packager?  If so you can use fedpkg just like normal
23:10:55 <abadger1999> fedpkg clone python-jsonpointer
23:11:00 <tonet666p> abadger1999, yes, i'm
23:11:08 <tonet666p> ok
23:11:16 <fedmsg-python> 15github.pull_request.synchronize -- Riamse synchronized pull request #54 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/54
23:11:33 <abadger1999> make changes, git commit, then you have to git format-patch -1 instead of git push since you won't have permissions to push to that specific repo.
23:12:42 <frafra> mayorga: thanks :)
23:12:44 <frafra> mayorga++
23:12:45 <zodbot> frafra: Karma for mayorga changed to 1 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
23:14:18 <tonet666p> abadger1999, i get Permision denied when i clone with fedpkg
23:14:53 <fitoria> going out for a few hours, I’ll get back later tonight :)
23:15:02 <abadger1999> tonet666p: hmm.. try fedpkg clone --anonymous python-jsonpointer
23:15:57 <tonet666p> abadger1999, sucessful
23:16:30 <MSK61> Hello. I'm working on anjuta and I've found out that almost nothing in its sources should be changed to work with python3.
23:17:10 <MSK61> Python is mainly probed by autotools in the early stages of the build process. The build instructions in the spec file can be updated to specify python 3 explicitly.
23:18:59 <abadger1999> MSK61: k.  if there's nothing in code that needs changing and it can be done entirely in the spec file then it should be much easier.
23:19:22 <abadger1999> you can either make a patch to hte spc or open a bugzilla on bugzilla.redhat.com describing the changes.
23:19:32 <frafra> it's getting late for me :) good night and thank you!
23:19:37 * decause is aobut to clock out
23:19:38 <potty> threebean: are you there?
23:19:39 <abadger1999> (and then we can link to that bugzilla from the portingdb to make sure someone follows up later)
23:19:48 <abadger1999> frafra: thanks!
23:20:35 <MSK61> abadger1999: OK. I'll open a bug report on redhat bugzilla.
23:22:29 <threebean> potty: I am, but am about to take off for a while too :)
23:22:39 <frafra> oh, last thing
23:23:07 <potty> threebean: you own the package python-dopy, but its functionality only works for DO API v1.1 (currently deprecated)
23:23:17 <potty> threebean: should the package be orphaned?
23:23:25 <frafra> I was looking at fail2ban, and they don't seem really interested in Python 3; they prefer python 2.6: https://github.com/fail2ban/fail2ban/issues/1106
23:23:26 <threebean> oh!  no, I still use it.  I'll make sure to update it.
23:23:31 <threebean> potty: thanks for the tip!
23:23:46 <frafra> (I have no time now to do another merge request)
23:23:46 <frafra> bye ;)
23:24:13 <potty> threebean: you are welcome
23:25:14 <abadger1999> frafra: k
23:25:19 <abadger1999> I'll take care of it.
23:26:56 <SigmaWP> Gah
23:26:58 <SigmaWP> it's not working
23:27:20 <fedmsg-python> 15github.issue.comment -- Riamse commented on issue #54 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/54#issuecomment-156757913
23:27:57 <fedmsg-python> 15github.pull_request.closed -- Riamse closed pull request #54 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/54
23:28:01 <fedmsg-python> 15github.pull_request.reopened -- Riamse reopened pull request #54 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/54
23:30:19 <abadger1999> frafra: Looks like fail2ban does support python3 upstream.
23:30:33 <abadger1999> https://github.com/fail2ban/fail2ban/blob/master/README.md
23:31:36 <SigmaWP> threebean: oh, you're ralph
23:31:36 <SigmaWP> oops
23:31:56 <SigmaWP> the keybinder was exploding
23:32:55 <carlwgeorge> Howdy everyone, what can I do to help with the PY3 stuff?
23:32:59 <fedmsg-python> 15github.issue.comment -- Riamse commented on issue #54 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/54#issuecomment-156758113
23:33:00 <fedmsg-python> 15github.pull_request.closed -- Riamse closed pull request #54 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/54
23:33:31 <SigmaWP> Panic
23:33:50 <fedmsg-python> 15github.fork -- Riamse forked fedora-python/portingdb 10https://github.com/Riamse/portingdb
23:35:11 <fedmsg-python> 15github.push -- abadger pushed 1 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/d28eaec12b5c...6ef07e01a1c3
23:36:38 <fedmsg-python> 15github.pull_request.opened -- Riamse opened pull request #59 on fedora-python/portingdb: python-twiggy update 10https://github.com/fedora-python/portingdb/pull/59
23:39:11 <fedmsg-python> 15github.pull_request.synchronize -- Riamse synchronized pull request #59 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/59
23:40:34 <tonet666p> abadger1999, i have the patch
23:41:38 <SigmaWP> Damn it
23:41:49 <SigmaWP> All I want to do is convert C extensions to Python 3
23:41:55 <SigmaWP> Is there a filter for that on the website >.>
23:43:55 <abadger1999> tonet666p: cool,  Want to pastbin it?
23:44:42 <abadger1999> carlwgeorge: We have a list of packages to port (in some ways shape or form... some need to be ported upstream.  Others just need packaging work) here: http://portingdb-encukou.rhcloud.com/
23:45:12 <tonet666p> abadger1999, http://fpaste.org/290603/75447001/
23:46:54 <abadger1999> SigmaWP: we don't have a filter for that on the website :-(.  createrepo_c is a C extension, I think wxpython is as well (and that's blocking quite a few packages)
23:47:09 <carlwgeorge> Thanks abadger1999.  I'm interested in keystoneclient, it looks to be a blocker for lots of openstack stuff.  What I'm not able to tell from the website is the first step.
23:47:21 <SigmaWP> correction: c extensions that can be plausibly ported in less than a month >.>
23:47:31 <carlwgeorge> Should I contact the current maintainer and ask to be a co-maintainer?
23:47:37 * SigmaWP examines createrepo_c
23:48:57 <abadger1999> tonet666p: Cool.  I think that might be backwards though -- in fedora rawhide we want the defualt be to use the python3 version of hte script.
23:49:15 <abadger1999> tonet666p: So we probably should move the script to the python3 subpackage rather than making the script use /usr/bin/python2
23:49:37 <abadger1999> SigmaWP: threebean ahs started the port.  Did you see the link to his repo?
23:49:41 <SigmaWP> yeah
23:49:42 <SigmaWP> i see.
23:49:44 <abadger1999> Cool.
23:50:15 <abadger1999> carlwgeorge: First step is probably to see if there's anything going on upstream to port.
23:50:53 <abadger1999> carlwgeorge: If there isn't then putting forward some patches for upstream to look at merging is probably step 2.
23:51:11 <carlwgeorge> upstream has a trove for 3.4 support https://github.com/openstack/python-keystoneclient/blob/4a070903d29aca07a8d19b59bb20818d1c759c44/setup.cfg#L20
23:51:42 <carlwgeorge> I also use it with 3.5 on Arch with no issues
23:52:03 <abadger1999> carlwgeorge: ah -- if it already supports it then it could just be a matter of updating our package.. so yeah, you can ask to be a comaintainer -- you can also just work on the spec file to make it use python3 instead of python2 and then submit that in bugzilla.
23:52:56 <carlwgeorge> Excellent.  Thanks!
23:52:57 <abadger1999> carlwgeorge: and we can update the portingdb app to show that there's a patch in bugzilla to move the package to python3 (in case the maintainer doesn't take action on it someone who watches the app can followup on it later.)
23:53:22 <tonet666p> abadger1999, i have a poor english but i understand s/%{__python}/%{__python2}/, right?
23:53:55 <abadger1999> tonet666p: So the original spec file was installing hte script with /usr/bin/pytohn3 in the shebang.  So that was what we want.
23:54:10 <abadger1999> tonet666p: what it was doing wrong was adding that script to the python2 subpackage.
23:54:19 <abadger1999> tonet666p: So instead of having
23:54:20 <abadger1999> %files
23:54:28 <abadger1999> %{_bindir}/8
23:54:32 <abadger1999> %{_bindir}/*
23:54:45 <abadger1999> we want to take that out of %files
23:54:57 <abadger1999> and put it into %files python3-jsonpointer instead
23:56:06 <abadger1999> %files -n python3-jsonpointer
23:56:08 <abadger1999> %{_bindir}/jsonpointer
23:56:12 <abadger1999> Like that^
00:00:55 <fedmsg-python> 15github.fork -- carlwgeorge forked fedora-python/portingdb 10https://github.com/carlwgeorge/portingdb
00:03:00 <fedmsg-python> 15github.pull_request.synchronize -- Riamse synchronized pull request #59 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/59
00:03:11 <fedmsg-python> 15github.issue.comment -- Riamse commented on issue #59 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/59#issuecomment-156762517
00:05:13 <tonet666p> abadger1999, then, i only need to change one line
00:05:47 <abadger1999> tonet666p: yeah -- move one line to another section (and changelog, and bump release number)
00:06:22 <tonet666p> abadger1999, lol, i'm learning english too
00:07:01 <fedmsg-python> 15github.push -- abadger pushed 4 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/6ef07e01a1c3...bb79c7c2a890
00:07:02 <fedmsg-python> 15github.pull_request.closed -- abadger closed pull request #59 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/59
00:07:49 <abadger1999> :-)
00:13:57 <fedmsg-python> 15github.pull_request.opened -- carlwgeorge opened pull request #60 on fedora-python/portingdb: python-keystoneclient is PY3-ready upstream since 0.7.0 10https://github.com/fedora-python/portingdb/pull/60
00:14:50 <tonet666p> abadger1999, then, this is the new patch http://fpaste.org/290610/14475463/
00:15:17 <abadger1999> tonet666p: Cool.  Looks good.
00:15:25 * abadger1999 merges that into the package
00:16:57 <abadger1999> tonet666p: Building: http://koji.fedoraproject.org/koji/taskinfo?taskID=11841591
00:22:06 <fedmsg-python> 15github.pull_request.opened -- dperson opened pull request #61 on fedora-python/portingdb: Add notes that upstream fail2ban already supports Python3 10https://github.com/fedora-python/portingdb/pull/61
00:22:18 <tonet666p> is that all?
00:24:41 <rodrigc> abadger1999: how does someone submit patches to https://git.fedorahosted.org/git/kernel-tests.git
00:25:08 <abadger1999> rodrigc: Probably bugzilla.redhat.com
00:25:31 <abadger1999> and you can mention it in the portingdb so someone can make sure it gets followed to conclusion.
00:25:42 <abadger1999> tonet666p: Yep!  (just finished building successfully)
00:25:58 <abadger1999> tonet666p: It should go out to the yum repository tonight.
00:26:05 <tonet666p> ok, thank you abadger1999 (for your patience)
00:26:29 <tonet666p> i will go to my kitchen
00:26:32 <abadger1999> tonet666p: and then the next time encukou updates the app data from the yum repo it will show up as fixed.
00:26:47 <abadger1999> tonet666p: Quite welcome.  thank you for working on this ;-)
00:29:43 <rodrigc> abadger1999: I don't have an account on bugzilla.redhat.com
00:30:47 <rodrigc> I don't feel like making one.  Can someone with an account take a patch and submit it for me?
00:37:05 <fedmsg-python> 15github.pull_request.opened -- MSK61 opened pull request #62 on fedora-python/portingdb: anjuta fedora package in-progress 10https://github.com/fedora-python/portingdb/pull/62
00:43:22 <fedmsg-python> 15github.issue.comment -- dperson commented on issue #61 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/61#issuecomment-156765538
00:43:23 <fedmsg-python> 15github.pull_request.closed -- dperson closed pull request #61 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/61
00:46:35 <potty> rodrigc: ok
00:46:54 <rodrigc> potty: gimme a sec, I have a patch coming
00:58:17 <fedmsg-python> 15github.pull_request.opened -- dperson opened pull request #63 on fedora-python/portingdb: Add upstream support note for iotop 10https://github.com/fedora-python/portingdb/pull/63
01:10:17 <fedmsg-python> 15github.pull_request.synchronize -- dperson synchronized pull request #63 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/63
01:14:40 <rodrigc> potty: I have patches here: https://github.com/rodrigc/kernel-tests/tree/python3
01:21:39 <rodrigc> potty: can you open a bug at bugzilla.redhat.com ?
01:23:22 <potty> tell me more
01:23:24 <potty> about
01:23:35 <potty> what do you want me to put there
01:28:04 <rodrigc> potty: open a bug against  https://git.fedorahosted.org/git/kernel-tests.git , saying that you have patches to fix those scripts on Python 3
01:28:16 <rodrigc> and the patches are at: https://github.com/rodrigc/kernel-tests/tree/python3
01:29:26 <potty> ok
01:32:01 <rodrigc> potty: also, ask if the bug can be assigned to Justin M. Forbes <jforbes@redhat.com> , since he is doing all the commits to kernel-tests
01:33:41 <potty> ok
01:40:22 <fedmsg-python> 15github.pull_request.opened -- rodrigc opened pull request #64 on fedora-python/portingdb: m2crypto update 10https://github.com/fedora-python/portingdb/pull/64
01:41:11 <rodrigc> potty: did you open the bug?
01:42:48 <jflory7> Ooh, it'll be nice to see those scripts updated to Python3. The FAS log submission scripts never worked for me on Python 3.
01:43:12 <rodrigc> jflory7: where is the source code for FAS log submission scripts?
01:44:11 <jflory7> rodrigc: https://git.fedorahosted.org/cgit/kernel-tests.git/tree/fedora_submit.py
01:45:58 <rodrigc> jflory7: I have it: https://github.com/rodrigc/kernel-tests/blob/python3/fedora_submit.py
01:46:07 <jflory7> rodrigc++
01:46:14 <jflory7> Want me to test it?
01:49:04 <abadger1999> Okay guys, I'm heading out -- probably won't be here tomorrow so best of luck!
01:50:08 * potty going out too
01:50:12 <potty> bye
01:51:00 <jflory7> rodrigc: This is my current output using the script. http://pastebin.com/wv61bjGy
01:55:44 <potty> Yes
01:55:46 <rodrigc> jflory7: is that expected?
01:56:09 <jflory7> rodrigc: As far as I know, the script should automatically upload my logs to the kerneltest app.
01:56:18 <jflory7> So, I guess the answer is no.
01:56:39 <jflory7> Oh, wait
01:56:42 * jflory7 facepalms
01:56:46 <jflory7> It's running with Python 2
01:56:53 <jflory7> One second, rodrigc, let me re-run that again
01:56:57 <rodrigc> yeah but even with python 2, is that error expected?
01:57:05 <rodrigc> I want the script to work with python 2 or python 3
01:57:19 <jflory7> Nope, shouldn't be happening in Python 2 either.
01:57:42 <rodrigc> what is the unexpected openid provider?
02:01:17 <jflory7> rodrigc: Doesn't run in Python 3 either. http://paste.fedoraproject.org/290618/52791144
02:01:22 <jflory7> Umm, let me check
02:03:26 <jflory7> rodrigc: As far as I know, https://apps.fedoraproject.org/kerneltest/ is the site that the results should be uploaded to. But https://id.fedoraproject.org/ is the actual OpenID auth service.
02:04:37 <Benjami> !
02:04:54 <Benjami> Would like to join this initiative
02:06:11 <rodrigc> potty: where is the bug you filed?
02:06:39 <Benjami> I have some experience in python3 and would like to improve my skills by contributing
02:06:54 <Benjami> can someone help me get started ?
02:09:17 <jflory7> Benjami: I'm not specifically involved with the initiative, but are you familiar with the portingdb? :)
02:10:11 <Benjami> not so much.. whats is it about
02:10:30 <rodrigc> jflory7: do you have an account at bugzilla.redhat.com ?
02:10:35 <jflory7> rodrigc: I do.
02:10:57 <jflory7> Benjami: The portingdb is a database full of software that needs to be ported to Python 3. Let me dig up a link.
02:11:20 <Benjami> http://portingdb-encukou.rhcloud.com/
02:11:20 <fhansen> http://portingdb-encukou.rhcloud.com/ :)
02:11:23 <rodrigc> jflory7: can you add a commen to https://bugzilla.redhat.com/show_bug.cgi?id=1282133 and ask if the bug can be assigned to Justin M. Forbes <jforbes@redhat.com> , since he is doing all the commits to kernel-tests
02:11:24 <Benjami> would this be it
02:11:35 <jflory7> Benjami: See this wiki page for starters (https://fedoraproject.org/wiki/FAD_Python_3_Porting_2015). Scratchpad is here (https://titanpad.com/S3r8qX7OQJ).
02:11:44 <jflory7> Benjami, fhansen: That's it!
02:12:13 <Benjami> ahh.. ok let me check it out.. thanks jflory7, fhansen
02:12:26 <jflory7> rodrigc: Sure thing
02:15:56 <potty> rodrigc: https://bugzilla.redhat.com/show_bug.cgi?id=1282133
02:16:34 <rodrigc> potty: thanks
02:17:00 <fhansen> So, I noticed in that list that one of the packages that needs to be ported is libdmtx. I actually ported this earlier this year, but never bothered to even try to submit it upstream as the project hasn't been maintained since ~2013.
02:17:46 <fhansen> I'll fire an e-mail off to the author, but I won't hold my breath for a reply. :)
02:18:03 <jflory7> rodrigc: Added the comment.
02:18:16 <jflory7> Let me know if you need me to do more testing for the scripts.
02:20:43 <condor> hi, I'm back!  Examining this link  https://fedoraproject.org/wiki/Category:Package_Maintainers  is enlightening!
02:27:16 <condor> Becoming  maintainer is personal goal for me, but I can tell a fine piece Sqlite!  This portingdb is classy stuff, my hat is off to the authors.  I'm glad I stopped in this afternoon.
02:32:15 <Sr_Kraken-W> .fas srkraken
02:32:16 <zodbot> Sr_Kraken-W: srkraken 'Efren Antonio Robledo Moreno' <efren.a.rm@gmail.com>
02:32:28 * Sr_Kraken-W México
02:59:47 <jflory7> Welcome condor, thanks for stopping by. :)
03:00:02 <jflory7> And welcome to you too, srkraken!
03:04:55 <srkraken> hello people that can help
03:06:42 <jflory7> srkraken: Did you have any questions?
03:10:06 <wmoreno> ping
03:10:11 <wmoreno> today is the python3 FAD
03:10:18 <wmoreno> ?
03:11:20 <jflory7> Welcome wmoreno!
03:11:20 <fujimotos> yes.
03:11:35 <wmoreno> :)
03:11:49 <wmoreno> it is anything I can help?
03:11:56 <wmoreno> .fas williamjmorenor
03:11:56 <zodbot> wmoreno: williamjmorenor 'William Moreno' <williamjmorenor@gmail.com>
03:12:05 <wmoreno> .fasinfo williamjmorenor
03:12:06 <zodbot> wmoreno: User: williamjmorenor, Name: William Moreno, email: williamjmorenor@gmail.com, Creation: 2012-06-24, IRC Nick: williamjmorenor, Timezone: America/Managua, Locale: es, GPG key ID: , Status: active
03:12:09 <zodbot> wmoreno: Approved Groups: +packager docs cla_fpca cla_done ambassadors designteam freemedia videos fedorabugs fudcon +fedora-ni
03:12:27 <jflory7> wmoreno: Sure, have you seen the portingdb yet?
03:13:13 <jflory7> wmoreno: See this wiki page for starters (https://fedoraproject.org/wiki/FAD_Python_3_Porting_2015). Scratchpad is here (https://titanpad.com/S3r8qX7OQJ). The portingdb is the magical list of "things to be done". http://portingdb-encukou.rhcloud.com/
03:15:44 <wmoreno> thanks for the links
03:16:17 <wmoreno> I think i will statr with todocli than is a small package than I maintaing and have only python2 support
03:17:02 <wmoreno> Is it usefull if I do a check of packages with outdates specs than are not using the new python-provides macros?
03:18:36 <jflory7> wmoreno: I think so, but I'm not the best person to answer.
03:19:10 <wmoreno> well I will paste a link to the bug in the pad
03:19:14 <wmoreno> thanks
03:19:28 <jflory7> I know some of the active contributors have headed off to bed in their time zones now, so things have kind of slowed down for a bit right now. But there's a few lingering around right now, I think.
03:19:54 <jflory7> Things were definitely hopping earlier, mad amounts of PRs and issues being filed earlier!
03:20:27 <rodrigc> jflory7: thanks for your help
03:20:54 <jflory7> rodrigc: No problem. I'll be around for the next 30 minutes to an hour or so, if you need me to test any new changes, definitely let me know!
03:21:40 <rodrigc> jflory7: you comment is a bit wrong though.  Justin is not the maintainer of the kernel repo
03:21:52 <rodrigc> jflory7: he is the maintainer of the kernel-tests repo
03:22:00 <rodrigc> jflory7: big difference
03:22:54 <jflory7> Oops, thought I had said that. Will clarify.
03:24:18 <condor> jflory7:While friends were becoming Rubyists I was doing the abc's of SQL a few years back.  I'm working on getting git access and all the rest.  This is a great project to sink one's teeth into:
03:24:55 <rodrigc> jflory7: Justin maintains the kernel-tests at https://git.fedorahosted.org/git/kernel-tests.git , might want to mention that
03:25:06 <condor> It is long term and fundamentally important to community!   I gotta run!
03:27:46 <jflory7> rodrigc: Hmmm, I think the point will be made with my past comment, I don't want to spam the ticket with too many comments :p
03:28:56 <rodrigc> jflory7: it's OK, better to include the details in multiple comments, than to leave the bug with half accurate/confusing info
03:31:25 <fujimotos> If I know some package has already supported Python 3 in upstream, what should I do then? Just updating the "upstream.yaml" will be sufficient?
03:36:13 <rodrigc> fujimotos: yes
03:36:22 <fedmsg-python> 15github.fork -- mayorgatellez forked fedora-python/portingdb 10https://github.com/mayorgatellez/portingdb
03:36:36 <fedmsg-python> 15github.fork -- jflory7 forked fedora-python/portingdb 10https://github.com/jflory7/portingdb
03:37:02 <rodrigc> fujimotos: some people have done exactly that for other packages
03:39:37 <fujimotos> Thanks. I just wondered if I should take an additional step, like, notifing the mainteners of the packages.
03:40:08 <mayorga> wmoreno: http://synfo.github.io/2015/10/14/Porting-Database/
03:43:18 <fedmsg-python> 15github.pull_request.opened -- jflory7 opened pull request #65 on fedora-python/portingdb: Add kernel-tests to database 10https://github.com/fedora-python/portingdb/pull/65
03:50:20 <fedmsg-python> 15github.pull_request.opened -- mayorgatellez opened pull request #66 on fedora-python/portingdb: Updating status of python-pyprintr 10https://github.com/fedora-python/portingdb/pull/66
03:50:34 <zhaodi> Hello?
03:51:36 <SigmaWP> hi
03:52:27 <zhaodi> Sorry, this is my first time using irc. :x dont really know whats happening
03:54:44 <SigmaWP> heh
03:54:50 <SigmaWP> right back at you
03:55:35 <staranjeet> Hi all, I am Taranjeet
03:55:40 <SigmaWP> hhi
03:55:51 <staranjeet> and I am willing to work on porting Python2 code to Python3
03:55:55 <jflory7> Welcome zhaodi and staranjeet!
03:56:06 <jflory7> Have you both seen the resources for getting started?
03:56:13 <staranjeet> no
03:56:17 <jflory7> See this wiki page for starters (https://fedoraproject.org/wiki/FAD_Python_3_Porting_2015). Scratchpad is here (https://titanpad.com/S3r8qX7OQJ). The portingdb is the magical list of "things to be done". http://portingdb-encukou.rhcloud.com/
03:56:19 <staranjeet> i just saw this
03:56:21 <staranjeet> https://fedoramagazine.org/help-port-python-packages-python-3/
03:56:22 <zhaodi> Hello, jflort7
03:56:44 <jflory7> staranjeet: Awesome, well you are in the right place. :) Check out those links above to figure out what all is happening.
03:56:55 <staranjeet> ok let me check
03:57:26 <jflory7> Same goes to you, zhaodi. ^^ If either have any questions, feel free to ask. :)
03:57:52 <staranjeet> sure jflory7
03:58:05 <zhaodi> How experienced do u need to be to start?
03:58:45 <jflory7> zhaodi: The great thing about this is that anyone of any skill level can help with the porting. :) There are more experienced members of this FAD that can help you get started if you are still digging into Python.
03:59:08 <zhaodi> Thats great :D
04:22:54 <staranjeet> i have been through the wiki. @jflory7: how can i find the packages which needs to be ported
04:23:08 <staranjeet> i guess the list is here
04:23:09 <staranjeet> https://github.com/fedora-python/portingdb/issues/9#issuecomment-153654009
04:23:14 <jflory7> staranjeet: The portingdb is your best friend.
04:23:57 <staranjeet> in portingdb, idle packages?
04:24:03 <jflory7> staranjeet: I think this may have a couple of other things on it too. https://github.com/fedora-python/portingdb/blob/master/data/fedora-update.yaml
04:44:22 <staranjeet> how should i start if i have selected the package
05:02:02 <jflory7> staranjeet: From then on, I'm probably not the best person to ask. There's some much more knowledgeable people like threebean and others, but many of them went to bed in their timezones. In a few hours, some of the European ones should begin popping back in. :)
05:02:35 <jflory7> Things were hopping earlier today, but things have slowed down for a bit since many went to sleep.
05:03:28 <staranjeet> ok for now, i have found out the link to package
05:03:30 <fedmsg-python> 15github.pull_request_review_comment -- ralph commented on PR #65 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/65#discussion_r44867545
05:03:33 <staranjeet> https://github.com/lericson/pylibmc
05:05:10 <fedmsg-python> 15github.pull_request.closed -- ralph closed pull request #58 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/58
05:05:12 <fedmsg-python> 15github.push -- ralph pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/bb79c7c2a890...fc0b33dafdbf
05:05:38 <fedmsg-python> 15github.pull_request.closed -- ralph closed pull request #60 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/60
05:05:39 <fedmsg-python> 15github.push -- ralph pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/fc0b33dafdbf...e4e08cf7d042
05:05:59 <fedmsg-python> 15github.push -- ralph pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/e4e08cf7d042...45f1c807eff5
05:06:00 <fedmsg-python> 15github.pull_request.closed -- ralph closed pull request #62 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/62
05:06:07 <staranjeet> sure i will wait fr them
05:06:25 <fedmsg-python> 15github.pull_request.closed -- ralph closed pull request #63 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/63
05:06:29 <fedmsg-python> 15github.push -- ralph pushed 6 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/45f1c807eff5...88c56560a9e3
05:07:05 <fedmsg-python> 15github.pull_request.closed -- ralph closed pull request #66 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/66
05:07:06 <fedmsg-python> 15github.push -- ralph pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/88c56560a9e3...0b140667ca99
05:08:18 <threebean> staranjeet: for pylibmc, it looks like they already support python3 upstream
05:08:26 <threebean> staranjeet: see the 'tox.ini' file here?  https://github.com/lericson/pylibmc/blob/master/tox.ini
05:08:42 <fedmsg-python> 15github.pull_request.synchronize -- jflory7 synchronized pull request #65 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/65
05:09:04 <staranjeet> ohh
05:09:09 <threebean> so, if you can verify that the tests actually pass on py3, that's great.
05:09:21 <threebean> you can 1) update the data/upstream.yml file in the portingdb app to say that upstream does in fact already support python3
05:09:49 <fedmsg-python> 15github.issue.comment -- jflory7 commented on issue #65 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/65#issuecomment-156781813
05:10:01 <threebean> and if you are a fedora packager, you can 2) update the fedora .spec file for pylibmc to add a python3 subpackage. and then after that 3) update the fedora status in data/fedora-update.yml
05:10:41 <fedmsg-python> 15github.issue.comment -- ralph commented on issue #65 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/65#issuecomment-156782090
05:10:46 <fedmsg-python> 15github.pull_request.closed -- ralph closed pull request #65 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/65
05:10:47 <fedmsg-python> 15github.push -- ralph pushed 3 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/0b140667ca99...4e75d213316d
05:11:24 <jflory7> threebean++
05:11:24 <zodbot> jflory7: Karma for ralph changed to 9 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
05:11:26 <jflory7> Still going!
05:12:21 <threebean> :D
05:12:39 <threebean> but I'm off to bed for the night now.  will catcha tomorrow!
05:14:47 <jflory7> Night, threebean!
05:20:36 <wmoreno> todocli is done
05:20:38 <wmoreno> http://koji.fedoraproject.org/koji/rpminfo?rpmID=6990778
05:20:40 <wmoreno> :)
05:20:46 <wmoreno> I sent the patch upstream
05:25:35 <wmoreno> Some of my packages did build with python3.5 in rawhide, i will work on it
05:30:23 <jflory7> wmoreno++
05:30:24 <jflory7> Nice work!
05:35:28 <wmoreno> thanks
05:35:32 <wmoreno> :)
05:46:12 <wmoreno> my fas is williamjmoreno jflory7
05:46:25 <jflory7> williamjmoreno++
05:46:34 <jflory7> williamjmorenor++
05:46:34 <zodbot> jflory7: Karma for williamjmorenor changed to 1 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
05:46:35 <jflory7> ?
05:46:38 <jflory7> There we go :)
05:46:54 <williamjmorenor> jflory7++
05:46:54 <zodbot> williamjmorenor: Karma for jflory7 changed to 10 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
05:47:09 <jflory7> Cookies for everyone!!!
05:47:14 <williamjmorenor> mayorga++
05:47:14 <zodbot> williamjmorenor: Karma for mayorga changed to 2 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
05:47:20 <williamjmorenor> potty++
05:47:21 <zodbot> williamjmorenor: Karma for potty changed to 3 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
05:47:23 <williamjmorenor> :)
05:56:18 <srkraken> jflory++
05:56:28 <srkraken> jflory7++
05:56:29 <zodbot> srkraken: Karma for jflory7 changed to 11 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
05:56:42 <jflory7> Woohoo :)
05:57:28 <srkraken> williamjmorenor++
05:57:28 <zodbot> srkraken: Karma for williamjmorenor changed to 2 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
05:58:20 <srkraken> potty++
05:58:20 <zodbot> srkraken: Karma for potty changed to 4 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
05:58:43 <srkraken> echevemaster++
05:58:43 <zodbot> srkraken: Karma for echevemaster changed to 1 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
05:59:33 <srkraken> tonet666p++
05:59:33 <zodbot> srkraken: Karma for tonet666p changed to 1 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
06:00:14 <srkraken> danielbruno++
06:00:14 <zodbot> srkraken: Karma for dbruno changed to 1 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
06:00:48 * jflory7 is going to head out for the evening now.
06:03:59 <srkraken> creaturahpc++
06:03:59 <zodbot> srkraken: Karma for creaturahpc changed to 1 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
06:04:22 * srkraken karma for my friends in Latam
06:04:52 <williamjmorenor> srkraken++
06:04:52 <zodbot> williamjmorenor: Karma for srkraken changed to 1 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
06:05:26 <williamjmorenor> hola efren como estas? srkraken
06:05:41 <srkraken> Bien williamjmorenor
06:06:46 <fedmsg-python> 15github.fork -- staranjeet forked fedora-python/portingdb 10https://github.com/staranjeet/portingdb
06:07:20 <srkraken> williamjmorenor Como va la migracion ???
06:08:12 <williamjmorenor> pase un paquete sencillo que se llama todocli, pero algunos de mis paquetes fallaron con python3.5 en rawhide y estoy recompilandolos
06:08:23 <williamjmorenor> vi que te gustaria ser empaquetador
06:08:28 <williamjmorenor> yo puedo ayudarte en eso
06:09:10 <srkraken> si compa yo quiero se empaquetador
06:19:40 <williamjmorenor> ok
06:19:44 <williamjmorenor> veamos eso entonces
06:22:18 <srkraken> williamjmorenor +1
06:53:29 <williamjmorenor> I am going to sleep, good nigth and happy hacking
07:04:02 <fedmsg-python> 15github.pull_request.opened -- staranjeet opened pull request #67 on fedora-python/portingdb: info updated about pylibmc 10https://github.com/fedora-python/portingdb/pull/67
07:23:11 <bkabrda> hi everyone!
07:23:20 <mhroncok> good morning
07:23:45 <staranjeet> morning!
07:24:26 <mhroncok> staranjeet: about pylibmc, will you make sure fedora ships python3 subpackage?
07:25:25 <staranjeet> and how can i make sure that?
07:26:30 <mhroncok> staranjeet: are you a python packager?
07:26:33 <mhroncok> sorry
07:26:38 <mhroncok> fedora packager?
07:26:46 <staranjeet> no
07:27:00 <staranjeet> i have started contributing to fedora today only
07:30:17 <mhroncok> staranjeet: you can file a bug in bugzilla on that package, linking to upstream information about python3 compatibility
07:30:25 * mstuchli waves, in shame
07:30:42 <mhroncok> staranjeet: do you know how to do that, or should I guide you?
07:31:00 <mhroncok> mstuchli: woke up now?
07:31:41 <mstuchli> I should be there in ~15 minutes :)
07:31:48 <mstuchli> And yeah, just about now :(
07:33:32 <staranjeet> i guess it involves creating a new bug at bugzilla.redhat?
07:35:53 <staranjeet> https://bugzilla.redhat.com/show_bug.cgi?id=1282161
07:35:57 <staranjeet> is this ok?
07:38:08 <mhroncok> staranjeet: almost. It's good to provide some links to actuall evidence that the upstream works with python 3
08:39:50 <fedmsg-python> 15github.fork -- QuLogic forked fedora-python/portingdb 10https://github.com/QuLogic/portingdb
08:43:18 <fedmsg-python> 15github.pull_request.opened -- QuLogic opened pull request #68 on fedora-python/portingdb: Add upstream status of several scientific packages. 10https://github.com/fedora-python/portingdb/pull/68
08:52:44 <frafra> morning! :D
08:54:30 <frafra> pbrobinson: hi; are you working on autotrash?
08:55:40 <pbrobinson> frafra: sorry, context?
08:56:40 <frafra> <fedora-notifs> pbrobinson's autotrash-0.1.5git1e3c902-1.fc24 completed (arm) seconds ago
08:57:07 <frafra> ~30 minutes ago
08:57:14 <pbrobinson> frafra: that's aarch64 builds, it's part of koji-shadow builds I suspect
08:58:06 <frafra> pbrobinson: ok, so it's an automatic procedure, right?
09:00:49 <pbrobinson> frafra: pretty much
09:02:09 <frafra> thank you
09:06:32 <fedmsg-python> 15github.push -- churchyard pushed 1 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/4e75d213316d...a88ac0362d90
09:08:34 <fedmsg-python> 15github.issue.opened -- sYnfo opened issue #69 on fedora-python/portingdb: Add the various Fedora spins to Package Groups 10https://github.com/fedora-python/portingdb/issues/69
09:27:01 <frafra> hi jpigface :)
09:27:09 <jpigface> frafra: buongiorno!
09:29:13 <jpigface> frafra: metto subito tra le news il FAD di python
09:36:13 <fedmsg-python> 15github.issue.opened -- churchyard opened issue #70 on fedora-python/portingdb: In-progress things stay in-progress until deleted form yamls 10https://github.com/fedora-python/portingdb/issues/70
09:36:14 <fedmsg-python> 15github.issue.labeled -- churchyard labeled issue #70 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/issues/70
09:37:48 <jpigface> frafra: oh, I've just noticed we're in the international channel and not in the italian one. My apologies
09:37:54 <frafra> ;)
09:43:22 <ignatenkobrain> hey hey
09:43:24 <ignatenkobrain> how its going?
09:43:35 <frafra> I almost finished with autotrash... silly docbook-to-man
09:43:42 <ignatenkobrain> is FAD still going?
09:43:50 <frafra> well, thank you :) yes!
09:44:09 <mstuchli> ignatenkobrain: It is! :)
09:44:17 <ignatenkobrain> mstuchli: cool! how I can hepl?
09:44:21 <ignatenkobrain> help
09:44:31 <mstuchli> We've started a while ago, as part of the PyCon sprints
09:44:36 <mstuchli> Have you been here yesterday?
09:44:41 <ignatenkobrain> nope
09:44:42 <jpigface> ignatenkobrain: have you read this? http://synfo.github.io/2015/10/14/Porting-Database/
09:44:53 <ignatenkobrain> I'm not attending pyconcz
09:44:55 <mstuchli> ^
09:44:57 <ignatenkobrain> =(
09:45:00 <mstuchli> That's fine!
09:45:10 <mstuchli> It's jus that there's a bunch of people doing the FAD here :)
09:48:02 <ignatenkobrain> I did some stuff for py3 last days =)
09:48:08 <ignatenkobrain> I mean with porting
10:00:43 <potty> Hello mstuchli
10:00:47 <potty> Good evening from Panama
10:00:53 <potty> Its 5AM here
10:01:08 <frafra> welcome back potty :)
10:01:20 <potty> Hi frafra
10:03:40 <tyll_> frafra: are you working on an update for the youtube-dl spec?
10:06:02 <frafra> tyll: actually no, please go
10:06:20 <frafra> I just created the issue on bugzilla
10:07:07 <frafra> I'm releaseing an update of autotrash, so I can move on something else
10:07:35 <tyll> frafra: yes, I saw it - I planned to look at youtube-dl as part of the FAD anyhow and saw that you also assigned it to you in the etherpad
10:08:58 <frafra> tyll: sorry, I'll try to add more infos to the pad, in order to be clear what I'm doing/what I've done :D
10:09:20 <tyll> frafra: btw. it might be helpful to make the python3 support conditionalized so the same spec can be used for all releases and EPEL
10:10:37 <frafra> tyll: oh, ok; so, epel + f23 and lower -> py2, everything else -> py3?
10:13:59 <tyll> frafra: I guess python3 might be ok for f23 as well - at least I was planning to do it for youtube-dl unless there are guidelines against switching the python version in a release
10:15:07 <tyll> I wonder if ther is a rpm switch to make the %python macros to be python3 instead of python2
10:15:25 <frafra> yes, I saw it
10:15:38 <frafra> let me check
10:17:34 <frafra> %{!?__python2: %global __python2 /usr/bin/python2}
10:17:47 <frafra> I think you can use something like this for __python too
10:17:49 <frafra> like...
10:18:05 <frafra> %{!?__python3: %global __python /usr/bin/python3}
10:19:02 <frafra> %{!?__python3: %global __python %{__python3}} <- I don't know it this works
10:22:03 <tyll> frafra: I will take a look later, I got to prepare food now
10:22:16 <frafra> ok
10:23:20 <frafra> mmm... youtube-dl has no Requires: python
10:26:02 <frafra> https://fedoraproject.org/wiki/Packaging:Python#Macros
10:30:21 <mstuchli> frafra: Could I have a link to that etherpad?
10:30:44 <mstuchli> tyll: There are no guidelines preventing you from switch python version AFAIK :)
10:30:54 <mstuchli> frafra: What are those macro definitions supposed to do?
10:32:03 <tomspur> mstuchli: Why do you do mass bug filling about the python_provide macro and not let just provenpackager fix it?
10:32:52 * tomspur has that on his list actually. Now when one needs to touch many packages anyway to fix the broken deps in rawhide :)
10:32:57 <mstuchli> tomspur: Sorry what? I did not do any mass filing, unless I did that while sleep walking :)
10:33:01 <rkuska> tomspur: we havent done any mass bug filling
10:33:50 <tomspur> Ah, it wasn't you ;)
10:33:52 <tomspur> .bug 1282146
10:33:53 <zodbot> tomspur: Bug 1282146 Packages with outdated spec (not using python-provides macro, not python2 subpackages) - https://bugzilla.redhat.com/1282146
10:34:05 <mstuchli> tomspur: Yeah, I was confused about that as well
10:34:23 <frafra_web> ops, I'm back
10:35:26 <frafra_web> what we should do with python apps? just moving them to py3 or should we use macros and if in order to build them with python 2 with older fedora and/or epel?
10:35:56 <rkuska> wimby: http://portingdb-encukou.rhcloud.com/
10:36:26 <rkuska> wimby: http://synfo.github.io/page2/
10:40:56 <mstuchli> frafra_web: The Python 3 in epel isn't in a great shave AFAIK, so if the app is there, you should prolly use if's for sure
10:41:24 <frafra_web> mstuchli: so, py3 for everything except epel
10:42:11 <frafra_web> py3 even for f21/f22, right?
10:42:16 <mstuchli> Hmmm
10:42:42 <mstuchli> I'd say yes, folks around me say no :)
10:42:48 <frafra_web> heheehhe
10:43:05 <frafra_web> f23 and greater -> py3, everything else py2?
10:43:15 <mstuchli> That sounds reasonable :)
10:43:37 <frafra_web> I would like to give you more cookies :D
10:44:50 <frafra_web> what about the default __python macro: it points to /usr/bin/python; should we avoid it and specify the python version? should we change every shebang in order to have python2 or python3 but not python?
10:45:58 <mstuchli> frafra_web: Definitely yes and yes! :)
10:46:29 <frafra_web> mstuchli: ok, really really thank you :)
10:46:31 <tomspur> I see "python" as the current default one. So if people want to switch with the default python, it's fine to
10:51:36 <fedmsg-python> 15github.push -- sYnfo pushed 1 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/commit/1b477b1fc63e
10:51:37 <fedmsg-python> 15github.create -- sYnfo created a new branch "spins_groups" at fedora-python/portingdb 10https://github.com/fedora-python/portingdb
10:51:57 <fedmsg-python> 15github.pull_request.opened -- sYnfo opened pull request #71 on fedora-python/portingdb: [groups] Add KDE and Xfce spins 10https://github.com/fedora-python/portingdb/pull/71
10:58:58 <fedmsg-python> 15github.push -- churchyard pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/a88ac0362d90...b987cdb17911
10:58:59 <fedmsg-python> 15github.pull_request.closed -- churchyard closed pull request #71 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/71
10:59:13 <fedmsg-python> 15github.pull_request.opened -- fabaff opened pull request #72 on fedora-python/portingdb: Add jabber-roster 10https://github.com/fedora-python/portingdb/pull/72
11:01:32 <faffolter> is portingdb updated manually? it seems that i'm still looking at the same data as 12 hours ago
11:07:46 <frafra_web> http://paste.fedoraproject.org/290711/75856431 <- spec file for an universal py2/py3 app; is it ok?
11:09:22 <frafra_web> I don't know if it's possible to change %py_build in order to build for 2 or 3, but vars are easy to change globally
11:10:01 <fedmsg-python> 15github.pull_request.closed -- sYnfo closed pull request #67 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/67
11:10:02 <fedmsg-python> 15github.push -- sYnfo pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/b987cdb17911...72f0ad078b54
11:10:08 <fedmsg-python> 15github.issue.comment -- sYnfo commented on issue #67 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/67#issuecomment-156802505
11:14:52 <frafra_web> %if 0%{?fedora} >= 23 || 0%{?rhel} > 7
11:15:09 <frafra_web> it should be ok, I suppose
11:15:52 <Son_Goku> yeah, that’s fine
11:16:11 <frafra_web> thank you Son_Goku
11:16:20 <Son_Goku> it’s generally assumed that Red Hat won’t leave out Python 3 for yet another RHEL release
11:17:04 <Son_Goku> they may even provide it in RHEL 7 in the future, but that’s not our problem atm
11:17:14 <Son_Goku> if that turns out to happen, they’ll fix it
11:17:18 <Son_Goku> … hopefully
11:17:38 * Son_Goku doesn’t even understand why it was left out of RHEL 7 at all
11:24:17 <dperson> @Son_Goku that is crazy, I knew that it wasn't in our default server builds at work, but didn't realize it wasn't in the repos (we're just finally rolling out 7, sigh)
11:25:00 <Son_Goku> dperson: it’s in EPEL, though *sigh*
11:25:24 <Son_Goku> which technically means it could be ripped out of EPEL and put into the core as soon as more packages are available that work with it
11:25:46 <Son_Goku> that’s what happened with cmake and a bunch of other packages in RHEL 6, anyway
11:26:35 <Son_Goku> dperson: if you have a Red Hat subscription, bang on them to actually get Py3 into the core
11:26:50 <Son_Goku> because it’s annoying having it essentially impossible to depend on...
11:27:20 <dperson> @Son_Goku Yes, but my corporate overlords don't want EPEL to be intsalled. I'm just a sysadmin.
11:27:30 <Son_Goku> exactly
11:27:43 <Son_Goku> that’s why banging on Red Hat to include it in the core is important
11:28:19 <dperson> I'll do what I can
11:28:34 <Son_Goku> ffs, they’re already planning on upgrading GNOME to 3.18 in RHEL 7.3!
11:28:52 <Son_Goku> and introducing Wayland, and a bunch of other things
11:29:17 <Son_Goku> now if only they’d also introduce Plasma 5 too...
11:39:12 <fedmsg-python> 15github.pull_request.opened -- dperson opened pull request #73 on fedora-python/portingdb: Fix typo in speedtest-cli upstream.yaml 10https://github.com/fedora-python/portingdb/pull/73
11:44:28 <frafra> mmm... when you have a mass rebuild in f23, do you execute a simple merge in f22 or you try to remove the mass rebuild commit because it's not related with the f22 branch?
11:53:58 <fedmsg-python> 15github.pull_request.synchronize -- dperson synchronized pull request #73 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/73
11:57:14 <fedmsg-python> 15github.pull_request.synchronize -- fabaff synchronized pull request #72 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/72
12:03:21 <fedmsg-python> 15github.pull_request.closed -- fabaff closed pull request #72 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/72
12:04:23 <fedmsg-python> 15github.fork -- fabaff forked fedora-python/portingdb 10https://github.com/fabaff/portingdb
12:04:42 <mhroncok> http://blog.spreedly.com/2014/06/24/merge-pull-request-considered-harmful/
12:06:54 <fedmsg-python> 15github.pull_request.opened -- fabaff opened pull request #74 on fedora-python/portingdb: Add jabber-roster 10https://github.com/fedora-python/portingdb/pull/74
12:08:13 <fedmsg-python> 15github.pull_request.opened -- fabaff opened pull request #75 on fedora-python/portingdb: Add btest 10https://github.com/fedora-python/portingdb/pull/75
12:14:18 <frafra> autotrash finished: bodhi updates pushed
12:16:39 <frafra> mhroncok: really interesting, thank you
12:23:50 <frafra> http://portingdb-encukou.rhcloud.com/pkg/greylistd/ requires python, but there's no python code, it's just perl
12:23:53 <frafra> how could it be?
12:24:25 <Son_Goku> does it exec python?
12:32:01 <frafra> Son_Goku: it doesn't seem so... but I've just seen that I can't download the sourcecode using spectool
12:32:14 <Son_Goku> :S
12:39:09 <fedmsg-python> 15github.fork -- booxter forked fedora-python/portingdb 10https://github.com/booxter/portingdb
12:41:10 <fedmsg-python> 15github.pull_request.opened -- booxter opened pull request #76 on fedora-python/portingdb: Added crudini status 10https://github.com/fedora-python/portingdb/pull/76
13:00:36 <fedmsg-python> 15github.pull_request.opened -- frafra opened pull request #77 on fedora-python/portingdb: libssh2-python added 10https://github.com/fedora-python/portingdb/pull/77
13:20:10 <Son_Goku> it looks like getting repoview to py3 is going to be annoying
13:20:21 <Son_Goku> I can’t even find the website for the kid templating engine
13:23:18 <ardian> Hello, I am a beginner in Python is anything I can help for the FAD ? my region is EMEA
13:24:35 <frafra> hi ardian, I'm from EMEA too :)
13:24:44 <frafra> there are many tasks to accomplish
13:25:01 <frafra> https://communityblog.fedoraproject.org/help-port-python-packages-to-python-3/
13:25:14 <frafra> https://titanpad.com/S3r8qX7OQJ
13:26:17 <ardian> frafra: Thank you, let me take a look.
13:26:25 <frafra> ardian: you're welcome :)
13:27:37 <tyll> btw. can someone add the FAD links to the channel's topic?
13:29:38 <michaeleekk> Seems like the titanpad link got all the info everyone needs ;) https://titanpad.com/S3r8qX7OQJ
13:29:55 <lupinix> hi all
13:39:26 <faffolter> is '%py3_install' including different flags than 'CFLAGS="%{optflags}" %{__python3} setup.py build'?
13:48:35 <potty> Bot does not allow
13:48:48 <potty> Tried yesterday twice
14:08:56 <fedmsg-python> 15github.issue.comment -- sYnfo commented on issue #77 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/77#issuecomment-156814003
14:08:59 <fedmsg-python> 15github.pull_request.closed -- sYnfo closed pull request #77 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/77
14:09:00 <fedmsg-python> 15github.push -- sYnfo pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/72f0ad078b54...ddd9cb3e7a01
14:09:21 <fedmsg-python> 15github.issue.comment -- sYnfo commented on issue #76 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/76#issuecomment-156814018
14:09:22 <fedmsg-python> 15github.pull_request.closed -- sYnfo closed pull request #76 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/76
14:09:23 <fedmsg-python> 15github.push -- sYnfo pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/ddd9cb3e7a01...ada8d77c1fcb
14:10:01 <fedmsg-python> 15github.pull_request.closed -- sYnfo closed pull request #73 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/73
14:10:02 <fedmsg-python> 15github.push -- sYnfo pushed 3 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/ada8d77c1fcb...1f738e777420
14:11:03 <fedmsg-python> 15github.push -- sYnfo pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/1f738e777420...7c7475d578a0
14:11:04 <fedmsg-python> 15github.pull_request.closed -- sYnfo closed pull request #75 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/75
14:11:27 <RaphGro> ?
14:12:07 <fedmsg-python> 15github.issue.comment -- sYnfo commented on issue #74 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/74#issuecomment-156814129
14:24:26 <potty> #chairs
14:24:43 <zodbot> potty: Error: Can't start another meeting, one is in progress.
14:25:06 <potty> Sorry. Just verifying everthing is all good.
14:25:13 <frafra> :)
14:28:30 <jflory7> All those GitHub notifications are awesome to see :)
14:35:19 <potty> Indeed
14:35:37 <potty> That way is an evidence of this great effort
14:35:43 <fedmsg-python> 15github.pull_request.opened -- frafra opened pull request #78 on fedora-python/portingdb: python-bash8 added 10https://github.com/fedora-python/portingdb/pull/78
14:38:35 <michaeleekk> If a package supports py3.3+, should be good?
14:40:02 <frafra> f23 has python 3.4; it should be ok if you don't plan to port it on older releases
14:41:19 <michaeleekk> Okay, because i saw a package, http://portingdb-encukou.rhcloud.com/pkg/python-ipaddress/, that has a 2.6 - 3.2 alternative. And 3.3 supports native from stdlib. Maybe I will suggest alternatives ;)
14:42:57 <frafra> many packages are 3.3+ because during 3.0-3.2 they changed many things
14:43:22 <michaeleekk> I see..
14:58:14 <fedmsg-python> 15github.issue.comment -- sYnfo commented on issue #78 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/78#issuecomment-156816203
14:58:34 <fedmsg-python> 15github.issue.comment -- fabaff commented on issue #74 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/74#issuecomment-156816219
14:59:25 <RaphGro> python3.5 is in rawhide, I got some rebuilds of my packages.
15:02:34 <fedmsg-python> 15github.issue.comment -- frafra commented on issue #78 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/78#issuecomment-156816396
15:07:52 <fedmsg-python> 15github.pull_request.opened -- fabaff opened pull request #79 on fedora-python/portingdb: Add python-restsh 10https://github.com/fedora-python/portingdb/pull/79
15:13:58 <fedmsg-python> 15github.issue.comment -- sYnfo commented on issue #78 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/78#issuecomment-156817078
15:21:51 <fedmsg-python> 15github.fork -- tyll forked fedora-python/portingdb 10https://github.com/tyll/portingdb
15:25:32 <fedmsg-python> 15github.issue.comment -- frafra commented on issue #78 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/78#issuecomment-156817899
15:41:07 <fedmsg-python> 15github.pull_request.opened -- tyll opened pull request #80 on fedora-python/portingdb: youtube-dl is on its way to Rawhide 10https://github.com/fedora-python/portingdb/pull/80
15:51:29 <tyll> .fasinfo sergiopr
15:51:30 <zodbot> tyll: User: sergiopr, Name: Sergio Pascual, email: sergio.pasra@gmail.com, Creation: 2006-03-07, IRC Nick: , Timezone: Europe/Madrid, Locale: en, GPG key ID: 2BE83718, Status: active
15:51:33 <zodbot> tyll: Approved Groups: cla_done cla_fedora fedorabugs packager cla_fpca
16:15:00 <fedmsg-python> 15github.pull_request.opened -- tyll opened pull request #81 on fedora-python/portingdb: Add pdfrw and fix other stuff 10https://github.com/fedora-python/portingdb/pull/81
16:28:51 <ardian_> I was looking into this Package http://portingdb-encukou.rhcloud.com/pkg/libsolv/ I see that Python 3 has green light for fedora, does this mean this is ready ?
16:31:25 <tyll> ardian_: it seems to be using the wrong shebang from what I understand from the page
16:32:44 <tyll> ardian_: the shell script in the documentation of the python3 pkg uses #!/usr/bin/python
16:34:00 <tyll> ardian_: I guess one could check whether the example script also works with python3 or port it and then fix the shbang
16:35:00 <ardian_> hmm maybe I can take a loot at that, it's just I am very new to the porting stuff, trying to find my way through
16:36:36 <tyll> ardian_: me too :-) the easiest task is probably checking whether upstream already supports python3 for packages in Fedora that do not support python3
16:41:39 <ardian_> tyll: are you using this https://github.com/fedora-python/portingdb/issues/9#issuecomment-153654009
16:42:40 <fedmsg-python> 15github.pull_request.opened -- michaeleekk opened pull request #82 on fedora-python/portingdb: update python-oauth2 status 10https://github.com/fedora-python/portingdb/pull/82
16:49:14 <tyll> ardian_: no, I did not look at this list
16:49:33 <borginator> how can I help?
16:50:22 <michaeleekk> But if updating the shebang to #!/usr/bin/python3, then it will break python2 ?
16:52:31 <tyll> michaeleekk: since python3 is default in f23+, the example could just use python3 instead of python2 imho
16:53:27 <tyll> borginator: welcome, there is a pad with information at https://titanpad.com/S3r8qX7OQJ
16:56:11 <michaeleekk> tyll: but other distros might not be ready for py3 default, possibly the github owner won't merge the shebang fix?
16:56:23 <Dremor> Hi there
16:57:51 <tyll> michaeleekk: then it is something that needs to be done only in the fedora pkg as part of the packaging
16:58:07 <tyll> Dremor: welcome, there is a pad with information at https://titanpad.com/S3r8qX7OQJ
16:58:12 <michaeleekk> Right okay :)
17:06:51 <Dremor> Thank you :)
17:07:07 <Dremor> I'll start to work as soon as possible.
17:07:39 <jpigface> hi folks. I've tested that a package written for py2 is also fully compatible with py3. Where (and how) should I report this kind of information?
17:12:33 <juliuxpigface> (that's great... a crash of wayland right after I wrote a question on IRC, lol)
17:12:40 <fedmsg-python> 15github.push -- sYnfo pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/7c7475d578a0...1e6b87b5f185
17:12:41 <fedmsg-python> 15github.pull_request.closed -- sYnfo closed pull request #79 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/79
17:13:52 <fedmsg-python> 15github.pull_request.closed -- sYnfo closed pull request #80 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/80
17:13:53 <fedmsg-python> 15github.push -- sYnfo pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/1e6b87b5f185...2cb77c44d545
17:14:47 <fedmsg-python> 15github.pull_request.closed -- sYnfo closed pull request #81 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/81
17:14:48 <fedmsg-python> 15github.push -- sYnfo pushed 4 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/2cb77c44d545...8da82baea8e8
17:15:08 <michel_slm> anyone knows if it's worth porting python-urlgrabber or not? looks like it was part of yum, but not dnf ... but koji, live* tools and osc do depend on it
17:17:11 <michaeleekk> I saw a package is already packaged, should i mark it in data/fedora-update.xml ?
17:17:17 <michaeleekk> http://pkgs.fedoraproject.org/cgit/python-http-parser.git/commit/?id=679051b1b7384460a4e8ff5b3234cb52a4f7e781
17:18:14 <fedmsg-python> 15github.fork -- pigjuliux forked fedora-python/portingdb 10https://github.com/pigjuliux/portingdb
17:18:38 <mstuchli> michel_slm: IIRC my colleague tried porting it and it's not pretty difficult, though I could be missremebering things
17:19:02 <tyll> jpigface: which package is it?
17:19:06 <michel_slm> mstuchli: ah, any idea what happened to that port? if it's in progress I wouldn't want to step on it
17:19:26 <michel_slm> .... and if it's abandoned I could continue the work
17:19:30 <jpigface> tyll: it's http://portingdb-encukou.rhcloud.com/pkg/python-django-countries/
17:19:32 <mstuchli> michel_slm: I'll try asking him on Monday, not sure right now
17:20:25 <mstuchli> michaeleekk: In this case, you don't have to mark it. It was fixed today during the pycon sprint and the dnf plugin will pick it up when we refresh the fedora.json sometimes next week :)
17:20:43 <michel_slm> mstuchli: cool, I'll claim the package and take a look at the code now, will check with you on Monday
17:20:46 <michaeleekk> mstuchli: nice ;)
17:21:19 <mstuchli> jpigface: Have you seen http://synfo.github.io/2015/10/14/Python3-Porting-Database/ ? :)
17:21:51 <jpigface> mstuchli: yep, I have, but I feel a bit confused, since I'm not an experienced developer.
17:22:14 <mstuchli> jpigface: Do you know git/github?
17:22:25 <jpigface> mstuchli: If I've understood correctly, I should fork the repo on github, edit the xml file and the submit a pull request
17:22:33 <mstuchli> Correct!
17:22:39 <mstuchli> The upstream.yaml file in this case
17:24:16 <tyll> jpigface: it is not xml btw but yaml - also you can open a bug in https://bugzilla.redhat.com and ask the maintainer to provide a python3 pkg - then the bug can be linked in the yaml file
17:25:09 <jpigface> tyll, mstuchli: thank you both. Now everything is clear :).
17:28:17 <fedmsg-python> 15github.pull_request.opened -- michel-slm opened pull request #83 on fedora-python/portingdb: Note that python-urlgrabber is being looked at 10https://github.com/fedora-python/portingdb/pull/83
17:38:22 <fedmsg-python> 15github.pull_request.opened -- pigjuliux opened pull request #84 on fedora-python/portingdb: Add python-django-countries 10https://github.com/fedora-python/portingdb/pull/84
17:56:17 <fedmsg-python> 15github.pull_request.opened -- michaeleekk opened pull request #85 on fedora-python/portingdb: update python-HTMLgen status 10https://github.com/fedora-python/portingdb/pull/85
18:07:23 <frafra> why https://bugzilla.redhat.com/show_bug.cgi?id=1282044 blocks https://bugzilla.redhat.com/show_bug.cgi?id=1282146 ?
18:09:23 <jflory7> Hi ardian_! Can you share the package you are working on again in here?
18:09:44 <ardian_> Hi jflory7 http://portingdb-encukou.rhcloud.com/pkg/mc/
18:11:54 <jflory7> ardian_: Mind sharing your dilemma in here as well? I think there's some people around who can help get you a better idea of the next step. :)
18:12:21 <tyll> frafra: williamjmorenor would know, not sure if he is here
18:13:24 <ardian_> so I am not sure how I should proceed with this package, (How do I assign this to me)
18:13:56 <ardian_> or should I just send email to upstream and coordinate
18:14:20 <tyll> frafra: I guess he uses the tracking bug to track the efforts of this FAD, e.g. if the autotrash bug is closed, it is tracked in the tracking bug
18:14:22 <fedmsg-python> 15github.pull_request.opened -- michaeleekk opened pull request #86 on fedora-python/portingdb: update pysendfile status 10https://github.com/fedora-python/portingdb/pull/86
18:15:00 * pingou has pkgdb-cli at hand
18:17:07 <ardian_> And I am not sure if mc has anything to do with Python
18:18:23 <tyll> ardian_: mc uses python scripts in /usr/libexec/mc/
18:23:55 <ardian_> tyll: would you mind explaining the workflow you are doing for a package ?
18:26:09 <frafra> tyll: yes, good guess
18:26:18 <tyll> ardian_: I know mc, therefore I looked where it stores its helper scripts with "rpm -ql mc" and then greped for python in /usr/libexec/mc/
18:27:07 <tyll> ardian_: this shows me these findings: https://paste.fedoraproject.org/290826/76119991/
18:27:32 <tyll> ardian_: therefore the next step would be to look at /usr/libexec/mc/extfs.d/uc1541 and /usr/libexec/mc/extfs.d/s3+ and see if they work with python3 or can be ported
18:27:56 <tyll> ardian_: or first check whether there are already fixes upstream
18:28:04 <tyll> ardian_: does this help you?
18:29:52 <fedmsg-python> 15github.pull_request.opened -- frafra opened pull request #87 on fedora-python/portingdb: autotrash spec file fixed 10https://github.com/fedora-python/portingdb/pull/87
18:30:46 <ardian_> tyll: yes, and if you find that there is a python3 support, how do you proceed ?
18:31:02 <ardian_> also the output of rpm -ql mc
18:31:10 <ardian_> is different when I grep for python
18:31:14 <ardian_> shows only /usr/share/mc/syntax/python.syntax
18:32:45 <tyll> ardian_: Sorry, this was confusing. I greped like this: "ag python /usr/libexec/mc/"
18:33:00 <tyll> ardian_: I used rpm -ql to find the /usr/libexec/mc/ directory
18:35:40 <tyll> ardian_: you could check upstream, if they already do some testing for the scripts and then try to run it with python3 instead of python2 - or you need to prepare a test yourself
18:37:26 <ardian_> tyll: thanks a lot
18:40:54 <threebean> howdy howdy :)
18:41:23 <pingou> o/
18:42:13 <fedmsg-python> 15github.pull_request.opened -- michaeleekk opened pull request #88 on fedora-python/portingdb: udpate pysnmp status 10https://github.com/fedora-python/portingdb/pull/88
18:52:54 <fedmsg-python> 15github.push -- sYnfo pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/8da82baea8e8...96bcac785c9e
18:52:55 <fedmsg-python> 15github.pull_request.closed -- sYnfo closed pull request #88 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/88
18:53:24 <fedmsg-python> 15github.push -- sYnfo pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/96bcac785c9e...4deac8c65aaf
18:53:25 <fedmsg-python> 15github.pull_request.closed -- sYnfo closed pull request #83 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/83
18:54:11 <fedmsg-python> 15github.pull_request.closed -- sYnfo closed pull request #84 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/84
18:54:13 <fedmsg-python> 15github.push -- sYnfo pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/4deac8c65aaf...b161780dd6b1
18:56:53 <fedmsg-python> 15github.push -- sYnfo pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/b161780dd6b1...0a4a109a7a13
18:56:54 <fedmsg-python> 15github.pull_request.closed -- sYnfo closed pull request #87 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/87
19:01:57 <fedmsg-python> 15github.pull_request.opened -- michaeleekk opened pull request #89 on fedora-python/portingdb: update pypdf status 10https://github.com/fedora-python/portingdb/pull/89
19:03:38 <fedmsg-python> 15github.push -- ralph pushed 1 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/0a4a109a7a13...59c343aa2e1d
19:26:55 <threebean> tracking down abi confusion in rawhide for some packages
19:27:19 <threebean> python3-fedora needs python3-openid, which failed to rebuild.
19:28:22 <threebean> and it failed due to python3-defusedxml...
19:46:56 * handsome_pirate rolls in
19:48:07 <threebean> mstuchli: you don't happen to be near churchyard, do you?
19:48:41 <mstuchli> threebean: I was few hours ago
19:48:45 <handsome_pirate> threebean:  Ahoy!
19:48:45 <mstuchli> What do you need from him?
19:48:53 <handsome_pirate> What can I poke at?
19:49:15 <threebean> mstuchli: i just have a patch for a package of his.. I'll attach it to a ticket.
19:49:19 <handsome_pirate> Is the FAD still a going?
19:49:20 <mstuchli> k :)
19:49:25 <threebean> handsome_pirate: I think so :p
19:49:26 <mstuchli> handsome_pirate: Yarrr
19:49:56 <handsome_pirate> arrr!
19:50:11 <mstuchli> handsome_pirate: You know about the portingdb?
19:50:57 <handsome_pirate> mstuchli:  I do not
19:51:08 <mstuchli> Feast your eyes, then: http://synfo.github.io/2015/10/14/Python3-Porting-Database/
19:51:41 * handsome_pirate looks
19:52:03 <tyll> handsome_pirate: there is also a pad with infos https://titanpad.com/S3r8qX7OQJ
19:52:09 <threebean> if there are any provenpackagers around -- want to consider applying the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1282251 ?
19:52:26 <mstuchli> threebean: I'm one, I'll take a look
19:53:18 <handsome_pirate> Thanks, y'all
19:54:09 <mstuchli> Churchyard does not take kindly to people touching his packages :D
19:54:18 <mstuchli> But this seems reasonable, I'll commit it :)
19:55:03 * handsome_pirate might could start working on the kernel tests
19:55:14 * handsome_pirate knows kernel pretty well, and py3, so it's a win
19:55:43 <mstuchli> handsome_pirate: Coolio!
19:57:31 <tyll> threebean: it seems to be to be a good idea to add %{!?_licensedir:%global license %%doc} to make the spec work on all branches - it defines %license as %doc if %_licensedir is not defined afaiu
20:02:26 <threebean> mstuchli: thank you :)
20:02:56 <threebean> tyll: fwiw, it doesn't have a fedora-based conditional around with_python3, indicating that it isn't intended to be built for epel (yet)
20:03:00 <threebean> tyll: but true enough.
20:07:30 <jflory7> handsome_pirate: Someone was working on the kernel-test scripts last night, but we were unable to get the FAS submission script to work properly.
20:07:43 <jflory7> Let me dig through my logs for the stacktraces if you want to pick up on that.
20:08:46 <jflory7> handsome_pirate: This was Python 2, I also have one with Python 3 somewhere. http://pastebin.com/wv61bjGy
20:09:01 <jflory7> Here we are: http://paste.fedoraproject.org/290618/52791144/
20:09:27 <jflory7> If you need a tester for that too, just ping me and I can run it on a F22 and F23 system for you.
20:10:00 <handsome_pirate> jflory7:  I sort of just jumped into the tests themselves, working on the hugetblfs test
20:10:21 <jflory7> Sounds good - just let me know if you want any testing help on that. :)
20:10:40 <handsome_pirate> Indeed :)
20:10:45 <handsome_pirate> I have F23 at the moment
20:11:24 <mstuchli> threebean: built: http://koji.fedoraproject.org/koji/taskinfo?taskID=11854535
20:13:50 <handsome_pirate> jflory7:  Would you believe the first one I settled on (basically at random) was already broken
20:14:20 <handsome_pirate> # Temporarily skip this test until we get more time to look at it.
20:14:43 <jflory7> handsome_pirate: lol. There's some things that have been amiss with those scripts for a while, I think.
20:15:58 <tyll> threebean: I do not follow, the %license is used unconditionally for the python2 pkgs afaics
20:16:56 <threebean> mstuchli: thanks again!
20:17:33 <mstuchli> o7
20:17:40 <threebean> tyll: short story - you're right.  longer story, the 'with_python3' macro at the top of the file is defined unconditionally.. so, even without my changes the spec file wouldn't build for epel7.
20:18:01 <threebean> tyll: I just looked though, and there are epel branches,, they just have commits of their own that disable the with_python3 conditional.
20:23:25 <handsome_pirate> jflory7:  Still python3ifying it, so when jwb et al do poke at it again, it will be ready to go :)
20:23:43 <jflory7> handsome_pirate: Sweet!
20:25:42 <tyll> threebean: I added the %license macro now since the patch was already applied
20:30:20 <threebean> tyll: thank you :)
20:35:00 <fedmsg-python> 15github.pull_request.opened -- MSK61 opened pull request #90 on fedora-python/portingdb: anjuta package ready in rawhide 10https://github.com/fedora-python/portingdb/pull/90
20:37:55 <handsome_pirate> How much from future are we supposed to be using, to keep this runable under python2, or do we not care?
20:50:22 <threebean> handsome_pirate: what's the project?  kernel runtests?
20:50:53 <threebean> imho, it's good to keep py2 compatibility where you can.. just to give room for people to jump the gap.
20:51:32 <handsome_pirate> threebean:  Aye, the kernel runtests
20:52:15 <handsome_pirate> threebean:  To do the fancy output formatting, though, wants the actual print() function, and it kind of makes it not py2 compatible
20:53:24 <threebean> it actually is :)
20:53:35 <threebean> print() works on py2.6 and py2.7 out of the box iirc.
20:53:49 <threebean> on py2.5 you need to add 'from __future__ import print_function'
20:53:55 <threebean> but, imho, we don't need to bother with that.
20:54:47 <handsome_pirate> but, end='' is a thing
20:55:12 <handsome_pirate> unless there's another way to not get newlines?
20:58:08 <handsome_pirate> threebean:  Anyway, I'll go ahead and make sure it's there, just to be safe
20:58:45 <fedmsg-python> 15github.pull_request.opened -- williamjmorenor opened pull request #91 on fedora-python/portingdb: Update status of todocli and python-xlwt 10https://github.com/fedora-python/portingdb/pull/91
21:03:29 <fedmsg-python> 15github.push -- ralph pushed 1 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/59c343aa2e1d...920cb07c3d09
21:11:03 <fedmsg-python> 15github.pull_request.synchronize -- williamjmorenor synchronized pull request #91 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/91
21:23:58 <threebean> python3-openid is being really troublesome :(
21:24:40 <handsome_pirate> ouch
21:26:28 <fedmsg-python> 15github.issue.comment -- QuLogic commented on issue #91 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/91#issuecomment-156855331
21:28:51 <fedmsg-python> 15github.pull_request.closed -- ralph closed pull request #68 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/68
21:28:52 <fedmsg-python> 15github.push -- ralph pushed 3 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/920cb07c3d09...ab4dbbefd080
21:30:10 <fedmsg-python> 15github.issue.comment -- ralph commented on issue #82 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/82#issuecomment-156856193
21:30:55 <fedmsg-python> 15github.issue.comment -- ralph commented on issue #86 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/86#issuecomment-156856233
21:32:20 <handsome_pirate> jflory7:  I don't have git access to that particular repo; do you reckon I should open a bug with a patch?
21:32:49 <jflory7> handsome_pirate: There is actually a bug already filed. You could probably add info to that.
21:33:01 <handsome_pirate> jflory7:  Do you happen to have a number?
21:33:38 <jflory7> handsome_pirate: https://bugzilla.redhat.com/show_bug.cgi?id=1282133
21:35:54 <potty> Hello people
21:36:19 <handsome_pirate> Ahoy!
21:37:14 <handsome_pirate> doh
21:37:26 <handsome_pirate> jflory7:  Looks like I just duplicated work
21:41:43 * mstuchli waves
21:42:07 <fedmsg-python> 15github.pull_request.opened -- williamjmorenor opened pull request #92 on fedora-python/portingdb: python-xlwt 10https://github.com/fedora-python/portingdb/pull/92
21:44:15 <fedmsg-python> 15github.pull_request.opened -- williamjmorenor opened pull request #93 on fedora-python/portingdb: todocli 10https://github.com/fedora-python/portingdb/pull/93
21:44:43 <fedmsg-python> 15github.pull_request.closed -- williamjmorenor closed pull request #91 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/91
22:14:02 <jflory7> handsome_pirate: His work wasn't 100% complete as far as I know.
22:45:35 <tonet666p> hi again guys
22:45:43 <tonet666p> i returned
22:50:22 <jflory7> Welcome back, tonet666p!
22:51:11 <tonet666p> abadger1999, what packages are waiting for work?
22:51:20 <SigmaWP> if I've marked a package as in-progress, how do I mark it as finished?
22:54:58 <SigmaWP> because, like, I finished
23:03:50 <threebean> SigmaWP: set the status to 'released'
23:03:52 <threebean> :)
23:04:09 <threebean> or, if its not released yet, keep it as in-progress since upstream would still need to accept it (if they haven't already)
23:04:43 <threebean> I made a little more progress on createrepo_c tonight.  if anyone out there knows what they're doing with porting c extensions, feel free to have a go at it.  I'm ... learning.  :p
23:05:03 <threebean> have a good night all!  this has been awesome.
23:05:21 <frafra> :)
23:05:22 <frafra> bye!
23:08:05 <SigmaWP> threebean: bye
23:10:07 <fedmsg-python> 15github.pull_request.opened -- Riamse opened pull request #94 on fedora-python/portingdb: lorem-ipsum-generator is done 10https://github.com/fedora-python/portingdb/pull/94
23:18:53 <fedmsg-python> 15github.pull_request.closed -- sYnfo closed pull request #94 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/94
23:18:54 <fedmsg-python> 15github.push -- sYnfo pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/ab4dbbefd080...7856bf5bb138
23:24:38 <SigmaWP> mstuchli: does porting a single package merit a parselmouth badge?
23:25:03 <mstuchli> SigmaWP: Can you show me what package? But I reckon it should :)
23:25:15 <SigmaWP> It was just recently merged
23:25:28 <SigmaWP> Like, really recently
23:26:01 <mstuchli> SigmaWP: can you give me a link?
23:28:11 <SigmaWP> i pm'd you.
23:33:34 <klurl> Hey, I'd love to help out. Can I help someone port something?
23:37:22 <frafra> klurl: https://titanpad.com/S3r8qX7OQJ
23:39:06 <klurl> Thanks
23:42:59 <frafra> yw
23:47:37 <fedmsg-python> 15github.pull_request.opened -- Riamse opened pull request #95 on fedora-python/portingdb: lorem-ipsum-generator bug link 10https://github.com/fedora-python/portingdb/pull/95
23:47:38 <fedmsg-python> 15github.push -- sYnfo pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/7856bf5bb138...83dc7a003099
23:47:39 <fedmsg-python> 15github.pull_request.closed -- sYnfo closed pull request #95 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/95
23:58:19 <QuLogic> that... is not in any order, is it?
00:05:30 <frafra> bye! thank you for this FAD :)
00:10:45 <potty> Hey
00:11:00 <potty> frafra: you leaving?
00:32:47 <potty> hello people
00:32:58 <potty> question: does anyone have the portingdb working?
00:39:26 <zhaodi> Do we just go on http://portingdb-encukou.rhcloud.com/ and choose a package to port?
00:41:58 <potty> zhaodi: i think it is not updated
00:42:17 <zhaodi> Then where would u suggest i start at?
00:42:20 <potty> https://github.com/fedora-python/portingdb
00:42:34 <potty> Updated data is in that repo
00:43:47 <potty> Find instructions here: http://synfo.github.io/2015/10/14/Porting-Database/
00:48:06 <zhaodi> potty: im gonna have to install pip for this to work right?
01:00:35 <QuLogic> you don't really need to run it; you can just look at the data
01:00:46 <QuLogic> the yaml files override the json
01:03:31 <potty> zhaodi: not necess
01:03:45 <potty> QuLogic: i kno... just askin
01:04:11 <QuLogic> potty: you... didn't ask, though?
01:04:27 <potty> i'm sorry
01:04:32 <potty> misunderstood your message
01:04:58 <potty> sorry
01:09:48 <zhaodi> i just look at the yaml files?
01:14:42 <zhaodi> the yaml files are a bit hard to read..
01:16:57 <zhaodi> statuses.yaml right?
01:18:08 <zhaodi> nvm
01:43:09 <fedmsg-python> 15github.pull_request.opened -- QuLogic opened pull request #96 on fedora-python/portingdb: Mention porting effort upstream for libfreenect. 10https://github.com/fedora-python/portingdb/pull/96
01:55:48 <dsouza> hi
04:11:13 <rodrigc> is anyone looking at portingdb?  there are a bunch of pending pull requests
04:31:58 <QuLogic> I think most have gone to sleep or something
07:18:05 <fedmsg-python> 15github.star -- pvergain starred fedora-python/portingdb 10https://github.com/fedora-python/portingdb/stargazers
07:33:33 <fedmsg-python> 15github.pull_request.closed -- sYnfo closed pull request #96 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/96
07:33:34 <fedmsg-python> 15github.push -- sYnfo pushed 2 commit(s) to fedora-python/portingdb 10https://github.com/fedora-python/portingdb/compare/83dc7a003099...ff1a860a630b
08:02:05 <fedmsg-python> 15github.pull_request.synchronize -- rodrigc synchronized pull request #64 on fedora-python/portingdb 10https://github.com/fedora-python/portingdb/pull/64
08:28:14 <rodrigc> can someone look at: https://github.com/fedora-python/portingdb/pull/64
09:59:33 <mrunge> without looking further into it, subunit fails on python-3.5, where it passed on python-3.4
10:01:51 <potty> Thanks for participating
10:01:53 <potty> It is over
10:02:00 <potty> Wait for statistica
10:02:10 <potty> #endmeeting