[00:34] <RainCT> Hi
[00:35] <RainCT> Isn't "bzr pack" supposed to reduce the size of .bzr, and not to double it? http://paste.ubuntu.com/215878/plain/
[00:36] <RainCT> Or is it keeping an uncompressed backup around or something?
[00:43] <pygi> RainCT, you need to clean the old packs
[01:50] <RenatoSilva> bzr revno file:///d:/Programação/Utilidades/csvt.rb
[01:50] <RenatoSilva> bzr: ERROR: Unsupported protocol for url "file:///d:/Programa├º├úo/Utilidades/csvt.rb"
[04:13] <jkakar> lifeless: I've integrated bzrlib.commands.Command and Command.hooks into Commandant and I have all the tests passing!
[04:14] <jkakar> lifeless: There's still more tests to write and I'd like to do some cleanup.  Thanks a lot for the Command.hooks refactoring, it's really working well for me.
[07:10] <Junqiang> EOL filter doesn't work in bzr, is there any plan on it?
[15:35] <faceprint> how interested are you guys in hearing about crazy (but real world) comparisons between 2a and 1.14-rich-root?
[15:37] <LarstiQ> faceprint: rather
[15:39] <faceprint> I'm moving my development team off of CVS to bzr later this month.  The repository dates back to 2003, and I've used tailor to create and keep up to date a bzr mirror of the CVS repository.  I've got about 30k revisions of about 10k files.
[15:40] <LarstiQ> faceprint: that's a nicely sized tree
[15:40] <faceprint> I've got code files that have between 1 and a few hundred revisions, typical development commit patterns, and then some data files that are less-than-ideal for an SCM.  One example has 220 revisions, about 400k lines, and weighs in at about 10 MB
[15:41] <LarstiQ> right
[15:41] <faceprint> I've been trying to benchmark this repo 6 ways from sunday so I can be prepared for any complaints from my teammates
[15:42] <faceprint> on a 1.14-rich-root copy, that big data file takes 5:30 to annotate, and chews up about 1.8 GB of memory in the process
[15:42] <LarstiQ> ouch
[15:42] <LarstiQ> faceprint: which version of bzr is that with?
[15:42] <faceprint> 1.16.1
[15:42] <LarstiQ> ok
[15:43]  * LarstiQ looks up when jam's annotate-for-big-files changes landed
[15:43] <faceprint> 2a has been running for 30 minutes so far, and I think it's up over 6 GB of memory
[15:44] <faceprint> this is the first thing i've seen "worse" on 2a, thought you guys might like to hear about it
[15:44] <Raim> hi
[15:44] <LarstiQ> faceprint: certainly!
[15:44] <Raim> is there a way to bypass aliases for automation?
[15:45] <LarstiQ> faceprint: could one of the core devs experiment with a copy?
[15:45] <faceprint> LarstiQ: unfortunately that's out of the question.  very private repo.
[15:46] <LarstiQ> Raim: --no-aliases?
[15:46] <faceprint> but if you can tell me which "dimension" of absurdity to go in, I might be able to try and recreate something similar that exhibits the behavior
[15:47] <LarstiQ> faceprint: I think jam or igc would be better suited to give you that feedback
[15:47] <Raim> LarstiQ: yeah, was looking for that exactly. thanks :)
[15:47] <LarstiQ> Raim: lifted from `bzr help global-options`
[15:47] <LarstiQ> Raim: now, if you're doing automation with python and bzrlib, the answer would be different :)
[15:48] <LarstiQ> faceprint: are you subscribed to the mailing list?
[15:48] <faceprint> LarstiQ: not yet.  i've been reading archives all weekend ;-)
[15:49] <Raim> LarstiQ: no, it's about shell automation. I ran into a problem as I aliased "bzr diff" to "diff --using 'colordiff -u'" and then patch naturally chokes on the color codes
[15:49] <LarstiQ> faceprint: since a post about this to the list will get more exposure than irc when most core devs are not working :)
[15:49] <LarstiQ> Raim: right
[15:50] <faceprint> LarstiQ: is it relatively easy to grab bzr.dev and use it w/o touching my regular install?
[15:50] <LarstiQ> Raim: how about `bzr cdiff` from bzrtools? Doesn't it do terminal detection?
[15:50] <LarstiQ> faceprint: yes, very
[15:50] <LarstiQ> faceprint: since bzr runs from source, no installation required, just invoke the right binary
[15:51] <faceprint> excellent.  i'll give that a whirl and see what kind of results I get.
[15:51] <LarstiQ> faceprint: you will want to make sure the C extensions are built for performance, but that can happen inplace
[15:51] <LarstiQ> just run `make` and install the dependencies (pyrex, python-dev and a C toolchain afaik. Oh, libz-dev perhaps
[15:52] <LarstiQ> faceprint: do I understand it correctly that your 1.14-rr is based on a continual tailor conversion?
[15:53] <Raim> LarstiQ: I think I tried that, but it had problems in combination with bzr-pager
[15:53] <LarstiQ> Raim: ah
[15:53] <LarstiQ> Raim: sounds like something to fix :)
[15:53] <LarstiQ> Raim: if you can tell me how to reproduce it, I can file a bug
[15:54] <faceprint> correct.  it syncs the CVS once an hour to a 1.14-rr that is bound to a server with a rich-root-pack repo (because I can't upgrade that copy of bzr yet)
[15:54] <Raim> LarstiQ: this one, https://bugs.launchpad.net/bzr-pager/+bug/329845
[15:54]  * LarstiQ sits back as other people file bugs ;)
[15:55] <LarstiQ> Raim: also seems like luks merged the fix
[16:25] <faceprint> LarstiQ: FYI, bzr.dev on the 1.14-rr was twice as slow as 1.16.1.  I'm running it on 2a now.
[16:26] <LarstiQ> faceprint: specifically annotate on that large file?
[16:26] <faceprint> crap, I forgot about running make.  that's probably not valid results
[16:27] <LarstiQ> valid if you want pure python, but slower :)
[16:28] <faceprint> i'll wager that my 1.16.1 deb has the C extensions, so not apples to apples at the very least
[16:32] <faceprint> wow, big difference.  bzr.dev much faster on that repo now.  1:02 vs 5:28 with 1.16.1
[16:33] <fullermd> Yeah, there's some new stuff with annotate since then.  In the last few days, actually.
[16:36] <faceprint> 2a is much better as well: 2:32 vs (did not finish) with 1.16.1.  and it ended up using a few hundred MB, vs 6 GB with 1.16.1
[16:36] <faceprint> are those speedups destined for 1.17, or a later version?
[16:37] <fullermd> They'll be in 1.17 I'm pretty sure, it hasn't branched yet.
[16:37] <fullermd> (always barring bugs being found that call for backing it out prior to that of course)
[16:38] <faceprint> naturally
[18:57] <garyvdm> Is it possible to have shelve give me a move granular choice. It's groups some changes together.
[18:57] <garyvdm> s/move/more
[18:57] <LarstiQ> garyvdm: as opposed to?
[18:58] <garyvdm> It groups some of the changes together.
[18:58] <garyvdm> I want to shelve only some of them,
[18:58] <LarstiQ> garyvdm: in one hunk you mean?
[18:58] <LarstiQ> garyvdm: ie, you want hunksplitting?
[19:00] <garyvdm> LarstiQ:http://paste.ubuntu.com/216364/
[19:00] <garyvdm> I want to shelve the refresh button code.
[19:00] <garyvdm> but not the larst change.
[19:01] <LarstiQ> garyvdm: yeah, hunk splitting
[19:01] <garyvdm> Ok
[19:01] <LarstiQ> garyvdm: which would be very cool to have
[19:01] <garyvdm> I would think that those are different hunks...
[19:02] <garyvdm> anyway
[19:02] <LarstiQ> garyvdm: right, but the diffing algorithm didn't
[19:02] <LarstiQ> garyvdm: so that is where you as a human could come in to augment the algorithm
[19:03] <garyvdm> LarstiQ: from my understanding of the term hunk - the diffing algorithm would think that those are different hunks.
[19:05] <LarstiQ> garyvdm: they're both in the same set between @@' right?
[19:05] <garyvdm> Yes
[19:05] <LarstiQ> those are the hunk delineators
[19:06] <garyvdm> Ok
[19:06] <LarstiQ> gnu diff has some options to make it try harder to make the hunks smaller
[19:06] <LarstiQ> don't know about patience diff
[19:07] <LarstiQ> garyvdm: all a long way of saying, afaik you can not easily do that right now
[19:07] <LarstiQ> garyvdm: but I'd really like to be able to :)
[19:24] <saedelaere> hi
[19:24] <saedelaere> i'am completely new to a vcs and bazaar. i've read the user guide but having some problems to understand some things.
[19:26] <saedelaere> i'am developing a software that is hosted on sourceforge and want to use the bazaar service there. I'am the only developer there so i need the repo so users can get the latest source code.
[19:26] <saedelaere> so the first thing. i did
[19:26] <saedelaere> bzr init
[19:26] <saedelaere> bzr add
[19:26] <saedelaere> bzr commit -m "blabla"
[19:27] <saedelaere> bzr push ...
[19:27] <saedelaere> now i get a message
[19:27] <saedelaere> "This transport does not update the working tree of<EMAIL_ADDRESS>See 'bzr help working-trees' for more information.
[19:27] <saedelaere> Created new branch."
[19:28] <saedelaere> what does this mean? when i did some changes to the code. how do i update the repository on sourceforge? using bzr push?
[19:29] <LarstiQ> saedelaere: yes, using bzr push
[19:29] <LarstiQ> saedelaere: I wonder why youget that message though
[19:29] <LarstiQ> saedelaere: how did the branch at .../tv-viewer/ come into existance?
[19:30] <LarstiQ> bzr should only say that if there is a working tree present, which there is no need for
[19:30] <fullermd> Well, presumably by that push, since it said 'created new branch'...
[19:31] <LarstiQ> fullermd: then why does it mention updating a working tree?
[19:33] <saedelaere> should i have done this first?
[19:33] <saedelaere> bzr init-repo --no-trees sftp://centralhost/srv/bzr/PROJECT
[19:33] <saedelaere> and then continue like this?
[19:33] <saedelaere> http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/index.html#publishing-a-branch
[19:33] <LarstiQ> saedelaere: not per se
[19:34] <LarstiQ> saedelaere: it will consume less storage and be faster if you use multiple branches, but other than that no difference
[19:34] <saedelaere> branch, working-trees puhh still not understanding completely :)
[19:34] <saedelaere> ok then i've done nothing wrong
[19:35] <saedelaere> like i said i need the repo on sourceforge only so users can get the latest source code
[19:35] <garyvdm> No - people will still get a working tree when they pull
[19:35] <garyvdm> I would think that is a bug with the hosting.
[19:35] <garyvdm> *think*
[19:35] <LarstiQ> garyvdm: are you seeing someting I'm missing?
[19:36] <garyvdm> LarstiQ: I'm baseing that on a big assumption. Let me just somthing.
[19:36] <LarstiQ> sure
[19:40] <saedelaere> ok one more thing. when i ever find someone who whants to contribute and is also allowed to write to my repo, how do we keep our work synchronized? bzr merge "path_to_my_repo_on_sourceforge", will this command add all changes to my local repository?
[19:41] <garyvdm> LarstiQ: my assumption was wrong. So the branch with working tree must have been created before the push?
[19:42] <garyvdm> saedelaere: Yes
[19:42] <LarstiQ> garyvdm: I don't really understand what is going on, lack of information
[19:42] <LarstiQ> saedelaere: that will work
[19:43] <garyvdm> saedelaere: and if someone else who does not have permissions to you trunk branch on sf, they can push there changes to another branch sf, and you can merge from that branch.
[19:44] <garyvdm> This is one of the big wins for Distributed VCS.
[19:44] <LarstiQ> or you can even use `bzr send` and email the commits
[19:45] <garyvdm> saedelaere: If you get the "can't update remote wt" error in future...
[19:46] <garyvdm> You need to get on of the sf admins to do "bzr remove-tree BRANCH" on the server.
[19:47] <LarstiQ> if you can access it with bzr+ssh, you can do it yourself
[19:47] <garyvdm> Oh
[19:47]  * fullermd isn't sure that follows...
[19:48] <garyvdm> LarstiQ: bzr: ERROR: You cannot remove the working tree of a remote path
[19:48] <LarstiQ> garyvdm: I was thinking of hitchhiker
[19:49] <LarstiQ> but you are right, that is more manual than `bzr remove-tree`
[19:49] <garyvdm> hitchhiker?
[19:49] <LarstiQ> which I guess is not a good idea for non-experienced people
[19:49] <garyvdm> What is hitchhiker?
[19:49] <LarstiQ> garyvdm: lp:hitchhiker, an ftp like client based on bzr's transports
[19:49] <garyvdm> ok
[19:50] <fullermd> It's sorta a manual shell on the bzr protocol.
[19:51] <garyvdm> I understand why we can push to a remote wt, but would it not be easy to code bzr to remove a remote wt?
[19:52] <garyvdm> s/can/can't
[19:53] <LarstiQ> garyvdm: not entirely
[19:53] <LarstiQ> garyvdm: you need to check for unknowns
[19:53] <garyvdm> Oh - right
[19:53] <LarstiQ> garyvdm: you are right that we don't have to do conflict merging, so no getting of the content
[19:54] <LarstiQ> so at a minimum one extra listdir
[20:05] <saedelaere> ok i just pushed my second revision and the error did not appear again.
[20:05] <saedelaere> thanks for all your help and hints. oh and great tool. really easy to use. I also tried svn but that was much to complicated.
[20:06] <LarstiQ> saedelaere: good to hear :)
[20:37] <saedelaere> i do a commit with
[20:37] <saedelaere> bzr commit -m "foo"
[20:37] <saedelaere> now i want to add several different messages to this commit
[20:37] <saedelaere> bzr -m "foo
[20:37] <saedelaere> bar
[20:37] <saedelaere> baz"
[20:37] <saedelaere> seems not to be possible to split the message into several lines. Correct?
[20:38] <LarstiQ> saedelaere: incorrect. But if you use -m it depends on your shell being able to handle it.
[20:38] <LarstiQ> saedelaere: I use zsh and there it works.
[20:39] <LarstiQ> saedelaere: alternatively, don't use -m and just let the editor come up, or write a commit message to file and use -F
[20:39] <LarstiQ> saedelaere: see `bzr help commit`
[20:39] <saedelaere> ah thats a good idea, thanks :)
[20:47] <garyvdm> saedelaere: There also guis available.
[20:47] <garyvdm> bzr qcommit from qbzr
[20:47] <garyvdm> or bzr gcommit from bzr-gtk
[20:48] <garyvdm> On windows - qbzr comes with the installer.
[20:51] <saedelaere> i wanted to learn bazaar from the scratch so i started with the terminal. perhaps later i will try a frontend
[21:54] <lifeless> moin
[21:55] <lifeless> jkakar: glad you like it ;) I did it to tease apart bits of bzrlib mainly. Still its very nice that its found external love as well.
[21:56] <jkakar> lifeless: It's awesome, getting takes_args and takes_options for free is worth a lot. :)
[21:57] <jkakar> lifeless: I'm using run_bzr to run the commands and that's working pretty well too.
[21:57] <jkakar> lifeless: At some point I'd like to see if there's a way to make use of the bzrlib.help_topics stuff.  Right now I'm using my own code, but using Command.get_help_text to generate verbose output for commands.
[21:58] <lifeless> jkakar: have you seen bzr-guess?
[21:58] <jkakar> lifeless: Nope.
[21:59] <lifeless> It was one of the things I had in mind with the hooks ;)
[21:59] <lifeless> you might like to load that particular bzr plugin in commandant
[21:59] <jkakar> lifeless: That is creepy. :)
[21:59] <lifeless> (import bzrlib.plugin; bzrlib.plugin.set_plugin_path(); import bzrlib.plugins.guess)
[22:00] <lifeless> jkakar: ?
[22:00] <jkakar> lifeless: bzr-guess, that is. :)
[22:00] <lifeless> why creepy?
[22:00] <jkakar> lifeless: Hmm, I guess I'd also need to register a function for "get_missing_command" to look at plugins.
[22:01] <jkakar> lifeless: Right now I implement hooks for "list_commands" and "get_commands" and leave the rest in their default unbound state.
[22:01] <lifeless> no; get_missing_command is one of the three hooks we provide
[22:01] <lifeless> bzr-guess hooks get_missing_command
[22:01] <lifeless> but it only depends on list and get
[22:01] <jkakar> Ah ha, I get it, nice.
[22:02]  * saedelaere zzz
[22:25] <mwhudson> jelmer: hi?
[22:32] <LarstiQ> mwhudson: iirc jelmer is on a 4-day trip atm
[22:32] <mwhudson> LarstiQ: ok
[22:33] <LarstiQ> mwhudson: yeah, at oxegen.ie
[22:59] <jml> spm, hello.
[23:01] <spm> jml: howdy!
[23:01] <jml> spm, I need to release a new version of Bazaar, and I need you to help me
[23:01] <spm> jml: your wish is my command :-)
[23:02] <jml> spm, can you please make a pqm managed branch for 1.17?
[23:03] <spm> jml: sure. one sec or three
[23:03] <jml> spm, thanks
[23:11] <spm> jml: that should be all systems go for 1.17
[23:11] <jml> spm, thank you!
[23:12]  * jml trundles off to a leisurely breakfast where bzr may in fact be released
[23:13] <spm> jml: bzr v1.17 "Coffee & Danish" ?
[23:13] <jpds> spm: Sounds better than KFC!
[23:14] <jml> spm, "So late it's brunch", more likely
[23:14] <spm> jpds: for breakfast? KFC? blurg. :-)
[23:14] <spm> jml: not... optimistic enough imho :-)
[23:15] <jml> oh well, I'll have plenty of time to think about it on the way to crows nest :)
[23:15] <garyvdm> "So late it's brunch" - Ha Ha +1
[23:21] <lifeless> jml: are you still on leave?
[23:33] <igc> morning
[23:33] <mwhudson> igc: hello
[23:36] <igc> hi mwhudson!
[23:38] <mwhudson> igc: i still need to reply to that mail about bzr-svn
[23:38] <mwhudson> but basically i think we need to talk to jelmer a bit
[23:39] <garyvdm> Hi igc
[23:39] <igc> mwhudson: cool. I have 800 emails to start the day so I'm not missing it. :-)
[23:39] <igc> hi garyvdm
[23:40] <igc> garyvdm: it looks like jam has been playing with Qt tree models. Is he aware of your stuff yet?
[23:40] <garyvdm> I don't know.
[23:40] <garyvdm> igc: What's jam doing?
[23:42] <igc> garyvdm: not sure exactly - fixing bugs maybe?
[23:42] <igc> garyvdm: https://code.edge.launchpad.net/bzr-explorer
[23:59] <garyvdm> igc: lp:~jameinel/bzr-explorer/wt_model very much duplicates the work I've done. - I'll send jam an email.
[23:59] <igc> garyvdm: thanks


