[00:34] Heya gang [00:34] hi bddebian [00:34] hey bddebian [00:35] Hello j1mc, protonchris === Czessi is now known as Czessi_ [00:57] ... === Czessi_ is now known as Czessi [01:00] imbrandon: Hello! [01:00] Heya imbrandon, RAOF [01:00] now look what you've done [01:00] * bddebian gives ajmitch a hug [01:00] * ajmitch leaves [01:00] :'-( [01:01] heya RAOF bddebian [01:02] ajmitch! [01:03] Hobbsee: ? [01:03] ajmitch: hello. [01:04] hi === asantoni_ is now known as asantoni === jescis_ is now known as jescis === santiago-pgsql is now known as santiago-ve === superm1 is now known as Daviey_ === Daviey_ is now known as superm1 [02:41] I have a packaging question that might be able to be answered here. :) [02:41] I have a PPA and somebody filed a bug against me asking me to include a changelog so he can see the changes made in Update Manager. [02:41] I said that I *do* include a changelog and that as far as I knew there was no way to make the changes appear in Update Manager. [02:42] I would *love* to be wrong. :) [02:43] nhaines: PPA questions should be addressed to #launchpad [02:44] ScottK2: it's not really a PPA question once parsed [02:44] ScottK2: I was thinking in a more generic repository sense. [02:44] ScottK2: it's an update-manager question and the short answer is changelogs will only be displayed for official Ubuntu packages [02:44] with changelog entries on changelogs.ubuntu.com [02:44] jdong: If it's for an upload to a PPA, it's nothing to do with Ubuntu [02:44] nhaines: ^^ [02:45] jdong: I know about changelogs.ubuntu.com. I hadn't yet gone as far as to peek at update-manager.py but was hoping there was some other facility for it. :) [02:45] Okay, well, short answer is good. Is there a long answer as well? [02:50] Okay, mucho thanks for the answer. At least that's a starting point. I'll take a look at update-manager's code and take it up in #launchpad. [02:55] \sh_away: Recalling your interest in Octave, I mention Debian Bug 432375 (since it's fixed in a later version of the package than we have). [02:55] Debian bug 432375 in octave2.1-forge "octave2.1-forge: FTBFS: /usr/bin/ld: cannot find -lgfortranbegin" [Serious,Fixed] http://bugs.debian.org/432375 [03:13] Okay, so on the topic of Universe, I'm the packager for the Pyroom project, and we have a nice, stable 0.2 release planned that's only waiting on translations now. [03:14] It's our understanding that there's no way to get it into Universe for hardy, so we have intrepid in mind. [03:14] Question is: once it's been accepted, how are bugfix updates maintained? We find a MOTU to sponsor? [03:18] nhaines: Yes. [03:19] nhaines: You start with REVU to get your package into Ubuntu and then if there are updates we have a sponsorship process. [03:19] !revu | nhaines [03:19] nhaines: 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 === anthony is now known as tonyyarusso [03:20] nhaines: https://wiki.ubuntu.com/SponsorshipProcess [03:27] ScottK2: It wasn't clear to me that the Sponsorship presses pertained also to bugfix updates to packages that have gone throught the REVU process. Thanks! [03:27] nhaines: Yes. [03:28] REVU is new packages and then regular sponsorship process for updates after that. [03:29] Okay then, time to polish up my packaging skills, and then I'll be all set for intrepid! :D [03:52] ok, so I got sbuild working, but it doesn't seem to cache the build dependencies it downloads. Is there a way to get it to do that? [03:52] I didn't see anything obvious in the man page [03:53] LaserJock: You can set a local mirror, or bind-mount your apt-cache directory. [03:56] ok, so I need to figure out how to bind-mount in schroot === kitterma is now known as ScottK2 [06:07] good morning [06:17] imbrandon: so do you know what's happened to qa.ubuntuwire.com/weatherreport? [06:19] Heya all [06:19] slangasek: a bit of lack of planning , subst .com with .org for now [06:19] * imbrandon dident get the dns updated in time [06:20] imbrandon: hrm? qa.ubuntuwire.{com,org}/weatherreport both 404 for me. [06:20] hrm ok /me looks [06:20] imbrandon: did ogasawara not manage to get in touch with you about this? [06:22] probably not, i've been avoiding irc [06:24] hrm looks like it should be working, i might have to prod Fujitsu when he is arround, he has been running the show moreso than me lately [06:25] hrm i could setup some nagios monitoring .... *thinks* [06:26] oh, ok, perhaps Fujitsu is who she talked to then [06:26] yea i just got the inital ball rolling per say, the rest of the team has really taken over most aspects of it the last 2 months [06:26] while i took a "break" :) [06:27] i just now crawled back on irc tonight with a little proding from laserjock and ajmitch :) [06:28] heh, ok :) [06:28] yours was the only name I knew to associate with the domain, but I assume ogasawara knows better since she must've been coordinating all this with someone in the first place [06:29] slangasek: ahh yea the whole "team" officaly is http://people.ubuntuwire.com/~uwsa/ , but there are others than help tremendously too [06:29] but anyone on that page should have garenteed admin access over everything afaik [06:30] imbrandon: hi! [06:30] imbrandon: it has been a while! [06:30] imbrandon: i hear you were sick? are you ok now? [06:31] well initial i was sick ( only the flu ) then when i recovered i took a bit of a break from irc [06:31] i'm still arround and kickin [06:31] * dholbach hugs imbrandon [06:31] heya dholbach [06:32] i never "left" per se, just got away from 24x7 on this distraction :) [06:32] * nxvl HUGS imbrandon too [06:32] hehe [06:32] email and jabber always work though :) [06:32] dholbach: btw, why did you declined Bug #162167 for hardy? [06:32] Launchpad bug 162167 in mysql-dfsg-5.0 "mySQL password asks only once" [Wishlist,Confirmed] https://launchpad.net/bugs/162167 [06:32] (just asking) [06:33] nxvl: the development release is the default target [06:33] nxvl: so there's no need to nominate for hardy [06:33] slangasek / dholbach : wow , so i guess i missed a bit-o-dramma from iwj ( re: dpkg ) [06:33] it was just "house keeping", not a release decision [06:34] nxvl: does that make sense? [06:34] dholbach: well, actually that bug is somehoe critical, due it can make that a user which makes a mistake won't be able to use his/her mysql [06:34] somehow [06:34] nxvl: you don't need to nominate for the current development release [06:34] nxvl: sure you can easily reset the password with mysqladmin [06:35] but it is a bug, but not "critical" imho [06:35] nxvl: "hardy" is the default for all bugs that are open right now [06:35] dholbach: but we use release-targeting to track bugs that are release critical... [06:35] dholbach: yes, it make sense for me, i also thought it would be for ibex, BUT nijaba wanted it for hardy as you can se on https://bugs.edge.launchpad.net/ubuntu/+source/mysql-dfsg-5.0/+bug/162167/comments/7 [06:35] Launchpad bug 162167 in mysql-dfsg-5.0 "mySQL password asks only once" [Wishlist,Confirmed] [06:35] slangasek: aren't they milestoned? [06:35] dholbach: but i'm agree with you, just asking why's [06:36] dholbach: bugs that are nominated and accepted (or not declined) for hardy get on the release team radar [06:36] slangasek: OK [06:36] imbrandon: thats why i added "somehow" [06:36] milestoned bugs do as well. But other bugs do not, regardless of bug priority [06:36] I'm happy for it to be on the radar - it was my misunderstanding then [06:36] excusez-moi [06:37] dholbach: the one how will actually one or other way discuss it and defend the patch would be nijaba as he ask me to fix it on yesterday server team meeting [06:37] ok [06:37] :D [06:37] i just did my work === jescis_ is now known as jescis [06:41] dholbach: btw, you always woke up really early, didn't you? [06:42] nxvl: yes, my girlfriend had to get up early today and I thought "if I go back to sleep now it'll be 12 when I wake up again" :) [06:42] heh [06:43] wich time is at berlin? 7 am? [06:43] 7:43 now [06:43] I had a lousy night thought... somebody in the house had some kind of party last night - at 3 I decided to stop their party [06:44] s/thought/though [06:45] *yawn* [06:45] mm just 6 hour difference [06:50] hiya dholbach! [06:50] hi nixternal [06:54] slangasek: try http://qa-2.ubuntuwire.com/weatherreport ( redirect comming soon ) [06:57] imbrandon: ah, that looks a bit better, thanks :) [07:01] holy smokes, it is imbrandon [07:02] heya nix [07:04] wasabi homeskillet? [07:06] imbrandon: How's WoW going? :-P [07:06] lvl 38 [07:06] :) [07:06] Way cool. [07:07] got my wife playing, now she plays more than me [07:07] lol [07:07] Haha [07:07] So she's a 60? :-P [07:07] heh nah, like 46 or 45 [07:08] been running though SM alot [07:08] cept my debian install on my lappy broke yesterday [07:08] so no wow for me untill i fix it [07:08] * StevenK took 2 40s through ZF last night [07:10] you should transfer to my server [07:10] and join [07:10] PvE [07:10] My friends on Dath would kill me :-) [07:11] like 80% of the original guild i was in broke off and made ironic a few days ago [07:12] and the GM is the guy that i know in RL ( at work ) that got me playing , lol [07:12] Whoa. Bet that was fun [07:12] funny thing is after like 4 days we were higer on wowjitsu rankings than the old guild by like 10 slots [07:13] imbrandon: is ubuntuwire already up? [07:13] nxvl: mostly , still a few kinks to work out [07:13] imbrandon: but qa already work? [07:14] yes [07:14] wooohooooo [07:14] i missed it! [07:19] * imbrandon yawns [07:43] <_ruben> any thoughts on performing module-assistant stuff in a pbuilder environment other than pbuilder --login and go from there? i'd prefer to issue commands and have the resulting package(s) end up in the usual results dir === thekorn_ is now known as thekorn === \sh_away is now known as \sh === gary4gar is now known as cool [08:11] <\sh> moins [08:32] good morning folks :) [08:47] <_ruben> morning [08:50] <_ruben> googling for pbuilder + module-assistant doesnt yield much useful :-/ .. guess i'll have to stick with the pbuilder login approach for now [08:53] _ruben: That's likely the best approach, as module-assistant has it's own special places to store things. You might create a simple wrapper around pbuilder to login, install & configure the module, copy the results to the bind-mount, and clean up. [08:53] <_ruben> persia: hmm .. would have to look into that .. any starting points for info on automating such a process? [08:54] <_ruben> am rather new to the pbuilder thing [08:55] _ruben: I don't use pbuilder, but I presume that you can pass a script to be executed when calling pbuilder-login. So long as this script exists in the master tarball, you should be all set. [08:55] <_ruben> persia: thanks [08:56] <_ruben> --execute [08:56] <_ruben> Execute a script or command inside the chroot, in a similar manner to --login [08:56] <_ruben> The file specified in the command-line argument will be copied into the chroot, and invoked. [08:56] <_ruben> The remaining arguments are passed on to the script. [08:56] That would be the one :) [08:56] <_ruben> guess i should've looked at the manpage earlier ;) [08:56] * _ruben slaps self [08:57] Given the special behaviour of copying the script before executing, you don't even need to mangle the clean chroot tarball. [08:57] <_ruben> indeed [08:57] * _ruben is becoming more fond of ubuntu by the day ;) [09:41] <_ruben> hrm .. is there an option similar to 'bash -x' but then for 'make' ? i'd expect it to exist, cant find it tho [09:44] _ruben: What are you trying to do? The answer may be yes, but the bash manpage doesn't give me enough information about -x to be sure. [09:44] <\sh> -x is debugging output...more like a trace [09:45] <\sh> make has -d and --debug=[flags], man make helps [09:45] <\sh> persia: set -x ;) [09:46] Ah. I typically use -d or -p, depending on what is being traced. -p indicates all the predicates to determine expected program flow, and -d is extra-noisy. [09:49] <_ruben> im looking a trace of within the makefile .. the -d option for make only shows me debugging up to the point where it starts using the makefile [09:50] <_ruben> i have 2 source trees, one full, one trimmed down .. one builds fine, the other doesnt .. i dont see any obvious references to missing parts in the trimmed down tree .. so im curious why the makefile ends up being processed differently [09:50] <_ruben> for which in a bash script i'd use -x [09:52] <\sh> _ruben: man make...--debug option...--debug=im is eventually what you want..I'm not sure [09:52] <_ruben> \sh: tried that, doesnt show anything from within the makefile [09:52] _ruben: Likely the tests are different. Each make stanza not listed explicitly as a dependency of .PHONY is an implicit test for the existence of the file in the local directory. In a dirty tree, this can result in non-execution of some stanzas. [09:53] <_ruben> persia: and thats exactly what im trying to debug/find out [09:53] _ruben: And the build log doesn't show any error? [09:54] <_ruben> persia: running make manually, so no build log afaik [09:54] _ruben: run under script :) [09:55] <_ruben> persia: if only i knew what you meant by that [09:56] _ruben: `aptitude install bsdutils; script; $(initiate build); exit; $(PAGER) typescript` [10:00] <_ruben> ah .. kinda like running it through tee .. wont be of much use .. thought it was a magic trick to generate more logging or something ;) [10:01] <_ruben> shit .. bailed out of my pbuilder .. gotta set things up again now :p [10:06] <_ruben> oh well .. i'll just print out the Makefile .. try to figure out how it flows through it, and hopefully learn my fair share of make stuff from it ;) [10:07] make -p will print out the map of what make is planning, which is typically easier to manually trace than the raw makefile. [10:14] how can i tell aptitude to update just one single archive? [10:16] tbf: You can't easily. Why wouldn't you want to update the cache of the others? [10:21] persia: 'cause my internet link is quite slow right now... or modified checks not working for hardy's main repos. [10:22] persia: well, but resolved the issue causing me to call "aptitude update" frequently.... [10:22] persia: so thanks for help - and nevermind :-D [10:23] tbf: Sorry to not have a better answer :( If you're trolling in the future, you can just download the Packages and Sources files from the archive directly, and replace it locally. aptitude can't do this, but it can use the results of you doing it manually. [10:24] persia: indeed. good idea. thanks. [10:25] persia: well, and no indend to troll. just wondered my aptitude didn't offer a certain package for update... [10:25] persia: i knew it was updated in the package archive... [10:26] persia: after grepping the relevant files in /var/lib/apt/lists/, i realized that apt already knew about the new package... [10:26] persia: so i moved my ass into aptitude just to get reminded that i temporarly removed the package [10:26] persia: DUH! [10:26] tbf: Sorry. I should have used "poll" rather than "troll". I meant in the sense of fishing for the good bit, rather than seeking human interaction. [10:27] heh [10:27] ah, ok. [10:37] <\sh> perfect now I'm able to test ubuntu mobile stuff [10:52] are there any special measures needed to convice dpkg to install stuff in /etc/dbus/system.d/ ? [10:53] ...the .deb archive contains my file, but appearently aptitude doesn't drop it at /etc/dbus/system.d/ [11:04] interesting, removing the package with "aptitude purge" and then reinstalling it, also dropped the dbus configuration file at its place [11:04] so how to i ask dpkg to __always__ overwrite a certain file at /etc? [11:04] well, or at least ask the user if overwriting is ok? [11:05] that's what it normally does? [11:05] apt, at least [11:06] tbf: --force-confmiss [11:07] slangasek: thanks, googling for that term [11:07] Hobbsee: well, the file was even missing, and aptitude didn't install the package's version [11:07] * tbf reads http://www.debian.org/doc/debian-policy/ap-pkg-conffiles.html now [11:13] ok, debuild/cdbs/whoever automatically added that file to the conffiles section! [11:13] strange. [11:13] is anyone able to view yahoo webcam in kopete4? [11:16] tbf: CDBS does magic. Create an empty (or accurate) debian/package.conffiles if you want it to be less magic. [11:16] IIRC debhelper can do that for you too - any files shipped in /etc should be conffiles so it doesn't need great magic. [11:17] broonie: not sure about stuff in /etc/dbus/system.d/ [11:18] broonie: dbus-activation services cannot gain root privileges, when their file is missing from that folder [11:18] Including that. [11:19] broonie: well, imho treating such files as configuration files is harmful [11:19] broonie: editing those files usually just breaks applications [11:20] Everything in /etc is supposed to be editable by the admin; in the case of the dbus policy files they may want to add additional permissions, for example. [11:20] hmm... maybe dbus is wrong, by placing the files there [11:20] broonie: my file really should says "yes, root is allowed to claim that dbus service name" [11:21] broonie: if root is not allowed to do that, the application will break [11:21] broonie: hmm... maybe i should add a comment to that file [11:22] * broonie has edited things there in the past to say stuff like "...and group X is also allowed to talk to it", FWIW [11:33] siretart: Yes, funny indeed. [11:34] siretart: I have a long-lost step brother you know. ;) [11:42] RainCT: should I attach new files for gbrainy 0.6.1 ? [11:42] eh 0.61 [11:51] sebner: isn't necessary :) [11:52] RainCT: fine :) [11:53] DktrKranz2: anything new about tapiir? [12:19] hi folks [12:19] hio siretart [12:19] ho sistpoty|work [12:19] hi sebner [12:20] heya sistpoty|work [12:20] hi RainCT [12:24] <\sh> hey sistpoty|work [12:24] <\sh> sistpoty|work: thx for the +1 [12:25] * sebner hugs sistpoty|work for ACKing and \sh for making it possible :) [12:25] <\sh> sebner: we wait for debian now :) [12:25] <\sh> sistpoty|work: if you be so kind, please ack bug #204016 ;) [12:25] Launchpad bug 204016 in zend-framework "[FFe] zend-framework 1.5.0" [Undecided,New] https://launchpad.net/bugs/204016 [12:26] <\sh> that will give hardy more love from zend ;) [12:26] hi \sh [12:26] \sh: how long ca? [12:26] <\sh> sebner: today, tomorrow...who knows...but it will hopefully go before hardy will be released ;) [12:26] it's already tagged as release in svn, so I assume that it (probably?) is getting uploaded already [12:27] \sh: xD xD xD [12:27] <\sh> sistpoty|work: well, I checked fteqcc from debian unstable, and they were bumping the version of it, so they are not using the provided svn export of nexuiz [12:28] sistpoty|work: it's not yet in incoming [12:33] \sh: but I'm often asking me why we wait for a debian release. Why not packaging ourselfs (so no need to hope that they release it soon) [12:33] <\sh> sebner: anyways...I have all packages handy..so we can always upload directly [12:33] <\sh> sebner: check the numbers of maintainers debian has, and compare them with voluntary contributors of ubuntu [12:34] \sh: true, but for very important stuff .... as you did now with nexuiz [12:34] <\sh> sebner: so, we are less in numbers, and we want to decrease the divergence of ubuntu towards debian, especially inside universe/multiverse [12:35] \sh: Yeah I fully understand that but sid is a rolling release and ubuntu not [12:36] <\sh> sebner: so, ubuntu devel releases are still rolling, too :) [12:37] <\sh> sebner: did you see one of sabdfls presentations? regarding ubuntu development cycles and the dependency towards debian sid? [12:37] \sh: unfortunately not. And yes I know that ubuntu really depends on debian [12:41] sebner: Also, it can be difficult to share patches if the md5sums for the Debian and Ubuntu releases are not the same. As there is no infrastructure for Debian to sync from Ubuntu, Debian goes first (and also, nexiuz is actuively being packaged in Debian at the current time: racing without touching base with the Debian person is often duplicated work) [12:41] aloha afflux [12:42] huh [12:42] ah, hih sebner :) [12:42] persia: yeah, I understand. though debian/ubuntu team packaged it IIRC [12:42] afflux: ^^ [12:42] sebner: Ah. I'm still catching up on email, so that may well be the case :) [12:47] persia: :) btw. worked on my first bugfix: replace icedtea-java7 references with openjdk-6 references \o/ [12:48] sebner: Excellent. Nice job. If you want to look at more merges / reverse-merges, all of http://qa.ubuntuwire.com/bugs/rcbugs/ need to be reviewed/fixed before release. [12:49] persia: merges \o/ \o/ \o/ [12:50] persia: ah stupid question. but I'm also allowed to prepare debdiffs for main and just subscribe core-dev then? [12:51] sebner: Sure. Note that the ubuntu-release team has slightly different rules for freeze exceptions from motu-release, so you have to be more careful about documenting the bug being fixed clearly. [12:51] Also, not core-dev, but ubuntu-main-sponsors. [12:51] persia: ah sry. tur [12:51] *true [12:52] <\sh> sebner: but we brb [12:52] <\sh> grmpf [12:52] <\sh> brb === \sh is now known as \sh_away [13:01] persia: how can I get something removed from it (e.g I worked on the streamtuner merge but in the end we decided to wait until intrepid because it's not worth it) [13:01] hi french1 && sebner. hi folks [13:02] siretart: Hi there. [13:03] sebner: Removed from a sponsors queue? Ask for a sponsor to unsubscribe the team. [13:05] persia: ahh :) [13:05] Hobbsee: he improved? ;) [13:06] siretart: no, but it's the motu council's job to put conditions on it, not mine. I've been told by jono that if we (any of us) feel that the MC is not doing their job in this matter, we should email him, with proof, and he has promised to look into it. [13:06] siretart: and/or to go to the CC> [13:06] siretart: as it is, the policy on ban evasion is supposed to go in front of the motu meeting at the next meeting. [13:07] persia: and how can I mark/let others know that something isn't necessary? [13:07] siretart: i presume the part w.r.t. not doing their job and jono still applies for that. [13:07] Umm. MC doesn't control IRC. IRC Council is the place to determine who is banned. MC does have a general request that Marco not participate in Development until he can get a couple developers to request he be granted permission to participate again. [13:07] sebner: Just ask here. [13:07] pochu: [13:07] ping :) [13:07] persia: i've been told it's not my domain. if you don't think that's the case, you'll really need to take that up with jono - or email the irc mailing list requesting the ban, from the council. [13:08] persia: but, mere people are not to act. [13:08] it must be the councils. [13:08] Not necessary on ubuntuwire; simgear <-- ubuntu doesn't support those platforms (debian fixed a FTBFS on Alpha, HPPA, and S/390) [13:08] Hobbsee: I'll chat with Jono, but won't request a ban unless the new permission to speak is abused. [13:08] err, aren't we all a bit overexagerating here? [13:08] as soren rightly points out, motu is not an anarchy. [13:09] sebner: Oh, for those? Add a comment in the comment field. [13:09] persia: there is a comment field? XD XD XD [13:09] * persia thought there was, unless there was a regression in rcbugs [13:09] persia: no there is [13:09] persia: but my eyes are not the best ^^ [13:10] siretart: Likely only being extra pedantic... [13:10] siretart: what makes you say that? [13:15] arg, can someone link me to the help page for ppa's can seem to find it... sigh [13:16] jussio1: https://help.launchpad.net/PPAQuickStart [13:16] Hobbsee: because I didn't intend to provoke a discussion about responsibilities of decisions, and certainly not discuss responsibilities of powers of our institutions [13:17] Iulian: thnk you :) [13:17] siretart: true. i was also using some of hte information that i'd gained on the recent conference call with jono, which may be of use to other people :) [13:18] which ended up being relevant to the previous comments [13:18] How the heck did he get unbanned? [13:19] persia: 1 done. More people should work on the list because 1) more fixes for ubuntu 2) more users could join 5-a-day ^^ [13:19] ScottK2: i did it. [13:19] Why? [13:19] ScottK2: wasn't my domain to ban in the first place. see the first few lines. [13:20] * ScottK2 disagrees. [13:20] persia: What possible benifit is there to not having the ban. [13:21] Hobbsee: IRC ops aren't allowed to ban people? [13:21] ScottK2: in the eyes of various developers, not if they're acting on their own, or not if the respective councils haven't agreed to. [13:21] unless it's spam, etc, [13:21] ScottK2: I'm guessing that they are deeming it a conflict of interest, althoguh I disagree. [13:21] ScottK2: that being said, anyone can get ops in here... [13:22] ScottK: Shorter ban list on freenode? [13:22] persia: Fewer developers is also I likely benifit [13:22] ScottK: Sure. I don't personally care if there is a ban or not, so long as Marco is not active in this channel. [13:22] Further, I don't presume to speak regarding IRC policy. [13:22] persia: we're nowhere near the limit for here. #ubuntu and #ubuntu-offtopic, however.... [13:23] We want to remove python-xml before release. Also libxml? [13:23] persia: you'll now be relying on his own restrant, or a MC council decision for that. [13:23] sebner: No. Just python-xml [13:23] persia: which is probably the way it should ahve been originally [13:23] ScottK: k, thx [13:23] How much evidence do we need that his own restraint is non-existant === \sh_away is now known as \sh [13:25] ScottK2: then you collect evidence, and go to jono/the CC that the MC isn't doing it's job. [13:25] persia: I gather then that kmos is still not fired, just being requested. [13:25] ScottK2: if they didn't act. [13:25] er, don't act, in a reasonable form of time. [13:25] Hobbsee: I'm confused? There is an MC decision that Marco should not participate in development, and ask ScottK points out, he has not demonstrated restraint. [13:25] We're way past that [13:25] s/ask/as/ [13:25] <\sh> now we have divergence [13:25] persia: So we are undoing the one thing that's actually been done to restrain him. [13:25] <\sh> really [13:25] <\sh> Source: flashplugin-nonfree-pulse [13:25] <\sh> which is our libflashsupport ;) [13:26] ScottK: Well, one of the things, but yes, and I'm not attempting to defend that removal. [13:26] persia: I do not have the spare cycles to deal with Kmos or a do nothing MC. [13:26] * Hobbsee emails the ML [13:26] ScottK: Umm. I agree with you. I don't wish to see Kmos back. [13:27] <\sh> hmmm? what's wrong again with kmos? [13:27] Then fix it. You're management. I'm not. === asantoni is now known as asantoni_mixxx [13:27] \sh: The IRC ban has been removed. [13:28] <\sh> ScottK2: so he's back in #u-d... [13:28] <\sh> I see [13:28] Dunno. Just know the possibility exists. [13:28] The issue is more that MC doesn't control IRC. Once I understand why the ban removal was requested, I'll see what needs doing to have it either reinstated or someone to assure me that the lack of a ban will not be a problem. [13:28] I don't see what possible reason we would have for not wanting him banned. [13:28] <\sh> 14:27 -!- Kmos [n=gothicx@unaffiliated/kmos] [13:28] <\sh> 14:27 -!- ircname : Marco Rodrigues [13:28] <\sh> 14:27 -!- channels : #ubuntu-devel [13:28] The rest is just bureacracy [13:28] \sh: it was a quiet for a long time. [13:29] \sh: btw, wb [13:29] <\sh> TBH, we can't force kmos to not use freenode services, until someone from canonical buys the network ,->, but I would be happy, if we can ignore him only, that's it...all technical solutions will not help us to help him with his social problems [13:30] * Hobbsee shrugs. it's out of my hands now :) [13:31] \sh: I'm well beyond worrying about his social problems as long as he has them elsewhere. [13:31] * \sh hopes that this is not bringing back any stress into this community :( [13:32] <\sh> ScottK2: that's what I mean, we can't k-line him...the only way is to ignore [13:32] \sh: As long as he can't speak. I don't care if he's in channel. [13:34] It appears to me that the best way to get an IRC ban removed is to make a new LP account and go against what the MC asks. [13:35] Well, LP accounts and IRC bans aren't related, and any attempts at direct contribution from Marco will not currently be well received. [13:36] persia: Just look at action and reaction. You may separate those in your head, but that's the net effect. [13:36] mail sent. [13:36] ScottK: These are coincidence, but I can see how they may be linked. [13:39] I agree that the timing is coincidental, but what has happened has happened [13:40] <\sh> whooza....nexuiz hit debian incoming [13:40] ScottK2: the LP account was unrelated. i've been asked to help figure ways to deal with the ban evasion, too. i presume you are as well [13:41] Hobbsee: They are separate issues from an Ubuntu management perspective, but the net result is the guy evades the ban and he gets his IRC restored. [13:42] Hobbsee: No. I haven't been asked. [13:42] ScottK2: the two were coincidental. [13:42] Yet what happened happened. [13:43] sure, but you're putting words into people's mouths, which happen to be accurate, if you insist there's a link. [13:43] er, which happen *not* to be accurate. [13:43] which is dangerous [13:44] I don't mean to imply that anything about the timing is intentional. [13:45] <\sh> ScottK2: you can always overcome an irc channel ban... [13:46] \sh: Agreed, but that was actually working. Things have been so much nicer here since. [13:46] <\sh> if you don#t hang onto your nick, you just forget about it choose a new one, reg it, push no realname in it...etc. [13:46] I think the whole atmosphere of MOTU has improved. [13:46] Agreed. [13:46] <\sh> ScottK2: for sure... [13:46] <\sh> ScottK2: but I don't think kmos would leave his nickname behind, just because of ubuntu :) [13:47] <\sh> but there was a decision, and this decision is now at stake [13:47] ScottK2: i think it would be wrong to assume that the MC would not have seen the change since he's left, and not work in the best interest of MOTU to keep it more productive. === DktrKran12 is now known as DktrKranz2 [13:48] uhm, lintian calls writing GTK instead of GTK+ a spelling-error [13:48] I wonder if it does the same with QT instead of Qt :P [13:48] <\sh> apachelogger: if not, send diff ;) [13:49] <\sh> but as we have motu release here... [13:50] <\sh> ScottK2: Hobbsee sistpoty|work : do we need for this patch (bug #198861) an FFe? [13:51] <\sh> bah...ubuto is dead ;) [13:51] <\sh> and can't parse data [13:51] <\sh> bug #198861 [13:51] Launchpad bug 198861 in claws-mail "There's no flag to enable hildon interface when building for lpia" [Wishlist,Confirmed] https://launchpad.net/bugs/198861 [13:51] <\sh> ah now [13:52] Hobbsee: I'm really not very knowledgeable about all the different councils. Nor am I particularly interested in the bureacracy and frictions between the various bits that have removed what I consider something very helpful. [13:52] \sh: I'd say not. [13:53] <\sh> ScottK2: well, I ported the patch now to 3.3.1 but I'm not sure how I could test it without the hardware (the changes are on input side) ... even with the lpia environment running ... this is not a thing we can test without the hardware [13:53] \sh: don't think so [13:53] \sh: Is there any regression risk with the patch? [13:54] <\sh> ScottK2: well, it changes some behaviour of upstream it looks like... [13:54] <\sh> ScottK2: that's why I pushed lool and adilson for an FFe...because I don't really know the difference in this maemo stuff and touchpads [13:54] \sh: If you can test that there's not a regression, then I think actually working would be considered a bonus. [13:54] <\sh> s/pads/screens/ [13:55] <\sh> ScottK2: well, i386,amd64 are running and compiling..no prob...but I can't test on lpia...but ah come on, I'll try to start it in my lpia environment and check its running [13:55] * \sh needs a smoke and has meeting...bbl [13:57] Heya gang [13:58] heya bddebian. [13:58] Hi ScottK2 [14:00] ahoi bddebian [14:00] Hello sebner [14:04] hi bddebian [14:06] Heya sistpoty|work [14:27] persia: I should join 10-a-day ;) [14:28] sebner: Don't bother counting. I've had bugs that took me years to fix, and hours where I could process 100. [14:28] persia!! [14:28] bdfreese!!! [14:29] <\sh> re [14:29] persia: no I just like it. It's funny. though after >5 sync requests it's gettin boring ^^ [14:29] wb \sh [14:29] Heya \sh [14:29] ScottK2: so now persia gets the blame. [14:29] persia: Did you see that I got a working attal uploaded? [14:29] <\sh> hey bddebian :) [14:29] bddebian: I saw the upload. I didn't know it worked. Congrats! [14:30] <\sh> well, 5-bugs-a-day is something for new contributors, I see it as a challenge...but funny to see, that pitti e.g. is participating ;) [14:32] <\sh> Hobbsee: /window 13 [14:32] <\sh> grmpf [14:32] <\sh> hehe [14:32] heh [14:32] fail. [14:32] <\sh> what I wanted to say... [14:33] <\sh> Hobbsee: please review bug #204016 (I want to have it from my todo list) and [14:33] Launchpad bug 204016 in zend-framework "[FFe] zend-framework 1.5.0" [Undecided,New] https://launchpad.net/bugs/204016 [14:34] <\sh> and it wasn't window 13 but 14... [14:38] Are bad copyright informations a reason for syncing a new version? [14:39] sebner: sure why not? [14:39] slytherin: that's why I asked ;) [14:39] sebner: Depends on how bad. In most cases, yes, as correct copyright attribution is required for most of the licenses we use, and otherwise it becomes undistributable. [14:39] persia: in debian it's marked as "Important" [14:42] sebner: That is typically not enough to make it undistributable. See http://www.debian.org/Bugs/Developer#severities. I'd recommend first closing all the critical bugs, then grave, and going down the list that way. [14:43] persia: hmm. ^^ I choose bugs by hazard ^^ [14:43] persia: FYI ... I will be able to find enough time tomorrow and day after that. I am planning to fix some FTBFS and also planning to update bluez-gnome. Please let me know if you think there is anything more important pending. [14:44] slytherin: FTBFS, rcbugs, and NBS are the most important, from my point of view. Updates should be avoided unless there is some critical regression or bugfix that we need. [14:45] persia: it is bug fix release only. But now sure if corresponding bugs have been logged in LP [14:46] slytherin: bugfix updates are good. The importance of such an update is strongly related to the importance of the fixed bugs. [14:47] persia: Ok. Let's talk in my night. Can you please tell me your timezone? [14:48] UTC+9 [14:49] persia: Cool. Mine is +5:30. Not much difference. :-) [14:49] persia: Are you located in Australia? [14:49] persia: Bedtime :P . to make you happy I'll take the grave ones from now on :) [14:49] slytherin: Tokyo [14:49] geser: ghc6 finally made it on sparc, I guess we'll only need some give-backs now for the libs :) [14:50] sebner: If you can close all the grave ones, Hardy will be much improved :) [14:50] persia: I only against all grave ones? ^^ [14:50] *alone [14:52] sebner: Don't be alone then. There are 207 other people in the channel: I suspect if you were willing to explain the process, quite a few would be happy to help. [14:53] persia: don't steal me the fun :P I have 1 month left :D === dholbach_ is now known as dholbach [14:55] sebner: There's all the Severe bugs too, don't forget. And if you run out of those, there's all of the really-fix-it bugs as well... [14:56] persia: ^^ yeah I know. It was just a joke. But also mind to search people for clearing u-u-s :P [14:57] oh noooo! more merges from sebner :) [14:57] DktrKranz2: hrhr [14:57] DktrKranz2: How many did I today so far? [14:58] dunno, but queue is +4 long since last time, and there are yours :) [14:58] well [14:58] I should be ~10 now ^^ [14:58] persia: I love ubuntuwire :) thx for the hint [14:58] * DktrKranz2 hides [14:59] DktrKranz2: yeah 99% are syncs. I suppose easy ones ^^ [15:00] sebner: Just remember to document the RC bug in the sync request bug description: it makes it a lot easier for the sponsor. [15:01] persia: damn. I have to edit 10 bugs now ^^ [15:01] persia: But it doesn't matter. DktrKranz2 is willing to approve all :P [15:03] sebner: It does matter, because the archive admin needs to approve it, and the release team will want the documentation for review if there are any complications. [15:03] * sebner seems to suck at making jokes :\ [15:08] sistpoty|work: good, wasn't there already a giveback of haskell-* on sparc because I've got some emails about build failures on sparc? [15:08] geser: yes, but not all came trough as it seems [15:09] Hobbsee: can you give back packages? if so, please give back haskell-regex-base on sparc, thanks [15:09] geser: I merges haskell-opengl and it built fine on sparc [15:09]