[00:07] aaaaahhh... all my mail seems to be gone [00:08] dear kmail, please don't shock me like this, sincerely yours, stefan. [00:14] If I send a patch for Hardy, should I send the patch for Intrepid too? [00:17] cyberix: The general rule is that nothing not fixed in intrepid will be uploaded to hardy. [00:17] cyberix: for an SRU? [00:17] To avoid confusion, I'd recommend putting both patches in the same bug. [00:18] no, just a small patch [00:18] Actually there is no use to ship this for Hardy [00:18] cyberix: Any change to hardy at this point is an SRU, even a just a 1-bit change [00:18] I'm just trying to understand how the processes work [00:18] k [00:19] so it is stable instead of source :-) [00:24] has someone an idea what went wrong during this build? http://launchpadlibrarian.net/15562990/buildlog_ubuntu-intrepid-i386.libgnupg-interface-perl_0.36-1_FAILEDTOBUILD.txt.gz [00:26] geser: hm... "which gpg ... gpg (GnuPG) not found at Makefile.PL line 21." might give some clue? [00:27] sistpoty: But build-essential depends on dpkg-dev, which depends on gnupg [00:27] persia: which doesn't mean that Makefile.PL is correct thought ;) [00:27] sistpoty: True. [00:28] sistpoty: it builds in my pbuilder [00:28] geser: hm... strange [00:28] * persia tries in sbuild, to see if it is due to pbuilder-satisfybuilddepends [00:29] persia, geser: oh, dpkg-dev doesn't b-d on gnupg [00:30] ! [00:30] (at least not 1.14.20ubuntu1) [00:30] How did that become Suggests: ? That's rather unexpected. [00:30] but gnupg is installed (see the gpg signature check after the source is extracted) [00:31] No, that's just me reading apt-cache output wrong. [00:33] geser: There's something very odd: that buildlog also has "sh: gcc: not found" [00:33] hm... dear kmail, don't disconnect me from the outside world, by not letting me receive mails from a local mbox. thanks. [00:33] Builds cleanly in my intrepid sbuild chroot. [00:34] persia: hm... however it has: "Setting up g++-4.3 (4.3.1-1ubuntu2) ..." [00:34] sistpoty: Right, which is why I thought "sh: gcc: not found" was odd. [00:35] I find it especially odd right after "Toolchain package versions: ... gcc-4.3_4.3.1-1ubuntu2" [00:35] if I understand the Makefile.PL correnctly the second "gpg" in the line "which gpg ... gpg" should come from the system() call, right? [00:36] geser: Right. I would have expected "/usr/bin/gpg" [00:37] I think that system($gpg_find) is returning nothing, and the second gpg is coming from 'die "gpg (GnuPG) not found";' [00:38] yes, you are correct [00:38] perl -e "system('which gpg')" returns here /usr/bin/gpg [00:39] Looks like this was the first build since edgy. Maybe this is a case of someone hand-adjusting things. [00:39] persia: gcc-4.3 only provides /usr/bin/gcc-4.3, /usr/bin/gcc is in gcc but that's also installed [00:39] geser: Still, it's odd to see a report that gcc is not found. [00:40] true [00:40] someone messing with $PATH? [00:41] http://launchpadlibrarian.net/3087635/buildlog_ubuntu-edgy-i386.libgnupg-interface-perl_0.33-6_FULLYBUILT.txt.gz looks rather different: Makefile.PL likely changed a bit upstream. [00:41] Could be the common situation with arch:all that the Debian build wasn't run in a sanitised chroot... [00:43] but why does the same source package build in my pbuilder and your sbuild but not on the buildd? [00:43] Do you have gnupg installed in your chroot? It seems to be in mine. [00:44] sistpoty: thanks for sponsoring my memaker upload :) [00:44] bobbo: thanks for providing a debdiff in the fisrt place ;) [00:44] sistpoty: hehe, my pleasure [00:46] persia: I have, but how did dpkg-source (on the buildd) check the gpg signature without gnupg? (gpg: Signature made Tue Jun 24 07:31:19 2008 BST using DSA key ID 9725F63B) [00:46] * sistpoty goes to bed now... gn8 everyone [00:49] persia: the "sh: gcc: not found [00:49] " seems to be normal now [00:50] it's also in successfully build logs, e.g. http://launchpadlibrarian.net/15590444/buildlog_ubuntu-intrepid-i386.apache2_2.2.9-2ubuntu1_FULLYBUILT.txt.gz [00:51] That's very odd. Maybe the "gcc" package isn't installed, or poorly configured, or something. [00:53] "Setting up gcc (4:4.3.1-1ubuntu2) ..." seems ok to me [00:54] geser: I have to agree that gpg is installed. I don't know why "which gpg" wouldn't work. [00:54] persia: n8, I'll try to ask the buildd admins if they have an idea why libgnupg-interace-perl FTBFS (and also about the "sh: gcc: not found" thing) [00:54] is anybody using sbuild+some apt cacher with both Debian and Ubuntu ? [00:54] * persia checks the default /bin/sh in the sbuild schroot [00:55] No, I seem to have dash, so that's not it. [00:55] * persia is baffled [00:56] persia: a reason why gcc and gpg are not found could be that /usr/bin is not in the PATH for some reason on the buildd [00:57] geser: Maybe, but why would it be able to call dpkg-source (also in /usr/bin)? [00:57] Further, dpkg-source checks for the existence of /usr/bin/gpg, but then calls gpg without a prefix path. [00:58] It's backticks rather than system(), but that oughtn't be sufficient to make it work or fail. [01:01] does it get called as "dpkg-source" or "/usr/bin/dpkg-source"? [01:02] hmm, dpkg-source calls gpg without the full path to do the signature check, so PATH seems to be ok [01:02] Right. [01:05] what about giving it back to the buildds and hope that it gets tried on a different buildd? [01:06] That's why they put the button there :) [01:11] nothing changed :( still FTBFS [01:12] * geser goes to bed now [01:13] geser: Sleep well. === macd_ is now known as macd === rockstar` is now known as rockstar [07:56] Hm. Gnome-do-plugins in Ubuntu has a do-plugins as its source package, but gnome-do-plugins in Debian has gnome-do-plugins as its source package. I'm rebasing the Ubuntu package on the Debian package; do I upload as gnome-do-plugins and ask for removal of do-plugins? [08:11] RAOF: Please... do. [08:12] wgrant: :P [08:16] wgrant: Do you know if I need to ask for the removal of do-plugins source before uploading gnome-do-plugins? Otherwise there'll be a binary package name conflict, and I'm not sure how those get dealt with. [08:16] RAOF: As long as the version is greater, it will be fine. [08:17] They'll go through binary NEW, but then dominate the old binaries, so your new ones won't be removed with the old source just because they have the same name.\ [08:24] Grmph. Why is Full Circle Magazine recommending Webmin? [08:24] And 'sudo su'? [08:36] Ehem, and they used a pre-Hardy interview... [08:38] And they recommend using Debian packages. Ew ew ew. [08:49] wgrant: Where? [08:50] Flannel: To which bit? [08:51] <\sh> moins [08:51] wgrant: Um, all of them if theyre convienent [08:51] wgrant: I think you can find them lurking in #fullcirclemagazine ;-= [08:51] moin \sh [08:51] jpds: Ah, perhaps. [08:51] Flannel: I glanced through the latest edition (#14). [08:52] They're fairly easy to find with any search functionality. [08:52] wgrant: Alright, thats all I needed to know [08:52] Didn't want to start from 0 [09:03] G'morning [12:07] hi folks [12:11] hi sistpoty [12:12] hi geser [12:12] hm... last nights dist-upgrade with many kde parts getting upgraded left me with a gnome session... epic fail *g* [12:13] sistpoty: it's part of the hidden master plan to convert all kde users to gnome :) [12:13] haha [12:14] i like the sound of this plan... [12:15] Hm. I'm just trying Intrepid KDE. Again. [12:16] Is the display settings panel _meant_ to do anything, or just look (not) pretty? :) [12:16] someone remind me of the build a .dsc command? [12:17] sbuild -d intrepid foo.dsc ? :) [12:17] On the other hand: dear GTK: please implement something like the smooth animation of the output list. [12:17] no, the dpkg one? [12:17] Is there one? [12:18] hrm... /me goes to google more [12:18] You dpkg-source -x it, then dpkg-buildpackage the extracted source. [12:18] (or debian/rules binary, if you're confident it's policy-compliant :)) [12:18] RAOF: ahh, yeah thats the one [12:19] RAOF: its just a personal thing, nothing for ubutnu atm. [12:19] Um. Why does Kubuntu default to playing a 'ding' every time I press a button? [12:29] RAOF: Because it's kool. [12:29] Gah! KDE is so easy to break! [12:30] I seem to have created a panel covering my entire second monitor. [12:31] Nice! [12:31] KDE4 or not? [12:33] Kwin now believes that maximise about 30x20 pixels in the top left corner, too. [12:33] KDE4 [12:35] Hm. It is apparently imperitive that I don't alt-tab, lest kwin consume 100% cpu and lock the desktop. [12:36] RAOF: Just use the panel on your second monitor to control which app you are using. That way you won't need the keyboard at all :) [12:37] The panel on my second monitor is entirely empty, and unresponsive to mouse clicks :) [12:38] Maybe it's not even a panel? Maybe something just decided to fill my second monitor with all black. === Kopfgeldjaeger2 is now known as Kopfgeldjaeger [12:39] Oooh, maximising works again! [12:42] I was going to spend some time using kde to file some bugs, but kubuntu appears to be composed entirely of bugs. I must be an expert kde-breaker. [12:42] "I'd file bugs, but maybe what I think are bugs are really features." [12:43] Everything in a feature, for the right use case... [12:43] The biggest "feature" seems to be semi-awareness of dual head. [12:43] It knows my laptop's running at 1680x1050, so the panel is 1680 wide. [12:44] However, when it started up my two monitors were cloned. Thus, the desktop is the size of the smaller of the two. [12:44] Sadly, this means that the left hand side of the panel, containing, among other things, the launcher, is offscreen. [12:44] Teehee [12:45] W.T.F? [12:45] * RAOF blinks again. [12:45] Right-justification is always correct :) [12:46] Pressing the "configure this panel" button (not labelled as such in any way, of course) brings up, among other things, 3 arrows. [12:46] In some as yet undiscovered way, these three arrows influence the size of the panel. [12:47] That sounds intutive. [12:47] As well as some left/centre/right justification boxes. [12:47] Also intuitively: selecting the text which is left justified causes the panel to be right justified on my right hand monitor. [12:48] Centre works as expected, but the right-justification button causes it to be right-justified on my left monitor. [12:51] Hm. How do I make the clock show 12h time? Hint: it doesn't involve right clicking on the clock, apparently. [12:52] RAOF: You switch to Ubuntu? [12:52] Entirely possible, yes. I'd like to file at least _some_ bugs first, though. [12:52] Such as "has no concept of multi-head" [13:00] Could anyone explain why pycentral might report "pycentral: pycentral pkginstall: not overwriting local files", as in http://launchpadlibrarian.net/14327059/DpkgTerminalLog.txt? Is this likely due to user customisation, or is it a packaging issue? [13:05] persia: looking into /usr/bin/pycentral this seems to be set from the option "overwrite-local" in /etc/python/debian_config [13:06] I don't have it set in my /etc/python/debian_config [13:06] persia: I've seen the problem with a Dapper upgrade. [13:07] man pycentral mentions this option in the FILES section [13:07] But it doesn't look like it could be the problem here. [13:07] So, do I need to do anything to the package to fix it, or just leave it alone? (I'm processing NBS, so like to minimize actual changes) [13:07] In my case, python-opengl didn't conflict with python2.4-opengl, so pycentral refused to overwrite the python2.4 opengl bits. [13:08] Adding a conflicts against it was the solution there, but it could be a local installation in this case. [13:09] Should python-csound conflict with python2.5-csound, just to be sure? [13:10] It currently Provides: it, which makes me think that such a package used to exist (or maybe python2.4-csound) [13:12] the provides are generated: Provides: ${python:Provides} [13:13] morning [13:15] geser: Right. I'm just wondering if it needs a conflicts, or if bug #227651 is not really valid. [13:15] Launchpad bug 227651 in csound "package python-csound 1:5.08.0.dfsg2-1ubuntu3 failed to install/upgrade: subprocess post-installation script returned error exit status 1" [Undecided,New] https://launchpad.net/bugs/227651 [13:21] Grumble. Publisher appears out of date for glib2.0-dev on archive.ubuntu.com :( [13:25] persia: Hm? [13:26] There is no glib2.0-dev, is there? [13:27] And all right libglib2.0-devs are there.. [13:27] Err. Right. libglib2.0-dev. 1ubuntu2 is in packages for amd64, and 1ubuntu3 is in the pool (1ubuntu2 is gone). I presume it will catch up soon. [13:27] Oops. [13:27] That is a bug. [13:28] Though it may be a sysadmin bug. [13:28] Yep. The first package I ran worked, but the ~12:00 UTC run seems to have befuddled it. [13:28] Is the bug likely to be a Packages.gz construction issue, or just a timing issue? [13:29] Um, glib2.0 has been a sync for three weeks now. [13:29] No ubuntuX. [13:31] persia: hardy or intrepid? [13:31] Oh, right, Hardy makes more sense. [13:31] I forget that it still exists. [13:32] geser: intrepid. I'm tesing bare package install now, rather than looking at a build failure, just in case I did something wrong. [13:32] What's the full version you want? [13:33] 'Version: 2.17.2-1' [13:33] That's in amd64 Packages.gz on a.u.c. [13:34] Right. I'm not sure where I got the error. I may have inadvertantly spelled intrepid h-a-r-d-y. [13:34] Heh [13:37] A have a project readfile. i have made .debs for it and they are in my ppa (krzysdrewniak on launchpad) check it out. [13:37] what should i do now? [13:37] i made a .deb of wine 1.0 [13:37] krzysz01: What is your goal? [13:38] i'm trying readfile into the repos, but it needs some polishing still [13:39] krzysz01: Are you up for polishing it, or do you need review? [13:40] i am adding some new features before i submit it for review [13:40] i'm still working on it [13:41] krzysz01: Then the answer to the question "what should i do now?" is "add some new features before submitting it for review". [13:41] stay tuned it will probably be good when i get to 1.0 [13:41] see ya [13:42] bah... packages.{ubuntu.com,debian.org} are not responding [13:44] DktrKranz: packages.qa.debian.org, launchpad.net/ubuntu/+source/$(pkgname) [13:45] unluckily, I needed them for some tests, so I guess I have to wait [13:45] persia: can you please take a look at https://bugs.edge.launchpad.net/ubuntu/+source/crystalspace/+bug/242961 ? I need 2 sponsors for it [13:45] Launchpad bug 242961 in crystalspace "Please update crystalspace to 1.2.1" [Undecided,Confirmed] [13:46] devfil: I really know nothing about crystalspace, except that it's a mess. Anyway, why do you need two sponsors? [13:46] persia: it is a new package [13:47] NEW? mmh [13:47] persia: a new huge work as wxwidgets2.8 [13:47] not new package, new version, sorry [13:47] probably it deserves four eyes to look at it, but it's not NEW :) [13:49] there are a few RC in crystal space affecting debian's release [13:50] rzr: this is why I upgraded it to the latest stable version [13:50] good job [13:53] rzr: I also asked Debian maintainer to let me work at it (NMU), but I didn't receive any reply for now [13:53] i know him personnaly [13:53] he's offline now [13:53] can you NMU it ? [13:54] rzr: yes [13:54] what is NMU? [13:55] bliZZardz: Non Maintainer Upload in Debian [13:55] Non-Maintainer Upload (Debian) [13:55] only DD can NMU packages right? [13:55] and does that mean that people who do not maintain it, contribute a patch/feature? [13:56] rzr: I don't know, if I do it, probably, Debian maintainer should sponsor it [13:57] rzr, DD can upload packages, but everyone can propose a NMU if there's RC or release-goal bugs [13:57] devfil: well I would attach a debdiff to the bug first [13:57] i was exploring Dbus yday, i need some mentor to help me out understand it better. Would this be the right forum? [13:58] rzr: A debdiff of a new upstream? Isn't that hard to read (and might it be impossible to generate given binary changes in the upstream tarball)? [13:58] bliZZardz: For some very limited types of questions, yes. For deeper questions, probably not. [13:59] persia : and that would be? [13:59] persia: you :) ? [13:59] Not I, no :) [14:05] rzr: why Debian maintainer of crystalspace is offline? [14:05] he probally has a life :) [14:06] not so bad, after all [14:06] bah, rl is overrated *g+ === bliZZardz is now known as bliZZardz_ [14:07] bliZZardz_, I guess the most qualified person is pitti, but he's on holidays at the moment and he's a very busy developer [14:08] DktrKranz : presently i am doing some triaging, but i would like to get into Dev - hence am looking out for some mentors. I am comfy with Python. [14:09] whoa! I've just become a DM! \o/ [14:09] DktrKranz: Congratulations! === bliZZardz_ is now known as bliZZardz [14:09] persia, thanks [14:10] DM? (deb mentor?) [14:10] bliZZardz, well... if you're comfortable with dbus (or utopia-related stuff), pitti has some mentoring slots available [14:11] DktrKranz: just started with DBus..need some initial pointers [14:12] so I guess triaging bugs should be good at the moment [14:12] personally, I haven't any documentation available [14:13] DktrKranz: what abt projects(in python) that have mentoring slots available? [14:14] bliZZardz, for python related bugs, you may want to look at pythonistas bugs [14:15] DktrKranz : yes - am there. [14:15] cool :) [14:16] just getting a feel of the bugs ; looks like most of them need complete module knowledge [14:16] I'm sure there are some entry-level bugs [14:17] eventually, you can look at bugs marked as bitesize [14:31] <\sh> we made it ! http://leonov.tv/content/leonov-launchpad-desktop-client-first-coming [14:32] \sh: Congratulations. Nice job. [14:32] <\sh> persia: thx :) [14:32] * \sh is sweating like hell [14:33] \sh: great job! [14:33] \sh: The bugs will come. Have no fear :) [14:33] persia : LOL ") [14:33] <\sh> persia: seele was reviewing our work already...so I have a lot of them already :) and no, I don't fear any bugs :) [14:34] \sh: apt-cache showsrc leonov doesn't yield a result... please fix :P [14:35] sistpoty: Please file a needs-packaging bug to request new software :p [14:35] ACK from me, please upload to NEW queue :D [14:36] <\sh> sistpoty: lol [14:42] * sistpoty is now off again, enjoying the weekend... cya [14:43] \sh: congratulations :) when will we be able to download bug informations for offline usage? (ok ok.. jocking) [14:43] <\sh> tacone: please file a wishlist report (seriously) :) [14:44] <\sh> tacone: I thought about that already, tbh [14:44] \sh: I feared you would have asked that. [14:44] ehehe [14:47] \sh: seems I can't mark it as wishlist myself https://bugs.launchpad.net/leonov/+bug/243960 [14:47] Launchpad bug 243960 in leonov "Please store bug information for offline usage" [Undecided,New] [14:48] <\sh> tacone: done :) [14:48] \sh: nice [14:48] <\sh> ah da nixternal [14:52] <\sh> phew... [14:52] yay power [14:53] nixternal: You're one of those kubuntu folk right? Are you guys chasing NBS yet? There seems to be a few packages listed... [14:54] <\sh> nixternal: dude, you are also mentioned in our announcement :) [14:55] what announcement? [14:55] <\sh> nixternal: check p.u.c [14:55] persia: dunno, ask Riddell...I have been working to much lately, so unfortunately I haven't been that close to what is going on [14:58] hehe, \sh...that has come along quick man...I liked reading the posts seeing how much it changed almost daily [14:58] good job! [14:59] \sh: p.u.c is ambiguous: people.u.c, packages.u.c, planet.u.c :) [14:59] <\sh> nixternal: that's only the beginning of something really bug^Wbig [14:59] popcon as well! [14:59] I wonder if any other letter is as ambiguous. [14:59] geser: ya, I did packages.ubuntu.com at first :P [14:59] <\sh> damn...b.u.c is missing...beer.ubuntu.com ;) [14:59] then I went, OH! Planet! [15:00] <\sh> packages is pkg.u.c. ;) [15:29] persia: NBS? [15:38] siretart: Hi, as you seem to care about ffmpeg-free: should "ffmpeg-config --libs avformat" result in the same output as "pkg-config --libs libavformat"? [15:38] I ask because I stumbled about a package which FTBFS (moc) because ffmpeg-config still lists "-la52" [15:42] Riddell: http://people.ubuntu.com/~ubuntu-archive/NBS/ [15:42] Looks like either there's a lot of changes expected, or lots of rebuilds to process. [15:45] changes are expected, since we moved to KDE 4 [15:47] Riddell: OK. I won't poke them then. Thanks. [15:50] geser: ffmpeg-config will go away in the next upload. please make the package use pkg-config instead [15:55] siretart: I've done that. I just wondered if the output of ffmpeg-config should match the output of pkg-config as long as ffmpeg-config still exists. [16:04] geser: it probably should. that's one of the reasons why we want to get rid of ffmpeg-config [16:20] Does anyone have a good ddeb recovery hook for sbuild? I'm generating ddebs, but throwing them away, which doesn't seem ideal. === wolfger__ is now known as wolfger [16:26] persia: wow, a lot of upload today [16:27] devfil_: Trying to clean up some of the outstanding transitions for universe. [16:27] persia: good job [16:27] Hello [16:27] hi AnAnt [16:28] Bah. Uploaded things out of order again :( At least the retry button works. [16:29] persia: that brainstorm discussion is dead ? [16:29] persia: nobody is perfect [16:29] AnAnt: I think so. [16:40] persia: ok, I know I'm asking for a big thing, I mean about glibc [16:41] -ECONTEXT [16:41] huh ? [16:41] what's that ? [16:41] Context error, meaning I have no idea about what you are writing [16:42] persia: the suggestion I mentioned on brainstorm post [16:42] persia: i prefer this: http://heresabunnywithapancakeonitshead.com/ [16:42] is packages.ubuntu.com working ? [16:48] AnAnt: Oh, right. Alternate calendars. I have no idea how that might work, but think it deserves it's own idea on brainstorm, rather than getting mixed in with that one. [16:49] is there a problem with packages.ubuntu.com ? [16:52] hi everyone! [16:55] I want to use a .deb package to install some files, but I'm not sure where to put them. I'm using the openweakhardy/PackagingA tutorial and the only problem I have is to install that files! [16:56] where do I put them? in ed-0.9/debian/ folder?? [16:58] I created 'ed-0.9/debian/tmp/mp/' and 'ed-0.9/debian/tmp/database/' folders. made the 'debuild -us -uc' and it returned no errors! [16:59] i4x: What kind of files? [16:59] but when installing, the postinst can't find the folders and .... [17:00] persia: I need to install: /tmp/database/mp.sql and /tmp/mp/runner (script) [17:01] AnAnt: yeah package.ubuntu.com is down for me too [17:02] s/package/packages [17:02] I have a quick question. The package I am working on comes with .desktop files (not the debian directory). The package does not have a patch system in place. Should I add a patch system to the package in order to modify the .desktop files? If so, which type of patch system should I use? Or should I just modify the .desktop files in the debdiff? [17:02] i4x: You really don't want to install anything to /tmp. Why not install the sql into /usr/share/$(package)/$(package).sql, and embed the script in the postinst? [17:03] nhandler: I'd only add a patch system for big changes [17:03] geser, So for this instance, it would be better to modify something outside of the /debian directory in the debdiff than to add a patch system? [17:03] nhandler: I'd recommend checking other packages by the same maintainer, and possibly introducing a patch system that matches their style. [17:04] nhandler: especially if the package has already some changes (from Debian) adding a patch system isn't wise (for small changes) as you end with some changes as patches (Ubuntu) and some changes applied directly (Debian) [17:04] * persia very strongly agrees with geser about packages with changes in diff.gz [17:05] persia: the script will be installed to init.d to run at startup, and the database will only be used once by postinst that installs the database and then removes it. [17:05] nhandler: depending how much you want to change, I wouldn't add a patch system just to change a few lines in a .desktop file [17:06] i4x: For the init script, investigate dh_installinit. For the sql, I still think it belongs in /usr/share/$(package)/$(package).sql for later reference by the user. [17:06] geser, It looks like I'll just be adding Icon lines to a few .desktop files that are in the package. I might also be making a few minor changes to the .desktop files to make them validate. [17:06] geser: I've had more success getting patches into Debian when I follow the maintainer's style, which is why I recommend that research. [17:08] persia: I know there are some .ex files as init.d.ex .. but I don't understand so much to use them. and, are you saying to install the sql to /usr/share/$(package)/$(package).sql ? if so, how? [17:09] i4x: Put it in debian/ then add it to your $(package).install file. [17:10] persia: hm, ok.. I'll search for the *.install file.. [17:10] i4x: read the manual pages for dh_install and dh_installinit [17:10] persia and geser: It looks like the Debian maintainer only has 7 packages. I'll look at them and see if I can find a preferred patch system. If I can't, I think I'll just include the changes in the debdiff [17:11] persia: thx, I'll do that! (y) [17:18] persia, I just checked all 7 of the Maintainer's packages. None of them use a patch system. In this case, do you agree that I should just include the changes to the files that are outside of the debian directory in the debdiff? [17:18] nhandler: Very much so. [17:18] geser and persia: Thank you for your help. I'll go and make the changes now. [17:32] warp10: ping [17:38] i'm looking to build the debian package for nautilus-open-terminal on Hardy [17:38] the version for Debian Experimental requires a newer version of libpango (i guess because it was just built against it) [17:38] how do i get the source from DebExp? [17:39] If it's in experimental, it's probably there for a good reason. [17:39] there's nothing much experimental about nautilus-open-terminal [17:39] it gets about 3 commits a year [17:39] One was is to go to packages.qa.debian.org, find the package package page, and then dget -x the .dsc. [17:40] thanks, i see the DSCs [17:40] It might be building against the new libpango is the only reason it's there. [17:41] ScottK-laptop: that got me a .orig.tar.gz and a .diff.gz [17:41] Did you use -x? [17:41] (sorry, i'm used to apt-get source wiping my bottom for me) [17:42] yes [17:42] It should have unpacked the source too then. [17:42] If it didn't, you can dpkg-source -x filename.dsc to unpack it. [17:42] it bombed here" dscverify: can't find any Debian keyrings [17:43] So it couldn't verify the signature. [17:43] IIRC, the package with the Debian Keyring in it is deceptively called debian-keyring. [17:44] I've got a little X windows problem here, so I'll be back (hopefully) in a little bit. [17:48] Hopefully that will be better. [17:48] OK, nautilus-open-terminal package in Debian Experimental builds fine on Hardy [17:48] and works as expected [17:48] what do i need to do to get it pushed into Hardy Universe? [17:48] It needs to get into Intrepid. [17:49] can it then go via hardy-backports->hardy-updates? [17:49] Not usally. [17:49] What bug are you fixing to get it updated? [17:49] the on-desktop behaviour drops you in $HOME previously [17:49] Is there a bug? [17:49] it was fixed, with the old behaviour being in a gconf option [17:49] a long time ago [17:50] and 0.9 was released on 28 February 2008, so the debian packages have just been lagging [17:50] Intrepid already has 0.9 [17:51] oh... hmm... i probably should have just used that [17:51] haha, oh well [17:52] yay, now to just drop the habit of typing cd ~/Desktop every time i open a terminal [17:53] alex-weej: I don't think this qualifies for -updates. It's not a regression, data loss, or crash issue. [17:53] You could get the new version in -backports. [17:54] ok, is it a lot of effort? [17:54] No. [17:55] what do i do? [17:55] You've already done virtually all the work (testing). [17:55] !backports | alex-weej [17:55] alex-weej: If new updated Ubuntu packages are built for an application, then they may go into Ubuntu Backports. See https://help.ubuntu.com/community/UbuntuBackports - See also !packaging [17:55] You file a bug against the hardy-backports project as described above. [17:55] got it, thanks [17:56] alex-weej: Ping me when it's done and I'll approve it. [17:56] well... i haven't really tested it properly... :S [17:56] i mean, it works [17:56] maybe i should use it for a bit first [17:57] For backports, the standard is "Builds, installs, runs" - You pass that. [17:57] More testing is welcome, but you've done the minimum. [17:57] Note that backports is not enabled by default for what are generally considered good reasons ... [17:57] Actually we have very few problems. [17:57] yeah of course [17:58] ok just a mo [18:03] ScottK: you beat me to the original bug :P [18:03] ;-) [18:03] i will link it in the backport request === _neversfelde is now known as neversfelde [18:06] ScottK: https://bugs.launchpad.net/hardy-backports/+bug/244017 [18:06] Launchpad bug 244017 in hardy-backports "Backport nautilus-open-terminal 0.9 from Intrepid to Hardy" [Undecided,New] [18:07] alex-weej: Mark it confirmed to show you've tested it. [18:08] done [18:10] alex-weej: Approved and passed to the archive-admins. It should get backported the next time the process backports. [18:10] cheers [18:13] ppl, I'm trying to understand how to use 'dh_install', but I'm confused.. anyone knows how to use it and gives me an example? I just need to understand how the package recognizes the folders/files to install and moves them! [18:14] i4x: Did you read man dh_intall? [18:16] ScottK-laptop: yes, I did! [18:17] i4x: Did you see the bit about "debian/package.install"? [18:19] ScottK-laptop: I've no '($package).install' file.. [18:19] Make one that lists the files you want installed. [18:20] ScottK-laptop: do I have to modify anything in rules? [18:20] ok, but where do I create it? debian/ ? [18:21]