/srv/irclogs.ubuntu.com/2007/11/16/#ubuntu-motu.txt

JimersonGood Evening All.00:43
JimersonI have some questions about sponsorship, I have read through the wiki, and I have some questions if someone is willing to help me.00:45
rick_h_jcastro: you see the video of the new rythmbox plugin? Browse artists is kind of cool00:56
* Hobbsee waves01:06
ajmitchhey Hobbsee01:16
Hobbseehiya ajmitch01:16
ajmitchhow's it going?01:16
Hobbseeexams suck.01:16
Hobbseephysics should die.01:16
Hobbseeapart from that, fine!01:16
ajmitchyay :)01:17
ajmitchhave you finished exams now?01:18
Hobbseehah.  no.01:18
Hobbsee2 more01:18
minghuaHuh.  I hope physics lives fine.01:18
=== tritium_ is now known as tritium
JimersonI have some questions on sponsorship, I have read the wiki's information and would like to talk to someone about it.01:52
Hobbseeshoot :01:52
JimersonYour following me :)01:53
JimersonHobbsee: mind if I pm you?01:53
* Hobbsee is omnipotent :)01:53
HobbseeJimerson: would prefer you to ask in here, then multiple people can answer01:53
* Hobbsee is a bad mentor, tbh.01:53
persiaJimerson: It's generally best to ask any questions in-channel, and not to specific people, so everyone can learn.01:53
eneko_tabwe are trying to relaunch the Ubuntu Home Server project as it seems death01:53
eneko_tabUHS would be analog to the windows home server01:54
* Hobbsee wonders how that fits in with ubuntu server.01:54
StevenKpersia: Your make foo fails!01:54
eneko_tabhowever, we need help specially in the management01:54
JimersonFair enough. I have not really found any information on how to find a sponsor, I am new to this, and am interested in helping, just need a kick in the right direction.01:54
StevenKpersia: make says "The directory exists, so I don't need to do anything"01:54
persiaStevenK: Hrm?  Which part?01:54
HobbseeJimerson: got a bug in particular, or wanting to know in general?01:54
StevenKpersia: The $(MAKE_DIRS) bit01:54
JimersonHobbsee: general.01:55
persiaStevenK: Did you not add $(MAKE_DIRS) as a dependency of .PHONY?01:55
HobbseeJimerson: you usually just make sure the patch is correct, and subscribe ubuntu-universe-sponsors01:55
jdongstupid GPG question: can I have GPG show "info" about an encrypted file or signature (i.e. who signed it, who's it encrypted to, etc)01:55
StevenKpersia: Oh, was I supposed to? :-)01:55
persiaJimerson: You don't need to find a sponsor: the sponsors need to find your patches.  This is done with bug subscriptions.01:55
eneko_tabanyone is experienced managing an open source sw prject?01:55
Hobbseejdong: you can do gpg --validate-sig or something, for the first.01:55
persiaStevenK: Sorry: I was tired last night.  Yes, if you don't want it to block on timestamps :)01:55
Hobbseejdong: i dont think that's right, but it's close enough that the man page should help01:56
Jimersonpersia: where is a good place to get started.01:56
Hobbseeeneko_tab: we're MOTU's.  we manage universe ;)01:56
jdongHobbsee: hmm I'm perusing thru the manpage currently01:56
Hobbseesilly question.01:56
persiaJimerson: What do you seek to accomplish?01:56
Hobbseejdong: gpg --verify01:56
Hobbseei was close :)01:57
Jimersonpersia: to help in any way that I can, does not matter to me what I accomplish, I would just like to give something back wherever it is needed.01:57
jdongHobbsee: ah, ok01:57
Hobbseejdong: no idea on who it's encrypted to.  i've not had to use it.01:57
persiaJimerson: If you want to help MOTU, the best ways are 1) bug triage, 2) patches, and 3) Preparing candidate revisions with the patches to close the bugs.  There's an overview at https://wiki.ubuntu.com/MOTU/Contributing01:58
persiaJimerson: I'd suggest starting with #1, doing #2 when there's an obvious solution, and doing #3 when you've a package where you can close a few of the bugs due to #2.01:59
Jimersonpersia: Thank you for your answers and time.02:00
bddebianHeya gang02:08
HobbseeTheMuso: for u-u-s fun - all of http://tinyurl.com/2nynzm02:45
HobbseeTheMuso: that's a list fo bugs that have patches associated.  the users presumably havent subscribed the sponsorship team.  just if you get bored02:45
Hobbseepersia: ^ bluekuja02:45
persiaHobbsee: Yep.  There's a link there from qa.ubuntuwire.com :)  Part of the issue is that most of those patches aren't debdiffs.  I'd say they aren't appropriate for sponsorship, although they are certainly appropriate for regular MOTU updates (just a different hat).02:46
Hobbseepersia: might be a good thing for new people to do02:47
Hobbseethat way they don't have to write the code themselves, but take the patch and apply it.02:47
bddebianHeya persia, Hobbsee02:47
persiaHobbsee: Absolutely.02:47
Hobbseehi bddebian02:47
persiaHi bddebian02:47
Hobbseebddebian: right, youv'e got a job.02:47
persiabddebian: 1500 patches that need debdiffs & uploads (or just flat rejection) :)02:48
Hobbseeno, not quite that02:48
Hobbseeto write the documentation, and help new people out with applying them.02:48
bddebianHuh?02:48
ajmitchbddebian: hop to it, before you get beaten02:49
* persia suggests that editing https://wiki.ubuntu.com/MOTU/Contributing might be a good way to do that, but thinks most of it is already there02:49
bddebianWhat am I doing?02:50
ajmitcheverything02:50
persiabddebian: You're the new meta-MOTU: you get to make sure everything gets done :)02:50
ajmitchmore specifically, taking patches that aren't on the u-u-s watchlist02:50
bddebianhahaha02:51
ajmitchbddebian: you seem to think that we're joking?02:52
bddebianYou must be since you all know that I suck :)02:52
ajmitchno, this is a way to shut you up & keep you so busy that you can't complain about sucking or being stupid :)02:53
bddebianhah02:54
TheMusoHobbsee: Thanks.03:02
=== _czessi is now known as Czessi
LaserJockman I love merging hugemongous packages :/03:34
bddebianheh03:34
bddebianAs much as I love reviewing crappy ones? :-)03:34
LaserJockrunning grab-merge.sh on gcompris is gonna take almost 400MB03:35
StevenKMmmm, yummy03:35
StevenKLaserJock: Ponies!03:35
=== rob1 is now known as rob
* StevenK works on giving LaserJock a complex some more03:35
Hobbseeyay, ponies!03:36
* LaserJock twitches03:40
bddebianJesus, could we get a few more packages on REVU please?03:53
StevenKSure.03:54
LaserJockI'm sure that could be arranged03:54
* imbrandon uploads 40 more03:55
bddebianThat's just 40 more that will get ignored ;-P03:55
imbrandonmaybe REVU should be wiped at every FF ( e.g. start clean for the next release )03:56
imbrandonatleaste all packages "archived" , thus a new upload will bring them back03:56
Hobbseeimbrandon: that was the plan03:58
Hobbseebut people started uploading stuff for hardy, during gutsy.03:58
imbrandonahh then those people need to have gotten a "too bad" when they asked what happened :)03:59
imbrandonlol03:59
imbrandonbtw hiya *03:59
Hobbseegreetings :)04:00
bddebianwtf: aswvdial_0.1patch2.dsc04:00
imbrandonheh04:01
bddebianWell that was worth wasting my time on04:05
mdomschfor uploads to REVU, do we have to change debian/changelog to use hardy now, or can it remain as gutsy?04:12
bddebianHardy04:12
StevenKmdomsch: If you upload as Gutsy, Soyuz will yell at you.04:13
persiamdomsch: Just to make sure, are you considering an upload of a candidate for hardy, or a candidate for gutsy?04:14
mdomschhardy most likely, though Dell will likely publish the packages for feisty and gutsy too04:14
mdomschfirmware-tools and firmware-addon-dell for flashing BIOS04:14
persiamdomsch: Hmm...  Is there a backporting / update policy for the Dell repos?04:15
imbrandoni would target hardy then -backport it04:15
imbrandonDell has seperate repos? why04:15
* persia tends to agree with imbrandon, but it may depend on Dell policies04:15
persiaimbrandon: Special add-ons which we don't have or want yet.04:16
mdomschwe don't have policies yet, we haven't published debs yet04:16
mdomschbut we do publish rpms for other distros/versions04:16
* bddebian covers his ears04:16
mdomsch:-)04:16
imbrandonmdomsch: assuming your part of the DELL team i would closely follow the Ubuntu policy ( or atleaste have a good reason not to )04:16
mdomschimbrandon, yes, which is why I'm asking and trying to understand04:17
Hobbseemdomsch: this is the problme that you need to sign with the dell key, isnt it?04:17
mdomschI believe no more new packages will be accepted for feisty and gutsy via MOTU04:17
persiamdomsch: I'm generally in favor of using distro releases when feasible, so in this case, I'd suggest an upload to hardy, and performing the backport for the others.04:17
imbrandon:) mdomsch normaly it would be targeted at the current development release, then semi automaticly added to -backports after a but of testing04:17
mdomschyet those are the releases we're shipping now or will soon04:17
Hobbseemdomsch: correct, but you're dell.  so it's probably possible to mangle things.04:18
Hobbseeassuming soyuz doesnt blow up.04:18
imbrandonmdomsch: technicly yes, but new {feisty,gusty}-backports can happen04:18
mdomschahh, -backports - I hadn't seen that04:18
imbrandon:)04:18
Hobbseemdomsch: would the hardy/gutsy/feisty packages be the same?04:18
Hobbseeimbrandon: except that a lot don't use backports, so -updates might be smarter.04:19
mdomschHobbsee, certainly same source; most likely different packages due to different python versions04:19
imbrandonHobbsee: this is for dell, theey can enable -backports if they want :)04:19
* persia votes for -updates with special pleading to the archive-admins04:19
mdomschwhich is fine by me04:19
mdomschimbrandon, Hobbsee, if it's not enabled by default, we haven't enabled it in our factory images04:19
imbrandonmdomsch: will python-central python-support not take care of the versioning diffrences ?04:19
Hobbseeimbrandon: then i dont want to see a repeat of the flashplugin fiasco.04:20
persiaimbrandon: True, but it's "Community Support": do you want backports by default?04:20
mdomschoh, that's right - debs build the .pyc files at install time04:20
imbrandonpersia: personaly since i'm on the backports team it wouldent bother me, but i see your point04:20
mdomschthen the same package will probably work on all04:20
persiamdomsch: Right.  .py is distributed, and .pyc is local.04:20
Hobbseemdomsch: right.  then throw it into hardy, and then get the archive admins to copy it to the other releases.04:20
mdomschpersia, fedora does that different, fwiw04:20
Hobbseeabuse of power, but oh well.04:20
persiamdomsch: So does everyone not debian-derived :)04:21
imbrandonheh yea ubuntu == <304:21
* mdomsch tries to understand and follow the rules before discarding them04:21
imbrandonwell you've come to the correct place :)04:21
Hobbseemdomsch: the rules are "no new packages to released versions, unless they fit !sru, unless there's a damned good reason.  assuming the build system wont curl up in a ball and die"04:21
Hobbseein a nutshell, that's the rule04:22
Hobbseeeasiest way to get something in is to get it into the development version, then get it backported.04:22
Hobbseeor, in special cases as this, copied, so it appears in -updates04:22
imbrandonand persia fwiw i did do a fresh install of gutsy for my step-dad tonight ( converting him from vista w00t ) and multiverse is indeed on04:22
Hobbseedoes the help?04:22
mdomschnow for backports, do I or do I not have to edit debian/changelog to s/hardy/gutsy/ ?04:23
mdomschif it's just a file copy on the archive, I assume no04:23
imbrandonyou dont, its automagic04:23
mdomschcool04:23
Hobbseemdomsch: it would be to gutsy-backports anyway.  </pedant>04:23
imbrandonassuming no source changes are needed etc etc etc04:23
Hobbseei dont think you *can* upload to gutsy anymore, without the build system blowing up.04:24
Hobbseei think it has to be -updates or -backports04:24
imbrandonif source changes are needed then a direct upload to -backports is required and alot of a$$ kissing to the archive team04:24
Hobbseeimbrandon: chocolate accepted.  :)04:24
imbrandonheh04:24
Hobbseeother bribes also accepted.04:24
persiaimbrandon: Thanks for the confirmation.  I think that's broken, but will wait until I'm organised to complain.04:25
Hobbseeimbrandon: just none of multiverse is used by default.04:25
imbrandoncorrect04:25
Hobbseei guess that makes sense - the first step in any ubuntu script is to enable universe, do an update, then install the required codec04:25
imbrandonnothing is used, and i 1000% agree with the way it is04:25
imbrandonHobbsee: right04:25
imbrandonbut we had this "disscussion" the other nigth04:26
imbrandonnight*04:26
Hobbseeah right.  i was probably "studying"04:26
imbrandoni 1000% agree it should be on but nothing installed from it, saves tons of support04:26
Hobbseeheh04:26
* Hobbsee just wants to know how people randomly manage to remove parts of their kernel.04:27
persiaWhereas I believe that due to the questionable nature of some of the contents, there should be a click-through at least.04:27
persiaHobbsee: rm?04:27
StevenKHobbsee: Wielding sudo mv/rm ?04:27
tonyyarussoHobbsee: I dd zeros in the middle of it.04:27
* StevenK high fives persia 04:27
imbrandonpersia: thats easy to fix, if its questionable dont put it in the archive :)04:27
persiaTonio_: That's living dangerously :)04:27
Hobbseehaha04:27
Hobbseeno, they seem to remove the generic kernel package.  and then whine that they have no l-u-m, so their card doesnt work.04:28
Hobbseethe stuff is seeded, it's on installs, it's mandatory to have it for upgrades...yet somehow people still file bugs due to not having it.  *sigh*04:28
imbrandonthey might be manualy installing a -rt or kernel image , e.g. linux-image-2.X.X-rt not the meta package04:29
imbrandonthat woudl do it04:29
Hobbseehm, yeah, could do.04:29
persiaimbrandon: I'll also agree with that, but https://lists.ubuntu.com/archives/motu-council/2007-November/000512.html is authoritative today.04:30
imbrandonsure04:30
LaserJockpersia: authoritative regarding what?04:39
persiaLaserJock: Multiverse inclusion policy04:39
LaserJockpersia: there wasn't much said04:39
persiaLaserJock: To give context, last week imbrandon and I were debating whether multiverse should be configured by default.04:40
LaserJockah04:40
LaserJockI thought mayber we were back to Windows binaries04:41
LaserJock*maybe04:41
bddebianheh04:41
persiaEssentially, imbrandon's position is that it's a support nightmare to explain to each and every user how to enable multiverse, and it's my position that parts of multiverse are possibly inappropriate for some uses.  We're both right, but it doesn't help that there are no restrictions on multiverse inclusion.04:41
persiaLaserJock: Related, but not the current topic of debate.  The policy I cited applies in both cases.04:42
LaserJockwell, kinda04:42
LaserJocksomebody really needs to respond to that thread04:43
LaserJockI don't think anybody knows what it was about04:43
imbrandonwhat thread?04:43
persiaLaserJock: I disagree that the thread needs a response.  Someone needs to define a reasonable goal for multiverse, and promote that set of criteria.04:43
LaserJockimbrandon: https://lists.ubuntu.com/archives/motu-council/2007-November/000498.html04:43
persiaIf approved, the thread can be revisited.04:43
LaserJockpersia: they don't know about it04:44
LaserJockI talked to dholbach04:44
persiaLaserJock: Who doesn't know about it?04:44
LaserJockand he didn't know what was going on04:44
LaserJockhe thought it was just non-free stuff04:44
persiaRight.  And pq has an advocate on REVU.04:44
LaserJockwhich of course is fine fore Multiverse04:44
LaserJock*for04:44
LaserJockthe question is specifically about Windows binaries04:44
LaserJockand that *hasn't* been brought up04:44
persiaLaserJock: Thanks for the heads-up: I thought this was intentional.  I've a draft I've been not posting, and will send it wiithin the next 12 hours.04:45
imbrandonLaserJock: what makes a diffrence if its a windows binary or a BSD binary etc ? if its distributable04:45
LaserJockand dholbach was like, "why hasn't anybody said anything then?"04:45
LaserJockimbrandon: some MOTUs are concerned about security, viruses, etc.04:45
imbrandonok then take wine out, wtf04:46
persiaBecause Toni reported it as a Windows binary in the blob post.04:46
imbrandonthat makes no sense04:46
persiaimbrandon: I'm not opposed to wine, or windows binaries, but I can't support them.  That's the essence of my point.04:46
LaserJockimbrandon: because it's a slipper slope according to crimsun04:46
LaserJock*slippery04:47
imbrandonLaserJock: the slope was choosen when we put wine in, i mean you cant give somone a tool and expect them not to use it04:47
LaserJockno04:47
LaserJockbut that doesn't mean we have to have packages for it04:47
LaserJockwe have 0install04:47
TheMusoYay. Storm coming.04:48
LaserJockbut we don't provide 0install packages04:48
* persia still thinks there is a difference between supporting user-insalled Windows software and distributing Windows software.04:48
LaserJockin any case, the objection was brought up04:48
LaserJockseveral MOTUs had problems with it04:48
StevenKTheMuso: Really? Still bright and sunny here04:48
LaserJockso we should have some sort of discussion and resolution of the issue04:49
TheMusoStevenK: Yeah. Cloudi is building up, and thunder can be heard.04:49
imbrandonpersia: i think you mix up supporting the packaging and supporting a program, very few is ANY programs we support as the coomunity, i've seen you make that statement before and it baffles me04:49
imbrandonLaserJock: i thought the resolution was pretty clear when mdz said "if its distributeable"04:50
LaserJockI honestly don't care what the resolution is, I just think we should have some sort of policy04:50
persiaimbrandon: When I have time, I try to fix all the bugs I can.  I further try to help users to use the software, and make sure it works.  90% off the stuff I investigate is for packages I will never use, sometimes in languages I do not know.04:50
LaserJockimbrandon: well, not exactly04:50
persiaI try to provide support.  I do not require you to do so, but I do expect that you will not make it harder for me to do so.04:50
imbrandonLaserJock: how is that not clear ? seems cut and dry to me04:50
StevenKTheMuso: Neat. Hopefully it won't end up as muggy as it was yesterday04:51
persiaLaserJock: We do have a policy.  The last message in the thread is authoritative.04:51
TheMusoStevenK: Yeah.04:51
LaserJockpersia: I don't think it exactly is04:51
imbrandonpersia: and i also like to make the end user experince for adding new software easy, i dont ask you to support it either04:51
imbrandonsame other reverse04:51
imbrandononly*04:51
LaserJockit was stated that Debian wouldn't take it04:51
persiaimbrandon: Actually, you do :), but that's a different issue (and I don't mind)04:52
LaserJockand since that was the criteria for the policy we have04:52
imbrandonLaserJock: how is it not, its from the CEO of canonical and a member of .....04:52
persiaLaserJock: Ah.  Good point.  That means it's not acceptable to us.04:52
LaserJockimbrandon: if they didn't know the specifics04:52
LaserJockbah04:52
persiaLaserJock: You might want to leave a comment on the REVU entry...04:53
imbrandonwe have firmware and other bits ( firefox ) that debian wont take, we're != debian04:53
imbrandonLaserJock: they dont have to know the specifics04:53
imbrandonyou think someone will change their mind because its a BSD or SUNOS or $other binary ? wtf04:53
LaserJockyes04:53
LaserJockwell many MOTUs felt so04:54
LaserJockso it's worth addressing04:54
LaserJockfrom mdz: My implicit policy for multiverse has always been that it must be04:54
LaserJockdistributable, and little else.  It was modeled after Debian non-free, which04:54
persiaI don't think the source of the binary matters: I'd be just as opposed to a new BSD or SunOS binary.04:54
imbrandonwtf so inclusion would read "if its distributable but not built on Windows"04:54
LaserJockis similarly defined (everything which doesn't meet the DFSG but is still04:54
imbrandonwhat if its a reactos binary?04:54
LaserJockdistributed by Debian).04:54
LaserJockthe point being that Multiverse is modeled after Debian non-free04:55
LaserJockand several people said that Debian would never take this package04:55
imbrandonyes but not byte for byte, just as ubuntu != debian04:55
LaserJockso it's *worth* discussing for goodness sakes04:55
LaserJockI honestly don't care about the outcome04:55
LaserJockbut I really feel like we need so real resolution04:56
imbrandonand it was, and because the awnser wasent liked it has to be driven out, thats what i'm getting at, a specific question was asked "what is the inclusion policy" and one was give, it falls in that so whats the problem04:56
LaserJockimbrandon: the question is specifically about Windows binaries04:56
persiaLaserJock: I'm not sure we don't have real resolution at this point.  I don't understand how the last message isn't clear, and I don't understand why only Windows is bad.04:56
LaserJockbecause when I talked with dholbach he was like "oh, I didn't know that that was about"04:57
LaserJockI think they thought it was just the usual thing04:57
LaserJockwhich we all know04:57
persiaLaserJock: Check with elmo: that's the only person who needed to know.04:57
imbrandonomfg listen to the words i'm saying LaserJock , one second, listen to me , the specific question was "what is the multiverse inclusion policy" and that windows binary falls into it, NOW if you want to bring up a second question or exception fine, but the decision is very clear IMHO04:57
LaserJockimbrandon: but that was *not* the question04:58
* persia agrees with imbrandon despite not agreeing with the decision04:58
imbrandonLaserJock: it WAS https://lists.ubuntu.com/archives/motu-council/2007-November/000498.html04:58
imbrandon^^ READ04:58
LaserJockimbrandon: that was the guy who's trying to push his stuff04:58
imbrandonand?04:58
LaserJockhe *nowhere* mentions the stuff that crimsun and the other guys talked about04:58
imbrandonerr shit wrong link04:59
LaserJockthey know the multiverse policy as much as everybody else04:59
persiaLaserJock: So, what does that matter.  Interested party asks project leader.  Project leader identifies delegate.  Delegate publishes policy.04:59
LaserJockbahhhh04:59
LaserJockscrew it04:59
imbrandonLaserJock: mdz stated "any thing thats distributweable"04:59
* mdomsch uploads firmware-tools and firmware-addon-dell to REVU04:59
LaserJockimbrandon: I know, but I don't feel like he looked at the issue04:59
LaserJockI just want to be sure05:00
LaserJockbut well, it's not my package and I don't care about this at all05:00
LaserJockI just want to make sure that the objections that people had are addressed05:00
persiaLaserJock: Please, I do agree that the policy needs to be redefined, I just don't think that is the place to argume about it.  I think a wiki draft policy, review by MC, and presentation to TB would have a greater chance of accomplishing something.05:00
* mebrown says thanks to mdomsch...05:00
imbrandonLaserJock: what issue, i think he looked at it very clearly, its not a question if X can be included, its a question of what can be, you cant do every package on a case by case you have to follow or change the policy05:00
LaserJockpersia: that's what I'm trying to do!!!!!05:01
persiaLaserJock: Ah.  My misunderstanding.  From your notes above, I had the impression you were arguing with the process for establishing the current policy.05:02
imbrandonLaserJock: and if that is the case then all firmware will have to be removed because it was built on and for windows to be used by those drivers05:02
LaserJockI'm saying that this hasn't been properly addressed05:02
LaserJockthe guy sent an email to Mark05:02
LaserJockwho then CCd the MC05:02
LaserJockit's not addressing the issue that MOTUs had05:03
imbrandonLaserJock: you are looking at the wrong email, you should be looking at the one titled "multiverse inclusion policy"05:03
LaserJockimbrandon: I am looking at it05:03
imbrandonLaserJock: ok then you see where mdz said "ok" ?05:03
imbrandoni'm not seeing your point here05:03
persiaLaserJock: Ah.  Right.  I think that comes from no activity on part of MC: I'm not sure how we are intended to prod them to action.05:03
Zelutanyone know a good resource for setting gconf settings via the shell/scripts?05:03
LaserJockpersia: I talked to dholbach last night05:04
imbrandonLaserJock: as the policy stands right this second the package is ready for multiverse05:04
LaserJockhe wondered why the MOTUs who objected didn't reply to the email05:04
LaserJockimbrandon: I would agree with you, other MOTUs didn't05:04
persiaLaserJock: Right.  Based on that, I'm of the opinion there is more to be said, but I'm just not sure that continuing that thread is the way to do it, nor do I know that the final decision is not an infomed decision.05:05
LaserJockpersia: I'm just not sure05:05
LaserJockthat's why I'm trying to get people to write something up, get it going05:05
LaserJockmy goodness05:06
imbrandonman-o-man but firmware built for and on windows is "OK" wtf is the diffrence05:06
persiaLaserJock: Regarding replies, I suspect most MOTU don't follow MC closely, and I also suspect that most would not feel obliged to respond to queries directed to MC.05:06
LaserJockI'm just trying to get us to get this thing resolved05:06
persiaimbrandon: No difference.  Personally, I'd like to see all acceptable binary blobs restricted to "restricted", where an NDA can be signed, and followed.05:07
imbrandonLaserJock: i dont and dident volenteer to because i whole heartly agree with mdz's statement "anything thats distributable" and that falls into that category IMHO so why do i need to reply or write something ?05:07
imbrandonin other words it IS resolved untill someone oposing brings up an issue and gets a new policy05:08
LaserJockimbrandon: I didn't say you did05:08
LaserJockbahhhhhhhhh05:08
persiaimbrandon: I'll agree to that: I think LaserJock is only trying to start the opposition at this point.05:08
imbrandonright05:09
LaserJockall I'm saying is that it looks like the opposition to the policy was not getting heard05:10
LaserJockI'm just trying to make sure we get proper resolution to the issue05:10
LaserJockI personally agree with imbrandon, but the specific issue should be addressed by MC/TB IMO05:11
imbrandonsure i can agree to that since they dident email anyone they cant be heard, but on the other hand saying "Windows" binarys cant be in multiverse wont fly i can 1000% tell you that05:11
imbrandonyou might find some other way to get that package not included but it wont be for that because all other binary only packages could be removed using the same arguments05:11
LaserJockwell, I'm not going to argue about it05:12
imbrandonLaserJock: mdz is still on the TB afaik05:12
LaserJockbut there were some well-respected MOTUs who disagree05:12
LaserJockimbrandon: and?05:12
imbrandonseemed like a official response to me05:13
LaserJockno it's not05:13
LaserJockmdz != TB05:13
imbrandonit dident say it was a personal opinion and it came from his ubuntu adrress to the -devel ML05:13
imbrandonpretty official05:13
* persia doesn't think it matters, and suggests forgetting about the history of that thread, and that those interested draft an alternate policy.05:14
* imbrandon agrees05:15
LaserJock*sigh*05:15
* imbrandon packages Photoshop CS05:16
imbrandonand runs05:16
LaserJockthat only took half an hour :/05:16
persiaLaserJock: What sort of response do you seek?  Do you want us to all agree with the undefined position, and argue that the current policy was badly generated, never applied, and something else should?05:17
* bddebian packages Wolfenstein: Enemy Territory05:20
persiaimbrandon: That doesn't even meet the current policy :)05:20
LaserJockpersia: no, I was trying to say exactly what you just said05:20
* StevenK makes a movie called "imbrandon and bddebian must die" and then packages it.05:20
bddebianhahaha05:20
persiaLaserJock: Ah.  OK.  I misinterpreted "*Sigh*".  My apologies.05:20
imbrandonLOL05:20
bddebianStevenK: At least mine is "free" :)05:20
imbrandoncan i package Photoshop CS2 as Gimp-NG ?05:20
StevenKbddebian: Mine can be under whatever license I want, so there05:20
bddebianheh05:20
persiaimbrandon: With permission from Adobe, yes.05:20
=== xopher- is now known as xopher
bddebianGnight gang05:48
RAOFHey, anyone know if it's safe to build gecko-embedding packages against libxul1.9-dev yet?05:48
RAOFOk, given we don't *have* a 1.9 libxul package, I'll call that "no".05:51
=== asac_ is now known as asac
warp10Hi all!06:37
LaserJockRAOF: hehe06:44
dholbachgood morning06:45
* Hobbsee stomps on midi files.06:45
persiaHobbsee: Why?  What did they do to you?06:45
Hobbseepersia: they wont play in wine.06:45
Hobbseei dont know why.06:45
* Hobbsee wants aoe music.06:45
persiaHobbsee: Do you have a MIDI device defined in WINE?06:46
persiaHobbsee: Alternately, might I suggest timidity?06:46
Hobbseepersia: afaics, yes.  but i may be looking in th wrong place06:46
Hobbseetimidity is running - but i still never get music.06:46
persiaHobbsee: Right.  Do you have a soundfont installed?06:47
Hobbseepersia: taht would not be in conjunction with "Just Working", i'm sure.06:47
Hobbseeie, no.06:47
persiaHobbsee: I forget.  I have heaps of soundfonts, and don't actually know if one is installed by default.  Open a bug, and subscribe me, and I'll take a look this weekend.06:48
Hobbseeokay06:48
Hobbseepersia: oh, hmm, i presume i follow http://frankscorner.org/index.php?p=mid or something?06:49
persiaHobbsee: I thought that timidity had an init.d that did the last step, I'm just not sure about the soundfont.  That page should work though.06:50
LaserJockdholbach's here, that's my que to go to bed06:51
* dholbach hugs LaserJock06:51
dholbachLaserJock: sleep tight!06:51
persiaHobbsee: I still want the bug, as I'll forget to investigate otherwise.06:51
* LaserJock hugs dholbach 06:51
Hobbseepersia: will do06:51
LaserJocknight MOTU Land!06:51
Hobbseepersia: any idea wht the init.d was?06:51
persiaHobbsee: /etc/init.d/timidity I think.  I'm not near a useful machine now, and it was back in Dapper / Edgy I was chasing that.06:52
Hobbseeok06:52
=== asac_ is now known as asac
Lutinpersia: looking at the ggobi merge: can you recall by xdg/ggobi.png is converted to xpm ?06:56
persiaLutin: s/by/why/ ?06:56
persiaIf so, it's to support the Debian menu system, for e.g. fluxbox users.06:57
Lutinpersia: yep, sorry :)06:57
Lutinpersia: ah ok06:57
persiaLutin: Just in the spirit of full disclosure, I don't remember ggobi specifically at all, but that's true for everything.  Ideally, every GUI package has a debian menu file with a 32x32 xpm as well as a .desktop file.06:58
imbrandon( even some non gui apps , e.g. nano do )06:59
imbrandon:)06:59
Lutinhehe :)06:59
persiaimbrandon: True.  I've never really understood that.  Does it call x-terminal-emulator and execute inside?07:00
imbrandonyea07:00
persiaimbrandon: Do you think that should be standard?  I'd prefer to limit at least the standard menus to GUI apps, although I'm not volunteering to strip all the extra menu files.07:01
imbrandonreally i have no opinion either way, i think some apps should yea, mutt , nano , etc but ls and other binutils ?07:04
persiaimbrandon: Hmm..  Interesting point.  Perhaps curses apps are OK, and others less so?07:05
imbrandonyea, thats kinda what i was getting at and dident know it07:05
* persia doesn't dare propose the inclusion of .desktop files for curses apps to -desktop07:06
imbrandonLOL07:06
imbrandonalthough tech curses apps are ( a form of ) GUI ( see: MS Windows 1.0 )07:07
* imbrandon ducks07:07
persiaimbrandon: I did, and I didn't want to remember having done so.07:07
imbrandonlol07:07
imbrandonbut serouisly i guess thats the thinking, because mc does too07:08
imbrandonand others the more i think about it07:08
imbrandon( the debian menu, not .desktop )07:08
jdongimbrandon: poke; would you like to sponsor KTorrent 2.2.3 into hardy for me? :)07:08
* persia encourages jdong to use the sponsors queues, and scream when they are broken, rather than poking people07:08
Hobbsee<gasp>07:09
imbrandonjdong: if it can wait ~9 hours, i definately will, i'm in total wind-down mode tonight07:09
Hobbseethanks, persia!07:09
* jdong heeds advice :)07:09
imbrandonbtw jdong why havent you applied for MOTU yet ? heh07:09
jdongimbrandon: funny you should mention that07:10
persiaimbrandon: You should check your mail...07:10
jdongimbrandon: just sent off that e-mail07:10
imbrandonahhh lol07:10
* imbrandon looks07:10
jdongooh look at that, bug reports I can close in ktorrent at the same time :D07:10
* persia wonders why imbrandon isn't a listed sponsor, given vocal support over a long time07:11
imbrandonand having sponsord a few packages :)07:11
imbrandonhrm i dont seem to find the email, was it sent reciently ?07:12
imbrandone.g. last 2 hours07:12
jdongI smacked my forehead when I hit send07:12
jdongrealized I forgot to put imbrandon down :)07:12
jdongwho has been unfortunate enough to be dragged into sponsorin my junk in the past ;-)07:13
persiaimbrandon: You weren't cc'd.  jdong: you might want to forward that mail :)07:13
imbrandonpersia: i'm on the MC list though07:13
imbrandonso i should have still a copy07:13
jdongI'm sitting in mod queue for MC list07:13
imbrandonahh07:13
dholbachapproved 2 minutes ago07:13
persiaimbrandon: Hmm...  I don't know why you don' have it then.07:13
imbrandonslow mail ( gmail via imap ) it'll be here if it was approved 2 minutes ago07:14
imbrandonrsn07:14
imbrandonpersia: infact i replied to your mc mail about IRC heh, so i know i'm subscribed :)07:16
persiaimbrandon: Right.  I was trying to ignore that :)07:16
* imbrandon kills afterthoughts07:16
imbrandonhehe07:16
imbrandonanyone else notice they got osx 10.5 loaded on an eeepc :)07:18
=== gpocente1 is now known as gpocentek
persiaMOTU applicants: it's awfully nice when there are links to LP and your wiki page in your application :)  Your sponsors know who you are, but it's an extra hunt.07:18
jdongpersia: oops, this isn't a good start of me doing things right :)07:18
persiajdong: Unfortunately it's something we each only get to do once.  I wasn't happy with my own application after sending it either :)07:19
* imbrandon got a ~1 hour drilling by mdz and co. instead of a nice email to MC :)07:20
imbrandonactualy that was for core-dev, not sure whom I talked to for MOTU07:21
jdongyeah I remember you coming back from the core dev one breathing a huge sigh of relief :)07:21
imbrandonheh yea07:21
imbrandoni was sweating IRL, then went for beer that night :)07:22
jdongalright fine, taunt me about the alcohol thing :P07:22
imbrandonlol07:22
imbrandoni'm sure with some MIT in your blood you can find ways, not that i'm encouraging it07:22
imbrandonstill no mail /me goes to troll the archives07:23
* jdong makes wishlist for Santa07:25
jdong(1) 3.0GHz quad-core penryn......07:26
=== \sh_away is now known as \sh
imbrandon(1) eeepc (2) new computer chair (3) Employment at a FL/OSS based company07:27
imbrandonheh07:27
imbrandoni'm easy07:27
jdongooh (2) eeepc!07:27
\shmoins07:28
jdongumm... (3) Dodge Charger RT AWD....07:28
imbrandonheya \sh07:28
imbrandonjdong: what email do you use for REVU ?07:36
jdongimbrandon: probably jdong@ubuntu.com if I've uploaded anything there (vaguely recall a long time back)07:37
persiaimbrandon: It's not REVU.  It's in the sponsors queue: https://bugs.launchpad.net/~ubuntu-main-sponsors07:37
jdongimbrandon: careful though, Tonio_ says he got it ;-)07:37
persiaimbrandon: There are 38 others available for you :)07:37
jdongimbrandon: remember this tangle from when I first started doing KTorrent? :D07:37
imbrandongot what ?07:37
jdongthe KTorrent upload07:37
imbrandoni was gonna include a link for http://revu.ubuntuwire.com/upload.py?user=blah@blah.com :)07:38
Tonio_jdong, imbrandon: currently building here07:38
imbrandonTonio_: kk07:38
imbrandonpapa !!07:38
Tonio_imbrandon: not yet still07:38
persiaimbrandon: Ah.  Right.  I forgot about that.07:38
imbrandonheh, but always fun trying07:38
RAOFHm.  I wonder under what circumstances os.getcwd() can throw a "file not found" exception.07:38
Tonio_imbrandon: don't laugh about that, but I'll have to do a spermogram exam soon07:38
Tonio_imbrandon: not that fun :/07:39
imbrandonheh07:39
jdongRAOF: when the cwd doesn't exist anymore?07:39
RAOFjdong: I suppose so.  Miro's being strange, then.07:39
Tonio_we've been trying to make it to work for 18 month now, so it looks like there is a problem07:39
* Tonio_ whishes making a baby is as simple as packaging07:39
imbrandonheh07:40
\shlol07:40
jdongdoes wife go under Suggests or Recommends?07:41
* jdong ducks07:41
Tonio_jdong: build-depends I suspect07:41
jdong:)07:41
Tonio_but you have to make a dh_shlibsdeps exception, since the package will depend on "mother | second-gay-father"07:42
Tonio_not to say that probably should be a recommend or even suggest thing07:42
jdongmeh we can put a Suggest on parents07:43
Tonio_imbrandon: so yes, not "papa" yet, and it looks like not going to for a moment :'(07:43
imbrandonsomeday, Tonio_ :)07:43
Tonio_imbrandon: hopefully07:43
Tonio_:)07:44
imbrandonmaybe next time you are in the US you will get a call saying "yes" :)07:44
imbrandonerr on second thought, i dunno if i wanna wish comming to the US on anyone07:44
imbrandon:P07:45
imbrandongrr dholbach i sent the mail to MC from the wrong email address, mind pushing it though ?07:45
jdongimbrandon: have you figured out any way for mutt or something in the sending stack to rewrite from: based on to:?07:46
jdongI'd love to be able to rewrite my @gmail to @ubuntu based on if I'm sending to a Ubuntu list07:47
imbrandonheh yea me too07:47
persiajdong: procmail can do that for you, if the internal mutt scripts aren't sufficiently powerful07:47
imbrandononly its from @brandonholtsclaw.com07:47
\shoh damn...more exploits for wireshark07:47
persia(Just tell mutt to use procmail on outbound, and tell procmail where to look for an SMTP server)07:48
jdongpersia: interesting idea :) I'll have to look into that07:48
imbrandonyea i can see my stack now, incomming is already complicated enough, now i'll have going out evolution --> procmail --> sendmail --> gmail smtp --> ....07:49
jdonghaha07:49
jdongyeah I don't like watching my mail evolve to rocket science either :D07:49
imbrandoni've just learned to try and keep most things serverside so i dont have alot of setup on a new box07:50
* persia apologies to all German speakers for poor spelling :(07:50
imbrandonbefore gmail's imap i had an "interesting" setup to say the leaste07:51
imbrandonbasicly all mail forwarded to gmail , then i got gmail via pop to my own server and used imap to access it from there, and google smtp out so my "sent" would be in the webui too07:52
imbrandonnow atleaste i get to cut my own server out of the equasion, except for archives07:53
\shimbrandon, so it's easier to setup a mail service directly and not using gmail ;)07:53
imbrandon\sh: maybe, but gmail spam filter > spamassasin07:53
persia¥sh: In that case it's harder to use the gmaili spam filter07:54
jdongimbrandon: I still have that setup (mirrored via getmail/fetchmail and served thru dovecot) going :D07:54
imbrandonjdong: enable imap via the settings hehe07:54
jdongimbrandon: set it up like two weeks before IMAP came out07:54
jdongGRR :)07:54
imbrandonlol07:54
jdongbut it's working now so I'd rather not change it.... got a spare 250GB drive sitting here to collect mail so thought what the heck, might as well07:55
imbrandonssh jdong@dovecot shutdown -h now07:55
jdonghaha07:55
* jdong shamefully admits writing an apparmor profile excitedly to secure dovecot :D07:55
imbrandonlol07:55
dholbachimbrandon: done07:56
imbrandondholbach: thanks, my mistake07:56
jdongit's that new-security-system reflex.... gotta use it like crazy for a day then abandon it :D07:56
dholbachno problem07:56
* dholbach hugs listadmin07:56
jdongwow it's 3AM, time for bed :)07:56
Hobbseeyay, listadmin!07:59
* Hobbsee goes thru ti too08:00
* Hobbsee thougth norsetto was a MOTU.08:00
dholbachnorsetto is08:01
RAOFThey are, aren't they?  Recently approved.08:01
Hobbseehis mail's getting moderated.  i wonder if norsetto@u.c isnt listed on launcphad or something.08:02
\shoh damn..I'm doomed...why I took the wireshark for security fixing08:03
\shthis package is evil but important..:(08:03
persiaHobbsee: Is it based on LP emails?  I thought listadmin was separate.08:03
Hobbseepersia: this is ubuntu-devel, which i believe takes a list of the people in ~ubuntu-dev, and whitelists them.08:04
persiaHobbsee: Ah.  That might be special.  I was thinking of the subscriber-only block.08:04
Hobbseeah yes.08:04
Hobbseethere's whitelisting and stuff from listadmin, i think08:05
* Hobbsee hasnt needed to use it yet08:05
gesermorning08:08
\shdamn....27 CVEs for wireshark/etherreal from 0.99.0 up to 0.99.5 that means dapper will get a lot of love now..and a lot of dpatches08:09
\shFujitsu, ping dapper wireshark/ethereal08:33
Fujitsu\sh: Hi.08:35
\shFujitsu, the only way to fix at least CVE-2006-3627 CVE-2006-3628 CVE-2006-3629 CVE-2006-3630 CVE-2006-3631 CVE-2006-3632 is to try to find a way to bump the dissectors of 0.99.0 in dapper to 0.99.208:37
ubotuUnspecified vulnerability in the GSM BSSMAP dissector in Wireshark (aka Ethereal) 0.10.11 to 0.99.0 allows remote attackers to cause a denial of service (crash) via unspecified vectors. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3627)08:38
ubotuMultiple format string vulnerabilities in Wireshark (aka Ethereal) 0.10.x to 0.99.0 allow remote attackers to cause a denial of service and possibly execute arbitrary code via the (1) ANSI MAP, (2) Checkpoint FW-1, (3) MQ, (4) XML, and (5) NTP dissectors. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3628)08:38
ubotuUnspecified vulnerability in the MOUNT dissector in Wireshark (aka Ethereal) 0.9.4 to 0.99.0 allows remote attackers to cause a denial of service (memory consumption) via unspecified vectors. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3629)08:38
ubotuMultiple off-by-one errors in Wireshark (aka Ethereal) 0.9.7 to 0.99.0 have unknown impact and remote attack vectors via the (1) NCP NMAS and (2) NDPS dissectors. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3630)08:38
ubotuUnspecified vulnerability in the SSH dissector in Wireshark (aka Ethereal) 0.9.10 to 0.99.0 allows remote attackers to cause a denial of service (infinite loop) via unknown attack vectors. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3631)08:38
ubotuBuffer overflow in Wireshark (aka Ethereal) 0.8.16 to 0.99.0 allows remote attackers to cause a denial of service and possibly execute arbitrary code via the NFS dissector. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3632)08:38
Fujitsu\sh: Why can't we backport those fixes?08:38
\shFujitsu, most of this stuff is not documented correctly in wireshark svn...even RH and others upgraded to 0.99.2 because of those issues these days08:39
FujitsuI recall them doing that yes... hmm..08:40
FujitsuHow big is the diff, and what kind of changes are there?08:40
\shFujitsu, I'm just trying to diff from 0.99.0 to 0.99.2 and prepare some patches and hopefully it works08:40
\shFujitsu, go to the wireshare viewsvn and diff e.g. epan/dissectors/packet-gsm.c from 18759 (0.99.2) to 17982 (0.99.0) revisions08:41
Fujitsu\sh: Are their patches these days a bit more sane and locatable?08:43
\shFujitsu, yepp08:43
\shFujitsu, 0.99.0 was the first wireshark release...everything before was ethereal...and I don't know why they documented the stuff much better...08:44
=== LucidFox_away is now known as LucidFox
Fujitsu\sh: OK, so once we're at 0.99.2, we should be OK forever?08:45
\shFujitsu, nope, I don't think so08:46
\shFujitsu, but let me try something first...I need to test something08:47
\shFujitsu, no...doesn't work .. we need to bump at least to 0.99.2 or we try to backport latest wireshark to dapper09:09
\shFujitsu, tbh, I don't know what is the best way...carrying a big patch from 0.99.0 to 0.99.2 in the package and patch more CVE fixes from 0.99.2 upto now09:11
Fujitsu\sh: Argh, damn.09:11
\shFujitsu, thinking about the importance of this package...I would try to carry a patch ....09:11
\shFujitsu, and we should ask for main inclusion for hardy :)09:12
FujitsuI swear, some upstreams are really looking to get themselves killed. phpMyAdmin, WordPress, [insert other PHP projects here]...09:19
\shFujitsu, agreed ;)09:19
\shFujitsu, I'll raise the wireshark discussion on -devel.09:20
FujitsuI guess I'd better have a look at phpMyAdmin in Gutsy at least.09:22
FujitsuWoah, they provide patches too now!09:23
pwnguinarg. why does gnome have to redo all the basic types09:28
persiapwnguin: flexibility09:31
pwnguini guses09:37
pwnguinguess09:37
pwnguinbut it also sucks having to know what the hell g_new0() does in order to debug code09:38
awalton__O_o that's a problem?09:38
persiapwnguin: No, really.  The idea is that compliant GTK apps could be ported to an environment where the definitions of the basic types were different, and the application would never need any changes, as long as GTK worked.09:38
pwnguinits a problem in the sense that i dont know gtk off hand09:39
persiapwnguin: It's an object layer.  Works about the same as for any OO environment.09:39
persiaAh.  There's docs :)09:39
awalton__good docs too09:39
pwnguini like to take a kantian cosmopolitan approach09:39
pwnguineverywhere looks the same ;)09:39
pwnguinthe sad thing is, everyone writes their portable code different09:40
pwnguinsdl doesnt look like gtk doesnt look like qt09:40
awalton__tis a shame.09:40
persiapwnguin: Well, you could learn WX.  There's a couple apps need porting :)09:40
pwnguinanyways, i think i found the offending line09:41
pwnguinhelpfully commented09:41
pwnguin/* When opening enclosures we need the type to determine09:41
pwnguin   the configured launch command. The format of the enclosure09:41
pwnguin   info: <url>[,<mime type] */09:41
=== Nafallo_ is now known as Nafallo
awalton__whatcha debugging pwnguin09:41
pwnguinliferea09:41
awalton__ah.09:42
pwnguinthat's supposedly to do with podcasts / enclosures09:42
s1024kbnorsetto: hello my teacher09:51
norsettohiya s1024kb09:51
dholbachhey s1024kb, hey norsetto09:52
norsettos1024kb: happily merging!?09:52
geserhi s1024kb, hi norsetto09:52
s1024kbnorsetto: i am happy to see you again! just want to finish "yappy" now09:52
s1024kbgeser: hi!09:52
norsettohi dholbach!09:52
s1024kbdholbach::^^09:52
norsettoheya geser :-)09:52
emgentheya norsetto ^^09:54
norsettoemgent: oh, now I feel safe ....09:54
emgent:)09:54
* cyberix hopes nmap 4.23 will make it for Hardy.09:55
cyberix(note: /me does not live in Germany)09:55
norsettocyberix: don't worry, we all know about you and your boots ;-)09:56
DaveMorriscan someone review my package on revu please  - http://revu.tauware.de/details.py?package=cpptest09:56
norsettoDoes anyone know how often dad is checking the debian archives for packages to sync/merge?09:58
geserDaveMorris: the changelog entry could be more infomative, like "* Initial packaging (LP: #162913)"09:59
DaveMorrisok, I'll do that on my other packages as well10:00
geserDaveMorris: if you have no files in /usr/{s,}bin don't list it in debian/dirs10:00
geserand your rules files looks like a mix from cdbs and a normal rules file with debhelper (and you include two different patch systems)10:00
DaveMorriswhich 1 do I need?10:01
s1024kbnorsetto: i had already use "grab-merge" to merge "yappy", now i should edit the changelog in /debian, right?10:01
norsettos1024kb: right10:02
DaveMorrisgeser: I'm afraid I don't know what you mean by it been a mix of debhelper and cdbs10:03
norsettos1024kb: you checked if grab-merge did a good job? You happy about the resulting package?10:03
geserDaveMorris: and name the -dev package only "libcpptest-dev" (you usually don't need the soversion in the -dev package name)10:03
s1024kbnorsetto: in this case, i think yes... what i should add to the changelog? i open "yappy_1.8-3ubuntu1.patch", shall i copy the paragraph "merge from debian unstable..." and paste them in changelog?10:04
norsettos1024kb: you should work on the source tree that grab-merge expanded for you10:04
geserDaveMorris: you include files from cdbs (line 3 and 4). with cdbs you only specify the targets which are different than usual (or need additional steps)10:04
s1024kbnorsetto: don't know what to do...10:05
geserDaveMorris: the rest of your rules file looks like a rules file which doesn't use cdbs but only debhelper10:05
norsettos1024kb: in the dir where you run grab-merge, there should be a directory called yappy-1.810:05
DaveMorrisI was under the impression I need lines 3/4 for the cdbs patches to be applied10:06
s1024kbnorsetto: yes10:06
norsettos1024kb: do you see it? Thats the root of the source tree that grab-merge expanded for you; it contains its guess of the merge10:06
s1024kbnorsetto: yes, see it10:06
norsettos1024kb: well, then you should work on that tree10:07
norsettos1024kb: check if the changes that grab-merge made are acceptable, and if so fill in the changelog in its /debian directory10:07
norsettos1024kb: its like for any other source tree you have seen before10:08
geserDaveMorris: yes, but you mixed different packaging styles10:09
DaveMorrisok, which one am I best to use in this instance?10:09
BugMaNhi all10:10
norsettobugman: hola10:11
s1024kbnorsetto: i had read all the files carefully already, and i thought that they're like what i imagine... and i open /debian/changelog,  i saw that the second record is about yappy 1.8.3, the changes of debian. and the top record is "merge from debian...", shall i add anything in the file now?10:11
BugMaNnorsetto: ave :)10:11
norsettos1024kb: I think so, what would you add in the changelog?10:12
* pochu waves10:13
s1024kbnorsetto: ... i don't know... i have been thinking about it for 2 days already...10:13
geserDaveMorris: if you want to use dpatch, include "/usr/share/dpatch/dpatch.make" in your rules file, man the clean target depend on unpatch and the build target depend on patch10:13
geserDaveMorris: and you need to convert your patch files to dpatch10:14
DaveMorrisI created the patches using cdbs-edit-patch is that a problem10:14
geserthe alternative would be to convert your rules file complete to cdbs10:14
geserDaveMorris: they are then for simple-patchsystem from cdbs10:15
norsettos1024kb: you should report all the changes from previous ubuntu versions which you are carrying over10:15
s1024kbnorsetto: but the file seems to have written them already...10:16
norsettos1024kb: I don't think the changelog has though10:17
norsettos1024kb: what is in the changelog now?10:17
s1024kbnorsetto: Line 1: yappy (1.8-3ubuntu1) gutsy; urgency=low10:18
s1024kbnorsetto: line 2:   * Merge from debian unstable, remaining changes:10:18
s1024kbnorsetto: line 3:     - SUMMARISE HERE10:19
s1024kbnorsetto: line 4:  -- Ubuntu Merge-o-Matic <mom@ubuntu.com>  Mon, 24 Sep 2007 23:35:32 +010010:19
norsettook, lets work line by line. You are happy about line 1?10:19
s1024kbnorsetto: line 5: yappy (1.8-3) unstable; urgency=low10:20
s1024kbnorsetto: line 6: * Bug fix: "python-yappy: typo in Description: field", thanks to Olivier10:20
s1024kbnorsetto: line 7: Tetard (Closes: #443680).10:20
norsettos1024kb: ok ok ... don't paste the whole thing :-)10:20
norsettos1024kb: lets work line by line. You are happy about line 1?10:20
s1024kbnorsetto: line 1, yes...10:21
norsettos1024kb: are you sure, for what distribution are we doing the merge?10:21
norsettos1024kb: are we merging for gutsy?10:23
s1024kbnorsetto: yappy-1.8, ... is it right?10:23
norsettos1024kb: yes the version number is correct, but, are we merging for gutsy?10:24
gesers1024kb: small hint: what's the current development version of Ubuntu?10:24
s1024kbnorsetto: gutsy? right?10:25
norsettos1024kb: well, gutsy is now what we call a Stable Release10:25
norsettos1024kb: we only fix very serious bugs for it10:25
norsettos1024kb: our development version is not gutsy10:26
s1024kbnorsetto: understand so far... so it's...10:26
norsettos1024kb: when you made your pbuilder, you did it with ....?10:27
gesers1024kb: h...y (replace the . with a-z)10:27
s1024kbnorsetto: feisty?10:27
norsettos1024kb: did you? Seriously?10:27
gesers1024kb: next hint: https://edge.launchpad.net/ubuntu (look at Series)10:29
norsettos1024kb: what I'm asking is for what version of pbuilder are you building, not where you installed it10:29
s1024kbnorsetto: hoary?but why? (sorry)10:33
Hobbsee...?10:34
Hobbseewhy on earth would we use pbuilders for now unsupported versions of ubuntu?10:34
norsettos1024kb: ok, do you know that our next version of ubuntu is called hardy?10:35
s1024kbnorsetto: yes10:35
norsettos1024kb: ok, thats our next version, is what we call our development version10:36
DaveMorrishas anyone got an example of what a <pkg>.install file should look like10:36
DaveMorrisI can't find one :(10:36
s1024kbnorsetto: okay10:36
norsettos1024kb: hardy is our development version, gutsy is our current version, feisty is not our current version but we still support it10:36
s1024kbnorsetto: okay, understand10:37
norsettos1024kb: so, why would we merge for gutsy? Do we need to do that? (I answer: NO)10:38
norsettos1024kb: therefore you have to change the first line, agreed?10:39
s1024kbnorsetto: we merge for "Hardy", oh, i understand now!10:39
s1024kbnorsetto: so i should change: "yappy (1.8-3ubuntu1) hardy; urgency=low"10:41
s1024kbnorsetto: and now i understand why we're fixing bugs, merging packages here... for the next version. because in my experience i thought that we're doing that for the current OS... i guess that it's what a windows user will think...10:45
effie_jayxcould anyone help me with my gpg key10:45
norsettos1024kb: right10:45
effie_jayxit's preventiing me from signing anything10:45
effie_jayxI am playing around making debdiffs and it says it can't saign the packages10:46
effie_jayxI know I have my key in my system10:46
norsettos1024kb: its indeed a very common problem with many users10:46
norsettos1024kb: now, back to business, what changes are we carrying over from previous ubuntu changes?10:47
s1024kbnorsetto: i have to apologize, before this i really don't have the "next version" in mind... sorry10:47
norsettos1024kb: don't have to be sorry, its a very common problem many users are having10:47
s1024kbnorsetto: i guess that the 1.8-3 is the latest version in this case?10:49
norsettos1024kb: yes, but is that an ubuntu version?10:50
norsettos1024kb: that version is coming from Debian, doesn't include whatever change was made by Ubuntu, which is why we need to merge10:50
s1024kbnorsetto: the latest ubuntu version should be 1.8-3ubuntu1?10:51
norsettos1024kb: no, thats the one we are doing10:51
norsettos1024kb: we are working on that right now, the one before that is the last10:52
s1024kbnorsetto: 1.8-2? sorry...10:54
norsettos1024kb: what versions you you see in the changelog?10:54
gesereffie_jayx: does your key uid match the name entry in the changelog (including all comments)?10:55
s1024kbnorsetto: 1.8-3ubuntu1, 1.8-3, 1.8-2ubuntu1, 1.8-2, ...10:56
norsettos1024kb: ok, so what would be the last ubuntu version, the one before 1.803ubuntu1 ?10:56
norsettosorry, before 1.8-3ubuntu110:56
s1024kbnorsetto: 1.8-3?10:57
norsettos1024kb: the last UBUNTU version10:57
effie_jayxgeser,  let me check10:57
s1024kbnorsetto: 1.8-2?10:58
effie_jayxgeser,  checked .. it maches10:59
* effie_jayx echo's DEBEMAIL and DEBFULLNAME10:59
geserand you get that error that the secret key couldn't be found?11:01
effie_jayxgeser,  yes11:01
geserbtw signing is only imporant when you want to upload not for debdiffs11:02
effie_jayxgeser,  it says ... public key not found11:02
geserpublic key?11:02
effie_jayxgeser,  really?. I am new to this so I though it was needed11:02
gesercan you paste bin the whole output?11:02
effie_jayxgeser,  it read public key not fpund11:02
effie_jayxok11:02
gesereffie_jayx: yes, as the signture is only on the .dsc file and .changes file and both files aren't in the debdiff11:03
s1024kbnorsetto: i guess that they're both had been modified from yappy-1.8, in Ubuntu the modified version is yappy-1.8-2, in Debian the modified version is yappy-1.8-3, so is it the last ubuntu version yappy-1.8-2?11:03
effie_jayxgeser, http://pastebin.ubuntu-nl.org/44712/11:04
effie_jayxgeser,  it seems to me ... it's trying to search for a key that signed the package in 2005, no?11:05
gesereffie_jayx: debdiff tries to verify the signature of the debian.dsc and complains that you don't have that public key11:06
geseryou can ignore it11:06
effie_jayxgeser,  ok11:06
effie_jayxthanks geser11:07
effie_jayxok I ma ready to make patches if needed :D11:09
norsettos1024kb: sorry, I'm having some net troubles11:09
Lutinnorsetto: every 30 mins iirc (how hoften DaD checks for new merges)11:09
Lutinot maybe an hour11:09
Lutinor*11:09
norsettolutin: oh, I see, I'm asking since I've seen a merge in MoM since a couple of days but not yet in DaD11:10
Lutinnorsetto: Oo . what one ?11:10
s1024kbnorsetto: sorry my teacher...  i had a hard time just now, i guess that you were angry with my stupid mistakes...11:10
norsettolutin: cuyo11:11
s1024kb norsetto: i guess that they're both had been modified from yappy-1.8, in Ubuntu the modified version is yappy-1.8-2, in Debian the modified version is yappy-1.8-3, so is it the last ubuntu version yappy-1.8-2?11:11
norsettos1024kb: not at all, its that I have many things to do all at once11:11
Lutinnorsetto: indeed ... weird11:12
s1024kbnorsetto: so if you're busy now, shall we do it the tomorrow?11:12
Lutinnorsetto: Oo, can't find it on MoM actually11:13
gesers1024kb: you hope he'll be less busy tomorrow? :)11:13
norsettos1024kb: well, you do require a lot of attention11:13
norsettolutin: just checked now and it was there!?11:13
norsettolutin: can it be the funny version number?11:14
Lutinnorsetto: well I checked merges.ubuntu.com/c/ , and there"s no cuyo package11:14
norsettos1024kb: the last ubuntu version is 1-8-2ubuntu1, you have to report in the changelog all the changes from that version which you are merging11:15
gesernorsetto: really a very interesting version 2.~-1.0~beta1-111:15
norsettolutin: funny, I see it11:15
s1024kbnorsetto: sorry... thank you my teacher...11:15
Lutinnorsetto: you see the link on the html page, but the folder doesn't exist11:16
gesernorsetto: ask Keybuk why MoM lists it11:16
Lutinnorsetto: actually I think it's a merge from experimental11:16
norsettolutin: oh yes11:16
LutinDaD never polls experimental for updates11:16
norsettolutin: ah right, it is indeed11:17
Lutinmaybe MoM has some code to see if a merge comes from experimental, but it seems it just doesn't merge the package11:18
norsettolutin, geser: that explains it, thanks11:18
s1024kbnorsetto: i guess now i understand what i shall write in the changelog... thank you very much. i try to do it at home... i go home now, thank you for showing me a new world.11:19
norsettos1024kb: thanks to you selene, see you soon then!11:19
s1024kbnorsetto: thank you again my teacher, i will not give up, i will work hard and i wish that i can depend on myself soon...11:21
norsettos1024kb: don't worry, one step at the time and we will be there soon11:21
s1024kbnorsetto: many many thanks. i see the dawn today... :-)11:22
proppyhi11:38
norsettoheya proppy11:41
proppyheya norsetto11:42
proppynorsetto: wassup11:44
norsettoproppy: well, soon lunch !11:45
proppynorsetto: I bet you'll be eating some viking food again11:45
norsettoproppy: actually I got some kind of stomach flu today11:45
norsettoproppy: maybe some rice :-(11:46
proppynorsetto: My room mate ordered a rice cooker, it's a must have11:46
norsettoproppy: we have plenty of those already, my wife is a fanatic of oriental cooking11:47
norsettoproppy: what about you? still trying to digest debhelper?11:48
proppynorsetto: maybe she can share some receipe with my girlfriend :), does she have a blog (ahah) ?11:48
norsettoproppy: she has actually :-)11:48
proppynorsetto: I'm kinda stuck with an impossible choice (like usual)11:48
proppynorsetto: a friend of mine recently give me a CMakeList.txt to build juce11:48
proppynorsetto: and as the original makefile does not generate shared library11:49
proppynorsetto: and I feel pretty unconfortable patching a premake generated Makefile11:50
proppynorsetto: I've give a though using cmake instead of the upstream provided makefile11:50
norsettonot knowing the details I see 4 choices here11:50
proppynorsetto: but if I do so, I'll be trouble with debuild reverse patching, as cmake will overwrite the upstream provided Makefile, and then cdbs patch will have trouble to revert11:51
proppyI'll be glad to have some guru thought about this :)11:51
norsettoproppy: well, why do you patch something which is not there?11:52
proppynorsetto: I'll be using patch to add the cmake support11:52
proppynorsetto: and remove the upstream provided makefile11:52
norsettoproppy: is this cmake a nice new toy or you really need it (meaning, you can't do otherwise)?11:53
proppynorsetto: but as cmake will create a different makefile, reverse-patch will be troublesome I guess11:53
proppynorsetto: I thought about this, cause I get my hands on a CMakeList.txt for juce, then I don't have to write it myself11:54
proppynorsetto: but the alternative is to patch a premake.lua generated Makefile11:54
proppynorsetto: which doesn't sound nice either11:54
=== dholbach_ is now known as dholbach
norsettoproppy: well, the cleanest would be to ask upstream to use it11:55
proppynorsetto: you mean to use cmake, or to generate a shared library and have some install rules ?11:56
norsettoproppy: generate a shared library and have some install rules11:56
norsettoproppy: which they can do easily with some #IFDEFS11:56
proppynorsetto: I guess premake.lua already support it11:57
norsettoproppy: I mean, are they interested to port this properly to linux or not?11:57
proppynorsetto: but then instead of patching the generated Makefile11:57
proppynorsetto: I have to patch the lua script with generate the makefile11:57
proppynorsetto: and then propose my patch to the upstream11:58
proppyso step 1: report missing install rules and shared library on forum11:58
proppystep 2: work on a patch11:58
proppystep 3: reply with the patch11:58
proppyok ?11:58
norsettoproppy: why not just report the missing install rules and shared library with a patch?11:59
proppynorsetto: I use to thought that report first, then fix, is a good habit12:00
proppynorsetto: but it may be a wrong idea12:00
norsettoproppy: it depends on upstream, some like if you report a problem and a (possible) fix at the same time12:00
proppynorsetto: the upstream is very responsive, maybe he will fix it himself12:01
proppynorsetto: in the next version12:01
dholbachMOTU Q&A session in #ubuntu-classroom now12:01
proppynorsetto: but it should speed thing if I post the fix too12:01
norsettoproppy: it usually does12:02
proppynorsetto: thanks for your time12:02
proppynorsetto: go to class now !12:02
norsettoproppy: heck, you should go to class!12:02
* norsetto writes a report to the principal about proppy not showing in time to class12:03
proppynorsetto: already in12:03
deadwillmorning12:08
norsettohey deadwill, join us in #ubuntu-classroom12:10
\shwoohoo...edgy wireshark cves fixed12:11
Fujitsu\sh: Nice one!12:12
\shFujitsu, 10 fixes cherry picked :) 5 backported from 0.99.6 for feisty (applies for edgy too)12:12
proppynorsetto: bug #158605 commented12:13
ubotuLaunchpad bug 158605 in ubuntu "[needs-packaging] juce" [Wishlist,In progress] https://launchpad.net/bugs/15860512:13
norsettoproppy: looks good12:15
Fujitsu\sh: Sounds painful.12:21
rexbronDon't you want to review? http://revu.tauware.de/details.py?package=openlibraries and http://revu.tauware.de/details.py?package=genpo12:36
* rexbron is running out of creative ways to ask for a review....12:36
HobbseeFujitsu: wants to review.12:38
norsettorexbron: bribes usually work .....12:39
norsetto:-X12:39
rexbronnorsetto: Want a cookie?12:39
zulmorning12:39
=== effie_jayx is now known as man
=== man is now known as effie_jayx
eneko_tabmorning12:49
DaveMorrisgeser: I've done it with cdbs now, hopefully its right,  can you check for me please http://revu.tauware.de/details.py?package=cpptest12:50
\shFujitsu, dapper is a no go...you can't change it back to old variable names...they changed everything ...13:01
Fujitsu\sh: -grumble-13:01
\shFujitsu, bumping to 0.99.2 is valid, and we can backport all fixes like I did now with 0.99.313:01
FujitsuDapper will have to rot, then. Maybe try to backport the latest through -backports.13:02
\shwell, when edgy is in the security archive, we can backport them...13:02
FujitsuWe can't really backport from -security.13:02
\shwireshark package has transitional packages handy13:02
\shFujitsu, the real problem is the complete namechange they went through13:03
\shthey even changed the libnames on windows and looks like on unix too13:03
FujitsuLovely. I don't think we can support Ethereal in Dapper then. People will have to rely on -backports, if anything.13:04
\shFujitsu, funny thing about edgies version was, debian upstream maintainer put some not official svn checkout in..:(13:04
\shFujitsu, e.g. for epan/dissectors/packet-http.c I had to patch it three times, to apply the CVE fix...and the real upstream version is correct :(13:05
Fujitsu\sh: Fun. I'll work on phpMyAdmin back to at least Feisty, and maybe Dapper/Edgy tomorrow, but sleep for me shortly.13:07
\shFujitsu, I'm done for today looks like...13:09
\shI think it's the longest changelog ever (actually for me)13:09
Fujitsu\sh: I saw that it was rather long, yeah.13:11
\shFujitsu, that was only feisty....edgy is much more ,)13:12
FujitsuHaha.13:13
FujitsuI guess it would be.13:13
geserDaveMorris: looks better. Why are you shipping README and README.in in libcpptest0? Have you tried to install both libcpptest0 and libcpptest-dev as both ship /usr/lib/libcpptest.so.0? And you probably should add a (versioned) dependency on libcpptest0 to libcpptest-dev.13:34
DaveMorrisok geser I'll look at that, I must of over looked the readme thing13:35
proppyDaveMorris: (you know unittest++?)13:36
DaveMorrisyeah, cpptest is another one which I used in my project13:36
DaveMorrisso I thought I'd get it packaged13:36
proppyDaveMorris: (cause I packaged unittest++ for debian, just in the case you need it)13:37
proppy:)13:37
geserDaveMorris: and you should also work on debian/copyright. At least the upstream authors and upstream copyright is missing.13:37
proppyDaveMorris: do you supply a non -dev package ? cause I dropped it for unittest++, cause you don't really need to ship executable that depends upon a unittest shared library do you ?13:38
DaveMorrisproppy: good point, I hadn't thought about it that way13:39
proppyDaveMorris: btw I still have an empty libunittest++0 for retro compatibility which is odd :(13:40
proppyanyone know a package builded with premake (lua) ?13:56
Fujitsu\sh: That is an impressive changelog.14:08
Fujitsu(entry)14:08
\shFujitsu, yeah :)14:08
DaveMorrisgeser: Do you mind having a look at my latest attempt?14:11
DaveMorrishttp://revu.tauware.de/details.py?package=cpptest14:11
geserDaveMorris: as you don't use dpatch you don't need to build-depend on it14:16
DaveMorrisk14:16
DaveMorrisgeser: anything else apart from that?14:20
rexbronHobbsee: Hey, how are things on your side of the world?14:21
Hobbseerexbron: well, we're upside down still, so things are normal14:21
rexbron:)14:21
rexbronHobbsee: Have time for a review?14:21
Hobbseeno, sorry14:22
* Hobbsee has an exam tomorrow, and needs bed soon14:22
rexbronits ok14:22
rexbrongogogo14:22
rexbronand good luck14:22
=== proppy is now known as procurry
=== procurry is now known as propasta
=== doko_ is now known as doko
geserHobbsee: good luck for your exam14:35
Hobbseegeser: thanks :)14:36
=== cprov is now known as cprov-lunch
MagicFabhi14:47
Hobbseeoh noes, it's MagicFab14:48
MagicFabHow can I check which package installed another one as dependency ? I am trying to find out how debsig-verify got installed on a system.14:48
MagicFabHobbsee, I am glad to see you too :)14:48
HobbseeMagicFab: the unefficient method would be to do an apt-cache rdepends <dependancy>, and see which of those you've installed.14:49
Hobbseeother effective ways are trying to remove it, and seeing what else it takes with it - assuming it's not a recommends14:49
Hobbseei think there's been something on the debian package of the day thing that does that, though14:49
mrignshmm debsign -S fails...  wrong passphrase, I does not even ask me anymore for it14:50
MagicFabI mean I know how to go in Synaptic and seach in " dependencies "  only, but I' d like to know how to do the same in command line14:50
griffincHi there -- I am working on a merge and was wondering where to put my debdiff when it's done for folks to look at?  should I open a bug on launchpad?14:50
HobbseeMagicFab: then use the rdepends stuff.14:51
mrignsapt-cache depends should also work14:51
MagicFabmrigns, I want that but the other way around ("list of packaages that depend on debsig-verify :" ) - but tx, didn' t know that one14:52
mrignsoh, well, didn't follow the conversation ;P14:53
mrignsnp14:53
MagicFabHobbsee, rdpeends lists dependencies of dependencies etc. recursively but tx.14:54
* Hobbsee thought it only did it one layer deep14:55
MagicFabhmm found a script: http://noisybox.net/computers/debdeps/14:56
* Hobbsee is still havign trouble figuring out if you want the deps, or rdeps of a particular package14:56
mrigns*sigh* I got the same problem with debuild failing to sign packages with seahorse installed, but this time seahorse isn't involved at alle14:56
Hobbseedebuild doesnt sign by default, iirc, unless you specify the key ID.14:57
Hobbseeor sometimes borks at the keys14:57
Hobbseegriffinc: yes, bug, subscribe ubuntu-universe-sponsors.14:57
Hobbseesecond link in the topic, iirc.14:57
norsettoHobbsee: heh, I'm moderated because somebody knows me well ;-)14:58
Hobbseenorsetto: nah, i think something's just borked.14:58
Hobbseenorsetto: although your mail was somewhat harsh, though.14:58
norsettoHobbsee: you think so? It wasn't meant to be14:59
MagicFabdeborphan does the job :D14:59
* MagicFab is now happy14:59
* Hobbsee dont need no deborphan :P14:59
MagicFabtx all15:00
mrignsHobbsee: debuild -S always asked me for my passphrase to unlock my gpg key, the one I specified in my bashrc, but now it just skips the point where I can enter my passphrase15:02
norsettoHobbsee: must be the latino who is buried in me ...15:02
mrignsafter that it complains the passphrase would be wrong15:02
Hobbseemrigns: specify it with -k<yourkeyid> then15:02
Hobbseeon teh debuild15:02
Hobbseenorsetto: must be :P15:03
* Hobbsee --> bed.15:03
mrignsnight15:03
mrignshmm there is no -k for debuild *sigh*15:04
\shmrigns, sure there is15:04
Hobbseemrigns: yes there is.15:04
\shdebuild -S -sa -k<your id>15:04
\shas an example15:04
\shguys, what was the name of the webfrontend for the server administration what soren wanted to add to ubuntu?15:05
StevenKEbox15:05
\shthx...15:05
mrignshmm it's not mentioned in the man page15:05
\shdebuild knows everything of dpkg-buildpackage15:05
mrignshmm i c15:06
mrignswell doesn't work either, still skips the part where I'm prompted for my pass15:06
\shmrigns, debuild -S -ksh@source e.g. works for me.15:07
\shmrigns, sure, that you have a secret key handy? :)15:07
mrignsIt recognises my key and everything15:08
mrignsnow, this really drives me mad15:12
=== propasta is now known as proppy
\shphew...end of business, let's drink a beer15:21
=== elkbuntu_ is now known as elkbuntu
=== ogra1 is now known as ogra
mrignshmm killing gpg-agent solved it15:27
mrignssorry, for bothering15:27
simui downloaded jdk 6 for amd_64 bit but I did not found a plugin folder in the jre directory15:33
simuno java browser plugins for 64bit yet??15:33
simushit wron channel15:33
ograsimu, well http://packages.ubuntu.com/gutsy/devel/icedtea-java7-plugin claims its for amd6415:34
dfilonican someone view this package: http://revu.ubuntuwire.com/details.py?package=wxwidgets2.8 ?15:44
azeemview or review?15:44
dfilonireview15:45
dfilonisorry15:45
griffincDebian has added "Homepage" to its control files -- do we keep this for Ubuntu or remove it?15:45
pochugriffinc: keep it, since dpkg will be merged to support it (if it hasn't already)15:46
griffincpochu: makes sense. thanks!15:47
proppyhi15:49
\shanother bug bytes the dust.....openldap2.2 dapper love15:51
\shok..cu later guys15:51
=== \sh is now known as \sh_away
griffincone more question:  I have specified "hardy" as the distribution and lintian gives me an error 'you've specified an unknown target distribution in your upload debian/changelog file.'  I assume it's because I am running gutsy even though I am using a hardy pbuilder environment?  ok to ignore for now?15:51
proppymaybe lintian@hardy doesn't know hardy yet :)15:52
minghualintian@hardy knows about hardy.15:54
minghuagriffinc: It's fine to ignore.  You can also run lintian in a hardy chroot, of course...15:55
griffincminghua: ah, yes.  thanks -- I'll do that.15:55
proppydpkg -L lintian | xargs grep hardy15:56
proppyseems that gutsy knows hardy as well15:56
proppynorsetto: I've just beat premake.lua !15:56
griffincproppy: interesting.  my lintian message lists warty through gutsy but no hardy.15:57
proppynorsetto: http://hg.juce.aminche.com/rev/7ce48f47eda715:57
proppygriffinc: dpkg -l lintian ?15:58
norsettoproppy: dll to you too15:58
proppyroot@juce:/home/www/juce-1.45/build/linux# ls ../../bin | grep .so15:59
proppylibjuce_debug.so15:59
proppynorsetto:15:59
proppyyeappa15:59
griffinc1.23.32ubuntu115:59
proppygriffinc: mine is ii  lintian        1.23.36ubuntu1 Debian package checker15:59
griffincproppy: yep, you have the hardy lintian pkg16:00
proppygriffinc: :)16:01
proppygriffinc: strange grep hardy in my source.list doesn't show anything16:02
proppygriffinc: maybe it's because of gutsy-proposed16:02
pochuproppy: try apt-cache madison lintian16:03
proppyit's gutsy-backports :)16:03
proppypochu: thanks16:03
proppygriffinc: lintian@gutsy-backports knows hardy16:04
griffincproppy: ok, cool. thanks!16:06
proppynorsetto: my dll is bigger than yours16:08
norsettoproppy: everyone is .... I haven't got any16:09
proppynorsetto:  libjuce.a  libjuce_debug.a  libjuce_debug.so  libjuce.so16:10
proppynorsetto: replyed with the patch upstream16:17
proppynorsetto: waiting for his review16:17
bddebianHeya gang16:42
geserHi bddebian16:42
bddebianHi geser16:42
huatshey bddebian16:44
bddebianHello huats16:48
LaserJockmorning bddebian17:04
bddebianHeya LaserJock.  Did you ever have any luck with any of those machines?17:05
LaserJockyes17:06
LaserJockI mashed them all together17:06
LaserJockand got a 1.7GHz P4, 512MB RAM, 200GB hard drive machine going17:07
LaserJocknow I have to figure out what to do with the leftovers17:07
bddebianheh17:09
proppynorsetto: here ?17:11
norsettoproppy: yes?17:13
geserLaserJock: ebay?17:13
proppynorsetto: what about packaging premake ?17:13
* RainCT thinks: is this a questions contest? :P17:13
norsettoproppy: yes, what about it?17:13
proppynorsetto: it will ease juce makefile hacking, even if my change get accepted upstream17:14
proppynorsetto: and in the end others project could benefit of this17:14
norsettoproppy: I know nothing about premake, is there any reason why is not packed by debian? like license or even technical ones?17:15
proppynorsetto: I've just unpackaged the (zip) tarball17:15
proppylooks like GPL17:15
proppymany of .c files that build very fast17:15
jdonghehehe lol at LaserJock's comment on my MOTU application :)17:16
proppyand a nice executable in the end17:19
proppynorsetto: I'm glad that they don't use premake to generate premake makefile17:19
proppyoups17:19
proppyTHEY ARE !17:19
proppynorsetto: sorry I didn't get your message if there were any17:20
proppy(06:18:06 PM) proppy: norsetto: so the reason why it's not in debian, may be that you actually need premake to regenerate premake Makefile,17:20
=== neversfelde_ is now known as neversfelde
norsettoproppy: heck, must have been at least 10 of them, I m not going to repeat them17:21
proppysorry17:21
proppyjust past them somewhere17:22
proppyhttp://bugs.debian.org/cgi-bin/bugreport.cgi?bug=26286417:22
ubotuDebian bug 262864 in wnpp "ITP: premake -- A build script generator for C, C++, and C#" [Wishlist,Open]17:22
proppythere is an tip17:22
proppyitp17:22
norsettoproppy: just kidding ;-)17:22
norsettoproppy: well, it doesn't seem to be a very warm welcome to that package17:23
proppynorsetto: it's on mentors http://mentors.debian.net/debian/pool/main/p/premake/17:23
norsettoproppy: if its there since august I wouldn't raise your hopes too much17:24
=== \sh_away is now known as \sh
\shre17:27
proppynorsetto: premake: A build script generator for C, C++, and C#, 1201 days in preparation.17:27
proppynorsetto: there've been plenty of preparation on it17:27
norsettor\sh17:28
LaserJockjdong: you deserve it dude17:31
proppynorsetto: let's ask #debian-mentors17:31
norsettoproppy: what is tiddlywiki!?17:33
LaserJocktiddlywiki is cool17:34
LaserJockwiki done mostly in JavaScript17:34
=== \sh is now known as \sh_away
proppynorsetto: a self contained wiki17:35
proppynorsetto: a wiki in a file17:35
proppynorsetto: an html page that can edit itself locally17:35
proppynorsetto: you open the html file, you modify some text in it, you save it to the same html file17:36
proppyanother one ?17:37
proppythe best way to figure what it is, is to try it: wget http://www.tiddlywiki.com/empty.html && firefox empty.html17:39
proppynorsetto: how did you find about it ?17:41
proppyLaserJock: do you use it ?17:41
norsettoproppy: was checking to see if you were in #debian-mentors and found out you were in #tiddlywiki17:43
proppynorsetto: debian-mentors is on irc.debian.org17:43
proppynorsetto: http://lp152438.aminche.com/ tiddlywiki in action17:44
norsettoproppy: yes, I realised it too late :-)17:44
LaserJockproppy: no, but I often look around at wikis17:44
LaserJockespecially personal ones17:44
proppyLaserJock: there is a lot of tiddlywiki derivative, some of them implementing GTD stuff17:45
LaserJockneat17:45
norsettoproppy: ok, so suppose I want to modify it how do I do it?17:45
LaserJockI'm using pmwiki currently17:45
proppyput you name in authors17:46
proppyclick on options17:47
proppyput you username in the box17:47
proppythen click advancedoptions17:47
proppyuncheck 'Hide editing features when viewed over HTTP'17:47
proppyand reload the page17:47
proppythen you will be able to edit and save on the remote url17:48
proppyvia webdav17:48
proppyif you want to edit it locally17:48
proppyi.e: not on http://lp152438.aminche.com/17:48
proppyjust wget http://lp152438.aminche.com/index.html -O norsetto_vs_tiddlywiki.html && firefox norsetto_vs_tiddlywiki.html17:49
proppyand you should be able to edit it locally17:49
norsettoproppy: ok, but, what is different form your everyday wiki?17:49
proppynorsetto: ?17:50
norsettoproppy: ops .....17:50
proppyI'm not sure to understand what you mean17:50
proppyby everyday wiki ?17:50
norsettoproppy: err, can you check that page again?17:50
norsettoproppy: phew .... never mind that17:51
proppyhttp://lp152438.aminche.com/ looks fine17:51
norsettoproppy: I mean, like the ubuntu wiki?17:51
LaserJockit's a lot different17:51
norsettoproppy: moinmoin or whatever is called17:51
LaserJockmoin, mediawiki, etc. require installation and setup17:52
LaserJockmediawiki for instance requires PHP and a DB like MySQL17:52
LaserJockmoin at least doesn't require a DB necessarily but it's still involved17:52
proppynorsetto: the wiki engine, is self contained in the html file17:52
norsettoLaserJock: ok, so its different from the server side, from a user pov its the same?17:52
LaserJocknorsetto: it's different in that it's mostly JavaScript17:53
norsettoproppy: ok, think I got it17:53
LaserJockso it looks different17:53
proppynorsetto: you can't grab a copy of a mediawiki or a moin wiki on your local machine easily17:53
LaserJockand it's got different features17:53
proppynorsetto: you can fork the wiki with cp17:53
norsettoLaserJock, proppy: sure, I get it now17:53
proppynorsetto: you can thought about it as a decentralized wiki17:53
proppynorsetto: just like bzr versus svn17:54
norsettoproppy: well, I just checked the source to see whats in there :-)17:54
proppynorsetto: you can clone the wiki locally edit it, and then someone can poll you changes back17:54
proppynorsetto: are you considering using tiddlywiki for some hot stuff ?18:00
norsettoproppy: hot stuff? You should see my home page ;-)18:01
proppythe launchpad one ?18:03
davromaniakis somerville32 here ?18:05
norsettoproppy: no, the real one, red hot ....18:09
proppynorsetto: url !18:09
proppyoops18:10
proppyseems that I've overwrited a package on mentors18:10
proppy:(18:10
norsettoproppy: I'm not so sure you can survive it ... its only for a mature audience18:10
bddebianproppy: It's not biggie :)18:11
bddebianErr no18:11
proppynorsetto: nothing can beat cuteoverload.com18:11
proppydoesn't understand my dput didn't reject me18:11
bddebianproppy: I'm just trying to make sure something actually gets uploaded to Debian :-)18:11
proppyaaaa18:12
proppyit's the same bdd*18:12
proppyI've just realised it :)18:12
bddebianYeah, they made me change my name over there ;-P18:13
proppyglad to see someone in between18:13
proppy:)18:13
norsettobddebian: so, you are bdubuntu there?18:14
bddebiannorsetto: Hahah, yeah I should have ;-P18:16
=== Tonio__ is now known as Tonio_
txwikingerDas every package for ubuntu get the -0ubuntu1 suffix?18:27
txwikingerDoes18:27
jdongit depends on the origin of the packagesl18:28
jdongpackages directly pulled from Debian without any changes retain their Debian version18:28
txwikingerif the package itself is the first time it is packaged as a .deb18:28
jdongpackages where Ubuntu has made changes get version suffic <debian_version>ubuntu118:28
jdongif there is no previous debian package it's based on, 0ubuntu1 is used18:29
txwikingerthank jdong18:29
txwikingerI have another question18:29
txwikingerwhat is if a copyright file in the original package is missing18:29
txwikingerbut there is copyright statement in another file18:29
jdonghmm, good question; I'm not sure how to handle that, perhaps someone more knowledgeable can give an answer18:30
bluekujatxwikinger, actually every upstream tarball should contain a copyright file18:30
bluekujatxwikinger, like COPYING18:31
txwikingerwell some don't, but have a statement in i.e README18:31
bluekujatxwikinger, and anyway every license should reported in debian/copyright18:31
txwikingershould I just create one then18:31
jdongI've seen some that just say "Licensed under GPL" in some documentation18:31
jdongI'm not sure how to handle those cases18:31
bluekujatxwikinger, and if differents just list file-->license18:31
txwikingerI have create a debian/copyright18:32
jdongIdeally, see if you can get upstream to more explicitly license their tarball ;-)18:32
bluekujatxwikinger, of course...18:32
txwikingerI don't know if there needs one also in the package root18:32
bluekujatxwikinger, without that the package cannot be archived18:32
bluekujaand accepted18:32
desertcAre the MOTU involved with the Update Manager package releases?18:33
bluekujatxwikinger, plus every source file should contain license headers18:33
bluekujaif not, ping upstream18:33
bluekuja;)18:33
desertcI mean to say, involved with deciding what gets pushed out?18:33
bluekujadesertc, I would say core-devs18:33
desertcTY!18:33
bluekujadesertc, that package is in main actually18:33
jdongdesertc: ultimately that's the archive manager's call18:33
=== norsetto is now known as norsetto_limbo
bluekujadesertc, get to #ubuntu-devel18:34
bluekujaand ask there18:34
desertcAlready there.18:34
bluekujaperfect then :)18:34
bluekujaok, I'm off18:34
bluekujahave a good evening18:34
desertcThanks again18:35
txwikingerbye bluekuja18:35
somerville32davromaniak, Hi18:37
somerville32I'm here18:37
davromaniaki saw you've proposed youtranslate upgrade in revu18:38
davromaniakit's good, but I've declared a bug, and I'm working on it (correcting minor mistakes in the package)18:39
BlueDevilhi guys18:59
BlueDevilwhere is the proper place to report that security.ubuntu.com is giving 403 - Forbidden errors?18:59
jdongBlueDevil: it's a known issue18:59
jdongBlueDevil: the Samba update has been disabled due to a few regressions spotted19:00
jdongas a safeguard users are denied access to these broken updates19:00
jdongc.f. bug #16304219:00
ubotuLaunchpad bug 163042 in samba "nmbd crashes after routine Dapper upgrade" [Critical,In progress] https://launchpad.net/bugs/16304219:00
BlueDevilok19:01
BlueDevilthanks19:01
somerville32davromaniak, okay.19:11
somerville32davromaniak, What is the bug number?19:11
davromaniakBug #15924919:13
ubotuLaunchpad bug 159249 in youtranslate "[needs-upgrade] youtranslate 1.1.9 => 1.1.10" [Undecided,In progress] https://launchpad.net/bugs/15924919:13
pwnguinso what's a good runtime debugger for gtk applications?19:24
pwnguinpreferably something more than gdb19:24
azeempwnguin: nevimer, maybe?19:25
pwnguinpackage not found19:27
azeempwnguin: http://home.gna.org/nemiver/19:28
azeemnemiver*19:28
pwnguinah19:28
* Kmos gots miro 1.0 working with python 2.5 :)19:49
jdong:)19:49
Kmosjdong :)19:51
=== norsetto_limbo is now known as norsetto
dfilonisomeone can review this package: http://revu.ubuntuwire.com/details.py?package=wxwidgets2.8 ?19:56
=== jpatrick_ is now known as jpatrick
gnudleshello19:57
gnudlesI'd like to know when will you create gimp 2.4.1 package...19:58
LordKowhttps://bugs.launchpad.net/ubuntu/+source/exaile/+bug/163181 debian maintenance for this package seems to be almost non-existent20:03
ubotuLaunchpad bug 163181 in exaile "[hardy] New upstream release 0.2.11.1" [Undecided,New]20:03
somerville32LordKow, I'll update it.20:04
minghuagnudles: It's better to contact previous uploaders of wxwidgets2.8 instead of generally asking for review, IMO.20:05
gnudlesupdate the gimp package to version 2.4.120:05
LordKowis gimp a universe/multiverse package?20:05
_MMA_no20:06
gnudlesI didn't asked for review..20:06
somerville32LordKow, Can you upload an interdiff?20:06
LordKownever made an interdiff there a deb helper script for it?20:07
somerville32No.20:07
somerville32apt-get install interdiff20:07
somerville32interdiff the two diff files generated when you build the source package20:08
minghuagnudles: Sorry, speaking to wrong person...20:08
somerville32There is a flag you can use so you don't have to decompress them by hand.20:08
minghuadfiloni: It's better to contact previous uploaders of wxwidgets2.8 instead of generally asking for review, IMO.20:08
LordKowoh i see20:08
gnudlesa bot?20:08
LordKowokay i'll run interdiff against the 0.2.11 diff and my 0.2.11.1 diff and attach it20:09
somerville32LordKow, Thank you muchly20:09
gnudlesbut gimp is based on GTK, not on wxwidgets....20:10
gnudlesjust update it... please, It's very important package...20:10
LordKowwhat would be the standard way to name a file with the output of interdiff?20:11
_MMA_Hey guys. A idea to blow off some steam came out of UDS that Ive been working on. Just a little game server we can run around in.20:13
_MMA_The development page: https://wiki.ubuntu.com/CommunityGameServer and the "Solid info" page: https://help.ubuntu.com/community/CommunityGameServer (both a work in progress) I have 2 games done now.20:13
_MMA_If you wanna help us test the Warsow server now hit me up in PM.20:13
LordKowi didnt use debdiff, let me do that. i think it will produce the same results but its best to do it debian style whenever possible20:15
minghuaLordKow: interdiff is preferred over debdiff because debdiff would include all upstream changes as well, which we don't want.20:19
LordKowokay well i uploaded a giant selection of things20:19
LordKowdebdiff, interdiff, orig src, dsc... diff gz20:19
LordKowgo for it :P20:19
somerville32jdong, come for a visit to #xubuntu-devel svp :P20:20
somerville32LordKow, ermm...20:21
LordKowi wasnt quite sure what to do with the debian directory because apparently the exaile devs try to maintain it too20:22
somerville32LordKow, Can you do a -p1 with that interdiff20:23
somerville32The interdiff is not useful because it shows both copies of everything because the top directory name is different20:24
=== cprov-lunch is now known as cprov-away
somerville32the -p1 will ignore that so that we get a proper debdiff20:24
somerville32*interdiff20:24
LordKowdone20:25
somerville32LordKow, Did you upload it?20:27
LordKowhttps://bugs.launchpad.net/ubuntu/+source/exaile/+bug/163181/comments/720:27
ubotuLaunchpad bug 163181 in exaile "[hardy] New upstream release 0.2.11.1" [Wishlist,New]20:27
somerville32Much better :)20:27
gnudlesI checked, Gimp is a universe package..20:35
LordKowMaintainer: Ubuntu Core Developers20:35
gnudlesyes20:35
gnudlesbut It was in the list of the universe packages..20:36
gnudlesso where can I get them?20:36
LordKowthere was a site that does backports for ubuntu outside of ubuntu20:37
LordKowlet me find the link, im pretty sure they have gimp 2.4.120:37
LordKowhttp://www.getdeb.net/release.php?id=176020:37
LordKowi believe they only package 386 debs so you will need to build the source if you are on another arch20:38
LordKowi would imagine gimp 2.4.1 will get into hardy. a final release will always have much higher priority over an RC :P20:38
minghuagnudles: Gimp is in main, not universe.20:39
LordKoweven if its after the appropriate freeze20:39
LordKowif gutsy has an RC of 2.4.1 it will likely be updated there too20:39
gnudlesbut what about al the other users?20:40
minghuaGimp in gutsy won't be updated unless there is an important bug.20:40
gnudlesok...20:40
minghua...which exists in RC but fixed in 2.4.1, that is.20:40
LordKowgnudles, what makes the final release much more important than the RC's?20:40
gnudlesbut the RC is for 2.4.020:41
gnudlesnot for 2.4.120:41
LordKowah, okay well gutsy will likely not see 2.4.1 thats just how ubuntu works (unless there is a major bug fix)20:41
somerville32LordKow, Why did you redo rules?20:42
LordKowit will likely be in backports20:42
LordKowsomerville32, i didnt i copied it from upstream. i wasnt quite sure what to do with the debian folder because exaile maintains one20:42
nenolodif anyone asks about backports for audacious 1.4, i already did it20:42
gnudlesI'll check the change log..20:42
nenolodso someone could take my source and do an official one :P20:42
LordKowlook at the orig src and you will see a debian folder20:42
LordKowi guess i should have diff'd it to make sure we (ubuntu) didnt put in any ubuntu-specific things to the rules20:43
somerville32LordKow, right.20:44
LordKowour rules though are almost always verbatim to debian (are they not?)20:44
somerville32LordKow, You didn't look?20:44
somerville32You cut out a lot of stuff20:45
gnudlesI think it's quiet important bug fixes20:45
gnudleshttp://developer.gimp.org/NEWS-2.420:45
somerville32We don't use upstream's  debian/ directory20:45
LordKowwell as i said, make sure you look at the debian folder because im not quite sure what to do when the maintainers of the software also maintain a debian folder20:45
LordKoware we supposed to merge with them? or keep our own?20:45
somerville32Well, we don't just replace our stuff with their stuff20:46
gnudlesanyway, thanks..20:48
LordKowokay i jacked up the rules, i accept it ;)20:49
frafuHello, could anybody please tell me whether the people that review the packages in REVU, do review them with the available patches applied, or before applying the patches? (I am asking because the package that I am talking about does not have complete copyright and license information)20:50
LordKowhonestly somerville32, you should just do the upgrade yourself its basically a 1 minute max deal. the most work would be merging upstream rules with ours20:50
frafuThe patches complete that information.20:51
sistpotyhi folks20:54
LordKowi really think software developers should not include debian in their original source code let debianization happen downstream at the appropriate level20:54
bddebianHeya sistpoty20:54
sistpotyhi bddebian20:54
bddebianfrafu: I'm not sure I understand your question but debian/copyright should be populated regardless of patches20:55
minghuafrafu: Where is this patch about copyright/license information coming from?20:58
frafubddebian: I am talking for example about the missing gfdl license text; the debian folder is ok20:58
siretarthey sistpoty, hi emgent!20:58
sistpotyhi siretart20:58
emgenthey :D20:59
frafuI am a maintainer of the package; I added the patch to not raise the version number20:59
frafudebian copyright is ok, but the manual has an error, so that it does not show the license; moreover, the file that contains the complete license text is missing before applying the patch21:03
bddebianI would say that is generally frowned upon because upstream should be providing a license.  How do we know you aren't just sticking whatever license you want in there? :-)  Of course I am no where near an expert on licensing issues21:06
frafubdebian: I am one of the maintainers; moreover, I am the guy who wrote the manual 8-)21:09
frafuI am upstream21:10
somerville32bluekuja, Hey. Is there any reason why you changed the versioning for exaile by dropping the debian version?21:10
somerville32bluekuja, Okay. never mind.21:11
somerville32bddebian, Should I remove debian/ from the orig tarball or just endure the added delta?21:12
bddebiansomerville32: Sorry, for what ?21:13
bddebianfrafu: So add the file like it should be :)21:13
somerville32bddebian, For a package :P21:13
somerville32bddebian, If upstream ships a debian/ directory21:13
bddebiansomerville32: Get upstream to remove it :-)21:13
somerville32bddebian, Yes but for the time being :P21:13
bddebianProbably should repack it but I'm never sure21:14
somerville32bddebian, Would you upload if I didn't?21:14
frafubddebian: if I add the file, the source tree does not correspond anymore to the tarball we produced for the release. Will that not be a problem? (we forgot to add the file with the gfdl text in the release)21:17
slangasekfrafu: I would suggest using the pristine tarball from the upstream release and add the licensing info in the diff only21:18
slangasekfrafu: there are lots of cases where we effectively have to trust the packager's statements about the license, so this isn't really a big deal21:19
=== `23meg is now known as mgunes
minghuafrafu: Are you talking about the content of the GFDL text here?  In that case I think you don't even need to include that, just saying which files are licensed under GFDL in debian/copyright, and referring to /usr/share/common-licenses/GFDL-1.2 should be enough, IMHO.21:21
bddebianfrafu: slangasek would certainly know more than me :)21:24
bddebiansomerville32: I might but I'm a moron ;-)21:24
draremso i have glade and anujta, is that all i need for gtkmm or is there another recommended route to go?  I want to make cross-compatible applications (using the ftp lib stuff) and a nice gui?  I notice resizing controls in glade is a pain or non-existant21:24
LordKowbddebian, have some self-esteem :P21:29
frafuslangasek: I just tried: debuild -S copies the license from the in the ...diff.gz; so everything should be ok!?21:30
frafuthanks to all for your help21:32
Kmoshttps://wiki.ubuntu.com/PackagingGuide/Basic#ChangingOrigTarball21:32
LaserJockLordKow: he can't, it's impossible21:33
sistpotyKmos: if upstream changes the orig tarball it's not much of a problem imho, see the rationale given there21:34
bddebianLaserJock: You got it :)21:34
Kmossistpoty: this is for somerville3221:34
=== TreMobyl is now known as Solarion
sistpotythen maybe you should add a highligh for him, Kmos ;)21:35
KmosI think the orig tarball even with debian dir inside it, don't need to be changed. just report a bug upstream to remove it in the next release.21:35
sistpoty+t21:35
Kmossistpoty :)21:35
LordKowas long as our orig tarball matches debians i think we're fine21:35
LordKowthings get very difficult if our source tarballs are different than debians, especially when it comes to merging.21:36
LaserJockyes21:36
LaserJockI did that once21:36
LaserJockit's no fun21:36
sistpotyhah, and then you do everything correctly, where upstream provides a .zip and even have that get-orig-source thingy and end up with a different tarball from your sponsored package in debian (happened to me *g*)21:37
=== Martinp24 is now known as Martinp23
sistpoty(and I wrote that changing the orig tarball section in the first place *g*)21:38
LaserJockI forgot to remove the build stamp21:38
frafukmos: you link says that I should not change the tarball (if I get it right; I am rather new to this) ;-)21:38
LordKowthe latest debian unstable of exaile does not have the debian folder in its orig src21:38
LaserJockso it somehow got into my .orig.tar.gz21:38
LaserJockthat's was a real "doh!" moment21:38
Kmosfrafu: yes, but there are situations that you can change.. read more :)21:38
LordKownow, im not sure if the exaile developer added the debian folder to his latest src or if debian is removing it. regardless i think our orig src should not have it.21:39
LordKoworig src tarball should have no debianization in it21:39
KmosLordKow: mail the debian maintainer to know about it :) you already reported upstream a bug to remove it from tarball ?21:39
frafuLordKow: what do you mean by: "as long as our orig tarball matches debians"21:39
LordKowfrafu, if our src tarball is different than debians (same version of the package) then its difficult to merge with upstream even if its just releasing a new patch based on the same src21:40
LordKowdebian does everything against the src tarball, so do we. if the src tarballs are different than debian applied patches may fail against our src, for instance.21:41
sistpotyfrafu: if a package is both in debian and in ubuntu and we introduce a new upstream version and later debian does the same (and introduces a different orig.tar.gz than we have), it ends up in the manual merge section21:41
somerville32http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-specifying_versions21:42
somerville32I'm a little fuzzy about the XB-*21:42
Kmossomerville32: with XB- you can remove debian/pyversions21:42
somerville32XS goes in the first paragraph21:43
somerville32XB in the second, right?21:43
Kmosyes21:43
somerville32 So I can ignore dpkg-genchanges: warning: unknown information field 'Xb-Python-Version' in input data in package's section of control info file ?21:43
Kmossomerville32: no, you can add it to your debian/control21:44
KmosPackage: startupmanager21:44
KmosXB-Python-Version: ${python:Versions}21:44
Kmosfor example21:44
Kmosin the second21:44
KmosXS- goes after Standards-Version: 3.7.221:44
somerville32I have XB- in the second paragraph21:45
KmosXS-Python-Version: current21:45
somerville32I have XS-Python-Version: current, >= 2.421:45
somerville32The pyversions had 2.4-21:46
Kmossomerville32: http://svn.debian.org/wsvn/python-apps/packages/startupmanager/trunk/debian/control?op=file&rev=0&sc=121:46
Kmossomerville32: it's a package for hardy ?21:46
LordKowKmos, https://bugs.launchpad.net/ubuntu/+source/exaile/+bug/16318121:47
ubotuLaunchpad bug 163181 in exaile "[hardy] New upstream release 0.2.11.1" [Wishlist,New]21:47
LordKowignore all my attach's they're bogus21:47
DaveMorriscan someone please review my small package http://revu.tauware.de/details.py?package=cpptest21:48
somerville32Kmos, Yes.21:48
LordKowwith regards to exaile, the question as to whether the debian folder should be included in the orig src tarball is very important. what will be done to it upstream in sid?21:48
KmosLordKow: +Section: universe/devel , why universe/devel ?21:49
somerville32Kmos, LordKow said to disregard his work. I'm doing it now.21:50
Kmossomerville32: nice :) i'm not a motu, i just try to hlep21:50
Kmoshelp21:50
somerville32Kmos, He used the upstream debian directory21:50
LordKowyea there are actually a lot more issues with exaile than i originally thought. needs quite a bit of review which should be left to the MOTU team :)21:51
bddebianShould be done by the damn Debian maintainers21:51
LordKowexactly21:51
sistpotyDaveMorris: give me a little bit time, and you'll get a review ;)21:51
LordKowi was going to leave it out of ubuntu but the debian maintainer is slacking21:51
bddebianHave you poked them?  There is a maintainer and co-maintainer and they did upload in 200721:52
Kmosi've reported a bug to BTS about exaile new upstream version21:52
LordKowBTS?21:52
Kmoslet's see if lazy maintainer do something :)21:52
DaveMorristhanks, I'll be here for a bit21:52
LordKowKmos, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=45154921:52
ubotuDebian bug 451549 in exaile "New upstream version 0.2.11.1" [Wishlist,Open]21:52
somerville32Well, I'm going tto finishh tisu p and we can meerge/sync latre. :]21:52
KmosLordKow: exactly21:52
LordKowthats you?21:52
Kmosyeah21:53
LordKowoh cool ;p21:53
somerville32LordKow, Is he some demi-guru? :P21:53
LordKowi only brought this down to the ubuntu level because i noticed that 0.2.11 was never put into sid so i figured it was not being maintained well at all21:53
* Kmos not gutu21:54
Kmoslol21:54
Kmos*guru21:54
bddebianLordKow: It's OK, I think we have already jumped Debian versions anyway but poking the maintainer is the "right thing to do"21:57
LordKowyea we did with 0.2.1121:58
LordKowbasically what im saying is we need to keep our version as close to debians non-existent version so that when/if debian updates exaile we can easily merge with it21:59
LordKowjust 1 more package that can be merged more easily without a lot of work22:00
sistpotyDaveMorris: please don't override lintian22:00
somerville32LordKow, You obviously don't know bddebian. He demands hard merges.22:00
LordKowk :P22:00
somerville32Only ones he does.22:00
sistpotyDaveMorris: though I haven't test-built it yet, it seems weird to me to ship a shared object in a -dev package22:00
DaveMorrissistpoty: I thought you where ment to for a good reason22:01
sistpotyDaveMorris: so what's the reason to do so22:01
DaveMorrissistpoty: its for unit testings and I didn't see the point of having a libcpptest and a libcpptest-dev22:01
sistpoty+?22:01
DaveMorrisas you'll only usee the -dev version22:01
Kmosbug 16320822:02
ubotuLaunchpad bug 163208 in exaile "Please remove debian directory from tarball" [Undecided,New] https://launchpad.net/bugs/16320822:02
Kmos:)22:02
sistpotyDaveMorris: so there is no real point in linking to the shared library?22:02
DaveMorrisonly as a programmer  who will need the header files etc22:02
DaveMorrisits the same as cppunit I believe22:03
sistpotyDaveMorris: but a progammer might want to use shared linking against libcpptest? or would he only be interested in static linking?22:04
sistpoty(he/she of course to be political correct)22:04
LordKowwell Kmos, somerville32 is working on the new version :P22:04
LordKowi think he is aware of it22:04
DaveMorrisI personally link using the shared object in my programming22:04
bddebiansistpoty: You are already looking at cpptest?22:04
sistpotybddebian: yep22:04
bddebianAh good I'll stop then :-)22:05
sistpotyDaveMorris: then it makes sense to build a shared library as well (I guess you know the library packaging guide?)22:05
DaveMorristhere should be a shared object lib in that package22:05
sistpotybddebian: hehe22:06
LordKowwhats the best/easiet way to report bugs in the debian system?22:06
sistpotyDaveMorris: but if s.o. wants to link against it, it should use the normal library packaging scheme (which means that a shared object should go in a package with the name of the soname)22:06
bddebianLordKow: Build a new package, upload to mentors and ping the maintainer pointing them at the new package :_)22:07
DaveMorrissince there  is no point  having it as a seperate package IMO since it'll only ever be used by people using the -dev package22:07
bddebianOf course that did work for me with valknut or pybliographer...22:07
LordKowthnx22:07
bddebianErr did NOT work for me :)22:07
sistpotyDaveMorris: let me think about this for a few minutes (while I'm out for a smoke...)22:07
bddebianGah WTF was I thinking starting a build on an 8Mb source package when I want to go home :(22:09
LordKowokay well if debian does exaile upstream correctly according to their specs, then debian folder shall not be in the src tarball :)22:10
somerville32bddebian, Just walk away :P22:10
bddebianheh22:12
jdongsomerville32: NEVER what if it FTBFS'es as soon as you leave??22:12
somerville32jdong, Than you find out when you come back :]22:12
bddebianI didn't screen and I'm ssh'd to home so I can't walk away :(22:13
DaveMorrisstart it in a screen and reconnect when you get home22:13
LordKowbddebian, now if you're really unlucky the build will fail at the end :P22:13
LordKowuse ccache? heheh22:13
jdongLordKow: heh idn, I wouldn't trust a build done in ccache for verification purposes22:14
jdongI recall from Gentoo days there were some pretty weird effects with ccache at times22:14
LordKowtrue22:14
LordKowyea jdong, i dont use ccache for that reason and the fact that i dont have enough disk space22:15
jdongthough, yeah, it's the most irritating thing ever when a build fails at one of the last steps :D22:15
LordKowthe problem with Gentoo is its so user specific that its hard to distinguish true bugs from jacked up systems22:15
jdongLordKow: agreed -- trying to isolate user error from a bug report is the hardest thing ever22:16
jdongI recall bugs being posted where the user has a 4-line CFLAGS variable22:16
LordKowLOL22:16
jdonglol no joke :)22:16
bddebianLordKow: Nah it died on build-deps so I got lucky :-)22:16
sistpotyDaveMorris: I guess what you want to do is to ship the shared object as "private" under /usr/lib/<packagename> in the -dev package. that way only people having the -dev package can link against it and you don't need to care about library packaging22:16
LaserJockjdong: I had one of those ;-)22:16
LaserJockat least 3 lines22:16
LordKowa mile long USE= flags are never good either22:17
DaveMorrissistpoty: how do you do that?  I've not heard of it beforre22:17
jdonghttp://bugs.gentoo.org/show_bug.cgi?id=7407222:18
jdong*THAT* is the one22:18
ubotubugs.gentoo.org bug 74072 in Unspecified "ld errors" [Trivial,Resolved: wontfix]22:18
sistpotyDaveMorris: move it around in debian/rules, or change the upstream make files (and probably adjust whatever needs adjusted, e.g. a *.pc file)22:18
bddebianusually configure --libdir will do it or you may need -rpath22:18
sistpotyor that ;)22:19
LaserJockjdong: that's quite funny22:20
jdongLaserJock: I'm shocked nothing else broke for him :)22:20
DaveMorrisso instead of installing it to /usr/lib install it to /usr/lib/cpptest/22:20
LordKowhahaha those CFLAGS are ridiculous22:21
* DaveMorris looks at how to do that in cdbs22:21
LordKowi stick with -march=k8 -O2 -pipe22:21
sistpotyjdong: lol, I've always thought that gentoo encourages to use -f-omg-superfast *g*22:22
jdongLordKow: likewise, the most I optimize is a -march close to my arch, -O2, -pipe, and sometimes -fomit-frame-pointer22:23
LordKowhttp://bugs.gentoo.org/show_bug.cgi?id=74072#c2 <-- LOL22:24
jdongand I don't even like applying -fomit-frame-pointer across the system22:24
ubotubugs.gentoo.org bug 74072 in Unspecified "ld errors" [Trivial,Resolved: wontfix]22:24
slangasek(.oO -O99 -pipe -hash -smoke-it)22:24
sistpotyhaha22:24
jdongslangasek: sadly I have seen -O99 suggested on Gentoo Forums as future proofing....22:24
jdongand people do rebuild all the packages on their system everytime GCC/glibc gets a minor version bump22:25
jdongI cringe to think about the carbon footprint of Gentoo :D22:25
sistpotyhm... I could abuse university compution power, but I'm too lazy :D22:25
LordKow4th largest supercomputer in the US about a block from me... >:)22:25
LordKowthat would help out ubuntu's build queue quite a bit22:26
somerville32Slowest computer in the world, 30cm from my feet22:26
RainCThi22:26
bddebianLater gang22:26
sistpotycya bddebian22:26
LordKowlater bddebs22:26
RainCTare PNG's on /usr/share/pixmaps required to be 48x48 or are 32x32 also ok?22:27
RainCT/me would prefer not to use uuencode22:27
sistpotyLordKow: nothing of that scale around here, but if it were I'd set up a heat pipe directly to my office (it's freaking cold in there in winter time)22:27
LordKowhm time to lurk the bug reports looking for a simple bug to fix22:27
jdongbug 163185   <-- is hell freezing over yet?22:27
ubotuLaunchpad bug 163185 in ubuntu "ubuntu freezes completely (all graphics and mouse) when executing shell ascii forkbomb" [Undecided,Invalid] https://launchpad.net/bugs/16318522:27
LordKowheh sistpoty you need my dual opteron desktop. one of the first revisions and they run like a furnace22:27
sistpotyhehe22:27
LaserJockman, that sounds good22:28
LaserJockI don't want to  have to pay for the electricity bill thoug22:28
LaserJock+h22:28
jdongLOL @ reproducing steps22:28
jdong(1) open shell (2) type in forkbomb (3) computer freezes22:28
sistpotywe need to shutdown everything unused over christmas, due to 1) electricity bill but much more due to 2) heating costs *g*22:29
Fujitsujdong: Blink.22:29
FujitsuThat has to go on one of the top 10 stupid bug lists.22:29
LordKowjdong, that actually does bring up a good point. should ubuntu be setting the max process limit?22:29
jdongLordKow: IMO no... it should make it easy, however, for users to set one via the User and Groups applet22:29
Fujitsujdong: I like your response: `One should avoid typing in forkbombs into the terminal if one does not want to forkbomb his computer.'22:30
sistpotyLordKow: it should and it does (as far as i can tell right now)22:30
jdongFujitsu: hehe I tried to disguise a bit of humor in there :D22:30
LordKowi might as well link that bug report to every linux distribution known to man :P22:31
jdongsistpoty: does it? I don't see it on Gutsy at least22:31
sistpotymom.22:31
jdongthat was the first vulnerability I found on my shared shell setup :)22:31
sistpoty!pastebin | sistpoty22:31
LordKowsistpoty, i dont think it does22:32
keescookwe do set a max process limit.22:32
jdongFujitsu: next we'll get "All files are deleted when executing rm -rf command" and an argument why Ubuntu should have an undo/cancel command for that :D22:32
keescookit's based on available physical memory (this is the default for modern kernels)22:32
LordKowkeescook, where?22:32
keescookLordKow: ulimit -u22:32
jdongkeescook: it's not enough to stop a forkbomb, is it?22:32
sistpotythat's what I get: http://paste.ubuntu-nl.org/44816/22:32
jdong818022:33
LordKowah okay, its dynamic22:33
keescookjdong: since a forkbomb won't every stop, no.  ;)22:33
LordKowor not22:33
sistpoty(though my .zshrc my interfere *g*)22:33
slangasekjdong: it may not be enough to prevent the fork bomb from spinning in an infinite loop trying and failing to fork more processes22:33
slangasekbut it will limit the total number of processes forked22:33
jdongslangasek: right; I doubt a system with 5000+ spinning processes will be all that interactive!22:34
keescookit's hard to protect someone from themself.  ;)22:34
LordKowof course if we took this far we could create some sort of shell wrapper script that parses the command to check for this sort of thing before initiating the command22:34
keescookin non-desktop shared environments, admins will usually set nproc much lower22:34
keescookLordKow: sure, but then the griefer would just adjust the syntax a little.22:35
LordKow"Running command <command> may lock your system, continue?"22:35
FujitsuEw.22:35
jdongLordKow: You are executing a command. Cancel or Allow? :)22:35
jdongThe command "oowriter" may cause your system to become slow or unstable. Cancel or Allow?22:36
* jdong ducks22:36
somerville32lol22:36
sistpotyhaha22:36
LaserJockCancel! Cancel!22:36
Fujitsus/may/will/22:36
LordKowit would check the syntax and thats all22:36
keescookbash: function call loop detected, aborting.22:36
slangasekjdong: well, you can nice the users who are inclined to do stupid things with their shells, and then it'll be nice and interactive for everyone else. ;)22:38
jdongaren't there people who have tried to write heuristic forkbomb detectors/preventers for Linux/OpenBSD?22:38
jdongI recall seeing a kernel patch relating to that before22:38
LordKowbug 16318822:43
ubotuLaunchpad bug 163188 in yelp "spelling and information issues " [Undecided,New] https://launchpad.net/bugs/16318822:43
LordKowdoes anyone know where exactly these typos are?22:43
LordKowoh i found it22:44
RainCTwhree should html documentation be installed?22:46
RainCT*where22:46
sistpotyDaveMorris: any reason to ship an older version of cppunit than available on sourceforge?22:46
sistpotyRainCT: /usr/share/doc/<packagename>/html22:47
RainCTok, thanks sistpoty22:47
DaveMorrismy package is cpptest, not cppunit22:49
sistpotyDaveMorris: sorry, of course cpptest22:49
sistpotyDaveMorris: hm22:50
sistpotyDaveMorris: sorry, been clicking on the wrong links22:50
DaveMorrissistpoty: I'vee just up loaded a revised version with you suggestions22:51
DaveMorrislinitan warrns about pointless calls to ldconfig but I have no idea how to stop them22:51
RainCTdo *.install files accept regex?22:52
slangasekRainCT: I believe they only accept globs22:53
RainCTglobs?22:53
slangasekRainCT: aka, "*"22:54
RainCTah ok22:54
jdongglobs: Regex Home Basic Edition :)22:55
RainCTso if I want to install everything in folder "data" that doesn't start with "html*", I've to copy everything and then remove the html* files?22:55
sistpotyDaveMorris: where can I actually download cpptest? (debian/copyright refers to the cppunit sf page, and I can't find a link there)22:55
=== Martinp24 is now known as Martinp25
DaveMorrissistpoty: you missed that I linked to the cppunit page when it sould of been cpptest22:58
DaveMorrishence why you though I had an old version22:58
DaveMorrislet me fix it22:58
sistpotyDaveMorris: ah, ok.22:59
DaveMorrishttp://cpptest.sourceforge.net/ anyway22:59
DaveMorrisI hate it when I make stupid mistakes like that23:01
sistpotyso do I, and I tend to make lot's of these23:02
DaveMorrishence the revu process I guess :)23:03
sistpotyDaveMorris: btw.: the patch you're adding via debian/patches about the .pc file: that's a new file rather than a change to an old one, right?23:03
DaveMorrisyeah new one23:03
DaveMorrisI was told before thats the better way to do it23:03
sistpotyDaveMorris: I'd just put it under debian and include it in the .install rule, but both have its benefits (and it's not wrong to do it either way)23:04
LordKowhttps://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/163076 is this something i can do or is there some automated system for this?23:05
ubotuLaunchpad bug 163076 in multipath-tools "New upstream version available" [Undecided,New]23:05
LordKowbasically just needs an upstream merge23:06
LordKowi guess i should have checked if this is even a universe package :P23:06
LordKownope, k nvmnd23:06
sistpotyDaveMorris: if I'm not mistaken the ldconfig call is generated from dh_makeshlibs (you could of course export DH_VERBOSE=1 in debian rules to get the details from the build (log).) However I'm not sure how to make cdbs not call dh_makeshlibs.23:07
DaveMorrisam I allowed to leave those calls there?23:08
DaveMorrisdh_makeeshlibs does do it as I learn't that earlier23:08
sistpotyDaveMorris: well, these are unneeded... if this is the only issue, I'd say why not (since a regular user won't install the -dev package and thus won't have delays in installing/upgrading)(23:10
sistpotyDaveMorris: of course if you want to dig, you could try to see if dh_makeshlibs can be tweaked into not adding that call for a known shared object (by looking at the man page first, and in doubt at the code)23:10
norsettosistpoty: there is a flag you can pass in cdbs to avoid dh_makeshlibs inserting a ldconfig call in the maintainers script. Is that usefull?23:11
sistpotynorsetto: sure, I guess DaveMorris would be interested ;)23:12
slangaseker, why are you having to override dh_makeshlibs then?23:12
sistpotyslangasek: building a shared object in /usr/share/<packagename>/23:13
slangasek...23:13
slangasekthat's an FHS violation23:13
sistpotyslangasek: where would these go then?23:13
slangasekI don't know, what is it?23:13
slangasekbinary objects don't belong under /usr/share, though, because /usr/share is for arch-independent data23:14
slangasekif you're ending up with auto-generated shlibs for the file, that probably indicates the object has an SONAME23:14
DaveMorrisits going into /usr/lib/<package namee>/23:14
sistpotyslangasek: testing framework for c++ (cpptest)23:14
norsettosistpoty, davemorris: its DEB_DH_MAKESHLIBS_ARGS_<package> -n23:14
slangasekwhich means it's either a library and belongs in /usr/lib, or it's not a library, should be stowed under /usr/lib/<package name>/, and shouldn't have an soname23:14
sistpotyslangasek: yes it does, but it wouldn't be of much use for anyone since it's a testing framework (you wouldn't want to link a binary against it, unless you're running a test suite and have the -dev package installed anyways)23:15
norsettog'night all23:16
slangaseksistpoty: then why does it have an soname?23:16
sistpotyslangasek: that's of course a good question... which I guess goes along the line of why does a soname not change if the compatibility changes *g*23:16
RainCTDoes anyone know why    install/lighyears:: rm -f debian/lightyears/usr/share/games/lightyears/data/html*    isn't removing the files that start with "html*" that were copied there because of an *.install file?23:17
DaveMorrisfor the logs it's actually DEB_DH_MAKESHLIBS_ARGS_<pkgname> := -n23:19
sistpotyslangasek: of course if you believe that if upstream provides a soname it should get library packaging style, (or otherwise if it's shipped as /usr/lib/<packagename> packaging should remove the soname), I'll be happy to know about as I'd really like to know the best practice there23:20
slangaseksistpoty: well, my point is that dh_makeshlibs is a very mature tool which always DTRT for me, so if you're seeing it do something unexpected, question the upstream library first23:21
slangasekrather than trying to force it to not be invoked for a given packgae23:21
sistpotyslangasek: sure, the soname is there (and upstream seems to have gotten it right). however the lib doesn't seem to make much use to link a regular binary against, so what to do then?23:23
RainCTgood night23:24
slangaseksistpoty: it exists for the purpose of linking against, doesn't it?23:25
slangasekif so, why make it harder to link things against it by moving it out of /usr/lib?23:25
sistpotyslangasek: hm... good point, and I guess that's where I wouldn't know how to chose a preference between the counter-argument (need to have install the -dev package to even want to link against the shared object) and this one23:28
sistpotyDaveMorris: so it looks like you should go for library packaging style after all. Sorry for the misinformation23:29
slangasekbut you *always* have to install the -dev package to link against shared objects :)23:29
DaveMorrisusing pkg-config means it's easy to find anyway23:29
slangasekbecause -dev is the package that provides the .so file23:29
slangasek(symlink)23:29
DaveMorrisslangasek: but no-one will be running a program which is linked against the so unless they are building it23:30
DaveMorrisso seems pointtless IMO to have 2 packages23:30
sistpotyslangasek: sorry, logic wrong way round... you'd not want to have some binary linked against the shared object, unless you'd have the -dev package installed anyways.23:30
sistpotys/some binary/any binary/23:31
sistpotyphew... logic is hard at that late time *g*23:31
DaveMorrisonly 23:30 here :)23:31
sistpotyone hour later here23:31
slangaseksistpoty: oh, I see23:33
DaveMorriswell it's up there all working as 1 packagee, you guys do this more than me.  What should I do with it?23:33
slangaseksistpoty: then perhaps it shouldn't have a separate lib package23:33
slangasekDaveMorris: ah, you reached this conclusion sooner than I ;)23:34
sistpotyslangasek: it doesn't *g* (it's DaveMorris package btw)23:34
DaveMorristhe way I see it, it's only ever gonna get used by programmers using the testing framework23:34
sistpotyslangasek: http://revu.tauware.de/details.py?package=cpptest (for the details ;)23:35
DaveMorrisso have 1 package, install the sso to /usr/lib/<pkgname> and poink pkconfig.pc file to i23:35
slangasekDaveMorris: I would still argue for installing the so in /usr/lib, but I can't convincingly argue that it's a bug if you don't23:36
DaveMorristbh  it'll only affect a handfull of users23:37
DaveMorrisbtw  has it been suggested to have an rss feed for http://revu.tauware.de/index.py and prehaps for each package (for people to follow certain packages)23:44
DaveMorrisslangasek: sistpoty will you advocate the package then if its fine?23:47
sistpotyDaveMorris: once its fine I will, but I didn't have a total look yet ;)23:48
DaveMorrissorry I though you had23:49
jaredthaneHey, guys I was looking at this page: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/9360323:49
ubotuLaunchpad bug 93603 in php5 "RFE: Add more php5 extensions (like php5-gmp)" [Wishlist,Confirmed]23:49
jaredthaneand I want to help out by creating a package how do I do it?23:50
DaveMorrishttps://wiki.ubuntu.com/MOTU/Contributing23:50
slangasekI confess to have not yet looked at the package, DaveMorris, and don't really have the time for it at the moment23:50
sistpotyDaveMorris: oh, btw.: sure the rss feed was requested, but I'm not convinced about rss feeds myself (and would have to search how to get it implemented), so I'm rather not getting this done myself... of course contributions are very welcome ;)23:50
DaveMorrisand see if someone in here has time to help you23:50
slangasekI could look later this evening, but that's several hours away here :)23:50
DaveMorrisslangasek: np23:51
DaveMorrisjaredthane: I'd help but I'm new as well so would prob be more of a hindarncee23:51
jaredthaneDaveMorris: Thanks.23:56
jaredthaneWould anyone mentor me particularly regarding creating packages perhaps with the bug I cited above?23:57
slangasekjaredthane: 1) forward the bug report to the Debian php5 maintainers; 2) make them do all the work? :)23:58
FujitsuCan anybody make any kind of sense of this? https://edge.launchpad.net/ubuntu/feisty/+bugs?field.component=1&field.component=4&field.component=2&field.component=323:58
FujitsuNote how each task is shown many times.23:58
FujitsuExcept for some that aren't.23:58
jdongok, that forkbomb bug is seriously frustrating me *unsubscribes*23:59
FujitsuHah.23:59
jaredthaneslangasek: Good idea, but besides, but I'd still like to learn how to make a package myself...23:59

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!