[00:01] RoAkSoAx: in the GNU make documentation [00:01] RoAkSoAx: (it's somewhat like a grep) [00:01] see 7.3 in the make info manual [00:01] package make-doc [00:01] pochu, awesome thanks :) === asac_ is now known as asac [00:04] pochu, what if for example a Makefile has this: ifneq (0,$(HAVE_NL))\n CFLAGS += -DLIBIPVS_USE_NL\n endif. How can I do something similar in debian/rules? [00:06] RoAkSoAx: just copy it :) [00:06] but don't tabulate it [00:07] (the ifneq and endif, the lines in between may have tabs or spaces if you wish) [00:08] pochu, ok cool thanks :) [00:08] yw [00:15] pochu, and how about specifying different CFLAGS for different Makefile's in the same app. For ex. I have a Makefile in the root of the source directory, and another Makefile in libipvs/Makefile. the Makefile in the root requires just -g and the one in libipvs/Makefile requires -fPIC ? How to do that in debian/rules? [00:18] bdrung_, ping :) [00:18] Zhenech: pong [00:19] Zhenech: thats faster [00:19] ah, you're on, fine [00:19] saw my mail? [00:19] yes, i was currently writing the response [00:19] your mail ending "grüße". are you German? [00:19] heh, I thought "wait, he has an @ubuntu mail, he is for sure in #motu [00:20] yes, you even wrote me mails in german already :P [00:20] Zhenech: i am in some debian channels, too. [00:20] Zhenech: too many people. [00:20] aye, I know that :) [00:20] and my brain can't remember names [00:21] and my name does not suggest I can speak german :) [00:21] german parents? [00:22] nope, just living here :) [00:22] ;) [00:22] so now to the bugs: 536582 [00:23] also https://bugs.launchpad.net/ubuntu/+source/shiki-colors-murrine/+bug/399457 [00:23] Ubuntu bug 399457 in shiki-colors-murrine "Shiki-Colors forces metacity install (Should be a recommendation)" [Low,In progress] [00:24] Zhenech: the problem is that the index files defining complete themes, so that the packages needs to depend on the shiki-metacity package. [00:25] Zhenech: what do you think? how should the problem resolved? [00:25] well, I run xfce here [00:26] just kicked metacity from the system [00:26] and the themes still looked as they should [00:27] so I'd prolly do Depends => Recommends and stuck with it [00:27] moving metacity from depends to recommends? [00:27] yes [00:28] ok [00:28] do you have a xfce setup to test it somewhere? so you can be sure it works as expected without metacity? [00:28] should shiki-colors add the xfce package to recommends or suggest? [00:29] Zhenech: i had tested it with xubuntu. [00:29] xubuntu should be fine [00:30] for xfce you can drop the shiki-metacity package. only when you have gnome installed the theme will be broken without the shiki-metacity package. [00:30] i have crashed my debian image. [00:31] currently i am reinstalling it. [00:31] well [00:31] but there i have gnome installed. [00:31] maybe i should setup a xfce version, too. [00:31] should shiki-colors add the xfce package to recommends or suggest? [00:32] the shiki colors meta package? not at all imho [00:32] yes [00:33] you say shiki-foo-theme can't live without the shiki-colors-metacity-theme in xfce too? [00:33] no, it makes only problems if you have gnome installed, too. if you only use xfce it would be possible to drop shiki-colors-metacity-theme [00:34] have a look at the shiki-foo/index.theme files. [00:34] there is a MetacityTheme specified. [00:35] then I'd say depends: shiki-colors-metacity-theme | shiki-colors-xfce-theme on all skiki-foo-theme packages and let the metacity depends [00:35] making it clear we need metacity when we want to use the metacity theme, but only then? [00:37] there is only one problem: if you have gnome and xfce installed and you only install shiki-colors-xfce-theme. then the GNOME-Metatheme is broken. [00:37] aye [00:38] aye? [00:38] i know, thats a "general" problem with the deb depends format [00:38] aye = yes [00:39] i think that is something the use should be able to handle himself [00:40] ok [00:43] Zhenech: next: broken selection. i talked with victor. he want a screenshot, so i wrote a response. [00:44] Zhenech: next: 536480 gnome-*-icon-theme overrides my start-here icon (Debian swirl): i made some changes upstream, so the patch will get shorter. can i wait for integrating the patch for the next upstream release? [00:44] sure [00:44] please give a short msg to the bug, saing you are working with upstream on this [00:44] :) [00:45] Zhenech: k [00:45] Zhenech: so only shiki will be changed. [00:45] are there other issues for gnome- or arc-? [00:46] none I have seen yet [00:46] just finished build [00:46] installing and testing :) [00:47] haha [00:47] minimal [00:47] Shiki-Wine is displayed Shiki-Wine in my Xfce setup :) [00:47] ew [00:47] Shiki-wine [00:47] (small w) [00:48] hm [00:48] where does xfce get the name? [00:48] typo somewhere, no blocker for the upload :P [00:48] shiki-colors-murrine-4.4 % grep -r Shiki-wine . [00:48] ./Shiki-Wine/index.theme:Name=Shiki-wine [00:48] guess here? :) [00:49] ok, this will be fixed upstream with the next release [00:50] fine [00:50] then give me fixed shiki and I upload [00:50] but not tonight anymore, my dsl here at home is crappy at best [00:50] either tomorrow from work [00:50] aaah, too many windows and tabs [00:50] or monday from university :) [00:51] How do you do quilt with dh7 if you want it to work with pre-karmic debhelper? [00:51] university? [00:51] maxb, include quilt.make and depend in the patch target? [00:51] bdrung_, uni duesseldorf [00:52] düsseldorf? [00:52] yes [00:52] * bdrung_ starts google map. :) [00:52] what, you dont know where it is? [00:53] dont tell me you know cologne but not ddorf... [00:54] i know the names, but i have no clue where they lie [00:55] i am not good in geography. [00:55] meh, I mean, I know where berlin is :P [00:55] i, too. ;) [00:56] i only know something about very near locations and very far locations (galaxy). [00:56] mh, that dust theme... it looks more like rust, not dust, I expected it to be grey :( [00:57] Dark Room is by far the best. [00:57] Zhenech: the dust icon theme fits perfectly with the dust theme. [00:57] [00:57] Zhenech: do you know where mühlacker is? [00:58] bdrung_, is mühlacker a city with more than 500k citizens a the capital of one of the german "bundesländer"? [00:58] :) [00:58] Zhenech: no, it's the city i am born. [00:59] but no, I dont know :) [00:59] * Zhenech is born a bit more on the east (kiew) [00:59] it's in bw [00:59] in baden or in schwaben? :) [01:01] schwaben [01:01] commit message: "shiki-*-theme: Depend on either the Metacity or the Xfwm theme." <-- good? [01:01] kk, my gf is from baden :) [01:02] lemme see the commit, but I guess it is :) [01:02] Internal Server Error [01:02] \o/ [01:04] mhh, bazaar.lp.net fails on me, code.lp.net works [01:05] "bzr branch lp:shiki-colors-pkg" is the shortest [01:05] Zhenech: fails how? [01:05] Zhenech: it's up now. [01:06] lifeless, fails as in gives me internal server error when accessing via web [01:06] pop into #launchpad if that happens [01:06] oook, whatever that was, works here now too [01:06] Zhenech: how long did you need to build gnome-colors? [01:14] Zhenech: shiki updated. now testing [01:14] oke, smoking and going to bed [01:15] mail me a short notice you updated the stuff and I upload [01:15] do i need to upload the package to mentors, or can you build the package from the bzr branch? [01:15] mentors pleas [01:15] I have no clue about bzr [01:15] ok [01:16] for our branches: simple run "uscan --force; bzr bd" [01:16] then you have the binary packages. [01:16] first I'd need to install bzr :) [01:17] Zhenech: thats pretty easy to do [01:18] Zhenech: bzr is simple (nearly like svn). [01:18] git is faster, but complex [01:19] well, I use svn and git for my stuff [01:19] and maybe I find some time to look at bzr in the future, but for now a .tar.gz is preferred :) [01:19] anyways, going to bed now [01:20] Zhenech: you will get the mail [01:20] thanks [01:21] n8 :) [01:21] Zhenech: do you know why http://packages.qa.debian.org/g/gnome-colors.html is not correct? [01:21] gn8 === Pici` is now known as Pici [04:21] hi, can one of you help me with a script? [04:21] woohoo: just post your question [04:22] I need to know a command where i can add a APT line to sources.list [04:22] Like something that can echo into a document really [04:24] micahg, you know what i mean? [04:25] well [04:25] do you already have the apt line and you want to put it somewhere [04:25] or are you building hte apt line? [04:25] micahg, yeah, it, i just need a command to add it to sources.list [04:27] woohoo: http://stackoverflow.com/questions/850730/how-can-i-append-text-to-etc-apt-sources-list-from-the-command-line [04:28] k thanx. This helps a lot. [04:30] micahg, is there a command to check if you're root? [04:30] whoami? [04:30] i mean, for the script to stop micahg if it is not root [04:30] check the return of whoami? [04:31] lol, nevermind [04:31] why would you do that [04:31] oh [04:31] I see [04:31] otherwise you need a passwd for sudo [04:32] you can check the effective user id [04:32] I don't remember offhand how to do that [04:32] id -u [04:32] there you go :) [04:32] thanks ajmitch [04:33] micahg, Ill tell you when I am done making it. 1 thing at a time [04:35] micahg, if i execute a script with sudo, the other commands dont have to have sudo, right? [04:49] correct [05:10] Laney: thanks for the ack. now to wait for someone to sync it.. === Amaranth_ is now known as Amaranth [06:27] good morning [06:33] morning dholbach [06:33] Good morning dholbach [06:34] hi RoAkSoAx, hi fabrice_sp [07:17] Hey guys, if anyone has time could you please review: http://revu.ubuntuwire.com/p/gnome-gmail-notifier and http://revu.ubuntuwire.com/p/lekhonee. It would be very much appreciated. Thanks a lot. [07:17] * RoAkSoAx off to bed. bye all [08:20] bdrung_, correct now? :) [08:20] (the site) [08:28] good morning o/ [08:35] good morning [08:46] <\sh> moins === korn_ is now known as c_korn [09:33] what is the kqemu-common pkg used for? [09:33] i thought kqemu-source provides the kernel module, that's enough, isn't it? [09:35] qiyong: Install the package and check yourself. [09:39] Laney: hi, news on hugs strangeness? [10:45] Hi, I have a few questions regarding generating .deb-packages [10:45] is this a good place? :) [10:45] Zhenech: yes [10:46] callekabo: yes [10:46] excellent [10:46] I have a PHP-project that depends on a few packages [10:46] php5, php5-sybase, php5-imagick etc. [10:47] and I'd like to put my project in a .deb file which lists theese packages as depencies [10:47] bdrung_, packages.qa. is sometimes slow :) [10:47] and then put the .deb-file in a local repository (reprepro) [10:48] but all the tutorials I can find for generating .deb-files talks about makefiles and how to set that up [10:48] Zhenech: seams so [10:48] but php-projects doesn't have a makefile [10:48] I just want my files put in /var/www [10:48] how do I do that? [10:49] is .deb-files and a repository a good aproach for this? [10:51] the best would be a shell script that took the folder with the php-files as an argument, read a file 'deps' inside the folder and than generated a .deb out of that [10:51] is this possible? [10:52] using ubuntu 8.04 BTW [11:18] does anybody know a better place where I can find answers to my questions? [11:27] shouldn't rmadison handle 302? [11:30] I guess you're talking about backporting the fix for bug 399891 [11:30] Launchpad bug 399891 in devscripts "rmadison needs update to new rmadison.cgi url" [High,Fix released] https://launchpad.net/bugs/399891 [11:31] well, it seems like it shouldn't need a fix [11:31] the server is telling it where to find the page it wants [11:31] it's just ignoring it [11:32] the curl call seems to be missing the option to follow redirects [11:36] gaspa: hahaha, grand timing [11:36] new GHC! [11:37] O_o === ripps_ is now known as ripps [11:37] I was just responding to that post on u-d-d [11:37] and saw it [11:37] * Laney pokes kaol [11:37] LOL [11:37] right. [11:40] Fri Jul 17 10:15:29 UTC 2009 Joachim Breitner * A script to draw a dependency graph (output not yet great) [11:40] \o/ [11:40] james_w: It is already fixed in jaunty. I have backported the fix to hardy and posted the debdiff to that bug. [11:41] slytherin: you made it follow redirects? [11:42] james_w: Yes. curl has -L option which follows redirect. The fix was provided by some other user. You also have option to uninstall curl in which case wget will be used. [11:42] excellent, thanks [11:43] james_w: The debdiff for hardy still needs sponsoring though. :-) [11:44] it's not a valid SRU bug yet though [11:44] james_w: Why not? [11:44] there's no TEST CASE, ubuntu-sru aren't subscribed etc. [11:45] Oh. I think I subscribed sponsors first. [11:46] callekabo: You need to have a debian/rules file which is a Makefile. And the in install target in that file you can copy the files in appropriate places. [11:48] james_w: Subscribed ubuntu-sru. What more information does it need? The fix is in jaunty already. I simply applied same fix in hardy and tested it. [11:48] https://wiki.ubuntu.com/StableReleaseUpdates [11:52] Laney: are you replying to u-d-d mail? [11:53] yep [11:54] ok, so i wont :P [11:57] james_w: Hmm. All the needed data is in the bug. [11:58] that may be so, but it's not laid out like requested [11:59] the SRU team deals with a lot of bugs, and so they ask for some consistency in order to help them get through them quickly [11:59] james_w: Do you have link to any idea SRU bug? [11:59] "Examples" in the page [12:13] done [12:46] slytherin: thanks [12:47] AnAnt: Welcome. [12:48] slytherin: thanks for ttf-liberation suggestion ! [12:48] so I need another advocate, right ? [12:49] AnAnt: Yes. Considering that it is java app, it is hard to find one. :-) [12:52] slytherin: you know how to write build.xml ? [13:13] AnAnt: as in the one used by ant? [13:14] slytherin: yeah [13:14] AnAnt: yes I know. [13:14] slytherin: ok, I'll need help about something , hang on [13:16] slytherin: http://pastebin.com/m16d0c0fb [13:16] slytherin: the help I need is with creating manifest file [13:17] slytherin: I did this: , but that didn't work [13:18] slytherin: ${buildlibs} is a path id [13:18] AnAnt: Let me check. [13:18] slytherin: what's the correct way to do this ? other than having to list the jar files again as I did in buildlibs ? [13:20] AnAnt: Where is buildlibs defined? [13:20] slytherin: in build.xml [13:20] slytherin: have you seen the pastebin URL ? [13:21] yes, found it. [13:21] I was not looking hard enough [13:24] AnAnt: Don't see any problem here. What is the issue? [13:25] slytherin: it doesn't subsitute ${buildlibs} with the classpaths listed in ${buildlibs} path id [13:25] slytherin: it instead puts a literal '${buildlibs} [13:25] slytherin: it instead puts a literal '${buildlibs}' in the manifest [13:27] AnAnt: can you try 'ant -verbose ' [13:28] slytherin: did that, but got nothing useful [13:30] AnAnt: looks like you need pathconvert. Check http://martin.ankerl.com/2005/11/30/howto-create-manifestmf-classpath-from-ant/ and http://www.guydavis.ca/log/view.jsp?id=851 [13:32] cool ! thanks [13:47] dholbach: enjoy your holiday! [13:47] thanks highvoltage :) [13:48] dholbach: where is it going to be ? [13:49] Iceland :) [13:49] and afterwards to Austria: Mimi's sister is marrying [13:49] ah, not Debconf [13:50] I don't think Mimi would appreciate the idea of going to Debconf during holidays :) [13:50] that's not her idea of holidays :) [13:50] but anyway I'm very much looking forward to lots of nature and hiking [13:50] cool, you must take pics [13:51] I will surely do that :) [13:53] Hi all, does anyone here know how easy (or hard) it is to change the name of a package that is in the repos? [13:54] dholbach, hope you ll enjoy holidays .. supermen with superpowers also need rest :) [13:54] coolbhavi: source package ? [13:54] coolbhavi: or just binary package ? [13:54] dstansby: depends on package [13:54] coolbhavi: I don't have super powers - that's cjwatson :-) [13:54] AnAnt, its not me its dstansby [13:55] coolbhavi: oh sorry ! [13:55] It's ddrescue from universe [13:55] dholbach, you are a superman.. thats accepted by everyone I believe :D [13:56] Trouble is it's name conflicts with another binary packages name, so it is proving confusing for some people [13:57] Sorry, ddrescue is a source package, whose name conflicts with that of a binary package installed by gddrescue [14:03] dstansby: What binary packages does ddrescue source package create? [14:04] slytherin: I'm not sure, is there a way of finding out? [14:06] dstansby: Looking at https://edge.launchpad.net/ubuntu/karmic/+source/ddrescue and https://edge.launchpad.net/ubuntu/karmic/+source/gddrescue I don't see any conflicts [14:08] slytherin; Sorry, I think I've figured it out now [14:11] slytherin: I think it was a case of the bug reporter getting confused when reporting, and me getting even more confused when trying to understand his origional bug. Thanks for your help though :D [14:15] Hey, I need some help with Launchpad, or there is something broken about danish translation ... [14:17] I joined the danish translation team, but when I want to translate something, I get "This translation is managed by 'De danske oversættere af Ubuntu". (This means, "The danish translators of Ubuntu". When I click this group, I don't get a chance to try and join this group, and if I try to open "Translation guidelines", I get: "Not allowed here Sorry, you don't have permission to access this page. " [14:17] slytherin: that worked like a charm ! thanks [14:17] good. [14:17] Hehe .. A Slytherin charm? :) [14:17] :-) [14:17] Dabian: can you come to the #launchpad channel, and we'll see if we can solve it there? [14:18] dpm: Thanks. [14:18] dpm: I am there! :) [14:18] dpm: Do you wish me to repost the question? [14:18] Dabian: yes please [14:31] hey folks -- any chance we can get version 0.25 of monkeysphere synced from debian unstable? [14:31] https://bugs.launchpad.net/ubuntu/+source/monkeysphere/+bug/345054 has been open for 4 months now [14:31] Ubuntu bug 345054 in monkeysphere "please sync monkeysphere 0.25 from debian unstable" [Undecided,New] === sbasuita_ is now known as sbasuita === dholbach_ is now known as dholbach [14:42] dkg0: Is ubuntu-universe-sponsors subscribed? [14:42] it is, yes. [14:42] Then it should get reviewed at some point. [14:42] (as of today only, though) [14:43] is it possible that it will make it for karmic? [14:43] dkg0: Maybe you should provide all the information asked for: https://wiki.ubuntu.com/SyncRequestProcess#Content%20of%20a%20sync%20request [14:47] simon-o: i think everything there has been supplied for the last 4 months. [14:47] is there something i'm missing? [14:49] dkg0: Source package version number to sync (0.25-1) and that it is in debian main are missing. But I think that's less important [14:51] i've just made those points explicit in a followup comment. i can't imagine that they would have confused anyone, but being explicit is better than being vague. thanks for pointing that out, simon-o. [14:52] dkg0: in ubuntu-dev-tools is the script requestsync. It provides all the information you need and files a bug automatically. Maybe you could try that next time :) === nxvl_ is now known as nxvl [14:53] i'll take a look, thanks. it was a little bit frustrating to have the bug get no response for 4 months :( Now i see that apparently i didn't have the right group subscribed to it. [14:54] maybe there's a way that launchpad could automatically subscribe *someone* for bugs against a given package? It just seems odd that there was not even any triage there. [14:55] and now i see that it's "declined for karmic by iain lane [14:55] with no other details? [14:56] dkg0: monkeysphere 0.25 was uploaded to Debian TODAY. [14:56] yes, it was. [14:56] and 0.24 has been around for 4 months. [14:56] So up until several hours ago there was nothing to sync. [14:56] ubuntu is still shipping 0.22 [14:57] dkg0: No. 0.24 is in Karmic already [14:57] not according to http://packages.ubuntu.com/monkeysphere [14:57] should i be looking somewhere else? [14:58] https://launchpad.net/ubuntu/+source/monkeysphere [14:58] and yes I declined it for karmic because this is not a release goal [15:00] Laney: That doesn't make any sense. [15:00] ok, i'm glad to see that 0.24 is shipping in karmic at least. [15:00] what doesn't? [15:00] I declined the release nomination [15:00] "Not a release goal" as a reason to not sync a package at this point in the cycle. [15:01] I didn't close the bug [15:01] i "nominated it for karmic release" thinking that meant "i'd like this to happen for karmic" [15:01] "Declined" carries the idea that we won't do it in this cycle. [15:01] dkg0: It's really unneeded for the development release. [15:01] if what it really means is "this is a release goal" then i was mistaken in marking it that way. [15:01] that's not the case :) [15:02] Laney: that's why declining is a problem. Other MOTU will look at it and think "there must be a reason we don't want to do this." [15:02] i think it would help to clarify the semantics of what "nominated for a release" means. [15:02] dkg0: monkeysphere 0.24 has failed to build. That is why you don't see it on packages.ubuntu.com [15:03] ScottK: Really? I would look at the status of the bug and not whether it has been accepted or declined [15:03] dkg0: https://edge.launchpad.net/ubuntu/karmic/+source/monkeysphere/+builds [15:03] slytherin: could you point me toward the build log then? [15:03] ah, thanks. [15:03] if it were really rejected then I would have set it to Invalid or Won't Fix [15:04] but yes I accept there is general confusion about the nomination feature as applied to the development series [15:06] I'm trying to backport passenger to hardy and running into a weird build-depends issue [15:06] it needs rake to compile, but when I have rake in the Build-Depends: it complains that it is a virtual package [15:06] slytherin: that failure is related to http://bugs.debian.org/527765 -- building within a group-writable or world-writable directory will cause the test suite to fail because the test suite emulates dealing with sensitive files related to ssh authentication. [15:08] mfoster: Do you have universe component enabled in pbuilderrc? [15:08] dkg0: The bug is marked as 'won't fix'. [15:09] that's correct. [15:09] the point of the test suite is to ensure that the package properly detects files and paths that could be modified by other people [15:09] so that it doesn't feed those files to sshd for authentication purposes. [15:10] we could disable the test suite, but then we would lose the check that the package is actually working as expected for users. [15:10] that seems like a bad security tradeoff. [15:11] slytherin: COMPONENTS was commented out, I'll try that, thanks! [15:11] in particular, the problem (from the test's perspective) is that /build/buildd is group-writable. [15:12] mfoster: you need to do 'pbuilder --update --override-config' after that. [15:13] dkg0: I can't say I understand all of that. But I guess you will have to wait for someone to see if 0.25 builds properly before it actually get synced. [15:13] dkg0: It will be great if you yourself can verify that in pbuilder. [15:13] 0.25 will have the same issue if /build/buildd is group writable. [15:15] is there an explicit design decision that it /build/buildd should be g+w ? [15:18] slytherin: so just to be clear, it's OK to use virtual package names in Build-Depends: ? [15:21] mfoster: That error is confusing. The package is in universe. By default only main component is enabled in pbuilderrc. [15:23] slytherin: thanks a mil! I've got it to build now :) [15:31] Hello, can someone confirm this syncrequest: LP 399123 [15:31] Launchpad bug 399123 in dico "Sync dico 2.0-2 (universe) from Debian unstable (main)." [Wishlist,New] https://launchpad.net/bugs/399123 [15:31] This fixes a bug making dicoweb uninstallable [15:36] Some packaging help, please? I've a package A that depends on package B. In a later version I decide that A should also depend on a third package C. [15:36] Now, if I use synaptic, it upgrades the package A and installs C to satisfy the dependencies. [15:36] But if I use apt-get update, then I get the error: The following packages have been kept back: A [15:36]