14:30:05 #startmeeting 14:30:06 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 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:30:10 rodrigc: Yup, that's the idea 14:30:19 threebean: I guess we may as well :) 14:30:26 #topic Python 3 Porting FAD 14:30:40 Welcome pythonistas! 14:30:40 So createrepo_c will need a python3 subpackage 14:30:41 do you guys know about this web site: https://caniusepython3.com/ 14:31:11 mstuchli: ok! thank you ;) 14:31:50 A site to help you transition to Py3,not bad. 14:32:09 :q 14:32:12 Hello everyone. 14:32:24 MSK61: Hey there :) 14:32:39 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 Welcome MSK61 14:33:25 MSK61: Have you seen http://synfo.github.io/2015/10/14/Python3-Porting-Database/ ? 14:33:43 I've checked tagia https://tree.taiga.io/project/synfo-fedora-python-3-porting/kanban but it looks empty for me. 14:33:47 This lists packages not yet Python3: https://python3wos.appspot.com/ 14:34:00 mstuchli: what time is it over there? 14:34:06 15:34 :) 14:34:21 rodrigc: use the portingdb app please 14:34:26 AFAIK pyinvoke is considered by maintainer as worthy successor to Fabric for python 3, at least for local scripting 14:34:29 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 The pycon sprint will start tomorrow ~10am 14:35:15 MSK61: Yes, the taiga won't be used in the end, sorry for the confusion :) 14:35:16 potty: I cloned it from github, I can't figure out which yaml file to update 14:35:23 dperson: Take a look at http://synfo.github.io/2015/10/14/Python3-Porting-Database/ 14:35:32 dperson: And see if you can pick something from the portingdb :) 14:35:40 rodrigc: What do you need to do again? 14:36:03 @mstuchli thank you 14:36:04 Using git huh. 14:36:35 patxi: yup 14:36:55 mstuchli: update info about python fabric and m2crypto 14:37:59 ]% python3 -m portingdb --datadir data/ load 14:37:59 Traceback (most recent call last): 14:37:59 File "/usr/local/lib/python3.5/runpy.py", line 170, in _run_module_as_main 14:37:59 "__main__", mod_spec) 14:37:59 File "/usr/local/lib/python3.5/runpy.py", line 85, in _run_code 14:37:59 exec(code, run_globals) 14:37:59 File "/usr/home/rodrigc/portingdb/portingdb/__main__.py", line 3, in 14:38:00 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 main() 14:38:00 File "/usr/home/rodrigc/portingdb/portingdb/cli.py", line 17, in main 14:38:01 return cli(obj={}) 14:38:01 File "/usr/home/rodrigc/astrenv/lib/python3.5/site-packages/click/core.py", line 700, in __call__ 14:38:02 return self.main(*args, **kwargs) 14:38:02 File "/usr/home/rodrigc/astrenv/lib/python3.5/site-packages/click/core.py", line 655, in main 14:38:03 raise RuntimeError('Click will abort further execution ' 14:38:08 wow, please use fpaste :) 14:38:17 Ivoz: no, he refused 14:38:27 rodrigc, recently? :) 14:38:31 Ivoz: https://github.com/fabric/fabric/issues/1378 14:38:51 rodrigc: Does this help? https://github.com/fedora-python/portingdb/pull/18 14:39:11 oh hmm, maybe I'm behind times on that 14:39:30 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 mstuchli: Can you help me with the error I got? 14:40:04 how do I configure the encoding? 14:40:33 rodrigc: I don't think I go the entire thing, could you put it on pastebin 14:40:56 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 Ivoz: it's all vaporware 14:41:36 pyinvoke isn't 14:41:45 works fine 14:41:57 pip uses it now 14:42:26 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 Ivoz: the pyinvoke web page says it is pre-1.0 and subject to change 14:44:22 Ivoz: meanwhile, I have tons of scripts that use Fabric, and many other people do to as well 14:44:39 Anyone is having problem with python-click? 14:44:41 I've been following invoke, it's getting very close to stable now 14:45:01 mstuchli: http://pastebin.com/B4fJhQZz 14:45:08 should we try and keep the yaml files in the portingdb git sorted? 14:45:31 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 Ivoz: it's annoying that upstream is rejecting the port 14:46:06 rodrigc: try define LANG=en_GB.utf8 LC_ALL=en_GB.utf8 14:46:37 rhuska: can I use a US locale? 14:47:18 rodrigc: sure 14:47:54 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 rkuska: I tried this: env LANG=en_US.utf8 LC_ALL=en_US.utf8 python3 -m portingdb --datadir data/ load 14:48:13 rkuska: and that failed 14:49:26 env LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 python3 -m portingdb --datadir data/ load 14:49:28 that worked 14:49:34 ok, now I am getting a different error 14:49:50 ImportError: No module named 'pysqlite2' 14:50:10 rodrigc: so install pysqlite2 now :-) 14:50:15 Missing dependencies 14:50:35 that needs to go in requirements.txt, I am installing everything in a virtualenv 14:50:49 Yup rodrigc 14:51:28 there is no pysqlite2 package 14:52:05 ok I tried to pip install pysqlite 14:52:07 and got this: 14:52:08 Complete output from command python setup.py egg_info: 14:52:08 pysqlite is not supported on Python 3. When using Python 3, use the sqlite3 module from the standard library. 14:52:18 WTF 14:52:59 rodrigc: Could you post the entire ImportError exception? I don't think portingdb requires pysqlite2 14:55:19 mstuchli: http://pastebin.com/ygwVzKck 14:59:15 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 rodrigc: Running it is definitely not necessary 15:00:20 rodrigc: But I *think* that's a system problem, not portingdb 15:00:23 What distro do you use? 15:00:41 I'm running my FreeBSD laptop, running Python 3.5 15:00:50 I installed everything in a virtualenv via pip 15:02:07 i'm off my mum gets mad after i'm more than 20 mins on the laptop! 15:02:29 oh if I remember, I think in FreeBSD ports, they don't compile sqlite into the default Python by default 15:02:32 GL porting all of that, huge step for the py devs. 15:02:39 patxi: Hah, tell her you're doing good work! ;) 15:02:43 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 and the way that SQLAlchemy works is, if it doesn't find sqlite3 module, it tries to load pysqlite2 15:03:07 fale: It's ongoing! :) 15:03:17 hi fale ;) 15:03:22 frafra: hi :) 15:03:32 fale: Take a look at http://synfo.github.io/2015/10/14/Python3-Porting-Database/ 15:03:39 mstuchli: awesome :) thanks 15:04:53 fale no matter timezone. The FAD is all saturday and sunday 15:05:20 potty: the Magazine indication is wrong, then ;) 15:05:38 It is ok 15:05:40 Welcome 15:05:46 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 any suggestion on a package to start with? 15:07:15 fale: scroll up someone posted the list of the packages 15:07:51 patxi: the list is pretty long, I've seen... I just pick one randmly? 15:08:23 fale: yeah download the source code and start working 15:10:18 patxi: thanks :) 15:20:23 Is there any order to the list in "data/upstream.yaml"? Currently, the list just seems unordered. 15:21:05 fujimotos: I think you can just append your text 15:21:48 frafra: Ok, I'll do that. thanks. 15:22:57 yw 15:26:12 Good morning all. 15:27:01 Do I have to be on the latest fedora 23? I'm currently on fedora 22. 15:27:32 MSK61: I don't think it's necessary 15:27:38 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 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 Grahhhh: thanks. marking it in upstream.yaml per some discussion in portingdb's github 15:29:12 mstuchli: want to add the portingdb app github activity to fedmsg? https://apps.fedoraproject.org/github2fedmsg/ 15:29:46 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 does Fedora use a lot of Python for it's own scripts? I remember stuff like anaconda 15:30:28 rodrigc: sure does. all over the place. 15:30:40 threebean: That would be super cool. Not sure how we'd use it right now tho 15:30:55 threebean: are all those internal scripts python3 in fedora23? 15:31:20 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 mstuchli: that github2fedmsg webapp should be self-service to turn it on (but you need admin rights on the github repo) 15:31:52 pyliblzma, why not set to dropped? I saw the status suggesting to use stdlib or python-backports-lzma 15:31:53 mstuchli: we could graph activity afterwards for a nice blog post :p 15:32:14 michaeleekk: sounds like a good idea. can you set it to dropped? 15:32:24 no prob ;) 15:32:27 ty! 15:33:23 threebean: Huh, that's an idea! I'll look into doing that 15:33:32 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 threebean: You have a link or somthing I can follow to enable it? 15:34:09 https://apps.fedoraproject.org/github2fedmsg/ 15:34:11 mstuchli: ^^ 15:35:24 threebean: Aww, shoot, do I really need to give the app access to all my org's repos? 15:35:46 :/ I think it only needs read and webhook access. 15:35:57 but you can control which ones are enabled. it doesn't turn them all on by default. 15:36:26 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 threebean: got that in mind 15:38:39 threebean: Could you do it yourself, if I set you as an admin? 15:39:05 mayorga: hola 15:39:59 potty: We have fitoria in #fedora-ni, but he is still unable to join this channel. 15:41:12 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 mstuchli: OK, I fixed the sqlite3 problem on my side and got portingdb to run 15:42:13 rodrigc: Cool :) 15:42:40 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 o/ 15:43:02 OT: Do you know of arm ressources to test/debug a current scipy failure? 15:43:12 ok according to portingdb it lists m2crypto as dropped 15:43:47 got it mstuchli 15:44:01 how are you getting the information about packages which are done? 15:44:33 there are other web apps which poll information about Python 3 packages directly from PyPI 15:44:55 I’m in now :) 15:44:58 where can I start? 15:46:04 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 +questions 15:46:14 go ti 15:46:16 it* 15:47:44 Bienvenidos! fitoria mayorga echevemaster 15:49:01 rodrigc: The done status is when the package in the fedora developmet branch (what we call rawhide) has a python3 subpackage 15:49:24 rodrigc: (with some checks that the python3 subpackage doesn't depend on python2 due to packaging errors) 15:49:46 hi guys 15:49:50 abadger1999: so it is not enough to have the package in PyPI? 15:50:02 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 i'm near to my home 15:50:08 rodrigc: correct. 15:50:26 abadger1999: well that's probably OK for now 15:50:30 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 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 abadger1999: well maybe the portingdb can have another state 15:52:09 Hey abadger1999 sup! 15:52:20 abadger1999: "available" or "ported upstream" 15:53:01 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 abadger1999: https://caniusepython3.com/ and https://python3wos.appspot.com/ poll the info about Python 3 readiness from PyPI 15:53:47 mstuchli: ^ rodrigc has a feature request. Not sure if we have something like that already? 15:53:59 (or something that could be expanded to that) 15:54:10 .fas tonet666p 15:54:10 tonet666p: tonet666p 'Tonet Pascualet Jallo Colquehuanca' 15:54:21 potty: buenos dias! 15:54:55 hola a todos | hi to everyone 15:55:40 abadger1999: Hmmm, I wonder how they figure out if a project supports Python 3 or not 15:56:35 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 abadger1999: That's not very reliable though 15:57:54 Probably more false negatives than false positives though. 15:58:12 why does portingdb have a README *and* a README.md file? 15:58:18 Perhaps, I'll talk to encukou about adding that feature 15:58:31 So it would be helpful for getting an initial list of upstream packages that packagers just need to update. 15:59:36 threebean: We are porting createrepo to python3, correct? 15:59:50 * abadger1999 will look at breaking the pyliblzma dependency if so. 15:59:51 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 abadger1999: createrepo_c, right, not createrepo 16:00:14 Yes 16:00:49 mstuchli: Hmm. okay, I have avoided delving into the C extenstion world so far. 16:03:35 so in fedora23, are all the internal fedora scripts which use python now python3 scripts? 16:03:44 rodrigc: nope, not yet. 16:03:47 abadger1999: I'm just going by what threebean said, I think createrepo is... deprecated, in this sense 16:03:53 mstuchli: k. 16:04:08 so what did fedora23 do with respect to python3? 16:04:11 I'll look for some other low hanging fruit for now. 16:04:36 rodrigc: we got python2 off of the workstation install (the most popular version of Fedora) 16:05:02 but how could you do that if the fedora python scripts are not python3? 16:05:13 rodrigc: which means that the packages that went into a default install of workstation are all python3 now. 16:05:33 rodrigc: Maybe I'm misunderstanding "internal" -- I take that to mean things that are used to build the distro. 16:05:43 abadger1999 +1 16:05:47 well building the distro is one 16:06:07 rodrigc: There are still a lot of python2 scripts and applications in that set. 16:06:17 but I was referring more to python scripts which are part of a base fedora distribution 16:06:30 such as the installer, or any management tools 16:06:33 rodrigc: ah -- yes, those should be ported to python3 at this point. 16:06:40 ok 16:06:47 that's a huge milestone 16:06:55 rodrigc: One thing that I'd love to see is the Fedora Server install also being completely python3. 16:07:16 So that might be one thing to take a look at where the dependencies lead. 16:07:25 yes, when Fedora Server is python3 that will be a bigger one 16:07:33 sgallagh: If you're around this weekend, I wonder if you know those off the top of your head. 16:07:41 Fedora is considered the more "serious" distro 16:08:20 abadger1999: Samba, FreeIPA, those are too big for this FAD thought, and they are being worked on separately 16:08:22 sgallagh: Or know of a list of the packages in Server that we can query. 16:08:27 16:08:51 mstuchli: perhaps in another FAD? 16:09:51 With people knowing the work flow of this FAD, next related FADs would be easier to manage 16:10:50 potty: maybe... they'll both need participation from the upstreams of those projects. 16:10:50 abadger1999: https://gist.github.com/sYnfo/fede3641ce603ca59b33 these should be the problematic on server 16:11:02 abadger1999: Exactly, those are some pretty big fish 16:11:08 potty: freeipa we'll need to know what they plan on replcing python-paste with. 16:11:21 (since last I heard isn't pporting to python3) 16:11:30 If someone is interested in XFCE, take a loot at exo 16:11:37 We don;t think it should depend on Python 2 16:12:08 abadger1999: i see 16:12:32 samba it looks like upstream is working on it but I suppose we could help out if they're stalled somewhere. 16:12:42 mstuchli: thanks for the list! 16:14:50 I gotta go for now, have fun! 16:14:57 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 >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 rodrigc: okay. Thanks! 16:16:20 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 I think we should push updates in rawhide abadger1999, 16:17:10 echevemaster: okay. 16:18:03 sorry to keep talking about portingdb 16:18:18 but a comment at the top of each yaml file would be helpful 16:19:37 which one do I modify to indicate I am working on m2crypto? 16:19:42 fedora-update.yaml? 16:20:33 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 lol 16:20:45 mstuchli: ^ Question about where to mark that one of us is working on porting. 16:22:25 abadger1999: https://github.com/fedora-python/portingdb/issues/25 16:23:16 I’m going to start working on boom 16:23:23 I'm going to take a guess and say that fedora-update.yaml is for dealing with fedora packaging 16:23:42 Should I mark it on upstream.yaml? 16:23:42 and upstream.yaml is for the upstream code on PyPI 16:23:48 great 16:23:51 going for it 16:24:10 but don't take anything I say about portingdb as true, I am just guessing 16:24:22 lol 16:25:03 fedora-update.yaml is alphabetically sorted 16:25:06 upstream.yaml is not 16:25:09 ?? 16:25:14 Good morning good folk ... I brought the Starbucks! 16:26:13 rodrigc: If you'd like to correct that, I will merge your pull request. 16:26:26 lol, ok 16:26:44 I think (except for he json file which is updated via a script) they should all be alphabetized. 16:27:43 I’ve created this PR https://github.com/fedora-python/portingdb/pull/26 16:28:15 lol condor 16:28:52 did anyone answer my question about why portingdb has a README *and* README.md file? 16:29:04 fitoria: Cool. I'll get to merging it shortly :-) 16:30:15 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 rodrigc: don't know if he has a reason for keeping the un-suffixed file around. 16:31:17 abadger1999: Oops, didn't notice it was a symlink!! 16:31:50 lol potty 16:31:52 :-) 16:38:24 ok, I'm slowly understanding how it works :) 16:38:45 that's a good way to learn many things about packaging 16:40:21 This event helps in many ways 16:40:31 I agree 16:40:37 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 I develop an upstream program with bindings in python2 using swig. What's the best way to add a python3 binding? 16:41:03 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 barracks510: I'm not intimately familiar with swig but I know that it supports building python3 bindings as well. 16:42:28 abadger1999: Would that be preferable over a setup.py modification? 16:43:00 ok, I'm logged into github, and following along. Just watching and learning stuff. 16:43:10 I have an eye on https://titanpad.com/S3r8qX7OQJ. Please update it so packagers can find packages to work on. 16:43:11 barracks510: http://www.swig.org/Doc1.3/Python.html#Python_python3support 16:44:49 abadger1999: https://github.com/fedora-python/portingdb/pull/27 16:46:04 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 abadger1999: ok wait 16:46:23 mayorga is right. Update the Etherpad indicating what are you currently working 16:46:36 So we avoid double efforts 16:47:48 abadger1999: Feel free to build it in rawhide 16:48:01 tomspur: Cool. Thanks! 16:48:56 abadger1999: Do you know of arm resources for packager? I try to track down a scipy bug currently... 16:49:11 I cannot connect to https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers 16:50:21 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 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 abadger1999: don't modify this file, I am 10 commits behind 16:50:56 rodrigc: k :-) 16:50:56 abadger1999: let me catch up 16:51:15 abadger1999: thanks 16:51:59 iamgregb: We'll need to push the changes to upstream. 16:52:25 wich is the list of packages for migrate to python 3? 16:53:04 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 tonet666p: the portingdb app has the overall picture for fedora. 16:53:21 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 tonet666p: http://portingdb-encukou.rhcloud.com/ 16:53:45 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 ty abadger1999 16:54:04 tomspur: k. I'm doing a scratch build now to see. 16:54:09 abadger1999: Doest upstream refer to where the package originates from or... 16:54:41 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 iamgregb: yes. 16:55:09 abadger1999, send me that list please 16:55:39 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 iamgregb: that way we don't have to maintain our own patchset for forever. 16:56:19 sounds reasonable 16:56:28 tonet666p: https://github.com/fedora-python/portingdb/issues/9#issuecomment-153654009 there's a list of packages in that comment 16:56:45 tonet666p: they all have python3 subpackages but something is wrong with them. 16:58:06 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 I'm a bit confused 16:58:18 abadger1999, reading... 16:58:57 tonet666p: You could look at python-jsonpointer if you want something to start on that's reasonably easy. 16:59:13 ok 16:59:15 tonet666p: It's from the list and I had looked at it earlier but not started rewriting hte spec file. 17:00:21 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 frafra: the python3 library is in its own subpackage. 17:01:14 frafra: For almost all apps, you wnat to switch it to use /usr/bin/python3 in rawhide. 17:01:54 wait a moment, i still have fedora 22, i necesary f23 for this work? 17:01:59 No 17:02:15 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 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 tonet666p: Most packages I can do all the work on whatever fedora I have installed (i'm on f21 right now). 17:04:10 tonet666p: some you can't build htem on older fedora because the python3 versions of its dependencies aren't there. 17:04:12 abadger1999: thank you :) 17:04:40 abadger1999: porters.yaml is for that 17:04:56 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 tonet666p: I've been using rawhide-test.scrye.com a lot for those sorts of packages. 17:05:41 mstuchli: k 17:06:02 thanks! 17:06:06 I've noticed that the last commit in portingdb, cabd81961c9d7b5f00ea525d290117176cb16dce, which merges pull request #22, causes the database creation to fail. 17:06:27 I've verified that just one commit before, it was working fine. 17:06:35 MSK61: k. I'll take a look. 17:08:29 Holy cow it got busy in here! 17:09:30 Is this https://tree.taiga.io/project/synfo-fedora-python-3-porting/ page going to be used? 17:10:07 abadger1999: Hello 17:10:09 logavanc: It was decided that it was superfluous. Use the titanpad page and the portingdb instead. 17:10:13 chandankumar: Greetings 17:10:34 logavanc: https://titanpad.com/S3r8qX7OQJ http://portingdb-encukou.rhcloud.com/ 17:10:35 abadger1999 +1 17:10:36 mstuchli: if you made me an admin, that would probably work :) 17:10:40 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 abadger1999: ++ 17:10:53 abadger1999: on createrepo, yeah. i was thinking of dropping createrepo, and instead just focusing on porting createrepo_c 17:11:08 threebean: Okay, thanks for the info! 17:11:15 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 threebean: done 17:12:35 portingdb creation failure log: http://pastebin.com/99bLXWWf 17:12:50 chandankumar: Excellent, thanks! 17:13:01 MSK61: yep, I have a fix ready. 17:13:28 Just waiting on rodrigc to resubmit his sorted list PR to commit it. 17:13:56 (The portingb only understands links of type bug: I think. So other links go in the notes section.) 17:14:13 abadger1999: try now 17:14:34 abadger1999: fwiw, I think it also understands links of type 'repo' 17:15:01 rodrigc: Thanks! 17:15:09 threebean: nice, I'll try that out. 17:17:25 abadger1999: oops 17:17:30 abadger1999: now I am getting this 17:17:31 aml.composer.ComposerError: found undefined alias 'obnam' 17:17:32 in "/usr/home/rodrigc/portingdb/data/upstream.yaml", line 27, column 10 17:17:38 :-( 17:18:46 Very odd... looks like the same syntax. 17:19:01 But it also looks like maybe it should have been $obnam; ? 17:19:24 mstuchli: all done! :) 17:21:11 hmm... alright maybe & is when you define it... 17:21:14 * abadger1999 looking further 17:22:05 oh... maybe it's being defined after it's being referenced now... 17:24:28 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 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 michel_slm, mstuchli: especially if there isn't an alternative module out there? 17:26:56 abadger1999: this application is not designed well. if people need to manually edit yaml files like this, that is no good 17:27:59 abadger1999: If they are not outright against porting, than perhaps keep it idle and add a note 17:28:06 it would be easier to just have a wiki, or a Google doc spreadsheet 17:28:40 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 rodrigc: we had tried a wiki in the past--- it definitely didn't work as well as this. 17:29:19