[07:21] -queuebot:#ubuntu-qt- Unapproved: pyqt5-sip (jammy-proposed/universe) [12.9.0-1 => 12.9.0-1build1] (i386-whitelist, kubuntu)
[07:27] -queuebot:#ubuntu-qt- Unapproved: accepted pyqt5-sip [source] (jammy-proposed) [12.9.0-1build1]


[01:17] <RAOF> 'Tis the season for SRU requests!
[01:22] <duflu> ... tra la la la la, la la la la?
[02:59] <duflu> Oh, pretty new raring wallpapers. I missed that.
[03:45] <RAOF> duflu: Oooh, yeah!
[03:46] <RAOF> robert_ancell: Fix it so that dynamic wallpapers work in unity-greeter, damnit :)
[03:46] <robert_ancell> RAOF, fix it yourself :)
[05:12] <darkxst> pitti, is a g-i update coming?
[05:15] <maxb> Does Totem count as 'desktop' or is there a more relevant place to talk about it? (I'm wondering if I should be making more noise about bug 1158594, as a regression in the default video player is fairly notable)
[05:15] <ubot2> Launchpad bug 1158594 in totem (Ubuntu) "Video is too yellow/bright, as if a grossly exaggerated gamma transform is applied (raring regression)" [Undecided,New] https://launchpad.net/bugs/1158594
[06:00] <pitti> Good morning
[06:00] <pitti> darkxst: yes, working on it; it needs glib 2.36.0, so that needs to build in Debian exp first
[06:14] <darkxst> pitti, ok np
[06:14] <mlankhorst> g'day
[06:15] <darkxst> pitti, another question, we currently patch gvfs to install the new goa modules, would there be some way we can incorparate this into the main archive? http://pastebin.com/2zckE7s1
[06:29] <pitti> darkxst: I'm not entirely sure; we certainly want that for Debian, though
[06:29] <pitti> darkxst: can we wait with this question until seb128 gets online?
[06:30] <darkxst> pitti, sure
[06:35] <pitti> darkxst: that doesn't need any additional build deps?
[06:35] <pitti> like libgoa-1.0-dev ?
[06:35] <darkxst> pitti, yes
[06:35] <pitti> darkxst: so that's not in your debdiff
[06:35] <darkxst> Pitti, sorry that was an old debdiff
[06:37] <pitti> darkxst: ah, I can apply it to Debian for now, debian has 3.7.91-1+b1
[06:38] <darkxst> pitti, ok this is the right one http://pastebin.com/PmBkKFWr
[06:38] <pitti> darkxst: http://paste.ubuntu.com/5651492/ ?
[06:39] <darkxst> pitti, yes looks good
[06:39] <pitti> darkxst: configure.ac checks for that version
[06:39] <pitti> ok, test-building
[06:39]  * pitti uploads g-i 1.36.0 to Debian exp, will sync in a few hours when it's imported into LP
[06:41] <darkxst> yes, I had the version check in there one stage, but lost it at some point
[06:48] <pitti> darkxst: builds fine, I committed that to the Debian packaging branch
[06:49] <pitti> we can't build that in Ubuntu yet as our goa version is too old
[06:49] <sarnold> anyone here have ops in #ubuntu-server? plan_1 probably needs a +q or +b
[06:50] <darkxst> yes I know that, but its painful trying to keep it up to date in the ppa.
[06:55] <darkxst> I guess I was kinda hoping we could either update goa, or put some if $GOA_VERSION magic so its just a rebuild required for each update
[07:10] <pitti> darkxst: I don't think it's a problem to update goa in raring, as we don't use it in the default desktop
[07:10] <pitti> we should coordinate that with seb128
[07:12] <darkxst> ok
[08:04] <jibel> good morning
[08:39] <seb128> hey desktopers
[08:42] <mlankhorst> g'daay
[09:33] <darkxst> seb128, hi, was talking to pitti before about updating goa
[09:33] <pitti> bonjour seb128
[09:33] <darkxst> and adding the new goa modules to gvfs
[09:38] <seb128> darkxst, pitti: hey
[09:38] <seb128> darkxst, I was pondering just dropping goa and building eds and co without it...
[09:39] <seb128> since we use uoa in Ubuntu
[09:39] <darkxst> seb128, we kinda need it though
[09:39] <seb128> or not
[09:39] <seb128> we have uoa
[09:39] <darkxst> seb128, as in ubuntu GNOME
[09:40] <pitti> "drop" would mean "drop build deps and move package to universe"?
[09:40] <darkxst> and re-patching gvfs everytime there is an update is a pain
[09:40] <seb128> pitti, yes
[09:40] <pitti> well, like that we now need to re-patch gvfs from debian on each update, and you need to re-re-patch it back to the Debian version
[09:41] <pitti> so for GNOME ubuntu it would be better to directly take the debian exp version
[09:41] <seb128> pitti, btw your gvfs update brings libsystemd-login0 in, is that wanted?
[09:41] <pitti> seb128: not deliberately
[09:42] <seb128> pitti, Debian added a build-depends on libsystemd-login-dev
[09:42] <pitti> (for raring, anyway)
[09:42] <seb128> pitti, which is in the version you used to do the 1.16 update
[09:43] <pitti> ah, it's used in the udisks2 monitor
[09:44] <pitti> it doesn't change behaviour if logind is not running, but if the extra depends is a problem I can take it out again
[09:44] <seb128> darkxst, pitti: in any case there is a limit of how much we can do GNOME without Ubuntu bits in Ubuntu, it's going to get harder and harder
[09:44] <pitti> seb128: actually, with ubuntu moving away from gnome piece by piece it should get easier again?
[09:44] <seb128> darkxst, pitti: like if apps like shotwell have a build-time option for goa or uoa we will build them with ubuntu online account, not goa
[09:44] <seb128> or you need 2 builds of shotwell with different flags/patch
[09:44] <seb128> it's a pain to start "forking" apps
[09:45] <seb128> shotwell as an example
[09:45] <seb128> going to be the same of e-d-s and other stuff
[09:46] <pitti> seb128: uploaded gvfs without the systemd-logind dep
[09:46] <darkxst> many of these things are dynamically loaded modules?
[09:46] <seb128> pitti, danke
[09:46] <pitti> seb128: so that you get your 24 kB back :)
[09:46] <seb128> darkxst, no, some are, but most software don't want that complexity
[09:47] <pitti> so it seems to me that dropping goa into universe, updating it to 3.7, and using it for ubuntu gnome only seems the right thing?
[09:47] <seb128> pitti, ;-) I was more unsure if that would have any side effect, I noticed because gvfs was on hold in my "upgrade"
[09:47] <pitti> seb128: no, it doesn't
[09:48] <seb128> pitti, don't you need libsoup 2.42 for goa 3.7?
[09:48] <pitti> peut-être, je ne sais pas
[09:48] <seb128> I think you do
[09:48]  * seb128 checks
[09:48] <seb128> libsoup-2.4 >= 2.41
[09:49] <seb128> yep, you do
[09:49] <seb128> too late to update that one in raring though
[09:49] <seb128> they went through quite some changes this cycle
[09:49] <seb128> like they dropped libsoup-gnome and merged the features in libsoup
[09:49] <seb128> and that impact on several components in the default installation
[09:50] <pitti> we can sort that out in sleazy, though
[09:50] <seb128> yeah
[09:50] <pitti> and raring will stay reasonably stable now, so ubuntu gnome should have little trouble
[09:50] <darkxst> gnome have a habit of breaking stuff post-freeze ;(
[10:10] <darkxst> pitti, seb128, what are the chances of landing the newly release spidermonkey and updated gjs in universe for raring?
[10:11] <seb128> darkxst, that was briefly discussed on the lists a few weeks ago, nobody seemed interested or picked it up, I guess it's late now
[10:11] <seb128> you can try asking for a FFe
[10:12] <darkxst> seb128, I know its late
[10:12] <darkxst> has taken about 4 months of prodding mozilla people and even patching their build systems to make it happen
[10:12] <seb128> I'm not fond of adding another version of a javascript engine without transitionning/replacing the old one
[10:13] <darkxst> seb128, except the benefits of the new engine for gnome-shell/gjs are huge
[10:13] <seb128> it's not like g-s was not working well atm
[10:13] <darkxst> seb128, its leaks like a sieve
[10:14] <darkxst> and there are regular deadlocks caused by GC
[10:14] <seb128> will teach them to write their shell in js? :p
[10:14] <seb128> joke aside, it's not my call
[10:14] <seb128> file a FFe if you feel strongly about it
[10:18] <darkxst> seb128, couchDB cannot transition to the new spidermonkey
[10:19] <seb128> darkxst, so we have an issue..
[10:19] <seb128> (if we still care about couchdb)
[10:19] <darkxst> they are using illegal JS syntax as a core feature of their user plugin system
[10:19] <darkxst> I don't really care about couchdb, but I presume others might
[10:20] <seb128> yeah
[10:20] <seb128> as said, not my call
[10:20] <seb128> file the FFe and see what they say
[10:20] <darkxst> ok will do
[10:20] <seb128> security might be fine with having 2 copies of libgjs in universe
[10:21] <darkxst> we don't need 2 copies of gjs
[10:21] <seb128> sorry, libmozjs
[10:21] <darkxst> the new gjs works perfectly with g-s 3.6
[10:21] <seb128> which is actually the security sensitive bit I guess
[10:22] <darkxst> I would have thought the security sensitive bit, is downloading random g-s extensions?
[10:22] <darkxst> i.e from outside the vetted code on e.g.o
[10:22] <seb128> you are speaking about gnome-shell there
[10:23] <seb128> not about having 2 copies of a javascript engine in the archive
[10:23] <seb128> which might each have security issues in their code
[10:24] <seb128> and might be used by random users/apps
[10:24] <seb128> ideally we would drop the old one and migrate to the new one and support only that one
[10:24] <seb128> but I don't see that happening for raring
[10:24] <seb128> especially that stuff like couchdb can't be easily ported as you said
[10:27] <darkxst> well I am no security expert, but that seems like the biggest weak point, its really not hard to get web folks to excute random shell command, and/or download from random ppa's etc.
[10:28] <darkxst> anyway will file a FFe
[10:40] <mhr3> xnox, ping?
[10:40] <xnox> mhr3: hola =)
[10:41] <mhr3> xnox, hey, you mentioned you'd be able to help us with s-c review and generating the indices, right?
[10:41] <xnox> mhr3: yes.
[10:41] <mhr3> (cc: jamesh) ^
[10:41] <mhr3> xnox, i think this will need some help and review - https://code.launchpad.net/~jamesh/archive-index/app-install
[10:42] <xnox> mhr3: I'm confused which branch it's based on....
[10:43] <mhr3> on the one mvo suggested
[10:43] <mhr3> afiar
[10:43] <xnox> yeah =) me got merge-proposal wrong way around.
[10:44] <mhr3> xnox, i see it just got mp-ed, so pls take a look at it, we'd need it asap
[10:45] <xnox> mhr3: yeah, looking.
[10:45] <xnox> mvo: I think I did last extraction the wrong way.... =(
[10:45] <mhr3> xnox, thx a lot! :)
[10:47] <xnox> mhr3: right, I'll generate new app-install-data, send it to a ppa or somewhere & then you will be able to test s-c. Do we already have scopes in the archive?
[10:47] <xnox> or do I need to scan the test ppa?
[10:47] <mhr3> xnox, you need the smart-scopes ppa
[10:47] <mhr3> https://launchpad.net/~ubuntu-unity/+archive/experimental-prevalidation
[10:48] <xnox> ack.
[10:55] <darkxst> seb128, I suspect I would bring down launchpad if I provide a debdiff of the new spidermonkey engine vs 185 ;) (as requested in ffe wiki
[10:57] <darkxst> hmm or I misread they want a diff of the non-existant upstream changelog
[10:57] <seb128> darkxst, the goal is to try to figure out what changed and how risky the changes are
[10:58] <darkxst> seb128, even the mozilla guys can't really keep track of what changed!
[10:58] <seb128> darkxst, doesn't speak good for your ffe...
[10:58] <seb128> that doesn't seem like the sort of change we want to see landing late
[10:59] <darkxst> 2 years is a long time!
[11:00] <seb128> right
[11:01] <darkxst> anyway, I guess we could just land it in the ppa, for now
[11:02] <darkxst> but the issue around having 2 seperate mozjs version will continue well into S
[11:03] <seb128> right, we need to decide if that's an issue or not
[11:07] <darkxst> seb128, ok, so how do we go about that ? this is going to likely be a continuing theme, with hopefully regular release from here on in
[11:07] <darkxst> i.e. mozjs24 in November will break, everything again
[11:08] <seb128> well, if we could keep only one or two versions at a time that would be good
[11:08] <seb128> we just need to figure out how we roll
[11:09] <darkxst> and I guess their is a catch 22 issue, most projects wont port to a version, until the distros carry it
[11:12] <seb128> would be easier if they had a forward compatibility story...
[11:12] <darkxst> although, on the plus side, once all the upstream patches filter down to the various releases, they should actually be esr point releases
[11:12] <seb128> but go GNOME for basing their shell on an abi unstable stack
[11:12] <darkxst> I pretty sure all this happened after the fact
[11:14] <darkxst> i.e mozilla abandoning any promise of ABI/API stability for the JS engine, all happened well after GNOME had already locking into their choice
[11:16] <darkxst> and actually porting gjs was not that bad, although the complete lack of documentation probably made it take 3x as long as it might have
[11:17] <darkxst> I have *spent* far more time, bugging mozilla for the release!
[11:27] <darkxst> anyway I can't really speak for the history of all of it, but my understanding is, that at the time gjs was far more mature than any of the alternatives
[11:28] <seb128> right
[11:28] <seb128> well, the bottom line is that the lower number of javascript engines we have to support the better
[11:28] <seb128> but I'm sure we can get the new version in
[11:29] <seb128> it's just really late for raring
[11:31] <darkxst>     things move slowly in mozilla land!
[11:32] <darkxst> the release was supposed to happen mid Feb after the patches landed
[11:32] <darkxst> and actually most of the patches havent even landed yet even though they are r+
[11:33] <darkxst> anyway regardless of all that, at the very least it would be good to have it there for S opening
[11:33] <darkxst> upstream have already switched to it for gjs master
[11:34] <darkxst> although I suppose that doesnt even matter, since ubuntu is now a cycle behind ;(
[11:37] <seb128> darkxst, right
[11:37] <darkxst> anyway I am now going to smash both my monitors since they keep turning off every 3secs, and then go to bed
[11:37] <seb128> darkxst, thanks for the work on that and sorry things are not easier to land
[11:39] <darkxst> seb128, I understand its way late in the cycle now.
[11:39] <seb128> darkxst, it's also that gnome-shell/gjs isn't our priority
[11:40] <seb128> so people will pay less attention to those
[11:40] <darkxst> seb128, well that I don't get, I mean obviously we would maintain the packages
[11:41] <seb128> darkxst, "we" being?
[11:41] <darkxst> seb128, ubuntu GNOME
[11:41] <darkxst> gnome3-team
[11:41] <seb128> darkxst, you are wanting to support security fixes for libmozjs and all its rdepends in the archive?
[11:41] <seb128> including couchdb etc
[11:42] <seb128> if you throw a javascript engine in the archive you can't claim it's for gnome-shell only
[11:42] <seb128> you need to proper support it and all its users
[11:42] <darkxst> hmm right, ok scrap that idea!
[11:42] <seb128> ;-)
[11:45] <darkxst> that said, I don;t see any security fixes in the 185 packaging
[11:45] <seb128> no, because mozilla probably doesn't do security work for standalone libmozjs
[11:45] <darkxst> so perhaps I just wait for mbiebl package it up, then we can sync it ;)
[11:45] <seb128> which is another good reason to try to limit the use of that lib
[11:46] <darkxst> seb128, they have point releases every 6 weeks in the esr branch, which are purely just security fixes
[11:47] <seb128> they do roll releases and ensure abi compat for those?
[11:48] <darkxst> they have promised to roll releases, once all the versioning stuff had landed
[11:48] <seb128> ok, let's see how that goes
[11:49] <darkxst> and abi compat should be assured, unless they really had to do something strange to fix the security issue
[11:49] <darkxst> seb128, I would guess more likely to start in 24 series
[11:49] <seb128> let's see
[11:50] <seb128> darkxst, thanks for the details
[11:50] <seb128> lunch time here
[11:50] <seb128> bbiab
[11:50] <darkxst> bed time here, cya
[13:07] <desrt> ughhhh
[13:10] <ogra_> desrt, bad day ?
[13:10] <desrt> sick :(
[13:10] <ogra_> uhh, go to bed
[13:18] <jcastro_> ah yes, finally, we can be free from the tyranny of atd
[13:19] <ogra_> lol
[13:19] <ogra_> did it attack you in your sleep and the like ?
[13:20] <jcastro_> no, just commenting on the thread on -devel about removing atd
[13:20] <ogra_> yeah
[13:20] <ogra_> i was just wondering about "tyranny" ... i mssed the irnoy tags i think
[13:20] <ogra_> *missed the irony
[13:22] <jcastro_> every time we remove something "UNIX" I feel a little bit of pride and happiness
[13:22] <jcastro_> I guess it's just me
[13:23] <seb128> jcastro_, you probably like systemd then ;-)
[13:23] <jcastro_> let's not get crazy
[13:23] <jcastro_> but I'm sure we can replace atd with systemd right?
[13:23] <desrt> yes.  it does that too.
[13:23] <desrt> of course.
[13:24] <desrt> if i get some time this weekend i'm going to rip out my sink in the kitchen
[13:24] <desrt> because, you know..... systemd now
[13:45] <ogra_> desrt, when does systemd grow an input layer and display server btw ?
[13:46] <ogra_> :)
[13:46] <desrt> ogra_: i give it another year, tops
[13:46] <seb128> lol, not friday guys!
[13:46] <desrt> maybe sooner if we release mir early =)
[13:46]  * ogra_ is sure its friday somewhere ... in a parallel universe :)
[13:51] <dobey> well bother. i just installed skype from software-center without any crashing. only problem was that the icon on the launcher never updated, so i thought it wasn't actually installing it
[13:52] <seb128> dobey, hey
[13:53] <seb128> dobey, I assigned you 2 s-c bugs that were ranking high on the errors tracker, I hope it's ok
[13:53] <seb128> dobey, let me know if you prefer those assigned to a team or tracked differently
[13:53] <dobey> oh, it seems all the reports are from 12.10
[13:57] <seb128> dobey, the bugs I assigned to you? should not, I did pick "13.04" as release on e.u.c
[13:57] <seb128> but maybe nobody reported them to launchpad from raring
[13:57] <dobey> well, there are no dups on launchpad it seems
[13:59] <dobey> but https://errors.ubuntu.com/bucket/?id=software-center%3Atrans-failed%3Aerror-dep-resolution-failed shows "Ubuntu 12.10" for almost all the errors from today and yesterday
[14:00] <dobey> also, the infinite scroll stuff is annoying as heck, because it's slow and causes the footer to constantly move down :)
[14:02] <dobey> "openswan: racoon: Depends: ipsec-tools (= 1:0.8.0-14ubuntu2) but 1:0.8.0-14ubuntu2 is to be installed"
[14:02] <dobey> lol wtf
[14:02] <dobey> that's the only one i've seen so far on 13.04 in that list, and that's on armhf
[14:03] <seb128> dobey, well, the bug might be the same on 12.10
[14:03] <dobey> i'm sure it is
[14:03] <seb128> dobey, the table shows 184 reports on 5.5.4, 91 on .5, 4+7 on .6
[14:04] <seb128> it's just that there is a magnitude less users on raring
[14:06] <dobey> but errors.ubuntu.com makes it hard for me to find useful data on it, because there are no dupes on lp, and the bug on lp only shows one of the failure cases, which when i tried, doesn't fail.
[14:08] <seb128> dobey, that's a side effect on a package being broken/not installable?
[14:12] <dobey> seb128: that specific crash seems to be, yes
[14:12] <seb128> ok
[14:13] <dobey> or at least, it's caused by install failure. i didn't go through all the error reports, but the ones i looked at were package not installable issues
[14:38] <seb128> desrt, did you have any distro specific systemd patch for "can-ntp" to work?
[14:39] <desrt> no
[14:39] <desrt> it's implemented the same way as it is upstream
[14:39] <desrt> and lennart took my patch into the new version of systemd (which already had a release)
[14:42] <seb128> desrt, we have 198 which includes it
[14:42] <seb128> desrt, I'm wondering why clicking on the property in d-feet doesn't give me a value
[14:42] <seb128> desrt, or rather I'm trying to figure why I can't select "time from internet" in the indicator-datetime g-c-c panel
[14:46] <chrisccoulson> awesome,
[14:46] <chrisccoulson> /dev/sda2       454G  5.3G  426G   2% /
[14:46] <chrisccoulson> \o/
[14:48] <seb128> nice
[14:48]  * seb128 wants
[14:51] <chrisccoulson> heh
[14:51] <chrisccoulson> seb128,
[14:51] <chrisccoulson> Mem:         15924       5131      10792          0        161       3845
[14:51] <chrisccoulson> ;)
[14:51] <seb128> chrisccoulson, make sure to watch your laptop at the next rally :p
[14:51] <chrisccoulson> hah
[14:53] <seb128> chrisccoulson, I guess it's nice and smooth, especially with a new install ;-)
[14:53] <chrisccoulson> seb128, yeah, it's running quite slick
[15:04] <desrt> seb128: hmmm.
[15:04] <desrt> seb128: are you sure timedated got restarted properly after the upgrade?
[15:05] <desrt> i did some testing of the old systemd with our vendor patch against our datetime panel
[15:05] <desrt> and also did some testing of the new patch against fedora with upstream gnome panel
[15:05] <desrt> in both cases it properly detected the availability of ntp
[15:06] <desrt> and fwiw, the 'time from internet' option in the panel is only disabled when the property exists _and_ is false
[15:06] <desrt> so a missing property would not cause it to be greyed out
[15:07]  * desrt updates his raring
[15:09] <desrt> is there a command that essentially produces the output of for i in `dpkg -l | cut whatever`; do apt-cache policy $i | grep '**'; done, but also with the package name in question on the same line?
[15:10] <seb128> desrt, we have the new systemd/timedated for some days and I reboot every morning
[15:10] <seb128> desrt, what are you to do with that command? see if you are using ppa versions?
[15:11] <desrt> ya.  exactly :)
[15:12] <desrt> that_command | grep ppa... would be great
[15:13] <seb128> desrt, dpkg -l | grep ~
[15:13] <seb128> if ppas are not crazy they use a version with ~
[15:14] <desrt> my ppa is often crazy :)
[15:14] <desrt> plus... the distro often uses those versions too
[15:19] <seb128> desrt, we don't record the source of the packages
[15:19] <seb128> desrt, if you use the same version as the archive no tools will be able to tell you where you got the installed one
[15:21] <desrt> huh
[15:22] <desrt> then how does apt know to reinstall the archive version over top of he same version that i build locally?
[15:22] <seb128> desrt, so I guess you are saying it works for you?
[15:22] <desrt> seb128: it worked when i tested.  i'm updating everything so i can test again.
[15:22] <seb128> desrt, does it reinstall versions? could be luck or md5sum
[15:22] <seb128> but the md5 just tell you that your version is not the archive one
[15:23] <seb128> not where it's coming from
[15:33] <seb128> desrt, let me know if you get the bug/or not and if I can help testing
[15:37] <desrt> seb128: what is the bug, specifically?  'automatically update time from internet' is greyed?
[15:37] <desrt> in current raring?
[15:37] <seb128> desrt, yes
[15:43] <desrt> seb128: seeing the issue.  will investigate.
[15:45] <seb128> desrt,
[15:45] <seb128> $ dbus-send --print-reply --system --dest="org.freedesktop.timedate1" /org/freedesktop/timedate1 org.freedesktop.DBus.Properties.Get string:"org.freedesktop.timedate1" string:"CanNTP"
[15:45] <seb128> method return sender=:1.546 -> dest=:1.561 reply_serial=2
[15:45] <seb128>    variant       boolean false
[15:45] <desrt> seb128: interesting.  looks like upstream changed behaviour in timedated
[15:45] <seb128>
[15:45] <seb128> ah
[15:45] <desrt> it looks for ntp implementations by searching in /etc/systemd/ntp-units.d
[15:45] <desrt> this allows you to have ntpd vs. chrony, for example
[15:45] <ogra_> ohmy
[15:46] <desrt> it used to default to 'ntpd.service' if none was found
[15:47] <desrt> seems that the new version no longer has the default, so if we have no files there, it assume we have no ntp implementation
[15:48] <desrt> i'll have systemd-shim install a file and that ought to fix it
[15:50] <desrt> oh good... it allows an alternate path in /usr/lib as well
[15:50]  * desrt hates having crap in /etc by defaul
[15:59] <xnox> seb128: is there qt/kde messaging-menu for KDE plasma available? cause libindicate works on KDE upstream release, but I can't seem to find the messaging-menu port for kde.
[15:59] <seb128> not that I know
[15:59] <seb128> larsu, ^
[16:00] <xnox> seb128: i ported a few things to messaging-menu & dropped pointless build-deps on linindicate from things that were ported. Thus reverse-depends src:libindicate is getting very small.
[16:00] <seb128> good
[16:11] <larsu> xnox: thanks! There are no qt bindings yet as far as I know...
[16:15] <xnox> larsu: so only messaging-menu apps work on Unity/Gnome desktop && only libindicate apps work on KDE desktop. \o/
[16:15] <xnox> .... wait /o\
[16:49] <marga> desrt, you around?
[16:49] <marga> desrt, I'm being pestered by this SIGBUS error :(
[16:50] <marga> I don't know what but something must have changed recently to start causing this more and more.
[16:51] <marga> Maybe there was an update to gnome-screensaver that makes it want to read dconf values while the screen is locked or something like that.
[16:52] <marga> Anyway, I'm going to try to find a way of catching the SIGBUS thing, that you already told me was not easy at all, so I'd appreciate any help.
[16:53] <seb128> marga, hey, re your -data missing package issue, the arch all binaries are built on i386 and only listed in the debs resulting from the build on that arch
[16:54] <seb128> if you went in the launchpad ui to download the debs
[16:54] <marga> seb128, yes, I figured it out eventually, but was very confused for a while :)
[16:54] <seb128> it can be confusing indeed
[16:54] <marga> I was particularly confused about the package not being in the build-log
[16:55] <marga> Now it makes sense, thanks.
[16:56] <seb128> marga, yw
[17:02] <desrt> marga: :(
[17:03] <desrt> marga: all i can say is that this is fixed in raring :/
[17:03] <desrt> and it's not easily backportable
[17:04] <pitti> cyphermox: some initial working testcases for wpa_supplicant, FYI: http://people.canonical.com/~pitti/tmp/networktest.py
[17:08] <pitti> happy Easter holidays everyone! I'll be back next Wednesday, off IRC; I'll read email sporadically
[17:11] <desrt> seb128: so i can fix this issue fairly easily, but there is a bit of a packaging issue
[17:11] <seb128> desrt, oh?
[17:13] <desrt> seb128: systemd services (timedated) will look in /usr/lib for the ntp unit files... but you setup the libdir of systemd-shim for multiarch
[17:13] <seb128> I don't set up anything, debhelper does that
[17:13] <seb128> it's easy enough to override the configure call to use the correct --libdir=
[17:13] <seb128> I will put it back to /usr/lib
[17:14] <desrt> i could also just hardcode the install path for the unit file
[17:14] <desrt> since according to the documentation it uses a fixed path
[17:14] <desrt> so installing to a fixed path probably makes sense
[17:14] <desrt> namely  /usr/lib/systemd/ntp-units.d/
[17:14] <seb128> desrt, wfm
[17:14] <desrt> k
[17:15] <desrt> i'll do a new systemd-shim soon
[17:15] <desrt> thanks for the catch... as i said, i tried the patch with fedora and new systemd and ubuntu and old systemd... not the new systemd on ubuntu :)
[17:19] <seb128> yw ;-)
[17:24] <desrt> seb128: is my installing files into /usr/lib directly going to cause trouble to your multiarch stuff?
[17:24] <desrt> like some failed lintian check or so...
[17:24]  * desrt updates the packaging for himself to see
[17:26] <seb128> desrt, no
[17:27] <seb128> the packaging doesn't care about the destination
[17:28] <seb128> it cares about files that are make installed and not in any binary
[17:33] <desrt> seb128: amd64 these days?
[17:33] <desrt> can you take http://people.gnome.org/~ryanl/systemd-shim_2-0ubuntu1_amd64.deb for a spin?
[17:34] <desrt> (hint: make sure you restart systemd-timedated)
[17:34] <marga> desrt, you told me that the fix did not fix the home going MIA.
[17:34] <marga> desrt, does it?
[17:34] <desrt> marga: stops the SIGBUS
[17:34] <marga> how?
[17:35] <desrt> because it stops the use of mmap for touching the homedir
[17:35] <desrt> and maps out of the xdg runtime dir instead
[17:35] <seb128> desrt, no, i386
[17:35] <desrt> my concerns about it not being completely fixed is that the daemon may still misbehave a bit if it tries to do an update and it finds it can't access ~
[17:35] <desrt> seb128: damn :p
[17:35] <seb128> desrt, just give me the tarball/source, I will give it a try in half an hour
[17:35] <seb128> need to run out for a bit
[17:35] <desrt> okay
[17:36] <seb128> thanks
[17:36] <desrt> i'm getting lars to check
[17:36] <desrt> he have amd64
[17:39] <marga> desrt, and you say it's very hard to backport this to precise?
[17:39] <desrt> yes
[17:39] <desrt> dconf underwent quite a lot of changes to make this possible
[17:39] <marga> uhm...
[17:40] <desrt> a backport would basically look like an SRU of the new package
[17:40] <desrt> and it wouldn't even help you that much because the new code uses a keyfile for settings on nfs, as i mentioned before
[17:40] <desrt> so you'd have this backcompat issue
[17:40] <marga> right
[17:41] <marga> well, I'll take a look at the new code tomorrow (I'm too jetlagged today to do anything that requires my brain to actually think), see how a patch to fix the mmap would look without changing the rest.
[17:42] <desrt> seb128: larsu confirms it works... i'll do a new upstream release now
[17:43] <desrt> marga: you'll have to write new code
[17:43] <desrt> the way the old system works: each app directly mmaps ~/.config/dconf/user
[17:43] <desrt> so when the NFS homedir goes away, every process is in danger of SIGBUS
[17:44] <desrt> the way the new system works: dconf-service creates a file in /run/user/desrt/dconf/user and every process maps that
[17:44] <desrt> then dconf-service keeps /run/user/desrt/dconf/user in sync with ~/.config/dconf/user.txt
[17:44] <marga> right
[17:44] <desrt> using normal Posix IO (no mmap over NFS)
[17:44] <desrt> but user.txt is a keyfile
[17:45] <desrt> so you'd need new code to keep it in sync instead with ~/.config/dconf/user which is a dconf-format database
[17:45] <marga> ok
[17:45] <marga> That sounds alright
[17:45] <desrt> if you did that and wanted to submit the patch upstream i'd be happy to consider it
[17:45] <marga> I consider myself capable of doing that
[17:45] <desrt> because i think this feature makes sense for people in your situation
[17:45] <marga> (although not today :)
[17:45] <desrt> it shouldn't be _too_ hard either
[17:45] <marga> Sure, doesn't sound too hard
[17:45] <desrt> because there are tools for reading/writing dconf databsaes to DConfChangesets
[17:46] <desrt> and a function for diffing and merging DConfChangesets
[17:46] <marga> Ok, great. I will take a look at it tomorrow and ask for help in case I get stuck.
[17:46] <marga> Thanks!!
[17:46] <desrt> documentation is not great, but you could look at the keyfile backend for some help
[17:46] <desrt> and ping me, of course
[17:49] <desrt> seb128: k.  new version is 'released'
[17:49] <desrt> in the usual place
[18:20] <seb128> desrt, ok, thanks
[18:21] <desrt> sorry for the wasted time
[18:22] <seb128> no worry, I didn't spend a lot of time on it before checking with you ;-)
[18:23]  * desrt wants to die
[18:57] <desrt> seb128: attente's computer is making a strange noise
[18:57] <desrt> i wonder if you can help with that
[18:58] <desrt> it's like chunkchunk CLICK
[18:58] <desrt> chunkchunk CLICK
[18:58] <desrt> chunkchunk CLICK
[18:58] <ogra_> harddisk failure ?
[18:58] <ogra_> check dmesg
[18:59] <desrt> i think it's because he dropped a patch from debian/patches/series and now he needs to refresh the entire stack on top of it
[18:59] <desrt> which he elects to do manually
[18:59] <desrt> chunkchunk CLICK
[18:59] <desrt> is there some (single) command to do that to all the patches?
[18:59] <ogra_> oh, developer failure ?
[19:00] <ogra_> :)
[19:00] <desrt> ya... noise is coming from the keyboard
[19:00] <ogra_> vim macros FTW :)
[19:00] <desrt> pretty ure chunkchunk CLICK is 'up, up, enter'
[19:00] <desrt> ogra_: it's at the shell
[19:00] <ogra_> then its even easier ... shellscript :)
[19:00] <desrt> it's like push patch, refresh, push patch, refresh, push patch, refresh
[19:01] <ogra_> do one a day and stay healthy
[19:01] <desrt> that's good advice
[19:16] <xnox> seb128: about generating updated app-data. I didn't manage to finish it today, it's tricky as they are not in the main archive - so i mirrored the ppa locally hacked up together Contents files for them and will regenerate app-installa-data and merge the ppa's scopes with ubuntu main archive data. Then the resulting package can be uploaded into the ppa to aid testing (e.g. enable one ppa and everything should work, including app-data & s-c)
[19:44] <seb128> desrt, (back from dinner), yeah, no built-in way to do that, I do to do "quilt push; quilt refresh" and go up-enter-up-enter
[19:45] <attente> haha
[19:48] <seb128> you can probably do "for name in debian/patches/*; do quilt push;quilt refresh; done
[19:48] <attente> it might count the series file
[19:49] <attente> hrm, i guess that doesn't matter though since overdoing it still works
[19:54] <seb128> right
[19:56] <ogra_> for i in $(cat debian/patches/series): ....
[20:01] <xclaesse> is it new that live search in nautilus search in subdirs recursively?
[20:02] <xclaesse> I don't think it was doing that a few days ago, on rarin
[20:03] <seb128> xclaesse, I backported some patches from 3.8 to re-enable it
[20:04] <seb128> xclaesse, https://launchpad.net/ubuntu/+source/nautilus/1:3.6.3-0ubuntu12
[20:04] <seb128> desrt, ogra_, attente: http://raphaelhertzog.com/2012/08/08/how-to-use-quilt-to-manage-patches-in-debian-packages/ recommends "while quilt push; do quilt refresh; done" ;-)
[20:04] <seb128> but yeah, it sucks that for a such common thing we don't have a command
[20:04] <xclaesse> seb128, hmm
[20:04] <seb128> everyone is having a custom command to run
[20:05] <xclaesse> seb128, I though that was a brillant idea from ubuntu to disable it
[20:05] <seb128> xclaesse, you liked better when it was not doing it?
[20:05] <xclaesse> with all my git checkouts, nautilus is just useless now
[20:05] <xclaesse> it freeze when I type something
[20:05] <seb128> well
[20:05] <seb128> that's only search
[20:05] <xclaesse> that' something I do all the time
[20:05] <seb128> stop doing it? ;-)
[20:06] <seb128> can't you just do typeahead?
[20:06] <seb128> e.g type what you need, without doing ctrl-f first
[20:06]  * xclaesse will backport nautilus 3.4, I really can't work with 3.6 :(
[20:06] <xclaesse> seb128, typeahead is what I do
[20:06] <xclaesse> but it recurse
[20:07] <seb128> oh, right, I didn't notice that
[20:07] <seb128> not so nice indeed :-(
[20:07] <seb128> I'm not fond of > 3.4 either
[20:07] <seb128> we should perhaps add back the old in the archive as a different package
[20:08] <mterry> Sweetsha1k, since when is liblangtag in libreoffice?  This isn't one of those packages you fold in for a quick release before splitting off?  ;)
[20:09] <xclaesse> seb128, if I can apt-get install nautilus-3.4 I will pay you a beer next time :D
[20:09] <seb128> xclaesse, ;-)
[21:41] <mokgable> need help with Realtek RTL8188CE wireless network card, in and out reception
[21:41] <mokgable> im using 12.04


