=== Zic is now known as Guest2281 [07:02] good morning [08:27] Hi, if I propose a bzr branch merge throw LP without setting a reviewer (don't know who can do the review/upload...) for universe package, do I also need to create a 'bug report'? Or is there a ubuntu team automaticaly notified and someone going to handle it? Or should I better follow https://wiki.ubuntu.com/SyncRequestProcess for people requiring sponsorship and not follow the bzr merge proposal way? [08:56] jfi: IIRC you shouldn't need to do any special things to get your branch sponsored. === ninjak_ is now known as ninjak [08:57] If it's listed on the sponsoring overview page then it should get picked up by a sponsor. [08:59] geser, yes, you are right, it is already in http://reqorts.qa.ubuntu.com/reports/sponsoring/. Thanks. === Guest2281 is now known as Zic === almaisan-away is now known as al-maisan === ricotz_ is now known as ricotz === al-maisan is now known as almaisan-away === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away === almaisan-away is now known as al-maisan === yofel_ is now known as yofel === al-maisan is now known as almaisan-away === Amaranthus is now known as Amaranth === jtechidna is now known as JontheEchidna [22:34] How do you know if pbuilder was successful? [22:34] in running a package? [22:35] running? [22:35] pbuilder builds [22:35] building. [22:35] sorry [22:35] exit code 0 and a result in the result folder [22:35] /var/cache/pbuilder/result by default [22:43] what if there is no result? [22:43] then it likely failed [22:43] if you were building a package [22:43] what does the log say? [22:43] does that mean a failure? (i was only trying out the packaging a new software tutorial at package guide site.) [22:44] where can I find the logs? [22:44] depends how you use pbuilder [22:44] if you use pbuilder-dist the result is in ~/pbuilder/*_result along with the log [22:44] pbuilder-dist precise ... [22:45] what part of the log is appropriate to share? [22:45] pbuilder calls it an invalid version. [22:46] the end is usually enough [22:46] it finished with a time-stamp [22:46] please use a pastebin, e.g. via pastebinit [22:46] what does that mean? [22:47] pastebins are just websites where you can paste text to share [22:47] ahh [22:47] echo "test" | pastebinit [22:47] do developers use pastebins often? [22:48] whoa! [22:48] yes its the most common way to share buildlogs [22:48] that's so cool [22:49] how do I pastebin the command? [22:49] 's results? [22:49] you can just copy it into http://paste.ubuntu.com/ [22:50] http://paste.ubuntu.com/1090686/ [22:50] pastebinit is a useful program to semi automatize this, it takes input from stdin or a file [22:50] looks like it was successful [22:50] ah ok. :) [22:50] there should be a result in ~/pbuilder/ somewhere [22:51] well, it was just a tutorial. how do know if it was successful? by not showing any errors? [22:51] yes [22:51] * epikvision shudders at the countless times of going through this tutorial for the past few weeks. [22:53] how do I use pastebinit? [22:53] for say, an output of a command? [22:54] either you save the log and do "pastebinit log" or you pipe it in with "command | pastebinit" [22:54] you can also just type pastebinit and paste the text followed by ctrl+d [22:54] see the manpage for some more options including syntax highlighting for source code [22:55] ok [23:00] thanks jtaylor for the help [23:01] I feel like I learn more from others than alone. [23:03] does motu do packaging work for the development release too? [23:03] yes [23:05] i heard that it's good practice to run the dev release via chroot. [23:05] you should have lots of chroots to build stuff [23:06] to fully run dev releases VM's are good [23:06] or if its more stable a extra partition [23:06] I tried virtualbox and qemu, and both fails... :( [23:11] we almost only work on the devolpment release, after all, it's the *development* release... [23:53] grah, precise's debmirror has no --config-file [23:54] debmirror takes a config file? [23:54] * tumbleweed is suprised he didn't notice that, considering I've been merging it for the last few releases [23:54] sure it does [23:54] you don't use one? [23:54] no, I use a script [23:55] anything clever? [23:55] (which made a lot of sense for other reasons too, such as rsyncing i18n, before debmirror supported that) [23:56] the most clever bit is that it calls a debmirror in a git checkout, containing all the patches I've submitted upstream that joey hasn't done anything about [23:57] such as the patch that stops my mirror being deleted when my upstream mirror has a hash mismatch [23:57] heh [23:59] * Laney starts the initial armhf sync [23:59] yay for being able to run a local mirror [23:59] it's not as big as i thought actually [23:59] http://paste.debian.net/178975/ [23:59] i hope it can deal with merging them into the same directory