[05:52] <nealmcb> funny you all should mention the reatek.  That was the first problem I had with the lemur: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/585938
[05:55] <nealmcb> ToyKeeper: so what happened a month ago?  Hungary ftw!
[05:55] <nealmcb> joey - join the party!
[09:41] <ToyKeeper> nealmcb: Oh, what happened is I got hired.
[09:42] <ToyKeeper> I'm not working directly on Ubuntu though; I'm doing infrastructure and support for the ISD team.
[14:48] <nealmcb> ToyKeeper: nice!
[17:36] <nealmcb> Headed out to the Farmer's market, then to Panera.  Hope we have more than 2 for our local Ubuntu Global Jam :)
[17:37] <nealmcb> ...which is at 13:00 today, Panera - 29th st mall in Boulder
[20:21]  * nealmcb looks around for folks at panera....
[20:30] <nealmcb> w0jrl: joining the ubuntu global jam?
[20:31] <w0jrl> nealmcb, yes, I wanted to see what this is all about.
[20:32] <w0jrl> I am in Denver, so this is the only way I can join.
[20:33] <nealmcb> w0jrl: is that Nick?
[20:33] <w0jrl> My name is Jeremy
[20:34] <nealmcb> welcome to the jam.  Did you see the link I posted earlier on how to contribute?
[20:35] <nealmcb> what sorts of things are you interested in?
[20:35] <w0jrl> I have not read it yet. I have been working a few minor bugs with the Orca screen reader.
[20:36] <nealmcb> sweet.  Which bugs?
[20:36] <w0jrl> main sugesting ways to the list to make orca work with natty
[20:39] <w0jrl> at the moment, orca is very unstable in unity. in my testing I couldn't access things like the applications menu or the notification ariea. There are alot of keyboard shortcuts missing.
[20:41] <nealmcb> yum.  I hope that doesn't happen with many apps....  I Haven't tried natty yet.
[20:43] <nealmcb> hopefully that's because screen readers are doing unusual things....
[20:43] <w0jrl> Word to the wise, try it in a VM if you can.
[20:45] <w0jrl> Well, part of the issue is that events that need to be passed to orca aren't geting there.
[20:49] <w0jrl> for example, the new launcher (as I understand it gos down the left side of the screen) is not accessible at all. This is a real bummer for me because I am a blind user, and need items on that bar to be spoken.
[20:52] <nealmcb> Yeah - that sounds like a pretty big issue.  Are there any alternatives to Orca, or is really a Unity problem?
[20:52] <nealmcb> Welcome, Nick!
[20:53] <nealmcb> 3 of us now - w0jrl (Jeremy) also
[20:53] <Guest95671> Thanks finally figured out how to join an IRC, haha.
[20:53] <nealmcb> great
[20:53] <Guest95671> Hi Jeremy
[20:54] <Guest95671> Hello Neil; you can disregard my last email obviously
[20:54] <nealmcb> (Neal)
[20:54] <Guest95671> Oh, sorry Neal
[20:54] <w0jrl> I am also trying to figure out a way to create an all-in-one scanning/ocr solution that is accessible. The default scanning tool in ubuntu is nice, but there is no way to tell what I scanned, or even if I have the sheet placed on the bed correctly.
[20:55] <w0jrl> hello
[20:55] <nealmcb> :)
[20:56] <nealmcb> w0jrl: Sounds like another great place to contribute!
[20:56] <Guest95671> What is a good open source IRC client. I had to 'evaluate mIRC' in windows and want to join with my Ubuntu system next time
[20:57] <w0jrl> If you all use smilies, will you put a text description beside them please? Orca has no idea what they are.
[20:57] <nealmcb> I've used both irssi (for folks that like fast flexible text-oriented stuff) and pidgin
[20:58] <w0jrl> empathy does well with irc.
[20:58] <Guest95671> Oh, I didn't even think of Pidgin....wow.
[20:58] <Guest95671> I just installed Ubuntu again on my new laptop and haven't quite had the time to configure everything
[20:58] <w0jrl> I am using empathy at the moment.
[20:59] <nealmcb> w0jrl: do you mean graphical smilies in something like pidgin, or text smilies like the :) smiley
[20:59] <w0jrl> gui
[21:00] <w0jrl> graphival
[21:01] <Guest95671> You gents going to be here for a bit?
[21:01] <w0jrl> yeah
[21:02] <Guest95671> I need to get my little one to sleep, takes me about an hour.
[21:02] <nealmcb> I may head home soon
[21:02] <w0jrl> I'm guessing there no one at your location neal?
[21:03] <Guest95671> Sorry to not keep your physical company there, Neal
[21:04] <Guest95671> gotta take care of naptime, ha. see you folks in a bit.
[21:04] <nealmcb> Right - just me at Panera.
[21:04] <w0jrl> I wish I could be there as well, but bus travel from Denver can be a pain in the ***.
[21:07] <nealmcb> I can believe that.  And the virtual world can work really well :)
[21:07] <w0jrl> yes
[21:13] <nealmcb> Well, I'm gonna walk home now.  Such a beautiful day.
[21:14] <nealmcb> (in case you missed that...) Well, I'm gonna walk home now.  Such a beautiful day.
[21:14] <w0jrl> ok
[21:15] <w0jrl> If you get bavk on, I'll be here.
[21:15] <nealmcb> Thanks again for joining in and helping out, w0jrl!   Hope to meet you in person some day
[21:15] <nealmcb> Great
[21:15] <w0jrl> I hope to meet you in person as well.
[21:16] <nealmcb> And my irc client is on a proxy at home, so I'll see what is posted while I'm gone
[21:16] <w0jrl> neet! Do you login using ssh?
[22:28] <Guest95671> Hey, sorry. I'm back now
[22:39] <nealmcb> ahhh - just missed them....