[04:18] <guiverc> Bashing-om, does the Canonical releases Ubuntu 23.04 read okay to you?  I don't like second sentence today (sorry I'm so late)
[04:19] <guiverc> maybe "Along with details of the product, we're given links so we can download it"
[04:26] <Bashing-om> guiverc: I look again - :D
[04:29] <Bashing-om> guiverc: Agreed - does not read the best - lemme see what I can do with it.
[04:29] <guiverc> focal updates 'felt' short to me, but I see nothing wrong on a quick check
[04:30] <guiverc> looks good Bashing-om ; that ^ sentence is all that stood out to me (i explore my 'feeling' & see nothing wrong with that)
[04:31] <Bashing-om> guiverc: How about we make it as " We are given details of this production, ..."
[04:33] <guiverc> why production?  details of this product?  (or products given server/desktop etc.. production I'd need time with..)
[04:34] <guiverc> what you reackon.. the current sentence is 'awkward'.
[04:37] <guiverc> s/whatever/what ^   (my brain at times....)
[04:37] <Bashing-om> I reckon "we're given links" addition is the better.
[04:41] <Bashing-om> guiverc: Wiki not letting me log in - may take me a bit to finagle my way in again to make the edit :(
[04:41] <guiverc> what was the sentence you were going to use?  I can probably change it.
[04:49] <Bashing-om> guiverc: What you suggest works well - I am in and will edit/save; see what you then think :)
[04:53] <Bashing-om> guiverc: OK see now - addded to the list also.
[04:57] <guiverc> yep I'm happy; though not sure what you meant by 'added to the list'  (if it was that item, I can't recall what was there & my screen isn't long enough for it all to fit; on review my print size is larger than normal)
[04:59] <Bashing-om> guiverc: Made it now "  We're told of some improved security, the new app store, support for Raspberry Pi 5 and SiFive HiFive Pro P500 devices, network configuration, and a refreshed Docker."
[05:00] <guiverc> okay & thanks... yep looks good.
[05:01] <Bashing-om> guiverc: :D -- Logging out of WIKI - we call issue809 as bedded - ready to go :D
[05:02] <guiverc> yep... did quick scan of whole page & looks good to me.  thanks Bashing-om
[05:02] <guiverc> sorry I was so late in review
[05:05] <Bashing-om> guiverc: Had my difficulties getting the issue together - was rather late. Still a few oops that krytarik caught.
[05:06] <guiverc> :)   we get there in the end.
[05:14] <Bashing-om> \o/
[18:26] -ubottu:#ubuntu-news- ::omg!ubuntu:: Ubuntu 23.10 Available to Download Again (Translations Issue Resolved) @ https://www.omgubuntu.co.uk/2023/10/ubuntu-23-10-available-to-download-again-translations-issue-resolved
[19:09] <Bashing-om> UWN: I propose we include the latest articles on the resolution of that malicious translation incident.
[19:13] <krytarik> Bashing-om: Yeah, I'd agree here.
[19:23] <Bashing-om> krytarik: Saving - "WIP" also pulled.
[19:54] <Bashing-om> UWN: Saved and will start the push soonest.
[20:05] <Bashing-om> UWM: M/L is away - Post to the Forums next.
[20:16] <Bashing-om> UWN: Forums posting done - doing Discourse next.
[20:55] <Bashing-om> UWN: Discourse posting done - Re-directs next.
[21:33] -ubottu:#ubuntu-news- ::omg!ubuntu:: How to Install GreenWithEnvy on Ubuntu (NVIDIA GPU Tool) @ https://www.omgubuntu.co.uk/2023/10/greenwithenvy-ubuntu-install-nvidia-gpu
[21:34] <Bashing-om> UWN: re-direects completed - Making up a Mastodon blog next.
[21:54] <Bashing-om> UWN: Blogged Mastodon - Pending now is release to the other Social Media platforms.
[22:11] <guiverc> wow, sorry I'd forgotten it's Tuesday.. will go get my 'cup of tea' & start on return.
[22:26] <guiverc> malicous & skystartrek links changed (fridge)
[22:26] <guiverc> https://fridge.ubuntu.com/2023/10/16/ubuntu-weekly-newsletter-issue-809/
[22:27] <Bashing-om> guiverc: :D ^ ,,, I had  rude before daylight start to my day - tough to get back into my normal routine.
[22:29] <guiverc> fyi. i noted both budgie & ubuntu desktop are marked 'ready'... mantic release will complete soon (i hope)
[22:30] <Bashing-om> Fridge: Spot check and all looks good.
[22:30] <guiverc> thanks Bashing-om (I'll heart your discourse when I get to it; so far I've only 'stolen' the URL)
[22:31] <Bashing-om> guiverc: Tine is on our side - I too still trying to catch up :P
[22:31] <Bashing-om> time*
[22:39] <guiverc> posted uwn 809 to twitter, telegram (mewe)
[22:40] <guiverc> I like (just noticed) the update on ISOs available for desktop & ubuntu-budgie; thanks Bashing-om
[22:42] <guiverc> also discovered https://lists.ubuntu.com/archives/ubuntu-announce/2023-October/000296.html   will ready it for fridge next 30 mins probably
[22:44] <Bashing-om> guiverc: Was worth breaking protocol in this case /// Speaking of protocol - FaceBook; we still want the URL in the Subscriber section ?
[22:47] <guiverc> I was considering going & looking for a new (cheap) phone today.. (again; 2fa for fb).. but i do like not having phone ringing so it's not high priority (if I run short of time, it rains I'll not go etc)  maybe wait a day or two..
[22:50] <Bashing-om> guiverc: I have seen no flak from our readership in missing Facebook releases - So guess still not an issue if we can not post to FB ?
[22:52] <Bashing-om> And NO!  I am not going to be burdened with a cell phone !
[22:53] <guiverc> the more readership the better, krytarik noted fb gets views, so i suspect better with it than without.  My phone is still ~useful; alas can't receive texts (2fa) or phone calls (nice!)
[23:09] <krytarik> It just occurred to me.. did Wild Man anytime recently contribute to the newsletter still?  This is wrt the contributor list, which we've kept stale for a while now.  Also, the idea of us still posting to what's now become X makes me shudder. >_>
[23:10]  * guiverc has no issues with dropping twitter  (i don't care; sorry I won't call it not-y)
[23:12] <krytarik> I just noticed one cannot even view pages there anymore without being logged in?
[23:20] <guiverc> i believe that's the case.. i don't use it
[23:27] <guiverc> krytarik, ubuntu 23.10 on fridge is ready for review; I think good (all done locally in mousepad; just pasted to fridge)
[23:29] <guiverc> sorry; one link is still not showing (i forgot to fix)
[23:29] <krytarik> Alright, I'll go log in..
[23:30] <guiverc> i'll edit & repaste ; give me a few secs
[23:30] <Bashing-om> guiverc: Clear now to wipe our evidence ?
[23:30] <guiverc> yep scrub away Bashing-om
[23:31] <guiverc> all good for review krytarik
[23:31] <Bashing-om> doing ^
[23:35] <krytarik> guiverc: Lgtm!
[23:36] <guiverc> thanks krytarik
[23:36] <guiverc> https://fridge.ubuntu.com/2023/10/16/ubuntu-23-10-mantic-minotaur-released/
[23:42] <Bashing-om> Ouch! I Have been kicked from Google Docs ! >> " We're sorry. You can't access this item because it is in violation of our Terms of Service." / What now to do ?
[23:43] <krytarik> Hah, that doesn't sound good indeed.. >_<
[23:44] <guiverc> yeah I'm getting the same... we'll maybe have to work elsewhere..  I think Nathan was the owner & maybe required to fix (as in fight with oogle) that one.
[23:47] <krytarik> Another option would be to continue as thought out and move to using Discourse as the primary platform including the preparation work.
[23:49] <guiverc> discourse fine by me.. the fridge script creates from wiki index; do we put on wiki? or can fridge detail be gained easily from discourse?
[23:50] <guiverc> on discourse (warts and all) may be appreciated by folks; faster to note, we may get more contribs etc
[23:51] <krytarik> I don't remember creating a Discourse variant of the Fridge script earlier, but if we do switch to Discourse as the primary platform then we'd stop posting to the wiki too.
[23:53] <guiverc> the fridge script I think was very reliant on wiki indexing; that would need to be an all new script i suspect


