[05:04] <lynorian> https://help.ubuntu.com/community/Lubuntu/Documentation/FAQ/Workarounds wow this has lots of old information
[05:05] <tsimonq2> lynorian: you gonna fix it? ;)
[05:07] <lynorian> Well yeah I was looking to fix some of it like the whole section on a workaround for using a ppa last updated for precise or quantal does not seem really a good idea
[05:07] <tsimonq2> I see
[05:07] <tsimonq2> yeah
[05:07] <tsimonq2> lynorian: you got details for the Lubuntu team page yet?
[05:08] <lynorian> and we do not ship chromium anymore
[05:08] <lynorian> on supported
[05:08] <tsimonq2> Correct.
[05:08] <lynorian> irc lynorian
[05:09] <lynorian> email<EMAIL_ADDRESS>[17:45] <krytarik> wxl_, tsimonq2: Please notice the query regarding the GetLubuntu wiki page in #lubuntu earlier - s/xenial/yakkety/ on the links.
[17:45] <tsimonq2> krytarik: will do, thanks


[07:22] <lordievader> Good morning
[10:46] <flowinho> Hey there 👋
[10:46] <lotuspsychje> !security
[10:46] <lotuspsychje> start here flowinho
[10:46] <flowinho> thank you lotuspsychje
[10:48] <lotuspsychje> flowinho: maybe if you share your specific purpose and services, volunteers can try to help you more specificly
[10:50] <lotuspsychje> flowinho: personally i also reccomend nmap your own ip aswell, to see how the outside world sees your server ports
[12:15] <vlm> is there any use of copying /etc/passwd and /etc/group file from / into a chroot when chrooting?
[12:18] <vlm> thing is,when i make a file using ssh like so : echo file|ssh user@chroot-host "cat > myfile" that file gets the proper owner regardless of presence of passwd and group file
[15:45] <locknet> #reddit-sysadmin
[15:46] <Maik> stop spamming
[15:46] <locknet> Maik, sorry, not trying to spam
[15:47] <locknet> trying to join a channel but hex cut my command
[15:50] <Maik> oh, ok :)
[17:34] <lordcirth_> I just rebooted a prod 16.04 server after way too much uptime, and now lxc-* commands are all hanging, and no containers will start. Looking at htop, I see [lxc monitor] in "D" state. Help?
[17:37] <lordcirth_> kill -9 of the hanging process kills the hanging command, but then the next command just hangs again
[17:41] <rbasak> D usually means blocked on I/O
[17:42] <rbasak> Do you have filesystem corruption or some kind of disk fault?
[17:42] <lordcirth_> Not that I can see, but I will check again
[17:43] <rbasak> NFS hang?
[17:43] <lordcirth_> rbasak, there are no IO errors in dmesg; some of the containers depend on cephfs, but not all, and the cephfs mount seems fine
[17:44] <lordcirth_> (it's only used for homes, not /)
[17:44] <rbasak> I don't know then, sorry.
[17:45] <rbasak> It does seems like too much of a coincidence that you're using cephfs and you (superficially) appear to have something blocked on I/O though.
[17:45] <rbasak> I would exhaust that avenue first.
[17:47] <lordcirth_> In the past, any cephfs error has been accompanied by tons of dmesg errors
[17:47] <lordcirth_> I will tried to revert kernel but grub-reboot didn't work
[18:36] <lordcirth__> rbasak, I rebooted with the cephfs mounts commented out and it still hangs. Trying now without nfs as well, but I'm not hopeful
[19:45] <lordcirth> Ok, so lxc-net is hanging on an iptables --wait command; but I have no idea why the iptables command is hanging. Maybe something else is hanging on the lock?
[20:00] <znf> strace it?
[20:01] <lordcirth_> znf, was that to me? (sorry, I keep reconnecting)
[20:01] <znf> yes, strace the iptables? :)
[20:03] <lordcirth_> I tried, it's just a wait4( that doesn't seem helpful... I don't use lxcbr0 anyway, so I am trying USE_LXC_BRIDGE="false" and rebooting
[20:13] <lordcirth_> Most of the containers have started now...


 file file_9964.MP4 too big to download (3658358 > allowed size: 1000000)
 Forwarded from IT MEM:
 file file_9965.MP4 too big to download (3241707 > allowed size: 1000000)
 Forwarded from IT MEM:
 file file_9966.MP4 too big to download (3307752 > allowed size: 1000000)
 Forwarded from IT MEM:


[00:59] -queuebot:#ubuntu-release- Unapproved: gnome-recipes (zesty-proposed/universe) [1.0.0-0ubuntu2 => 1.0.4-0ubuntu1] (no packageset)
[00:59] -queuebot:#ubuntu-release- Unapproved: accepted gnome-recipes [source] (zesty-proposed) [1.0.4-0ubuntu1]
[06:19] -queuebot:#ubuntu-release- Unapproved: arc-theme (zesty-proposed/universe) [20161119-1 => 20170302-0ubuntu1] (no packageset)
[06:55] -queuebot:#ubuntu-release- Unapproved: ncbi-vdb (zesty-proposed/universe) [2.8.1+dfsg-1ubuntu1 => 2.8.1+dfsg-2] (no packageset) (sync)
[06:55] -queuebot:#ubuntu-release- Unapproved: accepted ncbi-vdb [sync] (zesty-proposed) [2.8.1+dfsg-2]
[06:56] -queuebot:#ubuntu-release- Unapproved: ngs-sdk (zesty-proposed/universe) [1.3.0-1ubuntu2 => 1.3.0-2] (no packageset) (sync)
[06:57] -queuebot:#ubuntu-release- Unapproved: accepted ngs-sdk [sync] (zesty-proposed) [1.3.0-2]
[08:32] -queuebot:#ubuntu-release- Unapproved: freevial (zesty-proposed/universe) [1.3-2 => 1.3-2ubuntu1] (no packageset)
[08:34] -queuebot:#ubuntu-release- Unapproved: accepted freevial [source] (zesty-proposed) [1.3-2ubuntu1]
[12:56] -queuebot:#ubuntu-release- Unapproved: gpsshogi (zesty-proposed/universe) [0.7.0-1 => 0.7.0-1.1] (no packageset) (sync)
[12:57] -queuebot:#ubuntu-release- Unapproved: accepted gpsshogi [sync] (zesty-proposed) [0.7.0-1.1]
[14:30] -queuebot:#ubuntu-release- Unapproved: sra-sdk (zesty-proposed/universe) [2.8.1-2+dfsg-1ubuntu1 => 2.8.1-2+dfsg-2] (no packageset) (sync)
[14:30] -queuebot:#ubuntu-release- Unapproved: accepted sra-sdk [sync] (zesty-proposed) [2.8.1-2+dfsg-2]
[14:46] -queuebot:#ubuntu-release- Unapproved: ubuntukylin-meta (zesty-proposed/universe) [0.19 => 0.20] (ubuntukylin)
[18:03] -queuebot:#ubuntu-release- Unapproved: ubuntu-gnome-default-settings (zesty-proposed/universe) [17.04.1 => 17.04.2] (ubuntugnome)
[21:05] -queuebot:#ubuntu-release- Unapproved: unity-control-center (zesty-proposed/main) [15.04.0+17.04.20170314-0ubuntu2 => 15.04.0+17.04.20170402.6-0ubuntu1] (ubuntu-desktop) (sync)


[16:16] <Eickmeyer> OvenWerks: I'm back from vacation. Looks like krytarik helped you with your last ping.
[16:17] <Eickmeyer> How close are we on studio-controls?
[16:17] <OvenWerks> ya. I think I am pretty close to done with controls for this cycle
[16:18] <Eickmeyer> Sweet.
[16:18] <Eickmeyer> Just let me know.
[16:20] <OvenWerks> There is one item left on my todo which may be complete. It is at least part done... it has to do with making devices that are available when not using the alsa back end (alsa jack master) available as an extra device etc..
[16:21] <OvenWerks> and making sure the jack master device is not used as an extra device ...
[16:22] <OvenWerks> bluetooth headphones will not get there I think as I have other things to get to.
[16:23] <OvenWerks> firewire is back in, with a switch to turn alsa-firewire off (needs reboot)
[16:25] <OvenWerks> I have gotten it reliably restarting wth different buffer sizes now. I don't know if the work around I use is even needed with all FW devices but it shouldn't hurt.
[16:27] <OvenWerks> ffado mixer does have some problems still. I may need to restart ffado-dbus-server at each jack restart (which uses a busreset)
[16:28]  * OvenWerks is thinking out loud and now has a solution to try
[16:29] <OvenWerks> I also need to retest using a FW device with the alsa drivers.
[16:31] <OvenWerks> Eickmeyer: in the long run, I may switch from jackdbus to jackd. I do not think jackdbus allows usng more than one FW device at a time.
[16:32] <OvenWerks> but that is for another cycle, If I can get one device running well I will be happy.
[16:33] <OvenWerks> Eickmeyer: for 20.10 release notes: Controls adds firewire support (one of our devs got a fireiwre device)  :)
[16:33]  * OvenWerks is sure Eickmeyer can write it better
[16:44] <OvenWerks> Eickmeyer: different subject: The kde/plasma sw update tool (Discover) does not seem to auto remove old kernels.
[16:45] <OvenWerks> The one we use in xfce does this (or tries to, it misses whatever kernel was on the install media or the last kernel from the old version in an upgrade)
[16:51] <Eickmeyer> OvenWerks: Yeah, that's as easy as a "sudo apt autoremove" to get rid of the old kernels. Definitely something to make the Kubuntu team aware of. (RikMills might have more insight/this is a ping haha).
[16:51] <OvenWerks> Eickmeyer: I also noticed while removing linux-generic kept the sw updater from installing the new generic kernel, it did not mark the actuall kernel images as non-dependants (autoremovable)
[16:51] <OvenWerks> actually no, the autoremove did not work
[16:52] <Eickmeyer> Yeah, I don't know how that works. You might have to use muon to go in and individually remove the old kernels.
[16:52]  * OvenWerks has been doing that the few minutes
[16:55]  * RikMills has zero additional insight
[16:56] <Eickmeyer> RikMills: Perhaps that's a bug in Discover that it doesn't remove old kernels?
[16:56] <Eickmeyer> Or, maybe a missing feature?
[16:57] <OvenWerks> if the /boot directory is in a small partition, it is a bug
[16:58] <RikMills> feature I would guess. then again, you can argue how good an idea autoremove is, unless (as implied) space is running out
[16:59] <OvenWerks> 14 kernels is a bit much
[17:00] <OvenWerks> I actually thin this may be a linux-generic linux-lowlatency thing
[17:00] <RikMills> I had someone in the Neon chat running out of space in /boot the other day, so it is a concern
[17:01] <RikMills> but honestly it does not come up in 'help' topics much
[17:03] <RikMills> the idea of managing kernels with discover makes me queasy.... :P
[17:05] <Eickmeyer> RikMills: If one uses LVM at all, it's a concern as the default is only something like 300-500 MB for /boot.
[17:06] <RikMills> well will have to disagree. I dislike the idea of an updater deciding to remove kernels
[17:07] <Eickmeyer> RikMills: It's unselectable in update-manager, so I imagine it could be just as much opt-out in Discover.
[17:14] <RikMills> as discover is multidistro, I doubt KDE would want to implement it and maintain the data on what each distro calls its kernels packages
[17:16] <RikMills> feel free to ask thye discover dev Aleix Pol
[17:16] <RikMills> *the
[17:18] <Eickmeyer> RikMills: Ok. Thanks for the info. :)
[17:25] <Eickmeyer> OvenWerks: Ardour 6.2 headed to backports.
[17:35] <OvenWerks> RikMills: the updater being muti-distro is the right answer to the question
[17:36] <RikMills> you could have a distro supplied config file with the correct patterns...
[17:36]  * RikMills runs
[17:37] <OvenWerks> Eickmeyer: I think all kernel images are depends of something... this should mean that any one image (and co) should show up for auto remove when there dep is removed.
[17:37] <OvenWerks> *their
[17:38] <Eickmeyer> OvenWerks: Yeah, I would think. The thing is, update-manager is more intelligent in that it knows to remove all but the two most recent kernels.
[17:38] <Eickmeyer> I think it's hard-coded.
[17:39] <OvenWerks> so in theory... a depend on kernel + -1 and -2 should do it... except if the person has not upgraded for a year...
[17:41] <OvenWerks> A better hack would be for a new kernel package to create a meta package that replaces an old one with just depends on the last available kernel :)
[17:47] <Eickmeyer> linux-lowlatency and linux-generic anre both metas, so I don't know why they're doing that.
[17:47] <Eickmeyer> rather, why they're *not* doing that.
[17:52] <OvenWerks> RikMills: it would actually be better for ubuntu to have script that gets called (or can get called) as part of a new kernel install
[17:54] <OvenWerks> /etc/default/ could have a file with Clean_kernels=True/False or one line for each kernel
[17:55] <OvenWerks> however, there is no percieved reason to do this because ubuntu is gnome.
[18:08] <Eickmeyer> OvenWerks: That would make this something for the kernel team.
[18:11] <Eickmeyer> teward might have insight. (shameless ping)
[19:30] <OvenWerks> Eickmeyer: it does look like the depends in the kernel have some extra stuff.
[19:30] <OvenWerks> they have one more bit
[19:31] <OvenWerks> for example, I have 5.4.0-40 but the dep is <IP_ADDRESS>.40 or something like that.
[19:32] <OvenWerks> actually (=<IP_ADDRESS>.45)
[19:33] <OvenWerks> My guess is that apt does not deal with this they way the sw-updater does
[19:36] <Eickmeyer> Must be.
[19:36] <Eickmeyer> Either way, my job just got a little easier. lsp-plugins is upstreamed to Debian. \o/
[19:50] <OvenWerks> :)
[19:51] <OvenWerks> Eickmeyer: ok, controls is ready for feature freeze. just bug fixes anymore
[19:51] <OvenWerks> testing would be great:)
[19:52] <OvenWerks> when I say bug fixes I mean bugs I am not aware of, I do not have a list to fix
[19:53] <Eickmeyer> OvenWerks: Sounds great. So, that means a 2.0.0 release Awesome.
[19:54] <OvenWerks> Eickmeyer: when adding release notes about the reintroduction of firewire, it may be a good idea to note that this is only for single FW devices at this time. I don't think alsa can do that though the multi plugin may work. and I am not sure if jackdbus can either
[19:54] <Eickmeyer> Ok, good to know.
[19:55] <OvenWerks> yes, unless we want to do 1.9* for bug testing first.
[19:55] <OvenWerks> but whatever you feel is fine by me.
[19:55] <OvenWerks> Eickmeyer: Question, should this be announced in Linux Audio Announce?
[19:56] <OvenWerks> (after you tag the release)
[19:57] <Eickmeyer> Here's what I see: you have nothing left on your to-do list for this cycle. Because of that, that sounds to me like a new major release for the rebranding. So, yes, I think an announcement on Linux Audio Announce would be appropriate.
[19:57] <Eickmeyer> It'll also get backported.
[19:58] <Eickmeyer> 2.0.x would be bugfixes.
[20:16] <Eickmeyer> OvenWerks: Also, nice to see it done a month in advance!
[20:21]  * OvenWerks has other things he needs to work on.
[20:22] <OvenWerks> even if someone nees to use qjackctl or command line because they have three fw devices, The part I added to controls will be helpful
[20:24] <OvenWerks> I may try to modify ffado-mixer or fork it if upstream is not interested.
[20:26] <OvenWerks> I have found I need a bus reset every time I open a FW device... after which ffado-mixer no longer works. I have this working with controls but not for people starting jackd from CL


