[01:06] tumbleweed: I thought that a patch system was not supposed to be added when SRUing [01:13] It's not. === Zhenech_ is now known as Zhenech === Zhenech_ is now known as Zhenech === Zhenech_ is now known as Zhenech === Zhenech_ is now known as Zhenech [07:05] hi, i am new to packaging and i was wondering what you should put in the section part of the control file [07:12] i am actually packaging my first package cinelerra for maverick would anyone be able to help me through the process? === fabo_ is now known as fabo [07:25] micahg, ScottK: err yes, you aren't wrong. I guess I'm more permissive of them than I should be and in this case it was unwarranted. Should I ask for a queue rejection? [07:33] good morning! [07:45] i am wanting to package cinelerra for maverick which source should i use? [07:57] jfer: http://cinelerra.org/getting_cinelerra.php#ubuntu there is link there [07:58] should i get the source from sourceforge or the git repository? [08:12] how do i find the version of a source? === hanska is now known as dapal [08:44] dholbach: can you update the Homepage link on https://launchpad.net/harvest? [09:04] geser, done [10:25] directhex: have you an idea what caused the FTBFS in dbus-sharp? (http://launchpadlibrarian.net/58627499/buildlog_ubuntu-natty-i386.dbus-sharp_0.7.0-1_FAILEDTOBUILD.txt.gz) [10:25] geser: yes, ricotz has a patch but we haven't had time to apply it [10:25] it's a bashism [11:32] tumbleweed: I can reject it. What package? [11:32] ScottK: mongodb [11:34] tumbleweed: Rejected. You can reupload using the same version number when ready. [11:35] ScottK: thanks, SpamapS consider yourself prodded === yofel_ is now known as yofel [15:09] micahg: denunciator of you === jdstrand_ is now known as jdstrand [16:23] hi guys, I was wondering how to add a page on the ubuntu wiki? [16:26] rhlee: Go to a page that doesn't exist and it should ask you if you want to create it. [16:26] Pici: thanks === hannesw_ is now known as hannesw [17:12] ok, I have a ppa enabled, successfully built and uploaded my package, and I have a question, the package I built now is specified only for Maverick, I assume that is from the changelog file, how can I specify for more than one or all of the ubuntu editions? [17:14] shane4ubuntu: change maverick to lucid/hardy/whatever in the changelog, it's also a good idea to use different revision numbers (e.g. ~lucidppa1 instead of just ~ppa1) [17:15] afaik you can't just upload a package once and have it build on all releases [17:18] Bachstelze, ok, thanks! [17:31] tumbleweed: pong.. I am not sure what to do about this SRU [17:31] SpamapS: The part where you added a patch system: don't do that. [17:31] honestly I'm pretty much done trying to do anything with MongoDB anymore. Its unbelievable the amount of effort required to change anything that links to xulrunner. [17:32] SpamapS: do you want me to finish it? [17:33] micahg: I'll finish what I've started. I'm just frustrated with the level of detail required to get it right when if xulrunner had a real library, this would be a non issue. [17:33] SpamapS: well, it doesn't seem to be a priority for Mozilla ATM, maybe after 4.0 is released we can get it revisited [17:35] ScottK: shouldn't that be mentioned here: https://wiki.ubuntu.com/StableReleaseUpdates [17:35] SpamapS: I'd have thought wanting a minimal diff would cover it. [17:36] * micahg remembers seeing it in the docs somehwere [17:36] We'd actually prefer people not add a patch system even for the development release except in coordination with the Debian maintainer. [17:36] It falls under "don't monkey with the build system Debian set up". [17:39] ScottK: right, so the debian maintainer added it in 1.4... [17:39] This is the closest I found,https://wiki.ubuntu.com/PackagingGuide/Complete#Patching%20Other%20People%27s%20Packages, it used to be clearer [17:40] SpamapS: but we don't have it in Lucid, so you can't add it [17:41] So I ask again, should I not have a patch, or patch directly in the debian diff? [17:41] * SpamapS first asked in the merge proposal [17:41] SpamapS: if we end up updating mongodb to a later version due to the xulrunner change, we'll get a patch system with it most likely, but barring that, we can't add patch systems to Debian packages [17:41] SpamapS: patch the source directly [17:42] SpamapS: Make the changes inline (in the upstream code) and then it will appear correctly in the debdiff. [17:42] (as micahg says) [17:44] Ok, easy enough to rectify. [18:02] why the hell is mongodb using xulrunner? [18:04] zul: presumably for mozjs [18:07] dholbach: heyo! [18:08] highvoltage, in a call [18:08] dholbach: ok, if you have some time give me a poke, would like to talk about Gediminas's packages some time [18:09] highvoltage, can you reply to the emails? [18:09] email [18:10] dholbach: I can, it's the content that I need some clarification on. is there any exceptions that can be made, or should I tell him to follow the usual process for all 84 packages? [18:11] ScottK: if there is a bug in backported package should the bug be reported against ${release}-backports AND package, only ${release}-backports or only package? [18:11] kklimonda_: Only against $(release)-backports unless the bug also applies to the development release of Ubuntu, then both. [18:12] The preferred solution in these cases is a new backport. [18:13] highvoltage, can you follow up and I reply to it tomorrow? [18:13] highvoltage, I'm a bit busy right now [18:14] dholbach: ok [18:25] thanks highvoltage [19:11] whoa, why does firmware-b43-installer postinst script aborts if it detects wrong card? [19:11] ah, already reported === lifeless_ is now known as lifeless === kklimonda_ is now known as kklimonda [20:13] micahg: congratulations :) [20:13] set topic for him! glory for micahg! [20:13] ajmitch: thanks :) [20:13] ari-tczew: thank you [20:13] micahg: that was ironic... [20:14] ari-tczew: PM? [20:14] micahg: do you want me to pick up? [20:15] ari-tczew: ? [20:16] micahg: nevermind... come on [20:35] micahg: congrats :) [20:37] eh? what are the congradulations for? [20:38] He is MOTU. [20:38] * sebner waves at ScottK :) [20:38] * ebroder suspected that, but irclogs.u.c is lagging [20:39] Congrats! [20:39] sebner: thanks [20:39] ohh, congrats [20:39] ebroder: psusi: thanks [20:39] (bought time, too :-P) [20:39] now do you feel like sponsoring the revival of the defrag package? ;) [20:40] * micahg would suggest getting it back in Debian first [20:41] ari-tczew: I think if you have an issue with someone, random complaints during a DMB meeting " I don't trust that he will work on clean up sponsors queue" are not a very good way to deal with them. That and I don't understand " micahg is building his career by reporting on another folks from IRC rofl" at all, but it sounds childish. [20:45] bdrung: re sponsors queue, currently main -> 80, universeish -> 5, do you want me to apply for core-dev? ;) [20:46] micahg: yes :P [20:46] * micahg reminds chrisccoulson to go for core-dev ^^ :) [20:47] heh :) [20:47] micahg: keeping the universe queue empty is easy. get enough people doing sponsoring. [20:49] bdrung: k, I'll try to sponsor at least 1 per week (more if time permits) [20:50] micahg: honestly, the universe sponsoring queue seems to be staying short enough that you might have a hard time finding 1 per week needing sponsoring [20:51] ebroder: well, there's usually a handful available at any one time when I've checked [20:52] * micahg has plenty to do though for the Firefox/Xulrunner transition this cycle [20:53] micahg: congrats [20:53] JontheEchidna: thanks [20:53] micahg: sorry I missed the meeting, congrats :) [20:54] tumbleweed: no problem, thanks [21:00] ScottK: do you want to talk about it? [21:01] ari-tczew: We can if you want. I'm often of the impression that you are trying to be productive, but don't realize how your comments appear to others, so I mention it. If it's worth discussing, I'm willing to do it. [21:02] ScottK: I would, but today I'm busy busy busy busy. [21:03] OK. Let me know if/when you have time and want to discuss it further. [21:07] micahg: grats. Thought you were MOTU for a while already. But then, others thought the same about me. ;) [21:08] That's usually a strong sign it's time to apply. [21:08] Rhonda: thanks [21:08] * ScottK reminds kklimonda he's owing a python-visual fix (including the stack under it). [21:11] ScottK: actually I'm working on it right now :) [21:11] kklimonda: Excellent. [21:17] is it safe to kill gvfsd and restart it? [21:19] bdrung: yes [21:19] bdrung: you will loose all connections but it won't break your desktop :) [21:20] thanks kklimonda - that gives me 2 GiB back without a reboot [21:20] I tried to tell bzr about my launchpad account but it says I have no ssh keys, it's right but I have an openPGP key instead, can I not use this? === hanska is now known as dapal [21:28] paddy_: no, you need a separate ssh key [21:36] kklimonda, thanks [21:54] whoa, this optipng stuff is really slow [21:55] I shouldn't have pkgbinarymangler installed in pbuilder.. [22:11] I'm not sure but can't you disable this one through the config files? [22:29] micahg: congrats! [22:52] achiang: thanks [23:06] when I bzr branch I get Agent admitted failure to sign using the key. what is wrong? [23:19] ScottK: When you have some time can you take a look at https://github.com/kklimonda/atkmm1.6 ? [23:20] ScottK: I also got gtkmm and gtkglext built, I'll see if I can get python-visual to build now [23:21] OK. Great. [23:24] kklimonda: So in terms of the .la file problem, this is just a matter of rebuilding (plus you are making some other improvements)? [23:24] It still needs a debian/changelog entry. [23:24] ScottK: yes but gtkglextmm won't build with gtkmm < 2.22.0 [23:25] ScottK: yes, but I'd rather know if the rest of packaging makes sense (especially Breaks/Replaces) - adding a full changelog entry is a matter of few keystrokes. [23:26] kklimonda: At a glance it does. I do not, however, seem to find an existing aktmm1.6 package in the archive, so I'm a bit confused. [23:26] ScottK: that's the problem, there was non - until now atkmm was part of gtkmm and it has distributed with binary packages generated from gtkmm2.4 [23:27] there was none* even [23:27] kklimonda: OK. I'm starting to understand. Since this is a new package for Ubuntu, it would be helpful to upload the source to REVU once you've got it ~ there. [23:28] I was hoping I could get it into debian but I got no response in over a week :/ [23:29] ScottK: python-visual also builds fine [23:29] kklimonda: [23:29] Cool. [23:29] ScottK: ok, I'll open a bug on LP and upload atkmm1.6 to revu [23:33] hmm, interesting - update-maintainer sets me as a Maintainer anyway. Is it proper or should I change it to Ubuntu Developers manually? [23:35] oh well, I'll just change it [23:48] ScottK: http://revu.ubuntuwire.com/p/atkmm1.6 [23:58] :)