[06:37] <didrocks> good morning
[06:38] <jibel> Salut didrocks
[06:49] <didrocks> salut jibel
[06:56] <duflu> Morning didrocks, jibel
[07:13] <didrocks> hey duflu
[07:40] <oSoMoN> good morning desktoppers
[07:42] <didrocks> salut oSoMoN
[07:43] <duflu> Hi oSoMoN
[07:43] <oSoMoN> salut didrocks
[07:43] <oSoMoN> hey duflu
[07:47] <seb128> good morning desktopers
[07:49] <jamesh> hi seb128
[07:49] <duflu> Hi seb128 and jamesh
[07:50] <seb128> hey jamesh, duflu, how are you? did you have a good w.e? and how is monday going?
[07:50] <duflu> seb128, going well. The weekend was busy. In the middle of 6 birthdays in quick succession plus father's day. Monday is also good. How are you?
[07:50] <oSoMoN> salut seb128
[07:52] <andyrock> good morning!
[07:52] <duflu> Hey andyrock
[07:52] <oSoMoN> morning andyrock
[07:53] <seb128> hey andyrock! wb! had good holidays?
[07:53] <seb128> lut oSoMoN
[07:53] <seb128> duflu, I'm good, spent 3 days in France visiting my gf's familly, her sister just had a baby
[07:54] <andyrock> seb128: yeah doing camping in northern Greece
[07:55] <seb128> nice
[07:55] <jamesh> It's starting to feel like winter has ended, which is nice
[07:56] <duflu> jamesh, I hope you're right because I have some walking and bussing tomorrow. The forecast is not good
[07:56] <duflu> But yeah. Windows all open finally
[07:58] <duflu> And now it starts raining
[08:01] <Laney> YEAHHHHHH
[08:04] <duflu> Laney wins for enthusiasm. Morning Laney
[08:04] <oSoMoN> good morning Laney
[08:04] <duflu> And morning willcooke
[08:05] <didrocks> hey Laney! welcome back
[08:06] <willcooke> hihihi
[08:07] <seb128> hey Laney, wb! how are you? had good holidays?
[08:07] <seb128> hey willcooke
[08:08] <oSoMoN> hey willcooke
[08:11] <Laney> hey duflu oSoMoN didrocks seb128 willcooke!!!!!
[08:11] <Laney> how's it going?
[08:12] <duflu> I would say well, but sounds like not as well as you, Laney
[08:12] <Laney> had a good time yes, surfing (campsite in a cloud at the top of big hill was less fun, rain every evening) was nice & visiting ireland was grrrrrrrrrrrreat
[08:12] <Laney> I had 1 pint of Guinness to confirm that it isn't all that over there either
[08:13] <Laney> duflu: Just seen my emails, excitement abating.
[08:13] <Laney> what did I miss?
[08:16] <seb128> not a lot, business as usual
[08:16] <seb128> GNOME .0 tarballs day today!
[08:17] <seb128> also I think the appstream service went down after a maintainance round on the machine and it looks like nobody out of you has any clue about it so it stayed like that waiting for you :-/
[08:18] <Laney> someone want to learn?
[08:19] <seb128> maybe ask in the meeting tomorrow
[08:19] <seb128> otherwise I wonder if we should get someone from foundations to learn about it
[08:19] <Laney> ok then, for information I asked in the past too
[08:19] <seb128> it's sort of part of the deb/apt stack nowadays
[08:19] <seb128> willcooke, ^
[08:19] <Laney> k, feel free to do that if you want
[08:19] <Laney> what is the problem?
[08:20] <seb128> I don't know, someone on #u-r mentioned a "failed to connect" error
[08:20] <seb128> and jbicha was asking around about it
[08:20] <seb128> so I would guess the service is down
[08:21] <seb128> like it didn't come back up after an outage
[08:21] <Laney> does http://appstream.ubuntu.com/ work for you?
[08:21] <seb128> yes
[08:21] <willcooke> seb128, sounds like a topic for our Foundations meeting for sure, but yeah, makes sense for at least some other people in our team to know more about it
[08:22] <seb128> Laney, is there a timestamp of the last update somewhere?
[08:22] <Laney> in the .yml.gz file
[08:22] <seb128> Laney, https://irclogs.ubuntu.com/2018/08/22/%23ubuntu-release.html#t08:47
[08:22] <seb128> was the "report"
[08:23] <seb128> but maybe they sorted it out anyway
[08:23] <seb128> if you say everything is fine?
[08:23] <seb128> anyway, I wanted to point it out in case
[08:23] <Laney> dunno, let me look
[08:23] <Laney> thx
[08:23] <Laney> an email would have been good probably
[08:23] <Laney> ok, that's the internal rsync
[08:24] <seb128> right, I tried to chase down foundation/Steve, I though someone there would know aobut it
[08:24] <Laney> that is more information
[08:24] <seb128> ah
[08:24] <seb128> good :)
[08:24] <Laney> probably the  archive's copy is out of date then
[08:25] <seb128> andyrock, gnome-online-accounts 3.30 is in Debian if you feel like doing the merge/rebasing ours to the current one? :)
[08:25] <andyrock> seb128: kk
[08:25] <seb128> thx
[08:25] <Laney> laney@nightingale> GET http://archive.ubuntu.com/ubuntu/dists/cosmic/main/dep11/Components-amd64.yml.gz | zcat | sed '6q;d'                                                                                ~
[08:25] <Laney> Time: 20180821T043423
[08:26] <seb128> what does that sed bit does?
[08:26] <seb128> but yeah, outdated
[08:26] <seb128> I know where to check next time at least
[08:26] <Laney> print the nth line
[08:27] <Laney> sed -n '/^Time:/p' would hhave been cooler
[08:28] <seb128> :)
[08:28] <Laney> ubuntu@juju-prod-ue-appstream-back-machine-5:~$ uptime
[08:28] <Laney>  08:28:41 up 13 days,  1:11,  1 user,  load average: 1.09, 1.09, 1.07
[08:28] <Laney> bet that's when it broke
[08:31] <Laney> better now, had to restart the rsync daemon
[08:35] <seb128> jbicha, ^
[08:35] <seb128> Laney, thx
[08:35] <seb128> Laney, do we have any documentation at all about the service? could be useful to at least have a wiki page describing where the service is, how to connect to the machine and how to start/restart it in such situation
[08:36] <Laney> ok
[08:36] <seb128> thx
[08:37] <Laney> I still would like a co maintainer
[08:37] <seb128> Yes, agreed
[08:38] <Laney> good
[08:41] <willcooke> https://twitter.com/barton808/status/1035617038478336000 <-- moar Dell laptops with Ubuntu on
[08:50] <juliank> willcooke: It seems that some users are confused by the applications showing in the initial setup screen. I think the intention there was showing apps the user might not know already, but I'm not sure.
[08:50]  * juliank reads to much reddit
[08:51] <juliank> I found it interesting to see some apps I've never even heard of
[08:52] <juliank> but it might be worthwhile mixing in some popular apps too, for users new to Ubuntu so they see their favorite apps are available too
[08:53] <juliank> reference https://www.reddit.com/r/Ubuntu/comments/9c4m9w/is_there_a_reasoning_behind_the_welcome_apps/
[08:54] <willcooke> juliank, that list is dynamically updated from the promoted snaps at that time (do a "$ snap find")
[08:55] <juliank> I see
[08:55] <willcooke> so the advocacy team tend to promote things around release time like Spotify
[08:56] <willcooke> and then they cycle through the many other snaps as and when.  They might have a push on developer tools one week and games the next
[08:56] <willcooke> so it should be a continually revolving list
[08:56] <darkxst> hey desktopers, any plans to get spidermonkey 60 in for cosmic?
[08:56] <willcooke> juliank, reading the reddit thread now
[08:57] <juliank> It might make sense to have two lists "popular" and "promoted" and show both
[08:57] <willcooke> juliank, yeah, could be.  FWIW - it also hides snaps you already have installed
[09:39] <oSoMoN> popey, Wimpress: do we have a Travis CI account associated to https://github.com/ubuntu ?
[09:40] <popey> Not that I'm aware of
[09:40] <popey> Not sure I would know though.
[09:43] <oSoMoN> popey, do you know who might know if we do?
[09:43] <darkxst> also is there a freeze exception for 3.30 bits? or need to file FFe's for anything I want to upload? (mainly tracker right atm)
[09:43] <oSoMoN> didrocks, maybe you do ? ^
[09:44] <seb128> darkxst, there is no ffe, you need to ask for one
[09:45] <duflu> gdm3 will get updated, right?.... https://bugs.launchpad.net/ubuntu/+source/gdm3/+bugs?field.tag=fixed-in-gdm-3.29.92
[09:46] <darkxst> seb128, ok, that is fine, was only asking because sometimes in the past there was
[09:47] <oSoMoN> Laney, would you mind merging https://code.launchpad.net/~osomon/britney/hints-ubuntu-libreoffice/+merge/354161 ? I am currently re-assessing the situation with that java crash on i386, but don't want to block the LO migration in the meantime
[09:48] <seb128> darkxst, there is a standing ffe for GNOME minor updates, not for bumping through series
[09:49] <seb128> duflu, yes, anything that is on 3.29 is going to be updated to the stable version
[09:49] <seb128> probably even to .1 before 1801
[09:49] <seb128> 01->10
[10:05] <darkxst> seb128, and spidermonkey 60?
[10:05] <seb128> darkxst, no idea about that, no plan that I read of
[10:06] <popey> oSoMoN: ask kenvandine[m]  according to https://github.com/orgs/ubuntu/people
[10:06] <darkxst> so gjs will stay on a dev release?
[10:08] <darkxst> there are currently issues with i386 tests failing but otherwise it seems ok
[10:09] <seb128> I've no idea about that stack, they bumped the depends between 1.53.3 and stable?
[10:10] <RAOF> Hey desktop frens! In putting the finishing touches to the new colord I see Lintian suggesting the girs should go in the multiarch paths but meson doesn't put them there by default.
[10:10] <RAOF> How are people (or are people) getting their girs in the right place?
[10:11] <darkxst> seb128, yep, mozjs60 port came in around 1.53.90
[10:11] <darkxst> currently hanging in debian new queue
[10:11] <darkxst> mozjs60 that is
[10:13]  * duflu suggests a plymouth update for bug 1767918 and simultaneously runs away to make dinner
[10:22] <seb128> darkxst, well, I've no idea, best asking chrisccoulson maybe or jbicha
[10:22] <seb128> hey RAOF
[10:30] <seb128> RAOF, I don't know about the gir question, looks to gnome-bluetooth as an example it doesn't seem to do anything special  and it ends up in the multiarch dir
[10:30] <darkxst> seb128, chrisccoulson has nothing to do with spidermonkey
[10:31] <seb128> darkxst, good, you seem to know who does and who to ask then :)
[10:37] <darkxst> seb128, what is with the animosity? Yes I know someone that can help, but sometimes wonder why I should
[10:37] <seb128> ?
[10:38] <seb128> I'm unsure what's the problem, I tried to help, you didn't like my answer, no big deal
[10:39] <seb128> Chris had been doing recent mozjs update for security and knows about that stack, I though he could have an opinion
[10:39] <seb128> https://launchpad.net/ubuntu/+source/mozjs52/52.9.1-0ubuntu<IP_ADDRESS> is no "nothing" btw
[10:40] <Laney> I'd have thought whoever was doing the gjs update would sync / upload that
[10:43] <RAOF> <freenode_seb "RAOF, I don't know about the gir"> Hm. Ok, I'm check out gnome-bluetooth tomorrow...
[10:44] <darkxst> Laney, its still in Debian NEW and then still has issues, but yes
[10:46] <Laney> hopefully no big deal
[10:47] <darkxst> but it is a question of pre-release mozjs
[10:47] <Laney> pre release?
[10:47] <darkxst> yes
[10:48] <Laney> k, I miss that information, where's that?
[10:48] <darkxst> while gjs switched over, there is no official real yet of the standalone spidermonekry stuff
[10:49] <darkxst> http://ftp.mozilla.org/pub/spidermonkey/prereleases/60/
[10:51] <seb128> RAOF, totem-pl-parser and nautilus also don't do anything special and have their file in the multiarch dir ...  maybe your libdir is not correctly set?
[10:51] <RAOF> The shared libraries end up in the right libdir...
[10:52] <seb128> weird
[10:52] <seb128> I don't know then, sorry
[10:55] <seb128> RAOF, https://github.com/mesonbuild/meson/blob/master/mesonbuild/modules/gnome.py#L643
[10:55] <seb128> RAOF, that suggests the default in meson is to use libdir
[10:55] <RAOF> Hrm. It does, doesn't it. Thanks, I'll poke around a bit more tomorrow.
[10:58] <Laney> darkxst: right, that's mozjs releases for you, it comes from http://ftp.gnome.org/pub/gnome/teams/releng/tarballs-needing-help/mozjs/
[10:59] <Laney> similar happened for 52
[11:08] <darkxst> laney, without questioning their release process with is close to useless, the question was more will we be able to land it in cosmic
[11:09] <oSoMoN> thanks Laney for the hints update!
[11:44] <Laney> oSoMoN: np, forgot to reply on IRC, sorry!
[11:44] <didrocks> oSoMoN: no, it's just my personal account
[11:45] <Laney> darkxst: don't see why not, I think we basically just take whatever they throw out
[11:45] <Laney> probably will even update bionic with 60 at some point
[11:46] <Laney> but that means fixing javascript to not break
[11:46] <Laney> there's a tool to check for that in gjs tho, which is cool
[12:31] <didrocks> Trevinho: thanks for reducing the diff on Yaru!
[12:56] <didrocks999> dac, je viens de voir l'invitation :)
[12:56] <didrocks999> jibel: ^
[12:57]  * didrocks had a kernel freeze, looking for logs…
[13:12] <Trevinho> didrocks: yw, and eventually that line was the only wrong I think
[13:12] <didrocks> great!
[13:12] <didrocks> Trevinho: I'll be back on your MPs soon, have you updated the bileto ticket, do you think you need testing or can I just trust you? ;)
[13:13] <Trevinho> didrocks: I double-checked again, probably it was more manual mistake when adding that line than other
[13:13] <Trevinho> didrocks: well, bileto is updated
[13:13] <Trevinho> so testing can always be appreciated :)
[13:13] <didrocks> Trevinho: oki :)
[13:13] <didrocks> speaking of issues, the last one who merge the icon theme in Yaru did a cp instead of git merge…
[13:13] <didrocks> so now, conflicts everywhere
[13:13] <Trevinho> didrocks:  prior of syncing the VCS's I've to push the taged and changelog finalisation commits
[13:14] <Trevinho> didrocks: yay :-D
[13:14] <didrocks> Trevinho: ok!  It works fine, but it tends not to group items per user properly...
[13:15] <Trevinho> so implies some manual fixes -_-
[13:15] <Trevinho> unless there's a dch flag for fixing it
[13:15] <didrocks> Trevinho: is there any documentation in our wiki page for this?
[13:15] <Trevinho> as otherwise changelog entries won't say much and since it's a native package is nice to have debian/changelog to match
[13:15] <didrocks> I don't know about gbp dch either
[13:16] <Trevinho> didrocks: nope, we just said we could use that... and we did :-D
[13:16] <Laney> moin Trevinho
[13:16] <Trevinho> you know, we're less prone to legislation than you
[13:16] <Trevinho> 😂
[13:16] <didrocks> better to document if we want everyone to use it though :p
[13:16] <didrocks> so, I'll let you Laney and Trevinho doing this ;)
[13:16] <Trevinho> anyway, yes... I can add it somewhere, desktop/git or somewhere else?
[13:17] <didrocks> a note on desktop/git sounds good!
[13:17] <Laney> depends if it's recommended for all packages or just yaru
[13:17] <Trevinho> it's just ` gbp dch --debian-branch=$(git current-branch)`
[13:17] <Trevinho> well without the 2nd part whichj works only ehre
[13:17] <Trevinho> `gbp dch` works
[13:17] <didrocks> recommended for all native package I would say?
[13:17] <Trevinho> I'd say for native packages always
[13:17] <Trevinho> yep
[13:18] <didrocks> the lack of "moving directories" is a little bit annoying…
[13:18] <didrocks> like, as when merging Suru icon (even if the last merger did it right), the new icons are in Suru/ instead of icons/
[13:21] <Trevinho> Ouch.... those moments when you get to your bt keyboatd and the trackpoint gum is missing :-(
[13:32] <jbicha> seb128: you may want to cherry-pick https://gitlab.gnome.org/GNOME/gnome-disk-utility/commit/e13e73797f
[13:45] <didrocks> excellent, didn't know about git merge -s recursive -Xsubtree=…
[13:47] <seb128> jbicha, thx
[13:49] <jbicha> Trevinho: there is a multimaint-merge option for gbp-dch, we could probably add that to debian/gbp.conf
[13:49] <Trevinho> didrocks: how could you miss that... 😅
[13:49] <seb128> is there a gbp special worklow to cherry pick an upstream commit as patch?
[13:50] <Trevinho> (joking)
[13:50] <seb128> or do I just git show > patch and add to the serie as usual?
[13:50] <Trevinho> I mean, how with git can change the world by different arguments
[13:50] <Trevinho> noooo
[13:50] <Trevinho> seb128:
[13:50] <Trevinho> gbp pq import
[13:50] <Trevinho> git cherry-pick sha
[13:50] <jbicha> Trevinho: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/gbp.conf
[13:50] <Trevinho> gbp pq export --no-patch-numbers
[13:50] <Trevinho> done
[13:51] <seb128> Trevinho, thx
[13:52] <Trevinho> seb128: it's basically this https://wiki.ubuntu.com/DesktopTeam/git#Working_on_patches
[13:52] <Trevinho> i'd add the --no-patch-numbers as default to gbp.conf though
[13:52] <didrocks> Trevinho: sure! That was sooooooooooooo obivous ;)
[13:53] <seb128> Trevinho, number or not I don't care, it's just cosmetic of filenames
[13:53] <seb128> it's somewhat easier to reference/read in order with numbers imhop
[13:53] <seb128> but that's personnal taste
[13:54] <didrocks> seb128: feel free to rephrase if you didn't find it as https://wiki.ubuntu.com/DesktopTeam/git#Pick_some_upstream_commits
[13:55] <seb128> didrocks, ah thanks, I read the page but I forgot about that section
[13:56] <didrocks> well, with the amount of info, not surprised :)
[13:56] <seb128> especially that I'm still not comfortable with git
[13:56] <Trevinho> seb128: well, if they all were with numnbers... but well, changing numbering is bad
[13:57] <seb128> I did nuke a checkout again earlier today because it's just easier than trying to figure out how to "undo" changes to several branches
[13:57] <seb128> (I did a gbp import-orig on debian/experimental instead of debian/unstable)
[13:57] <Trevinho> seb128: in case of troubles, improvise :-D
[13:58] <Trevinho> seb128: do you have a ~/.bashrc with a PS1 so that you show the current branch on the cmd prompt?
[13:58] <seb128> now I'm trying to understand the difference between pq import and rebase and which one makes more sense to create a patch :p
[13:58] <seb128> Trevinho, no, but I knew in what branch I was
[13:58] <Trevinho> seb128: well, gbp pq import or git rebase or gbp pq rebase?
[13:58] <seb128> I just forgot that 3.30 uploads were going to unstable now
[13:58] <seb128> unless 3.29 which which we were uploading to experimental
[13:59] <seb128> Trevinho, sorry, gbp pq import vc gbp pq rebase
[13:59] <Trevinho> as gbp pq import only transforms patches into commits, gbp pq rebase refreshes the patches allowing you to fix conflicts on the way
[13:59] <Trevinho> so rebase is needed only when you've imported something old and need then to rebase on the latest one
[14:00] <seb128> well I don't want to "edit" other patches
[14:00] <Trevinho> like you import new upstream, patch doesn't apply, you force the import to an old version then it will rebase and stop for fixing
[14:00] <seb128> I think I'm just going to git show patch and add that to srie :p
[14:00] <Trevinho> nooooo
[14:00] <seb128> oh yes
[14:00] <seb128> simple & efficient :)
[14:00] <Trevinho> if gbp pq import doesn't work, then neither the build will
[14:00] <seb128> well I don't know
[14:00] <Trevinho> i tell you...
[14:00] <seb128> you guys gave me different workflows/commands
[14:00] <Trevinho> it's three commands for easy picking,
[14:01] <seb128> and I'm lost in deciding now
[14:01] <Trevinho> import -> cherry-pick -> export. Done
[14:01] <seb128> k, let me try that
[14:01] <Trevinho> and then you'll understand my love for this :D. or maybe not
[14:02] <seb128> let's see ;)
[14:02] <seb128> oh, lol
[14:02] <seb128> ok, not for this cycle, I forgot that gnome-disk-utility doesn't have a vcs on launchpad
[14:02] <seb128> WIN, I get the easy way out, dch & cp & debuild -S  & dput
[14:02] <seb128> \o/
[14:04] <Trevinho> oh... This old guy! :-D
[14:05] <Trevinho> hours of development in tools, when cp was the only method for making him happy!
[14:05] <seb128> :)
[14:05] <seb128> well, I did my share of updates using the new workflow now
[14:06] <seb128> so I'm fine with it
[14:06] <didrocks> and snapcraft starts to fail on CI…
[14:06]  * didrocks goes to #snappy once again
[14:06] <seb128> I keep forgetting to push tags and it's quite some commands/work but it's ok
[14:07] <seb128> I mean it probably take twice the time to do trivial updates compared to a more minimalistic workflow, but I accept that it pays back for those who do complex work then
[14:07] <seb128> still I'm happy when I can have an "easy" update ;)
[14:08] <didrocks> seb128: hum, if you initialize the repo with the command I gave, at least, tags shouldn't be an issue
[14:08] <didrocks> there can be others, I agree, but not that one :)
[14:09] <seb128> didrocks, I stopped doing that in Debian after spamming the #debian-gnome for 1 hour by pushing 70 upstream tags that were not in their vcs :/
[14:09] <seb128> each push trigerring some pipeline job in salsa
[14:09] <seb128> or something
[14:10] <didrocks> argh
[14:10] <didrocks> sorry for this :)
[14:10] <jbicha> seb128: blame mbiebl for that one, he didn't want upstream tags pushed there at first
[14:10] <seb128> he changed his mind?
[14:10] <jbicha> um
[14:10] <Trevinho> seb128: make your own script for using dch with cp.... so you'll get all done with a command again :)
[14:11] <jbicha> I don't know
[14:11] <seb128> k, anyway I stopped setting the followTag now because of that
[14:11] <didrocks> I imagine a lot of "oh, forgot to the tags" then :/
[14:11] <didrocks> (happens already in a lot of upstream projects…)
[14:19] <didrocks> Trevinho: ahah, you have been tricked by copy/paste and vcscode reformatting the C for you ;)
[14:19] <didrocks> Trevinho: keep happening when dealing with C code, paste, then Ctrl+Z to remove the autoformatting :p
[14:22] <didrocks> Trevinho: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-calculator/+git/gnome-calculator/+merge/353828/comments/921762 as well
[14:23] <didrocks> Trevinho: have you just repushed another commit with the initial date staying the same? (hard to know with launchpad MP UI)
[14:24] <didrocks> which sounds like from the diff
[14:24] <didrocks> ah interesting, you can switch the diff and you see the the new diff was generated on the 30 while the commit is still on the 28… (but no evidence that you pushed a new commit)
[14:25] <didrocks> quite confusing, used to gitlab/github when you see something else was pushed and overrides
[14:28] <Trevinho> didrocks: yeah, on vscode I've to use that ctrl+z, dont' know how to disable without getting the best part of it
[14:29] <didrocks> Trevinho: same, it's rather keep it or disable it completely, which is a shame as it's good otherwise :)
[14:29] <didrocks> Trevinho: trying your ppa, do you have special instructions to test long queries which should be cancelled?
[14:29] <Trevinho> didrocks: as for MP's I've subseeded them since I used different branches...
[14:29] <didrocks> Trevinho: not the one I pointed
[14:30] <Trevinho> didrocks: well, on gnome-calculator is easy
[14:30] <didrocks> but it's ok, it's just launchpad UI ;)
[14:30] <Trevinho> type 10!!! in the shell. and see cpu spinning
[14:30] <Trevinho> close the overlay and it should stop
[14:30] <Trevinho> check on top ofc
[14:30] <didrocks> good use case :)
[14:30] <Trevinho> for nautilus is the same, though it's not spining hard as htat
[14:31] <didrocks> Trevinho: mutter has no MP because we are in sync with debian I guess
[14:31] <Trevinho> if you try that on bionic (cosmic pre ppa) you keep that running forever.
[14:31] <didrocks> ok, it's from experimental
[14:31] <Trevinho> didrocks: yep
[14:31] <Trevinho> copied from there
[14:31] <didrocks> Trevinho: yeah, only testing cosmic though
[14:31] <didrocks> good!
[14:31] <didrocks> so, if my weechat crashes and didrocks is disappearing, blame Trevinho
[14:32] <Trevinho> good test case :D
[14:32] <didrocks> :p
[14:33] <Trevinho> didrocks: I'm pushing the finalize changelog commits and tags too then
[14:33] <didrocks> Trevinho: do I need to restart nautilus (nautilus-desktop) or this is an independant component?
[14:33] <Trevinho> it's independent, it's nautilus itself
[14:33] <Trevinho> didrocks: you can check by just using nautilus as `nautilus --gapplication-daemon` or whatever is
[14:33] <didrocks> k
[14:34] <Trevinho> `--gapplication-service`
[14:34] <Trevinho> if you want to check that process too
[14:34] <Trevinho> for calculator is under /lib/x.../gnome-calculator/...
[14:34] <didrocks> hum, it's helding back the Shell on upgrade
[14:34] <Trevinho> well libexec default
[14:34] <didrocks> let me check, can be due to some local modifications…
[14:35] <didrocks> The following packages have been kept back:
[14:35] <didrocks>   gnome-shell-common
[14:35] <didrocks> apt policy shows that I'm in sync with cosmic…
[14:35] <didrocks> and if I want to install -common, it wants to remove   chrome-gnome-shell gdm3 gnome-shell ubuntu-desktop ubuntu-session
[14:36] <didrocks> The following packages have unmet dependencies:
[14:36] <didrocks>  gnome-shell : Depends: libc6 (>= 2.28) but 2.27-3ubuntu1 is to be installed
[14:36] <didrocks>  libc6 | 2.28-0ubuntu1     | cosmic-proposed  | amd64, arm64, armhf, i386, ppc64el, s390x
[14:36] <didrocks> lalalala
[14:36] <Trevinho> a part from ordering... https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/354045
[14:37] <Trevinho> ah, ok.
[14:37] <didrocks> yeah, basically libc6 has some transitions or something forcing the new version
[14:37] <didrocks> do I really want to install it from -proposed? :p
[14:37] <Trevinho> well keep it temporary :)
[14:37] <Trevinho> that's why I use plenty of VMs and/or schroot more than actual metal
[14:38] <didrocks> yeah, let me dl a cosmic image and spawn a vm
[14:38] <didrocks> sounds safer
[14:48] <didrocks> installing "locale" on the live image and so recompiling/regenerating all of them, always a pleasure ;)
[14:48] <didrocks> ok, alt-f2 -> r, didn't crash :p
[14:50] <didrocks> ok, sounds to work
[14:51] <didrocks> Trevinho: +1 for me "works in my vm" is the new trend :)
[14:51] <Trevinho> :)
[14:51] <Trevinho> didrocks: I noticed I had to push this https://git.launchpad.net/~3v1n0/ubuntu/+source/gnome-calculator/commit/?id=1c45339f350ca659afe1ecb0c6827a3eac9777aa
[14:51] <Trevinho> can we leave it as unreleased for now and then we add on next round?
[14:51] <Trevinho> otherwise need to redo the package build and you can do that, but doing through bileto for me is annoying like hell
[14:51] <didrocks> good for me, so just merging all?
[14:52] <Trevinho> (as deleting the package takes forever)
[14:52] <Trevinho> yeah, let me push other branches finalizations
[14:52] <didrocks> did you see my space comment btw?
[14:53] <Trevinho> mh, ok... I'll do that at next iteration
[14:54] <Trevinho> as at that time I'll cherry-pick upstream finally approved commit again
[14:55] <didrocks> sounds good :)
[14:55] <Trevinho> ok, shell is updated too
[14:55] <Trevinho> missing nautilus
[14:56] <jbicha> one of these days I think I'm just going to upload that gnome-calculator epoch to Debian 😈
[14:59] <didrocks> lalalala :)
[15:01] <Trevinho> jbicha: ahaha, yeah, let's change epoch, this one is already boring
[15:01] <Trevinho> didrocks: nautilus pushed too
[15:02] <Trevinho> didrocks:  for shell, pull pristine-tar and upstream/latest from salsa, not sure I pushed to mine
[15:02] <Trevinho> but since we're 1:1 salsa, just use them
[15:04] <didrocks> Trevinho: sounds good! so, all everything is in sync?
[15:04] <Trevinho> didrocks: should be yes.
[15:04] <didrocks> s/all//
[15:04] <Trevinho> at least I've pushed :D
[15:04] <didrocks> ok, doing the branch dance :)
[15:05] <Trevinho> another option for such cases could be that we do the release with bileto then the sponsor does the gbp import-dsc from the one pushed...
[15:05] <Trevinho> so we're sure we don't miss anything
[15:06] <didrocks> Trevinho: as you wish, that's another option I'm fine with
[15:06] <Trevinho> like vcs merge of the proposed branch -> land bileto -> get the dsc published and update vcs with that
[15:06] <didrocks> Trevinho: if you prefer that, I can do
[15:06] <Trevinho> didrocks: it's too late now, as iv'e pushed the tags
[15:06] <didrocks> what branch did you use for g-s? as there were 2
[15:07] <Trevinho> but, next times we can go with that, so the sponsor does the import commit
[15:07] <Trevinho> didrocks: last one is based on the 1st
[15:07] <Trevinho> so.. .pulll the last (one with xubuntu-cancel)
[15:08] <Trevinho> didrocks: once bileto figures out the .diff is there, also https://bileto.ubuntu.com/#/ticket/3398 is ready to land if you're fine with that.
[15:09] <didrocks> Trevinho: one sec, doing one thing at a time, but ok ;)
[15:09] <Trevinho> so with this we can experiment the mixed merge way (merge vcs and then use dsc too)
[15:09] <Trevinho> yeah, sure.. I just noticed it was there on bileto, so I did that to you
[15:10] <Laney> why would you import a dsc?
[15:10] <Trevinho> Laney: to get the final changelog with proper timing, without that is me doing it
[15:10] <Trevinho> or well, you can also just do that part you
[15:10] <Laney> can't you push the finalise changelog commit?
[15:10] <Trevinho> but... if the .dsc was generted from bileto, and thus has my "finalse" entry, it needs to be 1:1 with that
[15:11] <Trevinho> I can, but then sponsor needs to remember tagging and such... so this coudl be another way to make sure that the vcs is 1:1 with packaging
[15:11] <didrocks> Trevinho: so, all pristine-tar and upstream/latest for the 3 components from salsa, correct?
[15:11] <Trevinho> as ometimes someone could forget a commit around or a change that didn't or did went though the .deb
[15:12] <Trevinho> didrocks: only for shell should be needed
[15:12] <Trevinho> the others are already in sync iirc
[15:12] <Laney> they need to remember the import-dsc, this is just a different command (gbp buildpackage --git-tag-only)
[15:12] <Laney> that is much more normal as a sponsorship workflow
[15:12] <didrocks> ok
[15:12] <Laney> imho
[15:12] <didrocks>  ! [rejected]            upstream/latest -> upstream/latest (non-fast-forward)
[15:12] <Trevinho> Laney: sure, but if I used bileto, you guys can't sponsor that way...
[15:12] <didrocks> Trevinho: so, merging?
[15:12] <Laney> publishing is sponsoring no?
[15:12] <Trevinho> and I rpefer to use bileto so I have all the components ready for you guys only have to hit a button.
[15:13] <Trevinho> Laney: yeah, but in that case is me doing the "finalise" commit.
[15:13] <Trevinho> while instead could be me the author, while the sponsor the committer.
[15:13] <Laney> you don't have to tag it though, that is the more important one
[15:13] <Trevinho> just formal thing, but..
[15:13] <didrocks> yeah, both pristine-tar and upstream/latest from salsa are conflicting with our branch as it's not a ff
[15:14] <Trevinho> ah ok... so... didrocks feel free to retag instead of me with your signature
[15:14] <didrocks> how do you want to handle those, merging or -f? (-f, we may miss some release)
[15:14] <Trevinho> if you wish
[15:14] <didrocks> Trevinho: the issue is not tagging here…
[15:14] <Trevinho> didrocks: well, if using my tag, just pull --tags from me
[15:14] <Trevinho> fetch --tags whatever
[15:14] <didrocks> Trevinho: you didn't get me, I'm talking about the salsa branches
[15:15] <didrocks> both branches from debian are conflicting with ours
[15:15] <Trevinho> ahhhh... sorry
[15:15] <Trevinho> mh, weird, what happened there... mhmh
[15:15] <Trevinho> I didn't touch ~ubuntu-desktop branches so not sure, but well, merge with salsa if that's the case.
[15:15] <didrocks> yeah
[15:16] <Trevinho> there should not be conflicts though.
[15:16] <Trevinho> if there are we've a problem
[15:17]  * Trevinho hads to put some woods on fire, back soon.
[15:17] <Trevinho> has*
[15:38] <andyrock> seb128: did you see this? https://code.launchpad.net/~azzar1/update-manager/add-livepatch-reminder/+merge/353304
[15:51] <didrocks> Trevinho: both bileto tickets published
[15:51] <didrocks> didn't merge gnome-session if you want to try the new workflow afterwards
[17:59] <willcooke> night all
[18:08] <seb128> andyrock, I did but I was waiting for Brian to review ... I'm going to have a look since he doesn't seem to pick it up again