[00:14] <valorie> KDE-ubuntu: you can install kubuntu-desktop or KDE-full or whatever, but unless you login to the Kubuntu session, you'll still be in Ubuntu Studio
[00:15] <valorie> however, depending on sofware versions, this might result in a bit of a mish-mash of applications and so forth
[00:16] <valorie> and you might have to fiddle to keep lightdm as your bootloader, since Kubuntu provides SDDM
[00:16] <valorie> instead
[00:16] <KDE-ubuntu> lightdm and SDDM is a login manager, not a boot loader
[00:16] <KDE-ubuntu> grub is a boot loader, or lilo
[00:17] <KDE-ubuntu> is it somehow the login manager conected / linked to the boot splash?
[00:18] <KDE-ubuntu> do I need to add ppa in Xenial Xerus 16.04.3 LTS for KDE-meta, or it just fine to search kde plasma and install everything?
[00:18] <KDE-ubuntu> if it breaks..., uhm well, it will break and I will reinstall the os
[01:47] <user|45301> hello
[07:10] <lordievader> Good morning
[10:34] <user|79523> how to upgrade from kubuntu 16.04 to 17.10
[10:35] <lordievader> You must first upgrade to 16.10, then you can upgrade to 17.04, and then finally you can upgrade to 17.10. Reinstalling directly to 17.10 is probably easier.
[11:58] <BluesKaj> Hey folks
[12:02] <someone_> Hi
[12:04] <someone_> anyone?
[12:04] <someone_> I have downloaded kubntu 17.10 through torrent but after I checked from sha265sum of the file it is not the same as on kubuntu's website , why ?
[12:05] <BluesKaj> where did you download it from?
[12:06] <someone_> I downloaded torrent file from kubuntu website
[12:09] <BluesKaj> try the md5
[12:10] <someone_> but kubuntu website does not contain md5
[12:10] <someone_> https://kubuntu.org/alternative-downloads
[12:11] <BluesKaj> why the alternative?
[12:13] <someone_> this is the page that I downloaded the torrent file from it .
[12:19] <someone_> as I know if I downloaded a file by torrent the hash should be as the orginal file without problems , but I don't what is this weird problem, Is that mean some hacking happened on kubuntu torrent file ?
[12:19] <lordievader> Or, the hash is outdated.
[12:20] <lordievader> someone_: Does it match http://cdimage.ubuntu.com/kubuntu/releases/17.10/release/SHA256SUMS
[12:21] <someone_> lordievader No
[12:22] <someone_> This is my sha265 of my file that I have:
[12:22] <someone_> fc2b000346117b644d19277d8d6546fbf6d244651230cc5d3074aaadc5b25465  kubuntu-17.10-desktop-amd64.iso
[12:24] <someone_> Could anyone download "kubuntu-17.10-desktop-amd64.iso" from torrent file which on this page https://kubuntu.org/alternative-downloads and check from what I say ?
[12:25] <BluesKaj> whynot just try it yourself to see if itworks rather than asking others to download it
[12:28] <someone_> BluesKaj  try what ? after I downloaded kubuntu 17.10 from that page I did not get the same sha265 hash as on kubuntu website
[12:30] <someone_> Is not this a weird problem ? Does not that mean that torrent file has been corrupted or something happened to it?
[12:32] <BluesKaj> difficult to know without trying it out
[12:35] <someone_> BluesKaj Ok try it , if you have a fast internet connection you could do that within two minutes.
[12:37] <someone_> Anyone download "kubuntu-17.10-desktop-amd64.iso" from torrent file which on this page https://kubuntu.org/alternative-downloads and checking from sha256 hash if it the same as on the page or not ?
[12:37] <BluesKaj> I don't have a fast connection here in the boonies
[12:38] <nameless> someone_: yes, it's the same
[12:38] <someone_> really , did you tried?
[12:38] <nameless> really
[12:42] <someone_> nameless Did you downloaded the torrent file which is on that page and checked from the sha256 ? Did you did that ?
[12:44] <someone_> Is there any kubuntu developer here ?
[12:45] <lordievader> someone_: They usually hang out in #kubuntu-devel
[12:46] <someone_> Ok , thanks
[12:49] <nameless> someone_: read my lips. i did that.
[12:49] <someone_> so, What is the explain to what happened with me ?
[12:50] <nameless> delete the iso file and restart the torrent
[12:51] <someone_> ok
[12:52] <nameless> better still, download the torrent file again too
[13:15] <someone_> The problem has been solved , Thank you .
[16:11] <agiorg_> ciao
[16:11] <agiorg_> !list
 Is the MySQLD service present in a typical installation with Kubuntu or do I have it installed without wanting to? Thank you.
 @IMR3D, Hello, it should be already installed since akonadi uses it
 I'm sorry, but I tested this system with exactly the same applications, configurations that I had in Linux Mint KDE (latest versions of both), but, Kubuntu, with prolonged use, has serious performance problems and with the administration of RAM ( I have 7 gigas). The same conditions and tests, but very different results.


