[10:03] <CIA-2> oem-config: cjwatson * r568 oem-config/debian/ (changelog oem-config.install): Fix debian/oem-config.install for new location of tzmap in build tree.
[10:07] <CIA-2> oem-config: cjwatson * r569 oem-config/debian/changelog: releasing version 1.54.1
[12:01] <CIA-2> ubiquity: evand * r2949 ubiquity/debian/ (changelog ubiquity.install-any):
[12:01] <CIA-2> ubiquity: Correct debian/ubiquity.install-any to refer to the new location of tzmap
[12:01] <CIA-2> ubiquity: in tzsetup.
[12:03] <cjwatson> hmm. GTK d-i frontend not what you might call entirely happy yet
[12:04] <cjwatson> evand: oh, thanks, sorry should have done that in ubiquity at the same time
[12:05] <evand> no worries, thanks for beating me to it.
[12:05] <evand> in oem-config, that is
[12:20] <CIA-2> debian-installer: cjwatson * r990 ubuntu/ (build/config/common debian/changelog debian/rules): Set default suite to jaunty.
[12:24] <CIA-2> debian-installer: cjwatson * r991 ubuntu/build/config/ (8 files in 6 dirs): more GTK frontend re-enabling
[12:30] <CIA-2> debian-installer: cjwatson * r992 ubuntu/debian/changelog: releasing version 20081029ubuntu1
[12:49] <CIA-2> debian-installer: cjwatson * r993 ubuntu/ (5 files in 4 dirs): Make mouse-modules temporarily optional on lpia and powerpc.
[13:18] <_ruben> wrt pxe booting (probably irrelevant), an ubuntu/debian-installer is versions specific right? as in, the version (gutsy,hardy,intrepid) is hardcoded into the installer, thus requiring a seperate installer for each version. or am i missing something here?
[13:22] <cjwatson> yes
[13:22] <cjwatson> yes, it is version-specific
[13:22] <_ruben> cjwatson: ok, thanks
[13:22]  * _ruben starts ripping the installer dirs from the various versions ;)
[13:48] <CIA-2> debian-installer: cjwatson * r994 ubuntu/ (build/pkg-lists/cdrom/ia64.cfg debian/changelog): Drop pata-modules from ia64.