[00:01] <cwong1> asac: I can do it now.  What is the quickest and safest way to do it?
[00:01] <asac> might miss some details, but i think checkout master
[00:01] <asac> then git merge NAMEOFBRANCH
[00:02] <asac> is a good start
[00:02] <cwong1> ok
[00:02] <asac> then fix conflicts
[00:02] <asac> and commit
[00:02] <cwong1> ok
[00:02] <asac> there shouldnt be much conflicts
[00:02] <asac> if any at all
[00:02] <asac> cwong1: you can finish QA while this is in -proposed
[00:03] <asac> giving it a good test before uploading is appreciated though
[00:03] <cwong1> asac: I can only test it with internal xulrunner because of the https problem.  Is that ok?
[00:04] <asac> cwong1: https? get the correct sources.list lines for hardy-propsed from jimmy (i assume its the same issue)
[00:04] <asac> the build should be much faster that way
[00:05] <cwong1> asac: but I thought the https sites dont work when Jimmy build it with the new xulrunner.  Did you fix that already?
[00:05] <asac> cwong1: the only issue i am aware of is the gconf problem
[00:06] <asac> at best test it with that xulrunner (minus the gconf setting test) and for the rest go with in-source xul.
[00:06] <cwong1> asac: yes that is why the https site dont work, right?
[00:06] <asac> ill check it with the PPA xulrunner to be sure before uploading
[00:06] <asac> cwong1: not sure, but i guess yes.
[00:06] <asac> i did the merge for testing here and it worked
[00:06] <asac> (not being behind a proxy)
[00:07] <cwong1> yes, it works fine with direct connection but not if it is behind a proxy.
[00:07] <asac> ok thats gconf then
[00:07] <asac> ill check that before uploading
[00:08] <asac> but please check once with in-source xul so we know that the merge is not broken in general for this case
[00:08] <cwong1> I will do the merge and let you know as soon as I am done.
[00:08] <asac> you can do that test after you pushed to master ;)
[00:08] <asac> thanks!!
[00:08] <cwong1> ok
[00:29] <asac> bug 205010
[00:33] <fta> asac, tb3 is moving fast toward xul-sdk upstream. at least, faster than ever
[00:37] <asac> nice
[01:18] <cwong1> asac: I have merged the RC1 branch into Master. .. I am going to do some testing tonight.
[03:56] <saivann> asac : ping
[04:00] <saivann> asac : Little reminder, my packages are ready for review : bug #230209 . You can email at anytime in the next 2 weeks. I'll be on vacancy after that.
[05:02] <asac> ok i need to re-roll xul 1.9 RC1 ... fun
[10:06] <gnomefreak> asac: people in Debian want ubufox to install plugins for them like we have it
[10:46] <gnomefreak> bug 234726
[10:54] <gnomefreak> asac: are you planning on fixing bug 102684 for Ffox-2, I marked wont fix due to reason in https://bugs.edge.launchpad.net/ubuntu/+source/firefox/+bug/102684/comments/8
[11:33] <gnomefreak> asac: if you added new icon to sunbird its than we need to look into it, If i get time i will but im trying a clean install or sunbird to see if it happens during install since upgrade it didnt change icon
[11:42] <asac> gnomefreak: how do you know that debian wants plugins like we do?
[11:43] <gnomefreak> someone sent an email to one of the mailing lists about it
[11:43] <gnomefreak> i want to say its pkg-debian or something like that
[11:44] <gnomefreak> let me know if you have it if not i can look for it in my gmail account from website
[11:47] <gnomefreak> i cant find the damn hebrew locale bug that was fixed in 'he' it has upstream bug on it.
[11:53] <fta_> Bug 237030
[11:54] <fta_> cannot reproduce
[12:09] <asac> Bug Management  13937 (Karma wh0re)
[12:11] <asac> fta: can we get error console in-place for prism?
[12:11] <fta> yes
[12:11] <asac> i guess its helpful to prove reports where the real but is
[12:11] <asac> bug is
[12:12] <asac> fta: can you put that on a key? e.g. ctrl+F2
[12:12] <asac> or something
[12:12] <fta> there's a menu at the bottom
[12:12] <asac> at the bottom? if i start prism-google-reader, i dont get any menu :/
[12:12] <fta> then Tools / Error console
[12:12] <asac> well prism-google-mail i tested a day back or so
[12:13] <asac> cant remember a menu
[12:13] <fta> the wheel icon in the toolbar
[12:13] <gnomefreak> asac: did you add the fix for the he locales in Hardy lang-packs
[12:14] <asac> gnomefreak: no idea which fix you are talking about
[12:14] <fta> or start in shell with prism-something -d
[12:14] <asac> most likely not i guess
[12:14] <gnomefreak> asac: it was the font rendering for hebrew (still looking for bug atm) but its not looking that i will find it
[12:15] <gnomefreak> it would have been added either just before UDS or during UDS
[12:16] <asac> i can remember a maili about he. .. not idea if it was a bug
[12:16] <asac> but most likcley you are right
[12:17] <gnomefreak> asac: im thinking it was bug 234029
[12:17] <fta> mozilla bug 428848
[12:17] <fta> regression
[12:18] <gnomefreak> yep that would be the bug it looks like
[12:25] <asac> gnomefreak: ok thats fixed then in proposed i'd say
[12:25] <gnomefreak> yep im noting it on another bug atm
[12:26] <gnomefreak> im thinking bug 23267 is same issue so i made a few comments on how to test it
[12:30] <gnomefreak> yep sunbird clean install still has calendar as icon
[12:30] <gnomefreak> ill set it up again later
[14:49] <Flop> Why doesn't the Mozilla Team put FF3 in a PPA repository?
[14:50] <fta> it is
[14:51] <fta> hardy-proposed, ~mozillateam, and ~fta (in that order depending on what you want.. from more stable to fresher)
[14:51] <Flop> I mean RC1
[14:52] <Flop> hardy-proposed contains other packages which may not be desirable.
[14:52] <fta> rc1 is there
[14:53] <Flop> mozillateam seems to contain alpha7
[14:53] <Flop> fta gives me an error
[14:53] <fta> ?
[14:54] <fta> mozillateam has firefox-3.0 - 3.0~rc1+nobinonly-0ubuntu<IP_ADDRESS>mt1
[14:54] <fta> fta has firefox-3.0 - 3.0~rc2+nobinonly-0ubuntu1~fta1~hardy
[14:55] <Flop> where is that repository (mozillateam)?
[14:55] <fta> https://edge.launchpad.net/~mozillateam/+archive
[14:56] <Flop> Oh, I don't know what I was looking at, I'll try that one
[14:57] <Flop> finally, that one works
[14:57] <Flop> thank you
[14:58] <fta> np
 fta gives me an error <= what do you mean ?