[05:53] <kalstabakken> Can someone please set Bug #822071 to 'Wishlist'? Thanks.
[12:32] <pedro_> bdmurray, thanks for fixing the firefox-lp-improvements! you rock!
[15:04] <hggdh> bug 822071
[15:34] <bulldog98> can someone mark bug #773183 as won’t fix, since java-sun won’t be in supported anymore
[16:18] <micahg> bulldog98: that's not clear in Ubuntu yet
[16:19] <bulldog98> micahg: ah ok
[16:19] <micahg> bulldog98: and regardless, the same bug might apply to openjdk, just that the user had sun-java installed
[16:20] <bulldog98> yeah could be
[16:58] <pedro_> QA Meeting at #ubuntu-meeting in ~2 mins
[19:26] <om26er> who opens release specific bugs ?
[19:27] <bdmurray> om26er: what do you mean?  who has the permissions to open release tasks?
[19:28] <om26er> bdmurray, like when we nominate a bug for SRU a task is opened for Natty so who can do that? *which team*
[19:28] <bdmurray> bug control can nominate to a release of ubuntu
[19:29] <bdmurray> who can approve nominations is a combination of ubuntu-release and ubuntu-dev for the component the package is in
[19:30] <bdmurray> om26er: does that help?
[19:30] <om26er> bdmurray, yep understood ;)