[07:06] <poningru> where are we doing UWN?
[07:07] <rjian> can someone give me the link of the UNWN?
[07:07] <rjian> i mean UWN
[07:07] <rjian> :)
[07:14] <poningru> https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue31
[07:21] <rjian> poningru: do it still more article?
[07:22] <poningru> clarify
[07:22] <rjian> i mean can i still add article on the community news?
[07:23] <Madpilot> the UWN Monster is always hungry.
[07:27] <poningru> yeah dude
[07:27] <poningru> add away
[07:22] <tuxcrafter> hello guys is this good english?  So I want to create a wiki for system for ubuntu to upload my special reviews! Can someone help me create a good wiki layout
[08:18] <tuxcrafter> I want to have my personal ubuntu wiki to have a menu to my review and bechmark system
[10:18] <tuxcrafter> i am going know let me now if someone can help with wiki i will be on the meetings irc
[10:18] <tuxcrafter> bye


[16:05] <kees> \o
[16:12] <kees> *crickets*
[16:18] <infinity> o/
[16:18]  * stgraber waves
[16:19] <infinity> Hi chair.
[16:19] <mdeslaur> hi stgraber
[16:19] <infinity> kees: You around?
[16:20] <infinity> mdeslaur: I'll sort out recreating the meeting schedule on the calendar, just need kees to give me a preferred address for the invite.  For the rest of us, I'll use our canonical first.last addresses.
[16:21] <mdeslaur> infinity: ack
[16:21] <stgraber> #startmeeting TB
[16:21] <meetingology> Meeting started Tue Jun 21 16:21:14 2016 UTC.  The chair is stgraber. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:21] <meetingology> Available commands: action commands idea info link nick
[16:21] <mdeslaur> infinity: I suggest marking the dumbass as read-only
[16:21] <stgraber> #topic Action review
[16:21] <stgraber> ACTION: infinity to follow up with maas SRU exception
[16:21] <infinity> stgraber: Defer. :(
[16:21] <stgraber> ACTION: infinity to document the new Docker SRU process
[16:21] <infinity> And defer.  And also defer for the next.
[16:21] <stgraber> ok :)
[16:22] <stgraber> ACTION: mdeslaur to look into flavour CVE tracking
[16:22] <mdeslaur> stgraber: defer please
[16:22] <infinity> The seed/maint-check one, I need to tackle before the point release, though.
[16:25] <stgraber> #topic Scan the mailing list archive for anything we missed (standing item)
[16:25] <infinity> All I see is Budgie, which is well-handled on the list.
[16:25] <stgraber> not seeing anything which wasn't addressed on list
[16:25] <stgraber> #topic Check up on community bugs (standing item)
[16:25] <stgraber> nada
[16:25] <stgraber> #topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)
[16:25] <stgraber> infinity: that's you
[16:25] <infinity> Sure is.
[16:26] <infinity> Backup, kees.
[16:26] <stgraber> #topic AOB
[16:26] <infinity> Other than the calendar being deleted, I have no OB.
[16:26] <infinity> I'll fix that shortly.
[16:27] <stgraber> trying to log into the wiki to update the agenda... this thing isn't getting any faster
[16:28] <stgraber> #endmeeting
[16:28] <meetingology> Meeting ended Tue Jun 21 16:28:18 2016 UTC.
[16:28] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting-2/2016/ubuntu-meeting-2.2016-06-21-16.21.moin.txt
[16:28] <mdeslaur> thanks stgraber
[16:28] <mdeslaur> thanks everyone