[00:52] -queuebot:#ubuntu-release- New binary: linux-signed-oracle [amd64] (xenial-proposed/main) [4.15.0-1030.33~16.04.1] (kernel)
[05:41] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle-5.0 [amd64] (bionic-proposed) [5.0.0-1008.13~18.04.1]
[05:41] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle-5.3 [amd64] (bionic-proposed) [5.3.0-1007.8~18.04.1]
[07:48] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle [amd64] (xenial-proposed) [4.15.0-1030.33~16.04.1]
[08:59] -queuebot:#ubuntu-release- New binary: linux-signed-azure-5.3 [amd64] (bionic-proposed/main) [5.3.0-1008.9~18.04.1] (no packageset)
[09:14] -queuebot:#ubuntu-release- New binary: linux-signed-gcp-5.3 [amd64] (bionic-proposed/main) [5.3.0-1009.10~18.04.1] (no packageset)
[09:24] -queuebot:#ubuntu-release- Unapproved: python3.7 (eoan-proposed/main) [3.7.5-1ubuntu1 => 3.7.5-2~19.10] (core)
[10:18] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-edge [s390x] (bionic-proposed/main) [5.3.0-24.26~18.04.1] (kernel)
[10:19] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-edge [amd64] (bionic-proposed/main) [5.3.0-24.26~18.04.1] (kernel)
[10:19] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-edge [ppc64el] (bionic-proposed/main) [5.3.0-24.26~18.04.1] (kernel)
[10:19] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-edge [arm64] (bionic-proposed/main) [5.3.0-24.26~18.04.1] (kernel)
[10:19] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (xenial-proposed/main) [4.15.0-1064.69] (kernel)
[10:27] <cpaelzer> anyone around to accept strongswan in focals new queue?
[10:28] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (xenial-proposed) [4.15.0-1064.69]
[10:28] <cpaelzer> we had this as libcharon-standard-plugins already, Debian now accepted it but under the better name of libcharon-extauth-plugins
[10:28] <cpaelzer> so it isn't "so new" after all, but hangs there
[10:28] -queuebot:#ubuntu-release- New: accepted linux-signed-azure-5.3 [amd64] (bionic-proposed) [5.3.0-1008.9~18.04.1]
[10:28] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-edge [amd64] (bionic-proposed) [5.3.0-24.26~18.04.1]
[10:28] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-edge [ppc64el] (bionic-proposed) [5.3.0-24.26~18.04.1]
[10:28] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp-5.3 [amd64] (bionic-proposed) [5.3.0-1009.10~18.04.1]
[10:28] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-edge [s390x] (bionic-proposed) [5.3.0-24.26~18.04.1]
[10:28] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-edge [arm64] (bionic-proposed) [5.3.0-24.26~18.04.1]
[10:29] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle [amd64] (eoan-proposed) [5.3.0-1007.8]
[11:14] -queuebot:#ubuntu-release- New binary: php-illuminate-container [amd64] (focal-proposed/universe) [5.8.35-1] (no packageset)
[11:14] -queuebot:#ubuntu-release- New binary: php-illuminate-database [amd64] (focal-proposed/universe) [5.8.35-1] (no packageset)
[11:14] -queuebot:#ubuntu-release- New binary: php-robmorgan-phinx [amd64] (focal-proposed/universe) [0.9.2-2] (no packageset)
[11:14] -queuebot:#ubuntu-release- New binary: php-illuminate-support [amd64] (focal-proposed/universe) [5.8.35-1] (no packageset)
[11:14] -queuebot:#ubuntu-release- New binary: ratchetphp [amd64] (focal-proposed/universe) [0.4.1-3] (no packageset)
[11:15] -queuebot:#ubuntu-release- New binary: movim [amd64] (focal-proposed/universe) [0.14.1-6] (no packageset)
[11:15] -queuebot:#ubuntu-release- New binary: php-nesbot-carbon [amd64] (focal-proposed/universe) [1.27.0-2] (no packageset)
[12:14] -queuebot:#ubuntu-release- New binary: linux-signed-oracle [amd64] (bionic-proposed/main) [4.15.0-1030.33] (kernel)
[12:14] -queuebot:#ubuntu-release- New binary: linux-signed-oem-osp1 [amd64] (bionic-proposed/universe) [5.0.0-1030.34] (no packageset)
[12:41] -queuebot:#ubuntu-release- Unapproved: accepted python3.7 [source] (eoan-proposed) [3.7.5-2~19.10]
[14:08] <mdeslaur> how do we mark this test as known bad so that imagemagick can migrate? http://autopkgtest.ubuntu.com/packages/o/openscad/focal/s390x
[14:12] <seb128> mdeslaur, seems like it's fixed in the version from proposed, so get that to migrate?
[14:13] <seb128> mdeslaur, needs to fix https://launchpad.net/ubuntu/+source/openscad/2019.05-2/+build/17954217 for that though
[14:14] <mdeslaur> yeah, eww
[14:18] <mdeslaur> seb128: I'm a bit curious how the autopkgtest report says it tested 2019.05-2 when it FTBFS
[14:18] <seb128> mdeslaur, I've retried it, there is a similar upstream report which hints that the build hit a NOTENOUGHRAM issue
[14:18] <seb128> mdeslaur, it ftbfs of ppc64el only
[14:18] <seb128> on*
[14:18] <mdeslaur> oh! right
[14:19] <mdeslaur> seb128: thanks, I'll watch it
[14:19] <seb128> mdeslaur, np
[14:35] -queuebot:#ubuntu-release- New: accepted movim [amd64] (focal-proposed) [0.14.1-6]
[14:35] -queuebot:#ubuntu-release- New: accepted php-illuminate-database [amd64] (focal-proposed) [5.8.35-1]
[14:35] -queuebot:#ubuntu-release- New: accepted php-nesbot-carbon [amd64] (focal-proposed) [1.27.0-2]
[14:35] -queuebot:#ubuntu-release- New: accepted ratchetphp [amd64] (focal-proposed) [0.4.1-3]
[14:35] -queuebot:#ubuntu-release- New: accepted php-illuminate-container [amd64] (focal-proposed) [5.8.35-1]
[14:35] -queuebot:#ubuntu-release- New: accepted php-robmorgan-phinx [amd64] (focal-proposed) [0.9.2-2]
[14:35] -queuebot:#ubuntu-release- New: accepted php-illuminate-support [amd64] (focal-proposed) [5.8.35-1]
[14:46] <xnox> mdeslaur:  one can trigger openscad s390x test, with both imagemagick and openscad from proposed, then it will pass then it will migrate?
[14:47] <mdeslaur> xnox: is there a tool to do that?
[14:47] <xnox> mdeslaur:  hand editing the retry URL and appending &trigger=openscad/foo to it. I.e. i copied the retry url and tweaked it at the end https://autopkgtest.ubuntu.com/request.cgi?release=focal&arch=s390x&package=openscad&trigger=imagemagick%2F8%3A<IP_ADDRESS>%2Bdfsg-2.1ubuntu9&trigger=openscad/2019.05-2
[14:48] <mdeslaur> xnox: oh, cool, thanks
[14:48] <xnox> click that to submit the request
[14:48]  * xnox didn't submit it
[14:48]  * mdeslaur clicks away
[14:49] -queuebot:#ubuntu-release- New binary: qscintilla2 [s390x] (focal-proposed/universe) [2.11.2+dfsg-5] (no packageset)
[14:51] -queuebot:#ubuntu-release- New binary: qscintilla2 [i386] (focal-proposed/universe) [2.11.2+dfsg-5] (no packageset)
[14:52] -queuebot:#ubuntu-release- New binary: qscintilla2 [ppc64el] (focal-proposed/universe) [2.11.2+dfsg-5] (no packageset)
[14:53] -queuebot:#ubuntu-release- New binary: qscintilla2 [amd64] (focal-proposed/universe) [2.11.2+dfsg-5] (no packageset)
[15:01] -queuebot:#ubuntu-release- Unapproved: libvirt (bionic-proposed/main) [4.0.0-1ubuntu8.13 => 4.0.0-1ubuntu8.14] (ubuntu-server, virt)
[15:02] -queuebot:#ubuntu-release- New binary: qscintilla2 [armhf] (focal-proposed/universe) [2.11.2+dfsg-5] (no packageset)
[15:02] -queuebot:#ubuntu-release- Unapproved: libvirt (disco-proposed/main) [5.0.0-1ubuntu2.5 => 5.0.0-1ubuntu2.6] (ubuntu-server, virt)
[15:03] -queuebot:#ubuntu-release- New binary: qscintilla2 [arm64] (focal-proposed/universe) [2.11.2+dfsg-5] (no packageset)
[15:10] -queuebot:#ubuntu-release- New: accepted qscintilla2 [amd64] (focal-proposed) [2.11.2+dfsg-5]
[15:10] -queuebot:#ubuntu-release- New: accepted qscintilla2 [armhf] (focal-proposed) [2.11.2+dfsg-5]
[15:10] -queuebot:#ubuntu-release- New: accepted qscintilla2 [ppc64el] (focal-proposed) [2.11.2+dfsg-5]
[15:10] -queuebot:#ubuntu-release- New: accepted qscintilla2 [arm64] (focal-proposed) [2.11.2+dfsg-5]
[15:10] -queuebot:#ubuntu-release- New: accepted qscintilla2 [s390x] (focal-proposed) [2.11.2+dfsg-5]
[15:10] -queuebot:#ubuntu-release- New: accepted qscintilla2 [i386] (focal-proposed) [2.11.2+dfsg-5]
[17:16] <vorlon> Eickmeyer: eh, you're probably right that I didn't git push ubuntustudio-meta, I didn't notice that package was maintained in git considering most of the metapackages are not (the contents are primarily autogenerated from germinate)
[17:28] -queuebot:#ubuntu-release- New binary: odin [s390x] (focal-proposed/universe) [2.0.3-2] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: fontforge [s390x] (focal-proposed/universe) [1:20190801~dfsg-2] (ubuntustudio)
[17:32] -queuebot:#ubuntu-release- New binary: fontforge [amd64] (focal-proposed/universe) [1:20190801~dfsg-2] (ubuntustudio)
[17:33] -queuebot:#ubuntu-release- New binary: odin [ppc64el] (focal-proposed/universe) [2.0.3-2] (no packageset)
[17:34] -queuebot:#ubuntu-release- New binary: fontforge [i386] (focal-proposed/universe) [1:20190801~dfsg-2] (ubuntustudio)
[17:34] -queuebot:#ubuntu-release- New binary: odin [amd64] (focal-proposed/universe) [2.0.3-2] (no packageset)
[17:36] -queuebot:#ubuntu-release- New binary: fontforge [ppc64el] (focal-proposed/universe) [1:20190801~dfsg-2] (ubuntustudio)
[17:49] -queuebot:#ubuntu-release- New: accepted linux-signed-oem-osp1 [amd64] (bionic-proposed) [5.0.0-1030.34]
[17:49] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle [amd64] (bionic-proposed) [4.15.0-1030.33]
[17:50] <vorlon> Laney, seb128: I see that the Ubuntu desktop dailies have again exceeded the latest size limit.  Should the limit be raised again or does something need trimming?
[17:53] <seb128> vorlon, let me investigate before we raise it (but that's for tomorrow, I'm about to call it a day)
[17:53]  * vorlon nods
[17:53] <seb128> vorlon, thx for pointing it out
[17:54] -queuebot:#ubuntu-release- New binary: odin [armhf] (focal-proposed/universe) [2.0.3-2] (no packageset)
[17:54] <seb128> we should add some warning about that on our report page
[18:04] -queuebot:#ubuntu-release- New binary: fontforge [arm64] (focal-proposed/universe) [1:20190801~dfsg-2] (ubuntustudio)
[18:06] -queuebot:#ubuntu-release- New binary: fontforge [armhf] (focal-proposed/universe) [1:20190801~dfsg-2] (ubuntustudio)
[18:13] -queuebot:#ubuntu-release- New binary: odin [arm64] (focal-proposed/universe) [2.0.3-2] (no packageset)
[19:36] -queuebot:#ubuntu-release- New: accepted fontforge [amd64] (focal-proposed) [1:20190801~dfsg-2]
[19:36] -queuebot:#ubuntu-release- New: accepted fontforge [armhf] (focal-proposed) [1:20190801~dfsg-2]
[19:36] -queuebot:#ubuntu-release- New: accepted fontforge [ppc64el] (focal-proposed) [1:20190801~dfsg-2]
[19:36] -queuebot:#ubuntu-release- New: accepted odin [arm64] (focal-proposed) [2.0.3-2]
[19:36] -queuebot:#ubuntu-release- New: accepted odin [ppc64el] (focal-proposed) [2.0.3-2]
[19:36] -queuebot:#ubuntu-release- New: accepted fontforge [arm64] (focal-proposed) [1:20190801~dfsg-2]
[19:36] -queuebot:#ubuntu-release- New: accepted odin [amd64] (focal-proposed) [2.0.3-2]
[19:36] -queuebot:#ubuntu-release- New: accepted fontforge [i386] (focal-proposed) [1:20190801~dfsg-2]
[19:36] -queuebot:#ubuntu-release- New: accepted odin [armhf] (focal-proposed) [2.0.3-2]
[19:36] -queuebot:#ubuntu-release- New: accepted fontforge [s390x] (focal-proposed) [1:20190801~dfsg-2]
[19:37] -queuebot:#ubuntu-release- New: accepted odin [s390x] (focal-proposed) [2.0.3-2]
[19:48] -queuebot:#ubuntu-release- New binary: libixion [ppc64el] (focal-proposed/main) [0.15.0-2] (ubuntu-desktop)
[19:48] -queuebot:#ubuntu-release- New binary: libixion [s390x] (focal-proposed/main) [0.15.0-2] (ubuntu-desktop)
[19:49] -queuebot:#ubuntu-release- New binary: libixion [amd64] (focal-proposed/main) [0.15.0-2] (ubuntu-desktop)
[19:51] -queuebot:#ubuntu-release- New binary: libixion [armhf] (focal-proposed/main) [0.15.0-2] (ubuntu-desktop)
[19:51] -queuebot:#ubuntu-release- New binary: libixion [i386] (focal-proposed/main) [0.15.0-2] (ubuntu-desktop)
[19:53] -queuebot:#ubuntu-release- New binary: libixion [arm64] (focal-proposed/main) [0.15.0-2] (ubuntu-desktop)