[09:07] <elichai2> is it possible to write on the repo line `testing` instead of `yakkety`?
[09:07] <elichai2> (so i'll always stay on the testing version)
[09:10] <k1l> no


[17:49] <tomahawk_> i need exorcism and Japan depatsy.  those darn boogers eat my soul products. you have pena ?  i have new one.  you want me to math no error.  thanking you. Glino/Meitzu
[17:49] <tomahawk_> Gilno


[01:02] <broder> has anybody else noticed issues with gpg verification when pushing to a ppa? i keep getting a "general error"
[01:03] <broder> ...apparently those errors are a soft failure. never mind, then
[01:49] <Laney> many, many people
[01:49] <Laney> :-(
[07:14] <tumbleweed> genjix: HERE!
[07:31] <nigelb> tumbleweed: Home already?
[07:35] <tumbleweed> nigelb: not quite
[07:35] <tumbleweed> but back in ZA
[07:35] <nigelb> tumbleweed: cool! :)
[13:33] <detly> is there a pasteboard you use for this channel? Pocoo's seems to be down
[13:43] <detly> I'm trying to upload my source package to RabbitVCS' PPA, but I keep getting this error from dupload: http://pastebin.com/HwjgUKHs
[13:44] <detly> I built using "debuild -S" and signed the package correctly (AFAIK), and launchpad has the key I'm using
[13:45] <genjix> hi
[13:45] <genjix> i keep getting this message:
[13:45] <genjix> The key 515927FAC03CDBA5B659C62790F8E860C21EA5BC has already been imported.
[13:45] <genjix> https://launchpad.net/~genjix
[13:48] <maco> So stop re-importing it?
[13:49] <genjix> it isn't imported. look at my page
[13:49] <genjix> "No OpenPGP keys registered."
[13:50] <detly> also, it doesn't seem to matter what I type in when dupload asks me for my FTP password
[13:51] <maco> Detly: ignore the error. It does that for everybody
[13:52] <maco> Any reason you're using dupload instead of dput? dput doesn't require a password
[13:52] <detly> maco: just what I've always used, I can't remember why
[13:53] <detly> I should probably set up dput
[13:54] <maco> If that's the error I think it is, it's one that happens frequently but is lying. If the package is actually rejected I think you should get an email.
[13:55] <genjix> so launchpad is fucked. it is impossible for it to accept my gpg key.
[13:56] <detly> maco: okay, I'll await an email either way (I get one whether it's accepted or rejected)
[13:56] <maco> I wonder if it's possible your key clashes with someone else's. I have no idea if lp would catch that
[13:57] <genjix> well i had an old account, but i deleted the key on there
[13:57] <genjix> however it doesn't seem to have actually deleted the key, just claims it has
[14:00] <genjix> aha i can merge my old account. nice
[14:18] <detly> it looks like dupload doesn't work at all with launchpad anymore — now that I'm uploading with dput, I'm actually getting emails, and I wasn't before
[14:24] <genjix> if i upload A then B then C
[14:25] <genjix> will they be built in that order?
[14:46] <Renegade15> good day
[14:46] <Renegade15> once more, I have returned to inquire about the XML bug import format
[14:47] <Renegade15> simple question, though: is the output of PHP's base64_encode() compatible with what the import expects for <attachment> -> <contents>?
[15:51] <Renegade15> oh, and another question: how to treat html tags in comment content? leave them be, encode them, ...?
[19:28] <timrc> I'm hitting https://answers.launchpad.net/launchpad/+question/152715 :/
[19:32] <lifeless> oh excellent.
[19:32] <lifeless> so its failing for you now
[19:32] <lifeless> ?
[19:32] <timrc> lifeless, yep
[19:32] <timrc> lifeless, just upload a dummy package and got the rejection
[19:32] <lifeless> no losas for a few hours, but I'll try to get this debugged this time
[19:33] <lifeless> ppa.lp.net ?
[19:33] <lifeless> or upload.u.c ?
[19:34] <lifeless> timrc: ?
[19:34] <timrc> lifeless, sorry... ppa.lp.net I believe, "dput ppa:timrchavez/test4 dummy_1.2_source.changes"
[19:34] <lifeless> yeah cool
[19:34] <lifeless> thanks
[19:37] <lifeless> timrc: will ou be around in 2.5 hours ?
[19:37] <lifeless> timrc: I might want to get you to try a few more uploads
[19:37] <lifeless> timrc: we don't know the way in which this faults yet
[19:42] <timrc> lifeless, hm, not sure if I'll be around or not
[19:42] <lifeless> ok
[19:42] <lifeless> I'm sure we can figure something out :)
[19:42] <lifeless> I will ping you just in case - there is a chance this issue is client specific
[19:42] <lifeless> e.g. tz or timestamp skew.
[19:42] <timrc> lifeless, I'll try to be around.. aye
[19:43] <timrc> interesting thought, considering it was daylight savings time
[20:30] <broder> would it be inappropriate for me to ask somebody to rescore https://launchpad.net/~broder/+archive/ubuntu-tests/+build/2905803 because the build fails locally (but works on lp's buildds)?
[20:30] <lifeless> right now we're a little short on builders ;)
[21:18] <Kiall> Anyone else having issues uploading to a PPA? "550 Changes file must be signed with a valid GPG signature: Verification failed 3 times: ['General error', 'General error', 'General error'] : Permission denied."
[21:18] <Kiall> (Yes - It is signed correctly0
[21:18] <Kiall> (Yes - It is signed correctly)
[21:19] <Kiall> oh wow - what happened to all the builders? lol
[21:21] <Renegade15> I believe it is a known issue: https://answers.launchpad.net/launchpad/+question/152715
[21:21] <Renegade15> but I'm only going by the few dozen lines spoken in the past few hours
[21:22] <Kiall> Renegade15: sure - just read the logs there a min ago aswell :)
[21:22] <Kiall> (probably should have asked before reading though ;))
[21:22] <Renegade15> eh, might as well give the illusion of activity in the channel ;)
[21:38] <lifeless> Kiall: we're looking at it now
[21:39] <Kiall> lifeless: cool, strangely, a few mins later I got a packaged accepted email..
[21:40] <lifeless> yes
[21:40] <lifeless> see bug 798957
[21:43] <lifeless> Kiall: Renegade15: I need a test upload to verify
[21:43] <lifeless> do you have the changes + dsc + diff.gz for one of your uploads that *errored* ?
[21:44] <Renegade15> heh, I'm not here for that
[21:44] <lifeless> ah np
[21:44] <lifeless> Kiall: ^
[21:44] <Renegade15> I joined seven hours ago for XML questions that never got answered :P
[21:44] <Kiall> lifeless: sure
[21:44] <Kiall> lifeless: should I just fire it up, or you need the details?
[21:45] <lifeless> Kiall: I want a copy to reproduce the problem
[21:45] <Kiall> K, I'll pop them in a .tgz on dropbox
[21:45] <lifeless> thanks
[21:45] <lifeless> or attach to the bug
[21:45] <Kiall> sure
[21:45] <lifeless> attaching to the bug might be better
[21:47] <Kiall> sure, on their way up
[21:47] <lifeless> Kiall: thanks
[21:47] <Kiall> done..
[21:50] <Noldorin__> where has the option on LP gone for configuring mailing lists?
[21:51] <lifeless> on the team page
[21:51] <Noldorin__> lifeless, and if i don't have a team, no mailing list?
[21:51] <lifeless> right
[21:52] <lifeless> the team represents the people involved with the list
[21:52] <lifeless> team admins are list admins
[21:52] <lifeless> team members are list subscribers
[21:52] <Noldorin__> lifeless, fair enough really. thanks for clearing it up
[21:52] <lifeless> the team name gives the list address @ lists.l.n
[21:52] <Noldorin__> lifeless, btw, noticed a popular proposal for wiki feature on LP. is that coming any time soon? we be a good addition to Blueprints i think
[21:53] <Noldorin__> either part of or separate
[21:53] <lifeless> its kindof wedged tbh
[21:53] <Noldorin__> oh, how do you mean?
[21:53] <lifeless> well, doing it well requires considerable though and attention to detail
[21:53] <lifeless> the non core dev who was putting some effort in ran out of steam :(
[21:54] <Noldorin__> yeah, doesn't surprise me
[21:54] <Noldorin__> hmm
[21:54] <lifeless> and we don't want to do it poorly
[21:54] <EvilResistance> anyone know if a package built for precise can be run effectively on a Natty environment?
[21:54] <EvilResistance> or would things explode
[21:54] <EvilResistance> oops wrong channel
[21:54]  * EvilResistance hates his computer
[21:54] <Noldorin__> ...no indeed
[21:55] <Noldorin__> lifeless, would simplify things if it were all repo-based :-)
[21:55] <Noldorin__> just using Markdown syntax or such
[21:57] <lifeless> EvilResistance: you need a chroot/vm/lxc or similar. pbuilder is good
[21:58] <Noldorin__> lifeless, ...would that be a sensible approach for Launchpad you think?
[21:59] <Kiall> Noldorin__: any wiki not using markdown should be deleted ;)
[21:59] <lifeless> Noldorin__: indeed, that is one of the possible/probably implementation angles. That also gets into a lot of scaling and security aspects: have to avoid login cookie disclosure, which means auditing of the escaping code bases, and questions like which repo to use to show the wiki for a project, and what about personal wikis? and how should this interact with our existing text fields?
[21:59] <Noldorin__> Kiall, yep. one of the things that still slightly annoys me about Wikipedia, though admittedly it is more complex :-)
[22:00] <Kiall> wikipedia is pre-markdown becoming popular I think, so its forgivable :)
[22:00] <Noldorin__> lifeless, i see... what do you mean about login cookie disclosure?
[22:01] <lifeless> Noldorin__: content that shows under launchpad.net, if it can provide javascript, can get at your login credentials on launchpad and do whatever it wants.
[22:01] <Noldorin__> Kiall, yeah. or even rST to be fair... eventually someone may get fed up and overhaul the syntax/convert all the pages though
[22:01] <lifeless> Noldorin__: this is why the librarian is at launchpadlibrarian.net so that if someone uploads an html file to a bug, they can't compromise the credentials of the person reading the bug
[22:01] <Noldorin__> ahh, makes sense
[22:02] <lifeless> Noldorin__: but if you want to show a wiki inline....
[22:02] <Noldorin__> lifeless, but surely we wouldn't allow anything close to javascript? Markdown syntax would do
[22:03] <lifeless> Noldorin__: thats why the audit
[22:03] <lifeless> Noldorin__: if someone finds a way to make markdown emit html ...
[22:04] <Noldorin__> lifeless, oh sure. i don't think that's a huge problem though. the original MD implementation, or the one StackOverflow uses has been thoroughly tested in live scenarios.
[22:04] <Noldorin__> it does proper escaping correctly in other words
[22:04] <Noldorin__> with guarantee
[22:04] <lifeless> not something I'm willing to take on faith
[22:04] <Noldorin__> heh, guess i'm just less cautious
[22:04] <lifeless> given that a compromise on launchpad is potentially a compromise on *millions* of users machines as root.
[22:05] <Kiall> yup - for a large site like LP, you don't take anything security related on faith :)
[22:05] <Noldorin__> StackOverflow is a rather bigger site than Launchpad, and it's had no problems :-)
[22:05] <Noldorin__> though arguably less crucial
[22:05] <Noldorin__> as you say
[22:05] <lifeless> Noldorin__: its a much smaller risk
[22:05] <Noldorin__> lifeless, yeah, see above concession ^
[22:05] <lifeless> :)
[22:06] <Noldorin__> lifeless, could always write a minimalistic MD renderer and run automated proof verification on it :-D
[22:06] <Noldorin__> that would make everyone's mind at ease
[22:06] <lifeless> for instance yes :) would rather audit and fix upstream.
[22:08] <Noldorin__> lifeless, how do you mean, audit upstream?
[22:10] <lifeless> go through the python md implementation
[22:11] <Noldorin__> oh, indeed
[22:11] <Noldorin__> lifeless, say, if i were ever interested in giving this a go. how would you recommend approaching it?
[22:11] <lifeless> carefully ? :)
[22:12] <Noldorin__> the LP source is all availble, i take it?
[22:12] <Noldorin__> hah, very funny
[22:12] <lifeless> oh yes
[22:12] <Noldorin__> lifeless, with regarding to testing/isolation/not wanting to care about all the other stuff on LP
[22:12] <lifeless> its mainly a matter of working with the lp product strategy team to agree on what we want to *achieve*, and then I can advise on implementation
[22:12] <Noldorin__> or indeed familiarising myself with the LP API
[22:12] <Noldorin__> code base...
[22:13] <Noldorin__> lifeless, i see. i may just have to approach them about that, if i find myself looking for a project in the next 6 months then? :-)
[22:13] <Noldorin__> is IRC a good point of contact?
[22:14] <lifeless> sure, or the launchpad-dev list
[22:15] <Noldorin__> lifeless, sounds good. i shall bring it up again... some time.
[22:15] <Noldorin__> perhaps when you least expect it!
[22:15] <lifeless> :)
[22:15] <lifeless> Kiall: thank you
[22:15] <lifeless> Kiall: we've established without a doubt that the gpg stuff is fine.
[22:15] <lifeless> Kiall: there is something broken, but we don't yet know what it is
[22:16] <Noldorin__> brb
[22:18] <Kiall> lifeless: debugging is always fun ;)
[23:00] <Kiall> lifeless: i just uploaded another package, failed the first time, passed the second.. issue fixed?
[23:00] <lifeless> faied in the same way ?
[23:01] <Kiall> yea - GPG error first time (a few mins ago).. then I just retired and it went straight in
[23:03] <lifeless> oh thats very interesting
[23:03] <Kiall> cluster where only some servers are rejecting?
[23:03] <lifeless> there is just one server involved for this
[23:03] <Kiall> scratch that idea then ;)
[23:04] <lifeless> Kiall: how long ago is a few minutes, precisely ?
[23:05] <Kiall> Already closed the console.. and dont think it tells me the time anyway!
[23:05] <lifeless> k
[23:05] <lifeless> we restarted 45 minutes ago
[23:05] <lifeless> before that I would have expected a failure
[23:05] <Kiall> maybe 30 - 40mins or so ago?
[23:05] <lifeless> and after it not
[23:05] <lifeless> ah, so yes, that fits. Phew :)
[23:05] <Kiall> guess it was 45 mins ago then ;)
[23:06] <Kiall> BTW .. Is the GPG error related to 63 disabled builders? ;)
[23:08] <lifeless> nope
[23:08] <lifeless> thats a separate issue, being looked at (different team)
[23:08] <Kiall> busy day I then guess ;)
[23:09] <spm> many of those should be back by now. why they're not is a matter of some concern and is being chased.
[23:10] <wgrant> Argh, forgot to check them.
[23:10]  * wgrant reenabled.
[23:10] <wgrant> reenables
[23:10] <Kiall> spm: a typical day in ops then ;)
[23:11] <spm> hmm. not typical. but ... yes. :-)
[23:12] <Kiall> ah ... thats better .. 6 hour wait down to an hour ;)
[23:13]  * Kiall waits for "ftpmaster.internal" to fall over with all 63 builders pulling at once ;)


