=== Logan__ is now known as Logan_ [05:52] hi all [05:54] What should I do to upload a package into the repository of the current release? === glebihan_ is now known as glebihan === pi-rho|away is now known as pi-rho [18:36] TheLordOfTime: here I am... the oackage is only in Ubuntu [18:36] did you see my last privmsg? [18:36] for uploading, only Ubuntu Devs, Sponsors, the SRU team, and I think the Security team have uplaod rights [18:36] (there may be others!) [18:36] but the process is to file an SRU [18:36] and either branch the package's code and update it (then file a merge request) [18:37] or attach a debdiff to the bug [18:37] apply the SRU template [18:37] and then subscribe ubuntu-sponsors (i think) [18:37] you may need to subscribe the SRU team [18:37] TheLordOfTime: why they accept only one bug per upload? [18:37] that's not what i said [18:38] so apparently you don't listen. [18:38] <TheLordOfTime> but i'm not sure whether multiple-bug-fixes will be accepted. [18:38] Typically, bugfixes should be "separate" for SRUs. [18:38] the idea is only the smallest code change per "fix" is accepted [18:38] in the case of the last SRU I did, I was told by a member of the Ubuntu Server Team to include two bugfixes into one SRU [18:39] but those two don't interfere with each other [18:39] the idea with bugfixing is that patches which contain the smallest fixes should be used. such that the fix can be tested individually [18:39] in the event a fix doesn't fix the bug, or makes the thing unstable, it can be rejected for that individual fix [18:39] but again [18:39] i'm not on the SRU team. [18:40] if you *want* to include multiple bug fixes, you're free to try, but each bug you're fixing would need linking *back* to that merge/debdiff-upload you do [18:40] (you'd only do that *once*, to *one bug*, and attach SRU templates, and link the other bugs you're fixing to that merge request/debdiff) [18:42] anyone on the MOTUs would be able to point you to the right information, the package you told me (subdownloader) is in Universe, so... [18:42] alo21: you can open one metabug with SRU & debdiff; but it should close all individual sru bugs, and each bug needs a template & steps to test & verify changes. [18:42] ^ that [18:42] * xnox is core-dev [18:42] hah, nice [18:42] xnox: isnt that a subset of the dev team? [18:42] alo21: please read https://wiki.ubuntu.com/StableReleaseUpdates [18:42] or is it its own "dev team" === cheako911 is now known as cheako [18:43] i try not to do SRUs. Typically, all I do are security updates. Or major-fix SRUs... [18:43] although most my SRUs are for php5 :P [18:43] TheLordOfTime: xnox ok... thanks. I thins use private PPA is the fastest way for my aim [18:44] to get a fix that you can use, yes. [18:44] but remember: PPAs arent technically "supported: [18:44] !ppa [18:44] A Personal Package Archive (PPA) can provide alternate software not normally available in the offical Ubuntu repositories - Looking for a PPA? See https://launchpad.net/ubuntu/+ppas - WARNING: PPAs are unsupported third-party packages, and you use them at your own risk. See also !addppa and !ppa-purge [18:44] TheLordOfTime: the structure is interesting many people can upload into Dev series (e.g. core-dev, motu, per-package uploaders), and the same people can sponsor uploads into $stable, but all of them simply end up in "Unapproved" queue. [18:44] LOL [18:44] xnox: out of pure curiosity, who can upload to -proposed? is that also the same "upload-worthy" teams? [18:44] TheLordOfTime: fromt that queue: ubuntu security or sru teams can promoted packages into -proposed, -updates, -security etc. [18:45] ah, so there's this queue of basically limbo :P [18:45] before a specific team uploads to the intended repo :) [18:45] i know Security targets -security, so... [18:45] :P [18:45] * TheLordOfTime has fixed a couple of CVEs in NGINX :P [18:45] well... [18:45] "debdiff'd the patches" is a better way of saying that :P [18:45] TheLordOfTime: yeah. more or less. So if you call upload the package, you can upload into -proposed apart from it being stuck in the unapprove queue before it actually gets uploaded into -proposed. [18:46] s/call/can/ ? [18:46] yeah.... =) [18:46] * xnox can't type [18:48] no problem :) [18:48] which explains why debdiffs or code merges are preferred for updates :P [18:48] the debdiffs can be applied and uploaded. [18:48] yes. [18:48] and it's a moving target [18:48] indeed [18:48] any potential SRU can be "overtaken" by -security update [18:48] before you know it =) [18:49] indeed [18:49] saw that happen for nginx once... :P [19:19] oop, i think i found a bug in apt :P [19:19] it was not resolving the dependencies for the linux kernel :/ [19:20] http://pastebin.com/VgWQ6Ng1 if you're curious to see what i was seeing [19:21] TheLordOfTime: use dist-upgrade [19:21] no but, expected behaiviour. [19:22] xnox: actually i used aptitude upgrade --full-resolver [19:22] it just wasnt resolving the deps [19:22] :P [19:23] there is no bug. [19:24] *shrugs* [19:24] seemed like a bug [19:24] dist-upgrade will upgrade to 12.04.1 right? [19:25] or is that a compulsory upgrade? [19:25] upgrade: will not remove or upgrade unrelated packages [19:25] dist-upgrade: will offer to remove or upgrade unrelated package to complete the upgrade [19:26] read the manpage $ man apt-get [19:26] the second question was unrelated [19:26] dist-upgrade does not "change" target distributions. [19:26] is 12.04.1 a compulsory or voluntary upgrade? [19:26] it you are on lucid, you will stay on lucid. [19:26] i'm on precise [19:27] 12.04.1 is nothing bug 12.04 + packages from '-security' & '-updates' pockets. [19:27] s/bug/but/ [19:27] and new ISOs with packages from '-updates' [19:27] ah [19:27] i see === pi-rho is now known as pi-rho|away