[00:11] <RainCT> wth is ftp://ftp.gnome.org/conspiracy/index.html? XDDD
[00:12] <jpds> Anyone know who uploaded: https://edge.launchpad.net/ubuntu/+source/emelfm2 ?
[00:13] <Laney> jpds: As in who sponsored it?
[00:13] <jpds> Laney: Yeah.
[00:14] <Hobbsee> oh dera.
[00:15]  * Hobbsee looks it up
[00:16] <jpds> Hobbsee: It was definiatly sponsored, cos the guy doesn't have upload rights.
[00:17] <Laney> jpds: dholbach
[00:17] <Hobbsee> the key was 059DD5EB
[00:17] <Hobbsee> actually, it doesn't look to be that bad.
[00:17] <Hobbsee> https://lists.ubuntu.com/archives/hardy-changes/2007-November/002095.html
[00:18] <Hobbsee> who knows why dholbach decided to allow him to use 3 changelog entries for the one entry, i've no idea
[00:18] <jpds> Ahh, right. bobbo ^
[00:18] <bobbo> ah, I bet it was from changes in REVU
[00:18] <Hobbsee> bobbo: ppa, most likely
[00:18] <bobbo> Hobbsee: yeah, something like, that
[00:19] <bobbo> rofl, I almost cried when I saw it :)
[00:19] <Hobbsee> based on the second changelog entry, anyway
[00:19] <Laney> It looks to be alright apart from the changelog though
[00:19] <Laney> from a scan of the diff
[00:19] <marnold> looks like all changelog entries were included in the .changes
[00:20] <marnold> but lp doesn't recognize it
[00:22] <marnold> which is odd
[00:36] <badzero> hallo ubuntu package-devs pleas merge this packet to newer version <IP_ADDRESS> http://packages.ubuntu.com/intrepid/vuze
[00:37] <marnold> oh and Laney ant changes are related to the multiuser patch so I'm not going to touch that and dh_links is ui selector
[00:38] <marnold> sorry
[00:38] <Laney> marnold: It's often good to list which files are touched by each change
[00:38] <Laney> debian/rules, debian/control: Do foo because bar
[00:41] <marnold> and badzero Ubuntu has patches against 3.1 so i don't think anybody is going to touch that until the person who made said patches merges them with 4.x
[00:42] <badzero> aha ok thx
[00:42] <marnold> thats not to say a new vuze4 package is out of the question
[00:43] <marnold> but motu-p2p should do that
[00:43] <marnold> he left :/
[00:44] <marnold> hate it when people leave when i'm talking
[00:45] <directhex> it's how the kids use irc these days
[00:45] <directhex> you;re lucky he stuck around long enough for you to actually be able to get an answer in
[00:48] <marnold> directhex, i know i run an IRC network thats only populated for 1hr/day, because of that
[00:49] <marnold> :(
[00:49] <directhex> evidently you're just not hip enough for the web 2.0 generation
[00:49] <directhex> they use their tweeters and friendfaces and yourspaces, not this irc nonsense!
[00:50] <marnold> I am supposedly a part of it so :( again
[00:51] <marnold> even my CS class is like that
[00:51] <marnold> i was explaining why somebody's for loop didn't work
[00:52] <marnold> and when i asked if he understood
[00:53] <marnold> he says "No, because you were talking to much"
[00:55] <directhex> they don't need to understand things, that's wikipedia's job!
[00:56] <directhex> well i never, a genuine NCommander!
[00:56] <marnold> and then he says "So whats the code to correct this?"
[00:56]  * NCommander fails to validate
[00:56] <NCommander> I'm not genuine at all :-P
[00:56] <Hobbsee> marnold: i thought that was where you gave them the wikipedia link, and said "read this first, then come back with questions"
[00:57] <directhex> Hobbsee, give a man a fire, he's warm for a day. set him on fire, and he's warm for the rest of his life!
[00:57]  * Hobbsee actually found wikipedia quite helpful this yera for one of her subjects - although perhaps that was because the lecturers, and hte lecture notes, weren't great.
[00:57] <Hobbsee> directhex: indeed!
[00:57] <marnold> no the Professor came in
[00:57]  * Hobbsee sets directhex on fire
[00:57] <directhex> or, erm, woman. i'm an equal-opportunity immolator.
[00:57] <Hobbsee> directhex: did I see you say you'd sent a mail to ubuntu-devel@?
[00:58] <marnold> gave him an earfull
[00:58] <directhex> Hobbsee, not recently. why?
[00:58] <Hobbsee> oh, good ;)
[00:58] <marnold> and then almost kicked him from the lab for swearing
[00:59] <marnold> he changed his major after that
[00:59] <marnold> :P
[01:08] <serialorder> Question that has been confusing me lately. How should one choose among: iceape-dev, seamonkey-dev, libxul-dev, xulrunner-1.9-dev ?
[01:09] <directhex> serialorder, 'ubuntu-mozillateam
[01:09] <serialorder> directhex, thanks
[01:09] <directhex> serialorder, generally speaking, is your package browser specific, or does it apply to all moz-based browsers?do you want to use your package on debian?
[01:11] <serialorder> it was a merge i was working on last week. It FTBFS because it depended on iceape-dev but when I changed it to depend on libxul-dev it built fine. Then as I investigated the various packages there seemed to be those four and each one recommended using another one rather than itself.
[01:12] <serialorder> but i will now go pester ubuntu-mozillateam
[01:14] <directhex> IIRC it should be xulrunner-dev (>= 1.9) | xulrunner-1.9-dev
[01:14] <directhex> for debian AND ubuntu joy
[01:15] <directhex> but don't quote me on that
[01:35] <vorian> ScottK: I've been in contact with the kdenlive folks.  It seems our FFmpeg is missing a few things, and there is also some libs missing from our MLT.
[03:37] <crimsun> does motu have an lp liaison again?
[03:38] <crimsun> if not, i'd like to propose someone =)
[03:38] <crimsun> oh wait, this was answered at uds. nevermind.
[03:39] <Hobbsee> crimsun: I believe it does, but i'm not sure if it's by name only
[03:39] <Hobbsee> or if he's still interested in doing it
[04:28] <hyperair> does anyone have time to revu? http://revu.ubuntuwire.com/details.py?package=codelite
[04:36] <nhandler> hyperair: I'll review it again tomorrow
[04:53] <hyperair> nhandler: okay thanks
[05:33] <ScottK> vorian: OK.  For ffmpeg, siretart is the one to talk to.
[08:30] <AnAnt> Hello, how do I know the list of motus ? or UUS ?
[08:33] <iulian> AnAnt: launchpad.net/~motu/+members and ~/universe-contributors/+members.
[08:38] <AnAnt> thanks
[09:04] <huats> Silly question, but I have installed a jaunty alpha  to test my packages in a vm, and I notice that there is an empty xorg.conf... is it normal ?
[09:08] <persia> huats, Yes, and intentional.  Everything you need should be autodetected.
[09:08] <huats> persia: yeah I assumed :)
[09:09] <huats> persia: hello btw
[09:09] <huats>  :)
[09:09] <huats> I was just wondering since the resolution is very low
[09:09] <huats> and I'd like to have a bigger one...
[09:13] <_ruben> huats: you might need an extra/3rd-party driver, depending the virtualization product you use
[09:13] <huats> _ruben: hum
[09:13] <huats> _ruben: may be indeed
[09:13] <didrocks> huats: for virtualbox, you need to add some extra values (it set it up when needed)
[09:13] <didrocks> hi btw too ;)
[09:14] <huats> but it was working fine as it (I use kvm)
[09:14] <huats> _ruben: but I'll have a look in that direction :)
[09:15] <_ruben> no experience with kvm myself, but i dont expect it to require additional drivers, could be wrong though .. might be a (k)vm setting as well
[09:17] <persia> huats, For some virtualisation solutions, you can just use xrandr to change the resolution.
[09:36] <AnAnt> Hello, can someone please bug 311763 ?
[13:42] <AnAnt> Hello, can someone review bug 311763 ?
[15:33] <AdamDH> if I am unpacking my source inside the rules file, do I have to move the source any where after that? it would just be in a packagename.version directory
[15:34] <pmjdebruijn> AdamDH: that's bad practise...
[15:35] <AdamDH> i am unpacking upstream source then applying a patch
[15:35] <pmjdebruijn> AdamDH: I think the fontforge package does that as well, you might want to look at that... if you _must_...
[15:35] <AdamDH> this is my second package so any advice would be welcomed
[15:35] <pmjdebruijn> AdamDH: yeah, then you don't need to unpack the sources in the rules file
[15:35] <pmjdebruijn> AdamDH: why do you need to unpack in the rules file?
[15:36] <AdamDH> dont you need to unpack so you can apply a patch? I am just shipping the upstream .ta.gz for binutils
[15:36] <pmjdebruijn> huh
[15:36] <pmjdebruijn> no?
[15:36] <pmjdebruijn> AdamDH: have you read up on dpatch?
[15:36] <pmjdebruijn> AdamDH: why are you packaging binutils? it is already packaged...
[15:37] <AdamDH> because I am packaging a cross compiler, so I apply a patch to the binutils source to add msp430 support like the AVR project does
[15:37] <pmjdebruijn> uh
[15:38] <pmjdebruijn> AdamDH: why not take the current package, and modify that. instead of starting from scratch?
[15:38] <pmjdebruijn> AdamDH: http://packages.ubuntu.com/jaunty/binutils-avr
[15:39] <pmjdebruijn> AdamDH: there are several binutils-XXXX already package... take of one those... and modify to your liking
[15:39] <AdamDH> i have been playing about with packing on and off for two days and every example package I look at does something diffrent in rules, even if its the same package
[15:40] <AdamDH> the binutils-avr package does:
[15:40] <AdamDH> binutils-2.18.tar.bz2:
[15:40] <AdamDH>         ln -s /usr/src/binutils/binutils-*.tar.bz2 binutils-2.18.tar.bz2
[15:40] <AdamDH> so there is a symbolic link to the upstream source, is this the correct way to do this/
[15:40] <AdamDH> ?
[15:43] <mgdm> AdamDH: is that for 8-bit AVRs or AVR32?
[15:43] <pmjdebruijn> AdamDH: you're not particularly starting with the easier thing to package
[15:43] <pmjdebruijn> AdamDH: I have no clue on how to "best" handle this
[15:43] <AdamDH> the cross compiler I am working on is for the MSP430 microcontrollers
[15:43]  * pmjdebruijn is not familiar with building crosscompilers
[15:43]  * mgdm has been swearing at them recently
[15:44] <mgdm> but I didn't try to package it
[15:44] <AdamDH> well I know how it all works from a source install
[15:45] <AdamDH> mgdm: you have worked with the MSP430s?
[15:45] <mgdm> AdamDH: I haven't, I've been fiddling with an AVR32 device lately
[15:47] <mgdm> an NGW100
[15:49] <AdamDH> pmjdebruijn: the cross compiler is easy to get working from source, just wanted to stop doing a source install on my systems and package it, basically you have a set of configure arguments, thats easy to run in  a package, and a patch I have, you apply the patch to the upstream source, confiure make make install thats all there is to it, oh and some cleaning about
[15:50] <AdamDH> so my package was going to have the upstream binytils-2.18.tar.gz I was going to unpack that inside rules and apply the patch, simular to the udev package, is this not the best way to do it?
[15:53] <AdamDH> mgdm, running embedded linux on that?
[15:53] <mgdm> AdamDH: yep
[15:57] <loic-m> Is there anything else to do for a backport request, after filing the bug and ensuring the packages build fine and run ok (in the case of a package that didn't exist in previous versions)?
[15:58] <Laney> I think you should set the bug to confirmed, but IANAbackport
[15:58] <Laney> er
[15:59] <Laney> grr, I can't repro this rcbug
[16:05] <AnAnt_> Hello, can someone review bug 311763 ?
[16:05] <loic-m> For backport, the Ubuntu wiki says that for anyone wanting to help, the 3rd step is "Helping to build test packages, or feed package requests to the PPA "
[16:06] <AnAnt_> I have already uploaded the new source package to the bug report
[16:06] <loic-m> How does one feeds "package requests to the PPA"? Is it personnal PPA or a special PPA?
[16:08] <loic-m> in other words, is "Backports Tester Team PPA" already done?
[16:10] <AdamDH> mgdm, done some embeded work, looking at getting a beagleboard next
[16:10] <AdamDH> did you homebrew your dev board?
[16:11] <mgdm> AdamDH: Nah, it's an Atmel NGW100 reference design
[16:11] <mgdm> I fancy a Beagleboard too, but i wanted something with Ethernet first
[16:11] <AdamDH> same thats what is putting me off
[16:11] <AdamDH> been looking at the gumstixs
[16:13] <mgdm> I've seen a real Beagleboard decoding Big Buck Bunny at big resolution, it was cool :)
[16:19] <AdamDH> the beagle boards have alot of potential, if they added ethernet on board it would be ideal
[16:20] <mgdm> I was slightly confused that they don't have it on board - otherwise it'd be (theoretically) great for a cheap MythTV front-end or some such, I'd imagine
[16:20] <mgdm> Disclaimer: I might be talking rubbish
[16:21] <AdamDH> myth would run fine on it I think
[16:24] <DRebellion> DktrKranz, hey! Didn't get a chance to thank you on the ACK for cifer, so thanks :D
[16:25] <DktrKranz> DRebellion, you're welcome ;)
[16:25]  * sebner feels ignored :P
[16:25] <AdamDH> my next myth front end would probally be a cheap mac mini self upgraded
[16:26] <DktrKranz> sebner, you feel ignored, me feels unpaid ;)
[16:26] <AdamDH> what does dh_testdir actully do?
[16:26] <sebner> DktrKranz: ahahahaha
[16:26] <AnAnt_> DktrKranz: are you a UUS ?
[16:27] <DktrKranz> AnAnt_, yep
[16:28] <AnAnt_> DktrKranz: can you upload the package in this bug 311763
[16:28] <DRebellion> sebner, Dec 19 21:55:23 <DRebellion>	sebner, thanks for the advocation :D
[16:28] <DRebellion> :P
[16:28]  * DktrKranz looks
[16:28] <sebner> DRebellion: xD
[16:29] <DktrKranz> sebner, you always want greets twice... bad boy
[16:29] <sebner> DktrKranz: better than money :P
[16:29] <DktrKranz> I can't go supermarket with "greets"
[16:32] <sebner> DktrKranz: you can greet the supermarket employees :P
[16:33] <AdamDH> does any one know to any packages where patches are applied without dpatch?
[16:33] <DktrKranz> AdamDH, do you look for a specific patch system, or just a "custom" one?
[16:33] <nhandler> AdamDH: https://wiki.ubuntu.com/PackagingGuide/PatchSystems lists a few
[16:34] <AdamDH> just playing around at the moment seeing whats the best way to package this
[16:35] <AdamDH> thanks for the link
[16:35] <nhandler> You're welcome
[16:35] <DktrKranz> quilt *cough*
[16:35] <sebner> AdamDH: of course quilt :P
[16:37] <AdamDH> i am looking at the rules inside binutils-avr as this is exactley the same way the binutils-msp package should work the one I am creating, can any one just explain a few lines to me? binutils-2.18.tar.bz2 $(patched) what is $(patched)?
[16:37] <AdamDH> its in the configure section:
[16:39] <DktrKranz> AdamDH, I played with it a bit
[16:39] <AdamDH> ah its part of debhelper I think
[16:39] <DktrKranz> binutils-avr uses vanilla binutils source package, taken from binutils-src
[16:40] <DktrKranz> it unpacks it in a directory and applies patches using a custom routine
[16:41] <DktrKranz> probably because it was too complex to let quilt/dpatch/whatever to work properly that way
[16:41] <AdamDH> i played with the patch systems nothing seemed to work so I decided to apply them by hand
[16:42] <AdamDH> seems to work better
[16:42] <DktrKranz> AdamDH, are you interested in binutils-msp?
[16:42] <DktrKranz> I thougth it was OK, probably I was wrong
[16:43] <AdamDH> is there a binutils-msp?
[16:44] <AdamDH> i am packaging the whole mspgcc tool chain at present
[16:44] <DktrKranz> mh... it was probably a different name, then
[16:52] <AdamDH> i understand whats going on and whats required its just the paths, does the source have to be in the root or can it be in a directory so inside rulles I do cd ../package && ./configure etc?
[16:53] <DktrKranz> IIRC, there's a given directory for that
[16:54] <AdamDH> given directory?
[16:55]  * DktrKranz looks at http://package-import.ubuntu.com/b/binutils-avr/jaunty/files
[16:55] <DktrKranz> 505 error...
[16:56] <AdamDH> seems to be harder to create a debian package 2 days compared to 3 hours for gentoo
[16:56] <AdamDH> so much conflicting information
[17:06] <bbs> http://dpaste.com/103409/
[17:06] <bbs> can someone please help me with this?
[17:06] <bbs> my deb is perfect except for this
[17:08] <iulian> DktrKranz: That's odd. When I browse package-import.u.c, I get a "502 Proxy Error" message.
[17:08] <DktrKranz> iulian, typo ;)
[17:08] <Laney> bbs: When you do gpg --list-secret-keys, do you see exactly the same name and email as that?
[17:10]  * bbs checks
[17:11] <iulian> DktrKranz: Did you get that error when you were browsing it?
[17:11] <DktrKranz> iulian, sometimes. I usually get it only for "jaunty"
[17:11] <bbs> Laney: uid                  james toy (www.dexrex.com<EMAIL_ADDRESS>[17:11] <Laney> bbs: That's not the same
[17:12] <bbs> oO
[17:12] <bbs> why since there is a comment?
[17:12] <Laney> yep
[17:12] <AdamDH> I might leave off Debain support for a while I just cannot get my head around it all or find anything that works
[17:12] <iulian> DktrKranz: Ah-ha, OK. Then it's not just me.
[17:13] <bbs> Laney: thanks a lot
[17:15] <AdamDH> does any one know to a clean example where a patch is applied without a patch system confiure arguments are run and then make make install without any crap in the rules files? just a clean example that just does it from scratch without debhelp cdbs etc?
[17:18] <AdamDH> Why is debian packaging so complicated?
[17:25] <directhex> AdamDH, because debian packages cover a variety of scenarios
[17:26] <directhex> AdamDH, for simple packages, the hard part (debian/rules) needs to be 3 lines max
[17:26] <sebner> directhex: 2 if you delete the comment :P
[17:29] <AdamDH> directhex can you pastebin me a generic rules file please?
[17:29] <AdamDH> just something so I can see how far back it can be stripped back
[17:30] <directhex> %:
[17:30] <directhex>         dh $@
[17:31] <directhex> well, with "#!/usr/bin/make -f" on the first line, of course
[17:32] <directhex> and since it's a makefi;e, that's a tab, not 8 spaces
[17:32] <AdamDH> yup but there is nothing past to configure no make no make install no make clean so nothing is going to get built?
[17:33] <AdamDH> *passed
[17:33] <james_w> Laney: thanks a lot for forwarding all of the mono patches
[17:33] <directhex> AdamDH, you asked for minimal!
[17:33] <AdamDH> i meant minimal that would actually be used to build something minimal
[17:33] <AdamDH> *ment
[17:33] <directhex> AdamDH, that runs configure with appropriate prefix, make, make install, make clean, etc.
[17:33] <directhex> AdamDH, that's enough debian/rules to make a package
[17:34] <AdamDH> this is what confuses me coming from another system where it uses basically just shell scripts and you can see cleanly how it works, I have written make files for c / cxx projects
[17:34] <Laney> james_w: you're quite welcome
[17:35] <AdamDH> with debain I don't see the flow and everyone does something diffrent there is no standard as such, everything seems to just build
[17:35] <directhex> AdamDH, so you don't want minimal, you want full.
[17:35] <jmarsden|work> AdamDH: man dh may help, look at the examples?
[17:36] <AdamDH> i just want to work without a system just a rules file, something blank to start with, I packaged some really basic stuff yesterday to play around but was not 100% sure how things worked
[17:36] <directhex> AdamDH, a rules file is a makefile. nothing more, nothing less.
[17:37] <james_w> directhex: do you want a sponsor for a merge of gnome-subtitles?
[17:37] <directhex> try http://svn.debian.org/wsvn/pkg-mono/mono-basic/trunk/debian/rules?op=file&rev=0&sc=0 as a less automated example.
[17:37] <directhex> james_w, need sublib first, and ftpmaster just rejected it
[17:37] <james_w> ah
[17:38] <AdamDH> thanks directhex that looks clean, I can follow that I will have another play
[17:38] <Laney> how did it build in debian?
[17:38] <directhex> Laney, debian is the land of binary uploads :)
[17:38]  * Laney pukes
[17:39] <Laney> there's no policy that it has to be buildable from the archive?
[17:39] <directhex> Laney, technically. but with binary uploads, it often isn't the case :)
[17:39] <james_w> Laney: yeah, it's an RC bug if it doesn't (and it's in main/contrib)
[17:40]  * directhex is fighting ikvm. currently, ikvm is winning
[17:40] <Laney> I guess experimental is more relaxed about these things
[17:40] <james_w> indeed
[17:40] <james_w> directhex: what makes it tricky?
[17:41] <directhex> james_w, generally speaking? it requires its own modified source snapshots of openjdk and gnu classpath, and uses nant to build. those are a good start on the pile of suck
[17:41] <directhex> james_w, so for one thing it takes 1.5 gig of ram to compile
[17:42] <directhex> thanks to javac bloat
[17:42] <james_w> urgh
[17:42] <james_w> my sympathies
[17:42] <directhex> in this specific case, i'm working on test builds of the new upstream release, to update the neolithic package we have
[17:42] <directhex> a test build i now have working! except if i enable assembly signing, it ftbfs with some bollocks reason
[17:43] <Laney> talked to upstream?
[17:43] <directhex> not yet. hanska did, and the aswer generally was "don't build from source", which is hardly acceptable
[17:43] <Laney> hahaha
[17:43] <directhex> but i've made more progress than he did
[17:44]  * directhex gets out the decompiler, starts decompiling & diffing
[17:45] <Laney> inline changes--
[18:00] <james_w> Laney: genpo uploaded with a few minor tweaks. Thanks for your contribution to Ubuntu :-)
[18:04] <Laney> james_w: Heh, I did wonder about that bzr repo
[18:04] <Laney> but that guy seemed to keep up with it and I thought he might complain if I took it out
[18:04] <Laney> :P
[18:39] <jpds> What's the python code is output a list (["x", "y", "z"]) as: "x, y, z"?
[18:41] <Laney> >>> ",".join(["a","b","c"])
[18:41] <Laney> 'a,b,c'
[18:41] <Laney> jpds: That close enough?
[18:41] <Laney> I guess ", ".join(... would work
[18:42] <jpds> Laney: Yay, that's works.
[19:20] <hyperair> anyone got time for revu? http://revu.ubuntuwire.com/details.py?package=codelite
[19:25] <AdamDH> does someone mind taking a look at this and telling me where I have gone wrong? http://pastebin.com/m3c210057
[19:27] <james_w> AdamDH: what's the problem you are having?
[19:28] <AdamDH> make: *** [build] Error 2
[19:28] <AdamDH> dpkg-buildpackage: failure: debian/rules build gave error exit status 2
[19:28] <AdamDH> oh this was before it make: *** [build] Error 2
[19:28] <AdamDH> dpkg-buildpackage: failure: debian/rules build gave error exit status 2
[19:28] <AdamDH> sorry:
[19:28] <AdamDH> make[1]: *** No targets specified and no makefile found.  Stop
[19:29] <james_w> ah
[19:30] <james_w> you have "$(MAKE)", but you probably want "cd src && $(MAKE)", or similar
[19:30] <james_w> because you want to build what you unpacked in to "src"
[19:30] <james_w> "$(MAKE) -C src" might do it as well
[19:32] <AdamDH> a thanks james_w did not notice that
[19:33] <AdamDH> i got some better code for the patch just hard coded it for the moment to see if it will work
[19:35] <AdamDH> cd src && /usr/bin/make
[19:35] <AdamDH> cd: 1: can't cd to src
[19:36] <AdamDH> so its not extracting the source then?
[19:43] <james_w> AdamDH: ah, because build doesn't depend on configure, configure doesn't depend on patch, and patch doesn't depend on unpack
[19:43] <AdamDH> right I follow
[19:44] <AdamDH> i will fix that
[19:51] <AdamDH> thanks James seem to be getting some where now
[19:52] <AdamDH> what path do I use for the patch? patches/patch.patch?
[19:59] <AdamDH> it cant find the files to patch No file to patch.  Skipping patch.  patch -stuN -p1 < patches/msp430-binutils-2.18-msp430-cvs.0.0.20081229.patch, should the patch be in the source dir and applied?
[19:59] <james_w> nope
[19:59] <james_w> it's the same problem as before
[19:59] <james_w> you need to cd to src first
[20:01] <AdamDH> ah thanks I fought dh_testdir moved into the src, added a cd into it
[20:25] <AdamDH> how do I pass arguments to gcc?
[20:30] <jmarsden|work> AdamDH: Traditionally, in the Makefile you can do something like CCFLAGS="-ggdb"  and make sure the compiler invocation uses $(CFLAGS)
[21:00] <AdamDH> here is a good one: checking for C compiler default output file name... configure: error: C compiler cannot create executables not had that error for a while, what would cause that?
[21:01] <james_w> AdamDH: check config.log
[21:02] <james_w> there will be some error in the test compilation
[21:03] <AdamDH> where would the log be? had a quick look around cant see it
[21:04] <james_w> find . -name "config.log"
[21:05] <james_w> it's usually in the same place as the configure script, but it can end up elsewhere in some situations
[21:07] <AdamDH> ah solved it, passed Wall as part of the CCFLAGS
[21:07] <AdamDH> just getting make problems now to look at
[21:07] <AdamDH> is there a document documenting what is required of a package to get it submitted into Ubuntu?
[21:08] <Laney> AdamDH: see /topic
[21:26] <AdamDH> im getting cc1: warnings being treated as errors, never had this before while compiling the code from source on other systems. I noticed -Werror is part of the defualt CCFLAGS
[21:31] <AdamDH> not to sure if passing -Wno-error is a good idea, its not good practice to do that
[21:40] <AdamDH> are patches in /patches automatically applied?
[21:41] <james_w> ./debian/patches?
[21:41] <james_w> not by default
[21:41] <james_w> you can enable a patch system, some of which will do it
[21:41] <AdamDH> its applying my patch twice once before configure then once after configure and before make
[21:43] <Laney> AdamDH: are you using a patch system?
[23:05] <AdamDH> configure and make seem to work well but I get make[1]: *** No rule to make target `install'.  Stop.
[23:05] <AdamDH>  any ideas? I have a $(MAKE) install
[23:11] <jmarsden|work> AdamDH: Does that need to be cd src && $(MAKE) install perhaps?
[23:11] <AdamDH> crap yes!
[23:18] <AdamDH> right its done configure make and make install and I have a feeling for how things should be done now, but I get mkdir: cannot create directory `/opt/msp430': Permission denied right at the end. Any ideas?
[23:26] <jmarsden|work> Does the src/Makefile correctly use $(DESTDIR) in its install target?
[23:29] <AdamDH> the src/Makefile is from upstream bin-utils with a patch applied, I am guessing it should do
[23:29] <jmarsden|work> That'snot good enough... read it and understand it :)
[23:30] <jmarsden|work> It sounds like your "make install" is installing into the real /opt/msp430/ instead of into ~you/package/debian/whatever/opt/msp430
[23:30] <jmarsden|work> Which is probably because there is a $(DESTDIR) missing in the Makefile.
[23:32] <AdamDH> ah because we are using a chroot to build the package
[23:32] <AdamDH> so we install inside that chroot
[23:34] <jmarsden|work> Not really a chroot, during the build we install under the package-x.y/debian because we have permission to do that, we don't have full root privs or we'd potentially break our development box...
[23:36] <AdamDH> I was doing everything inside a VM as I don't have access to my dev server here
[23:36] <jmarsden|work> OK, but you still don't want a packaging attempt to break your VM...
[23:37] <jmarsden|work> Imagine packaging gcc if the install during a packaging attempt overwrote /usr/bin/gcc :)
[23:44] <AdamDH> yer exp as the gcc cross compiler I am working with is for a diffrent arch!
[23:44] <AdamDH> i am packing binutils gcc libc for the msp430 microcontrollers
[23:45] <AdamDH> learning allot more about the inner workings of ubuntu / debian by packaging this project
[23:45] <AdamDH> we usally do source installs but as I am working on more than one system now that can be time consuming exp if you need to patch in another processor
[23:46] <jmarsden|work> OK... so now you know why the install needs to go somewhere other than the "real" install location :)  And yes, you'll learn a lot.  As the packaging guide says "It is also a good way to learn how Ubuntu and the applications you have installed work."
[23:47] <AdamDH> its a bit stress full as I am also new to ubuntu been a gentoo user for a while, but as new people use this project mspgcc its nice to have the packages there for ubuntu as this is what most people favour using now
[23:47] <AdamDH> last error I get is dpkg-gencontrol: error: current host architecture 'amd64' does not appear in package's architecture list (i386) but I set in control i386 so does this need to be set as amd64?
[23:48] <AdamDH> or set as any?
[23:49] <jmarsden|work> You're jumping into the deep end somewhat packaging a crosscompiler...
[23:50] <jmarsden|work> Wait, you are building i386 binaries of a embedded microcontroller compiler on amd64??
[23:50] <jmarsden|work> Sort of cross-cross-compiling?
[23:51] <AdamDH> my dev system is amd64
[23:51] <AdamDH> but its an i386 binary thats required
[23:52] <jpds> bigon: Thanks for that bug report. Fix commited to Bazaar now
[23:52] <jmarsden|work> AdamDH: I think you can't really do that, can you?  Maybe you should have made the VM be a 32bit VM???  You need more of a cross compiling/multiple architecture expert than I am to answer that one, I think.
[23:53] <bigon> jpds: np :)
[23:53] <AdamDH> ah ok should have used a 32bit vm
[23:53] <AdamDH> not a problem as If the rules work and I get an amd64 binary then I am allmost there
[23:54] <jpds> bigon: Could bzr branch lp:ubuntu-dev-tools and test it out for me?
[23:55] <Laney> jpds: The requestsync man page says -ns at the top, but -n in the body
[23:56] <jpds> Laney: -s is forced sponsorship-required
[23:56] <AdamDH> got my .deb now but when I check with dpkg there are no files included inside the deb just ./ ? why is this?
[23:56] <Laney> oh, two separate options/
[23:56] <Laney> ?
[23:56] <bigon> jpds: seems to work now
[23:56] <jpds> Laney: Yeah.
[23:57] <jpds> bigon: \o/ Brilliant.
[23:57] <bigon> :)
[23:58]  * jpds => bed. G'night all.
[23:58] <bigon> gn
[23:58] <AdamDH> so I created a deb that has nothing inside it at least I created a deb package!


