[17:22] <jdstrand> hi!
[17:22] <chrisccoulson> hi!
[17:22] <jdstrand> #startmeeting
[17:22] <meetingology> Meeting started Mon Nov 10 17:23:11 2014 UTC.  The chair is jdstrand. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:22] <meetingology> Available commands: action commands idea info link nick
[17:23] <jdstrand> The meeting agenda can be found at:
[17:23] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[17:23] <jdstrand> [TOPIC] Weekly stand-up report
[17:23] <jdstrand> I'll go first
[17:23] <jdstrand> I got pretty side-tracked last week with unplanned things
[17:24] <jdstrand> so, I'd like to finish the click-apparmor 0.3 for vivid and finish apparmor-easyprof-ubuntu for vivid
[17:24] <jdstrand> I'd also like to finish my update for click-reviewers-tools changes
[17:24] <jdstrand> once again, adjusting UCT for derivative branches
[17:24] <jdstrand> and then pending updates
[17:25] <jdstrand> that includes the sponsored konversation and kde-workspace that should go out today
[17:25] <jdstrand> mdeslaur: you'r up
[17:25] <jdstrand> mdeslaur: nm
[17:25] <jdstrand> sbeattie: you're up
[17:26] <mdeslaur> oh, I'm here now
[17:26]  * sbeattie pauses
[17:26] <mdeslaur> darn time zones
[17:26] <jdstrand> yes, my apologies
[17:26] <jdstrand> it is scheduled for ~ 1 hour ago
[17:26] <mdeslaur> I'm on triage this week
[17:26] <jdstrand> maybe next week...
[17:26] <mdeslaur> And have a few updates planned
[17:26] <mdeslaur> and an embargoed issue I need to look at
[17:27] <mdeslaur> and pending that, I'll be going down the list again
[17:27] <mdeslaur> that's it from me
[17:27] <mdeslaur> sbeattie: you're up
[17:28] <sbeattie> I'm working on the gcc pie-by-defaulton-x86-64 stuff; I have the patch applying cleanly again, and am currently hammering my laptop as it finishes building gcc locally.
[17:29] <sbeattie> Once that finishes, I'll start doing test builds of other packages against it.
[17:29] <sbeattie> I also need to do the usual apparmor stuff.
[17:29] <sbeattie> that's it for me; tyhicks?
[17:30] <tyhicks> I'm currently working a parser bug in trusty (LP: #1390592)
[17:31] <tyhicks> I've identified the bad patch and am in the process of testing a new package built with the correct upstream patch
[17:31] <tyhicks> after that, I need to revisit the dbus-daemon unrequested replies bug (LP: #1362469)
[17:32] <jdstrand> tyhicks: oh, it was the parser after all. and this is something for trusty sru?
[17:32] <sbeattie> tyhicks: oh, hunh, we have a different patch in ubuntu to add @{profile_name} from upstream?
[17:32] <tyhicks> jdstrand: it is something for a trusty sru - does someone have one in progress?
[17:32] <tyhicks> (I know we were talking about SRUing the python utils fixes)
[17:33] <jdstrand> I think sbeattie and mdeslaur were working to prepare one
[17:33]  * jdstrand isn't sure of the status
[17:33] <tyhicks> sbeattie: nope, the bad patch is one that attempted to fix and cleanup escape sequence handling
[17:33] <sbeattie> yeah, though I've mostly been doing prep work, I haven't got a tree in progress yep.
[17:33] <sbeattie> s/yep/yet/
[17:33] <sbeattie> oh, hrm.
[17:34] <tyhicks> sbeattie: ubuntu patch add-decimal-interp.patch should be replaced with upstream rev 2456
[17:34] <tyhicks> I have a bit more testing to do, though
[17:35] <tyhicks> re dbus-daemon unrequested replies bug> folks are thinking that the newer dbus might fix an issue that dbus-daemon is hitting in rtm
[17:36] <jdstrand> so, bug #1390592 is pretty important to fix
[17:36] <tyhicks> jdstrand: should we do an SRU just for it?
[17:37] <jdstrand> if we aren't planning to fix the python tools now, I think we should
[17:37] <tyhicks> ok
[17:37] <tyhicks> I should be able to prepare an SRU for that today
[17:37] <jdstrand> ok, thanks
[17:37] <tyhicks> np
[17:37] <sbeattie> okay, that's fine.
[17:38] <tyhicks> also, I'll continue work on turning the apparmor policy cache setup and loading code into a library
[17:38] <tyhicks> it has taken a little longer than expected but I finally feel like I'm making progress now
[17:38] <jdstrand> oh, I forgot-- I plan on finishing my upstream patch for docker so it can apply policy based on parser capabilities
[17:39] <tyhicks> (it is a little difficult to pull out the cache handling bits from the profile parser)
[17:39] <tyhicks> ok, that's it for me
[17:39] <tyhicks> chrisccoulson: I think it is your turn
[17:39] <tyhicks> skipping jjohansen and sarnold (time zone victims)
[17:40] <jdstrand> jj is off today
[17:40] <tyhicks> oh yes
[17:40] <chrisccoulson> this week, I'm hoping to finish off the header bar controls in oxide. I'm also going to be working on several bugs that affect single-process mode
[17:40] <chrisccoulson> I've just got chromium out (not for precise though)
[17:40] <chrisccoulson> and I've got one embargoed update to do
[17:41] <jdstrand> nice
[17:41] <chrisccoulson> I think that's me done
[17:41] <jdstrand> chrisccoulson: any news on precise?
[17:41] <mdeslaur> what's wrong with precise?
[17:41] <chrisccoulson> oh, and reviewing updates to the mediahub branch when they arrive
[17:42] <chrisccoulson> chad's still working on building a compiler that can actually build it
[17:42] <jdstrand> good stuff
[17:42] <jdstrand> [TOPIC] Highlighted packages
[17:42] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/stunnel4.html
[17:42] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/lib3ds.html
[17:42] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/qmail.html
[17:43] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/c-icap.html
[17:43] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/smokeping.html
[17:43] <jdstrand> The Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so.
[17:43] <jdstrand> See https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved.
[17:43] <jdstrand> [TOPIC] Miscellaneous and Questions
[17:43] <jdstrand> Does anyone have any other questions or items to discuss?
[17:47] <jdstrand> sarnold: hey, can you give a quick update?
[17:48] <sarnold> I'm on community this week; I have some outstanding apparmor patches to review, and I'd like to keep working on programming scopes and applications for the touch environment
[17:49] <sarnold> I found david planella's Ubuntu On Air video from last week really useful to understand the otherwise baffling ubuntu sdk environment, well worth watching that if you're new to it
[17:49] <sarnold> there's two more videos in the series, and even though they are ridiculously long, I found the first one worth watching, so I'll try the other two as well
[17:50] <sarnold> that's me; is it back to jdstrand or chrisccoulson?
[17:51] <jdstrand> me
[17:51] <jdstrand> but actually, that's it
[17:51] <jdstrand> sarnold: thanks :)
[17:52] <jdstrand> mdeslaur, sbeattie, tyhicks,chrisccoulson, sarnold: thanks!
[17:52] <jdstrand> #endmeeting
[17:52] <meetingology> Meeting ended Mon Nov 10 17:52:58 2014 UTC.
[17:52] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-11-10-17.23.moin.txt
[17:52] <mdeslaur> thanks jdstrand!
[17:53] <sbeattie> jdstrand: thanks!
[17:54] <sarnold> jdstrand: thanks!


[04:52] <CIA-12> Ubuntu Documentation: mantha feisty * r4022 /edubuntu/ (5 files in 2 dirs):
[04:52] <CIA-12> Ubuntu Documentation: * update changelog to 0.6-1
[04:52] <CIA-12> Ubuntu Documentation: * install images
[04:52] <CIA-12> Ubuntu Documentation: * take out Build-Depends-Indep as we aren't building anything
[04:52] <CIA-12> Ubuntu Documentation: * updated image links to the right path
[04:52] <CIA-12> Ubuntu Documentation: * updated Student Control Panel to Thin Client Manager
[05:13] <CIA-12> Ubuntu Documentation: mantha * r4023 edubuntu/ (7 files in 3 dirs): * sync from Feisty branch r4022
[05:15] <nixternal> go LaserJock go!
[05:20] <LaserJock> wahoo ;-)
[05:20] <nixternal> yes, I wrote 2 more handbooks for KDE today ;)
 :)