[00:00] <genii> stdin: OK, asks for my keyphrase, but then chunks out wanting me to force it to use existing dir or such
[00:00]  * genii sips his coffee
[00:03] <genii> OK, so after doing that, the page reflects I've done something but it still appears empty, saying use bzr push lp:~mystic-scientist/+junk/pdfedit-0.4.1     but that results in a weird error on this end
[00:03] <genii> eg: bzr: ERROR: Cannot lock LockDir(http://bazaar.launchpad.net/%7Emystic-scientist/%2Bjunk/pdfedit-0.4.1/.bzr/branch/lock): Transport operation not possible: http does not support mkdir()
[00:04] <stdin> yeah, lp: seems broken for pushing
[00:04] <stdin> it'll take a couple mins for the commit to show and the code to appear
[00:04] <genii> OK
[00:04] <genii> Guess I'll drink more coffee and wait for propogation
[00:04] <genii> stdin: Thanks for the help
[00:05] <stdin> you'll get used to LP one day, scary eh? ;)
[00:05] <genii> Yes :)
[00:06] <genii> This all began with wanting a more recent pdfedit than 3.something    :)
[00:09] <genii> stdin: I must have forgot signing up there sometime in 2005
[00:12]  * stdin can't remember when he signed up for LP
[00:12] <stdin> probably in '06 though
[00:17] <genii> Do I have to commit or so?
[00:18] <genii> eg: Last modified: 16 minutes ago ... Last Commit: This branch is empty
[00:19] <stdin> push should have do that, maybe it just takes longer for the initial commit
[00:23] <genii> How long is normal before you should see a change?
[00:25] <genii> stdin: I just noticed when I made it I put branch type as Hosted. Should it have been Mirrored instead?
[00:26] <stdin> no, hosted is right
[00:26] <genii> Thats what I thought.
[00:27] <stdin> genii: did you bzr commit before pushing?
[00:28] <genii> stdin: Yes had to do --unchanged to force it
[00:29] <genii> Maybe I'll make some minor change and re-commit
[00:30] <stdin> worth a go
[00:37] <genii> stdin: OK looks like somethings finally chugging
[00:42] <genii> Success :)
[00:43] <stdin> got there in the end :)
[00:44] <genii> stdin: What I'm wondering about is if I wanted to distribute some deb package, should I just host some falcon repo?
[00:45] <stdin> you could just use the PPA
[00:45] <genii> stdin: I haven't been able to get anywhere with it :(
[00:45] <genii> Maybe I'm just obtuse
[00:47] <stdin> did you ask in #launchpad about it?
[00:47] <stdin> or look at https://help.launchpad.net/PPAQuickStart
[00:48] <nixternal> woo
[00:48] <nixternal> anyone going to work on the 4.0.82 packages for Hardy?
[00:48] <genii> Ah didn't even think they had a channel
[01:05] <vorian> evening :)
[01:44] <supert0nes[A]> too bad the neon ones can't be converted they are nice!!
[02:48] <jjesse_> so what would happen if i cahnged my sources.ist to intrepid and distu-upgraded
[02:48] <jjesse_> besieds learned to type
[02:49] <Jucato> heh :)
[02:50] <jjesse> ;0
[02:50] <Jucato> good evening jjesse
[02:51] <jjesse> here goes nothing
[02:51] <jjesse> good morning Jucato
[03:14] <jjesse> halfway through my update to ibex :)
[03:14] <jjesse> can't wait to see how this vm responds
[05:15] <dasKreech> Hi Hobbsee
[05:15] <dasKreech> Saluit seele
[05:28] <Hobbsee> hey dasKreech!
[05:29] <dasKreech> How are you?
[05:35] <Hobbsee> doing OK
[05:35]  * Hobbsee has had the fun of composing a mail to the CC>
[05:42] <dasKreech> I normally compose to the BCC
[06:27]  * Jucato waves to Hobbsee and dasKreech
[06:27]  * Jucato also KicKs dasKreech
[06:29] <dasKreech> Ow!
[06:29] <dasKreech> What?
[06:29] <dasKreech> Fine I'll play MMORPGS With you
[06:29] <Hobbsee> hey Jucato!
[06:29] <Jucato> hehehe
[06:30] <Jucato> suddenly I feel that my 1280x1024 monitor is not enough to fit all the plasmoids I want to have :)
[06:31] <dasKreech> Zoom out. Add a new one :0
[06:31] <Jucato> that almost *never* works for me
[06:31] <dasKreech> strange works a lot for me
[06:31] <Jucato> adding new activities?
[06:31] <dasKreech> Kopete and Konqueror however haeva 10% chance of hosing the entire machine
[06:31] <dasKreech> Yeah
[06:32] <dasKreech> works almost all the time for me
[06:32] <dasKreech> I think it crashed the first time
[06:32] <Jucato> dunno. whenever I try to do that my graphics slows like hell... like the mouse is being weighed down by Hobbsee or something
[06:33] <dasKreech> ooooooh
[06:33] <dasKreech> that's slow
[06:33] <dasKreech> what driver?
[06:34] <Jucato> well.. considering it's an nvidia legacy driver, I shouldn't be surprised :)
[06:34] <Jucato> (but that doesn't really contradict what I said about it not working for me :P)
[06:34] <dasKreech> what card?
[06:34]  * Hobbsee pinches the mouse.
[06:35] <Jucato> nvidia geforce4 mx 4000
[06:35] <dasKreech> Oh a Geforce2
[06:35] <Jucato> 4!! not 2. 4!
[06:36] <dasKreech> a geforce4 mx is a geforce2 card
[06:36] <Jucato> ah
[06:36] <Jucato> ok. if you say so :P
[06:36] <Jucato> whatever it is. it sucks :)
[06:36] <dasKreech> pretty high end Geforce 2 but still not quite as good a low end Geforce3
[06:36] <Jucato> this is the first (and hopefully the only) situation that nvidia has let me down
[06:37] <dasKreech> :-)
[06:37] <Jucato> situation = Qt/KDE 4
[06:37] <dasKreech> well a new card shouldn't hurt too much
[06:37] <dasKreech> (newer)
[06:37] <Jucato> actually it will
[06:37] <Jucato> you know why?
[06:37] <dasKreech> a geforce4 non Mx should be dirt cheap if you can find it
[06:37] <dasKreech> like .. free
[06:38] <Jucato> well, only if it's AGP.
[06:38] <Jucato> PCI-E is out of the question
[06:38] <dasKreech> Well yeah I don't know if there were Geforce4 PCI-e cards
[06:39] <Jucato> don't you mean AGP cards? PCI-E's the current "standard" while AGP's almost obsolete
[06:39] <dasKreech> Yeah and geforce was state of the art like 5 years ago
[06:39] <dasKreech> they are obsolete now
[06:40] <Jucato> right. so buying a video card that would work better with Qt/KDE 4 argb stuff requires me to buy a new mobo
[06:40] <Jucato> which I will lead to buying a new processor as well (dual core maaaybe)
[06:40] <Jucato> all in due time
[06:41] <dasKreech> Jucato: a geforce4 should be damn near free if you can find one and a double jump above what you have now
[06:42] <Jucato> *if* I can find one
[06:42] <Jucato> throw me a model name and I'll try to remember if I've seen something similar to it
[06:50] <dasKreech> Geforce 4 ti 4600
[08:03] <Arby> morning
[08:08] <clau30> how can I see what changes have been made to a package from feisty to gutsy?
[08:09] <Jucato> debian/changelog?
[08:09] <Arby> clau30: it will be in the changelog, which package?
[08:09] <\sh> apachelogger: I fixed yesterday the kdebindings 4.0.80 for amd64
[08:09] <\sh> (and the change works for i386 as well)
[08:09] <clau30> Arby: mount
[08:10] <clau30> thanks
[08:11] <Arby> clau30: search for the package on launchpad
[08:12] <clau30> Arby: found it on packages.ubuntu.com
[08:12] <Arby> clau30: it's part of util-linux so it's here on launchpad https://launchpad.net/ubuntu/+source/util-linux
[08:13] <dasKreech> Jucato: which MMO?
[08:14] <clau30> Arby: ah ok, thanks
[08:14] <Jucato> dasKreech: it's called Cabal Online. another Korean-made MMORPG
[08:16] <clau30> Arby: it's the problem that my usb stick doesn't get mounted on gutsy anymore, but works fine in feisty..
[08:17] <clau30> thought to look at the changelog (although not sure the problem is mount)
[08:17] <dasKreech> Jucato: I think I have wallpapers from that
[08:18] <Jucato> I have one on my desktop :)
[08:18] <Jucato> dasKreech: http://jucato.org/stuff/jucato-kde4.1-1.png
[08:18] <dasKreech> :-)
[08:19] <dasKreech> Jucato: What's in the lower left?
[08:19] <Jucato> Show Dashboard widget
[08:21] <clau30> Arby: ugh, sorry, I ment it works on hardy and doesn't on gutsy :)
[08:22] <clau30> Arby: ugh, sorry, I ment it works on gutsy and doesn't on hardy - this is the right one!
[08:28]  * dasKreech sighs at Konversation :(
[08:30] <Arby> clau30: sorry I know nothing about how mount actually works.
[08:31] <Arby> check for related bugs and if there isn't one similar to your situation file one
[08:31] <clau30> there is one, yes
[08:31] <clau30> thanks anyway ;)
[09:25] <dwidmann>  Jucato: sure, you were talking about it hours and hours earlier, but if I were you I would spring for a geforce 6 or 7, if you dig you can still find them easily enough, and they're pretty darned cheap too.
[09:37] <apachelogger> \sh: yeah, I noticed, pretty cool
[09:37]  * apachelogger hands \sh a cookie
[09:43] <\sh> apachelogger: and it works...thanks to you :)
[09:44] <apachelogger> :)
[10:24] <apachelogger> \sh: Import Error: No module named klineedit
[10:24] <apachelogger> for leonov
[10:28] <\sh> apachelogger: then kde4.py is not in uic/widget_plugins/ in pykde4
[10:28] <\sh> make clean and redo make
[10:28] <apachelogger> doesn't help
[10:28]  * apachelogger checks for kde4.py
[10:29] <\sh> 4.0.80 ppa4?
[10:29] <apachelogger> well
[10:29] <\sh> it works here and for others :)
[10:29] <apachelogger> that is the question really
[10:29] <apachelogger> no
[10:29] <apachelogger> haha
[10:29]  * apachelogger is not using the ppa
[10:29] <\sh> lol
[10:29] <apachelogger> well
[10:29] <apachelogger> it probably makes sense, since I need a fallback version in case kde-nightly breaks
[10:30] <apachelogger> oh, btw
[10:30] <apachelogger> kde-nightly goes public today or tomorrow
[10:59] <nixternal> mornin'
[11:05] <apachelogger> yo Nightrose
[11:05] <apachelogger> yo nixternal as well
[11:05]  * apachelogger hands everyone a cookie
[11:05] <apachelogger> yay! kde-nightly-qt built :D
[11:09] <apachelogger> \sh: omg, I haz menus :D
[11:09] <\sh> apachelogger: yes...but now qt-designer4 is bugging with oxy
[11:10] <\sh> apachelogger: but first after the pykde4 update ;)
[11:10] <apachelogger> lol
[11:10] <apachelogger> I get a segmentation fault
[11:10] <apachelogger> :D
[11:24]  * jpds hugs apachelogger
[11:51]  * nixternal is working on going totally green
[11:52] <nixternal> no more car! I shall bike everywhere I want to go, even Antarctica :)
[11:52] <Riddell> yay!
[11:53] <nixternal> I will ride my bike to your house Riddell :)
[11:54] <Riddell> just don't tell Betty downstairs, she's getting annoyed at the number of bikes in the stairwell :)
[11:54] <nixternal> round trip bike ride to work == ~60 miles or about 100km
[11:54] <Riddell> hardcore
[11:54] <nixternal> ya, my arse and legs said the same thing :)
[11:55] <nixternal> I am >.< that close to getting the companie's exchange calendar working in Kontact
[11:56] <nixternal> then I can ditch Evolution, which I have to admit, is fairly decent, even in KDE when you work past the font woes
[11:56] <nixternal> company's exchange calendar that is
[11:56] <nixternal> and I can't wait for the day to ditch Yum repositories, as they have to be the biggest mess I have ever seen in my life
[12:05] <nixternal> who here was working on FAI with Ubuntu/Debian? I remember someone here working on it
[12:06] <nixternal> this is exactly what I need to move forward on a CentOS to an Ubuntu based appliance
[12:06] <Riddell> ScottK?
[12:06] <nixternal> I thought \sh honestly
[12:09] <Riddell> mibby
[12:10] <smarter> FAI?
[12:12] <nixternal> Fully Automatic Installation
[12:13] <nixternal> our appliance servers right now use a CentOS (v5) customized distro that is fully automated so our machines can automatically boot up and iso image and start loading w/o us having to do a thing
[12:14] <nixternal> right now I am trying to get kickstart to pass the -m 0 flag to mkfs.ext3, but I am doing it rather hackishly
[12:14] <nixternal> would be nice if anaconda could pass this
[12:20] <\sh> nixternal: i did yes :)
[12:20] <nixternal> so my brain still works :)
[12:21] <nixternal> fairly easy to setup? I would rather go that way than preseeding with answer files probably
[12:23] <\sh> nixternal: well, if you know the system behind FAI it's fairly easy...you need the right infrastructure for it...which could be a problem
[12:23] <\sh> nixternal: also FAI in Ubuntu has problems with unionfs, which is broken in ubuntu kernel
[12:24] <nixternal> we are using ext3, so that wouldn't be an issue for us
[12:25] <nixternal> I will start playing around with it and get an infrastructure in place for it
[12:25] <nixternal> for v2 of our software, I would love to move away from RPMs
[12:45] <nixternal> time for work, ttyl
[12:46]  * apachelogger hugs jpds back
[12:50] <ScottK> Riddell: Yes?
[12:51] <ScottK> nixternal: FAI features in that spec I pointed you at.
[12:51] <Riddell> ScottK: nixternal's question not mine
[12:52] <Riddell> although, since you have supplied an answer, I could say the question was "fancy making me some lunch?"
[12:52] <ScottK> Right.  Got that once I read the scrollback.
[12:52] <ScottK> Sure hold on while I send it.
[12:58] <etretyak> Hi everyone!
[12:58] <apachelogger> hey etretyak
[12:59] <etretyak> Riddell: Should I follow kubuntu_printer_configuration.pdf for app design and usability? Or just mimic gnome version of system config printer?
[13:02] <Riddell> etretyak: until now I've been mostly following the gnome one since that's easiest to get it working, then will move to kubuntu_printer_configuration.pdf when it mostly all works
[13:02] <Riddell> etretyak: but there's no menu bar in anticipation of kubuntu_printer_configuration.pdf
[13:03] <seele> hum.. if artemis_fowl pops in, i'm around today
[13:03] <seele> missed his ping yesterday..
[13:05] <etretyak> Riddell: the menu bar exists in gnome version of system-config-printer..
[13:07] <Riddell> etretyak: right, but not in our one (since our one should one day be a kcontrol module)
[13:07] <etretyak> Riddell: i see
[13:18] <Riddell> Mez, ScottK: what to do with bug 214030?
[13:19] <Riddell> Artemis_Fowl meet seele
[13:19]  * ScottK looks
[13:19] <ScottK> Riddell: Please unsubscribe ubuntu-archive and I'll follow-up on it.
[13:20] <Riddell> ScottK: ok, done
[13:20] <Mez> ScottK, why hold off?
[13:21] <ScottK> Mez: To get confirmation that the current version is good.
[13:22] <Mez> ScottK, I can confirm that - I'm the debian Maintainer
[13:22] <ScottK> Mez: Please mark in the bug what version and that it builds/runs/installs and then ping me.
[13:22] <Artemis_Fowl> Riddell: ?
[13:24] <Mez> ScottK, added
[13:25]  * ScottK looks
[13:29] <ScottK> Riddell: As Mez says, bug 214030 is good to go now.
[13:35] <eagles051387> Nightrose afternoon question about those talks
[13:41] <ScottK> Riddell: re Bug 231098 - Please see persia's comment.  I'm no Java expert, but I think more work is needed before SRU.
[13:57] <Riddell> ScottK: mvo replied
[13:57]  * ScottK looks.
[14:04] <Riddell> Mez: php-xdebug isn't in intrepid
[14:04] <Mez> source package xdebug
[14:06] <smarter> Are we going to package kdeplasmoids?
[14:07] <Riddell> when beta 2 gets tagged
[14:07] <Riddell> which ought to be today
[14:07] <Mez> Riddell, see bug #234960
[14:07] <smarter> cool
[14:07] <smarter> Is someone already working on it?
[14:07] <Riddell> smarter: no, waiting for the tagging
[14:08] <smarter> You're going to do it?
[14:09] <Riddell> smarter: I expect it'll just be using the packaging from debian
[14:10] <smarter> okay
[14:10] <Riddell> smarter: looking for things to package?
[14:10] <smarter> yep ;)
[14:10] <smarter> I wonder if K3B is going to be released soon
[14:11] <smarter> looks like it's already usable
[14:11] <Riddell> smarter: guidance-power-manager needs packaging if you can do python
[14:11] <smarter> sure
[14:11] <eagles051387> Riddell wouldnt launchpad be a good place to look for stuff that needs packaging
[14:11] <smarter> where is it?
[14:12] <Riddell> smarter: kdesvn for now
[14:12] <Riddell> smarter: extragear/utils/
[14:12] <smarter> ok
[14:12]  * smarter svn co
[14:12] <Riddell> this would be good to have packaged too http://code.google.com/p/arora/
[14:12] <Riddell> eagles051387: if people have made bugs yes
[14:13] <smarter> Riddell: there's already a package on the site which looks pretty okay
[14:13] <apachelogger> Riddell: arora is going to debian soonish IIRC
[14:13] <smarter> it's on REVU
[14:13] <Nightrose> re
[14:13] <Nightrose> eagles051387: what question
[14:13] <Riddell> ah, cool
[14:13] <mornfall> Riddell: Hi.
[14:14] <Riddell> hi mornfall
[14:14] <apachelogger> in fact
[14:14] <apachelogger> it already is in debian
[14:14] <apachelogger> http://packages.debian.org/sid/arora
[14:14] <mornfall> Riddell: Do you think it would be hard to add a trigger to icecc that would restart iceccd when new gcc appears?
[14:14] <mornfall> I just have been bitten by upgrading gcc without iceccd restart : - \.
[14:14] <Riddell> mornfall: hmm, I don't know much about triggers
[14:15] <mornfall> Neither do I -- but I could try to check and come up with something : - ).
[14:15] <mornfall> So I'll poke you when I figure something.
[14:15] <apachelogger> well, gcc package could just restart iceccd if it is installed
[14:15] <smarter> Riddell: can I use debhelper 7 goodness for g-p-m or do you plan to backport it?
[14:16] <Riddell> smarter: I don't plan to backport
[14:16] <Riddell> smarter: what's good in debconf 7?
[14:16] <mornfall> Isn't there a dh cdbs-alike in there?
[14:16] <Riddell> apachelogger: that sounds improper
[14:16] <smarter> yep
[14:16] <mornfall> smarter: Is it better than cdbs?
[14:17] <apachelogger> Riddell: well, easier than making iceccd detect a chaned gcc and restart once no job is going on ;-)
[14:18] <smarter> It doesn't have all the rules files (/usr/share/cdbs/*) but it's supposed to replace cdbs one day
[14:20] <eagles051387> Nightrose are those talks goign to be a nightly thing
[14:20] <Nightrose> eagles051387: huh?
[14:21] <mornfall> Riddell: Ah, nevermind. The triggers in rpm are something entirely different than dpkg (what I have thought they would be).
[14:21] <mornfall> Riddell: (Or maybe they aren't... let me dig more.)
[14:23] <mornfall> man 5 deb-triggers
[14:24] <eagles051387> Nightrose those talks that took place the other night are they going to become a daily thing
[14:24] <Nightrose> eagles051387: no
[14:24] <eagles051387> ok
[14:26] <apachelogger> smarter: why would you use dh7 even though we have fullblown cdbs files for kde4?
[14:26] <apachelogger> Nightrose: I think you disappointed him
[14:26] <Nightrose> apachelogger: think so too - want me to do daily talks now? :P
[14:27] <apachelogger> Nightrose: yes
[14:27] <Nightrose> hmmmmm
[14:27] <Nightrose> NO!
[14:27] <apachelogger> you could setup a bot
[14:27] <Nightrose> ;-)
[14:27] <apachelogger> give the same talk over and over again
[14:27] <Nightrose> hehe
[14:27] <Nightrose> insanity to the rescue
[14:27] <smarter> apachelogger: yep, cdbs is a better choice atm
[14:28] <mornfall> ...
[14:32] <Riddell> ScottK: bug 211756 seems to be an outstanding backport
[14:33]  * ScottK looks
[14:34] <ScottK> Riddell: No one has ack'ed Feisty, so I'd suggest unsubscribe ubuntu-archive for now.
[14:34] <Riddell> ScottK: ok
[14:37] <jjesse> so what wierd and crazy things can i expect on my virtual machine on a dist-=upgrade from kubuntu 8.04 remix to intrepid?
[14:38] <Riddell> mm, it may well explode
[14:38] <Riddell> although not as much as after I remove the -kde4 packages
[14:42] <jjesse> will looking for it to explode then ;)
[14:42] <danimo> hi
[14:42] <Riddell> hi danimo
[14:45] <seele> hmm.. anyone want to give some feedback on kgrubeditor and how we're handling automagic?
[14:45] <seele> http://www.hotlinkfiles.com/files/1437949_gluha/kgrubeditor.ogv
[14:45] <seele> i dont think it is quite right yet, i'd prefer a better solution than a bunch of warning messages
[14:46] <jjesse> Riddell: dpkg: error processing /var/cache/apt/archives/debconf_1.5.22_all.deb (--unpack) on my dist-upgrade
[14:47] <jjesse> from hardy remix to intrepid
[14:50] <smarter> Riddell: are we going to remove kde-guidance-powermanager from intrepid?
[14:52] <Riddell> smarter: yes
[14:54] <nixternal> oi what a morning commute
[14:56] <yuriy> morning
[14:56] <nixternal> mornin'
[14:56] <yuriy> nixternal: bug 215012 still present in hardy 4.1beta packages?
[14:57] <nixternal> dunno, I think somebody did the kdebindings packages for beta..I didn't
[14:57] <yuriy> oh
[15:08] <mornfall> Riddell: Do you want patch, or should I reportbug it against Debian and it'll get to you that way?
[15:08] <apachelogger> yuriy: it's kde4bindings now
[15:09] <apachelogger> Riddell: anything I can do to help with the name changes?
[15:09]  * apachelogger is getting confused :S
[15:11] <smarter> Riddell: guidance-power-manager package almost done
[15:11] <smarter> but it breaks things that depends on guidance-backends
[15:14] <smarter> Riddell: they both provide a xf86misc.py file and pysupport doesn't like that
[15:30] <mornfall> Riddell: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486668
[15:30] <mornfall> (eeeevil bug, it's got 666 in there...)
[15:31] <apachelogger> lol
[15:34] <nixternal> ahhhh, dude that was my iceccd issue the other day I bet
[15:38] <yuriy> apachelogger: in hardy ppa too?
[15:39] <apachelogger> yuriy: yes
[15:39] <apachelogger> actually I fixed it in a branch
[15:39] <apachelogger> but forgot to merge it in before I uploaded to the ppa
[15:39] <apachelogger> so it's broken ... again
[16:19] <Riddell> smarter: just assume that guidance-backends is disappearing
[16:19] <smarter> okay
[16:19] <smarter> so I'll Conflicts/Replaces/provides on kde-guidance , guidance-backends and guidance-powermanager
[16:20] <Riddell> smarter: yep
[16:37] <JontheEchidna> w00t, Wine 1.0!
[16:44] <Riddell> quick, set a world record for downloads!
[16:47]  * apachelogger adds mozilla.com to his school's firewall blacklist :P
[17:46] <Artemis_Fowl> so seele,
[17:47] <Artemis_Fowl> how should the Automagic thing be handled?
[17:49] <Riddell> that video looks good Artemis_Fowl
[17:50] <Artemis_Fowl> Riddell: nice to hear that. but it shows only the entry-related functionality. there are still lots to be done...
[17:53] <Riddell> mornfall: "Riddell: Do you want patch" what was that about?
[17:55]  * |Artemis_Fowl| hates his ISP
[17:56] <\sh> nixternal: if you need help regarding fai<EMAIL_ADDRESS>[17:57] <mornfall> Riddell: icecc
[17:58] <Riddell> mornfall: looks like we just get it from debian so fine to do it through that route
[18:01] <ScottK> \sh and nixternal: siretart knows a bit about it too.
[18:02] <nixternal> right now I am hacking initrd.img, minstg2.img, and stage2.img files and my head wants to explode
[18:02] <\sh> ScottK: right :)
[18:30] <_Artemis_Fowl_> Riddell: wasn't seele supposed to be around today?
[18:31] <Riddell> _Artemis_Fowl_: she did say she was
[18:33] <seele> _Artemis_Fowl_: i'm here!
[18:34] <_Artemis_Fowl_> seele: good. I was about to leave :)
[18:34] <seele> _Artemis_Fowl_: i reviewed your screen cast.. automagic sucks
[18:34] <_Artemis_Fowl_> +1 from me :)
[18:34] <seele> i think the warning messages you provide are fine.. but it's still kindof messy
[18:35] <seele> i wonder if we should ask a few people to use it and see if they would prefer 1) having the option to break automagic or 2) not give them the option
[18:35] <seele> 1) would be the way it is implemented now, and 2) would be creating 2 lists, one for automagic and another for the configurable ones
[18:36] <_Artemis_Fowl_> 2 lists?
[18:36] <seele> yeah, or a separator
[18:36] <seele> otherwise, the up/down arrows would be disabled for the top half of the list
[18:36] <seele> hmm.. i guess that wouldnt be too much worse than two lists
[18:37] <seele> i guess there are two questions.  1) do people want to reorder automagic stuff, and 2) if they do want to reorder automagic stuff, do they care they break automagic
[18:40] <_Artemis_Fowl_> the concept of 2 lists sounds really strange to me
[18:41] <_Artemis_Fowl_> if i had to do something like this I would prefer the up/down disabling
[18:41] <seele> ok
[18:41] <_Artemis_Fowl_> anyway, should I do something for the time being?
[18:41] <seele> is the latest version in your ppa?
[18:42] <_Artemis_Fowl_> I have no PPA :-) I use SVN to store the source code
[18:42] <seele> actually, if you could put up two versions, one as is, and the other with the up/down disabled.. i can try to find some people to test it out
[18:42] <seele> hmm
[18:42] <_Artemis_Fowl_> packaging takes places when I release a new version
[18:42] <_Artemis_Fowl_> (by apachelogger)
[18:43] <seele> maybe he will be nice and make me two packages for user testing :)
[18:43] <seele> apachelogger: ping!
[18:43] <apachelogger> sure
[18:43] <apachelogger> just dump me a tarball
[18:43] <seele> whoot
[18:44] <_Artemis_Fowl_> so seele,
[18:44] <seele> _Artemis_Fowl_: think you could do the other version with the buttons disabled?  that way we wont hvae to do this twice
[18:44] <_Artemis_Fowl_> how exactly should something like this be iimplemented? disable the up/down arrows for all Automagic entries?
[18:46] <seele> yeah
[18:46] <_Artemis_Fowl_> ok
[18:46] <seele> can you have a different tooltip for a disabled widget?
[18:47] <seele> actually, the dialog needs some instruction/text at the top.  we can worry about that later i guess
[18:47] <ScottK> nixternal: You've got mail.
[18:47] <seele> we need to put some kind of message about automagic entries before the user makes a mistake
[18:48] <_Artemis_Fowl_> the different tooltip is possible
[18:48] <_Artemis_Fowl_> albeit strange :)
[18:48] <seele> yeah, that's why i didnt follow up with my thinking-out-loud
[18:48] <seele> just leave it as it is for now, we can figure out the user information later
[18:48] <seele> because it will be different depending on the approach we decide on
[18:49] <_Artemis_Fowl_> so all I have to do is pack the current version, modify it to fit the disabling way and pack this new approach too?
[18:49] <nixternal> ScottK: will check it when I get home
[18:50] <nixternal> carrying 2 laptops is way to much...I think it is time to either setup IMAP again, or just put Mutt back on my server that IRC sits on
[18:50] <ScottK> nixternal: You may want to check it now if you can.  You're invited to a tech board meeting in 1 hour and 10 minutes if you can make it.
[18:50] <seele> _Artemis_Fowl_: yes
[18:50] <nixternal> hr
[18:50] <nixternal> m
[18:50] <seele> _Artemis_Fowl_: then i will find a few people to test it on and see which way is better
[18:51] <ScottK> Yeah.  I'd suggest find a way to show up.  They don't come around that often.
[18:51] <ScottK> This is why I pinged you.
[18:51] <seele> the warning messages or disabling the up/down buttons
[18:51] <_Artemis_Fowl_> seele: good.
[18:51] <_Artemis_Fowl_> apachelogger: you will have mail tomorrow then
[18:51] <apachelogger> ok
[18:52] <_Artemis_Fowl_> time to leave then...
[18:52]  * seele waves
[18:53] <nixternal> ScottK: rock, thanks!
[18:53] <_Artemis_Fowl_> seele: oh, I almost forgot it: Congrats! (both for the ring and your talk at kubuntu-tutorials-day) :-)
[18:53] <nixternal> ScottK: if you don't see me talk in about an hour, or right before my turn, gimme a ping please...I should be at my lappy, just in another term building rpms and losing track of time :)
[18:54] <ScottK> nixternal: Sure thing.  You're welcome.
[18:54]  * _Artemis_Fowl_ leaves
[19:50] <Arby> Riddell: kopete-cryptography can't build because it depends on kdepim-kde4 which apparently no longer exists
[19:50] <Arby> Riddell: can I drop the dep or what replaces it?
[19:52] <Riddell> Arby: kdepim-kde4 is now kdepim
[19:52] <Riddell> which has failed to build
[19:52] <Arby> ah, bit of a block there then
[19:53] <Arby> it'll have to wait then
[19:54] <Arby> also , hooray MIR for QCA2 approved
[19:59] <Riddell> ooh, great
[20:03] <nixternal> Riddell, ScottK, Hobbsee == #ubuntu-meeting in a few for my core-dev app
[20:03] <Riddell> ooh
[20:03] <Arby> Riddell: if things are failing to build after upload due to missing build deps do I need to do anything?
[20:03] <Arby> or just wait until those pacjages are ready
[20:03] <Arby> *packages
[20:04] <Riddell> Arby: depends if it's the fault of the package or another package
[20:04] <Riddell> Arby: what are we talking about?
[20:04] <Arby> several things, let me find an example
[20:05] <Riddell> hi Xand3r, I approved screenie-qt, good job
[20:05] <smarter> print "Groovy"
[20:05] <smarter> I don't need to look at the copyright to know who did guidance-power-manager/cmake-modules/FindPyKDE.py ;)
[20:05] <Xand3r> Riddell: thx verry much
[20:06] <Arby> Riddell: for example http://launchpadlibrarian.net/15358768/buildlog_ubuntu-intrepid-amd64.kmldonkey_4%3A2.0.2-kde4.0.80-0ubuntu1_FAILEDTOBUILD.txt.gz
[20:07] <Arby> Riddell: much of the extragear stuff I've done is failing to upload
[20:07] <Arby> errors like 2008-06-17 15:53:06 WARNING     kcoloredit_4.0.80-0ubuntu1_ia64.deb: Version older than that in the archive. 4.0.80-0ubuntu1 <= 4:3.5.9-0ubuntu1
[20:07] <Riddell> Arby: "No rule to make target `/usr/lib/libSM.so'"
[20:07] <Riddell> Arby: that's the fault of kde4libs
[20:07] <Riddell> Arby: I fixed it yesterday
[20:07] <Riddell> Arby: are you able to retry that build?
[20:07] <Arby> can do yes
[20:07] <Arby> well locally I can
[20:08] <Riddell> Arby: I mean on launchpad
[20:08] <Riddell> it may be only core-devs who can
[20:08] <Arby> on launchpad no
[20:08] <Arby> I don't have the power
[20:08] <jpds> ~motu can
[20:10] <Arby> Riddell: for the version conflicts the '4:' seems to confuse the issue
[20:10] <Arby> not sure what to do about that
[20:11] <Riddell> Arby: retried kmldonkey
[20:11] <Arby> thanks
[20:11] <Riddell> Arby: kcoloredit needs that 4: epoch version then
[20:11] <Arby> *sigh* mass rebuild take 17
[20:14] <smarter> Riddell: guidance-power-manager.py has "version = 4.1.0", should I use that as the package version or 4.1.0~svn$(date -foo) ?
[20:34] <Arby> Riddell: I can't work out how to make kcoloredit take the epoch version
[20:34] <Arby> is it enough to just rename the files?
[20:40] <Riddell> Arby: no just change it in the changelog
[20:40] <Riddell> Arby: dch -i for a new changelog entry and stick a 4: at the front of the version there
[20:40] <Riddell> smarter: 4.1.0~svnfoo is good
[20:40] <Arby> I did that manually and it made no difference, let me try again with dch
[20:41] <\sh> Riddell: do you have a code beautifier for kate especially for python sources?
[20:41] <smarter> Riddell: okay
[20:43] <Riddell> \sh: nope
[20:46] <Arby> Riddell: didn't work. files are still named 4.0.80
[20:46] <Arby> changelog has kcoloredit (4:4.0.80-0ubuntu2) intrepid; urgency=low
[20:47] <Riddell> Arby: perfect
[20:47] <Arby> oh
[20:47] <Riddell> that's it then
[20:47]  * Arby <- confused
[20:47] <Arby> I was expecting the .dsc etc numbers to change
[20:48] <Riddell> naw, the epoch is mostly hidden, it's just used for when the numbering system gets screwed up
[20:48] <Arby> ah ok
[20:48] <Arby> files incoming then
[20:51] <Arby> Riddell: new .dsc and .diff.gz for kcoloredit on lichts
[20:51] <Arby> kiconedit to follow soon
[20:56] <Arby> Riddell: kiconedit done
[21:20] <Nightrose> Hobbsee: http://mfrost.typepad.com/cute_overload/2008/06/omg-ponies11.html ;-)
[21:26] <jpds> Nightrose: arg, überladen
[21:26] <Nightrose> ;-)
[21:31] <Arby> Riddell: kpovmodeler done, ready for upload
[21:37] <Arby> scratch that, needs a rebuild
[22:05] <Riddell> Arby: groovy, kdepim compiling away here for the next while
[22:05] <Arby> cool kpovmodeler fixed now
[22:05] <Arby> working on kfax now
[22:05] <Arby> Riddell: did I hear that extragear-plasma was going to disappear?
[22:10] <Riddell> Arby: yes, ignore it
[22:10] <nixternal> oi oi
[22:10] <nixternal> let me just say, editing .img files are so much fun!
[22:10] <Riddell> nixternal: feeling fit?
[22:10] <nixternal> no, feeling sore :)
[22:11] <nixternal> I think I dropped my buttocks a couple of towns over
[22:25] <Arby> Riddell: kfax done, ready for upload