[04:17] <mup> Bug #1499356 changed: all units have false hook errors after reboot <sts> <juju-core:Expired> <https://launchpad.net/bugs/1499356>
[04:20] <mup> Bug #1499356 opened: all units have false hook errors after reboot <sts> <juju-core:Expired> <https://launchpad.net/bugs/1499356>
[04:23] <mup> Bug #1499356 changed: all units have false hook errors after reboot <sts> <juju-core:Expired> <https://launchpad.net/bugs/1499356>
[05:02] <lazypower|travel> do we have 3 instances of mup running somewhere? seems odd that mup is spamming the same state changes 3 times over a course of 9 minutes.
[10:18] <mup> Bug #1540047 opened: Error in Jujuclient with Python3 <juju-core:New> <https://launchpad.net/bugs/1540047>
[10:21] <mup> Bug #1540047 changed: Error in Jujuclient with Python3 <juju-core:New> <https://launchpad.net/bugs/1540047>
[10:24] <mup> Bug #1540047 opened: Error in Jujuclient with Python3 <juju-core:New> <https://launchpad.net/bugs/1540047>
[11:33] <mup> Bug #1540061 opened: juju 2.0 alpha + local LXD provider: dns hostname inconsistency <juju-core:New> <https://launchpad.net/bugs/1540061>
[11:45] <mup> Bug #1540061 changed: juju 2.0 alpha + local LXD provider: dns hostname inconsistency <juju-core:New> <https://launchpad.net/bugs/1540061>
[11:48] <mup> Bug #1540061 opened: juju 2.0 alpha + local LXD provider: dns hostname inconsistency <juju-core:New> <https://launchpad.net/bugs/1540061>
[13:30] <mup> Bug #1540076 opened: Storage Hooks before Install <juju-core:New> <https://launchpad.net/bugs/1540076>
[23:06] <axw> wallyworld: we can remove the "show-cloud" card from backlog right?
[23:14] <wallyworld> axw: yep