[05:20] <LaserJock> cool
[05:21] <nixternal> and my code for the "new" khelpcenter of course broke it ;p
[05:21] <LaserJock> I can't figure out where these update*.png files are from
[05:21] <LaserJock> well, I mean, I don't have them
[05:21] <LaserJock> and I don't know where the references came from
[05:21] <nixternal> there is no telling. I can't believe they would wipe the old svn server before checking though
[05:21] <nixternal> truthfully..
[05:22] <nixternal> YOU KNOW WHAT!!!
[05:22] <nixternal> those images are from the old Cookbook that got nuked I bet
[05:23] <LaserJock> hmm
[05:24] <LaserJock> that's really really old though for screenshots
[05:26] <nixternal> ya, they didn't create the handbook from scratch, they copied in all of the old cookbook stuff
[05:26] <nixternal> I went through about 90% of it updating it, that I do remember
[05:26] <nixternal> and removing :) and :( from every other paragraph
[05:27] <LaserJock> bah
[05:27] <LaserJock> well, I see a lot of ''' for bolds
[05:27] <nixternal> ya, the handbook never stood a chance 6 months to a year ago for sure
[05:27] <nixternal> that is the cookbook pull in from the wiki
[05:27] <nixternal> I thought I got all of those
[05:29] <LaserJock> you know, I sort of wonder if we had so many copies of this stuff running around that maybe some of your stuff got reverted :(
[05:30] <nixternal> very well could have been, but here is the thing, it would have been me reverting it unless someone else had svn access to our server
[05:30] <LaserJock> i.e. me
[05:30] <LaserJock> I uploaded some stuff from sbalneav
[05:31] <LaserJock> I wonder if it was based on older stuff
[05:31] <LaserJock> I *thought* it was from the doc team svn
[05:31] <nixternal> well, sbalneav's stuff would have been all LTSP I would think
[05:32] <nixternal> I didn't touch any of the LTSP stuff except to clean it up so that it would at least validate
[05:33] <LaserJock> ok, that's where the problems I'm seeing are from
[05:34] <nixternal> heh, he must have been working from a wiki then
[05:34] <LaserJock> I think maybe he just hasn't gotten to that section
[05:34] <LaserJock> it's the last in the LTSP chapter
[05:35] <LaserJock> anyway, I sooo don't have time for it all :-)
[05:35] <nixternal> very well could have been
[05:35] <LaserJock> I think I'll get some new stuff from sbalneav
[05:35] <LaserJock> cbx33 is doing TCM screenshots
[05:35] <LaserJock> and ogra is proofreading
[05:35] <nixternal> there was a lot of bad original docs to begin with, that is why I never really pressed for SVN accounts
[08:59] <mdke> morning
[11:10] <ubotu> New bug: #100090 in xubuntu-docs (main) "No link to xubuntu-docs, bout Xfce box refers to Xfce docs." [Undecided,Unconfirmed]  https://launchpad.net/bugs/100090
[02:10] <ubotu> New bug: #101864 in ubuntu-docs (main) "Wrong reference in windows document" [Undecided,Unconfirmed]  https://launchpad.net/bugs/101864
[07:17] <ubotu> New bug: #101894 in xubuntu-docs (main) "Spelling error in 1 st line of "New to Linux"" [Undecided,Confirmed]  https://launchpad.net/bugs/101894
[07:46] <ubotu> New bug: #101930 in ubuntu-doc "Shared Folders is not documented" [Medium,Confirmed]  https://launchpad.net/bugs/101930
[07:48] <nixternal> stop with the New bugs already you stinkin' bot!
[07:55] <LaserJock> heh
[07:55] <LaserJock> we just need it to automatically close all new bugs ;-)
[07:56] <nixternal> lol
[07:56] <nixternal> dude, look at the bugs chan
[07:56] <nixternal> he is constantly spitting out new bugs
[07:56] <nixternal> sumpin' tells me they are either working on the bot, or the bot is broke
[07:57] <nixternal> hrmm
[07:57] <LaserJock> Seveas said a little while ago that he broke it
[07:58] <nixternal> I need to figure out how to setup a custom highlight for ubugtu so I can see his messages over everyone elses
[07:58] <nixternal> heh, go figure, he is constantly breakin' his puppets
[08:52] <CIA-12> Ubuntu Documentation: mdke feisty * r4024 /ubuntu/ (19 files in 18 dirs): tweaks to translate script, trying to get it to work; unnecessary pot rebuild.
[08:52] <mdke> and now the high five
[09:13] <nixternal> hiya mdke! getting the bot high isn't recommended ;)
[09:16] <mdke> nixternal: hiya
[09:17] <mdke> translations this cycle are going to be a challenge
[09:17] <nixternal> so it seems
[09:17] <nixternal> they started late for one, and it seems they aren't being translated as quickly
[09:18] <nixternal> I think that if/when the community switches to the repo setup for development purposes, or the one source thing, that it might make it easier
[09:19] <mdke> well, the translations are going pretty fast actually
[09:19] <nixternal> it seems that KDE and GNOME have no problems with it, and their process seems larger than ours when it comes to translations
[09:19] <mdke> I mean, importing them will be a challenge
[09:19] <nixternal> ahh
[09:19] <nixternal> we can't use the old scripts, or at least tweak them a bit?
[09:20] <mdke> yeah, we have an improved script :)
[09:21] <nixternal> woohoo
[09:21] <nixternal> well that is good at least
[09:21] <mdke> and I'm going to work on danilo to do one which can regenerate fixed translations for upload to launchpad so our changes are not lost
[09:21] <nixternal> ahh, now that would be awesome
[09:21] <mdke> the improved script will allow translators to do their own testing too, so hopefully that will help lessen the burden a bit
[09:22] <nixternal> with Edgy the burden wasn't as bad as it was with Dapper, and I am hoping the trend continues
[09:22] <mdke> we'll see!
[09:23] <nixternal> hhe
[09:23] <nixternal> err, hehe rather
[09:23] <Gwaihir> mdke: I wanted to test in these days the italian translations...
[09:23] <mdke> Gwaihir: I'll try and post about how to do it soon. I need to make sure things are working
[09:23] <Gwaihir> great!
[09:25] <mdke> bbl
[10:21] <ubotu> New bug: #102059 in kubuntu-docs (main) "kubuntu-docs contains another incorrect string" [Undecided,Unconfirmed]  https://launchpad.net/bugs/102059
[11:02] <Admiral_Chicago> does someone have a link to the trunk of the docs
[11:03] <Admiral_Chicago> ah wait nvm
[11:04] <Admiral_Chicago> found it...topics are good.
[11:21] <mdke> wait for it...
[11:31] <CIA-12> Ubuntu Documentation: mdke feisty * r4025 /ubuntu/ (902 files in 17 dirs): adding initial po files download, for testing
[11:31] <mdke> phew, that's a lot of dots


[07:20] <doko> Riddell: see the mail to ubuntu-devel, after the flight-1 CD
[09:14] <Riddell> doko: ok, well qt and above are all sitting here waiting on it so I look forward to being able to upload :)
[01:18] <jbailey> doko: Thinking of which.
[01:18] <jbailey> doko: kyle pointed out that monticito is dropped ia32 compatability in hardware.
[01:19] <jbailey> So I'm wondering if we should drop ia32-libs for ia64 for now, or if there's a software emulator we should be using for those cases?
[01:20] <doko> hmm, why keep it at all?
[01:21] <jbailey> Only for openoffice and such.
[01:21] <jbailey> But if we could drop it without consequence, it would save some hassle, I think.
[01:22] <doko> to drop it we need libc6-i386-dev first, *hint*, *hint* ;-P
[01:22] <fabbione> doko: hey dude
[01:22] <fabbione> hi jbailey
[01:22] <fabbione> so when is the libstdc++++++ transition++ planned to start?
[01:23] <jbailey> Heya Fabio
[01:23] <fabbione> immediatly after flying-1 or will you give us time to stop the buildd?
[01:27] <doko> fabbione: sure, but I want to be able to build it probably before the weekend
[01:27] <fabbione> doko: for me it's enough to be able to stop the buildd before you upload the 3 billion pkgs :)
[03:47] <lamont-away> so what's the word on new gcc?  should I start the hppa buildd back up for now?
[04:16] <doko> lamont-away: please do, we are waiting for the flight-1 CD
[06:21] <doko> jbailey: ping
[06:21] <doko> jbailey: any estimate for 2.3.6?
[06:27] <jbailey> doko: Upstream or in Ubuntu, and with which features?
[06:29] <doko> jbailey: Ubuntu, merges and libc6-i386
[06:29] <jbailey> merges will be post-flight-1, 2.3.6 from upstream will be this afternoon (with the X fix).
[06:29] <jbailey> libc6-i386 should probably be after, since it means fixing ia32-libs at the same time.
[06:31] <jbailey> doko: Anything else you need in before flight-1?
[06:33] <doko> jbailey: no, not at all
[06:33] <jbailey> Luvly.
[08:11] <lamont-away> uh, doko....
[08:11] <lamont-away> expect-tcl8.3 [!hppa !hurd-any !hurd-i386]
[08:11] <lamont-away> from debian gcc-4.0...
[08:11] <lamont-away> which then ftbfs
[08:20] <doko> hmm, ok, it's already in the archive, fixed for the next one
[08:26] <elmo> oi, lamont
[08:26] <lamont-away> hi elmo
[08:27] <lamont-away> doko: that was gcc-4.0_4.0.2-4
[08:27] <elmo> lamont-away: did you manually upload binutils for hppa in Debian?
[08:27] <lamont-away> uh.  I don't remember doing that particularly
[08:28] <lamont-away> elmo: talking about expect b0rkage type issues or something else?
[08:28] <elmo> lamont-away: yes, I suspect so
[08:28] <elmo> both builds on the buildd failed with testsuite death
[08:28] <elmo> and yet a binary "appeared" in the archive
[08:28] <elmo> with no corresponding successful build
[08:28] <lamont-away> quite possible that I helped it along - but I don't think I manually built it, no.
[08:28] <lamont-away> who's sig on the .changes?
[08:29] <elmo> that'd be like.. effort.  can't you just admit it? :-P
[08:29] <lamont-away> (my normal involvement with expect and hppa's buildd comes in the form of 'killall -9 expect' once the build hangs
[08:29] <lamont-away> but those give you success logs...
[08:30] <lamont-away> I wish expect would either switch to tcl8.3, or they would fix the threads in 8.4
[08:32] <lamont-away> elmo: fwiw, it'd be really cool if the .changes files were publicly available somewhere.
[08:33] <lamont-away> (for both debian and ubuntu)
[08:33] <elmo> they are, on merkel
[08:33] <elmo> for debian, for ubuntu - yeah
[08:33] <lamont-away> oh, even better
[08:33] <elmo> I don't want to bloat the archive with them tho
[08:33] <doko> elmo: that was me. I tried with expect first, which failed, then expect-tcl8.3. you should have a mail in your mailbox
[08:33] <lamont-away> no sense to mirror them, that's for sure
[08:33] <lamont-away> elmo: see, I'm innocent
[08:34] <elmo> ok, doko and lamont are not allowed to go to conferences anymore
[08:34] <elmo> clearly doko has been hanging around lamont too long ;-P
[08:34] <lamont-away> elmo - I always leave tracks.
[08:34] <elmo> doko: dude, the correct fix for that is a bug, not a random upload of a package that can't be built on the buildds
[08:42] <doko> elmo: submitted.
[08:56] <lamont-away> elmo: fwiw, doko is just one more in the long line of people who "fix" hppa build failures that I've left failed by uploading something they built themselves.  go debian
[08:58] <jbailey> lamont-away: There is possibly a reasonable argument that the buildd is broken if it fails to build something that can be reasonably built in a clean chroot on a standard Debian setup.
[08:58] <elmo> jbailey: dude, this is NOT the buildd being broken
[08:58] <elmo> jbailey: and even if it was, that's not an even remotely sane argument
[08:58] <elmo> this same buildd has to be used for security builds
[08:59] <jbailey> Right, but if the buildd is configured in a different way than the standard OS (different kernel, different kernel settings), then that machine is misconfigured in an important way
[08:59] <elmo> and should be fixed
[08:59] <elmo> not worked around
[08:59] <jbailey> I'm not saying the right soluton is to build it yourself and upload it.
[09:00] <jbailey> I'm arguing that having alignment checking turned on by default on the buildd machines for hppa and not on the standard hppa kernel is probably a bug.
[09:00] <jbailey> Among other tweaks that might be done to various buildds.
[09:00] <jbailey> rather alignment checking turned on for standard builds, and not turned on for the buildd.
[09:00] <elmo> yeah, fine I can agree with that
[09:00] <jbailey> But you know what I mean.
[09:01] <elmo> but one day, I really am going to block non-buildd uploads in debian too :-P
[09:01] <lamont-away> jbailey: yeah...
[09:01] <lamont-away> but I can't really file a bug against camm for having broken thinking in how he does packaging.
[09:01] <lamont-away> although i suppose I could file a bug against the b0rked packages - not that it would change much
[09:02] <jbailey> elmo: And I will phear i386 on Debian so much less when you do. =)
[09:02] <jbailey> lamont-away: Hmm, bug queues on people.
[09:02] <jbailey> lamont-away: I wonder if there should be some ritual when people show up at Debconf where the people with the most bugs on them get thrown out on the assumption that they must be mouldy and rotten?
[09:03] <jbailey> Or perhaps we can be gentler and write "corpse" on their forehead with indelible marker? =)
[09:05] <lamont-away> with a sharpie.  the day before a job interview.  upside down.
[09:07] <elmo> what's a sharpie?
[09:07] <lamont-away> permanent marker
[09:07] <lamont-away> "sharpie" is a brand name
[09:08] <lamont-away> the person was up for several hours turning his autographed forehead into a red not-quite-bloody forehead.
[09:09] <elmo> oh
[09:09] <elmo> I assume it was like those compasses you had at school, the one with the sharp metal ends
[09:09] <elmo> which would have been, like, harsh
[09:11] <lamont-away> yeah, well, they would have had a hard time talking George into it, too... as it was, they just bodily carried jack over and said "Mr Takei, would you please sign this?  thx"
[09:13] <lamont-away> hrm.. /me realizes that signing foreheads has nothing to do with toolchains anywhere, let alone ubuntu


 Forwarded from matrix_t2bot: *Standreas*: https://lxqt-project.org/release/2023/04/15/release-lxqt-1-3-0/
 Nice!
 It won't land in 23.04 but it should be in Backports in the next week or two, and definitely in 23.10
 Perfect


[02:43] <THKitten> anyone here know anything about sidekiq?
[02:43] <THKitten> I'm getting an error I don't know how to resolve
[03:02] <tomreyn> have you tried #ruby?
[03:05] <sarnold> or giving details? :)
[18:10] <dvergurinn> hey guys, pretty new to setting up a cluster with maas and i'm looking at PXE booting a poweredge t310 which i am intending to provision and commission as a MAAS node where the regional controller is on another server. i have the second eth nic for each server connected to an offline router which i have turned off DHCP and reserved the addresses for my two servers.
[18:11] <dvergurinn> i am actually having trouble finding info online about how to make sure that my bmc firmware is confed correctly and also how to connect, or know that i've connected, to PXE. expecially from MAAS
[18:12] <dvergurinn> i guess i'm looking for a general run through?
[18:13] <dvergurinn> or should i be asking a more MAAS specific question for this?
[19:41] <dvergurinn> anyone around ????????????
[19:54] <dvergurinn> am i in the right group for questions?
[22:26] <penguinepimple> hi, i'm having an issue with setting up a maas cluster. in that i have one server that needs PXE booted and i'm a complete nood to maas and pxe. i was wondering how i would register my PXE boot device in maas to allow it to be remotely booted?
[22:30] <penguinepimple> the second server that i'm looking to PXE boot is a poweredge t310, is it makes a difference
[22:30] <penguinepimple> i'm basically looking for an overview, or a run through of what i should be doing or paying attention to
[23:02] <penguinepimple> anyone have any suggestions?
[23:08] <OerHeks> penguinepimple, i am interested in maas and saas too, maybe this is a help https://blog.ubuntu.com/2018/03/06/maas-for-the-home
[23:09] <OerHeks> and then back to https://docs.maas.io/1.9/en/intro-architecture
[23:20] <penguinepimple> @OerHeks, ok, that first one is pretty good. i'm looking through it right now.
[23:21] <penguinepimple> how far have you gotten with maas so far?
[23:21] <penguinepimple> ugh, far far
[23:22] <OerHeks> i just got my raid controller, and start to do the lvm works but not tonight :-D
[23:29] <penguinepimple> haha nice, a friend gave me his old lga771 dual xeon server a couple weekends ago, and i cleaned up the t310 from an e-cycle dump. it's missing its SAS drives only
[23:29] <OerHeks> 3 x 2Tb and 2 spare 1Tb  , on an i3 / 8gb
[23:40] <penguinepimple> very nice. yeah, i definitely need more storage to raid. especially on the t310.
[23:51] <OerHeks> all i need more is a private mirror, for speed and offline
[23:52] <OerHeks> As of September 2019, the Ubuntu Archive takes up approximately 1 TB of space.
[23:52] <OerHeks> funny, this doc is from the future
[23:52] <OerHeks> https://help.ubuntu.com/community/Rsyncmirror
[23:53] <OerHeks> so a pool of 2 spare would do


[15:10] <Tanvir> hello alokito
[15:12] <alokito> hi Tanvir
[15:14] <Tanvir> সচরাচর আমরা খুব বেশি মানুষ এই চ্যানেলে দেখি না।
[15:14] <Tanvir> আপনাকে দেখতে পেয়ে ভালো লাগছে
[15:14] <alokito> I know
[15:15] <alokito> please write english, pidgin is messing up bangla fonts in win7 :(
[15:15] <Tanvir> Hehehe
[15:15] <alokito> nice to see you too
[15:15] <alokito> whats your full name/online id?
[15:16] <Tanvir> You are logged in to ubuntu-bd using Windows. :P
[15:16] <alokito> yes
[15:16] <alokito> so? :P
[15:16] <Tanvir> Nothing. :)
[15:16] <alokito> ok
[15:16] <Tanvir> I'm Tanvir Rahman. Tanvir is my nickname on IRC.
[15:16] <alokito> it's pidgin's fault, not win's
[15:17] <alokito> ok, I'm Tanvir Mustafiz Khan
[15:17] <alokito> :D
[15:17] <Tanvir> Great!
[15:17] <alokito> yup
[15:17] <Tanvir> I'm also use pidgin, but in Ubuntu, that's quite okay for me.
[15:18] <Tanvir> Windows has problem to show bengali characters at many palaces.
[15:18] <alokito> pidgin has no rendering problem in linux
[15:18] <alokito> not really
[15:18] <Tanvir> Like Inkscape.
[15:18] <alokito> by default, yes... but not after you install avro
[15:18] <Tanvir> As I know you cannot write Bengali there, you need to copy-paste.
[15:18] <alokito> hmm all gtk apps I guess :-/
[15:19] <Tanvir> Aye, that one.
[15:19] <alokito> no longer, avro 5 supports ascii input!
[15:19] <Tanvir> Linux is great solution for that. XD
[15:19] <alokito> I use linux in other pc... not this one
[15:19] <alokito> this is for gaming :D
[15:19] <Tanvir> I'm using XChat now. Great client for IRC.
[15:19] <alokito> I know
[15:20] <alokito> no free windows version of XChat
[15:20] <Tanvir> I don't play video game usually. Not very fond of game too.
[15:20] <alokito> ok
[15:20] <Tanvir> There is!
[15:20] <alokito> hmm
[15:20] <Tanvir> I only played few games. The favorite one is..
[15:21] <alokito> no it's not free, XChat windows
[15:21] <Tanvir> 1) Project IGI: I'm Going In
[15:21] <alokito> afaik*
[15:21] <Tanvir> 2) Project IGI: Covert-strike
[15:21] <alokito> old game
[15:21] <Tanvir> 3) Far Cry
[15:21] <Tanvir> Yes, I know
[15:21] <Tanvir> But I loved those.
[15:21] <Tanvir> And still love them
[15:21] <alokito> yup I like far cry
[15:22] <Tanvir> Still I've Far Cry installed. XD
[15:22] <Tanvir> Oh, BTW, is there a cheat for Far Cry for not to die?
[15:22] <alokito> guess I'll download FC2... didn't play much
[15:22] <alokito> don't know, search google!
[15:22] <Tanvir> I googled.
[15:23] <Tanvir> But I didn't find cheats for that.
[15:23] <alokito> then there probably isn't
[15:23] <alokito> search for trainers
[15:23] <Tanvir> I got all ammos.. but not life. :P
[15:23] <Tanvir> And I'm afraid of Trygens. :P
[15:23] <alokito> trainers should have godmode
[15:23] <alokito> ? use antivirus
[15:24] <alokito> brb
[15:24] <Tanvir> I have avast free in Windows.
[15:24] <alokito> yup avast is good
[15:24] <alokito> I use it too
[15:25] <Tanvir> brb; now it's me. :P
[15:28] <Tanvir> And I'm back.
[15:57] <alokito> back


[00:27] <NCommander> doko, mind if I ask some glibc questions?
[00:28] <doko> just ask
[00:30] <NCommander> doko, to configure glibc to go into /lib32, vs /lib, it appears I need to set a few configure flags, but I'm kinda stumped on which ones those might be, and I was hoping you would know
[00:31] <doko> hmm, the current glibc package should work fine. afaicr we move things around after the build
[00:35] <NCommander> doko, I'm not building the package, sourceful build; I'm rebootstrapping the toolchain from scratch using a different set of CFLAGS (-fPIE/-fPIC enabled by default)
[00:36] <doko> sorry, don't know this by heart
[00:37]  * NCommander nods
[00:37] <NCommander> You work more with GCC itself vs. glibc if memory serves
[00:38] <doko> and it's 2am here, so maybe post to the list
[00:38] <doko> yep
[00:38] <NCommander> doko, you always ack my m68k toolchain patchs in Debian so thank you for that and your assistance ;-)
[02:35] <ScottK> doko: Still no luck on lpia.  I retried clamav and it failed with the same error and I don't see any successful lpia builds today.  I verified from the build log that gcc-4.3 4.3.2-1ubuntu4 was used.
[02:35] <ScottK> http://launchpadlibrarian.net/17354296/buildlog_ubuntu-intrepid-lpia.clamav_0.93.3.dfsg-1ubuntu1_FAILEDTOBUILD.txt.gz
[05:05] <NCommander> doko, is there a way I can place the -fPIE flag somewhere will it will only affect compilation and linking against 64-bit (-m64) targets, but not the 32-bit ones in a biarch compiler
[05:27] <ScottK> doko: Not just lpia either: http://launchpadlibrarian.net/17356138/buildlog_ubuntu-intrepid-ia64.kdelibs_4%3A3.5.10-0ubuntu3_FAILEDTOBUILD.txt.gz
[07:38] <lukehasnoname> so is it known/acceptable that I can't put LVM on top of encryption?
[07:54] <cjwatson> lukehasnoname: known, bug 267048. I think it's also Debian bug 494910 which would make it an easy fix; I'll look at it when I'm more awake
[07:59] <lukehasnoname> mk, just wanted to make sure that was a predictable occurance.
[09:46] <geser> doko: should gcc-4.3 (4.3.2-1ubuntu4) be good again?
[14:23] <ScottK> geser: It's not.
[14:40] <doko> geser, ScottK: what does 'ls -l /usr/lib/gcc/*' say on your local machine?
[14:42] <geser> on my local machine the symlinks are there
[15:11] <doko> geser, ScottK: thanks, sent email to ubuntu-devel. but I suppose we'lll have to wait for infinity or cprov-afk to have a look at the buildds
[15:17] <ScottK> doko: I also see the problem on ia64 and hppa:
[15:17] <ScottK> http://launchpadlibrarian.net/17360353/buildlog_ubuntu-intrepid-ia64.kdelibs_4%3A3.5.10-0ubuntu3_FAILEDTOBUILD.txt.gz
[15:17] <ScottK> http://launchpadlibrarian.net/17356476/buildlog_ubuntu-intrepid-hppa.kdelibs_4%3A3.5.10-0ubuntu3_FAILEDTOBUILD.txt.gz
[15:19] <ScottK> Additionally, it looks like primero (hppa) is broken in it's own special way as Hardy builds are dying there due to CHROOT problems.
[16:53] <EagleSn> hi
[16:55] <EagleSn> i am making a patch for a package, i am using: diff original.source.folder edited.source.folder > patch.diff
[16:55] <EagleSn> i am using it well?
[16:59] <cjwatson> EagleSn: diff -ru
[16:59] <cjwatson> (never use diff without the -u option)
[17:00] <cjwatson> if you created new files, diff -ruN
[17:00] <EagleSn> -run == -Nur
[17:00] <cjwatson> incorrect, -n != -N
[17:01] <EagleSn> thanks you
[17:12] <EagleSn>  if i want to build a new binary debian package with my patch applied, i think i have to make debian/patched folder and copy my patch into, then debuild will apply my patch automatically, am i right?
[17:13] <ion_> pitti, tkamppeter: Rebased the CUPS patch again.
[17:13] <cjwatson> if there isn't a debian/patches directory already, you should just apply the patch rather than adding a patch system
[17:16] <EagleSn> cjwatson than my patch wont be in the sources
[17:30] <ion_> pitti: Btw, using ${vcs}-buildpackage or equivalent would entirely remove the possibility of local changes sneaking into diff.gz. :-)
[18:55] <fta> since 2.6.27, top and ps are acting strangely... http://www.sofaraway.org/ubuntu/tmp/top.gif
[18:55] <fta> (look at %cpu)
[19:00] <EagleSn> hi
[19:27] <cjwatson> EagleSn: what makes you say your patch won't be in the source if you just apply it directly?
[19:27] <cjwatson> EagleSn: (obviously if there already is a debian/patches/ directory then it's usually best to add the patch there.)
[19:31] <EagleSn> yeah
[19:32] <EagleSn> then i apply my patch directly to sources
[19:32] <EagleSn> patch -p1 routr/to/my/patch
[19:32] <EagleSn> i will submit my patch in Launchpad, then i want to make it correctly
[19:34] <cjwatson> EagleSn: you should follow https://wiki.ubuntu.com/PackagingGuide/Howtos/Debdiff, then
[19:35] <EagleSn> i already have read it
[19:36] <EagleSn> but the patches i usually see in surces are not debdiff, they are diff or patch extension
[19:36] <cjwatson> it's the same format
[19:37] <cjwatson> you can apply any of them with patch
[19:37] <cjwatson> the debdiff program just ensures some basic level of consistency in how the patch is created, and so is preferred for patches submitted as Ubuntu bug reports
[19:56] <EagleSn> gpg gives me error at singing, it is as my passphrase was incorrect
[19:57] <EagleSn> is any way to see my passphare for gpg? i dont use it since much time ago, may be i am typing it wrongly
[19:57] <jpds> No, when you lose a passphrase, the key is useless.
[19:58] <EagleSn> any quickly way to gpg ask me for password and can try multiple?
[19:59] <jpds> The option: "--passphrase-repeat N" might help.
[20:00] <EagleSn> debsign?
[20:00] <jpds> No, that's a gpg option.
[20:02] <EagleSn> --passphrase-repeat N must be typed in debuild command?
[20:02] <jpds> Forget it, I just remembered that option is used when creating keys.
[20:03] <EagleSn> i ma lamost sure that i am typing well the pasphrase
[20:03] <EagleSn> i have imported today my gpg key, may be i imported it bad
[20:05] <EagleSn> i have 4 files: my-private.key; my-public.key; mykey-ASCII.asc and revoke-mykey.asc
[20:06] <EagleSn> i also printed my key in ASCII in paper
[20:15] <EagleSn> i did gpg --import my-public.key
[20:15] <EagleSn> gpg --import my-private.key
[20:15] <EagleSn> was it enought for restoring my key?
[20:21] <EagleSn> is it possible that gpg is working bas in Intrepid?
[20:22] <EagleSn> working bad *
[20:22] <cjwatson> I've not heard any complaints from developers who use it all the time
[20:22] <cjwatson> check gpg --list-secret-keys output to make sure it imported your secret key to the right place
[20:23] <EagleSn> right place?
[20:23] <cjwatson> gpg maintains two different keyrings, one for public keys and one for secret keys
[20:23] <cjwatson> gpg --list-secret-keys will show the contents of the secret keyring
[20:24] <EagleSn> i ma sure that i am entering well my passphrase, i have done an experiment to know it, and gpg fails
[20:24] <cjwatson> why do you care about the signature anyway?
[20:25] <cjwatson> if you're just going to produce a debdiff, it doesn't matter if the signing step fails
[20:25] <EagleSn> i think it is important
[20:25] <cjwatson> that only matters if you have upload privileges and are going to upload it to an archive
[20:26] <EagleSn> okay, but i would like to discover what is happening with my sign
[20:26] <cjwatson> what is the error message from gpg?
[20:26] <EagleSn> it is in Spanish
[20:26] <cjwatson> 'LC_ALL=C debsign'
[20:27] <EagleSn> i think there is a coomand to all output in console to be in English
[20:27] <cjwatson> export LC_ALL=C
[20:28] <EagleSn> that only affects to this terminal session?
[20:28] <cjwatson> yes
[20:28] <cjwatson> (this is quite basic; you might want to go elsewhere for general Unix help)
[20:30] <EagleSn> when it ask me for pass, if i put it wrong intentionally, it warn me about it is incorrect, and ask for me again until 3 times
[20:30] <cjwatson> if gpg is literally saying that your passphrase is wrong, then there are two possibilities: (1) you have another secret key with that UID etc., and gpg is using that rather than the one you expected (you can force it with 'debsign -kKEYID'), or (2) your passphrase is wrong
[20:31] <EagleSn> yes, but if i put the pass correctly, it do not tell me that it is incorrect, directtly gives me an error
[20:31] <Mithrandir> you can set it permanently in ~/.devscripts by having DEBSIGN_KEYID=$yourkeyid there.
[20:32] <Mithrandir> you need to provide us with the error if we're going to help you debug it.
[20:32] <EagleSn> yes, now
[20:32] <EagleSn> now it is asking for pass, ok i am going to put it correctly
[20:34] <EagleSn> look http://paste.ubuntu.com/44299/
[20:37] <EagleSn> gpg: problem with the agent - disabling agent use
[20:37] <EagleSn> that appears before i type passphrase
[20:39] <cjwatson> comment out use-agent in ~/.gnupg/options; or else (if you're intending to use an agent) configure the agent to keep your key for some reasonable amount of time, and prime it in advance by signing some random bit of text
[20:39] <cjwatson> (I use http://people.ubuntu.com/~cjwatson/tmp/gpg-refresh-cache for the latter purpose)
[20:40] <EagleSn> i dont understand nothing lol
[20:40] <EagleSn> reading the link
[20:40] <cjwatson> if you have no idea what I'm talking about, then make sure use-agent is not set in ~/.gnupg/options
[20:41] <cjwatson> and if you have no idea what I'm talking about, then gpg-refresh-cache is unlikely to be of any use to you
[20:42] <EagleSn> ok, what is agent than, wehere can i read some ?
[20:42] <cjwatson> oh, meh, we use an agent by default now, that's a bit annoying
[20:43] <cjwatson> EagleSn: I suggest just putting 'no-use-agent' at the end of ~/.gnupg/options (create that file if it doesn't already exist)
[20:43] <EagleSn> there is not options file in ./gnupg
[20:43] <cjwatson> as I just said, "create that file if it doesn't already exist"
[20:43] <EagleSn> ok
[20:44] <EagleSn> options file does need any header?
[20:44] <cjwatson> no
[20:44] <EagleSn> i did it
[20:45] <EagleSn> try debuild again?
[20:46] <cjwatson> please, this is a developer channel and we expect people to try things for themselves :)
[20:46] <EagleSn> i am doing it..
[20:47] <EagleSn> exactly tha samep roblem is happening
[21:33] <EagleScreen> cjwatson it seems that ./gnupg file is being ignored, see the output: http://paste.ubuntu.com/44322/
[22:07] <cjwatson> EagleScreen: oh, I suppose it's ~/.gnupg/gpg.conf now
[22:09] <EagleScreen> yes, i already did it
[22:09] <EagleScreen> there are no problem now
[22:09] <EagleScreen> thansk for your atention
[22:10] <EagleScreen> i think in Debian Agent is not used by default, may be by that i hadn't problems with this before, this is the first time I use debuild in an Ubuntu system
[22:24] <EagleScreen> where can i leanr the utility of gpg Agent?
[22:24] <EagleScreen> *learn
[22:33] <doggymenz> look, i have good idea for ubuntu to make it better
[22:33] <doggymenz> http://img504.imageshack.us/img504/3081/pinkvolumewz2.png
[22:49] <EagleScreen> doggymenz are you serious?
[22:49] <doggymenz> yes
[22:49] <doggymenz> you can choose color of volume partition, so you can have pink for porno, or maybe other color for something
[22:50] <EagleScreen> i think your idea is to can custom icon of disk drives?
[22:50] <doggymenz> ya
[22:50] <EagleScreen> report it to Launchpad and also in bugzilla
[22:50] <doggymenz> oh
[23:07] <doggymenz> i request 10000 packages on launchpad, but nobody make them
[23:49] <Ampelbein> hi there. i just tried uploading a source-package to my ppa but the build failed with the error "configure: error: C compiler cannot create executables". Is there something broken with my package or with the buildsystem?


[09:48] <MCR1> Is there a IRC channel dedicated to Compiz development also, now that Compiz has moved to lp ?
[09:54] <ahayzen> MCR1: From the compiz wiki...'#compiz channel  is for help and community chat, and the #compiz-dev channel is for discussion about development'... hope that helps
[09:55] <MCR1> ahayzen: Not really, because #compiz-dev is quite dead... :(
[09:55] <ahayzen> :(
[09:56] <MCR1> But I am happy that development of Compiz itself seemed to have moved to lp:compiz :)
[09:58] <MCR1> I am currently helping with adding "unsupported" plug-ins to lp:compiz (converting from git to bzr and merging with the new source), but I have some questions left and communication via launchpad is slow and ineffective
[09:58] <MCR1> https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1011083
[10:02] <MCR1> Uh oh! Launchpad down :P
[10:04] <MCR1> Is there a chance that Emerald might be used as future standard Unity-window-decorator ?
[10:05] <gord> not really
[10:08] <MCR1> gord: What are the arguments against it ?
[10:09] <gord> no one interested in doing the work? ;)
[10:17] <MCR1> gord: Actually there won't be much work involved in achieving this. In fact I got Emerald running here since ages, now on 12.04.
[10:18] <MCR1> gord: Currently the original source does not compile on 12.04, but somebody already fixed that - and there is just one small bug I know of in Emerald, which would have to be eliminated ofc.
[10:19] <MCR1> https://bugs.launchpad.net/compiz/+bug/1009570
[10:20] <mhr3> MCR1, what would be the benefit of using it?
[10:20] <MCR1> Multiple benefits :), mhr3
[10:20] <mhr3> like?
[10:21] <MCR1> glow, transparency, advanced visual appearance on the visual side
[10:21] <MCR1> also support for animated buttons
[10:22] <MCR1> a fully working and already developed configurator (Emerald Themer)
[10:22] <MCR1> and programmable title-bars and buttons on the functional side
[10:24] <mhr3> i see... so extreme customizability
[10:25] <MCR1> no, not only - we could make Quantal look really great with a default theme
[10:25] <MCR1> http://imagebin.org/216898
[10:25] <MCR1> but ofc I like the fact that I can shade/unshade set sticky/unsticky roll-up/down with a button ;)
[10:27] <MCR1> Unity-2d will be dropped as I've heard, so Emerald, which was designed for running with Compiz would be ideal for Ubuntu
[10:29] <MCR1> Unity is looking stylish already, combined with Emerald we could blow everything else away ;)
[10:29] <gord> well work would be needed to port the current theme over right? along with work to get zero pixel borders and such, i mean if you wanna do it, fantastic, get it working and get a conversation going
[10:30] <MCR1> That is why I am here ;)
[10:31] <MCR1> I want to help with Compiz/Unity development 8-)
[10:36] <MCR1> Got a launchpad account, already set up branches to merge with Compiz (wip) to get lost functionality back there (workspacenames is already merged with lp:compiz), but I would like to know, if there would be support for Emerald and what would need to happen to evolve Emerald to a point to be fit for Compiz/Unity in 12.10 ?
[10:41] <MCR1> Trevinho: I guess the question is for you ^^
[10:53] <gord> MCR1, you might try posting to the unity-dev mailing list
[10:55] <MCR1> gord: Yeah, probably should do that.
[10:57] <MCR1> Currently 44 branches are proposed for merging into Unity :)
[10:58] <MCR1> hmmm
[11:13] <MCR1> Just found out that by re-compressing the .png files in plugins/unityshell/resources (with Trimage Image Compressor) a lot of the png files could be optimized thus improving performance by lowering loading times - maybe I should add a branch for this ? : http://imagebin.org/216909
[11:15] <MCR1> I guess most of those .png files could also use indexed 8bit colors, which would further reduce filesizes 40-60%.
[11:17] <mhr3> MCR1, we've been there, it's a balance thing, you do less io, but more cpu to decompress it
[11:17] <MCR1> mhr3: So you ran actual tests on that ?
[11:18] <MCR1> on the indexed color thing as well ?
[11:18] <MCR1> 8bit->24bit vs. 40/100% filesize ?
[11:18] <mhr3> compression yes, indexed colors no afaik
[11:19] <MCR1> I guess all those values could differ a lot depending on the hardware used, no ?
[11:20] <MCR1> mhr3: Is there a link to those tests ?
[11:22] <mhr3> MCR1, sure, it's very hardware dependant, i dont think the results are still somewhere, it was comparison of daily build bootchart vs reference ones
[11:26] <MCR1> I guess there is quite a bit of potential regarding file and package sizes, maybe the improvements in loading performance might be partially eaten up by additional resources needed for conversion to 32bit and decompressing, but overall things should be much more optimized there, alone when thinking about package sizes and download times, no ?
[11:28] <MCR1> I mean, I see potential to lower the .png resources filesizes to about 30% of their current size, without any visual impact or regression...
[16:55] <jaytaoko> bschaefer: hello
[16:55] <bschaefer> jaytaoko, hey jay
[16:55] <jaytaoko> bschaefer: welcome!
[16:55] <bschaefer> thanks!
[16:56] <jaytaoko> bschaefer: do you have access to the internal wiki page
[16:56] <bschaefer> jaytaoko, nope, my account still doesn't have permission
[16:57] <bschaefer> jaytaoko, Ive emailed hr, but I haven't heard back
[16:59] <bschaefer> jaytaoko, so at this point im not sure what I should be doing haha
[16:59] <jaytaoko> bschaefer: ok, i am writing to #is. See if they can help...
[17:00] <bschaefer> jaytaoko, on freenode? cause I don't see anyone in #is
[17:00] <jaytaoko> bschaefer: it is on canonical... I don't think you have access yet
[17:01] <bschaefer> jaytaoko, yeah...hmm...
[17:07] <JanC> I suppose they are mostly the same people as #canonical-sysadmins on Freenode?  ;)
[17:08] <jaytaoko> bschaefer: someone from #is is looking into it...
[17:09] <bschaefer> jaytaoko, thanks!
[17:12] <bschaefer> JanC, thats good to know thanks!
[17:14] <bschaefer> jaytaoko, also thanks, talking with someone now
[17:15] <jaytaoko> bschaefer: yw!
[18:52] <bschaefer> jaytaoko, hey, so im all set up
[18:53] <bschaefer> jaytaoko, I don't see you on the other IRC, not sure what channel you're in
[18:54] <jaytaoko> bschaefer: good!, I am on #dx and #coding-ninjas
[18:54] <bschaefer> jaytaoko, sweet
[19:45] <Zhenech> charles, thanks for merging!
[19:51] <Neis> Hi all! I would like to know how I can integrate my application with the ubuntu hud
[19:52] <ahayzen> Neis: As long as your application works with the global menu then you are integrated with the HUD.
[19:54] <Neis> Mmm, I thought so, but when I run this simple python example, I can't find the exit in the hud...
[19:54] <Neis> http://zetcode.com/gui/pygtk/menus/
[19:57] <ahayzen> I had the same issue before with a python app...
[19:57] <ahayzen> hang on...
[19:57] <Neis> allright:)
[19:58] <ahayzen> how are you running the application?
[19:58] <Neis> from the console
[20:01] <ahayzen> i think i had to get it to change the process name or something
[20:01] <Neis> ok, I will search for that:)
[20:02] <ahayzen> it was like the application had to be 'installed'
[20:02] <Neis> Mmm
[20:02] <ahayzen> so it was like the name had to exist as an installed app
[20:04] <Neis> do I have to change the filename or the displayname or something? Cause changing the procesname is impossible I read on Google
[20:04] <ahayzen> Neis: This sortof works for me...http://pastebin.ubuntu.com/1047992/ ... i've changed my application name to nautilus
[20:04] <ahayzen> but don't know it if will work for u
[20:05] <Neis> yes it does:)
[20:05] <ahayzen> and it is in Gtk3
[20:05] <Neis> thanks:)
[20:05] <charles> Zhenech: no problem! :)
[20:05] <ahayzen> so u may have to port the Gtk => gtk etc unless you change to Gtk3
[20:05] <Neis> I will use Gtk3 from now on
[20:05] <Neis> thank you :)
[20:05] <Zhenech> charles, seems you were on a merging spree :)
[20:06] <ahayzen> Neis: http://python-gtk-3-tutorial.readthedocs.org/en/latest/index.html
[20:06] <ahayzen> that is a helpful tutorial for Python Gtk3
[20:06] <Neis> allright:)
[20:06] <charles> Zhenech: yes, an overdue one...
[20:09] <ahayzen> Neis: You can also find the undocumented stuff by going.... dir(Gtk)... then for a button... dir(Gtk.Button) ... this will then list the methods and classes etc
[20:09] <ahayzen> hope that helps
[20:10] <Neis> ahayzen: where do I have to type that? And do you also know if it is possible to send paramters via the HUD?
[20:11] <ahayzen> just run it from terminal...
[20:11] <ahayzen> andy@andy-XFX-Nforce-680i-LT:~$ python
[20:11] <ahayzen> Python 2.7.3 (default, Apr 20 2012, 22:39:59)
[20:11] <ahayzen> [GCC 4.6.3] on linux2
[20:11] <ahayzen> Type "help", "copyright", "credits" or "license" for more information.
[20:11] <ahayzen> >>> from gi.repository import Gtk
[20:11] <ahayzen> >>> print dir(Gtk)
[20:11] <ahayzen> Neis: What do u mean by send parameters?
[20:13] <Neis> Ah like that. WIll try in a minute. What I mean with sending paramters: like if i wanted to exit the application with a specific error code, i could type in the hud 'exit 0'  zero for example
[20:14] <ahayzen> i don't think that is currently possible.... the HUD is currently, to my understanding, just an extension or alternative to the current global menu
[20:14] <ahayzen> but you could create an menu entry called 'exit 0'
[20:15] <ahayzen> which then could be connected to a function that does what you want
[20:15] <Neis> yeah, but actually i wanted to create a simple chat app where you could respond in a chat via the hud:) Will have to tackle that one differently
[20:16] <Neis> thanks for your great help, that documentationfunction is really helpful
[20:16] <ahayzen> hmmm...would probably have to talk to some more knowledgeable people about who know more about HUD
[20:17] <Neis> I can try the mailing list
[20:17] <ahayzen> yep
[20:17] <ahayzen> i find Gtk3 is lots of trial and error at the moment as there isn't much documentation
[20:21] <Neis> programming can be a pain indeed
[20:23] <ahayzen> well it is new so all of the documentation is for the old version .... also everything is going to Python3 aswell
[20:23] <ahayzen> i am currently porting my applications to Python3
[20:42] <Neis> ahayzen: another thanks for your help. I'm outie:)
[22:09] <elky> Well, my work desktop has just done the disappearing icons thing
[22:12] <thumper> elky: that sucks
[22:12] <thumper> I've not found any reliable way to reproduce that bug
[22:15] <elky> It's probably one of the apps I always have open. I'm starting to think it could be keepassx because i don't always close it down when i move between computers.
[22:16] <thumper> elky: if you can work out how to reproduce it, we can fix it!
[22:17] <ajmitch> elky: that's the sort of thing that happens to me after being logged in for weeks
[22:17] <JanC> do you mean the icons in the launcher disappearing?
[22:17] <ajmitch> trying to reproduce it is a pain
[22:21] <elky> ajmitch, I've actually had it happen within hours, once.
[22:21] <elky> JanC, well for values of disappear. they get all piled on top of each other at the top of the panel
[22:22] <ajmitch> aka bug 806248 ?
[22:22] <elky> but their active areas are still spread out along the panel, but at exaggerated intervals
[22:22] <JanC> hah, I've seen both: piling up & disappearing
[22:22] <elky> yes, i didn't find that while looking. i raised a new one
[22:22] <ajmitch> it's been around for awhile, I first saw this happen in natty :)
[22:23] <elky> yeah, it's been around forever
[22:23] <JanC> and in both cases the intervals are exaggerated
[22:23] <elky> knowing what to search for is probably the limiting factor
[22:23] <elky> ZOMG IM NOT THE ONLY ONE
[22:24] <ajmitch> lucky you :)
[22:28] <thumper> I used to get it regularly on my desktop
[22:28] <thumper> not seen it for ages now
[22:28] <thumper> running precise now
[22:29] <elky> yeah ive never had it on my work desktop
[22:29] <elky> i'm now up to having access to 3 machines that it happens on
[22:30] <elky> https://bugs.launchpad.net/ubuntu/+source/unity/+bug/962852 is the bug i raised if someone wants to add it as a dupe


[07:02] <\sh> neversfelde: pong
[13:11] <JontheEchidna> Riddell, apachelogger: http://lists.kde.org/?l=kde-release-team&m=121996611510162&w=2
[13:14] <JontheEchidna> http://bugs.kde.org/show_bug.cgi?id=170162
[13:15] <apachelogger> JontheEchidna: I know about that
[13:15] <apachelogger> dirk fixed it in SVN and probably already rolled a new tarball
[13:15] <JontheEchidna> cool
[13:15] <apachelogger> I'll exchange the tarballs before uploading
[13:16] <apachelogger> or whenever I have time to
[13:16]  * JontheEchidna has to go now for a few hours
[13:16] <JontheEchidna> carwash
[13:16] <apachelogger> that sounds pretty boring ;-)
[13:16] <JontheEchidna> yeah...
[14:20] <apachelogger> hm, no tonio in sight :S
[15:28] <\sh> apachelogger: do you have contact to the quassel maintainer in debian?
[15:29] <apachelogger> \sh: no, I had at some point with a guy who wanted to abuse my packaging for debian
[15:29] <apachelogger> but we didn't hear anything ever since
[15:31] <\sh> apachelogger: ok...just wanted to make sure that you are not involved ...
[15:31] <apachelogger> \sh: are you starting an affair? :P
[15:32] <\sh> apachelogger: no
[15:32] <\sh> apachelogger: but I would like to see the package in debian what we have now in ubuntu ,-)
[15:33] <apachelogger> hm
[15:33] <apachelogger> mean joke
[15:33] <apachelogger> uhh
[15:33] <apachelogger> must resist
[16:05] <apachelogger> http://aplg.kollide.net/screencasts/fedora-root-fix-2.ogg
[16:09] <RainCT> Hi
[16:10] <apachelogger> ahoy RainCT
[16:11] <apachelogger> smarter: is kepas maintained in the kde svn?
[16:11] <RainCT> Does kio-apt only affect Konqueror or also other KDE applications? And would a /usr/share/services/*.protocol file affect the same applications as the ioslave?
[16:12] <apachelogger> RainCT: technically a kio slave can be access from anything which looks like an addressbar
[16:13] <apachelogger> kio-apt though provides the information through html
[16:13] <apachelogger> so it will only work in konqueror
[16:14]  * RainCT is working on a new apturl version and someone provided a .protocol file for it, so he needs to know if I need a "Conflicts: kio-apt" if I add that file to apturl, and if so, if adding a "Provides: kio-apt" too would be goot (so that replacing kio-apt in favour of apturl won't uninstall kubuntu-desktop)
[16:18]  * RainCT looks at apachelogger :)
[16:18] <apachelogger> E: Package kio-apt has no installation candidate
[16:22] <apachelogger> Deleted on 2008-08-28 by Jonathan Riddell (no kde 4 version)
[16:23] <RainCT> Oh, nice. /me wonders why he still has it in it's cache
[16:23] <apachelogger> RainCT: the source didn't get removed
[16:23] <apachelogger> jr is away until wednesday
[16:24] <apachelogger> I'll tell him to remove the source once he is back
[16:24] <RainCT> apachelogger: Alright. Thanks :)
[16:25] <RainCT> btw, does/will packagekit have a KDE version?
[16:26] <apachelogger> RainCT: pretty much so, otherwise it's gonna be the Qt GUI I guess
[16:27] <apachelogger> RainCT: http://www.kde-apps.org/content/show.php/KPackageKit?content=84745
[16:31] <RainCT> thx
[17:47] <smarter> apachelogger: IIRC, yes
[17:47]  * smarter checks
[17:48] <apachelogger> kdepim is completely broken btw
[17:48] <smarter> w00t
[17:48] <smarter> what's the problem?
[17:48] <apachelogger> dpkg-shlibdeps: failure: couldn't find library libkabcgroupwise.so.4 needed by debian/kdepim-wizards/usr/bin/groupwarewizard (its RPATH is '').
[17:48] <apachelogger> we don't package that file according to not-installed
[17:49] <apachelogger> so I have no clue how to make that anything like it won't mess up debian compatibility
[17:49] <smarter> why would it mess up compatibility?
[17:49] <apachelogger> if I introduce a new package we need to maintain an upgrade path
[17:50] <apachelogger> which is causing unnecessary diff from debian
[17:50] <smarter> add it to the same package that groupwarewizard?
[17:50] <apachelogger> that is kdepim-wizards
[17:50] <smarter> or see if the debian guys have already packaged 4.1.1 in their svn?
[17:51] <apachelogger> they don't
[17:51] <smarter> yay for introducing new lib files in minor releases
[17:51] <apachelogger> it's not new
[17:51] <apachelogger> the linking is just new apparently
[17:52] <apachelogger> I think I will just dump the files in libkdepim4
[17:52] <apachelogger> seems to be the most appropriate package
[17:52] <smarter> yep
[17:53] <smarter> http://websvn.kde.org/trunk/playground/network/kepas/
[17:53] <smarter> do  you think it's worth packaging a snapshot?
[17:54] <apachelogger> it is broken right now
[17:54] <smarter> maybe it needs a rebuild?
[17:54] <apachelogger> no
[17:54] <apachelogger> plasma api from 4.0 isn't compatible with 4.1
[17:55] <smarter> hmm, but they probably have good reasons not to release a 0.10/1.0
[17:55] <apachelogger> that is a pointless assumption :P
[17:56] <apachelogger> smarter: package a snapshot and test it
[17:56] <apachelogger> maybe get some others to test as well
[17:56] <apachelogger> if it works somewhat resonable upload it
[17:57] <ScottK> smarter: Did you see my ping about kde-pim changes needed for crypto support?
[17:59] <smarter> ScottK: about adding gnupg, pinentry and others to kmail deps?
[17:59] <ScottK> smarter: Yes.
[17:59] <ScottK> I guess that answers my questions.
[18:00] <smarter> :)
[18:00] <smarter> they were already suggested, I changed that to recommends so they get installed with kmail
[18:00] <ScottK> Not having that would be a regression from Hardy.
[18:00] <smarter> kdepim already build-deps on the appropriate packages
[18:00] <ScottK> Great.
[18:00] <ScottK> Debian can't make them recommends because some of the needed packages are extra while KDE Is optional.
[18:01] <ScottK> So it's a needed divergence (was a spec'ed improvement for Gutsy).
[18:01] <ScottK> Thanks.
[18:01] <smarter> you're welcome ;)
[18:54] <Arby> evening all
[18:58] <jpds> evening Arby
[19:11] <meven> is there someone using kdesvn-build to build kde trunk ?
[19:12] <meven> i would need tips about this tool
[19:17] <smarter> I used it
[19:21] <meven> with my config it seems to fail to checkout kde svn
[19:22] <smarter> it happens sometime
[19:22] <smarter> just let it finish and try again
[19:30] <meven> it stops
[19:31] <meven> apparently it tries to dowload an archive file for each module
[19:31] <jussi01> apachelogger: ping
[19:31] <meven> and doesn't find it
[19:32] <apachelogger> pong
[19:32] <apachelogger> jussi01:
[19:33] <jussi01> apachelogger: have you got a working, updated deb for firefox-qt?
[19:33] <apachelogger> isn't the current one working?
[19:34] <jussi01> apachelogger: sorry, should have mentioned the word, "hardy" in there
[19:34] <jussi01> yep
[19:34] <apachelogger> isn't the current one for hardy working?
[19:34] <jussi01> there is a current hardy one?
[19:35] <apachelogger> of course
[19:35] <jussi01> where?
[19:38] <meven> smarter: i have a solution, checkout the first time manually each modules
[19:39] <jussi01> apachelogger: ^^
[19:39] <apachelogger> in the repo
[19:39]  * apachelogger out
[19:39] <jussi01> which, your ppa?
[19:39] <jussi01> ok
[19:39] <apachelogger> killing kdepim
[20:14] <JontheEchidna> Riddell: updaten-notifier-kde should have taken care of bug 37461, correct?
[20:32] <apachelogger> JontheEchidna: yus
[20:33] <JontheEchidna> unfortunately update-notifier is borked. :P
[20:33] <JontheEchidna> meh
[20:34] <JontheEchidna> I'm going to have to use kate until that sonnet but is fixed
[20:45] <apachelogger> JontheEchidna: new packaging is already up
[20:46] <JontheEchidna> apachelogger: :D
[20:46] <JontheEchidna> which pacakge was affected>?
[20:46] <apachelogger> libs
[20:47] <JontheEchidna> thansk
[20:47] <JontheEchidna> blargh
[20:47] <jjesse> afternoon :)
[22:01] <Riddell> JontheEchidna: yes (to bug 37461)


[01:57] <cjwatson> sergio-br2: yes, that's the bug I referred to earlier, still trying to get it sorted out.
[04:14] <cjwatson> sergio-br2: fixed now
[04:14] <sergio-br2> yay
[04:17] <sergio-br2> oh my
[04:17] <sergio-br2> it's building
[04:18] <sergio-br2> https://code.launchpad.net/~dolphin-emu/+recipe/dolphin-daily-trusty
[04:18] <sergio-br2> exciting
[04:37] <sergio-br2> nice, it build
[04:37] <sergio-br2> I should move to git then
[04:37] <sergio-br2> because dolphin users often asks about the fancy git hash and the revision
[04:46] <sergio-br2> eh, I'm not getting the revision number...
[04:47] <sergio-br2> cjwatson, there's no .git/ at the source? Even using git repo?
[04:47] <sergio-br2> does launchpad just get the tarball from the master branch?
[06:38] <alkisg> Hi, the edubuntu live CD currently fails to build because it has a program of mine called epoptes preinstalled, and epoptes.postinst runs this commands, which fails on the live cd build environment:
[06:38] <alkisg> faketime '1970-01-01 00:00:00 UTC' openssl req -batch -x509 -nodes -newkey rsa:1024 -days $(($(date --utc +%s) / 86400 + 3652)) -keyout /tmp/epoptes.key -out /tmp/epoptes.crt
[06:38] <alkisg> The error is: "sem_open: Function not implemented"
[06:39] <alkisg> My problem is that I can't reproduce the error anywhere, in chroots, with or without /dev bind-mounted etc
[06:39] <alkisg> So I was thinking to ask, if someone here can tell me how is /dev mounted in the live cd build environment, so that I could reproduce the problem locally,
[06:40] <alkisg> or, if someone has ssh access to such an environment, to run that ^ command above and tell me that this is indeed the part that fails...
[06:56] <Peng> "rsa:1024"!?
[07:09] <wgrant> alkisg: faketime requires /run/shm to be mounted. Why do you need faketime?
[07:10] <Peng> "rsa:1024"?!
[07:10] <alkisg> Hi wgrant, first, I can't make faketime fail in a chroot, with or without mounting /dev etc. Could you give me a way to reproduce the issue?
[07:10] <wgrant> alkisg: Is it a chroot of the right Ubuntu series?
[07:11] <alkisg> highvoltage, the edubuntu maintainer, told me that it's happenning now on 16.04 edubuntu builds
[07:11] <wgrant> That would make sense.
[07:11] <wgrant> Are you testing in a 16.04 chroot?
[07:11] <alkisg> I don't have access to the logs, but he mailed me a big log (1 mb or so), I could put it somewhere if needed
[07:11] <alkisg> Yes
[07:11] <alkisg> And I can't make it fail no matter what I try
[07:11] <wgrant> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778462 is probably relevant
[07:12] <alkisg> About why I need it. epoptes.postinst creates a certificate. This by default is valid from today to +10 years. But some clients have failed CMOS batteries, and dates of e.g. 01-01-2000, and the certificate is invalid then. So I need faketime to force openssl to create a certificate valid since the Epoch.
[07:12] <alkisg> I've seen that bug report, but I can't reproduce it on 16.04
[07:12] <alkisg> Meh
[07:12] <wgrant> (in addition to Peng's point, is it save to have a certificate shared by all installations from that image...?)
[07:13] <alkisg> Sorry, no, I'm not trying on a 16.04 chroot. I was trying from 16.04 server to a wheezy chroot that I had handy. Trying on 16.04 chroot now...
[07:13] <wgrant> That's hopefully it.
[07:13]  * alkisg didn't realize Peng's point, sorry...
[07:13] <wgrant> 1024-bit RSA is pretty much obsolete at this point.
[07:14] <wgrant> It's within the realm of easy crackability.
[07:14] <Mikaela> the minimum considered as secure is currently 2048, and I think 4096 is recommended
[07:14] <wgrant> alkisg: So we should probably tell launchpad-buildd to mount /run/shm in the chroot if it exists, but this also raises the other crypto issues with the image build process.
[07:14] <wgrant> 4096 should be used for long-term keys, indeed.
[07:16] <alkisg> Thank you guys, I was able to reproduce it on a 16.04 chroot, and I'll increase 1024 to 4096.
[07:16] <alkisg> I'll work around it in epoptes.postinst, falling back to not using faketime there, it's up to you to do whatever's needed for /run/shm, epoptes.postinst won't fail though if it's not there
[07:17] <wgrant> alkisg: Does it make sense to generate the cert as part of the image build at all?
[07:18] <alkisg> Even if the certificate is public knowledge (it being on a live cd), I think it still offers encryption when there's no man in the middle
[07:18] <alkisg> It would be nice if edubuntu regenerated it dynamically, but it doesn't hurt to already have it there in the live cd
[15:27] <voldyman> how can i add a webhook from the web UI? it is mentioned in the webhook docs but can't find the link anywhere
[15:32] <cjwatson> voldyman: "Manage webhooks" on the branch or repository index page.
[15:33] <voldyman> cjwatson: i can't create say a webhook for all merge requests in a project?
[15:34] <voldyman> i am right now polling that information once per hour
[15:35] <cjwatson> voldyman: Only per target branch (Bazaar) or repository (Git) at the moment.  But even for a whole project, I would expect most of the merge requests to be targeted at the development focus.
[15:37] <voldyman> cjwatson: hmm, my use cases is that all the merge requests that are created in the projects under http://launchpad.net/elementary are posted in our slack. creating webhooks for each repo would be too much also i'll have to manually go and create the webhook for any new project
[15:40] <cjwatson> voldyman: Ah, you mean a project group then
[15:40] <voldyman> yup
[15:40] <cjwatson> voldyman: Do file a bug, it's probably not ridiculously hard to do
[15:40] <cjwatson> To some extent we've been waiting for real use cases before filling things out
[15:41] <voldyman> :) filing a bug now.
[15:41] <voldyman> you guys are awesome
[15:43] <voldyman> cjwatson: https://bugs.launchpad.net/launchpad/+bug/1538613
[15:49] <cjwatson> thanks
[15:50] <sergio-br2> hey cjwatson
 does launchpad just get the tarball from the master branch?
[15:51] <sergio-br2> I expected it had .git/ directory in the source, because the dolphin-emu build use some hash from there
[15:54] <cjwatson> no, it doesn't just get the tarball.  the problem you're hitting is that launchpad-buildd calls dpkg-buildpackage with -i -I, thereby stripping .git etc. (as is usual for source packages, they aren't normally expected to contain .git)
[15:54] <cjwatson> it's usually a mistake for a package's build process to rely on having the git tree there; if I were you I would find some way to patch around that
[15:55] <cjwatson> depends what it's trying to do with it
[15:58] <sergio-br2> it's not important, it's just some revision numbers
[15:59] <sergio-br2> there's no way to workaround the dpkg-buildpackage setting right?
[15:59] <cjwatson> No
[15:59] <cjwatson> If you write the recipe such that the relevant information is in the version number (if that's sensible), then you can use dpkg-parsechangelog in debian/rules to parse it out
[16:00] <cjwatson> That may not be appropriate, I don't know
[21:23] <ubuntiste-msakni> Hey! Anyone around?
[21:23] <cjwatson> ubuntiste-msakni: What's the problem?  (Usually best to just ask straight out.)
[21:25] <ubuntiste-msakni> cjwatson: I'm trying to use API to get all the informations in here https://launchpad.net/ubuntu/+mirror/ubuntu.mirror.tn-archive2 using https://api.launchpad.net/devel.html#distribution_mirror
[21:25] <ubuntiste-msakni> But I'm not able to do that.. :/ :(
[21:26]  * ubuntiste-msakni is a n00b who couldn't understand the API documentation :(
[21:26] <cjwatson> ubuntiste-msakni: It might not all be exported.  What in particular can't you get?
[21:26] <dobey> it doesn't seem to be all exported. sync status for series/arch doesn't seem to be in the api
[21:27] <dobey> (same question was asked the other day, and i poked at the docs a bit to see what was missing)
[21:27] <ubuntiste-msakni> First of all I couldn't find the way to get any information from that exact mirror.. It always return info about distros  like ubuntu, centos, kiwilinux, etc :/
[21:28] <ubuntiste-msakni> dobey: That was me who asked it..
[21:28] <cjwatson> the archive_mirrors attribute of a distribution has a collection of its mirrors
[21:28] <cjwatson> (or cdimage_mirrors, depending which you want)
[21:29] <cjwatson> and you can use distribution.getMirrorByName(name="whatever") to get a specific one
[21:29] <dobey> the URL for the distribution_mirror docs seems wrong too
[21:29] <cjwatson> http://paste.ubuntu.com/14682682/
[21:30] <cjwatson> it is, yes
[21:30] <cjwatson> probably needs a manual hack in the wadl-to-html stuff
[21:30] <cjwatson> bug please
[21:31] <cjwatson> and and if you need series/arch freshness status, I agree that isn't currently exported; file a bug with rationale for why you need it (we do need a reason to export things, because it can affect performance - would have to look at how expensive this in particular is to return)
[21:31] <ubuntiste-msakni> I'm not used to work with LP API, but don't you find that help.launchpad.net  need more detailled doc? :(
[21:32] <ubuntiste-msakni> cjwatson: Actually I was looking for those exact information :D
[21:32] <ubuntiste-msakni> cjwatson: dobey what I want to do is to get those informations and export them as graphs to monitor the status of that mirror..
[21:32] <cjwatson> I don't personally find that it needs more detailed documentation, but then that's because I already know the API well!  If *you're* confused by something in particular, then you'd need to explain it
[21:32] <cjwatson> Don't tell me here, write it in a bug report
[21:33] <cjwatson> Since I'm about to go
[21:33] <cjwatson> And IRC is pretty ephemeral
[21:34] <ubuntiste-msakni> cjwatson: I'm just having a chat :D :p I'll report a bug when I can really understand what's in the API and what's not, and can understand how to consume every thing already there.. For now I'm tottaly lost
[21:34] <cjwatson> Graphing is a decent rationale, just want to avoid ending up with that object timing out on the API because it's trying to export too much
[21:34] <cjwatson> ubuntiste-msakni: I definitely recommend playing about with lp-shell in the lptools package, especially if you also install ipython.
[21:35] <cjwatson> In combination with the overview docs on https://help.launchpad.net/API/launchpadlib you can do quite a bit of interactive exploration that way, which helps.
[21:35] <ubuntiste-msakni> I never heard of lp-shell.. I use that py lib, I'm installing lp-shell right now to play with it
[21:35] <cjwatson> lp-shell is a simple wrapper around launchpadlib, designed for interactive use
[21:35] <ubuntiste-msakni> Great :)
[21:35] <ubuntiste-msakni> I'm starting from there :)
[21:36] <cjwatson> And you want ipython for that since the standard Python REPL lacks completion and such
[21:36] <ubuntiste-msakni> thx cjwatson dobey.. Even if I can't find what I need, I should understand that API :/
[21:37] <dobey> the API is pretty simple to understand
[21:37] <dobey> as far as APIs go anyway
[21:38] <cjwatson> There's some Stockholm Syndrome here, I'm sure :)
[21:38] <dobey> heh
[21:39] <elacheche_anis> cjwatson: dobey I'm not a dev.. I'm not used to work with apis :) I'm a n00b x(
[21:39] <dobey> well, i'm sure if we developed it anew today, it'd probably be better, but i've certainly dealt with far worse things :)
[21:40] <elacheche_anis> btw
[21:41] <elacheche_anis> are you aware that the text in here → https://api.launchpad.net/ tell the users that there is a stable version fo the API ?
[21:41] <cjwatson> The actual layout is mostly not too bad.  The main problems with it are things like terrible batch behaviour and other such efficiency problems, and a few too many implementation details being brought to the surface (e.g. in collections).
[21:41] <elacheche_anis> As the v1.0 is (based on that link) not supported anymore x)
[21:41] <cjwatson> Yes, we know about the API versioning stuff.  It needs to be revisited, as the original scheme never worked out to be sensible.
[21:42] <elacheche_anis> :)
[21:42] <cjwatson> Most simple clients can just use devel unless you have some reason to ship them in a way that's hard to update (e.g. code that actually ships with Ubuntu).
[21:43] <cjwatson> If we were doing that again we'd probably version different bits of the API separately or something, but it's not clear that it's worth the effort for major rearrangements.
[21:44] <elacheche_anis> I see :)
[21:44] <elacheche_anis> I'm just trying to use the info in LP on my LoCo website :) So our contributors will use LP, right now they all ignore it
[21:45] <cjwatson> At some point we should indeed make the docs a bit clearer there though.
[21:45]  * cjwatson -> evening


[19:23] <solar_sea> Hi. I'd like to add to another fs option to the installer and regenerate a mini.iso image. Can any kind soul please link me to the respective docs ?
[19:25] <solar_sea> alternatively, if there is a way to set the partition's mount point externally during the installation, skipping the predefined fs list, that's mighty fine for me as well :)