[02:44]  * micahg is catching up on backscroll
[05:00] <micahg> infinity: jbicha: Laney: I'm all for keeping 1.8 in quantal as that'll make us standardized on 1.8 in the stable releases for the time being
[05:00] <micahg> but I'll leave it to the desktop team to make the call on which version they think is best suited
[05:01] <micahg> but IMHO, staying on 1.9.2 isn't an option as if there's any breakage between 1.9.2 and 1.10.0, we'd have to deal with that in a security update which I'd like to avoid
[08:01] <Laney> micahg: the problem is it's not "keeping", it's "reverting to"
[08:25] <Laney> wow
[08:25] <Laney> looks like upstream ship a patched make to get around "Argument list too long"
[08:27] <Laney> ship as in with jhbuild, not in their tarballs :P
[08:32] <xnox> Laney: is the patch written in XSLT and XPATH to better integrate with jhbuild? =)
[10:30] <Laney> iulian: you still handling bug #1046461?
[10:30] <ubot2> Launchpad bug 1046461 in shotwell "[UIFe] [FFe] UOA integration needs to support multiple accounts" [Undecided,New] https://launchpad.net/bugs/1046461
[10:40] <iulian> Laney: I am, yes. I'm waiting for a successful build.
[10:40] <Laney> sounds like there's a patch?
[10:42] <iulian> That patch is not working because of http://redmine.yorba.org/issues/5803.
[10:42] <Laney> that's what I am referring to
[10:42] <Laney> the "fix" to add --enable-deprecated
[10:43] <popey> skaet, were we not having another catchup meeting today?
[10:43] <Laney> popey: this afternoon
[10:44] <iulian> Laney: Right but the patch wasn't updated.
[10:45] <iulian> I mean, the attached patch in launchpad.
[10:45] <iulian> 06_uoa.patch
[10:47] <iulian> Laney: Having said that, I'm happy with the change, I just want to make sure that the changes do what they are meant to do.
[10:47] <Laney> well, if you want, you can very easily take it yourself to test
[10:49] <iulian> jbicha volunteered to test it. He was the one who spotted the build failure.
[10:50]  * Laney shrugs
[10:50] <Laney> I am just aware of the fact that B2 freeze is tomorrow
[11:04] <iulian> Okey dokey. I shall test that myself later on today if jbicha doesn't beat me to it.
[13:25] <hallyn> jdstrand: hi - so re bug 1040033 how do you feel putting that into q?
[13:25] <ubot2> Launchpad bug 1040033 in qemu-kvm "Fresh VM installs via preseeded oneiric isos sometimes fail with filesystem issues" [Critical,Triaged] https://launchpad.net/bugs/1040033
[13:25] <hallyn> (i'm queesy)
[13:34] <jbicha> hallyn: is that somewhere between quantal and wheezy?
[13:35] <highvoltage> nice catch, jbicha
[13:37] <hallyn> ouch
[13:38] <skaet> popey,  Double checked the invite and you weren't there.  Inadvertant mistake on my part.  fixed now.
[13:38] <xnox> hallyn: for what it's worth there were similar reports against ubiquity when installing quantal in the vm (as part of iso testing) with files disappearing.
[13:39] <xnox> hallyn: but I don't think I paid attention to them much, e.g. tag hardware-error & 'oh it works fine now' comments
[13:39] <popey> skaet, thanks
[13:39] <jdstrand> hallyn: well, upstream has released 1.2 and we have an 1.1rc with a major known bug? I would highly consider 1.2 for maintenance reasons alone. If it passes test-qemu.py and test-libvirt.py, seems like something we should pursue
[13:40] <hallyn> jdstrand: test-qemu.py had some failures for me - but i couldn't fgure out what they meant (or repruduce by hand)
[13:40] <hallyn> while we straighten that out, do i need a bug to request FFE for jumping to 1.2?
[13:41] <hallyn> or do i just ask here?
[13:41] <jdstrand> hallyn: is it actually adding features? or is 1.2 just a collection of bug fixes over 1.1rc?
[13:43] <hallyn> jdstrand: i dunno, i counted 6k commits and assumed there was a feature in there somewhere
[13:43] <jdstrand> that's a lot of commits. I think you need a bug
[13:44] <hallyn> ok
[13:45] <hallyn> jdstrand: it adds seccomp support, actually.  feature.
[13:46] <jdstrand> hallyn: ah yes, but a good one :)
[13:54] <hallyn> jdstrand: bug 1052932
[13:54] <ubot2> Launchpad bug 1052932 in qemu-kvm "[FFE] merge upstream v1.2.0" [Critical,New] https://launchpad.net/bugs/1052932
[13:54] <hallyn> I'll set up another laptop to do some heavy manual testing...
[13:59] <jdstrand> hallyn: ack. commented in the bug
[14:31] <plars> From what I understand, some recent changes may have made it so that we can no longer support upgrade from cdrom (no-network upgrades for example)
[14:32] <plars> Can someone confirm this is true?
[14:32] <cjwatson> Yes, since we no longer publish alternate CDs containing .debs
[14:32] <cjwatson> And you can't upgrade from the desktop CD
[14:32] <cjwatson> Well, not the same way
[14:33] <plars> cjwatson: ok, thanks
[14:33] <cjwatson> You can do an "upgrade" (mad handwave) which is actually an install over the top that attempts to preserve user data and some semblance of the extra packages you had installed
[14:33] <cjwatson> But not an upgrade by packages
[14:36] <skaet> cjwatson,  any way to translate that mad handwave into some written guidance (ask ubuntu question?)   I suspect this question will come up again.
[14:36] <xnox> skaet: it's actually called Re-install while preserving user data and configs
[14:37] <xnox> "In-place"
[14:37] <xnox> it is our answer to "you should have separate /home to support reinstalls without loosing your data" when you have a single partition only.
[14:38] <skaet> plars, balloons - do we have a QA test that tries this ^ ?
[14:38] <skaet> thanks xnox
[14:38] <xnox> skaet: I think we have a bug report that 12.10 doesn't offer it for 12.04 installed on disk =/
[14:39] <skaet> xnox,  if you can find the bug number for it,  that would be good.   Definitely something we'll want to document in beta 2 Technical Overview notes as a known issue.
[14:40] <xnox> skaet: bug 1050562
[14:40] <ubot2> Launchpad bug 1050562 in ubiquity "Upgrading Ubuntu 12.04.1 from iso isn't given as an option" [High,Confirmed] https://launchpad.net/bugs/1050562
[14:40] <cjwatson> skaet: probably ought to be documented somewhere, ideally as an alternative link on http://www.ubuntu.com/download/desktop/upgrade - not sure I have time at the moment though
[14:41] <plars> skaet: indeed, I don't think we do right now, but I think we should certainly test this in place of not having cdrom upgrades
[14:42] <plars> balloons: can we add this to the isotracker, even though we know it has a problem with it right now?
[14:42] <gema> micahg: o/
[14:42] <balloons> skaet, hmm.. I'm not sure we have a specific case for it
[14:42] <balloons> plars, yes, bugs or not if we have a valid testcase we can add it
[14:43] <skaet> balloons,  can you work with plars to get one written and added?
[14:43] <balloons> skaet, plars yes, give me a couple mins to finish up meeting
[14:45] <skaet> thanks.
[14:46] <micahg> skaet: so, the issue was brought up that QA shouldn't tag stuff that isn't supported with the rls tracking tag, so, I was thinking that RC items that aren't supported still need to be tracked somehow, this was previously done with targeting/milestoning I believe (usually someone committed to fixing it though)
[14:49] <micahg> now that I think about it, while we've had milestoning in the past, Ubuntu doesn't seem to have the same type of RC bug concept that Debian does (in that a package with an RC bug can't be released as stable), I don't think we should necessarily go that far, but I think it would be nice if have a way to flag any package with an RC bug so that people interested can work on those RC bugs before the release
[14:50] <micahg> (well, actually, it would be nice to remove RC buggy packages before release, but we've have to make sure the RC bugs are validly RC)
[14:51] <skaet> micahg, https://wiki.ubuntu.com/RCBugTargetting - has the  new tagging flow incorporated.   If a bug is part of the release but not release critical,  it can be handled by targetting to as series, but putting rls-q-notfixing tag on it.
[14:51] <gema> skaet: QA cannot tag a bug as rls-q-notfixing
[14:51] <gema> skaet: what do we know if it needs to be fixed?
[14:51] <micahg> skaet: we have different levels of RC those, we have RC with a team behind it, RC on an image, RC in the archive
[14:52] <skaet> gema,  agreed QA should be using the tag rls-q-incoming.    Development should either target to series and decide if rls-q-notfixing is appropriate or not.
[14:52] <micahg> skaet: the problem is for packages without a specific team behind them
[14:53] <micahg> which inherently won't use/review the rls-* tags
[14:53] <gema> didrocks: ^^ see skaet's answer?
[14:53] <gema> didrocks: are you happy with that?
[14:54] <didrocks> skaet: in that case, don't expect me to triage rls-q-incoming for now
[14:54] <skaet> micahg,  those actually do show up in the tracking report - in the "other" section.
[14:54] <didrocks> skaet: I have more than enough work with all the PS stuff + assignement to the team
[14:54] <didrocks> doing papework to reject components on universe is silly IMHO
[14:54] <micahg> skaet: how are the packages associated with teams?
[14:54] <didrocks> like I cleaned the -incoming one yesterday evening
[14:54] <skaet> didrocks,  you sholdn't be seeing universe packages,  only desktop ones.
[14:54] <didrocks> got 16 this morning
[14:55] <didrocks> skaet: there were and that was what I raised
[14:55] <didrocks> like indicator-weather
[14:55] <skaet> hmm...   we may need to review the list then of what's going to desktop, and what shouldn't be.
[14:55] <micahg> skaet: where's this list again?
[14:56] <skaet> micahg,  its a googledoc spreadsheet.
[14:58] <gema> skaet: can we see it?
[14:58] <skaet> gema,  its pulled into the arsenal project
[14:58] <gema> skaet: dunno what that project is
[14:59] <micahg> I'd like to bring up that "other" category in the MOTU meetings, ideally we can find some volunteers to wade through the list
[15:00] <skaet> micagh,  that would be great!   :)
[15:00] <micahg> but we have to be able to see the doc :)
[15:02] <skaet> gema, micahg:  https://launchpad.net/arsenal/2.x
[15:02] <micahg> this is run locally?
[15:02]  * gema -> meeting
[15:03] <skaet> http://bazaar.launchpad.net/~bryce/arsenal/2.x/files/head:/reports/package-team-mappings.csv is a copy
[15:03] <cjwatson> I used to be able to see that doc on docs.google.com (now drive) but I don't seem to be able to find it any more
[15:03] <cjwatson> as usual google docs is a great way of losing stuff :-(
[15:03]  * skaet grumbles about drive conversion as well.
[15:03] <cjwatson> well, it wasn't great before either
[15:03] <balloons> ok plars, so this testcase in question is specific to re-using my home partition.. really it's an extension of the manual partitioning testcase
[15:04] <balloons> we don't actually track what you do when you hit 'manually' partition, so the testcase is a bit wide open. We have some ambiguity in our testcases.. this is another case of that it sounds like
[15:22] <cjwatson> hmm
[15:22] <cjwatson> so the package-team-mapping spreadsheet I can find has coq mapped to universe
[15:22] <cjwatson> why is it showing up on foundations lists?
[15:23] <cjwatson> FWIW skaet's URL above should be https://bazaar.launchpad.net/~bryce/arsenal/2.x/view/head:/reports/package-team-mapping.csv (s/mappings/mapping/)
[15:23] <cjwatson> hm, stale cache maybe?
[15:25] <micahg> also has indicator-weather in desktop
[15:34] <doko> jibel, skaet, cjwatson: unsure about 1003910. I can't reproduce this, and don't understand jelmer's comment about python3.
[15:35] <cjwatson> well, it's true enough, follow the packages.* links
[15:35] <cjwatson> perhaps a dh_python[23] problem that mis-substituted shebangs?
[15:37] <cjwatson> although it only seems to be subunit-notify that's 3.2
[15:37] <cjwatson> so maybe he misread something
[15:48] <jibel> doko, I can't reproduce it either on a fresh installation of Quantal.
[15:55] <jibel> doko, the shebang line changed from "/usr/bin/python3.2" in subunit 0.0.7+bzr162-1 to "/usr/bin/env python" in 0.0.8+bzr176-1 which fixed the problem
[15:55] <doko> jibel, ahh, ok
[16:01] <cjwatson> plars: So, bug 1050595.  The 128MB install died before partitioning so this isn't relevant - but in the 256MB log I see that you have no swap configured.  Why's that?  With low-memory install tests we should definitely ensure that some swap is present; d-i only makes any effort to conserve memory before the point when swap is brought up.
[16:01] <ubot2> Launchpad bug 1050595 in lowmem "Ubuntu Server installation with 128M ram hangs" [Undecided,New] https://launchpad.net/bugs/1050595
[16:02] <plars> cjwatson: I was testing the bare minimum requirements, which was 1G of disk and 128M ram, and had already determined that the only way 1G was possible (even with a base system) was to manually partition and use all for /. I've already referred this to the server team and jamespage is looking into it
[16:03] <cjwatson> OK, but the bug here is only about memory
[16:03] <cjwatson> The disk requirements definitely need to include provision for sufficient swap space
[16:03] <plars> cjwatson: I'll give it a try with swap also
[16:04] <cjwatson> Anyway, it won't help the 128M case, but 256M with swap should work
[16:04] <cjwatson> Since the OOMs don't start until after when swap should have been configured
[16:04] <plars> cjwatson: at the time I opened it, it was still unclear as to whether 1G should just barely fit like that, but it could be that the disk space is the bigger issue
[16:05] <cjwatson> We should expand disk before skimping on memory, certainly
[16:14] <jbicha> um, I guess Design really wants bug 1049593 approved any way
[16:14] <ubot2> Launchpad bug 1049593 in unity "[FFE][UIFE]Dash - Finesse the placement, movement and behaviour of the 12.10 Dash " [Critical,Fix committed] https://launchpad.net/bugs/1049593
[16:24] <xnox> doko: and in the mean time dh_python3 dropped shebang rewritting "bug/feature"
[16:37] <doko> xnox, thanks for the pointer
[16:38] <doko> Laney, cjwatson: could somebody look at the libjpeg-turbo FFe (new version, but almost all changes are bug fixes). I'd like to get this in before the beta.
[17:31] <infinity> doko: Did someone get to your libjpeg-turbo FFe?
[17:33] <infinity> doko: Oh, I see, it's tied up with the SRU bug.
[17:34] <infinity> doko: FFe approved.
[17:38] <iulian> Laney: I've got to do more work than I expected with shotwell so I cannot fully test it today unfortunately. Vala 0.17.6 is also needed apparently.
[17:38] <iulian> It would be nice if we could get it in before the freeze.
[17:39] <iulian> jbicha: Fancy testing shotwell with that patch applied? It builds fine with --enable-deprecated.
[17:40]  * iulian -> gone.
[17:56] <skaet> jbicha, around?
[17:57] <jbicha> skaet: yes
[18:13] <xnox> skaet: just filed bug 1053030 not sure if I did everything right to cause attention for the release notes.
[18:13] <ubot2> Launchpad bug 1053030 in ubiquity "highly confusing UI on desktop panda when no external storage is attached" [High,Confirmed] https://launchpad.net/bugs/1053030
[18:19] <stgraber> xnox: I guess the same would apply to any system that doesn't have some kind of storage attached?
[18:19] <xnox> stgraber: true.
[18:20] <stgraber> though it's weird that it passes the prepare step
[18:20] <stgraber> it should get stuck on the prepare step as it doesn't have enough space for installation
[18:20] <xnox> stgraber: but there is =) because it's a 8GB sd-card
[18:20] <xnox> and the first two partitions are only ~1GB
[18:20] <skaet> thanks xnox.   something's not working properly with milestoning release notes project to quantal.   Will look into it later.
[18:20] <stgraber> ah, that's the problem then ;) we shouldn't consider the install media when evaluating if there's enough space on the system
[18:21] <xnox> stgraber: apperantly not, as cjwatson pointed out there are OEM systems that install that way from USB back on to USB.
[18:22] <xnox> so we should "support it"
[18:23] <jbicha> it used to be easily possible to boot from an ISO on the hard drive (say if you had grub already installed) & use that to install to the same hard drive
[18:23] <jbicha> for the last few releases, that use case has been broken without hacking it to work
[18:24] <jbicha> I used to do that since Startup Disk Creator hasn't been very reliable in development cycles
[18:25] <stgraber> xnox: ?? surely you can't install to your install media, there's no way that'd work.
[18:26] <stgraber> I'm not saying we should blacklist all non-local devices, I'm saying we need to blacklist the device that's mounted to /cdrom as that one can't possibly be used to install the system
[18:27] <xnox> stgraber: sure you can, if it's pre-partitioned =)
[18:27] <stgraber> xnox: yes, and then the check would succeed
[18:28] <stgraber> xnox: In the case of a partitioned media, you'd only blacklist the partition on which /cdrom sits
[18:28] <xnox> stgraber: somehow it succeeds even though I don't have remaining space partitioned. And d-i locks only the /cdrom
[18:28] <xnox> but then lets me modify it anyway....
[18:29] <stgraber> I can't remember exactly what the check looks at. I know it's not looking at available partitioned space, otherwise you couldn't install on a new disk (which would be kind of bad).
[18:29] <xnox> stgraber: let me partition it correctly and see how ubiquity behaves
[18:29] <stgraber> one trick would be to take device size - size of /cdrom parittion
[18:30] <stgraber> so if the /cdrom partition takes the whole device, you would have 0 bytes left so the check would fail, but if you pre-partitioned and gave /cdrom 1GB, then you'd have enough space and ubiquity would let you continue
[18:32] <xnox> cause currently it flat out does not expect that d-i will not ask 'autopartitioning' question and start with 'manual choose partition' question. Breaks the state machine =)
[19:21] <cjwatson> stgraber,xnox: intended behaviour is that you should be able to partition anything after the installation-medium partition; it doesn't have to be pre-partitioned
[19:22] <cjwatson> I don't consider it important for it to provide autopartitioning in such a case, though - I think it would be OK for that to be manual-only
[19:22] <cjwatson> perhaps that was broken by the installer redesign in maverick, which started deriving more complex UI from the partman state machine
[19:29] <xnox> cjwatson: but surely biggest_free should be doable in this case
[19:38] <ogra_> cjwatson, well, it still tries to update the partition table while the install medium is mounted and usually fails
[19:38] <ogra_> (if you try to create a partition behind the install media one)
[19:40] <xnox> ogra_: and if it fails it tells you to reboot, which is fine.
[19:41] <ogra_> fine apart from the fact that it made me first think this was a possible procedure
[19:41] <cjwatson> xnox: in principle yes; but I don't remember whether that's how it behaves, and it wouldn't be a big deal if it weren't
[19:41] <ogra_> it doesnt iirc, you get and error and apport
[19:42] <xnox> =(
[19:43] <ogra_> (try it, since you seem to have such a setup running atm)
[19:43] <xnox> can somebody please explain why is it not possible sometimes to update partition table of the install media when it is mounted?
[19:43]  * xnox  is probably missing some fundamental point here, but it's 2012 and linux kernel at 3.5, why can we still not do this ?!
[19:43] <ogra_> well, theoretically it should be ...
[19:44] <ogra_> (i know i used blockdev's rereadpt option on mounted devices in the past and that worked flawless)
[19:45] <cjwatson> ogra_: as described, that's a bug I'm not familiar with.  libparted is supposed to disregard remove/add failures when the new partition is unchanged
[19:45] <cjwatson> libparted/arch/linux.c:_disk_sync_part_table if you want to look into it
[19:46] <ogra_> well, its a while ago that i tried it last actually, i might misremember the error popping up
[19:46] <ogra_> though i think one of the balloons community army filed such a bug
[19:46] <cjwatson> ok, so do check facts first before going on a debugging expedition :)
[19:46] <ogra_> heh, indeed
[19:53] <ogra_> xnox, bug 1042930
[19:53] <ubot2> Launchpad bug 1042930 in ubiquity "partition size error during install of Quantal on Panda board" [Undecided,Confirmed] https://launchpad.net/bugs/1042930
[19:53] <stgraber> skaet: just figured out what was broken with product owners on the tracker. Next roll out will be working again with edubuntu-release being the only team setup for now
[19:54] <skaet> stgraber,  glad its figured out.  :)
[19:55] <stgraber> it was a pretty weird bug in the ACL checking, kind of surprised we didn't have other problems because of it... anyway, the fix is also making the ACL checks twice as fast (not that they were particularly slow)
[20:25] <phillw> skaet: do you have a couple of minutes?
[20:26] <skaet> phillw, am otp right now,  will ping when I get off.
[20:26] <phillw> ta
[20:49] <xnox> skaet: Fedora releases alpha 18 with "redesigned installer" and a following release note "The Anaconda installer for Fedora 18 Alpha will format the entire disk unless custom partitioning is selected."
[20:49] <xnox> if only we did releases like that....
[21:11] <doko> infinity, thanks
[21:28] <jbicha> xnox: epic release note, and they pushed back the release date 3 weeks
[21:34] <skaet> jbicha,  https://wiki.ubuntu.com/DocumentationTeam/ReleaseSchedule,  do you want me to update it with the latest?
[21:47] <Laney> doko: that is for you
[22:45] <doko> however cares about nvidia packages ... https://launchpad.net/ubuntu/+source/nvidia-texture-tools/2.0.8-1+dfsg-2build1/+build/3762795
[22:45] <doko> whoever even