[02:04] <cmaloney> God bless coffee house conversations
[02:05] <rick_h_> hah
[02:06] <cmaloney> I <3 hearing half-baked plans to get rich
[04:14] <rick_h_> home sweet home and no ditches yay
[04:14] <rick_h_> though the tow truck companies must be raking it in tonight
[04:15] <rick_h_> so many ditches, so much room to fill
[12:21] <cmaloney> Good morning
[12:21] <cmaloney> rick_h_: Glad you made it home safely.
[12:21] <cmaloney> I <3 the Royal Oak Public Library but they drive me nuts some times
[12:22] <cmaloney> outside of the "we send images as newsletters"
[12:22] <cmaloney> It looks like htey have a new site
[12:22] <cmaloney> and it has a RSS feed
[12:22] <cmaloney> so I click on it.
[12:22] <cmaloney> http://www.ropl.org/?format=feed&type=rss
[13:58] <rick_h_> woot https://play.google.com/store/apps/details?id=net.heikobehrens.pebblecam
[14:15] <cmaloney> rick_h_: That's awesome.
[14:16] <rick_h_> cmaloney: yea, now I just need my torso for and I can have all kinds of selfie fun
[15:07] <brousch> Hm. My Google+ tab started chiming and told me a call was coming in to Hangouts. But my phone did nothing
[15:07] <brousch> This is disturbing
[15:07] <rick_h_> ruh roh ghost calls
[15:08] <brousch> I guess I'll keep that tab closed so it doesn't intercept more calls
[15:14] <jrwren> anyone know of a command which will color highlight a match like grep, but won't actually filter?
[15:15] <jrwren> nevermind. stack overflow to the rescue
[15:19] <waf> what's the answer?
[15:19] <jrwren> grep -E 'willbecolored|^' everything matches ^ and it doesn't get colored
[15:21] <waf> ah, nice
[16:09] <greg-g> cmaloney: hahaha at that rss feed
[16:09] <cmaloney> greg-g: Yeah, I'm thinking of sending a "WTF" note.
[17:07] <cmaloney> Wow, IBM started the x86 revolution, and with today's sale of their servers to Lenovo IBM exits the x86 market.
[17:31] <jrwren> do you mean by IBM PC ?
[17:56] <cmaloney> I mean the IBM 5150 (aka the PC)
[19:03] <cmaloney> What the fuckity fuck makes this a $119 book? http://www.amazon.com/Agile-Software-Architecture-Processes-Architectures/dp/0124077722
[19:04] <greg-g> cmaloney: it used far too many capital A's in the title
[19:04] <brousch> Must be a textbook
[19:04] <greg-g> cmaloney: also, "Agile" in title twice
[19:04] <greg-g> that too
[19:05] <greg-g> "in the end, you'll pay $119 plus interest on your 10 year student loan"
[19:07] <cmaloney> Stupid
[19:08] <cmaloney> I read one book for Slashdot that was pretty good in discussing developing under a UNIX environment
[19:08] <jrwren> it says architecture
[19:08] <cmaloney> Would have been a good $35-$50 book
[19:08] <cmaloney> But because it was a "textbook" it was over $100
[19:09] <cmaloney> which, while good, was not worth that kind of cash
[19:10] <cmaloney> Pearson still sells the K&R book as an eBook for what I would consider ridiculous cash
[19:10] <brousch> ebooks are expensive to manufacturer
[19:10] <brousch> All of those bits
[19:12] <cmaloney> http://www.mypearsonstore.com/bookstore/c-programming-language-9780131103627?xid=PSED
[19:12] <cmaloney> Well, considering it was published in 1988
[19:12] <cmaloney> And one of the authors has passed on
[19:15] <cmaloney> Anywho, just wondered if I was crazy for thinking a collection of essays on Agile might not warrant a $119 pricetag
[19:17] <brousch> If you cannot afford it, you are not worthy of learning it
[19:22] <waf> as a general rule I stay away from anything that capitalizes the word "Agile"
[19:25] <cmaloney> waf: Yeah, now if it had said "Scrum vs. Kanban - DEATHMATCH!" I would have been all over it.
[23:32] <cmaloney> https://bitbucket.org/benallard/galileo/src
[23:33] <cmaloney> Apparently someone figured out how to get the fitbit to sync under Linux
[23:33] <rick_h_> hah, if you build it, they will actually make it work
[23:33] <cmaloney> There was a project called libfitbit but that seems to have gone by the boards.
[23:34] <cmaloney> Neat thing is it's all Python
[23:34] <cmaloney> And apparently the fitbit sends your password stuff in the clear.
[23:34] <rick_h_> wheee
[23:34] <rick_h_> lastpass to the rescue
[23:34] <cmaloney> so I hope they enjoy my suer-secret password. :)
[23:35] <cmaloney> Oh I don't need lastpass for this password.


[09:25] <cpaelzer> hi mirespace:
[10:26] <Guest48> Hi i am having issue to configure GUI and vnc server on ubuntu 20.04
[10:26] <Guest48> i am in oracle cloud instance
[10:26] <Guest48> is any one can help
[10:28] <madhan> Hi
[10:28] <quadrat> madhan you would need to explain more, what your issues are
[10:28] <madhan> i want to config gui and vnc on ubuntu server
[10:29] <madhan> server is Oracle cloud instance
[10:29] <madhan> is any one can help?
[14:38] <lordievader> Is the Oracle cloud instance running Ubuntu?
[14:38] <lordievader> Also, vnc over the internet ain't fun. IMO better use ssh to administer the server/vm.
[14:39] <lordievader> madhan: ^
[17:24] <octav1a> How can I enable remote locking on an NFS share? Default options cause locking with flock to timeout. statd is running.