[07:13] <MarwenDo> how r u doing Na3iL :)
[07:16] <Na3iL> Morning MarwenDo fine ty, yourself?
[12:18] <yreg> Hello guys !
[12:37] <elacheche> hey yreg
[13:17] <elacheche>  akaisora o/
[13:17] <akaisora> elacheche: hello o/
[13:17] <akaisora> how is it going?
[13:18] <elacheche> Hello there and welcome to #ubuntu-tn
[13:19] <akaisora> Thanks :D
[13:19] <elacheche> 1st time here!
[13:20] <akaisora> Yeah I knew the community but never got in touch really
[13:21] <elacheche> :)
[13:21] <elacheche> Can I help you with something or just taking a look :)
[13:23] <akaisora> Fun fact, i'm your friend "Computez Geekz" from facebook :D
[13:24] <elacheche> Oh! nice to know.. I don't (almost) use fb anymore.. x) I can't even go and check your profile right now becasue I autocencered it @work x)
[13:24] <elacheche> Yo Na3iL :) we have visitors :)
[13:26] <akaisora> What do you use? Twitter?
[13:27] <elacheche> mail twitter & irc
[13:27] <akaisora> Oh, there is also my friend yreg who new here as well :-)
[13:27] <elacheche> yep, he's afk I think
[13:28] <yreg> I am here
[13:28] <elacheche> Hello and welcome too :)
[13:28] <yreg> Thanks
[13:29] <Na3iL> Aww :D
[13:29] <Na3iL> Welcome akaisora and yreg
[13:29] <akaisora> thanks!
[13:30] <yreg> elacheche, Na3iL thank you both for the warm welcome !
[13:30] <elacheche> :)
[13:31] <yreg> I was looking the other day ffor ways to create **my own distribution** of ubuntu with alfresco, pentaho, imagemagic and few other softwares preinstalled
[13:32] <yreg> but failed to find any one on the main ubuntu channel to help with the 4 GB limitation while creating the iso
[13:32] <elacheche> Cool idea.. But that raises some questions..
[13:33] <yreg> already tried a few things to get mkiso create the bootable ISO with 6 Gb
[13:33] <elacheche> 1# What's the 4GB limitation you're looking for? 2# Why you're need a custom distro with those packages? 3# Is it for fun or production?
[13:33] <yreg> but the installation was hanging in an early stage (just after chosing an option on grub menu)
[13:34] <yreg> #1 appearently it is something related to some old RFC saying that an ISO should not exceed 4 GB in terms of size
[13:35] <elacheche> Oh, OK.. didn't knew that..
[13:36] <yreg> #1 I have a client, with a strict NO-INTERNET policy in his intranet and it is hell alot easier (or that was what I thought) to create a custom distribution with preinstalled and preconfigured packages
[13:37] <yreg> than having to fetch those packages and their dependencies manually, backup configuration, and restore it to my customers environment manually ...
[13:37] <yreg> s/#1/#2/
[13:38] <elacheche> I see.. That answers the 3rd question as well..
[13:38] <elacheche> OK, I have some ideas in mind
[13:38] <yreg> I did investigate the issue further
[13:39] <elacheche> But first, you're trying to get a Desktop version or a headless one?
[13:39] <yreg> and it turned out that µshell invoking the live system was unable to mount squashfs files that are larger than a certain limit (forgot what the limit was)
[13:40] <yreg> but when I try to mount the file on my own ubutu desktop it works like a charm
[13:40] <yreg> any would do
[13:40] <yreg> Ubuntu / Ubuntu-Server are both viable options
[13:40] <elacheche> Great! Then I can share my ideas :D
[13:41] <elacheche> Try to use a minimalISO to create your distro, that my ùake it smaller, did you tried this? if so I'm sorry x)
[13:42] <elacheche> Don't forget to rm /var/cache/apt/*
[13:43] <elacheche> Or you can install ubuntu on a vm(kvm), configure it then for your client, just configure a virtualisation server and use that VM..
[13:43] <yreg> no did not try it, but I got over the ISO size limitation as I managed to switch to mkiso and set a flag so it does not fail on +4Gb iso
[13:43] <elacheche> Or instead of that, you can clonezilla it, then restore that clone to the harddirve directly..
[13:43] <yreg> but I got stuck just after the boot menu
[13:44] <elacheche> Or, you can fiorget about VMs, and go for docker..
[13:44] <yreg> elacheche, I do not know why I did not think of cloning the hard drive
[13:45] <yreg> maybe I though it would eat my disk space like a beast !
[13:45] <yreg> LoL
[13:45] <yreg> Docker you say !
[13:45] <elacheche> Emm.. Clonezilla have good options afaik..
[13:46] <elacheche> Docker is cool, but need some practice to know what to do and what to NOT do (espacially that xD )
[13:46] <yreg> I barely convinced my customer to use ubuntu 14.04 instead of his OLD RedHat 7.0
[13:47] <elacheche> I know the stragle with old RHEL
[13:47] <yreg> 6.0**
[13:48] <yreg> They almost never update their systems
[13:48] <elacheche> :)
[13:49] <elacheche> Are in Germany ?
[13:49] <yreg> Nope, Tunisia
[13:49] <yreg> eGov project
[13:49] <elacheche> Oh! You're using the German frenode server
[13:49] <elacheche> x) sorry, I need an other coffee I guess :)
[13:50] <elacheche> BTW, what's with the no-internet policy?
[13:51] <yreg> if you are any where near Berges du Lac II, be my guest I would gladly discuss this project further with you on a good coffe :D
[13:51] <yreg> Security measure !
[13:51] <elacheche> I'm @Sousse :)
[13:52] <yreg> lucky you !
[13:52] <yreg> I will need to get back to work now !
[13:52] <elacheche> Hahaha I know :)
[13:52] <yreg> Thank you for sharing your thoughts with me
[13:53] <yreg> and have a nice day
[13:53] <elacheche> come back anytime to have chitchats :D
[13:53] <elacheche> Happy to share :)
[13:58] <akaisora> I knew the ubuntu-tn community was small, but never expected it to be this small ^^
[13:58] <elacheche> define "small" :(
[13:59] <akaisora> #define small
[14:00]  * akaisora ** thuglife **
[14:00] <elacheche> x)
[14:00] <akaisora> xD
[14:01] <akaisora> elacheche: what is your company's name?
[14:01] <elacheche> In here I'm part of the Ubutnu community :p
[14:02] <elacheche> BTW, it's not small.. but there is fiew active members.. :/ :(
[14:02] <elacheche> And too many fb members who won't contribute outside fb
[14:11] <akaisora> Yeah, sadly.
[14:20] <elacheche> yep :/
[14:20] <akaisora> i'll try to contribute whenever i get the chance :)
[14:32] <elacheche> :)
[18:22] <AkaiSora> hello


