[00:10] LaserJock: its per user in /var/spool/mail/user iirc [00:11] even if /usr/sbin/sendmail exists? [00:12] no, you ask where it was sent too [00:12] s/too/to [00:12] e.g. how does it know, it knows by user@system and delivers to /var/spool/mail [00:12] Sendmail (or variant) is what writes to /var/mail/ ... [00:12] right [00:12] err yea [00:13] so I think I need to set up msmtp to do that :/ [00:13] LaserJock: why not just install postfix? [00:13] bah, maybe I should just install exim4/postfix [00:13] if you want local only, there is very little if any config for postfix [00:14] on install [00:14] well, I want system mail local, but I want to be able to send email out via SMTP [00:14] I was using msmtp for sending out email to the smarthost [00:14] smtp from your local box? most people will make that as spam imediately [00:14] ahh ok [00:15] but I think that meant that system mail got dropped [00:15] smarthost, yea you can config postfix for a smarthost on install via debconf questions [00:15] fairly simply [00:15] yeah, I was just trying to go "lightweight" ;-) [00:16] although I was just messing around with exim4 and I couldn't get it to work with my smarthost [00:17] I'll see if postfix does any better [00:17] :) [00:20] LaserJock: ssmtpd [00:28] oh for goodness sakes, postfix is messy [00:31] LaserJock: Is it? [00:31] I don't think it is. [00:31] For setting up local with smarthost, debconf should do it all. [00:31] But even so, I find postfix' configuration to be not at all bad. [00:31] my smarthost uses SSL authentication [00:31] Ahahaha. [00:32] both exim4 and postfix seem to choke when I get to SSl [00:33] I'm just gonna set up a system-wide msmtp config and see if that works === bperry is now known as brandonperry === brandonperry is now known as bperry [01:07] is there a reason for gnome-games being stuck at 2.20.1 for gutsy? (and 2.20.0.1 for hardy btw) We are getting a ton of crasher reports from bugs in these old versions [01:09] phomes: we usually don't update, but talk with seb128 [01:13] well, practically speaking for hardy things are stuck at 2.20.0.1 because 2.21.4 pulls in a new build-dependency which hasn't gone through the main inclusion process yet [01:14] Burgundavia: okay, thanks [01:16] oh, correction; the problem for hardy now seems to be that the last build attempt happened right while LP was being ornery, and installing all build-deps failed [01:18] slangasek: ok. No chance to get in alpha 3 then right? Too bad. I get the impression most testing of unstable versions come from people trying the alpha/betas of ubuntu [01:19] phomes: not much chance of getting it in alpha 3; depends on me snagging someone who can requeue it [01:20] Hobbsee: ping :) [01:24] slangasek: what needs to be done with the hardy alpha 3 page? [01:24] what new features need to be added? [01:26] For Alpha release notes is it appropriate to mention new stuff that needs testing. [01:26] ? [01:27] Burgundavia: good question. the new OOo might be worth a mention, if that sneaks under the wire [01:28] Burgundavia: otherwise, it's anything that looks good from -changes :) [01:28] ScottK: sure [01:28] I ask because we recently did the libclamav2 -> libclamav3 transition and went from 0.91 to 0.92, so anything that uses clamav could use a good workout. [01:29] slangasek: That effort made me appreciate the Debian BinNMU process a lot more. [01:29] Not that it was a lot of packages, but it was my first library transition. [01:32] slangasek: pong [01:33] slangasek: I will poke this evening [01:34] Hobbsee: hi; do you want to try to send gnome-games back through the ringer? It looks to me like these build failures were tied to the mirror issue [01:34] slangasek: done, & reprio'd. [01:34] Hobbsee: cheers [01:34] ScottK: yes, it's been interesting for me to readjust to not having binNMUs... :) [01:35] slangasek, Hobbsee: nice, thanks :) [01:36] Burgundavia: It'd be nice to get a mention the we've switched to libclamav3 and packages that use it really need some testing to make sure they still work as expected. [01:38] Hi everybody. I've written a debian file indexing page, and I'm looking for people who would like to comment on it and people who would like to help adding debian archive urls. Any takers? [01:39] bmm: What problem are you trying to solve? [01:39] ScottK: some of that is release notes stuff, but maybe we should merge the release notes and this page, I don't know [01:39] slangasek: ^ [01:40] Burgundavia: surely this is the release notes we're talking about? [01:40] ScottK: My brother asked me if there was a lgenerals-data package somewhere, and how he should get that data on his computer. I couldn't find a way of finding out, so I decided to create an index of debian file urls. [01:40] bmm: Asking Google isn't enough? [01:41] slangasek: are we still doing seperate release notes detailing issues with the release? [01:41] Burgundavia: by "the release" do you mean hardy, or hardy alpha 3? [01:41] ScottK: nope, didn't solve that for me.. but of course asking google is the next best thing. [01:42] Burgundavia: https://wiki.ubuntu.com/HardyHeron/Alpha3 is the draft for the alpha 3 release notes. For final release notes, I'm assuming there's not much point in having anything separate yet since issues will come and go [01:42] ScottK: I'm not sure google is that good at indexing debian files. Matching on filenames is not easy and knowing that it's a debian file is not really possible. I tried filetype:.deb but it didn't really result in anything ;-) [01:44] bmm: While for a data package it probably doesn't matter so much, mixing and matching Debian packages built for different releases can be problematic. [01:44] ScottK: yes, that's true. It may be a good idea to post that on my page :-) [01:47] Ok, I've added a notice to the page :-) [01:47] ScottK: Thanks for you comment! [01:48] bmm: You're welcome. === _nuu is now known as nuu [01:54] phomes: right, so, on the next round the buildd itself works fine and shows again that one of the build-dependencies is not available in main, so. [01:55] nor do I see that anyone's started the process of trying to get it accepted in main [01:55] Am I reading this correctly: "#!/usr/bin/python or #!/usr/bin/env python (the former is preferred)" means that I should uphold #!/usr/bin/python in favor of the env version right? [01:56] (I would suspect the env python method being more flexible) [01:56] you should use #!/usr/bin/python, yes [01:56] bmm: #!/usr/bin/python is preferred [01:56] bmm: #!/usr/bin/python is more reliable. [01:56] Heya gang [01:56] '#!/usr/bin/env python' will search PATH, so could use /usr/local/bin/python leading to unexpected behavior [01:57] /usr/bin/env is only more flexible for supporting systems that don't support .deb packages [01:58] Hihi, every time I start typing a comment, somebody answers it :-D [01:58] Ah, I see no response as usual from the games team on asc.. [01:59] bddebian: er, I saw one response earlier when I looked at the list archive [01:59] Heya bddebian. [01:59] Hi ScottK [01:59] bddebian: anyway, it's come to my attention that the only uploading the current "Uploaders" ever did was to adopt the package into the games team [01:59] slangasek: Yeah, just Miriam [02:03] slangasek: so that person starting that process should be me I guess (co-maintainer of gnome-games) any hints on where I should go to do this? [02:04] bddebian: asc? [02:05] phomes: https://wiki.ubuntu.com/MainInclusionProcess needs to be started for ggz-gtk-client, if gnome-games is going to be using ggz in Ubuntu [02:06] bddebian: btw, does asc end up with a binary dep on libboost-regexp with this new upstream version? [02:06] phomes: Advanced Strategic Command [02:06] or do I dare hope that maybe it just needs a few templates? [02:06] I love asc! :D [02:07] slangasek: Hmm, good question [02:07] is the games team a ubuntu team or would that be gnome-games team (me...)? Cause I should read up on asc then :) [02:07] Debian Games Team [02:08] We have several Ubuntu members :-) [02:08] good - as long as it's not me not doing what I should :) [02:10] slangasek: Depends: asc-data (>= 2.0.1.0), libboost-regex1.34.1 (>= 1.34.1-2.1) :-( [02:11] bddebian: what a horrible thing [02:13] I'm sure that's pulled in by shlib deps though, no? [02:13] yes [02:13] Might not really be necessary? [02:13] it's /using/ boost that's the horrible thing [02:13] Well... [02:16] especially since boost_regexp adds no significant functionality over regcomp() regexec() regfree() [02:16] well, ok - it gets you C++ memory management. I don't think that's a very compelling reason to get one's application tangled up in boost. :) [02:17] Heh, aye [02:18] slangasek: "C offers you enough rope to hang yourself. C++ offers a fully equipped firing squad, a last cigarette and a blindfold." [02:21] hey again everyone [02:21] StevenK: oh, but it gets better [02:21] slangasek: Oh? [02:21] My preinst automatically downloads a 1.3mb file, its all working well but obviously it only shows the file download progress in the terminal window (its downloading using wget) is there a way to have it also output it graphically for users installing via synaptic or gdebi-gtk? [02:22] what's the one regexp in the whole program that asc uses boost for? [02:22] strrchr('.') [02:22] * StevenK sobs [02:22] behold, the C++ Way [02:24] oh, no, my bad; there are others here that I overlooked [02:25] yes, yes - there's also one here that does dirname() [02:25] heh [02:30] bddebian: well if I were you I would hit your upstream with a shovel for doing this; but it's largely going to be your problem, not mine, that the package depends on boost and will be doomed to eternal pain where Debian testing is concerned, so - uploading [02:30] slangasek: Why is boost getting removed? [02:30] but the jwz quote is very apt here [02:30] bddebian: it's not, it's just constantly undergoing stupid ABI changes [02:31] Oh, aye, OK [02:33] and it has lots of other large reverse-dependencies which are never ready to go at the same time [02:34] hey, would the person who keeps feeling the need to smash me over the head with a large hammer every time i get up please stop? [02:34] * bddebian hides the hammer [02:35] it's YOU! [02:36] * ScottK relaxes [02:38] * Fujitsu sneaks up behind ScottK. [02:41] * ScottK looks in the rear view mirror [02:50] boost is not managed for ABI [02:50] AFAICT, by upstream [02:54] Rock on, thanks slangasek! [02:55] slangasek: Wanna join the games team, we NEED DDs? ;-P [03:09] bddebian: thanks, I'm on enough teams [03:09] lifeless: yes, which means that every time there's a release there's an soname change, which is an ABI change :) === bigon is now known as bigon` === Am|NickTaken is now known as Amaranth [03:34] c [03:34] ugh [03:36] c [03:36] argh orca let go of my keys [03:37] I suspect it did, because we saw that. [03:50] hmm, this is still troubling me [03:50] The configure script changes the lib directory to lib64 on 64bit archs [03:51] and makes the install fail [04:57] hey guys, in my package there is a shell script for launching the application "urbanterror" the shellscript is to be placed in /usr/games/urbanterror. However since one of the two binary packages created by this source package is also called urbanterror, dh_install tries to copy the temporary build dir debian/urbanterror rather than the script which is also debian/urbanterror (but a file rather than a directory). any ideas how i can [04:57] get around this, short of renaming the shellscript or package [05:06] Burgundavia: OOo is almost certainly not going to make the cut for alpha3 at this point, since it just ftbfs on amd64. [05:07] oh goody [05:07] you can mention kde4, if it actually works though [05:07] * Hobbsee heads to work [05:08] slangasek: lovely [05:11] anyone know how i can deal with my dh_install problem? [05:12] jscinoz, use the -p option [05:12] jscinoz: Don't call the script debian/urbanterror [05:12] jscinoz: Call it debian/launcher or something, and then install it as debian/urbanterror/usr/games/urbanterror [05:13] i am using the -p option somerville, [05:13] stevenk, i was unware that dh_install would rename files [05:15] jscinoz: dh_install can't rename files. [05:16] then how do i get it from srcdir/debian/launcher to usr/games/urbanterror [05:18] dh_install copies files, which means it can copy them to arbitrary locations === bigon` is now known as bigon [05:26] i know, but i think what stevenk was suggesting is i have it named one thing in debian/ and another thing when its actually installed, and not sure how that would work [05:36] >_< [06:02] Hi, I was wondering why the fix for flash is taking so long still. Anyone know? [06:31] because nobody has figured out what to do with it? [06:37] tonyyarusso: you know something I don't? :-) [06:39] good morning [06:41] good morning [06:41] Hey dholbach. [06:42] hey TheMuso, heya boomer [06:44] dholbach! [06:45] hey LaserJock! [06:45] hello [06:46] dholbach: I sent you an email [06:47] LaserJock: I noticed but didn't get to it yet - I'll take a look at it in a bit [06:50] LaserJock: Really? I thought imbrandon said it would only be another day or two - like two weeks ago. Thought maybe something strange had come up that was unforseen, b/c he sounded like it was under control (and fixed in Hardy already, just not released vers) [06:50] tonyyarusso: yes, I'd say something came up: https://lists.ubuntu.com/archives/ubuntu-devel/2007-December/024877.html [06:51] Yes, Adobe is silly. [06:51] And Konqueror doesn't like XEmbed. [06:51] LaserJock: ty [07:01] BAH! [07:02] I wanted to check on getting another domain name, something a bit more professional sounding than 'nixternal.com', so I said hell, let me check johnson.com, and I could do richard@johnson.com, especially since my middle initial is A. [07:02] so I go to godaddy.com and enter Johnson.com and it tells me it is already taken, but here are some other options [07:02] http://www.nixternal.com/~rj/johnson.png <-- these are the other options [07:02] wtf has this world come to? [07:02] Hahahahaah. [07:03] lol [07:03] Nice, nice. [07:03] I am just going to change my name [07:03] my first name is Richard and my last name is Johnson, so I hear it all of the time, but a damn domain registrant telling me the same [07:03] this has gone to far [07:04] I was thinking donjohnson.com but that might date me [07:04] you dated don johnson? [07:04] * Fujitsu once knew a Richard Head. [07:04] sick [07:04] I know a Richard Head [07:04] went to high school with one [07:04] Same. [07:04] our football coach even called him dickhead [07:04] Haha. [07:05] * Fujitsu notes that Firefox 3 is being even safer than IE7 wrt. untrusted certificates. [07:05] It doesn't even say where to go to add an exception. [07:05] Well, it does, but it's not right. [07:05] and if everyone has seen the old Little Ceasers pizza commercials, they will remember 'Pizza Pizza!' [07:05] well my Peurto Rican buddy started 'Pinga Pinga!' [07:06] Fujitsu: when is FF3 final btw? [07:06] tonyyarusso: No idea whatsoever. [07:06] * tonyyarusso remembers Pizza Pizza! [07:06] ok, back to bed for me...g'nite all [07:06] Night nixternal. [07:06] All I know about FF at the moment is that FF3b3 is actually worth using, unlike earlier FF releases. [07:08] "Mozilla is on track to release the final version of Firefox 3 during the first quarter of 2008...we can expect the Beta 3 release sometime in February" [07:08] So, quite likely before Hardy is released, but not necessarily by much? [07:12] bigon: Ping! Re: gnome-keyring-sharp. [07:13] RAOF: mmm I will recontact upstream [07:14] what is gnome-keyring-sharp? [07:14] bigon: Oh, why? [07:14] bigon: I'm just hacking on your packages as found on LP bzr. [07:14] Adding a get-orig-source target, updating the versioning, etc. [07:15] seems to not be in gutsy, all right [07:15] svn://svn.debian.org/svn/pkg-cli-libs/packages/gnome-keyring-sharp/trunk [07:15] actually [07:15] RAOF: I don't think the bzr branch is uptodate [07:15] I thought I went there and found nothing. Maybe the websvn was lying. [07:16] Ok, let's see what's changed... [07:18] Right. Not that much. [07:19] RAOF: upstream is waiting some feedback before making an official release [07:20] bigon: Right. From whom? [07:20] somebody who test his software :o [07:20] Such as may be garnered by putting a package into Debian Experimental, say? :) [07:23] bigon: I don't have write access to pkg-cli-libs svn. If I supply you a diff would you kindly apply it? [07:23] RAOF: ok if you could send it by mail [07:24] Yup, certainly. [07:24] I'll just check that the package as it is currently fails to build current SVN, then fix it :) [07:27] Yup. Good. === asac_ is now known as asac [07:35] RAOF: Finally reached level 60 :-D [07:37] StevenK: In not so impressive news, I've hit 30 :P [07:37] Heh === cassidy_ is now known as cassidy [07:50] bigon: Patch sent. [07:51] RAOF: thx [07:53] bigon: Do you remember offhand what else was required for banter (which is what I was originally interested in g-k-s)? [07:54] telepathy-sharp(already pkg) gnome-keyring# [07:54] apachelogger_: thanks a lot for your mail - you should be on the net in a bit :) [07:54] and notify@ [07:54] # [07:55] Thanks. [07:55] RAOF: if I remember slomo was working on notify# [07:55] As in, libnotify-sharp? [07:56] Ah, inotify. [07:58] no libnotify [08:00] RAOF: I'm not sure if the .dll must go in /usr/lib/cli or /usr/lib/mono [08:01] gtk is in /usr/lib/mono [08:02] pochu: http://git.fedorahosted.org/git/cobbler.git/?p=cobbler;a=blob;f=setup.py;h=c8a6b8136e2e6b7ba97290e8321c69defabedd13;hb=HEAD [08:06] bigon: Fair enough. [08:07] LaserJock: ROCK! BehindMOTU works now! [08:11] ;-) [08:14] bigon: Ahhh... that'd be because gtk-sharp has dllmaps to native code, which is mono specific. gnome-keyring-sharp doesn't, so I think it's meant to go in /cli. [08:15] asking upstream [08:15] bigon: That'd be a #debian-mono question, surely? [08:16] right :o [08:16] http://pkg-mono.alioth.debian.org/cli-policy/ch-packaging.html [08:17] "The commonly seen /usr/lib/mono/packagename path should only be used for Mono project packages." [08:20] RAOF: about notify-sharp https://bugs.edge.launchpad.net/ubuntu/+bug/139356 [08:48] hi, is Lukas Fittl around? [08:50] lucas: his nick is 'lfittl' [08:57] good morning [09:13] man-di: ping [09:14] slytherin: pong [09:14] slytherin: please write direct content when pinging me [09:15] slytherin: I will answer when online or read backlog [09:15] man-di: Ok. Did you find any time to build lucene2 on debian? [09:15] nope, sorry === ember_ is now known as ember === cprov-out is now known as cprov === rzr is now known as rZr [11:03] Hi, I'm still looking for a revu of my package - http://revu.tauware.de/details.py?package=libserial - all previous comments have been addressed [11:12] When creating an .orig.tar.gz from SVN, should I remove .svn directories? [11:21] LucidFox: yes [11:22] lintian gives you an error about that [11:26] Greetings norsetto. [11:27] heya TheMuso [11:27] themuso: hope to see you soon in the core team ;-) [11:27] norsetto: I hope so too. [11:39] Its a Hobbsee! [11:40] heya! [11:40] it is! [11:40] anything interesting happen? [11:40] No, been rather quiet the last few hours. [11:45] aww [11:46] * Hobbsee points at http://www.linuxno.de/_data/gallery/nwl7/_medium_DSCN7823.JPG for a bit of amusement [11:46] heya hobbsee, long time no see [11:46] * persia questions the safety of such an arrangement, and wonders if a longer lead just wasn't available [11:46] hiya norsetto, how were your holidays? [11:46] llery/nwl7/_medium_DSCN7823.JPG for a bit of amusement [11:46] 22:46:31 < norsetto> heya hobbsee, long time no see [11:46] llery/nwl7/_medium_DSCN7823.JPG for a bit of amusement [11:46] 22:46:31 < norsetto> heya hobbsee, long time no see [11:47] Oops. [11:47] oookay? [11:47] Stupid Synaptics. [11:47] I tried to three-finger click on the link, but missed. [11:47] heh [11:47] I feel pasted :-) [11:47] * Hobbsee reads kmos report [11:48] LOL! right then. [11:48] sync requested but not really checked. Could not provide a justification beside "...it's the only way to get things updated..." [11:50] * Hobbsee notes that dholbach perhaps needs to check his sponsorships more carefully, toto [11:52] anyone know of a mouse cursor for kde? [11:52] * Hobbsee updates the wiki page [11:52] I mean, a mouse cursor in the shape of a mouse ..... === asac_ is now known as asac [11:56] * Hobbsee hasn't [12:11] soren: I don't know whether you can change variables from debian/rules, sorry. [12:11] say i want to maintain a package for 2 flavours of ubuntu and for debian unstable, what are common practices for maintainging this? at the moment i just change the release in the top changelog record before making source package for each flavour, but it feels wrong [12:13] If that's your only change, that's likely the best answer for something external to the repositories. You might define the special release "artm", and just compile it several different ways, but this may make it more difficult for your users to clearly identify against which environment the package they are using was compiled. [12:14] pochu: You can export make variables to shell variables. If you can get the shell variables into python, you should be all set (unless I have the wrong context). [12:16] persia: he wants to change some variables without patching the file [12:17] persia: well, so far that is the only change. eventually i would like to get the packages into official distributions, but for now I share them with our little community from my PPA so we can test/polish the package before suggesting it [12:17] pochu: That's harder. Does python autoset internal variables from specially crafted shell variables or accept them on the command line? If neither, you're right. === LucidFox is now known as Sikon_Stargate [12:17] i.e. changing wwwpath = "/var/www/cobbler/" to "/usr/share/cobbler/www/" [12:17] artm: Then playing with the changelog is your best bet. [12:18] pochu: Well.... If I can do it by passing arguments to setup.py, then I can do it from debian/rules. [12:18] persia: thanks [12:18] soren: of course, but I don't know whether you can change just one of those variables with an argument to setup.py :) [12:18] pochu: Ok, fair enough :) [12:19] soren: you can change all of them (or all of data_files), but just one... dunno [12:19] Maybe it's possible and I don't know it, who knows :) [12:19] If you can change all of them, you can change one: just extract them all from setup.py, adjust the one you want, and change them all to the adjusted values. [12:19] pochu: Ok. Meh.. It's fine to maintain a patch to setup.py. I was just curious is there was a more correct way to do it. [12:20] persia: That's even more of a maintenance burden, though. [12:20] (the writing of the limited python parser is left as an excercise for the make programmer) [12:20] soren: I agree. I'm a fan of patches, personally. [12:21] The quick & dirty way is to run sed -i against setup.py, but that'd be painful to understand for the next person. [12:21] :) [12:21] hi everyone [12:22] persia: not if you put a nice comment :) [12:23] not sure if this is the right place, but I have a problem in makefile.am [12:23] pochu: Maybe. Depends on the package. I avoid using sed to patch in debian/rules unless there is an active maintainer already doing so. It makes it hard to meet both the build-twice-in-a-row and the debian/rules-clean-is-really-clean tests. [12:23] what I have: file.xml which will create file.h and file.cpp [12:24] how could I define this in makefile.am [12:24] promag: You can put regular make rules in makefile.am. [12:25] I've tried it but how can I make the dependency work? [12:26] promag: Er... You haven't given nowhere near enough information for that question to make sense (let alone be answered). [12:26] promag: file.h file.cpp: file.xml [12:26] what I put in _SOURCES? [12:27] file.xml? [12:27] or file.xml and file.cpp ? [12:27] Have you tried? [12:28] yes.. the custom target isn't called... [12:30] I have tried this: http://unix.derkeiler.com/Newsgroups/comp.unix.questions/2003-04/0157.html [12:33] I belive #devtools on OFTC is the autotools support channel. [12:36] thanks [12:36] promag: I've done something similar, hang on [12:37] mok0: great! [12:37] promag: put the file.cpp in _SOURCES [12:38] it is already [12:38] promag: and make a rule to generate file.cpp [12:38] .cpp: %.xml [12:38] echo $@ && touch $@.cpp [12:38] file.cpp: file.xml [12:38] I have this [12:38] promag: that rules doesn't do anything? [12:39] no [12:39] file.cpp: file.xml /n/t xml2cpp < file.xml > file.cpp [12:40] if I specify file.cpp: file.xml then its ok... but if I use %.cpp: %.xml then it fails [12:40] I need a generic rule [12:40] promag: hm [12:40] otherwise I'll have lots of those [12:41] promag: but you are not generating any .cpp files from the .xml (?) [12:41] yes I am... touch file.cpp :) [12:42] just empty files? [12:42] well it works :P [12:42] later I'll switch touch to the generator [12:42] promag: what does this program do? :-P [12:42] what? [12:42] what program? [12:43] the generator? [12:43] promag: it was a joke... a program with null files... [12:43] :P [12:43] well it doens't matter what the .cpp has [12:43] (for now) [12:43] promag: there may be some restriction on using generic rules inside Makefile.am, I'm not sure [12:44] mok0: yes I think generic makefile rules doens't work in Makefile.am [12:44] if you see /usr/share/automake-1.10/am/yacc.am [12:44] promag: why don't you make a small script that generates the mass of individual rules [12:45] because automake should be the solution no? [12:45] promag: just to generate the individual rules to put in Makefile.am [12:45] I'm not happy with that solution [12:46] promag: I understand. But it would work [12:46] promag: you may zoom in on a better solution later [12:55] mok0: soren: persia: any idea of a package that could have a similar process? [12:55] promag: What happens to generic rules you put in Makefile.am? [12:56] I wouldn't expect automake to just remove them. [12:56] nothing [12:56] Ill check makefile [12:57] its right after .PHONY [12:57] So it's there? [12:57] Ok, what was the problem again? [12:57] promag: then it should work [12:58] hoooooooo [12:58] %.cpp fails [12:58] but if I do %Generated.cpp: %.xml then it works [12:58] promag: Don't put anything after .PHONY. Also, try adjusting %.cpp: %.xml to be $(CPP_FILES_TO_BE_CONSTRUCTED): %.cpp: %.xml [12:59] I'm not putting anything .PHONY... automake is! [13:00] * persia disagrees with automake on this stylistic point, but the important part is $(expression): (variable extraction): (variable replacement) [13:00] If you don't have both colons, make assumes you are talking about a file called %.cpp === azeem_ is now known as azeem [13:01] promag: http://libre.adacore.com/viewvc/trunk/polyorb/docs/Makefile.am?view=markup [13:02] you are most helpful! [13:06] Hey, im trying to track down a change to the Makefile in linux-ubuntu-modules. Specifically, the reason why rtl8180 is disabled [13:10] Toma-: have you looked in the changelog file? [13:11]