[00:00] <Linux000> Okay, I thought it had to have the debian directory in the source
[00:01] <vorian> actually, the patch should be the current source versus your changed source
[00:01] <Linux000> Okay, when I make the patch(I might be doing it wrong) it complains about not having a changelog
[00:03] <vorian> what kind of patch?
[00:06] <Linux000> As I said I am most likely building it wrong, the error is when I run 'debuild -S'
[00:08] <Linux000> It is just a small basic patch to a python file
[00:27] <Daviey> Anyone fancy a quick sponsor frolic?
[00:59] <Riddell> cody-somerville, jdong: please review bug 534561
[01:10] <Linux000> When editing the change log, do we put our email address, or the ubuntu developer list address?
[01:14] <\sh> Linux000: your email address
[01:15] <Linux000> \sh: Thanks
[01:17] <Linux000> And should I set the Maintainer to Ubuntu Dev's for non-ubuntu packages(i.e. Firefox)
[01:19] <\sh> non-ubuntu packages?
[01:19] <Linux000> Like Firefox/Pidgin
[01:23] <micahg> Linux000: what are you doing with Firefox?
[01:24] <micahg> and why is it a non-ubuntu package?
[01:24] <Linux000> Thats an example, I am not trying to fix firefox, it pychess, bug 534761
[01:25] <Linux000> by non-ubuntu package, I mean a project by itself, that doesn't rely on ubuntu Dev's
[01:26] <micahg> Linux000: you should get the ubuntu-dev-tools pacakge
[01:26] <micahg> in it is a script called update-maintainer that you can use on a package like pychess that's imported from debian
[01:26] <Linux000> Thanks
[01:29] <\sh> Linux000: then you should add in debian/control your own maintainer email address...
[01:30] <Linux000> Thanks
[01:33] <micahg> \sh: update-maintainer sets it as ubuntu-devel-discuss I think...
[01:33] <\sh> micahg: yes...but doing a package for self maintained packages and not for ubuntu shouldn't set an ubuntu maintainer
[01:33] <Linux000> Yes it does, it moves the listed maintainer to XSBC-Original-Maintainer:
[01:34] <micahg> \sh: ah, ok, I thought Linux000 was going to patch for archive
[01:34] <\sh> micahg: if so, I didn't understand it ;)
[01:34] <micahg> Linux000: are you making a debdiff for lucid?
[01:34] <vorian> Linux000: sorry i dropped you, I had something come up
[01:35] <vorian> you are in good hands with \sh though
[01:35] <Linux000> Yes, a Debdiff for the Lucid Repo
[01:35] <micahg> Linux000: yeah, then just use update-maintainer
[01:35] <Linux000> vorian: np, I had to eat to
[01:35] <Linux000> Great
[01:35] <vorian> Linux000: have you reviewed the guides on the wiki?
[01:35] <Linux000> Yes
[01:36] <vorian> there is a good recipe that i like to use as an example
[01:36] <\sh> Linux000: ok...then I did misunderstand you...if you are doing a debdiff for ubuntu you need to update the debian/control maintainer field with update-maintainer of ubuntu-dev-tools (which is the easy way of doing it)
[01:36] <Linux000> vorian: which recipe?
[01:36] <vorian> lemme see here
[01:38] <vorian> https://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff
[01:38] <\sh> vorian: I don't have any clue ...;)
[01:38] <Linux000> Thats the one I'm looking at
[01:38] <vorian> sorry it took forever to find :P
[01:38] <Linux000> no
[01:38] <Linux000> np
[01:39] <vorian> ok
[01:39] <vorian> so, you can do this
[01:39] <vorian> or rather, have you done dch -i
[01:39] <Linux000> okay, this is my first patch, so I am trying to make sure I do this right
[01:40] <vorian> that's no problem, you've a whole channel of people trying to help
[01:40] <Linux000> yes, I updated the change log
[01:40] <vorian> great
[01:42] <vorian> what patch system does the package use (if any)?
[01:42] <Linux000> What do you mean by patch system?
[01:43] <\sh> cdbs (simple-patchsys), dpatch, quilt, doko-patch-system , etc.pp.
[01:43] <vorian> well, if you diff the sources ( old new > patch.diff ) you toss that in debian/patches
[01:44] <vorian> we don't use direct changes to the source, souyez would reject the package
[01:44] <vorian> besides, it's best to keep the source so others can modify it how they please
[01:44] <Linux000> right now I am following https://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff , if that helps, I belive it is cdbs
[01:45] <\sh> vorian: it does? what about packages, which doesn't have a default patch system...we don't invent one when package maintainer choose to not use one
[01:45] <vorian> *shrug*
[01:45] <micahg> vorian: I thought debuild adds any source changes to teh .diff.gz?
[01:46] <vorian> it does, but the changes are made in the debian directory
[01:46] <vorian> or unless the maintainer chooses otherwise
[01:46] <RoAkSoAx> vorian, long time no see
[01:46] <vorian> yo RoAkSoAx
[01:46] <RoAkSoAx> how's you dfoing man?
[01:46] <ajmitch> unless something has changed, soyuz shouldn't reject those packages with changes made directly
[01:46] <vorian> Linux000: check out chm2pdf on a patch
[01:46] <vorian> alright, I stand corrected :P
[01:46]  * ajmitch dislikes trying to add a patch to a package which uses cdbs+tarball-in-tarball
[01:47] <\sh> vorian: if package debian/control doesn't list anything about cdbs, dpatch, quilt or whatever it could use to apply patches from debian/patches, it's always inline source patches, which is quite ok for debian because diff.gz itself is a patchsystem
[01:47] <ajmitch> I wonder fi I can get away with adding dpatch back into this package
[01:48] <\sh> hey ajmitch :)
[01:48] <vorian> i'm sorry, i havent explained myself very well
[01:48] <ajmitch> hi \sh  :)
[01:48] <vorian> as usual :)
[01:48] <vorian> RoAkSoAx: doing much much better
[01:48] <vorian> RoAkSoAx: how's school?
[01:48] <RoAkSoAx> vorian, I'm glad to hear that. And is school is going pretty good actually... busy but good :)
[01:49] <\sh> bah...I really hate writing unittests, or better I hate myself to not write unittests before I implement the real logic
[01:49] <vorian> good deal
[01:49] <Linux000> All I have to do for a patch is edit the source(to fix the bug), the modify debian/changelog, and create a debdiff right?
[01:49] <vorian> Linux000: give it a shot, and a sponsor will review it
[01:50] <vorian> it may be easier to walk you through it once we see what you've done
[01:55] <\sh> is "if var is False" correct pythonic or is "if var == False" correct...(it's really too late)
[01:55] <Linux000> Okay then, I fixed the bug, and added the changes to the change log, now I get an error in debian/rules when I run 'debuild -S'
[01:56] <ajmitch> or 'if not var' :)
[01:57] <jdong> \sh: "is" is pythonic for False, True, None which are distinct value constants.
[01:58] <ajmitch> 'is' checkd for object identity as well as equality
[01:58] <\sh> well...vlan_obj = self.proxy.faidb.vlan.insert( 4096, "192.168.1.0/24", "TestVlan", 10 , "Test Vlan" ) => vlan_obj == False ; vlan_obj = self.proxy.faidb.vlan.insert( 4095, "192.168.1.0/24", "TestVlan", 10 , "Test Vlan" ) => type(vlan_obj)=='dict'
[01:58] <jdong> well it's only checked for object identity, right?
[02:00] <ajmitch> \sh: so it's returning a dict, but that dict is equal to false?
[02:00] <ajmitch> odd, since I didn't think even an empty dict would be == False
[02:01] <\sh> ajmitch: well...actually my example was useless...the first parameter is the vlan_id which means it can only be between 1 and 4094 so everything > 4094 will cause the methods return value to be False/None
[02:02] <ajmitch> ok
[02:02] <\sh> ajmitch: if the vlan_id is between 1 and 4094 will cause the methods return value be a dict with the added vlan obj
[02:02]  * ajmitch isn't understanding what your problem is then :)
[02:03] <\sh> i just want to know if "if vlan_obj is False" is correct python language
[02:03] <ajmitch> yes, it should be
[02:04] <ajmitch> just beware of None != False
[02:07] <Linux000> I believe it is "if var == False"
[02:08]  * ajmitch still prefers to use 'if not var'
[02:08] <Linux000> Also, should I compress the debdiff, or leave it before sending to launchpad?
[02:08] <ajmitch> you should be able to leave it as-is, if it's not too large
[02:08] <\sh> ah...someone needs to complain later...;) it will be released as gplv3 anyway
[02:09] <\sh> so now for the 10th bottle of redbull for today...I don't know if that could harm my body...who cares
[02:09] <ajmitch> live short & burn out with a bang?
[02:10] <\sh> ajmitch: I think my son will be angry about the "burn out with a bang" ;)
[02:11] <ajmitch> it's about 3AM there? :)
[02:11] <\sh> ajmitch: yes...
[02:11] <\sh> ajmitch: we have rollout night
[02:11] <ajmitch> how fun
[02:12] <\sh> colleagues next to me are just deploying new cisco ASR config...
[02:12] <ajmitch> so sleep is in another 18 hours or so
[02:12] <\sh> during this time I can stop my puppet magic
[02:13] <\sh> ajmitch: oh...I got up yesterday morning around 8am went to office around 3pm and we started at 10pm yesterday with our work
[02:14] <Linux000> If someone answered, sorry, my computer went down for a second, but, should I compress the debdiff for a patch, or leave it before sending to launchpad?
[02:14] <\sh> ajmitch: and if we are not done with the work around 6am this morning we are getting F.U.B.A.R
[02:15] <ajmitch> Linux000: you should be able to leave it as-is, if it's not too large
[02:15] <Linux000> ajmitch: Thanks
[02:15] <ajmitch> \sh: tight deadlines like that are great, aren't they?
[02:16] <\sh> ajmitch: yes..especially when management doesn't listen to the guys doing the work...actually we don't have a clue about what we are doing...and how much work that is actually...but manager has
[02:16] <\sh> .oO(#fail)
[02:17] <\sh> the next nightshift will be from thursday evening  to friday morning...and next week again two nightshifts with more downtimes
[02:18] <\sh> and WTH does windows 7 put my laptop into sleep mode instead of restarting it...
[02:23] <ajmitch> \sh: oh, you have management that know best? that's fairly common :)
[02:24] <\sh> ajmitch: a standard so to say :)
[02:46] <\sh> ajmitch: what's the diff between php-memcache and php-memcached? ;)
[02:47] <ajmitch> different library used, they work slightly differently
[02:47] <ajmitch> I use one of them on servers here, can't remember which one ;)
[02:49] <\sh> ajmitch: close bug #532083 then...you just fixed it ;)
[02:49] <ajmitch> currently we're just using it for things like a session handler & a few small things
[02:49] <ajmitch> hm, must have missed that when checking for bugs to close
[02:49] <\sh> ajmitch: yeah...I use also php5-memcache for shared session management ...
[02:58] <ajmitch> hopefully most of the important php extensions are rebuilt now for 5.3
[02:58] <ajmitch> just a couple that are problematic
[02:59] <\sh> zend-framework should also be 5.3 compatible
[04:39] <jdong> Riddell: ACKed-ish, patch ok, but as commented, would like SRU bug description to be there for verification.
[05:00] <MTecknology> !info dh-make-drupal
[05:00] <MTecknology> weird
[07:38] <dholbach> good morning
[09:18] <duanedes1gn> trying to install some manpages into a package. The rules file is fairly complex so i was unsure where to call dh_installman
[09:19] <duanedes1gn> http://paste.ubuntu.com/392379/
[09:21] <geser> It doesn't look like the package is using debhelper. Is debhelper listed in Build-Depends?
[09:23] <persia> For that package, I'd probably add `cp -a ...` lines to the binary-arch rule.
[09:26] <geser> persia: do you remember how the automatic package removal import from Debian works? does it ignore ubuntu changes?
[09:26] <duanedes1gn> thank you
[09:27] <geser> duanedes1gn: looks like you are working on db4.2. db4.2 got removed in Debian and I assume Ubuntu will follow soon too.
[09:29] <duanedesign> geser: ahh, ok
[09:29] <duanedesign> geser: it is a rather old bug report :)
[09:31] <persia> geser: There isn't really an "automatic" package removal.  There's a script the archive-admins run to discover removals from Debian, and then they remove the packages.
[09:32] <geser> s/automatic/semi-automatic/ :)
[09:32] <persia> geser: I don't know if there is any other automation in the workflow, and I'd hope that the archive-admins at least examined anything with ubuntu-specific changes carefully.
[09:32] <persia> But ask an archive-admin for real details
[09:32] <geser> ok
[09:33] <geser> this part is a little bit under-documented and I never know if a removal bug should be filed or not
[09:34] <persia> My personal habit is to file RoQA removal bugs in Debian until DIF, and then file Ubuntu removal bugs if packages are still present at BetaFreeze.  This cycle the gap has been narrow, but when it's wide, I don't think it matters much.
[09:53] <duanedesign> persia: what about bug 534638 does that seem like a reasonable patch?
[09:53] <bcj> I think vpnc has a packaging bug.
[09:54] <bcj> After install I get errors stating that a file doesn't exist; the file is in the package, but it isn't copied to the right place - manually copying it fixes the problem.
[09:54] <persia> duanedesign: In what sense?
[09:54] <persia> bcj: I think you're right, for that behaviour.  Did you file a bug?
[09:55] <bcj> "sh: /etc/vpnc/vpnc-script: not found
[09:55] <bcj> Copying the file from the package fixes it.
[09:55] <bcj> No, I couldn't find where to file it in launchpad.
[09:55] <persia> bcj: Copying the script from the source package, or from where?
[09:55] <persia> bcj: Try `ubuntu-bug vpnc`
[09:55] <bcj> Copying vpnc-script from the .deb
[09:56] <bcj> At the command line?
[09:56] <persia> Yes.
[09:56] <persia> bcj: What?  The script is in the .deb and not installed?  try dpkg -L vpnc
[09:56]  * persia very much expects it is installed, and something else is up
[09:56] <bcj> Yes
[09:57] <bcj> If I ls /etc/vpnc the file is not there.
[09:57] <bcj> I can do a clean install later and check file permissions/ownership then.
[09:57] <bcj> Now I know how to submit the bug I should be ok.
[09:57] <bcj> Thanks for the help.
[09:58] <geser> If you once remove /etc/vpnc/vpnc-script in the past, dpkg honours your "configuration" at package upgrade
[09:58] <bcj> geser: I hadn't removed it.
[09:59] <bcj> I'll completely uninstall the package and try from scratch - checking file permissions, etc.
[09:59] <persia> bcj: don't forget to *purge* it.  Otherwise it may be respecting a prior deletion of a conffile.
[10:00] <bcj> How does one do that?  I normally do "sudo apt-get autoremove <package>"
[10:00] <bcj> sudo apt-get purge <package>?
[10:00] <geser> "sudo apt-get --purge remove vpnc"
[10:00] <bcj> Thanks
[10:01] <bcj> A bug will be submitted later if I can reproduce the problem.
[10:03] <duanedesign> persia: well since my last project didnt go so well I am just looking for another to help with reviewing patches
[10:04] <persia> duanedesign: I tend to shy away from kernel bugs, unless I'm closely coordinating with the #ubuntu-kernel folk.  The patch in question was submitted by one of them, so I suspect she doesn't need help to land it.
[10:05] <duanedesign> heh, yeah probablly not :)
[10:29] <kmdm> Morning all - Don't suppose there's an easy-ish answer (when backporting a package from lucid to karmic) to the following rejection error from the PPA system: format '3.0 (quilt)' is not permitted in karmic.
[10:29] <geser> kmdm: you need to transform the package back to v1 source format, which might be easy or not depending on the used v3 features
[10:31] <kmdm> geser: *nod* - I've no experience with where the v3 / v1 comes into play, is there a quick dummies guide for where to look etc..?
[10:31] <duanedesign> persia: any hints on what i should look for on list of bugs with the 'patch' tag to work on.
[10:33] <geser> kmdm: the changelog might give some hints why it was converted to v3. does the package use an .orig.tar.gz or .orig.tar.bz2?
[10:33] <persia> duanedesign: I generally look at the bugs for the packages that have the tag.  If a package looks unloved, I tend to try to triage/fix all the bugs all at once.
[10:34] <persia> duanedesign: If a package looks well-tended, I tend to look for something else.
[10:34] <duanedesign> ahh, good idea
[10:34] <duanedesign> thank you
[10:39] <kmdm> geser: .tar.gz (it's asterisk 1.6.2.2-1ubuntu2)
[10:45]  * kmdm reads http://wiki.debian.org/Projects/DebSrc3.0
[10:51] <Rhonda> kmdm: Usually it is just a "rm -r debian/source" away.
[10:52] <kmdm> Rhonda: That's exactly what I just did... just gotta wait and see now :)
[11:03]  * kmdm peers at the ppa system: liblua5.1-0-dev: Depends: libreadline5-dev but it is not going to be installed
[11:06] <kmdm> they install fine on my karmic machine
[11:07] <kmdm> and that builds fine under pbuilder... well, that's me confused ;)
[11:08] <kmdm> http://launchpadlibrarian.net/40683304/buildlog_ubuntu-karmic-i386.asterisk_1%3A1.6.2.2-1ubuntu2~karmic1~ppa1_FAILEDTOBUILD.txt.gz
[11:17] <pufuwozu> Hi everyone
[11:17] <pufuwozu> I'm trying to package up a Python extension
[11:18] <pufuwozu> I've uploaded it to REVU, here: http://revu.ubuntuwire.com/p/python-pybox2d
[11:18] <pufuwozu> My lintian output is giving me a few warnings: http://revu.ubuntuwire.com/revu1-incoming/python-pybox2d-1003090142/lintian
[11:18] <pufuwozu> Is there anything I can do about them?
[11:19] <persia> -1 is only correct if you're planning a Debian upload, in which case the name in the last changelog entry needs to match something in Maintainer: or Uploaders:
[11:20] <persia> If you target Ubuntu, consider -0ubuntu1, which won't show those messages.
[11:20] <pufuwozu> So I can just add -0ubuntu1 to a new package?
[11:22] <persia> Instead of -1, yes.
[11:26] <pufuwozu> Thanks persia, that helps heaps!
[12:25] <soc> hi
[12:25] <soc> any plans/time to package intellij for 10.04?
[12:26] <directhex> too late afaik
[12:26] <persia> soc: Time no.  For plans, check the needs-packaging bugs on LP.
[12:27] <soc> ok
[12:34] <soc> https://bugs.launchpad.net/ubuntu/+bug/516252
[12:34] <soc> this is it
[12:34] <persia> Looks like nobody claimed it yet.
[12:35] <persia> Just subscribe to the bug, and if someone claims it, they *should* update it.
[12:39] <soc> ok, done
[12:39] <soc> would be nice to have that additional ide in ubuntu
[12:40] <persia> Mostly needs someone to package it.  You could, if you like.
[12:40] <soc> i have no experience in packaging java things ...
[12:40] <soc> i've done some fonts, but i guess i can't do that without extensive guidance ...
[12:41] <soc> and i have exams atm :-/
[12:41] <persia> Maybe later, if someone else doesn't get to it first :)
[12:41] <soc> :-)
[12:42] <soc> imho, it would be intelligent to package the raw intellij thing without any functionality (plugins) first, even without the plugins which are delivered normally
[12:43] <soc> and then do things like intellij-idea-java,  intellij-idea-scala,  intellij-idea-groovy,  intellij-idea-maven,  intellij-idea-ant,  intellij-idea-git etc.
[12:43] <soc> this way dependencies would be more manageable
[12:45] <soc> btw, i just wonder why we still have that 32bit flashplayer in the 64bit repos ...
[12:59] <skwashd> ttx: you about?
[12:59] <skwashd> testing your solr build atm
[12:59] <skwashd> hit a snag
[13:00] <ttx> skwashd: tell me
[13:01] <skwashd> ttx: java.io.IOException: Cannot create directory: /usr/share/solr/data/index
[13:01] <skwashd> i'm suspecting that is a build/packaging issue
[13:01] <skwashd> it should be using /var/lib/solr/data/index iirc
[13:01] <ttx> skwashd: it's probably also present in the debian build, since I didn't touch anything near permissions
[13:02] <skwashd> ttx: the path doesn't exist
[13:02] <ttx> skwashd: mind moving this discussion to #ubuntu-java ? thkoch, debian solr maintainer, hangs there
[13:03] <skwashd> ttx: no worries
[13:03]  * skwashd jumps 1 chan right
[15:47] <gamesNvideos> hi
[15:47] <persia> hey
[15:48] <gamesNvideos> i looked up ubuntu-motu on distrowatch and it brought up ubuntu ultimate. is that correct?>
[15:49] <gamesNvideos> ohh
[15:49] <gamesNvideos> nope
[15:49] <gamesNvideos> ok. i have one question. do you guys receive any kind of compensation?
[15:51] <gamesNvideos> ill take that as a yes
[15:54] <persia> Bother got distracted.
[16:08] <sanderqd> hi, i'm new to packaging and i'm trying to fork a package, so that i can distribute an improved version through launchpad. should i 'bzr branch lp:ubuntu/gnome-applets' or 'apt-cache source gnome-applets'?
[16:08] <persia> They should get you the same source: it's up to you which you want to use.
[16:10] <gamesNvideos> hi again
[16:10] <gamesNvideos> persia
[16:10] <Rhonda> sanderqd: Rather apt-get source, not apt-cache source, but I guess you are aware that that was a mistake. :)
[16:10] <shadeslayer> sanderqd: i did a ppa session on this a few days ago,you can read the log :)
[16:10] <persia> gamesNvideos: Hey.  Sorry for getting distracted before.
[16:10] <gamesNvideos> no problem, persia
[16:11] <sanderqd> ok, thanks! will look at the logs
[16:11] <Rhonda> gamesNvideos: Depends on what you consider compensation. There is no payment involved, if you mean that.
[16:11] <persia> gamesNvideos: We tend to discourage "Ubuntu Ultimate"./
[16:11] <Rhonda> The compensation is rather the self-esteem getting pushed by user feedback. :)
[16:11] <gamesNvideos> ok rhonda was just wondering. are there any other perks?
[16:11] <gamesNvideos> oh
[16:11] <persia> gamesNvideos: How do you mean "perks"?
[16:12] <gamesNvideos> I just meant benefits
[16:12] <Rhonda> "Sounds good on a CV"
[16:12] <gamesNvideos> why do you discourage ubuntu ultimate?
[16:12] <gamesNvideos> CV?
[16:12] <Rhonda> resume
[16:12] <gamesNvideos> oh
[16:12] <Rhonda> curriculum vitae
[16:12] <\sh> what is ubuntu ultimate?
[16:13] <directhex> because it's a single-user operation, of unknown quality. and not all the changes in it are smart, let alone done properly
[16:13] <sanderqd> shadeslayer: was it a session for the Opportunistic Developer Week, or under what category should i find it?
[16:13] <Rhonda> directhex: But then, not all the changes in ubuntu are smart, let alone done properly. Or in Debian, or further upstream. :)
[16:14] <gamesNvideos> does ubuntu have any packages by default that could be used by any companies to intrude on a persons privacy?
[16:14] <persia> gamesNvideos: "Ubuntu Ultimate" is based on a script that was based on other scripts, that has a long history.  Several revisions have been code-revewed, and they all did things in ways that we feel are wrong.  Most of the effects can be achieved usefully in other ways.
[16:14] <directhex> Rhonda, right. but at least they're more tested!
[16:14] <shadeslayer> sanderqd: itll be under ubuntu classroom packaging
[16:14] <directhex> gamesNvideos, it ships a web browser. do you know what "cookies" are?
[16:14] <gamesNvideos> yes
[16:14] <sanderqd> shadeslayer: great, found it
[16:14] <directhex> well then
[16:14] <gamesNvideos> any software packages?
[16:15] <gamesNvideos> besides the webbrowser
[16:15] <\sh> oh ubuntu ultimate is an evolution of ubuntu-extreme-rm_Rf /
[16:15] <persia> gamesNvideos: There's no "call home" function by default.  If you use a browser, the information collected by anywhere to which you connect is another matter (this is OS independent).  Some features integrate with network services that require more authentication, but none of them are mandatory.
[16:15] <shadeslayer> persia: btw i missed out a few points during the class,youll have to read the bottom part first to complete it successfully
[16:15] <shadeslayer> meh
[16:15] <shadeslayer> sanderqd: ^^
[16:15] <Rhonda> gamesNvideos: Like, IM clients, or email clients?
[16:15] <gamesNvideos> Rhonda, any applications at all
[16:15] <directhex> \sh, remember "ultamatix"? iirc that one uses "killall" a lot to in its package manglement
[16:15] <gamesNvideos> any packages
[16:16] <Rhonda> gamesNvideos: Or technically all network services, that's not too much limited to web browsers and cookies, but that's an example that people easily understand.
[16:16] <directhex> popcon! i don't think that's by default though
[16:16] <persia> directhex: That was the most immediate precessesor to "Ultimate Ubuntu"
[16:16] <directhex> persia, they're the same thing. link to ultamatix right from ultimateedition.inf
[16:16] <persia> shadeslayer: Hrm?
[16:16] <directhex> o
[16:16] <gamesNvideos> no i mean like call home features and back doors
[16:17] <shadeslayer> sanderqd: oh and dont forget to move your debian/ folder into the new upstream untarred folder
[16:17] <shadeslayer> persia: my bad ;)
[16:17] <persia> gamesNvideos: There are no call home features by default, and we close any backdoors or other security issues as soon as we discover them.
[16:17] <persia> shadeslayer: No worries.  Just checking :)
[16:17] <\sh> directhex: yes yes..I got it ;)
[16:17] <shadeslayer> sanderqd: i think i forgot to mention that at the end :_
[16:17] <Rhonda> gamesNvideos: Noone sanely doing any distribution would leave in (enabled) call home features and back doors.
[16:17] <sanderqd> shadeslayer: right, thanks
[16:17] <persia> directhex: Nice to see cooperation and collaboration even for things like that :)
[16:17] <Rhonda> gamesNvideos: We even did patch out the "upgrade check" in nexuiz that did sort-of call home.
[16:18] <gamesNvideos> so if open a music file I downloaded from the internet, there's no way it could call home?
[16:18] <Rhonda> persia: Well, some packages still might have call-home features that go undetected.
[16:18] <persia> gamesNvideos: For most formats (e.g. .flac, .aac, .ogg, .mp3) it shouldn't do
[16:18] <matttbe> Hello, I'm part of Cairo-Dock team (maybe persia, you remember me). We still not receive an ack about our 2 bugs (CD upgrade), should we worry :) ?
[16:18] <directhex> gamesNvideos, well, if the media player crashes, then you're given the option of uploading a crash report that may include the filename or parts of the file
[16:19] <persia> Rhonda: I believe everything in the default set got at least minimal code audit, but maybe :)
[16:19] <gamesNvideos> persia, what if its a flash music video that was downloaded and played in totem?
[16:20] <directhex> recent banshee has optional call-home
[16:20] <persia> matttbe: It's good to remind us, because of the freeze tomorrow.  Which were the bugs again?
[16:20] <matttbe> persia: https://bugs.launchpad.net/ubuntu/+source/cairo-dock/+bug/521534
[16:20] <matttbe> and https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/521536
[16:20] <persia> gamesNvideos: flash can do anything it wants.  There may be enough bugs in how totem handles flash to prevent call-home, but possibly not.
[16:20] <gamesNvideos> ok
[16:21] <gamesNvideos> thanks a lot for your answers. and thanks for your efforts for ubuntu.
[16:21] <persia> Anyone from the release team about?  Could you check matttbe's bugs?
[16:21] <matttbe> persia: the debian files are ready, we just need an ack
[16:21] <matttbe> it seems that cjwatson, iulian, Riddell, pitti, nhandler, ScottK, sistpoty or slangasek can help us :)
[16:22] <persia> Well, yes, but I don't like to highlight them all at once :)
[16:22] <matttbe> oh, sorry
[16:23] <persia> If nobody was here, I'd have asked in #ubuntu-release.  Since you've highlighted them all, maybe they'll respond here.
[16:23] <matttbe> persia: ok, thanks again for your help !
[16:23] <persia> No problem.  Good luck on getting those approved.
[16:24] <Rhonda> persia: Things happened to slip in in the past, and I doubt that the tex age check was only overlooked in debian. :)
[16:25] <Rhonda> persia: Well, flash itself can do anything indeed. flash *video* though is a totally different topic.
[16:26] <persia> Rhonda: Heh.  Good point.
[16:26] <persia> Rhonda: Flash Video doesn't support ActionScript?
[16:26] <matttbe> persia: thanks but I hope we don't need luck because you see... "luck" is not our friend with official Cairo-Dock Ubuntu packages :þ
[16:27] <Rhonda> persia: I doubt that.
[16:27] <Rhonda> persia: clive some youtube video that has overlay text and play it and you'll see that it doesn't contain those.
[16:27] <Rhonda> That's part of the webbased inline flash player, not part of the flash _video_ layer.
[16:28] <Rhonda> … besides that one always has the option to download mp4 instead of flv or convert on oneself.
[16:29] <persia> Rhonda: Ah.  I didn't know that, but yeah, transcoding would make it go away even if I hadn't been wrong.
[16:29] <sistpoty|work> matttbe: I assume you've tested cairo-dock and cairo-dock-plug-ins extensively?
[16:30]  * persia notes that matttbe is part of upstream
[16:30] <matttbe> sistpoty|work: yes of course, this branch is tested by many people on our repositories
[16:30] <sistpoty|work> matttbe: excellent, FFe granted.
[16:30] <didrocks> sistpoty|work, persia: FYI, I gave a look too at the packaging side and now it's cleaned
[16:31] <persia> didrocks: Feel like uploading, now that it has FFe?
[16:31] <didrocks> persia: sure :)
[16:31] <matttbe> thanks guys :)
[16:31] <persia> sistpoty|work: Thanks for the accellerated IRC response.
[16:31] <sistpoty|work> np
[16:43] <siretart`> superm1: FYI, I've now finally pushed my local changes to the mplayer package now, bdrung is currently reviewing my changes
[16:45] <superm1> great, thanks to hear
[16:45] <superm1> er thanks, great to hear
[16:45] <siretart`> http://git.debian.org/?p=pkg-multimedia/mplayer.git;a=shortlog;h=refs/heads/ubuntu in case you want to join :-)
[17:12] <wrapster> lets assume that pkg P1 was providing a binary B1 in some older version of P1 , now supposing over a period of time P1 evolved into P10(1--->10 mean so many build changes...)and now the the binary provided by P1,aka-P10 is moved to a different pkg.. say P'10. In such a case if dist-upgrade is run from the older machine it fails.. what could be the best solution to rectify this?
[17:15] <joaopinto> wrapster, http://www.debian.org/doc/debian-policy/ch-relationships.html -> check Conflicts and Replaces
[17:16] <joaopinto> P10 replaces files from P1
[17:38] <ScottK> bdrung: Why did you upload python-utmp with native packaging versioning?
[17:38] <ScottK> Oh, I see Debian did the same.
[17:39] <ScottK> Weird
[17:39] <bdrung> ScottK: python-utmp?
[17:39] <ScottK> Yeah, you sponsored it a while ago.
[17:39] <ScottK> https://launchpad.net/ubuntu/+source/python-utmp/0.8ubuntu1
[17:39] <ScottK> I see now you just followed what Debian did.
[17:40] <bdrung> ScottK: https://bugs.launchpad.net/ubuntu/+source/python-utmp/+bug/496397/comments/9
[17:41] <ScottK> bdrung: Thanks.
[17:47] <sanderqd> so what would be the most launchpad-y way to create a package for my gnome-applets customization? first fork gnome-applets to make the change, export a patch, then fork ~ubuntu/gnome-applets to import the patch and create a package from that?
[17:48] <sanderqd> s/~ubuntu/gnome-applets/lp:ubuntu/gnome-applets
[17:50] <sanderqd> i see 3 branches: lp:gnome-applets (which is a clone from git.gnome.org), lp:ubuntu/gnome-applets (which contains the source code and debian/), and lp:~ubuntu-desktop/gnome-applets/ubuntu (which only contains debian/). i'm confused :-)
[18:07] <sanderqd> never mind, got my answer
[18:07] <geser> sanderqd: lp:gnome-applets is the imported upstream branch, lp:ubuntu/gnome-applets is the packaging branch (generated from the source packages), and lp:~ubuntu-desktop/gnome-applets/ubuntu is the bzr branch the ~ubuntu-desktop uses for maintaining the the debian directory (IIUC they use the upstream .tar.gz, a checkout from the ~ubuntu-desktop/gnome-applets/ and build a source package from both)
[18:10] <sanderqd> geser: right, that's clear, thanks!
[18:18] <vincs> Hi Masters of the Universe
[18:21] <lfaraone> For "Replaces:", can I use a version number? (ie. autokey-common replaces files in autokey less than 0.61.4)
[18:22] <geser> yes
[18:26] <vincs> I have uploaded my first package to REVU. If someone can comment my work I would be glad.  I am not in a hurry as Lucid is not even published. http://revu.ubuntuwire.com/p/libglobalhotkeys-ruby1.8
[18:27] <geser> vincs: why limiting the architecture to i386 and amd64? doesn't it work on others?
[18:29] <vincs> I do not have test it on other. Is any a valid string for architecture ? (It did not work on my ppa a long time ago)
[18:29] <Rhonda> Just put any. :)
[18:30] <vincs> Ok. I will.
[18:30] <geser> and you shouldn't hard-code library names into Depends but use dpkg-shlibdeps instead
[18:30] <geser> or isn't this dependency not recognized?
[18:31] <Rhonda> vincs: And leave standards version as 3.8.4, lintian will eventually recognize it. :)
Thanks.
[18:32] <Rhonda> vincs: Actually, the version in lucid should already recognize it, as the version in karmic-backports
[18:33] <vincs> For library name, I never use  dpkg-shlibdeps that is why I have harcoded them.
[18:33] <Rhonda> You should never do that.
[18:34] <Rhonda> Put ${shared:Depends} into there.
[18:35] <Rhonda> dpkg-shlibdeps -Tdebian/substvars -dDepends $(CURDIR)/debian/tmp/usr/lib/ruby/* should do the trick.
[18:35] <geser> ${shared:Depends}? not ${shlibs:Depends}?
[18:35] <vincs> Should I use only ${shared:Depends} in depends? What for Build-Depends ?
[18:36] <Rhonda> But you might want to settle for using debhelper instead of ding all the stuff in the rules files directly.
[18:36] <Rhonda> Ah, right, geser has it properly.
[18:36] <Rhonda> Qq
[18:37] <Rhonda> You also want to add install to the .PHONY targets
[18:38] <vincs> I have do all stuff in rules cause I am learning packaging but il will take a look at debhelper.
[18:38] <vincs> I have forgotten the .PHONY rule!
[18:39] <Rhonda> If you really want to understand packaging without debhelper, you might want to take a look at e.g. netris. :)
[18:41] <vincs> Maybe I will. But maybe I should take a look at debhelper before.
[18:41] <Rhonda> I expect debhelper to be the better idea in the long run, unless you really want to dig into handmade rules and understand what all this dh magic does. :)
[18:42] <vincs> Should I hardcoded "Build-Depends" ?
[18:42] <Rhonda> No.
[18:42] <Rhonda> Oh.
[18:42] <Rhonda> Wait, yes, of course.
[18:44] <vincs> Ok hardcoded package in "Build-Depends" and "${shared:Depends}" in "Depends".
[18:44] <sanderqd> if i want to put this patch inside ubuntu's gnome-panel package, (where) should i attribute the author? http://cvs.fedoraproject.org/viewvc/devel/gnome-panel/panel-padding.patch?view=markup
[18:45] <vincs> Is there a good place to learn dh magick ?
[18:50] <cemc> what can I do if I want to build a package on Hardy, but dpkg-source: error: Unsupported format of .dsc file (3.0 (quilt))
[18:53] <Rhonda> cemc: rm -r debian/source
[18:54] <Rhonda> vincs: persia sometimes gives debhelper lectures. Not sure if one got recorded somewhere, though.
[18:59] <vincs> Rhonda: I gonna to google persia and dh. Thanks.
[19:00] <vincs> Should I move my rules file to dh or is it acceptable the way it is ?
[19:14] <Rhonda> vincs: Whatever suits you better. But you might find more people happier if you move to debhelper. :)
[19:15] <Rhonda> happier as in being able to help you out
[19:15] <Rhonda> or take over
[19:18] <vincs> I will let it that way for now. I gonna learn debhelper before uploading my next package. Then I will move this one to dh (for the next version!).
[19:40] <micahg> a no source change against a debian version of a package should have what version?
[19:49] <ajmitch> micahg: just a rebuild, is it?
[19:50] <Laney> dch -R will give you the right version
[19:52] <micahg> Laney: k, but that won't conflict if debian does the same thing?
[19:52] <Laney> no
[19:52] <micahg> Laney: k, thanks
[19:54] <cemc> how can I include the orig tarball when uploading to PPA ?
[19:55] <geser> debuild -S -sa
[19:55] <vincs> Thanks Rhonda and geser. I gonna upload the changes. For comments on REVU, I suppose that I have to wait for Lucid release.
[19:58] <cemc> geser: thx
[20:40] <kenpark> hi porthose
[20:43] <porthose> kenpark, hey :)
[20:45] <kenpark> porthose: got around to comment on bug #533989 - just wanted to say hi and check 'cause my explaination is somewhat.. well not really pretty :-)
[20:45] <porthose> kenpark, np, working on a fix right now :)
[21:08] <sanderqd> when using quilt, does it matter whether i've applied the patches to the working dir or not?
[21:08] <sanderqd> never mind, i see that quilt applies them before building
[22:51] <porthose> kenpark, ping! see PM :)
[22:53]  * kenpark wakes up
[22:54] <kenpark> Wonderful work prothose, will test tomorrow.
[23:27] <getxsick> hi
[23:28] <LLStarks> hi. i noticed that the gstreamer stack has been updated save for -bad. is that on the queue?
[23:29] <Adri2000> at this point in the release cycle, what are the chances that I get an ack from the release-team to sync a NEW package from debian?
[23:29] <Adri2000> 9p
[23:29] <Adri2000> oops, sorry
[23:45] <getxsick> my package depends on libbz2 however there is libbz2-1.0, when i try `apt-get install libbz2` it seems like this is a virtual package. but i get an error when i try to install my package. do i have to set dependencies on libbz2-1.0 ?