=== Logan__ is now known as Logan_ | ||
alo21 | hi all | 05:52 |
---|---|---|
alo21 | What should I do to upload a package into the repository of the current release? | 05:54 |
=== glebihan_ is now known as glebihan | ||
=== pi-rho|away is now known as pi-rho | ||
alo21 | TheLordOfTime: here I am... the oackage is only in Ubuntu | 18:36 |
TheLordOfTime | did you see my last privmsg? | 18:36 |
TheLordOfTime | for uploading, only Ubuntu Devs, Sponsors, the SRU team, and I think the Security team have uplaod rights | 18:36 |
TheLordOfTime | (there may be others!) | 18:36 |
TheLordOfTime | but the process is to file an SRU | 18:36 |
TheLordOfTime | and either branch the package's code and update it (then file a merge request) | 18:36 |
TheLordOfTime | or attach a debdiff to the bug | 18:37 |
TheLordOfTime | apply the SRU template | 18:37 |
TheLordOfTime | and then subscribe ubuntu-sponsors (i think) | 18:37 |
TheLordOfTime | you may need to subscribe the SRU team | 18:37 |
alo21 | TheLordOfTime: why they accept only one bug per upload? | 18:37 |
TheLordOfTime | that's not what i said | 18:37 |
TheLordOfTime | so apparently you don't listen. | 18:38 |
TheLordOfTime | <TheLordOfTime> but i'm not sure whether multiple-bug-fixes will be accepted. | 18:38 |
TheLordOfTime | Typically, bugfixes should be "separate" for SRUs. | 18:38 |
TheLordOfTime | the idea is only the smallest code change per "fix" is accepted | 18:38 |
TheLordOfTime | 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:38 |
TheLordOfTime | but those two don't interfere with each other | 18:39 |
TheLordOfTime | 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 |
TheLordOfTime | 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 |
TheLordOfTime | but again | 18:39 |
TheLordOfTime | i'm not on the SRU team. | 18:39 |
TheLordOfTime | 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 |
TheLordOfTime | (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:40 |
TheLordOfTime | 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 |
xnox | 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 |
TheLordOfTime | ^ that | 18:42 |
* xnox is core-dev | 18:42 | |
TheLordOfTime | hah, nice | 18:42 |
TheLordOfTime | xnox: isnt that a subset of the dev team? | 18:42 |
xnox | alo21: please read https://wiki.ubuntu.com/StableReleaseUpdates | 18:42 |
TheLordOfTime | or is it its own "dev team" | 18:42 |
=== cheako911 is now known as cheako | ||
TheLordOfTime | i try not to do SRUs. Typically, all I do are security updates. Or major-fix SRUs... | 18:43 |
TheLordOfTime | although most my SRUs are for php5 :P | 18:43 |
alo21 | TheLordOfTime: xnox ok... thanks. I thins use private PPA is the fastest way for my aim | 18:43 |
TheLordOfTime | to get a fix that you can use, yes. | 18:44 |
TheLordOfTime | but remember: PPAs arent technically "supported: | 18:44 |
TheLordOfTime | !ppa | 18:44 |
ubot2` | 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 |
xnox | 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 |
TheLordOfTime | LOL | 18:44 |
TheLordOfTime | xnox: out of pure curiosity, who can upload to -proposed? is that also the same "upload-worthy" teams? | 18:44 |
xnox | TheLordOfTime: fromt that queue: ubuntu security or sru teams can promoted packages into -proposed, -updates, -security etc. | 18:44 |
TheLordOfTime | ah, so there's this queue of basically limbo :P | 18:45 |
TheLordOfTime | before a specific team uploads to the intended repo :) | 18:45 |
TheLordOfTime | i know Security targets -security, so... | 18:45 |
TheLordOfTime | :P | 18:45 |
* TheLordOfTime has fixed a couple of CVEs in NGINX :P | 18:45 | |
TheLordOfTime | well... | 18:45 |
TheLordOfTime | "debdiff'd the patches" is a better way of saying that :P | 18:45 |
xnox | 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:45 |
TheLordOfTime | s/call/can/ ? | 18:46 |
xnox | yeah.... =) | 18:46 |
* xnox can't type | 18:46 | |
TheLordOfTime | no problem :) | 18:48 |
TheLordOfTime | which explains why debdiffs or code merges are preferred for updates :P | 18:48 |
TheLordOfTime | the debdiffs can be applied and uploaded. | 18:48 |
xnox | yes. | 18:48 |
xnox | and it's a moving target | 18:48 |
TheLordOfTime | indeed | 18:48 |
xnox | any potential SRU can be "overtaken" by -security update | 18:48 |
xnox | before you know it =) | 18:48 |
TheLordOfTime | indeed | 18:49 |
TheLordOfTime | saw that happen for nginx once... :P | 18:49 |
TheLordOfTime | oop, i think i found a bug in apt :P | 19:19 |
TheLordOfTime | it was not resolving the dependencies for the linux kernel :/ | 19:19 |
TheLordOfTime | http://pastebin.com/VgWQ6Ng1 if you're curious to see what i was seeing | 19:20 |
xnox | TheLordOfTime: use dist-upgrade | 19:21 |
xnox | no but, expected behaiviour. | 19:21 |
TheLordOfTime | xnox: actually i used aptitude upgrade --full-resolver | 19:22 |
TheLordOfTime | it just wasnt resolving the deps | 19:22 |
TheLordOfTime | :P | 19:22 |
xnox | there is no bug. | 19:23 |
TheLordOfTime | *shrugs* | 19:24 |
TheLordOfTime | seemed like a bug | 19:24 |
TheLordOfTime | dist-upgrade will upgrade to 12.04.1 right? | 19:24 |
TheLordOfTime | or is that a compulsory upgrade? | 19:25 |
xnox | upgrade: will not remove or upgrade unrelated packages | 19:25 |
xnox | dist-upgrade: will offer to remove or upgrade unrelated package to complete the upgrade | 19:25 |
xnox | read the manpage $ man apt-get | 19:26 |
TheLordOfTime | the second question was unrelated | 19:26 |
xnox | dist-upgrade does not "change" target distributions. | 19:26 |
TheLordOfTime | is 12.04.1 a compulsory or voluntary upgrade? | 19:26 |
xnox | it you are on lucid, you will stay on lucid. | 19:26 |
TheLordOfTime | i'm on precise | 19:26 |
xnox | 12.04.1 is nothing bug 12.04 + packages from '-security' & '-updates' pockets. | 19:27 |
xnox | s/bug/but/ | 19:27 |
xnox | and new ISOs with packages from '-updates' | 19:27 |
TheLordOfTime | ah | 19:27 |
TheLordOfTime | i see | 19:27 |
=== pi-rho is now known as pi-rho|away |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!