[07:44] <dholbach> good morning
[08:07] <iulian> Hey dholbach.
[08:08] <dholbach> hey iulian
[09:46] <hrw> hi
[09:46] <hrw> what is a proper way to upload NEW package to ubuntu and get PPU for it?
[09:46] <geser> sponsporing
[09:46] <hrw> ok
[09:47] <geser> LP only lets add PPU rights for existing source packages
[09:48] <hrw> ok
[09:48] <geser> so you have to find someone who does the first upload for you and once LP knows about the source package PPU rights can get added
[09:48] <hrw> http://home.haerwu.biz/~hrw/ubuntu/ has my gcc-4.6-armel-cross 1.48 package. will try to find someone who will take a look at it and do uplaod for me
[09:49] <evaluate> If the package isn't ubuntu specific, it would be best to upload it to Debian first and then request a sync though, wouldn't it?
[09:49] <hrw> evaluate: for now it cant be uploaded into ubuntu
[09:49] <hrw> evaluate: I have 6 packages which are on a way to Debian. this is one of them
[09:50] <evaluate> I see.
[09:50] <hrw> evaluate: have to convince Debian Kernel team first that my patch is really worth adding
[09:51] <hrw> evaluate: https://wiki.linaro.org/MarcinJuszkiewicz/Projects/MergeCrossToolchainIntoDebian
[09:53] <geser> hrw: as your PPU rights for gcc-4.6-armel-cross got approved together with with your other packages, you just need to find someone to do the initial upload and prod a TB member later to add the PPU rights for it
[09:53] <hrw> geser: I will do that
[11:32] <nigelb> geser: I talked to dholbach, we can do the whole activity inside harvest of getting the ftbfs marked appropriately.
[11:32] <nigelb> I'm now making sure the data gets imported.  Harvest using the karmic csv unfortunately :/
[11:33] <nigelb> dholbach: https://code.launchpad.net/~nigelbabu/harvest-data/fix-ftbfs-url/+merge/62960 :)
[13:52] <Laney> https://launchpad.net/ubuntu/+source/packaging-tutorial
[14:09] <bdrung_> micahg: yeah, you can sync eclipse 3.6 from experimental
[15:57] <tumbleweed> bdrung_: had a look at my udt todo list today, couldn't remember a few details so listened to the recording. Looks like our audio stream was just static :/
[15:58] <bdrung_> tumbleweed: static?
[15:58] <tumbleweed> white noise
[15:59] <bdrung_> tumbleweed: do you have the url to it?
[16:00] <tumbleweed> http://mirrors.tumbleweed.org.za/uds-o/2011-05-12-06-55-other-o-udt-upstreaming.ogg
[16:01] <bdrung_> tumbleweed: one  todo item is to get the final names for http://anonscm.debian.org/gitweb/?p=collab-maint/release-info.git
[16:01] <tumbleweed> yup, that's what I'm busy writing an e-mail on
[16:02] <bdrung_> that stream contains silence
[16:02] <tumbleweed> yeah
[16:06] <tumbleweed> bdrung_: so, IIRC, ftp-masters wanted it into devscripts, but now launchpad would like it to be a separate package, so we are asking derivatives front desk what it should be called?
[16:07] <bdrung_> tumbleweed: yes
[16:31] <achiang> fta: micahg: ping, i managed to build chromium 11 on lucid/ARM. the same package almost worked, just needed one minor change: http://pastebin.ubuntu.com/615405/
[16:31] <achiang> fta: micahg: need to add line 9 to debian/rules and then it builds
[16:32] <fta> achiang, jpegturbo? it's already in the last upload
[16:34] <fta> achiang, http://paste.ubuntu.com/615408/  but maybe micahg didn't merge it down
[16:35] <achiang> fta: could entirely be my fault. i may not have grabbed the latest package. but the short fyi is that the package does indeed built on ARM
[16:36] <fta> achiang, i'm more concerned about https://launchpadlibrarian.net/72379090/buildlog_ubuntu-oneiric-armel.chromium-browser_11.0.696.71~r86024-0ubuntu1_FAILEDTOBUILD.txt.gz
[16:36] <fta> achiang, 100% reproducible ld crashes on oneiric
[16:38] <achiang> fta: ah, that might be the toolchain problem that micahg was worried about. i haven't had a chance to debug that one yet
[16:39] <bdrung_> tumbleweed: thanks for the mail. the mail doesn't make it clear, that we are searching for a name for 'distro-info' script and library and not only for the package
[16:40] <Laney> doesn't launchpad have its own API for getting that information?
[16:40] <Laney> i.e. why would they want to use such a library?
[16:42] <tumbleweed> bdrung_: care to reply then?
[16:42] <bdrung_> tumbleweed: maybe after lunch
[16:43] <tumbleweed> lunch at 6pm? :)
[16:47] <bdrung_> tumbleweed: yes
[16:47] <bdrung_> tumbleweed: i eat lunch between 12 and 23 o'clock
[16:48] <tumbleweed> heh, us geeks aren't very good at sticking to normal schedules
[18:55] <LaserJock> anybody know what this might mean when building a source package:
[18:55] <LaserJock> dh clean --with python2,python3
[18:55] <LaserJock> dh: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm
[18:57] <cjwatson> missing build-dependency on (something that depends on) python3?
[19:00] <LaserJock> I'll try python3-all and see if that works
[19:01] <cjwatson> doesn't python policy prescribe a particular dependency?
[19:02] <LaserJock> well, this thing has 4 python3 build dependencies
[19:02] <LaserJock> I just need a source package out, so I was trying to install the minimum amount needed
[19:03] <LaserJock> hmm, is debuild used still?
[19:04] <LaserJock> I'm trying to build a natice source package and I get: dpkg-source: error: can't build with source format '3.0 (quilt)': no orig.tar file found
[19:04] <LaserJock> shouldn't it create a .tar for me?
[19:04] <micahg> LaserJock: should be 3.0 (native) if it's native
[19:05] <LaserJock> hmm, ok
[19:05] <LaserJock> well, maybe I'm going about this the wrong way
[19:06] <LaserJock> I've got a bzr branch that I'm trying to make a source package from. I don't know if there is a orig.tar or not, I assumed it was native
[19:07] <cjwatson> if it's non-native, you need to get the orig.tar somehow; either there's pristine-tar data on the branch to allow bzr to figure it out (there sometimes is) or else you have to fetch it independently
[19:07] <cjwatson> the auto-importer deals with pristine-tar data, but that won't necessarily hold for branches people have assembled in other ways
[19:10] <maxb> LaserJock: Generally 'bzr builddeb -S' (or just 'bzr bd -S') and let bzr-builddeb figure out what to do
[19:10] <maxb> It's quite clever at retrieving necessary tarballs from whereever it can find them
[19:12] <LaserJock> < grabbing bzr-builddeb >
[19:14] <LaserJock> maxb: that seemed to work, I have no idea what it did but it spit out a source package :-)
[19:15] <maxb> Early in the output it will have printed information on where it found an upstream tarball to ue
[19:15] <maxb> *use
[19:16] <maxb> Oh, and it will have done its temporary work in ../build-area/ ftr
[19:16] <LaserJock> http://launchpad.net/python-distutils-extra/trunk/2.27/+download/python-distutils-extra-2.27.tar.gz
[19:16] <LaserJock> what does that mean? it got it from the archives?
[19:18] <maxb> That link points to an upstream project's download site, that just happens to be on launchpad
[19:19] <LaserJock> oh, ok
[19:19] <maxb> So, no, it didn't fetch it from the Ubuntu/Debian archive
[19:19] <maxb> It may have asked uscan to locate a tarball based on the content of debian/watch
[19:23] <LaserJock> it did, but said it couldn't find it
[19:23] <LaserJock> oh, no
[19:24] <LaserJock> it tried get-orig-source
[19:24] <LaserJock> uscan worked
[19:36] <micahg> achiang: thanks for testing chromium, I'll throw up builds tonight with that change
[19:38] <achiang> micahg: np
[19:40] <micahg> achiang: do you have systems where you can smoke test the binaries?
[19:41] <micahg> I have natty set up ATM
[19:42] <achiang> micahg: hm, i have lucid/armel systems to test on
[19:42] <micahg> achiang: k, would you be willing to smoke test chromium armel?
[19:42] <achiang> micahg: yes, i can do so
[19:42] <achiang> micahg: just need you to ping me, please (unless there's a way to subscribe to a build or something)
[19:42] <micahg> achiang: cool, thanks, I"ll ping when the builds are available
[19:43] <achiang> micahg: great, thanks
[20:58] <xdatap1> hi everybody
[20:59] <xdatap1> just an info. The mail from Kate on the<EMAIL_ADDRESS>about soft freeze affects only main or also universe? I'm a newbie and I'm working on a merge, in case I'll wait next days
[20:59] <micahg> xdatap1: anything seeded
[20:59] <micahg> xdatap1: what package?
[21:00] <xdatap1> micahg, it's dspam
[21:00] <micahg> xdatap1: should be fine
[21:00] <xdatap1> micahg, ok, thanks
[21:01] <cjwatson> I think it's more accurate to say "anything that goes on CD images" rather than "anything seeded"
[21:01] <cjwatson> (and probably clearer to most people)
[21:01] <xdatap1> cjwatson, great thanks, now it's very clear :)
[21:02] <cjwatson> though I need to correct myself, I should just say "images" to cover DVDs and such as well
[23:20] <ScottK> Laney: Could you set up the transition tracker for the boost1.42 -> boost1.46 transition?  Bad is anything with *boost*1.42* in depends/build-depends.  Good is anything *boost* that's not !1.42 (i.e. either unversioned or using 1.46).
[23:21]  * ajmitch hopes that not too many patches are needed for the transition
[23:21] <cjwatson> ScottK: you have permissions to do it directly
[23:22] <ScottK> cjwatson: Permissions but not knowing how.
[23:22] <ScottK> (and I'm trying specifically to avoid learning it this week)
[23:22] <cjwatson> fair enough
[23:33] <Laney> I'll just use true for is_good for now.
[23:33] <Laney> ScottK: http://paste.ubuntu.com/615544/ look ok?
[23:33] <Laney> with the missing semicolon
[23:34] <ajmitch> will the link to the transition tracker fit in the channel topic?
[23:34] <ScottK> Laney: Looks reasonable.
[23:34] <ScottK> Probably more important than something there.
[23:34] <Laney> pushed
[23:36] <ScottK> Where do I find it?
[23:37] <Laney> updates at :55 IIRC
[23:37] <ScottK> After that?
[23:37] <Laney> at http://people.canonical.com/~ubuntu-archive/transitions/
[23:37] <ScottK> Thanks.
[23:38] <ajmitch> ok, so I was even looking at the wrong URL
[23:38]  * ajmitch should have read further in the thread
[23:38] <Laney> heh


[11:05] <magicaltrout> kjackal: stupid question but seemingly something i've not got in any of my charms... or not that I can find
[11:05] <magicaltrout> if I set a state in a reactive charm
[11:05] <magicaltrout> how do i then unset it when the relation goes away?
[11:14] <stub> magicaltrout: Use the newer Endpoint system and it is @when_not('endpoint.foo.joined'). With the older stuff, it is rather difficult.
[11:40] <elmaciej> Morning
[11:40] <elmaciej> Question about openstack charms - can I mix nova-lxd and nova-kvm hypervisors in one cloud ? it would be really cool
[11:43] <elmaciej> from charms in store descriptions I see that it is not possible but maybe someone know a workaround :)
[11:52] <TheAbsentOne> Are there any tomcat juju pro's here? I'm looking for the correct way to deploy the tomcat charm and connect (jndi) to a deployed mysql charm. So that I can deploy a war that uses a db from the mysql server.
[12:06] <zeestrat> elmaciej: If you mean running kvm hypervisor on one host and lxd hypervisor on another host, then I imagine you should be able to deploy multiple different instances of the nova-compute charm, e.g. one for kvm and one lxd on different hosts. jamespage could probably confirm.
[12:11] <elmaciej> zeestrat:  ok, so quickly - I prepare to charm configs and deploy juju deploy --config nova-lxd.yaml nova-compute --to 1 and juju deploy --config nova-kvm.yaml nova-compute --to 2
[12:19] <zeestrat> elmaciej: Almost. You need to define the different deployments as different applications in juju. So you'd get something like `juju deploy nova-compute nova-lxd --config nova-lxd.yaml --to 1` where `nova-lxd` is the name of that application/deployment. Likewise with `juju deploy nova-compute nova-kvm --config nova-kvm.yaml --to 2`. Note that that you will then need to setup relations for these individually with their
[12:19] <zeestrat> new application name.
[12:19] <gsimondon> Is there a recommended production setup for bare metal for canonical kubernetes with juju?
[12:21] <elmaciej> zeestrat: that's cool, but honestly when I think about it what are the pros/cons in having nova lxd hypervisor ? just wondering also on this one to deploy manually: https://docs.openstack.org/zun/queens/install/overview.html
[12:24] <kjackal> magicaltrout: You could have a look here: https://github.com/juju-solutions/interface-kube-control/blob/master/requires.py#L52
[12:26] <kjackal> gsimondon: what kind of setup would you expect? MaaS I guess would be nice to have so you can put cdk on top
[12:26] <zeestrat> elmaciej: Depends on your use case. Are you comparing lxd to kvm?
[12:27] <elmaciej> well from end user point of view. it will be still available as an instance in horizon so only things like latency etc will be better on lxd
[12:27] <elmaciej> right?
[12:30] <gsimondon> kjackal: nothing like MaaS, we have a custom solution for maas
[12:30] <gsimondon> kjackal: basically I know I can create a manual cloud by adding machines but when you spin up apps (units) juju tries to create a new machine
[12:31] <gsimondon> kjackal: that's the part that's confusing me in this bare metal setup.
[12:31] <kjackal> gsimondon: let me understand something, you have MaaS already setup?
[12:32] <gsimondon> kjackal: if you are talking about maas.io - no, we are not using that
[12:33] <kjackal> ok, so you you want to use the manual provider over machines you already have provided
[12:33] <gsimondon> kjackal: yes.
[12:34] <kjackal> You need to pre-provision any machines: https://jujucharms.com/docs/2.2/clouds-manual and then...
[12:35] <kjackal> deploy the cdk bundle: https://api.jujucharms.com/charmstore/v5/canonical-kubernetes/archive/bundle.yaml
[12:36] <kjackal> But you might need to change this bundle a bit
[12:36] <gsimondon> kjackal: I did that multiple times when I was evaluating this distribution the first time. Basically my questions would be 1) It sucks that I have to specify where to deploy apps. Is it possible to now do that? 2) If I deploy stuff from machine A, how can I use that machine to deploy apps to it? When you do juju status it will show only two machines that I manually added using add-machine but machine A
[12:36] <gsimondon> won't be available
[12:37] <gsimondon> kjackal: 3) Is LXD something worth considering for isolation of components in this setup?
[12:39] <kjackal> gsimondon: yes, creating lxd containers will work
[12:41] <kjackal> so tou your questions: 1) in the manual provider you have the pre-rpovision you machines so you should be explicit on where each app should go 2) I guess you could add the Machine A as a cloud machine with "juju ssh ubuntu@machine-A"
[12:42] <kjackal> 3) lxd should work, I know we do this trick in orange boxes when we do not have enough nodes
[12:43] <gsimondon> kjackal: Thanks, very helpful. Do you use LXD just for kubernetes master and workers or basically for everything being deployed by juju?
[12:45] <kjackal> gsimondon: have a look at how easyrsa is deployed in this bundle https://api.jujucharms.com/charmstore/v5/kubernetes-core/archive/bundle.yaml it says --to: lxd:0 This might work for you
[12:46] <kjackal> My suggestion would be not to place workers inside an lxd container, although it should work you may run into trouble when trying to expose a docker container running inside that lxd container
[12:47] <gsimondon> Any rule of thumb on what to put in LXD and what to keep out so far?
[12:49] <zeestrat> elmaciej: Yeah, so it depends if you and your users want those lxd advantages. Canonical has a nice marketing page for that: https://www.ubuntu.com/containers/lxd
[12:50] <kjackal> gsimondon: not rules, but do not put the etcds on lxd containers on the same host machine :)
[12:51] <gsimondon> kjackal: yeah, that wouldn't be so smart. :)
[13:17] <pekkari> kwmonroe: do you, or do you know any moderator in bigdata mailing list?
[13:22] <kjackal> pekkari: I saw your message do you have the charm somewhere so we can see it in action?
[13:22] <kjackal> We would only need to deploy zookeeper, right?
[13:23] <pekkari> for the testing is enough to deploy zookeeper kjackal
[13:23] <pekkari> I was firing the charm in my laptop, so no environment we can share and see unless we get on a hangout and show it to you
[13:24] <kjackal> I think I know what is wrong with it
[13:25] <kjackal> you have somewhere:
[13:25] <kjackal> @when('zookeeper.started', 'leadership.is_leader', 'zkpeer.changed')
[13:25] <kjackal> def check_cluster_changed(zkpeer)
[13:25] <pekkari> any suggestion is really appreciated, as I'm running out of ideas
[13:27] <kjackal> no, turns out I donot...
[13:27] <kjackal> its not what i thought it was, sorry
[13:30] <pekkari> sorry kjackal, my irc just crashed
[13:30] <pekkari> I'm all ears
[13:30] <kjackal> no, turns out I donot know what is wrong with it
[13:31] <magicaltrout> http://canacopegdl.com/images/all-ears/all-ears-9.jpg
[13:31] <kjackal> magicaltrout: :)
[13:32] <kjackal> is github down for you people or it only me?
[13:32] <magicaltrout> https://cdn.head-fi.org/a/6941207_thumb.png or maybe this one
[13:32] <magicaltrout> just you
[13:32] <kjackal> xm... it is possible to get banned from gh :)
[13:33] <magicaltrout> with you
[13:33] <magicaltrout> anything is possible
[13:36] <kjackal> I am afraid so...
[13:36] <pekkari> kjackal: I'm starting to think it's platform related, I just tried to use xenial machines and here I can see the hook triggered with no problem: http://dpaste.com/25CB8NJ
[13:37] <pekkari> for similarity with the end user I was using trusty
[13:38] <kjackal> Is it possible at some point you had a build without the <method_name>(self) without the self?
[13:39] <pekkari> no, I don't think so, this very same build I'm deploying now is what I was testing last friday, no modification on the code
[14:06] <elmaciej> zeestrat: kjackal: Guys, do you know when the queens go official with juju charms? queens going to be released in 2 days and it bring's the 18.04 support
[14:07] <zeestrat> elmaciej: https://docs.openstack.org/charm-guide/latest/release-schedule.html
[14:08] <elmaciej> zeestrat: that's cool! thx
[14:10] <zeestrat> elmaciej: If it ain't in the OpenStack Charm Guide, then you can ask the folks on the mailing list (https://docs.openstack.org/charm-guide/latest/find-us.html) or in #openstack-charms
[14:21] <pekkari> kjackal: contribution ready, thanks for the help!
[14:21] <kjackal> did nothing, we are the ones to thank you
[15:04] <elmaciej> last question for today guys, is there a way to set default user and password when adding a machine to the model ?
[15:09] <pmatulis> elmaciej, just for add-machine?
[15:09] <elmaciej> yes, I need a user to login directly not by ssh only
[15:19] <elmaciej> pmatulis: I know that these images are using the cloud-init so I was wondering on two options - rebuild the image and change the cloud.cfg or somehow passing the user data to create user during the creation
[15:51] <zeestrat> elmaciej: passing user data already has some support in 2.3.1+. https://bugs.launchpad.net/juju/+bug/1535891 Note the caveats such as not being able to use the users section. Please feel free to add a new bug/request for that.
[15:51] <mup> Bug #1535891: Feature request: Custom/user definable cloud-init user-data <cpe-onsite> <juju:Fix Released by hmlanigan> <https://launchpad.net/bugs/1535891>
[15:53] <elmaciej> zeestrat: Thanks for that. I'm trying to modify default curtin preseed to add the default user with oneliner
[19:41] <bdx> kwmonroe: I have a requirement for hiveserver2 to be hooked up to zookeeper
[19:41] <bdx> I find here https://www.cloudera.com/documentation/cdh/5-0-x/CDH5-Installation-Guide/cdh5ig_hiveserver2_configure.html, the configuration that need be mended
[19:43] <bdx> kwmonroe: I'm wondering if you have any suggestions toward managing the config xml for the bigtop software
[19:43] <bdx> ?
[19:57] <kwmonroe> bdx: that's gonna be tricky.  the hive-site.xml that bigtop uses is here: https://github.com/apache/bigtop/blob/master/bigtop-deploy/puppet/modules/hadoop_hive/templates/hive-site.xml, but as you can see, none of those properties are available there.  that means the charm doesn't have an easy way to set/change/manage them.
[19:58] <kwmonroe> bdx: so the first step to do this right would be to open an issue for bigtop to expose those config options: https://issues.apache.org/jira/secure/Dashboard.jspa -- that requires you to have an apache jira account.  if you don't have one, it's of course easy to create, or i can open the jira for you.
[19:59] <kwmonroe> and then step 2 would be to get the hive charm to support the zookeeper interface.  that likely wouldn't be too difficult.  we'd do it very much like we do zookeeper's relation for hbase:  https://github.com/apache/bigtop/blob/master/bigtop-packages/src/charm/hbase/layer-hbase/lib/charms/layer/bigtop_hbase.py#L30
[19:59] <kwmonroe> and pass in the appropriate overrides to set the values in hive-site.xml.
[20:03] <bdx> kwmonroe: "so the first step to do this right would be to open an issue for bigtop to expose those config options" - the config options already seem to exist in hive-site.xml
[20:03] <bdx> https://github.com/apache/bigtop/blob/master/bigtop-deploy/puppet/modules/hadoop_hive/templates/hive-site.xml#L39
[20:04] <bdx> ahhh, the concurrency option is missing
[20:04] <kwmonroe> bdx: also, line 39 isn't hive.zookeeper.quorum :)  read it again
[20:05] <bdx> ooooo
[20:05] <bdx> good eye
[20:05] <bdx> darn
[20:05] <bdx> so, cloudera just drops those properties right in there then?
[20:07] <kwmonroe> well, hive upstream probably has those options too.. the full hive-site.xml is like 1000 lines.  bigtop only uses a subset of those things that *they* support as being changeable from the default.
[20:07] <kwmonroe> so we just need to get bigtop to include options related to hive.zookeeper, and then the charms can manage them.
[20:08] <kwmonroe> bdx: i need to run my kid to an appt, but should be back on in about an hour to hear you curse the day you ever mentioned expanding hive to support zookeeper.  biab :)
[20:08] <bdx> :) ok
[20:09] <bdx> https://imgur.com/a/f1W3r - something to think about while you are waiting at your appt
[20:18] <magicaltrout> my biggest issue with kwmonroe's work.... is it puts hadoop in the hands of people who don't need it but don't know better ;)
[20:18] <magicaltrout> shut it all down kwmonroe
[20:23] <bdx> hey
[20:25] <bdx> coming from someone who has ran hdfs on / for the entirety of all time
[20:26] <bdx> magicaltrout: letting me down holmes
[20:30] <magicaltrout> haha :)
[20:31] <magicaltrout> i'm not really directing it at you bdx, but people still bug me with "I have data, i need to deploy hadoop" and it irks :)
[20:31] <magicaltrout> because then they a) don't have data that requires hadoop b) don't have the volume for hadoop c) don't have the budget for hadoop d) don't have a clue how to write stuff to run on hadoop e) don't know how to monitor hadoop
[20:31] <magicaltrout> when all they really need is a column store DB at most
[20:45] <bdx> I see the same thing
[20:45] <bdx> happens across all technologies
[20:46] <magicaltrout> true dat
[20:46] <magicaltrout> I like the ones in here
[20:47] <jujuuser> hello, I'm trying to deploy openstack
[20:47] <magicaltrout> oh really, hows that going?
[20:47] <bdx> magicaltrout: we are moving a ~10TB dataset through a slew of pipelines mon
[20:47] <jujuuser> well I have a 5 server setup, but its asking to deploy stuff via floppy disk
[20:47] <bdx> shoot!
[20:47] <magicaltrout> really? What are you deploying on
[20:48] <jujuuser> Pentium 4 machines I have lying around in my lap
[20:48] <bdx> jujuuser: where does it say "floppy disk"?
[20:49] <magicaltrout> hehe
[20:49] <magicaltrout> thats honestly a real story from last year
[20:49] <magicaltrout> he was having issues because his juju powered openstack cluster was trying to boot from  floppy disk
[20:50] <bdx> no
[20:51] <bdx> lol I believe you
[20:51] <bdx> jujuuser: make sure the minimum requirements are met all the way around
[20:52] <magicaltrout> hehe
[20:52] <magicaltrout> I am excited about DruidIO coming to the Apache Foundation
[20:52] <magicaltrout> I'm gonna get that charmed up
[20:52] <magicaltrout> for high volume timeseries stuff
[20:52] <magicaltrout> that'll be cool
[20:53] <magicaltrout> i'm also tidying up my apache-drill charm which makes hooking up SQL apps to all these platforms much easier
[20:56] <bdx> magicaltrout: apache-drill just hooks up to a nosql database and lets you query it with SQL?
[20:57] <bdx> magicaltrout: what happens when you hook it up to hdfs?
[20:57] <magicaltrout> yeah its a distributed SQL interface for NOSQL platforms
[20:58] <magicaltrout> flat files, hdfs, hive, hbase, kafka, s3 are the most common ones
[20:59] <magicaltrout> so on hdfs you can query a variety of different file formats, it'll do stuff like auto schema discovery for json/csv style files, if they follow a naming strategy it can do cross file queries etc
[20:59] <magicaltrout> you can convert files to parquet DB's quickly and easily for more effective querying at scale
[21:00] <magicaltrout> it'll push down what it can to the underlying query engine and make up the rest in memory unlike a lot of the JDBC interfaces out there
[21:00] <magicaltrout> sponsored and largely developed by MapR and a few Dell folk IIRC
[21:02] <magicaltrout> also provides ODBC & REST interfaces for other uses
[21:02] <magicaltrout> and data federation capabilities so you can do stuff like "select * from mysql left join (select * from hbase))
[21:04] <magicaltrout> it leverages a lot of Apache Calcite which provides the SQL interface, and has a bunch of other adapters to do SQL over X
[21:04] <magicaltrout> https://calcite.apache.org/docs/adapter.html
[21:38] <bdx> super cool
[21:43] <bdx> for anyone that cares to deploy volumes > 1T https://bugs.launchpad.net/juju/+bug/1751909
[21:43] <mup> Bug #1751909: turn up the volume - artificial quotas? <juju:New> <https://launchpad.net/bugs/1751909>
[21:43] <kwmonroe> 1T is too much
[21:43] <bdx> no, 1T works
[21:43] <bdx> but anything over seems to fail
[21:43] <bdx> orr ooo
[21:43] <bdx> 1000 GB works
[21:43] <bdx> possibly 1T woudl fail
[21:44] <kwmonroe> here's the thing bdx, when you get past a couple gigs, you really need hdfs.  magicaltrout, back me up.
[21:44] <bdx> oooh sorry ... I'm crossing wires here, ^ is unrelated to hdfs
[21:45] <magicaltrout> when IRC needs a joy emoticon
[21:45] <kwmonroe> no bdx, i'm just being hilarious.  /me just finished backscroll of how i'm pushing hadoop on people that don't need it.
[21:45] <bdx> ahh yes yes
[21:45] <bdx> aha
[23:25] <kwmonroe> magicaltrout: are you still looking at ranger?
[23:26] <magicaltrout> yeah slowly
[23:27] <kwmonroe> magicaltrout: would ranger's inclusion in bigtop help you?
[23:27] <magicaltrout> absolutely
[23:28] <kwmonroe> magicaltrout: please add ranger to https://github.com/apache/bigtop/tree/master/bigtop-packages/src to include it in bigtop.
[23:28] <kwmonroe> ;)
[23:28] <kwmonroe> i'm chuckling quietly
[23:29] <kwmonroe> who am i kidding, i'm totes LOL.  get it done magicaltrout.
[23:29] <magicaltrout> :'(
[23:29] <magicaltrout> sad times
[23:34] <magicaltrout> i will get around to doing something with it soon enough, I've got the LDAP bits and piees that need finishing up because they'll work for Saiku as well
[23:34] <magicaltrout> and I had the start of a ranger snap
[23:34] <magicaltrout> but then I got sidetracked with the day job
[23:35] <magicaltrout> but now i'm circling back around to Hadoop -> Drill -> Saiku stuff for JAAS, i have an excuse to look at it again
[23:48] <kwmonroe> magicaltrout: i know somebody on the bigtop PMC if you need support.
[23:52] <magicaltrout> i heard the Bigtop PMC was just a bunch of jerks
[23:53] <magicaltrout> We'll see, i need to get it in somehow, but I also have DruidIO, Janusgraph and some other stuff on my high priority todo list
[23:53] <magicaltrout> Not sure where the chips will land with all of that
[23:54] <magicaltrout> plus once the contracts are sorted out at JPL I'm supposed to be getting 80+ hrs a week and 20 odd on a separate cancer research project
[23:55] <magicaltrout> so I need to resource them and sleep at some point ;)