[00:33] <devfil> Riddell, apachelogger: I've just uploaded gtk-kde4 to REVU
[01:03] <vorian> apachelogger: wha?
[03:33] <JontheEchidna> AHAHAHA: http://wadejolson.wordpress.com/2008/08/26/be-careful-of-what-you-wish-for/
[03:42] <jjesse_> lol'ed at that
[03:42] <jjesse_> from jorge on identi.ca
[04:03] <jjesse_> i hate it when there is severe weather when i travel
[04:03] <jjesse_> i never remember what county i'm in to figure out if the storm warning is for me or not
[05:16]  * ScottK tries sudo dpkg -i every non-debug binary in kde 3.5.10.
[06:13] <ScottK> Riddell: bug #261366 is uploaded and I asked slangasek to accept it.  I'm headed to bed, so please accept away if he hasn't.
[07:32] <apachelogger> vorian: what did I do?
[09:04] <apachelogger> Oo
[09:05] <apachelogger> if bugzilla's search was any worse...
[09:05] <apachelogger> searching for 'online reader' brings up results where the topic matches this string as the very last item -.-
[09:54] <\sh> sebas: this is humiliation what you did to wade...;)
[10:34] <ScottK> \sh: You say that like that's a bad thing.
[11:04] <seaLne> is rsibreak-kde4 4:0.9.0~beta3-kde4.0.80-0ubuntu1~hardy1~ppa1 just displaying blank dialogs in hardy for anyone else?
[11:06] <seaLne> mainly configure dialog but also welcome tip
[11:45] <Riddell> seaLne: seems quite broken in intrepid :(
[11:59] <Riddell> devfil: did I hear you were going to motu?
[11:59] <devfil> Riddell: yes, yesterday I have sent my email to MOTU council mailing list
[12:03]  * Riddell e-mails support
[12:06] <devfil> Riddell: thanks
[12:08] <ScottK-laptop> Riddell: I assume it was you accepted the 3.5.10 backports?  Thanks.
[12:08] <ScottK-laptop> Now if the buildd's would just peddle faster.
[12:09] <apachelogger> devfil: http://paste.ubuntu.com/40637/
[12:09] <ScottK-laptop> To test the 3.5.10 build I installed every single non-debug KDE package on my laptop.  I'm learning about all kinds of new stuff.
[12:10] <Riddell> arts and kdelibs compiled
[12:10] <devfil> apachelogger: thanks, I'm also looking to qt4-style that should be included in gtk-kde4
[12:10] <ScottK-laptop> Riddell: Is there anyone you can ping about Bug #259436.  I find it highly annoying as I don't routinely use anything but Konqueror.
[12:10] <apachelogger> devfil: k
[12:10] <apachelogger> Riddell: why did you delete kinfocenter in intrepid?
[12:11] <ScottK-laptop> Riddell: Yes, I'm watching through the web U/I and anxiously checking for build failure mail (none so far).
[12:11] <Riddell> ScottK-laptop: #canonical-sysadmin ?
[12:11] <Riddell> apachelogger: I did?
[12:11] <apachelogger> Riddell: https://edge.launchpad.net/ubuntu/intrepid/i386/kinfocenter
[12:11] <apachelogger> Deleted on 2008-08-05 by Jonathan Riddell (not in KDE 4)
[12:12] <ScottK-laptop> Riddell: Dunno.  I was thinking you might have more luck than me at it.  I can ask.
[12:12] <Riddell> apachelogger: I accepted a kinfocenter from New recently
[12:13] <nixternal> good morning
[12:13] <ScottK-laptop> Heya nixternal.
[12:13] <Riddell> apachelogger: hmm, I don't know
[12:13] <nixternal> UPS better deliver my machine at work today, otherwise I woke up for nothing :P
[12:13] <apachelogger> https://edge.launchpad.net/ubuntu/+source/kinfocenter
[12:14] <Riddell> I accepted a binary
[12:14] <apachelogger> all very strange
[12:15] <Riddell> but I don't see it now
[12:18] <apachelogger> I think any binary would show up at https://edge.launchpad.net/ubuntu/intrepid/i386/kinfocenter
[12:19]  * ScottK-laptop guesses Soyuz was hungry that day.
[12:19] <apachelogger> ...
[12:19] <apachelogger> Riddell: it will be republished with 4.1.1 anyway
[12:27] <smarter> heya
[12:30] <apachelogger> salut smarter
[12:31] <smarter> hallo apachelogger ;)
[12:38] <davmor2> Riddell: any clue when the fix will go in for the "about kubuntu" icon on desktop?
[12:38] <Riddell> davmor2: nope
[12:38] <davmor2> Okay :)
[12:38] <Riddell> JontheEchidna: get my jockey e-mail?
[12:41] <devfil> apachelogger: do you suggest me to put qt4 style to another package?
[12:42] <apachelogger> devfil: no
[12:42] <devfil> ok
[12:42] <apachelogger> gtk-kde4 doesn't make much sense without that style and I guess the style doesn't without gtk-kde4
[12:43] <apachelogger> smarter: when do you apply for master of the unemployeds?
[12:44] <smarter> apachelogger: right after Feature Freeze I think
[12:44] <apachelogger> i.e. tomorrow?
[12:44] <JontheEchidna> Riddell: yeah, no clue what it means though...
[12:45] <smarter> apachelogger: FF is in two days, no?
[12:45] <apachelogger> I honestly dunno
[12:45] <JontheEchidna> maybe /me needs a few more minutes to wake up
[12:46] <apachelogger> fridge doesn't say a word about ff -.-
[12:46] <apachelogger> smarter: indeed, 28th it is
[12:52] <JontheEchidna> Riddell: I don't see anything I changed that would make a difference... I see no reference to a --check option in the current version of jockey in the repos
[12:53] <seele> oh nice. kernel panic when rebooting
[12:56] <Riddell> JontheEchidna: in jockey/ui.py ?
[12:57] <JontheEchidna> ah
[13:01] <Riddell> how does this read?   http://www.kubuntu.org/news/kde-3.5.10
[13:02] <Riddell> JontheEchidna: maybe look at how language-selector parses command args, but then pass a copy of the original sys.args since kcmdlineargs will eat the bits it cares about
[13:02] <seele> Riddell: misspelled repository, second para
[13:03] <seele> Devid or David?
[13:03] <Riddell> Devid apparantly
[13:03] <Riddell> thanks seele
[13:07] <apachelogger> Riddell: we should work on the appearance of news
[13:07] <apachelogger> they aren't too attractive IMHO :S
[13:11] <Riddell> apachelogger: more bling welcome
[13:14] <JontheEchidna> Riddell: where would I pass the a copy of the original args to?
[13:16] <Riddell> JontheEchidna: ui.py seems to read it directly from sys.argv but kcmdlineargs can eat entries from sys.argv so you might need to take a copy and copy it back
[13:16] <JontheEchidna> ah, so I don't need to implement everything with KCmdLineArgs?
[13:17] <Riddell> no but you need to make it accept the arguments else it'll moan that they're incorrect
[13:19] <JontheEchidna> let's see if this works...
[13:19] <JontheEchidna> nope
[13:21] <JontheEchidna> think I should just clear sys.argv after I get a copy so that the KApp won't far out?
[13:21] <JontheEchidna> cool, that works
[13:21] <Riddell> that's an idea
[13:22] <Riddell> don't clear sys.argv but pass an empty list to kcmlineargs
[13:22] <Riddell> then sys.argv will be left in peace to be ready by ui.py
[13:23] <JontheEchidna> yeah, that's what I did
[13:23] <JontheEchidna> argscopy = sys.argv
[13:23] <JontheEchidna> sys.argv = [""]
[13:23] <JontheEchidna> KCmdLineArgs.init(sys.argv, aboutData)
[13:23] <JontheEchidna>     kapp = KApplication()
[13:23] <JontheEchidna>     sys.argv = argscopy
[13:23] <JontheEchidna> ...without that weird whitespace junk that konvo did
[13:24] <Hobbsee> stdin: jpds ping?
[13:24] <JontheEchidna> and the args work :D
[13:25] <\sh> ScottK: hmm..no..actually I found it funny, that wade did do as requested ,-)
[13:25] <JontheEchidna> Riddell: pushed to bzr
[13:31]  * apachelogger broke his khc branch -.-
[13:32]  * JontheEchidna disappears for a bit
[13:45] <jpds> Hobbsee: pong.
[13:50] <Dekans> Is the grub entry selection (for reboot) fixed in KDE 3.5.10 ?
[14:08] <toma> is there a repository for qt 4.4.1 ?
[14:09] <Riddell> toma: no, I don't think anyone has looked into backporting it unfortunately
[14:10] <toma> Riddell: there seems to be a problem with kde and that version (hence not in backports), but i need 4.4.1 for a non-kde user so i was just wondering if anyone had a secret repository
[14:25] <jeroen-> hwh
[14:25] <jeroen-> heh
[14:25] <jeroen-> why not put kde 3.5.10 in the normal updates for hardy?
[14:29] <seele> has anyone seen Artemis_Fowl around?  I haven't seen him since akademy (or shortly thereafter)
[14:29] <ScottK> jeroen-: Because of upstream changes you can't build it all in Main.  kdeartwork needs a package from Universe, so it would fail to build.
[14:29] <ScottK> jeroen-: Up until last night, hardy-proposed -> hardy-updates was the plan.
[14:30] <ScottK> jeroen-: I've gotten stuff copied from backports to updates before, so it may end up there eventually.
[14:31] <jeroen-> ScottK: ok, but e.g. Firefox is also in the normal updates; and if kdeartwork needs a package from universe, that will also affect backports? right?
[14:32] <ScottK> jeroen-: No.  Backports doesn't care about Main/Universe.
[14:32] <jeroen-> ScottK: ok hopefully it will, because I have a bunch of PC's I don't want to switch to kde4 yet, because those people are just learning kde3
[14:32] <jeroen-> ScottK: I didnt know thta
[14:33] <ScottK> Since things move between Main and Universe in different release, Main backports would be very tough if that wasn't the case.
[14:33] <jeroen-> ok thanks for your answer
[14:40] <devfil> apachelogger: I've uploaded a new gtk-kde4 package
[14:50] <davmor2> Riddell: Adept still not working. nor is the updater opens and closes again immediately
[14:56] <jjesse> davmor2: in intrepid?  adpet 3 and adeptupdater 3 are the replacements
[14:58] <davmor2> jjesse: yes intrepid.  Are these in place on the 20080826 cd?
[14:58] <jjesse> davmor2: i dont think they are on the cd but check w/ Riddell
[14:58] <jjesse> i know i installed them on my intrepid build
[14:58] <davmor2> jjesse: ah okay thanks
[15:00]  * lamont wonders just how kdelibs4c2a/hardy Depends: sudo
[15:03]  * smarter is preparing Kvkbd 0.5.99 release
[15:05] <jpds> lamont: kdelibs (4:3.5.8-3ubuntu1) hardy; urgency=low
[15:05] <jpds> lamont: - build with --with-sudo-kdesu-backend and build-dep on sudo and make kdelibs4c2a depend on sudo
[15:06] <lamont> how very.. sigh.
[15:06] <lamont> it would be nice, sometime, to be able to install kde libs in a chroot without getting sudo in the chroot.
[15:16] <lamont> if the backend knew to try a couple different methods, rather than just one, then it could recommend sudo, and fall back to su if sudo wasn't there
[15:16] <ScottK-laptop> devfil: You have comments.
[15:23] <smarter> Ladies and Gentlemen, Kvkbd 0.5.99 is officialy released :) http://ks33313.kimsufi.com/~smarter/kvkbd/kvkbd-0.5.99.tar.gz
[15:23] <smarter> Bzr branch here: https://code.edge.launchpad.net/~smarter/kvkbd/trunk
[15:23] <smarter> Debian packaging here: https://code.edge.launchpad.net/~kubuntu-members/kvkbd/ubuntu
[15:24] <smarter> Riddell: ^ could you please review/upload that? :)
[15:25] <devfil> ScottK-laptop: I have questions about comments
[15:26] <ScottK-laptop> Shoot.
[15:26] <devfil> 1: if I don't set THIS_SHOULD_GO_TO_UNSTABLE = 1 it will not debuild
[15:26] <devfil> dpkg-parsechangelog | grep ^Distribution | grep -q 'experimental\|UNRELEASED'
[15:26] <devfil> make: *** [clean] Error 1
[15:26] <devfil> for all ubuntu packages using kde4.mk it should be used as we don't have exprerimental release
[15:27] <devfil> right?
[15:27] <ScottK-laptop> apachelogger: ^^^?
[15:27] <ScottK-laptop> I haven't done much with KDE4 yet.
[15:27] <ScottK-laptop> Seems like an omission in kde4.mk to not have the Kubuntu releases in it.
[15:27] <ScottK-laptop> OK.  Let's leave that for now.
[15:28] <devfil> I: gtk-kde4 source: debian-watch-file-is-missing (I wouldn’t block on this for the initial upload if you commit to do it before release).
[15:28] <devfil> how can I do the watch file if the project is hosted in kde-apps?
[15:28] <devfil> the download link is http://www.kde-apps.org/content/download.php?content=74689&id=3&tan=22218831
[15:28] <ScottK-laptop> Why is that a problem?
[15:28] <devfil> etc...
[15:28]  * ScottK-laptop looks
[15:29] <devfil> uhm it points to http://betta.h.com.ua/no-site/gtk-kde4v0.8b.tar.gz that I hope is the upstream site
[15:29]  * ScottK-laptop hands devfil http://betta.h.com.ua/no-site/
[15:29] <ScottK-laptop> Yes.
[15:30] <devfil> A lot of files in the upstream code are executable that don’t need to be. Please make then not executable in debian/rules.
[15:31] <devfil> in the rules there are commands to make them not executable
[15:31]  * ScottK-laptop looks
[15:31] <devfil> after # Fix executable-not-elf-or-script lintian warnings
[15:32] <ScottK-laptop> devfil: OK.  The other stuff isn't installed in the binary package, so it's OK as it.
[15:32] <ScottK-laptop> it/is
[15:32] <devfil> to fix I: kcm-gtk-kde4: arch-dep-package-has-big-usr-share 1276kB 90% (please look into this one, not sure it’s worth the trouble).
[15:32] <devfil> I can move the qt4theme to another package
[15:33] <ScottK-laptop> Yes.  If you can do that, it would be better.  I'll save over 1MB/per arch.  It all adds up.
[15:33] <devfil> ScottK-laptop: 1MB per arch?
[15:34] <devfil> the deb is ~120kb
[15:34] <ScottK-laptop> Odd.
[15:34] <devfil> 131,4kb
[15:34] <smarter> it's gzipped
[15:34] <ScottK-laptop> Right.
[15:35] <ScottK-laptop> devfil: Add a lintian over-ride for that one then.
[15:35] <ScottK-laptop> smarter: Thanks.
[15:35] <devfil> ok
[15:35] <smarter> ScottK-laptop: you're welcome ;)
[15:35] <devfil> ScottK-laptop: a lintian override for an info?
[15:36] <ScottK-laptop> devfil: I wouldn't block if it's not there, but it's preferred.
[15:40] <devfil> ScottK-laptop: uhm, for the watch file.... upstream uses a particular way to call tarballs, the package is 0.8~beta1 but the tarball gtk-kde4v0.8b.tar.gz, how can I do the watch file so?
[15:41] <ScottK-laptop> devfil: Pull out your regex book and get to work.
[15:41] <ScottK-laptop> This is why I said I wouldn't block on it.  Getting that right will take some work that can be done after feature freeze.
[15:41] <devfil> ScottK-laptop: I can do a regex, but in the next version probability will not work
[15:43] <ScottK-laptop> So you need a better regex I guess.  I think it's a solvable problem, but am not a super regex wiz, so I don't have specific suggestions.
[15:43] <ScottK-laptop> Worry about it for later.
[15:45] <devfil> ScottK-laptop: if I use ~b1 as package version I think it is simple to do
[15:46] <ScottK-laptop> OK.
[15:55] <devfil> ScottK-laptop: echo "0.8~b1" | sed 's/~//;s/[0-1]$//;'
[15:56] <ScottK-laptop> If it works, I'm happy.
[16:02] <devfil> ScottK-laptop: it works
[16:02] <devfil> Newest version on remote site is 0.8rc2, local version is 0.8~b1
[16:02] <devfil>  (mangled local version number 0.8b)
[16:03] <ScottK> devfil: Then how about we package rc2 then?
[16:03] <devfil> ScottK-laptop: it isn't released on kde-apps so I prefer to not update to it now
[16:03] <ScottK-laptop> OK.
[16:11] <Hobbsee> can someone deal with taskjuggler?  it's dying over kdepim-dev.  Thanks!
[16:11] <Riddell> smarter: kvkbd working well here
[16:11] <Riddell> smarter: shall I just upload it?
[16:20] <ScottK-laptop> devfil: I need to run.  Feel free to paste the relevant bits of our conversation into REVU so other MOTU will know what we agreed.
[16:21] <devfil> ScottK-laptop: ok
[16:26] <Riddell> JontheEchidna: was jockey ported to use install-package?
[16:26] <JontheEchidna> Riddell: no, I don't think it uses adept-batch after all
[16:27] <Riddell> grep doesn't suggest it does
[16:27] <Riddell> JontheEchidna: ok, let me see if I can work out how to upload this
[16:27] <JontheEchidna> thanks
[16:34] <ScottK> Riddell: After reading the KDE announcement for 3.5.10 that includes "changelog is not complete as our developers often forget to document their work", I feel better about backports.
[16:35] <Riddell> ScottK: mmm
[16:39] <Riddell> JontheEchidna: hmm, do-release fails miserably
[16:39] <smarter> Riddell: go ahead, upload it :)
[16:40] <JontheEchidna> :(
[16:41] <Riddell> JontheEchidna: this is always what happens when I try and touch jockey
[16:41] <JontheEchidna> Think we'll be able to get a FFE for it?
[16:43] <Riddell> smarter: uploaded, thanks
[16:43] <Riddell> smarter: did you contact the original author?
[16:43] <smarter> Riddell: sending a mail right now
[17:01] <Riddell> JontheEchidna: uploaded!
[17:01] <JontheEchidna> Riddell: you figured it out? :D
[17:02] <Riddell> JontheEchidna: well, I worked around it
[17:02] <Riddell> JontheEchidna: probably I did it wrong and pitti will moan but that's what he gets for going on holiday before FF :)
[17:02] <JontheEchidna> ;-)
[17:02] <JontheEchidna> and if it's broken enough it'll ensure a release with the pykde changes, \o/
[17:59] <apachelogger> khelpcenter(29192) KHC::SearchEngine::search: SearchEngine::search() commonSearchProgram is EMPTY
[17:59] <apachelogger> no goody goody
[18:34] <apachelogger> \sh: [19:23:21] <mr_clark> Hi guys. Everytime I start up my laptop with KDE4 on Kubuntu, Adept tells me I need to update python-qt4 and python-qt4-common. I do the update but it comes up again saying it needs an update. Any idea why? This has been going on for over a week.
[18:37] <smarter> ok, time to update all the packages I maintain to latest version before Feature Freeze :)
[19:12] <smarter>   libmysqlclient15off: Depends: mysql-common (>= 5.0.67-0ubuntu2) but it is not installable
[19:12] <smarter> yay for mysql being b0rken two days before feature freeze :/
[19:13] <Riddell> so long as it has the features, it doesn't matter if they don't work :)
[19:13] <smarter> yep, but I can't pbuild my packages
[19:18] <smarter> anyway, as long as I don't change the deps, it should work
[19:18] <smarter> Riddell: do you have some times to upload some packages? :)
[19:19] <Riddell> smarter: can do
[19:19] <smarter> cool
[19:22] <smarter> Riddell: please upload https://code.edge.launchpad.net/~kubuntu-members/bespin/ubuntu and https://code.edge.launchpad.net/~smarter/qdevelop/ubuntu
[19:24] <Riddell> smarter: is there a magic command for doing the get-orig and debuild and stuff?
[19:24] <smarter> Riddell: debian/rules get-orig-source(or -svn) && bzr builddeb --merge
[19:24] <smarter> or bzr bd --merge
[19:24] <smarter> resulting build will be ../build-area
[19:25] <smarter> if you just want to debuild -S -sa, add --builder='debuild -S -sa'
[19:25] <Riddell> bzr: ERROR: A Debian packaging error occurred: Could not find upstream tarball at ../tarballs/kde4-style-bespin_0.1~svn080826.orig.tar.gz
[19:25] <smarter> after the get-orig-thing
[19:25] <smarter> move the tarball to ../tarballs
[19:27] <Riddell> ok, think I got it to do something
[19:28] <smarter> great
[20:09] <smarter> Riddell: I've updated webkit too: https://code.edge.launchpad.net/~kubuntu-members/webkit-open-source/webkitkde-ubuntu :)
[20:09] <smarter> and splitted it in 4 binary packages
[20:10] <smarter> oh, wait for rev9
[20:11] <smarter> I forgot something
[20:11] <smarter> should be okay now
[20:15] <Riddell> smarter: ah, webkitkde
[20:17] <Riddell> uploaded, thanks smarter
[20:32] <smarter> you're welcome ;)
[20:33] <smarter> hmm, adept is not the only app that doesn't work with kdesudo, kvpm doesn't start too
[20:35] <smarter> Riddell: I've modified kvpm to use cdbs' kde4.mk: https://code.edge.launchpad.net/~kubuntu-members/kvpm/ubuntu
[20:36] <JontheEchidna> Riddell: any idea why kio-bookmarks, plasmoid-lancelot, and plasmoid-toggle-compositing all failed?
[20:36] <smarter> JontheEchidna: mysql is b0rken, and qt depends on mysql
[20:36] <JontheEchidna> blah
[20:37] <JontheEchidna> actually it seems that everything built on i386
[20:37]  * smarter is 64 bits :)
[20:38] <JontheEchidna> well this means I can file a new-upstream-release bug for lancelot
[20:38] <JontheEchidna> yay!
[20:38] <JontheEchidna> 1.0 just in time for feature freeze
[20:38] <smarter> JontheEchidna: hmm, actually kio-bookmarks failed for another reason
[20:38] <smarter> kdelibs5-dev: Depends: kdelibs5 (= 4:4.1.0-0ubuntu12) but it is not going to be installed
[20:38] <smarter>                 Depends: libsoprano-dev (>= 2.1) but it is not going to be installed
[20:38] <smarter> and it's probably the same for the other one
[20:54] <mornfall> smarter: Hm, and it still doesn't, even with the fixed desktop files?
[20:54] <smarter> mornfall: oh, it works now
[20:54] <smarter> what did you change?
[20:55] <mornfall> desktop files...
[20:55] <smarter> yes, but what did you change in the desktop files? :]
[20:55] <mornfall> smarter: Ask apachelogger I guess, he fixed them, IIRC.
[20:55]  * smarter grabs the changelog
[21:02]  * JontheEchidna testbuilds lancelot 1.0
[21:17] <JontheEchidna> Anybody up for sponsoring bug 261602?
[21:49] <seele> is there something wrong with openid on the wiki?  it doesnt keep me logged in past the forward page
[21:49] <JontheEchidna> Yes, all konqueror users get that
[21:49] <JontheEchidna> :(
[21:50] <seele> bah, i have to use ugly firefox?
[21:51] <Riddell> could try arora
[21:51] <coreymon77> ugly?
[21:51] <coreymon77> thats what themes are for
[21:53] <seele> Riddell: i happen to have it installed too.  some developer randomly asked me to look at it a while back.
[21:53] <seele> JontheEchidna: did you change any plasma desktop defaults since the last meeting?  i think there were a few suggestions we made
[21:55] <JontheEchidna> seele: Yup. Would you like a screenshot of the default desktop?
[21:55] <seele> JontheEchidna: maybe put it somewhere so we can look at it during the meeting tomrrow
[21:56] <JontheEchidna> k, the latest round of changes are only in bzr and still need publishing, etc
[21:56] <seele> i think one of the things we havent done yet is figure out which plasmoids are on the desktop by default besides the file plasmoid (if there will be anything else)
[21:56]  * JontheEchidna goes off to grab a screenshot
[21:57] <coreymon77> hehehehehehehahahahaha
[21:57] <coreymon77> jailbreaking an itouch is so fun
[21:57] <coreymon77> particularily the stuff you can do with it afterwards
[22:00]  * JontheEchidna is back, uploading screenshot
[22:03] <JontheEchidna> seele: http://i31.photobucket.com/albums/c355/Woremar/intrepiddefault.png
[22:04] <seele> JontheEchidna: need to add the Show Dashboard widget to the panel
[22:05] <JontheEchidna> oh yeah, I forgot we discussed that
[22:05] <JontheEchidna> any opinion on where it goes?
[22:07] <seele> hum.. i dont know. i'd say keep all of the utility stuff together, but you've separated the desktop navigator from the device notifier
[22:09] <JontheEchidna> I could put the device notifier back between the clock and systemtray like it was in 4.0.x
[22:09] <JontheEchidna> then maybe put show dashboard between the system tray and desktop navigator
[23:15] <Riddell> out of all the packages I've reviewed today, I wonder if hamster-applet or guake should get the prize for worst name
[23:16] <coreymon77> lol
[23:16] <coreymon77> i love my fugitive itouch
[23:16] <coreymon77> :P
[23:16] <coreymon77> but those are bad names
[23:21] <JontheEchidna> Haha @ hamster-applet
[23:22] <coreymon77> whats hamster-applet do
[23:23] <waylandbill> as long as it aint the hamster dance.
[23:30] <smarter> Riddell: fix for bespin and qdevelop FTBFS on their bzr branches
[23:31] <Riddell> Merging from remembered location<EMAIL_ADDRESS>[23:31] <Riddell> Nothing to do.
[23:33] <smarter> oops, forgot to push change
[23:34] <smarter> (by the way, you should use pull to get new revs, not merge)
[23:34] <smarter> Pushed up to revision 20.
[23:35] <smarter> and someone should figure out why kdelibs5 is uninstallable on every arch but i386 on the buildds
[23:36] <Riddell> word on the streets is mysql's fault
[23:36] <smarter> damn
[23:37] <smarter> I've updated kvpm to use kde4.mk too if you want to take a look: https://code.edge.launchpad.net/~kubuntu-members/kvpm/ubuntu
[23:37]  * smarter is off to bed
[23:37] <smarter> thanks for uploading my packages Riddell ;)
[23:37] <smarter> and good night all
[23:46] <smarter> (and there's still no l10n for kde4 :p)
[23:48] <Riddell> pitti is on holiday so no chance of language packs even if launchpad was doing them
[23:48] <smarter> doh :/
[23:49] <smarter> half-translated kde4 is no fun
[23:50] <neversfelde> I would like to do a bug report for menue editor, can you tell me which package it is associated with?


[01:48] <kenvandine> jdstrand, thx!
[02:32]  * RAOF learns about the new (symver) dpkg-symbols modifier. Woot!
[02:45] <duflu> RAOF: What's that?
[02:46] <RAOF> Take the version of a symbol from the symbol version 😀
[02:47] <RAOF> So, to pick a random example:
[02:47] <RAOF> (symver)MIR_SERVER_45 0.25
[02:48] <RAOF> To make all those symbols resolve to a version dependency of >= 0.25
[04:50] <didrocks> good morning
[04:52] <jibel> morning
[04:52] <jibel> salut didrocks
[05:01] <didrocks> salut jibel
[05:01] <jibel> didrocks, tu es là de bonne heure ce matin. Ca va ?
[05:02] <didrocks> jibel: ça va bien, en fait, je commence souvent vers 7h avant que Martin ne se réveille, je ne lance pas IRC tout de suite par contre
[05:02] <didrocks> jibel: et toi, comment ça va ?
[05:06] <jibel> didrocks, très bien, tout le monde part à l'école enfin un peu de calme :)
[05:07] <didrocks> héhé, j'imagine :)
[05:07] <didrocks> Martin dort encore, j'ai une heure de tranquilité :p
[05:16] <jibel> ah moi j'ai jusque 17h ;)
[05:17] <duflu> Morning didrocks, jibel
[05:22] <jibel> Morning duflu
[05:35] <didrocks> hey duflu
[05:40] <ricotz> hey desktopers
[05:45] <didrocks> hey ricotz
[07:05] <colinl> Hi everyone!
[07:05] <colinl> duflu: I've updated the patch we were talking about yesterday :)
[07:06] <colinl> and subscribed ubuntu-sponsors. I hope it'll go in (and upstream too!) :)
[07:06] <duflu> colinl, thanks. I'm not a sponsor myself, and I know the sponsors queue can be weeks deep. So it's good to get it in there early
[07:07] <colinl> I'm crossing fingers :)
[07:07] <colinl> TBH I already push my patched package to my users' desktops, but I'm sure that'll cause me more work as long as it's not upstreamed
[07:25] <didrocks> in the "fun bugs" style:
[07:26] <didrocks> - in a terminal, gnome-screenshot -a -> works as expected
[07:26] <didrocks> in the dock "quicklist" -> it doesn't
[07:47] <seb128> didrocks, do you debug it?
[07:47] <seb128> I can confirm, it's weird
[07:50] <didrocks> seb128: I don't right now, on other things
[07:50] <didrocks> seb128: it's the only option which isn't upstream btw
[07:50] <seb128> k, I'm poking a bit
[07:50] <didrocks> seb128: I wonder if it's related to "run in a terminal"
[07:50] <seb128> which one?
[07:50] <didrocks> the "take a Screenshot of selected area" desktop entry
[07:50] <seb128> the take a screenshot of a win doesn't work either for me
[07:50] <seb128> in the context menu
[07:50] <didrocks> oh
[07:51] <didrocks> it did for me, or didn't?
[07:51] <didrocks> let me retry
[07:51] <didrocks> you're right, I thought I saw the flash first
[07:51] <didrocks> (as it's really subtile clues that it's been taken
[07:51] <didrocks> ok, so one upstream option doesn't work either
[07:52] <didrocks> would be easier to push on bugzilla thus :p
[07:52] <didrocks> seb128: could be related on a race grabbing something from wayland
[07:52] <didrocks> to*
[07:52] <seb128> could be
[07:52] <seb128> I'm looking at the env
[07:52] <didrocks> I would say try a "sleep 1 &&"
[07:53] <didrocks> just to rule that out
[07:53] <seb128> the syslog has
[07:53] <seb128> gnome-screensho[9531]: Unable to use GNOME Shell's builtin screenshot interface, resorting to fallback X11.
[07:53] <didrocks> (unsure how you can reload the desktop file though without reloading the shell)
[07:53] <didrocks> hum?
[07:53] <didrocks> and when ran on a terminal
[07:53] <didrocks> no message I guess?
[07:53] <seb128> no
[07:53] <seb128> maybe an env issue
[07:53] <didrocks> yeah
[07:53] <seb128> I think the action is dbus activated
[07:53] <didrocks> well, the shell should have all dbus env…
[07:53] <didrocks> but yeah, good lead! :)
[07:57] <willcooke> morning
[07:59] <didrocks> happy friday willcooke
[08:00] <seb128> hey willcooke, happy friday
[08:00] <seb128> didrocks, no diff in the env, sleep delay doesn't make a difference
[08:02] <Laney> ahoy
[08:02] <seb128> hey Laney
[08:02] <Laney> hey seb128, happy friday
[08:02] <Laney> waht's up
[08:03] <Laney> wh
[08:03] <Laney> at
[08:03] <didrocks> seb128: interesting… Have you tried Terminal=true? (maybe even on the main element for debugging as I don't know if that can be overriden per desktop action)
[08:03] <didrocks> hey hey Laney
[08:05] <seb128> didrocks, let me keep looking a bit
[08:05] <seb128> Laney, it's friday!
[08:06] <didrocks> even *F*riday :)
[08:06] <Laney> hey didrocks!!!
[08:06] <didrocks> fry day ? ;)
[08:06] <Laney> ah good old friday
[08:06] <Laney> my friend
[08:09]  * Laney has<PHONE_NUMBER>99 emails
[08:10] <Laney> seems prodstack swift was a bit sad overnight
[08:11] <didrocks> testing thunderbird's limit?
[08:16] <Laney> oho
[08:16] <Laney> *mutt* could deal with it easily :P
[09:06] <didrocks> anyone knows the difference between org.gnome.settings-daemon.plugins.power button-power vs power-button-action?
[09:07] <didrocks> (we were already overriding the first one, the second seems to be the "new" one?)
[09:08] <didrocks> greppingin g-s-d source code doesn't show up button-power
[09:09] <seb128> didrocks, those are old deprecated/removed in g-sd
[09:09] <seb128> didrocks, https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=50564cde
[09:10] <didrocks> ah, making sense, so changing semantic and so removed
[09:10] <Laney> ones we kept for usd/ucc?
[09:10] <didrocks> hum, I don't know if we depends on it for ucc
[09:10]  * didrocks looks
[09:10] <didrocks> yep
[09:10] <didrocks> we still use them there
[09:10] <Laney> nod
[09:10] <didrocks> ok, so just adding the new override
[09:10] <Laney> we have a few reverts for dropped stuff like that
[09:11] <didrocks> I wonder if it worths adding to migration keys
[09:11] <didrocks> are it seems it's not a one to one
[09:11] <didrocks> maybe doesn't worth it
[09:12] <Laney> mmm
[09:12] <Laney> those reverts might be a good thing to look at generally though, nice idea
[09:12] <seb128> what migrated to what?
[09:12] <Laney> maybe some others can be migrated sensibly
[09:12] <didrocks> for our users button-power -> power-button-action
[09:13] <Laney> like if gsd upstream dropped something and we kept it, see what it was dropped for, maybe something to migrate there
[09:13] <didrocks> Laney: unsure anyone have cycles to look at usd/ucc for those
[09:13] <didrocks> but yeah, maybe some others can be migrated
[09:13] <seb128> power-button -> power-button-action?
[09:13] <Laney> fine, that's just an idea
[09:13] <seb128> wfm
[09:13] <seb128> well they dropped it
[09:13] <seb128> then added back under another name
[09:13] <seb128> https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=69d9d8b
[09:14] <seb128> (go GNOME go)
[09:14] <seb128> so yeah migrationg makes sense
[09:14] <didrocks> let me look if the enum is the same
[09:16] <Laney> https://bazaar.launchpad.net/~ubuntu-desktop/gnome-settings-daemon/ubuntu/files/head:/debian/patches/ some more reverts in there
[09:17] <didrocks> the enums are different
[09:18] <didrocks> and there isn't a one to one mapping
[09:18] <didrocks> let's override the default for now
[09:18] <didrocks> with interactive, as we discussed the other day
[09:19] <seb128> +1
[09:20] <seb128> didrocks, the enum seems similar, there was just a logout action at the end which isn't there anymore
[09:20] <seb128> no?
[09:20] <didrocks> are you sure?
[09:21] <didrocks> I http://paste.ubuntu.com/25488815/
[09:21] <didrocks> have this ^
[09:21] <didrocks> there is logout, the numbers don't match
[09:21] <didrocks> no more shutdown, a "blank" as well which was != from nothing
[09:21] <seb128> ah ok
[09:24] <seb128> didrocks, that's what I was looking at, http://paste.ubuntu.com/25488823/
[09:24] <seb128> so wrong thing I guess
[09:25] <didrocks> seb128: interesting that it doesn't match the enums schema file…
[09:25] <seb128> anyway I don't think there is much need to migrate
[09:25] <seb128> so yeah, interactive for all is good :-)
[09:25] <didrocks> yeah, I don't think it's the most important settings to migrate
[09:25] <didrocks> (and I'm not one telling that, note it down!)
[09:25] <didrocks> :p
[09:25] <didrocks> "that day"…
[09:26] <didrocks> ok, pushing this for the ubuntu session
[09:30] <didrocks> Trevinho: hey, did you work (I don't remember if there is a branch you proposed on the gtk theme) about separators?
[09:30] <didrocks> https://didrocks.fr/images/artful-shell-transition/dock_settings_finale.png
[09:31] <didrocks> -> I guess we are not supposed to have separators at all in the title bar
[09:31] <seb128> speaking of theme
[09:31] <didrocks> (next to settings, we can see one, same next to the minimize/maximize/close buttons)
[09:31] <seb128> does anyone else find that the spaces between items on the GNOME menus looks buggy
[09:31] <seb128> like in the shell appmenu and in the context menus on the launcher
[09:32] <didrocks> (actually, there are separators, but they are aligned)
[09:32] <seb128> it seems the same under adwaita (if I tested that correctly)
[09:33] <didrocks> you meant the separators are taking a whole line?
[09:33] <didrocks> instead of just separate?
[09:33] <seb128> https://doc.ubuntu-fr.org/lib/exe/fetch.php?tok=4ff128&media=http%3A%2F%2Fi.imgur.com%2FImRfmSe.png
[09:33] <seb128> that ^
[09:34] <seb128> I mean there is like 1km space between sections
[09:35] <seb128> so yeah, maybe it's just one line
[09:35] <seb128> but lines are big
[09:35] <seb128> the space looks even bigger than a line of text
[09:36] <didrocks> yeah
[09:36] <didrocks> it seems like the separators are taking a while menu entry
[09:36] <didrocks> whole*
[09:37] <didrocks> (with the extra spaces between it, I think that's why it looks bigger)
[09:37] <didrocks> it didn't bug me much TBH, but I can see why you don't like it
[09:37] <seb128> let's see if we get more people thinking it's a bug
[09:40] <didrocks> flexiondotorg: hey! Once you get time, as you are working on the gtk theme, do you mind looking at the g-c-c alignement issue + double border on the side panel? ^
[09:51] <willcooke> didrocks, andyrock - the badge support for dock, is there a branch I can point to for the newsletter?
[09:51] <seb128> didrocks, so gnome-screenshot makes the dbus call telling the shell to take a screenshot but the shell doesn't do it, it works if I change the focus though
[09:52] <seb128> didrocks, seems like a shell bug/limitation
[09:52] <seb128> didrocks, the context menu "takes a grab" or some modern equivalent, or at least makes the screenshooting fail
[09:52] <seb128> the file is never creates on disk
[09:53] <Trevinho> didrocks: in headerbar yes
[09:53] <seb128> which makes the screenshoting fail/display the "can't talk to shell" warning
[09:53] <seb128> the gerror is "can't open file"
[09:53] <seb128> which is the file shell is supposed to write
[09:54] <didrocks> willcooke: andyrock proposed it to dash to dock, but it's under review: https://github.com/micheleg/dash-to-dock/pull/590
[09:54] <willcooke> didrocks, perfect, thanks
[09:55] <willcooke> good work andyrock
[09:55] <didrocks> seb128: some of those options are upstream, correct?
[09:55] <seb128> didrocks, yes, https://git.gnome.org/browse/gnome-screenshot/tree/src/org.gnome.Screenshot.desktop.in#n23
[09:56] <seb128> in any case even if they were not, the issue is a shell one
[09:56] <didrocks> yeah
[09:56]  * andyrock is working on the rest of api right now
[10:01] <didrocks> Trevinho: also, it seems that it doesn't really support people tweaking the button to the left: http://www.hostingpics.net/viewer.php?id=350870Capturedcrande20170908114547.png
[10:03] <Trevinho> didrocks: I remember I had that issue, but I think it's related to how that app is done...
[10:03] <Trevinho> Like using two bars. Thus the issue
[10:04] <didrocks> Trevinho: would make sense, I told the guy to report it to bugzilla anyway
[10:57] <flexiondotorg> @didrocks: I'll get what I worked on landed and then look at g-c-c borders after.
[11:13] <willcooke> seb128, finally got round to reading the meeting notes from this week while writing the news letter - it's been a busy week!  Really exciting to see lots of fixes and improvements going in.  Thanks desktoppers, good work!
[11:13] <Trevinho> :)
[11:27] <seb128> willcooke, indeed :-)
[12:07] <colinl> hi!
[12:08] <colinl> are packages upstream versions already frozen for Artful ?
[12:09] <Laney> not exactly, but we are bug fixing rather than introducing new features now, and there is a freeze in place enforcing that
[12:09] <colinl> thanks
[12:09] <Laney> so it depends what is in the upstream version
[12:10] <seb128> colinl, what package are you looking after?
[12:10] <colinl> seb128: nothing special. I'm just in the process of fixing a few bugs we hit at work on Xenial, trying to work with upstream maintainers to get them integrated. I guess i'll file bugs with debdiffs once the patches will go in upstream :)
[12:10] <colinl> and then SRU bugs for Xenial
[12:15] <seb128> colinl, that sounds like a good idea, bugfixes and fine for artful for a while
[12:15] <colinl> ok :)
[12:16] <colinl> am I right in believing it's better to have my patches ack'd upstream before submitting them to Launchpad?
[12:18] <jamesh> colinl: as a general rule, we'd prefer to minimise the number of patches we need to maintain.
[12:19] <jamesh> colinl: when moving forward to a new upstream version, each of those patches could break and need to be fixed
[12:19] <colinl> completely understandable - that's why I'm trying to get them upstream too :)
[12:19] <seb128> yeah that's better
[12:19] <seb128> then cherrypicking to the package is fine
[12:19] <jamesh> a backport patch is a lot simpler though: the way to port it forward is to delete it :-)
[12:19] <colinl> indeed :)
[12:20] <colinl> well, I hope my patches will get some maintainer attention (it's sometimes hard in big projects :) )
[12:37] <willcooke> seb128, Laney - could you proof read the weekly newsletter when you get a mo?
[12:39] <seb128> sure
[12:46] <doko> willcooke: who is responsible for firefox/thunderbird, at least in current development versions?
[12:47] <seb128> doko, nobody
[12:47] <seb128> which is an issue we know
[12:48] <doko> ok, good =) doesn't help migration of the current packages ;p
[12:49] <seb128> right, patches/help are welcome
[12:49] <seb128> it's one of the reasons we want to drop some archs, cf -devel list discussion
[12:49] <seb128> though currently armhf is failing and that one needs fixing
[13:26] <kenvandine> chrisccoulson, when are we going to get firefox 55 in artful?
[13:37] <doko> kenvandine: ^^^ fix the armhf build ;-P
[13:38] <kenvandine> doko, oh... :-p
[13:38]  * kenvandine runs and hides
[13:43] <doko> he really ran ...
[13:43] <seb128> kenvandine, somebody needs to fix it but we don't have a maintainer, you are welcome to give it a try
[13:43] <kenvandine> lol
[13:44] <kenvandine> i crashed gnome-shell somehow
[13:44] <seb128> though foundations said they would help to fix the armhf issue
[13:44] <chrisccoulson> can foundations take rust instead?
[13:44] <seb128> willcooke, can you copy/share it to me in some other way? I don't know where my ubikey is and my google auth is not working for some reason so I'm out of 2fa
[13:45] <seb128> chrisccoulson, that would be an idea :-)
[14:05] <Laney> willcooke: the snaps section is a copy of last week's?
[14:05] <willcooke> Laney, yeah, I moved it while I was copy and pasting to wordpress
[14:05] <willcooke> I wont put it in the email
[14:05] <willcooke> ta
[14:06] <Laney> ok
[14:06] <Laney> I guess that's what the yellow thing is
[14:07] <willcooke> ya
[14:18] <Laney> k, that'll do pig
[14:19] <willcooke> :)
[14:50] <doko> chrisccoulson, seb128: I provided the initial packages for the backports. the agreement was that these would be maintained by the desktop team. you're already doing all the llvm backports for mesa anyway,
[15:03] <jbicha> didrocks: it looks like your prediction was right https://bugzilla.gnome.org/787446
[15:03] <ubot5`> Gnome bug 787446 in general "panel: Disable top bar transparency (by default)" [Normal,New]
[15:25] <didrocks> jbicha: yeah, I was expecting this to happen, seeing the time it took us to get good transparency/blur on Unity…
[15:39] <seb128> doko, I don't think desktop has been touching any of those packages in the recent cycles
[15:40] <doko> seb128: sure, tjaalton does on a regular basis
[15:40] <doko> or isn't he -desktopish?
[15:41] <seb128> doko, he isn't
[15:42] <doko> ohh, great
[15:45] <tjaalton> nah, hwe
[17:11] <willcooke> night all, have a good one
[21:56] <ahoneybun> oh goodness no
[21:56] <ahoneybun> https://didrocks.fr/images/artful-shell-transition/new-theme-main-view.png
[21:57] <ahoneybun> who thinks that looks good?
[22:04] <jbicha> ahoneybun: please be more respectful
[22:05] <jbicha> fwiw, there's a good chance the GNOME 3.26 top bar won't be translucent
[22:07] <tsimonq2> (imho it would look still being a little translucent but if it's darker than the panel :) )
[22:20]  * acheronuk looks at his customised plasma 5 with transparent panels
[22:27] <ahoneybun> with that wallpaper it does not look good with transparent
[22:28] <Gargoyle> Evenin'
[22:30] <Gargoyle> Anyone got any thoughts on why "gnome-software --gapplication-service" is running at 450% cpu?
[22:34] <Gargoyle> This is 17.10 with all the latest updates to about 10 mins ago.
[22:35] <Gargoyle> Actually, launching gnome software spins up another 4 processes and takes it to 750%
[22:39] <Gargoyle> killall = gone. No side effects! :/ !?