[06:29] Folks: which is the deadline that would apply to uploading a new version of a current universe package? (Tahoe-LAFS) [06:30] Beta Freeze? [06:30] Tahoe-LAFS v1.6.1 is currently packaged in Lucid. [06:30] The current stable release of Tahoe-LAFS is v1.7.1. [06:31] I *hope* that Tahoe-LAFS v1.8.0 will be released by the end of August, but that is a few days past the Beta Freeze and anyway the Tahoe-LAFS schedule could well slip. [06:31] So, I guess I should try to get Tahoe-LAFS v1.7.1 uploaded for Maverick. :-) [06:32] Hm... how do I initiate that process? Tahoe-LAFS is not (yet) in Debian. [08:57] okay [08:57] when I try to build with pbuilder-dist sid armel build, it spams the console with [08:57] "qemu: Unsupported syscall: 335" === CieD is now known as Ciemon [09:32] "qemu: could not open serial device 'stdio': Success" === yofel_ is now known as yofel [13:05] what is the sence of lintian-override files? [13:07] bulldog98, I think it is when a certain lintian error or warning clearly doesn't apply to you, or you are justified in ignoring a certain error/warning, you can override it. [13:07] ok thanks umang [13:08] sure. [13:08] bulldog98, I'm not sure about MOTU, but on Debian you have to inform anyone sponsoring your upload about the override and why you've done it while requesting for a sponsor. [13:09] umang: that’s not the point I simply wanted to update an package and understand why there are files like that [13:09] ^^ [13:10] bulldog98, ok. [13:10] :) [14:27] if i wanted to add a patch to package in a development release (i.e. maverick) what would i need to do? [15:32] ScottL: use "edit-patch" on the source, if it uses a patch system. [15:35] lfaraone, oh, i know how to apply the patch, rather i meant how do i get the patch applied to the package in the archives ? [15:38] ScottL: you submit a debdiff or a bzr branch and request sponsorship. [16:03] lfaraone, that's what i thought, thanks! [16:03] ScottL: which package? [16:07] lfaraone, gnome-system-tools , this is the package that ubuntu studio uses for network connections (and configuration) but a patch was applied to disable the interfaces because network-manager was chosen as default [16:08] unfortunatly the 10_disable_interfaces.patch prevents configuration of network, which prevents ubuntu studio users from configuring their network [16:09] since gnome-network-admin (the actual package built by gnome-system-tools) is now in universe and not installed by default on ubuntu desktop i was hoping to remove the 10_disable_interfaces.patch [16:09] thus given ubuntu studio users the functionality to configure their network [16:11] it should be pointed out that ubuntu studio has chosen not to use network-manager because of its dynamic loading that it puts onto the cpu which intermittantly increases latency [16:11] which should be recognized as a Bad Thing (yes, i capitalized that) for a multimedia distribution [16:11] ScottL: dynamic loading? [16:16] azeem, my understanding is that network-manager does not apply a consistent cpu loading, i believe this is when it is searching for other wifi networks that are available [16:24] If I'm sponsoring a merge that has a debian-ubuntu debdiff, should I dget the latest Debian version and apply the diff? [16:26] lfaraone: yes, for example if you're going to sponsor foobar 0.0.1-1ubuntu1 and the debian package is 0.0.1-1 you will want the dsc of foobar 0.0.1-1 from debian [17:21] anyone around to sponsor : Bug #604636 ? [17:21] Launchpad bug 604636 in One Hundred Paper Cuts "Description: Cheese is too "cheesy"!" [Low,In progress] https://launchpad.net/bugs/604636 [17:24] vish: you are mistaken: that text is in the Debian description [17:25] Laney: it was in the ubuntu diff [17:25] ...I just looked at it [17:26] oh! [17:26] laney@chicken> grep cheesy debian/control ~/temp/cheese-2.30.1 Cheese is a cheesy program to take pictures and videos from your web [17:27] Laney: cheese_2.30.1-0ubuntu2.diff.gz , mentioned it , so am a bit confused :s [17:27] the diff.gz contains all changes, not just ubuntu ones [17:28] lsdiff -z *.diff.gz [17:28] but is this really the kind of thing that papercuts is about anyway? [17:28] seems exceedingly trivial [17:29] Laney: this cycle the descriptions are getting a make over too [17:29] as you wish, it's your time [17:30] I suggest that you don't deviate from Debian over this though [17:30] Laney: hmm , now I have to re-open upstream bug :s [17:30] * vish need to figure that out.. [17:30] http://www.debian.org/Bugs/Developer get this page bookmarked [17:31] Laney: how to re-open a debian bug? [17:31] that page will guide you [17:31] just now , did the -done reply [17:31] * vish reads :) [17:40] MoM/universe: package hp-ppd 0.9ubuntu2 0.9-0.1 is it possible to upload 0.9-0.1ubuntu1 ? [17:42] no [17:46] ari-tczew: note that 0.9ubuntu2 will always sort after 0.9-0.1ubuntu1 (you can use dpkg --compare-versions to confirm) [17:47] crimsun_: well, in this case only fakemerge is possible right? [17:47] upload ubuntu3 with changes like in merge [17:48] ari-tczew: "fakemerge"? Are you meaning to drop the Ubuntu delta ("fakesync") or to perform a merge? [17:48] crimsun_: perform a merge in ubuntu3 [17:48] yeah, you'll have to merge it [17:48] crimsun_: are you expierenced with sound system? [17:49] (do I really want to answer that question...?) [17:49] ask away [17:50] crimsun_: because I don;t have a sound on maverick and I;m not sure who is a sound system mastermind - you or TheMuso [17:52] well, bugs are good, but what's the issue? Have you filed a bug using ubuntu-bug alsa-base? [17:52] (nearly always filing a bug is more efficient) [17:56] crimsun_: and what I can write there? I don't have a sound? [17:56] ari-tczew: I need the apport-attached info more than I need your description of "don't have a sound" [17:57] sorry, I don't intend that to sound rude, but "no sound" is too vague to be useful [17:57] crimsun_: why do you write that: (do I really want to answer that question...?) [17:58] because I don't understand [18:01] ari-tczew: I've endured a fairly significant amount of grief for sound issues over the past five years. [18:02] heh [18:03] * hyperair wonders what kernel maverick has. [18:03] i know that 2.6.35-rc6 successfully borked both sound and bluetooth for me. [18:03] not sure how those two are related though [18:03] maverick's currently released kernel is 2.6.35-rc5-based [18:04] hmm then it can't be that =) [18:04] ubuntu-maverick.git has 2.6.35-rc6 merged (in 2.6.35-12.17); you can find it in the kernel ppa [18:05] maybe i'll give that one a go. i might have screwed something up here on my own. [18:26] does someone want to merge phpbb3? [18:37] Are there any chances of php5-5.3.3 making it into maverick? [18:38] or would that be an extremely high expectaction? [18:38] s/expectaction/request/ [19:03] MTecknology: it'd be easier if it were already in Debian unstable [19:05] crimsun_: I'd consider trying to help get it there, I'm sure zul needs help. I remember the last time I tried to work with that package I wound up in an angry place for a week straight and then just gave up.. [19:06] crimsun_: I should try again anyway, huh? - when's the import freeze? [19:07] oh.. that was a month ago.. [19:11] crimsun_: maybe for 11.04, right? :) [19:16] MTecknology: it's never too late to help in Debian, and exceptions can always be requested in Ubuntu [19:17] crimsun_: I'll do my best - it was only release a few days ago iirc :) [21:48] .join #Ubuntu-MOTU-Sponsors [23:52] * Laney wonders what that channel is