[16:36] <Zurk> Hi ppl
[16:36] <Zurk> I need help in ubuntu phone plz
[16:44] <PaulW2U> Zurk: hi there, this channel is for feedback/questions during live broadcasts. maybe try joining #ubuntu-touch ?
[17:08] <Zurk> Ok thanks


[12:21] <kedar_apte> Jammy's point release is simply awesome
[12:21] <kedar_apte> kudos to the team.. thanks
[12:38] <bittin> https://i.imgur.com/lhT9GNp.png kinda hard to read the text, when its behind a picture, having some spare time today for the first time in 2 months so testing the new 22.10 installer again
[16:05] <luna__> #freebsd,#centos,#ubuntu-server,#ubuntu-desktop,#ubuntu,#kernel,#bsd,##bsd,#unix,##unix,#freebsd,#fsfe
[16:06] <luna__> sorry missed /j
[16:06] <ogra> now we at least know where to find you 😉
[16:07] <luna__> :p


[02:04] <cpsalvestrini> Hi
[02:04] <cpsalvestrini> I have a question
[02:05] <cpsalvestrini> how can i make my pc run with the performance governor while it's plugged to ac power and with the ondemand governor while it's running on batteries?
[02:07] <pochu> cpsalvestrini: gnome-power-manager is your friend ;)
[02:08] <cpsalvestrini> ok let me look for it on synaptic...
[02:09] <cpsalvestrini> o wait... i already have it, but i have to manually assign governors when i change from battery to AC
[02:13] <cpsalvestrini> heloo? ne1?
[02:15] <pochu> cpsalvestrini: there is an option in the applet: you can say: when I'm on battery, I want this, an when AC, I want that :)
[02:18] <cpsalvestrini> ummm... ive tried, there is no such an option... looking @ prefs right now
[02:20] <pochu> cpsalvestrini: please, type my nick when you write ;)
[02:20] <pochu> cpsalvestrini: which ubuntu version do you have?
[02:21] <cpsalvestrini> pochu, i have edgy eft
[02:21] <pochu> cpsalvestrini: ok, do you have the g-p-m in the applet?
[02:22] <cpsalvestrini> pochu: yes, i do, it's a battery
[02:22] <pochu> cpsalvestrini: right click>preferences
[02:22] <pochu> then: On AC power | On Battery Power :)
[02:22] <pochu> that's all :)
[02:23] <cpsalvestrini> pochu, i have it as you say, but my governor is still ondemand
[02:23] <cpsalvestrini> even when i plug in the ac cord
[02:24] <pochu> cpsalvestrini: don't know. maybe you should restart... maybe it doesn't work fine in edgy
[02:24] <pochu> I use Feisty :D
[02:24] <cpsalvestrini> pochu i hear you
[02:28] <cpsalvestrini> that's precisely why i wanted to make a script that i can daemonize to properly detect my ac adaptor state and switch governors for me
[02:30] <pochu> cpsalvestrini: which laptop do you have?
[02:30] <cpsalvestrini> pochu, i got a toshiba satellite
[02:30] <pochu> cpsalvestrini: tri "acpi -V" and look if the output is right
[02:31] <pochu> with AC and with battery
[02:31] <pochu> and see if the charge level works fine
[02:31] <pochu> however, I think g-p-m doesn't use acpi
[02:31] <pochu> but I'm not sure
[02:31] <pochu> I didn't get g-p-m working well with Edgy
[02:32] <pochu> now with Feisty it works very better :)
[02:32] <cpsalvestrini> lol good for you pochu
[02:32] <pochu> https://wiki.ubuntu.com/?action=fullsearch&context=180&value=laptop+toshiba+satellite&titlesearch=T%C3%ADtulos
[02:33] <pochu> cpsalvestrini: look for your model
[02:33] <pochu> maybe you can find some trips there
[02:33] <pochu> :)
[02:35] <cpsalvestrini> ok pochu i found a model close to mine
[02:35] <cpsalvestrini> my battery charge is working properly
[02:36] <pochu> cpsalvestrini: with g-p-m?
[02:36] <cpsalvestrini> no, with the acpi -V
[02:36] <pochu> oh
[02:36] <pochu> that's fine
[02:36] <pochu> but does g-p-m show the battery level fine?
[02:36] <pochu> both when charging and when running with battery
[02:37] <cpsalvestrini> yeah it does pochu
[02:37] <pochu> cpsalvestrini: wooh!
[02:37] <pochu> cpsalvestrini: you are lucky :)
[02:37] <cpsalvestrini> but i think that somewhere along the way g-p-m forgets to switch governors
[02:38] <pochu> cpsalvestrini: you can try to run it in a terminal: maybe then you will see any error messabe
[02:38] <pochu> message*
[02:39] <cpsalvestrini> pochu, no error msg
[02:39] <pochu> "gnome-power-manager --verbose"
[02:39] <pochu> did you do "--verbose"?
[02:41] <cpsalvestrini> pochu i did
[02:41] <pochu> ok
[02:41] <cpsalvestrini> i think i found something @ forums
[02:42] <pochu> that's fine
[02:42] <pochu> is it useful?
[02:42] <pochu> sure it will be better than me ;)
[02:44] <cpsalvestrini> i think, let me try
[03:04] <cpsalvestrini> yay! done pochu
[03:04] <cpsalvestrini> now it works like i want :)
[03:05] <cpsalvestrini> well im off
[06:59] <pochu> bug 1


