[00:57] <ScottK> claydoh: It was you.  If you look right before the ping, there was some release notes discussion.
[00:58] <claydoh> ScottK: kk thanks
[02:46] <JontheEchidna> shadeslayer: you didn't bump the package name for kdevplatform1-libs when you packaged kdevplatform 1.0.82
[03:11] <JontheEchidna> http://websvn.kde.org/?view=revision&revision=1178415 <- do want
[03:48] <ScottK> JontheEchidna: Bug #645705 really confused me, FYI.
[03:48] <ScottK> (look who filed it)
[03:48] <JontheEchidna> oh yeah, there's another jonathan thomas out there
[03:49] <JontheEchidna> I'm surprised I've only been mistaken for him once before on the internets
[03:49] <dasKreech> JontheEchidna: Sonic?
[03:49] <JontheEchidna> dasKreech: my usersname? yes
[03:50] <dasKreech> Who you've been mistaken for
[03:50] <JontheEchidna> ah
[03:50] <JontheEchidna> [22:48:17] <ScottK> JontheEchidna: Bug #645705 really confused me, FYI.
[03:50] <JontheEchidna> [22:48:18] <ubottu> Launchpad bug 645705 in openshot (Ubuntu) "Sync openshot 1.2.2-1 (universe) from Debian unstable (main)" [Undecided,New] https://launchpad.net/bugs/645705
[03:50] <JontheEchidna> [22:48:25] <ScottK> (look who filed it)
[03:50] <JontheEchidna> [22:48:38] <JontheEchidna> oh yeah, there's another jonathan thomas out there
[03:52] <ScottK> JontheEchidna: Could you look at kymymoney and skrooge in Debian Experimental and see if we want the updates (if I file the request, I can't approve them).
[03:52] <JontheEchidna> sure
[03:59] <JontheEchidna> skrooge seems to break feature freeze
[04:02] <ScottK> Which would just mean I have something to approve.
[04:02] <ScottK> (if we want it)
[04:04] <JontheEchidna> Yeah, we'd want it
[04:05] <JontheEchidna> we want kmymoney as well (packaging fix), but until both actually show up in experimental I can't use requestsync
[04:05] <JontheEchidna> E: The versions in Debian and Ubuntu are the same already (4.5-1). Aborting.
[04:05] <ScottK> JontheEchidna: OK.  Please ping me when there's something to approve.
[04:06] <JontheEchidna> will do
[04:06] <ScottK> (if the kymymoney one is just bugfix, then it can go straight to ubuntu-archive to do the sync)
[04:24] <lex79> Riddell: I pushed Qt to bzr, it's ftbs in ninja ppa, my connection sucks in this moment so I can't upload it. Testbuild and run ok.
[04:52] <lucidfox> Where can I find Qt 4.7 packages for Lucid?
[04:56] <ScottK> lucidfox: In the ~kubuntu-ppa beta PPA.
[04:57] <lucidfox> danke
[04:57] <ScottK> No problem.
[04:57] <ScottK> Riddell: Is it by design that there's no option to install in the first menu on the live CD?  One has to start the live session and then install.
[04:58] <ScottK> Riddell: Nevermind.  I was one screen to soon.
[10:04]  * persia curses version control systems, erases everything, and starts over with "export", vowing to avoid svn this time
[10:06] <Riddell> KDE git opens in a week.  I'm dreading it.
[10:07] <valorie> all the projects?
[10:07] <valorie> or just as they choose to move?
[10:08] <persia> More likely one at a time, in a "voluntary" manner until everything is moved, for maximum transition pain (although, honestly, I'd not be surprised to see KDE make a clean-break transition at one point, based on clear direction)
[10:09] <valorie> I'm not sure what would be maximum pain, tbh
[10:12] <persia> My last statement comes in part from bitterness directed at all VCS.
[10:13] <persia> That said, I think that a group deciding to move, as a group, to a different solution is likely less painful than forcing all the developers to use two simultaneous solutions, unless one gets the interplay precisely right.
[10:13] <persia> Mind you, such "forcing" of all the developers is best done as consensus after considering all input, etc.
[10:16] <valorie> I've heard that all of KDE is moving to GIT
[10:16] <valorie> but I hadn't heard the timing
[10:16] <ScottK> It is.
[10:17] <ScottK> It's getting close.
[10:17] <valorie> we're happy in Amarok with it
[10:18] <Sput> everybody actually using it is
[10:18] <Sput> I'm quite sure all the nay sayers in the community won't admit they ever were against the move in a year or so :)
[10:19] <Sput> also, Riddell, isn't it already open? at least amarok and konversation already are on git.kde.org
[10:20] <valorie> yes
[10:20] <valorie> but reviewboard has only been up and working for a few days
[10:23] <Tm_T> Amarok and Konversation are there acting as test subjects, so when main modules will be imported, all would be tested and smooth as possible
[10:26] <Riddell> Sput: I don't know, I just hope there's a good tutorial for when I have to care
[10:26] <Sput> Riddell: well, both amarok and konversation have been on git for a while now
[10:26] <Sput> and it seems to be working well :)
[10:27] <ScottK> Sput: For the people that are used to using Git.
[10:28] <Sput> ScottK: well yes, but that's true for any other VCS :)
[10:28] <ScottK> Sput: More so with Git than some others.
[10:28] <Sput> I don't know how bzr performs in that department, but I'm quite sure that any DVCS is vastly superior to svn for software development
[10:29] <ScottK> Certainly.
[10:29] <Riddell> I disagree, bzr is trivial for those used to svn if you want to use it in the same way as svn (and easy if you want to use distributed stuff).  git isn't.
[10:29] <Sput> using a DVCS "the same way as svn" is an oxymoron, in my book :)
[10:29] <ScottK> Sput: But allowing people to work centralized or distributed is a great transitional model.
[10:30] <Sput> hmm, I don't see how these two concepts can match though
[10:30] <Sput> conceptually
[10:31] <ScottK> With bzr, you can use, essentially, svn emulation mode where you svn/bzr what you know from subversion (e.g. bzr co) or you can branch and work in a distributed manner.
[10:32] <Sput> ScottK: and that works with people mixing the two approaches on the same project?
[10:32] <ScottK> Sput: It does.
[10:32] <Sput> interesting.
[10:33] <ScottK> My experience is that the major problem is that the people used to svn make huge monolithic commits that are hard to understand.
[10:33] <ScottK> But that's inherent in that model and not really an integration problem.
[10:35] <Sput> from my own experience, it's especially the special features of git (mainly the staging area and the possibility to rebase/rewrite history) that I found extremely valuable, though I agree using the latter correctly requires some understanding of the concept
[10:36] <Sput> on the other hand, there's no reason to use those advanced features :)
[10:36] <Sput> what I find stupid is that they remapped well-known commands to do something entirely different
[10:36] <Sput> that is just a stupid way to make it harder
[10:38] <Riddell> bzr checkout <url>; edit; bzr commit    nice and easy for svn users
[10:39] <Riddell> bzr branch <url>; edit; bzr commit; bzr push   distributed goodness
[10:39] <Sput> does that kind of stuff work offline?
[10:39] <ScottK> The branch/commit does
[10:39] <Sput> so can you switch branches, commit, diff, log etc offline as well?
[10:39] <ScottK> Yep
[10:39] <Sput> that's important
[10:39] <Sput> it's also what makes svn unusable for me nowadays :)
[10:39] <Riddell> bzr checkout <url>; edit; bzr commit --local; bzr push    changed my mind and want to do it distributed
[10:41] <Riddell> I've been trying to get qtwebkit out of git for the last two days, still no idea what's going wrong
[10:49] <superfly> Riddell: use the bzr-git bridge ;-)
[11:01] <agateau> Riddell: do we need a "git intro for kubuntu devs" session at uds?
[11:03] <agateau> Riddell: I'd volunteer for such a session
[11:04] <persia> I'm not sure UDS is the best forum for such a session.  Might be better to contact the classroom folk.
[11:06] <agateau> persia: I think talking about VCS is easier when there is a drawing board, that's more difficult over irc
[11:06] <Riddell> i'd like that
[11:09] <agateau> (lunch time)
[11:09] <persia> agateau, I'll agree to that: I just generally believe UDS to be poorly attended, and having often been a non-attendee try to encourage folks to avoid things other than spec discussion there.
[11:24] <larsivi> do anyone know why there's no libqt4-opengl-dbg packages? are the symbols in a different package?
[11:27] <Riddell> in libqt4-dbg
[11:34] <persia> Riddell, KDE bug #251866 has an updated patch against a trunk pull from 9:06 UTC
[11:39] <Riddell> persia: great, I'll apply that
[12:12] <larsivi> Riddell: doesn't appear to help for QGLShader
[12:29] <ScottK> Argh! diff from 4:4.7.0~rc1+git20100917-0ubuntu1 to 4:4.7.0-0ubuntu1 (27.8 MiB)
[12:30] <persia> Just pray it's N iterations of a mechanical change
[12:35] <nigelb> heh
[12:58] <sheytan> Hey there ;)
[12:58] <shadeslayer> whee... qt is FTBFS in ppa...
[12:58] <sheytan> Is this true that moun will replace kpk in 11.04?
[12:59] <shadeslayer> sheytan: maybe ... who knows
[12:59] <shadeslayer> if JtE pushes hard enough :>
[12:59] <sheytan> shadeslayer come on, the new one is way user friendly then muon. Leave both or kpk :D
[13:00] <shadeslayer> sheytan: well if thats the opinion, it wont be changed
[13:01] <sheytan> shadeslayer, but don't you agree with me? Kubuntu should be for both power users and new onse ;)
[13:01]  * sheytan gets back to work on kubuntu webpage
[13:02] <shadeslayer> sheytan: if it works the way its intended to why would we change it
[13:03] <sheytan> i just heard that it will repalce kpk, but i'm disagree for this :D
[13:03] <shadeslayer> sheytan: where did you hear this?
[13:04] <Riddell> there's been no decision or even discussion so far
[13:05] <debfx> kpk is broken in double-click mode :(
[13:06] <debfx> it wants me to rename categories instead of showing the packages ^^
[13:07] <debfx> bug #645638
[13:11] <sheytan> debfx report it to dantti. He was about to fix it i think, but he might  forget ;)
[13:11] <debfx> dantti_work: ↑
[13:12] <sheytan> shadeslayer, a dude on my blog commented my article about kpk with this and i want to make sure :)
[13:13] <shadeslayer> oh hmm
[13:19] <shadeslayer> aha! i found the issue
[13:19] <shadeslayer> fabo: pingly
[13:20] <shadeslayer> JontheEchidna: theres talk of muon replacing kpk in 11.04 :>
[13:20] <Riddell> ScottK: I'm rejecting qt4-x11, I just received an updated appmenu patch to add to it
[13:21] <ScottK> OK.  I'll stop looking at it.  Thanks.
[13:22] <shadeslayer> Riddell: does we need 11_build_translations.diff  in qt4-X11 ?
[13:22] <shadeslayer> in this release
[13:23] <Riddell> shadeslayer: seems to, lex already added that and got it to compile
[13:23] <shadeslayer> yeah.. thats the i issue i think
[13:25] <shadeslayer> JontheEchidna: kdevplatform-libs1 needs bumping to 2?
[13:25] <JontheEchidna> and libsublime. I uploaded a fix for maverick but never got around to lucid
[13:25] <JontheEchidna> the fix for lucid will be identical
[13:26] <shadeslayer> JontheEchidna: ok looking into it
[13:26] <JontheEchidna> lul: http://i.imgur.com/vWaub.jpg
[13:26] <fabo> shadeslayer: pong
[13:27] <shadeslayer> fabo: oh Riddell sorted my issue :)
[13:27] <fabo> k :)
[13:27] <Riddell> well, lex did
[13:28] <fabo> Riddell: any relevant changes before I upload to Debian?
[13:28] <fabo> Riddell: not sure which version you have for QtWebKit, but you'll need 2.1 branch (I'm using week37)
[13:31] <ScottK> Wahoo.  Comics widget fixed.
[13:32] <Riddell> fabo: why 2.1 branch?
[13:32] <Riddell> fabo: the fix for the 4.7 release was just to add back 11_build_translations.diff
[13:32] <fabo> Riddell: needed for Qt WRT
[13:32] <fabo> k
[13:32] <Riddell> what's WRT?
[13:32] <JontheEchidna> The following packages have unmet dependencies:
[13:32] <JontheEchidna>   bzip2: Depends: libbz2-1.0 (= 1.0.5-4) but 1.0.5-4ubuntu1 is to be installed.
[13:32] <JontheEchidna> archive skew \o/
[13:32] <fabo> Qt Web Runtime
[13:33] <Riddell> fabo: I'm none the wiser
[13:33] <ScottK> JontheEchidna: No, mirror lag.
[13:33] <fabo> Riddell: http://gitorious.org/qt-web-runtime
[13:33] <ScottK> Update again in a few minutes
[13:34] <JontheEchidna> ok
[13:34] <fabo> Riddell: http://labs.qt.nokia.com/2010/07/19/the-qt-web-runtime-journey-begins/
[13:34] <JontheEchidna> anybody else have planned kde4libs changes? I'll do an upload assuming this pbuilds/installs/works
[13:34] <Riddell> JontheEchidna: none here
[13:35] <ScottK> JontheEchidna: I noticed there are a few commits in the 4.5 branch that fix memory leaks.  I was considering cherrypicking them.
[13:35] <JontheEchidna> iirc we got 2 memleak patches recently
[13:36] <ScottK> OK.
[13:36] <Riddell> fabo: that sounds interesting but not something we need to care about for our 10.10 release
[13:38] <ScottK> Riddell: When you get a moment, I've put kdeplasma-addons in the queue and I'd appreciate it if you'd review/accept.  Among other things it fixes the comics widget (this is critical).
[13:38] <fabo> Riddell: k
[13:39] <Riddell> yes, that is a vital part of Kubuntu, I'll get straight to it
[13:39] <Riddell> fabo: what I want is a qtwebkit 2.0 tar but upstream hasn't bothered to do one and I can't work out the git magic to create one
[13:39] <Riddell> agateau: this appmenu patch has no version number in it, should it?
[13:40] <agateau> oh
[13:40] <agateau> my mistake
[13:40] <agateau> Riddell: I redid it before sending it and did not add the header
[13:41] <Riddell> I can just put it in if you tell me what to add
[13:41] <agateau> Riddell: can you add it or do you want me to send you a new one?
[13:41] <agateau> Riddell: Basically my release check list says this:
[13:41] <agateau> # Generate patch
[13:41] <agateau> echo "Appmenu patch $tag" > ~/tmp/appmenu.diff
[13:41] <agateau> git diff 4.7..appmenu >> ~/tmp/appmenu.diff
[13:42] <agateau> where tag is $(date +%Y%m%d)
[13:42] <Riddell> done
[13:42] <agateau> great
[13:43] <agateau> First diff was 22Mb because I forgot to update my 4.7 branch :)
[13:43] <agateau> so I regenerated the diff but did not prepend the header
[13:44] <fabo> Riddell: get make-package.py script from gitorious and use it to generate the tarball
[13:45] <fabo> Riddell: we should have weekly tag now
[13:45] <fabo> Riddell: git://qt.gitorious.org/qtwebkit/tools.git
[13:49] <fabo> Riddell: still, I'll suggest to use 2.1 branch ;)
[13:50] <fabo> Riddell: for bug fixing and performance improvements
[13:55] <Riddell> fatal: The remote end hung up unexpectedly
[13:55] <Riddell> that's what I get when trying to clone the qtwebkit git
[13:59] <fabo> maybe gitorious issue, retry later
[14:06] <Sput> Riddell: I think you need to omit the qt.
[14:06] <Sput> git clone git://gitorious.org/qtwebkit/tools.git works for me
[14:13] <Riddell> Sput: tools is fine but the actualy qtwebkit repository won't checkout, people on #qtwebkit are confirming the same
[14:17] <Sput> ah.
[14:49] <CIA-116> [ubuntu] Jonathan Thomas<EMAIL_ADDRESS>*<EMAIL_ADDRESS>* debian/ (3 files in 2 dirs) Add kubuntu_77_fix_plasma_tooltip_holes.diff from upstream to work around an Xorg bug where Plasma tooltips would create holes in windows
[14:52] <JontheEchidna> bah, too good to be true. causes crashes
[14:54]  * JontheEchidna uncommits and doesn't push
[14:58] <shadeslayer> is there a way to make irssi display notifications when someone highlights you using the KDE notification system? i found a script but it uses dcop :P
[15:12] <JontheEchidna> make the script call kdialog --passivepopup, iirc
[15:13] <JontheEchidna> kdialog --passivepop "messagetext"
[15:13] <JontheEchidna> kdialog --passivepopup "messagetext" ;-)
[15:24]  * shadeslayer switched to weechat
[15:41]  * shadeslayer_ hugs fejjerai
[15:45] <shadeslayer> fejjerai: works for me :P
[15:46] <CIA-116> [libqapt] jmthomas * 1178690 * trunk/extragear/sysadmin/libqapt/CMakeLists.txt Bump the library .so version so I don't keep getting symbol lookup errors :P (and we need to anyways since we have new methods in trunk)
[15:50] <ari-tczew> hey kubuntu masters, could you take a look on bug 645740 ?
[15:52] <ari-tczew> debfx: as last uploader, I'm pinging you for this one. ^^
[15:52] <CIA-116> [muon] jmthomas * 1178693 * trunk/extragear/sysadmin/muon/ (12 files in 4 dirs) (log message trimmed)
[15:52] <CIA-116> Make all PackageWidget subclasses use the proxymodel filtering facilities rather
[15:52] <CIA-116> than using setPackages with a QApt::PackageList. By setting the filter before
[15:54] <CIA-116> [muon] jmthomas * 1178694 * trunk/extragear/sysadmin/muon/updater/UpdaterWindow.cpp We don't need to worry about Xapian events in the updater since it doesn't use Xapian search
[15:57] <CIA-116> [muon] jmthomas * 1178695 * trunk/extragear/sysadmin/muon/libmuon/StatusWidget.cpp This attempt at right-aligning the xapian progress bar within the status bar didn't work...
[15:58] <CIA-116> [muon] jmthomas * 1178696 * trunk/extragear/sysadmin/muon/libmuon/StatusWidget.cpp Oops, unrevert.
[16:16] <shadeslayer> JontheEchidna: halp http://gitorious.org/qzsync/qzsync/blobs/master/widget.cpp
[16:16] <shadeslayer> it doesnt load zsync :(
[16:17] <shadeslayer> and no progressbar
[16:29] <debfx> ari-tczew: I've attached a better debdiff to the bug. Could you sponsor it?
[16:29]  * apachelogger votes for code formatting
[16:29] <ari-tczew> debfx: sure
[16:31] <shadeslayer> apachelogger: yeah im looking at how to do that in qtcreator right now :P
[16:32] <ari-tczew> debfx: did you tested it?
[16:32] <apachelogger> shadeslayer: http://www.bikeforest.com/CAD/faq/enter_key.jpg
[16:32] <shadeslayer> apachelogger: lol
[16:32] <apachelogger> that is even a plaform independent feature, so you can also use that on osx and windows
[16:32] <apachelogger> saved me a couple of times I must say
[16:33] <debfx> ari-tczew: yes, it adds the necessary dependencies
[16:35] <shadeslayer> apachelogger: fixed in git .. lookie
[16:36] <ari-tczew> debfx: hmm, very interesting. I'll upload this one after watching film. thanks!
[16:36] <ari-tczew> debfx: also, please forward changes to Debian :)
[16:37] <apachelogger> it is a mergery
[16:38] <apachelogger> shadeslayer: from glimpsing at the code I woud say that your process starts but then falls into pieces because of bogus arguments
[16:38] <apachelogger>         arguments<< " "<< url->text() <<  " -A hostname=" << hostname->text() << ":" << password->text() << " -i" << fileName;
[16:39] <apachelogger> that most likely aint not gonna work
[16:39] <apachelogger> well
[16:39] <apachelogger> unless you ahve a hostname and password ^^
[16:40] <apachelogger> what is arguments<< " "<<  supposed to be anyway?
[16:41] <apachelogger> the void?
[16:41] <Riddell> how do I know what X driver I'm using?
[16:42] <shadeslayer> apachelogger: whitespace between 2 arguments
[16:42] <shadeslayer> oh wait
[16:42] <shadeslayer> :O
[16:42] <apachelogger> shadeslayer: qprocess does that
[16:42] <shadeslayer> apachelogger: just realised that
[16:42] <apachelogger> that is why you pass it a qstringlist
[16:42] <apachelogger> so it can make list.join(" ")
[16:42] <apachelogger> well actually it will do more sophisticated things to it, but that is the basic idea ;)
[16:43] <shadeslayer> hmm this means everything in arguments is foobared
[16:43] <shadeslayer> i need to re think that part
[16:44] <shadeslayer> apachelogger: how do i pass -i filename to the QProcess ?
[16:44] <shadeslayer> as 2 seprate QSL entries?
[16:44] <apachelogger> yup
[16:44] <apachelogger> QStringList args; args << "-i" << filename;
[16:44] <shadeslayer>         arguments<< url->text() << " -i" << fileName; :
[16:45] <shadeslayer> ohk...
[16:45] <apachelogger> also
[16:46] <apachelogger> you need to make that arguments << "-u" << url->text() << "-i" << fileName;
[16:46] <apachelogger> zsync  [  -u  url  ]  [ -i inputfile ] [ -o outputfile ] [ { -s | -q } ] [ -k file.zsync ] [ -A hostname=username:password ] {
[16:46] <apachelogger>        filename | url }
[16:47] <apachelogger> and
[16:47] <apachelogger> shadeslayer: if I understand this correctly then you should be using -o?
[16:47] <apachelogger> or maybe both?
[16:47] <shadeslayer> IIRC no need to use -o
[16:47] <shadeslayer> it automatically creates a new file
[16:48] <apachelogger> well yes
[16:48] <shadeslayer> im just passing the input file
[16:48] <apachelogger> but from the manpage it does not sound like it would be creating the file in place of -i
[16:48] <apachelogger> but your app asks where to save the file
[16:48] <shadeslayer> one sec
[16:48] <apachelogger> so you need ot use -o
[16:51] <shadeslayer> ah yes.. that should really say : Choose input file
[16:51] <apachelogger> what if I dont have one :P
[16:52] <shadeslayer> apachelogger: ill be putting a case for that soonish
[16:52] <apachelogger> I think you are going at the problem the wrong way :P
[16:52] <apachelogger> anyhow
[16:53] <apachelogger> -u urly apparently does not work
[16:53] <apachelogger> no here anyway
[16:53] <apachelogger> so you need to append the zysnc url last to the arguments
[16:53] <shadeslayer> err... isnt  it zsync args url ?
[16:53] <shadeslayer> or zsync url args
[16:53] <apachelogger> yours is zsync url args
[16:53] <apachelogger> it should be zsync args url
[16:54] <apachelogger> however I wonder why there is a -u argument
[16:54] <shadeslayer> IIRC ive used it both ways
[16:54] <apachelogger> shadeslayer: zsync url args surely did not work :P
[16:55] <apachelogger> or maybe it did
[16:55] <apachelogger> well, depends on the internal argument parser
[16:55] <apachelogger> per manpage only zsync args url should work
[16:57] <sheytan> Hey
[16:58] <sheytan> is this  list of loco teams complete? http://www.kubuntu.org/community
[16:58] <sheytan> i mean, can i finde more anywhere?
[16:58] <shadeslayer> sheytan: loco.ubuntu.com
[16:59] <apachelogger> not approved
[16:59] <apachelogger> ^^
[16:59] <apachelogger> what is that
[17:00] <apachelogger> didnt pay certificaton fee of 3k? :P
[17:01] <sheytan> shadeslayer thanks
[17:01] <shadeslayer> apachelogger: whut? :D
[17:02] <apachelogger> there are locos that say not approved
[17:02] <shadeslayer> oh
[17:02] <shadeslayer> dunno :P
[17:02] <apachelogger> also the main site is of doubtable use IMHO
[17:02] <shadeslayer> the indian loco is not approved as well :>
[17:02] <apachelogger> oh wellz
[17:02] <shadeslayer> oh and something else
[17:02] <apachelogger> shadeslayer: you did not pay!!!!
[17:02] <apachelogger> :P
[17:02] <shadeslayer> my passport was issued \o/
[17:02] <shadeslayer> well.. its in the mail now
[17:02]  * apachelogger got his today
[17:03] <apachelogger> that reminds me that I still need to ack my sponsoring
[17:03] <shadeslayer> ill get mine by saturday i guess
[17:03]  * apachelogger looks for motivation to do that
[17:03] <shadeslayer> apachelogger: you didnt ack it? :O
[17:03] <apachelogger> nah
[17:03] <apachelogger> I am not into commitments
[17:04] <shadeslayer> Passport will be ready on 23-09-2010 subject to all documents being in order. It will be dispatched by post on 24-09-2010 :: whee
[17:04] <sheytan> apachelogger is there a site for u1 project or maybe you have u1 tag on your blog we can link in the website?
[17:04] <apachelogger> u1-kde is dead!
[17:05] <sheytan> f***
[17:05] <apachelogger> like a vampyr
[17:05] <sheytan> apachelogger why? :((((
[17:05] <ulysses> apachelogger: :(
[17:05] <shadeslayer> apachelogger: dude.. zsync url args works
[17:05]  * apachelogger goes looking for a blood sucker smiley
[17:05] <ulysses> Rule one: the Doctor lies. -> s/Doctor/apachelogger/
[17:06] <apachelogger> :-)=
[17:06] <ulysses> u1-kde shall live!
[17:06] <apachelogger> ulysses: that is a generalization of first order
[17:06] <sheytan> so i'm confused. is u1-kde still alive or not? :P
[17:07] <shadeslayer> sheytan: google will force apachelogger to maintain u1-kde
[17:07] <shadeslayer> :D
[17:07] <apachelogger> there is no proper vampire smiley :(
[17:07] <ulysses> :[
[17:07] <shadeslayer> ulysses++
[17:07] <sheytan> well, in this case
[17:08] <sheytan> i need new community project to put on the website
[17:08] <sheytan> anyone? :D
[17:08] <sheytan> muon is already there
[17:08] <Quintasan> Project Neon
[17:08] <apachelogger> http://www.techbanyan.com/wp-content/uploads/2010/08/article-0-0AD3C2B0000005DC-799_470x636.jpg
[17:08] <apachelogger> that is what u1-kde looks like
[17:08]  * shadeslayer slides qzsync towards sheytan
[17:08] <Quintasan> apachelogger: wtw?
[17:08] <Quintasan> WTF?
[17:08] <sheytan> shadeslayer what's that?
[17:08] <Quintasan> Cannot unsee.
[17:09] <shadeslayer> sheytan: qt GUI for zsync :P
[17:09] <shadeslayer> sheytan: http://gitorious.org/qzsync
[17:09]  * apachelogger starts downloadings true blood
[17:09] <ulysses> sheytan: write about Project Neon!
[17:09] <shadeslayer> aye ^
[17:09] <shadeslayer> sheytan: design shiny new logo as well :P
[17:09] <sheytan> ok, Project Neon is there, but ofcourse it's for the new website ;)
[17:09] <apachelogger> ulysses, sheytan: https://bugs.edge.launchpad.net/ubuntuone-client/+bug/375145
[17:10] <apachelogger> comment 56
[17:10] <Quintasan> it seems that shadeslayer is getting more and more good at ordering ppl around :P
[17:10] <shadeslayer> apachelogger: you know you can directly link to comments :P
[17:10] <apachelogger> sheytan: kubuntu is the community project?  :D
[17:12] <sheytan> and Muon
[17:13] <Quintasan> shadeslayer: We can blame him even without that.
[17:13] <sheytan> But well, we can ofcourse have more of them :)
[17:13] <sheytan> I'll just put two for the mockup
[17:13] <sheytan> and then talk  to ofirk if we can put more ;)
[17:13] <Quintasan> I think it's not question if we can put more
[17:13] <sheytan> Quintasan: does PN have a webpage?
[17:13] <Quintasan> it's a question HOW do we stuff more in there :P
[17:14] <shadeslayer> sheytan: no.. just a lp page
[17:14] <sheytan> Quintasan i think not more then 4 ;)
[17:14] <apachelogger> Quintasan: it is not the getting in, it is the getting out
[17:14] <Quintasan> and a empty Wiki page
[17:14] <Quintasan> :P
[17:14] <sheytan> shadeslayer can u link?
[17:14]  * sheytan doesn't like wiki pages at all :D
[17:14] <Quintasan> http://launchpad.net/~neon
[17:14] <Quintasan> sheytan: ^
[17:14] <sheytan> thanks
[17:14]  * apachelogger had them wiki pages back in the days
[17:14]  * apachelogger also had them forum posts
[17:14] <Quintasan> I mean, why still apachelogger is owner?
[17:14] <apachelogger> I think I became a greater being
[17:15] <Quintasan> apachelogger: Hand over the ownership :P
[17:15] <apachelogger> for I can survive without wikis or forums or irc or anything
[17:15] <sheytan> Quintasan and others what about PN as a subpage to kubuntu.org?
[17:15] <apachelogger> Quintasan: I am the overlord
[17:15] <sheytan> i think we can do that
[17:15] <apachelogger> that is why I have ownership
[17:15] <Quintasan> dunno, we should ask Riddell first
[17:15] <shadeslayer> Quintasan: we really really need neon.kubuntu.org i think :P
[17:15] <Quintasan> Riddell: ^
[17:15] <Riddell> what what?
[17:16] <apachelogger> shadeslayer: you can get one until 2013
[17:16] <apachelogger> 2020 tops
[17:16] <shadeslayer> whai?
[17:16] <apachelogger> slowness
[17:16] <shadeslayer> slow sysadmins? :D
[17:17] <apachelogger> totally reminds me on the snails form http://en.wikipedia.org/wiki/Uzumaki
[17:17] <sheytan> i can make a mockup, ofirk the code and we're home ;)
[17:17] <Quintasan> Riddell: or tell shadeslayer who he should be bugging and he will get it done in no time
[17:17] <Quintasan> :P
[17:17] <shadeslayer> lemme at em
[17:18]  * shadeslayer will poke neon rods all over sysadmins
[17:18] <Riddell> Quintasan: what's the question?
[17:18]  * apachelogger puts a nice pink hat on shadeslayer so he'll be more successful
[17:18]  * sheytan still needs to use google translator ;/
[17:18] <Quintasan> Riddell: shadeslayer thought that we should have neon.kubuntu.org
[17:18] <shadeslayer> still do ^
[17:18] <Quintasan> apachelogger claims that we can't get one until 2013
[17:19] <Riddell> why not just use a page on kubuntu.org and wiki pages?
[17:19] <Quintasan> Exacly my point :P
[17:19]  * apachelogger thinks shadeslayer just wants to post nakkid pictures of Quintasan on nko anyway
[17:19] <Quintasan> @_@
[17:19]  * Quintasan takes banhammer out
[17:19]  * Quintasan hits apachelogger
[17:20] <apachelogger> see
[17:20] <ulysses> Quintasan: that won't be enough:(
[17:20] <apachelogger> it makes more sense if you use a whip
[17:20] <apachelogger> ...
[17:20] <Quintasan> ...
[17:20] <apachelogger> http://upload.ecvv.com/upload/Product/20085/China_sex_toy_whip20085221551479.jpg
[17:20] <ulysses> we must seal apachelogger into the Pandorica!
[17:21] <neversfelde> someone already working on this amarok scanning bug?
[17:21]  * Quintasan puts some concrete boots on apachelogger
[17:21] <shadeslayer> Quintasan: i guess kubuntu.org/neon then? which points to a wiki page
[17:21] <apachelogger> what is an amarok scannign bug?
[17:21]  * shadeslayer doesnt like wiki theme tbh
[17:21] <neversfelde> apachelogger: Jeff mentions it on the amarok packager list
[17:22] <apachelogger> oh
[17:22] <apachelogger> I havent read mails in a week or so
[17:22] <Quintasan> shadeslayer: dunno, just mention it on community projects with link to wiki
[17:22] <Quintasan> and we are done
[17:23] <neversfelde> apachelogger: the fix is here http://tinyurl.com/35kxvcn
[17:23] <apachelogger> the only good thing about the you bun too wiki is that every launchpad us0r also got wiki access
[17:23] <apachelogger> *only*
[17:23] <Quintasan> I think Jono wanted me to inform him when we are ready so he can spread the word
[17:23] <apachelogger> neversfelde: Riddell is upping that he said
[17:23] <neversfelde> apachelogger: great, I'll backport it to the lucid package, if he does not
[17:24] <Quintasan> shadeslayer: seriosly, dunno, let's get this working first
[17:24] <shadeslayer> yeah ... thats more important :P
[17:24] <Quintasan> and then worry about fame and/or broken systems
[17:24] <apachelogger> Quintasan: if you like being abused for other people's PR
[17:24] <shadeslayer> Quintasan: we still need to make a entry file for KDM
[17:24]  * apachelogger likes being abused on any occasion
[17:24] <shadeslayer> and put it in the meta package
[17:24]  * Quintasan takes out a whip
[17:24] <Quintasan> not
[17:24] <Quintasan> that won't be effective
[17:25] <Quintasan> hmmm
[17:25] <shadeslayer> apachelogger: get your ruby skilz and package us a neonmake script :>
[17:25] <Quintasan> vuvuzela time!
[17:25] <apachelogger> shadeslayer: then it wont be no metapackage no more, will it?
[17:25] <apachelogger> shadeslayer: there is a neonmake script
[17:25]  * Quintasan hits apachelogger with vuvuzela
[17:25] <shadeslayer> apachelogger: itll work with our packaging?
[17:26] <apachelogger> *shrug*
[17:26] <Quintasan> shadeslayer: why on earth do we want neonmake script?
[17:26] <apachelogger> there is also a kdm file
[17:26] <shadeslayer> Quintasan: easier to compile stuff with it
[17:26] <apachelogger> there is all sorts of stuff
[17:26] <ulysses> Before I forget again, we have begin to write the monthly report: https://wiki.kubuntu.org/Kubuntu/TeamReports
[17:26] <apachelogger> if you cared to look
[17:26] <Quintasan> shadeslayer: what do we want to compile with it?
[17:26] <shadeslayer> Quintasan: dude!!!
[17:26] <apachelogger> ulysses: I did nothing
[17:26] <apachelogger> (I think)
[17:26] <apachelogger> though I think I tought that something is note worthy
[17:26] <shadeslayer> Quintasan: like if someone wants a app from kde-apps.org compiled with neon packages
[17:27] <apachelogger> but that was sometime early on this month
[17:27]  * ulysses writes to the wiki that apachelogger did nothing
[17:27] <Quintasan> apachelogger: it's not like it is any different from what you usually do :P
[17:27] <apachelogger> and I was afraid I would forget
[17:27] <apachelogger> and indeed I forgot
[17:27] <apachelogger> how fitting
[17:27] <shadeslayer> ulysses: lol The server encountered an internal error or misconfiguration and was unable to complete your request.
[17:27] <shadeslayer> wikifail
[17:27] <apachelogger> Quintasan: I still do more than nixternal though :P
[17:27] <ulysses> shadeslayer: works for me ;)
[17:27] <shadeslayer> works now :P
[17:27] <Quintasan> Isn't nixternal a member of like over 9000 teams?
[17:27] <apachelogger> shadeslayer: *only*
[17:28] <apachelogger> Quintasan: so are other people
[17:28] <Quintasan> "We love Harald"?
[17:28] <ulysses> Do we?
[17:28] <apachelogger> I do not
[17:29] <Quintasan> Isn't that some sort of apachelogger's fanclub on LP?
[17:29] <Quintasan> I think apachelogger does the most work there
[17:29] <Quintasan> :P
[17:29] <ulysses> founded by little emo girls?
[17:29] <Quintasan> lol
[17:29] <apachelogger> cool
[17:29] <apachelogger> my GSOC stuff arrived
[17:29] <shadeslayer> apachelogger: only now?
[17:29] <apachelogger> and fedex only now informed me
[17:30] <apachelogger> I find this funny
[17:30] <apachelogger> I get a mail *after* it was delivered
[17:30] <apachelogger> not before or anything
[17:30] <Quintasan> >Harald Sitter's Groupies
[17:30] <Quintasan> https://launchpad.net/~we-love-harald
[17:30] <Quintasan> :D
[17:30] <apachelogger> UPS rulez!
[17:30] <shadeslayer> lag?
[17:30] <Quintasan> hey, wtf, why am I a member?
[17:30] <apachelogger> shadeslayer: no no, was delivered today
[17:30] <shadeslayer> Quintasan: you didnt know about that? look at the members :>
[17:30] <apachelogger> shipped on 21
[17:31] <shadeslayer> 39 Active members :P
[17:31] <shadeslayer> all of them K/Ubuntu Members :P
[17:31] <apachelogger> I must be loved
[17:31] <ulysses> 39 cultist
[17:31]  * apachelogger takes a note to tell his therapist about that
[17:32]  * apachelogger as too much stuff in his inbox and closes the browser again
[17:32] <Quintasan> no, seriously, I have homework to do and I'm losing time on browsing through apacheloggers fans
[17:32] <shadeslayer> apachelogger: browser = rekonq? :D
[17:33] <apachelogger> konqueror
[17:33] <shadeslayer> oic...
[17:33] <apachelogger> I am not using that dirtbag no moar
[17:33] <apachelogger> made me depressed
[17:33] <shadeslayer> apachelogger: http://rekonq.kde.org/ :P
[17:34] <apachelogger> now it could not use capacity I recon
[17:34] <apachelogger> gotta love the level of integration
[17:35] <apachelogger> http://www.amnesiagame.com/
[17:35] <apachelogger> uhhh
[17:35] <apachelogger> that is one spooky game right htere
[17:36] <ari-tczew> debfx: your change provides following warnings in buildlog: http://paste.ubuntu.com/499228/ is ot okay?
[17:36] <ari-tczew> s/ot/it
[17:40] <sheytan> banana banana banana juice :D
[17:41] <sheytan> ok, this is the old community page http://i.imgur.com/DX35A.jpg
[17:41] <sheytan> and here's the new one http://i.imgur.com/huvtv.jpg : D
[17:42] <shadeslayer> sheytan: s/productive/production
[17:42] <sheytan> shadeslayer my english isn't perfect :P
[17:43] <shadeslayer> sheytan: nobody has perfect english... apart from the Queen i suppose :P
[17:43] <sheytan> yep :D
[17:43] <sheytan> anyway, how's the design/
[17:43] <sheytan> ?
[17:44] <shadeslayer> sheytan: looks ok to me.. you need more projects :P
[17:45] <sheytan> shadeslayer as you can  see i don't have space in  the mock, so they'll be added to the 'true' page :D
[17:45] <shadeslayer> hehe :D
[17:49] <nixternal> apachelogger: dust does more than I do
[17:50] <shadeslayer> apachelogger: http://pastebin.com/XhqN90UD : still doesnt work i think
[17:53] <apachelogger> nixternal: but we do not love dust as much as we love our nixternal :)
[17:53] <apachelogger> shadeslayer: you broke it
[17:54] <shadeslayer> :>
[17:54] <shadeslayer> whats wrong?
[17:54] <apachelogger> shadeslayer: if I were you I would first try to get stuff working without -i :P
[17:54] <shadeslayer> oh :P
[17:55] <shadeslayer> apachelogger: works without -i
[17:56] <shadeslayer> need to put -o to save the file somewhere and see if its actually downloaded
[17:57] <shadeslayer> doesnt work now -.-
[17:57] <shadeslayer> and progressBar() is foobared
[17:59] <shadeslayer> im sleeping.. terrible headache... cya everyone
[17:59] <apachelogger> o/
[18:14] <smarter> JontheEchidna: hey (sorry for being a bit MIA, college just started, no laptop until today, etc), when apt is already running and you try to install something with qapt-batch, it doesn't complain, download the package, and acts like the installation succeeded when it didn't
[18:15] <smarter> also, when trying to install codecs with amarok, qapt-batch with something like ' Couldn't find package "" ', ps aux says the command line is "/usr/bin/qapt-batch --install  libavcodec-extra-52 libmp3lame0", note the extra space, which apparently isn't ignored
[18:16] <shadeslayer> smarter: iirc that is fixed
[18:16] <smarter> not on the version present in maverick it seems
[18:17]  * smarter hasn't installed the svn version on his laptop yet
[18:17] <shadeslayer> smarter: https://edge.launchpad.net/bugs/644947
[18:18] <smarter> oh, cool
[18:18] <smarter> JontheEchidna: I'll try to work on that tomorrow/this week-end
[18:20] <JontheEchidna> smarter: same deal here with college ;-)
[18:20] <JontheEchidna> smarter: ' Couldn't find package "" ' was a QStringList in kubuntu-notification-helper with an empty QString in it
[18:20] <JontheEchidna> updating should fix
[18:20] <smarter> great
[18:21] <JontheEchidna> btw, you should check out the latest batch of muon commits
[18:21] <smarter> will do
[18:21] <smarter> maybe I'll hack on qapt/muon during my "Introduction to OOP" class in Java :p
[18:21] <JontheEchidna> :P
[18:22] <JontheEchidna> I have an "Intro to C++" class. Apparently we don't get to OOP until the end of the semester
[18:22] <JontheEchidna> so it's all just procedural crap
[18:22] <smarter> confuse your professors by using templates :P
[18:23] <JontheEchidna> :P
[18:24] <JontheEchidna> I did use an std::list when they wanted me to write a program that would take user input for 5 numbers and average them
[18:24] <JontheEchidna> I used it to make it so that the user could average as many numbers as they wanted :P
[18:25] <JontheEchidna> they went "you're using advanced data structures in your program. What C++ background do you have?"
[18:25] <smarter> haha
[18:27] <smarter> I didn't know linked list were advanced :p
[18:27] <debfx> ari-tczew: yes, they probably just don't haven an SONAME
[18:27] <debfx> not sure why dpkg-shlibdeps displays the same warning 4 times
[18:27] <ari-tczew> debfx: uploaded
[18:27] <JontheEchidna> Quintasan: if I am correct progressBar() will only be called once when the QProcess starts
[18:27] <debfx> ari-tczew: thanks
[18:27] <JontheEchidna> Quintasan: and if it was called multiple times it would create a new progress bar each time it was called
[18:29] <JontheEchidna> It would be better to make a pointer to a QPlainTextEdit as a member variable inside the header, then initialize it in the class constructor, then hook it up to update the text using signals and slots
[18:31] <JontheEchidna> smarter: so basically now all PackageWidget subclasses declare their own filters across all available packages. It doesn't incur a performance hit for Update/Review since getting a list of pointers is cheap, and most of the pain that ManagerWidget has is due to sorting
[18:32] <smarter> okay, great!
[18:33] <smarter> did you try typedef'ing QLatin1String to workaround QVariant creating QString?
[18:33] <JontheEchidna> I haven't tried that, no
[18:33] <smarter> I'll look into it
[18:34] <JontheEchidna> For the xapian update progress bar, we're using the dbus interface that the updater exposes, but I think it's busted since it never sends a 100% and/or finished signal :/
[18:34] <JontheEchidna> means I'll have to break out the python and fix upstream'
[18:34] <JontheEchidna> s bugs :P
[18:35] <JontheEchidna> for us it means that the progress bar won't go away after the xapian update is done
[18:35] <smarter> I saw your commits, but I don't know when the xapian index is updated
[18:35] <JontheEchidna> muon tells libqapt to check if the xapian index is outdated after a cache refresh/installation
[18:36] <JontheEchidna> if it needs updating, it tells libqapt to tell the qaptworker to update it, and it uses the dbus interface to communicate between muon -> update-apt-xapian-indexs
[18:37] <smarter> 'kay
[18:37] <smarter> it shouldn't be too hard to make qapt-batch check if dpkg is already running before trying anything, no?
[18:37] <smarter> and getting the fix into Maverick
[18:38] <JontheEchidna> if dpkg is running the worker should throw a LockError, no?
[18:38] <smarter> well, when I tested it today it didn't seem to do so
[18:39]  * JontheEchidna tests by installing something with debconf
[18:42] <JontheEchidna> seems to work with installing aiccu with apt-get, but it hangs on obtaining authorization if another program is using qaptworker
[18:42] <JontheEchidna> (where work == throw lock error)
[18:43] <JontheEchidna> I'm wondering if qapt-batch shouldn't just use libqapt, even at the cost of 14 MiB ram.
[18:43] <smarter> not here, it tries(and says it succeeded) installing stuff when aptitude full-upgrade is downloading packages
[18:44] <JontheEchidna> dpkg isn't running when packages are downloading
[18:44] <smarter> but /var/lib/dpkg/lock is present
[18:44] <JontheEchidna> somehow the qapt-worker is obtaining the lock
[18:45] <JontheEchidna> /var/lib/dpkg/lock is always present
[18:45] <smarter> oh right
[18:45] <smarter> how is that even possible? :p
[18:45] <JontheEchidna> must be something about the contents of the lock that determines locked-ness?
[18:46] <smarter> E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
[18:46] <smarter> that's what apt-get and aptitude say when downloading package
[18:47] <JontheEchidna> ah, the locking application must open the file in such a way so that other programs can't
[18:47] <JontheEchidna> ...which reminds me. Synaptic locks the package system even when not committing changes.
[18:47] <JontheEchidna> perhaps we (and aptitude, apparently) should do the same so that other apps don't change things underneath us
[18:48] <smarter> that would be safe, yes
[18:48] <JontheEchidna> though iirc the Ubuntu Software Center can actually detect these changes somehow...
[18:50] <JontheEchidna> hmm, or maybe not
[18:50] <smarter> sudo fuser /var/lib/dpkg/lock doesn't change when qapt-batch is running and ignoring the lock
[18:53] <JontheEchidna> ah, I'm seeing the ignoring, too
[18:54] <JontheEchidna> it only seems to respect the lock when /var/lib/dpkg/lock is locked *and* dpkg is running, or something
[18:54] <smarter> it happened when downloading
[19:09] <smarter> 'night!
[19:17] <neversfelde> is launchpad offline?
[19:18] <JontheEchidna> iirc there was a scheduled outage for code hosting
[19:18] <neversfelde> k
[19:19] <neversfelde> Riddell: are you going to upload amarok with the new patch for Lucid?
[19:19] <CIA-116> [libqapt] jmthomas * 1178722 * trunk/extragear/sysadmin/libqapt/src/worker/ (worker.cpp worker.h) Herp derp. I can't tell the difference between bool and int. :/
[20:58] <Riddell> neversfelde: if you could upload amarok with the patch to lucid that would be great
[21:19] <CIA-116> [muon] jmthomas * 1178750 * trunk/extragear/sysadmin/muon/ (2 files in 2 dirs) (log message trimmed)
[21:19] <CIA-116> Workaround to prevent a crash that happened because the backend was being
[21:19] <CIA-116> reloaded twice. (Once in ManagerWidget, once in ReviewWidget) A PackageWidget
[21:41] <mgraesslin> lately we get many crashreports from Maverick with a crash in the driver. Is there anything we could do to get the users to *not* report those?
[22:03] <sheytan> http://madsheytan.blogspot.com/2010/09/wiesci-z-prac-nad-strona-kubuntu.html take a look at some mockups :D
[22:34] <Mamarok> neversfelde: thanks for the Amarok package, but did you see the alert on the packagers list for this patch? -> http://gitweb.kde.org/amarok/amarok.git/commitdiff_plain/79d86829294ac54132c01153660e70e30c15c378?hp=fd2a40d970c57fa2102e95de1a60c59e37892638
[22:40] <Riddell> Mamarok: he did but maybe he's gone away, I can do tham
[22:41] <Mamarok> Riddell: that would be nice indeed
[22:44] <Riddell> Mamarok: uploaded
[23:01] <debfx> Mamarok: that commit is a bit broken
[23:01] <debfx> it checks data[i].unicode() < 20 && data[i].unicode() != 9 && ...
[23:02] <debfx> oh wait that's actually correct
[23:05] <Riddell> debfx: see jefferai's post on kde-packager for the details
[23:08] <debfx> Riddell: I haven't got a mail about that issue
[23:09] <debfx> the kde-packager archive also doesn't show one
[23:18] <dantti> Riddell: hey :) sheytan suggested Apper as a new name, what do you think? :D


