=== nhandler_ is now known as nhandler [01:26] I applied a lot of patches to some code. I know the configure and generated_lists files changed. Because those two files changed I know that files in debian/ need to change. the configure file changed a lot. How should I handle this with the rules file? [01:26] or, it debian/ at all? [01:27] What are you trying to accompiish? [01:27] More detail helps get a real answer. It may get you redirected, but that's not enough for any value. [01:28] persia: I'll show you what I'm looking at [01:29] http://github.com/dreamcat4/php-fpm/blob/master/readme.markdown -- "Integrated Compilation" [01:29] I really think you want to talk to PHP packagers about this :) [01:29] You didn't find them here really, other than pointers to PPAs. [01:29] I have php5-5.3.1 building the package successfully; I applied those patches [01:30] Maybe some of the PPA owners, or the debian folk. [01:30] So, you changed some configure flags. [01:30] Which changed the set of files that were produced. [01:30] And the .debs that you ended up with didn't include these files/ [01:30] none yet, there's a ./buildconf --force that auto generates the whole configure file [01:31] s#/#?# [01:31] I didn't make a .deb yet because I know things will be exactly as they are now [01:31] Will they? That's usually not the case. [01:31] oh.. [01:32] Go test, and when you get a failure, maybe someone can help. [01:32] ok [01:32] I just know I'm far from done [01:32] (but again, we don't necessarily know much about PHP packaging) [01:32] I definitely don't. === nhandler_ is now known as nhandler [01:32] And you can' make me. [01:32] right, I could ask in debian-mentors but I just like the friendly in here [01:33] MTecknology: Have you tried asking the debian maintainers? That's probably better than debian-mentors. [01:33] where do I find them? [01:34] I see a name in the changelog- jsut email? [01:37] persia: does my unwaivering determination at least impress you a little? [01:38] :) [01:38] Not especially. Lots of people are determined :) [01:39] I''d be more impressed if you were working closely with the Debian PHP team, and interested teams in Ubuntu towards accomplishing something that would generally improve Ubuntu. [01:39] am I at least a little more unique? [01:39] But maybe I have a narrow focus :) [01:40] hey - do you ever sleep? [01:40] Several times a week, at least. [01:41] I just don't happen to have a close attachment to the planet's diurnal period. [01:41] I was just wondering because I went to sleep, you were on; i woke up, you were on; i'm on now, you're on [01:42] it's building in pbuilder === nhandler_ is now known as nhandler [02:06] persia: my proc is almost 200 deg F [83 deg C] [02:07] 188.6F [02:09] 206.6 F [02:18] 212 F [02:31] Is there a way to run the configure step of a deb alone? [02:35] Argh. Never mind that won't help me in any case. [02:35] quidnunc: Maybe dpkg-reconfigure? [02:35] heh :) [03:06] it's almost done building - i think [03:09] persia: it built fine in pbuilder - no idea what to do now :P [03:09] gotta run for a bit [04:47] Good morning [05:50] my doubt is more or less like I want to package the latest pidgin. how do I know what its dependencies are? Where do I see it? [05:50] micahg: ^ [05:50] nigelb: there's already a pidgin developers PPA [05:50] nigelb: https://launchpad.net/~pidgin-developers/+archive/ppa [05:51] I know [05:51] its more for the learning that for usage [05:51] I dont really want to install it, but I'm trying to learn the process [05:51] nigelb: for compiled apps, look at the configure file [05:51] ah [05:55] micahg: whoa, thats a big mess. is there a shortcut here? [05:56] nigelb: a README or INSTALL file possibly...maybe you should start with a smaller app [05:57] micahg: suggestions? (I thought pidgin was small) [05:58] nigelb: maybe gtg [05:58] micahg: lemme try that out [05:59] nigelb: pidgin is small compared to firefox [05:59] which is small compared to openoffice.org [05:59] everything is relative :) [05:59] heh [06:40] nigel_nb: BTW, there are many pieces to packaging...patching would be first I would think [06:40] micahg: lol, I'm pretty sure of my way with patching now [06:40] micahg: patched 2 packages now [06:41] third one, probably before I hit the bed [06:41] nigel_nb: k, that's good, how about merging/updating a package, that would be step 2 I would think [06:41] micahg: unfortunately, I got involved with motu around feature freeze, so now I'll wait until next cycle to learn more [06:43] nigel_nb: feature freeze doesn't stop everything [06:43] nigel_nb: There's heaps of work doing in MOTU if you're looking for something. [06:44] persia: there is? [06:44] No need to wait until the next cycle. [06:44] There is. [06:44] um, how do I find it? [06:44] So, there's about 20,000 bugs open and many are triaged, and need fixing. [06:44] Ask, usually. :-) [06:44] I'm in the processing of fixing one ;) [06:44] nigel_nb: You'll learn not to say you're bored around persia -- he'll bury you in work. [06:45] StevenK: oh [06:45] There's heaps of packages in the archives with unmet dependencies, which will make users unhappy if they try to install them. [06:45] Running `apt-cache -i unmet` against a lucid apt-cache will show a goodly list. [06:45] the unmet dependency is something I want to understand too [06:45] There's a bunch of packages that can't be built, and someone needs to fix those. [06:45] Any of that interest you, or you want more categories ? [06:46] whats the sane way to figure out dependencies? [06:46] I'll stick to that one [06:46] OK. [06:46] So, with apt-cache you can get a list of stuff that is broken. [06:46] Often this is because there was some change in packaging since the last release. [06:47] So it's just a bit of detective work to read the history of the packages that aren't provided anymore by comparing karmic and lucid. [06:47] And then checking how the dependencies are set in debian/control in the affected package. [06:47] And then making some changes. [06:47] can you help on one such example? [06:47] This kind of work is also a good way to better understand package relationships, get famliar with control files, and learn the various ways one calls apt-cache. [06:48] * micahg still needs to learn that [06:48] OK. Let's look at boa-constructor. [06:48] It has an unmet dependency on pychecker. [06:49] Do you see that? [06:49] yea, package not available [06:50] OK. Now take a look at a karmic apt-cache. [06:50] for boa or pycheker? [06:50] For pychecker. [06:51] I see it [06:52] OK, Next hunt down the latest changelog for that source on changelogs.ubuntu.com [06:54] there is only a kamic changelog [06:54] nothing for lucid [06:54] Well, that's true for thoulsands of packages. [06:54] so, we gotta bring it to lucid? [06:55] Well, not necessarily. [06:55] First we find out why it's not there. [06:55] Usually this is a removal. [06:56] ah [06:57] So, looking at the changelog, there are some "unstable" entries, which means it was in Debian also. [06:57] yeah [06:57] If we remove a package from Ubuntu only that is still in Debian, it shows up in the blacklist:http://people.canonical.com/~ubuntu-archive/sync-blacklist.txt [06:58] this could also help. https://edge.launchpad.net/ubuntu/+source/pychecker/+publishinghistory [06:58] You can check the status of the package in Debian at http;//packages.qa.debian.org [06:59] ah, pychecker was removed because it depends on python 2.5 [07:00] nigel_nb: Note that 0.8.18-2ubuntu1 was removed. [07:00] Now check the status in Debian. Is there a newer version? [07:00] (or revision, technically) [07:00] there is a 0.8.18-3 version [07:01] Now, check that changelog entry and see if it says anything about adding support for python2.6 [07:01] nope [07:02] In that case it's probably still not ported. [07:02] So we aren't going to be able to get back pychecker. [07:02] so we remove boa? or add python 2.5? [07:02] Next, take a look at the boa-constructor source. See if you can figure out why it needs pycheker. [07:02] One of the release goals for lucid is to not ship python2.5 :) [07:04] getting source [07:04] but I'm not if I can poke around enough to figure out if it needs pychecker [07:05] Well, it's not usually that hard to figure out. [07:05] Running grep on the source is often enough. [07:05] oh [07:06] something wrong with archive today? seems to be awfully slow [07:07] It's probably your mirror (or you don't have one set up). [07:07] i'm degetting the dsc file from package.ubuntu.com [07:07] I dont think that uses a mirror [07:07] good morning [07:08] I'm seeing slowness as well, but it's a Telstra problem [07:08] mine's not really slow. Its stuck! [07:08] nigel_nb: apt-get source in a lucid chroot/install is better. packages.ubuntu.com can be days out of date sometimes. [07:08] I only see "HTTP request sent, awaiting response... " [07:08] sudo pbuilder login works fine? [07:09] Plus, with apt-get source you can set up multiple source mirrors in your sources.list, and it pulls from the the first one in the last that contains the newest source. [07:09] Sure. That's a fine way to get into a chroot :) [07:10] my chroot is a mess [07:11] it doesnt have a sources.list it seems? [07:11] "You must put some 'source' URIs in your sources.list" [07:11] It ought to. [07:11] Oh, it has a sources.list, but it doesn't have any deb-src lines [07:12] now, I have to take the pain of install vim inside chroot [07:13] If you're not running lucid and you're developing lucid, it may be convenient to set up a long-running development chroot. [07:13] meaning? [07:13] For instance, create a new tarball with pbuilder and give it a different name. Install all your development tools in there with --save-after-login [07:13] Or use a persistent schroot. [07:14] I have no clue how to do either, but the first one sounds attractive [07:14] There are a number of packages where the source only builds (or only builds correctly) in lucid. [07:14] I use pbuilder-dist for building packages [07:14] Well, if you set up pbuilder the first time, you'd just run the script again, perhaps with an extra parameter. [07:14] and pbuilder as such for other stuff.. like now [07:15] I should probably isntall an ubuntu-minimal in one of them [07:16] Hrm. I'm not sure how to advise you to do this with pbuilder. [07:16] I don't see any --name option or anything. [07:17] And I'm not going to recommend someone running karmic install schroot unless they have some specific reason for doing so, because it's complicated (and most of the complication goes away with lucid) [07:19] this is turning up even more screwed up [07:19] How so? [07:20] Is this the correct line? "deb-src http://lk.archive.ubuntu.com/ubuntu/ lucid main restricted universe multiverse" [07:21] I get the error "E: Could not open file /var/lib/apt/lists/lk.archive.ubuntu.com_ubuntu_dists_lucid_main_source_Sources - open (2: No such file or directory)" [07:21] Did you run apt-get update after adding the line? [07:21] ugh [07:22] looks like I'm doing all the wrong things posible [07:24] persia: I'm going to loose power in exactly 8 minutes. If I get cut off, we'll have to pick up 2morrow [07:24] (scheduled power cuts) [07:24] nigel_nb: where do you stay? [07:24] stefanlsd: India [07:24] nigel_nb: You're going to have to remind me where we are from scratch, but OK. [07:25] if we're lucky it may go an hour late, never know ;) [07:27] OK. So when you have source and a working environment, run grep :) [07:27] yeah, def an issue somewhere, cant connect to security.ubuntu.com from za and us [07:28] ah, so it was not just me [07:39] apt-get source is pulling from debian svn, is that sane? [07:42] Not only is it not sane, it's wrong. Are you sure, or is it just warning you that the soruce is in svn? [07:42] its just warning me I guess [07:43] * persia got a warning, but pulled from the mirror === hannesw_ is now known as hannesw [08:05] persia: if you're still around, I did a grep [08:06] And what did you see? [08:06] i see something in prefernces [08:07] and controllers [08:07] OK, so this tells us that the code is really using pychecker. [08:07] So, we have three options [08:08] 1) remove boa constructor [08:08] 2) patch boa constructor to not use pychecker (which means going through the source, and finding out how it's used, etc.) [08:09] Because it's listed in Preferences, this might be just a matter of adjusting the default preferences, adding a wrapper around the actual pychecker call to report an error if pychecker is missing, and demoting pychecker to Suggests: [08:11] 3)demote pychecker to Suggests, change the default config, file a bug about boa constructor crashing when configured to use pychecker and pychecker is not installed. [08:11] Of these, 2) is generally preferred, because 1) removes something that doesn't *have* to be removed and 3) leaves a buggy package for users. [08:12] Since this is going to take a while, file a bug about it and assign yourself. [08:13] When you have questions, ask them here. Lots of people know python and will gladly help you work on unmetdeps [08:13] persia: I got till "Because.." [08:13] (lost connection in between) [08:14] Ah. [08:14] 3)demote pychecker to Suggests, change the default config, file a bug about boa constructor crashing when configured to use pychecker and pychecker is not installed. [08:14] Of these, 2) is generally preferred, because 1) removes something that doesn't *have* to be removed and 3) leaves a buggy package for users. [08:14] Since this is going to take a while, file a bug about it and assign yourself. [08:14] When you have questions, ask them here. Lots of people know python and will gladly help you work on unmetdeps [08:14] is there a standard format for the bug? [08:17] Not really. [08:18] File it against boa constructor reporting that boa-constructor cannot be installed in lucid. [08:18] Explain why it can't be installed. [08:19] is there a way to test run the code I edit? [08:19] Yes, but I don't know how to do it with your environment, so I'm going to give you general guidelines. [08:19] k [08:20] 1) Run what-patch to determine how to patch the source, and follow that method. [08:20] 2) build the source package including your changes and build it locally with your preferred build tool [08:21] 3) Enter a chroot preserving enough environment to be able to launch xclients inside the chroot and show them on your main X server [08:21] 4) install the program in the chroot and run it [08:21] Note that this method has limitations: it can't test stuff that really exercises X or the kernel or does lots of D-Bus coordination, etc. [08:21] I didnt understand step 3 [08:22] But for standalone apps with no hardware interaction, it works great. [08:23] I don't know how to do it for your environment. I use e.g. `schroot -c -p lucid-armel` [08:23] Err, "-p -c" [08:23] I can build another evironment (I really dont mind) [08:23] Do you already use LVM? [08:24] no :( [08:31] nigelb: Then just ask someone else how to access the system X server from inside a pbuilder chroot. That I don't know shouldn't either limit you or require you to do strange things to your system. === yofel_ is now known as yofel [09:40] * siretart` would very much appreciate testing of x264 encoding with the [09:40] recently built ffmpeg-extra package in lucid [09:41] it is using a very recent x264 version to encode, a libx264.c wrapper has been backported [12:44] dholbach: ping [12:45] dholbach: rowinggolfer in #launchpad has agreed to join me in the PPA session [12:51] shadeslayer: can you please mail packaging-training-coordinators @ lists.launchpad.net with the details? [12:52] thanks a bunch in advance [12:52] :) [12:52] sure :) [12:52] dholbach: what details would you need btw? [12:53] who, when, what :) [12:53] ok :) [12:53] thanks :-) [13:25] dholbach_: dispatched a mail to the abovesaid address [13:25] shadeslayer: awesome, thanks [13:25] shadeslayer: somebody should be in touch with you soon === dholbach_ is now known as dholbach [13:34] fta, Is there a way to get older releases of your daily thunderbird from the ubuntu-mozilla-daily ppa? Thunderbird 3 is horribly broken and has been for a week or so [13:38] dholbach: awesome :) [13:38] I'm new here and I'm new to packaging... I want to update a package in jaunty as its old compared with the karmic package [13:38] I'd like to contribute and I'm reading this: https://wiki.ubuntu.com/PackagingGuide/Complete [13:39] Could someone please re-assure me that this isn't as difficult as it looks? :) [13:40] rlp10: it isnt [13:40] rlp10: i can help :) [13:40] rlp10, There is a good chance you could just download the source package, rebuild it with pbuilder, and have shiney debs [13:40] rlp10: since the package is already in the repos,its *very* easy [13:41] yay :) [13:41] can anyone tell me what the *.install files created by dh_create do? [13:41] is there somewhere I should be looking at with instructions to do that rather than the complete packaging guide? [13:41] rlp10: if you have a launchpad account its super easy [13:41] ok, I'll sign up now [13:42] rlp10: ill help you step by step if you want [13:42] shadeslayer: can you help me step by step? :D [13:42] shadeslayer: thanks so much [13:43] I need a lot of help :P [13:43] MTecknology: sure [13:43] MTecknology: ive learnt how to package stuff already in the repos [13:43] MTecknology: and not fishy stuff like hookscripts :D [13:43] s/not/no [13:44] MTecknology: what are you trying to package? [13:44] shadeslayer: I'm logged into launchpad [13:44] shadeslayer: well, I aplied patches for php-fpm to php5-5.3.1. I know how to build what I have from source and get what I want, but I want to build this package. [13:45] MTecknology: ok is this a existing package [13:45] rlp10: ok now make a PPA [13:45] ya, not in ubuntu repos yet [13:45] rlp10: you cannot change your launchpad url after you do this! [13:46] MTecknology: ok im struggling with native packages right now :P [13:46] MTecknology: i can help with : https://wiki.ubuntu.com/PackagingGuide/Complete [13:47] shadeslayer: I think this is beyond that massive document :P - all I have left to figure out is the debian/ stuff [13:47] rlp10: also read this : https://help.launchpad.net/Packaging/PPA [13:47] I'm kind of considering just building it from source on my server and letting a really smart person take over the rest [13:47] shadeslayer: thanks, reading [13:47] MTecknology: theres a script called dh_make which does all the stuff for you [13:48] MTecknology: usage is : dh_make -e myemail@host.com [13:48] shadeslayer: I was trying to work off of what they already did [13:48] you think I should start with a fresh debian/ ? [13:48] MTecknology: ok well you need the patch system in the rules file [13:48] MTecknology: well... depends [13:49] MTecknology: it would certainly help :) [13:49] If that's best I'll gladly do it [13:50] I'll pull up info on the patch I've been working with [13:51] http://github.com/dreamcat4/php-fpm/blob/master/readme.markdown - "Integrated Compilation" [13:51] shadeslayer: so I need to make a PGP key and sign the code of conduct, right? [13:51] MTecknology: you just need to add one line in the rules file to implement the patch system [13:51] rlp10: yes [13:51] rlp10: you do know how to make one? [13:51] shadeslayer: no sorry, I understand the concept in general terms tho [13:52] rlp10: youll also need to authorize a few packages for uploading stuff to the ppa [13:52] shadeslayer: ooh, that's how I should have applied patches.... [13:53] shadeslayer: what does authorise mean in this context? [13:53] I'm trying to install files from usr/lib/python*/site-packages/autokey/gtkui into my package, but dh_install doesn't seem to be expanding the glob. How should I write this for it to work as I intend? [13:53] rlp10: authorise as in.. make launchpad realise that this upload should go to your ppa [13:54] shadeslayer: ok... I'm following instructions here for creating a key https://help.ubuntu.com/community/GnuPrivacyGuardHowto [13:55] rlp10: cool :) [13:55] shadeslayer: I just removed the patches I applied and moved the patch to debian/patches/ [13:55] rlp10: also according to launchpad : These applications have been authorized to access Launchpad on your behalf. If you revoke an authorization, that application will not be allowed to do anything in Launchpad on your behalf. [13:55] MTecknology: thats better :) [13:55] shadeslayer: I feel better; this makes more sense too [13:55] MTecknology: do you know the line you need to put to apply the patch system? [13:56] no [13:56] is it in the guide? [13:56] MTecknology: dont think so.... ill have to pull it from somewhere [13:56] alrighty [13:58] shadeslayer: the file is called fpm.patch [13:59] MTecknology: youll need to add quilt as a build-depend [13:59] shadeslayer: there's already a lot of patches being applied [14:00] in debian/patches/ there's ~46 files [14:00] MTecknology: is this a KDE package? [14:00] PHP5 [14:00] hmm [14:01] well im not sure about the patch line then [14:01] shadeslayer: so perhaps I can just toss the patch in there and build? [14:01] for kde apps its : include /usr/share/pkg-kde-tools/makefiles/1/cdbs/kde.mk [14:01] MTecknology: so there already was apackage? [14:01] ya [14:01] !info php5 [14:01] MTecknology: can you pastebin the rules file in debian/ [14:01] ok [14:01] php5 (source: php5): server-side, HTML-embedded scripting language (metapackage). In component main, is optional. Version 5.2.10.dfsg.1-2ubuntu6.4 (karmic), package size 1 kB, installed size 20 kB [14:02] http://paste.ubuntu.com/382986/ [14:03] MTecknology: lines 33 to 40 [14:04] make that 42 [14:04] rlp10: done with the key? [14:05] shadeslayer: working on it, I'm afraid real work is calling too, so I might have to come back to this :( [14:05] rlp10: sure :) [14:06] rlp10: i might be giving a session on 27th Feb 1700 UTC [14:06] shadeslayer: so the patch will be applied just by being in that directory? [14:06] for this particular purpose [14:07] MTecknology: yeah,just copy the patches in debian/patches [14:08] shadeslayer: that would be great, would it be in this room? [14:08] rlp10: #ubuntu-classroom [14:09] rlp10: its not finalized yet,ive sent a mail to the organisers :) [14:09] shadeslayer: http://paste.ubuntu.com/382989/ This is how you're supposed to install after appying that patch; I'm guessing deb/rules needs to change for that? [14:09] shadeslayer: i've pencilled it in my diary in any event [14:09] shadeslayer: thanks for your help today and sorry I couldn't follow it through to completion [14:10] rlp10: no problem [14:10] rlp10: i might also tell something about pbuilder [14:11] MTecknology: that is a part of what file? rules? [14:12] MTecknology: btw im reading : http://www.debian.org/doc/maint-guide/ch-dreq.en.html#s-rules [14:12] its pretty good [14:13] shadeslayer: if you're compiiling php from source and apply that patch, that's how you're supposed to compile php with the patch after you apply that patch [14:13] shadeslayer: now? or in your class? [14:13] rlp10: in the class :) [14:14] MTecknology: no no... the patches are handled by lines 33 to 42 in the rules file [14:14] shadeslayer: I saw something about that in the guide, it looked like clever stuff [14:14] rlp10: nah... [14:14] rlp10: it just mimics what the ppa servers do [14:14] but instead on your local machine [14:15] shadeslayer: right, i have that much - how do I make it build that package so it can be installed? [14:15] MTecknology: ok well youve applied the patches,updated changelog and added any other build deps right? [14:16] shadeslayer: well it's clever stuff from where I'm sitting [14:16] :P [14:16] shadeslayer: ya [14:16] MTecknology: ok do you have a very fast net connection? [14:16] kinda fast [14:17] MTecknology: sudo apt-get install pbuilder debootstrap devscripts [14:17] done [14:17] how can I access my system X server from inside a pbuilder chroot? [14:18] I have a vm with all that installed [14:19] MTecknology: um [14:19] MTecknology: so youre applying the packages etc in a VM? [14:19] ya, any package work is in the vm [14:20] ok [14:20] I could do a shroot, but then I don't get firefox and thunar :P [14:20] MTecknology: ok now : sudo pbuilder create --debootstrapopts --variant=buildd [14:20] MTecknology: i would suggest you make a pbuilderrc first with a close server [14:21] ( a server which is close to your home ) [14:21] I don't have a spare system atm :( [14:21] I like that idea though [14:21] I'm using cdbs, and I need to provide an error handler for dh_installinit. Is there an override I can set? [14:21] my laptop got up to 100 C yesterday building php [14:22] MTecknology: ok well you can upload to a PPA in that case [14:23] ya, only thing I don't like with that is having to change the version for every failed build [14:23] but that's not such a big deal :P [14:23] MTecknology: hehe [14:24] well theres a small problem of authourizing the system to upload stuff.... i cant remember it [14:24] better than a proc that's 212 deg F :P [14:24] :D [14:25] JontheEchidna: can you upload polkit-qt{,-1}? might be better if somebody from the K people uploads those two :) [14:26] dholbach: would if I could, but the kubuntu-dev upload rights are very incomplete [14:27] JontheEchidna: maybe you could prod somebody in #kubuntu-devel? :) [14:27] sure [14:27] thanks muchly! [14:28] dholbach: hi [14:28] hi MTecknology [14:28] dholbach: how've you been? [14:29] good good [14:29] how can I access my system X server from inside a pbuilder chroot? Trying to learn how to fix an unmet dep :) [14:30] nigelb: mount proc and bind-mount tmp in the chroot (eventually you'll need sys as well) [14:30] sistpoty|work: you'll have to get it down a little more understandable level :( [14:31] nigelb: mount -t proc whereveryourchrootis/proc; mount -t bind /tmp /whereeveryourchangerootis/tmp; mount -t sysfs /whereveryourchrootis/sys [14:32] this has to be from out the chroot I'm guessing? [14:32]