| hallyn | arges: bug 1432644 - you had claimed that bug blocked qemu-kvm users from creating vms. I don't see that. i see a few (16) annoying messages in syslog but vms start just fine. | 03:06 |
|---|---|---|
| ubottu | bug 1432644 in libvirt (Ubuntu) "VM permanently tries to read /dev/shm/lttng-ust-wait-5" [High,Fix released] https://launchpad.net/bugs/1432644 | 03:06 |
| MasterPiece | !help | 11:49 |
| ubottu | Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-) See also !patience | 11:49 |
| === gusnan is now known as Guest44211 | ||
| === Guest44211 is now known as gusnan | ||
| === gusnan is now known as Guest98304 | ||
| === zsombi_ is now known as zsombi | ||
| === Guest98304 is now known as gusnan | ||
| === gusnan is now known as Guest95576 | ||
| === gusnan is now known as Guest75377 | ||
| === gusnan_ is now known as gusnan | ||
| === gusnan is now known as Guest36278 | ||
| === Guest36278 is now known as gusnan | ||
| === gusnan is now known as Guest27177 | ||
| sidi | hi, currently developing patches for nautilus's ubuntu package. i know how to add patches and rebuild a deb, but what i want now is to build a source tree with all the existing patches added, so i can test my code on top of this tree. How can I achieve that? | 19:23 |
| sidi | somewhat bzr bd -S seems to be what I want but I dont know where the source ends up. orig.tar.xz packages dont appear to contain local patches | 19:39 |
| rbasak | sidi: a Debian source package consists of a .dsc, .orig.tar.gz and (usually) .debian.tar.gz. The .debian.tar.gz contains the patches. Build the .dsc with sbuild, which will pick up the other two files automatically. | 19:41 |
| rbasak | sidi: eg. https://wiki.ubuntu.com/SimpleSbuild | 19:42 |
| nabukadnezar43 | are there minimal images of ubuntu daily? | 19:44 |
| nabukadnezar43 | apperantly it's called core | 19:46 |
| sidi | rbasak, say i already have my own working tree, with some patches i wrote and applied and know are valid. I can of course build the whole package with bzr bd and test it, but what i want is to extract the source code of this working tree, along with the already written trees, to manually hack and build it like i'd do with a tarball downloaded off the internet (so I can write the next patch) | 19:46 |
| sidi | it seems to me most tools only want an existing source package (either from apt-cache) or local | 19:46 |
| sidi | so i'd need to build a source package from my working tree to set up this "hacking" source directory? | 19:46 |
| rbasak | sidi: you can install all build dependencies locally if you want (or in a schroot). Then apply all patches with "quilt push -a" but you'll need to set up quilt first - https://wiki.debian.org/UsingQuilt | 19:47 |
| Unit193 | nabukadnezar43: Like http://archive.ubuntu.com/ubuntu/dists/vivid/main/installer-amd64/current/images/netboot/mini.iso ? | 19:47 |
| rbasak | sidi: finally, run "debian/rules build" to build the tree. If the packaging is done well, then you can change the source and "debian/rules build" again | 19:47 |
| sidi | rbasak i'm using quilt atm, i followed http://packaging.ubuntu.com/html/patches-to-packages.html | 19:47 |
| sidi | i'm not sure i got that bit. | 19:48 |
| sidi | what would be the benefit of using sbuild by the way, over just using quilt? I expect to have the non-amd64 packages built on the PPA, not to do it myself | 19:48 |
| rbasak | sbuild builds in a clean environment. Eg. without any additional packages apart from the build dependencies. So other stuff cannot influence the build. | 19:49 |
| nabukadnezar43 | Unit193 thanks that's what i was looking for | 19:49 |
| Unit193 | nabukadnezar43: Great! I presume you can find the 32bit one if needed too. | 19:49 |
| rbasak | (also then you don't have to install all the build dependencies locally, so you don't clutter up your dev system itself) | 19:49 |
| nabukadnezar43 | yes but amd64 is what i need | 19:50 |
| infinity | Unit193: FWIW, linking to http://cdimage.ubuntu.com/netboot/ is a lot less typing and much easier for people to remember more than 5 seconds after you tell them. :) | 19:50 |
| * infinity notes that he needs to remove Saucy from that list, and does so. | 19:51 | |
| Unit193 | infinity: ...That, would help. Yes. Kind of wondered why it wasn't there at one point, turns out.. | 19:51 |
| Unit193 | Thanks. | 19:51 |
| Unit193 | Well I'm a genius... | 19:52 |
| elfy | ... | 19:52 |
| sidi | rbasak i see. i dont think it's a very big deal though if i've only installed an ubuntu for that purpose? or will i reliably run into trouble if i dont use sbuild? (mainly trying to avoid some work here, i wont be needing this build system for more than 1 or 2 months...) | 19:53 |
| maxb | You can probably do most experimental dev work just find without sbuild, but you will always face the possibility of undeclared build-deps or other detected quirks causing a different result on builders to your local testing | 19:55 |
| rbasak | sidi: yeah, what maxb said. So it depends on what sort of thing you're changing. | 19:55 |
| rbasak | If you're messing with stuff that has little to do with the packaging, then you should be fine. | 19:55 |
| === Guest27177 is now known as gusnan | ||
| sidi | alright i see | 19:56 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!