[12:11] <hakermania> Hey...
[17:26] <ari-tczew> does anybody run maverick? I need a test of clementine package to backport. bug 690297
[17:49] <hakermania> I run maverick, how can I help?
[17:50] <ari-tczew> hakermania: follow with guide on above bug and install clementine from my PPA
[18:04] <hakermania> ari-tczew: I can't figure out how to install the PPA :/. I just run  'add-apt-repository ppa:ari-tczew/testing' What about now?
[18:05] <ari-tczew> hakermania: sudo apt-get update && sudo apt-get install clementine
[18:05] <hakermania> Ok
[18:06] <hakermania> ari-tczew: After testing I'll left my comment to the bug report. Right?
[18:07] <ari-tczew> hakermania: right, but if you have any concerns, please talk to me first
[18:07] <hakermania> ari-tczew: Ok ;)
[18:11] <hakermania> ari-tczew: It is a Qt app, QtPy?
[18:14] <ari-tczew> hakermania: do you asking whether package is based on python?
[18:15] <hakermania> ari-tczew: No, I'm asking whether it is programmed with Qt C++ or QtPy
[18:15] <hakermania> :)
[18:15] <ari-tczew> hakermania: dunno, I'm not author
[18:15] <hakermania> Oh, OK.
[18:15] <ari-tczew> rather c++
[18:15] <ari-tczew> hakermania: you can ask on #clementine
[18:18] <hakermania> ari-tczew: I noticed a bug on 1)right click on song 2)delete from disk (the file was a text file named something.mp3, to see the behavior of the program to non-music files) 3) Program crashed with output http://paste.ubuntu.com/545691/
[18:19] <hakermania> ari-tczew: Same with real music files
[18:22] <hakermania> ari-tczew: Also it seems to be a unicode problem in displaying the lyrics info. However the song have native english lyrics. I cannot understand the reason. It is the 'Sweet Dreams are made of this' of Marilyn Manson (he is a bit psycho, I know)
[18:25] <ari-tczew> hakermania: I must ask upstream
[18:25] <hakermania> ari-tczew: What should I do know~?
[18:26] <ari-tczew> hakermania: I'm asking second tester to check deleting files from disk
[18:26] <hakermania> ari-tczew: Ok
[18:49] <ari-tczew> hakermania: could you prepare a backtrace for upstream? btw. would be nice if you could join #clementine and help find bugs
[18:49] <ari-tczew> !backtrace | hakermania
[18:50] <hakermania> ari-tczew:  Yes, I will, but I will may need your help, I've never did a backtrace before.
[18:51] <ari-tczew> hakermania: above link is great, please try first follow with it. if you will have problem, ask here
[18:52] <hakermania> ari-tczew: I'm currently reading it. :)
[19:00] <hakermania> ari-tczew: 'gdb clementine 2>&1 | tee ~/gdb-clementine.txt' doesn't start clementine. gdb is installed and at the latest version
[19:01] <hakermania> ari-tczew: found it.
[20:51] <bdrung> tumbleweed: what do you think about the ISC license?
[20:57] <bdrung> tumbleweed: "prefix = sys.argv[0].upper().replace('-', '_') + '_'" -> you should strip get the basename of argv[0]
[21:02] <ari-tczew> tumbleweed: can I use your sponsorship template for endorsement?
[21:04] <tumbleweed> bdrung: I've also been a MIT/Expat user, although I tend to just use GPL
[21:04] <tumbleweed> bdrung: oh, good point re basename
[21:05] <tumbleweed> bdrung: I'm glad you are looking at it :) What do you think of the general approach? (I tried to follow devscripts style)
[21:05] <bdrung> tumbleweed: confusing :)
[21:07] <tumbleweed> ari-tczew: the script I use is here: lp:~stefanor/ubuntu-dev-tools/sponsor-list It isn't perfect, but it finds me bugs to look at
[21:08] <ari-tczew> tumbleweed: ah, I mean whether can I copy and edit for me your table :)
[21:09] <tumbleweed> ari-tczew: the script generates the table, by mining the changes list archives
[21:09] <micahg> tumbleweed: there should be a way to query the LP API to find out what pacakges were sponsored
[21:09] <tumbleweed> micahg: unfortunatly there isn't, I started down that path
[21:10] <tumbleweed> the closest I can get is bugs both people are subscribed to
[21:10] <micahg> tumbleweed: the info is certainly in LP
[21:11] <tumbleweed> micahg: yeah, but not queryable over the API (that I could work out)
[21:12] <tumbleweed> another complication is archive-admin-assisted syncs, which this script misses
[21:14] <ari-tczew> tumbleweed: what
[21:14] <ari-tczew> is the command?
[22:41] <bdrung> tumbleweed: the quality requirements are raised - new code needs to have unit tests
[22:42] <bdrung> tumbleweed: and please document the get_value function. in which order are which values evaluated? (and give an example).
[22:43] <bdrung> from low to high: /etc/devscripts.conf, ~/.devscripts, environment variable
[22:44] <bdrung> tumbleweed: would you mind releasing config.py under ISC?
[22:45] <tumbleweed> bdrung: scripts get tricky to test, but yes I was considering that.
[22:45] <tumbleweed> I have no problem with ISC
[22:45] <ebroder> bdrung: Can I talk you into putting off your testing requirement until New Year's or so? I'm planning to have time to setup a testing infrastructure during my time off
[22:45] <bdrung> tumbleweed: this script is easier to test than online requiring tools like sponsor-patch
[22:46] <tumbleweed> bdrung: yeah, the library stuff is testable, the wrapper-scripts less so
[22:46] <bdrung> ebroder: yes
[22:47] <tumbleweed> btw, I'm not using environment variables, except through the compat_vars mechanism (copying devscripts style)
[22:48] <bdrung> tumbleweed: environment variables should be always supported
[22:48] <tumbleweed> bdrung: ok, that's what I was originally planning, I didn't realise how little devscripts used them
[22:49] <bdrung> tumbleweed: the devscript config files should just be another place for storing those environment variables
[22:50] <bdrung> ebroder, tumbleweed: delaying the setup of a testing infrastructure doesn't prevent us from thinking about testcases