[01:42] -queuebot:#ubuntu-release- Unapproved: xorg-server-lts-xenial (trusty-proposed/main) [2:1.18.3-1ubuntu2.2~trusty3 => 2:1.18.3-1ubuntu2.3~trusty1] (no packageset)
[03:02] -queuebot:#ubuntu-release- New: accepted graphene [source] (zesty-proposed) [1.5.4-0ubuntu1]
[03:03] -queuebot:#ubuntu-release- Unapproved: python-os-brick (xenial-proposed/main) [1.2.0-2ubuntu0.1 => 1.2.0-2ubuntu0.2] (openstack, ubuntu-server)
[03:07] -queuebot:#ubuntu-release- New binary: graphene [ppc64el] (zesty-proposed/universe) [1.5.4-0ubuntu1] (no packageset)
[03:07] -queuebot:#ubuntu-release- New binary: graphene [amd64] (zesty-proposed/universe) [1.5.4-0ubuntu1] (no packageset)
[03:08] -queuebot:#ubuntu-release- New binary: graphene [s390x] (zesty-proposed/universe) [1.5.4-0ubuntu1] (no packageset)
[03:09] -queuebot:#ubuntu-release- Unapproved: accepted xorg-server-lts-xenial [source] (trusty-proposed) [2:1.18.3-1ubuntu2.3~trusty1]
[03:09] -queuebot:#ubuntu-release- New binary: graphene [arm64] (zesty-proposed/universe) [1.5.4-0ubuntu1] (no packageset)
[03:11] -queuebot:#ubuntu-release- New binary: graphene [powerpc] (zesty-proposed/universe) [1.5.4-0ubuntu1] (no packageset)
[03:11] -queuebot:#ubuntu-release- Unapproved: python-os-brick (yakkety-proposed/main) [1.6.1-0ubuntu1 => 1.6.1-0ubuntu1.1] (openstack, ubuntu-server)
[03:28] <tjaalton> slangasek: what happened to xorg-server-lts-xenial? 1.18.4 was already pretty much verified but it got replaced with an older version?
[03:29] <slangasek> tjaalton: there were a significant number of bugs linked from the changelog which had not been verified; I was discussing it with bdmurray because this was blocking fixing snapd installability on the desktop, and as we couldn't see any immediate path to getting this one verified to his satisfaction, we decided to swap in just the packaging fixes and reupload 1.18.4 afterwards
[03:30] <tjaalton> ok
[03:30] <tjaalton> well
[03:31] <tjaalton> I don't see anyone actually verifying all those bugs
[03:31] <tjaalton> on trusty
[03:32] <slangasek> then it didn't really seem to be following the SRU process?
[03:32] <tjaalton> aren't these backports special?
[03:33] <slangasek> tjaalton: bdmurray expressed concern about the test case in bug #1619142
[03:34] <slangasek> I didn't review the SRU bugs myself in any detail, I'm just the messenger here
[03:34] <tjaalton> sure
[03:36] <slangasek> tjaalton: anyway, the SRU had certainly stalled out already by having a bunch of other, non-verified bugs linked from the changelog / .changes file... hwe backports aren't special for that
[03:36] <tjaalton> should've uploaded with just the mre/snapd bugs?
[03:36] <tjaalton> in .changes
[03:37] <tjaalton> that'd take care of the process ;)
[03:46] <bdmurray> It wouldn't improve the test case / results in bug 1619142 though
[03:48] <tjaalton> that bug didn't actually have any test case when the upload was acked ;)
[03:49] <tjaalton> then someone requested it yesterday and I put something
[03:52] <tjaalton> added some
[09:10] <philroche> Hi, would anyone be able to do accept gce-compute-image-packages in to trusty-proposed? This is a new package and exists in zesty, yakkety and xenial already. lp bug - https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1643585 Package in upload queue - https://launchpad.net/ubuntu/trusty/+queue?queue_state=0&queue_text=gce-compute-image-packages.
[10:33] <apw> philroche, other than the version number being inconistent with those in the other backports it looks ok
[10:35] <ginggs> apw: would you please add 'force-badtest ocrmypdf/4.3.5-2/s390x' to your hints?
[10:36] <ginggs> and 'force-badtest freecad/0.16+dfsg2-3/ppc64el freecad/0.16+dfsg2-3/s390x' in p.itti's hints
[10:36] <philroche> apw. Updating version number now
[10:38] <ginggs> apw: and lastly, please 'force-badtest python-pysam/0.10.0+ds-1ubuntu1/armhf python-pysam/0.10.0+ds-1ubuntu1/i386' - it doesn't actually build on those, not sure why its trying to run tests there
[10:42] -queuebot:#ubuntu-release- New: rejected gce-compute-image-packages [source] (trusty-proposed) [20160930-0ubuntu3~14.04]
[10:43] <apw> ^ rejecting to get a new version number
[10:51] -queuebot:#ubuntu-release- New source: gce-compute-image-packages (trusty-proposed/primary) [20160930-0ubuntu3~14.04.0]
[10:52] <philroche> apw: Version number for gce-compute-image-packages updated and reuploaded https://launchpad.net/ubuntu/trusty/+queue?queue_state=0&queue_text=gce-compute-image-packages
[10:59] <apw> philroche, it just told me above :)
[11:05] <philroche> :)
[11:12] -queuebot:#ubuntu-release- New: accepted gce-compute-image-packages [source] (trusty-proposed) [20160930-0ubuntu3~14.04.0]
[11:12] <apw> philroche, ^
[11:14] -queuebot:#ubuntu-release- New binary: gce-compute-image-packages [i386] (trusty-proposed/universe) [20160930-0ubuntu3~14.04.0] (ubuntu-cloud)
[11:17] -queuebot:#ubuntu-release- Packageset: 160 entries have been added or removed
[11:32] -queuebot:#ubuntu-release- Packageset: 111 entries have been added or removed
[11:53] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (yakkety-proposed) [2.22.2+16.10]
[11:54] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (xenial-proposed) [2.22.2]
[11:55] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (trusty-proposed) [2.22.2~14.04]
[12:02] <apw> Laney, have you seen cases where britney run tests for packages which are in depwait ?
[12:05] <Laney> apw: no, but I've never looked for such a thing - you can check th elogs to see what it did
[12:05] <Laney> also that's the kind of thing you could write a testcase for and then fix ;-)
[12:05] <apw> Laney, :-p
[12:06] <apw> ginggs, look sensible, done.
[12:06] <Laney> Although I suppose it might be valid to run testsuites in the case of arch:all binaries
[12:06]  * apw thinks about that ... maybe
[12:06] <Laney> Maybe
[12:07] <apw> it really feels if we have builds in a faliure state that we cannot know if we have what we need to run tests
[12:07] <apw> we may have, but we do not know
[12:09] -queuebot:#ubuntu-release- New: accepted libopenshot [i386] (zesty-proposed) [0.1.2+ds1-1]
[12:09] -queuebot:#ubuntu-release- New: accepted libopenshot [i386] (zesty-proposed) [0.1.2+ds1-3]
[12:09] -queuebot:#ubuntu-release- New: accepted libopenshot [amd64] (zesty-proposed) [0.1.2+ds1-3]
[12:13] <Laney> Looks like in this case it used to work on those arches and then stopped with an update
[12:13] <Laney> otherwise it wouldn't be a regression
[12:15] <Laney> And the source does build an arch:all binary package which could be tested
[12:17] -queuebot:#ubuntu-release- Packageset: Removed myspell-ku from personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Removed mythes-it from personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Removed mythes-sv from personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added fonts-adf to personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added fonts-atarismall to personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added fonts-ddc-uchen to personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added fonts-firacode to personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added fonts-go to personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added fonts-liberation2 to personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added fonts-ocr-b to personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added fonts-oradano-mincho-gsrr to personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added fonts-sambhota-tsugring to personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added fonts-tiresias to personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added hunspell-bo to personal-gunnarhj in zesty
[12:26] <ginggs> apw: many thanks!
[13:17] -queuebot:#ubuntu-release- New: accepted gce-compute-image-packages [i386] (trusty-proposed) [20160930-0ubuntu3~14.04.0]
[13:19] <acheronuk> Hi. Can someone please review and accept our sources in the NEW queue please? they are needed before we can our packageset refresh done.
[13:19] <acheronuk> namely minuet, konqueror, kommander, klinkstatus, kimagemapeditor,kfind, kfilereplace, keditbookmarks, kdialog
[13:19] <acheronuk> thanks
[13:19] <acheronuk> most of those are actually OLD packages, but KDE have now split the sources
[13:19] <acheronuk> .
[13:19] <acheronuk> minuet is part of the full KDE applications 16.04.0 release that we were unable to get into yakkety, due to not have some build depends for it in the archive
[13:19] <acheronuk> see: https://www.kde.org/announcements/announce-applications-16.04.0.php
[13:19] <acheronuk> in 16.12 KDE app we are now doing...
[13:19] <acheronuk> kde-baseapps (split into kdialog, keditbookmarks, kfind, konqueror)
[13:19] <acheronuk> kdewebdev (split into kfilereplace, kimagemapeditor, klinkstatus, kommander)
[13:19] <acheronuk> hence these are nothing new per se. just split and some ported to KF5
[13:19] <acheronuk> see: https://community.kde.org/Applications/16.12_Release_Notes#Tarballs_that_we_have_split
[13:19] <acheronuk> thanks :)
[13:37] -queuebot:#ubuntu-release- Unapproved: im-config (xenial-proposed/main) [0.29-1ubuntu12.3 => 0.29-1ubuntu12.4] (input-methods, kubuntu, personal-gunnarhj, ubuntu-desktop)
[13:50] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (zesty-proposed/main) [4.9.0-16.17] (core, kernel)
[13:51] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (zesty-proposed) [4.9.0-16.17]
[13:56] -queuebot:#ubuntu-release- New: accepted kdeclarative [amd64] (zesty-proposed) [5.30.0-0ubuntu1]
[13:56] -queuebot:#ubuntu-release- New: accepted kdeclarative [armhf] (zesty-proposed) [5.30.0-0ubuntu1]
[13:56] -queuebot:#ubuntu-release- New: accepted kdeclarative [powerpc] (zesty-proposed) [5.30.0-0ubuntu1]
[13:56] -queuebot:#ubuntu-release- New: accepted kdeclarative [s390x] (zesty-proposed) [5.30.0-0ubuntu1]
[13:56] -queuebot:#ubuntu-release- New: accepted kdeclarative [arm64] (zesty-proposed) [5.30.0-0ubuntu1]
[13:56] -queuebot:#ubuntu-release- New: accepted kdeclarative [ppc64el] (zesty-proposed) [5.30.0-0ubuntu1]
[13:56] -queuebot:#ubuntu-release- New: accepted kdeclarative [i386] (zesty-proposed) [5.30.0-0ubuntu1]
[14:04] -queuebot:#ubuntu-release- New: accepted knewstuff [amd64] (zesty-proposed) [5.30.0-0ubuntu1]
[14:04] -queuebot:#ubuntu-release- New: accepted knewstuff [armhf] (zesty-proposed) [5.30.0-0ubuntu1]
[14:04] -queuebot:#ubuntu-release- New: accepted knewstuff [powerpc] (zesty-proposed) [5.30.0-0ubuntu1]
[14:04] -queuebot:#ubuntu-release- New: accepted knewstuff [s390x] (zesty-proposed) [5.30.0-0ubuntu1]
[14:04] -queuebot:#ubuntu-release- New: accepted knewstuff [arm64] (zesty-proposed) [5.30.0-0ubuntu1]
[14:04] -queuebot:#ubuntu-release- New: accepted knewstuff [ppc64el] (zesty-proposed) [5.30.0-0ubuntu1]
[14:04] -queuebot:#ubuntu-release- New: accepted knewstuff [i386] (zesty-proposed) [5.30.0-0ubuntu1]
[15:13] -queuebot:#ubuntu-release- Unapproved: landscape-client (trusty-proposed/main) [14.12-0ubuntu0.14.04 => 14.12-0ubuntu4.14.04] (ubuntu-desktop, ubuntu-server)
[15:52] -queuebot:#ubuntu-release- New binary: graphene [ppc64el] (zesty-proposed/universe) [1.5.4-0ubuntu2] (no packageset)
[15:53] <apw> acheronuk, as these new binaries are not yet in debian, do we have confirmation that debian will use the same epoch ?  we do not want to be epoching ahead of them
[15:53] -queuebot:#ubuntu-release- New binary: graphene [amd64] (zesty-proposed/universe) [1.5.4-0ubuntu2] (no packageset)
[15:53] -queuebot:#ubuntu-release- New binary: graphene [i386] (zesty-proposed/universe) [1.5.4-0ubuntu2] (no packageset)
[15:53] -queuebot:#ubuntu-release- New binary: graphene [arm64] (zesty-proposed/universe) [1.5.4-0ubuntu2] (no packageset)
[15:54] -queuebot:#ubuntu-release- Unapproved: im-config (xenial-proposed/main) [0.29-1ubuntu12.3 => 0.29-1ubuntu12.4] (input-methods, kubuntu, personal-gunnarhj, ubuntu-desktop)
[15:55] -queuebot:#ubuntu-release- New binary: graphene [s390x] (zesty-proposed/universe) [1.5.4-0ubuntu2] (no packageset)
[15:56] -queuebot:#ubuntu-release- New binary: graphene [powerpc] (zesty-proposed/universe) [1.5.4-0ubuntu2] (no packageset)
[15:57] -queuebot:#ubuntu-release- New: rejected graphene [amd64] (zesty-proposed) [1.5.4-0ubuntu1]
[15:57] -queuebot:#ubuntu-release- New: rejected graphene [powerpc] (zesty-proposed) [1.5.4-0ubuntu1]
[15:57] -queuebot:#ubuntu-release- New: rejected graphene [s390x] (zesty-proposed) [1.5.4-0ubuntu1]
[15:57] -queuebot:#ubuntu-release- New: rejected graphene [arm64] (zesty-proposed) [1.5.4-0ubuntu1]
[15:57] -queuebot:#ubuntu-release- New: rejected graphene [ppc64el] (zesty-proposed) [1.5.4-0ubuntu1]
[16:11] <acheronuk> apw: keditbookmarks, kdialog are genuinely not yet in debian so the epoch was dropped.
[16:12] <acheronuk> the others ARE in debian, with an epoch, so we cannot drop it for those debs
[16:12] <acheronuk> https://packages.debian.org/sid/konqueror
[16:12] <acheronuk> https://packages.debian.org/sid/klinkstatus
[16:12] <acheronuk> https://packages.debian.org/sid/kimagemapeditor
[16:12] <acheronuk> https://packages.debian.org/sid/kfind
[16:12] <acheronuk> https://packages.debian.org/sid/kfilereplace
[16:13] <apw> acheronuk, bah why do they not show up in rmadison
[16:14] <apw> oh ... there are already binary packages of those names ... right
[16:15] <acheronuk> yes, so where there were not, we dropped epoch. where there was, we could not for now
[16:16] <apw> i guess they cannot do anything other than what you have done
[16:23] -queuebot:#ubuntu-release- Unapproved: rejected im-config [source] (xenial-proposed) [0.29-1ubuntu12.4]
[16:25] -queuebot:#ubuntu-release- Unapproved: accepted im-config [source] (xenial-proposed) [0.29-1ubuntu12.4]
[16:28] -queuebot:#ubuntu-release- New binary: graphene [ppc64el] (zesty-proposed/universe) [1.5.4-0ubuntu3] (no packageset)
[16:29] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (xenial-proposed) [2.0.9-0ubuntu1~16.04.1]
[16:29] -queuebot:#ubuntu-release- New binary: graphene [arm64] (zesty-proposed/universe) [1.5.4-0ubuntu3] (no packageset)
[16:29] -queuebot:#ubuntu-release- New binary: graphene [armhf] (zesty-proposed/universe) [1.5.4-0ubuntu3] (no packageset)
[16:30] -queuebot:#ubuntu-release- New binary: graphene [amd64] (zesty-proposed/universe) [1.5.4-0ubuntu3] (no packageset)
[16:30] -queuebot:#ubuntu-release- New binary: graphene [s390x] (zesty-proposed/universe) [1.5.4-0ubuntu3] (no packageset)
[16:30] -queuebot:#ubuntu-release- New binary: graphene [i386] (zesty-proposed/universe) [1.5.4-0ubuntu3] (no packageset)
[16:32] -queuebot:#ubuntu-release- New binary: graphene [powerpc] (zesty-proposed/universe) [1.5.4-0ubuntu3] (no packageset)
[16:34] -queuebot:#ubuntu-release- Unapproved: accepted lxc [source] (yakkety-proposed) [2.0.7-0ubuntu1~16.10.1]
[16:37] -queuebot:#ubuntu-release- Unapproved: accepted lxcfs [source] (yakkety-proposed) [2.0.6-0ubuntu1~16.10.1]
[16:40] -queuebot:#ubuntu-release- Unapproved: accepted lxcfs [source] (xenial-proposed) [2.0.6-0ubuntu1~16.04.1]
[16:41] -queuebot:#ubuntu-release- Unapproved: accepted lxc [source] (xenial-proposed) [2.0.7-0ubuntu1~16.04.1]
[16:49] -queuebot:#ubuntu-release- Unapproved: accepted os-prober [source] (xenial-proposed) [1.70ubuntu3.3]
[16:52] <apw> jbicha, are you going to fix that graphene armhf ftbfs ?
[16:53] <apw> jbicha, that is intended as a query, as it is stuck in New on all other arches
[17:26] <jbicha> apw: it's fixed now :) https://launchpad.net/ubuntu/+source/graphene/1.5.4-0ubuntu3
[17:27] <apw> jbicha, heh
[17:30] -queuebot:#ubuntu-release- New: rejected graphene [amd64] (zesty-proposed) [1.5.4-0ubuntu2]
[17:30] -queuebot:#ubuntu-release- New: rejected graphene [i386] (zesty-proposed) [1.5.4-0ubuntu2]
[17:30] -queuebot:#ubuntu-release- New: rejected graphene [ppc64el] (zesty-proposed) [1.5.4-0ubuntu2]
[17:30] -queuebot:#ubuntu-release- New: rejected graphene [arm64] (zesty-proposed) [1.5.4-0ubuntu2]
[17:30] -queuebot:#ubuntu-release- New: rejected graphene [s390x] (zesty-proposed) [1.5.4-0ubuntu2]
[17:30] -queuebot:#ubuntu-release- New: rejected graphene [powerpc] (zesty-proposed) [1.5.4-0ubuntu2]
[17:31] -queuebot:#ubuntu-release- New: accepted graphene [amd64] (zesty-proposed) [1.5.4-0ubuntu3]
[17:31] -queuebot:#ubuntu-release- New: accepted graphene [armhf] (zesty-proposed) [1.5.4-0ubuntu3]
[17:31] -queuebot:#ubuntu-release- New: accepted graphene [powerpc] (zesty-proposed) [1.5.4-0ubuntu3]
[17:32] -queuebot:#ubuntu-release- New: accepted graphene [s390x] (zesty-proposed) [1.5.4-0ubuntu3]
[17:32] -queuebot:#ubuntu-release- New: accepted graphene [arm64] (zesty-proposed) [1.5.4-0ubuntu3]
[17:32] -queuebot:#ubuntu-release- New: accepted graphene [ppc64el] (zesty-proposed) [1.5.4-0ubuntu3]
[17:32] -queuebot:#ubuntu-release- New: accepted graphene [i386] (zesty-proposed) [1.5.4-0ubuntu3]
[17:33] <jbicha> thanks
[17:34] <acheronuk> apw: exactly, debian will have to do the same if they want to keep those apps
[17:36] <santa_> I have a question which is slightly offtopic here but I need to ask
[17:36] <santa_> we got recently a new testcase added to the kio testsuite which apparently needs to access the network
[17:37] <santa_> so it's failing on the official autopkgtest ubuntu infra
[17:37] <apw> santa_, i believe the lxc and docker.io tests do do that kind of thing
[17:38] <santa_> doing it by the book the correct solution would be adding the isolation-container restriction to the testsuite
[17:38] <nacc> santa_: i believe you can specify the isolation-container restriction ... yeah :)
[17:38] <santa_> however I'm concerned that this would result in the testsuite being skipped on the official infra
[17:39] <santa_> so I'm wondering if it would be better to just disable the test case which access the network
[17:40] <santa_> so we would get the tests running even if the official infra doesn't provide the stuff needed for isolation-container
[17:40] <santa_> so the million dollar question is: does the official infra provide support for that?
[17:40] <santa_> any other toughts?
[17:41] <santa_> apw: thanks for the info btw
[17:41] <nacc> santa_: could you break up the tests in d/t/control to have the tests that don't need network in one stanza and the one that does in another?
[17:41] <nacc> santa_: not sure if that's possible or not
[17:41] <apw> that indeed
[17:41] <apw> though all are at least containers
[17:42] <santa_> well I think i could break up the tests
[17:43] <santa_> calling the cmake thing to execute the one needing network, and another one to call the remaining tests
[17:43] <santa_> I would need to dig into that
[17:43] <nacc><EMAIL_ADDRESS>seems to imply docker.io is going to the network for something ("Pulling from library/hello-world")?
[17:43] <santa_> I have the impression it would be possible with enough time
[17:44] <santa_> nacc: indeed
[17:45] <apw> i suspect those have complex proxy management in them to make it work
[17:45] <apw> as i believe all arches are network capable but needing proxy
[17:46] <nacc> apw: ah good point
[17:46] <nacc> santa_: yeah, i'd look at what docker.io actually has to do to make it work
[17:48] <santa_> ok, I will try to dig into this if I have time
[17:48] <santa_> apw, nacc: thank you very much for the info :)
[18:43] -queuebot:#ubuntu-release- New: rejected snapd-glib [amd64] (zesty-proposed) [1.5-0ubuntu1]
[18:43] -queuebot:#ubuntu-release- New: rejected snapd-glib [s390x] (zesty-proposed) [1.5-0ubuntu1]
[18:43] -queuebot:#ubuntu-release- New: rejected snapd-glib [arm64] (zesty-proposed) [1.5-0ubuntu1]
[19:10] -queuebot:#ubuntu-release- New: accepted snapd-glib [amd64] (zesty-proposed) [1.6-0ubuntu1]
[19:10] -queuebot:#ubuntu-release- New: accepted snapd-glib [armhf] (zesty-proposed) [1.6-0ubuntu1]
[19:10] -queuebot:#ubuntu-release- New: accepted snapd-glib [powerpc] (zesty-proposed) [1.6-0ubuntu1]
[19:10] -queuebot:#ubuntu-release- New: accepted snapd-glib [s390x] (zesty-proposed) [1.6-0ubuntu1]
[19:10] -queuebot:#ubuntu-release- New: accepted snapd-glib [arm64] (zesty-proposed) [1.6-0ubuntu1]
[19:10] -queuebot:#ubuntu-release- New: accepted snapd-glib [ppc64el] (zesty-proposed) [1.6-0ubuntu1]
[19:10] -queuebot:#ubuntu-release- New: accepted snapd-glib [i386] (zesty-proposed) [1.6-0ubuntu1]
[19:27] <cyphermox> fossfreedom_: why does budgie-wm need to be run with --replace for ubiquity-dm? Seems wrong and likely to look bad (ie. you need this if some other WM starts, and in that case, you'll see some flickering as the first wm dies and budgie-wm starts; it looks clunky)
[20:04] -queuebot:#ubuntu-release- Unapproved: flash-kernel (xenial-proposed/main) [3.0~rc.4ubuntu62.1.1 => 3.0~rc.4ubuntu62.2] (core)
[21:25] -queuebot:#ubuntu-release- New sync: linux-hwe (xenial-proposed/primary) [4.8.0-35.40~16.04.1]
[21:26] -queuebot:#ubuntu-release- New: accepted linux-hwe [sync] (xenial-proposed) [4.8.0-35.40~16.04.1]
[21:28] -queuebot:#ubuntu-release- New sync: linux-signed-hwe (xenial-proposed/primary) [4.8.0-35.40~16.04.1]
[21:38] <apw> infinity, the meta is in unstable
[21:51] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [sync] (xenial-proposed) [4.8.0-35.40~16.04.1]
[22:01] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.8.0-35.40~16.04.1] (no packageset)
[22:05] -queuebot:#ubuntu-release- New sync: linux-meta-hwe (xenial-proposed/primary) [<IP_ADDRESS>.7]
[22:06] -queuebot:#ubuntu-release- New: accepted linux-meta-hwe [sync] (xenial-proposed) [<IP_ADDRESS>.7]
[22:06] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.8.0-35.40~16.04.1]
[22:50] -queuebot:#ubuntu-release- Unapproved: bind9 (trusty-proposed/main) [1:9.9.5.dfsg-3ubuntu0.11 => 1:9.9.5.dfsg-3ubuntu0.12] (core)
[22:52] <lamont> tbf, ^^ the bind9 SRU was targeted at trusty-updates 4 march 2016.  /me is slow sometimes.
[23:08] <infinity> lamont: Well, to be fair, you are really, really, really old, so we expect things to sometimes slip your mind.
[23:08] <infinity> (Did I miss a "really"?)
[23:09] <lamont> I'm not old yet.  old is totally in the mind.  and I had other things on my mind that month.
[23:09] <lamont> :p
[23:09] <infinity> s/month/year/
[23:09] <lamont> infinity: does that mean you'll let it into proposed to percolate. :p
[23:10] <lamont> I'd offer to hug you, but I'm not sure which behavior that would incent.
[23:10] <lamont> doko: ever feel like you walked into the middle of a very awkward conversation?
[23:11] <infinity> You can hug doko, it's cool.
[23:12] <lamont> lol
[23:15] -queuebot:#ubuntu-release- Unapproved: accepted bind9 [source] (trusty-proposed) [1:9.9.5.dfsg-3ubuntu0.12]
[23:32] <lamont> ta