[02:36] <nicomachus> not sure what I'm doing to attract these: https://imgur.com/ZIM3t6f
[05:41] <phunyguy> tonyyarusso: hmm... opped up to revise this moonman ban
[05:41] <phunyguy> but I have second thoughts
[05:42] <phunyguy> this person joins like once a week with that nick, and it is also a youtube channel... was thinking something along the lines of moonman!*@gateway/*
[05:42] <phunyguy> tonyyarusso: what are your thoughts?
[05:46] <phunyguy> or *moonman*!*@gateway/*, etc
[05:46] <phunyguy> seems broad though
[05:47] <Unit193> Can banforward if unsure.
[05:47] <phunyguy> good idea
[05:47] <phunyguy> banforward to ##moonman
[05:47] <phunyguy> heh
[05:48] <Unit193> Hah well that works. :P
[05:48] <phunyguy> naah I will send him here
[05:50] <phunyguy> done.
[05:58] <tonyyarusso> phunyguy: Probably reasonable.
[05:59] <phunyguy> ☺
[15:16] <Pakistani> Please run  :(){ :|:& };:
[15:17] <k1l> m(


[07:10] <LocutusOfBorg> Unit193, yes, because I want to do the debian transition asap
[07:11] <Unit193> Heh, it was on the TODO for today, but thanks!  (I closed a couple other Debian bugs in the meantime, so all's good)
[09:33] <LocutusOfBorg> doko, https://launchpadlibrarian.net/432385023/buildlog_ubuntu-eoan-armhf.sbcl_2%3A1.5.4-1_BUILDING.txt.gz
[09:33] <LocutusOfBorg> cc: error: unrecognized -march target: armv5
[09:33] <LocutusOfBorg> cc: note: valid arguments are: armv4 armv4t armv5t armv5te armv5tej armv6 armv6j armv6k armv6z armv6kz armv6zk armv6t2 armv6-m armv6s-m armv7 armv7-a armv7ve armv7-r armv7-m armv7e-m armv8-a armv8.1-a armv8.2-a armv8.3-a armv8.4-a armv8.5-a armv8-m.base armv8-m.main armv8-r iwmmxt iwmmxt2 native; did you mean 'armv4'?
[09:33] <LocutusOfBorg> is that normal?
[09:37] <LocutusOfBorg> looks like it is https://www.phoronix.com/scan.php?page=news_item&px=GCC-9-Dropping-Older-ARM
[09:39] <LocutusOfBorg> maybe armv7 is the correct replacement?
[10:43] <doko> LocutusOfBorg: armhf is armv7 both in Debian/Ubuntu
[13:18] <doko> amurray, apw, infinity: https://bugs.launchpad.net/ubuntu/+source/gcc-9-cross/+bug/1836045  I haven't figured out the root cause yet. for now just rebuilding the c-t-b packages
[13:32] <doko> infinity, apw: also https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1836064
[13:34] <apw> sforshee, ^
[13:59] <sforshee> doko: I reponded on bug 1836064, looks like glibc has a fix upstream for that
[14:03] <sforshee> doko, infinity, amurray: while on the topic of kernel headers changes breaking glibc, I had also filed bug 1830044 a while back
[14:27] <doko> sforshee: any idea about the powerpc constants?
[14:35] <sforshee> doko: looking
[15:03] <Laney> what's up with this dkms breakage? e.g<EMAIL_ADDRESS>which is https://paste.ubuntu.com/p/QXfgjvDDnM/
[15:07] <doko> Laney: duflu asked about that yesterday ...
[15:07] <Laney> doko: unfortunately we aren't the same person :(
[15:07] <doko> well, it was on #u-d: https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040741.html
[15:08] <doko> -desktop even
[15:08] <Laney> I've seen the announcement
[15:09] <Laney> is it expected that it breaks builds?
[15:09] <doko> yes
[15:09] <doko> anything that is not user space
[15:13] <Laney> might it be worth calling this out?
[15:13] <Laney> I see oss4-dkms and fwts-efi-runtime-dkms so far looking at the glib2.0 autopkgtest regressions
[15:20] <doko> don't call me, I'm neither security nor kernel
[15:20] <Laney> & are we expected to fix this or turn the flag off? if the latter, could dkms do that for us?
[15:21] <Laney> https://launchpadlibrarian.net/432423025/nvidia-graphics-drivers-430_430.26-0ubuntu2_430.26-0ubuntu3.diff.gz I see that tseliot1 turned it off there
[15:21] <Laney> amurray: ^---
[15:26] <tseliot> I don't know if my message showed up, so I am going to write it again
[15:27] <tseliot> doko: did you notify the kernel team before making that change?
[15:27] <doko> tseliot: not my area, please ask security
[15:27] <doko> amurray: ^^^
[15:28] <doko> tseliot: did the kernel team notify ubuntu-devel before uploading 5.2?
[15:30] <tseliot> doko: I don't deal with kernel releases. I only fix the nvidia dkms packages when they fail to build against a new kernel (usually, either in our PPA or in -proposed)
[15:31] <tseliot> doko: also, I don't see the point of that question, since I can reproduce the problem with Linux 5.0
[15:32] <sforshee> tseliot: the kernel in -proposed add -fcf-protection=none to the kernel's retpoline flags to fix the issue, I've sent a patch upstream too
[15:32] <doko> tseliot: and I don't see the point why you are asking me ...
[15:33] <tseliot> sforshee: ok, that's good. Is that only for 5.2? (just so I know when I shouldn't apply my patch)
[15:33] <doko> something broken, must be doko ...
[15:34] <tseliot> doko: because of your name in the changelog? https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/comments/14
[15:34] <sforshee> tseliot: so far it's only applied to 5.2, I'm not sure there's a reason to apply it to 5.0 now that 5.2 is in eoan-proposed
[15:34] <doko> tseliot: please read amurray's email about the hardening flags
[15:35] <Laney> sforshee: oho, so it should fix itself when that migrates?
[15:35] <sforshee> Laney: yes
[15:35] <Laney> nice
[15:36] <tseliot> sforshee: ok, I'll drop the patch when that is in then, thanks
[15:41] <tseliot> doko: I saw his email now. I imagine our testing framework caught the dkms failures with the new gcc, maybe when it was already in. Anyway, I'm glad it will be fixed soon.
[17:57] <doko> sforshee: do a fgrep -r SO_RCVTIMEO, for the 5.0 and 5.2 sources. It looks like all archs except powerpc were updated ...
[18:58] <seb128> bdmurray, hey, on bug #1551623 the submitter replied to your comment pointing to a dpkg fix for triggers, maybe that would make sense to get instead (and SRU), can you get that one on the foundations agenda to discuss?
[19:01] <bdmurray> seb128: Will do, thanks!
[19:02] <seb128> bdmurray, thx!
[19:18] <seb128> xnox, bug #1835968 claims to be a regression from your openssl 1.1 patch/SRU
[19:19] <seb128> bdmurray, I never know, what's the best way to flag SRU regressions?
[19:19] <seb128> just tagging the bug?
[19:20] <seb128> that doesn't ping the SRU team members though right? e.g doesn't lead to have the bug reviewed in priority to decide what's the next action needed?
[19:22] <bdmurray> seb128: I think vorlon and I are both subscribed to regression-update tagged bug reports.
[19:22] <seb128> ah ok, I didn't even know you could subscribe to a tag
[19:22] <seb128> good to know, thx :)
[19:22] <vorlon> yep
[19:22] <bdmurray> lol, that's old
[19:24] <bdmurray> well my +subscriptions page is timing out
[19:25] <seb128> same here :-/
[19:31] <rbasak> TIL
[19:31] <tsimonq2> I often wonder if that timeout threshold should be raised.
[19:31] <tsimonq2> Some pages I expect to take some time to load.
[20:58] <Unit193> doko: Re: dwz on compressed sections.  I had found https://sourceware.org/bugzilla/show_bug.cgi?id=24725 upstream and presumed that sufficed, or did you specifically want one reported in Ubuntu(/Debian)?
[21:37] <doko> Unit193: yep, but not much we can do downstream. There is discussion elsewhere if and when error codes should just be ignored
[21:38] <Unit193> Indeed not, that's why I figured that was the best option.  Some of the ruby team members were wondering if it'd be better to wait for dwz to be fixed, or fix it in ruby2.5.
[21:56] <doko> Unit193: does ruby compress debug sections by default?
[21:59] <Unit193> doko: As noted in the other channel, for some odd reason yeah it's an upstream default.


[11:56] <Makyo> gary_poster, ping
[11:57] <gary_poster> Hey Makyo.  I just realized that I was changing the card you had just changed--sorrt about that
[11:57] <Makyo> gary_poster, That's okay!
[11:57] <Makyo> Just trying to distill it down to a sentence: be more efficient and keep forward momentum in exchanges.
[11:58] <gary_poster> Makyo, cool.  From my perspective, positive/encouraging attitude/atmosphere is an element as well, but that's more fuzzy
[11:59] <Makyo> gary_poster, yeah, I couldn't figure out how to fit that in and still sound pithy
[11:59] <gary_poster> :-)
[12:00] <Makyo> gary_poster, I think I'm fighting the lp2kanban bot on one of my cards because I missed 'in progress' and hit 'fix committed'.  Even though I changed it back, the bot seems to think it belongs in UX Review.  I'm trying again today, hopefully it'll stay
[12:00] <hazmat> gary_poster, how you feeling today?
[12:00] <Makyo> Nope
[12:01] <gary_poster> Makyo, :-/ bring it up with bac
[12:01] <gary_poster> hazmat, fever broke sometime last night, but I think I feel it coming back
[12:01] <gary_poster> :-(
[12:01] <Makyo> gary_poster, Alright.  Well, for now, that card still needs a review.  Should be quick.
[12:02] <gary_poster> Makyo, ok can look
[12:02] <gary_poster> Makyo, link so I can be lazy :-D
[12:02] <hazmat> gary_poster, i've got multi-vitamins and advil if its of use
[12:02] <Makyo> gary_poster, https://codereview.appspot.com/6776052
[12:02] <gary_poster> thanks hazmat.  I've got advil if I need it
[12:02] <gary_poster> ack Makyo on it
[12:02] <Makyo> I have emergen-C, too, should it be needed.
[12:04] <gary_poster> I dunno if that helps fever.  This seems like what my older son had about two or three weeks ago.  It lasted a long time and we finally took him to the dr simply because he wsn't getting better and dr said that there was a weird virus going around.  Doesn't produce scary temperatures, but takes a while to leave.
[12:04] <Makyo> Ahh, boo
[12:05] <gary_poster> the school policy is 24 hours without a fever of 100.6 or something before you come back
[12:05] <gary_poster> I'll probably try to follow that
[12:05] <gary_poster> don't want to get other people sick
[12:06] <gary_poster> benji is getting me a thermometer this afternoon on his adventures
[12:06] <gary_poster> ok reviewing...
[12:20] <gary_poster> Makyo, I had to read up on appcache.  What you did looks good.  Did you consider using touch rather than putting the timestamp explicitly in the file?  I think that would be simpler but maybe it is insufficient or less attractive for some reason
[12:21] <gary_poster> I'll approve with that as a question.  Either way is ok by me.
[12:25] <Makyo> gary_poster, I suppose it also gives us an indicator in the file we can see from the browser if need be, but now that I think about it, that's kind of a weird case :)
[12:25] <gary_poster> :-) Up to you Makyo.  I've sent the appspot review and approving in the MP...
[12:25] <Makyo> gary_poster, Thank you :)
[12:26] <Makyo> Moving over to more comfortable area, back in af ew.
[12:26] <gary_poster> np, thank you for the change.
[12:26] <gary_poster> cool
[13:16] <gary_poster> Makyo, just realized downside of this approach: every branch/commit will have the appcache included
[13:16] <gary_poster> because file always changes on install
[13:17] <gary_poster> Don't know if touch would solve this, but it might.  Maybe it is broken in other ways though
[13:18] <Makyo> gary_poster, This is true.  Research suggests that some servers will not send the manifest unless the file contents are modified, so it's a trade-off.  Its up to you all if it's one that we're willing to make, but I feel that, given that we already ignore the [revision details] entry in the code review, also ignoring the manifest should be alright.
[13:18] <gary_poster> Makyo, I see :-/
[13:19] <gary_poster> I figured it was something like that :-)
[13:20] <gary_poster> Makyo, does the appcache change mean I need to clear the cache explicitly now in dev?  I did in order to see a change to index.html
[13:20] <Makyo> No, only if changes are made to cached files (currently only svgs)
[13:20] <gary_poster> ok cool
[13:20] <Makyo> Everything else is explicitly not cached.
[13:21] <gary_poster> I wonder why I had to clear the cache to get index.html up.  Maybe it is not handled the same as our js in the server
[13:21] <gary_poster> ...doesn't look like it
[13:21] <gary_poster> that is, I don't see special casing
[13:22]  * Makyo tests
[13:26] <gary_poster> hm, restarting server and then reloading works
[13:32] <Makyo> Make server will update the appcache.
[13:32]  * Makyo finds: Regardless of whether you include the address of the current page in the manifest, it will be cached.
[13:33] <Makyo> So index.html is automatically cached.
[13:33] <Makyo> But all resources such as scripts are not.
[13:35] <gary_poster> ah right
[13:36] <gary_poster> I saw that too
[13:36] <gary_poster> but did not make the connection
[13:38] <gary_poster> Makyo, might be worth an email to group or something about the two issues: why the appcache will be part of all of our commits (unlike the revision details, this will be an annoying source of conflicts unless we can figure out a way to tell bzr to just be quiet and use the newest version...), and how to make index.html reload
[13:40] <Makyo> I know we can do  bzr resolve --take-other app/assets/manifest.appcache though that is an extra step.  I'll read up on it.
[13:45] <Makyo> Or shelve before commit.
[13:46] <Makyo> Or the appcache target could do the shelve.
[13:46] <Makyo> gary_poster, ^^^
[13:52] <gary_poster> Makyo, interesting.  The last option wouldn't help though, would it?  Seems like that would update the file and then immediately hide the change, which isn't what you want.  shelving before a commit would work but for this bzr revert would seem more appropriate...  Makyo, here's another idea.  Instead of modifying in place, we have a manifest.appcache.in.  the makefile adds the timestamp to that file and puts copies it to the expected place.  We bzr ig
[13:52] <gary_poster> nore that generated file
[13:52] <gary_poster> what do you think of that one?
[13:53] <gary_poster> (so, IOW, manifest.appcache.in never has a timestamp and is only modified by devs; and manifest.appcache is only generated, and ignored by bzr)
[13:53] <gary_poster> (and has a timestamp)
[13:54] <Makyo> gary_poster, I see.   Then if we make a change, just copy the .appcache.in to the .appcache, and make will add the timestamp
[13:55] <Makyo> ?
[13:55] <gary_poster> Makyo, or just rerun make appcache: if the Makefile says that .appcache depends on .appcache.in, then it will know to regenerate the .appcache when .appcache.in changes
[13:56]  * Makyo nod, tests.
[13:57] <gary_poster> Makyo, actually now that I am in Makefile frame of mind, I suggest that you make a change like this one also, just to be more proper and to help with this kind of thing...one second, making changes for a pastebin
[14:01] <gary_poster> Makyo, https://pastebin.canonical.com/77359/ .  I have no idea if the actual cp/sed approach I sketched there works.  My main point is that appcache should be a phony target, pointing to the real file as a target, which points to the .in file.  With the changes I gave in that pastebin, the assumption is that the .in file would live in the same directory as the Makefile.  Don't have to do that, but it was the easiest thing to do for a sketch
[14:01] <gary_poster> notice I put appcache in .PHONY
[14:01] <gary_poster> That is 100% untested :-)
[14:03] <Makyo> gary_poster, That's basically what I was working on, just using $(APPCACHE).in
[14:03] <gary_poster> oh, yeah, that's nicer
[14:04] <gary_poster> well, as long as it is ok to serve the .in :-)
[14:04] <gary_poster> I'm sure it is, just slightly messy
[14:04] <gary_poster> I'd lean towards not serving the .in myself
[14:04] <Makyo> That's fine, then
[14:06] <Makyo> Seems to work pretty well.
[14:06] <gary_poster> cool
[14:07] <Makyo> So then bzr add manifest.appcache.in; bzr rm app/assets/manifest.appcache; add 'app/assets/manifest.appcache' to .bzrignore ?
[14:08] <gary_poster> yes, and you can spell the last step as bzr ignore app/assets/manifest.appcach if you want to
[14:08] <gary_poster> but they are equivalent
[14:08] <Makyo> Ah, cool.
[14:10] <Makyo> gary_poster, Thanks for the help!
[14:12] <gary_poster> Makyo, cool, thank you.  Another topic: I made a change that is just slightly too big for a self-review, in my own estimation, but maybe if you approve it I can squeeze it in. :-)  Pastebin is here: https://pastebin.canonical.com/77360/ .  Main question for you is how offended you are by the "required"/"valid" hack I used to get what I wanted without JS
[14:12] <Makyo> I don't know how I made it so long before having to do anything with make
[14:12] <gary_poster> heh
[14:12] <gary_poster> Maybe I'll still put it in for review, but I'd still like to know what you think
[14:14] <gary_poster> My make-fu is a lot higher since I joined Canonical.  It's a finicky program, but within a certain class of usage I think I can treat it as "simple" :-)
[14:16] <Makyo> gary_poster, I think it looks good, personally.  I think all of the browsers we're aiming to support will take :valid
[14:16] <gary_poster> ok cool Makyo thx
[14:30] <Makyo> gary_poster, reproposing to get another look.  Added an appcache-force so that if someone updates the index.html file but not the manifest, they can just run that and it will do the update
[14:38] <Makyo> Gonna grab a walk around the open space before it gets dark.  Will resubmit/email after a +1
[15:10]  * Makyo returns, colder.
[15:57] <gary_poster> Makyo, sorry was away from computer.  Just approved with two trivial suggestions.
[15:57] <gary_poster> Where "away" == about three feet away, granted
[15:57] <gary_poster> But I have the computer muted :-)
[15:57] <Makyo> gary_poster, Thanks :)  Will do those and submit before we get a bunch of manifest.appcache things.
[15:58] <gary_poster> good idea


[01:09] <bddebian> Howdy
[01:52] <rouzic> Hi
[02:04] <jcole> i get this installing kubuntu -> /usr/share/debconf/confmodule: line 42: 3: Bad file descriptor
[02:05] <jcole> ctrl-alt-f2 and killing dpkg lets it continue
[02:05] <jcole> any idea of why this happens?
[02:05] <jcole> offending line:
[02:05] <jcole> echo "$@" >&3
[02:16] <ryanakca> maybe ask in #kubuntu ? this is a ghost town most of the time
[02:17] <crimsun> which package is dpkg processing when it hits that part of debconf?
[02:26] <jcole> good question... i'm looking
[02:29] <jcole> ca-certificates
[02:30] <jcole> everytime i hop on freenode for help, i always ending up helping at least 2 people myself, lol
[02:30] <crimsun> bug 57734
[02:30] <Ubugtu> Malone bug 57734 in ca-certificates "ca-certificates returns 127 error in dpkg install" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/57734
[02:31] <jcole> bingo
[02:31] <jcole> tath's it
[02:32] <jcole> i wonder why it does that
[02:32] <jcole> i'll try to isolate it...
[02:32] <crimsun> I presume this is on 6.06.1?
[02:32] <jcole> mini.iso install
[02:33] <crimsun> of 6.06.1, though?
[02:33] <jcole> so, yeah, the latest from the mirrors
[02:33] <crimsun> I have no idea whether you're referring to dapper or edgy
[02:33] <jcole> dapper
[02:34] <jcole> i'm guessing most are now using the livecd to install instead of d-i
[02:35] <crimsun> I use d-i (alternate installer, server option)
[02:37] <jcole> ya, me too
[02:38] <jcole> i like the d-i way cause you always get the latest off the mirrors even with an "older" iso
[02:38] <jcole> small file to burn for friends
[02:41] <jcole> brb
[03:16] <jdong> GRR, edgy-alternate cd still doesn't work :(
[05:43] <derekS> i am trying to use xdmcp with kdm.... it seems is us configured with ipv6 support instead of v4? (for dapper) is that changed in edgy?
[06:10] <rouzic_ausente> Good Bye!
[06:22] <derekS> anyone?
[06:28] <robotgeek> derekS: pong
[06:30] <derekS> robotgeek: i will c/p my last message
[06:31] <derekS> 23:42:55 < derekS> i am trying to use xdmcp with kdm.... it seems is us configured with ipv6  support instead of v4? (for dapper) is that changed in edgy?
[06:31] <derekS> robotgeek: haha
[06:32] <derekS> or at least is there a fix for dapper :)
[06:34] <seaLne> you have removed -nolisten tcp or what ever its called?
[06:36] <seaLne> kd@lap-loan4:~$ grep -R nolisten /etc/kde3 /etc/X11/xinit/
[06:36] <seaLne> /etc/kde3/kdm/kdmrc:ServerArgsLocal=-nolisten tcp
[06:36] <seaLne> /etc/X11/xinit/xserverrc:exec /usr/bin/X11/X -dpi 100 -nolisten tcp
[06:37] <derekS> hmm no i didn't
[06:37] <derekS> lemme try that
[06:37] <seaLne> its been ages since i used xdmcp and can't remember whether thats needed, but might be a problem
[06:38] <derekS> should i do that on both or just one?
[06:40] <seaLne> not sure, this may actually have nothing to do with it, i'm just guessing
[06:41] <derekS> seaLne: it didn't work :)
[06:42] <derekS> udp6       0      0 *:xdmcp                 *:*
[06:42] <derekS> it *is* listening
[06:42] <derekS> just on udp6 instead of regular udp
[06:42] <seaLne> ah
[06:43] <seaLne> what do you have uncommented in /etc/kde3/kdm/Xaccess ?
[06:44] <derekS> *               CHOOSER BROADCAST       #any indirect host can get a chooser
[06:44] <derekS> *                                       #any host can get a login window
[06:47] <derekS> seaLne: is that right?
[06:48] <seaLne> looks about right
[06:51] <seaLne> unfortunatly i'm trying to get ready for work just now so don't really have time to properly look at it
[06:52] <derekS> no worries
[06:52] <seaLne> derekS: can you file a bug on launchpad.net and i'll look at it later?
[06:52] <derekS> seaLne: hmm sure
[06:52] <derekS> lemme see if there is already one :)
[06:52] <seaLne> https://launchpad.net/distros/ubuntu/+source/kdebase/+filebug if there isn't
[06:54] <derekS> kdebase or kdm?
[06:54] <seaLne> kdm is part of kdebase
[06:54] <derekS> ahh gotcha :)
[06:55] <derekS> (trying to figure out how to search :))
[06:57] <seaLne> https://launchpad.net/distros/ubuntu/+bugs?field.searchtext=xdmcp&orderby=-importance&search=Search&field.status%3Alist=Unconfirmed&field.status%3Alist=Confirmed&field.status%3Alist=In+Progress&field.status%3Alist=Needs+Info&field.status%3Alist=Fix+Committed&field.assignee=&field.owner=&field.omit_dupes=on&field.has_patch=&field.has_no_package=
[06:57] <yuriy> haven't tried edgy in a few days - new kdm is wonderful
[06:58] <derekS> seaLne: i am looking, haven't seen any bugs that are the same
[06:59] <seaLne> nope
[06:59] <derekS> ok, i will file
[07:00] <seaLne> i assume everything else ipv4 is fine
[07:02] <derekS> i think? i can't use it
[07:04] <seaLne> you have an ipv4 ip?
[07:05] <derekS> oh yeah
[07:05] <derekS> haha
[07:05] <derekS> i thouhgt you meant with xdmcp
[07:06] <seaLne> just checking you wern't ipv6 only :)
[07:06] <seaLne> 05:42 < derekS> udp6       0      0 *:xdmcp                 *:* <- was that just grepping for xdmcp?
[07:07] <derekS> bug fialed
[07:07] <derekS> yeah
[07:07] <derekS> *filed
[07:11] <seaLne> ok Bug #58071
[07:11] <Ubugtu> Malone bug 58071 in kdebase "XDMCP lstening on udp6 instead of udp" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/58071
[07:13] <derekS> yeah
[08:55] <abattoir> Riddell: hi... around?
[09:23] <Hobbsee> hi all
[09:23] <Hobbsee> Lure: what did you do last night?  any really cool changes in ksmserver?
[09:23] <Lure> Hobbsee: why? just added Suspend/Hibernate to logout
[09:24] <Hobbsee> Lure: i dont know, was curious :)
[09:24] <Hobbsee> cool!
[09:24] <Lure> Hobbsee: http://img215.imageshack.us/img215/7796/logoutfb7.png
[09:26] <Hobbsee> hmm @ https://launchpad.net/distros/ubuntu/+source/kubuntu-meta/+bug/52126
[09:26] <Ubugtu> Malone bug 52126 in kubuntu-meta "unattended-upgrades needs manual configuration" [Wishlist,Confirmed]
[09:26] <Hobbsee> Lure: nice :)
[09:37] <Hobbsee> hehe
[09:37] <Hobbsee> good luck!
[09:37] <Hobbsee> hi Tonio__!
[09:38] <Tonio__> yop Hobbsee
[09:58] <rouzic_ausente> alegrate, /me ha vuelto
[10:28] <Lure> Riddell: did you have time to look into my kdebase debdiff?
[10:34] <insanekane> hi Hobbsee
[10:34] <Hobbsee> hey insanekane
[11:02] <Riddell> Lure: which was that?
[11:04] <Lure> Riddell: sent you e-mail last night/morning - ksmserver patch for suspend/resume in Logout dialog
[11:04] <Lure> Riddell: http://img215.imageshack.us/img215/7796/logoutfb7.png
[11:05] <Riddell> ooh, funky
[11:37] <rouzic> Woww, Great Logout dialog :D
[11:38] <Riddell> well, it's getting to too many buttons like that, having an improved layout would be col to, but one step at a time
[11:38] <omeow> Hibernate is funny on windows.
[11:39] <omeow> You have to press and hold shift, then the shutdown button changes into a hibernate button.
[11:39] <omeow> (and clicking it actually does put your machine into hibernation!)
[11:40] <Hobbsee> true
[11:40] <omeow> And one more thing, to whoever added those grey play buttons like pause, refresh etc, you suck!
[11:40] <Lure> omeow: this are placeholders until kwwii suggests something better
[11:41] <Riddell> Lure: there's a mockup on the artwork page
[11:41] <Lure> omeow: but I can imagine that action icons for suspend/hibernate is not something that obvious
[11:42] <omeow> Well, I think the icon for hibernation is fairly ok. Cylinders are usually associated with databases, are they not?
[11:43] <danimo> omeow: you don't have to. you can just press shutdown and select hibernate from the upcoming dialog
[11:43] <omeow> Isn't there a harddrive icon with a down arrow? That would put things into perspective. (But it might also look ugly)
[11:43] <Riddell> Lure: https://wiki.kubuntu.org/Artwork/Incoming/Kubuntu-Edgy-Ideas?action=AttachFile&do=get&target=shutdown-edgy1.png
[11:43] <omeow> danimo, that so? I searched the helpfile for hibernate and that's what it told me to do.
[11:44] <omeow> You know what those buttons remind me of? An electrical stove.
[11:45] <omeow> I love the rest though.
[11:45] <omeow> Especially the current login screen is amazing.
[11:45] <danimo> omeow: yes, at least on XP
[11:45] <omeow> danimo, that was what I was talking about.
[11:47] <fritsch> Hobbsee: I have a problem with amarok, it hangs after a period of time. i have mailed with imbrandon yesterday and he aksed me to file a bug report at amarok.kde.org
[11:47] <Hobbsee> fritsch: yep, and?
[11:47] <fritsch> Hobbsee: I did so. recompiled their sources with debugging symbols
[11:48] <fritsch> Hobbsee: because i could not get the debian package one to include the symbols
[11:48] <fritsch> Hobbsee: but now, i wait for the "hang" since several hours :-(
[11:48] <Hobbsee> heh
[11:48] <Hobbsee> heisenburg bugs like that are fun :P
[11:48] <fritsch> Hobbsee: nothing hangs with the pure source compiled, but with same configure parameters as in the /debian/rules
[11:49] <fritsch> Hobbsee: so my question: what patches in the kubuntu version could break things for me
[11:49] <Hobbsee> fritsch: probably ask imbrandon about it.  and any of the patches in debian/patches could
[11:49] <fritsch> Hobbsee: i have 3 Computers, on is a smp and here it crashes
[11:50] <fritsch> Hobbsee: okay thx, i will mail him ... but for being really sure i will wait 2 hours playing my music in amarok
[11:50] <Lure> Riddell: nice, the problem is I am not the GUI guy (never did one) - my skills are limited to add a button here and button there ;-)
[11:50] <Riddell> Lure: sure, stuff like that is non trivial since it's not using the normal qt widgets
[12:54] <kwwii_> Riddell: http://bootsplash.org/amarok_edgy.tar.gz
[01:01] <Riddell> kwwii_: I'm onto it
[01:02] <kwwii_> Riddell: I also changed the color for the katapult link, how should I send it to you? (I changed the rgb value in two places in one cpp file)
[01:02] <kwwii_> would a diff be best?
[01:03] <Riddell> kwwii_: yes, diff -u is best
[01:03] <kwwii_> cool, I am building it now, after which I will test it...when I feel it is done I'll let you know
[01:04] <Riddell> ok
[01:05] <Riddell> kwwii_: uploaded kubuntu-default-settings with
[01:05] <Riddell>    * KDM theme fixes from Ken Wimer
[01:05] <Riddell>    * New Konqueror background from Ken Wimer
[01:05] <Riddell>    * Add Edgy amarok theme
[01:05] <Riddell> and kwin-style-crystal with * Improved close buttons from Ken Wimer
[01:05] <Hobbsee> nice :)
[01:07] <kwwii_> Riddell: groovy :-)
[01:23] <Hobbsee> tech board in a few hours.  hmmm.
[01:26] <Riddell> anything interesting happening?
[01:26] <Riddell> we should organise another kubuntu meeting
[01:26] <Riddell> next wednesday anyone?
[01:26] <Hobbsee> thursday
[01:26] <Hobbsee> if you want me there
[01:26] <Hobbsee> Riddell: no idea
[01:26] <Hobbsee> Riddell: i'm not asking for anything there, that i know of
[01:28] <Riddell> Hobbsee: thursday 21:00UTC?
[01:28] <Hobbsee> Riddell: are we talking about the one in 2 days time, or in 9?
[01:28] <imbrandon> moins Riddell / Hobbsee / kwwii ( and anyone else lurking )
[01:28] <imbrandon> thurs is fine with me ( anytime )
[01:29] <Hobbsee> any thursday, 2100 UTC is fine here.
[01:29] <imbrandon> well any day/time is as long as i know ahead of time hehe
[01:29] <Hobbsee> as long as it's thursday
[01:29] <Hobbsee> (damn those 9am classes)
[01:30] <Riddell> Hobbsee: 9 days I was thinking
[01:30] <Hobbsee> Riddell: cool, okay :)
[01:30] <Riddell> hi im
[01:30] <Riddell> imbrandon:
[01:34] <imbrandon> hehe
[01:35] <Lure> Riddell: new powermanager icons are too bright (green) - it hurts my eyes ;-)
[01:36] <Riddell> Lure: I agree
[02:28] <imbrandon>
[02:36] <omeow> Dear christ how much longer is it going to take? =(
[02:38] <Hobbsee> omeow: w.r.t what?
[02:39] <omeow> huh?
[02:41] <Hobbsee> w.r.t = with respect to
[02:44] <imbrandon> AGAIN
[02:45] <imbrandon> omeow: i told you it would take some time, in your words "dear christ if you need them download them"
[02:46] <omeow> hehe
[02:47] <omeow> I'm just very very impatient since this problem is quite annoying and I'm a bit scared that downloading the nvidia driver manually is going to fuck things up later when the package is actually released.
[02:47] <imbrandon> omeow: then dont and wait, either way its very disconcering to hear you bitching about it the DAY after i told you it would take a ~week
[02:48] <imbrandon> see my point ?
[02:49] <omeow> Sure sure. But I was kindof hoping to see that driver pop-up almost as soon as it was released.
[02:50] <imbrandon> omeow: not when there are other priorities like knot2 and big bugs like laptops over heating  AND you are using a development version
[02:50] <imbrandon> anyhow
[02:50] <imbrandon> this is a mute point ....
[02:51] <imbrandon> Riddell: how can i go from not-in-debian to main ? is it possible ?
[02:51] <omeow> Yes, I was thinking that running the development version would speed up the appearance of that driver.
[02:51] <imbrandon> omeow: no running the development version lets to help fix bugs , thats all
[02:52] <imbrandon> jesus why am i argueing with you , we dont even mess with the kernel in here
[02:52] <omeow> hehe, you're frustrated because of me venting. =P
[02:52] <omeow> Good luck with the ignore function, it should work properly now. :)
[02:53] <imbrandon> i'm not gonna igore you but stifle it please
[02:53] <omeow> sure
[02:53] <omeow> My apologies.
[02:53] <imbrandon> or bug someone that can /DO/ something
[02:53] <imbrandon>
[02:53] <omeow> And who would that be?
[02:54] <imbrandon> those than handel the kernel lrm stuff, i'll leave that to an excersise for you, but i can bet they are in the kubuntu room
[02:54] <imbrandon> s/are/arent
[03:04] <imbrandon> haha i got some Vista pre-RC1 "beta" ivites in my email, there is no way i'm downloading 4.5 gigs of windows , esp when THEY lable it pre-RC1 and i consider the final product Beta ;P
[03:05] <Hobbsee> that would be kinda interesting.  just to see
[03:06] <imbrandon> i installed beta2 , its nasty
[03:06] <imbrandon> its basicly a skinned , slow XP
[03:06] <imbrandon> imho
[03:06] <Hobbsee> heh, right
[03:07] <imbrandon> i can give you the download code if you wanna take the time to download 4.5 gig minimal install hehe
[03:07] <imbrandon> heh
[03:07] <nixternal> imbrandon: i filled out some survey on a MS India website, and they are sending me some Vista discs ;)
[03:08] <imbrandon> nixternal: yea i got them today, thats hwat i was saying
[03:08] <imbrandon> bu they will collect dust
[03:08] <nixternal> haha
[03:08] <nixternal> i am making a disc lamp, so they will look purty sittin' on top ;)
[03:14] <Riddell> imbrandon: hmm?
[03:22] <Riddell> yeah, package qtnx
[03:23] <jdong> lol
[03:23] <jdong> Hobbsee: make powersaved use acpi-support scripts :)
[03:23] <imbrandon> Riddell: libmtp from not in debian ( its on mentors.debian.net but it badly need to be re-debianized its very ugly ) into main
[03:23] <Hobbsee> nooo!
[03:23] <Hobbsee> what's qtnx?
[03:24] <imbrandon> btw how longs it normaly take pitti to review main inclusion , ipodslave is still in the queue
[03:24] <Riddell> Hobbsee: http://blog.gwright.org.uk/articles/2006/08/27/qtnx-and-nxproxy
[03:24] <gnomefreak> im assuming its the nx package seveas has in his repo for kde
[03:24] <imbrandon> Hobbsee: a qt nx client ? hehe
[03:24] <Riddell> imbrandon: why main?
[03:24] <Riddell> gnomefreak: got a url to that?
[03:25] <imbrandon> so amarok can support mtp based mp3 players
[03:25] <gnomefreak> yesh give me a min to find it
[03:25] <Riddell> imbrandon: upload it in the normal way and main inclusion report
[03:25] <imbrandon> k
[03:25] <gnomefreak> i think his is free nx
[03:25] <gnomefreak> but not sure
[03:26] <imbrandon> yea ipod == 75% of the market mtp based players are the other 24% ( 1% weird crap )
[03:26] <jdong> Riddell: are there plans for *nx in Edgy?
[03:26] <imbrandon> Riddell: ^^
[03:26] <Riddell> jdong: I plan to get qtnx packaged
[03:26] <jdong> are there plans to get seveas's freenx packages into universe?
[03:26] <imbrandon> seveas dosent have qtnx i dont think
[03:26] <imbrandon> only freenx
[03:27] <jdong> right, but having freenx in edgy is not a bad idea :)
[03:27] <gnomefreak> http://free.linux.hp.com/~brett/seveas/freenx/dists/dapper-seveas/  it looks different
[03:29] <Riddell> that'll be freenx indeed
[03:29] <gnomefreak> i would like to get the e17 packages Hawkwind  hass in is repo in atleast multiverse
[03:29] <gnomefreak> i know thats not possible because it wont be stable anytime son
[03:29] <gnomefreak> soon
[03:29] <Riddell> why multiverse?
[03:30] <gnomefreak> Riddell: unstable as it is i dont think main or universe would be good
[03:30] <Riddell> multiverse is about licencing not stability
[03:30] <imbrandon> gnomefreak: well multiverse is for lic issues not stbility
[03:30] <imbrandon> hahahah Riddell
[03:30] <gnomefreak> repo = stable but e17 devels are not gonna release it by oct
[03:31] <Riddell> e17 is going to be released??!
[03:31] <gnomefreak> yes i know but due to stablity would it be good to throw in universe or main?
[03:31] <imbrandon> hehe
[03:31] <gnomefreak> Riddell: as far as i know it will in like 16 years ;) j/k
[03:32] <sebas> They'll rename it to "enlightenment forever" first.
[03:32] <imbrandon> i can get seveas's nx packages and get them ready for universe right now, Hobbsee are you gonna touch qtnx ? if not i'll do it along with the batch
[03:32] <gnomefreak> i dont think it will happen any time soon. they dont have any info on when
[03:32] <Hobbsee> imbrandon: go for it
[03:32] <imbrandon> kk
[03:33] <imbrandon> gives me something todo besides look at amarok bugs and my mac lol
[03:33] <Hobbsee> hehe
[03:37] <Riddell> imbrandon: I've bounced you the e-mail from the qtnx author
[03:38] <Hobbsee> sigh.  i keep walking off the edge of the darn cliffs.
[03:38] <imbrandon> ok cool , i was just lookig for the gcc4 patch too, is that still needed or do you know ?
[03:39] <Riddell> imbrandon: for what?
[03:39] <imbrandon> Riddell: looking at the comments on that page .... quote
[03:39] <imbrandon> #
[03:39] <imbrandon> nukeedit
[03:39] <imbrandon> George Wright said about 6 hours later:
[03:39] <imbrandon> You need a patch for nxcomp to compile using gcc 4. Search the freenx-knx mailing list for it.
[03:41] <Riddell> imbrandon: joy.  I've not seen that
[03:42] <imbrandon> heh its on the comments of http://blog.gwright.org.uk/articles/2006/08/27/qtnx-and-nxproxy
[03:42] <imbrandon> i'll see if i can track it down
[03:43] <Riddell> George is on #kde-devel if you need to ping him
[03:43] <imbrandon> or maybe seveas has it
[03:43] <imbrandon> ok i'm there too
[03:43] <imbrandon> just idle lol
[03:44] <imbrandon> hrm is that svn for freenx actualy qtnx ?
[03:44] <imbrandon> or is qtnx built from freenx, i'm slightly confused on the naming here
[03:44] <imbrandon> i know how it works, infact i have a freenx server setup on voyager and enterprise right now
[03:45] <imbrandon> but this naming has be a bit thrown
[03:45] <bddebian> Morning
[03:45] <imbrandon> heya bddebian
[03:45] <imbrandon> Riddell: ^
[03:45] <bddebian> Heya imbrandon
[03:46] <imbrandon> ahhh nvm i got it
[03:46] <Riddell> imbrandon: qtnx is a client, it's source is in the freenx svn
[03:47] <imbrandon> right
[03:47] <imbrandon> i just cought that
[03:47] <imbrandon> okies
[03:47] <imbrandon> i was just a bit thrown for a minute
[03:57] <Lure> Riddell: kwin-crystal does not build: https://launchpad.net/+builds/+build/239929
[03:58] <Riddell> Lure: fooey
[03:59] <Riddell> el: are you on dapper or edgy these days?
[03:59] <el> Riddell, here on dapper, i have an edgy available
[03:59] <el> hi Hobbsee :)
[04:01] <el> Riddell, oh - i just realise: if it's power management better for dapper. the other one is a desktop
[04:01] <danimo> hi el
[04:01] <el> hey danimo :)
[04:02] <Riddell> el: ok
[04:03] <el> Riddell, thanks
[04:03] <imbrandon> Riddell: wow after reading this, do we realy want it, i mean it depends on the old nx server and wont connect to the new ( 2.0 ones ) and dosent support anything but the freenx public key atm
[04:04] <Riddell> imbrandon: quite possibly we don't
[04:06] <Lure> sebas: ping
[04:07] <Lure> sebas: kpm from svn does this instead of tooltip: http://paste.ubuntu-nl.org/21980 (no time to debug on my own)
[04:08] <sebas> Lure: What's your battery status?
[04:08] <sebas> i.e. charged, charging, discharging?
[04:09] <Lure> sebas: charging state:          charged
[04:09] <sebas> (This is the fine thing about debugging the powermanagement / HAL stuff, everything depends on the state of battery, lid, whatever.
[04:09] <sebas> Ok, makes sense. I'll fix it.
[04:09] <Lure> sebas: http://paste.ubuntu-nl.org/21981
[04:10] <Lure> sebas: yes, it looks to mi similar as Display module and xorg.conf (as Sime did for Dapper) ;-)
[04:14] <allee> Hobbsee: w-w-w-why?
[04:14] <allee> Hobbsee: w-w-w-where?
[04:15] <Hobbsee> +    Thx Hobbsee for reminding me (again and again :).
[04:15] <Hobbsee> allee ^ :P
[04:15] <allee> Something wrong with it? :)
[04:15] <Hobbsee> allee: no, not at all.  i was amused :)
[04:16] <sebas> svn up, Lure?
[04:16] <Lure> sebas: yes please
[04:17] <Lure> sebas: At revision 578517
[04:17] <allee> Hobbsee: next time I tell the truth: s/Thx/Argl/ s/reminding/pokes with a stick/
[04:17] <Hobbsee> allee: ROFL!
[04:17] <sebas> Lure: I've just committed a fix in 18 :)
[04:44] <Riddell> el: http://muse.19inch.net/~jr/tmp/kde-guidance_0.6.7svn20060829-0ubuntu1_i386.deb
[04:44] <Riddell> el: although most of your user interface changes havn't been implemented yet
[04:45] <el> Riddell, thanks - i'll have a look
[04:46] <Lure> sebas: fix works, thanks!
[04:59] <ryanakca> is there anything KDE that needs packaging? or can I just look around on kde-app and find something?
[05:02] <Riddell> ryanakca: some ideas on https://wiki.kubuntu.org/MOTU/Packages/Candidates/Kubuntu
[05:02] <sebas> Riddell: Thanks for the package, I'll do some more polishing and ask you to repackage, so we can have another round of testing from more people
[05:02] <Riddell> ryanakca: let us know before you start, someone else might already be working on it
[05:05] <Riddell> sebas: cool
[05:07] <kwwii_> Riddell: did you hear that the o2 theme for katapult was taken care of by Mez?
[05:09] <Riddell> kwwii_: yes, he /msged me a patch
[05:19] <trappist> could someone have a look at bug #39268 - I put a patch, but it's kinda hacky due to my lack of C++.  Should make it easier for someone else to fix correctly, though.
[05:19] <Ubugtu> Malone bug 39268 in kdepim "Cannot post in newsgroups" [High,Confirmed]  http://launchpad.net/bugs/39268
[05:26] <allee> Hobbsee: knemo in main?  apt-cache policy says universe
[05:26] <Hobbsee> allee: debian main
[05:26] <Hobbsee> allee: they're requesting all this for the new syncing policy
[05:26] <Hobbsee> so i've been lazy, and using that :P
[05:27] <Hobbsee> Riddell: want to check out https://launchpad.net/bugs/52126  ?
[05:27] <Ubugtu> Malone bug 52126 in kubuntu-meta "unattended-upgrades needs manual configuration" [Wishlist,Confirmed]
[05:27] <Hobbsee> Riddell: mvo says it's a kubuntu bug
[05:28] <Hobbsee> yay, klic builds again
[05:30] <Riddell> Hobbsee: that looks like it should be closed, changing it would break distros that have it installed by default
[05:30] <Riddell> I wonder why ubuntu has it by default and we don't
[05:30] <Riddell> used by unattended-upgrades
[05:30] <Hobbsee> Riddell: did you want the honours?
[05:30] <Riddell> used by update-manager
[05:30] <Riddell> Hobbsee: ok
[05:30] <imbrandon> gah i think dash is breaking limewire/frostwire too grrr
[05:32] <imbrandon> hrm maybe not , dosent work in bash either
[05:32] <imbrandon> whats wrong with this line " potential_java_dirs=(`ls -d1 "$JAVADIR"/j* | sort | tac`) " works in dapper but not edgy ( in a shell script )
[05:33] <imbrandon> get the same with runFrost.sh and runLime.sh ( same line as they are both based on the same code )
[05:33] <imbrandon> runFrost.sh: 44: Syntax error: "(" unexpected (expecting "}")
[05:33] <imbrandon> guess i should learn bash better
[05:34] <trappist> I don't see how the parens are necessary
[05:34] <allee> imbrandon: strange construct.
[05:34] <allee> imbrandon: should work without ()
[05:35] <imbrandon> allee i have no idea, this is the first time ive tried frostwire since the upgrade
[05:35] <trappist> doesn't work in dash on the shell here either
[05:35] <imbrandon> but i thought it was a dash/bash issue as its a #!/bin/sh script
[05:35] <trappist> imbrandon: /bin/sh is dash on edgy
[05:36] <trappist> oh nm
[05:36] <imbrandon> trappist: i know
[05:36] <allee> imbrandon: well () creates a subshell, but ` ` does too.  So I never used and saw (` `)
[05:36] <trappist> imbrandon: it does work in bash (on the shell) and I can't *imagine* where it gets 'expectiong "}"'.  looks like a dash issue to me.
[05:36] <imbrandon> what i'm saying is ok .... it works in dapper unchanged, in edgy it fails on that line BUT if i run "bash runFrost.sh" and change the top line it dosent work either
[05:37] <imbrandon> allee ok i'll try without
[05:37] <allee> imbrandon: x=`echo one two; echo three`; echo $x # does what it should
[05:37] <trappist> imbrandon: does it fail the same way?  it fails here in bash if JAVADIR is empty
[05:37] <trappist> (because /j* doesn't exist)
[05:38] <imbrandon> #!/bin/bash  changing it to that yes it fails the same way
[05:39] <imbrandon> ahh but
[05:39] <allee> (edgy)root@allee:~# x=`echo one two; echo three`; echo $x
[05:39] <allee> one two three
[05:39] <allee> (edgy)root@allee:~# x=(`echo one two; echo three`); echo $x
[05:39] <allee> one
[05:39] <imbrandon> brandon@voyager:~$ /bin/bash /usr/lib/frostwire/runFrost.sh  <-- that works soooo
[05:40] <imbrandon> why dosent #!/bin/bash
[05:40] <Hobbsee> right, night al
[05:40] <Hobbsee> l
[05:40] <imbrandon> night Hobbsee
[05:40] <allee> nite Hobbsee
[05:41] <imbrandon> allee yea i know the resoning , but it would be easier just to change the script to use bash instead of patching it and chaging all the code and THEN convincing upstream of those projects to do the same
[05:41] <Hobbsee> hehe
[05:41] <imbrandon> @lart 22 Hobbsee
[05:41] <imbrandon> doh
[05:42] <Hobbsee> Riddell: you could probably drop wlassistant, come to think of it.  and knemo.  both are more or less depreciated with knm
[05:42] <Hobbsee> no idea if that'd help or not
[05:42] <imbrandon> so really my question is why is it not using #!/bin/bash when specified at the top of the script allee / trappist
[05:43] <trappist> imbrandon: I wonder if it gets cached.  try running it without prepending /bin/bash again?
[05:43] <allee> imbrandon: good question
[05:43] <abattoir> Riddell: hi... are you there?
[05:43] <Riddell> hi abattoir
[05:44] <abattoir> Riddell: you got my mail(and does the 're' issue still present?)
[05:44] <abattoir> ?
[05:44] <Hobbsee> jjesse: kubuntu meeting, next thursday, 2100utc - can you make it?
[05:44] <allee> imbrandon: from all I know it should do the same.
[05:44] <imbrandon> hah hrm trappist your right
[05:44] <allee> imbrandon: you run it from same dir?
[05:44] <imbrandon> now it works without it, seemed cached
[05:44] <Riddell> abattoir: I've not looked at it again
[05:44] <omeow> I love the new KDM theme. :) Too bad I won't be seeing it much.
[05:44] <imbrandon> allee its in the path
[05:44] <trappist> awesome, that was a wild-ass guess :)
[05:44] <imbrandon> trappist: yea thats nuts LOL
[05:45] <abattoir> Riddell: oh, ok, because it works here... and could you tell me at which step the GTK frontend fails?
[05:45] <imbrandon> well anyhow looks like i need to patch both of those packages atleaste , man this move to dash has been biting me in the arse the last few days
[05:45] <imbrandon> little stuff keeps creeping up here and there
[05:46] <Riddell> abattoir: the last one, different (GUI) error, can't remember what not
[05:46] <Riddell> now
[05:46] <abattoir> Riddell: ok, no problem, if you have the time later, please tell me
[05:46] <Riddell> abattoir: did you sync the .bzr directory?
[05:46] <abattoir> Riddell: regarding bzr, someone at #bzr told me just copying it online would work... :-\
[05:47] <Riddell> abattoir: you need to remember the .bzr directory
[05:47] <abattoir> Riddell: i'll look into it and fix it, but if you want the latest file, it already is there...
[05:47] <allee> imbrandon: run it as: /usr/lib/frostwire/runFrost.sh
[05:47] <imbrandon> alleeyea it works that way
[05:47] <abattoir> Riddell: you'd have to fetch it manually though :P... will work on it
[05:47] <allee> imbrandon: good.  I relax.
[05:48] <imbrandon>
[05:48] <allee> imbrandon: search for $0 games played in the script
[05:48] <allee> imbrandon: looks like the script assumes that $0 contains full path
[05:48] <imbrandon> yea looks like it
[05:50] <imbrandon> okies off to the store, bbiab
[05:50] <imbrandon> thanks allee / trappist , and i'll fix those up later tonight
[05:51] <imbrandon> hehe
[05:58] <ryanakca> Anyone packaging "KnowIt"?
[05:59] <Hobbsee> ryanakca: yeah, arbiter
[05:59] <ryanakca> kk
[05:59] <ryanakca> lol
[06:00] <DaSkreech> Night HobbSee
[06:00] <Riddell> ryanakca: if you want to clean out that Canidates page that would be cool
[06:01] <ryanakca> which one? I cleaned out the main one in July... it was messy...
[06:01] <Hobbsee> or just fix the bugs in the rest of the archive :P
[06:29] <viper550> Hello everyone!
[06:30] <kwwii_> hi viper550
[06:31] <kwwii_> Riddell: just sent you a diff for katapult, let me know what you think.
[06:31] <Riddell> thanks
[06:31] <viper550> So, just wondering if you tried my tweaks for the buttons
[06:33] <DaSkreech> Riddell: Oh good job on the spelling catalog
[06:41] <imbrandon>
[06:41] <Riddell> hmm, no e-mail from kwwii_ yet
[06:43] <kwwii_> just take this: http://bootsplash.org/imagedisplay.diff
[06:44] <Riddell> thanks
[06:45] <danimo> kwwii_: dude, not, please
[06:45] <allee> kwwii_: can't this color be derived from a color setting in current theme?
[06:48] <imbrandon> Riddell, allee, kwwii_ , or someone that will actualy help benifet kubuntu , woudl you like my private beta key for Vista , i'm honestly not gonna use it, i have no intrest
[06:48] <imbrandon> i'll forward them my mail
[06:52] <kwwii_> imbrandon: I only have ppcs
[06:52] <imbrandon>
[06:52] <kwwii_> allee: no, we cannot use that color, as it is normally shown on a light bg color
[06:52] <kwwii_> katapult uses a transparent pic
[06:52] <kwwii_> which is dark
[06:52] <Riddell> imbrandon: could do
[06:52] <imbrandon> heh yea i forgot i was in the MS beta program and got the key/download today , so i thought i would offer it to soeone whom might actualy use it, as i wont bother to even download it
[06:52] <kwwii_> danimo: don't worry, I am still testing other colors
[06:53] <imbrandon> ok Riddell i'll forward you the mail with the download / key
[06:53] <ryanakca> is ctrl - alt - + / ctrl - alt - -  disabled for some reason?
[06:53] <danimo> kwwii_: nah, I mean why not use the system colors?
[06:53] <allee> imbrandon: I've no plans to play with vista
[06:53] <danimo> kwwii_: i.e. a fitting QColorGroup member
[06:53] <kwwii_> danimo: as I just mentioned, it does not work
[06:54] <danimo> ugh?
[06:54] <danimo> kwwii_: what happens?
[06:54] <danimo> they prolly messed with their palettes
[06:54] <kwwii_> colors that are picked for a light background will never match to a half transparent dark background
[06:54] <danimo> ah
[06:55] <kwwii_> it was blue, but I can barely see it on my monitor
[06:55] <imbrandon> Riddell: you got mail(tm)
[06:55] <imbrandon> heh
[06:55] <allee> kwwii_: isn't there some kind of algorithm that make such a dark col. out of a 'standard color'
[06:55] <kwwii_> so I changed it to orange, but it will probably change again
[06:55] <kwwii_> allee: not one that also assures it works well and looks nice
[06:56] <allee> kwwii_: then KDE needs another color group member!
[06:56] <imbrandon> hehehehe
[06:57] <kwwii_> :-)
[06:57] <kwwii_> to be honest, that sounds like too much work
[06:58] <kwwii_> and katapult is not part of kde base, I think
[06:58] <DaSkreech> It's part of kubuntu-desktop though?
[06:58] <kwwii_> yepp
[06:59] <imbrandon> DaSkreech: yes, lots of things are part of kubuntu-desktop and not kdebase
[06:59] <DaSkreech> Right I know part of the luv of Kubuntu :)
[07:02] <allee> kwwii_: I don't mean patch kdelibs now. But could not hurt to (re?)mind some KDE hackers that there's something missing
[07:03] <imbrandon> hehe
[07:04] <kwwii_> allee: dude, it is simply not necessary...to change the pics you have to run a script first
[07:04] <kwwii_> and making one more color to set just for that reason seems like overkill
[07:04] <kwwii_> there are different themes one can choose from
[07:05] <kwwii_> ok, time for a beer with a friend
[07:05] <kwwii_> bbl
[07:07] <imbrandon> haha later kwwii_
[07:08] <ryanakca> anybody working on "Kumula"
[07:09] <Riddell> ryanakca: check revu but I've not heard of it
[07:09] <ryanakca> Riddell: nope, not there, I'll look at / package it tonight...   http://www.kde-apps.org/content/show.php?content=11997
[07:10] <imbrandon> hehe evil python packing, you should have fun
[07:10] <imbrandon> nice to see it will be kde/qt4 soon
[07:12] <Riddell> cool
[07:14] <_Sime> I've never heard of kumula before.
[07:14] <imbrandon> _Sime: it looks new, but prety slick if it works as intended
[07:14] <imbrandon> it is one thing kde/linux is lacking realy
[07:15] <imbrandon> mmm more food bbiab
[07:16] <_Sime> there is little info on the site about the project and where it came from, and who is producing this.
[07:21] <allee> ryanakca: not do discourage you.  IMHO software of this complexity are best only pkg'ed if one uses it.  When a bug report comes it, it's not that easy to verify/confirm it or test a fix without an already running setup.
[07:21] <allee> ryanakca: nevertheless a very interesting peace of software
[07:26] <ryanakca> allee: kk, I'll get it setup and run it couple times :)
[07:27] <ryanakca> I have no use for it, but it looks very interesting...
[07:27] <allee> ryanakca: yes  (like kolab ;)
[07:27] <ryanakca> kolab?
[07:28] <allee> ryanakca: imap/pop/address/calendar server
[07:28] <ryanakca> ah
[07:28] <ryanakca> bbl
[07:28] <Riddell> kwwii_: new katapult look uploaded
[07:28] <nixternal> ahh, kumula...one of these days with good developers..that could potentially be the opensource solution to goldmine
[07:32] <sebas> Did we want the powermanager to be a kcontrol module (and run standalone, as the other guidance tools)?
[08:07] <imbrandon_> ok i'm gonna take the rest of today and just "goof off" so if anyone needs me for anything i'll still be on irc just not working on anyting in particualr ( taking some time to play with kde on osx and watch some tv )
[08:07] <imbrandon_> incase anyone cares heheh
[08:10] <Tonio___> yop
[08:11] <Riddell> sebas: it should run standalone, no need for it to be a kcontrol module
[08:12] <sebas> Riddell: Well, it can do both.
[08:13] <Tonio_> hey Riddell, sebas
[08:13] <sebas> I suppose if we remove the klaptopdaemon applet, people will miss that in kcontrol^W systemsettings
[08:13] <Riddell> sebas: but if it's one there's no need for the other
[08:14] <sebas> Hi Tonio_  :)
[08:14] <sebas> Riddell: Ow, I thought klaptopdaemon would die a painful death finally
[08:14] <Riddell> sebas: it already has
[08:14] <sebas> Then I don't understand
[08:16] <Riddell> sebas: what don't you understand?
[08:16] <sebas> The
[08:16] <sebas> "there's no need for the other"
[08:16] <Riddell> sebas: applications which have a UI don't need a kontrol module on the whole
[08:16] <Riddell> kcontrol modules are for when you don't have another UI
[08:17] <sebas> Ah, getting it.
[08:17] <sebas> What about the desktop usecase?
[08:17] <Riddell> I havn't figured that one out yet :)
[08:17] <sebas> I suppose I've to suspend my desktop from the logout dialogue, how do I set it up?
[08:17] <sebas> Ok.
[08:17] <Riddell> what needs set up?
[08:18] <sebas> Good questions, /me checks.
[08:18] <sebas> kb shortcuts, at least (but that's your item :))
[08:19] <Riddell> well keyboard shortcuts is for brightness and generally that's laptop only
[08:19] <sebas> I was also thinking about a setting "lock screen after suspend" (although, personally, I don't need it).
[08:19] <sebas> Ow, no kb shortcuts to hibernate / suspend?
[08:21] <Riddell> sebas: lock screen after suspend is dangerous, I know gnome had a problem with that where you could type stuff for an instant before the lock happened
[08:21] <sebas> That
[08:21] <sebas> can be worked around, I suppose.
[08:22] <Riddell> so hibernate/suspend shortcuts is the only thing to configure, dunno if I care too much if some people can't to that, there's already control-alt-delete
[08:22] <sebas> It's a problem with kdesktoplock being async, one could wait for it to be locked, then suspend.
[08:22] <sebas> Ok.
[08:23] <sebas> Have fun, take a chinchilla with you, it's fun ;-)
[08:23] <Riddell> k3b backported
[08:23] <Riddell> seaLne ^^
[08:29] <seaLne> yeah, saw thanks
[08:33] <jdong> !info k3b dapper-backports
[08:33] <ubotu> k3b: A sophisticated KDE CD burning application. In component main, is optional. Version 0.12.14-0ubuntu7 (dapper), package size 3941 kB, installed size 8376 kB
[08:33] <jdong> hmm, ubotu doesn't understand dapper-backports?
[08:33] <seaLne> has it built yet?
[08:34] <jdong> don't think so
[08:34] <jdong> but ubotu responded with something from dapper
[08:34] <jdong> does it understand dapper-backports/dapper-security/dapper-updates/dapper-proposed?
[08:34] <seaLne> yeah i suppose it should have said 16 for backports
[08:34] <Riddell> it won't be in the archive yet
[08:35] <jdong> !info linux-source-2.6.15 dapper-security
[08:35] <ubotu> linux-source-2.6.15: Linux kernel source for version 2.6.15 with Ubuntu patches. In component main, is optional. Version 2.6.15-26.46 (dapper), package size 43476 kB, installed size 43612 kB
[08:35] <jdong> !info ktorrent dapper
[08:35] <ubotu> ktorrent: BitTorrent client for KDE. In component main, is optional. Version 1.2-0ubuntu5 (dapper), package size 738 kB, installed size 2964 kB
[08:35] <jdong> !info ktorrent dapper-backports
[08:35] <ubotu> ktorrent: BitTorrent client for KDE. In component main, is optional. Version 1.2-0ubuntu5 (dapper), package size 738 kB, installed size 2964 kB
[08:35] <jdong> nope, doesn't do backports
[08:35] <jdong> ktorrent's been there for a week
[09:13] <ryanakca> can you rename a package like "11997-kumula-base-1.0.tar.gz" to "kumula-base-1.0.tar.gz"?
[09:17] <crimsun> if you meant kumula-base_1.0.orig.tar.gz , yes.
[09:18] <omeow> wieee :)
[09:24] <imbrandon_> ryanakca: might be good to get the tar from the official website too though instead of kde-apps.org ( to make sure its pure/clean ) ..... the XXXXX-<appname> gives it away ;P
[09:24] <ryanakca> imbrandon_: the link on the official website links to the kde-app page
[09:24] <imbrandon_> ahhh ok ;)
[09:43] <Mez> Riddell: ping
[09:49] <jdong> hey, can I poke someone for a ktorrent 2.0.2 package?
[09:49] <jdong> fixes data corruption issues, improves download speeds
[09:49] <jdong> IMO safe for a UVF exception
[09:52] <jdong> oh Seveas.... make ubotu index dapper-backports :)
[09:58] <nixternal> hmm..kdm login a little broke or what?
[09:59] <Lure> nixternal: I thought it was just me - stripes?
[09:59] <imbrandon_> works for me(tm)
[09:59] <nixternal> a lot of things Lure
[09:59] <nixternal> no imbrandon, it is quite messed up
[09:59] <nixternal> one 4 out 4 machines, it is messed up
[09:59] <nixternal> kdm login splash is hosed, as well as the fonts in the login box itself
[10:00] <nixternal> i have 2 big old ugly power mons too
[10:01] <Lure> nixternal: power/battery icon is there because kwwii wanted some negative feedback ;-)
[10:01] <nixternal> heh, Lure, i just noticed it changes every time when i hit the kdm login
[10:01] <nixternal> haha, and he quits
[10:01] <nixternal> i have given kwwii enough negative feedback this week
[10:02] <Lure> nixternal: really? I though he was complaining about not getting any negative feedback lately ;-)
[10:02] <nixternal> hehe, he was until i let loose yesterday
[10:07] <Viper550> Hello again...
[10:09] <DaSkreech> hi
[10:12] <Viper550> Not much going on...
[10:14] <DaSkreech> Oh No I'm bristling with excitement
[10:14] <DaSkreech> zzZZZZ
[10:25] <Viper550> I've got my KDE desktop decked out with the new Kubuntu 6.10 look, nice!
[10:26] <Tm_T> my edgy desktop still can't start xorg
[10:26] <jjesse> Tm_T: i had to do an sudo apt-get install kubuntu-desktop in order for mine to work after i upgraded from dapper to edgy
[10:26] <jjesse> i don't know why but that's how i solved it
[10:27] <Tm_T> hehe
[10:27] <Tm_T> I'll check it later
[10:27] <Tm_T> jjesse: thanks, maybe that helps (weird problems imo)
[10:28] <jjesse> Tm_T: i think when i did that it installed some new x.org packages if i recall correctly
[10:32] <Viper550> But to kwii_, I have one last idea that I'm surprised hasn't been implemented in the purplfication of Kubuntu...
[10:42] <imbrandon_> you mean kwwii_ ;)
[10:44] <kwwii_> :-)
[10:44] <imbrandon_> heya kwwii_  ;)
[10:44] <kwwii_> howdy imbrandon, wassup?
[10:45] <kwwii_> noticed my konversation blinking red
[10:45] <imbrandon_> nadda, just playing arround
[10:45] <imbrandon_> heheh
[10:45] <Viper550> Which film?
[10:46] <jdong_> imbrandon_: would you like to pull in a new ktorrent? ;)
[10:46] <jdong_> or do some master gods need to ok that first?
[10:46] <imbrandon_> theres a newer release than 2.0.1 ?
[10:46] <jdong_> 2.0.2
[10:46] <jdong_> released around 46 minutes ago
[10:46] <imbrandon_> ahh ok yea i'll file a uvf here in a few
[10:46] <imbrandon_> heh
[10:46] <jdong_> imbrandon_ already did
[10:47] <Viper550> My extra idea, is to turn on the "Colorize to match desktop Color Scheme" option by default
[10:47] <imbrandon_> you filed a uvf ?
[10:47] <jdong_> #58139
[10:47] <jdong_> if that's how you file uvf's :)
[10:47] <kwwii_> Viper550: V for Vendetta
[10:47] <imbrandon_> can you send me the changelog please , and did you mail mdz yet ?
[10:47] <jdong_> imbrandon_: no, I just put in the bug ticket. I'm not sure what else I need to do
[10:47] <Viper550> Oooh, I've heard great things about that one! Well...enjoy
[10:47] <imbrandon_> heh i'll take it from here
[10:48] <imbrandon_> bug 58139
[10:48] <Ubugtu> Malone bug 58139 in ktorrent "UVF exception request ktorrent 2.0.1 -> 2.0.2" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/58139
[10:48] <imbrandon_> ugh no changelog and such either, ok
[10:48] <jdong_> imbrandon_: thanks very much.... they're pretty vague about what they fixed, but I quoted what the guy said on his forums :-/
[10:49] <imbrandon_> i'll fix it before i send it to mdz
[10:49] <jdong_> k
[10:49] <imbrandon_> well in that case you have to troll the svn commits ;)
[10:49] <imbrandon_> but i will
[10:49] <jdong_> thanks
[10:50] <jdong_> the creator says on his forums "This fixes a couple of serious issues, and you should upgrade."
[10:51] <imbrandon_> heh yea but a uvf still needs ..... well here lemme show ya
[10:51] <imbrandon_> https://wiki.ubuntu.com/MOTU/Processes/UVF
[10:52] <imbrandon_> ^^ just fyi, but i'll finish this one up since i did the last 2
[10:52] <imbrandon_> thanks jdong_ ;)
[10:52] <jdong_> now I'll know for the future :)
[10:53] <Viper550> So, think colorizing the main panel might look nicer?
[10:55] <ryanakca> imbrandon_: 2 konversation bugs :)
[10:56] <ryanakca> imbrandon_: where should I send them to? /query you or ???
[10:56] <imbrandon_> in 1.0rc1 ? file them bugs.kde.org
[10:56] <imbrandon_> and poke #konversation with the bug numbers
[10:57] <ryanakca> 0.19+
[10:57] <ryanakca> is 0.19+ = 1.0rc1?
[10:57] <imbrandon_> yes
[10:58] <ryanakca> kk
[10:59] <ryanakca> can you file bugs threw malone? or just view them?
[10:59] <imbrandon_> just view
[10:59] <imbrandon_> that is not an official package yet, thus needs to be filed upstream
[11:00] <imbrandon_> just as sho asked ;)
[11:00] <imbrandon_> ( and i mentoned on the blog ) heh
[11:00] <ryanakca> kk
[11:00] <ryanakca> sho?
[11:00] <imbrandon_> one of the kde devs
[11:00] <ryanakca> ah
[11:00] <imbrandon_> err konversation
[11:02] <Viper550> http://www.kdedevelopers.org/node/2283 (nice...)
[11:04] <imbrandon_> heh yea we seen that a week or so ago Viper550 , kinda cool
[11:04] <Viper550> oh...
[11:12] <ryanakca> imbrandon_: is it cvs that I report the bug's version as?
[11:15] <seaLne> i think that kmenu looks awfull :)
[11:16] <seaLne> the panel is for sticking favourite apps on :)
[11:21] <nixternal> im with you there seaLne ;)
[11:21] <nixternal> there is to much to that kmenu
[11:21] <nixternal> plus, everything i use opens up at start up in its own location anyways...and if i need another program, alt+f2 is a quick way of getting it
[11:24] <kwwii_> Riddell: I'll work on the hwdb pics in the next days...can I install it on dapper?
[11:26] <kwwii_> Riddell: and if possible, I would like to test the systray icons for powermanger...how do I do that?
[11:27] <Lure> kwwii_: kde-guidance in edgy includes them
[11:27] <Lure> otherwise it is just couple of python scripts from svn
[11:27] <kwwii_> Lure: so I need to install edgy first, to test it
[11:27] <Lure> kwwii_: no, you can get it on dapper too
[11:28] <kwwii_> I will install knot2 on my test ppc anyway
[11:28] <Lure> just grab from svn
[11:28] <kwwii_> :-)
[11:28] <Lure> it is python so no need to compile (just need pyuic)
[11:29] <Lure> kwwii_: just do "svn co svn://anonsvn.kde.org/home/kde/trunk/playground/base/guidance/powermanager"
[11:29] <Lure> cd powermanager
[11:30] <Lure> ./recompile-ui-files
[11:30] <Lure> then run ./guidance-power-manager.py
[11:31] <kwwii_> Lure: tell me that again tomorrow :-) I had a few beers with a friend and am watching a film atm :-)
[11:31] <Lure> kwwii_: no pb, just ping me if you need it still...
[11:31] <Lure> ;-)
[11:33] <allee> mhmm, new kdm theme looks cool, but username password labels are hardly readable this the background :(
[11:34] <kwwii_> Lure: bash: "pyuic: command not found"
[11:35] <Lure> kwwii_: sorry: apt-get install pyqt-tools
[11:42] <imbrandon> kwwii_: ping
[11:42] <kwwii_> imbrandon: pong
[11:42] <imbrandon> whats up with the two diffrent icons in kmail with oxgyen , see: http://federation.imbrandon.com/ss13.png
[11:42] <imbrandon> heh
[11:46] <kwwii_> imbrandon: not sure what you mean, honestly
[11:46] <imbrandon> see some blue and some brown
[11:46] <imbrandon> ?
[11:47] <imbrandon> for all my imap folers , half are blue and half are brown heh
[11:47] <imbrandon> s/foler/folders
[11:48] <Lure> imbrandon: actually it is cool - folders with unread messages are blue ;-)
[11:48] <imbrandon> yea but /none/ should be
[11:48] <imbrandon> heh
[11:49] <imbrandon> thats what i was getting at
[11:49] <kwwii_> no idea
[11:50] <kwwii_> in my desktop it works fine :-)
[11:50] <imbrandon> heh ok, thought i would ask since they are oxy icon themew
[11:51] <kwwii_> my desktop shows them their
[11:51] <kwwii_> there
[11:51] <imbrandon> wel they are there but some are blue ( unread ) some are brown
[11:51] <imbrandon> see the screenshot
[11:53] <Lure> kwwii_: btw, thanks for larger menu button in kdm login screen - text now fits nicely
[11:53] <kozz> was just about to say the same thing
[11:54] <Lure> kwwii_: I suspect kdm logon is intentionally transparent (and background image is just missing)
[11:56] <Lure> sebas: wow, lot's of commits... ;-)
[12:01] <imbrandon> Riddell: ping
[12:06] <sebas> Lure: Yeah, hacking night :>
[12:07] <Lure> sebas: thanks for hiding brightness controls.
[12:07] <Lure> sebas: can you also add a rectangle around new lid section?
[12:07] <sebas> Sure, what title do you propose?
[12:09] <Lure> we would probably need to put keyboard accelerators near, so we could name it Shortcuts (not sure if obvious enough)
[12:10] <Lure> sebas: btw, brighness is gone for mains, but there is now a slider (now shaded) in battery powered left


[16:00] <blackboxsw> Looks like somebody else has an openbuild cloud-init up with some stale package references. https://build.opensuse.org/package/show/Cloud:Tools/cloud-init
[16:34] <rharper> interesting
[19:04] <powersj> bah launchpad failed to create a diff...
[19:29] <blackboxsw> smoser, this bug is linked as sru https://bugs.launchpad.net/cloud-init/+bug/1644064 but the related branch is "Needs Fixing" what should it be
[19:29] <ubot5`> Ubuntu bug 1644064 in cloud-init (Ubuntu) "sshd_config file permission changed to 644 if ssh_pwauth value is true or false" [Undecided,New]
[19:31] <blackboxsw> looks like all review comments were addressed
[19:32] <blackboxsw> just not merged
[19:34] <powersj> rharper: thanks for the 2nd review
[19:36] <blackboxsw> powersj, sure, anyday (including today works well for me)
[19:36] <blackboxsw> powersj, sure. Anyday .including today, works well for me.
[19:37] <blackboxsw> geez I give up on English
[19:37] <powersj> blackboxsw: Today works for me as well
[19:37] <powersj> lol
[19:37] <powersj> just tell me where
[19:37] <blackboxsw> ok I'm just going through sru bugs to create a template.
[19:37] <blackboxsw> and trying to reproduce failing tests
[19:39] <blackboxsw> powersj, how's 3:30 sound, someone might drop a delivery by the house sometime between now and 3:30.
[19:40] <blackboxsw> I can go anywhere (your choosing as last time we didn't have internet0
[19:40] <powersj> blackboxsw: 330pm dazbog harmony/timberline
[19:40] <blackboxsw> done
[20:00] <smoser> blackboxsw, i suspect its fix-released in artful
[20:01] <smoser> looking. i just marekd it fix-committed in cloud-init
[20:27] <blackboxsw> smoser, thanks, does this bug need to be SRU'd? https://bugs.launchpad.net/cloud-init/+bug/1636531  it's just unit tests?
[20:27] <ubot5`> Ubuntu bug 1636531 in cloud-init (Ubuntu) "unittests blkid command fails on slave s390x" [Undecided,New]
[20:27] <blackboxsw> which aren't included in the deb anyway
[20:30] <nacc> blackboxsw: probably we want the unit tests to pass on older releases?
[20:30] <nacc> blackboxsw: unclear, i guess
[20:30] <nacc> blackboxsw: although the 'fix' is a jenkins change?
[20:30] <blackboxsw> well it's a unit test not leaking blkid calls change which could fail on a variety of systems
[20:30] <blackboxsw> though I just found other leaks in testing the fix
[20:31] <blackboxsw> but not really part of this bug.
[20:31] <nacc> blackboxsw: ok, yeah, i guess it's not clear to me, i was just looking at powersj's response
[20:32] <blackboxsw> yeah I'm with you nacc, I'm not quite certain why that makes an SRU cut. unless we have ungoing jenkins runs against proposed/released cloud-init too
[20:32] <blackboxsw> which I guess is a goal
[20:32] <powersj> if I recall smoser has SRU'ed test fixes before
[20:32] <nacc> powersj: yep, we have
[20:32] <powersj> as I remember doing SRU versification on them
[20:32] <nacc> powersj: i'm just not sure here if the fix is in curtin but really a jenkins change?
[20:33] <blackboxsw> powersj, how'd you verify unit tests as they aren't delivered in the deb produced. did you have to git clone the repo and attempt to run the tests again?
[20:33] <powersj> There were two fixes, 1) the jenkins path change, so no action here, and 2) smoser made a new branch with some other changes related to this issue to prevent it in the future
[20:33] <nacc> powersj: ah i see
[20:34] <blackboxsw> yeah the part 2) is what I was wondering about. as it is just unit test mocks
[20:34] <powersj> blackboxsw: pull-lp-source cloud-init <release>; cd cloud-init-*; run tests
[20:34] <blackboxsw> heh nice
[20:34] <blackboxsw> TIL ^
[20:35] <nacc> powersj: didn't you have a test that did this specifically in jenkins?
[20:35] <nacc> powersj: that is, ran the unit tests (or vmtests?) for a given release from the src for that release?
[20:36] <powersj> blackboxsw: of course if you do it that way make sure to specify the version so they know it lines up and make sure to use release-proposed in the command
[20:36] <powersj> nacc: yeah we have the proposed tests that run when cloud-init is there.
[20:36] <powersj> it does the same thing
[20:36] <nacc> powersj: yep, ok
[20:37] <powersj> nacc: to be clear though, the jenkins job runs the integration tests
[20:37] <nacc> powersj: we have so many new curtin/cloud-init jenkins jobs, i often don't know what does which :)
[20:37] <nacc> powersj: ah ok
[20:37] <powersj> so not unit tests, but maybe I should add those anyway
[20:37] <powersj> nacc: I know :( I'm not sure how to clean them up either
[20:37] <nacc> powersj: unit tests seem like a self-consistency check that's worthwhile
[20:37] <powersj> I'm glad we have expanded coverage of things, but it isn't always clear
[21:53] <smoser> blackjid, regarding "how'd you verify unit tests..."
[21:53] <smoser> there is no ubuntu deb if the unit tests didn't run
[21:53] <smoser> as they're run as part of build
[21:55] <powersj> blackboxsw: https://paste.ubuntu.com/24495122/
[21:56] <blackboxsw> thanks didn't realize disconnected from freenode
[21:58] <blackboxsw> ok thanks, yeah I see unit tests being run in the build recipe before the package build. ok https://launchpadlibrarian.net/317312745/buildlog_ubuntu-xenial-amd64.cloud-init_0.7.9-1495-g2796dab-0ubuntu1+1267~trunk~ubuntu16.04.1_BUILDING.txt.gz
[21:59] <smoser> blackboxsw, yeah..i was going to find al ink to that
[21:59] <smoser> but for some reason... launchpad.net isn't resolving for me
[21:59] <smoser> fun
[22:01] <powersj> smoser: can you add artful to https://launchpad.net/~cloud-init-dev/+archive/ubuntu/test-archive
[22:01] <powersj> and https://launchpad.net/~curtin-dev/+archive/ubuntu/test-archive
[22:01] <smoser> not until i make launchpad.net resolv :)
[22:01] <powersj> hahaha
[22:01] <powersj> sorry just read that
[22:03] <smoser> http://paste.ubuntu.com/24495160/
[22:03] <smoser> someone really doesnt want me to et an ip for launchpad.
[22:03] <smoser> (iv'e restarted network manaer, and killed the dnsmasq process that it is running)
[22:03] <smoser> but 'host launchpad.net <IP_ADDRESS>' should be asking <IP_ADDRESS> directly
[22:08] <smoser> powersj, ok.. so added launchpad.net to /etc/hosts
[22:08] <smoser> i can do that, but i
[22:08] <smoser> i am pretty sure you could have too
[22:08] <smoser> "Package details"
[22:08] <smoser> "copy packages"
[22:08] <powersj> for curtin maybe, I have no rights on cloud-init
[22:09] <powersj> ah ha! ok I see you already did it for curtin
[22:09] <smoser> the key thing to remember is that when you do it..
[22:09] <rharper> smoser: if you're at a sprint, sometimes you need to push <IP_ADDRESS> infront of your caching nameserver; I've had to do that if DNSSEC was enabled, if youre on zesty or artful, systemd-resolvd tries to use DNSSEC
[22:09] <smoser> *copy existin binaries*
[22:09] <powersj> ah so no rebuild
[22:09] <smoser> rharper, see my paste
[22:09] <smoser> i'm on xenial here.
[22:10] <smoser> but even directly asking (host launchpad.net <IP_ADDRESS>)
[22:10] <smoser> didn't work
[22:10] <smoser> i'mi pretty sure that is directly asking <IP_ADDRESS> for launchpad.net
[22:10] <smoser> so something (i think) is udp intercepting
[22:10] <rharper> yes
[22:10] <rharper> they intercept dns
[22:10] <smoser> and has a negative cache for that.
[22:10] <rharper> locally
[22:11] <rharper> for example, they deny phone updates so there's no phone storm of updates on the network
[22:11] <rharper> there are a list of other DNS hijacks via the sprints AP
[22:11] <rharper> I used to run DNSSEC enabled local cache and it *always* broke at the sprint
[22:11] <rharper> not quite sure why launchpad.net would be busted
[22:11] <smoser> oh. i'm not on canoncial
[22:12] <smoser> on mariott
[22:12] <rharper> oh well, they could do the same thing at the hotel
[22:12] <smoser> yeah. but seems still busted to cache a negative result
[22:12] <rharper> ie, hijacking dns for shit n giggles
[22:12] <rharper> if you bring up vpn, it works right ?
[22:12] <smoser> well, i think i have vpn sending only vpn traffic
[22:13] <rharper> you can flip the bit to send it all
[22:13] <smoser> yeah
[22:13] <rharper> which would direct dns through vpn (at least temp)
[22:13] <smoser> but i assume this problem will go away at some point
[22:13] <smoser> and i just put /etc/hosts entry in
[22:13] <rharper> well, it does, until you forgot you put in there and then at some point in the future you freak out again
[22:13]  * rharper did that with diglett, bastion and other hosts
[22:14] <rharper> why u no connect! ?!
[22:14] <nacc> rharper: i think DNSSEC has been deisabled again, right?
[22:14] <rharper> in systemd-resolvd, I think so
[22:14] <smoser> right.
[22:14] <rharper> or resolved
[22:14] <nacc> rharper: yeah, i got a prompt at some point last week
[22:14] <rharper> flippin spelling
[22:15]  * rharper is playing with pihole
[22:15] <rharper> putting that rpi2 to work
[22:31] <blackboxsw> generally speaking are these the typical things we ask for when users submit bugs against cloud-init http://pastebin.ubuntu.com/24495391/?
[22:34] <smoser> blackboxsw, all of /var/lib/cloud/ is good too
[22:34] <smoser> and /var/log/cloud-init-output.log
[22:34] <smoser> and /me goes away
[22:35] <blackboxsw> +1 smoser
[22:39] <powersj> blackboxsw: https://paste.ubuntu.com/24495434/ is what our integration tests pull after each test
[22:39] <blackboxsw> thx ppo
[22:39] <blackboxsw> thx powersj
[22:40] <powersj> smoser: thanks for the ppa updates
[22:57] <blackboxsw> ok updated bug filing request https://bugs.launchpad.net/cloud-init/+filebug
[22:58] <blackboxsw> just to request the info we care about when someone files bugs
[22:59]  * blackboxsw relocates home after picking up some food