[03:29] <Bluefoxicy> Is 13.04 beyond feature freeze?
[03:29] <Bluefoxicy> I'm trying to find out if some packages can get promoted to main and added to tasksel
[03:39] <jbicha> Bluefoxicy: https://wiki.ubuntu.com/RaringRingtail/ReleaseSchedule
[03:40] <Bluefoxicy> Don't know the difference between FeatureDefinitionFreeze and FeatureFreeze
[03:41] <Bluefoxicy> oh
[03:41] <Bluefoxicy> red links don't mean "not in wiki"
[03:41]  * Bluefoxicy confused by the non-standard color scheme!
[03:42] <Bluefoxicy> Hmm, I guess then for 13.10 this is a target.
[03:44] <jbicha> definitionfreeze is just for planning, MIRs can still be considered for 13.04
[03:44] <jbicha> https://wiki.ubuntu.com/MainInclusionProcess
[03:47] <Bluefoxicy> jbicha: at a cursory glance, looks good.
[03:47] <Bluefoxicy> the packages in question are puppet and puppetmaster
[03:48] <Bluefoxicy> these appear to be maintained fairly well in Debian, and fairly popular in the field.  In fact they're in Ubuntu Universe as a direct import from Debian, I believe.
[03:49] <Bluefoxicy> it does however rely on a number of Ruby packages.
[03:50] <Bluefoxicy> Heh I should actually go through this later when I have time.  Maybe find someone familiar with the process to help me keep on track.  Possibly next week.
[03:51] <bjsnider> jbicha, who would i talk to to find out some technical info about globalmenu?
[03:51] <bjsnider> who designed it?
[04:32] <Bluefoxicy> heh I'm dumb
[04:32] <Bluefoxicy> it's already in main.
=== jtechidna is now known as JontheEchidna
=== yofel_ is now known as yofel
[21:19] <avis-> #ubuntu-offtopic
[23:30] <uKev> hi, anyone who can help my try a patch from launchpad? I'm fimiliar with the normal patch syntax, but I'm a bit confused about the patch/build debian/ubuntu world
[23:30] <uKev> how can I apply a patch to a ubuntu package and then build it?
[23:31] <uKev> I get the source with apt-get source packagename
[23:31] <uKev> the patch was created using debdiff I guess
[23:32] <jtaylor> a debdiff applies like a normal patch on the unpacked packag esource
[23:32] <jtaylor> assuming you have the right version
[23:32] <jtaylor> cd extracted-source; patch -p1 <patchfile
[23:34] <uKev> but patch prints some error, because there is some kind of changelog on top of the diff
[23:34] <uKev> (I'm developer, but not from the ubuntu world)
[23:34] <uKev> I've read through the ubuntu packaging wiki pages
[23:35] <uKev> there was an example on howto create such a patch
[23:35] <jtaylor> if its just the changelog you can remove that part from the patch
[23:35] <uKev> but not on howto test (and build) with it
[23:35] <jtaylor> which package and where is the patch?
[23:35] <uKev> yes, right, bit I was woundering if there isn't any automatic-tool to do such stuff as it looks like ubuntu has a lot of helper scripts
[23:35] <penguin42> uKev: Get the dependencies using apt-get build-dep package name    and then in the tree to   dpkg-buildpackage
[23:35] <jtaylor> not that I know of
[23:36] <jtaylor> for more complex patches usually some vcs is used
[23:36] <jtaylor> like git
[23:36] <uKev> https://bugs.launchpad.net/ubuntu/+source/gnome-games/+bug/995281/+attachment/3166590/+files/04_fix-segfault.patch
[23:36] <ubottu> Ubuntu bug 995281 in gnome-games (Ubuntu) "glines segfault" [Medium,Triaged]
[23:36] <uKev> from https://bugs.launchpad.net/ubuntu/+source/gnome-games/+bug/995281
[23:36] <jtaylor> ok that is no debdiff
[23:36] <jtaylor> its a patch of the original sources which works differently
[23:36] <uKev> yes, I gut the dependencies (that was mentioned in the wiki, so I used apt-get build-dep)
[23:36] <uKev> I got+
[23:38] <uKev> so I apply that patch in some way and just dpkg-buildpackage?
[23:38] <jtaylor> hm that patch seems malformed
[23:39] <jtaylor> how to handle patches for the upstream sources depend on the package
[23:40] <jtaylor> this one is a 3.0 package, so patches are handled via quilt
[23:40] <uKev> but that patch mentions the ubuntu packages, gnome-games-3.4.1 - isn't that right?
[23:40] <jtaylor> you normally would extract the source package, and just run quilt push -a; quilt import <patchfile>
[23:40] <jtaylor> and the build the package
[23:40] <uKev> 3.0 package? what's that?
[23:41] <jtaylor> its just the package source format
[23:41] <bjsnider> source format
[23:41] <jtaylor> there are three, 1.0 which is pretty much free form and the patch system can be anything (including nonexistant)
[23:41] <jtaylor> 3.0 for non debian specific packages uses quilt for patch management
[23:41] <bjsnider> quilt is so easy to use a monkey could be trained in it
[23:41] <jtaylor> which boils down to a folder with the patches and a file defining the ordering
[23:42] <jtaylor> see debian/patches
[23:43] <penguin42> bjsnider: But you don't even need to - there is edit-patch
[23:43]  * penguin42 likes edit-patch
[23:44] <uKev> yes, I read about edit-patch in the wiki
[23:44] <uKev> but I didn't found anything about quilt/package format versions
[23:44] <uKev> I find it quite difficult to get into all that kind of stuff
[23:44] <uKev> but I will keep trying
[23:45] <uKev> so I use edit-patch or quilt to apply it... how would I build it then? dpkg-buildpackage?
[23:48] <jtaylor> yes
[23:48] <jtaylor> dpkg-buildpackage -us -uc if you have no gpg key
[23:49] <penguin42> it's a pity patches take so long to go around the mill
[23:51] <uKev> ok thanks a lot. I will try that.
[23:51] <uKev> If I can verify that the patch solves the issue. I put a comment below it that the patch will work.
[23:51] <jtaylor> this patch should actually work: http://paste.ubuntu.com/1465834/
[23:51] <jtaylor> import it with quilt import
[23:51] <uKev> How do I get someone to integrate the patch into ubuntu?
[23:51] <jtaylor> thats the hard part :)
[23:53] <jtaylor> that its not upstream makes it even harder :/
[23:54] <penguin42> it'd be relatively easy to make a bzr branch with the fix in, but would it get merged if upstream haven't taken it?
[23:54] <uKev> currently the package is completely broken on 32bit... and it's quite widely used (as it's installed per default)
[23:54] <jtaylor> first ubuntu sponsors should be subscribed
[23:54] <jtaylor> that puts it onto the queue
[23:54] <jtaylor> first it must be fixed in raring, which is easy
[23:54] <jtaylor> then follow https://wiki.ubuntu.com/StableReleaseUpdates
[23:55] <penguin42> jtaylor: Can sponsors be subscribed if it's just a patch, or does it need to be bzr'd first?
[23:55] <uKev> what is "raring"?
[23:55] <jtaylor> the development 13.10 release
[23:55] <jtaylor> 130.04
[23:55] <uKev> ah ok.
[23:55] <jtaylor> penguin42: a full patch would be good
[23:56] <jtaylor> but as there is already a patch a sponsor could fill in the packaging busywork
[23:56] <jtaylor> depends on the sponsor
[23:56] <jtaylor> I'd do it but its main, so I can't touch it
[23:57] <jtaylor> but I could create the branch unless uKev wants to do it himself?
[23:57] <jtaylor> let me dig out my 32 bit netbook
[23:57] <uKev> I just want to have it fixed at the end... :)
[23:57] <penguin42> 32bit vms are easier :-)
[23:57] <uKev> yes, I'm installing it in my 32bit vm at the moment...
[23:57] <jtaylor> I'd use a 32 bit chroot with X
[23:58] <jtaylor> but I forgot how to get X to start in it ._.
[23:58] <jtaylor> booting my netbook is faster :)