[00:56] <Bashing-om> Wild_Man: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue574 up for acceptance.
[03:46] <guiverc> Bashing-om, release schedule for dingo is thursday (18th) so 'next week' in general community news should say "last this week"
[03:48] <Bashing-om> guiverc: Good catch ! .. will correct when I remove "WIP" .// Do you expect to be around tomorrow eve to do the socials ?
[03:48] <guiverc> that'll be a bit late... it's monday arvo already; we usually publish early tuesday my local time  :)   yeah is your answer
[03:49] <guiverc> (i haven't finished my read thru - i'll do it as I can..)
[03:50] <Bashing-om> guiverc: :) .. I keep forgetting the Aussie in you :P
[03:51] <guiverc> :)
[04:18] <guiverc> Bashing-om, Ubuntu Ratings/Reviews   s/are are/are/  (ie. remove the double-word)
[04:20] <Bashing-om> guiverc: Noted too :)
[04:22] <guiverc> in Disco Disco (19.04) Release Candidate testing  there's another "released next week" however should this be dropped completely; duplicate of disco final freeze first notice (just different wording)
[04:22] <guiverc> ^ those two are in hub
[04:23] <Bashing-om> guiverc: Noted .
[04:27] <guiverc> https://plus.google.com/+UbuntuWeeklyNewsletter  needs to be removed  (and from skeleton too!)
[04:28] <Bashing-om> guiverc: K - will do that also :)
[04:28] <guiverc> my read thru is complete anyway; you want to remove g+ from skeleton.
[04:30] <guiverc> skeleton/template https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/IssueTemplate
[04:32] <guiverc> change made Bashing-om  (g+ shouldn't re-appear in subsequent issues)
[04:32] <Bashing-om> guiverc: My my you are feelinng industrious :P
[05:13] <guiverc> Bashing-om, minor ones edited (/next/this/ & /are are/are/ & /g+//  but didn't touch  hub.disco.rc,testing /next/this/OR duplicate/drop?
[05:14] <Bashing-om> guiverc: Lemme look and see what you see :P
[05:18] <Bashing-om> guiverc: As the hub summary has amplified testing info - I would like to keep it. tsimonq2 Also has an announcemnet but adds nothing that is not already covered.
[05:20] <Bashing-om> guiverc: Yeah agreed ,, the "next week " should be amended to "this week". - but next week is the authors words.
[05:21] <guiverc> yep - I wondered about keeping too, also if next/this really applies (b/c of Apr.. 18th specific mention)
[05:21] <guiverc> I'm happy with the wording as is b/c of date mention
[05:24] <Bashing-om> guiverc: Well, we could make it explicit that "next" is from the author as by [next] ??
[05:25] <guiverc> i'm not really a fan of "Apr... 18th"  -- but it's a direct quote so I ignored it...  why I left that alone & didn't touch it with my barge pole :)
[07:50] -SwissBot:#ubuntu-news- ::Security:: Episode 28 @ https://ubuntusecuritypodcast.org/episode-28/
[18:57] <Bashing-om> Pulling "WIP" and editing "next" too.
[20:03] <Bashing-om> M/L is away .. doing the forum post next.
[20:06] <Bashing-om> Forum posting is done - re-directs next.
[20:17] <Bashing-om> re-directs also done. Pending is posting to the social medias :)
[21:15] <guiverc> Want me to push #574 fridge?  (I need a 2nd)
[21:16] <Bashing-om> guiverc: Yeah .. All looks good - :)
[21:18] <guiverc> :)    thanks Bashing-om i'll take your response as my 2nd once I finish clearing spam on fridge
[21:18] <guiverc> we've got offers for someone to help write (author stuff) - from a diy solar panel... interested?
[21:18] <Bashing-om> guiverc: Works for me to be that 2nd -for what that is worth.
[21:19] <Bashing-om> guiverc: Always interested on a means to lighten/enlarge our load :)
[21:19] <guiverc> krytarik & tsimonq2 felt I didn't need to worry about 2nd due to regularly schedule for uwn - but fridge rules say it so I like it...
[21:20] <Bashing-om> guiverc: I like sticking to a known good procedure :)
[21:21] <guiverc> :)
[21:25] <guiverc> http://fridge.ubuntu.com/2019/04/15/ubuntu-weekly-newsletter-issue-574/
[21:28] <guiverc> I'll do social media posts later.. time for bird feed...
[21:28] <Bashing-om> guiverc: Fridge looks good :)
[21:33] <Bashing-om> Bot confirmtion that the Fridge is posted :)
[21:45] -SwissBot:#ubuntu-news- ::Planet:: The Fridge: Ubuntu Weekly Newsletter Issue 574 @ http://fridge.ubuntu.com/2019/04/15/ubuntu-weekly-newsletter-issue-574/
[21:50] <guiverc> mewe & tweet done.
[21:51] <Bashing-om> guiverc: :) clear now to wipe Gdoc574 ? We start all over again ?
[21:52] <guiverc> i was looking for my high-tech exercise book (passwd) to log into fb - not done yet..
[21:52] <Bashing-om> guiverc: Excuse me for rushing :(
[21:53] <guiverc> (now to look for my phone..)  but yeah you can wipe .. i won't use it & it's out-of-date anyway
[21:53] <guiverc> (we have the wiki)
[21:54] <Bashing-om> guiverc: K - on your say-so I do :)
[21:55] <guiverc> fb now done too :|
[22:01] <Bashing-om> Anddd .. we do UWN575 :)
[23:15] <Wild_Man> All done?
[23:16] <guiverc> yep :)   and thanks Wild_Man
[23:16] <Wild_Man> Thanks guys another, job well done!
[23:16] <Bashing-om> Wild_Man: We do UWN575 now :P
[23:18] <Wild_Man> WOOT!
[23:19] <guiverc> fyi:  i'll be unable to put 19.04 to fridge till very late friday (my local)... my passion play committment is higher priority (spel?) for me so I won't be available when I expect 19.04 to finally be released...  I can be a pre-2nd if acceptable before-hand (???)
[23:22] <Wild_Man> We announce when 19.04 comes out?
[23:22] <Wild_Man> It is our responsibility
[23:23] <guiverc> Wild_Man, http://fridge.ubuntu.com/2018/10/18/ubuntu-18-10-cosmic-cuttlefish-released/  - but it's a ubuntu-news team responsibility;  not just uwn
[23:25] <Wild_Man> guiverc, I see, I will be busy that day until late, it will be the 19th UTC time by the time I am here
[23:26] <guiverc> (Wild_Man they're a bit more work than uwn; source is ML post which is all text; so all formatting is added...)  - it'll get done when we're available/when we can..
[23:27] <Wild_Man> guiverc, is it a copy and paste? or we have to right up the summary?
[23:28] <guiverc> we copy/paste ... only the bottom paragraph is added but no writing, just insert name/team/date etc in correct places (from a prior one.. 50% of time taken is looking for ML post itself!)
[23:31] <guiverc> (okay ~10-20% of time is looking for post..)
[23:31] <Wild_Man> guiverc, okay if I get back before you and get to it I will give it a go


[03:08] <ScottK> Right.  So now that I fixed the bug in clamav where the test suite didn't actually run, turns out the existing ppc64el binaries probably don't work.
[03:08] <ScottK> Removing them wouldn't be a real regression and I've no idea about fixing it.
[03:08] <ScottK> Thoughts?
[03:08] <ScottK> Sorry.  Meant that for -devel.
[12:04] <sergiusens> can someone check this? https://bugs.launchpad.net/ubuntu/+bug/1282966 need to figure out if I logged it right
[12:04] <ubot2`> Launchpad bug 1282966 in Ubuntu "[FFe] Sync golang-go-dbus 1~bzr20140217-1 (universe) from Debian unstable (main)" [Undecided,New]
[12:06] <cjwatson> processed
[12:07] <cjwatson> no idea what John Kim was thinking but it was obviously nonsense ...
[12:09] <sergiusens> thanks
[16:50] <jamespage> !regressionalert
[16:50] <ubot2`> Factoid 'regressionalert' not found
[16:51] <infinity> jamespage: Wrong channel for that.
[16:51] <jamespage> infinity, yeah - I noticed :-)
[16:52] <jamespage> doing it in the right place now
[18:56] <rsalveti> infinity: mind checking bug 1289455?
[18:56] <ubot2`> Launchpad bug 1289455 in Ubuntu "[FFe] Including kernel packages for Nexus 5" [Undecided,New] https://launchpad.net/bugs/1289455
[19:43] <Noskcaj> Can someone look at bug 1282937 please?
[19:43] <ubot2`> Launchpad bug 1282937 in xfburn (Ubuntu) "FFe: Please package xfburn 0.5.0" [Undecided,New] https://launchpad.net/bugs/1282937
[20:05] <ScottK> infinity: ^^^ if you're still around - that's the exact change from Debian that fixed it in Trusty.
[20:33] <ScottK> OK, so maybe Adam's onto his next flight.  If any other SRU team member is around, I'd appreciate a look at the saucy check SRU I mentioned above.  It's blocking me backporting the current clamav and I'd really like to get that done.
[20:39] <stgraber> ScottK: accepted
[20:46] <ScottK> stgraber: Thanks.
[22:05] <ScottK> stgraber: I've verified the check SRU by rebuilding a package that failed before.  I'm not sure how much sense letting it sit and age makes.  The only way that will result in testing happening is if someone else uploads an SRU/backport that happens to use check's .pc file.  I'd be tempted to push it out.  Your call though since I'm not acting with my SRU hat on here.
[22:06] <stgraber> yeah, I'm fine with that, will release it now
[22:07] <stgraber> there you go
[22:12] <ScottK> Thanks.
[23:54] <bdmurray> slangasek: I uploaded an ubuntu-release-upgrader SRU to the saucy queue if you are reviewing today...
[23:55] <slangasek> bdmurray: looking
[23:56] <bdmurray> also any idea why release.tar.gz.gpg is slow to be created?
[23:56] <bdmurray> http://archive.ubuntu.com/ubuntu/dists/trusty/main/dist-upgrader-all/current/
[23:56] <slangasek> hum, that seems like it shouldn't happen
[23:57] <bdmurray> looking at the saucy one there is about a 10 minute delay
[23:57] <slangasek> no idea why... what populates the rest of the dir?
[23:59] <bdmurray> I think its DistUpgrade/build-dist.sh