[07:08] <otubo> powersj, I'm gonna take a look. Thanks!
[10:28] <andras-kovacs> huh... I didn't know Azure can be this terrible... I made a VM template with cloud-init installed in it, but disabled. My intention was to start to use it with Azure's own telemetry-collector whatnot than change to cloud-init as soon as possible.
[10:28] <andras-kovacs> But it says "[ProvisionError] cloud-init appears to be running, this is not expected, cannot continue."
[10:29] <andras-kovacs> I found a bug and the reason of it is/are probably the dhclient + NetworkManager scripts, but still...
[10:29] <andras-kovacs> I believed it can't be worse after the fixed-size IDE connected vhd files. But actually, it can.
[10:31] <andras-kovacs> https://github.com/Azure/WALinuxAgent/issues/806
[10:32] <andras-kovacs> I was wondering... why do they need to re-invent the wheel?
[11:37] <andras-kovacs> Even more funnier this waagent doesn't even log it's error on error level to journal. :D
[12:54] <StyXman> is it possble that if I deploy a user, setting its password  and marking it as expired, the password is set *after* it was marked as expired, so this password set overwrites the expiration date? BTW, there is no expriration date in /etc/shadow, only last change date and max password age
[12:56] <StyXman> here's my config: https://dpaste.org/4g89
[13:21] <StyXman> in fact it's a bug: the image I'm using has a adduser who ignores --expirredate and there seems to be a function to go arund such bugs, but it doesn't seem to be used
[13:53] <Odd_Bloke> StyXman: Are you saying it's a bug in the image you're using, or you think it's a bug in cloud-init?
[13:59] <StyXman> https://bugs.launchpad.net/cloud-init/+bug/1872995
[14:36] <otubo> Odd_Bloke, powersj by the way, just found another bug on the swap file stuff. But won't make it to the release cut this time. Can't make upstream/backport in less than an hour.
[14:36] <Odd_Bloke> otubo: OK, hm, should we back out the original change so we can reland it with these fixes applied?
[14:36] <otubo> Odd_Bloke, powersj I'll post another PR soon, together with a unittest.
[14:37] <otubo> Odd_Bloke, that part is correct, the assignment should be after the try/except. The bug is at create_swapfile()
[14:38] <otubo> cmd = ['fallocate', '-l', '%dM' % size, fname] ---> is treating size as %d when it is %s
[14:38] <otubo> errmsg = "Failed to create swapfile '%s' of size %dMB via %s: %s" ---> here too
[14:45] <otubo> Odd_Bloke, I'll fix it and include the unittest by tomorrow. No need to drop anything right now.
[14:45] <powersj> otubo, thank you!
[16:12] <mutantturkey> so i have only enabled a few specific modules from cloud init, but another thing cloud-init is doing is setting the 'hostname'
[16:12] <mutantturkey> i don't actually want it to do so, is there a way to prevent it from overwriting my hostname i set in my custom image?
[16:13] <blackboxsw> mutantturkey: the hostname gets set early in boot by cloud-init to fix a number of platforms that need hostname set before the initial dhcp request..... I'll get you where that's done.
[16:13] <blackboxsw> and we'll see if it can be disabled
[16:13] <mutantturkey> is it    199 ^[[0;32m    digitalocean: /usr/lib/python3/dist-packages/cloudinit/config/cc_set_hostname.py^[[0m
[16:13] <mutantturkey> sorry the output got munged
[16:14] <mutantturkey> i did find a "echo "preserve_hostname: true" > /etc/cloud/cloud.cfg.d/99_hostname.cfg" but i wasn't sure if that was accurate
[16:15] <blackboxsw> mutantturkey: it's in cloudinit/cmd/main.py
[16:15] <blackboxsw> mutantturkey: https://github.com/canonical/cloud-init/blob/master/cloudinit/cmd/main.py#L698-L713
[16:16] <blackboxsw> so it's set only if user-data or meta-data on the cloud provides that value
[16:16] <blackboxsw> but yes, ultimately calls cc_set_hostname
[16:17] <andras-kovacs> could you point me to the right direction to find a cloud.cfg which works in Azure? I mean which can set the hostname, etc. from the meta data.
[16:19] <blackboxsw> mutantturkey: you can check if DO provides that hostname in metadata with `cloud-init query --all`
[16:20]  * andras-kovacs sent a long message:  < https://matrix.org/_matrix/media/r0/download/matrix.org/SZJZxEKrgcFXnlWGZLCUSoed >
[16:20] <andras-kovacs> but cloud-init query -a gives [] nulland ""
[16:22] <mutantturkey> blackboxsw: cloud-int query --all: error argument subcommand: invalid choice 'query'
[16:23] <mutantturkey> cloud-init -v: 15:58 <@blackboxsw> but yes, ultimately calls cc_set_hostname
[16:23] <mutantturkey> sorry, /usr/bin/cloud-init 18.3
[16:23] <andras-kovacs> but I can read the meta data with curl... hmmm..
[16:23] <andras-kovacs> mutantturkey: cloud-init query -a
[16:24] <andras-kovacs> mutantturkey: I like your name. Do you watch SouthPark?
[16:24] <Odd_Bloke> andras-kovacs: Where is your current cloud.cfg coming from?
[16:24] <mutantturkey> andras-kovacs: no, i mean i have seen it, but i dont know the reference
[16:24] <Odd_Bloke> andras-kovacs: mutantturkey: 18.3 predates `cloud-init query` being available, I believe.
[16:24] <mutantturkey> Odd_Bloke: seems so
[16:25] <mutantturkey> i am fairly certain that the hostname is set by cloud init, as it sets it to the first part name of the DO box. (x.y.z: it is set to x)
[16:25] <mutantturkey> and the logs confirm
[16:26] <mutantturkey> Running command ['hostname', xzy]
[16:26] <andras-kovacs> Odd_Bloke: from the package, the default. So I need to play around with it. It worked so good with openstack for the first try. But Azure is really different. Do you have a link or sg. for a working sample config? I saw the one in the doc but I got confused because of the __builtin__ and dhclient_lease_file part.
[16:27] <mutantturkey> yeah; 2020-04-14 17:59:09,190 - util.py[DEBUG]: Read 51 bytes from /var/lib/cloud/data/set-hostname
[16:27] <andras-kovacs> I don't know yet how to define the the lease file, because I use NetworkManager and it looks like /var/lib/NetworkManager/dhclient-5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03-eth0.lease
[16:33] <Odd_Bloke> andras-kovacs: "the package" on what distro?  It works out of the box on Ubuntu, and I haven't heard of any other substantial issues.
[16:56] <andras-kovacs> RedHat 7.8. I could proceed further, but now I see: DataSourceAzure.py[WARNING]: Could not crawl Azure metadata: No Azure metadata found.
[17:20] <Vitto> Hello, I am a novice programmer and I am trying to use the cloud init functionality via Scaleway API but cannot seem to get it to work. I have a working cloud init shellscript that does its job when launched via web dashboard. Instead, when I try to submit it via API it seems that the cloud init boot does detect the script. Is anyone able to help
[17:20] <Vitto> me?
[17:23] <rharper> hi Vitto  one possible issue is how the API attaches the user-data to their instance ... some platforms require the user-data content (cloud-config yaml) to be base64 encoded ... is there any API documentation on scaleway that migth help ?
[17:30] <johnsonshi> Hi guys, I have a question regarding trying to specify my own systemd unit to start in the middle of cloud-init.service and cloud-config.service. The question is here at: https://paste.ubuntu.com/p/tR6vMm6SGd/
[17:44] <Vitto> rharper this is the user data section of the scaleway API https://developers.scaleway.com/en/products/instance/api/#user-data-35f60e, it does not mention anything regarding base64 encoding, I'll ask them directly in the meanwhile.
[17:55] <mutantturkey> so documentation says hostname can be specified via hostname key, in my cloud-init ustom config would that be
[17:55] <mutantturkey> hostname: myname
[18:10] <mutantturkey> that worked, and since i know the expected hostname, my problem is solved. dope
[20:14] <Odd_Bloke> blackboxsw: rharper: https://github.com/canonical/cloud-init/pull/316 should fix swap file creation in master; I'd appreciate a speedy review so we can discuss cherry-picking it to fix focal before Final Freeze (tomorrow :p).
[20:14] <Odd_Bloke> otubo: Apologies to perhaps duplicate your work; today is the last day to get fixes into the next Ubuntu release on day one, so this is urgent for us. :)
[20:23] <blackboxsw> Odd_Bloke: +1 grabbing
[20:35] <blackboxsw> Odd_Bloke: nit comment  https://github.com/canonical/cloud-init/pull/316#pullrequestreview-394115233
[20:47] <blackboxsw> Odd_Bloke: I see in the failure path case on cc_mounts:create_swapfile that if create_swap fails, it deletes fname, but then create_swapfile proceeds to     util.chmod(fname, 0o600)
[20:47] <blackboxsw> which should no longer exist
[20:48] <blackboxsw> is it worth create_swap raising in the util.ProcessExecutionError failure path?
[20:48] <blackboxsw> just after the warning and del_file
[20:48] <Odd_Bloke> blackboxsw: I'm just trying to apply the minimal fix that gets previously-working configurations to continue working.
[20:49] <Odd_Bloke> (I'm not saying there isn't work to be done to improve the failure mode, but that's not RC.)
[20:49] <blackboxsw> good pt. so for that, we can avoid the failure path test case (because it exposes this error).  I was trying to write up a failure_path test to get coverage on the errmsg  template as well
[20:50] <blackboxsw> so we are good with happy_path test only
[20:50] <johnsonshi> Hi guys, does including both "After=cloud-config.target" and "Before=cloud-config.service"
[20:50] <johnsonshi>  in a custom systemd unit ensure that the custom systemd unit is started after cloud-init.service finishes but before cloud-config.service starts?
[20:50] <Odd_Bloke> blackboxsw: Responded to your comment; will also work to improve the tests here.
[20:51] <Odd_Bloke> (But I don't think we should block landing this on improved tests; it's completely broken right now, I can't make it worse with this change. :p)
[20:51] <blackboxsw> johnsonshi:  maybe After=network-online.target cloud-config.target and Before cloud-config.service
[20:51] <blackboxsw> Odd_Bloke: +1 on your PR with that in mind that we will have a followup
[20:52] <Odd_Bloke> blackboxsw: Ack, thanks.  (Can you mark that in GH so I can land it?)
[20:53] <blackboxsw> Odd_Bloke: merged
[20:55] <johnsonshi> blackboxsw: Thanks for the that tip! Hopefully this time the custom systemd unit should always run in the correct order. Thanks!
[21:02] <rharper> johnsonshi: I think your initial config is sufficient;   cloud-config.target already has After on cloud-init.service; and cloud-config.service runs after cloud-config.target;
[21:11] <blackboxsw> Odd_Bloke: rharper https://github.com/canonical/cloud-init/pull/318
[21:12] <blackboxsw> cherry-pick release to review
[21:12] <Odd_Bloke> I'm not 100% sure how to replicate that locally currently, but that LGTM.
[21:14] <blackboxsw> Odd_Bloke: sorry added cmdline steps
[21:14] <blackboxsw> to the PR description
[21:28] <Odd_Bloke> blackboxsw: +1
[21:33] <Odd_Bloke> blackboxsw: https://github.com/canonical/cloud-init/pull/319 is the best I can do for additional tests; the sad path is actually broken more deeply than just the variable substitution (as you pointed out), so I'll leave it for now.
[21:33] <blackboxsw> thanks Odd_Bloke will look it over before tomorrow
[21:39] <blackboxsw> community notice: [ubuntu/focal-proposed] cloud-init 20.1-10-g71af48df-0ubuntu4 (Waiting for approval)
[21:39] <blackboxsw> we are hoping to release that swap file creation into Ubuntu Focal before LTS  release is final