[00:50] <maxb> Does anyone use Bazaar to version Java projects built with Maven?
[01:18] <awilkins> maxb, I do
[01:18] <awilkins> maxb, Oh ,wait, I version the sources
[01:18] <awilkins> maxb, Not the outputs
[01:42] <offby1> maxb: geez, you're in every revision-control channel! :)
[03:56]  * igc lunch
[03:58]  * mwhudson stares at bzr for setting BZR_HOME to a unicode string in a test case
[04:03] <mwhudson> hmm, seems r4707.1.1 is at fault
[04:05] <idnar> nice
[05:38] <poolie1> igc, hi?
[05:38] <igc> hi poolie1
[05:38] <poolie1> hi
[05:38] <poolie1> i thought we could try to get sphinx going
[05:38] <igc> poolie1: +1 from me
[05:38] <poolie1> i just need to find where they installed this thing
[05:39] <igc> poolie1: 35067 is the rt# if that helps
[05:40] <poolie1> k
[05:40] <poolie1> i always get confused between pchroot schroot and dchroot :)
[05:41] <poolie1> ie 3 implementations of more or less the same thing
[05:41] <poolie1> anyhow i have the mail
[05:41] <lifeless> dchroot is now just wrapper of schroot
[05:42] <poolie1> heh
[05:42] <poolie1> I have no name!@escudero:/$ exit
[05:44] <poolie1> igc: so you should be able to run
[05:44] <poolie1> dchroot -c karmic
[05:44] <poolie1> then sphinx-build seems to work
[05:44] <poolie1> the environment is a bit rough and ready though - no /etc/passwd, hence the message i pasted above
[05:47] <igc> poolie1: so dchroot -d karmic works for me
[05:47] <poolie1> ok
[05:47] <igc> where/how do you want to build things?
[05:47] <poolie1> i'm just going to try going into a current checkout and building the docs there
[05:47] <poolie1> it builds them under my home directory at the moment
[05:47] <poolie1> but that's not available inside the chroot
[05:47] <igc> poolie1: can we start small?
[05:48] <igc> bzr+ssh://bazaar.launchpad.net/~bzr/bzr-alldocs/trunk/
[05:48] <poolie1> what do you have in mind?
[05:48] <igc> this is the wrapper site over doc.bazaar-vcs.org/en, ru and the other languages
[05:48] <poolie1> oh ok
[05:49] <igc> I just added the bzr team tracker to these a few minutes ago
[05:49] <poolie1> and how do i build things inside it?
[05:49] <poolie1> checked out to /srv/bazaar.canonical.com/doc/alldocs
[05:49] <poolie1> "team tracker"?
[05:49] <igc> pull the branch, then run the magic script ...
[05:51] <poolie1> http://doc.bazaar-vcs.org/alldocs/_build/en/  <--- woo
[05:51] <igc> poolie1: the magic script is build_sites.py as you probably seen by now
[05:51] <poolie1> yep, done, and the results are in that url
[05:52] <poolie1> it looks good to me, what do you think?
[05:52] <poolie1> is there meant to be an html file above the /en/ directory?
[05:53] <igc> poolie1: something not quite right ...
[05:53] <igc> did you get rev 26?
[05:54] <igc> poolie1: maybe we just need to reset the sym links to point to the new build locations?
[05:54] <igc> instead of into my home area?
[05:54] <poolie1> i do have r26
[05:55] <poolie1> which symlinks? there don't seem to be any in the tree
[05:56] <igc> poolie1: ok. (confused with other bits)
[05:56]  * igc keeps looking
[05:57] <poolie1> the other questions are: is:
[05:57] <poolie1> at what url do we eventually want this to appear
[05:57] <poolie1> and how should it mesh with the docs that are already there
[05:58] <igc> poolie1: ok. /en is a copy, not a link to the site
[05:58] <igc> so we could change that or ...
[05:58] <igc> change the build script to copy to the right place
[05:59] <igc> poolie1: I think linking is ok
[05:59] <poolie1> doc.b.o/en is the old version uploaded by you
[06:00] <poolie1> i haven't changed it yet
[06:00] <igc> poolie: answering your Qs ...
[06:00] <poolie1> as you said, small steps
[06:00] <igc> doc.b.o/en, doc.b.o/es, etc. all need to point into the area you just built
[06:00] <poolie1> ok
[06:00] <poolie1> what do we want to have at the top level of the site
[06:01] <poolie1> like under doc.b.o/
[06:01] <poolie1> no change for now?
[06:01] <igc> poolie1: right now, let's leave it as is
[06:01] <igc> poolie1: it's helpful for users wanting to find a particular version ...
[06:01] <igc> e.g. 2.0.0 when 2.0.1 is out
[06:02] <igc> the en/ru/etc pages don't reveal *every* old version, just the latest point release of old versions
[06:02] <poolie1> right
[06:02] <poolie1> how do they know which versions to link in?
[06:03] <poolie1> ideally they wouldn't have to be updated on every release
[06:03] <igc> poolie1: the en/etc pages link to logical names ...
[06:03] <igc> latest, test, development
[06:05] <igc> poolie1: I update the symlinks when new versions roll out currently
[06:05] <igc> (after rebuilding docs, uploading them, editing the cover sites, uploading them, etc.)
[06:05] <poolie1> ok
[06:05] <igc> (it's a pain)
[06:05] <poolie1> maybe we can automate that more separately
[06:05] <poolie1> so
[06:06] <poolie1> could you please login, run 'umask 2' to make things you touch group writable
[06:06] <poolie1> then move the en fr ja ru docs into old-sphinx
[06:06] <poolie1> and then we can try making symlinks into alldocs
[06:07] <igc> umask 2 done
[06:07] <igc> poolie1: en etc moved
[06:08] <igc> poolie1: you doing the new links?
[06:08] <poolie1> yes
[06:08] <poolie1> you'd just made the old ones unwritable by anyone else
[06:08] <poolie1> and i don't have sudo so i needed you to move them
[06:08] <poolie1> thanks
[06:09] <poolie1> k http://doc.bazaar-vcs.org/en/ looks good now?
[06:09] <igc> yep - sweet
[06:09] <igc> just tried View>Page Source and I see the new JavaScript
[06:09] <poolie1> how are you meant to reach the non-english versions?
[06:09] <poolie1> great
[06:09] <igc> links at bottom of page
[06:09] <igc> to other languages
[06:10] <igc> see them?
[06:10] <igc> all tested ok
[06:11] <igc> poolie1:^
[06:12] <poolie1> ah ok i see it
[06:12] <poolie1> i overlooked it
[06:12] <poolie1> imbn if it was in the footer on somewhere that's more clearly meta-content

[06:13] <poolie1> that looks good
[06:14] <igc> poolie1: so the next 3 simple ones are ...
[06:14] <poolie1> igc, the script that built the old documentation has some code to determine the right versions
[06:14] <poolie1> we could glue that in
[06:14] <igc> migration, plugins and explorer
[06:15] <poolie1> ok, they're separate trees?
[06:15] <igc> poolie1: by glue, you mean generate the version numbers current in bzr_alldocs_conf.py?
[06:15] <poolie1> right
[06:16] <igc> sure
[06:16] <poolie1> or to do something to make it non-manual
[06:16] <poolie1> are the migration, plugins and explorer things separate trees like this?
[06:16] <igc> sphinx may even let us see them on the command line if that helps
[06:16] <poolie1> i'm at spiv's house now and i need to go home from here in a sec
[06:16] <igc> yes, different trees
[06:16] <poolie1> i'm just going to setup a cronjab
[06:16] <poolie1> job*
[06:16] <igc> :-)
[06:16] <poolie1> could you mail me the branches?
[06:16] <igc> die cron die
[06:16] <igc> :-)
[06:17] <igc> sure
[06:17] <igc> thanks btw
[06:17] <igc> I'll email you now
[06:17] <igc> poolie1:^
[06:17] <poolie1> np, thanks for setting it up
[06:17] <igc> say hi to spiv
[06:17] <spiv> igc: hi :)
[06:18] <igc> poolie1: it looks good, it just fiddly to maintain
[06:18] <igc> this will help
[06:18] <igc> hi spiv!
[06:18] <poolie1> k cronjob seems to work
[06:19] <poolie1> now we'll see how many errors turn up when it really runs :)
[06:19] <igc> :-)
[06:55] <vila> hi al
[06:55] <vila> all even
[07:11] <Peng> Hi. :) Though I'm probably about to go AFK. :P
[08:04] <Glenjamin> hey guys, does anyone know a good way of getting an application shortcut to bzr explorer on mac os x?
[08:07] <vila> Glenjamin: send a patch ? :-D
[08:07] <Glenjamin> ?
[08:08] <vila> Glenjamin: kidding, try getting in touch with igc
[08:09] <vila> but his week-end is about to begin (Australian time zone), what do you want exactly ? A short-cut for an existing command or the ability to assign short-cuts from outside bzr explorer itself ?
[08:09] <Glenjamin> just a shortcut with an icon to run bzr explorer
[08:10] <Glenjamin> the guide recommends I make one and pin it to the dock, but doesn't say how to
[08:10] <vila> ohhh, that kind of short-cut, sry. I can't help here, I haven't installed bzr explorer on my mac
[08:18] <igc> Glenjamin: try emailing the bzr-mac list for input. See https://launchpad.net/~bzr-mac
[08:18] <Glenjamin> ah, ta -  I was just posting a question on the bzr-explorer page :)
[08:26] <igc> night all - have a good weekend
[08:27] <spiv> igc: g'night
[08:27] <vila> g'night Ian
[09:18] <leo> hello, looking for some help with loggerhead
[09:51] <Peng> Oh thank goodness leo left, I was just checking IRC before going to bed. :P
[14:56] <MTecknology> The location where I need to pull/push my branch changed. How can I tell bzr that this is where it should always pull/push instead of having that only work once.
[14:58] <vila> MTecknology: --remember ftw !
[14:58] <MTecknology> vila: thanks :)
[16:11] <bialix> hi GaryvdM
[16:11] <GaryvdM> Hi Alex
[16:11] <bialix> I can work on 0.14.5 today
[16:12] <GaryvdM> bialix: Cool - I just stared looking at it to.
[16:12] <bialix> 2 weeks ago we discussed what we want to backport from 0.15
[16:12] <bialix> I want to g through that list today
[16:12] <bialix> *go
[16:13] <bialix> feel free to mark any bug for backport
[16:13] <GaryvdM> Yes
[16:13] <bialix> cool
[16:13] <bialix> let's go :-)
[16:15]  * bialix likes bug-url command, thanks luks
[16:18] <visik7> anyone with bzr on windows ?
[16:18] <bialix> what?
[16:18] <visik7> I need to test a little thing
[16:18]  * sidnei raises hand
[16:18] <sidnei> i would have to restart though :(
[16:19] <visik7> what bzrlib.user_encoding returns ?
[16:19]  * bialix on windows but a bit busy
[16:19] <visik7> I mean the exact string
[16:19] <bialix> visik7: it returns ANSI encoding
[16:19] <visik7> yes but could you run it and tell my your ?
[16:19] <bialix> visik7: it depends on current user settings
[16:19] <visik7> I know
[16:19] <bialix> for me (Russian) it's cp1251
[16:19] <visik7> and is there a way to get this encoding without bzrlib ?
[16:19] <jam> visik7: I'm also on windows, what was the original question?
[16:20] <bialix> for US/Western Europe I believe it's cp1252
[16:20] <visik7> jam I'm tring to remove the bzr dependancies from a program that use bzrlib to get the current encoding
[16:20] <bialix> visik7: do you mean via python?
[16:20] <visik7> yes
[16:20] <jam> visik7: if you look at bzrlib/osutils.py it has the details of how we determine the encoding
[16:20] <jam> something like
[16:20] <bialix> look at the code
[16:20] <jam> import locale; locale.getpreferredencoding()
[16:21] <jam> though there is also
[16:21] <jam> sys.getfilesystemencoding()
[16:21] <jam> and stuff to determine the terminal encoding
[16:21] <visik7> thanks
[16:21] <jam> all different
[16:21] <bialix> hi jam
[16:21] <visik7> the FS enc is ok
[16:21] <jam> filesystem is usually 'mbcs', locale is usually latin-1, and terminal is cp???
[16:22] <bialix> latin-1 == cp1251?
[16:22] <bialix> cp1252, rats
[16:22] <visik7> bzrlib use terminal locale or fs ?
[16:22] <visik7> I look the code
[16:23] <jam> visik7: fs encoding for *filenames*, locale for the *content* of files (generally)
[16:23] <jam> and terminal for the way to format bytes for display on the screen
[16:23] <jam> of course, on reasonable systems *all* of those are "utf-8" :)
[16:23] <bialix> windows supports unicode for filenames, no need to use fs encoding, it's always mbcs anyway
[16:35] <bialix> GaryvdM: I think I've marked all bugs I know: https://launchpad.net/qbzr/+milestone/0.14.5
[16:37] <GaryvdM> bialix: cool - I'm going to to the tag one now
[16:37] <bialix> GaryvdM: I'm porting qsubprocess --bencode
[16:39] <GaryvdM> bialix: I did push uncommit commit push on lp:qbzr/0.14, so you may need to do pull --overwrite
[16:39] <GaryvdM> bialix: err - no - you beat me to the second push never mind
[16:39] <bialix> ok
[16:46] <jam> can a losa check out lp:~bzr-pqm/bzr/2.1.0b2 it was meant to be created from "lp:bzr" but it seems to be at revno 4668, when lp:bzr is at 4778 (about 110 revisions newer)
[16:46] <mthaddon> jam: sure
[16:46] <jam> spm created it for me last night, and I didn't notice until today
[16:46] <jam> mthaddon: if you want to just "bzr push" to force it to update, that would be fine with me
[16:46] <mthaddon> jam: from current lp:bzr ?
[16:47] <jam> mthaddon: yeah
[16:52] <mthaddon> jam: revno 4778
[16:52] <jam> thx
[16:52] <mthaddon> done
[16:55] <corp186> I accidentally pushed the wrong branch to a new lp branch
[16:56] <corp186> how do I revert the lp branch back to the initial state?
[16:56] <bialix> GaryvdM: I see there is all green now
[16:57] <bialix> rats
[16:57] <bialix> corp186: re-push with --overwrite flag
[16:57] <corp186> bialix: I get "No new revisions to push."
[16:58] <bialix> you wrote: corp186>	I accidentally pushed the wrong branch to a new lp branch
[16:58] <bialix> do you have copy of original "right" branch
[16:58] <bialix> ?
[16:58] <corp186> ahh, I see what you're saying
[16:58] <corp186> yeah
[16:58] <bialix> cd to "right" branch and push --overwrite
[16:59] <corp186> bialix: thanks, that worked
[17:00] <bialix> always happy to help (c) jam
[17:00] <bialix> :-)
[17:11] <GaryvdM> My irc is very lossy - I can only see in chatzilla, half of what I can see here: http://irclogs.ubuntu.com/2009/10/30/%23bzr.html
[17:12] <GaryvdM> And - messages that I have sent don't appear there. No wonder no one answers my questions some times.
[17:14] <bialix> Garyvdm: I've backport all revno I remember
[17:14] <bialix> I see you finished too
[17:14] <GaryvdM> Yes
[17:15] <GaryvdM> bialix: When you are idle, check this out: http://garyvdm.googlepages.com/out.ogv
[17:15] <GaryvdM> Bialix: rename in qbrowse/qcommit
[17:15]  * bialix opens link
[17:15] <GaryvdM> 1.1mb
[17:16] <bialix> Garyvdm: I'll wait till tomorrow morning to cut tarball, ok?
[17:16] <bialix> GaryvdM: what is ogv?
[17:16] <GaryvdM> Ok - I'm going to do some hacking  - on drag and drop move
[17:16] <GaryvdM> ogg video
[17:17] <GaryvdM> Best player on windows for that would be vlc
[17:17] <bialix> hmm, I hope K-lite codec pack knows how to play it
[17:18] <GaryvdM> Hi luks
[17:18] <bialix> GaryvdM: COOOOOOOOOOOOOOOOOOOOOL
[17:19] <GaryvdM> :-)
[17:19] <bialix> and how to move file? drag-n-drop?
[17:19] <GaryvdM> Yes - that's what I'm working on now.
[17:19] <luks> hey
[17:19] <bialix> oh, cool cool cool
[17:19] <bialix> heya luks
[17:20] <jelmer> hi *
[17:20] <jelmer> /topic Welcome in #qbzr ;-)
[17:20] <GaryvdM> And for --after - you will be able to select a missing, and a unversioned and chose mark as resolved
[17:20] <GaryvdM> Hi jelmer
[17:20] <bialix> heya jelmer
[17:20] <bialix> what's .topic?
[17:21] <bialix> what's /topic?
[17:21] <GaryvdM> Topic for #bzr is “Bazaar version control system | 2.0.1 and 2.1.0b1 are official! | try https://answers.launchpad.net/bzr for more help | http://bazaar-vcs.org | http://irclogs.ubuntu.com/”
[17:21] <GaryvdM>  /topic allows you to change that
[17:22] <bialix> ah, ok
[17:24] <bialix> jelmer: cool article about bzr-svn/git/hg
[17:25] <bialix> jelmer: we all hope on bzr-hg
[17:26] <bialix> GaryvdM: how you made that video?
[17:28] <GaryvdM> bialix: with gtk-recordMyDesktop
[17:28]  * bialix nods
[17:29] <GaryvdM> bialix: it very easy, but I think it is linux only.
[17:29]  * bialix nods
[17:33] <bialix> GaryvdM: everything ready to release, will do it tomorrow
[17:33] <GaryvdM> bialix: cool
[17:34] <bialix> I leave 0.16? for you
[17:34] <GaryvdM> bialix: I'm going to see where I can get to with move and rename, and release 0.16 on Sunday
[17:34] <GaryvdM> yes
[17:37] <jelmer> bialix: thanks
[17:37] <bialix> FTW!
[17:38] <bialix> if only there will be something like github or bitbucket but for bzr with reasonable small fee for private repos -- I'll be mostly happy
[17:43] <bialix> GaryvdM: do you have any codename for 0.16 in mind?
[17:44] <GaryvdM> bialix: Sorry - no
[17:44] <GaryvdM> Lots of work in the Tree view
[17:44] <GaryvdM> *TreeWidget
[17:45] <jelmer> bialix: whatever happened to the work that rocky burton was doing?
[17:45] <bialix> what's nice tree in your region?
[17:45] <bialix> jelmer: rocky burton? sorry, I don't follow
[17:46] <bialix> GaryvdM: what's nice tree in your region? tree you like?
[17:46] <GaryvdM> bialix: http://en.wikipedia.org/wiki/Acacia
[17:47] <GaryvdM> http://savannaenvironment.files.wordpress.com/2008/04/acacia.jpg
[17:48] <bialix> GaryvdM: Acacia grew and here too
[17:48] <bialix> so let's use its name?
[17:48] <GaryvdM> I see - was just reading the Wikipedia article.
[17:49] <bialix> but in my region it has white flowers
[17:50] <bialix> I'll add Acacia as codename to 0.16, ok?
[17:51] <bialix> GaryvdM ^
[17:51] <GaryvdM> Cool
[17:51] <bialix> :-)
[18:03] <GaryvdM> bialix: are you using trunk?
[18:04] <bialix> right now I'm testing 0.14.5
[18:04] <bialix> I'm switching between both from time to time
[18:04]  * bialix is very busy with my main work
[18:05] <GaryvdM> bialix: Sure, I understand
[18:05] <GaryvdM> bialix: I'm looking for feedback on the new directory grouping in qcommit.
[18:06] <bialix> ok, I'll switch and will test it these days
[18:20] <bialix> Garyvdm: ping
[18:21] <GaryvdM> pong
[18:21] <bialix> Garyvdm: recently I've discovered that qlog FILE don't show revisions where file was removed
[18:22] <bialix> e.g. if you re-add file later
[18:22] <bialix> the same with plain log though
[18:22] <GaryvdM> bialix: yes - know bug, same in log
[18:22] <vila> bialix: hmm, lovely codename :-) I love Acacias, they can smell so good at times...
[18:22] <bialix> heya vila
[18:22] <bialix> GaryvdM: there is already bug?
[18:23] <GaryvdM> bialix: I think so - trying to find it.
[18:23] <bialix> vila: I have a misteriuos plan according to which we will name all qbzr releases after trees
[18:23] <GaryvdM> bialix: bug 181520
[18:24] <vila> lol
[18:24] <bialix> vila: but sometimes it make sense to use something funny
[18:24] <vila> bialix: That's quite  appropriate, there so many branches there :)
[18:24] <bialix> GaryvdM: lol, it's my bug
[18:25] <GaryvdM> bialix: I'm sure I also log a dup...
[18:25] <bialix> GaryvdM: I mean: can we fix it for qlog or it depends heavily on bzrlib behavior?
[18:25] <bialix> vila: :-D
[18:25] <fullermd> Isn't acacia technically a bush, not a tree?
[18:25] <bialix> GaryvdM: I have feeling that we have fixed it in the past
[18:26] <GaryvdM> bialix: The method is similar for qlog and log, so if we fix it for one , then fixing it for the other is easy.
[18:26] <GaryvdM> bialix: It would be easy to fix, but it would be slower.
[18:26] <bialix> :-/
[18:27] <bialix> fullermd: wikipedia said it's a group of shrubs and trees
[18:27] <vila> fullermd: hmm, well, there was one in my parent's home garden, it was a tree, definitely :)
[18:27] <bialix> fullermd: I saw only trees in my city
[18:27] <bialix> there is a lot of acacias
[18:28] <bialix> slower is bad word
[18:29] <GaryvdM> bialix: Here is the bug I logged: bug 368976 That says it only happens log uses deltas, which happens if you do log dir, or log file -v
[18:30] <GaryvdM> Oh - sorry - thats a different bug.
[18:31] <bialix> GaryvdM: ok, so it's related to the fact file-graph missing deletion
[18:31] <bialix> GaryvdM: that bug looks ok
[18:32] <GaryvdM> bialix: no - Your bug is that it does not show the revision that removes the file. My bug is that if you remove, and re add a *dir*, it only shows the second bit of history, not the first
[18:33] <GaryvdM> bialix: My bug is the one that would be easy to fix, but it would be slower.
[18:33] <bialix> ah, sorry, I misread
[18:34] <bialix> anybody knows about undelete plugin?
[18:35] <GaryvdM> bialix: Your bug - I don't know how we could fix. (Except for looking at the inventory for every revision, which would be much much slower.)
[18:35] <bialix> GaryvdM: so, am I correct that this sort of info just missing in per-file-graph?
[18:36] <GaryvdM> bialix: yes
[18:36] <bialix> bad
[18:52]  * GaryvdM ventures out to seek food.
[19:28] <lau> hi, i am noobing here but any time i perform a modification on a file (local branch)
[19:28] <lau> i first have to bzr add before bzr commit ?
[19:32] <dereine> i need to replace lp: with the right url?
[19:32] <dereine> does someone know where lp points to?
[19:35] <Pilky> dereine: lp:project equates to bzr+ssh://bazaar.launchpad.net/~ownerOfMainBranch/project/mainbranchname
[19:35] <Pilky> dereine: eg lp:bazaarx equates to bzr+ssh://bazaar.launchpad.net/~bazaarx-dev/bazaarx/dev/
[19:35] <dereine> Pilky: thx
[19:36] <dereine> so for https://code.launchpad.net/~d7cx/d7cx-views/DRUPAL-7--3 it would be bzr+ssh://bazaar.launchpad.net/~d7cx/d7cx-views/DRUPAL-7--3 ?
[19:38] <Pilky> dereine: in theory, yes
[19:38] <dereine> Pilky: is there a  public commando from the bzr commando?
[19:39] <Pilky> hmm? not sure what you mean
[19:39] <GaryvdM> lau: Only the first time the file is committed.
[19:40] <corp186> How can I delete a tag in a remote repository?
[19:40] <corp186> I know no one else has cloned the branch yet
[19:41] <GaryvdM> corp186: bzr tag --delete
[19:41] <GaryvdM> corp186: Then bzr push
[19:42] <lau> thx GaryvdM, i have a scenario i do not clearly understand
[19:42] <lau> 1- i bzr update from a lp bzr repo
[19:42] <corp186> GaryvdM: I even used bzr push --overwrite, but it still didn't delete the tag
[19:42] <lau> 2- i modify 2 files from my working dir
[19:43] <lau> 3- i bzr commit to lp bzr repo
[19:43] <lau> 4- it commits my 2 modified files _+ 2 others files w/ MERGE-SOURCE in them
[19:44] <lau> what could be the root cause of the MERGE-SOURCE text in these 2 files ? w/o any
[19:44] <lau> error during the bzr update ?
[19:45] <GaryvdM> corp186: maybe try bzr tag --delete -d url/to/remote
[19:45] <dereine> Pilky: perhaps "bzr get_path lp:foo"  would return the bzr+ssh.... url from the project to check out
[19:46] <GaryvdM> lau: What is the url of the branch on lp?
[19:46] <Pilky> dereine: I don't there is an option, because if you're using bzr you should be able to just use the lp:foo path anywhere you need to
[19:46] <Pilky> dereine: what exactly are you needing the URL for?
[19:46] <corp186> GaryvdM: -d did the trick, thanks :)
[19:46] <lau> GaryvdM: it is a personal project i prefer not to tell ? i really think it is my fault because
[19:46] <lau> i am noobing here ...
[19:47] <dereine> Pilky: awesome, i just don't need to transfer the url, just give bzr branch the url, thx for the eye-opener
[19:47] <Pilky> dereine: yeah, anywhere there is a path you can pass in an lp:foo eg to branch bzr itself you'd type
[19:47] <Pilky> bzr branch lp:bzr mylocalbranch
[19:48] <dereine> Pilky: would it be able to define own shortcuts?
[19:50] <Pilky> dereine: I believe so, but I'm not sure how. I think it may require a plugin to be written
[19:50] <GaryvdM> dereine, Pilky: bzr-bookmarks
[19:51] <GaryvdM> https://launchpad.net/bzr-bookmarks
[19:51] <dereine> thx
[20:00] <lau> GaryvdM: i think know that it was old trash from my working tree
[20:01] <lau> these 2 files with some MERGE-SOURCE and TREE in them
[20:01] <lau> without any .BASE, .THIS or .OTHER
[20:01] <lau> was a old remanation from my working tree, does it make sense ?
[20:01] <GaryvdM> Yes
[20:01] <GaryvdM> lau: You can uncommit, remove the cruft, and then commit again
[20:02] <GaryvdM> lau: If you use qcommit, it will remember the commit message for you.
[20:03] <lau> yes i did that thx
[20:03] <lau> what are the tools i can use in order to prevent this happen again ?
[20:04] <lau> i mean old dirty stuff in my working tree that i commit inadvertently ?
[20:04] <GaryvdM> lau: read the diff before you commit?
[20:04] <lau> :) right ok
[20:05] <GaryvdM> lau: bzr will allways tell you if there was a conflict, and it has put in thoes merge things.
[20:05] <GaryvdM> lau: Many bzr commands to merges to the working tree: pull, update, merge, switch
[20:22] <GaryvdM> jam: ping
[20:27] <GaryvdM> If I have a list of paths, is there a easy way to get the path of the lca using a python, or bzrlib api?
[20:28] <jam> hey GaryvdM
[20:28] <GaryvdM> Hi jam
[20:28] <GaryvdM> jam: I wanted to ask you the question above.
[20:29] <GaryvdM> if I have ["a/b/c", "a/b/d", "a/c"] I want to get "a"
[20:29] <jam> GaryvdM: lca? Do you mean the minimal paths to include everything you specified?
[20:29] <jam> osutils.get_minimum_path_selection() IIRC
[20:29] <GaryvdM> yes
[20:29] <GaryvdM> Ah -cool
[20:30] <jam> it is used along with 'is_inside_any'
[20:30] <jam> this is to avoid passing the entire tree in for 'first commit' ?
[20:30] <GaryvdM> Thanks alot.
[20:30] <GaryvdM> jam: No - it for qbrowse, drag and drop move
[20:31] <GaryvdM> I need to work out of a selection of paths is ok for a move
[20:34] <GaryvdM> jam: this is ok: http://imagebin.ca/img/UH2_flra.png
[20:34] <GaryvdM> This is not ok: http://imagebin.ca/img/Zynept0Z.png
[20:38] <jam> GaryvdM: perhaps, but I could see the latter being ok, just taking more work to figure out what exactly goes where...
[20:39] <GaryvdM> Jam: do you create a new "ui" dir, or dump it in the root of where it was moved to?
[20:40] <jam> GaryvdM: good question :)
[20:40] <jam> hence the "what goes where"
[20:40] <jam> *I* would say that if you select files, then they get dumped into the target dir
[20:41] <jam> w/o creating a new 'ui' dir
[20:42] <GaryvdM> jam:  I guess that would make sense for a selection like this: http://imagebin.ca/img/UZLOAps9.png
[20:43] <jam> GaryvdM: right
[20:43] <jam> though you could always "punt" and say that all files must be in the same dir, etc.
[20:43] <GaryvdM> jam: for now, I would prefer to just disable it. It needs to do what the user expects, and there will always be uncertainty here.
[20:45] <GaryvdM> So I want to check that if a path is  selected from a sub dir, then both the dir, and all of it children must be selected.
[21:02] <smartgpx_> nck smartgpx
[21:02] <smartgpx_> nick smartgpx
[21:02] <lifeless>  you want a / at the start of that
[21:04] <smartgpx> lifeless: thanks Robert
[21:09] <GaryvdM> jam: get_minimum_path_selection was not what I was looking for, but was what I needed :-)
[21:14] <jam> GaryvdM: I'm glad you got what you wanted
[21:16] <lifeless> jam: its saturday for me, but if you want to talk about the push regression I'm up for that
[21:17] <jam> lifeless: debugging further it seems to only occur if you have a remote bzrdir w/o a remote branch
[21:17] <jam> so it isn't quite as critical as I thought
[21:17] <jam> It then pushes the whole repo
[21:17] <jam> rather than just the ancestry
[21:17] <lifeless> so
[21:17] <lifeless> /.bzr/repository
[21:17] <lifeless> /foo/.bzr
[21:17] <lifeless> bzr push ../foo
[21:17] <lifeless> ?
[21:17] <jam> foo/.bzr/branch-format but no foo/.bzr/branch/
[21:18] <jam> lifeless: right, something like that
[21:18] <lifeless> so I've seen some odd stuff in that space recently too
[21:18] <jam> lifeless: the checkout stuff ?
[21:18] <lifeless> I filed a bug about branch references getting pushed
[21:18] <jam> yeah
[21:18] <jam> I've been trying to walk through the steps
[21:18] <jam> and we have some *horribly* indirections
[21:19] <jam> 'Branch.push()' calls into InterBranch.push which calls _basic_push which calls Branch.update_revisions which calls InterBranch.update_revisions which...
[21:19] <jam> lifeless: and I believe that is when you *do* have a target branch
[21:19] <jam> which I was trying to compare w/ when you *don't*
[21:20] <lifeless> yeah
[21:20] <jam> I need to just single-step through it and figure out what is going on
[21:20] <lifeless> I expressed concerns about IB but jelmer felt it was really needed
[21:20] <lifeless> It was already arcane deeper in anyhow
[21:20] <lifeless> but IB won't be related to the new branch case, I'm fairly sure
[21:21] <lifeless> thats all in .clone()
[22:48] <jamey_uk> I'm trying to pull a branch in and get this error: "bzr: ERROR: Invalid url supplied to transport: "invalid port number  in url: bzr+ssh://[my-url]"
[22:51] <jamey_uk> in my ~/.ssh/config file I have 'Host [ip-address] \n User [username] \n Port 1989 \n Hostname [my-domain.com]'
[22:51] <lifeless> bzr won't care about that
[22:51] <jamey_uk> Does anyone know why I get the error if I've set my custom port in ~/.ssh/config?
[22:51] <lifeless> what is the actual url you are using
[22:52] <lifeless> you can replace the host and path with arbitrary thgins
[22:52] <lifeless> but we need to see something that is equivalent to tell whats going on
[22:52] <jamey_uk> kind of following, one sec
[22:52] <jamey_uk> bzr pull bzr+ssh://dropoutuk@dropoutuk.com:/home/dropoutuk/www/
[22:53] <lifeless> get rid of the :
[22:53] <jamey_uk> at the beginning?
[22:53] <lifeless> no
[22:53] <lifeless> before /home
[22:53] <jamey_uk> oh
[22:56] <jamey_uk> great, what's an easy way to find out the bzr version installed? the server i'm pulling from is ubuntu 9.04 and this machine is ubuntu 9.10 - i'm getting "Bazaar repository format 2a (needs bzr 1.16 or later)"
[22:56] <jamey_uk> and just out of interest, I've used that syntax before for ssh:// paths, why the missing colon before the path? (or am I mistaken generally)
[23:04] <sven_oostenbrink> fullermd: bzr is FAST... in comparison with SVN / SVK anyway... I have a source code tree of 40.000+ files and its bzr add, boom, done... bzr commit... okay, takes a bit more, but still.. FAST! :)
[23:05] <jamey_uk> Can anyone help me with my bzr 1.16 or greater problem?
[23:09] <lfaraone> Have any speed benchmarks been done with the new branch format and git? http://bazaar-vcs.org/Benchmarks only seems to cover size.
[23:11] <jamey_uk> I've got a repo on my remote server and trying to pull locally into a freshly init'd repo but keep getting error "azaar repository format 2a (needs bzr 1.16 or later)". Any ideas?
[23:11] <vila> jamey_uk: 'bzr version' will tell you which version you're using
[23:12] <sven_oostenbrink> fullermd: I have a development group of 3 persons (myself included).. I want every developer to work on his own branch so that everybody is working seperately on their own laptops (so there will be 3 branches).. then I want the trunk to be on a central server.. we will all merge our changes to that place..
[23:13] <vila> jamey_uk: to upgrade to the latest stable version, see https://edge.launchpad.net/~bzr/+archive/ppa for instructions
[23:13] <jamey_uk> vila, thanks seems like Ubuntu 9.04 has 1.13.1 whilst 9.10 has 2.0.0. What's the safest way to upgrade to 2.x on the former?
[23:13] <sven_oostenbrink> fullermd: That sounds like a good idea? to do it like that? Then, I have the current tree over here on my laptop..  I bzr init, bzr add and bzr commit that tree.. How do I get it to be on that server? bzr push ssh+bzr://me@server ?
[23:13] <jamey_uk> vila, thanks you beat me to it :)
[23:14] <vila> jamey_uk: always happy to help (mt) :-D
[23:14] <vila> s/mt/tm/
[23:15] <jamey_uk> vila, how do I add the key for that source to my apt?
[23:16] <vila> jamey_uk: read that page, open the Technical details, click 'Read about installing'
[23:17] <vila> You'll get all the gory details with ready-to-copy commands
[23:17] <jamey_uk> that's exactly what I did but I has only bash at my disposal :)
[23:17] <jamey_uk> no X here my friend
[23:18] <vila> jamey_uk: ? 'ssh -Y' to the rescue ?
[23:18] <lifeless> jamey_uk: the : at the end leads into a port, bzr uses urls, not rsh paths
[23:19] <jamey_uk> haha no, no, I don't need no X11 thank you :)
[23:19] <jamey_uk> lifeless, ah yes of course thanks for explaining
[23:20] <jamey_uk> vila, being a total n00b sorry, I thought it was a two stage process - first to fetch a GPG key or something, then to use apt-key. all is swell
[23:21] <vila> jamey_uk: great, because I just realized I'm wat past bed time :-)
[23:21] <vila> g'night all !
[23:24] <jamey_uk> g'night, thanks for your help!