[03:25] <lukehasnoname> Evening gents
[08:45] <pitti> bonjour seb128
[08:45] <seb128> hello pitti!
[08:45] <pitti> seb128: FYI, doing the ekiga 3 update ATM
[08:45] <seb128> cool, thanks
[08:47] <seb128> grrr at xulrunner breaking $webbrowser, brb
[09:23] <seb128> lool: hi, do you still need the evince hildon patch? it has been disabled some time ago and nobody complain but there is still a copy in the package I'm wondering if it should stay there
[09:27] <seb128> lool: I think we stopped using it because it was using the hildon fileselector changes and that was not working in intrepid
[10:07] <pitti> seb128: argh, ekiga 3 forgets *all* configuration settings from 2 :(
[10:08] <seb128> pitti: urg, upstream deserves some kicking there
[10:08] <pitti> it starts with the wizard, doesn't know my SIP numbers in evo any more, no call history any more, etc.
[10:08] <pitti> so I'm not sure at all whether I should upload this now
[10:09] <seb128> could you try to figure if that's an upstream choice or a bug?
[10:09] <seb128> we are not likely to do the upstream work there so if that's a choice we can decided to stay on the current version for ever or upload the new one
[10:12] <pitti> seb128: I'll file some bugs upstream, let's see
[10:12] <seb128> ok
[10:14] <pitti> seb128: using @ekiga.net numbers doesn't even work any more
[10:14] <pitti> gah
[10:41] <pitti> seb128: ok, done, and mentioned the upstream bugs in bug 274085
[10:41] <seb128> pitti: thanks
[10:48] <huats> morning everyone
[10:49] <seb128> hello huats
[10:49] <huats> hey seb128
[11:23] <lukehasnoname> What package involves the top menus in Gnome?
[11:23] <seb128> lukehasnoname: what do you mean exactly?
[11:26] <lukehasnoname> well,
[11:27] <lukehasnoname> I don't exactly know where to start, but I very strongly prefer the "fedora" style of the top menus, where the preferences and system menus are broken into smaller groups of similar tasks
[11:28] <lukehasnoname> and just for kicks I was wondering what packages are involved in fixing that, so that I could "patch" the issue I have on my own
[11:30] <seb128> lukehasnoname: gnome-menus has the layouts and the applications .desktop set their own categories then so you might need to change those too
[11:32] <lukehasnoname> thanks, I'll check and see if that is what I want
[11:32] <lukehasnoname> I really should go to bed though
[11:32] <lukehasnoname> it's 5:30am and I have class at 10
[12:36] <kagou> Hi
[12:38] <seb128> hey kagou
[14:27] <lool> seb128: Thanks for the headsup, I think we're using plain evince gtk for now for the reason you described
[14:27] <lool> seb128: ideally, we'd reenable it with an evince-hildon build, just removing the hildon-fm part, but we can do that anytime
[14:28] <seb128> lool: does it make easier if we keep the patch copied in the debian directory somewhere meanwhile?
[14:29] <lool> seb128: I don't understand
[14:29] <lool> seb128: You mean you propose to put the patch somewhere?
[14:29] <lool> seb128: Anywhere is fine
[14:30] <seb128> lool: the current package has the patch copied in the debian directory but not used since it didn't apply and we didn't want to block the update, so we copied it out of the patches directory
[14:30] <lool> seb128: Oh right, just rename it to .patch.disabled if you like
[14:30] <seb128> that's what we did
[14:31] <seb128> the question was whether we should keep it under this name or if we can drop it
[14:31] <seb128> ie, will it be useful when you try to hildonize it again
[14:31] <lool> seb128: It's easiest to find it like this, but if it's a pain, remove it
[14:32] <seb128> no it's not, I was just wondering if you planned to hildonize it again some day
[14:32] <seb128> I'll keep it
[14:32] <seb128> lool: otherwise I've been looking at syncing pygobject and pygtk on debian
[14:32] <seb128> did you try to build the new pygtk?
[14:32] <lool> seb128: Let me check
[14:33] <lool> seb128: BTW I'm not supposed to do distro stuff this week
[14:33] <seb128> the make checks breaks there because it tries to access the su recently-used
[14:33] <lool> seb128: Yeah, I recall that testsuite failure
[14:33] <lool> seb128: I didn't look into it, but I made the testsuite not fail the build
[14:34] <lool> seb128: I didn't merge any of the late pygtk/pygobject work to debian though
[14:34] <lool> Too much in a hurry back then
[14:34] <seb128> lool: ah, I didn't know, there is no hurry those will likely wait next week anyway because debian bumped the python version to 2.5 which will force to rebuild eveything which uses python2.4-gobject
[14:34] <seb128> and there is a CD planned for this week
[14:34] <lool> I see
[14:34] <seb128> anyway enough distro questions for you for now then, thanks for replying ;-)
[14:36] <lool> happy to help :)
[14:36] <lool> (It's ok to answer short questions, just can't start any real distro work)
[14:48] <seb128> pedro_: you closed bug #83326 too quickly, the crash is a gnome-keyring one, they dupped the upstream bug wrongly or reassigned to the wrong component
[14:49] <pedro_> seb128: ok looking at it
[14:50] <pedro_> seb128: i'll re open it and re assign the upstream one
[14:50] <pedro_> seb128: thanks!
[14:50] <seb128> pedro_: thank you ;-)
[14:58] <seb128> fta: are you still interested to look at the cairo update?
[15:31] <asac> seb128: hi ... do you know anyone from upstream we could bribe to take a look at the at-spi patch from gnome bug 558028  (lp 278095)?
[15:33] <seb128> asac: hello, no I don't really know the a11y contributors, you should try asking to themuso rather
[15:33] <asac> seb128: yeah did so i -devel. just thought you might know more ;)
[15:34] <seb128> was worth asking but I don't ;-)
[15:52] <seb128> mvo: bug #297362
[15:53] <seb128> mvo: would it be possible to filter out those errors? or autoduplicate rather
[15:53] <seb128> that's a dpkg bug or something?
[15:53] <james_w> would a bug pattern work?
[15:54] <seb128> james_w: aren't bug pattern specific to a source or binary component?
[15:54] <james_w> not sure, sounds likely though
[15:56] <mvo> seb128: I will add it
[15:57] <seb128> grrrrrr, xulrunner stucked again, how can we ship such crappy softwares
[15:57] <seb128> need to restart
[16:01] <seb128_> re
[16:01] <seb128_> mvo: thanks
[17:06] <asac> seb128: xulrunner? during what use case?
[17:07] <asac> flash? or general epiphany bustage?
[17:07] <seb128> asac: still the same issue I gave you valgrind logs about during the hardy cycle
[17:08] <seb128> asac: it sometimes crash or hang when you close it
[17:08] <asac> ok crash.
[17:08] <seb128> no, crash is alright
[17:08] <seb128> sometime it hangs
[17:08] <seb128> and blocks any other new instance
[17:09] <seb128> the stacktrace looks similar when it hangs
[17:11] <seb128> I think I read on some debian bug that the next xulrunner upload will fix a similar issue
[17:11] <seb128> let's see if it's fixed this cycle ;-)
[17:11] <asac> seb128: fixed upstream or in debian?
[17:11] <asac> let me search for the bug
[17:12] <seb128> the debian maintainer wrote in a bug that the next xulrunner upload to debian should fix the issue
[17:12] <seb128> dunno if the fix is an upstream one or a debian specific change though
[17:17] <asac> hmm buglist of xulrunner in debian is quite short
[17:18] <seb128> the bug is one assigned to epiphany-browser, I would have read the comments otherwise, I just read pkg-gnome bugs there
[17:18] <seb128> but there was no useful detail
[17:19] <asac> seb128: would be grateful for a bug id ;)
[17:19] <asac> no pending bugs in epiphany-browser atm
[17:19] <seb128> asac: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504441
[17:34] <asac> seb128: a bit strange. the crash has a line number upstream doesnt have in nsThreadUtils.cpp
[17:34] <asac> looked at debian diff.gz and it seems they have a tentative fix
[17:34] <asac> that would make the file match that line number again
[17:35] <asac> but that means the fix doesnt work
[17:35] <asac> http://paste.ubuntu.com/73407/
[17:35] <seb128> they didn't do any upload since they added the comment though
[17:35] <asac> a bit strange because the crash is a null deref
[17:35] <seb128> which would suggest the change has not been uploaded yet
[17:36] <asac> yeah. must be
[20:02] <pitti> if I have a gconftool --dump output, how can I feed that back into gconf?
[20:15] <pitti> found it (--load)
[21:08]  * calc thinks he might be getting an ear infection :\
[21:09] <calc> never had one of those before though so not quite sure what it feels like