[02:03] <lotuspsychje> good morning
[04:36] <marcoagpinto> morning!
[06:38] <ducasse> good morning
[07:25] <akem> Hey.
[07:27] <akem> Ubuntu will change its logo to a flying donkey.
[07:27] <akem> Apriiillll fooolllllzzz ;P
[07:27] <akem> But it could have been fun  :)
[07:57] <ruedii> Yes?
[07:58] <lotuspsychje> ruedii: you can start polls/discussions here if you like
[07:58] <lotuspsychje> ruedii: i didnt have the case on ssd's causing issues yet myself
[09:55] <Maik> good morning


[00:19] <shadeslayer> yofel:   [ Philip Muškovac ]
[00:19] <shadeslayer>   * Bump build-dep on python-sip-dev to >= 4.14
[00:19] <shadeslayer> in pykde4
[00:19] <shadeslayer> yofel: do you remember why?
[00:20] <ScottK> It would have been to prevent archive skew.
[00:20] <shadeslayer> so, can be dropped?
[00:20] <ScottK> Yes.  We should be the same as Debian.
[00:20] <shadeslayer> because pykde4 for quantal is FTBFS'ing
[00:20] <shadeslayer> ack
[00:21] <ScottK> Hmmm.
[00:22] <ScottK> I'm wrong.
[00:22] <shadeslayer> oh?
[00:22] <ScottK> if(SIP_VERSION STRLESS "040e00")    # These version numbers also appear in ../CMakeLists.txt
[00:22] <ScottK>     message(FATAL_ERROR "The version of SIP found is too old. 4.14 or later is needed.")
[00:22] <ScottK> endif()
[00:22] <shadeslayer> drat :/
[00:22] <ScottK> So that's something you need to keep.
[00:22] <shadeslayer> too late, I uploaded for quantal
[00:22] <shadeslayer> but it'll still fail obviously
[00:22] <ScottK> Sorry
[00:23] <shadeslayer> that's fine, it's in staging
[00:23] <shadeslayer> backport python-sip-dev?
[00:23] <shadeslayer> I wonder how much trouble that'll cause
[00:25]  * shadeslayer backports from raring
[00:26] <shadeslayer> oh hurray
[00:26] <shadeslayer>  pykde4_4.10.90-0ubuntu1~ubuntu12.10~ppa1_source.changes rejected
[00:26] <shadeslayer> no harm done :)
[00:26] <ScottK> You'll need python-qt4 too then.
[00:26] <shadeslayer> okay
[00:26] <ScottK> if(PYQT4_VERSION STRLESS "040905")  # These version numbers also appear in ../CMakeLists.txt
[00:26] <ScottK>     message(FATAL_ERROR "The version of PyQt found is too old. 4.9 or later is required.")
[00:26] <ScottK> endif()
[00:27] <ScottK> Don't recall what's there, but you generally want sip4 and python-qt4 paired with what upstream released together.
[00:28] <shadeslayer> I see
[00:28] <shadeslayer> I've backported the official raring packages
[00:28] <shadeslayer> should be enough
[00:31] <shadeslayer> http://qa.kubuntu.co.uk/ninjas-status/build_status_4.10.90_quantal.html < mostly sorted out :)
[00:38] <shadeslayer> hm, everything should auto resolve
[00:38] <shadeslayer> will test later today then
[03:44] <manchicken> I am on vacation.
[03:44] <manchicken> Sweet.
[04:16] <manchicken> Anybody home?
[05:23] <ScottK> manchicken: No.
[05:26] <manchicken> ScottK: lies!
[05:26] <manchicken> I need something to do.
[05:26] <manchicken> Do people use kdevelop?
[05:26] <ScottK> Some do.
[05:29] <manchicken> What about Qt Develop? It looks like that's shooting at Xcode or Android Studio, seems like it's mainly pointed at Ubuntu Touch and qml.
[05:33] <ScottK> The Ubuntu Touch stuff is (as you might guess) an Ubuntu only plugin that's added.
[05:33] <ScottK> It is mostly aimed at Qt/QML.
[05:34] <apachelogger> no JT :(
[05:34] <apachelogger> someone do something to bug 1183615 plz :(
[05:34] <ScottK> apachelogger: But you have a willing coder awaiting enlightement.
[05:35] <apachelogger> :O
[05:35] <apachelogger> and that at 7:35
[05:35] <ScottK> manchicken is looking for work to do.
[05:37] <apachelogger> manchicken: https://trello.com/c/8T4OXfLX could be something
[05:37] <apachelogger> essentially bzr clone lp:kubuntu-debug-installer
[05:39] <apachelogger> right now it tries to find debug packages using the already active repositories, what we need it to do is allow us to add repositories on-the-fly
[05:39] <apachelogger> e.g. see https://wiki.ubuntu.com/DebuggingProgramCrash#Debug_Symbol_Packages
[05:39] <ScottK> Bonus points for detecting if XMir and declining to file kwin bugs if it is.
[05:40] <apachelogger> TLDR: most debug packages are autogenerated and put in a separate package repository, so to get access that other repoistory needs to be added to apt
[05:40] <apachelogger> ^^
[05:40] <apachelogger> ScottK: I think that is another card TBH
[05:41] <ScottK> But we can't add it by default because if everyone enabled that repository, it would get crushed.
[05:41] <apachelogger> ^ that
[05:42] <apachelogger> so I was thinking ... debug-installer gets started -> tries to find debug packages for files -> fails -> adds the ddebs repository -> updates apt cache -> tries to find debug packages -> failure/success, regardless it removes the repository again -> updates cache
[05:43] <apachelogger> but I guess you could just play around with it a bit see where the code takes you
[05:45] <apachelogger> ScottK: trello says we should discuss the MRE list on kubuntu-devel btw
[05:45] <apachelogger> https://trello.com/c/JT78Qcz3
[05:46] <ScottK> OK.
[05:55]  * manchicken looks...
[06:00] <apachelogger> !info user-manager saucy
[06:01] <apachelogger> :/
[06:01] <apachelogger> afiestas_: didn't you do a release?
[06:02] <manchicken> apachelogger: So we're trying to modify the crash handler so that it will install dbgsym packages in the absence of dbg packages?
[06:02] <apachelogger> yes
[06:02] <apachelogger> well
[06:02] <apachelogger> TBH it probably should just always use dbgsym
[06:03] <manchicken> dbgsym is just the debug symbols for the existing binaries?
[06:03] <manchicken> Does it replace the binaries with ones using -g flags?
[06:04] <apachelogger> nope, essentially it's the debug symbols of the binaries
[06:05] <manchicken> Is that a supplemental file, similar to a dSYM file on OS X?
[06:05] <ScottK> apachelogger: A new change though is that if a -dbg package exists, the -dbgsym is and empty dependency package that depends on the -dbg.
[06:05] <manchicken> I've never done debug symbols on GNU/Linux without it being compiled in.
[06:05] <ScottK> No point in going to the -dbgsym if the -dbg is available.
[06:06] <apachelogger> so the binaries are built with -g by default and then some packaging tool strips all debug symbols into a shadow binary (i.e. instead of one binary you have two, one with the functional code and one with the debug code). gdb can then put those files back together and allow debugging of a binary that technically has no debug symbols
[06:06] <apachelogger> manchicken: dsym sounds similar enough
[06:06] <manchicken> apachelogger: Okay, that makes sense.
[06:06] <apachelogger> ScottK: actually even more so
[06:06] <manchicken> But that actualy doesn't matter for this project, right? We're just dealing with package installs.
[06:06] <apachelogger> if dbgsym is just a dep on dbg it makes even more sense to only go for dbgsym
[06:07] <ScottK> Maybe.
[06:07] <ScottK> Yes, just package installs.
[06:07] <apachelogger> that way you have consistent handling and the package relationship will take care of -dbg packages
[06:07] <ScottK> OK
[06:07] <apachelogger> so we install only -dbgsym but indeed -dbg gets in as well
[06:07] <apachelogger> manchicken: pretty much
[06:07] <manchicken> Let me look at this existing package. I think step 1 is figuring out what we already have.
[06:08] <apachelogger> yeah, bzr clone lp:kubuntu-debug-installer
[06:09] <apachelogger> it's a really simple program ... it gets a list of files that could not be traced (i.e. no debug symbols present) and it uses qapt to find the packages containing those files, then it tries to find the -dbg/-dbgsym package associated
[06:09] <apachelogger> manchicken: general code refactoring is also very welcome, that was just quickly hacked together and since part refactored once or twice ^^
[06:11] <manchicken> apachelogger: While it's loading (slow internet), is this C++, Ruby, Python, other?
[06:11] <apachelogger> manchicken: c++
[06:12] <apachelogger> bug 103378
[06:12] <manchicken> I'm getting a permission error.
[06:12] <apachelogger> Mount Wars 2: The Floppy Strikes Back
[06:13] <manchicken> Evidently it's attempting to send my SSH key and then rejecting it.
[06:14] <apachelogger> manchicken: launchpad.net
[06:14] <apachelogger> check that the right public key is available there
[06:14] <apachelogger> and that the right key is used on your end I guess
[06:14] <manchicken> I'm gonna need to generate a new one I think, I doubt that I still have the old one lying around...
[06:14] <manchicken> I'll check my old FSF thumb drive, that's probably where I would have put it :)
[06:16] <ScottK> Also make sure the username is right.
[06:17] <ScottK> Host bazaar.launchpad.net
[06:17] <ScottK>   User $USERNAME
[06:17] <ScottK> in ~/.ssh/config
[06:18] <ScottK> If your LP username and your local username aren't the same.
[06:29] <manchicken> Making a new key it is!
[06:30] <manchicken> My FSF thumb drive is corrupt :)
[06:30] <manchicken> Glad I only stored keys on it.
[06:34] <manchicken> I'm in business!
[06:34] <manchicken> I think
[06:35] <manchicken> That said, this DL is going to interrupt The Doctor.
[06:36] <apachelogger> NO, NOT THE DOCTOR :O
[06:36] <manchicken> Yeah, I just started the new one. S1E1.
[06:37] <manchicken> I know I'm behind the times... but there are only so many geek-culture references I can miss before I can stop ignoring things.
[06:37] <apachelogger> shadeslayer, Riddell: https://trello.com/c/DplmVapI that does nto seem complete at all........................
[06:38] <apachelogger> manchicken: ^^
[06:38] <manchicken> apachelogger: I don't understand what you mean by "^^"
[06:38] <ScottK> manchicken: I'm probably a close to two decades older than you and I watched the Doctor in college.
[06:38] <ScottK> How can you have missed that one?
[06:39] <manchicken> ScottK: I am 31... and three children old.
[06:39] <ScottK> Right, so 1 year short of two decades older and three also.
[06:40] <manchicken> Heh
[06:40] <apachelogger> http://www.urbandictionary.com/define.php?term=%5E%5E
[06:41]  * valorie started on season one as well, but I'm halfway through
[06:41] <valorie> the Beeb has done a nice job on cleaning up those old tapes
[06:42] <manchicken> You're a brave man, trusting anything to urbandictionary.com.
[06:42] <manchicken> I wasn't sure if you were doing the ^_^ thing, or if you were trying to point up.
[06:43] <ScottK> Not brave.  apachelogger's the right kind of insane for urbandictionary.
[06:44] <manchicken> Nice
[06:44] <apachelogger> manchicken: pointing up is ↑
[06:44] <apachelogger> compose key magic
[06:44] <manchicken> Oh, cmake... I forgot about cmake.
[06:45] <apachelogger> seamake
[06:45] <manchicken> I like the compose key.
[06:45] <apachelogger> today in apachelogger's package wonderland: flooding launchpad with projects to import git repos
[06:45] <manchicken> I still pretend like I speak a little french, it's useful for that.
[06:46] <apachelogger> oh la la
[06:46] <manchicken> Oais :)
[06:46] <manchicken> Ouais
[06:47] <manchicken> Please note: I only pretend to speak a little French, never said I could type.
[06:48] <apachelogger> uhm
[06:48] <apachelogger> yofel_, Riddell: it would appear we lost the kwallet kde-runtime patches
[06:49] <manchicken> I've got a buddy who is the language chair of Illinois Wesleyan University. He's helping me improve my language skills. The goal is to get work to transfer me to Montreal or Paris for a year.
[06:51] <apachelogger> paris ftw?
[06:52] <apachelogger> well, unless one is into maple syrup I guess
[06:52] <apachelogger> omnomnom
[06:52] <manchicken> I'm actually not picky.
[06:52] <valorie> Montreal is beautiful though
[06:52] <manchicken> I want to go somewhere to actually use my French, not terribly picky where.
[06:53] <valorie> my friend from Paris tells me that the french is not much like what is spoken in France
[06:53] <manchicken> Montreal would be preferred since it's within driving distance, however.
[06:53] <apachelogger> and Paris is not? :O
[06:53] <apachelogger> ah well, I guess Paris is beautiful in a different way ^^
[06:53] <valorie> more like what was spoken a few hundred years ago
[06:53] <valorie> yes, Paris is amazingly beautiful
[06:53] <manchicken> Yeah, my buddy says that Québecois french is much more antiquated than French french.
[06:53] <soee> good morning
[06:54] <manchicken> Morning.
[06:58] <manchicken> LMFAO, garbage can eats a dude... obligatory burp...
[07:01] <manchicken> It's been a while since I've seen C++
[07:01] <manchicken> Outside of that stuff we have at work, where we use C++ as nothing more than OO around our C.
[07:03] <apachelogger> manchicken: their french hasn't received updates for quite a while I guess
[07:03] <apachelogger> imagine the security problems
[07:03] <apachelogger_> quassel is only lagging a bit
[07:12] <manchicken> apachelogger: Indeed! They're a commonwealth afterall.
[07:14] <manchicken> They need a hotkey to flip between workspaces like you can Alt-Tab
[07:16] <apachelogger_> manchicken: meta+tab?
[07:16] <apachelogger_> depending on what you mean by workspace
[07:17] <manchicken> apachelogger: Only rotates through them. Doesn't start with the most recently active one like alt+tab does.
[07:20] <apachelogger_> ah yeah, that doesn't exist
[07:26] <manchicken> It should. I use workspaces a lot.
[07:31] <apachelogger> manchicken: file a wish bug on bugs.kde.org I guess
[07:33] <manchicken> apachelogger: Well, since it's a feature I would use, it's a clear omission which warrants the highest priority.
[07:38] <apachelogger> I agree.
[07:38] <apachelogger> doesn't change the process though :P
[07:41] <manchicken> Also a problem.
[07:41] <manchicken> I am loving Dr Who.
[07:41] <manchicken> How did I live this long without this cheesy and amazing sci-fi?
[07:43] <valorie> manchicken: it was all leading up to this day
[07:52] <manchicken> grumble... why won't this thing build?
[07:52] <manchicken> CMake Error at CMakeLists.txt:10 (kde4_add_executable):
[07:52] <manchicken> I know I'm missing something obvious... I just don't know what.
[07:55] <apachelogger> sudo apt-get install install kdelibs5-dev?
[07:55] <apachelogger> meh, GL issues in virtualbox -.-
[07:56] <manchicken> Naw, that didn't work
[07:58] <yofel_> soee: please do NOT backport pykde
[07:58] <apachelogger> manchicken: paste complete output please
[08:01] <manchicken> http://pastie.org/8105989
[08:03] <yofel_> tab fail
[08:03] <yofel_> sry soee
[08:03] <apachelogger> yofel_: hello
[08:04] <yofel_> shadeslayer: please don't backport pykde4 to << raring unless you want to backport the whole SIP stack with rebuilds and want to do the python << 3.3 porting
[08:04] <soee> yofel_, np
[08:04] <apachelogger> yofel_: btw, fwiw, considering we have native packages I'd not put the packaging revision as the actual package revision as that will block uploads if the packaging changed but not the source
[08:04] <apachelogger> e.g. https://code.launchpad.net/~neon/+recipe/project-neon5-attica
[08:05] <smartboyhw> yofel_, I still can't get dh_strip working, it just wasn't even executed during build.
[08:05] <yofel_> apachelogger: er, what?
[08:06] <yofel_> we intentionally have revno:packaging in there so you can upload a new package with new packaging
[08:06] <apachelogger> that won't work if it is -revno
[08:06] <apachelogger> needs to be +revno-0
[08:06] <yofel_> no
[08:06] <yofel_> the packaging is never part of the program source
[08:06] <yofel_> ever
[08:07] <tsdgeos> Riddell: is there no debug package for /usr/lib/x86_64-linux-gnu/libQtGui.so.4.8.4 ? I installed libqt4-dbg but still don't get line numbers
[08:07] <apachelogger> it's le native
[08:07] <apachelogger> native packages have no revision
[08:07] <smartboyhw> yofel_, what do you think will make it work?
[08:07] <apachelogger> otherwise they are not really native are they
[08:07] <apachelogger> and also packaging is always part of the prgram source for native
[08:07] <apachelogger> because, well, they are native
[08:07] <yofel_> project-neon5-attica_0.0+git20130703+r417~8f3b796-16~saucy1.tar.xz already exists in Project Neon KDE Frameworks 5
[08:07] <yofel_> that's the damn same packaging revno
[08:07] <apachelogger> yes
[08:08] <apachelogger> doesn't change the fact that the revision is wrong
[08:08] <yofel_> with native packaging the -XXX part is relevant too
[08:08] <apachelogger> yes
[08:08] <apachelogger> relevantly wrong
[08:08] <yofel_> NO
[08:08] <manchicken> apachelogger: Any idea?
[08:08] <yofel_> you uploaded  project-neon5-attica - 0.0+git20130703+r417~8f3b796-16~saucy1
[08:08] <apachelogger> yes
[08:08] <apachelogger> I am not arguing attica
[08:08] <yofel_> now you tried uploading the damn same thing twice
[08:08] <apachelogger> I am arguing the version being shit
[08:08] <yofel_> it's not
[08:08] <yofel_> you can't just rebuild unchanged things
[08:09] <smartboyhw> !language | apachelogger
[08:09] <yofel_> if you change something please bump the version
[08:09] <yofel_> in all uploads I see revno:packaging is 16, so what changed?
[08:09] <apachelogger> ubottu: SFU will you
[08:10] <apachelogger> obvious
[08:10] <yofel_> what you just did is the completely wrong thing to do
[08:11] <apachelogger> yofel_: http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version
[08:11] <apachelogger> see debian_revision
[08:11] <yofel_> apachelogger: just to note: in native packaging, the "-foo" part is not ignored but part of the source version itself
[08:12] <yofel_> look at the tar filename
[08:12] <apachelogger> yes
[08:12] <yofel_> you just never committed something
[08:12] <apachelogger> it is still wrong
[08:12] <apachelogger> I forgot to push the branchy
[08:12] <yofel_> so nothing changed
[08:12] <apachelogger> it is still wrong
[08:12] <yofel_> no it's not
[08:12] <yofel_> it's packaging, so it should be - to represent that
[08:12] <apachelogger> It is optional; if it isn't present then the upstream_version may not contain a hyphen. This format represents the case where a piece of software was written specifically to be a Debian package, where the Debian package source must always be identical to the pristine source and therefore no revision indication is required.
[08:13] <apachelogger> "where the Debian package source must always be identical to the pristine source"
[08:14] <yofel_> what's a pristine source?
[08:14] <yofel_> the upstream source?
[08:14] <yofel_> the debian/ folder is not part of the upstream source
[08:14] <apachelogger> the unaltered source
[08:15] <apachelogger> if it were upsteram source it would say upsteram not pristine :P
[08:15] <yofel_> well, for native packages that doesn't exist. We only do - to represent that we add the debian/ package later
[08:15] <apachelogger> sure it does
[08:15] <apachelogger> native package == pristine source
[08:15] <apachelogger> non-native package .orig.tar.* == pristine source
[08:16] <manchicken> apachelogger: libapt is what I was missing.
[08:16] <yofel_> look, I'm trying to represent something that doesn't match the debian package workflow in a sane way
[08:16] <apachelogger> manchicken: oh that makes sense, I guess we are not checking properly for it
[08:16] <apachelogger> yofel_: sure it does
[08:16] <apachelogger> it's a native package
[08:17] <yofel_> apachelogger: I'm calculating not from a source package POV but from a recipe POW
[08:17] <yofel_> *POV
[08:17] <apachelogger> dude
[08:17] <yofel_> SIGH
[08:17] <apachelogger> whatever
[08:17] <smartboyhw> !calm | apachelogger yofel_
[08:17] <smartboyhw> !?!!??!??!!??!?!??!?!?!!?!??!?!!?
[08:17] <apachelogger> smartboyhw: dude
[08:17] <yofel_> for all I care make it +neon{revno:packaging}
[08:17] <yofel_> that would be fine a swell
[08:18] <manchicken> I also learned about .kdev_include_paths.
[08:18] <apachelogger> no one knows what that does
[08:18] <yofel_> manchicken: as that debug installer thing is kde, maybe ask JT when you see him how you can use QApt
[08:19] <yofel_> apachelogger: version string is now "0.0+git{date}+r{revno}~{git-commit}+neon{revno:packaging}", good?
[08:20] <apachelogger> yah
[08:20] <apachelogger> <3
[08:23] <manchicken> I'm not entirely unfamiliar with QApt... I still have fond memories of it in Adept.
[08:23] <manchicken> s/fond memories/horrible nightmares/
[08:23] <kubotu> manchicken meant: "I'm not entirely unfamiliar with QApt... I still have horrible nightmares of it in Adept."
[08:23] <manchicken> I suspect/hope it has changed since 2008 though.
[08:23] <apachelogger> manchicken: not the same QApt
[08:23] <apachelogger> in fact not related at all
[08:24] <manchicken> Yay
[08:24] <manchicken> Not worse, right?
[08:24] <apachelogger> no? :P
[08:24] <manchicken> There's the confidence I needed, right there :)
[08:25] <manchicken> What's the usage for kubuntu-debug-installer? kubuntu-debug-installer `which kdesudo`
[08:25] <manchicken> ?
[08:26] <yofel_> it's usually called from inside Dr. Konqi from the 'Install debugging symbols' button in the backtrace view
[08:26] <yofel_> not sure how that's done
[08:27] <manchicken> It looks like it takes a program, or maybe a debug package.
[08:28] <apachelogger> list of file paths
[08:28] <apachelogger> kdesudo may be a bad example though ^^
[08:28] <apachelogger> anyway
[08:29] <manchicken> Yeah, it finds a package for a file, then it tries to guess the debug package.
[08:29] <apachelogger> manchicken: for real examples you could just start konqueror and kill -s ill `pidof konqueror`
[08:29] <apachelogger> that should bring up drkonqi
[08:29] <manchicken> I think I found it.
[08:29] <manchicken> kdesudo kubuntu-debug-installer `which kate`
[08:30] <manchicken> BAM!
[08:30] <manchicken> apachelogger: This is your work, yeah?
[08:31] <apachelogger> in cooperation with JontheEchidna, yeah
[08:32] <apachelogger> manchicken: no kdesudo needed btw
[08:32] <manchicken> apachelogger: It's rather nice for what you described as a quick and dirty. Nice and simple. Not too noisy.
[08:32] <apachelogger> :)
[08:33] <manchicken> What do we need to do with this now then?
[08:33] <manchicken> It seems like dbgsym packages are already included.
[08:33] <apachelogger> manchicken: see the wiki page
[08:33] <smartboyhw> yofel_, still here?
[08:33] <apachelogger> manchicken: you need to add an entire repository
[08:33] <yofel_> yes, but gone now. sorry
[08:33] <manchicken> Oooh, so we need the ability to have this thing add a repo before doing its deed?
[08:34] <smartboyhw> yofel_, :(
[08:34] <apachelogger> manchicken: what it does right now is simply take dbgsym into account, but to make use of that the user has to manually add the repo
[08:34]  * smartboyhw really needs someone on advice of why the hell dh_strip isn't run.
[08:34] <manchicken> Wait a minute... Did you just RTFM me?
[08:35] <apachelogger> manchicken: yeah... simply put echo "repourl" >> /etc/apt/sources.list.d/foo && apt-get update && finddbgsympackages && if (found) install && rm /etc/apt/sources.list.d/foo && apt-get update
[08:36] <apachelogger> i.e. add the repo (unless it is present already <- fun part), update cache, do guessing, possibly install stuff, revert changes (drop repo and update cache again)
[08:40] <manchicken> apachelogger: That doesn't sound all that tricky, actually.
[08:40] <manchicken> So we don't want to keep the repo in the list even if we install a package?
[08:40] <manchicken> What about CVEs?
[08:41] <apachelogger> how do CVEs play into it?
[08:42] <apachelogger> and I'd imagine that once that is working we may want a checkbox somewhere to allow permanent use of the repo
[08:42] <apachelogger> the problem is ... the repo pretty much doubles the time apt-get update takes, so it's not something we'd want to introduce if someone files a crahs report once an installation lifetime
[08:43] <manchicken> What if there's some update to the package, we have debug symbols installed, but now they're out of date.
[08:43] <apachelogger> OTOH if someone is a tester of pre-release software it's something they'd probably want to keep
[08:43] <apachelogger> manchicken: the package gets thrown out
[08:43] <manchicken> Good point.
[08:43] <apachelogger> (in theory - that requires verification actually)
[08:44] <manchicken> Well, either it'd get thrown out or the user would hold it in conflict preventing an update, right?
[08:44] <apachelogger> usually though since the packages are not pulled in by relationships with another package they have a weak dep chain and would get removed to satisfy the upgrade request
[08:44] <apachelogger> manchicken: yes
[08:44] <manchicken> Then what you said sounds pretty reasonable.
[08:45] <manchicken> And then when it's done, have some dialog that says "we had to add a repository in order to get the debug symbols, would you like to keep it or trash it?" and then do what they say.
[08:45] <apachelogger> if it doesn't work we can probably do some apt magic to lower the package score or something
[08:45] <apachelogger> such that they would get removed regardless
[08:45] <apachelogger> manchicken: yeah, something like that
[08:45] <manchicken> Okay, cool.
[08:46] <manchicken> I'm gonna go to bed now, I've got almost 0400 on the clock. The boys aren't going to let me sleep all day :)
[08:46] <apachelogger> manchicken: hehe, good night
[08:47] <yofel> smartboyhw: re
[08:47] <manchicken> I'll start playing with this tomorrow after I finish my SQL Server trigger for a client.
[08:47] <smartboyhw> yofel, hello. I still can't get dh_strip working and as you did said, it doesn't even seem to be run.
[08:48] <yofel> smartboyhw: can you plese run debian/rules clean, tar everything up and upload it to my server? I need to try this myself
[08:48] <smartboyhw> yofel, I forgotten how to get to it...
[08:49] <yofel><EMAIL_ADDRESS>ssh port 2224
[09:04] <smartboyhw> yofel, just pick https://launchpad.net/~smartboyhw/+archive/ppa/+files/libkgapi_2.0.1-0ubuntu1.dsc instead
[09:05]  * smartboyhw watches yofel through ssh:P
[09:05] <yofel> wrong syntax...
[09:05] <smartboyhw> :O
[09:06] <yofel> makefiles required tabs, not spaces
[09:06] <yofel> *require
[09:07] <yofel> smartboyhw: http://www.gnu.org/software/make/manual/make.html#Rule-Syntax
[09:08] <yofel> smartboyhw: now it worked ;)
[09:08] <smartboyhw> yofel, sorry:)
[09:08]  * smartboyhw hates tabbing BTW
[09:08] <smartboyhw> :P
[09:08] <yofel> everyone does, just gnu make likes it -.-
[09:08] <smartboyhw> yofel, -.-
[09:08] <smartboyhw> I think I haven't done the copyright info though....
[09:08] <tsimpson> when writing makefiles is the only time my tab key actually creates a tab character
[09:09] <yofel> yeah, I esp. have a behaviour override for makefiles in vim
[09:11]  * apachelogger blinks
[09:11] <apachelogger> :/
[09:11] <smartboyhw> yofel, copyright done.
[09:12] <smartboyhw> Well, all files belong to him it seems:p
[09:13] <apachelogger> yofel: https://code.launchpad.net/~neon/+recipe/project-neon5-dbusmenu-qt suggestions?
[09:13] <smartboyhw> yofel, review + upload?
[09:13] <smartboyhw> Well, that's all GPL-2+
[09:14] <smartboyhw> Alright, there are some differences it seems
[09:14] <yofel> yep
[09:15] <smartboyhw> yofel, the tests it seems
[09:15] <yofel> not only tests
[09:15] <yofel> Jan is missing in general
[09:15] <yofel> please add then I'll continue
[09:15]  * smartboyhw cheats and adds Jan to * only:P
[09:17] <smartboyhw> yofel, done?
[09:17] <yofel> smartboyhw: add yourself to the packaging copyright ;)
[09:18] <smartboyhw> yofel, ...
[09:18] <smartboyhw> For all the packages I've worked, this is the first time I'm asked to add my own name into debian/* :P
[09:19] <smartboyhw> yofel, yeah, so many files without copyright:P
[09:20] <yofel> yeah, but that's fine from what I see
[09:20] <yofel> so add yourself and we're done
[09:20] <yofel> I think
[09:23] <yofel> smartboyhw: ok, let me do one last thing
[09:23] <smartboyhw> yofel, alright.
[09:24]  * smartboyhw waits for the grand finale:P
[09:25] <smartboyhw> What's eatmydata!?!?!
[09:26] <yofel> makes fsync() and sync() a noop when used. Speeds up disk writes that don't need to be safe
[09:27] <yofel> this is an SSD though so the effect isn't as great as it is with a HDD
[09:27] <smartboyhw> yofel, meh, SSD, boo:P
[09:28]  * smartboyhw likes pbuilder-dist BTW
[09:28] <yofel> didn't meet my needs
[09:28] <yofel> have fun reading my pbuilderrc :P
[09:29] <smartboyhw> :PO
[09:29] <smartboyhw> :O
[09:29] <smartboyhw> really?
[09:30] <yofel> back when I tried it, it did not. Maybe it would today, dunno
[09:30] <smartboyhw> yofel, wait, you got tanglu things:P
[09:35] <yofel> smartboyhw: uhm... libkgapi2-2.install has development files
[09:35] <yofel> please move to -dev
[09:35] <smartboyhw> yofel, which?
[09:36] <yofel> uh, for example usr/include/* ?
[09:36] <yofel> see libkgapi1.install and libkgapi-dev.install
[09:36] <yofel> for 1, those are both correct
[09:39] <yofel> smartboyhw: wait, you haven't written that file yet, right?
[09:39] <yofel> (you need a better editor...)
[09:39] <smartboyhw> yofel, ?
[09:39]  * smartboyhw likes nano, sorry.
[09:40] <yofel> well, go ahead then
[09:41] <yofel> smartboyhw: I'm off for lunch, will look at it later
[09:45] <smartboyhw> yofel, done.
[09:45]  * smartboyhw likes asterisks!
[09:46] <Quintasan> \o
[09:47] <apachelogger> o/
[09:47] <Quintasan> Debian does not like wildcards for some reason
[09:53] <apachelogger> FTW when an upstream source contains a debian/ simply nest the source into src/ and the packaging into debian/ then set --sourcedirectory on dh and all will be awesom
[09:53] <apachelogger> e
[09:53] <apachelogger> also you may need a stub branch to use as main branch
[09:53] <apachelogger> https://code.launchpad.net/~neon/+recipe/project-neon5-dbusmenu-qt
[10:07] <smartboyhw> Guys, LOL http://www.wimbledon.com/en_GB/news/log/2013-07-03/201307031372841499648.html
[10:08] <lordievader> Good afternoon.
[10:10] <Quintasan> \o
[10:10]  * smartboyhw made a fool of himself there, yes!
[10:15] <kubotu> ::workspace-bugs:: [1197317] After KDE update in Saucy, PowerDevil does not suspend the system @ https://bugs.launchpad.net/bugs/1197317 (by Wladimir Mutel)
[10:45]  * smartboyhw wonders should he get a KDE developer account so he can upload patches of packages whenever he wanted (not a really great idea, right?:P)
[10:46] <apachelogger> you cannot upload patches whenever you wnat
[10:46] <apachelogger> not all patches anyway
[10:46] <smartboyhw> Ofc
[10:48] <Riddell> I think they'd want a better reason than that
[10:49] <smartboyhw> ofc
[10:50] <apachelogger> they just want someone supporting the request :P
[10:50] <smartboyhw> apachelogger, Supporting Evidence *
[10:50] <smartboyhw> Please provide links to mailing list postings, review requests or other publicly accessible material which indicates your involvement with the KDE Community.
[10:50] <smartboyhw> Sure, I will be dead.
[10:50] <smartboyhw> \o/
[11:09] <tsdgeos> Riddell: when running the distro qt i get lots of valgrind warnings in qgtkstyle but if i apt-get source the package and compile it myself i don't, any idea why that may happen? could a rebuild automagically fix it?
[11:10] <Riddell> tsdgeos: if you apt-get qt4-x11 ?
[11:11] <tsdgeos> yes?¿
[11:11] <tsdgeos> don't really understand the question :D
[11:13] <Riddell> qt4-x11 was last compiled in saucy a month ago, I guess something might have happened since then to upset valgrind
[11:14] <Riddell> gtk+3.0 was uploaded more recently
[11:14] <tsdgeos> it's complaining about strdups and whatnots
[11:14] <tsdgeos> in the gtk handling
[11:14] <tsdgeos> and then on my compile all is nice
[11:14] <Riddell> tsdgeos: want me to just throw up qt to saucy again to see if it helps?
[11:15] <tsdgeos> and i'm seeting lots of graphical corruption too
[11:15] <tsdgeos> Riddell: if it's not much work
[11:36] <BluesKaj> Hey all
[11:39] <apachelogger> weeeh, new keyboard
[11:40] <tester56> hi!, yet another bug I ran into recently in kde 4.11: sometimes the window content of all windows is blanked when applying settings: for example  open task switcher dialog change a setting, cklick apply and all your windows will be blank
[11:41] <apachelogger> I recommend filing a bug at bugs.kde.org
[11:47] <shadeslayer> yofel: erk
[11:47] <shadeslayer> yofel: no 4.11 for Quantal / Precise then
[11:47] <jdrab> hi guys are there any plans to include "firefox addon for kwallet" ? maybe as a dependency for kubuntu-firefox-installer?
[11:48] <tester56> shadesplayer: i am on saucy
[11:48] <smartboyhw> tester56, hey, sessionk is now in Neon
[11:48] <tester56> nice :D
[11:49] <Riddell> smartboyhw: simon uploaded!
[11:49] <smartboyhw> Riddell, thank you!
[11:49] <Riddell> apachelogger: aren't the kwallet patches upstream?
[11:49] <Tm_T> finally I got some china-made recharger for the ibook
[11:49] <smartboyhw> Riddell, you did fix what shadeslayer gave you?
[11:49] <tester56> is anybody in the mood to test if they can reproduce this ? then I'll file a bug
[11:49] <Riddell> smartboyhw: I took what you gave me and fixed it
[11:49] <smartboyhw> Riddell, great:)
[11:50] <smartboyhw> Oh, yofel's back
[11:50] <yofel> shadeslayer: right, they'll have to live with pykde 4.9 as far as I see :/
[11:50] <Riddell> jdrab: much of the firefox integration stuff had to be removed and can now only be found in the blue-shell PPA
[11:50] <Riddell> tester56: what needs tested?
[11:50] <smartboyhw> yofel, how did the new .install files go?
[11:51] <smartboyhw> ah, you're test-building
[11:51] <yofel> need fixing, which is what I'm doing now
[11:51] <jdrab> Riddell: well that's sad :[ ty
[11:51] <smartboyhw> yofel, OK
[11:51] <shadeslayer> yofel: didn't think of this before I started -.-
[11:52] <shadeslayer> yofel: and 4.9 was enough for KDE 4.10?
[11:52] <shadeslayer> *pykde4 4.9
[11:52] <yofel> well, it worked
[11:52] <tester56> Riddell: If for e.g. changing a setting in Task Switcher and applying produces alle windows going blank / black
[11:52] <smartboyhw> yofel, why it shows so.2.0.2? -.-
[11:52] <yofel> shadeslayer: you should've checked what packages were removed before just copying the release package list for the backports
[11:52]  * smartboyhw never got THAT error during build
[11:52] <yofel> 2.0.1
[11:53] <smartboyhw> yofel, dh_install: libkgapi2-2 missing files (usr/lib/*/libkgapi2.so.2.0.2), aborting
[11:53] <smartboyhw> .............
[11:53] <Riddell> tester56: I changed from cover switch to flip switch, clicked apply, all works good
[11:53] <shadeslayer> yofel: true
[11:53] <Riddell> tester56: I would guess it's graphics card specific?
[11:53] <shadeslayer> No KDE 4.11 for Quantal/Precise then
[11:54] <Riddell> shadeslayer: quantal in staging PPA says /topic
[11:54] <yofel> pykde you mean
[11:55] <shadeslayer> yofel: but then alot of things depend on pykde4 4.10?
[11:55] <shadeslayer> like kate I think
[11:55] <yofel> they do depend on pykde, but do they need 4.10?
[11:57] <tester56> Riddell: I'll figure out later
[11:57] <tester56> I am on nvidia-319 proprietary driver
[11:58] <Riddell> tester56: mm I'm on Intel, I suspect that might be significant
[11:59] <tester56> i'll try nouveau driver later
[11:59] <yofel> would need to check, I'm on nvidia-319 too but didn't notice any grave rendering issues
[11:59] <yofel> (if anything the only one I had was caused by nvidia-310)
[12:00] <tester56> yofel: have you tried changing and applying a setting in Task Switcher?
[12:00] <yofel> that's where again?
[12:01] <tester56> seach task switcher in kickoff
[12:01] <tester56> switch for example the visualitzation method
[12:04] <Riddell> how do you switch between nvidia and nouveau?
[12:04] <tester56> booting a live cd ;-)
[12:04] <yofel> hm, no, that's fine here it seems
[12:04] <tester56> yofel: very weired
[12:05] <tester56> I'll reinstall my nvidia driver
[12:06] <yofel> what do you mean with "blank" btw.?
[12:06] <yofel> the window contents are black?
[12:06] <tester56> yeah
[12:06] <shadeslayer>  python-kde4-dev : Depends: python-kde4 (>= 4:4.9.4-0ubuntu0.1) but it is not going to be installed
[12:06] <shadeslayer> why that sounds like fun
[12:06] <tester56> and some windows are 100% transluent
[12:06] <yofel> I got that when changing the display configuration back with nvidia-310, doesn't happen anymore with 319
[12:07] <yofel> the translucent part I never saw
[12:07] <smartboyhw> !screenshot | tester56
[12:07] <smartboyhw> I think that will be better for us to understand the situation:)
[12:07] <Tm_T> hey anything particular I should test on PPC ?
[12:07] <smartboyhw> Tm_T, you got your PPC power cord back?
[12:07] <Riddell> we still have powerpc?
[12:08] <smartboyhw> Yay, we don't need to depend on Lubuntu PPC testers anymore:P
[12:08] <Tm_T> smartboyhw: indeed I bought some china made power supply
[12:08] <smartboyhw> Tm_T, :O
[12:08]  * smartboyhw warns Tm_T that it will explode one day:P
[12:08] <Tm_T> finally found a cheap one
[12:08] <Tm_T> smartboyhw: so will I ... wait what
[12:09] <smartboyhw> yofel, thanks for fixing, it builds now:)
[12:09]  * smartboyhw hates powerpc actually
[12:09] <smartboyhw> Making developers and packagers having to spend time making it work on powerpc
[12:11] <tester56> okay i have found the reason: i am using a script that install all my packages on a new install ... i seem to have used an old version this time that install nvidia 304 ...
[12:11] <yofel> I guess there's enough people that still use it
[12:11] <tester56> sorry for the wrong informations
[12:11]  * tester56 is using nvidia-304 actually
[12:12] <shrini> Riddell: hi
[12:12] <shrini> how can i contribute to kde or kubuntu by testing?
[12:12] <shrini> is kde uses autopilot for testing?
[12:13] <shadeslayer> shrini: I started writing some autopilot scripts
[12:13] <shadeslayer> needs more love though
[12:13] <shadeslayer> shrini: https://code.launchpad.net/~rohangarg/+junk/autopilot
[12:13] <shrini> shadeslayer: awesome
[12:13] <smartboyhw> shrini, we also have image testing pre-release:)
[12:14] <Riddell> shrini: mostly hang around on the irc channel until something needs testing
[12:14] <Riddell> shrini: want to be added to the !testers call?
[12:14] <smartboyhw> How long have we NOT used !testers?
[12:14] <Riddell> I've used it plenty
[12:14] <shrini> Riddell: what is that call?
[12:14] <Riddell> shrini: a ping to anyone who's offered to help test things
[12:14] <smartboyhw> shrini, it calls testers when needed:)
[12:15] <yofel> shadeslayer: that test would fail on my system btw. ^^
[12:15] <shadeslayer> yofel: what
[12:15] <shadeslayer> :O
[12:15] <shadeslayer> wfm
[12:15] <smartboyhw> :O
[12:15] <yofel> is alt+f1 the default now? Because for me it's "None"
[12:15] <shadeslayer> but then I'm on saucy
[12:15] <shadeslayer> oh
[12:15] <shrini> great
[12:15] <shadeslayer> Wasn't alt+f1 always the default
[12:15] <shrini> Riddell: please add me
[12:15] <smartboyhw> Yeah, we got a new tester!
[12:15] <shadeslayer> ahh
[12:15] <shrini> :-)
[12:15] <smartboyhw> How long have we not used !ninjas BTW?
[12:15] <shadeslayer> yofel: maybe you added the plasmoid manually?
[12:15] <shrini> is it manual test or need autopilot script?
[12:16] <shadeslayer> because the Kubuntu plasma init script sets it to alt + f1
[12:16] <smartboyhw> shrini, manual normally, if we use !testers currently:)
[12:16] <Riddell> !testers
[12:16] <smartboyhw> Yes, like that
[12:16] <smartboyhw> :)
[12:16] <Riddell> ubottu: no testers is Help is needed in #kubuntu-devel. Please ping Riddell, yofel, soee, Tm_T, shadeslayer, BluesKaj, James147, smartboyhw, Quintasan, lordievader, shrini for information.
[12:16] <tester56> Riddell: would be nice if you could add me too :D
[12:16] <Riddell> 13:16 <ubottu> Your edit request has been forwarded to #ubuntu-ops.  Thank you for your attention to detail
[12:17] <Riddell> ubottu: no testers is Help is needed in #kubuntu-devel. Please ping Riddell, yofel, soee, Tm_T, shadeslayer, BluesKaj, James147, smartboyhw, Quintasan, lordievader, shrini, tester56 for information.
[12:17] <Riddell> 13:17 <ubottu> Your edit request has been forwarded to #ubuntu-ops.  Thank you for your attention to detail
[12:17]  * smartboyhw wonders why the hell is shadeslayer not in the !testers factoid...
[12:17] <smartboyhw> Riddell, I don't think so....
[12:17] <shadeslayer> I am
[12:17] <BluesKaj> Riddell, I assume that test call was for shrini 's benefit and is not real
[12:17] <yofel> shadeslayer: hm, dunno, but then again this session is 3 years old. It sadly doesn't tell me whether I changed it or not
[12:17] <Riddell> smartboyhw: he is
[12:17] <Riddell> BluesKaj: right, sorry for the noise
[12:17] <smartboyhw> Riddell, I mean, the factoid
[12:17] <shrini> thanks for adding me
[12:17] <smartboyhw> You miss one thing
[12:17] <shadeslayer> yofel: heh, either way, just set it to alt + f1 :P
[12:17] <Riddell> shrini: want to test owncloud?
[12:17] <BluesKaj> Riddell, np :)
[12:17] <shrini> sure
[12:18] <shrini> will love to do it
[12:18] <shrini> i am new to testing
[12:18] <Riddell> shrini: what release are you on?
[12:18] <shrini> guide me on what to do
[12:18] <shadeslayer> shrini: feel free to contribute to the autopilot tests if you have some experience there
[12:18] <shrini> i am on Linux Mint 15 Olivia
[12:18] <shrini> shadeslayer: sure
[12:18] <shadeslayer> and hurray, Firefox KDE updated
[12:18] <shrini> i am learning autopilot
[12:18] <shadeslayer> cool :)
[12:18] <yofel> shadeslayer: why are you trying to open it twice btw.?
[12:19] <Riddell> shrini: ah, harder to test kubuntu without being on it
[12:19] <shrini> Riddell: i am Linux Mint 15 Olivia
[12:19] <shadeslayer> yofel: first call is to open, second call is to close it
[12:19] <smartboyhw> !no testers-#kubuntu-devel is <reply> Help is needed in #kubuntu-devel. Please ping Riddell, yofel, soee, Tm_T, shadeslayer, BluesKaj, James147, smartboyhw, Quintasan, lordievader, shrini, tester56 for information.
[12:19] <yofel> aah
[12:19] <smartboyhw> Riddell, that's the one
[12:19] <smartboyhw> You need <reply>
[12:19] <shadeslayer> yofel: though I think mouse support is broken, atleast in saucy
[12:19] <shrini> Riddell: oh. is there any difference on kubuntu and mint wih kde?
[12:19] <shrini> I am on KDe only
[12:19] <smartboyhw> shrini, Linux Mint!?:O
[12:20] <shrini> smartboyhw: yes
[12:20] <Riddell> shrini: sure, they're different distros, mint will add or change a load of stuff
[12:20] <shrini> Riddell: okey
[12:21] <shrini> will install kubuntu and update you all
[12:23] <smartboyhw> yofel, aroof works on i386 too:)
[12:24] <Tm_T> smartboyhw: factoid applied
[12:25] <shrini> I am intestested in kde development too
[12:25] <shrini> but not a c/c++ guy
[12:25] <Riddell> shrini: find a bug and fix it :)
[12:25] <shrini> know python
[12:25] <shadeslayer> yofel: care to look at okular while I fix kdepim-runtime?
[12:25] <smartboyhw> Tm_T, thanks:)
[12:26] <shrini> is it any possibloe to contreibute via python?
[12:26] <shadeslayer> shrini: sure
[12:26] <smartboyhw> shrini, try packaging:P
[12:26] <shrini> where to start?
[12:26] <smartboyhw> LOL
[12:26] <Riddell> shrini: find a bug in gdebi, or jockey, or usb-creator-kde and fix it :)
[12:26] <shrini> Riddell: rite
[12:26] <shadeslayer> actually, wasn't usb-creator-kde pretty bugged?
[12:26] <Riddell> yeah I can point out obvious bugs in usb-creator-kde
[12:26] <shrini> is there any page listing applications written in python and qt?
[12:26] <smartboyhw> shadeslayer, it's not as buggy as usb-creator-gtk
[12:27] <Riddell> shrini: apt-cache rdepends python-kde4
[12:27] <smartboyhw> We have complained about it for at least a WHOLE YEAR
[12:27] <smartboyhw> yofel, wait, let me get you the bug number
[12:27] <yofel> smartboyhw: what was up with the tests again?
[12:28] <yofel> ah
[12:28] <yofel> I remember
[12:28] <smartboyhw> yofel, :)
[12:28] <smartboyhw> 1196977
[12:28] <shrini> Riddell: yes. that command gives some list
[12:28] <shrini> will check for the
[12:28] <shrini> m
[12:28] <Riddell> shrini: the most important thing is to hang around in here, irc is the main means of communication :)
[12:28] <smartboyhw> yofel, ^
[12:28] <shrini> where to check the availalebus?
[12:28] <shrini> sure
[12:28] <Riddell> shrini: availalebus?
[12:28] <shrini> available bugs?
[12:29] <yofel> smartboyhw: just to give it a try
[12:29] <shrini> where to check the available bugs for any given software?
[12:29] <Riddell> shrini: depends on the app, gdebi jockey usb-creator-kde are ubuntu things so they're in launchpad.net/ubuntu
[12:29] <smartboyhw> yofel, +1
[12:29] <shrini> okey
[12:29] <shrini> fine
[12:29] <shrini> moving to a meeting noiw
[12:29] <shrini> will meet you all
[12:30] <shrini> after isntalling kubuntu
[12:30] <shrini> today night
[12:30]  * smartboyhw is trying to figure out what KDE project should he start on programming
[12:30] <tester56> sessionk :D
[12:31] <smartboyhw> tester56, meh
[12:31] <tester56> would be very sensible
[12:31] <smartboyhw> tester56, really? Seriously? Are you sure?
[12:32] <tester56> sure ... a fast starting plasma session is always sensible
[12:32] <Riddell> smartboyhw: no, but ask dantii about what makes sense in terms of looking at it (he was talking about it in here recently)
[12:33] <smartboyhw> Riddell, looking at it = ?
[12:33] <Riddell> Subject: [Announce] Qt 5.1 released
[12:33] <Riddell> smartboyhw: if it makes sense to have it in a PPA or something, I don't know
[12:34] <smartboyhw> Riddell, \o/ for the first one, OK let me ask for the second
[12:34] <tester56> right now it is not ready as it does not start kcm modules
[12:34] <smartboyhw> We do have already neon though
[12:34] <tester56> so you don't get a fully working plasma at the moment without further changes
[12:35] <smartboyhw> Riddell, probably not a PPA, just use neon
[12:35] <smartboyhw> If one day it's stable enough, I can provide PPAs.
[12:36] <smartboyhw> and probably, package it into Ubuntu.
[12:36] <tester56> but it would definitely be sth. that makes sense to a wider range of users
[12:36] <tester56> (imho)
[12:37] <tester56> dantii told me right now he is very busy with his email client ...
[12:38] <tester56> and there are no other devs yet for sessionk
[12:38] <tester56> right now
[12:38] <smartboyhw> tester56, the first patch I would provide is actually a README. (LOL)
[12:38] <tester56> lol
[12:39] <smartboyhw> yofel, great thanks!
[12:40] <shadeslayer> LP is soooo slow
[12:41] <smartboyhw> shadeslayer, why?
[12:41] <shadeslayer> too many packages in the PPA
[12:42] <smartboyhw> shadeslayer, which? Staging PPA?
[12:42] <shadeslayer> yes
[12:42] <shadeslayer> times out
[12:42]  * smartboyhw thinks they should do some PURGING
[12:42] <smartboyhw> s/they/we/
[12:42] <kubotu> smartboyhw meant: "thinks we should do some PURGING"
[12:45] <smartboyhw> Riddell, um armhf simon wasn't fixed
[12:45] <Riddell> smartboyhw: what wasn't fixed about it?
[12:45] <smartboyhw> Riddell, qreal again
[12:46] <smartboyhw> https://launchpadlibrarian.net/144079254/buildlog_ubuntu-saucy-armhf.simon_0.4.1-0ubuntu1_FAILEDTOBUILD.txt.gz
[12:46] <Riddell> error: no matching function for call to 'qBound(qreal, double&, qreal)'
[12:46] <Riddell> hmm, the usual
[12:47] <smartboyhw> guys, has anyone here tried out KLyDE yet?
[12:47] <yofel> smartboyhw: I'll upload
[12:47] <smartboyhw> yofel, greato
[12:47] <shadeslayer> ENOTIME
[12:48] <smartboyhw> shadeslayer, for wut?
[12:48]  * tester56 upgraded to nvidia-319 and the problem with black windows is still there! :-(
[12:48] <shadeslayer> to do anything apart from regular Kubuntu stuff
[12:48] <tester56> yofel: did you do a new install or just upgrading?
[12:48] <smartboyhw> shadeslayer, :)
[12:48] <yofel> upgrade here
[12:49] <shadeslayer> need moar time
[12:49] <tester56> yofel: nvidia-319 or nvidia-319-dev package?
[12:49] <shadeslayer> ETRTS
[12:49] <yofel> nvidia-319. I don't have the dev stuff
[12:50] <tester56> are you using the default repo version or xorg-edgers ?
[12:51] <yofel> default
[12:51] <tester56> weired ... me too
[12:51] <tester56> latest upgrades?
[12:52] <yofel> A day old I think, I didn't get to updating yesterday
[12:53] <tester56> I'm out of ideas now
[12:56] <tester56> the windows need to be resized to make the content appear again
[12:56] <tester56> or i need to apply settings a second time
[12:58] <shadeslayer> yofel: do you think we can somehow add ordering by build status to the build page
[12:58] <shadeslayer> with some fancy js
[12:59] <shadeslayer> so that we can order the FTBFS builds at the top
[13:00] <yofel> possibly, but I can't tell you offhand how
[13:00]  * yofel hides, bbl
[13:01] <yofel> The signer of this package is lacking the upload rights for the source package, component or package set in question.
[13:01] <yofel> yaay
[13:02] <tester56> yofel: does not happen in project-neon session
[13:02] <yofel> :/
[13:02] <tester56> why :/?
[13:02] <yofel> no idea, maybe it's something in the cache? or some old setting?
[13:02] <yofel> what rendering option are you using for kwin?
[13:03] <yofel> I'm on OpenGl 3.1 / Raster
[13:03] <tester56> tried them all opengl 2.0, 3.0 all vsync options
[13:03] <yofel> then I'm clueless
[13:03] <tester56> even tried guest session (in case it was cache) did happen there too
[13:03] <tester56> but in project neon it does not happen
[13:04] <tester56> so if it was a bug it's fixed upstream
[13:08] <yofel> could some MOTU please sponsor https://launchpad.net/~yofel/+archive/ppa/+files/libkgapi_2.0.1-0ubuntu1%7Eppa1.dsc - thanks
[13:10] <shadeslayer> yofel: if either one of us were MOTU's this wouldn't have been an issue :P
[13:10] <shadeslayer> didn't we resolve to apply for MOTU status at some point?
[13:10] <yofel> true...
[13:10] <yofel> we did, but things came up and...
[13:11] <shadeslayer> hmm
[13:20] <Riddell> yofel: onto it
[13:21] <Riddell> smartboyhw: yofel: still going for the two -dbg packages?
[13:24] <smartboyhw> Riddell, yeah
[13:26] <smartboyhw> This libkgapi is going to cause a lot of NEW :P
[13:29] <Riddell> uploaded libkgapi
[13:30] <smartboyhw> Riddell, \o/ thanks
[13:39] <tester56> does anyone know the GLX_EXT_buffer_age state in kwin?
[13:42] <tester56> does not seem to be implemented right now
[13:43] <tester56> btw: i am experiencing some kwin performance regressions on saucy ... kwin uses heck a lot more cpu (using nvidia proprietary)
[13:43] <tester56> watching videos (not fullscreen)
[13:44] <tester56> i tried disabeling sync to vblank ... did not change the behaviour ... opengl backend does not seem to matter
[13:48] <smartboyhw> yofel, er, you still didn't add the packaging bug for me;(
[13:48] <smartboyhw> I think I will have to manually close it then
[13:52] <yofel> ooops
[13:52] <shadeslayer> tester56: please report a bug upstream
[13:53] <tester56> okay i have found the reason ... it is the new sync to vblank
[13:53] <shadeslayer> bah
[13:53]  * shadeslayer waves fist at okular
[13:53] <tester56> only when sync to vblank is disabled the cpu usage reaches normal levels
[13:54] <tester56> als sync to vblank options are cpu intense with automatic being the worst
[13:55] <Riddell> !testers | test owncloud update on raring http://ec2-54-224-232-46.compute-1.amazonaws.com/owncloud/
[13:55] <Riddell> hmm
[13:55] <Riddell> !testers
[13:55] <smartboyhw> Riddell, how!?!?!?!!?
[13:55] <soee> oh you, again?
[13:56] <smartboyhw> Riddell, username, password?
[13:56] <tester56> the new sync to vblank options are more reliable than the old implementation bug ... but consume too much cpu
[13:56] <shadeslayer> Riddell: username / pw?
[13:56] <Riddell> jr/hello
[13:56] <shadeslayer> that reminds me
[13:56] <soee> tester56, black window content area ?
[13:56] <shadeslayer> why is your root password on your machine hello -.-
[13:57] <smartboyhw> shadeslayer, LOL
[13:57] <tester56> soee: no ... sync to vblank consuming too much cpu
[13:57]  * smartboyhw has uploaded libkfbapi 1.0 to ownCloud (for fun:P)
[13:58]  * shadeslayer uploads a blurry pic of spain
[13:58] <smartboyhw> shadeslayer, :I
[13:59] <smartboyhw> Whoa, :I that's a nice symbol!
[13:59] <smartboyhw> :A
[13:59] <smartboyhw> :B
[14:00]  * tester56 uploaded snapshot1.png
[14:00] <tester56> c ya!
[14:04] <Riddell> shadeslayer, smartboyhw: bits I changed were using the built in pdfjs, timepicker, fontawesome, php-aws-sdk, php-sabre-dav, php-sabre-vobject, php-seclib
[14:04] <Riddell> so check those work if you can work out how
[14:04] <shadeslayer> ah just a sec @ pdf.js
[14:04] <smartboyhw> ?
[14:14] <shadeslayer> Riddell: pdfjs doesn't work
[14:17] <Riddell> shadeslayer: does for me using firefox
[14:17] <shadeslayer> hm, sec
[14:17] <Riddell> http://ec2-54-224-232-46.compute-1.amazonaws.com/owncloud/index.php/apps/files  click on FCC
[14:17]  * shadeslayer checks his owncloud instance
[14:18] <Riddell> and rekonq
[14:19] <Riddell> right, same thing on quantal
[14:19] <Riddell> !testers
[14:19] <Riddell> http://ec2-107-21-174-83.compute-1.amazonaws.com/owncloud/
[14:19] <Riddell> root/a  is the mysql password
[14:19] <smartboyhw> Riddell, wait, what's pdfjs supposed to do?
[14:20] <smartboyhw> Riddell, database name?
[14:20] <Riddell> smartboyhw: view PDFs
[14:20] <Riddell> smartboyhw: whatever you want I'd think
[14:20] <smartboyhw> Riddell, it works on FF
[14:21] <Riddell> smartboyhw: what does?
[14:21] <smartboyhw> Database name: owncloud_quantal_jr
[14:21] <smartboyhw> Riddell, pdfjs
[14:23] <smartboyhw> Uploaded a .jpeg to quantal (actually, that's Nicholas Skaggs)
[14:23] <Riddell> smartboyhw: what username/pass did you use?
[14:23] <smartboyhw> Riddell, same as raring
[14:32] <smartboyhw> Archive builds don't really build fast
[14:33] <smartboyhw> libkgapi saucy powerpc build start in 2 hours
[14:34] <Riddell> powerpc is always slow, but then nobody cares about it
[14:36]  * smartboyhw yawns
[14:36] <smartboyhw> Looks rather relaxing now:)
[14:37] <shadeslayer> bah
[14:37] <shadeslayer> yofel: any recommendations on what to do with okular
[14:37] <shadeslayer> because we'll need to remove the plasma okular app
[14:37] <shadeslayer> and also somehow remove it from the control file
[14:39] <yofel> control file I think not, it would be an empty package
[14:39] <yofel> just remove the build-dep and the install file
[15:13] <Riddell> who knows about apache
[15:13] <Riddell> apache in precise is complaining about line 6 http://paste.kde.org/788342/
[15:13] <Riddell> not unreasonably I'd say
[15:28] <lordievader> Good afternoon.
[15:34] <shadeslayer> hmm okay
[15:37] <shadeslayer> yofel: btw I need a sed tip for also deleting the new line
[15:38] <yofel> what new line?
[15:38] <shadeslayer> ed -e 's/plasma-active-dev,//g' -i debian/control  leaves me with http://paste.kde.org/788360
[15:38] <shadeslayer> line 25
[15:39] <yofel> see e.g. kde-runtime hook line 5
[15:39] <yofel> sed has a delete line command
[15:41] <Riddell> shr
[15:41] <Riddell> tsk
[15:42] <shadeslayer> aha
[15:44] <kubotu> ::qt-bugs:: [1177823] qdbus needs qtchooser dependency to work @ https://bugs.launchpad.net/bugs/1177823 (by Patola)
[16:01] <Riddell> ScottK: owncloud in bug 1079150 for SRU approval
[16:07] <shadeslayer> &*^&^
[16:07] <shadeslayer> [ 91%] make[4]: *** No rule to make target `/usr/lib/libboost_thread-mt.so', needed by `resources/kolabproxy/akonadi_kolabproxy_resource'.  Stop.
[16:07] <shadeslayer> !find usr/lib/libboost_thread-mt.so quantal
[16:08] <shadeslayer> but ... but ... but libboost-thread1.49-dev is pulled
[16:08] <shadeslayer> oh
[16:08] <shadeslayer> suggested packages
[16:08] <shadeslayer> -.-
[16:08] <smartboyhw> LOL
[16:08] <smartboyhw> ...-...---.---.-.----.-.-.-.--.-----....-..-.-.-.-
[16:08] <smartboyhw> Morse code!
[16:08] <smartboyhw> (LOL)
[16:37] <shadeslayer> smartboyhw: that stuff is boring
[16:37] <smartboyhw> Back here shadeslayer please help to complete http://qa.kubuntu.co.uk/ninjas-status/build_status_4.10.5_raring.html :P
[16:37] <shadeslayer> also, seems like only kdeplasma-addons is remaining?
[16:37] <smartboyhw> shadeslayer, well that pleases the raring users, we got people in G+ asking already
[16:37] <smartboyhw> shadeslayer, dunno, there might be some more:P
[16:37] <shadeslayer> I don't see any red
[16:38] <shadeslayer> apart from kdeplasma-addons
[16:38] <smartboyhw> shadeslayer, well red isn't the only standard
[16:39] <shadeslayer> too damn hot
[16:39] <shadeslayer> will do it tomorrow
[17:25] <Peace-> mmm there is somethin  of strange here
[17:25] <Peace-> just upgraded kubuntu and it did not boot
[17:26] <Peace-> grub just doesn't show up
[17:26] <Peace-> restored grub and it has been installed in the wrong partition i guess
[17:27] <Peace-> infact if i select restore windows etc etc it starts kubutnu with grub
[17:27] <Peace-> xD
[18:58] <aseny> hi everyone i am new here and i want a good place to start learning Kubuntu development
[19:17] <ScottK> Welcome aseny.