[00:11] <jono> anyone here familiar with writing PyGI apps?
[13:17] <alabd> Good day all , wana chanage perm of a file on ntfs usb external hard disk , but without error chmod 777 does not take affect
[13:18] <commandoline> alabd: you might be helped better in the help channel: #ubuntu
[13:18] <commandoline> this channel is about development of Ubuntu
[13:20] <alabd> ok thanks  bye
[13:36] <valterstr> hello
[13:36] <valterstr> I would be interested in developing ubuntu
[13:37] <valterstr> and this will sound silly, but, what programming language is used?
[13:39] <bkerensa> valterstr: A variety
[13:39] <valterstr> I am looking at https://code.launchpad.net/~ubuntu-branches/ubuntu/precise/bzr/precise
[13:40] <valterstr> lp:ubuntu/bzr
[13:40] <valterstr> vala seems to be used
[13:41] <valterstr> but the directory tree is unusual for mee.
[13:41] <penguin42> valterstr: I'm not sure if there are many things that use vala; but it's quite neat; but there is a lot of C, Python, C++, perl - everything really
[13:42] <valterstr> is there an ide?
[13:42] <valterstr> wait. valac-*.**
[13:42] <valterstr> ?
[13:42] <penguin42> a few - I don't use them myself; I think anjuta is used by various people, not sure what it's like or which languages it supports
[13:42]  * valterstr googes...
[13:42] <valterstr> *googles.
[13:43] <valterstr> looks good. will install.
[13:43] <valterstr> many dependencies...
[13:49] <valterstr> I have the source files and I have Anjuta
[13:50] <valterstr> Now when I try to import the project, it asks if I want to use makefile backend or directory backend.
[13:50] <valterstr> which should I choose?
[13:51] <valterstr> testing makefile then...
[13:52] <valterstr> looks ok. but could someone explain which files is the code itself in?
[13:59] <valterstr> as I have understood, /bzrlib contains the software code in lp:ubuntu/bzr
[14:00] <valterstr> but in lp:ubuntu/cowbell it is /base
[14:00] <valterstr> @penguin42: so, there is no "default" directory tree?
[14:00] <udevbot_> Error: "penguin42:" is not a valid command.
[14:00] <valterstr> penguin42: so, there is no "default" directory tree?
[14:01] <penguin42> I don't know what you mean
[14:01] <valterstr> I mean, e.g. all software files are held in /base folder.
[14:01] <valterstr> it is different for different packages
[14:02] <valterstr> ubunte/cowbell package files: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/cowbell/precise/files
[14:03] <valterstr>  /base folder is used there
[14:03] <valterstr> ubuntu/bzr package files: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/bzr/precise/files
[14:03] <valterstr>  /bzrlib is used.
[14:04] <valterstr> penguin42: that's what I mean.
[14:04] <commandoline> valterstr: Ubuntu consists about a number of different programs, different packages. They use all kinds of different programming languages and different directory tree structures, it depends on the preference of the developers of the packages.
[14:04] <penguin42> valterstr: Some of those directories are just what the author decided they wanted - that's the source tree, and the author can make up those names as they want
[14:05] <valterstr> ok
[14:05] <penguin42> valterstr: There are some that are fixed in debian/ubuntu packages (e.g. the debian directory) and some that are common (e.g. po and lib)
[14:05] <valterstr> noticed.
[14:05] <valterstr> thanks for the info.
[20:06] <glD> Hi all, I have a problem with new package "esys-particle". It builds fine, but on Ubuntu during start the following error appears
[20:06] <glD> "ImportError: /usr/local/lib/python2.7/dist-packages/esys/lsm/util/libFoundationPy.so.0: undefined symbol: _ZTIN5boost6python15instance_holderE"
[20:06] <glD> It seems, it is an ubuntu-related problem, because the same package works fine on Debian
[20:07] <glD> I would appreciate, if somebody gives an advice how to fix that
[20:07] <glD> there is a corresponding bug on that: https://bugs.launchpad.net/esys-particle/+bug/916724
[20:08] <glD> thanks ahead
[20:20] <jtaylor> most likely an as-needed problem
[20:20] <jtaylor>  /usr/local/lib/python2.7/dist-packages/esys/lsm/util/libFoundationPy.so.0 is probably not linked correctly
[20:21] <jtaylor> glD: ^
[20:21] <jtaylor> do you have a buildlog of it?
[20:22] <glD> jtaylor: yes, just a moment
[20:23] <glD> Debian: https://buildd.debian.org/status/fetch.php?pkg=esys-particle&arch=amd64&ver=2.1-1&stamp=1324594155
[20:23] <glD> Ubuntu: https://launchpadlibrarian.net/89385870/buildlog_ubuntu-precise-amd64.esys-particle_2.1-1_BUILDING.txt.gz
[20:31] <jtaylor> glD: there is a bunch of stuff underlinked, see the dpkg-shlibdeps warnings
[20:31] <jtaylor> also in debian
[20:31] <jtaylor> that should be fixed
[20:35] <glD> jtaylor: ok, thanks
[20:35] <glD> I will try
[20:35] <jtaylor> python is often one of the first to notice that as undefined symbols in pythion extensions are pretty normal (e.g. libpython stuff)
[20:36] <jtaylor> thus problems only detected at runtime
[20:36] <glD> jtaylor: it means, that the code should be patched somewhere?
[20:37] <jtaylor> no its a makefile issue
[20:37] <glD> Ok, thanks
[20:54] <jtaylor> that package has a bunch of far to general library names
[20:54] <jtaylor> libFields, libParallel
[20:54] <jtaylor> libModel
[20:55] <jtaylor> how did that get through in debian :O
[20:56] <glD> jtaylor: it should be something like libEsysModel, libEsysFields..?
[20:56] <jtaylor> probably yes
[20:56] <jtaylor> or they should be private libraries
[20:56] <jtaylor> = installed in a subfolder of usr/lib
[21:22] <glD> jtaylor: there are also errors on both buildlogs
[21:22] <glD> ImportError: libFoundationPy.so.0: cannot open shared
[21:22] <glD> |            object file: No such file or directory (line 15)
[21:29] <jtaylor> glD: thats a problem of the PYTHONPATH
[21:30] <jtaylor> or library path not sure
[21:30] <jtaylor> should not be a problem when the package is installed
[21:30] <jtaylor> setting this should work LD_LIBRARY_PATH=debian/tmp/usr/lib/python2.7/dist-packages/esys/lsm/util/
[21:31] <glD> ah, ok
[21:31] <jtaylor> having that in PYTHONPATH  should do the same
[21:32] <glD> jtaylor: what do you think, why the problem appears in Ubuntu, not in Debian?
[21:32] <glD> I mean the first problem, with symbols
[21:33] <jtaylor> ubuntu enables as-needed during build by default debian does not
[21:33] <jtaylor> this has some effect on indirect links which are used here
[21:34] <glD> can the "quick" workaround be to switch off it? --no-as-needed to make the package working?
[21:34] <glD> and then to fix all of other issue
[21:34] <jtaylor> the fix is to link everything properly
[21:35] <jtaylor> underlinking library causes all kinds of issues
[21:35] <jtaylor> In my opionion those dpkg-shlibdep warnisn should be errors, that would save a huge amount of trouble
[21:35] <jtaylor> nobody reads warnigns ...
[21:42] <glD> jtaylor: ok, thank you!
[21:42] <glD> will try to fix that
[22:07] <jtaylor> glD: one issue is in debian/rules, LDFLAGS := -lboost_system
[22:07] <jtaylor> libraries do not go in LDFLAGS, those will be placed wrongly by autotools
[22:08] <jtaylor> LIBS is normally the correct varaible
[22:08] <mdeslaur> hallyn: yes, iso downloads use releases.ubuntu.com
[22:24] <tsdgeos> tkamppeter: you around by chance?
[22:28] <tkamppeter> tsdgeos, hi
[22:29] <tsdgeos> tkamppeter: seen my mail about the huge speed regression?
[22:30] <tsdgeos> tkamppeter: re poppler and lcms
[22:33] <tkamppeter> Yes, so you found one PDF where Poppler with lcms2 takes 10 times longer than Poppler with lcms1?
[22:34] <tsdgeos> i had found that pdf already in 2010 yes
[22:34] <tsdgeos> but nobody seems to read the mails i sent back then :D
[22:34] <tkamppeter> tsdgeos, can you attach the file to the thread or at least send it to me?
[22:34] <tsdgeos> google for it, it's everywhere
[22:34] <tsdgeos> http://www.eci.org/doku.php?id=es:downloads
[22:35] <tsdgeos> altona_technical_1v2_x3.pdf
[22:35] <tkamppeter> tsdgeos, that time you did a migration, nmow Koji Otani did one independently. Did you already try to run the file through Koji Otani's version of the migration?
[22:35] <tsdgeos> err
[22:35] <tsdgeos> is my english that bad?
[22:35] <tsdgeos> yes, i used koji's version
[22:36] <tkamppeter> tsdgeos, is this the only file which gets that much slower, you told abot 5-10% performance loss is usual.
[22:37] <tsdgeos> that was koji
[22:37] <tsdgeos> and me too probably
[22:37] <tsdgeos> originally i found it to be even faster on some files
[22:37] <tsdgeos> but going from 0.5 to 5 sec
[22:37] <tsdgeos> is a bit of a no go
[22:38] <tsdgeos> i did not try any other files
[22:39] <tkamppeter> If it is only that one file, you should perhaps report a bug to the lcms developers with the file attached and also tell Koji as he did the migration (and so he could have done something wrong, too).
[22:39] <tsdgeos> have you even looked at the patch?
[22:39] <tsdgeos> the migration is basically renaming of stuff
[22:39] <tsdgeos> you can't do that wrong
[22:40] <tkamppeter> tsdgeos, OK, then it looks more like a bug in lcms2 which gets triggered by said file.
[22:41] <tsdgeos> i'd agree
[22:41] <tsdgeos> i prefer to use software i know it works instead of buggy one
[22:42] <tsdgeos> and i'd suggest ubuntu to the same ;-)
[22:42] <glD> jtaylor: ok, thanks, will fix that
[22:42] <jtaylor> glD: also it appears the libraries don't link with libTml*
[22:43] <jtaylor> that has been patched for the executables, but not for the libraries
[22:43] <tkamppeter> tsdgeos, to do a real test one should use a large amount of PDF files (you should have some test repository of PDFs for Poppler's QA) and run them all through the current Poppler, once with and once without Koji's patch, afterwards counting how the results compare in speed and also how many crash without and how many with the patch.
[22:44] <tsdgeos> tkamppeter: i can't make my pdf suite public, i don't have rights to distribute them
[22:45] <tsdgeos> tkamppeter: how many crash without the patch? none
[22:46] <tkamppeter> tsdgeos, but you can publish the statistics.
[22:46] <tsdgeos> sure
[22:46] <tsdgeos> i don't feel like doing the work since i've already found a showstopper
[22:47] <tsdgeos> i mean, found it two years ago :D
[22:53] <tsdgeos> anyhow, sleep time, let's see if either koji or the lcms dude you put in the CC have anything to say in the matter
[22:54] <tsdgeos> night@all
[23:33] <slangasek> hallyn: bug #893450> cjwatson is certainly the expert where sector sizes are concerned... not sure how high that'll be on his list though :/  The bug description sounds like a race condition, not a perf problem?