=== exodus_ is now known as exodus [04:19] ScottK: do we support dist-upgrades from lucid -> precise with backports enabled? [04:44] micahg: Yes. [04:45] That's why the versioning has to increase all the way up. [04:46] ScottK: ok, it wasn't relevant in this case, just means we need to be careful backporting xz binaries to lucid and older [04:46] err...precise and older [04:46] Yes. [04:51] it's been a long time since I did an upgrade with backports installed and the backports pocket had anything in it [04:57] micahg: that LP change is almost in, honest :) [04:57] heh, hi ajmitch [04:58] the MP has been approved so I'll probably need a backporter to test that it all works as intended [05:02] ScottK: do you have time to teach me about NEW in backports? [05:02] You don't need to worry about any of the normal New stuff like licensing. [05:03] ok, what do I need to look for? [05:03] I'd just check it doesn't steal an existing binary from something and then normal backports stuff like versioning. [05:03] Stealing a binary may actually be OK, but if it does, then you need to make sure that was really intended. [05:04] ScottK: is binary stealing showed somewhere? [05:04] No. [05:04] ok [05:05] Honestly I don't usually bother to explicitly check for it. [05:05] is that it? [05:05] It's somewhat rare, but it can happen, but often there's a hint. [05:05] (based on package name) [05:05] Yes. [05:05] Ther'es not a lot to it really. [05:06] is that on both source and binary NEW then? [05:07] For binary new, just look at the package and make sure it's not empty/has a sane file layout. [05:07] An existing binary name from a different source won't hit binary New, so you won't see that. [05:08] oh, is that only source NEW that hits? (I thought it hit some type of NEW) [05:10] If it's new in that release, it'll hit new, but if that binary name exists in that release, although built from another source, it won't. [05:12] ok [05:12] ScottK: do I need to worry about component/section/priority in backports? [05:13] You need to worry about Getting Main/Universe or Multiverse right, but not within Main or Universe. Ideally you'd put it in Universe if it were new. [05:14] Priority Ubuntu doesn't care about. [05:14] You shouldn't need to override anything. [05:14] ok [06:41] hi everyone [06:41] I'm trying to build a package with pbuilder-dist, but I get some errors because it is trying to update/install some inexisting packages [06:42] this is what I'm trying to build: pbuilder-dist quantal build ../xfce4-terminal_0.4.8-1ubuntu2.dsc [06:42] and for example it is trying to get libatk1.0-data all 2.5.4-0ubuntu1, but the quantal version is actually 2.5.95 [06:42] what's going wrong here? [06:49] radu: pastebin [06:50] tumbleweed, http://paste.ubuntu.com/1208340/ [06:51] radu: notice all thoso 404 errors? [06:51] run a pbuilder-dist quantal update [06:52] hrm, I thought those were because the package doesn't exist in the repository [06:52] ok, i will try that [06:52] if it doesn't exist, it wouldn't try and download it. It has a list of everything in the repository [07:06] that worked, thanks tumbleweed === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away === imbrando1 is now known as imbrandon === hyperair is now known as Guest14260 === jbicha is now known as Guest21308 === tuomasjj1asanen is now known as tuomasjjrasanen === Guest21308 is now known as jbicha === zz_Kiall is now known as Kiall [16:09] these yaks are looking well groomed [16:09] is yaks the right plural? [16:10] sure is [16:10] heh [16:15] is anyone here more familiar with objective C binary deps? see bug 1051389 [16:15] Launchpad bug 1051389 in sope (Ubuntu) "Sync sope 1.3.16-1 (universe) from Debian unstable (main)" [Undecided,Incomplete] https://launchpad.net/bugs/1051389 [18:04] hi motu people, a few days ago i wrote to the devel-discuss list, that i have ported tilda to gtk+3 and added some new features [18:05] i was invited here to discuss if the new version could be included into the next ubuntu release 12.10 [18:05] isnt 12.10 under freeze? [18:06] i believe the new version has more benefits than disadvantages, and that given these facts a freeze exception would be ok [18:06] it would be nice to discuss that with someone who can actually make such an exception [18:07] i have just written to devel-discuss and explained the changes in tilda 1.0.0 [18:07] unfortunately the gmane archive is a bit slow so i cant post a link right now [18:09] basically the current tilda version in ubuntu is unmaintained since 2009 and has several known bugs [18:09] stgraber, ping [18:09] you'll realize why i'm asking about quantal in -release if you look here. [18:10] TheLordOfTime: I know, I was reading both channels [18:10] wasnt sure [18:10] ;) [18:10] for example it is currently not possible to map the CTRL key to tilda [18:10] anyway, just follow https://wiki.ubuntu.com/FreezeExceptionProcess and you'll have a proper answer [18:11] as I said in -release, if it doesn't impact any of the images we build and is a significant step up to what's currently in the archive, it has good chances of being approved [18:12] stgraber, i'm not in -release, so not sure that was said there [18:13] how do i substribe to ubuntu-release? it seems to be a closed list [18:13] lanoxx, i asked about quantal and the freeze [18:13] :P [18:13] ah ok [18:13] so not specific to your package, just Quantal in general [18:13] :p [18:15] stgraber, so should i file a bug agains tilda with 'ubuntu-bug tilda' ? [18:16] stgraber, i'm still investigating, but the php5 package in quantal might need an FFe for a fix in the docs [18:16] due to this crit level bug: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1047520 [18:16] Launchpad bug 1047520 in php5 (Ubuntu Quantal) "NEWS and release notes need updating" [Critical,New] [18:17] i am still checking, though [18:17] for all i know they actually updated that in Debian and I can mark that as already fixed :p [18:19] that doesn't sound like something that'd require an FFe [18:20] tumbleweed, within the package itself? [18:20] eh? [18:20] tumbleweed, the documentation in php5 would need upating [18:20] not wiki, the actual docs in the package [18:20] assuming they havent updated it of course [18:20] that shouldn't be too problematic [18:21] if that's the case, and 12.10's froze, wouldnlt that need an exempt? [18:21] s/FFe/Feature Exempt/ earlier [18:21] * TheLordOfTime typed too fast [18:21] no, it's a bug fix [18:21] if a freeze exceptions would be granted, then how does it work? will someone of the motu team pull the sources from my git repository and upload it to ubuntu? Or do I have to provide a package are do some other things first? [18:21] are/and [18:21] !sponsorship|lanoxx [18:21] lanoxx: You can find out about the package sponsorship process here http://wiki.ubuntu.com/SponsorshipProcess - For !UDS sponsorship see http://uds.ubuntu.com/participate/sponsorship/ [18:21] basically, you should prepare a debdiff / bzr branch [18:28] tumbleweed, am i required to use bzr (like described in the sponsorship page) or can i also use git? [18:30] a bzr branch / debdiff is preferred iirc [18:32] would be cool if launchpad had integrated git support :) [18:33] lanoxx: we have bzr branches of all ubuntu packages, but not git branches [18:33] but really, if you can use git, you can use bzr. It's easy, unlike git :) [18:34] hmm, i tried to use bzr a few times and i found the way git does branching much more intuitive, but anyway i will take a look, i think there is a bzr frontend for git, so i can just import everything into bzr and use it as an interface for launchpad [18:35] there needs to be common ancestory from the ubuntu package branch, so importing is unlikley to help you [18:35] just generate a debdiff, if you don't like bzr [18:38] when i use pbuilder-dist should i set the name of the version which im running (e.g. precise) or the version for which my package is going to be? [18:39] the latter [18:40] (the point of pbuilder-dist, is that it does everything in a chrootted install of the target distribution) [18:41] does pbuilder download the whole quantal release (700mb)? [18:42] no, just build-essential [18:43] tumbleweed, i see, and where does it store all that stuff? [18:43] ~/pbuilder [18:44] um, there is only a logfile and a 0 byte big tar.gz [18:44] sounds like it failed [18:44] pastebin the output? [18:45] you do need to "pbuilder-dist create" before you can "pbuilder-dist build" [18:45] its still running, but still im currious [18:46] ah ok, now its done and the tar.gz has a 100mb [18:51] so i have done most of the stuff on that sponsoreship page, i just need to finish the gpg part thing, but i remember i already have a gpgkey somewhere so i just have to find that later [18:51] now what would be next? do i file a bug first and ask for a freeze exception or do i create a package first_ [18:51] now what would be next? do i file a bug first and ask for a freeze exception or do i create a package first? [19:02] erm, nothing in preparing a sponsored upload should require a gpg key [19:03] you aren't creating a new package, just updating an existing one. And yes, do that first [19:03] you can't know if updating it is a good idea, unless you've tried, and tested it. And we can't judge the FFe without a proposed patch and some testing [19:05] tumbleweed, https://launchpad.net/~lanoxx <--- does that look like a good start? [19:06] that's your LP account, what am I looking at? [19:11] gpg key and ssh key are already added, im even member of the bug squad, just wanna know if there is anything else i should prepare [19:12] nope, you are set up [19:13] tumbleweed, cool, though the gpg key is from my notebook, is that system dependend or can i somehow copy it on my desktop? [19:13] you won't need it. gpg keys are only needed to sign uploads by ubuntu developers [19:14] e.g. can u just scp the ~/.gnupg folder to my desktop [19:14] (or uploads to PPAs) [19:14] yes, you can [19:14] ah good to know [19:18] alright, i will continue with this tomorrow, so just to be clear, next step is to create an updated package out of the existing tilda package, then upload that to launchpad (somehow), and then file a bug to include it into ubuntu [19:18] tumbleweed, ^ [19:19] either push a branch to LP, or attach a debdiff from the current ubuntu package to your one, to the bug [19:21] and i file the bug with ubuntu-bug tilda against the existing tilda package right [19:22] yes [19:29] alright, thanks then, im gonna be back soon === AlanBell is now known as zAlanBell === zAlanBell is now known as AlanBell === Caesar_ is now known as Caesar