[00:00] <directhex> mrooney, run "requestsync" from ubuntu-dev-tools
[00:01] <mrooney> directhex: okay, now if I am the ubuntu maintainer but don't have upload rights, is there anything special I should do?
[00:01] <directhex> anakron, the version number of a package in debian/changelog should be appropriate. if it's an ubuntu-specific package based on 1.0-1, it should be 1.0-1ubuntu1
[00:01] <directhex> mrooney, nope
[00:01] <mrooney> directhex: excellent, thanks!
[00:03] <anakron> ping directhex : and if i got "Patch 10_remove_encoding_from_desktop_file does not remove cleanly (refresh it or enforce with -f)
[00:03] <anakron> after applying patches
[00:03] <anakron> then i must remove them?
[00:04] <directhex> anakron, patches must be removable as well as addable
[00:07] <anakron> but, what i must do now
[00:08] <anakron> ?
[00:08] <directhex> anakron, check your patch - it might be slightly buggy
[00:08] <directhex> anakron, if in doubt, regenerate the patch. it can help
[00:08] <anakron> it's not mine
[00:08] <anakron> can you check it? its qtpfsgui
[00:09] <anakron> i want to add some changes
[00:09] <anakron> oops
[06:08] <dholbach> good morning
[06:08] <fabrice_sp_> Good morning dholbach !
[06:10] <dholbach> hiya fabrice_sp_ :)
[07:00] <stefanlsd> Morning!
[07:01] <dholbach> hiya stefanlsd
[07:07] <stefanlsd> hihi
[07:07] <ara> morning dholbach :)
[07:07] <stefanlsd> dholbach: Is there going to be an official gbj close meeting...
[07:07] <dholbach> stefanlsd: what would you expect to happen there?
[07:07] <stefanlsd> dholbach: just maybe people who attended or had concerns to  raise them. problems we encountered or things we thought worked well
[07:08] <dholbach> stefanlsd: I didn't plan anything of that sort yet - maybe we could ask for feedback on ubuntu-bugsquad@ and loco-contacts@?
[07:13] <didrocks> I have to microblog about the bugjam in Paris... Let's say this evening to have my photos :)
[07:14] <stefanlsd> didrocks: FR did great!
[07:14] <didrocks> stefanlsd: for a first officiel participation, yeah, little pride about it :)
[07:14] <didrocks> but most important: Paris wins over Toulouse :)
[07:14] <didrocks> take that huats :p
[07:16] <dholbach> didrocks: on a bug-per-inhabitants basis? :)
[07:17] <didrocks> dholbach: no, that's not good stats. I can assure you ;p
[07:17] <dholbach> :-)
[07:17] <didrocks> dholbach: how did you compute this stats? It's not the number of touched bugs?
[07:18] <dholbach> why isn't it?
[07:18] <didrocks> hum, I was just wondering, seeing yesterday that there was some bugs like Toulouse having 23 000+ points ;)
[07:19] <dholbach> that was a bug I fixed
[07:19] <didrocks> I am just impressed by the number of touched bug by us, Didn't realize it was so much
[07:20] <stefanlsd> didrocks: yeah, us neither
[07:20] <didrocks> dholbach: I am sure it's huats who asked you to do such a bug ;)
[07:21] <dholbach> didrocks: no, I broke it just myself :)
[07:21] <didrocks> stefanlsd: you too? apparently, it's hard to count/estimate number of touched bugs ;)
[07:21] <didrocks> dholbach: :)
[07:35] <stefanlsd> Did we have a blog for ubuntu dev stuff? Was it on fridge, or was that only developer news?
[07:36] <mok0> stefanlsd: we don't. It was proposed but never decided on
[07:37] <didrocks> stefanlsd: yes, there were an open thread about it
[07:38] <mok0> Someone mentioned we might use the fridge
[07:39] <stefanlsd> mm. yeah. i think it would be a nice feature to have
[07:39] <stefanlsd> i think often there's alot of stuff going on, and guys could help, just you dont have a good way of putting it out there, or asking
[07:40] <mok0> stefanlsd: yep
[07:40] <xakep> well there is one way
[07:40] <stefanlsd> and things like a common thing that biting everyone at the moment. maybe some big api change or something that would help a bunch of people hitting the same issue
[07:41] <xakep> how about a forum
[07:41] <mok0> stefanlsd: and important information like the python 2.6 upgrade
[07:41] <xakep> haha
[07:41] <xakep> python is pretty nice
[07:42] <xakep> why not use the 3.0.2 stable version
[07:42] <mok0> xakep: that's an understatement...
[07:42] <xakep> no thats not
[07:42] <directhex> xakep, pythono 3 is incompatible with 2.x by design
[07:42] <xakep> cause ScITE much better
[07:42] <stefanlsd> mok0: yeah. stuff like that.
[07:43] <mok0> oh, here comes my cat...
[07:43] <xakep> python 3 will eventully be compatable
[07:43] <stefanlsd> i dont mind hosting a drupal site with a blog with openid to LP for this. Who would be the right person to check with?
[07:43] <mok0> xakep: nonsense
[07:44] <xakep> well i counld open something like that
[07:44] <xakep> in a matter of minutes
[07:44] <xakep> what would it be called
[07:44] <xakep> good urls are hard to find these days
[07:45] <xakep> maybe wordpress would work
[07:45] <dholbach> didrocks, stefanlsd: I'm just checking the code - it might be that I counted some bits twice :-/
[07:45] <mok0> If it's meant to be for the -devs, you need the blessing of a MOTU meeting
[07:46] <dholbach> didrocks, stefanlsd: will let you know
[07:46] <didrocks> dholbach: don't cheat to make ubuntu-berlin the first one :)
[07:46]  * didrocks keep an eye on dholbach ;)
[07:46] <xakep> there is a beta verison of python that might work
[07:46] <dholbach> didrocks: let's continue in #ubuntu-bugs :)
[07:47] <xakep> that is strange code thou
[07:47] <xakep> beta versions seem to crash allot
[07:48] <xakep> I have been having allot of luck with Ruby
[07:49] <xakep> well im trying to repair damaged driver files
[07:50] <directhex> well that was odd
[08:19] <ara> Hey MOTUs! Today is an Ubuntu Testing Day!: https://wiki.ubuntu.com/Testing/UbuntuTestingDay/20090223
[08:20] <ara> help us testing the new features!
[08:25] <huats> morning
[09:14] <AnAnt> Hello, can someone review http://revu.ubuntuwire.com/details.py?package=webstrict ?
[09:16] <slytherin> anyone here with access to an ia64 machine.
[09:16] <directhex> no comment
[09:16] <directhex> why?
[09:19] <slytherin> directhex: mjpegtools fails to build on ia64 with error that libquicktime-dev is not installable because some particular version of libquicktime1 is not installable.
[09:20] <directhex> slytherin, can you phrase that in the form of a SLES10 question?
[09:21] <slytherin> directhex: I don't think so.
[09:23] <stefanlsd> Are blueprints meant to be discussed before proposed, or proposed and then discussed?
[09:29] <AnAnt> persia: ping
[09:29] <AnAnt> persia: I have fixed the issues you mentioned in webstrict
[09:29] <Koon> stefanlsd: I would say both
[09:31] <Koon> stefanlsd: some blueprints are well advanced when discussed at UDS... for some others its the UDS discussion that sparks the blueprint
[09:32] <stefanlsd> Koon: mm. ok. I was wondering about a opt in / out notification for new merges / syncs to the last uploader. Also some way of that uploader saying, i will do this / i dont have time and feel free to take it.
[09:34] <Koon> stefanlsd: interesting.
[09:35] <Koon> since the merge/sync window usually starts before UDS I guess that should be discussed well before
[09:37] <stefanlsd> I think it will make the merge/sync stuff alot smoother.  I often didnt realise that there was a new merge available, and the merges that were there ,I didnt really wanna 'steal' someone elses merge.. - mm. i could register a blueprint i guess. (i actually already have done the python code to check for updates and notify if new merges are available).
[10:20] <Laibsch> Is this the right place for motu-sru?
[10:23] <Hobbsee> Laibsch: on irc?  Yes.
[10:29] <StevenK> We
[10:35] <devfil2> Laibsch: what do you need?
[10:36] <Laibsch> I'd really like bug 221010 to be pushed
[10:36] <Laibsch> outstanding for dapper and gutsy
[10:37] <devfil2> Laibsch: ah, I forgot to ack it
[10:38] <Laibsch> Here's your reminder ;-)
[10:38] <devfil2> Laibsch: the problem is only the icon?
[10:39] <Laibsch> icon and url
[10:39] <Laibsch> the debdiff should be taking care of both
[10:39] <Laibsch> url icon and the url where the image links too have both changed
[10:39] <Laibsch> s/too/to
[10:39] <Laibsch>  /
[10:39] <devfil2> Laibsch: why is it so important?
[10:40] <Laibsch> Did I say it is important?
[10:41] <Laibsch> it is a question of user experience, though
[10:41] <Laibsch> And now that I've gone to the trouble of preparing the patch, I guess I want to see it released
[10:42] <DktrKranz> Laibsch: gutsy will reach EOL very soon, so I guess it won't be processed in time (speaking with former motu-sru hat)
[10:42] <Laibsch> too bad
[10:42] <Laibsch> it lingered for a while
[10:43] <Laibsch> all the more reason to release dapper quickly ;-)
[10:43] <devfil2> Laibsch: uhm it's ok
[10:43] <Laibsch> That being said, I still see feisty around
[10:44] <DktrKranz> Laibsch: huh? Feisty is EOL since october
[10:44] <Laibsch> officially
[10:44] <Laibsch> oops, you're right
[10:44] <Laibsch> But it wasn't taken off pages like http://packages.ubuntu.com/search?keywords=aptitude immediately
[10:45] <devfil2> DktrKranz: can you upload the debdiffs?
[10:45] <DktrKranz> devfil2: no gpg key handy right now
[10:46] <DktrKranz> Laibsch: probably it's still displayed, but I'm not sure we can actually push packages to a "obsolete" distro with success
[10:46] <DktrKranz> soyuz could reject them
[10:48] <Laibsch> I'm not suggesting to push packages to already eol'd releases
[10:49] <Laibsch> I was merely trying to point out that although eol is looming, releases sometimes have a bit more room to breath even after official eol
[10:49] <Laibsch> DktrKranz: can I ping you when you are around your GPG key or would it be better to ask somebody else?
[10:54] <devfil2> Laibsch: I'm uploading your debdiffs
[10:56] <Kamping_Kaiser> i know this is slightly OT here, but how long can i expect a build of Linux to take in a Launchpad PPA?
[10:56] <Kamping_Kaiser> i'm at 3 hours, I'm wondering if it'll be another hour, or another 15 :)
[10:56] <slytherin> Kamping_Kaiser: check how much time it takes for the official builds.
[10:56] <geser> linux == kernel?
[10:56] <Kamping_Kaiser> geser, yes.
[10:56] <Kamping_Kaiser> slytherin, where can i look for that info?
[10:57] <slytherin> Kamping_Kaiser: https://edge.launchpad.net/ubuntu/jaunty/+source/linux/+builds
[10:58] <Kamping_Kaiser> slytherin, thanks
[10:59] <devfil2> Laibsch: I'm changing your debdiffs to use the patch system
[11:02] <Kamping_Kaiser> interesting. I cant view https://edge.launchpad.net/ubuntu/hardy/+source/linux/+builds
[11:02] <Kamping_Kaiser> jaunty kernel will have to do.
[11:03] <geser> Kamping_Kaiser: I don't know if the package was already named linux in hardy
[11:03] <Kamping_Kaiser> geser, aaah. I'll go and look. thanks for that pointer
[11:07] <Kamping_Kaiser> I can view the builds via https://edge.launchpad.net/ubuntu/hardy/+source/linux/2.6.24-24.50 , but +source/linux/+builds i cant view. would this be worth asking about #launchpad ?
[11:11] <geser> Kamping_Kaiser: just checked myself, I see "not allowed here" too, will ask in #launchpad
[11:12] <Hobbsee> i get a 404 there
[11:12] <Hobbsee> https://edge.launchpad.net/ubuntu/+source/linux/+builds
[11:12] <Kamping_Kaiser> Hobbsee, https://edge.launchpad.net/ubuntu/hardy/+source/linux/+builds
[11:12] <Hobbsee> oh, right
[11:13] <Hobbsee> forbidden, even here.  strange.
[11:13] <Kamping_Kaiser> hiya, btw.
[11:13] <Hobbsee> no one shall have access to that page!
[11:13] <Hobbsee> greetings!
[11:13] <Kamping_Kaiser> hehe.
[11:13] <Kamping_Kaiser> gday.
[11:21] <slytherin> can anyone provide any insight in this build failure - http://launchpadlibrarian.net/22998337/buildlog_ubuntu-jaunty-ia64.mjpegtools_1%3A1.9.0-0.0_FAILEDTOBUILD.txt.gz
[11:21] <slytherin> I checked the archive (ports.ubuntu.com) and both libquicktime-dev and libquicktime1 are present on ia64.
[11:26] <wgrant> slytherin: It could mean a conflict of some sort.
[11:27] <Laibsch> I'm working on bug 139661 and have prepared patch http://oss.leggewie.org/wip/LP139661.diff
[11:27] <wgrant> libquicktime1 could well not be installable on ia64.
[11:27] <Laibsch> I'm not terribly familiar with translation.  Do I even need to patch all those .po files?
[11:27] <slytherin> wgrant: I am not able figure out the problem from log.
[11:27] <Laibsch> or just ui.cc and possibly the .pot file?
[11:28] <wgrant> slytherin: It's not too useful for debugging things at that stage of the build. You need to try to resolve the deps yourself, I suspect, and see what's broken.
[11:28] <wgrant> (ideally in an ia64 chroot)
[11:29] <slytherin> wgrant: I don't have access to ia64 chroot. :-(
[11:33] <directhex> slytherin, debootstrapping, just for you
[11:33] <slytherin> directhex: thanks. :-)
[11:33] <slytherin> And I now have a hunch where the problem could be.
[11:34] <directhex> NOW you tell me, after messing about with debootstrap rpms...
[11:35] <geser> directhex: can you install libquicktime-dev?
[11:37] <slytherin> directhex: I believe libquicktime needs a rebuild. Because I can see libavcodec51 as runtime dependency in libquicktime1 package for ia64. But libavcodec51 is not a package anymore in jaunty.
[11:38] <directhex> The following packages have unmet dependencies:
[11:38] <directhex>   libquicktime1: Depends: libavcodec51 (>= 3:0.svn20080206-8) which is a virtual package. or
[11:38] <directhex>                           libavcodec-unstripped-51 (>= 3:0.svn20080206-8) which is a virtual package.
[11:38] <slytherin> directhex: right, so libquicktime needs a rebuild.
[11:39] <directhex> that what you were after?
[11:39] <slytherin> No. I wasn't sure before.
[11:40] <slytherin> I will do the rebuild today.
[11:40] <directhex> can i delete this chroot? it's a production box...
[11:40] <slytherin> or if any motu free enough to upload a build1 source package for libquicktime, that will be great. :-)
[11:40] <slytherin> directhex: sure, thanks for your help.
[11:41] <DktrKranz> Laibsch: if you're online around 20 UTC, sure
[11:41] <directhex> i wish i knew why the test box wasn't booting
[11:42] <devfil2> DktrKranz: I've already uploaded Laibsch packages
[11:43] <Laibsch> DktrKranz: most likely not, I'm in Japan
[11:43] <Laibsch> devfil2: oh, thanks!
[11:43] <Laibsch> great
[11:43] <devfil2> slytherin: a rebuild of libquicktime?
[11:44] <slytherin> devfil2: yes
[11:44] <slytherin> devfil2: to pickup correct dependencies (libavcodec).
[11:45] <ScottK> devfil2: Your koffice upload FTBFS.
[11:45] <ScottK> You going to fix it?
[11:46] <devfil2> ScottK: it FTBFS on i386 due to sh script if I remember right, feel free to check it
[11:46] <DktrKranz> Laibsch: oh... pretty incompatible, then. But they're already in unapproved
[11:47] <ScottK> devfil2: Your upload FTBFS.  I don't find telling me to check a very responsible attitude.
[11:47] <devfil2> ScootK: ok, I can look at it
[11:48] <Laibsch> is this the mailgraph package?
[12:02] <james_w> anyone have any items they think would be good for the Developer News?
[12:03] <directhex> mono 2.0 app transition done? ;)
[12:03] <DktrKranz> directhex: can you read my brain? :)
[12:03] <directhex> yes
[12:04] <directhex> ew, you disgusting child, is that even legal? :o
[12:04] <DktrKranz> it's legal given that you don't disclosure my password to launch nuclear missles
[12:14] <savvas> This is weird - I'm listed as subscribed in most of the packages I submitted in revu-ubuntuwire, but I don't receive the comment updates
[12:18] <james_w> directhex: yeah, that will be on there
[12:18] <james_w> savvas: I think you have to enable email notifications
[12:18] <devfil2> ScottK: koffice ftbfs due to kdelibs changes
[12:22] <savvas> james_w: I have that checked! I think I have to subscribe to each package I upload, or was that supposed to be done automatically?
[12:23] <savvas> e.g. http://revu.ubuntuwire.com/u/medigeek shows I'm subscribed to "Own packages, fatrat, fspy", whereas I am listed in the subscribers at http://revu.ubuntuwire.com/p/lxsplit
[12:26] <RainCT> savvas: have you checked your mail address?
[12:27] <RainCT> (hint: preferences page)
[12:28] <savvas> RainCT: yes, I've just unchecked and checked it again - but why am I listed in subscribers at the package page http://revu.ubuntuwire.com/p/lxsplit and not shown in my user page?
[12:30] <savvas> RainCT: also at the lxsplit page I have a "Subscribe" link on the top menu, not "Unsubscribe"
[12:31] <RainCT> savvas: because it's your package
[12:31] <RainCT> savvas: so in the profile it's displayed as "Own packages"
[12:32] <RainCT> savvas: the link says "Subscribe" because you can still subscribe to that package and then you'd remain subscribed if later you uncheck the "get notifications for all my packages"
[12:34] <RainCT> (btw, if REVU stops working access it from revu.ubuntuwire.org.. just heard in #ubuntuwire that the .com has expired)
[12:34] <savvas> ok at my preferences page I have checked "Yes, I want to receive email notifications about everything related to my uploads."
[12:34] <savvas> lxsplit package page says I'm a subscriber: http://revu.ubuntuwire.com/p/lxsplit (at the bottom of the page)
[12:35] <savvas> I've just sent a test comment
[12:36] <savvas> oh
[12:36] <savvas> wait, .org ?:P
[12:36] <RainCT> savvas: did you get email before?
[12:36] <RainCT> *did you get email notifications before, ie. is it just failing today?
[12:37] <savvas> I used to get them some time ago
[12:37] <RainCT> perhaps it's because of the domain then
[12:37] <savvas> I think it was fspy
[12:40] <savvas> RainCT: this is the last email I got (or I know I got) from revu: http://paste.ubuntu.com/121804/
[12:42] <savvas> oh anyway, perhaps there was a database update
[12:42] <savvas> let me click on Subscribe, and see if it works then
[12:43] <RainCT> uhm I'm not getting mail either
[12:43] <RainCT> either it's the domain or I broke something :P
[12:44] <savvas> do you see a "Subscribe" on top or "Unsubscribe"?
[12:45] <RainCT> unsub
[12:47] <savvas> hm.. same here now
[12:48] <RainCT> ok, it's the domain
[12:48] <savvas> http://revu.ubuntuwire.org/p/lxsplit - didn't receive neither of the last 3 test comments :(
[13:02] <AnAnt_> Hello, I'm making a package for some CAD tool, the upstream makes a lot of shared libs, and I get this lintian warning: herb: package-name-doesnt-match-sonames libAbe0 libAbl0 libAbt0 libAbv0 libAut0 libBdd0 libBeh0 libBhl0 libBtr0 libBvl0 libCst0 libCtl0 libCtp0 libElp0 ...
[13:03] <AnAnt_> is that alright to override ?
[13:05] <JontheEchidna> yeah... I wouldn't expect you'd need binary packages for each of those
[13:05] <JontheEchidna> that'd be crazy
[13:07] <AnAnt_> ok, thanks
[13:07] <AnAnt_> I still need to make shlibs & symbols control files ?
[13:16] <RainCT> savvas: you didn't get any email, did you?
[13:22] <savvas> RainCT: nope
[13:30] <AnAnt_> do I still need to make shlibs & symbols control files ?
[13:58] <sistpoty|work> hi folks
[14:01] <DktrKranz> hi sistpoty|work
[14:02] <sistpoty|work> hi DktrKranz
[15:07] <bddebian> Heya gang
[15:07] <geser> Hi bddebian
[15:08] <bddebian> Hi geser
[15:10] <sistpoty|work> hi bddebian
[15:11] <bddebian> Heya sistpoty|work
[15:23] <slytherin> directhex: openjdk on armel is surely taking ages. :-)
[15:23] <directhex> slytherin, it's STILL there? o_o
[15:23] <directhex> slytherin, no matter, moonlight is built for armel now ;)
[15:23] <slytherin> directhex: yes, it has been five days now
[17:24] <mok0> OT: Anyone here familiar with R
[17:35]  * sistpoty|work calls it a day... cya
[17:38] <ScottK> mok0: There's a guy on planet.debian.org who blogs about it a lot.  Dirk something.  Also maintains the R packages in Debian.  Seems very knowlegable about it.
[17:39] <mok0> ScottK, thanks a lot, I guess I can find his name then. I solved my problem, though :-)
[17:41] <ScottK> mok0: If you care about R, there are a fair number of R packages that are FTBFS in Jaunty.  Mostly just need a retry I think.  I looked into it a bit, but then it exceeded my caring factor to get it all done.
[17:41] <mok0> ScottK, you are talking about r-cran-* packages?
[17:41] <ScottK> Yes.
[17:42] <ScottK> And some others too.
[17:42] <mok0> ScottK, I will take a look at those
[17:42] <ScottK> I just started looking through the r-base rdpends.
[17:42] <savvas> I made some transitional packages for boost (1.34) to boost1.35 - bug 332120 - I don't know if it was required, but it was a good practise :P
[17:43] <ScottK> savvas: I uploaded your boost1.35 FTBFS fix the other day.  Thanks.  I also used it as a model to fix boost and boost1.37.
[17:43] <mok0> ScottK: R's coolness never cease to amaze me :-)
[17:43]  * ScottK doesn't know much about it.
[17:44] <savvas> ScottK: sure, no problem :) by the way, I think boost 1.34 needs an update for it as well - unless ubuntu jaunty is going to be without boost 1.34
[17:44] <ScottK> boost == boost1.34.
[17:44] <savvas> ah it's renamed now?
[17:45] <ScottK> We are actually only about 3 packages away from being able to remove boost entirely.
[17:45] <savvas> let me guess.. deluge?
[17:46] <ScottK> No luabind, cgal, and btk-core unless I missed some.
[17:47] <ScottK> mok0: Are you still interested in btk-core?
[17:47] <savvas> any takers? I have an hour or so to play around :)
[17:47] <mok0> ScottK, I have to check again, but I'm afraid it's been abandoned upstream
[17:47] <ScottK> mok0: Would you mind taking a look at Bug 331896?
[17:47] <savvas> I mean, any non-taken :P
[17:47] <mok0> ScottK, of course
[17:48] <ScottK> mok0: I think we should either fix it or remove it then.
[17:48] <mok0> ScottK, yes
[17:48] <savvas> btw, a guy has ported glife to gtk+ 2 - bug 205218
[17:49] <mok0> ScottK, can you fill me in on the boost1.35 transition?
[17:49] <ScottK> savvas: I think rather than add more transitional packages, I think it'd be better to work on fixing luabind or cgal.
[17:49] <savvas> ScottK: will try :)
[17:49] <ScottK> mok0: Main transitioned from boost (1.34) to boost1.35 and so I was hoping we could push the older version out of the archive.
[17:50] <mok0> ScottK, you are looking at versioned rdepends?
[17:50] <ScottK> We currently have boost, boost1.35, and boost1.37.
[17:50] <ScottK> mok0: It's different package names.
[17:50] <mok0> Ah
[17:51] <ScottK> And then boost1.38 hit Sid too late for Jaunty, but it'll get added the next time around.
[17:51] <ScottK> So we need to work on getting rid of the old one....
[17:51] <mok0> ScottK, I will see what I can find out about upstream of btk-core... I've emailed them a couple of times on their sf.net email accounts
[17:51] <ScottK> mok0: Thanks.
[17:52] <mok0> NP
[18:01] <savvas> "  * Update Standards-Version to 3.8.0 (explain in debian/copyright why package
[18:01] <savvas>     is in non-free)."
[18:01] <savvas> yet in debian/control: Standards-Version: 3.7.3
[18:02] <savvas> oh sorry, cgal package :P
[18:05] <savvas> I guess the debian maintainer forgot to bump it, cgal 3.4-2 is 3.8.0
[18:06] <ScottK> savvas: Don't change it.
[18:06] <ScottK> Updating standards version from Debian is a pointless change that Ubuntu policy says not to do.
[18:06] <savvas> alrighty, thanks for the tip :)
[18:07]  * savvas notes
[18:09] <savvas> ScottK: Should I change the maintainer, since it's the first ubuntu change? If so, should I note in changelog that I changed the maintainer or is that unnecessary?
[18:09] <ScottK> Change it, but don't mention it.
[18:09] <savvas> ok
[19:20] <savvas> lpia is an official arch?
[19:20] <directhex> yes
[19:21] <savvas> E: Package libatlas-base-dev has no installation candidate
[19:31] <hyperair> hmm it would seem that some people managed to get exa working properly with i915 with driconf
[19:40] <Laney> I think something is up with udev on my Jaunty upgrade
[19:40] <Laney> the last thing before it hangs at boot is renaming wlan0 to wlan1
[19:40] <geser> bug 332270 perhaps?
[19:41] <jdong_> popular bug of the day :)
[19:41] <jdong_> I'm on a livecd sorting out that one on my macbook
[19:44] <Laney> aha
[19:45]  * Laney tries disabling watch then
[19:56] <Laney> yay
[19:56] <Laney> of course, x is broken, but still
[20:55] <RainCT> jdstrand: hey
[20:55] <jdstrand> hi
[20:56] <savvas> darn, can't get past this: http://launchpadlibrarian.net/23016291/buildlog_ubuntu-jaunty-amd64.luabind_0.7.dfsg-5ubuntu1~ppajaunty1_FAILEDTOBUILD.txt.gz
[20:56] <RainCT> jdstrand: just to be sure, about bug #292923, is backporting the version from Jaunty the Right Thing?
[20:57]  * RainCT is mentoring Vincenzo
[20:57] <jdstrand> RainCT: heh, I *just* clicked 'Save Changes' in LP on that bug :)
[20:58] <RainCT> heh
[20:58] <jdstrand> RainCT: he needs to patch the version that is in intrepid
[20:58] <jdstrand> (and hardy if he is interested)
[20:59] <RainCT> jdstrand: OK. The version in Hardy is the same as in Intrepid, the only change being a Standards-Version bump and the addition of a watch file. It still needs a different patch, though?
[21:01] <jdstrand> RainCT: the upstream version is the same, but the Ubuntu/Debian version is not
[21:01] <RainCT> Right
[21:01] <jdstrand> RainCT: eg, intrepid is 1.2.3-2, and hardy is 1.2.3-1
[21:02] <jdstrand> RainCT: so intrepid becomes: 1.2.3-2ubuntu0.1 and hardy become 1.2.3-1ubuntu0.1
[21:02] <jdstrand> (this is also in SecurityUpdateProcedures)
[21:05] <RainCT> jdstrand: Yeh. Just asking because I find stuff like this rather pointless (the packaging changes done between both revisions are absolutely *not* going to cause any impact, and having the same version in both will make successive maintainance easier), but after all doing it twice isn't that difficult (and in this case perhaps even good as he'll get more practice by doing it twice)
[21:06] <RainCT> jdstrand: Anyway, thanks :)
[21:06] <savvas> ScottK: Here's cgal debdiff for boost1.35: http://paste.ubuntu.com/122044/ - however there is an lpia dependency problem: https://launchpad.net/~medigeek/+archive/ppa/+build/880368 (amd64 and i386 were built fine in my PPA)
[21:07] <ScottK> RainCT: The build system won't let you upload the same revision twice.
[21:07] <ScottK> savvas: Thanks.  Looking
[21:07] <jdstrand> RainCT: in this case, the change may be minimal, but very often there are more significant changes
[21:08] <jdstrand> RainCT: tbh, it is easier to create the extra patch than to review all the changes between versions and decide if they could cause a regression
[21:08] <RainCT> ScottK: changing the version number is still easier than doing a new debdiff (and optimally there should be an option to copy the package from one distro to the other).. but anyway, ignore my rands, I'll actually get used to it ;)
[21:09] <savvas> ScottK: And about luabind - I got stuck at a problem while compiling, I'm not that code-literate to fully understand it: https://launchpad.net/~medigeek/+archive/ppa/+build/880369 :)
[21:09] <jdstrand> RainCT: and it doesn't save you anything in terms of testing, because all need to be tested on each Ubuntu release that will get the patch
[21:10] <anakron> HI RainCT
[21:10] <anakron> HI all
[21:12] <RainCT> jdstrand: good point (the review time), but I still think SRU and Security updates are overly bureaucratic (surely for packages in main with lots of rdepends it makes sense, but not that much in the case of standalone universe apps where the risk is minimal..)
[21:13] <ScottK> savvas: The missing package failed to build on lpia (and armel), so not your problem at all.
[21:14] <jdstrand> RainCT: well, perhaps. But IMO I'd rather err on the side of caution than to risk a regression. Regressions are no fun
[21:14] <RainCT> but I guess I'll get over it once I get used to them.. right now I'm still in the initial fase of trying to make sense of the system :P
[21:14] <RainCT> hi anakron
[21:14] <anakron> can you look this? https://bugs.launchpad.net/ubuntu/+source/qcad/+bug/311476
[21:15] <jdstrand> RainCT: this is an exceedingly longstanding 'bureaucratic' measure to minimize risk (it started with Debian a *long* time ago)
[21:15] <anakron> I'll test it and now i'll send it to debian maintainer too
[21:16] <savvas> ScottK: oh, great! 1 out of 2 isn't bad :P
[21:17] <RainCT> anakron: Looks good! (though the changelog entry isn't really clear.. adding a "debian/qcad.desktop:" in front of it would make it more understandable)
[21:17] <RainCT> anakron: please wait a few days to see if Debian reacts and we can request a sync before subscribing u-u-s
[21:18] <anakron> im looking for desktop bugs...but it's too difficult to find them with LP
[21:19] <anakron> you can't got an exact search from lp
[21:19] <savvas> qcad has a weird versioning
[21:19] <anakron> XD
[21:20] <savvas> I thought I was seeing double because I'm tired heh
[21:20] <RainCT> lol
[21:24] <savvas> Does anyone see anything weird in this debian/rules? http://paste.ubuntu.com/122054/
[21:25] <savvas> let me check if it builds ok with boost 1.34
[21:28] <anakron> why are you looking for something weird
[21:28] <savvas> anakron: http://launchpadlibrarian.net/23016291/buildlog_ubuntu-jaunty-amd64.luabind_0.7.dfsg-5ubuntu1~ppajaunty1_FAILEDTOBUILD.txt.gz
[21:29] <savvas> it fails to build and I'm playing around with patches and boost include directories :P
[21:30] <anakron> thats weird
[21:30] <anakron> xD
[21:31] <anakron> RainCT, im doing a "nice" debdiff file
[21:31] <anakron> and then ill sent it to debian maintainer
[21:32] <savvas> RainCT: the emails are back :P
[21:32] <savvas> ah no wait sorry
[21:33] <savvas> it was from google code
[21:48] <anakron> someone here knowns something about emma? im wanna know how is her icon
[21:49] <anakron> i found one and it's mysql dolphin with "emma" writed
[21:51] <savvas> anakron: /msg memoserv send emma yadda yadda yadda :p
[21:51] <anakron> ?¿
[21:52] <savvas> oh, I thought you mean emma/em, with nickname emma
[21:52] <savvas> sorry :)
[21:57] <anakron> :)
[21:57] <anakron> its a project
[22:17] <andersk> Can someone sync open-vm-tools 2008.11.18-130226-1lenny1 into Jaunty (bug 289921)?
[22:24] <james_w> thanks nhandler
[22:25] <nhandler> james_w: For what? The News page update?
[22:25] <james_w> yeah
[22:25] <nhandler> james_w: No problem. It is a great resource. I just keep forgetting to update it.
[22:27] <james_w> the problem is there has been LOADS happening in the last month :-0
[22:28] <nhandler> james_w: Do you want to mention the stuff going on regarding the MC? Or do you want to wait until after the election?
[22:28] <james_w> hum
[22:29] <james_w> I didn't find any announcements about that, except the long-expired call for nominations, did I miss something?
[22:29] <nhandler> Daniel's membership expired
[22:29] <nhandler> So currently, we only have 4 people on the MC
[22:30] <ScottK> The did do the first new style MOTU application.
[22:30] <ScottK> The/They
[22:30] <nhandler> scottk: That is already included
[22:30] <ScottK> K
[22:33] <james_w> nhandler: I'm not sure that's really appropriate
[22:33] <POX> is Gabriel Ruiz here?
[22:35] <POX> anyway, please remember to check the newest Debian package before you'll duplicate the work ;P
[22:36] <POX> haha
[22:36] <anakron> hi
[22:36] <POX> andersk: did you see emma 0.6-3 ? :-P
[22:36] <anakron> someone can review it?
[22:36] <anakron> https://bugs.launchpad.net/ubuntu/+source/firestarter/+bug/301603
[22:36] <anakron> look it
[22:36] <anakron> https://bugs.launchpad.net/ubuntu/+source/emma/+bug/333049
[22:37] <POX> andersk: sorry, wrong nick
[22:37] <POX> anakron: ^^
[22:37] <anakron> jaja
[22:38] <anakron> i was doing a patch for emma
[22:38] <anakron> yes
[22:38] <POX> please check -3 then
[22:38] <anakron> why?
[22:38] <anakron> :O
[22:38] <anakron> :)
[22:39] <anakron> hi Piotr
[22:39] <POX> hi :)
[22:39] <anakron> it was a patch for 0.6-3
[22:39] <anakron> but i sent it like 0.6-2
[22:39] <anakron> i was doing a patch for emma source package for jaunty
[22:40] <POX> but the .xpm file is already there
[22:40] <anakron> :O
[22:40] <anakron> ops
[22:40] <POX> or do you want to change it?
[22:40] <anakron> so...
[22:40] <anakron> no
[22:40] <anakron> so
[22:40] <anakron> forget it
[22:41] <anakron> or there is an icon, but it doesn't get loaded?
[22:41] <POX> ok, just remember to check Debian or you'll waste some time ;P
[22:41] <goshawk> hi, am i the only one that couldn't reach REVU?
[22:41] <anakron> :) ok
[22:41] <POX> Ubuntu has -2, so you probably want to sync it
[22:41] <anakron> mm
[22:41] <anakron> i'll fill it
[22:41] <nhandler> goshawk: revu.ubuntuwire.org
[22:42] <nhandler> goshawk: ubuntuwire.com is down right now
[22:42] <goshawk> nhandler: wasn't it .com?
[22:42] <goshawk> ah yes :)
[22:42] <goshawk> thx
[22:42] <nhandler> It was .com until the domain name expired ;)
[22:46] <goshawk> i'm packaging an application which is licensed as gpl v2, but there are some parts in other licenses (artistic and MIT/X11), should i write all the licenses in the debian/copyright file?
[22:46] <directhex> yes
[22:46] <goshawk> the package is dsss and it's in REVU
[22:46] <goshawk> oki so it will be a long copyright file :)
[22:47] <nhandler> goshawk: Just so you are aware, we are now in Feature Freeze, so we are focusing on making Ubuntu more stable. Your package most likely will not make it into Jaunty
[22:48] <goshawk> nhandler: yes i know
[22:55] <superm1> nhandler, its a popular item to use with mythgame, so there is a vested interest
[22:55] <goshawk> dput ppa seems not working due to ubuntuwire.com down, can i switch to ubuntuwire.org?
[22:56] <goshawk> s/dput ppa/dput revu
[22:56] <jpds> goshawk: revu.ubuntuwire.com not working?
[22:56] <james_w> the domain expired
[22:56] <goshawk> yep : [23:42] <nhandler> goshawk: ubuntuwire.com is down right now
[22:57] <jpds> james_w: Gah!
[22:57] <james_w> goshawk: and yes, you can switch to .com
[22:57] <james_w> .org I mean
[22:57] <goshawk> .org you mean :)
[22:57] <goshawk> ok
[22:57] <goshawk> and i like .org more :P
[22:57] <james_w> yeah, I need more beer or less, it's not yet clear
[22:57]  * jpds really think we should get it registered with the -eu.org guys.
[22:59] <nhandler> superm1: But is it a mythbuntu package that would fall under your delegation for a FFe?
[22:59] <superm1> nhandler, no it wouldn't.  that's why i didnt comment on it
[22:59] <superm1> nhandler, we have an interest in it, but in the end it's a regular ole' universe package
[23:00] <superm1> so i certainly dont want to overstep my bounds with it
[23:00] <nhandler> superm1: Ok, then I'll take a look. I just wanted to make sure I wasn't stepping on your toes here
[23:00] <jpds> goshawk: Point dput at revu.tauware.de
[23:00] <superm1> nhandler, i seem to think it makes sense to at least bring in that patch if we dont jump versions personally
[23:01] <superm1> and maybe that's better until upstream does a "formal" release including the patch
[23:03] <nhandler> superm1: By any chance is the package in a PPA?
[23:03] <superm1> nhandler, i seem to doubt joel put it in one, but you can check his ppa i guess
[23:04] <nhandler> superm1: Ok, it isn't a huge deal. It just would save me a few minutes
[23:05] <superm1> right
[23:05] <superm1> nhandler, the versioning in his packaging might need to be looked at anyway. i didn't give it that much of a look, figured it's more important to see it's right on principle before looking much into it
[23:07] <goshawk> jpds: why?
[23:08] <jpds> goshawk: Nevermind, I thought that domain had been pointed there.
[23:58] <salty-horse> hi. why does flashplugin-nonfree still uses nspluginwrapper on amd64 instead of the native 64-bit beta?