[20:12] <cody-somerville> Hi Folks.
[20:13] <cody-somerville> If you're not aware, the hardy-backport of flashplugin-nonfree contains a high impact regression. Unfortunately, the update is not yet blocked so please advise users not to install.
[20:14] <cody-somerville> Users can block the upgrade with: sudo aptitude forbid-version flashplugin-nonfree
[20:42] <PriceChild> cody-somerville: is there a bug report?
[20:43] <cody-somerville> PriceChild, Yes. Are you subscribed to ubuntu-devel?
[20:43] <nhandler> Hi everyone. I just became an Ubuntu Contributing Developer. This also makes me an Ubuntu member. As a result, I qualify for an IRC cloak. The wiki said I should request one here.
[20:43] <PriceChild> nhandler: bear with me
[20:44] <nhandler> PriceChild, ok. I'm in no hurry
[20:44] <nalioth> nhandler: got a LP page?
[20:44] <PriceChild> cody-somerville: example of page causing a problem?
[20:44] <nhandler> nalioth:
[20:45] <nhandler> https://edge.launchpad.net/~nhandler
[20:45] <cody-somerville> PriceChild, I actually have to jet at the moment but the bug reports list pages.
[20:45] <cody-somerville> http://blogs.adobe.com/penguin.swf/2008/07/addessing_wmode_crashes.html
[20:46] <PriceChild> euronews crashed here too.
[20:47] <PriceChild> But isn't that the point in backports?
[20:47] <PriceChild> Possibly crackful, less tested new packages?
[20:47] <PriceChild> Personally I believe its improved my flash situation on other sites.
[20:47] <cody-somerville> According to the wiki page, regressions for backports are highly unlikely
[20:47] <cody-somerville> And due to the large number of sites that cause the crash, it is best to warn users. :)
[20:48] <PriceChild> I guess.
[21:07] <nhandler> Thank you for the cloak


