[00:01] <michaelh1> Hi there.  libatomic-ops-dev needs a one line source code fix to compile on later ARM versions.  I'm new to this - could someone point me at the documentation on how to do this and submit it? (http://www.debian.org/doc/maint-guide/ch-build.en.html assumes a quilt patchset)
[00:17] <geser> michaelh1: https://wiki.ubuntu.com/SponsorshipProcess https://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff that should hopefully help you for the start
[00:28] <achiang> is there a way to get dpkg to just download the .deb of a package?
[00:28] <ebroder> achiang: aptitude has an aptitude download
[00:28] <achiang> ebroder: ah, thank you. i'll go read the man page
[00:28] <ebroder> I think I heard mvo say he added an apt-get download recently (i.e. natty only)
[00:30] <achiang> ebroder: aptitude download works.... almost. now i want to get a different arch. :)
[00:31] <achiang> ah, append=
[02:03] <c2tarun> i was using "sudo pbuilder build <name>.dsc" to build a package, pbuilder found some packages and start downloadiing them. can anyone please tell where can i see the log of this activity???
[02:50] <c2tarun> i got this error while i was practicing packaging from a tutorial. http://paste.ubuntu.com/535431/ please help :(
[02:53] <ajmitch> c2tarun: that looks like quite an old version of brasero you're working with
[02:53] <c2tarun> i was working on a tutorial on this page    https://wiki.ubuntu.com/PackagingGuide/Recipes/PackageUpdate
[02:54] <ajmitch> I suspect that needs to be updated to use a newer package. I think that version of brasero needs some patches to work on a recent system :)
[02:55] <c2tarun> ok, sorry sir i m not familiar with patching stuff now. infact brasero was my first package. any suggestions for me??
[02:56]  * ajmitch is just trying to think of a fairly simple package that wouldn't be too problematic
[02:56] <c2tarun> ok thank you sir :) i'll go for small and easy packages.
[02:57] <ajmitch> yeah, there should be a few that you could practice on :)
[03:10] <abuDawud> if a packaging assignment has been assigned to someone for a year and I want to work on it, is it okay for me to unassign it from them?
[03:11] <ajmitch> I'd generally comment on the bug first & see if there's any response after a few days, though you can probably get started on doing the packaging work
[03:11] <RAOF> abuDawud: I'd try pinging them first, in case there's a reason why it's been hanging around for a year.
[03:13] <ajmitch> also, check that it's not already in ubuntu, debian or on revu
[07:56] <dholbach> good morning!
[08:01] <quadrispro> hi dholbach !
[08:03] <dholbach> hey quadrispro
[11:01] <quadrispro> hi all
[12:09] <andol> I have a question regarding the instructions on https://wiki.ubuntu.com/PbuilderHowto. Wouldn't I also want to have something like this in my configuration, to build against the latest packages? OTHERMIRROR="deb http://se.archive.ubuntu.com/ubuntu/ $DIST-updates main restricted universe multiverse"
[12:09] <andol> (Actually I do suspsect there might be a good reason for only building against the base packages, I just don't know what it is.)
[12:11] <Rhonda> In some cases it's needed to build against updates, but in general it's preferred to not do so.
[12:11] <soren> Rhonda: Why?
[12:11]  * soren always builds with -updates and -security enabled.
[12:12] <ari-tczew> BlackZ: how do you feel after meeting? are you discouraged to contribute? do you will continue strengthen main?
[12:13] <Rhonda> soren: To have least surprises. "Why not?"
[12:17] <BlackZ> ari-tczew: 1. it's ok; 2. no; 3. certainly. Why do you ask?
[12:20] <ari-tczew> BlackZ: I'm watching on contributors behaving and motivation.
[12:22] <soren> Rhonda: Because it's what the buildd's would do.
[12:22] <soren> Rhonda: ...and it's what my own box would do outside of a pbuilder.
[12:23] <Rhonda> soren: The buildds would do? Didn't check their configuration, with same priority, i.e. always pulling in updates, no matter if build-depends are sufficient in the regular release?
[12:23] <soren> Rhonda: Sure.
[12:24] <Rhonda> Actually that's not so "sure" to me
[12:24] <Rhonda> Otherwise I wouldn't ask or be astonished. :)
[12:25] <soren> Rhonda: -proposed builds against -updates and -security.
[12:26] <soren> If we don't even trust -updates ourselves, how could we expect our users to? :)
[12:47] <ari-tczew> how can I avoid to creating files in quilt3 'debian-changes'XXX' ?
[12:47] <kklimonda> ari-tczew: make sure that there are no inline changes to the source.
[12:48] <ari-tczew> kklimonda: there are not... it's related to handle debian/patches
[12:49] <BlackZ> ari-tczew: are you introducing a new patch or is it an existing one?
[12:49] <ari-tczew> BlackZ: I removed deprecated patch and add refreshed
[12:50] <BlackZ> ari-tczew: then pick up the reapplied changes from there and add them to the "deprecated patch". Be sure to run 'pop quilt -a' then remove the generated patch during the build
[12:51] <ari-tczew> BlackZ: example: bug 676303
[12:53] <BlackZ> ari-tczew: usually if upstream introduced minor changes in the files to be patched it should not be a problem to refresh the related patch(es)
[12:55] <BlackZ> ari-tczew: ah sorry, I mean "quilt pop -a" and not "pop quilt -a" :)
[12:58] <Rhonda> BlackZ: rather quilt pop, not pop quilt ;)
[12:58] <Rhonda> oh, you corrected already
[12:58] <BlackZ> Rhonda: :)
[13:00] <ari-tczew> lol
[13:56] <om26er> i am backporting a fix to a debian synced package and debuild does not work unless 'Maintainer' has a @ubuntu email. what should i do?
[13:57] <hrw> om26er: strange - my ubuntu packages have non ubuntu email
[13:57] <tumbleweed> om26er: run update-maintainer
[13:57] <dholbach> (from ubuntu-dev-tools)
[13:57] <dholbach> https://wiki.ubuntu.com/DebianMaintainerField has the reason for it
[14:00] <om26er> tumbleweed, thanks worked
[14:01] <hrw> new-dev-process question: are persons who want to endorse me on a wiki page needs themself to be ubuntu developers?
[14:03] <ScottK> hrw: It's not strictly required, but endoresements from developers are weighed more heavily.
[14:03] <hrw> ok thx
[14:03] <hrw> ScottK: and I understand why
[14:05] <gaurava> hey all ... i am trying to set up a serial console in ubuntu 10.10 for debugging purpose but no luck till this time
[14:06] <siretart> quadrispro: congrats to core-dev membership!
[14:07] <quadrispro> siretart, thank you very much :)
[14:07] <hrw> gaurava: you want to have serial console access to machine or to connect from your machine to serial console?
[14:07] <gaurava> i want to have serial console access to the machine ..
[14:08] <hrw> gaurava: ok
[14:08] <gaurava> actually i am following this article https://help.ubuntu.com/community/SerialConsoleHowto
[14:08] <gaurava> i did all the steps as mentioned in it .. but still not getting any output on my serial console
[14:08] <hrw> gaurava: cd /etc/init/ cp tty1.conf ttyS0.conf?
[14:09] <siretart> hrw: that's not enough
[14:09] <siretart> "sed s,tty1,ttyS0, /etc/init/tty1.conf > /etc/init/ttyS0.conf" should do it
[14:09] <gaurava> currently my ttyS0 contains the following content:
[14:09] <gaurava> start on stopped rc RUNLEVEL=[2345]
[14:09] <gaurava> stop on runlevel [!2345]
[14:09] <gaurava> respawn
[14:09] <gaurava> exec /sbin/getty -L 115200 ttyS0 vt102
[14:11] <gaurava> do i still need to do the changes as suggested by sietart ??
[14:11] <ari-tczew> gaurava: you can press [TAB] for autocomplete nicks
[14:14] <zul> soren: just updated the workitems for the openstack-integration spec fyi
[14:14] <soren> zul: url?
[14:14]  * soren likes things he can click on
[14:14] <zul> soren: one sec
[14:14] <zul> https://blueprints.launchpad.net/ubuntu/+spec/cloud-server-n-openstack-integration
[14:15] <gaurava> ari-tczewsorry i didn't get it
[14:28] <soren> zul: What are "zone files"?
[14:29] <zul> soren: memory and disk sizes...ill change that in the spec
[14:29] <soren> zul: eh?
[14:29] <achiang> mdeslaur: hi, thank you for uploading pbuilder for me; i see that it experienced a FTBFS, but looking at the build log, it looks... unrelated to my change
[14:30] <zul> soren: ie how much memory  you allocate for m1.small
[14:30] <soren> How is that a "zone"?
[14:31] <mdeslaur> achiang: oh?
[14:31]  * mdeslaur looks
[14:31] <mdeslaur> achiang: ugh :)
[14:31] <zul> soren: its not ill update the spec
[14:31] <achiang> mdeslaur: does that build log make any sense to you?
[14:32] <soren> zul: Yay.
[14:32] <mdeslaur> achiang: not yet, but i'm looking into it now
[14:33] <achiang> mdeslaur: i wonder if it's just natty toolchain issues, and not related to the uploaded debdiff at all. has pbuilder been built in natty yet anyway?
[14:34] <mdeslaur> achiang: it had (and it did locally for me with my outdated schroot)
[14:35] <mdeslaur> achiang: but I updated my schroot and it's not building locally anymore
[14:37] <achiang> mdeslaur: a quick scan of pbuilder.8 doesn't show any obviously illegal characters in vim
[14:37] <mdeslaur> achiang: yeah, and doing "LANG=C MANWIDTH=80 man --warnings -E UTF-8 -l pbuilder.8 >/dev/null" in a natty schroot works...
[14:55] <geser> I can reproduce this in my natty pbuilder (but not in my natty chroot)
[14:55] <geser> achiang: I've tested rebuilding 0.199ubuntu1 which fails too
[14:56] <achiang> geser: well, it's a small comfort to know that i didn't directly cause this issue. :-/ thanks
[15:36] <akoskm> hi! if some package is available in the updates/universe repo, how can I enable that repo in pbuilder?
[15:42] <quadrispro> akoskm, by setting COMPONENTS properly in your pbuilderrc file (see man 5 pbuilderrc)
[15:45] <akoskm> quadrispro, thank you
[15:45] <quadrispro> you're welcome
[15:52] <hyperair> quadrispro: i hear you're a core dev now. congrats! =)
[15:53] <quadrispro> thanks hyperair !
[15:53] <hyperair> =)
[17:05] <mdeslaur> achiang: pbuilder is fixed. not your fault :)
[17:09] <achiang> mdeslaur: thank you. i did read some of the scrollback in #ubuntu-devel and saw that a) it was related to locales and b) you were doing a fine job of handling it, so decided to let you keep going. :)
[17:10] <mdeslaur> achiang: by "doing a fine job", you mean "panicking", right? :P
[17:11] <achiang> mdeslaur: i note that the word 'euphemism' is composed of two greek words, 'eu', meaning 'good or beautiful' and 'phemism' meaning 'possible interpretation of random irc text'.
[17:11] <achiang> ;)
[17:12] <mdeslaur> hehehe
[17:25] <achiang> can someone help me recover from a bad natty dist-upgrade? it looks like xulrunner's postinst is hanging indefinitely. i killed the apt-get. my next thought was to purge xulrunner from my system since i use chrome, not firefox, but attempting to purge it seems to cause apt to want to reconfigure it or something...
[17:27] <persia> achiang, maintainer scripts live in /var/lib/dpkg/info/... and can be edited by root.  If you make them completable, you can complete the dpkg operations.  Fixing the system afterwards is an exercise for the user :)
[17:31] <achiang> persia: good hint. i'm a developer, i should be able to fix broken stuff, right? ;)
[17:31] <\sh> achiang: that depends ;)
[17:32] <achiang> persia: is there a way to make apt a little more chatty? can i just stick a 'set -x' at the top of all the xulrunner maintainer scripts and try to see what's going on?
[17:32] <\sh> achiang: you can set -x to the maintainer script in the directory persia mentioned before and start it manually if you want
[17:32] <Sarvatt> achiang: fixed xulrunner-1.9.2 was uploaded already, hopefully it wont be too much longer :)
[17:32] <Sarvatt> achiang: https://bugs.launchpad.net/ubuntu/+source/gcc-4.5/+bug/663294 is the problem
[17:33] <achiang> Sarvatt: ah, thank you for the fish. i am now requesting a fishing lesson. :)
[17:34] <achiang> \sh: ok, right, that makes sense. i was just wondering if there was a more generic way to do it, but that's fine too
[17:35]  * persia usually modifies the stubborn maintainer script and then calls it with `dpkg --configure -a`
[18:23] <ari-tczew> cjwatson: is it true, that do you planning sponsor bug 662276? if not, I'll subscribe ubuntu-sponsors
[18:25] <ari-tczew> BlackZ: I found the merge bug, which could interest you ;) bug 507778
[18:28] <micahg> version is out of date
[18:33] <ari-tczew> micahg: ?
[18:34] <micahcowan> ari-tczew, perhaps he means that the current Debian testing version is 1:2.0.6-1
[18:34] <micahg> yep
[18:35] <ari-tczew> micahg: and?
[18:35] <ari-tczew> do you know, that launchpad has got option like edit bug?
[18:35] <geser> ari-tczew: as far as I know cjwatson will sponsor it (once it reached the top of his queue)
[19:58] <blueyed> I have backported a PHP snapshot, based on the ubuntu package, but the build fails (without any clear error): http://launchpadlibrarian.net/59509213/buildlog_ubuntu-lucid-i386.php5_5.3.4%7Esnap201011231530-0ubuntu1%7Eblueyedppa1_FAILEDTOBUILD.txt.gz - "dpkg-buildpackage: error: debian/rules build gave error exit status 2", but no real reason apparently. Hints?
[20:01] <micahcowan> blueyed, Not "no reason". Search above that point to find the errors that resulted in the final error returned by "debian/rules build".
[20:01] <micahcowan> build -> build-pear-stamp -> install-pear, apparently.
[20:02] <micahcowan> At which point it appears that some rule was running wget to download a file from pear.php.net (as part of the build process?!), but wget couldn't resolve the pear.php.net hostname
[20:03] <micahcowan> Haven't done launchpad builds myself, and don't know much about them, but I wouldn't be surprised if normal external net access were disallowed for security reasons or somesuch.
[20:03] <blueyed> micahcowan: thanks, missed that and yes, that makes sense. I am not sure if the regular buildds allow network access?! will have to look into this later.
[20:07] <geser> blueyed, micahcowan: the buildds don't have net access
[20:21] <Sarvatt> achiang: fixed xulrunner-1.9.2 is out now
[20:22] <achiang> Sarvatt: ta!
[20:26] <achiang> Sarvatt: much better, thank you
[20:27] <Sarvatt> achiang: thank chrisccoulson, he found the problem fast when I bugged him about it :)
[20:29] <achiang> Sarvatt: yes, i peeked at the bug and it looked hairy, having to read the disassembly to figure out the answer. /me thanks chrisccoulson