[11:57] <tjaalton> tseliot: there's some race condition bugging nvidia users, see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053
[12:31] <tseliot> tjaalton: the problem is probably somewhere between Gdm and X11. I doubt that I can find it, as I can't reproduce it. Adding a "sleep 1" will probably do the trick, and I might have gpu-manager generate that on hybrid systems
[13:19] <tjaalton> alright


[01:34] <mhall119> nigelb: ping
[01:34] <mhall119> wakey wakey, it's Friday and you said you'd work on summit
[01:37] <mhall119> nigelb: https://code.launchpad.net/~mhall119/summit/fixes-814375/+merge/68764
[01:37] <mhall119> that's the last of the ones causing 500 errors on summit.u.c
[02:58] <nigelb> mhall119: Friday *evening*
[02:59] <nigelb> Ksplice acquired by Oracle and closed off unless you pay for Oracle support. I am sad.
[09:21] <daker> nigelb, http://i.imgur.com/gR1gY.png
[09:31] <nigelb> daker: Its *beautiful* ~
[09:31] <nigelb> !
[10:01] <YoBoY> daker: for a smartphone theme ? (looks great btw :) )
[10:02] <daker> yep
[10:02] <YoBoY> the  ← → are for next and past meetings ?
[10:03] <daker> pagination
[10:03] <daker> YoBoY, http://i.imgur.com/3j7Mq.png
[10:07] <YoBoY> next step the android app ? :)
[10:08] <daker> well actually we have just a read only API
[11:19] <cjohnston> mornin
[11:30] <cjohnston> nigelb: where are the summit mps?
[11:50] <cjohnston> mhall119: what is this series of errors all about
[11:50] <cjohnston> nigelb: did IS have anything to say about it when you asked yesterday
[11:54] <nigelb> cjohnston: No. Please ask again.
[11:54] <nigelb> cjohnston: what mps?
[11:54] <cjohnston> You said that today you were working on Summit
[11:54] <nigelb> cjohnston: Yes, in my free time. I'm at work now.
[11:55] <cjohnston> blah
[12:06] <daker> cjohnston, mhall119, nigelb  do you think we need a mobile version of LTP ? http://i.imgur.com/3j7Mq.png
[12:06] <cjohnston> no
[12:07] <nigelb> daker: Personally, I think it would rock.
[12:07]  * nigelb kicks cjohnston
[12:07] <nigelb> I thought a while back about having an android appp.
[12:07] <cjohnston> i just think its overboard
[12:07] <nigelb> cjohnston: No its not.
[12:08] <nigelb> Everyone has a phone. Its nice to see the guest list when you're at the venue
[12:08] <nigelb> or the map on the way.
[12:08] <daker> nigelb, we only have a read only API
[12:08] <nigelb> daker: *Now* I remember why I wanted a read-write API :D
[12:08] <nigelb> BUt really, the mobile app can be read only.
[12:08] <nigelb> Just display where you're headed, who's coming to that event, etc.
[12:09] <cjohnston> why not just use the ical
[12:09] <nigelb> ical just sucks as an interface, that's all.
[12:24] <YoBoY> since we are using a theme based on 960.gs can't we just extend it and use adapt.js who have a mobile part ? ( http://adapt.960.gs/ )
[14:37] <mhall119> nigelb: it's evening
[14:38] <cjohnston> mhall119: do you want the channel moderated?
[14:38] <mhall119> no
[14:38] <mhall119> it's going to be very informal
[14:39] <nigelb> o/
[14:39]  * cjohnston thinks nigelb needs to start putting up some MPs
[14:40] <mhall119> nigelb: can you please review my summit MP so my inbox will stop blowing up
[14:40] <nigelb> mhall119: will do.
[14:40] <mhall119> thank you sir
[14:40] <nigelb> cjohnston: I still think we should let mhall119's inbox blow upthough :P
[14:40] <cjohnston> nigelb: make him fix the bug that is making our inbox blow up first
[14:40] <nigelb> exactly!
[14:40] <mhall119> nigelb: cjohnston blows it up often enough without summit's help
[14:41] <mhall119> cjohnston: it's not a bug, it's a system failure, and I can't do anything about tha
[14:42] <nigelb> mhall119: I'm confused.
[14:42] <nigelb> Shouldn't meeting names be unique?
[14:43] <nigelb> Isn't that what we use for urls for meeting page?
[14:43] <mhall119> they are a non-unique field in the database
[14:43] <mhall119> nigelb: yes, that's what this fix is all about, the meeting page URL
[14:43] <mhall119> meeting names are *not* unique
[14:43] <mhall119> they aren't even required
[14:43] <nigelb> ah, adding a slug, thereby uniqifying the url
[14:44] <mhall119> I'm not adding a slug
[14:44] <cjohnston> mhall119: im gonna file an rt to get all community maintained sites put onto their own server so we can pick versions and not have to worry about other crap blowing our stuff up
[14:44] <mhall119> I'm adding the meeting ID to the URL
[14:44] <nigelb> yeah, adding ID *to* the slug
[14:44] <mhall119> cjohnston: cranberry pretty much is the community site's server
[14:44] <nigelb> well, not slug
[14:44] <nigelb> url
[14:44]  * nigelb fails today
[14:44] <mhall119> yes, to the URL
[14:44] <mhall119> the slug is just for show now
[14:44] <nigelb> gimme a minute to run the tests
[14:45] <mhall119> yay tests!
[14:45] <nigelb> I wonder if I should get tarmac to run the tests.
[14:45] <nigelb> cjohnston: Unfortunately, I can't give you isntant gratification for tarmac.
[14:45] <mhall119> that's something to bring up in about 15 minutes in -classroom
[14:45] <cjohnston> !fail
[14:45] <ubot4> Factoid 'fail' not found
[14:46] <nigelb> Nope, its because if you launch tarmac when one is already running it explodes.
[14:46] <cjohnston> add a check
[14:46] <nigelb> well, I feel its not worth it. Tarmac runs every 1 hour and its not mission critical anyway.
[14:47] <mhall119> let's promote tarmac to project manager, then it'll be mission critical
[14:47] <nigelb> if tarmac is the only user with commit access, it becomes mission crticical
[14:48] <cjohnston> i thought we setup tarmac for 30 minutes
[14:49] <nigelb> right, 30 minutes. I forgot. Just rechecked, its 30 mins
[14:50] <mhall119> but I want my branch landed *now*
[14:50] <cjohnston> +1
[14:50] <nigelb> mhall119: You should patch launchpad. It takes 4 hours for anything.
[14:50]  * mhall119 stomps his feet
[14:51] <cjohnston> nigelb needs to fix the bug in lp that he told me 3 weeks ago he would fix
[14:51] <nigelb> cjohnston: Won't touch it for a while. I'm getting mentoring for another bug :)
[14:51] <cjohnston> i dont care!
[14:51] <nigelb> I grabbed a chance to get mentoring when it turned up.
[14:53] <cjohnston> you could fix my bug in an hour or two
[14:54] <nigelb> Well, no.
[14:54] <cjohnston> yes
[14:55] <cjohnston> just add a toggle, display, no display
[14:55] <nigelb> ^ add toggle.
[14:55] <nigelb> that's the problem
[14:55] <nigelb> I'm fairly sure that's a new db field.
[14:57] <mhall119> Ronnie: daker: care to join us in #ubuntu-classroom?
[14:57] <Ronnie> mhall119: ill join
[14:58] <mhall119> was daker going to be able to join us?
[15:00] <cjohnston> i think he was
[15:01] <cjohnston> I dont be
[15:01] <cjohnston> newz2000: we are having a class on writing tests if your interested in #ubuntu-classroom
[15:04] <cjohnston> Its wonderful to be back in Maryland" and people go nuts.. wtf?
[15:07] <nigelb> cjohnston: huh?
[15:07] <cjohnston> The community-organizer in-chief is talking
[15:08] <nigelb> cjohnston: TV?
[15:08] <cjohnston> ya
[15:08] <nigelb> ah
[15:14] <mhall119> because DC is so far from Maryland
[15:14] <cjohnston> ;-)
[15:14] <cjohnston> lets see... well.. the line is how wide? hehe
[15:15] <cjohnston> crap.. i still suck at talking
[15:19] <cjohnston> I still wanna know why Michael Moore, Warren Buffet, and Obama haven't opened up their check books and sent back the $ from the tax breaks they get since they "want to pay more"
[15:23] <daker> awe sorry mhall119
[15:26] <mhall119> daker: it's not too late to join
[15:28] <daker> i am there
[15:45] <cjohnston> :-(
[15:59] <mhall119> nigelb: have you done anything with model_mommy?
[16:00] <nigelb> mhall119: I took a break fro summit after that.
[16:00] <nigelb> Today I'm playing with vagrant.
[16:00] <nigelb> I think i told you before, it lets you create vms
[16:06]  * cjohnston nominates mhall119 to be the test writer
[16:06] <mhall119> everybody is a test writer
[16:06] <cjohnston> unless your not done, your test fails
[16:09] <mhall119> do you already have the fix in place?
[16:11] <cjohnston> ?
[16:11] <cjohnston> me?
[16:11] <cjohnston> yes
[20:02] <cjohnston> nigelb: https://code.launchpad.net/~chrisjohnston/summit/etherpad/+merge/68901
[20:02] <cjohnston> are you home yet?
[20:29] <mhall119> cjohnston: why remove those last 2 summit items?
[20:29] <mhall119> - [summit-hackers] Automatically clear cache when the data it contains changes: TODO
[20:29] <mhall119> - [summit-hackers] List track lead information (name, photo, etc): TODO
[20:29] <cjohnston> bugs
[20:29] <mhall119> huh?
[20:30] <cjohnston> one of them was already a bug report, the other i created a bug report
[20:30] <cjohnston> linked both
[20:30] <mhall119> but, won't they not show on status.u.c now?
[20:30] <cjohnston> http://status.ubuntu.com/ubuntu-oneiric/group/topic-oneiric-community-web-projects.html
[20:30] <cjohnston> ctrl+f LP:
[20:32] <cjohnston> :-)
[22:30] <cjohnston> whats up with nigelb skipping out on working on summit
[22:43] <mhall119> dunno, it's like he's gotten himself a social life or something
[22:49] <cjohnston> mhall119: should we talk to the lp people about that bug or is there something we can do
[22:49] <mhall119> we have talked to them, I think daker_ lead that
[22:49] <cjohnston> ok
[22:50] <mhall119> I think the conclusion was "yeah, that's a bug, we're going to fix it sometime soon"
[23:35] <cjohnston> mhall119: https://code.launchpad.net/~chrisjohnston/summit/tl on trunk with the new migrations, I Get NoReverseMatch: Reverse for 'summit.schedule.decorators.inner' with arguments '('',)' and keyword arguments '{}' not found.


