[00:11] devfil: pong [00:11] pochu: I'm uploading wxwidgets2.8 [00:11] I've already uploaded it, but I've changed a bug number in the changelog [00:12] uploaded to where? [00:12] so I'm reuploading it [00:12] http://revu.ubuntuwire.com/details.py?package=wxwidgets2.8 [00:12] REVU [00:12] let me know tomorrow, I'm off to bed now [00:13] pochu: I'm uploading it now, so the best think is to wait ;) [00:13] and it needs attention [00:14] devfil: you could save bandwidth uploading just the diff.gz to the bug report ;) [00:15] pochu: I know, but I prefered this solution to have the orig.tar.gz with the good md5 etc... [00:15] ah, right [00:16] oh, let dato know about it, in case he uploads to Debian, so we have the same tarball and can sync in the future [00:16] now orig.tar.gz generated by get-orig-rules had the same md5 for each launch of rule [00:16] that's great [00:16] pochu: yes sure [00:16] I prefer firstly a review to see if it is ok [00:17] s/a/to have a/ [00:18] but tomorrow :) [00:18] good night [00:18] good night [00:48] Hobbsee: did I see you mention something about pidgin the other day? [01:25] good night [01:27] hi === keylocker is now known as leleobhz [02:44] ScottK: around? [02:44] nxvl: may I contact you in prv ? [02:45] well [02:45] ok [02:45] :D [02:45] if you have something prv to day [02:45] say* [02:46] lots :-) [02:46] if you like feel free to use rapache-devel for this === macd_ is now known as macd [03:06] lifeless: w.r.t? [03:06] out of date client or something [03:06] probably the icq mess [03:06] lifeless: oh yeah - icq being annoying again. [03:06] ajmitch: sounds like I'm hitting it :) [03:07] whats the story? [03:07] lifeless: they've pushed an update into proposed, afaik. [03:07] lifeless: every once in a while, icq decides that the old clients are too old, and won't let them connect. [03:07] with no other changes? [03:07] so every once in a while, we have to bump the ICQ version string on the clients. [03:07] yup. [03:07] spethial [03:07] well, presumably there's changes to the official clients, but not to us [03:07] yes, very... [03:08] changes probably means more advertising on the official clients [03:08] ajmitch: very likely. [03:08] can't pidgin just try a few new numbers and see if one works? [03:08] good question - i'm only familiar with the kde3 kopete side [03:09] lifeless: kopete does something similar: if it fails to log in, it grabs the newest version codes from the net, and tries with those. [03:09] but i think that's what the kde4 version is doing - auto-updating [03:09] Hobbsee: Isn't it only auto-updating the ICQ version information, rather than the whole application? [03:10] persia: yes, taht's what i meant, sorry [03:11] Hobbsee: No need to be sorry: I just wanted to make sure I had the right story. Thanks for the confirmation :) [03:12] hello people [03:15] persia: no problem [03:16] * TheMuso wonders what bitlbee does then, since I'm having no problems. [03:17] TheMuso: If you find out, could you port to the others? [03:17] persia: Perhaps, but I have no reason to dig unless it breaks. :p [03:18] Right. Maybe someone ought put a pointer to using BitlBee as a proxy in the pidgin bug :) === asac_ is now known as asac === keylocker is now known as leleobhz [03:54] ok [03:54] i think augeas has the correct copyright now [03:54] :D [03:55] nxvl: You've checked every single file? [03:56] yep [03:56] not only the *.c files [03:56] also the .m4 ones [03:56] * persia uses `less $(find .)` [03:57] nxvl: And the other files? No .h? No .xml? Nothing else? [03:57] i used: find . -name '*.*' | xargs head | less [03:57] my head hurts from reading mail about voting methods [03:57] nxvl: Be careful. Sometimes people put extra licensing conditions and the like below the first 10 lines. [03:58] i'm using .c and .h has same licenses [03:58] s/using/asuming/g [03:59] That's not safe. The .h files might be more open (e.g. ISC vs. GPL) for a common interface, or more tightly restricted where compatibility with some specific implemenation is required. [03:59] well, the only !LGPL are the tools used for building and things, and almost all of them are from GNU [03:59] * nxvl checks .h files [03:59] nxvl: As long as you're sure :) [04:00] yes, i am [04:00] Also, $(find .) is the same as $(find -name "*.*"), except that it also matches e.g. README (where there is no '.') [04:00] but a quick look doesn't hurt, don't it? [04:00] Never :) [04:01] well [04:01] i have read README files carefully [04:01] as well as all the non source files [04:06] ok [04:06] rechecked [04:11] now i'm sure it's correct [04:17] nxvl: Perfect! [05:19] if a patch closes duplicate bugs how do you show that in the changelog? (LP:XXX)(LP:XXX)? [05:19] null_vector: Do you mean two different bugs, or are the bugs themselves duplicate? [05:20] they're dupes [05:21] null_vector: Close the master. Make sure the duplicate is appropriately marked as a duplicate in launchpad. [05:25] nxvl: I'm around for a bit now. [05:25] about the revu comments [05:25] NEWS didn't install when installing dh_installdocs is runned [05:26] but it's also not required so i remove it [05:26] nxvl: If it doesn't install automatically, ignore my comment. [05:26] I thought it did. [05:26] Sorry about that. [05:26] also it has informatios about gnulib's license [05:26] It should be installed. [05:26] well, no problem [05:26] :D [05:26] every single comment is valid [05:26] they make me learn and investigate new things [05:42] good morning [06:01] Morning dholbach! [06:01] hi AstralJava [06:03] dholbach: How's life? You're up awfully early. :) [06:37] AstralJava: life is good - I'm quite busy with stuff, but will leave for holidays in around a week - how are you? [06:38] dholbach: you woke up really early today [06:39] dholbach: Fine, thanks. One and a half weeks till holiday, but I'll manage. Getting around some packaging and merge stuff again. Won't mention anything about the progress of my MOTU voyage, though, as I'm sure you've noticed also it takes a considerable amount of time... :D === Ekushey- is now known as Ekushey [06:39] I almost wake up at that time - it's summer, my girlfriend has to get up early for work, so.... [06:39] heh [06:39] :D [06:39] here it's winter [06:51] <\sh> ScottK: nope...but I'll check on it :) [06:59] \sh: I thought you might find it interesting. [07:05] <\sh> let's see..what comes after all launchpad features :) [07:06] <\sh> right now I'm planning on offline storage of the lp tasks into a sqlite db [07:24] any archive admins around? [07:25] slytherin: #ubuntu-devel might be a better choice [07:25] slytherin: Rarely in this channel. Try #ubuntu-devel [08:15] What is failed to upload error for a build? [08:20] Laney, geser: interview publichsed [08:20] published [08:20] * dholbach gets more coffee [08:21] slytherin: It typically indicates some issue with bits of Soyuz speaking with each other. I'd recommend asking someone to investigate on #launchpad. [08:38] anyone else having no sound in Intrepid? i enabled everything but stil no sound [08:42] gnomefreak: cat /proc/asound/cards Notice the new device. Change your default. Ask Hobbsee for details :) [08:42] In other news, you can now make your case warble whilst not interrupting your audio stream :) [08:48] Hobbsee: what would i need to do to get sound working in intrepid? [08:56] Hi MOTUs! [08:56] Could Someone review my package on REVU please? [08:56] The packages is rt-tests (http://revu.ubuntuwire.com/details.py?package=rt-tests): A set of programs that test and measure various components of "realtime" kernel behavior, such as timer latency, signal latency and the functioning of priority-inheritance mutexes. [08:56] Please be patient with me it's my first package. :-) [08:56] Thanks in advance! [08:57] sounds neat [09:07] abogani: Quick notes: 1) some of my points from January still stand, 2) You should target intrepid rather than hardy, 3) It's a new package, so still Initial release, 4) My lintian says policy is 3.8.0 [09:07] ScottK, poke [09:08] cody-somerville: he went to bed an hour ago [09:09] :( [09:09] Guys... it's sponsoring time! [09:09] persia: Ok Thank you a lot! [09:09] :) [09:17] Right. As this thread goes further, I get convinced of the benefits of the one-person, one-vote system. We just need the right person. [09:17] that reminds me, i was gonna work on some packaging this morning [09:18] bleh, new packages means NEW delay [09:18] persia : i plan to do some packaging this weekend. Are new packages being considered for Interpid? [09:18] directhex: NEW delay isn't as bad when fear-of-NEW delay is short :) [09:19] bliZZardz: Yep. Look for needs-packaging bugs in LP for candidates. [09:20] persia: i was more ref to those which are not even present there - will those be considered now? or is it better to concentrate on 'needs-packaging' ? [09:21] i need to start beating my DD contact with a bigger pole, or start considering a 0ubuntu1 package [09:21] bliZZardz: Things with needs-packaging are user requests. If you want something else, you need to put on your user hat, and make a request :) [09:22] persia : follow up Q to the previous, should i also consider backporting the packages that i target for Interpid? [09:22] or simply i can take it up later [09:22] bliZZardz: Anything present in intrepid is potentially available to be backported. [09:27] not anything. [09:27] "frameworks" are excluded, for example [09:29] persia: i do not understand when you say 'potentially available to be backported' [09:30] directhex: I doubt it: I suspect that if you had a framework that was a development target with no dependencies in the archive, it could be backported. [09:30] bliZZardz: A request for backporting may be made for any package in the current development archive. [09:31] well, yeah, dependencies is the problem. the cited reason being risk of regression in too many apps, iirc [09:31] You do. [09:35] sigh, this is my most complex packaging work so far. time to learn, fast. === asac__ is now known as asac [09:43] hrrm. Is ubuntu 8.04.1 releasing today? [09:43] enyc: There's testing. For current results (which would inform the release manager), you may want to ask in #ubuntu-testing. [09:45] persia: ok I shall go look /ask ;-) [09:45] persia: and report my findings etc... thanks for channel pointer ;-) [09:53] persia: ping [09:54] ScottK: Wine 1.0 has been in backports for some time, and no bugs filed yet...Would it be appropriate to move it to -proposed now? [09:55] devfil: It's *always* better to explain why you want someone. I suspect that regardless of your question, someone else here will be better able to answer it, but I'm here now: what are you asking? [09:55] persia: http://revu.ubuntuwire.com/details.py?package=wxwidgets2.8 [09:56] if you want to take a look at it [09:56] devfil: Right. You do know that I don't use *any* wx2.87 apps, right? [09:56] I'll add it to my review list. [09:56] s/7// [09:57] persia: but you know the package and for me you are the best to check for soname etc... [09:58] devfil: I'll review it. I'll also note that the only reason I know wx is because I was trying to purge an old version: it is familiarity through revulsion, rather than because I like the package :) [10:00] * sebner waves :) [10:01] * DktrKranz plans revenge [10:01] * sebner hides [10:07] * DktrKranz notes wxwidgets2.8 is finally in unstable, we should work closely with dato to have it finally in sync === quassel251 is now known as smarter [10:18] persia: DO you have time to advocate xml-commons-external? If it goes in archive today then I will be able to complete batik upgrade today itself. [10:19] slytherin: What does it need? [10:20] persia: I need seond advocate for my package on revu. geser has already advocated. === dholbach_ is now known as dholbach [10:27] persia: for some reason the package is neither on revu nor in archive [10:28] slytherin: You'll want to put it in one of those places if I'm going to look at it :) [10:28] persia: it was there on revu till 2 days ago. [10:31] slytherin: http://revu.ubuntuwire.com/details.py?package=xml-commons-external and https://launchpad.net/ubuntu/intrepid/+queue?queue_state=0&queue_text=xml-commons-external should explain the current status. [10:31] persia: someone already gave second opinion. It is being uploaded. [10:31] good morning [10:32] How do I use "bzr bd" with pbuilder to build a package (for upload to a ppa) [10:32] ? [10:32] persia: Cool. I will hopefully have batik updated and uploaded to review by tonight. [10:34] slytherin: Note that until xml-commons-external passes both source new and binary new, batik is likely to FTBFS. [10:35] persia: That is fine. The package review will take time. I will add a note on revu saying it needs xml-commons-external. [10:43] Laibsch: you want to use the "--builder" option to bd [10:43] james_w: Thanks. I'll give it a try [10:43] Laibsch: e.g. "bzr bd --builder pdebuild" [10:43] I did not see it in the man page [10:43] OK [10:43] james_w: Does that work with sbuild as well? [10:43] Laibsch: or, what I do, which is "bzr bd -S" and then use pbuilder-dist on the resulting source. === asac_ is now known as asac [10:44] That sounds good. [10:44] I tried -S, but then failed to sign the packages [10:44] s/packages/files/ [10:44] persia: it requires a builder that works from inside an unpacked source package, like dpkg-buildpackage does. I'm not familiar with sbuild. [10:44] .changes etc [10:44] Laibsch: debsign can help with that. [10:45] james_w: Ah. sbuild acts on prepared source packages. I suspect bd -S is the appropriate workflow for sbuild users (and likely also for most pbuilder users if they expect to get the results into Ubuntu) [10:45] yup [10:47] Laibsch: What error does it give when trying to sign package? [10:47] doko: re bug 218963, SRU FTBFSed. If you want, I can have a look at it [10:47] Launchpad bug 218963 in wink "libexpat1 does not contain libexpat.so.0 in 8.04 Beta" [High,Fix released] https://launchpad.net/bugs/218963 [10:49] slytherin: no particular error [10:49] DktrKranz: no need, there is a fix in the upload queue [10:49] I just did not get what I needed [10:49] I am not even sure, I used debsign [10:49] Laibsch: not sure if it is related but I usually use options -S -sa [10:50] doko: ah... noticed just now. sorry. [10:52] w [10:52] Oops [11:02] is anyone able to do proepr session recording with istanbul? [11:22] right, i think i'm done working on this package [12:07] dholbach: Woohoo! [12:07] :) [12:12] morning [12:13] howdy emgent_ === emgent_ is now known as emgent [12:14] hi folks [12:17] hey sistpoty|work [12:17] hi emgent [12:20] Hello emgent, sistpoty [12:20] hi Iulian [12:20] hi Iulian [12:21] How's life all? [12:24] Did we ever agree on any standards for DIF exceptions/acks? [12:25] cody-somerville: We did, but I hadn't sent out the minutes. I'll write them up now. [12:25] persia, Thanks. I was thinking of tackling the sponsor queue :) [12:25] persia: is geser aware of java team meeting today? [12:25] http://irclogs.ubuntu.com/2008/06/27/%23ubuntu-meeting.html has the log if you're curious [12:26] slytherin: I don't have private information, but I suspect the answer will soon be: "Yes" :) [12:28] is come bored core dev around? :P [12:28] *some even [12:29] * sistpoty|work is around, but not bored *g* [12:29] sebner, ping [12:33] Are we setting ACKed sync requests as triaged or confirmed? [12:33] either [12:34] sistpoty|work: there's the first debdiff from my mentee waiting at #68852, if you want to have a look at it :P [12:34] bug #68852 [12:34] Launchpad bug 68852 in findutils "Error in man page, re: -printf \ escape" [Low,Triaged] https://launchpad.net/bugs/68852 [12:36] RainCT: on a first glimpse, looks good. but as I'm at work I cannot build packages here... [12:36] Does anyone know how to unsubscribe with the new launchpad UI? [12:37] RainCT: if it's not uploaded this evening, I'll give it a closer look then ;) [12:37] cody-somerville: click on 'yourself' [12:37] sistpoty|work: okay, thanks :) [12:37] cody-somerville: When it's a red - symbol, it will unsubscribe [12:37] * Hobbsee wonders what sharm's regular nick now is? [12:40] cody-somerville: pong [12:40] sebner, when you file sync requests can you please be more verbose then just pasting the debian changelog? [12:41] cody-somerville: once an archive admin told me I shouldn't write more text since it will take them more time to read and check if it's ok O_o [12:42] lol [12:42] sebner, Do you remember which particular archive admin said that? [12:43] It confuses them [12:43] cody-somerville: though I'm a universe-contributor so you could trust me xD [12:43] cody-somerville: buh long ago. I'll check my bug reports [12:43] ....that's oh so wrong, on oh so many levels... [12:43] Hobbsee: hmm? [12:44] sebner: Please do provide some information including 1) Why any Ubuntu variation can be dropped, 2) what is good in the new version, and 3) whether it compiles & runs under the current development target. [12:44] [21:41] cody-somerville: once an archive admin told me I shouldn't write more text since it will take them more time to read and check if it's ok O_o [12:44] Even if the archive admins ignore it, it helps the rest of us understand why something was pulled or overwritten. [12:45] archive admins shouldn't be checking if it's correct anyway [12:45] sebner: bah, I don't trust you anymore :P [12:45] that's the job of the sponsor, or the MOTU. [12:45] persia: well the syncs I filed are real since and they were syncs in the past so nothing to drop, I testbuild everything so the only thing is to write why I sync the new version [12:45] and if they can't get that right, they clearly should not be sponsoring / requesting a sync for that particular package. [12:46] sebner: were you filing sync requests while the autosync was still on? [12:46] Hobbsee: nope [12:46] hm [12:46] sebner, Even if there is no Ubuntu delta, you should mention that. [12:46] sebner: You write the rationale for the sync and the new Debian changelog? [12:46] Hobbsee: btw, why was the auto-syncs going crazy yesterday? [12:46] sebner: it should be off, so i've no idea. [12:46] persia: not the rationale ;\ [12:46] * Hobbsee does not have access to it. [12:47] cody-somerville: exactly that was the complain by a archive admin [12:47] sebner: I think the rationale is the most important part: why should we sync? Post DIF, we ought have some reason, and pre-DIF all non-auto syncs are overwriting Ubuntu variation. [12:48] sebner, Well, if you tell us his or her name we can send Hobbsee after them : P [12:48] In the mean time, please follow the sync procedure. [12:48] I just use the requestsync tool from ubuntu-dev-tools, which tells you to put a rationale in [12:48] cody-somerville: kk, /me becomes too sloppy filing syncs (like motu') :P [12:48] ;] [12:49] persia: shouldn't the u-u-c be somehow more trustful than a normal contributor? Besides you are right writing the reason why to sync [12:49] sebner: Being sloppy about syncs is not ideal, regardless of which groups might accept one as a member [12:50] sebner: It's not about trust: it's about documentation for people investigating things later. [12:50] * cody-somerville nods. [12:51] persia: how big are my chances to get an ACK when I write: "Shiny new upstream version and still enough time to fix potential bugs" ? [12:51] sebner: low. [12:52] persia: that was my work for hardy cycle. you should sponsor/complain more :P [12:52] How about "New upstream provides features X, Y, and Z. No new dependencies. Compiles cleanly on intrepid, and runs well in Kubuntu". [12:52] persia: ok that's the long version of my sentence ^^ [12:52] sebner: Most of your stuff I saw in the hardy cycle had enough documentation that I could understand the reason for it. [12:53] * sebner can't remember [12:53] slytherin: I've seen the announcement for the java team meeting, perhaps I'll attend [12:53] Yep. Being just a little wordier than "shiny new upstream: please sync" is all that is required :) [12:53] sebner: hey, my comment was serious :P [12:53] RainCT: hrhr [12:54] persia: kay, will do in future. just a side-notice. (some) motu's are writing: Dear archive admins please sync + changelog .... [12:54] sebner, and if you file sync requests on packages that are related you should probably mention if they need to be synced together or not. [12:54] cody-somerville: refer to sauerbraten or simutrans? [12:54] maybe. [12:55] didn't know that they can do that =) [12:55] sebner, well, I don't want to approve one and not the other if it'll cause breakage. [12:55] sebner: I don't like that behaviour from anyone, regardless of who. Feel free to complain to them if you don't understand why something is a sync. [12:57] persia: I look at the changelog and the last ubuntu version and see why it is a sync so I don't mind. it's just, I already told you, that MOTU can do what they want and no one cares and a contributor always get complains (which are mostly good) [12:58] sebner: MOTU also get complaints. As I said, please complain if you see inappropriate behavious. [12:58] s/s.$/r./ [12:59] persia: the problem is that it don't disturbe me so I would have to complain for others/the rules [12:59] sebner: OK. Please spend more time tracking down regression bugs, and develop a new opinion. [13:00] cody-somerville: I'm awake now. [13:00] persia: kay. Besides I will start packaging things from scratch now so I won't file mass syncs again ;) [13:01] YokoZar: How about you file a bug against WINE to get moved and then ask for positive/negative comments there. Once we have some good story, then we do it. [13:06] rapache 0.4 is out with apache2 modules support [13:06] ScottK, :) [13:09] cody-somerville: I got ~ 4 hours of sleep last night, so I may not be entirely coherent. [13:09] ScottK, To be honest, I didn't sleep at all. [13:09] cody-somerville: I think the biggest advantage for condorcet is the one you pointed out about not dropping candidates early and so getting a good compromise candidate. [13:09] We need a ubuntu-dev-keyring package, methinks [13:10] I don't think it matters that it's more complex. I don't see any other downsides. [13:10] Laney: What for? [13:10] For who-uploads? [13:10] ScottK: For when I dget -x something, I hardly ever have the key so have to do another dpkg-source step [13:11] Yes, I could do xu, but it's nice to verify anyway [13:11] Laney: It'd probably be easy enough to script out of LP. === LucidFox_ is now known as LucidFox [13:13] I might look into doing it [13:17] morning [13:25] hello dholbach, I created the ubuntu-translator-tools package which contains little helpers for translators: firefox search for rosetta, podiff (compares po files), search-translation (allows to search for strings in the locally installed language packs) and enables the ppa with the automatic updates language-packs [13:25] dholbach, the ppa is at https://edge.launchpad.net/~ubuntu-translator-tools-hackers/+archive [13:26] dholbach, perhaps it is worth to add it to universe [13:26] dholbach, the ppa also includes python-polib which is required by podiff [13:29] dholbach, oh, but I would have to update it for intrepid before. [13:42] How does one merge branches in LP? Just pull the two branches, push the obsolete to the new branch and delete the obsolete branch? [13:43] I am talking about https://code.launchpad.net/~vcs-imports/subdownloader/trunk for example [13:44] what's the other branch? [13:44] Yay, my first SRU is published \o/ [13:45] Laney: welcome in the club :) [13:45] Thanks DktrKranz! [13:45] once started, it's hard to come back === evand_ is now known as evand [13:47] glatzor: sounds good - best to get it on REVU and get it reviewed [13:49] dholbach, I am just reading the howto [13:49] great [13:49] would you like to add me to uploaders team? [13:49] or is there a special requirements [13:50] hey glatzor [13:50] hello james_w ! [13:51] ok, I should have taken a look a before :) [13:52] ajmitch, hi, would you please sync the revu-upload keyring? [13:52] glatzor: sync is already in progress ;) [13:52] thanks sistpoty|work [13:52] np [13:53] And I was all ready and waiting this time. I will get it one of these times... [13:54] sorry persia ;) [13:58] sistpoty|work: No need to be sorry: you should celebrate your response speed :) [13:59] persia: well, I guess my fast response speed also means that I'm once again procrastinating *g* [14:00] glatzor: done [14:02] ls [14:09] Where do i file a version bump for an applicatien? [14:09] I'd like to get an application updated. [14:10] joshu: file a wishlist bug against the package [14:10] joshu: new bug on https://bugs.launchpad.net/ubuntu/+source/, and tag it "upgrade" [14:11] RainCT: Thank you. [14:16] null_vector: The other branch is https://code.launchpad.net/~subdownloader-developers/subdownloader/trunk [14:16] joshu: before filing bug make sure that version is not there already in intrepid [14:16] I guess my question is who is supposed to act on the "please merge this branch" flag === sommer_ is now known as sommer [14:18] Laibsch: The owner of the branch requested to perform the merge. === Syntux__ is now known as Syntux [14:20] hm, not really [14:20] I did [14:20] Laibsch: Maybe ask in #launchpad? They usually understand the correct UI better than we. [14:21] OK === joshu is now known as zhaozhou [14:41] If I want to deal with the NBS of this library (http://people.ubuntu.com/~ubuntu-archive/NBS/libopenbabel2), will it just be enough to file bugs for a rebuild? [14:42] (after b/i/r testing of course) [14:44] Laney: yes, if it builds with the new library version [14:44] geser: Cool, will do [14:44] Just check that it deps on openbabel3 after the build [14:45] Laney: please also check if there are easy bugs to be fixed for those packages [14:45] * Laney nods, will do === james_w_ is now known as james_w [15:47] Laney: libopenbabel3 rebuilds should probably wait till the weekend, the final 2.2 release is due tomorrow, and there's currently still discussions on what the library version should be [15:48] azeem: Oh right, thanks for letting me know === thekorn_ is now known as thekorn === Syntux is now known as Guest73215 === Syntux_ is now known as Syntux [17:09] Hi, can someone review my package update on REVU? http://revu.ubuntuwire.com/details.py?package=webstrict [17:09] * sistpoty|work heads home... cya [17:22] dholbach: standard-version should be 3.8.0 but besides it's a nice vid ;) [17:22] sebner: it was shot, when there was no 3.8.0 yet [17:23] kay === keylocker is now known as leleobhz === azeem_ is now known as azeem [17:46] In debian/control, do the Depends and Build-Depends fields, get filled automatically (and correct)? [17:46] Heya gang [17:46] amikrop: No. [17:47] ScottK: But what about some ${foo:Depends}? [17:47] For some cases that works, but not all and it's not for build-dep. [17:57] ScottK, I could upload (at least send the diff.gz file) of amsn 0.97.1 to Intrepid? I added 2 patches [17:58] and I want test [17:58] or I should wait to next bugfix release of amsn? [17:59] I say that for this: [17:59] https://bugs.launchpad.net/ubuntu/+source/amsn/+bug/244876/comments/6 [17:59] Launchpad bug 244876 in amsn "[hardy] Update request for aMSN 0.97.1 bugfix release" [Undecided,Invalid] [18:00] Festor: I'd discuss it with cody-somerville or bigon. They've both done recent uploads of the package. [18:00] ok [18:03] I want insert this plugin in amsn package: [18:03] http://www.amsn-project.net/plugins.php#5 [18:03] I made all work [18:03] and I have ready the patch but I need make diff.gz file [18:03] also [18:04] there is https://bugs.launchpad.net/ubuntu/+source/amsn/+bug/99605 [18:04] Launchpad bug 99605 in amsn "amsn sounds don't play while playing something else" [Low,Confirmed] [18:05]