[00:41] <xnox> infinity, could we pretend libreoffice on s390x never happend on s390x, by deleting s390x binaries from xenial-release? there is new libreoffice built in s390x but need more deps build before it can migrate.
[00:41] <xnox> infinity, cause otherwise i'll need to binNMU a bunch of kde* stuff, which i'd rather just naturally build in release pocket.
[00:42] <xnox> infinity, as in, would it be terrible if libreoffice/s390x binaries would be deleted from xenial-release?
[00:44] <xnox> infinity, or like just drop libreoffice-kde from s390x on xenial-release =)
[00:48] <infinity> xnox: What problem are you trying to solve?
[00:49] <xnox> infinity, trying to migrate qt+apt+poppler
[00:49] <infinity> xnox: Which also involves migrating libreoffice?
[00:49] <infinity> xnox: If so, deleting it from release solves nothing.
[00:49] <xnox> yes. which is migratable on all but arches, apart from s390x.
[00:50] <xnox> cause libreoffice built in -release thanks to bootstrap archive skew =)
[00:50] <xnox> oh, is libreoffice at all installable in s390x release i wonder.
[00:50] <infinity> xnox: It's uninstallable in both, I'm sure, but deleting it from release doesn't fix the one in proposed.
[00:51] <infinity> xnox: britney's complaining about the one in proposed.
[00:51] <xnox> sigh.
[00:52] <xnox> and it will not migrate an uninstallable package because... ?!
[00:52] <xnox> it's not a regression.
[00:52] <infinity> Because that's the whole point of proposed-migration.
[00:52] <infinity> Literally.
[00:52] <xnox> and we didn't mark s390x as a f##ked arch
[00:52] <infinity> And we won't.
[00:53] <infinity> Because then you need to go clean up the substantial mess after.
[00:53] <infinity> Which is worse than just fixing things.
[00:53] <infinity> It's not world-ending to take a couple of days to sort it all out.
[01:32] <xnox> infinity, imho undoing things in -release would be easier, cause the whole lot is in dep-wait in release on s390x at the moment. and now i'm rebuilding on all arches, rather than just s390x.
[01:32] <xnox> infinity, thus maybe libreoffice/s390x should be removed on both -proposed and -release pockets.
[01:34] <xnox> however s390x is pretty crap at the moment
[01:34] <xnox> I: [Thu Dec 10 01:21:30 2015] - > Found 781 non-installable packages
[01:34] <xnox> which is a lot, compared with ~22-38 on all other arches
[01:38] <xnox> Laney, looks like we need all of kde built on s390x...
[01:55] <infinity> xnox: Hrm?  What needs rebuilding and why?
[01:55] <xnox> infinity, all of k* packages, cause they only have a dep-wait build records in xenial-release on s390x, rather than -proposed.
[01:55] <xnox> (those that generate libkf5*-dev packages more or less)
[01:55] <infinity> xnox: We can work around that with the bootstrap archive.
[01:56] <xnox> infinity, can you copy existing qt* packages from s390x into bootstrap archive from xenial-release please?
[01:57] <xnox> infinity, can you copy existing qt* packages from s390x into bootstrap archive from xenial-proposed please?
[01:57] <xnox> and then re-trigger builds of all failed & dep-wait packages on s390x
[01:59]  * xnox ponders why release pocket shouldn't have been building with -proposed enabled on s390x, whilst we had bootstrap archive on as well.
[02:00] <infinity> xnox: I might need a better description than "qt*"
[02:01] <xnox> infinity, qt*-opensource-src
[02:02] <infinity> xnox: That didn't help. :P
[02:04] <xnox> infinity, http://paste.ubuntu.com/13877682/
[02:06] <xnox> infinity, that's list of source package, one needs to map that to binaries and take the lot for s390x.
[02:06] <xnox> into bootstrap, and mass-rebuild.
[02:06] <infinity> There are no qt3d binaries.
[02:06] <infinity> And that source is also royally messed up in LP.  Fun.
[02:07] <infinity> wgrant: https://launchpad.net/ubuntu/+source/qt3d-opensource-src/5.5.1-4ubuntu2 <-- lolwut.
[02:07] <xnox> yeah, cause it waits on a dep-wait package, which waits on qtbase-dev in release...
[02:07] <xnox> qt3d is leaf, so skip that one.
[02:08] <xnox> some of them are arch all anyway.
[02:08] <xnox> infinity, yeah, i was not sure what was going on with the builds listings for it....
[02:10] <xnox> infinity, there are a couple arch:all only packages, so take them too.
[02:11] <xnox> does that at all sound like a reasonablish thing to do? cause then by magic binaries in -release will start to appear with the right & installable deps, and then libreoffice will migrate eventually.
[02:11] <infinity> It'll vaguely work.
[02:11] <infinity> Though, going back and getting all the arch:all packages will be annoying. :P
[02:12] <xnox> at least we will avoid rebuilding the qt/kf5* on arm64 & armhf, and running autopackage tests for all qt/kf5* on those platforms which takes eternity, compared with s390x build speed.
[02:21] <wgrant> infinity: Probably a double-accept.
[02:22] <wgrant> https://bugs.launchpad.net/launchpad/+bug/682692 ish
[02:23] <wgrant> infinity, xnox: Are those duplicated builds actually causing any problems? The successful ones look fine to me.
[02:23] <infinity> wgrant: No, probably not.
[02:24] <infinity> wgrant: Though, I'm curious what'll happen if/when those dep-waits clear.
[02:24] <wgrant> infinity: They'll fail to upload.
[02:24] <wgrant> Duplicated binaries and such
[02:27] <wgrant> xnox: Is the qt stack unlikely to migrate to release soon?
[06:18] <Mirv> xnox: ok
[06:22] <Mirv> infinity: xnox: the qt3d was first uploaded and then binaries copied from a PPA. it was a main package that had a new universe dependency, but now qt3d should be demoted to universe.
[06:22] <Mirv> wgrant: my thinking was that Qt should be migrating soon, but now I'm unsure what would be needed next
[06:40] <Mirv> infinity: xnox: hmm, actually, rmadison would tell me it was demoted in xenial but not in xenial-proposed
[06:42] <didrocks> Mirv: what's the binary/source package name exactly? I can give a hand
[07:15] <Mirv> didrocks: qt3d-opensource-src
[07:16] <Mirv> (source)
[07:20] <didrocks> Mirv: done in xenial-proposed
[07:20] <didrocks> Mirv: http://paste.ubuntu.com/13885360/ for ref
[07:26] <Mirv> didrocks: thank you!
[07:27] <didrocks> yw ;)
[08:53] <xnox> wgrant, depends if infinity copied qt 5.5 into bootstrap, and whether that helped at all or not.
[08:53] <xnox> doesn't look like the case.
[08:53]  * xnox goes to the office to meet up with Laney
[09:09] <sil2100> Hello! o/ I'm disabling the system-image importer again for a while
[09:17]  * Ukikie checked to make sure he wasn't in scrollback.
[09:56] <xnox_> cjwatson: last night, infinity and I had an interesting idea.
[09:56] <xnox_> there are a lot of things dep-waiting on qt on s390x in xenial-release, which are incidentally needed to migrate a whole bunch of things from -proposed.
[09:57] <xnox_> instead of rebuilding libkf5*-dev on all arches in -proposed, we thought that taking qt5.5/s390x from proposed and dropping it into bootstrap archive should work
[09:57] <xnox_> and then retrigger builds of everything that dep-waits on qt in xenial-release/s390x.
[09:58] <xnox_> trying things this morning it seems like stuff hasn't been copied into bootstrap archive. Could I get a dump of everything what's in the bootstrap archive and get a few things copied from -proposed.
[09:58] <xnox_> otherwise i'll be binNMUing libkf5*-dev in -proposed, and Mirv will be sad.
[10:00] <Mirv> s/Mirv/phone landers/
[10:02] <Mirv> I was still thinking that if other blockers are resolved (currently checking aptdaemon issues with apt 1.1 AFAIK), s390x being a migration blocker could be postponed. but you know better
[10:15] <xnox_> infinity: oh i see things are in place.
[10:16] <xnox_> cjwatson: never mind.
[10:20] <xnox_> ooh shiny ubuntu-build
[10:26] <xnox_> infinity: thank you a lot!
[10:30] <xnox_> Mirv: i'm not touching xenial-release, and retrying builds on s390x
[10:38] <xnox_> not touching -proposed that is.
[10:38] <xnox_> hopefully s390x builds things really fast.
[10:47] <Mirv> fastness of s390x is a nice thing :) about identical to ppc64el.
[10:51] <xnox_> Mirv: checkout https://launchpad.net/builders =)
[10:52] <xnox_> Mirv: so, hopefully i can build enough of libkf* in release without uploading anything new, thanks for bootstrap archive ;-)
[10:57] <Mirv> xnox_: nice amount of builders too. arm64 could use more.
[10:59] <Odd_Bloke> Mirv: I believe that the Launchpad team are working on ironing out the last problems with arm64 virtualised builders, after which point there should be plenty more. :)
[11:04] <Mirv> Odd_Bloke: that'll be nice
[11:31] <xnox_> trying to fix sonet
[11:31] <xnox_> *sonnet
[11:37] <xnox_> uploaded sonnet, will need it in the bootstrap archive
[11:42] <xnox_> seb128: i want all s390x debs from https://launchpad.net/ubuntu/+source/sonnet/5.15.0-0ubuntu3/+build/8419927
[11:43] <xnox_> plus _all.deb from the amd64 build
[11:43] <xnox_> https://launchpad.net/ubuntu/+source/sonnet/5.15.0-0ubuntu3/+build/8419921
[11:47] <xnox_> seb128: http://paste.ubuntu.com/13891454/
[12:04] <cjwatson> xnox_: I'll sort that out for you.
[12:04] <cjwatson> seb128: ^-
[12:04] <cjwatson> Oh, somebody already has I think?
[12:05] <seb128> cjwatson, yes, I did, sorry
[12:05] <seb128> should have updated the channel
[12:05] <seb128> (we are sitting at the same table so bypassed IRC)
[12:26] <apw> it is probabally best to leave the kernel bits in new as we have a (possibly compiler related) issue with arm64
[15:04] <xnox_> cjwatson: infinity: Laney: i have no idea what happened, but britney says newly uninstallable packages in release: ubuntu-touch
[15:08] <xnox_> xenial-release is so uninstallable on s390x, that migrating broken things brought the total number of uninstallable things down, leading to this:
[15:08] <xnox_> start: 1277+0: a-38:a-22:a-21:i-22:p-24:p-22:s-1128
[15:08] <xnox_> orig: 1277+0: a-38:a-22:a-21:i-22:p-24:p-22:s-1128
[15:08] <xnox_> easy: 1161+0: a-105:a-83:a-145:i-68:p-88:p-82:s-590
[15:09] <cjwatson> Yeah, britney will trade off between arches, unfortunately
[15:09] <cjwatson> Fix it soon :)
[15:10] <xnox_> cjwatson: yes, Laney and I are prioritising to unbreak ubuntu-touch
[15:11] <xnox_> Mirv: so everything migrated, and ubuntu-touch is uninstallable.
[15:11] <Laney> fsvo everything
[15:16] <Mirv> xnox_: weird that it did that trading, but yes let's continue fixing
[16:00] <xnox_> so it's been an hour... lp is still publishing stuff
[16:07] <cjwatson> xnox_: finished a couple of minutes before you said that, actually
[16:08] <xnox_> cjwatson: rmadison for tulip is still at 4.7 on amd64
[16:09] <xnox_> that's the last package to copy.
[16:09]  * xnox_ can check ftpmaster.internal i guess.
[16:10] <cjwatson> xnox_: rmadison lags a little
[16:10] <cjwatson> only updates once snakefruit has got round to an archive-reports run
[16:10] <cjwatson> lag will depend on whether there's something like a very slow proposed-migration run hung off that
[16:52] <xnox_> Mirv: sil2100: ubuntu-touch depends on libqt53d5-gles, should it be renamed to the new package - the renderer thing?
[16:57] <xnox_> ..
[16:58] <infinity> ubuntu-touch is irksome that way, since it has hard deps on libraries and needs to track SONAME and other transitions. :/
[16:58] <xnox_> ditto that I did to ubuntu-core-meta yesterday for apt rename.
[16:58] <infinity> Might be nice if someone wrote an intelligend update script for it so that the preprocessed deps are dev packages, and it can regenrate the library deps without a human hunting them down.
[16:58] <xnox_> ok we are pushing it.
[16:59] <infinity> intellgent, even.
[16:59] <infinity> Argh.
[16:59] <infinity> Irony++
[16:59] <infinity> INTELLIGENT.
[17:00] <infinity> xnox_: subversion merge (which will unstick git) is incoming.  Just test-building locally to make sure it's not crap.
[17:00] <xnox_> good.
[17:00] <xnox_> and i have to do mono still...
[17:02] <infinity> xnox_: Bringing us up to 4.2?
[17:02] <infinity> Which just hit unstable today...
[17:03] <infinity> xnox_: Mono doesn't need a merge, FWIW, all the Ubuntu patches should be in 4.2
[17:03] <infinity> xnox_: Can just force sync and pray.
[17:03]  * infinity might do that now.
[17:05] <infinity> Oh.  But it's arch-restricted in Debian to not build on powerpc.  Irksome.
[17:05] <infinity> I guess I do need to fix that at least.
[17:05]  * infinity will look later.
[17:08] <cjwatson> infinity: directhex deliberately dropped support for powerpc recently on the grounds that he stopped being able to get it to work
[17:09] <cjwatson> infinity: there's a bunch on debian-powerpc@ about it
[17:09] <infinity> Well, I might give it a quick once-over, but if it's not obviously fixable, we can do some cleanup, I guess.
[17:09] <infinity> arm64 is in a similar boat.
[17:10] <infinity> So, clearly we don't need mono to get by.
[17:11] <Mirv> xnox_: sil2100: please remove it altogether, ubuntu-touch does not use Qt3D at all
[17:11] <Laney> oh well, next time :)
[17:12] <Laney> ...which is now
[17:12] <Laney> because I messed up...
[17:13] <cjwatson> infinity: https://gist.github.com/directhex/2b5def025fda42cc334b I believe
[17:14] <infinity> cjwatson: Yeah, found the thread and started reading.
[17:14] <infinity> cjwatson: I think it'll be saner to do an rdep cull for now and make this a side project for if/when I have free time.
[17:14] <infinity> cjwatson: Like I said, the fact that arm64 isn't entirely busted without mono seems to prove we don't "need" it, it's just nice to have.
[17:15] <cjwatson> Probably, yeah
[20:56] <stgraber> hmm, how did that qt mess get to the release pocket? a dist-upgrade on my laptop is trying to upgrade a ton of qt stuff and resolves it by removing chunks of unity, that doesn't seem quite right :)
[20:59] <stgraber> hmm, interesting, looks like installing liboxideqt-qmlplugin solves a lot of problems, it removes two packages from my system (oxideqt-codecs-extra and qtdeclarative5-ubuntu-ui-toolkit-plugin) and makes the upgrade look sane then
[21:01] <stgraber> seems like qtdeclarative5-ubuntu-ui-toolkit-plugin still needs some love so the ubuntu-desktop task is actually installable
[21:48] <xnox> stgraber, yes. britney traded -500 of uninstallable packages for +60 packages on all other arches, sans a dozen resolved things across all architectures.
[21:48] <xnox> stgraber, we are fixing ui-toolkit yes.
[21:49] <xnox> (-500 on s390x that is, so I am very happy about that =) )