[00:21] <astroo-> Ubuntu's Secure Boot support vulnerability threatens even Windows PCs  http://www.pcworld.com/article/3026346/linux/ubuntus-secure-boot-support-isnt-secure-and-threatens-even-windows-pcs.html
[21:57] <astroo-> ola pessoal


[13:37] <Odd_Bloke> meena: OK, nice!  So I think what you've produced there is closer to what we would have part way (or perhaps most of the way, I haven't looked at the exact set of things you've "migrated") through this migration process.  I haven't fully read through Ryan's comment yet (I was off yesterday), so I'll do that today and perhaps see if I can propose an initial structure for discussion.
[17:21] <blackboxsw> rharper: Odd_Bloke our debian/control depend on pyflakes (python2-version) anymore?
[17:22] <blackboxsw> it seems like we should be dropping that. pkg dep right? https://github.com/canonical/cloud-init/blob/ubuntu/devel/debian/control#L11
[18:52] <lucasmoura> Hi everyone, just a quick question about https://bugs.launchpad.net/cloud-init/+bug/1456277 . The ec2 mirrors should only be used by ec2 instances, right ? Or is there any other scenario that I should still enable them ?
[19:05] <lucasmoura> My idea here will be to enable those mirror only if the datasource platform_type is ec2, but I don't know if that is too restrictive
[19:12] <powersj> lucasmoura, I think in general AWS would be happy if only instances in their cloud use their mirrors
[19:12] <rharper> powersj: not sure but I don't think they are accessible from outside aws, no ?
[19:12] <rharper> it's internal ips that are mapped
[19:13] <powersj> http://us-west-2.ec2.archive.ubuntu.com/ubuntu/
[19:13] <Odd_Bloke> blackboxsw: Huh, I'm very surprised that hasn't come up in in Py2 removal, but perhaps Build-Depends aren't checked in the same way.  Yeah, looks like that should be pyflakes3 now.
[19:13] <rharper> powersj: heh
[19:14] <Odd_Bloke> I _believe_ that the Azure mirrors use in-cloud-only DNS servers so that only in-Azure instances will resolve the Azure mirrors to the Azure instances, so perhaps you're thinking of that, Ryan?
[19:15] <Odd_Bloke> lucasmoura: I'm not sure that bug is applicable any longer: `nslookup foobar.ec2.archive.ubuntu.com` gives me NXDOMAIN (whereas `nslookup us-east-1.ec2.archive.ubuntu.com` does return IP addresses).
[19:18] <Odd_Bloke> The "any subdomain will resolve" logic has moved to *.clouds.archive.ubuntu.com, which resolves to our mirrors by default instead of EC2's.
[19:23] <lucasmoura> Odd_Bloke, I think I am missing something, wouldn't it be possible for another cloud provider to set up their availability zone to a similar pattern than ec2 and enable the ec2.archive.ubuntu.com/ubuntu/ mirror ?
[19:26] <Odd_Bloke> lucasmoura: You're absolutely right, I misread the report initially, my mistake.
[19:28] <lucasmoura> Odd_Bloke, No worries. I will enable that mirror only for ec2 instances
[19:28] <lucasmoura> Thanks everyone for the help :)
[19:28] <Odd_Bloke> lucasmoura: I do worry that some cloud deployments may have configured their mirrors on the assumption that the EC2 pattern will always be searched.  (i.e. They have a `us-east-1` region, and they have their internal DNS return their internal mirrors when `us-east-1.ec2.archive.ubuntu.com` is resolved.)
[19:30] <lucasmoura> Odd_Bloke, makes sense. But is there a way to know that this kind of configuration is expected ? I mean is there any info on the datasource that might suggest that ?
[19:34] <Odd_Bloke> Nope, unfortunately.  So we need to think a little bit about how we want to release this change.  My initial thought is that this is _fairly_ easy to workaround: if you're hitting a problem as a result of this then you must already have some internal DNS configuration, so adding us-east-1.clouds.archive.ubuntu.com to resolve to your mirrors should be possible.
[19:35] <Odd_Bloke> (Actually, you could also hit a problem if you rely on the use of the EC2 mirrors but have firewalled off the Ubuntu mirrors.  Again, the workaround is to change your existing configuration, so shouldn't be too hard to deploy a workaround.)
[19:37] <Odd_Bloke> So I wonder if this is another case where we shouldn't be backporting the behaviour to current Ubuntu releases, but should change it going forward?
[19:40] <lucasmoura> Yes, I agree that it makes sense to change it only going forward. Should we support this change using the feature flags falcojr is implementing ?
[19:43] <Odd_Bloke> That's a good question: should this be configurable or not?
[19:51] <lucasmoura> I guess it shouldn't be, but I don't know if by doing non-configurable I would generate a headache on downstream package maintainers with they want to enable the ec2 mirror lookup. I know it would be still possible to edit this using patches, but it would be harder to find it in the code
[20:03] <Odd_Bloke> Sorry, let me rephrase: I think we _at least_ want to use a feature flag to capture the two different behaviours.  The question I'm asking is: should we allow this behaviour to be configurable at runtime by users (in which case it would be better as a configuration option than a feature flag)?
[20:19] <blackboxsw> Odd_Bloke: right, I think https://github.com/canonical/cloud-init/pull/373 is the first upload we've tried after the official drop of pyflakes
[20:19] <blackboxsw> *from the archive
[20:19] <blackboxsw> which looks like it happened about a month ago
[20:19] <blackboxsw> in groovy
[20:21] <Odd_Bloke> Oh, OK, so I guess this did get caught by Py2 removal, just later removal than I assumed. :p
[20:21] <blackboxsw> so lucasmoura and falcojr I added and edited the a comment response about what testing we look for  to validate a release. What I caught was that sbuild barked with a missing dependency error. when I tried to run `sbuild-it ../out/cloud-init_20.2-30-g8bcf1c06*dsc`
[20:22] <lucasmoura> Odd_Bloke, Now I see it. I think the best approach is allowing this to be configurable at runtime by users. But how should we proceed in making this configurable ? I initially thought about adding it to cloud.cfg, but the user can interact with it somehow ?
[20:23] <blackboxsw> I think this is the last step to validate that we can in fact upload a new-upstream-snapshot to the devel release. I pushed the changeset for a follow up review https://github.com/canonical/cloud-init/pull/373/files#diff-d837a1c17de0268bcea321239ddbed47
[20:24] <blackboxsw> lucasmoura: mentioned that he had a different debian/changelog in his review of 373. I think tomorrow I'd like to walk through that new-upstream-snapshot creation if we could to see what diffs you were seeing lucasmoura.
[20:25] <Odd_Bloke> lucasmoura: So presumably we will have this new behaviour enabled by default in groovy.  Under what circumstances would we want users to be able to switch back to the old behaviour?
[20:25] <Odd_Bloke> (Apologies for the Socractic method I'm employing here. ;)
[20:29] <lucasmoura> blackboxsw, I made a mistake when I reviewed that. Originally I thought that changelog was auto-generated, but after commenting that I spotted the differance, I realized that there is a commit that updates it
[20:30] <lucasmoura> So I don't think I have spotted anything unusual, I was just forgot that the changelog is not produce automatically as shown in the PR
[20:30] <blackboxsw> ahh; ok. that works. ok then I think we are fine here. I'll have a couple of other prs for folks to review in a moment dropping pyflakees from debian/control on all the other ubuntu/* branches we continue support for downstream releases
[20:43] <lucasmoura> Odd_Bloke, hahah no problem. But what about if we create a new config on apt configure module that enables and disables ec2 mirrors ?
[20:49] <lucasmoura> In this cc_configure_module function https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_apt_configure.py#L946 we can see if the ec2 mirror is disabled and filter out the mirrors
[20:52] <lucasmoura> We just need to guarantee that this config will always be true for ec2 instances, but I don't know if I config modules should perform actions based on the type of instance we are running
[21:04] <Odd_Bloke> lucasmoura: You may also want to look at https://github.com/canonical/cloud-init/blob/master/cloudinit/distros/__init__.py#L845-L848
[21:09] <lucasmoura> Yes, I have seen it when I was trying to understand how the mirrors were parsed from the cloud.cfg file. Do I still don't get your suggestion, do you think we alter the regex to not set the ec2_region ? Do we mean that we should allow this regex to be configurable ?
[21:13] <Odd_Bloke> lucasmoura: Sorry, give me a few minutes to finish up my response to Ryan's networking refactor comment, then you can have my full attention.
[21:13] <lucasmoura> Odd_Bloke, no worries
[21:39] <ACHLO> https://youtu.be/QokZbqwcHwc
[21:41] <Odd_Bloke> lucasmoura: OK, so "a few minutes" was evidently optimistic.  I don't really have this code in my brain at the moment (though I have touched it recently), shall we hop on a video call and pair for a bit tomorrow so we can investigate it together?
[21:42] <lucasmoura> Odd_Bloke, Okay, no problem
[22:00] <Odd_Bloke> rharper: meena: Just dropped a long response to Ryan's comment into https://github.com/canonical/cloud-init/pull/363 (enjoy the read ;)
[22:04] <rharper> Odd_Bloke: thanks!
[23:48] <sodapop> I'm trying to append to profile.d this line-> declare -x PATH=$PATH:$JAVA_HOME/bin
[23:48] <sodapop> can I somehow write it as is and not the expanded


 I'm going to have a big brunch/lunch with friends today, and then there's another party Saturday for my little cousin's 1st birthday
[15:25] <waltman> I hope MutantTurkey survived the day
[16:15] <InHisName> I went to ONE store for one item,   Radio Shack  32GB mem stick $10.    Fast and quick at 9:30am.  Still had some stock.
[16:34] <InHisName> anyone got a spare   1GB PC3200 DDR CL3 400MHz  184 pin memory for desktop ?
[17:26] <TheLordOfTime> InHisName, DDR?  not DDR2 or DDR3?
[17:26] <TheLordOfTime> why would you still need DDR?
[20:52] <jedijf> waltman: noooooo they got you
[20:52] <jedijf> again