[00:00] libxine-dev [00:00] is missing [00:00] which is needed for one plugin [00:00] Telling me isn't going to do any good. [00:03] * ajmitch notes that \sh uploaded a new revision just recently [00:04] ion_, which ad is that? === blueyed_ is now known as blueyed [00:31] c [00:31] wrog tab [00:31] TheMuso: I think you need an irssi script to automatically say `ugh', `wrong tab', `orca let go of my keys' when it sees ^c$. [00:33] Fujitsu: har har [00:33] Its this keyboard as well I think === RAOF_ is now known as RAOF [00:49] TheMuso: Or maybe just a script that filters "^c$" from input? :-) [00:51] possibly [01:25] * imbrandon yawns [01:27] evening all [01:27] Hey imbrandon. [01:27] man been a long 3 days at work, $world broke, but i got to be the saviour with a ubuntu live cd :) [01:28] hehe [01:29] imbrandon: Doesn't most of your equipment support EFI in one way or another? I don't suppose you could trick it to boot Ubuntu off the network on-demand so that you don't even need to open the cabinet when something can't boot. [01:30] yea mostly , but in this case someone already tryed to "fix" the issue [01:30] and i was left with scraps to fit back togather [01:31] generaly though we have port 46 on all the switches in the cabnets set to a DHCP + PXE + multi distro live + bart pe , etc etc etc [01:33] so when something breaks or we are swapping hardware we just unplug it from the network its plugged into and put it on 46 and reboot [01:33] choose from a ncurses menu the pxe env we want, dell diag, ubuntu/centos live , etc [01:33] * persia advocates switchport vlan reassignment over physically moving cables [01:34] :) [01:55] Hii all [01:55] we want to build a tool apt- package [01:56] its a tool which is used to create a mirror of the packages that a user wants [01:56] **I mean it is a tool which can be used [01:56] why not use apt-proxy [01:56] are there any alternatives already available for this?? [01:57] Kano: what is apt-proxy?? [01:57] is it somewhere close to what we have thought?? [01:57] well use it as proxy server for apt [01:57] it will cache the files [01:57] Kano: I did not get you [01:57] install it and read manpage [01:58] persia: you've fixed bug 74097, but bug 154180 requests that it should not run without confirmation.. what do you think? add a confirmation or remove the postinst-update again? [01:58] Launchpad bug 74097 in apt-file "apt-file update needs to be run" [Wishlist,Fix released] https://launchpad.net/bugs/74097 [01:58] Launchpad bug 154180 in apt-file "apt-file update should *not* be run in postinst without any feedback (was: [Feisty->Gutsy] apt-file causing upgrade to fail)" [High,In progress] https://launchpad.net/bugs/154180 [01:58] I have read the mapage but did not understand it [01:58] madrazr: apt-mirror [01:59] imbrandon: apt-mirror wont work for single packages I think right?? [01:59] say suppose I want only amarok to be mirrored [01:59] blueyed: Hrm. The issue is that apt-file won't work when installed (waits for the next cron run) if we don't run it, but I agree that I didn't consider the needs of those with bandwidth constraints when doing 74097. [02:00] so that I can install it on another machine not connected to internet [02:00] Maybe we could do something with debconf to allow the user to choose whether to run it automatically or manually later? [02:00] madrazr: aptoncd in that case [02:01] persia: why not just have apt-file run it automatically the first time it is run? [02:01] aptoncd is not working in the manner we want, and it works for only the packages that I have already installed on my system [02:01] imbrandon: actually I thought this as an extension for aptoncd [02:01] Burgundavia: That could work too, but means patching the script, rather than just maintainer scripts. [02:01] it is a cleaner solution [02:02] persia: yes, I've thought so.. but it should not be a "high-level" question and default to "no", so it won't make sense - except from providing this reconfiguration, which may be useful to some and later. [02:03] hey its Burgundavia :P [02:03] lol [02:03] imbrandon: what do you say for that?? can we take this up as an extension to aptoncd?? [02:04] hey joejaxx [02:04] Burgundavia: :) [02:04] so that it can handle the files that aren't cached also [02:08] Burgundavia: Thnking about it, I'm less sure. I can well imagine that users might try to find a high-bandwidth environment for upgrade, but be in a lower-bandwidth environment when trying out new packages. [02:09] blueyed: One possible workaround to improve user experience, without changing much of current behaviour would be to run the update in the background so that the package manager didn't appear to hang. This raises other issues, and doesn't solve the 14MB download without warning issue. [02:11] Heya gang [02:12] Hey bddebian [02:13] Hi persia [02:16] hello bddebian :) [02:17] Hi joejaxx [02:17] anyone here touch Xorg other than b r y c e ? [02:18] :) [02:18] * joejaxx checks the changelogs :) [02:19] joejaxx: There are other people who work on X, but they tend to follow weekdays, and tend to discuss things in #ubuntu-devel [02:19] oh bah [02:19] i just forgot xorg is in main [02:20] * persia is impressed [02:20] so i would have to get someone from core to sponsor a patch [02:20] persia: lol why :P [02:21] joejaxx: The process is about the same. Just subscribe ubuntu-main-sponsors. Sometimes it takes longer, as there are fewer active main sponsors [02:21] Why? Because forgetting X is part of main seems to be to take effort :) [02:21] lol :) [02:22] i keep forgetting there are two parts to the archive [02:22] Ah. That makes more sense. [02:22] yeah [02:25] persia: well, maybe it should just auto-detect the download capacity and fallback with a warning/info that download has been skipped.. [02:25] persia: i was reminded of that when i accidentally created patces for bugs that were in main [02:25] patches8 [02:25] dfdfgdfg [02:25] ..but that appears overly complex [02:25] patches* [02:26] blueyed: I'm not sure that is ideal either, but I think we need a complex solution. Both "do it" and "don't do it" received bug reports. === bigon is now known as bigon` [02:29] any ideas? [02:31] blueyed: We can't always download at install time, as the user may not have the bandwidth. We can't always download at runtime, for the same reason. It's not an important enough question to get -phigh, so we can't leave it up to the user. Maybe we could use the notification system, like alsa does to remind you to update your default card definition? [02:41] persia: I don't know the notification system, but why not add the notification to apt-file itself: notify the user if there's no index and point him at "apt-file update"? After all it's a cli tool. [02:41] I've fixed the download expressions already to output errors, I could add a hint there, too. [02:42] (through the exit code and in apt-file itself probably) [02:42] blueyed: I'd like to give the user some information that we don't expect it in advance, just so they can update the cache before getting on the plane, etc. [02:42] I do agree having a runtime check for the cache would be a nice improvement. [02:44] Regarding the notification system, this postinst seems to work: http://revu.ubuntuwire.com/revu1-incoming/mscore-0801022000/mscore-0.8.0+dfsg/debian/mscore.postinst, with a notifier file like http://revu.ubuntuwire.com/revu1-incoming/mscore-0801022000/mscore-0.8.0+dfsg/debian/soundfont-required.update-notifier [02:44] * persia doesn't understand the notifier system well enough to know if that is the preferred method of using it. [02:45] * blueyed doesn't know it at all.. but it looks self-explaining. [02:46] But I still think that we should disturb the user during installation.. [02:47] it's really straightforward to use, yes. [02:47] even when the download only takes 5 seconds.. the user would use the tool on the commandline anyway: why not just ask him to download the files, if there's no index yet (or it's outdated)? [02:48] arguably, the scripts should not assume you have an active Internet connection at the moment postinst is executed. [02:49] blueyed: Because the user in bug #154180 took a long time to download, which may not be ideal. [02:49] Launchpad bug 154180 in apt-file "apt-file update should *not* be run in postinst without any feedback (was: [Feisty->Gutsy] apt-file causing upgrade to fail)" [High,In progress] https://launchpad.net/bugs/154180 [02:51] crimsun: Good point, although we've quite a few packages that fail that test. [02:51] yes, flashplugin-nonfree being an infamous one [02:52] it asks, doesn't it? but it's not a cli tool. [02:52] I don't see how CLI vs. non-CLI is related to asking or not asking. [02:52] (I don't think *cli is revelant here.) [02:55] persia: the license on all of them does not fit in multiverse though [02:55] persia, many of them *should* stay in universe as they are [02:57] superm1: Packages in universe shouldn't Depend on packages in multiverse, which hits mythbuntu-control-centre, mythbuntu-meta, mythstream, mythtv-theme-mythbuntu, and ubiquity source packages. [03:02] I mean, you're supposed to call "apt-file search" anyway: then you could get asked.. [03:03] blueyed: Sure, but what if I run my install, and then get on a plane. If I'm not notified until runtime, I'm stuck without a cache for the next 17 hours :( [03:04] persia: good point. So just adding a notification instead of the automatic update? [03:04] blueyed: I think it requires a few things. 1) Dropping the automatic update, 2) Adding a notification, 3) checking at runtime, and suggesting an update if the cache is missing. [03:05] agreed. I think I could do that. [03:05] blueyed: Thanks. [03:45] persia, yick i see what you would mean there. === superm1_ is now known as superm1 [03:47] Oh, persia, got a minute? [03:48] bddebian: About 13 of them :) [03:48] Bah, probably not enough :) [03:48] bddebian: What's the issue? [04:58] Any motu hopefuls out there right now? [05:02] (me!) [05:02] * bddebian 2 [05:07] i did a pack for a tool, how can i concact a sponsor to upload this to multiverse? [05:07] Heh. [05:07] looks like Scott can! :-) [05:08] hophet: Is it a new package or an update to an existing one? [05:08] ScottK: new package [05:08] * ScottK is busy trying to take libmilter out of sendmail and make it a separate package so I can get it promoted to Main. [05:08] !revu | hophet [05:08] hophet: REVU is a web-based tool to give people who have worked on Ubuntu packages a chance to "put their packages out there" for other people to look at and comment on in a structured manner. See https://wiki.ubuntu.com/MOTU/Packages/REVU [05:09] i look for some request of this package, but there inst [05:09] so i pack it. [05:10] ScottK: thanks, let me see. [05:10] bddebian: Actually I feel like you seem to sometimes on this libmilter thing: WTF did I get my self into. [05:11] The sendmail build system is, um, interesting. [05:20] Much like the code? [05:20] ScottK: cool, i will follow the steps [05:21] good night for all [05:21] cya [05:21] Dunno. I haven't actually had to look at that, but the Debian sendmail package starts off with tarball in a tarball, CDBS with an incredible number of options set, and goes from there. [05:23] ScottK: :) [05:35] I have a single script that Id like to build into an existing package, what is the best way todo this?, add it in the source and build as norm? [05:56] macd: Is this for your own use or are you planning to try to get it into the archives? [05:56] universe [05:57] So there's an existing package you want to add the script to? [05:57] yes [05:58] actually I think its like 3 files, init script, and 2 in usr/bin [05:58] Add it to the debian dir of the package, modify debian/rules to install it, document your changes in a new revision of the package in debian/changelog and then build it as normal. [05:58] cool, thanks [05:58] For an init script, there's a debhelper program for that. [05:59] dh_installinit or some such. [05:59] alrite, I'll lookup some docs on that [06:00] thanks again [06:10] Hrm. Anyone else having trouble getting to LP pages? [06:11] yep [06:11] I had to turn off beta redirection [06:12] Ahhh, edge is busted [06:12] yeah, looks like === dmb__ is now known as dmb [06:21] Hello all :) [06:22] I am interested in making a package of Tom Christiansen's Perl Power Tools. Would Ubuntu have any interest in it? [06:22] Possibly. [06:22] Getting packages into Ubuntu is a community process. [06:23] New packages are uploaded to REVU and then considered for upload. [06:23] !revu [06:23] REVU is a web-based tool to give people who have worked on Ubuntu packages a chance to "put their packages out there" for other people to look at and comment on in a structured manner. See https://wiki.ubuntu.com/MOTU/Packages/REVU [06:23] I will go read the page. Thank you. [06:23] You're welcome [06:34] ScottK: can you confirm this not a bug but a support request (or maybe a spec) [06:34] https://bugs.launchpad.net/ubuntu/+bug/182190 [06:34] Launchpad bug 182190 in ubuntu "How my company and MSFT are Ubuntu Linux - Please Fix!!!!" [Undecided,New] === LucidFox is now known as LucidFox_Portal [06:36] Burgundavia: Looking [06:37] ugh, how do I turn off edge redirection? [06:38] Burgundavia: Dunno. I don't use it. [06:38] Burgundavia: I'd mark it wishlist (e.g. it'd need a spec). [06:39] I don't see why we need to support WDE [06:39] Burgundavia: Go to the front page, and press the button [06:39] Right, so it's not your wish. [06:39] well, I don't see the need [06:40] if the laptop is using windows it is using wde, with ubuntu it can use dmcrypt [06:40] StevenK: I cannot get to the edge frontpage to turn it off [06:40] the only way to turn off edge redirection is to logout [06:40] sorry if this a "no doh" but is LP down? [06:40] Burgundavia: The main front page: http://launchpad.net/ [06:41] LaserJock: Edge looks broken [06:41] just like everything else on LP [06:41] perfectly logical, if you are an alien [06:42] and requiring about 4 clicks too manyu [06:42] Burgundavia: but it's intuitively obvious to the casual observer, as we like to say in my lab ;-) [06:43] Burgundavia: No, you just don't understand how you're supposed to be doing development work in Ubuntu with LP. The LP devs will be glad to explain it to you. [06:43] StevenK: thanks, it was interfering with my Ponies, and we know how important that is [06:43] PONIES! [06:43] ScottK: I hate you :) [07:05] I got my key signed, woot :) [07:13] hmm, weird, Fedora just doesn't like VMWare Server [07:19] white: I've just signed your key and pushed it to a keyserver. [07:27] I need to make another UDS to get some more DD sigs [07:29] DD sigs are underrated [07:30] % gpg --list-sigs stevenk | grep -c debian.org [07:30] 21 [07:30] StevenK: well, they are underrated until you need them ... [07:31] I don't need them, and I have a whole bunch. :-P [07:31] I've got mako's but that's it for the Debian side of things [07:31] Debian Maintainer's need them, that's what I'm thinking of [07:31] How many do you need? [07:32] only 1 I think [07:32] so i think I'm good [07:34] * StevenK updates his key [07:37] steven@liquified:~% for i in $(gpg --list-sigs stevenk | grep '^sig' | tr -s ' ' | sed 's/sig [23] /sig /' | cut -d\ -f2) ; do gpg --list-keys 0x$i ; done | grep -c debian.org [07:37] 50 [08:00] StevenK: ok, time for bed, http://laserjock.wordpress.com/ [08:02] ember_: did you work on the gnumeric merge too (to avoid re-doing it on my side)? [08:05] Ponies are on Planet people! [08:05] good night [08:54] PONIES! === FlannelKing is now known as Flannel [09:12] And hmph. [09:13] I did the most uploads of any active MOTU for Gutsy, and I get no pony [09:13] StevenK: At least you got a mention :) [09:13] Yay woo yay === LucidFox_Portal is now known as LucidFox [09:23] StevenK: What was the need for the `active'? Are you implying there was an inactive one that was somehow more active than the most active one? [09:41] there are of course the MOTU reserves, who are distinct from the MOTU on active duty [09:57] slangasek: Don't discount the MOTU Reserves. They often step in for a day or two each cycle, and help out when we are otherwise swamped. [10:21] Hi [10:22] hello RainCT === Janito is now known as Lamego [10:25] Does anyone know what a number means next to a responsible in http://people.ubuntu.com/~dholbach/sponsoring/ ? e.g. seb128 (22) [10:26] And how are the responsibles assigned? [10:26] pochu: The source is available by bzr pull from the same address as the web page. [10:26] i.e. there are sometimes more than one assigne, I guess that's not from LP :) [10:26] persia: oh, I'll have a look, thanks. [10:26] Personally, I find that to be frequently out of date. Responsibility is assigned based on subscribers who are members of ~ubuntu-dev. [10:27] pochu: Also, for UUS stuff, don't be afraid to grab something for which someone else is "responsible", as long as they aren't "assigned". [10:27] persia: http://qa.ubuntuwire.com/lintian/reports/Tbuild-depends-on-obsolete-package.html -> can you update this? since november not updated.. [10:28] Kmos: I can't, but thanks for pointing it out. [10:28] Fujitsu? [10:28] persia: alright, thank you for the explanation. [10:28] persia: np :) [10:30] persia: Seems like apt-mark-sync source was accepted. Should i wait for the binary to be accepted as well, or post the update already? Also, if the binary is accepted, what is the proper way to post the update – REVU, just like when posting a new package? [10:30] persia: out of date -> tell dholbach to add it to cron.hourly ;) [10:31] And yes, the last update has more than 24 hours... [10:32] pochu: Doesn't help. Sometimes candidates are there for a couple weeks (when nobody wants to touch them). Sometimes they get pulled in 20 minutes. I once saw an upload 107 seconds after submission (although I doubt anyone but Mr. Chen can do that). [10:33] Does anyone feel like giving a second advocation to http://revu.tauware.de/details.py?package=hardware-connected? :-) It’s a program that checks whether given hardware exists in the system; useful for scripting. [10:33] ion_: If the source was accepted, the archive can accept updates to the source, and the buildds will just skip the superceded source. For updates, use debdiff or interdiff patches attached to bugs against the package. [10:33] Weeks sounds like a lot... I think bugs should ordered from older to newer, instead of the other way round. [10:33] persia: How about when there’s a new orig.tar.gz? [10:33] pochu: I generally sort by least-recently-changed (although I skip ones that I'm not sure I can review properly). [10:34] ion_: If there was a new upstream release, the interdiff should contain any modifications required to pull it cleanly. [10:34] persia: hmm, I'm talking about ~dholbach/sponsoring/, what are you talking about? :) [10:35] pochu: https://bugs.launchpad.net/~ubuntu-universe-sponsors?field.searchtext=&orderby=-date_last_updated&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package= [10:35] Or, just https://bugs.launchpad.net/~ubuntu-universe-sponsors, and adjust the sort order manually [10:36] persia: Oooops. That must have stopped running after my local mirror got eaten. liw is running a similar thing now, so I might just point to there. [10:36] https://bugs.edge.launchpad.net/~ubuntu-universe-sponsors?orderby=-date_last_updated is the cleanest url [10:36] I think ~dholbach/sponsoring/ is more useful for main (where things can be ignored much longer) and for new packages, where it prompts people to go look or bug the person working on it for a new revision. [10:37] pochu: My browser doesn't preserve that URL. [10:37] Fujitsu: Sure. Does liw have all your patches (or weren't there any for lintian), and does it run against universe as well? [10:39] persia: There weren't any patches other than to get it running on my local mirror, and I believe he runs it for each component. [10:40] http://people.ubuntu.com/~liw/lintian/ [10:41] Fujitsu: Is that considered "production" yet? I'm happy to change the QA page to point there (duplicated work is not ideal), but the front page makes me unsure. [10:47] persia: You should likely ask liw about that (I would, but I'm going to be largely without an Internet connection for the next two weeks). [10:47] Fujitsu: You'll be on holiday? [10:47] Unfortunately so. [10:47] Yay for family holidays to nowhere. Or not. [10:48] Heh. Any chance you might fix the links on http://qa.ubuntuwire.com/multidistrotools/ before you go? [10:48] What's broken about them? [10:49] Hm. [10:49] That main one looks wrong, but what else? [10:49] main is universe, universe hasn't been updated since november, and I don't see all the nifty new ones I've heard about. [10:49] That sounds rather odd. [10:49] * Fujitsu looks. [10:50] Specifically, ruby, java, ubuntustudio, etc. [10:51] Ruby and Java haven't had lists compiled yet, and I thought I'd linked ubuntustudio. [10:51] Gaaaaah I'm an idiot. [10:51] off-by-one error? [10:51] mdt removals removals.txt A < universe | mdt versions2html -t "Universe package" -d -u -a Sid -b Hardy > universe.html.new [10:51] mv universe.html.new main.html [10:52] That explains it :) [10:52] I suspect a left a g off the end of my regex months ago :( [10:53] * persia should have been reporting bugs in LP rather than randomly reporting in IRC. Sorry. [10:54] * Fujitsu should have got it right in the first place. [10:57] Right, UbuntuStudio is up and looking somewhat sane, and universe is rerunning.. [10:58] * Hobbsee waves [10:58] Fujitsu: what blew up? [10:59] I'm buggy and can't write regexps properly, so my mdt output was mixed up. [10:59] Fujitsu: Thanks. [11:00] persia: Sorry about that. [11:01] Fujitsu: No worries. I've been working around it, and didn't really care about main :p Only a few missed, but still a month to catch up. [11:10] PONIES!!! [11:11] And guess who didn't get one. [11:11] awww [11:11] you just need to yell more [11:12] awww, no pony for you. not yours [11:26] pochu: Why doesn't liferea use ~/.liferea? It's cluttering my home directory, but I don't know if it's a bug. [11:34] persia: It uses ~/.liferea_1.4 here... is that a problem? [11:35] Fujitsu: I have ~/.liferea_1.2/, ~/.liferea_1.3/, and ~/liferea_1.4/, which I imagine will eventually exhaust my inodes [11:35] Ah. [11:36] On the other hand, if upstream changes the preferences format at each significant release, the migration scripts are working perfectly, and I should have deleted them. [11:49] what was the command to check which package version is higher? [11:50] RainCT: dpkg --compare-versions ... [11:50] thanks [11:50] RainCT: There's no output, so add && echo YES || echo NO at the end. [11:51] or just do echo $? after execution ... [12:04] persia: yes, with every major release the database/feedlist/preferences are migrated, and left there in case something goes wrong. 1.3 was the unstable series for the 1.4, btw [12:05] pochu: OK. As long as it is intentional. I don't suppose 1.5 could contain a NEWS.Debian entry reminding people to delete the old directory if the migration worked? [12:06] Oh, and thanks for the confirmation. I like not filing non-bugs :) [12:06] That sounds like a good idea. I'll try to remember it when the time comes (hardy+1 I suppose). [12:11] pochu: Thanks. Do you want a bug as a reminder, or do you have a separate TODO somewhere? [12:26] * dennda would love to see (at least) icewm 1.3.34 in hardy instead of 1.3.33... Any chance? [12:30] dennda: Yes, absolutely. Please prepare a candidate for review :) [12:30] Uarg [12:30] I don't know anything about packaging at all [12:30] ;) [12:31] dennda: Several people here might be willing to help, although window managers aren't exactly an easy place to start. Are you familiar with the icewm code? [12:31] Not at all [12:31] dennda: then try to persuade the Debian maintainer for an updated package [12:32] how to get hold of him? [12:33] dennda: File a bug in the BTS against icewm of Severity: wishlist asking for an upgrade (http://bugs.debian.org/) [12:33] Ok, thanks [12:34] dennda: On the other hand, given the number of bugs open in the package, the Debian maintainer may also be busy, and may appreciate any help you can provide. [12:43] persia: I've created a TODO for it. [13:24] geser, asac: What is «Add /usr/include/xulrunner to CLASSPATH_INCLUDES in configure. Add MOZILLA_CFLAGS to configure» in classpath for? Is this still needed if it builds without adding it? [13:28] hello all [13:28] The new agreement is to go with diff.gz instead of interdiff, am I right? [13:28] heya effie_jayx [13:28] (That is, for bug reports) [13:31] pochu: No. That's currently under discussion. If the discussion quiets, and there is no opposition, it will be proposed in a MOTU Meeting. If it passes, it will be announced. I think it will be about three weeks, unless someone objects. [13:32] persia: ok, I've requested a diff.gz for the vinagre update to review it. [13:32] pochu: On the other hand, there's currently no official policy for U-M-S, so I can't advise you there. [13:32] pochu: which bug? [13:33] Is there a good reason to manually use ucf in .postinst for something that can be handled by conffiles? [13:34] slicer: Depends on taste, I'd say. Why do you ask? [13:34] persia: bug 176007. I'm looking into it. [13:34] Launchpad bug 176007 in vinagre "Please sponsor vinagre_0.4 into Hardy" [Wishlist,New] https://launchpad.net/bugs/176007 [13:35] persia: Someone is working on a debian version of my package, and they're using ucf manually for all the files in /etc. I'm trying to figure out if it's a good idea, but it seems to add nothing and just create a harder to maintain package. [13:35] pochu: We do still want an interdiff for that, but the interdiff ember_ provided is useless, as it was built with -p1 [13:37] slicer: Maybe it's easier for them to maintain. I suggest asking them why they choose to do it that way. One advantage of ucf is that it makes it easier to programatically modify conffiles if one wishes to later, which makes maintenance easier if there are any desired changes to the configuration files. [13:37] RainCT: well ... without looking i think those would still be needed. maybe configure just falls back to firefox-dev automatically? which value can you see for MOZILLA_CFLAGS in config.status ? [13:37] (after configure) [13:38] persia: The reason was to "avoid automagic stuff". [13:38] slicer: Seems like it would be doing the opposite to me, but I'm not a ucf expert. [13:38] persia: I fully agree. [13:39] persia: There's another issue. The server package was originally named mumble-server (on my part), which I renamed to murmur as that's what the server program is actually called. However, I've been informed that there is a package in debian called 'murmur' (but it's not in ubuntu yet). I assume the correct thing is to switch back to mumble-server? [13:41] slicer: Yes. Debian package namespace trumps Ubuntu package namespace except under special circumstances. [13:42] persia: *Nod*. Next question then. At the moment, logfiles are in /var/log/murmur/murmur.log, database in /var/lib/murmur etc. Is it correct to rename that to /var/log/mumble/murmur.log, /var/lib/mumble/murmur.sql etc? It seems a bit counterintuitive to me, but then again, policy often is :) [13:42] I guess it's ok to unsubscribe u-u-s if a report needs more work? [13:43] pochu: Yes. Subscribe yourself. Unsubscribe U-U-S. The current process is documented at https://wiki.ubuntu.com/MOTU/Sponsorship/SponsorsQueue [13:46] * pochu reads it [14:02] * persia declares the use of automake to install python packages aberrant. [14:04] Er, yeah. Ick. [14:07] Did anyone have any opinions on the directory naming issue? [14:08] persia: Even for Python extension packages? [14:09] minghua: The source of the package that caused my complaint consists of some images, some XML, two python scripts, autom4te fun, and GNU templates. [14:10] persia: Yeah, I suppose that's pretty unnecessary. [14:10] While having globals.py.in might have some benefits, I somehow think distutils would be more well suited. [14:10] * minghua still wants to learn proper packaging of python extension that uses autotools, though. [14:11] minghua: I'll let you know if I come across such a package. This wouldn't be a good example. [14:13] persia: :-) Thanks! [14:13] persia: Although I think I'll probably have to ask on debian-python list eventually. [14:13] morning [14:14] My package is kind of a special case. [14:14] minghua: Why not ask them now? I've heard they are freindly and helpful people. [14:14] persia: Have higher prority things on TODO list, mostly. [14:15] Ah. That's certainly understandable :) [14:15] I shouldn't be taking more packages anyway. I can't even give enough love to the ones I currently maintain. [14:16] * persia advocates collaborative maintenance === ember_ is now known as ember [14:35] ember: Re: #176007: why force 3.2? Will it FTBFS with a lower version? === Amaranth_ is now known as Amaranth [15:03] persia: maybe because of jwendell's comment, but I don't think that's reasonably. === bigon` is now known as bigon [15:18] hi folks [15:38] persia: I'm going to package vinagre in Debian, although let's upload ember's work to Hardy as it will need to be NEWed in Debian. === \sh_away is now known as \sh [15:46] * jonnymind is away: Sono occupato [15:47] Thank you for the information. [15:48] <\sh> moins [15:48] !away jonnymind [15:48] Sorry, I don't know anything about away jonnymind - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi [15:48] !away > jonnymind [16:02] Hi \sh.... alogg package at the end was a sync https://bugs.edge.launchpad.net/ubuntu/+source/alogg/+bug/182146 [16:02] Launchpad bug 182146 in alogg "Please sync alogg 1.3.7-1 (universe) from Debian unstable (main)" [Wishlist,Confirmed] [16:02] :) [16:04] <\sh> Hattory: I thought so :) [16:06] :D \sh Could i make a sync for mixmaster too? you are always the last uploader :D [16:07] <\sh> Hattory: do what you want :) flatrate merging...:) [16:08] yo, dudes [16:09] <\sh> preparing wine 0.9.53 [16:10] hello there ;) [16:11] someone can close my bug #181416 ? [16:11] Launchpad bug 181416 in wordpress "SQL injection vulnerability in wp-includes/query.php in WordPress CVE-2007-6318" [Undecided,Confirmed] https://launchpad.net/bugs/181416 [16:11] <\sh> emgent: is it fixed in ubuntu? [16:11] in hardy yes. [16:11] affected only gutsy and feisty [16:12] <\sh> emgent: so it's not fixed :) [16:12] patch avaiable (attached on bug) [16:12] \sh, i'm searching sponsor to commit :P [16:13] <\sh> emgent: well, this is security team work :) jdstrand or keescook are deeling with it :) [16:14] ok thanks \sh [16:14] <\sh> emgent: I see you subscribed motu swat and ust to the bug..so everything goes the right way :) [16:14] ;) [16:37] will hardy packages still get autosynced from debian at some point or is it on sync request only at the moment? (i've been out of the loop for too long, i forget how it works) [16:38] AndyP: we are past DebianImportFreeze, so only if you request them. [16:38] <\sh> AndyP: sync requs are required [16:38] Yeah. My first Pony. Thanks Laserjock (to bad he's not actually on to get the thanks) [16:38] \sh: I beat you ;) [16:38] woo, pony! [16:39] <\sh> pochu: hehe [16:39] pochu: \sh: thanks, i'll get them filed :) [16:39] minghua: Debian Python Modules Team exists precisely to help people like you who don't have time for dedicated maintenance (reading the scrollback). [16:39] <\sh> pochu: I was in the gym..and skyping on the other computer...so I'm a bit slow :) [16:40] ScottK: and a no-pony-award for StevenK :) [16:41] There's no such thing as bad publicity. [16:42] <\sh> hmmm? [16:43] unless you work for the gov't. [16:43] then just about all publicity is bad. [16:43] Well, there is that. [16:44] <\sh> crimsun: what happened...I read about your leave from the council [16:44] \sh: I don't have time to keep up with Ubuntu development anymore. [16:44] <\sh> crimsun: new jobs? :) [16:45] \sh: yeah [16:45] <\sh> crimsun: well, bad for motu and multimedia but good for you :) [16:45] I could say that I now work for Microsoft, but that would be wrong. [16:45] Yes. Working for Microsoft® would be wrong. ;-) [16:45] <\sh> crimsun: lol [16:46] <\sh> crimsun: but would give a lot of money .) [16:57] that's one of my sync requests done... the other one would be for a package which isn't even in ubuntu yet so i'm guessing filing that sync request would be futile, right? :) [16:58] AndyP: if it's in Debian but not in Ubuntu and you want the package in Ubuntu, then you need to request a sync. [16:59] pochu: oh ok, that's good, i assumed new packages wouldn't be allowed at this point [16:59] Until FeatureFreeze they are, and later if there's a good reason and no risk of regression (e.g. new packages) maybe [17:00] great, thanks [17:07] AndyP: You're working towards becoming a MOTU, right? [17:09] ScottK: i was last summer, but my priorities got changed when my final year at university began (++busy) so i don't think i could put in enough time to justify it really [17:09] OK. [17:10] Any MOTU hopefuls out there needing a small learning experience? [17:11] ScottK: Is it short work? [17:11] slytherin: Should be. [17:11] ScottK: Tell me, if I find enough time before I feel sleep, I will do it [17:12] OK [17:12]