[14:59] <gnomefreak> 3.0~rc1+nobinonly-0ubuntu<IP_ADDRESS> 0
[14:59] <gnomefreak>         500 http://de.archive.ubuntu.com hardy-proposed/main Packages
[14:59] <gnomefreak> its in hardy repos
[14:59] <Flop> When I tried to install firefox-3.0 using fta, it wanted to uninstall a lot of stuff like ubuntu-desktop and some other things
 hardy-proposed contains other packages which may not be desirable.
[14:59] <gnomefreak> than install firefox and nothing else
[15:00] <gnomefreak> after installing comment it out
[15:00] <gnomefreak> it will end up in security after some testing (although since we have been testing it it should be pushed into security
[15:01] <Flop> Well, eventually RC2 will come out
[15:01] <fta> Flop, hm, it should not do that. are you sure you were getting both firefox-3.0 *and* xulrunner-1.9 from my ppa (and not just ff3) ?
[15:01] <gnomefreak> you need 2 acks IIRC to get it pushed from proposed to security (or updates) cant remember what one off hand
[15:01] <Flop> fta, i even tried using the update manager
[15:02] <Flop> it said it could only do a "partial upgrade"
[15:02] <Flop> and firefox-3.0 was greyed out
[15:02] <gnomefreak> Flop: try using apt-get upgrade and let fta know the error :)
[15:02] <fta> strange, i'm using my ppa (obviously) and i have no problem on both hardy and intrepid, and noone else reported that either
[15:03] <gnomefreak> mines fine here
[15:03] <gnomefreak> from official and your PPA
[15:03] <Flop> the mozillateam one worked for me
[15:04] <gnomefreak> you shouldnt have both of the repos together use one or other fta's gets updated more than MT or mine
[15:04] <gnomefreak> i cleaned mine up finally and uyploaded a few packages
[15:04] <Flop> fta, did you say your repository has RC2? How is that possible?
[15:04] <gnomefreak> Flop: snapshot daily releases
[15:04] <fta> because code is frozen upstream
[15:04] <gnomefreak> we had ff3 testing since alpha1
[15:05] <Flop> aren't those supposed to be highly unstable
[15:05] <gnomefreak> no RC is fairly good
[15:05] <gnomefreak> Flop: mozilla has been known to push RC1 into final if no bad bugs
[15:05] <fta> no, rc1 and rc2 are really close. very few changes
[15:05] <gnomefreak> im gone be back after work
[15:07] <Flop> I assume the RCs fix all the problems people had with beta5
[15:09] <fta> indeed
[16:08] <armin76> mozilla bug 426228
[16:08] <armin76> fta: asac ^
[16:10] <fta> hm
[18:15] <fta> xul 1.9.1 and ff 3.1 are now alive :)
[18:31] <cwong1> asac: ping
[19:20] <armin76> yay ff3.1 released! *g*
[19:21] <fta> lol
[19:34] <gnomefreak> asac: on bug 102684 do you plan on fixing this in Ffox-2.0?
[19:57] <gnomefre1k> @now new_york
[19:58] <gnomefreak> @whoami
[19:58] <gnomefreak> @login
[19:58] <gnomefreak> @whoami
[19:58] <gnomefreak> thanks
[19:58] <fta> lol
[20:02] <armin76> @login
[20:02] <armin76> @kick fta
[20:08] <gnomefreak> the following is because i get booted not sure if it was seen by anyone
[20:08] <gnomefreak> 14:34 <      gnomefreak > asac: on bug 102684 do you plan on fixing this in  Ffox-2.0?
[20:11]  * gnomefreak thought bugs for hugs were ran by the bug team leader(s)
[20:19] <gnomefreak> ok looks like its working  :)
[20:22] <ubuntu-laptop> well nowi will see if its irssi or connetion that is dumping me :)
[20:23]  * gnomefreak wonders if asac should be at that meeting with the rest of the devel team
[20:42] <gnomefreak> ill be back for meeting
[20:44] <asac> which meeting?
[20:46] <gnomefreak> for me the CC meeeting
[20:47] <gnomefreak> theres one going on now with all the devs "hugs for bugs meeting"
[20:50] <asac> ah
[20:51] <asac> gnomefreak: looks more like a TB meeting
[20:51] <asac> TOPIC: core dev application of XXX
[20:51] <gnomefreak> yeah im seeing that now
[21:38] <ubuntu-l1ptop> hmmm i guess that means its my conection
[21:40]  * ubuntu-laptop has alot of work to do on this connection :(
[21:46] <gnomefreak> yay gnome updates :)
[21:46] <gnomefreak> !cc
[21:51]  * gnomefreak gonna miss meeting tonight im gonna see if i can fix this connection
[21:55] <ubuntu-laptop> Host 'FeistyFawn', running Linux 2.6.20-16-generic - Cpu0: Mobile Pentium II 299 MHz; Up: 1:45; Users: 3; Load: 1.86; Free: [Mem: 5/313 Mio] [Swap: 881/918 Mio] [/: 32039/36653 Mio]; Vpenis: 23.4 cm;
[22:04] <mgol> gnomefreak: at this site: https://wiki.ubuntu.com/MozillaTeam/PreviewArchives, there is a sentence: "These packages have been signed with gnomefreak's key, to add this key: ", but I can't see there the mentioned key. So, where is it?
[22:06] <fta> mgol, this sentence is obsolete, it's a leftover from before PPA ever existed. PPA are not signed (yet)
[22:07] <mgol> fta: ok, thanks.