[03:06] <acheron-a> ;)
[03:52] <Bashing-om> eyes are crossing ! Time !
[03:53] <acheron-a> hello again bash
[03:53] <acheron-a> time for sleep?
[04:48] <lotuspsychje> good morning to all
[04:51] <lotuspsychje> new xenial kernel
[04:51] <lotuspsychje> !info linux-image-generic xenial
[04:54] <lotuspsychje> morning baizon
[04:55] <lotuspsychje> 75mb update this morning / new kernel
[05:15] <baizon> hi lotuspsychje
[05:24] <lotuspsychje> morning philipballew
[05:45] <lotuspsychje> morning acheron-a & glebihan
[05:45] <acheron-a> hello lotuspsychje
[06:08] <EriC^^> morning lotuspsychje
[06:09] <lordievader> Good morning
[06:09] <lotuspsychje> hey EriC^^ & lordievader
[06:09] <lotuspsychje> you guys all sleep well?
[06:09] <EriC^^> morning lordievader
[06:10] <EriC^^> yeah
[06:10] <lordievader> Hey lotuspsychje, EriC^^
[06:10] <lordievader> Quite okay.
[06:10] <lordievader> You?
[06:10] <lotuspsychje> great here
[06:28] <lotuspsychje> morning BobbyJr
[06:31] <ducasse> hi all
[06:34] <lotuspsychje> hey ducasse
[06:34] <lotuspsychje> all ok in norway?
[06:39] <ducasse> lotuspsychje: all good, thanks. how are you today?
[06:42] <lotuspsychje> great here ducasse
[06:42] <lotuspsychje> 5 days off
[06:43] <ducasse> ahh, nice. any plans, or just relax?
[06:47] <lotuspsychje_> ducasse: and enjoying the weather
[06:47] <ducasse> 22 package updates for zesty today, getting closer to release...
[06:51] <lotuspsychje> ducasse: 75mb on xenial here
[06:52] <ducasse> that was with a kernel update? i got that on yakkety but not zesty.
[07:00] <lotuspsychje> yep
[07:00] <lotuspsychje> !info linux-image-generic xenial
[07:11] <lotuspsychje> http://news.softpedia.com/news/linux-kernels-4-10-6-4-9-18-lts-and-4-4-57-lts-released-with-updated-drivers-514312.shtml
[07:18] <ducasse> lotuspsychje: btw, i applied for membership in the wiki team, but haven't heard anything yet. i wrote up some stuff for the grep page, maybe i can submit it to someone in #ubuntu-doc?
[07:19] <lotuspsychje> ducasse: cool, but not sure those guys are alive there
[07:20] <ducasse> i don't even know if that is where the wiki people hang out, or if that's for things like the server guide etc
[07:20] <lotuspsychje> ducasse: perhaps the mailing list or so?
[07:21] <ducasse> which one? the launchpad page for the wiki team says there isn't one...
[07:23] <lotuspsychje> hmmm
[07:23] <ducasse> i can try contacting the admins, ask if i can just finish it up and submit it to them.
[07:24] <lotuspsychje> cant find neither
[07:24] <lotuspsychje> ah
[07:24] <lotuspsychje> ducasse: https://wiki.ubuntu.com/DocumentationTeam/Contact
[07:25] <ducasse> not the same team :)
[07:26] <lotuspsychje> ah
[07:26] <ducasse> aha, seems they use the same mailing list. i'll subscribe to that :)
[07:27] <lotuspsychje> :p
[07:28] <lotuspsychje> lets hope its a bit active
[07:28] <ducasse> easy to check...
[07:29] <ducasse> seems quite busy.
[08:42] <lotuspsychje> http://www.omgubuntu.co.uk/2017/03/rock-deepin-music-now-available-snap-app
[08:43] <lotuspsychje> handy stuff those snaps
[08:52] <lotuspsychje> http://fossforce.com/2017/03/fedex-will-pay-5-install-flash-machine/
[08:52] <lotuspsychje> wth?
[08:55] <ducasse> lol
[10:15] <BluesKaj> Hi folks
[10:20] <ducasse> hi BluesKaj, just as you arrive traffic picks up again, after over an hour quiet :)
[10:21] <BluesKaj> hi ducasse ...am i being followed ? :-)
[10:22] <ducasse> quick, cloak your traffic with tor! ;)
[10:24] <BluesKaj> I am cloaked , but it's slow to enable hence the IP leak
[10:26] <BluesKaj> I've noticed that bug for a while
[10:26] <BluesKaj> I'm not concerned tho
[10:27] <ducasse> i hadn't noticed, actually. not that i really care.
[10:29] <BluesKaj> suppose if I was concerned I could connect via vpn
[10:31] <ducasse> i could as well, i really should use my pia subscription more. i'm not getting my money out of it as it is, i hardly use it.
[10:31] <BluesKaj> tor isn't my much to my liking
[10:32] <BluesKaj> PIA is cheap tho and worth the money
[10:33] <ducasse> not a tor fan either, no need for it.
[10:33] <BluesKaj> my renewal comes up in 2 weeks
[10:34] <ducasse> mine is just around new year, as i got my first year as a christmas present. easy to remember :)
[10:39] <BluesKaj> some servers are better than others IME , at least here in NA, haven't used many of the euro or asian servers
[10:43] <ducasse> i get really good speeds from the euro servers, only slightly less than with no vpn.
[10:44] <BluesKaj> my dsl is quite slow do I don't notice any difference at all
[10:44] <BluesKaj> do=so
[10:45] <BluesKaj> but I have plenty of time
[10:45] <ducasse> got some good news from my isp yesterday, they've increased my tier with 30mbps, and from next month hbo nordic will be included in my subscription at no extra charge.
[10:46] <BluesKaj> nice :-)
[10:49] <ducasse> plus they've included their own streaming thing. not too much interesting stuff there, but some, and it's free :)
[11:55] <lotuspsychje> good afternoon to all
[11:56] <pauljw> hi lotuspsychje
[11:57] <lotuspsychje> hey pauljw
[11:58] <lotuspsychje> sunny weather over here
[11:59] <lotuspsychje> http://www.omgubuntu.co.uk/2017/03/stacer-ubuntu-system-cleaner-update
[12:00] <lotuspsychje> pretty nice app, too bad its not in our repos
[12:05] <BluesKaj> autoclean autoremove ftw
[12:05] <lotuspsychje> hey there BluesKaj
[12:05] <lotuspsychje> welcome ikevin
[12:05] <BluesKaj> hi lotuspsychje
[12:06] <ikevin> ty
[12:06] <lotuspsychje> ikevin: here is where we discuss topics, to serve #ubuntu better
[12:06] <lotuspsychje> BluesKaj: indeed, a bit like bleachbit also a GUI for autoclean etc
[12:07] <lotuspsychje> ikevin: what distro are you on?
[12:08] <BluesKaj> i have a lot of my regular commands aliased so a gui is not needed
[12:08] <ikevin> lotuspsychje, i use mint for work and ubuntu for personnal use
[12:08] <lotuspsychje> BluesKaj: same here, but some new users might like GUI apps like that, looks pretty neat that stacer
[12:08] <ikevin> i've some servers on ubuntu server and debian too
[12:08] <lotuspsychje> ikevin: LTS or non-lts?
[12:09] <ikevin> non lts, i always update to the last stable
[12:09] <ikevin> so, for servers i use lts
[12:09] <ikevin> but*
[12:09] <lotuspsychje> ikevin: cool! mint as personal choice, or your work, works with it by default?
[12:10] <ikevin> personnal choice, i'm the founder of my compagny
[12:10] <lotuspsychje> oh nice, what do you do ikevin?
[12:11] <ikevin> i'm developper
[12:11] <lotuspsychje> neat
[12:12] <lotuspsychje> i wonder what munich will do now..stick to ubuntu or leave to windows again
[12:14] <lotuspsychje> https://www.ubuntu.com/desktop/government
[12:18] <lotuspsychje> https://itsfoss.com/munich-linux-failure/
[12:18] <BluesKaj> costs plenty in man hours and money to switch OSs on that scale
[12:19] <ikevin> in some case it need some specifics software to be developped
[12:19] <lotuspsychje> BluesKaj: true, but i wonder how safe the network is when staying years on broken windows boxesµ
[12:21] <lotuspsychje> howdy brunch875
[12:24] <BluesKaj> lotuspsychje, the switch to MS is really unfortunate, there must be a lot of pressure by MS lobbyists in Bonn and Berlin, not just Munich. It's very disappointing. :/
[12:25] <lotuspsychje> BluesKaj: yeah think so too
[12:26] <BluesKaj> the MS anti viruses companies are gonna gave a field day now
[12:26] <lotuspsychje> lol
[12:27] <lotuspsychje> perhaps they should have chosen vanilla ubuntu instead of limux
[12:29] <lotuspsychje> afternoon pavlushka
[12:31] <BluesKaj> lotuspsychje, I think the Munich city council will more than regret their decision , W10 is an awful OS
[12:31] <pavlushka> afternoon lotuspsychje :)
[12:31] <pavlushka> lol
[12:32] <lotuspsychje> pavlushka: you joined at the right time :p
[12:33] <lotuspsychje> BluesKaj: it sure is, we will follow its developments in germany
[12:33] <pavlushka> lotuspsychje: that's I am, the person who joins at the right time :p
[12:33] <lotuspsychje> lol
[12:33] <lotuspsychje> OerHeks: !
[12:33] <BluesKaj> lotuspsychje, I'm sure you'll keep us informed :-)
[12:34] <lotuspsychje> BluesKaj: my eyes are pointed to the latest daily :p
[12:34] <OerHeks> hello hello :-)
[12:35] <BluesKaj> hey OerHeks
[12:36] <lotuspsychje> just on time for some ubuntu vanilla coffee with a !cookie
[12:36] <pauljw> hi OerHeks
[12:37] <lotuspsychje> for those who didnt see this mornings url: wth..http://fossforce.com/2017/03/fedex-will-pay-5-install-flash-machine/
[12:37]  * lotuspsychje is grabbing 5$ greedy :p
[12:51] <ducasse> they would need to add some zeroes behind that to get me to install flash on my systems :)
[12:51] <lotuspsychje> wahaha
[12:51] <lotuspsychje> install flash and get 10 exploits free with it
[13:11] <brunch875> damn
[13:14] <ikevin> lotuspsychje, + some freeze :p
[13:21] <pauljw> brb
[13:50] <lotuspsychje> wildpenguin = crazytux?
[13:52] <ducasse> i was wondering exactly the same thing.
[13:52] <OerHeks> something like that
[13:52] <lotuspsychje> smells like troll :p
[13:53] <ducasse> "i've installed mate and now i want lubuntu" sounds all too familiar
[13:53] <lotuspsychje> lol
[13:54] <OerHeks> he is on kali.
[13:54] <ducasse> he said mate earlier, but he knows well enough what we support...
[13:55] <lotuspsychje> i surely saw him changing nicks before
[13:56] <OerHeks> ♫ lonely people
[13:56] <ducasse> from...? too lazy to check.
[13:57] <lotuspsychje> servers (freenode)/#debian.log:jan 14 09:44:24 * WildPenguin is now known as CrazyTux
[13:58] <ducasse> surprise...
[13:59] <lotuspsychje> @1127 http://her0.be/index.php?action=logfile&date=20170114
[14:00] <lotuspsychje> #debian and #ubuntu troll installing mate, 16.10,lubuntu and kali lol
[14:01] <lotuspsychje> afternoon acheron-a
[14:01] <ducasse> lotuspsychje: should we ask for lsb-release output?
[14:02] <lotuspsychje> ducasse: perhaps he will outsmart us?
[14:02] <acheron-a> hello lotuspsychje
[14:02] <ducasse> maybe, maybe not.
[14:03] <lotuspsychje> ducasse: maybe trick him with cat issue lol
[14:03] <ducasse> i'll wait until he asks something.
[14:04] <lotuspsychje> great
[14:05] <lotuspsychje> no luck, he left :p
[14:05] <ducasse> i noticed.
[14:08] <lotuspsychje> bbl sunwalk
[14:08] <ducasse> lotuspsychje: enjoy! :)
[15:50] <OerHeks> Update your "Eject" package. Eject could be made to run programs as an administrator. Affects versions: 12.04 LTS, 14.04 LTS, 16.04 LTS, and 16.10
[15:57] <lotuspsychje> !info eject
[16:14] <lotuspsychje> we should have up to date !nvidia & !amd/ati triggers when things change on ubuntu versions
[16:14] <nacc> lotuspsychje: yeah, that would be good
[16:15] <lotuspsychje> all the explaining we need to do right now
[16:19] <lotuspsychje> !amd
[16:19] <nacc> this is alsowhere the hwe gets users confused
[16:19] <nacc> 14.04.5 is an archive snapshot and a kerenl/X stack
[16:19] <lotuspsychje> right
[16:19] <lotuspsychje> amd trigger seems updated
[16:20] <lotuspsychje> !nvidia
[16:20] <lotuspsychje> lets check wiki date here
[16:20] <lotuspsychje> 7/2016 not bad
[16:21] <lotuspsychje> 12/2016 for amd
[16:21] <lotuspsychje> looking pretty good
[16:22] <ducasse> if only people read and understood the links :)
[16:23] <lotuspsychje> yeah, thats tricky indeed
[16:23] <nacc> i got an ack to update the 14.04 release notes
[16:24] <lotuspsychje> what you mean nacc?
[16:25] <nacc> to clarify flgrx support
[16:25] <nacc> fglrx :)
[16:25] <lotuspsychje> kk
[16:27] <ducasse> nacc: "catalyst" was easier to remember and spell :)
[16:28] <nacc> heh
[16:31] <lotuspsychje> nacc: anything usefull here? https://help.ubuntu.com/community/RadeonDriver
[16:35] <nacc> ah yes htat's good
[16:35] <nacc> but it really should have been in the release notes
[16:36] <lotuspsychje> with !radeon triggers forward to !amd
[16:36] <lotuspsychje> and !releasenotes goes to xenial right now
[16:37] <brunch875> I just spotted the tiobe index
[16:37] <brunch875> javascript is going up onoooooo
[16:37] <brunch875> I had hoped to see Rust over there
[16:37] <nacc> lotuspsychje: grrr, really need the latter to be per-release :)
[16:37] <brunch875> but if C is going down so quickly... what is ubuntu being developed on?
[16:38] <nacc> go
[16:38] <lotuspsychje> nacc: yeah i know..
[16:38] <brunch875> isn't go interpreted?
[16:38] <nacc> brunch875: you can statically compile it, as well
[16:38] <lotuspsychje> brb
[16:38] <nacc> brunch875: also, i don't trust any such garbage sites :) the kernel is still in c
[16:39] <nacc> brunch875: and 'ubuntu being developed on' is a nonsense question -- every language under the sun
[16:39] <brunch875> ah yes, I know :)
[16:39] <brunch875> but I had Qt in mind
[16:39] <brunch875> which implies C++ for the most part
[16:39] <brunch875> which means performance!
[16:40] <brunch875> since nowadays a lot of applications are developed in javascript, I'm full of fears
[16:40] <ducasse> death to electron
[16:40] <brunch875> death to electron!
[16:42] <nacc> updated https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes lotuspsychje
[16:42] <nacc> brunch875: i don't know of any end-user applications that are 'developed' in javascript -- do you mean web apps/phone apps?
[16:44] <brunch875> nacc: I was mostly referring to apps such as atom, the discord client or the newest skype
[16:44] <nacc> !info atom
[16:44] <nacc> !info discord
[16:45] <nacc> !info skype
[16:45] <brunch875> haha surely you know what skype is :p
[16:45] <nacc> none of those are relevant to 'ubuntu being developed on'
[16:45] <nacc> as none are in ubuntu
[16:46] <brunch875> fair enough! But you understand my fear of ubuntu hopping onto this trend, right?
[16:47] <nacc> no
[16:47] <nacc> you mentioned 3 applications, none of which are in ubuntu
[16:47] <nacc> and aren't in zesty either
[16:47] <nacc> skype is a web based application, it can possibly be reasonable to write in js
[16:47] <nacc> for the web-based client, which is all that will exist eventually
[16:47] <nacc> but even then, it's not *all* js
[16:48] <nacc> there's still a server side application doing all the heavy lifting
[16:48] <nacc> and i feel like you are saying all of ubuntu is some monolithic thing
[16:48] <nacc> we still have fortran compilers
[16:48] <nacc> and COBOL
[16:49] <nacc> so will ubuntu allow you to build your app using whatever junk is out there?
[16:49] <nacc> probably
[16:49] <brunch875> what I feel like is ubuntu is mostly a performing operating system
[16:49] <nacc> will ubuntu ship an app that builds with that junk? if an upstream decides to
[16:49] <brunch875> without excessive overhead
[16:49] <nacc> ubuntu does not dictate what upstreams do or do not decide to do
[16:49] <brunch875> who decides what goes on upstream?
[16:50] <nacc> ...
[16:50] <nacc> upstream?
[16:50] <brunch875> errr lemme rephrase
[16:50] <nacc> brunch875: do you know how open source distributions work? :)
[16:50] <brunch875> who decides what upstreams we get?
[16:50] <brunch875> nacc: for the most part, no
[16:50] <nacc> brunch875: ah ok
[16:51] <nacc> brunch875: upstreams are (generally) distribution agnostic
[16:51] <nacc> e.g., a github project
[16:51] <nacc> distributions pacakge those upstreams for easy consumability by users
[16:51] <nacc> so packagers decide what upstream exist
[16:51] <nacc> in ubuntu, almost all of them are from debian
[16:52] <brunch875> so as long as debian doesn't become senile, we're good
[16:54] <nacc> ubuntu also does some of its own packaging and goes ahead of debian, where debian's rules might be a bit restrictive
[16:54] <nacc> and snaps will change things further
[16:54] <ducasse> is appimage support for ubuntu planned?
[16:55] <nacc> ducasse: is that a flatpak/snap competitor?
[16:55] <ducasse> yep.
[16:55] <ducasse> i noticed flatpak support exists, so just curious.
[16:56] <nacc> yeah,  i htink jbicha got flatpak support in, although in universe (snap support is in main of course)
[16:58] <nacc> ducasse: hrm, not seeing it in 17.04, but their site mentions they support ubuntu
[16:58] <nacc> ah they have their own .deb :/
[16:58] <ducasse> ah nice :) maybe 17.10, then :) i just noticed it wasn't in zesty here.
[16:59] <nacc> https://github.com/probonopd/AppImageKit/issues/339
[17:00] <ducasse> thanks, nacc
[17:00] <nacc> looks like debian packaging is forthcoming?
[17:00] <nacc> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854902
[17:00] <nacc> ducasse: i presume we'd get it automatically after that via sync
[17:01] <ducasse> right. sounds reasonable.
[17:02] <nacc> i think canonical has a vested interest in snaps; flatpak and appimage and others are competitors, and i think it's all a question of which wins the market share
[17:02] <nacc> i don't think it'd be great to have 2 or 3 of these formats out there
[17:02] <nacc> i think clear linux has their own as well
[17:02] <brunch875> let us hope one wins clearly
[17:03] <ducasse> tbh, i hope it won't be snaps
[17:03] <brunch875> why's that, ducasse?
[17:04] <ducasse> flatpak allows anyone to set up a repo and provides the necessary software, not so for snaps. has to be the ubuntu store.
[17:04] <davidj> So! Anyone using 17 yet? If so, stable?
[17:04] <davidj> 16 has been a shitfest for me, was hoping 17 would be a step up.
[17:04] <brunch875> davidj: Using it. I think I had more crashes in 16
[17:05] <ducasse> davidj: it's been stable here, but so was 16.04/16.10.
[17:05] <davidj> Hm. Nothing but crashes for me perpetually.
[17:05] <brunch875> I've only had one single crash and I believe it was my mistake
[17:05]  * davidj nods. Well, guess I'll give it a try instead of sincerely contemplating swapping to windows ;)
[17:05] <nacc> ducasse: that will be changing
[17:05] <nacc> ducasse: aiui
[17:05] <ducasse> nacc: oh? good.
[17:05] <nacc> ducasse: yeah, 'on-premise' store
[17:05] <brunch875> I'm a big fan of snaps because on how the plugs seem to work
[17:06] <nacc> ducasse: i think you can actually do it already, just requires some setup
[17:06] <brunch875> I only dislike that confinement sometimes goes in the way
[17:07] <brunch875> ie: can't click links on hexchat
[17:07] <brunch875> have to select, copy and paste
[17:07] <nacc> with the argument that once it 'just works', confinement is a huge win
[17:07] <nacc> brunch875: yeah, i assume that's a *bus issue ?
[17:07] <brunch875> nacc: no idea, never debugged it :
[17:07] <brunch875> but probably
[17:08] <nacc> brunch875: the whole desktop side of things is tricky
[17:08] <nacc> and snaps/flatpak/etc show how messy desktop has gotten
[17:08] <nacc> dependencies not being expressed, etc
[17:08] <brunch875> that's the problem with already developed technologies
[17:08] <brunch875> it's hard to retract from mistakes
[17:08]  * nacc wonders if they've fixed the issue where you can't just use two apache-based snaps because they compete for port 80
[17:11] <brunch875> I wonder if snaps will ever 'just work' or if confinement will become a never-ending headache
[17:12] <brunch875> where many installation instructions will prompt to "disable confinement"
[17:13] <nacc> brunch875: it's only been a year or so :)
[17:13] <nacc> brunch875: give it time
[17:13] <nacc> brunch875: well of the more aggressive model (UC16)
[17:13] <brunch875> nacc: believe me, I'm already suprised on how good it works
[17:13] <brunch875> otherwise I wouldn't use it over the 'regular' applications
[17:13] <nacc> yeah, they have done some amazing work, imo -- some things are way easier
[17:14] <nacc> esp. where upstream has owned the application, then you get the latest all the time, if you want (edge channel)
[17:14] <brunch875> heck, I can even drag-and-drop pictures to telegram
[17:15] <brunch875> but then I think about pip3
[17:15] <brunch875> and I really wonder how's that going to work with snaps
[17:16] <davidj> Yay. 17 is already more stable than 16 was for me. Thanks @brunch875
[17:16] <davidj> No graphics issues lingering. Then again, only booted a few moments. Let's see how it fairs :p
[17:16] <brunch875> davidj: already installed? Haha! Don't thank me, thank the developers :p
[17:16] <davidj> True, true.
[17:16] <lotuspsychje> nacc: didnt know you always was a wiki edit member?
[17:16] <davidj> Curious — anyone ever have issues with scroll wheel speeds? Razer synapse. Was going to try imwheel..., just didn't want to have to make a config for every program.
[17:17]  * davidj despises tinkering, I think I'm on the wrong OS :/
[17:17] <lotuspsychje> evening baizon
[17:18] <lotuspsychje> brunch875: the snap list grows by the minute..big list already
[17:18] <lotuspsychje> nacc: nice work on the wiki
[17:18] <nacc> lotuspsychje: np
[17:19] <brunch875> lotuspsychje: how can I check? 'snap find' only shows 4 entries
[17:19] <ducasse> brunch875: give it a keyword
[17:19] <lotuspsychje> nacc: does the wiki team have a special irc channel? or you subscribed to the mailing?
[17:19] <baizon> well hello there lotuspsychje
[17:19] <nacc> lotuspsychje: i don't think so -- i just asked timo in #ubuntu-devel
[17:20] <lotuspsychje> aha, you got connections nacc, good to know :p
[17:20] <nacc> lotuspsychje: :)
[17:20] <ducasse> brunch875: try 'snap find searchterm'
[17:20] <lotuspsychje> http://www.omgubuntu.co.uk/2017/03/rock-deepin-music-now-available-snap-app
[17:20] <nacc> lotuspsychje: and i'm a core-dev, so i can help usher fixes in
[17:20] <brunch875> ducasse: yeah, searching for 'a' got me a couple of entries
[17:21] <lotuspsychje> ducasse: ¨^handy for us wiki edits
[17:21] <nacc> not meant to be braggy, meant to be helpful :)
[17:21] <lotuspsychje> we know mate dont worry
[17:22] <lotuspsychje> we are simply the best lol
[17:22] <nacc> heh
[17:22] <lotuspsychje> time for snap to get that latest snaps search again grrr
[17:22] <lotuspsychje> snap find * or something
[17:23] <nacc> yeah, i think te biggest issue for snaps is all tooling
[17:23] <nacc> snap was broken for a while, and the 'api' keeps changing
[17:23] <ducasse> man, the snap 'find' command works in mysterious ways...
[17:23] <nacc> it's very much a wip
[17:23] <brunch875> rename it to "snap god"
[17:23] <nacc> i think the software GUI thing can also search for snaps, but i'm not sure
[17:23] <lotuspsychje> good ol apt is always stable
[17:24]  * nacc found a nice bug in it recently (well not in apt itself, but in ubuntu)
[17:24] <lotuspsychje> nacc: yes it does, and requiers ubuntu one account to install
[17:24] <nacc> lotuspsychje: right, so you can login to the store, i guess
[17:25] <lotuspsychje> lemme test that deepin snap holdon
[17:26] <nacc> brunch875: my guess as to the link issue with hexchat, is that, as you say, it requires mediation by someting to say what a link means to hexchat (or hexchat could technically ship their own browser :)
[17:26] <nacc> brunch875: in confined mode, that is, since it only sees hexchat (presumably) and its libs in the squashfs it runs in
[17:27] <lotuspsychje> yep, deepin-music showsup ubuntu-software
[17:27] <brunch875> oh, so hexchat isn't launching firefox because it doesn't exist
[17:27] <brunch875> witty
[17:27] <lotuspsychje> asking my ubuntu one account
[17:27] <nacc> brunch875: right, in confined mode, it presumably does not
[17:27] <brunch875> lotuspsychje: I got two snaps and it never asked me for login
[17:28] <lotuspsychje> brunch875: did you install it the sudo way?
[17:28] <ducasse> brunch875: only certain ones do
[17:28] <nacc> brunch875: i think there was some discussion in #snappy of the equivalent of a 'browser' plug
[17:28] <brunch875> ah I see
[17:28] <nacc> or interface
[17:28] <nacc> so that you can say, i need a browser to exist (or if it exists, connect me to it) in your snap
[17:28] <nacc> and then you send browser requests to it
[17:28] <brunch875> nacc: what about <program>:// urls?
[17:28] <nacc> it is interesting how it ends up looking like a massive message-passing thing
[17:28] <nacc> brunch875: i don't know any of the details, tbh :)
[17:30] <nacc> and what i do recall is out of date quickly it feels like :)
[17:30]  * nacc is not on that team directly
[17:40] <lotuspsychje> the new eject exploit oerheks suggested us: https://www.ubuntu.com/usn/usn-3246-1/
[17:41] <brunch875> solution: deprecate optical drives forever
[17:44] <lotuspsychje> lotuspsychje@RooTBooK:~$ apt-cache policy eject
[17:44] <lotuspsychje> eject:
[17:44] <lotuspsychje>   Geïnstalleerd: 2.1.5+deb1+cvs20081104-13.1ubuntu<IP_ADDRESS>
[17:44] <lotuspsychje> im good :p
[17:44] <lotuspsychje> !info eject xenial
[17:47] <lotuspsychje> yeah its true that generic guy is here all day..not sure who or what solved or not...
[17:48] <nacc> lotuspsychje: ah ok, thanks!
[17:48] <ducasse> lotuspsychje: asking 10 questions/minute...
[17:48] <lotuspsychje> sometimes i have irc dejavu's of usernames that keep comming back with all the same questions lol
[17:49] <nacc> Dreaman is on my hitlist right now (mentally)
[17:49] <lotuspsychje> we have nightmares of crazytux alias wildpenguin lol
[17:49] <nacc> lol
[17:50] <lotuspsychje> think im gonna write a blacklist
[17:50] <ducasse> my personal 'favorite' has to be crazytux, yes
[17:50] <lotuspsychje> haha
[17:50] <ducasse> he deserves a ban soon :-/
[17:50] <lotuspsychje> yeah its like that jackal movie
[17:51] <lotuspsychje> keeps comming back with other personalitys
[17:51] <ducasse> every single time he produces output he admits it's from mint, kali or whatever
[17:51] <lotuspsychje> he will make a big mistake soon ducasse, we will grab him :p
[17:52] <ducasse> lol
[17:52] <ducasse> "one day you will go too far, and we will be there waiting..."
[17:52] <lotuspsychje> and laughing
[17:53] <lotuspsychje> ducasse: thats my life MOTD, positive revenge karma
[17:54] <lotuspsychje> you cant keep fooling ppl, one day its your turn
[17:54] <ducasse> true
[17:57] <lotuspsychje> https://insights.ubuntu.com/2017/03/28/battlestar-solution/
[17:58] <lotuspsychje> interesting...as IOT grows, ddos attacks will also
[17:58] <nacc> absolutely true
[17:58] <nacc> esp. once a vulnerability is found
[17:58] <nacc> every networked fridge in america will become a massive botnet :)
[17:59] <nacc> e.g. :)
[17:59] <lotuspsychje> your vulnerable fridge or microwave
[17:59] <lotuspsychje> yep
[17:59] <nacc> and rolling out fixes will be ... tricky
[17:59] <nacc> as the router is also IOTish
[17:59] <nacc> and if it's also been hacked, you can fake the update
[17:59] <lotuspsychje> r00ters love 24/7 things and will always hunt them
[18:00] <lotuspsychje> so those ubuntu core mobo's better come fast everywhere
[18:01] <nacc> heh
[18:03] <lotuspsychje> Ingenic: good evening, welcome
[18:03] <Ingenic> hello
[18:05] <lotuspsychje> !grep
[18:07] <lotuspsychje> triggers getting better and better
[18:15] <lotuspsychje> anyone looking for the xp feeling? lol http://www.noobslab.com/2017/03/give-windows-xp-look-to-your-ubuntu.html
[18:16] <nacc> lol
[18:16] <lotuspsychje> nostalgic
[18:25] <Ingenic> I try to forget that xp is still used in important places
[18:25] <Ingenic> like banks
[18:25] <lotuspsychje> brrr
[18:26] <lotuspsychje> Ingenic: is there any windows thats safe in use?
[18:27] <lotuspsychje> my early xenial testing: http://www.deviantart.com/art/Ubuntu-16-04-64bit-Development-branch-598369242
[18:27] <lotuspsychje> http://www.deviantart.com/art/Ubuntu-16-04-64bit-Development-branch-601374206
[18:28] <Ingenic> lotuspsychje: probably not, but there's definitely better than xp hahaha
[18:28] <lotuspsychje> Ingenic: i think many countries still run windows ME, 98 and old server versions
[18:29] <lotuspsychje> think china, taiwan,korea
[18:29] <Ingenic> lotuspsychje: oh god, that can't be good
[18:29] <lotuspsychje> http://www.deviantart.com/art/Ubuntu-16-04-64bit-Development-branch-568865930
[18:31] <ducasse> lotuspsychje: why wouldn't they pirate later versions given that they don't exactly purchase licenses anyway?
[18:32] <lotuspsychje> ducasse: indeed
[18:36] <ducasse> hungry cat incoming, better serve dinner asap :)
[18:37] <lotuspsychje> lol
[18:37] <lotuspsychje> bon apetit cat!
[18:38] <lotuspsychje> nacc: speaking of the devil; new article in belgium hackers break in a IOT fridge, once their on the network they open the electric garage gate and steal it all
[18:39] <lotuspsychje> spokesman warns: dont leave the default login:pass on your fridge lol
[18:39] <nacc> lol
[18:39] <ducasse> well, duh.
[18:39] <lotuspsychje> we aint seen nothing yet guys
[18:40] <lotuspsychje> ive been warning ppl not to use online banking on smartphones for like 5 years now
[18:40] <lotuspsychje> now they come with online paying on smartphones just everywhere..
[18:41] <lotuspsychje> push a button and you bought it...
[18:42] <lotuspsychje> crazy world
[19:01] <lotuspsychje> someone looses his android phone, the thief can pay stuff anywhere
[19:06] <lotuspsychje> http://www.consortiuminfo.org/standardsblog/article.php?story=20170327154910861
[19:06] <lotuspsychje> IoT articles showing up everywhere now lol
[19:08] <pauljw> scary stuff
[19:09] <lotuspsychje> certainly knowing alot of cheap IoT devices will get sold that are highly vulnerable on weak Oses
[19:10] <pauljw> yep, to people that have no idea about the risks and how to implement network security.
[19:11] <lotuspsychje> its a weird thought, burglers are now half-crackers lol..a cowbar and a laptop
[19:11] <pauljw> heheh...
[19:11] <lotuspsychje> howdy acheron-a & Wirehunter
[19:12] <acheron-a> hello lotuspsychje
[19:13] <Wirehunter> Hi, good evening
[19:14] <lotuspsychje> hi yobagme
[19:20] <lotuspsychje> EriC^^: your the uefi wizard man!
[19:20] <lotuspsychje> good to have you here :p
[19:25] <acheron-a> the whole UEFI was an intel thing but then M$ for involved and forced BIOS makers to make changes for windows 8 and 8.1 and now there is complete irregular implementation of it because of that
[19:26] <acheron-a> for involved = got involved
[19:26] <lotuspsychje> i hope in the future more brands will choose barebones and leave the user the choice
[19:28] <lotuspsychje> forcing users with a specific Os is so wrong
[19:28] <acheron-a> even from the same MB maker just a difference in the model of MB, i can find variances in the implementation, some makers just gave up and caved to M$ and just left a legacy BIOS setting for everybody else
[19:28] <EriC^^> lotuspsychje: :P
[19:29] <acheron-a> and some don't even have that
[19:29] <acheron-a> so this causing real problems for Linux installs
[19:31] <acheron-a> especially on MB designed in the Win 8.1 era
[19:32] <Ingenic> yeah, they're forcing Linux users onto older hardware
[19:32] <lotuspsychje> alot of workarounds to install linux on machines :p
[19:33] <acheron-a> the newer GigaByte are pretty good
[19:33] <acheron-a> i wish people would publish a list or have a blog on what works and what doesn't and for what distro
[19:35] <acheron-a> HP has a fairly clean UEFI since they are a big Red Hat and SuSe partner
[19:36] <Ingenic> My Lenovo has been pretty accepting of most distros too
[19:41] <lotuspsychje> laterz guys, takeover the support
[19:41] <acheron-a> so are the newer Dells