[04:07] <veebers> thomi: do you mind confirming that this bug is now no longer valid due to the work you did with upstart app launch: https://bugs.launchpad.net/autopilot/+bug/1274139
[04:07] <thomi> veebers: uhh, I have no idea, sorry. I don't *think* we kill apps any more?
[04:08] <thomi> sorry - my memory isn't great, I don't remember fixing that bug anyway
[04:08] <veebers> thomi: ack, you didn't fix that bug specifically, it's fixed with the work you did with app/up start
[04:08] <thomi> oh? ok
[04:09] <veebers> ah right, the code is right here: UbuntuAppLaunch.stop_application(app_id)
[04:11] <thomi> veebers: what about for non-upstart launched apps?
[04:11] <thomi> veebers: oh BTW, inc ase you ahven't read it, you should see the convo in #subunit
[04:12] <veebers> thomi: hmm, i read that bug that it was only applicable for apps started with ubuntu app start
[04:12]  * veebers reads backlog


[05:23] -queuebot:#ubuntu-release- New binary: cpupower-gui [amd64] (mantic-proposed/none) [0.7.2-2.1] (no packageset)
[05:23] -queuebot:#ubuntu-release- New binary: cpupower-gui [ppc64el] (mantic-proposed/none) [0.7.2-2.1] (no packageset)
[05:25] -queuebot:#ubuntu-release- New binary: cpupower-gui [s390x] (mantic-proposed/none) [0.7.2-2.1] (no packageset)
[05:26] -queuebot:#ubuntu-release- New binary: cpupower-gui [arm64] (mantic-proposed/none) [0.7.2-2.1] (no packageset)
[05:26] -queuebot:#ubuntu-release- New binary: cpupower-gui [armhf] (mantic-proposed/none) [0.7.2-2.1] (no packageset)
[05:39] -queuebot:#ubuntu-release- New binary: cpupower-gui [riscv64] (mantic-proposed/universe) [0.7.2-2.1] (no packageset)
[11:38] <ItzSwirlz> vorlon, so im going on vacation for next week (which sounds like I won't do anything, but I do have plenty of downtime in early mornings since everyone will still be sleeping), before I turn off my bouncer and pack up, anything you need from me until 2 PM EDT
[11:40] <ItzSwirlz> ig all i can do now is wait for the next livefs build that picks up the changes
[12:24] <ItzSwirlz> well anyways - you got my email if you need anything
[13:12] <kathenas> I see some of the mesa updtes are passing to 22.04 systems and breaking booting to GDM etc. Have we an issue or am I asking in the wrong place?
[13:12] <kathenas> s/updtes/updates
[13:19] <kathenas> https://pasteboard.co/CFoO1ojsLGbG.png
[17:22] -queuebot:#ubuntu-release- New binary: chkservice [amd64] (mantic-proposed/none) [0.3-1.1] (no packageset)
[17:23] -queuebot:#ubuntu-release- New binary: chkservice [ppc64el] (mantic-proposed/none) [0.3-1.1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: chkservice [arm64] (mantic-proposed/none) [0.3-1.1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: chkservice [s390x] (mantic-proposed/none) [0.3-1.1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: chkservice [armhf] (mantic-proposed/none) [0.3-1.1] (no packageset)
[17:41] -queuebot:#ubuntu-release- New binary: chkservice [riscv64] (mantic-proposed/none) [0.3-1.1] (no packageset)
[18:03] -queuebot:#ubuntu-release- New: accepted chkservice [amd64] (mantic-proposed) [0.3-1.1]
[18:03] -queuebot:#ubuntu-release- New: accepted chkservice [armhf] (mantic-proposed) [0.3-1.1]
[18:03] -queuebot:#ubuntu-release- New: accepted chkservice [riscv64] (mantic-proposed) [0.3-1.1]
[18:03] -queuebot:#ubuntu-release- New: accepted cpupower-gui [arm64] (mantic-proposed) [0.7.2-2.1]
[18:03] -queuebot:#ubuntu-release- New: accepted cpupower-gui [riscv64] (mantic-proposed) [0.7.2-2.1]
[18:03] -queuebot:#ubuntu-release- New: accepted chkservice [arm64] (mantic-proposed) [0.3-1.1]
[18:03] -queuebot:#ubuntu-release- New: accepted chkservice [s390x] (mantic-proposed) [0.3-1.1]
[18:03] -queuebot:#ubuntu-release- New: accepted chkservice [ppc64el] (mantic-proposed) [0.3-1.1]
[18:03] -queuebot:#ubuntu-release- New: accepted cpupower-gui [armhf] (mantic-proposed) [0.7.2-2.1]
[18:03] -queuebot:#ubuntu-release- New: accepted cpupower-gui [amd64] (mantic-proposed) [0.7.2-2.1]
[18:03] -queuebot:#ubuntu-release- New: accepted cpupower-gui [s390x] (mantic-proposed) [0.7.2-2.1]
[18:03] -queuebot:#ubuntu-release- New: accepted cpupower-gui [ppc64el] (mantic-proposed) [0.7.2-2.1]
[18:03] <ahasenack> debian has removed the armhf build of blender (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024626)
[18:03] -ubottu:#ubuntu-release- Debian bug 1024626 in src:blender "blender FTBFS on 32bit" [Important, Open]
[18:03] <ahasenack> rmadison confirms it
[18:03] <ahasenack> but I don't see anything in its d/control to not build on armhf
[18:04] <ahasenack> for ubuntu, do we just remove the armhf builds too (old ones in mantic: current one doesn't build anymore), or do we need to omit armhf in d/control and do the same in debian?
[18:04] <ahasenack> iirc if we just pull the debian source, we will try to build everywhere d/control allows it, right
[18:10] <Eickmeyer> ahasenack: I could be wrong, but afaik, if Debian removes an upstream build, we remove the build as well and then just hint Britney so that it's not a migration blocker.
[18:11] <ahasenack> it's not a migration issue, it doesn't build
[18:11] <ahasenack> ah, maybe I see what you mean
[18:11] <Eickmeyer> Right, but Britney will freak out if it's missing a build.
[18:11] <ahasenack> britney will say "missing build on X", but that will be ignored
[18:11] <Eickmeyer> Right.
[18:11] <ahasenack> let me see if there is an example in the hints repo
[18:12] <ahasenack> # We no longer produce armhf builds for this package.
[18:12] <ahasenack> force-badtest nvidia-graphics-drivers-390/all/armhf
[18:12] <ahasenack> maybe that
[18:12] <Eickmeyer> Yep. That sounds right.
[18:13] <Eickmeyer> I mean, I'm not release team, but I have interest in Blender since it's in Studio and have a rudimentary knowledge on how this works.
[18:13] <ahasenack> so are you aware upstream doesn't support 32bit anymore?
[18:13] <ahasenack> I was fixing an ftbfs in mantic due to other issues, and now I see it doesn't build on armhf
[18:14] <ahasenack> and found https://archive.blender.org/lists/bf-committers/2019-August/050124.html
[18:14] <Eickmeyer> Yes, 100%. Studio really doesn't care since we only support amd64 as an arch.
[18:14] <ahasenack> and a corresponding debian bug
[18:14] <ahasenack> ok
[18:14] <ahasenack> I'll PR a hint change
[18:14] <Eickmeyer> I *do* care when thinks fail to migrate, as you might imagine. :)
[18:15] <Eickmeyer> 👍
[18:21] <ahasenack> it ftbfs on s390x now: https://bugs.launchpad.net/ubuntu/+source/blender/+bug/2030291
[18:22] -ubottu:#ubuntu-release- Launchpad bug 2030291 in blender (Ubuntu) "FTBFS on s390x" [Undecided, New]
[18:22] <ahasenack> https://launchpad.net/ubuntu/+source/blender/3.4.1+dfsg-2ubuntu1 armhf should be taked care of by that hints pr
[18:22] <ahasenack> arm64 should build, riscv64 should also build eventually ;)
[18:22] <Eickmeyer> That's unexpected (s390x). Same issue in Debian?
[18:23] <ahasenack> no, but the last build there was months ago
[18:23] <ahasenack> https://buildd.debian.org/status/package.php?p=blender
[18:24] <Eickmeyer> I see that, was just looking myself and answered my own question.
[18:25] <Eickmeyer> Very old version, they're being molasses slow on updating it. Just checked salsa, and same issue there.
[18:25] <ahasenack> what did you see in salsa?
[18:26] <Eickmeyer> https://salsa.debian.org/multimedia-team/blender/ is where they do the packaging.
[18:26] <Eickmeyer> No updates for 6 months.
[18:37] <ginggs> ahasenack: your hint would work if the autopkgtest was failing on armhf
[18:39] <ahasenack> ginggs: I copied what apw did for nvidia, pasted above
[18:39] <ginggs> but it's a FTBFS, so would need an AA to remove the armhf binaries from mantic-release
[18:39] <RikMills> blender in the release pocket already fails on armhf so looks good I think as is
[18:39] <ginggs> but i think this has already been done
[18:39] <ahasenack> ginggs: right, but how to keep the armhf build from being tried again when debian updates?
[18:40] <ginggs> you don't need to, it will just fail
[18:40] <ahasenack> and so it did, I just uploaded https://launchpad.net/ubuntu/+source/blender/3.4.1+dfsg-2ubuntu1
[18:40] <ahasenack> question is if that failure (armhf) will prevent migration
[18:40] <RikMills> it won't
[18:40] <ahasenack> but since s390x failed too, that might prevent the migration instead
[18:41] <ahasenack> ah, I see in https://launchpad.net/ubuntu/+source/blender/3.4.1+dfsg-2build3 that armhf already failed, ok, I missed that
[18:41] <ginggs> no, britney already does not complain about armhf:
[18:41] <ginggs> missing build on amd64: blender, blender-data (from 3.4.1+dfsg-2build3)
[18:41] <ginggs> missing build on arm64: blender (from 3.4.1+dfsg-2build3)
[18:41] <ginggs> missing build on ppc64el: blender (from 3.4.1+dfsg-2build3)
[18:41] <ginggs> missing build on riscv64: blender (from 3.4.1+dfsg-2build3)
[18:41] <ginggs> missing build on s390x: blender (from 3.4.1+dfsg-2build3)
[18:42] <ahasenack> ok, so just s390x needs a real fix
[18:42] <ginggs> but s390x will be an issue, then an AA needs to remove the binaries from mantic (or the build fixed)
[18:43] <ginggs> fwiw, blender/armhf was already removed in kinetic https://launchpad.net/ubuntu/kinetic/armhf/blender
[18:45] <ahasenack> ok, that's sorted then
[18:46] <ahasenack> I only touched blender because of my patch pilot shift yesterday :)
[18:52] <Eickmeyer> ahasenack: I appreciate your work. :)
[19:56] -queuebot:#ubuntu-release- New binary: ktextaddons [amd64] (mantic-proposed/universe) [1.4.0-0ubuntu1] (no packageset)
[19:56] -queuebot:#ubuntu-release- New binary: ktextaddons [s390x] (mantic-proposed/universe) [1.4.0-0ubuntu1] (no packageset)
[19:58] -queuebot:#ubuntu-release- New binary: ktextaddons [ppc64el] (mantic-proposed/universe) [1.4.0-0ubuntu1] (no packageset)
[20:00] -queuebot:#ubuntu-release- New binary: ktextaddons [arm64] (mantic-proposed/universe) [1.4.0-0ubuntu1] (no packageset)
[20:03] -queuebot:#ubuntu-release- New binary: ktextaddons [armhf] (mantic-proposed/universe) [1.4.0-0ubuntu1] (no packageset)
[20:43] -queuebot:#ubuntu-release- New binary: ktextaddons [riscv64] (mantic-proposed/universe) [1.4.0-0ubuntu1] (no packageset)