[18:33] <inetpro> fp
[19:41] <nuvolari> sp
[19:41] <nuvolari> whut?
[19:41] <nuvolari> sp for the day??
[19:53] <charlvn> he? fp? sp?
[19:53] <charlvn> wtf bbq
[19:55] <zeref> ???
[20:56] <nuvolari> lol
[20:56] <nuvolari> charlvn: fp = first post (of the day)
[20:56] <nuvolari> zeref: ^^
[21:07] <charlvn> nuvolari: and sp?
[21:08] <charlvn> second post?
[21:08] <charlvn> troll of the day: http://i.imgur.com/d2e5k.png
[21:16] <nuvolari> charlvn: yup, second post
[21:16] <nuvolari> lol @ TOTD
[21:16] <charlvn> very intellectual conversation this
[21:17] <nuvolari> how so? not much happening after all :P
[21:18] <charlvn> being sarcastic: http://icanhascheezburger.files.wordpress.com/2008/07/funny-pictures-cat-cannot-brain-today.jpg
[21:19] <charlvn> http://memeorama.com/wp-content/uploads/2012/03/I-Cant-Brain-Today-I-Have-The-Dumb-.png
[21:19] <nuvolari> oh dear, I had plenty such moments this week :-/
[21:47] <charlvn> http://groups.google.com/group/ihubrobots/browse_thread/thread/3cb860db66613314
[21:47] <charlvn> now we just need a lambda driver and then we have full metal panic
[22:16] <zeref> whew
[23:35] <locodir-user> Hello there
[23:35] <locodir-user> I NEED HELP IMMEDIATELY with Ubuntu 12.04 server
[23:36] <locodir-user> ANY HELP OUT THERE PLEASEEEEE???...


[13:50] <BluesKaj> Hey all
[22:15] <xapel> how do I upgrade from 12.10 to 13.04? If I run update-manager -d the GUI dialog pops up and says 13.04 is available but if I then select to upgrade the app exits and on the command line it says no new version is available.
[22:17] <bobweaver> xapel,  I upgraded by DL iso and upgrading that way. I also backed everything up first
[22:19] <Jswing> xapel:  sudo sed -e ’s/\quantal/raring/g’ -i /etc/apt/sources.list
[22:19] <Jswing> then do a apt-get update && sudo apt-get dist-upgrade
[22:20] <xapel> bobweaver: I was hoping to just do it the easy way
[22:20] <xapel> Jswing: thanks. will give it a go
[22:20] <bobweaver> there is also what Jswing  said but I did not want to say that
[22:21] <bobweaver> because last time I said that in this channel I got banned
[22:21] <Jswing> why ?
[22:21] <bobweaver> because I came back next day and said that gui was not working
[22:21] <xapel> why is update-manager - d not working?
[22:21] <bobweaver> xapel,  there is *no * alpha
[22:21] <bobweaver> that is why
[22:21] <bobweaver> I think
[22:22] <trism> xapel: you would have to tell us what the error is, although I do notice at least bug 1079251
[22:22] <trism> also bug 1079989
[22:23] <bobweaver> Jswing,  maybe    sudo sed -i 's|quantal|raring|g' /etc/apt/sources.list           what is difference ?>
[22:23] <xapel> ok, i'll see if I can replicate the error quickly
[22:23] <bobweaver> just wondering for knowledge
[22:24] <bobweaver> I think I see that -e runs though ? then -i  replaces ? maybe I am wrong
[22:25] <Jswing> why ?
[22:27] <bobweaver> Jswing,  no I was asking for my own gain I do not know what -e does just trying to learn . Sorry
[22:27] <bobweaver> looking at man
[22:28] <xapel> ok, when I run sudo update-manager -d. a dialog pops up
[22:28] <xapel> it says The software on this computer is up to date, however, Ubuntu 13.04 is now available (you have 12.10).
[22:29] <xapel> there are 3 buttons
[22:29] <xapel> settings...
[22:29] <xapel> upgrade
[22:29] <xapel> ok
[22:29] <xapel> I hit Upgrade
[22:29] <xapel> the dialog disappears
[22:30] <xapel> on the command line it says
[22:30] <xapel> Checking for a new Ubuntu release
[22:30] <xapel> No new release found
[22:31] <trism> xapel: what is prompt= in /etc/update-manager/release-upgrades ?
[22:31] <bobweaver>  f not options.quiet:
[22:31] <bobweaver>       print(_("No new release found"))
[22:31] <bobweaver>     sys.exit(NO_RELEASE_AVAILABLE)
[22:31] <bobweaver> lines 125 --- 130
[22:32] <bobweaver> how to do set -x  in python ? like in bash
[22:32] <xapel> trism: normal
[22:33] <trism> bobweaver: you can't, that I know of, you could use pdb though
[22:33] <bobweaver> thanks trism ,
[22:34] <jtaylor> bobweaver: http://www.doughellmann.com/PyMOTW/trace/
[22:35] <trism> nifty
[22:38] <bobweaver> cool stuff jtaylor !
[22:38] <jtaylor> everything is possible in python :)
[22:38] <jtaylor> (except decent threading ._. )
[22:39] <bobweaver> lol
[22:39] <bobweaver> yeah I need to sopend some more time with py and less with qt qml and c++ javascript ect
[22:40] <bobweaver> s|sopend|spend|g ^^
[22:41] <bobweaver> So I went out to dinner last night with girl friends fathers (gay couple) and I was wearing my raring ringtail shirt. and they where laughing at it. I was like what is so funny ?  then they told me . I wish that I never asked