[04:48] <ista> Does ubuntu ppa support http transfer?
[04:51] <ista> while trying dput with configuration method = sftp, I meet Unable to connect to SSH host ppa.launchpad.net; EOF during negotiation
[04:51] <wgrant> ista: You can only upload to a Launchpad PPA using SFTP or FTP.
[04:51] <wgrant> If your network doesn't permit either of those protocols to ppa.launchpad.net, you'll need to find another network from which to upload your packages.
[04:53] <ista> Uploading to my-ppa (via sftp to ppa.launchpad.net):
[04:53] <ista>   babl_0.1.8-1.dsc: Permission denied (publickey).
[04:53] <wgrant> ista: Ah, so you can connect over sftp, but your authentication setup isn't working.
[04:53] <wgrant> you need to have your Launchpad username in dput.cf, and your SSH key uploaded to Launchpad.
[04:54] <ista> but I have set my username
[04:54] <wgrant> What is your Launchpad username?
[04:54] <ista> kaelrenc
[04:55] <wgrant> Your Launchpad account doesn't have any SSH keys associated.
[04:55] <wgrant> https://help.launchpad.net/YourAccount/CreatingAnSSHKeyPair
[04:56] <ista> I'm sorry I don't remember that, thank you
[09:03] <ista> After uploading .deb packages, an email noted that Rejected: Source/binary(i.e.mixed)uploads are not allowed. Is there a clear difference between Source and Binary?
[09:03] <ista> dpkg-buildpackages -S OR dpkg-buildpackages -B?
[09:04] <cjwatson> Yes, pretty much
[09:04] <cjwatson> You must use -S for your uploads to Launchpad
[09:05] <ista> What's the details?
[09:06] <cjwatson> source uploads have "Architecture: source" in .changes and include a .dsc file and some other files referenced by it (original tarball, packaging)
[09:06] <cjwatson> binary uploads have machine architectures or "all" in the Architecture field in .changes and include binary packages such as .debs
[09:06] <cjwatson> mixed uploads are used in Debian but not in Ubuntu, and have some combination of both
[09:07] <ista> But I only want to build binary for amd64,
[09:08] <cjwatson> ista: You don't build the binary, Launchpad does (if you want it hosted on Launchpad)
[09:08] <cjwatson> ista: If you only want Launchpad to build your package for amd64, then put "Architecture: amd64" in debian/control in place of "Architecture: any"
[09:09] <cjwatson> But you still use dpkg-buildpackage -S
[09:09] <cjwatson> Launchpad does not accept *any* binary uploads from any entity other than its own builders.
[09:09] <ista> But why must run dpkg-buildpackages locally? It takes too much time
[09:09] <cjwatson> dpkg-buildpackage -S only builds the source package; it's usually quick
[09:10] <cjwatson> Unless the source package is gigantic
[09:10] <ista> Ah, If I dont't want to make a local .deb file, then I can simply run dpkg-buildpackages -S?
[09:11] <cjwatson> Yes
[09:11] <cjwatson> But it's spelled dpkg-buildpackage not dpkg-buildpackages
[09:12] <ista> sorry.
[09:12] <ista> get it.
[09:37] <ista> Another problem: launchpad.net sent build error
[09:38] <ista> here is the log: https://launchpadlibrarian.net/153368679/buildlog_ubuntu-precise-amd64.glib_2.39.0%2Bgit20131010-1_FAILEDTOBUILD.txt.gz
[09:39] <cjwatson> ista: That's an error in your packaging; missing Build-Depends: zlib1g-dev by the looks of it.
[09:39] <cjwatson> /usr/bin/ld: cannot find -lz
[09:40] <cjwatson> ista: There'll be several more.  Why not base your work on the existing glib2.0 source package in Ubuntu, rather than trying to reinvent the wheel?
[09:40] <cjwatson> It's usually not a good plan to repackage things from scratch.
[09:41] <ista> GLIB 2.36.0 or better is required. The latest version o
[09:42] <ista> glib v2.32 on ubuntu 12.04
[09:42] <cjwatson> ista: Sure, but why not simply backport the glib2.0 source package from raring or saucy?
[09:42] <cjwatson> ista: It'll be about a hundred times easier than trying to redo all the work yourself and then somehow keeping it reasonably compatible and not destroying your system when you try to install it
[09:43] <ista> use repositories of ubuntu raring?
[09:44] <cjwatson> ista: You can start by just downloading the source from raring or saucy, tweaking the version (say, add a new changelog entry with ~ppa1 appended to the version number), and uploading that to your PPA
[09:44] <cjwatson> It's possible that will fail but it will be a LOT easier to debug than hoping that dh_make will somehow duplicate the effort of many very experienced packagers over more than a decade
[09:45] <cjwatson> (It won't :-) )
[09:46] <ista> that should be much easier than build from scratch.
[09:47] <ista> good idea, I will have a try.
[15:58] <dsmythies> The revision date and time details seem to be based on the changelog entry and not on when the package import robot actually executed. Is there a way to determine when the import actually occurred and what upstream revision it imported?
[15:58] <dsmythies> Reference 1: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/ubuntu-docs/saucy/revision/113
[15:58] <dsmythies> Reference 2: https://code.launchpad.net/~ubuntu-branches/ubuntu/saucy/ubuntu-docs/saucy  (where rev 113 actually appeared on or about October 4th, not September 16th)
[15:58] <dsmythies> Reference 3: https://code.launchpad.net/~ubuntu-core-doc/ubuntu-docs/saucy  (where, as best as I can determine, rev 113 above seems to be based on upstream rev 274, but should have been rev 275)
[16:01] <cjwatson> You might need to ask #bzr for that
[16:03] <dsmythies> Oh... O.K. I'll go there.
[20:56] <bjf> is qastaging having issues? talking to it via the api just returns 403 errors
[23:30] <philsf> hello, I published code for two projects in lp, but in my innocence I used (bzr) tags to identify release versions. what is the best practice to track those in lp? do I need to branch at each version?