[00:01] Usually it doesn't matter for the source package. [00:23] cemc, ping [00:24] RoAkSoAx: pong [00:25] cemc, any luck with the fix for havp in debian ? :) [00:28] RoAkSoAx: well, not really... I opened a bugreport, and attached my patch, which I think would fix it. now it's up to the maintainer I think [00:30] cemc, I see. well I run into an issue that I've been told to discuss with you. The issue is when purging. Here i attach it as well as the possible fix: http://pastebin.ubuntu.com/335597/ [00:57] RoAkSoAx: I'm not sure this will work... I think that postrm script will have the same problem unmounting the loop file as the init script has [03:01] Hi Everyone [03:01] Hello sachin6870 [03:01] Hi Scott, I want to contribute to Gnome desktop for Ubuntu [03:02] I developed one gnome applet, I want it be part of ubuntu official repo [03:02] sachin6870: Then #ubuntu-desktop is probably a better place to start. [03:02] Oh. [03:03] We do help with packaging here, so this might be the right place. [03:03] ok thanks [03:03] http://cricscoreapplet.sourceforge.net/ [03:03] this is project home page [03:03] Can you please help me with procedure? [03:04] I can give you some general advice. [03:04] That will be great [03:04] I'm busy with a few other things tonight, so I don't have time for detailed assitance. [03:04] !revu | sachin6870 [03:04] sachin6870: REVU is a web-based tool to give people who have worked on Ubuntu packages a chance to "put their packages out there" for other people to look at and comment on in a structured manner. See https://wiki.ubuntu.com/MOTU/Packages/REVU [03:04] no problem. [03:05] !packagingguide | sachin6870 [03:05] sachin6870: The packaging guide is at http://wiki.ubuntu.com/PackagingGuide - See https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/UbuntuDevelopment - See also !backports [03:05] Those will get you started. [03:05] ok [03:05] When you have questions, just ask them and usually if someone is around who knows the answer, they will help you. [03:05] ok [03:06] Thanks Scott for your valuable time. [03:06] No problem. It's always good to see new people who want to contribute. [06:25] so, who are my unlucky souls using Analog Devices HDA codecs? [06:25] maco: how long are you gonna be up? [06:26] dtchen: sorry, HDA ATI SB here, but when you get to Realtek ALC888, count me in. [06:27] anyone have a link to the remove from archive instruction page? [06:27] diwic: ugh, Realtek is a mindfsck in and of itself [06:28] granted, the www.analog.com giving me crap for data sheet searches is less than useful [06:33] ok, never ever do a hard reset and then pull into a branch :( [06:33] I just nuked all my powerdown-analog work in one second. Thank goodness for rsync backups. [06:40] dtchen: git scares me in that sense at times. [06:40] being an incredibly powerful tool with a clunky UI, I've found it way too easy to do the wrong thing (tm) [06:40] of course I've typically been lucky enough to be in the presence of a git deity with some magic sequence of even less intuitive commands to get things back [06:40] (no pun intended) [06:41] jdong: you have the link to the package removal instruction page? [06:41] micahg: no, I do not [06:42] micahg: https://wiki.ubuntu.com/UbuntuDevelopment/PackageArchive#Removing%20Packages [06:43] I think! [06:43] thanks jmarsden [06:44] You're welcome === mac_v_ is now known as mac_v [08:27] with those motu videos on youtube (dholbach), is any of that stuff written down anywhere? [10:02] can anyone point me to a good basic tutorial on building a patch with quilt? [10:23] stochastic_: there is a wiki page about adding a patch with quilt [10:24] https://wiki.ubuntu.com/PackagingGuide/PatchSystems#quilt%20%28example%20package:%20xterm%29 [10:24] google found a nice explanatory pdf file after I hunted through about five other "introductions" that were more like latin than introductory. [10:25] that wiki page really doesn't explain how to add a patch, it gives a one-line example as the editor, but doesn't explain itself [10:25] to a beginner it's pretty useless. [10:26] * stochastic_ ended up reading this: http://www.suse.de/~agruen/quilt.pdf [10:42] quilt is not the easiest patch system to learn, but is awesome to work with once you've learnt it [10:50] pochu, so, once a quilt diff file exists in debian/patches, and is listed in debian/patches/series then what does a person need to do to ensure the patch is applied at build time? [10:50] check the build log :) [10:51] lol, okay. [10:51] if the patch system was already there and you only added a new patch, it should be okay though [10:51] no, there was no patch system [10:55] stochastic_: are you using cdbs, debhelper etc? [10:57] stochastic_: http://pkg-perl.alioth.debian.org/howto/quilt.html [10:57] diwic, the package uses debhelper - https://launchpad.net/ubuntu/+source/raul/0.5.1-1 [10:59] stochastic_: according to the howto I just posted you're supposed to do "dh --with quilt" in debian/rules [11:01] diwic, okay, thanks. Though the rules file in that package is really strange looking. http://pastebin.ubuntu.com/335808/ [11:02] stochastic_: that's normal for a debhelper 7 - just change "dh $@" to "dh --with quilt $@" [11:02] diwic, ahh thanks. [11:03] stochastic_: and add dependency debhelper >= 7.0.8 (and quilt) [11:06] diwic, yes I had quilt already added. debhelper needs to be >=7.0.8 though? [11:06] stochastic_: I'm just retelling the howto for you :-) [11:06] ;) [11:09] * stochastic_ waits for pbuilder to update to lucid... [11:09] 7.0.8 added the --with option [11:33] I am creating package for network daemon. Should I create sysv init script or upstart job or both ? What is the best pactice for ubuntu now ? [12:12] is there anywhere on the wiki that details how to setup your system for package building? [12:12] if not i could create a page [12:38] rjnienaber: sudo apt-get install build-essentials ? [12:39] i was thinking something more along the lines of this: http://owlsayswoot.therandomist.com/2009/12/06/maintaining-ubuntu-package-setting-up-your-system/ [12:39] rjnienaber: https://wiki.ubuntu.com/PackagingGuide [12:42] there seems to be some detail in the video that's not on the wiki [12:43] it is a wiki, edit it ;) [12:45] cool :) [13:35] identify beasty [13:35] oops [13:36] oops would be quite correct. [13:39] :) [14:49] Hi, I'm building a package which depends on pandoc. When I attempt to build it with pbuilder, pbuilder co mplains that it is a virtual package and cannot continue, but synaptic says it isn't a virtual package. What gives? [15:00] lfaraone: make sure pbuilder is using the right release and is up to date [15:08] tsimpson: it's on karmic, and I just rebuilt base.tgz [15:11] lfaraone: do you have universe enabled in your pbuilder? [15:12] randomaction: I didn't explictly enable it, what do I need to do/ [15:12] *? [15:40] lfaraone: try https://wiki.ubuntu.com/PbuilderHowto#Universe%20support [16:13] does the bot work in here? bug 394373 [16:13] Launchpad bug 394373 in qalculate-kde "Inconsistent menu entries across calculator program" [Undecided,Fix released] https://launchpad.net/bugs/394373 [16:13] strange, it works === highvolt1ge is now known as highvoltage [19:06] Hey, would a "package cannot be removed under non english locales" be SRU-worthy? [19:07] lfaraone: sure sounds like it to me [19:08] jdong: mk. [19:08] lfaraone: you have a linl to bug report about this package? I wonder what's wrong with it :) [19:10] kklimonda: it's a funny bug. the daemon "stop" code checks a error message for a string rather than looking for the error code. [19:11] kklimonda: bug 479131. I just checked in a fix upstream which works for me, and am now going to prepare my first SRU :) [19:11] and update calls restart, right? [19:11] Error: Could not parse data returned by Launchpad: The read operation timed out (https://launchpad.net/bugs/479131) [19:12] kklimonda: yes. [19:13] funny [19:14] kklimonda: mhm. the fix is trivial (see http://code.google.com/p/autokey/source/diff?spec=svn192&r=192&format=side&path=/trunk/src/lib/daemon.py&old_path=/trunk/src/lib/daemon.py&old=73 ), but I'll have to push out a new lucid revision first, right? [19:16] lfaraone: well, it depends but the best way is to fix it in current development version first indeed [19:17] i wonder if this fix is fine [19:17] before err.errno is checked err is casted to string so .errno is lost [19:19] kklimonda: oh! right, I forgot about that. [19:20] Fixed in svn:193 [19:23] kklimonda: does that look sane? [19:24] yes [19:36] while trying to install a pkg i get this erorr.."trying to overwrite `/usr/bin/logname', which is also in package coreutils [19:37] dpkg-deb: subprocess paste killed by signal (Broken Pipe [19:39] lintian is complaining about my DEP3-style headers (which lack "## DP:") [19:39] Is this a good reason to override? [19:40] wrapster: please pastebin the entire dpkg output [19:40] according to the 9.10 archive there is only one package that contains that file [19:40] dtchen: http://pastie.org/730680 [19:42] wrapster: is this nexenta? [19:42] dtchen: yeah. [19:42] but since it was a pkging issue i asked it here.. [19:42] sorry if i was worng. [19:42] but would really appreaciate if you could at least tell me where to look ? [19:43] wrapster: perhaps this package should also divert /usr/bin/logname but the nexenta guys should know better than us [19:43] geser: where are the diverts specified? and are they same as pkgname.links? file!! [19:44] i mean do both do the same job? [19:45] lfaraone: you should add comment to your patch. and if you are not willing to do that don't override lintian warnings - just let them be [19:47] geser: any idea? [19:58] wrapster: the nexenta web site is very confusing to me [19:59] wrapster: that source doesn't appear to be in hardy-unstable at all, either [19:59] wrapster: but yes, what geser said is correct [20:00] wrapster: it's probably best to approach the specific nexenta porting folks for this issue [20:01] dtchen: ok.. thanks [20:03] dtchen: i'm using a proprietary display/keyboard/mouse/audio peripheral from NComputing, and sound works under Gnome but not Sugar. What should I do to go about debugging it? [20:04] you lost me at proprietary [20:05] anyhow -- start with http://www.alsa-project.org/alsa-info.sh [20:07] dtchen: yeah, it pains me too. for some reason the company that produces them is worried that if they FOSS their software then people will make cheap knockoffs of their peripherals. [20:07] not my concern, really, but lack of source makes it difficult to point out bugs in the audio source code, yadda yadda [20:08] wow, there really is a crackton of broken HDA controllers [20:09] maybe we should just invert this list and make everything use position_fix=1 [20:10] you can bet that will bring its own set of problems [20:10] oh of course [20:10] * ajmitch gets the impression there's no silver bullet to fix this [20:11] if there's anything I've learned, it's that any action will break some non-trivial, very vocal portion of the userbase [20:11] maybe some garlic & stakes through the heart of HDA [20:12] nah, just through that of the OEMs [20:13] that'd be more fun === nxvl_ is now known as nxvl === nigel_nb_ is now known as nigel_nb === fbond_ is now known as fbond