[00:01] <nathwill> i'm already on 7.2.0-rm-stable-v1.1
[00:01] <bkerensa> no bleeding edge for u? :)
[00:01] <bkerensa> no big deal if you brick... Just get a new phone :P
[00:02] <nathwill> got an update for ubuntu one files app :)
[00:02]  * bkerensa needs to consider getting premium U1
[00:02] <bkerensa> idk though I have a huge box.net acct
[00:04] <slangasek> bkerensa: this week is the third Thursday of the month; any interest in colocating an Ubuntu Hour with the Debian beering this month?
[00:05] <bkerensa> nathwill: ^
[00:06] <nathwill> yep
[00:06] <bkerensa> nathwill: can you make it and possibly co-host?
[00:06]  * bkerensa will try and make it for sure
[00:07] <nathwill> yeah, i'm totally down.
[00:07] <nathwill> i don't work thursdays, so that's perfect
[00:07] <slangasek> Lucky Lab SE, 6pm for the Debian beering
[00:07] <bkerensa> nathwill: k I will create event on loco.u.c. and calagator and send it to the interwebs
[00:08] <nathwill> okey doke.
[00:16] <bkerensa> http://calagator.org/events/1250462386
[00:16] <bkerensa> http://loco.ubuntu.com/events/ubuntu-us-or/1782/detail/
[00:16] <bkerensa> and on mailing list
[00:16] <bkerensa> blkperl: ^ you should invite some PSU Ubuntu/Debian folk :P
[00:49] <bkerensa> bdmurray: do you know how many bugs per result page LP displays by default?
[00:49] <nathwill> 42
[00:49] <bdmurray> 75
[00:50] <bdmurray> well 75 is the max per page listing
[00:50] <bkerensa> hmm
[00:50] <bkerensa> k
[00:50] <bkerensa> bdmurray: 11479575 fix released bugs in Ubuntu?
[00:52] <bkerensa> 11479575
[00:52] <bkerensa> eck
[00:54] <nathwill> 153061
[00:54] <nathwill> http://bit.ly/JGxyKL
[00:54] <bkerensa> yes
[00:54] <nathwill> that's results, not pages
[00:55] <bkerensa> ahh?
[00:55] <nathwill> so... that's the answer
[00:55] <bkerensa> hmm ok
[00:57] <blkperl> bkerensa: most of us have a conflicting board game night on Thursday
[00:57] <bkerensa> ahh
[00:57] <blkperl> Ill pass it along to the general student
[00:58] <nathwill> bye folks. headed home to fiddle w/ this proliant now
[00:59] <bkerensa> :D
[01:13] <blkperl> bkerensa: calagator and the link you gave me conflict on the time
[01:14] <blkperl> bkerensa: also add a more useful describtion, nobody knows what Ubuntu/Debian beering means...
[01:24] <bkerensa> blkperl: patches accepted for improvements on description
[01:24] <bkerensa> :)
[01:24] <blkperl> bkerensa: is it git?
[01:24] <blkperl> in git?* :)
[01:25] <bkerensa> bkerensa: Submission of patches accepted via mailing list only
[01:25] <bkerensa> make sure to sign off on it too
[01:25] <blkperl> telling yourself these things, counts as voluneteering
[01:26] <bkerensa> ;p
[01:48] <nibalizer> blkperl: git send-email
[01:48]  * nibalizer finger pistols *
[01:57] <nathwill> woot. got the extra nic and extra stick of ram installed... downloading 12.04 server now :)
[01:58] <nathwill> beer break
[01:59] <nathwill> bkerensa: found us an extra 250G hdd :)
[04:09] <nathwill> mmmm... hoegaarden.
[04:20] <cy1> Has anyone used tmux? I'm finding a weird error...
[04:21] <cy1> if I redirect stderr to a log, it freezes while doing epoll on fd #3. If I don't redirect, it doesn't freeze. wtf
[04:21] <nathwill> interesting
[04:24] <cy1> I did an strace on it, and it's like... the server treats the client differently depending if the client is connected to a...terminal?
[04:25] <cy1> i.e. the server loses the client and leaves it hanging if going to logs
[04:26] <cy1> nah, but when I leave stdout on the terminal and only redirect stderr it *still* freezes...
[04:38] <cy1> Ugh, it looks like a kernel bug.
[04:38] <cy1>          * On Linux, epoll doesn't work on /dev/null (yes, really).
[04:38] <cy1> >>> in the tmux source
[04:38] <nathwill> lol
[04:39] <cy1> I'm not redirecting stdin to dev/null, but stderr to a log file, but it's probably along the same lines...
[04:49] <nathwill> damn it... this 4G ECC ram is DOA
[05:11] <cy1> Huh... so libevent and epoll can hang if they're trying to write to a filesystem file, but not a socket or a pipe.
[05:11] <cy1> i.e. offending-command 2>&1 | cat => no hanging.
[05:12] <cy1> even if it's cat > some/log/file.log
[05:43] <bkerensa> nathwill: SATA for the 1U box?
[05:43] <nathwill> bkerensa, yessir :)
[05:44] <nathwill> 250G came with my microserver, and i certainly don't need it
[05:44] <bkerensa> nathwill: LOL? what are you going to use then?
[05:44] <nathwill> one of several 2TB i have here :)
[05:45] <bkerensa> lol
[05:46] <bkerensa> nathwill: let me guess your going to use the proliant as a Seedbox/Firewall/App box?
[05:46] <bkerensa> :D
[05:47] <nathwill> yessir
[05:47] <nathwill> fire up a debian lxc for working upstream
[05:47] <nathwill> and then fire up lxc containers for local apps, and keep the base install clean aside from the virt and networking stuff
[05:47] <nathwill> :D
[05:48] <bkerensa> lol
[05:48] <bkerensa> nathwill: I am going to get a Xi3 to run as my server
[05:48] <bkerensa> it will sit by my router
[05:48] <bkerensa> :D
[05:48] <nathwill> well... i finally have something with dual nics, so i'm gonna go nuts
[05:48] <bkerensa> LOL
[05:49] <nathwill> bkerensa: that looks spiffy
[05:51] <nathwill> i'm assuming the little one, not the data center, right? ;)
[05:51] <bkerensa> the micro one yeah
[05:51] <nathwill> lol
[14:02] <nathwill> *yawn*
[16:44] <bkerensa> nathwill: ikr ^
[16:46] <nathwill> bkerensa: so turns out that ram stick is bad :(
[16:46] <nathwill> but i got everything else set up and rocking. (though still have to set up the hosts and routing)
[16:46] <bkerensa> nathwill: did you buy it somewhere?
[18:23] <bkerensa> Bug #996140
[18:50] <nathwill> bkerensa: HP hardware through newegg
[18:50] <bkerensa> ah
[21:30] <bkerensa> Ahh hah
[21:38] <bkerensa> slangasek: might you look at output from this source package I am trying to build? http://paste.ubuntu.com/991412/
[21:39] <slangasek> bkerensa: lines 57-59 are the error and, seemingly, the solution
[21:40] <bkerensa> slangasek: could these be due to debuild trying to use the 4.2.0 orig tarball instead of the new upstream version?
[21:41] <slangasek> bkerensa: well, given what it says on line 8, yes :)
[21:41] <slangasek> you have a wrong version number in debian/changelog, then
[21:41] <bkerensa> ah
[21:43] <bkerensa> slangasek: and now with fixed version number in debian/changelog http://paste.ubuntu.com/991424/
[21:44] <slangasek> bkerensa: ok, so, what did you do to create this source package?  It doesn't look like the patches you have in the debian/patches directory apply cleanly against the new upstream version
[21:44] <bkerensa> slangasek: https://wiki.ubuntu.com/PackagingGuide/Recipes/PackageUpdate
[21:45]  * bkerensa pulled new upstream tarball
[21:45] <bkerensa> pulled our stable
[21:45] <bkerensa> then merged our /debian into the extracted upstream source
[21:45] <slangasek> oh dear
[21:45] <bkerensa> added new changelog entry and then debuild
[21:45] <bkerensa> LOL
[21:45] <bkerensa> ^
[21:45] <slangasek> yeah, these instructions are all wrong
[21:45] <bkerensa> >.<
[21:45] <bkerensa> They just updated them during UDS
[21:45] <bkerensa> =/
[21:46] <slangasek> no, this page hasn't been updated since 2011-11-14
[21:46] <bkerensa> oh
[21:46] <slangasek> but it was wrong then, too :P
[21:47] <slangasek> so I'm not sure if this page should be fixed, or deleted / redirected somewhere else
[21:47] <slangasek> but the right thing to do is
[21:47] <bkerensa> Show me the Debian way? :P
[21:47] <slangasek> apt-get source (or dget -xu) $package
[21:47] <slangasek> wget $new_upstream_tarball
[21:47] <slangasek> cd $package-$oldver
[21:48] <slangasek> uupdate ../$new_upstream_tarball $new_upstream_version_number
[21:49] <slangasek> however, neither of those methods will auto-fix the patches for you - that part has to be done by hand, and is entirely missing from this page
[21:49]  * slangasek takes a peek at https://blueprints.launchpad.net/ubuntu/+spec/community-q-packaging-guide
[21:50] <slangasek> https://wiki.ubuntu.com/PackagingGuide: "The Packaging Guides on this wiki are no longer being actively maintained. [...]"
[21:50] <slangasek> so yeah, I'll shoot that page in the head
[21:59] <bkerensa> slangasek: is there a guide to fixing patches by hand?
[21:59] <bkerensa> I have complete all the other steps ^
[22:00] <slangasek> export QUILT_PATCHES=debian/patches; while ! quilt push -a; do quilt push -f; edit things by hand; quilt refresh; done
[22:02] <bkerensa> You just spoke Cantonese at me
[22:02] <slangasek> there's a lot of Cantonese in packaging
[22:03] <bkerensa> Ran ^ and its now doing some interesting looping in terminal
[22:03] <slangasek> um
[22:03] <slangasek> sorry
[22:03] <slangasek> ^C ;)
[22:03] <bkerensa> lol
[22:03] <slangasek> you were meant to expand that loop mentally
[22:03] <slangasek> because "edit things by hand" is not a shell command
[22:03] <bkerensa> LOL
[22:07] <slangasek> but everything /else/ there is a shell command
[22:07] <slangasek>  export QUILT_PATCHES=debian/patches - tells quilt where to find the patch set
[22:07] <bkerensa> yeah
[22:07] <slangasek> quilt push -a - tries to apply all patches in the set
[22:08] <slangasek> when it fails, you do 'quilt push -f' to force-push the next patch
[22:08] <slangasek> then go over everything that failed to apply, and when you're all done fixing it up, run 'quilt refresh' to regenerate the patch
[22:08] <slangasek> repeat as needed
[22:08] <bkerensa> nothing failed though
[22:08] <bkerensa> :D
[22:08] <slangasek> oh, interesting
[22:08] <bkerensa> just this occurred: File series fully applied, ends at patch 02-use-webkit-by-default.diff
[22:08] <slangasek> then you're done
[22:08] <bkerensa> ahh now build?
[22:08] <slangasek> yeah
[22:09] <slangasek> it may still fail if any of the patches were fuzzy
[22:09] <slangasek> but that's easily fixed
[22:12] <bkerensa> slangasek: assuming everything builds fine what is the most appropriate process for getting the new package sponsored?
[22:14] <slangasek> bkerensa: given that you're doing a new upstream version, that's a good question
[22:14] <slangasek> let me see
[22:15] <slangasek> I think it may be best for you to just attach the .diff.gz to a bug
[22:15] <slangasek> (no point in creating a debdiff, as that would just show all the upstream changes mixed in)
[22:15] <slangasek> or rather, the .debian.tar.gz since this is a 3.0 (quilt) package
[22:16] <bkerensa> slangasek: it would seem it failed to build http://paste.ubuntu.com/991451/
[22:17] <slangasek> strange, why is there no error message shown?
[22:17] <bkerensa> no idea
[22:17] <slangasek> did you omit 2>&1 from your pastebin?
[22:18] <bkerensa>   sp = my_subProcess.subProcess("cp -f share/penguintv.glade.desktop share/penguintv.glade")
[22:18] <bkerensa> NameError: name 'my_subProcess' is not defined
[22:18] <bkerensa> make: *** [debian/python-module-stampdir/penguintv] Error 1
[22:18] <bkerensa> dpkg-buildpackage: error: debian/rules build gave error exit status 2
[22:19] <slangasek> oh, well, no idea
[22:19] <slangasek> that's not a generic message - seems to be something specific to that package
[22:20] <bkerensa> kk
[22:20]  * bkerensa will ping upstream author
[22:20] <bkerensa> he is the one who requested we update
[22:20] <slangasek> you might want to double-check that the debian/patches aren't to blame
[22:21] <bkerensa> is there a preferred way of doing such?
[22:22] <bkerensa> >.<
[22:22] <bkerensa> #this file is a catastrophe. I'm sorry.
[22:22] <bkerensa> comment from one of the patches
[22:35] <slangasek> bkerensa: preferred way> yes, read the patch and see if it's the source of this "my_subProcess" command :)