[03:35] <AnnonyMouse> hi guys. did an update to my thunderBird last week, & since then my header info bar has dissapeared
[03:35] <AnnonyMouse> any ideas?
[03:36] <micahg> hmmm
[03:37] <micahg> which header info bar/
[03:39] <AnnonyMouse> on my mail view window/pane (below my subject/sender/date list), where it shows the msg, that bar that shows the header info, like the subject, date, sender, tags, etc
[03:40] <micahg> it shouldn't have changed it
[03:40] <micahg> did you check your settings under View
[03:41] <AnnonyMouse> yea. been through it all. think it may be a bug or bad update.
[03:41] <AnnonyMouse> Eventually I'll migrate to TB 3, but this is just a tad annoying for now
[03:42] <micahg> AnnonyMouse: maybe try reinstalling the package?
[03:44] <AnnonyMouse> yea.... was really hoping it was a simple setting so that I can avoid having to do that. will have to do a complete purge & reinstall, and may end up being a bigger complication than just living withthe bug...
[03:45] <micahg> nah, just reinstall the package in synaptic
[03:45] <micahg> it won't affect your profile
[03:46] <AnnonyMouse> aptitude reinstall u recon?
[03:46] <micahg> yeah
[03:46] <micahg> try that
[03:47] <AnnonyMouse> i should probably move 2 evolution @ some point....
[03:47] <micahg> why?
[03:47] <micahg> TB is nice :)
[03:47] <AnnonyMouse> yea... i rly like it. been using it 4 ages...
[03:47] <AnnonyMouse> like the fact that I can use many FF plugins too
[03:47] <micahg> yep
[03:47] <AnnonyMouse> (except NoScript)
[03:48] <micahg> just disable HTML by default
[03:48] <AnnonyMouse> pity about mailbox.inc
[03:48] <AnnonyMouse> i use TB to read my RSS's
[03:48] <micahg> Ah, I used to do that
[03:48] <micahg> TB3 fixed some bugs with that
[03:49] <micahg> ok, I have to go, I'll be back on in a couple of hours if you're still having trouble
[03:49] <AnnonyMouse> i should b fine, thnx
[16:04] <micahg> fta: how can I test a build of firefox-3.7.head?
[16:35] <fta2> micahg, er? not sure i understand. why not install the one from the ppa?
[16:36]  * micahg is testing a change for a bug fix
[16:37] <fta2> a fix not in the branch?
[16:38] <micahg> yes
[16:43] <fta2> branch the branch, add your stuff on top and bzr bd --merge it
[16:49] <micahg> I branched to a local copy
[16:50] <micahg> but I"m wondering how to build/get the orig.tar.gz
[16:51] <micahg> I think the problem is I'm trying to build using yesterday's tarball
[16:52] <micahg> ugh
[16:52] <micahg> why does it keep tryinig to upload a 34MB tarball?
[16:53] <micahg> nevermind
[16:54] <micahg> that's the directory
[16:54] <micahg> ok, I'm hoping it works now
[16:54] <micahg> I wanted to test the patch before merging
[16:54] <micahg> s/patch/fix/
[16:55] <fta2> get the last tarball from the ppa, and update your local changelog accordingly
[16:56] <micahg> I linked the mozilla daily ppa as a dependency
[16:56] <fta2> why are you uploading?
[16:56] <micahg> need a test build
[16:56] <micahg> don't want to build locally
[16:56] <fta2> oh
[16:56] <micahg> created a new mozilla test ppa
[16:56] <micahg> for me
[16:57] <micahg> https://edge.launchpad.net/~micahg/+archive/mozilla-test
[16:57] <fta2> i have 2 bzr aliases for that
[16:57] <fta2> bzr alias ppa="bd --merge --build-dir=../ppa --orig-dir=../tarballs/ --builder='dpkg-buildpackage -rfakeroot -S -sa -kB6EE20E8'"
[16:57] <fta2> bzr alias ppa2="bd --merge --build-dir=../ppa --orig-dir=../tarballs/ --builder='dpkg-buildpackage -rfakeroot -S -sd -kB6EE20E8'"
[16:58] <fta2> i do bzr ppa to create a package with the tarball
[16:58] <fta2> and bzr ppa2 when i don't need to push the tarball
[16:58] <fta2> -sa vs -sd
[16:58] <micahg> I'm hoping that linked the mozilla daily ppa will keep me from needing the tarballs
[16:58] <fta2> then i dput the *changes from ../ppa
[17:02] <micahg> what does bd --merge do?
[17:03] <fta2> it merges the debian dir with the tarball to create the proper directory, then you can build or create a source package from there
[17:04] <fta2> the branch is not enough as it doesn't contain the sources
[17:06] <micahg> ah, where do I get bdd?
[17:07] <micahg> bd?
[17:07] <fta2> bzr-builddeb
[17:08] <fta2> i think asac made a tutorial once
[17:08] <micahg> ok
[17:08] <micahg> cool
[17:08] <fta2> look at the classroom minutes
[17:08] <micahg> but I'm still hoping I don't need the tarballs :)
[17:09] <fta2> you need to have it locally, but you should not need to upload it
[17:11] <micahg> I'll find out in an hour
[17:12] <micahg> I managed to upload my branch to LP last night
[17:31] <micahg> fta, you're correct of course, I'll have to play with bd later
[19:31] <jcastro> fta: around?
[19:40] <fta> jcastro, yes
[19:40] <jcastro> fta: nm, figured it out
[19:48] <fta> jcastro, i see some patches landed in the gwibber packaging branch, is it ready? should I respin the dailies?
[19:50] <jcastro> fta: doesn't hurt to try
[20:01] <fta> [reed], is modules/distribution.js gone?
[20:02] <[reed]> not sure
[20:04] <fta> jcastro, hm, my bot says there's no change. did someone move the branch(es)?
[20:04] <fta> [reed], my build failed today: dh_install: firefox-3.7 missing files (debian/tmp/usr/lib/firefox-*/modules/), aborting
[20:04] <[reed]> hmm
[20:05] <jcastro> fta: ah, I don't think lp:gwibber is pointing to the new stuff yet
[20:05] <fta> [reed], yesterday, there was just /usr/lib/firefox-3.7a1pre/modules/distribution.js
[20:05] <jcastro> fta: lp:gwibber/trunk
[20:07] <fta> jcastro, hm, the packaging uses lp:gwibber
[20:08] <Mook_sb> fta: did you mean .jsm? the .js lives in components/ (and appears to be gone)
[20:09] <fta> Mook_sb, eh? my error is when building ff trunk, not songbird
[20:10] <Mook_sb> fta: yes, and I was referring to browser/ in m-c :)
[20:10] <fta> https://edge.launchpad.net/~ubuntu-mozilla-daily/+archive/ppa
[20:10] <fta> https://edge.launchpad.net/~ubuntu-mozilla-daily/+archive/ppa/+build/1192135
[20:15] <fta> between r32030 and r31978
[20:17] <fta> [reed], ^^
[20:26] <fta> [reed], something's wrong
[20:27] <fta> [reed], search for "Removing unpackaged files..." in both http://launchpadlibrarian.net/30909179/buildlog_ubuntu-karmic-i386.firefox-3.7_3.7~a1~hg20090827r32030%2Bnobinonly-0ubuntu1~umd1_FAILEDTOBUILD.txt.gz and http://launchpadlibrarian.net/30874616/buildlog_ubuntu-karmic-i386.firefox-3.7_3.7~a1~hg20090826r31978%2Bnobinonly-0ubuntu1~umd2_FULLYBUILT.txt.gz
[20:27] <fta> build/buildd/firefox-3.7-3.7~a1~hg20090827r32030+nobinonly should not be there
[20:36] <fta> mozilla 463605
[20:47] <fta> diff of the 2 build logs: http://paste.ubuntu.com/260511/
[20:48] <fta> -/usr/bin/perl -I../../xpinstall/packager -e 'use Packager; Packager::Copy( "../../dist", "../../dist/firefox-3.7", "packages-static", "unix", 1, 0, 1);'
[20:48] <fta> +/usr/bin/perl -I../../xpinstall/packager -e 'use Packager; Packager::Copy( "/build/buildd/firefox-3.7-3.7~a1~hgXXXXX+nobinonly/build-tree/mozilla/browser/installer/../../dist", "/build/buildd/firefox-3.7-3.7~a1~hgXXXXX+nobinonly/build-tree/mozilla/browser/installer/../../dist/firefox-3.7", "packages-static", "unix", 1, 0, 1);'
[20:48] <fta> this seems wrong
[20:59] <fta> [reed], http://hg.mozilla.org/mozilla-central/rev/0bd17bd1cbaf#l3.1
[21:00] <fta> [reed], i won't fix it in ubuntu, it's a regression from mac
[21:01] <[reed]> fta: the bug affects ubuntu, though, correct?
[21:01] <fta> it affects anyone using make install
[21:01] <[reed]> can you file a bug on it at least? you don't have to add a patch. I'll make sure somebody gets on it asap.
[21:10] <fta> [reed], mozilla 513067
[21:20] <fta> jcastro, ken's commit went to ~gwibber-team/gwibber/packaging, my dailies are based on ~gwibber-team/gwibber/packaging.trunk :(
[21:20] <fta> commitS
[21:28] <[reed]> fta: Is this via "make install" or "make package"?
[21:29] <fta> hm, make install