[02:48] <sagaci> im back in straya
[02:48] <sagaci> riding your kangaroos and drinking the vegemite
[08:16] <Tibor> Hi all
[08:17] <md_5> hi


  Thank you for getting involved with papercuts
[13:44] <AbhiJit> sladen, yah
[13:44] <sladen> klattimer: I'm here, but not being productive
[13:45] <spikeb> AbhiJit, i don't know what you did but thank you!
[13:45] <AbhiJit> :)
[13:45] <AbhiJit> spikeb, :D
[13:45]  * spikeb is always grateful to have a papercut fixed
[13:45] <AbhiJit> hello all
[13:45] <AbhiJit> i am new here to papercut system.
[13:46] <AbhiJit> i previusly had little experience in normal ubuntu bug squad.
[13:46] <AbhiJit> see my wiki https://wiki.ubuntu.com/abhijit
[16:02] <lamalex> API, reviewing your merge now
[16:02] <API> lamalex, ok, thanks
[16:02] <lamalex> av
[16:03] <lamalex> erm
[16:03] <lamalex> 435	+  g_type_class_unref (g_type_class_ref (UNITY_TYPE_UTIL_ACCESSIBLE));
[16:03] <lamalex> is that because it's a dummy implementation?
[16:03] <lamalex> because otherwise I don't understand :P
[16:03] <lamalex> API, ^
[16:04] <API> no, it is not because a dummy implementation
[16:04] <API> AtkUtil is an abstract class
[16:04] <API> unity-util-accessible implements it
[16:04] <API> this class_unref(ref
[16:04] <API> its to ensure that class_init is called
[16:04] <API> so you can call those atk_util methods
[16:04] <lamalex> ok
[16:04] <lamalex> sounds good
[16:05] <API> you normally call atk_util methods directly
[16:05] <API> class methods
[16:05] <lamalex> API, do you have commit access?
[16:05] <API> without asking for the instance
[16:05] <API> probably it would be good a kind of singleton implementation, but this would require changes on ATK itself
[16:05] <API> lamalex, hmmm don't know
[16:05] <API> as I don't know
[16:05] <API> probably this means no
[16:06] <lamalex> ok
[16:06] <lamalex> I've got two comments and I'm testing, then I'll merge
[16:06] <lamalex> API, this should advertise unity in accerciser right?
[16:08] <API> well, yes
[16:08] <API> anyway, as I said, right now this would only work with at-spi2
[16:08] <API> did you see that code to find the atk-bridge?
[16:09] <API> that gsettings, for the moment, is only on at-spi2
[16:09] <API> I thought that this would be the one to be included on Natty
[16:09] <API> this week we concluded at-spi
[16:09] <API> we need to make this change also on at-spi
[16:09] <lamalex> ah ok
[16:10] <API> lamalex, anyway, with this branch unity accerciser will be able to find unity
[16:10] <lamalex> so at-spi needs a patch to use gsettings
[16:10] <API> but as both util and root are dummies
[16:10] <API> without any children
[16:10] <lamalex> right
[16:10] <API> yes, at-spi needs that patch, I guess that right now is the most important task
[16:11] <lamalex> API, there are two very small changes to make. I'll make them and merge.
[16:11] <lamalex> nice job
[16:11] <API> I will ask TheMuso (Luke) if this my task or his task
[16:11] <API> lamalex, thanks, just to avoid do the same errors in the future, what changes?
[16:12] <lamalex> API, they're on the review. You didn't add atk to deps, and there was a comment involcing Clutter :P
[16:13] <lamalex> @see_also: #ClutterStage
[16:13] <API> lamalex, ups
[16:13] <API> yes
[16:13] <lamalex> :P no big deal
[16:13] <API> lamalex, and about the dep
[16:13] <API> as unity depends on gtk
[16:13] <API> and gtk on atk
[16:13] <API> I thought that was not required
[16:13] <API> but ok, thanks
[16:14] <lamalex> It's not required per se, but it's good form to just include it if we're linking againt atk.h
[16:14] <API> btw, I should also assign you the review of the other merge request?
[16:14] <lamalex> sure
[16:14] <API> lamalex, also the nux one?
[16:16] <lamalex> API, sure- any that you have
[16:17] <API> lamalex, ok
[16:21] <API> lamalex, reassigned
[16:24] <lamalex> API, great, will review now
[16:38] <lamalex> API,  are there just the 2? I'm building now but it looks quite good
[16:38] <API> lamalex, well yes, just two
[16:38] <API> although the unity one is really big
[16:38] <lamalex> yah
[16:38] <API> not a lot of functionality
[16:38] <API> but a lot of new objects
[16:39] <lamalex> yes
[16:39] <lamalex> lots of boilerplate gobject code
[16:41] <lamalex> API, I get a build failure, can you check the merge proposal?
[16:41] <lamalex> https://code.launchpad.net/~apinheiro/unity/bug701680/+merge/46080
[16:42] <lamalex> ah it requires a nux patch
[16:42] <lamalex> API, I see, sorry
[16:42] <API> lamalex, yes I added two requests
[16:42] <lamalex> yeah I missed it :)
[16:42] <API> I didn't found a way to say that the unity one requires the nux one
[16:43] <API> as the unity one had already  a dependency
[16:43] <API> with the atk-bridge-load one
[16:53] <kvalo> kenvandine: https://launchpad.net/indicator-network/trunk/0.3.3
[17:25] <gord> jcastro, hey, do you know if there is any effort to add the X-Ayatana-Desktop-Shortcut stuff to .desktop files? mainly just to make the right click menus of unity launchers more filled out and useful
[17:27] <jcastro> I think didrocks?
[17:32] <gord> he's busy and may explode into tiny didrocks fragments if i bug him about this before compiz is uploaded ;) thanks
[17:34] <seb128> gord, there is none
[17:56] <gord> seb128, if i were to make patches for all the desktop files of applications i use with desktop shortcuts in them, would you guys hate me forever? ;)
[18:56] <API> unity now requires libdbusmenu-glib-dev 0.4 but natty version is 0.3.90
[18:57] <API> where I can find the new version?
[18:57] <API> is there any ppa somewhere?
[18:58] <tareth> https://launchpad.net/dbusmenu
[18:59] <API> tareth, thanks
[19:00] <API> tareth, hmm odd, it says that latests version is 0.3.91
[19:00] <tareth> no problem :) had to figure that out earlier this morning
[19:00] <API> tareth, so now unity depends on 0.3.91 instead of 0.4?
[19:01] <kamstrup> njpatel: it's on lp:~unity-team/+junk/deesire
[19:10] <AbsintheSyringe> kenvandine, I packaged a lot of packages, got to compizconfig-backend-gconf and got into a problem
[19:15] <AbsintheSyringe> actually let me try one more thing :)
[19:38] <AbsintheSyringe> kenvandine, http://paste.debian.net/104554/ am looking into 01_add_transition_gconf.patch
[19:42] <kklimonda> hey, is anyone familiar with software-center online?
[19:43] <kklimonda> what is the "metadata" mpt has mentioned in https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/660372 ?
[19:55] <AbsintheSyringe> kenvandine, k nvm, got it figured
[21:18] <ronoc> gabaug, did that release get into to ubuntu ?
[21:18] <ronoc> to even
[21:18] <ronoc> even if there was a deb I could test out that would be great
[21:19] <ronoc> i want to test the playlist extension
[21:19] <gabaug> ronoc: hyperair is the packager for Ubuntu/Debian -- I'm not sure
[21:19] <ronoc> ah okay thx
[21:19] <ronoc> hyperair, ^
[21:21] <torkvemada> ronoc: d'you mean MediaPlayer2.Playlists?
[21:21] <gabaug> ronoc: oh, the daily builds might have it already (not sure if they're actually daily)
[21:22] <ronoc> torkvemada, yup
[21:23] <ronoc> gabaug, good point, I'll have a look
[21:25] <torkvemada> ronoc: don't you know, is there xml spec for interface available to download anywhere?
[21:25] <ronoc> torkvemada, for the playlists ?
[21:25] <torkvemada> yep
[21:26] <torkvemada> I'd like to implement it right now :)
[21:26] <ronoc> torkvemada, not that I know of, its quite a small extension - all the info you need can be found www.mpris.org
[21:29] <torkvemada> aah, will write it by myself>.<
[21:36] <kamstrup> njpatel: it's on lp:~unity-team/+junk/deesire
[21:36] <kamstrup> njpatel: it's on lp:~unity-team/+junk/deesire
[21:36] <kamstrup> njpatel: it's on lp:~unity-team/+junk/deesire
[21:36] <kamstrup> njpatel: it's on lp:~unity-team/+junk/deesire
[22:46] <torkvemada> ronoc: is 0.5.5-0ubuntu1 suitable for playlists testing?
[22:47] <ronoc> torkvemada, it 'should' be, although i have yet to be able to give it a good test drive
[22:47] <torkvemada> It seems that "stub" interface (providing no playlists) makes indicator-sound go mad
[22:49] <seiflotfy> kamstrup, how is unity-place-files coming
[22:49] <seiflotfy> cna u run it again
[22:49] <seiflotfy> #?
[23:02] <kamstrup> seiflotfy: you can run it if you have libunity and libdee from trunk
[23:40] <torkvemada> ronoc: that looks extremely strange, but if only I provide the Playlists interface, indicator-sound becomes mad. It requests "loopStatus", "metadata", "playbackStatus", "shuffle" and "volume" properties in an infinite loop. The indicator itself becomes unusable - it shows "muted" icon instead of normal and if you click on it,  the only item you'll get is player name.
[23:40] <torkvemada> But when I stop my daemon, indicator-sound becomes "normal"
[23:48] <ronoc> torkvemada, weird, I certainly do not request the loop status
[23:48] <ronoc> torkvemada, do you have a ppa from which I can test your app ?
[23:49] <torkvemada> one second, I'll make it produce a bit more debug and I'll push it to ppa
[23:53] <ronoc> torkvemada, ta, I'm bout to finish for the day but can look in the morning
[23:54] <torkvemada> so may be it's better to send you info by email?
[23:56] <ronoc> torkvemada, please, you can send it to the mailing list for indicator-sound-developers, i'll pick it up in the morning
[23:58] <torkvemada> ok, I'll send the info and address of ppa to the mailing list