[01:02] Hey all. I'm at an ISP, with an Ubuntu mirror which is already listed on launchpad under a former employee's details rather than an official address. What can I do to get this rectified? [01:08] zatricky: Ask a question at https://answers.launchpad.net/launchpad/+addquestion and an admin can sort it out for you. [01:09] thanks, I'll take it there [11:59] hi all, i am trying to build a new package for gnupg2, importing the old package into git with git import-dsc. when building with git-buildpackage, the compilation fails because of `binary file contents changed' errors. how can this be resolved? === jelmer__ is now known as jelmer [15:28] http://bazaar.launchpad.net/~zookeepr-contributors/zookeepr/contributors/annotate/head%3A/zookeepr/model/event.py?file_id=models-20060409124320-ab387444f2f673ff [15:29] why don't I see any lines? file size says 1.5K [16:40] I have some basic questions: I have a project (not on launchpad) and I would like to know how hard it would be to make it an ubuntu package and host it on launchpad. Which would be the best place to ask my (possibly stupid) questions? [16:42] its a python application and I have a script that runs it all through pyinstaller copies the resulting binaries and other needed files into a fakeroot and creates a binary .deb package already but it seems launchpad needs source packages and i have not the slightest clue how to do this [16:48] this is what I have used all the time to make the binary .deb http://pastebin.com/m7eSEF0j it is probably the complete wrong way but it is the simplest I have found and it works. I assume I would hzave to throw away all this and write complicated makefiles (no clue) and setup.py (no clue about it either) to make it work? [16:49] i have seen a dozen websites that explain all this as complicated as possible but I still miss the essence of it. There must be an easy way that is not twice as complicated as writing the application itself!? [16:51] what is the best place to ask these questions? [16:52] is there a mailinglist? the launchpad website has a zillion pages but no mention of a forum or a mailinglist for such beginners questions [16:53] am I in the wrong channel? [16:56] prof7bit: hi [16:56] hi [16:56] prof7bit: no, you're in the right channel but it's weekend now so there aren't a lot of people here [16:57] prof7bit: you would need to build a proper source package to have it built on launchpad [16:58] there are several packaging guides on the ubuntu wiki and the debian homepage explaining how to create packages [16:58] the #ubuntu-packaging channel is the primary channel for that kind of discussion [16:59] i have seen some of these guides, the problem is they all seem ten times more complicated than it was for me to write my application (sorry if i sound a bit frustrated) [17:01] prof7bit: that script only creates a binary package, not a source package [17:01] prof7bit: it's also very specific to your local environment [17:02] yes. the reason is i don't know how to make a source package for the only purpose to later make this binary package, thats the reason why i made this simple script that just puts the needed files together and then calls dpkg [17:02] prof7bit: so other people can modify the package, and so it can be rebuilt on launchpad [17:03] prof7bit: https://github.com/astraw/stdeb is sort of neat and might be worth a look [17:03] i assume i would have to put pyinstaller itself into the source package to make it build on the launchpad server [17:04] I'm not sure what pyinstaller is [17:05] similar to py2exe. it packs all python files and the python interpreter and wxpython and all needed libs into one executable that has no other dependencies than gtk2 [17:06] so i avoid problems with people having different versions of python and wxpython installed [17:07] an older version of my script ust distributed the python files themselves and i made it depending on python >= 2.5 but suddeny it broke with python 2.7 and this is what i want to avoid [17:11] i'm a great fan of self-contained software that "just works". therefore my affinity to tools like py2exe or pyinstaller or static linking or bundling all dependencies in one package [17:12] there are arguments against it, but i want to make things as robust and simple as possible [17:13] I imagine to make a source package of such a thing, you'll need to build all of those dependencies, not just include their ultimate binaries in your package [17:13] (the windows version of my application would run off a thumb drive on any windows >= XP) [17:14] maybe launchpad is not the optimal platform for this type of application [17:15] could be. otoh, you could also just add a 'python < 2.7' dependency to your package and not bundle all the depencencies. [17:17] (separate topic) does it make sense to have two different piles of code beneath a single launchpad project? in unrelated bzr branches? [17:17] the 2.7 problem is solved already, it was just an example. But I also want to make a distribution which is the equivalent of the "portable" windows version: something i can simply put on a thumb drive, plug it into any ubuntu PC and ust run it from there. [17:18] I have my actual project and another project that's a dependency, but could easily be used elsewhere. Can I host their code at the same place? Or should I make a new launchpad project for the dep? [17:18] prof7bit: Nothing says you have to abandon your pyinstaller for other platforms. But maybe it's not the best approach to packaging for Ubuntu. [17:19] and i thought if i already have a script that builds this portable linux app i can also ust stuff the binaries into a .deb for easy permanent installation [17:19] prof7bit: The self-contained version for Ubuntu is a deb, and debs for all its dependencies. [17:19] Of course, you can also keep doing what you're doing now, but launchpad probably won't help much, because it wants to build packages for a bunch of architectures and ubuntu releases. [17:20] And having big binary blobs in the package definition isn't compatible with that. [17:21] if i make a .deb that only contains the .py files and a start script in /usr/bin to start the application, would this be a binary or a source deb or something else? [17:21] it would not be able to create a binary deb but it could run from the .py files already [17:22] but it would be a "binary" in the sense that it contains runnable code [17:23] simple exmple: a .deb that only contains /usr/bin/hello.py [17:23] nothing else [17:23] what would this be? a source or a binary? [17:24] it could be installed without problems and then run, so it would be a "binary", wouldn't it? [17:25] I only sort of know what I'm talking about now, but I think you're misunderstanding the difference between source and binary packages [17:26] but if i upload this as a source package to launchpad what would happen on the server? [17:26] what would it try to do with it? [17:27] it will do the only thing it knows how to do, build binary packages out of it [17:27] that mostly means "run a makefile you provide" [17:28] and now I'm in danger of telling you completely made up things, so don't ask me any more questions about this :) [17:28] what would i put into this makefile? would it just be empty and do nothing (/usr/bin/hello.py is already executable) [17:29] and *where* do i put this makefile? [17:30] there is no source folder, there is only /usr/bin/hello.py [17:34] (sorry if i sound too frustrated, but i only see a myriad of overcomplicated things to achieve such a simpla task as ust copying one file into the directory where it belongs) [17:34] * exarkun shrugs [17:35] making debian packages isn't trivial, no doubt about that [17:35] I'd answer more of your questions, but I always give up at about this point [17:37] making a deb that ust works is actually quite eaysy (see my script, just copy the files where they belong and then dpkg -b) , what makes it complicated is the distinction of source and binary and the need for makefiles and other complicated things. [17:37] * exarkun shrugs === yofel_ is now known as yofel [20:07] hi [20:07] where can i find the list of supported sections in the debian/control file ? [20:07] Rejected: [20:07] gmediafinder_0.1-1.dsc: Unknown section 'AudioVideo' [20:07] ... [20:09] smo_, http://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections [20:10] thanks gusnan [20:33] ok, second thing i don t understand, i just made a change for the section in my debian/control file, i do the debuild... then reupload with dput and i have rejected package: File gmediafinder_0.1-1.debian.tar.gz already exists in Gstyle PPA, but uploaded version has different contents [20:34] i go in my pool, redownload the original orig.tar.gz, redo the debuild -S again and still rejected ??? [20:35] oh sorry [20:37] why doesn't launchpad know the ISC license? [21:05] raaaah, debuild regenerate my .debian.tar.gz file each time, how can i bypass it please? [21:07] smo_: it's supposed to [21:08] ok but my package is rejected for that [21:08] File gmediafinder_0.1-1.debian.tar.gz already exists in Gstyle PPA, but uploaded version has different contents [21:08] ... [21:08] smo_: only if it's the same version, you can't upload the same version twice [21:10] so what must i do? ^^ [21:11] bdrung: Only a few common licenses from each category are listed. [21:11] smo_: Change the version number. It is conventional to do call the version version 0.1-0ppa1, the second 0.1-0ppa2, etc. [21:11] ok wgrant [21:11] thx [23:16] Ursinha-afk: help me please