[02:36] <stgraber> infinity: that's the change which switches everyone to lxdbr0 and removes the dependency on old lxc and its bridge ^
[02:37] <stgraber> I'll tag and upload a new usptream rc soon but figured it'd be easier to have the packaging bits uploaded separately as they are pretty complex on their own
[02:37] <stgraber> (not as horrific as some of that stuff slangasek has been working on lately though :))
[02:38] <stgraber> I tested upgrade from current version and clean installs on both xenial and trusty, then doing a subsequent upgrade to confirm that things don't needlessly re-trigger, then tried a reconfigure and confirmed that everything does re-trigger in that case
[08:58] <flexiondotorg> Laney, Any chance I can get a release team ack on this? https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1565709
[08:58] <ubot5`> Launchpad bug 1565709 in ubuntu-mate-meta (Ubuntu) "FFe: Please updated ubuntu-mate-meta to add ubuntu-snappy-cli" [Undecided,New]
[09:02] <Laney> flexiondotorg: looks fine
[09:02] <flexiondotorg> Laney, Thanks.
[09:05] <xnox> Laney, any idea which go/juju people to bug about bug #1566200
[09:05] <ubot5`> bug 1566200 in golang-github-juju-loggo (Ubuntu) "package golang-github-juju-loggo-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/share/gocode/src/github.com/juju/loggo/package_test.go', which is also in package golang-juju-loggo-dev 0.0~git20150318-0ubuntu1" [Undecided,New] https://launchpad.net/bugs/1566200
[09:08] <Laney> xnox: I would try this person https://launchpad.net/ubuntu/+source/golang-juju-loggo/0.0~git20150318-0ubuntu1
[09:08] <Laney> ;-)
[09:08] <xnox> Laney, that's old working package, something else is uploaded as a conflict of that.
[09:09] <infinity> Kinda looks like it's a rename without Conflicts/Replaces.
[09:09] <Laney> the old package was Ubuntu only
[09:09] <infinity> Yeahp, so we need an Ubuntu delta for 3 weeks with a C/R, then we can drop it in 16.10
[09:10] <Laney> xnox: or this guy https://lists.ubuntu.com/archives/xenial-changes/2016-March/010537.html
[09:10] <Laney> or you could probably JFDI
[09:10] <xnox> lol
[09:11] <xnox> i was hoping to punt it on some other team.... not like my manager or the ex-team member
[09:11] <xnox> *sigh*
[09:11] <Laney> haha
[09:20] <infinity> xnox: A Conflict/Replace takes 5 seconds, JFDI. :P
[09:20] <infinity> xnox: And you can sync over it the next time Debian revs (post-release, that is).
[09:32] <mwhudson> yay for multiple packagings of go libraries
[12:58] <doko> infinity, powerpc-utils ftbfs, did you intend to sync/merge?
[14:37] <tyhicks> hello!/win 35
[14:37] <tyhicks> bah
[14:38] <tyhicks> I was wanting to ask if the apparmor FFe is on anyone's list to be looked at?
[14:38] <tyhicks> https://launchpad.net/bugs/1561762
[14:38] <ubot5`> Launchpad bug 1561762 in apparmor (Ubuntu) "[FFe] AppArmor 2.11 Beta 1 for policy namespace stacking and bug fixes" [Critical,New]
[14:42] <davmor2> tyhicks: let me guess you use irssi
[14:43] <tyhicks> you are correct :)
[14:45] <Ukikie> One could always link http://niklas.laxstrom.name/page/eng/irssi >_>
[15:14] <awe> I was wondering if anyone could comment on https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1552424
[15:14] <ubot5`> Launchpad bug 1552424 in network-manager-vpnc (Ubuntu) "[FFE] NetworkManager 1.2-beta" [Undecided,Confirmed]
[15:14] <awe> seb128, ^^
[15:14] <seb128> awe, thanks
[15:15] <seb128> cyphermox got busy with other things and nobody picked up the ball to push that one forward
[15:15] <seb128> but it would be really good to get in xenial
[15:15] <cyphermox> that's why he's asking ;)
[15:16] <seb128> unsure what was missing to get it reviewed
[15:16] <cyphermox> seb128: I suppose we just need to make sure it's ok with the release team to land so late
[15:16] <seb128> stgraber and pitti commented on it but it didn't get acked (yet)
[15:16] <cyphermox> right
[15:16] <seb128> cyphermox, right, I've been talking to awe about it
[15:16] <awe> I confirmed that there are applet icon issues with vpn
[15:16] <seb128> just trying to get people from here to re-review it and +1
[15:16] <awe> and that openvpn is currently broken
[15:16] <awe> trying to verify whether it's also broken on the touch images
[15:16] <cyphermox> awe: well, needs to be fixed before landing, obviously
[15:17] <awe> cyphermox, sure... just mentioning what I found out yesterday, as it wasn't super clear from the FFe bug what the current status was
[15:32] <stgraber> seb128: looks like the release team isn't subscribed to the bug, so that's probably why I didn't see the rest of that discussion
[15:32] <seb128> oh, that would explain why :p
[15:33] <seb128> stgraber, do you think it's still realistic to get that in?
[15:37] <stgraber> I'm a bit torn, on the one hand I know that getting us to 1.2 will make maintenance of 16.04 massively easier and it will fix a bunch of things people have been complaining about for a long time (multiple vpns and the like). On the other hand, NM version upgrades haven't gone so well in the past and I don't like shipping non-final versions of critical infrastructure bits in a LTS.
[15:37] <stgraber> the obvious problem being that if there is a bad bug affecting some set of hardware, which say, crashes NM immediately, those folks will have no way to get the fix, seeing how they need NM to work to connect to the network in the first place
[15:40] <seb128> stgraber, the 1.2 stable should be out this week or next if I remember correct what awe said
[15:41] <seb128> also LTS users mostly upgrade on .1
[15:41] <seb128> so it gives some bugfixing cycles
[15:43] <stgraber> seb128: I'm more concerned about the release iso image that users upgrading
[15:43] <seb128> yeah, I can understand that
[15:44] <seb128> we still have some weeks to fix bugs though, and then SRU to .1 which gets a new iso
[15:44] <seb128> but yeah, agreed, it would have been better done earlier
[15:44] <seb128> would it be more practical to do 1.2 as a SRU?
[15:46]  * awe is listening, but is participating in another mtg
[15:56] <stgraber> seb128: haha, no
[15:56] <stgraber> if we do 1.2 for 16.04, it's got to be before release, there are so many moving pieces and dbus changes that we really can't do that post-release
[15:57] <stgraber> seb128: ok, so has that VPN bug mentioned in the FFe been fixed? and if so, when would we have packages ready for upload?
[15:57] <awe> no it hasn't been fixed
[15:57] <awe> I will try and reproduce today on the phone
[15:58] <stgraber> if we are doing this, we're going to need that stuff uploaded ASAP so we have maximum user exposure before release
[15:58] <awe> cyphermox's packages aren't up-to-date w/upstream
[15:58] <seb128> awe, why on the phone? wouldn't be easier to do on desktop?
[15:58] <stgraber> I would have really liked to have it before the beta but it's too late for that now
[15:58] <awe> I've verified it's broken on desktop
[15:58] <awe> I have a later verison on the phone
[15:58] <seb128> stgraber, right, which is sort of why I'm rebooting the discussion while awe is looking at the update/issues
[15:58] <seb128> yeah, me too
[15:58] <awe> and want to see if it's fixed in my version or not
[15:58] <seb128> I though cyphermox was going to do
[15:58] <seb128> awe, k
[15:59] <seb128> the first step might be to update the ppa to beta3
[15:59] <awe> yes, that would be a good step
[15:59] <awe> I'm current with beta3 for the phone, which is why I was going to try and test the vpn issue on the phone
[16:00] <awe> although I don't yet have the openvpn package built for the phone yet, and will need to work with cyphermox on that
[16:14] <utlemming> hey...could I get an archive admin to ack in walinuxagent for -proposed for p and t?
[16:34] <ypwong> Laney, ping
[16:34] <slangasek> utlemming: well, you want the SRU team, not the archive admins for that?https://wiki.ubuntu.com/StableReleaseUpdates#Publishing says it's RAOF on Tuesday, but it's no longer Tuesday where he is, whoops.  I can try to take a look a bit later
[16:35] <utlemming> slangasek: thanks, most appreciated :)
[16:35] <utlemming> I was told to pop in here to make the ask by SRU team member
[16:35] <slangasek> uhm
[16:36] <slangasek> utlemming: it's not a new package, it's a package in the SRU queue, so I'm not sure why you would've been directed to the archive admins
[16:36] <utlemming> slangasek: not sure either
[16:46] <ypwong> slangasek, hi steve, is it still okay to accept these packages to xenial? https://bugs.launchpad.net/ubuntu/+bug/1546967
[16:46] <ubot5`> Launchpad bug 1546967 in Linux Backports "[FFe] [needs-packaging] linux backports and related meta packages" [High,New]
[18:08] <infinity> doko: Yeah, powerpc-utils is being futzed with here.
[21:48] <tjaalton> if someone's wondering about the new mesa version on the queue, it has a ffe and it's been tested via x-staging ppa for weeks
[21:54] <stgraber> that lxd upload is a super-trivial packaging change
[21:57] <stgraber> doko: why do you have a .dsc file inside that unbound upload? :)
[21:59] <doko> stgraber, because dpkg leaves temporary files when you cancel the signing


[07:18] <lordievader> Good morning
[10:49] <BluesKaj> Hi folks
[11:37] <IrcsomeBot2> LuxoCrypto was added by: LuxoCrypto
 Hi, just switched from W10 to Kubuntu and loving it. Just a small question: I want to backup my Kubuntu and move it to a Virtualbox VM. However, the backup is 22 GB. How do I do that? My problem is in Virtualbox I can create the new VM but I cannot access the backup files. Any suggestions?


 6A90F21
 XBWM
[13:26] <BluesKaj> Hi all
[17:35] <ben__> Hello
 Hello all
 I need an application in kubuntu but it requires I use a package called libssl1.1
 How do I go about getting it, from my observation it seems the package has been deprecated
[20:42] <sayem> hi, how's going


[21:10] <snail> mōrena, e hoa
[21:15] <ibeardslee> morning
[21:16] <ajmitch>  morning
[22:20] <mwhudson> morning
[22:21] <mwhudson> people appear to have spent the weekend sending me email
[22:21] <ajmitch> that's unfortunate
[22:39] <thumper> morning
[22:42] <chilts> morning
[23:16] <ibeardslee> Anyone got any feedback on the Intel GMA HD 3000 in linux notebooks?
[23:23] <mwhudson> i ordered a thinkpad with one in last week
[23:24] <mwhudson> hasn't arrived yet though
[23:24] <Atamira> morning


[16:24] <Towser> on Ubuntu mate I tried to install my drivers for my usb wifi dongle however the make wasn't successful and won't install. please see the terminal output ar https://pastebin.com/0HDGh537 for details
[16:58] <Towser> how do I make it work?
[16:58] <Mekaneck> Towser: if no one responds try the ubuntu mate discord channels
[16:59] <Mekaneck> more activity there
[16:59] <Mekaneck> the invite link can be found on the website
[18:18] <Mekaneck> Towser: also #ubuntu-irc isn't meant for support, you're in the wrong channel. There's #ubuntu-mate for support too
[18:18]  * Mekaneck just noticed we're both in the wrong channel


[16:00] <gnuoy> #startmeeting ubuntu-server-team
[16:00] <meetingology> Meeting started Tue Aug 23 16:00:34 2016 UTC.  The chair is gnuoy. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:00] <meetingology> Available commands: action commands idea info link nick
[16:00] <powersj> o/
[16:00] <nacc> o/
[16:00] <jgrimm> o/
[16:01] <gnuoy> I'll just give late arrivals a minute
[16:01] <smoser> o//
[16:01] <rharper> o/
[16:01] <gnuoy> #topic Review ACTION points from previous meeting
[16:01] <gnuoy> #subtopic rbasak update https://wiki.ubuntu.com/ServerTeam/Meeting/IRCCommands to match correct urls
[16:01] <gnuoy> They looked good to me
[16:01] <gnuoy> I think that is done
[16:01] <jgrimm> gnuoy, rbasak is out this week
[16:01] <gnuoy> ack, ta
[16:01] <gnuoy> #subtopic smoser: remember to take yourself off the chair list
[16:02] <jgrimm> but agreed
[16:02] <jgrimm> lol
[16:02] <gnuoy> he did!
[16:02] <rharper> heh
[16:02] <gnuoy> #topic Yakkety Development
[16:02] <gnuoy> #link https://wiki.ubuntu.com/YakketyYak/ReleaseSchedule
[16:02] <jgrimm> post FF obviously
[16:02] <gnuoy> yep
[16:02] <gnuoy> #subtopic Release Bugs
[16:03] <gnuoy> I see no link for that, there used to be didn't there?
[16:03] <jgrimm> oh.. yes, but i think rbasak was going to replace with a more useful link
[16:03] <gnuoy> ah, ok
[16:04] <gnuoy> Does anyone want to point at any bugs in particular?
[16:04] <nacc> probably woudl have been http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-y-tracking-bug-tasks.html#ubuntu-server prior
[16:04] <gnuoy> ta
[16:04] <jgrimm> nacc, yeah.. but that's mostly useless for a variety of reasons
[16:04] <nacc> jgrimm: yep, agreed
[16:04] <gnuoy> I'll move on unless someone wants to bring anything up here?
[16:05] <gnuoy> #topic Server & Cloud Bugs (caribou)
[16:05] <jgrimm> i'm good.
[16:05] <gnuoy> any set of bugs or bug that anyone wants to bring up  here ?
[16:05] <caribou> nothing special this week
[16:05] <gnuoy> kk
[16:05] <gnuoy> #topic Weekly Updates & Questions for the QA Team (powersj)
[16:05] <gnuoy> #link https://jenkins.ubuntu.com/server/
[16:05] <powersj> Working on an 'lxctest' wrapper for integration testing for cloud-init and curtin. Check in on various bugs and tickets this morning. Triage later, need to sync with nacc on who is doing what.
[16:06] <gnuoy> tip top
[16:06] <jgrimm> powersj: cpaelzer will be back tomorrow.. i want to rope him into the triage fun as well
[16:06] <powersj> jgrimm, ok! happy to have more help :)
[16:06] <nacc> jgrimm: should we take an action item ( powersj, myself or rbasak) to update https://wiki.ubuntu.com/ServerTeam/KnowledgeBase 's triaging section at some point?
[16:06] <jgrimm> nacc, yes!
[16:07] <nacc> i'm 99% sure the schedule, e.g., is wrong
[16:07] <powersj> ah yes we were going to use friday's meeting to update that, but got to busy wtih triage
[16:07] <gnuoy> nacc, I don't know how to assign action to multiple people!
[16:07] <powersj> Give it to me
[16:07] <jgrimm> nacc, i was just doing some updates to the wiki today to remove old cruft .. so timely observation
[16:07] <gnuoy> #action powersj  https://wiki.ubuntu.com/ServerTeam/KnowledgeBase
[16:07] <jgrimm> thanks powersj
[16:07] <meetingology> ACTION: powersj  https://wiki.ubuntu.com/ServerTeam/KnowledgeBase
[16:07] <nacc> someone asked to join it on #ubuntu-server recently
[16:07] <gnuoy> powersj, thanks
[16:07] <nacc> powersj: thanks!
[16:07] <powersj> np
[16:08] <powersj> nacc, let's chat after this
[16:08] <nacc> powersj: +1
[16:08] <gnuoy> #topic Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges)
[16:08] <smb> The 4.6 kernel update for yakkety unfortunately got delayed due to tooling/archive issues. I would expect a new attempt soonish, but I said something like that before
[16:09] <smb> The new libvirt-2.1.0 went up as planned
[16:09] <gnuoy> thanks for the update smb
[16:09] <gnuoy> #topic Upcoming Call For Papers
[16:09] <gnuoy> i dont have anything and no one else speaking up
[16:09] <jgrimm> smb, is there usually a corresponding update to python-libvirt needed?
[16:10] <jgrimm> smb, i haven't checked just noticed that versions seemed to be somewhat lockstepped in the past
[16:10] <smb> jgrimm, hm... probably that might have slipped through the cracks
[16:11] <jgrimm> smb, cool.. may not be relevant just a thought that crossed my mind reviewing outstanding merges
[16:11] <smb> jgrimm, Not sure either whether my limited upload rights are including that
[16:11] <smb> jgrimm, I guess it should be done
[16:11] <jgrimm> smb, if you don't have time let me know.. i'll find someone
[16:12] <smb> jgrimm, I think its not so much time as can do it
[16:12]  * smb is no core-dev
[16:12] <jgrimm> smb, only has a single ubuntu patch.. hopefullly an easy merge
[16:13] <gnuoy> apologies for the trigger happy topic change
[16:13] <gnuoy> anyone know of any calls for papers?
[16:13] <jgrimm> smb, no worries, just let me know if you want to take or pass along
[16:13] <smb> jgrimm, I think I opt for pass along
[16:13] <jgrimm> smb, :)
[16:14] <jgrimm> thanks for tackling libvirt!
[16:14] <smb> yw
[16:14] <jgrimm> gnuoy, ok, i'm done
[16:14] <gnuoy> ta
[16:14] <gnuoy> #topic Ubuntu Server Team Events
[16:14] <gnuoy> i'm giving this 15 seconds or so before moving to open dicsussion
[16:14] <jgrimm> linuxcon is on this week
[16:15] <gnuoy> anyone here attending?
[16:15] <jgrimm> good number of folks are there or presenting.  stgraber being one
[16:15] <gnuoy> kk
[16:16] <gnuoy> #topic Open Discussion
[16:16] <jgrimm> nada for me
[16:17] <gnuoy> on we go then
[16:17] <gnuoy> #topic Announce next meeting date, time and chair
[16:17] <gnuoy> next meeting will be Tuesday 2016-08-30 at 1600 UTC
[16:17] <gnuoy> chair will be rbasak
[16:17] <jgrimm> thanks gnuoy!
[16:17] <rharper> gnuoy: thanks!
[16:17] <gnuoy> Shall I skip the "ssigned merges/bugwork" topic ?
[16:17] <jgrimm> gnuoy, yep!
[16:17] <gnuoy> excellent
[16:17] <gnuoy> #endmeeting
[16:17] <meetingology> Meeting ended Tue Aug 23 16:17:49 2016 UTC.
[16:17] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-08-23-16.00.moin.txt
[16:18] <nacc> gnuoy: thanks!
[16:18] <gnuoy> np


[17:04] <sbeattie> @schedule Vancouver
[18:00] <ara> hey bdmurray
[18:00] <bdmurray> hi ara
[18:00] <davmor2> hello
[18:00] <pedro_> hello
[18:01] <ara> hi all
[18:05] <LaserJock> anybody around for QA Team meeting?
[18:05] <bdmurray> me ;)
[18:05] <ara> +1
[18:05] <LaserJock> no heno it seems, who's chairing?
[18:06] <intellectronica> hi
[18:07] <Mez> OHAI!
[18:07] <LaserJock> hola Mez
[18:08] <Mez> hola ;)
[18:08] <Mez> comos estas?
[18:08] <ara> the agenda seems empty. does anyone have any particular issues they want to rise?
[18:09] <LaserJock> Mez: bueno bueno
[18:09] <LaserJock> ara: I have one
[18:09] <LaserJock> I'm not sure if stgraber is around or not
[18:09] <LaserJock> but I was thinking it'd be cool to have a Global Testing Jam for Intrepid
[18:10] <LaserJock> I was thinking that it could be done for Beta
[18:11] <bdmurray> That seems a bit late to me
[18:11] <LaserJock> well, there is that
[18:11] <LaserJock> but I'm not sure if it'd work very well to do it on an Alpha
[18:11] <LaserJock> that's definitely a discussion point
[18:12] <LaserJock> my reasoning (which may be deeply flawed ;-) ) was that Beta is the  best chance of getting people to actually download the .isos
[18:13] <LaserJock> bdmurray: would Alpha 6 be better do you think?
[18:15] <bdmurray> LaserJock: or Alpha 5 something well before the kernel freeze as we'll benefit most from testing a wide variety of hardware
[18:16] <LaserJock> alpha 6 is 1 month before kernel freeze
[18:16] <ara_> #join #ubuntu-testing
[18:16] <LaserJock> alpha 5 would give use 3 weeks to get it set up
[18:17] <bdmurray> ogasawara: when do you think would be best?
[18:18] <LaserJock> we could do 2 I suppose, one for alpha 5 and at beta
[18:18] <ogasawara> bdmurray: the earlier before kernel freeze the better
[18:18] <LaserJock> that would be about 1 month inbetween if we did that
[18:19] <LaserJock> but in general, does the idea sound good?
[18:19] <LaserJock> seems like the Bug Jam was pretty successful and we need to get more people involved in the idea of pre-release testing
[18:20] <bdmurray> I think having more hardware tested via testing jam sounds reasonable
[18:20] <ogasawara> +1
[18:20] <LaserJock> agreed, that does seem to be a pain point
[18:21] <LaserJock> a lot of testing is being done via VMs
[18:21] <LaserJock> it'd be nice to see a spread of real hardware
[18:22] <LaserJock> anybody want to lead the charge on it? :-)
[18:22] <LaserJock> I talked to stgraber a bit about the idea a week or so ago and he liked it but I'm not sure if he has time to set it all up
[18:25] <LaserJock> I guess the main tasks will be 1) getting in touch with LoCos to get it set up 2) making sure there's enough good documentation on testing and what to do once you find a bug
[18:25] <tuxmaniac> I am not sure whether I can speak in this meeting. But dont you think most people will not be interested in moving to Intrepid until release on their production machines? And not all will have the liberty of having testing machines. Sorry for interupting if it is not to be done
[18:25] <bdmurray> tuxmaniac: A lot of testing can be done just using a Live CD
[18:26] <LaserJock> tuxmaniac: np, but for sure yes
[18:26] <LaserJock> we're not trying to get people to run Intrepid on their production machines
[18:26] <LaserJock> but my hope was that with a Global Testing Jam people could bring spare machines and have a day of testing fun
[18:27] <tuxmaniac> bdmurray: aah ok. that is very very much possible
[18:27] <tuxmaniac> LaserJock: ok
[18:27] <LaserJock> some might want to jump in on Intrepid (that's one reason I like Beta)
[18:27] <LaserJock> so it's almost like a Install Fest, but more focused on finding bugs :-)
[18:27] <bdmurray> I think we have alot more people running Intrepid than we expect
[18:28] <LaserJock> bdmurray: do we have any numbers on that? it'd be interesting to get some even rough numbers
[18:29] <bdmurray> LaserJock: not that I'm immediately aware of but I could query the database for unique users reporting bugs with Intrepid in the description
[18:29] <LaserJock> we certainly don't have as much as the stable/unstable case in Debian, but perhaps it's more than one would think
[18:30] <tuxmaniac> adding a point. I think LoCos can give some info in that too. Collect locally info on who all are running intrepid and provide that on a wiki page or to some contact?
[18:30] <pedro_> Ara is having some connection issues, she'll be back soon
[18:31] <davmor2> bdmurray: I think a lot of people might of stayed with hardy especially if they need a machine that works
[18:31] <LaserJock> davmor2: although I've seen a few reports of people jumping to Intrepid because of Hardy
[18:32] <LaserJock> but that's probably not a very significant percentage
[18:32] <bdmurray> Anyway, I think we are moving a bit off topic here.  It sounds like a testing jam would be a good idea
[18:32] <LaserJock> in any case, we clearly have a lack of .iso testing
[18:33] <LaserJock> ok, I'll start a thread on ubuntu-qa on it then?
[18:33] <bdmurray> Sounds good, I'd like to hear on the community team went about contacting locos
[18:34] <LaserJock> How's the status of the Intrepid specs?
[18:35]  * LaserJock waits forever for the wiki page to show up
[18:36]  * stgraber waves
[18:36] <LaserJock> stgraber!
[18:37] <LaserJock> could we just run down the Roadmap and see where everybody is at?
[18:38] <LaserJock> bdmurray: useful-bug-metrics?
[18:38] <bdmurray> LaserJock: that one still needs some work
[18:39] <LaserJock> bdmurray: just in implementation, the design is finalized?
[18:39] <bdmurray> LaserJock: right, and Launcpad is also missing some data for very old bugs
[18:40] <LaserJock> ah
[18:40] <LaserJock> I'm pretty excited about that spec, that data will be quite useful I think
[18:40] <bdmurray> Absolutely
[18:41] <LaserJock> ogasawara: how is package-status-pages coming? seems like a lot has been implemented
[18:41] <bdmurray> ogasawara: The kernel bug migration is finished right?
[18:42] <ogasawara> LaserJock: we've done a lot with the package-status-pages.  stgraber was awesome getting it set up on the staging qa.ubuntu.com site.  now I just need to find time to generate additional xml files for additional packages and knocking out some of the feature requests
[18:42] <ogasawara> bdmurray: yes, kernel bug migration was completed as of Monday
[18:42] <LaserJock> ogasawara: awesome
[18:42] <stgraber> ogasawara: just tell me when you are ready to have pkgstatus put on the production website and I'll work on a qawebsite update including it
[18:43] <ogasawara> stgraber: sweet.  Yah I'd like to test everything works when I create additional xml files etc first
[18:43] <LaserJock> cgregan: how's mobile-automated-tests going?
[18:44] <cgregan> LaserJock: Slowly.....
[18:44] <cgregan> I'm one tester for 6-7 individual projects
[18:44] <cgregan> Not a lot of time for other things...unfortunately
[18:44] <LaserJock> cgregan: ok, so what can we do to help?
[18:45] <LaserJock> are there any "bitesize" tasks that'd free you up for other things?
[18:45] <cgregan> LaserJock: If someone could take a look at the case Ara has produced and see what is relevant to UME. That would be great!
[18:46] <LaserJock> cgregan: could you just send a quick email on that to ubuntu-qa?
[18:46] <cgregan> LaserJock: Sure
[18:46] <LaserJock> great
[18:47] <LaserJock> cgregan: and any other tasks that somebody who's not deeply involved in your work could help out with ;-)
[18:47] <cgregan> There will also be some work for Ubuntu Netbook Remis soon
[18:48] <cgregan> Remix
[18:48] <LaserJock> stgraber: how goes the qa-website spec?
[18:48] <persia> That may be harder to coordinate directly.
[18:48] <cgregan> I'm porting some cases over to a new area now
[18:48] <stgraber> LaserJock: I need to recontact the Launchpad/Canonical sysadmins guys to have a copy of our website running with Drupal+OpenID enabled
[18:49] <LaserJock> sbeattie: around?
[18:49] <stgraber> ideally we'd like to do that after the upgrade to Hardy I requested last week
[18:49] <sbeattie> LaserJock: yep
[18:49] <cgregan> LaserJock: I can also send an email to QA email when I have something worth looking at
[18:50] <LaserJock> sbeattie: what is needed to finish off to fix-validation-tracking ?
[18:50] <LaserJock> cgregan: sounds great
[18:51] <LaserJock> So I put the specs on https://wiki.ubuntu.com/QATeam/RoadMap along with a list of Intrepid Tasks
[18:52] <LaserJock> the Tasks are to list stuff that either hasn't been spec'd yet or that doesn't really need a formal spec, but that we still want to do and is worth some priority
[18:52] <LaserJock> I added a few but I'd like to have people add to it things they plan on doing within QA for Intrepid
[18:53] <sbeattie> LaserJock: not a whole lot, I need to make the page I generate report against universe, and generally sync up more with pitti's sru script.
[18:53] <LaserJock> sbeattie: ok, I think I'll have some time to help with that a bit too
[18:54] <LaserJock> I need to get back into sru-tools
[18:54] <sbeattie> I also need to go back and pull out historical data/testcases
[18:54] <sbeattie> LaserJock: that'd be great.
[18:55] <LaserJock> sbeattie: perhaps we should talk to ubuntuwire.com about hosting all that?
[18:55] <sbeattie> if you want, I'm agnostic as to where it gets hosted.
[18:55] <LaserJock> right now I have a branch for qa.ubuntuwire.com/sru
[18:55] <LaserJock> k, we can talk about that later
[18:56] <LaserJock> alright, any more issues?
[18:56] <LaserJock> going once ...
[18:57] <LaserJock> twice ...
[18:57] <LaserJock> OK, I guess we'll call that the end of the meeting
[18:57]  * LaserJock rings the gong
[18:57] <LaserJock> thanks everybody for showing up!
[22:56]  * bryce grabs a seat early
[22:58]  * ArneGoetje rubs his eyes
[22:59] <calc> hi
[22:59]  * asac waves
[22:59] <james_w> hey all
[22:59] <liw> hello
[22:59]  * ogra waves
[23:01] <james_w> has someone been delegated responsibility today?
[23:02] <asac> james_w: is cjwatson on holiday?
[23:02] <bryce> not me
[23:02] <james_w> asac: yup
[23:02] <james_w> and evan and slangasek is at debconf I think
[23:03] <calc> hmm maybe no meeting for today then?
[23:03] <calc> it wasn't delegated to me either
[23:03] <asac> maybe a quick look at alpha-4 ;)
[23:03] <bryce> or we could just review blueprint status, and any milestone bugs?
[23:03] <james_w> sounds like a good idea
[23:03] <james_w> were there any action points from last week?
[23:03] <bryce> no action items
[23:03] <calc> so we start with ArneGoetje?
[23:04] <bryce> sure
[23:04] <bryce> hit it Arne
[23:04] <james_w> hey TheMuso
[23:04] <TheMuso> sorry I'm a bit late
[23:04] <ArneGoetje> hey
[23:04] <ArneGoetje> green light from my side, no show stoppers so far
[23:05] <james_w> ArneGoetje: any milestoned bugs for you?
[23:05] <ArneGoetje> nope
[23:05] <asac> ArneGoetje: do you have any spec assigned?
[23:05] <asac> is that on track?
[23:06] <ArneGoetje> just the language-selector thing, and yes, it is on track
[23:06] <asac> when will this land?
[23:06] <ArneGoetje> probably next week
[23:06] <asac> ok
[23:07] <bryce> okay cool, asac you're next alphabetically
[23:07] <asac> aug 28th is feature freeze ;)
[23:07] <asac> NM 0.7 entered the archive
[23:07] <asac> but we will probably see plenty of new snapshots before release
[23:07] <james_w> great!
[23:08] <james_w> (to the first point at least :)
[23:08] <asac> not sure when i will stop bumping versions, but upstream is still quite active with bugs getting fixed on a daily base
[23:09] <bryce> I noticed it's changed a bit when I updated by laptop yesterday.  Had to re-reboot but then it came up and has been working great since.
[23:09] <asac> bryce: the new approach is to require users to reboot
[23:09]  * slangasek waves in
[23:09] <ArneGoetje> asac: do you know if NM 0.7 includes code for 3G USB devices to switch from USB-Storage to Modem?
[23:09] <liw> asac, reboot? under what circumstance?
[23:09] <asac> liw: to apply upgrade
[23:09] <slangasek> (completely by accident, I can't guarantee that I'm here for the meeting :)
[23:09] <asac> we dont restart NetworkManager on upgrade
[23:09] <asac> slangasek: hi ;)
[23:09] <james_w> hey slangasek, how's debconf?
[23:10] <liw> asac, hrmph, that seems... non-unixy, but very well
[23:10] <slangasek> going pretty well so far - I'm on my way back to the US at the moment, doko, kees, and jorge are representin' for a few more days
[23:10] <liw> asac, (nothing you could do about it anyway, I guess :)
[23:10] <bryce> asac, yeah I remember that discussed last week, so I rebooted on first sign of wireless trouble, and then it worked fine.
[23:11] <slangasek> (today's the daytrip, so they're all out eating cow for the most part)
[23:11] <liw> slangasek, you had a short debconf, eh?
[23:11] <slangasek> yep
[23:11] <asac> another thing that will happen after alpa-4 is  nspluginwrapper everywhere
[23:11] <asac> e.g. not only on 64bit
[23:11] <bryce> slangasek: better than crow at least
[23:11] <asac> the idea is to not crash firefox when flash goes down
[23:11] <slangasek> *much* better. :)
[23:12]  * calc thinks better idea is to get rid of adobe flash and replace it with a fully implemented foss version :)
[23:12] <liw> asac, that sounds awesome
[23:12] <asac> flash experience spec has other eelements:
[23:12] <bryce> calc, please send a patch
[23:12] <calc> flash is so buggy even on windows :(
[23:13] <asac> 1. better description in plugin finder wizard: on track (code exists in bzr)
[23:13] <asac> 2. allow users to easily switch to other plugins that serve the same content-type:
[23:13] <asac>   we are working hard on that in mozillateam, but its not trivial
[23:14] <asac>   i still hope that we will get something for final intrepid
[23:15] <bryce> asac: anything else?  guess I'm next up
[23:15] <asac> the other specs have not much progress; the safe-upgrade code will land in next ubufox upgrade; users will be notified in firefox when they need to restart and are offered a button to actually do the restart
[23:15] <asac> hopefully this will fix the whole class of wierd upgrade issues users experience
[23:15] <asac> bryce: go ahead ;)
[23:16] <bryce> xorg-input-hotplug is the only major FF-critical blueprint, and I've been focusing on it this past week
[23:16] <bryce> the changes have all landed, and work more or less aside from various bugs which we're tracking
[23:17] <bryce> so the blueprint is down to just testing / documentation / bug fixing now
[23:17] <bryce> not a blueprint, but I also took a break from that the last couple days to look into GEM, which has just hit upstream's git trees
[23:18] <bryce> BenC is looking at the kernel side.  I've produced git snapshots of mesa, libdrm, and -intel for him to play with.
[23:18] <bryce> I found them to be quite buggy, but patches exist for the issues I saw, so it's possible we'll be able to pull that in by FF.  We'll see
[23:19] <liw> what is GEM?
[23:19] <bryce> it's a memory manager for X graphics
[23:19] <bryce> it's a fundamental requirement for fixing several major mis-features in X right now
[23:19] <calc> it replaces the old TTM (iirc)
[23:19] <bryce> righto
[23:20] <bryce> well, TTM never actually made it in; Fedora shipped it but no one liked it much
[23:20] <bryce> anyway, another blueprint-ish thing, is I've added apport support for most all X packages, at mdz's suggestion
[23:20] <bryce> I've not tested it much, but this should make it easier to report X bugs (hopefully not TOO easy)
[23:21] <bryce> afaik no alpha-4 bugs.
[23:21] <bryce> doko, you're up next, if you're here?
[23:21] <calc> he's not here apparenty
[23:21] <calc> i think i am next? :)
[23:21] <bryce> calc oops skipped you
[23:21] <asac> go
[23:21] <bryce> go for it
[23:22] <calc> so OOo 3.0rc1 is delayed to Aug 25
[23:22] <calc> which pushed back my A4 bugs to A5
[23:22] <asac> calc: packaging pre-snapshot doesnt make sense?
[23:22] <calc> ooo-langpacks is coming along ok, and i don't think it is really a FF issue
[23:22] <calc> asac: its already in the openoffice-pkgs ppa
[23:22] <calc> asac: 3.0 beta2
[23:22] <asac> calc: ok. what is intrepid right now? and what is in ppa?
[23:23] <calc> intrepid currently has 2.4.1, if OOo seems to be doing ok wrt 3.0rc1 not getting pushed back any more we will go with 3.0 in intrepid and upload on ~ Aug 25
[23:23] <asac> ok. so its not yet clear that we will go for 3.0?
[23:23] <calc> if it is pushed back again i will have to consult with colin, etc to see if it is wise to hope for 3.0 final coming out in time ;)
[23:24] <asac> then keeping 3.0 beta2 out of archive makes sense. thanks
[23:24] <calc> for example the delay between 2.4.0 rc1 and final was 6 weeks
[23:24] <calc> so if rc1 doesn't actually make Aug 25 then yea we might not put 3.0 in at all due to risking the release with just an RC, that might be ok but we haven't discussed it yet
[23:25] <asac> calc: how many testers are using your PPA?
[23:25] <calc> asac: not certain, is there a way to find this out? :)
[23:25] <asac> we... i mean: do you get good feedback?
[23:26] <calc> i haven't gotten any feedback actually
[23:26] <calc> perhaps i should promote usage of it more :)
[23:26] <asac> calc: ok. have you tried to ask on forums for testers?
[23:26] <calc> not yet, i think i will do that, should help get a lot of testers that way
[23:26] <asac> the quality of feedback can vary a lot, but usually there a lots of quite vocal testers available that want to test the latest-crack ;)
[23:27] <asac> ok cool.
[23:28] <asac> who is next? liw?
[23:28] <bryce> anything else calc?  else james_w is up
[23:28] <asac> ah ;)
[23:29] <james_w> I've been away since the last meeting, so I haven't made any progress
[23:29] <james_w> however, I was very happy with the feedback I got last time, so I think I can move forward.
[23:30] <james_w> I should be ok for feature freeze
[23:30] <james_w> I haven't got any milestoned bugs.
[23:30] <james_w> I haven't had a chance to look at pyrex+fontconfig either
[23:31] <liw> james_w, anything else?
[23:31] <james_w> nope, I don't think so
[23:32] <liw> then it's me, yes?
[23:32] <james_w> I think so
[23:32] <liw> CleanupCruft: progressing, cli is done, gui needs to be made, plugins need to be written, needs to be uploaded
[23:32] <asac> liw: ack ;)
[23:32] <liw> GetRidOfPythonCentralAndSupport: lagging, needs discussing with doko, and probably Debian Python people, but I first need to finish the document explaining the issues
[23:32] <liw> GobbyServerPersistentState: my patch works, upstream made their own (independently from me), I'll review that and take it from there
[23:32] <liw> the rest: low priority or postponed until after feature freeze
[23:32] <liw> end of list; any questions? :)
[23:32] <asac> liw: is it something we can test?
[23:32] <asac> (cleanup)
[23:33] <liw> asac, I have packages in my PPA, which I had a couple of people test and give me feedback on the usability of the command line interface
[23:33] <asac> liw: did upstream know that we were working on that too?
[23:33] <liw> gobby (sobby) upstream didn't know we were working on it, too
[23:33] <asac> liw: how much risk to break my system during cleanup?
[23:34] <liw> asac, at the moment, it removes packages, and the likelyhood of removing the wrong package is way bigger than 0, but you have to tell it which packages to remove
[23:34] <liw> so on the order of "apt-get remove" or "apt-get autoremove"
[23:34] <asac> liw: ok. so its interactive?
[23:35] <liw> you say "system-cleaner find" to find the packages, and "system-cleaner cleanup foo bar" to remove specific packages, or "system-cleaner cleanup --all" to remove everything; you can also mark particular packages as ignored (won't be removed)
[23:36] <asac> ok. is there a wiki page you want to give me while doing that ... or is manpage enough?
[23:36] <liw> the manpage is supposed to be enough
[23:36] <asac> ok. thanks. ill try tomorrow evening i hope
[23:36] <liw> cool, thanks
[23:36] <bryce> liw: anything else?  Otherwise Luke's up
[23:36] <liw> I'm done
[23:37] <bryce> TheMuso: take it away
[23:38] <TheMuso> Ok, since the dmraid spec is highest priority, I'm giving that my full attention. I won't be able to finish the accessibility review spec for intrepid, except for getting ubiquity more accessible/more reliably bringing up accessibility tools. This is more of a bug than a feature, so it will be addressed hopefully before feature freeze.
[23:38] <bryce> (slangasek: iirc you have no blueprints, and you're debconffing anyway so we'll skip you, unless you want to toss in any happy release manager comments)
[23:39] <slangasek> no milestoned specs
[23:39] <TheMuso> As for dmraid, I've spent a lot of time in the past few days toying with telling libparted some more about dmraid devices. Once this is done, I'll be working on making the D-I UI sane to use, and getting dmraid arrays brought up by udev.
[23:39] <TheMuso> Not all of this spec will be done for intrepid however, as dmraid dosn't expose enough useful information to be linked against vol_id for example to probe a single device to see if it is a RAID disk for a dmraid array.
[23:40] <TheMuso> So I'll  have to talk to upstream about getting such info exposed.
[23:40] <slangasek> on the release management side, there seems to be a big problem with the desktop CDs again, /etc/fstab ends up not being populated; an unfortunate bit of timing since cjwatson and evand are on vacation, and I'm (possibly) next in line and am only briefly not on a plane :/
[23:40] <james_w> slangasek: I think Mario had some insight in to that
[23:40] <slangasek> ah; is he around?
[23:41] <TheMuso> A few big changes for dmraid will land in both libparted and devmapper once the alpha is out, and other bits will be in the archive early next week, to enable dmraid event monitoring.,
[23:41] <TheMuso> So overall for functionality, dmraid is on track for intrepid.
[23:41] <james_w> superm1> pitti, i think i've gvot an idea of a quick hack that might get around it
 pitti, not necessarily the way that evan and colin will want to put in the end, but that should suffice for a4 to get out the door
[23:41] <james_w> slangasek: you could grab him in -devel if you want to speak to him
[23:42] <slangasek> right, just reviewed; looks ok to me for the nonce
[23:43] <bryce> TheMuso: cool.  Anything else?  How's audio?
[23:44] <TheMuso> bryce: Ah yes. I'm waiting on the kernel guys for alsa 1.0.17 in the kernel, then I can do userspace. Not sure if we will go pulse 0.9.11, but I'd like to, depending on how much time I can get for people to test from a PPA.
[23:44] <TheMuso> Doing that stuff is only a day's work max to get all needed patches from git trees, etc.
[23:45] <bryce> TheMuso: cool thanks, anything else?
[23:45] <TheMuso> Not from me.
[23:46] <bryce> slangasek: was just talking to superm1 on #ubuntu-x so he's around
[23:46] <bryce> slangasek: any other RM words?  Else I think we're done
[23:47] <slangasek> nopers
[23:47] <cody-somerville> :]
[23:47] <asac> ogra: are you in our team or not?
[23:47] <asac> :)
[23:47] <liw> slangasek, have a good flight back home
[23:47] <bryce> asac: I didn't see him comment earlier, I assume he's still busy with health stuff
[23:47] <asac> bryce: he waved
[23:47] <asac> ;)
[23:47] <bryce> oh!  sorry, missed that
[23:47] <slangasek> liw: I'll try, despite Texas's involvement in the process :-)
[23:48] <asac> 23:59  * ogra waves
[23:48] <ogra> well, i ave one open spec
[23:48] <ogra> *have
[23:48] <ogra> which i can close now i guess, i just uploaded the last changes to initramfs-tools and casper
[23:49] <ogra> so the next liveCDs should use 25% copncache virtual ram, please test if teh liveCD runs with 256M setups
[23:49] <ogra> *compcache
[23:50] <bryce> ogra: any milestoned bugs?
[23:50] <ogra> (does anyone know where exactly the current casper branch is located btw ? i seem to only be able to find broken branches on LP)
[23:50] <TheMuso> ogra: Its where it has always been, but its badly broken.
[23:50] <james_w> ogra: you mean broken as in bzr crashing?
[23:50] <ogra> bryce, i got back this evening from hospital, still about 300 bugmails to weed through :)
[23:50] <TheMuso> james_w: Broken as it broken when an upgrade was attempted.
[23:51] <ogra> bryce, but i'm not actually aware of any
[23:51] <TheMuso> james_w: If you try to pull it, it says 0 revisions.
[23:51] <ogra> so they must have shown up last week while i was away if there are any
[23:51] <TheMuso> and nothing gets pulled.
[23:51] <bryce> ogra: cool.  yeah sorry to hear about being stuck at the hospital.  I know how hospital days last 3 times longer than normal days.  :-/
[23:51] <james_w> yeah, I think this is a known problem, it looks like there was a bug in the converter from baz.
[23:52] <ogra> bryce, well, i wasnt exactly ill while being there so it would have been a great opportunity to do some work while being bored
[23:52] <bryce> we should have diverted kees there to hack into the phone system for you ;-)
[23:52] <ogra> james_w, well, for one branch i get 0 revisions, for the other one i get acrual errors
[23:52] <ogra> bryce, haha
[23:53] <bryce> okay, does anyone have anything else?  otherwise let's wrap it up.  :-)
[23:53] <asac> ust one reminder that folks that didnt like NM in the past maybe should give 0.7 a try
[23:53] <asac> and report features that are still missing to cover their use cases
[23:54] <asac> there are still rough edges in the system config part (which allows you to connect without logging in), but in general most features should be there
[23:54] <asac> VPN stuff will enter after alpha-4 ... if you are waiting for that
[23:55] <asac> and if you have a 3G capable phone ... please test to use that through USB (bluetooth wont be possible for 0.7 most likely)
[23:55] <james_w> asac: does it run a real daemon, or is it just dbus at gdm?
[23:55] <ArneGoetje> asac: do you know if NM 0.7 includes code for 3G USB devices to switch from USB-Storage to Modem?
[23:55] <asac> if your phone isnt detected its usually just hal-info tweakage
[23:56] <asac> ArneGoetje: you sure that you have to switch it?
[23:56] <asac> ArneGoetje: maybe its just that the modem is not detected, so it appears like its only storage
[23:56] <ArneGoetje> asac: yes, otherwise only usb-storage will load
[23:57] <asac> ArneGoetje: please open a bug for your device, and add it to the https://wiki.ubuntu.com/NetworkManager/Hardware/3G page
[23:57] <ArneGoetje> asac: see http://www.draisberghof.de/usb_modeswitch/
[23:57] <asac> ArneGoetje: attach lshal output and full syslog to get things started
[23:58] <asac> attach that link in the bug as well ;)
[23:58] <ArneGoetje> asac: ok
[23:58] <asac> (and add '0.7' in bug summary please)
[23:59] <asac> ArneGoetje: your device sounds strange. do you have other devices (3g phone) which you could use to test your provider?
[23:59] <ArneGoetje> asac: 3G phone
[23:59] <liw> are we done with the meeting?
[23:59] <liw> (time's up)
[23:59] <bryce> liw, I think so
[23:59] <ArneGoetje> asac: the usb_modeswitch is necessary for a whole bunch of devices, not only mine
[23:59] <asac> liw: good night ;)
[23:59] <calc> goodnight