[00:00] <vidd> yes...on about 8 computers
[00:00] <fs87> nice :)
[00:00] <vidd> various hardware configurations
[00:00] <fs87> which do you think is the best WM?
[00:01] <vidd> im not a good person to ask....i have only used gnome, KDE, and xfce
[00:01] <fs87> i'm using ion3 right now
[00:01] <vidd> the only reason i use xfce and not gnome is because i like having the same wm on all my machines
[00:01] <vidd> and some cant handle gnome
[00:02] <fs87> how long do you use linux?
[00:02] <vidd> about 3 years? maybe 4
[00:03] <fs87> tried other distro's?
[00:03] <vidd> yes
[00:03] <vidd> i dont like .rpm based distros
[00:03] <fs87> same here
[00:03] <fs87> my first was mandrake
[00:03] <fs87> crashed it many times
[00:04] <fs87> partly cause of the rmp's
[00:04] <vidd> we should move this to #xubuntu-offtopic b4 we get told to
[00:55] <Rohaq> howdy folks
[00:56] <ere4si> g'day
[01:15] <Tu13es> hmm
[01:16] <Tu13es> I want to share an external drive from my desktop running gutsy to my laptop running gutsy
[01:16] <Tu13es> what's the best way to do it?
[01:16] <Tu13es> before I used to use AFP from one Mac to another and it was nice and easy
[01:24] <nathan2> hey, I'm having problems with something.  Is anyone around that can help?
[01:28] <vidd> whats up
[01:59] <Robert8915> hello
[02:04] <zoredache> hi
[02:08] <Valternaz> ola
[02:49] <Jerimiah40> I'm having trouble getting Xubuntu to install, can anyone help me out?
[02:52] <BunnyRevolution> what trouble are you having?
[02:53] <Jerimiah40> Every time I try to install from a live CD (7.10), it gets to 15% complete, and then just locks up
[02:54] <BunnyRevolution> what does your memory look like?
[02:55] <BunnyRevolution> how much memory do you have?
[02:55] <Jerimiah40> 192MB
[02:56] <BunnyRevolution> do you have a high speed connection?
[02:56] <Jerimiah40> Internet?  It's reasonably high speed, yeah
[02:56] <BunnyRevolution> try the alternate cd
[02:58] <Jerimiah40> Alright, I'll try that
[02:58] <Jerimiah40> Just out of curiosity, what is the difference between alternate and desktop?
[02:59] <BunnyRevolution> the alternate installer is more text based, but asks the same questions and uses less mem
[03:00] <Jerimiah40> Alright
[03:00] <BunnyRevolution> so the installer is not as pretty, but works faster.  in fact, i use the alternate install over the normal install because i don't have to point and click, but tab, enter, tab enter
[03:01] <BunnyRevolution> even when i have lots of mem.  after downloading, test your cd, then install
[03:01] <Jerimiah40> okay
[03:01] <Jerimiah40> Does it install everything that the desktop installer does?
[03:01] <BunnyRevolution> yes
[03:01] <Jerimiah40> alright
[03:02] <BunnyRevolution> the alternate allows for some other options, one of them bieng LVM
[03:03] <Jerimiah40> Neat
[03:45] <Sl4y3r> anyone know why when i view flash videos in firefox even after deleteing the cache im not seeing the space re-freed
[03:45] <BunnyRevolution> flash videos are kept in /tmp sometimes
[03:46] <Sl4y3r> ah
[03:47] <Sl4y3r> nothing in there
[03:47] <Sl4y3r> ;x
[03:48] <BunnyRevolution> well, they don't end in *.s*
[03:49] <Sl4y3r> what would they end in?
[03:49] <BunnyRevolution> ~/.mozilla/firefox/somename.default/Cache , you need to look here as well
[03:49] <reindeer> I am looking for a way to bust open a .toast torrent file to extract the boot image for a complete, error-free bootable ISO. Any solutions?
[03:50] <BunnyRevolution> download the .torrent, and mount the iso and then extract the boot image
[03:52] <reindeer> The torrent is completely downed. Just need to find an app or utility which will extract the boot image from the file.
[03:52] <reindeer> From there, i hsould be able to mount it nicely.
[03:52] <reindeer> I should
[03:53] <reindeer> I'm just having trouble extracting the boot image.
[03:56] <reindeer> I'll see what 7zip will do. Gotta work the CLI from xterm. It may be the only option in which to extract the image from the toast torrent. Appreciate your help.
[04:20] <Ultraputz> if you want the wireless applet to remember a wep key, how do you do that?
[04:57] <Tuv0k> my xubuntu install has no pulse happening
[04:57] <Tuv0k> pam is getting "connection refused to server"
[04:59] <Tuv0k> !pulse
[04:59] <ubotu> Sorry, I don't know anything about pulse - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi
[05:00] <Tuv0k> !pulseaudio
[05:00] <ubotu> PulseAudio is a sound server intended as a drop-in replacement for !ESD - See https://wiki.ubuntu.com/PulseAudio for information and installation instructions
[05:36] <zoredache> I am surpised that someone hasn't banned you irseekbot
[05:39] <Tuv0k> http://pastebin.com/d1e28189f
[08:29] <ere4si> I need to get gnome-vfs module running so I can use gdesklets - how to install and run it pls
[08:31] <Iskr> synaptic?
[08:31] <ere4si> not listed there Iskr
[08:36] <ere4si> someone with an idea?
[08:41] <Iskr> well if i look for gdesklets on synaptic i find it
[08:42] <Iskr> and i presume that if i install it, it would, as usual, install needed dependencies
[11:12] <julian> hi ive got a problem with the xubuntu livecd
[11:12] <julian> and dunno if its a bug a feature or if i miss something
[11:12] <totalwormage> do tell
[11:12] <julian> im not able to use gparted how it should work
[11:13] <julian> opening gparted leads mount to mount everything automatically
[11:13] <julian> and if i change a partition it gets started working on it and suddenly xubuntu decides to mount everything again
[11:13] <julian> and i need to umount it in the terminal
[11:14] <julian> and that needs to be done quickly otherwise gparted stops working on the partition
[11:14] <totalwormage> that doesn't sound good
[11:14] <totalwormage> i think you shouldn't tinker with mounts while gparted is working on them
[11:15] <julian> normally xubuntu shouldnt auto mount everything
[11:16] <totalwormage> hm
[11:16] <julian> i dont have that problem with ubuntu livecd
[11:16] <totalwormage> anyone else here who knows about this kind of thing? :P
[11:16] <julian> gparted is crashing on both when using swapoff but that isnt a big problem
[16:44] <xemonoth> Hi, my RoseGarden program is telling me that the timing in the kernel is too slow.  How do I resolve this?
[17:48] <BunnyRevolution> stay in the channel so i can answer your question ...
[17:51] <BunnyRevolution> i need several world clocks on my desktop.  which program is best to use.
[17:58] <Stroganoff> BunnyRevolution: gdesklets may be the right one
[17:59] <siggjen> or gworldclock
[18:00] <BunnyRevolution> u know, i am gravitating more and more to xubuntu because of the support that is available in this channel
[18:01] <cody-somerville> :)
[19:35] <Ultraputz> any idea how to get network manager to remember WEP passwords ?
[19:37] <maxamillion> Ultraputz: you need the gnome keyring manage
[19:37] <maxamillion> manager*
[19:37] <Ultraputz> does it add a lot of overhead?
[19:39] <maxamillion> uhmm... a bit, yes
[19:39] <maxamillion> but it depends on what you consider "a lot"
[19:39] <Ultraputz> 700mhz p3
[19:41] <maxamillion> yeah, you should be fine ... there might be slight lag when it first negotiates the connection but after that you probably won't notice
[19:41] <maxamillion> Ultraputz: how much ram?
[19:42] <Ultraputz> .5g
[19:42] <Ultraputz> gnome keyring manager. gonna try that. machine is outside, bbiab
[19:43] <Ultraputz> thanks, btw
[19:43] <maxamillion> anytime :)
[19:57] <Stroganoff> whats the name of the xfce network manager package?
[19:59] <charlie-tca> In gutsy, installed package is Gnome-network-manager
[20:10] <slow-motion> hi
[20:49] <BunnyRevolution> xubuntu hardy beta fails the install on virutal box vm
[20:54] <uninvited> Now that is what i call a problem description :)
[21:04] <zoredache> BunnyRevolution: how does it fail?
[21:05] <zoredache> I didn't have any problems when installing in vmware
[21:08] <slow-motion> n8
[21:12] <fivehorizons> Can someone help me with a question about tunneling VNC through SSH?
[21:13] <charlie-tca> Depends on the question
[21:14] <charlie-tca> I've done it with vnc4server and xvnc4client
[21:14] <fivehorizons> I'm pretty much a linux newb but I followed the guide located here: http://www.bit-tech.net/bits/2007/06/05/build_your_own_server/6 to set up a file server
[21:15] <zoredache> fivehorizons: and what are you having problems with?
[21:15] <fivehorizons> I was able to use VNC through SSH the first time I tried it, but after I rebooted the server I keep getting an "Connection Failed - Error reading Protocol Version" message
[21:16] <fivehorizons> However, if I connect serverip:0 it works, but I don't want to do that
[21:17] <zoredache> you restarted your ssh tunnel after the server rebooted right?
[21:18] <fivehorizons> I think so....does that just require making a new SSH connection with putty?
[21:18] <zoredache> fivehorizons: maybe, it depends on if you saved your settings on the session that you had the tunnel working before
[21:19] <fivehorizons> Yeah, I had saved the settings. I'm essentially doing everything the same way as when it first worked. The only difference is that the server was rebooted in between, so I don't know if this screwed something up
[21:20] <zoredache> are you connected to the server now through ssh?
[21:20] <fivehorizons> Not at this moment because I'm at work, but I am able to connect through ssh just fine.
[21:21] <zoredache> well, anyway, when you are connected to the server through ssh runn a command like this 'netstat -ntl | grep 5900'
[21:21] <fivehorizons> ok, what will that tell me?
[21:21] <zoredache> if dont' see anything then x11vnc didn't get started
[21:22] <zoredache> if *you*
[21:22] <zoredache> the sharex11vnc command doesn't seem to be automatically started on its own
[21:23] <zoredache> you probably need to run that each time you ssh in... Or add it to rc.local
[21:23] <fivehorizons> ahh, yeah I actually did do something like that. It didn't start on its own, so i ran sharex11vnc manually.
[21:24] <BunnyRevolution> zoredache: let me re-download it and try again
[21:24] <zoredache> on a related note I would add another option to the x11vnc command line the script uses
[21:24] <fivehorizons> And like I said, VNC works fine if connect directly to the server IP, but if I try to go through localhost:0 it doesn't work
[21:25] <zoredache> I think you add the '-localhost' option so that vnc cannot be accessed unless you have your ssh tunnel working
[21:25] <fivehorizons> ah ok
[21:26] <zoredache> also, if you do that you could add the '-nopw' option which will make it so that you don't have to give vnc a password... Since you can only connect through ssh, it seems like you don't need the extra password.
[21:28] <fivehorizons> yeah, but at this point I'd be happy to see the password dialog box going through ssh haha
[21:28] <fivehorizons> I can't get anything but that stupid protocol error
[21:29] <BillyJoe> when I plug in my usb drive, it dosn't auto make the /media/"name" folder so it can not mount it... How do I get my system to auto create this folder?
[21:34] <zoredache> fivehorizons: sorry, but what question are you getting the 'protcol error' message from?
[21:34] <zoredache> bleah...  what program are you getting the protocol error from..
[21:34] <fivehorizons> UltraVNC when I try to connect to localhost:0
[21:35] <zoredache> do you have a vnc server running on your workstation?
[21:35] <fivehorizons> no, just on the fileserver
[21:36] <zoredache> and your workstation is winxp, vista, or?
[21:36] <fivehorizons> xp
[21:37] <zoredache> on your winxp computer do a command like 'netstat -nt | find "5900"'
[21:37] <zoredache> if you don't see anything in the list, then putting isn't setting things up correctly
[21:38] <zoredache> you also might want to try connecting to localhost::5900 in ultravnc
[21:39] <fivehorizons> Thanks zoredache.  I'll try both of those things when I get home
[21:39] <zoredache> sorry?
[21:40] <zoredache> aren't you trying to set it up so that you can connect from outside of your home?
[21:40] <fivehorizons> I'm not at the xp workstation right now. I'm at my work computer
[21:40] <fivehorizons> well, yes
[21:40] <zoredache> ah
[21:40] <fivehorizons> but I don't have my public IP atm
[21:40] <zoredache> ah
[22:18] <hyper_ch> TheSheep: hiho
[22:18] <TheSheep> hi hyper_ch
[22:19] <hyper_ch> TheSheep: what's up?
[22:21] <TheSheep> hyper_ch: ---> #xubuntu-offtopic
[22:34] <maxamillion> lol
[22:42] <StoneColdDude> Hi anyone home?
[22:42] <maxamillion> j0
[22:43] <StoneColdDude> Hi
[22:43] <zoredache> !anyone
[22:43] <maxamillion> StoneColdDude: actually, i have to brb ... very sorry
[22:43] <StoneColdDude> Are U a Xubuntu user?
[22:43] <zoredache> ubotu have you left us?
[22:43] <zoredache> anyway, whats up?
[22:44] <StoneColdDude> What type of dialup system does Xubuntu use??
[22:44] <StoneColdDude> I use kppp and want a light syatem
[22:45] <zoredache> the underlying system is of course based on ppp...  I am not sure if there is a gui, or how to use it... I think I saw something in Network Manager though
[22:45] <StoneColdDude> OK thank you
[22:45] <StoneColdDude> Gotta go now...bye!
[23:37] <Zoris> I have installed xfce4 from apt-get; how do I get it to work now? If I try to log into the session nothing happens


[04:07] <mark06> anyone knows a solution for this? http://i.imgur.com/PtfK5y5.png
[16:55] <zyga> hey, I'm trying to debug a bug in bzr join
[16:56] <zyga> what I'm seeing is that a bzrlib.inventory.Inventory has a duplicate entry
[16:57] <zyga> the curious thing is  that the file_id of the entry is just the filename
[16:59] <zyga> both entries seem to be coming from a git import of some repositories
[19:15] <jelmer> zyga: that's normal, file ids from git imports are mostly just paths


[03:21] <pleia2> ok, 319 has been sent to summary writers - write away! :)
[03:21]  * pleia2 makedinner
[20:10] <pleia2> anyone available today to do summaries?
[20:10] <pleia2> here: http://bit.ly/vDkJyf
[20:17] <PaulW2U> pleia2: I've done a few but been busy. I can take another look in a couple of hours
[22:18] <PaulW2U> pleia2: I've added a few more summaries but I'm struggling with those that are left :o(


[04:45] -queuebot:#ubuntu-release- New: accepted golang-github-vultr-govultr [amd64] (focal-proposed) [0.1.4+git20190904.cb344cc-1]
[04:45] -queuebot:#ubuntu-release- New: accepted rust-jemalloc-sys [amd64] (focal-proposed) [0.3.2-1]
[04:45] -queuebot:#ubuntu-release- New: accepted deepnano [amd64] (focal-proposed) [0.0+git20170813.e8a621e-3.1]
[04:45] -queuebot:#ubuntu-release- New: accepted deepnano [ppc64el] (focal-proposed) [0.0+git20170813.e8a621e-3.1]
[04:45] -queuebot:#ubuntu-release- New: accepted rust-jemalloc-sys [arm64] (focal-proposed) [0.3.2-1]
[04:46] -queuebot:#ubuntu-release- New: accepted rust-jemalloc-sys [i386] (focal-proposed) [0.3.2-1]
[04:46] -queuebot:#ubuntu-release- New: accepted vip-manager [arm64] (focal-proposed) [0.6+ds-1]
[04:46] -queuebot:#ubuntu-release- New: accepted vip-manager [i386] (focal-proposed) [0.6+ds-1]
[04:46] -queuebot:#ubuntu-release- New: accepted deepnano [arm64] (focal-proposed) [0.0+git20170813.e8a621e-3.1]
[04:46] -queuebot:#ubuntu-release- New: accepted rust-jemalloc-sys [armhf] (focal-proposed) [0.3.2-1]
[04:46] -queuebot:#ubuntu-release- New: accepted vip-manager [armhf] (focal-proposed) [0.6+ds-1]
[04:46] -queuebot:#ubuntu-release- New: accepted golang-github-boj-redistore [amd64] (focal-proposed) [1.2+git20180917.cd5dcc7-1]
[04:46] -queuebot:#ubuntu-release- New: accepted vip-manager [amd64] (focal-proposed) [0.6+ds-1]
[04:46] -queuebot:#ubuntu-release- New: accepted deepnano [i386] (focal-proposed) [0.0+git20170813.e8a621e-3.1]
[04:46] -queuebot:#ubuntu-release- New: accepted golang-github-jackc-fake [amd64] (focal-proposed) [0.0~git20150926.812a484-1]
[04:46] -queuebot:#ubuntu-release- New: accepted rust-jemalloc-sys [ppc64el] (focal-proposed) [0.3.2-1]
[04:46] -queuebot:#ubuntu-release- New: accepted vip-manager [ppc64el] (focal-proposed) [0.6+ds-1]
[04:46] -queuebot:#ubuntu-release- New: accepted deepnano [s390x] (focal-proposed) [0.0+git20170813.e8a621e-3.1]
[04:46] -queuebot:#ubuntu-release- New: accepted rust-jemalloc-sys [s390x] (focal-proposed) [0.3.2-1]
[04:46] -queuebot:#ubuntu-release- New: accepted golang-github-nrdcg-goinwx [amd64] (focal-proposed) [0.6.1-1]
[04:46] -queuebot:#ubuntu-release- New: accepted vip-manager [s390x] (focal-proposed) [0.6+ds-1]
[05:14] -queuebot:#ubuntu-release- New binary: fort-validator [amd64] (focal-proposed/universe) [1.1.1-2] (no packageset)
[05:15] -queuebot:#ubuntu-release- New binary: fort-validator [i386] (focal-proposed/universe) [1.1.1-2] (no packageset)
[05:15] -queuebot:#ubuntu-release- New binary: rpki-trust-anchors [amd64] (focal-proposed/universe) [20191019-1] (no packageset)
[05:15] -queuebot:#ubuntu-release- New binary: fort-validator [s390x] (focal-proposed/universe) [1.1.1-2] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: fort-validator [arm64] (focal-proposed/universe) [1.1.1-2] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: fort-validator [ppc64el] (focal-proposed/universe) [1.1.1-2] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: fort-validator [armhf] (focal-proposed/universe) [1.1.1-2] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: libgwenhywfar [i386] (focal-proposed/universe) [4.99.24rc8-1] (kubuntu)
[05:17] -queuebot:#ubuntu-release- New binary: libgwenhywfar [amd64] (focal-proposed/universe) [4.99.24rc8-1] (kubuntu)
[05:17] -queuebot:#ubuntu-release- New binary: libgwenhywfar [s390x] (focal-proposed/universe) [4.99.24rc8-1] (kubuntu)
[05:18] -queuebot:#ubuntu-release- New binary: libgwenhywfar [ppc64el] (focal-proposed/universe) [4.99.24rc8-1] (kubuntu)
[05:20] -queuebot:#ubuntu-release- New binary: libgwenhywfar [arm64] (focal-proposed/universe) [4.99.24rc8-1] (kubuntu)
[05:21] -queuebot:#ubuntu-release- New: accepted libgwenhywfar [amd64] (focal-proposed) [4.99.24rc8-1]
[05:21] -queuebot:#ubuntu-release- New: accepted libgwenhywfar [ppc64el] (focal-proposed) [4.99.24rc8-1]
[05:21] -queuebot:#ubuntu-release- New: accepted libgwenhywfar [arm64] (focal-proposed) [4.99.24rc8-1]
[05:21] -queuebot:#ubuntu-release- New: accepted libgwenhywfar [s390x] (focal-proposed) [4.99.24rc8-1]
[05:21] -queuebot:#ubuntu-release- New: accepted fort-validator [amd64] (focal-proposed) [1.1.1-2]
[05:21] -queuebot:#ubuntu-release- New: accepted fort-validator [armhf] (focal-proposed) [1.1.1-2]
[05:21] -queuebot:#ubuntu-release- New: accepted fort-validator [ppc64el] (focal-proposed) [1.1.1-2]
[05:21] -queuebot:#ubuntu-release- New: accepted libgwenhywfar [i386] (focal-proposed) [4.99.24rc8-1]
[05:21] -queuebot:#ubuntu-release- New: accepted fort-validator [arm64] (focal-proposed) [1.1.1-2]
[05:21] -queuebot:#ubuntu-release- New: accepted fort-validator [s390x] (focal-proposed) [1.1.1-2]
[05:21] -queuebot:#ubuntu-release- New: accepted fort-validator [i386] (focal-proposed) [1.1.1-2]
[05:21] -queuebot:#ubuntu-release- New: accepted rpki-trust-anchors [amd64] (focal-proposed) [20191019-1]
[05:23] -queuebot:#ubuntu-release- New binary: libgwenhywfar [armhf] (focal-proposed/universe) [4.99.24rc8-1] (kubuntu)
[05:33] -queuebot:#ubuntu-release- Unapproved: backport-iwlwifi-dkms (eoan-proposed/universe) [7906-0ubuntu1 => 7906-0ubuntu1.1] (no packageset)
[06:13] -queuebot:#ubuntu-release- New binary: libchipcard [amd64] (focal-proposed/universe) [5.1.4rc1-2] (no packageset)
[06:13] -queuebot:#ubuntu-release- New binary: libchipcard [s390x] (focal-proposed/universe) [5.1.4rc1-2] (no packageset)
[06:13] -queuebot:#ubuntu-release- New binary: libchipcard [i386] (focal-proposed/universe) [5.1.4rc1-2] (no packageset)
[06:14] -queuebot:#ubuntu-release- New binary: libchipcard [ppc64el] (focal-proposed/universe) [5.1.4rc1-2] (no packageset)
[06:14] -queuebot:#ubuntu-release- New binary: libaqbanking [amd64] (focal-proposed/universe) [5.99.43beta-1] (kubuntu)
[06:14] -queuebot:#ubuntu-release- New binary: libaqbanking [s390x] (focal-proposed/universe) [5.99.43beta-1] (kubuntu)
[06:15] -queuebot:#ubuntu-release- New binary: libaqbanking [i386] (focal-proposed/universe) [5.99.43beta-1] (kubuntu)
[06:15] -queuebot:#ubuntu-release- New binary: libaqbanking [ppc64el] (focal-proposed/universe) [5.99.43beta-1] (kubuntu)
[06:15] -queuebot:#ubuntu-release- New binary: libchipcard [arm64] (focal-proposed/universe) [5.1.4rc1-2] (no packageset)
[06:19] -queuebot:#ubuntu-release- New binary: libaqbanking [arm64] (focal-proposed/universe) [5.99.43beta-1] (kubuntu)
[06:38] -queuebot:#ubuntu-release- New: accepted libchipcard [amd64] (focal-proposed) [5.1.4rc1-2]
[06:38] -queuebot:#ubuntu-release- New: accepted libchipcard [i386] (focal-proposed) [5.1.4rc1-2]
[06:38] -queuebot:#ubuntu-release- New: accepted libchipcard [s390x] (focal-proposed) [5.1.4rc1-2]
[06:38] -queuebot:#ubuntu-release- New: accepted libchipcard [arm64] (focal-proposed) [5.1.4rc1-2]
[06:38] -queuebot:#ubuntu-release- New: accepted libgwenhywfar [armhf] (focal-proposed) [4.99.24rc8-1]
[06:38] -queuebot:#ubuntu-release- New: accepted libchipcard [ppc64el] (focal-proposed) [5.1.4rc1-2]
[06:39] -queuebot:#ubuntu-release- New: accepted libaqbanking [amd64] (focal-proposed) [5.99.43beta-1]
[06:39] -queuebot:#ubuntu-release- New: accepted libaqbanking [i386] (focal-proposed) [5.99.43beta-1]
[06:39] -queuebot:#ubuntu-release- New: accepted libaqbanking [s390x] (focal-proposed) [5.99.43beta-1]
[06:39] -queuebot:#ubuntu-release- New: accepted libaqbanking [arm64] (focal-proposed) [5.99.43beta-1]
[06:39] -queuebot:#ubuntu-release- New: accepted libaqbanking [ppc64el] (focal-proposed) [5.99.43beta-1]
[09:47] -queuebot:#ubuntu-release- New binary: mini-buildd [amd64] (focal-proposed/universe) [1.1.18] (no packageset)
[09:59] <rbalint> sil2100, could you please merge https://code.launchpad.net/~rbalint/britney/autopkgtest-hints/+merge/374971 to let systemd migrate to focal?
[10:00] <rbalint> sil2100, also please accept the eoan systemd sru which gets unblocked then
[10:02] -queuebot:#ubuntu-release- New: accepted mini-buildd [amd64] (focal-proposed) [1.1.18]
[11:19] <doko> please ignore the botch autopkg regression triggered by python-apt. caused by a new graphviz which already is in the release pocket
[11:20] <doko> filed Debian #944100
[12:19] -queuebot:#ubuntu-release- New binary: django-mailer [amd64] (focal-proposed/universe) [2.0-0ubuntu1] (no packageset)
[12:40] <slashd> sil2100, can you please have a look at 'network-manager' in bionic-proposed for official release ?
[12:40] <slashd> dgadomski ^
[12:42] <slashd> sil2100, and also 'grub2' found in Xenial upload queue
[12:43] <sil2100> slashd: sure thing! Will just finish up scribbling something and I'll move on to the SRU work
[12:44] <slashd> sil2100, thanks
[12:50] -queuebot:#ubuntu-release- Unapproved: rejected glib2.0 [source] (eoan-proposed) [2.62.2-1~ubuntu19.10.1]
[12:54] <sil2100> rbalint: hey, so I actually see 2 systemd uploads in the eoan queue
[12:55] <sil2100> rbalint: does the second one include all the changes from the first one? Is it supposed to override the previous one? Since I don't see the latest one having two versions in its .changes
[12:55] <rbalint> sil2100, let me check
[13:01] <rbalint> sil2100, it is only missing from the .changes
[13:02] <rbalint> ddstreet, could you please include 3.1's entry and reupload?
[13:03] <rbalint> ddstreet, as i see everything is fixed in focal now that goes into 3.2, thus it can be accepted skipping the 3.1 upload
[13:04] <rbalint> sil2100, ^
[13:06] <sil2100> Yeah, just a re-upload after rebuilding with -v242-7ubuntu3 would do the trick
[14:24] <sil2100> rbalint: do you want to re-upload it in that case, or can the systemd SRU wait?
[14:45] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [source] (xenial-proposed) [2.02~beta2-36ubuntu3.23]
[14:56] -queuebot:#ubuntu-release- Unapproved: grub2 (xenial-proposed/main) [2.02~beta2-36ubuntu3.23 => 2.02~beta2-36ubuntu3.23] (core)
[15:29] -queuebot:#ubuntu-release- Unapproved: grub2 (xenial-proposed/main) [2.02~beta2-36ubuntu3.23 => 2.02~beta2-36ubuntu3.23] (core)
[15:58] -queuebot:#ubuntu-release- Unapproved: accepted python3.8 [source] (eoan-proposed) [3.8.0-3~19.10]
[15:59] -queuebot:#ubuntu-release- Unapproved: accepted python3.8 [source] (disco-proposed) [3.8.0-3~19.04]
[16:10] -queuebot:#ubuntu-release- Unapproved: gcc-5 (xenial-proposed/main) [5.4.0-6ubuntu1~16.04.11 => 5.4.0-6ubuntu1~16.04.12] (core) (sync)
[16:47] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (bionic-proposed/main) [1:18.04.34 => 1:18.04.35] (core)
[17:09] <bdmurray> vorlon: Should we do anything about verifying bug 1825655 or do you think that's unnecessary?
[17:14] <vorlon> bdmurray: I don't want to spend the time verifying it
[17:14] <bdmurray> vorlon: Should anybody though?
[17:15] <vorlon> bdmurray: I'm biased and you shouldn't take my word for it ;)
[18:11] <vorlon> xnox, rbalint: do you know why the systemd-pstore.service will have started failing in the autopkgtests on armhf?
[18:16] <rbalint> vorlon, no, seeing it failing for first time
[18:18] <vorlon> ok. I'm not aware of any recent infrastructure changes on the container runners that would account for this.  Could be a kernel behavior change
[18:21] <vorlon> fwiw to folks, when processing NBS I'm being very liberal in removing python-related packages that still have reverse-build-dependencies, based on my experience last cycle that things get into removal circular dependencies (new packages not migrating to release pocket because the old binary is still there)
[18:21] <vorlon> this may leave us with additional build failures come time of the archive test rebuilds, but I think it's the only sane way to progress this
[18:25] <infinity> Ick. :/
[18:26] <infinity> vorlon: Maybe instead of waiting to find them in a sea of rebuild issues, we can do a missing r-build-dep check when the py2/py3 mess is mostly shaken out?
[18:26] <infinity> Should be a reasonably simple grep-dctrl + glue.
[18:35] <vorlon> could do that, yeah
[19:45] -queuebot:#ubuntu-release- Unapproved: grub2 (bionic-proposed/main) [2.02-2ubuntu8.13 => 2.02-2ubuntu8.14] (core)
[19:46] -queuebot:#ubuntu-release- Unapproved: grub2-signed (bionic-proposed/main) [1.93.14 => 1.93.15] (core)
[19:54] -queuebot:#ubuntu-release- Unapproved: sg3-utils (bionic-proposed/main) [1.42-2ubuntu1 => 1.42-2ubuntu<IP_ADDRESS>] (core)
[20:46] <mwhudson> who let salt back into the release pocket in time to block the package i uploaded :)
[20:48] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (xenial-proposed/main) [1:16.04.27 => 1:16.04.28] (core)
[20:58] -queuebot:#ubuntu-release- Unapproved: accepted sg3-utils [source] (bionic-proposed) [1.42-2ubuntu<IP_ADDRESS>]
[21:00] <infinity> mwhudson: britney? :P
[21:02] <infinity> mwhudson: (Steve removed a version with an Ubuntu delta, and then auto-sync picked up a shiny new one, which is actually that one that was removed from testing)
[21:03]  * infinity will remove it harder.
[21:04] <infinity> mwhudson: Gone again.
[21:04] <mwhudson> infinity: mostly just griping, i think the tests will pass on retry
[21:04] <mwhudson> ok that works too
[21:05] <infinity> mwhudson: Well, removing it due to the RC Debian bug still looks correct.
[21:05] <mwhudson> infinity: oh this one? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930178
[21:05] <mwhudson> does look fun
[21:06] <infinity> I mean, fixing that bug would also work.
[21:06] <infinity> But either way, it needs a new upload to be not broken, so.
[21:08] <mwhudson> right now is not the best time to have python packages in the archive with flaky tests
[21:16] <vorlon> anyone looked at why octave 5 is so unhappy on ppc64el?
[21:27] <infinity> I haven't until just now, but uninstallable deps seems like a tractable problem.
[21:41] <vorlon> infinity: octave-control/ppc64el isn't failing due to missing build-deps but due to test failures
[21:43] <infinity> vorlon: The latest log says uninst.
[21:44] <vorlon> is that later than 3.2.0-3?
[21:44] <infinity> vorlon: Or do you mean a build of a new octave-control?
[21:44]  * infinity was looking at autopkgtests, not builds.
[21:44] <vorlon> right
[21:44] <vorlon> the autopkgtests are all failing because of build failures, meaning there is no build on the arch built against liboctave7 instead of liboctave6
[21:45] <infinity> vorlon: Oh wow, that testsuite output crosses my eyes something fierce.
[21:50] <mwhudson> it's ppc64el so try rebuilding with -O2?
[21:50] <infinity> Possibly, yes, but also wat.
[21:50] <mwhudson> he says without looking at the test logs at all
[21:50] <infinity> One failure is these not matching:
[21:50] <infinity> 1.0000    6.0000   11.0000    6.0000
[21:50] <infinity> 1 5 6
[21:50] <mwhudson> it could be fused multiply add but that usually gets s390x and arm64 too
[21:51] <infinity> Now, if we all agree that OBVIOUSLY, 11-6 is 5, then we match.
[21:52] <infinity> I suppose something getting optimised into oblivion could cause that sort of whackadoo, but fma or imblongdouble are also possible candidates.
[21:52] <mwhudson>   Location  |  Observed  |  Expected  |  Reason
[21:52] <mwhudson>      .          O(1x2)       E(1x1)      Dimensions don't match
[21:52] <mwhudson> wat
[21:52] <infinity> Look down.
[21:52] <infinity> And up.
[21:52] <infinity> Ish.
[21:52] <mwhudson> you're also right in that this test suite output is brainbending
[21:52] <infinity> I guess more up.
[21:53] <infinity> Above that is the assertion that failed, then above that you can see the mismatched structs.
[21:53] <infinity> Which are meant to match to 1e-4
[21:53] <infinity> And totally do.
[21:53] <infinity> Except that one where there's, y'know, 1 fewer element, and it's somehow subtracted one from the other.
[21:53] <infinity> Because magic.
[21:55] <mwhudson> yeah
[21:55] <mwhudson> both the failures are like that
[21:56] <infinity> MAGIC.
[21:58] -queuebot:#ubuntu-release- New binary: openems [s390x] (focal-proposed/universe) [0.0.35+git20190103.6a75e98+dfsg.1-1ubuntu1] (no packageset)
[21:59] -queuebot:#ubuntu-release- New binary: openems [ppc64el] (focal-proposed/universe) [0.0.35+git20190103.6a75e98+dfsg.1-1ubuntu1] (no packageset)
[22:01] -queuebot:#ubuntu-release- New: accepted openems [ppc64el] (focal-proposed) [0.0.35+git20190103.6a75e98+dfsg.1-1ubuntu1]
[22:01] -queuebot:#ubuntu-release- New: accepted openems [s390x] (focal-proposed) [0.0.35+git20190103.6a75e98+dfsg.1-1ubuntu1]
[22:01] -queuebot:#ubuntu-release- New binary: openems [i386] (focal-proposed/universe) [0.0.35+git20190103.6a75e98+dfsg.1-1ubuntu1] (no packageset)
[22:03] <infinity> mwhudson: If they're hand-crafting these structures, it could also be some bizarre assumption that all __powerpc__ is either 32-bit or big-endian, but I'd expect either of those to cause a lot more failures.
[22:03] <infinity> I suppose I should download some source and stop guessing.
[22:04] <mwhudson> infinity: i tried a build in my ppa forcing -O2 but apparently i got it wrong somehow
[22:05] <mwhudson> i guess dh-octave doesn't honour DEB_CFLAGS_MAINT_APPEND ?
[22:05] <mwhudson> oh wait probably want CXX variant
[22:07] <vorlon> OCFLAGS
[22:11] <mwhudson> infinity: ok not -O3 this time https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+build/18025678
[22:12] <mwhudson> infinity, vorlon: bad-test initramfs-tools/i386 pls?
[22:13] <mwhudson> test depends on linux-image-generic
[22:21] <infinity> mwhudson: Fixed.
[22:28] <vorlon> mwhudson: but how will we regression-test my i386->amd64 cross-grades
[22:29] <infinity> If debian/tests/control can install "foo:arch [arch]" style deps, we could make it work again.  No idea if that level of fancy would work.
[22:45] <mwhudson> hm i haven't gotten accepted mails from Ubuntu Installer<EMAIL_ADDRESS>for a few days
[22:45] <infinity> gmail?
[22:45] <mwhudson> y
[22:45] <infinity> Check spam?
[22:46] <mwhudson> yeah, done already not there
[22:46] <mwhudson> goes via fastmail i guess i should check its spam
[22:46] <mwhudson> hmm nothing
[22:46] <infinity> mwhudson: I got mine from today's uploads.
[22:47] <infinity> From<EMAIL_ADDRESS>Mon Nov 04 18:24:25 2019
[22:47] <infinity>  Subject: [ubuntu/focal-proposed] initramfs-tools 0.133ubuntu11 (Accepted)
[22:47] <infinity>   Folder: /home/adconrad/.maildir/new/1572891865.17522_1.loki              5278
[22:47] <infinity> Etc.
[22:47] <mwhudson> infinity: ok
[22:48] -queuebot:#ubuntu-release- New: accepted openems [i386] (focal-proposed) [0.0.35+git20190103.6a75e98+dfsg.1-1ubuntu1]
[22:55]  * mwhudson disables enough of noscript to be able to actually pay for fastmail
[23:16] -queuebot:#ubuntu-release- New binary: hypre [s390x] (focal-proposed/universe) [2.18.2-1] (no packageset)
[23:17] -queuebot:#ubuntu-release- New binary: hypre [ppc64el] (focal-proposed/universe) [2.18.2-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: hypre [amd64] (focal-proposed/universe) [2.18.2-1] (no packageset)
[23:28] -queuebot:#ubuntu-release- New binary: hypre [i386] (focal-proposed/universe) [2.18.2-1] (no packageset)
[23:35] -queuebot:#ubuntu-release- New binary: hypre [arm64] (focal-proposed/universe) [2.18.2-1] (no packageset)
[23:35] -queuebot:#ubuntu-release- New binary: hypre [armhf] (focal-proposed/universe) [2.18.2-1] (no packageset)


[01:03]  * Fujitsu waits for mthaddon's next response to the lovely discourse in progress in question #21397.
[01:19]  * Nafallo tickles Fujitsu
[01:19]  * Fujitsu swats Nafallo.
[03:25] <jtt> does anyone know  how i can search launchpad for the pattern  dpkg --configure -a
[03:26] <spiv> jtt: http://www.google.com/search?q=site%3Alaunchpad.net+%22dpkg+--configure+-a%22
[03:26] <jtt> spiv thanks
[03:42] <forsaken> anyone that can help me start submitting my code to launchpad? I created a project, but i'm getting a public key error...
[03:43] <forsaken> i think i submitted my keys...?
[06:52] <emgent> hello someone here?
[07:06] <Fujitsu> emgent: For what do you wish?
[07:08] <emgent> heya Fujitsu, only one questione about my launchpad page (https://edge.launchpad.net/~emgent)
[07:08] <emgent> i'd like know why "answers" icon dont give up
[07:09] <Fujitsu> Have you asked/answered any questions?
[07:09] <emgent> sure
[07:09] <Fujitsu> Ah, I see you have.
[07:09] <emgent> it'snt normal.. :O
[07:10] <Fujitsu> I'm not sure what algorithm is used to work out whether you get one or not; I have asked three questions on the launchpad project, and have the icon...
[07:10] <emgent> uhm
[07:11] <emgent> possible bug'
[07:11] <emgent> s/'/?/
[07:11] <Fujitsu> It's probably based on karma, and you seem to have no answers-karma.
[07:11] <emgent> false
[07:11] <emgent> i have answers-karma
[07:12] <emgent> https://edge.launchpad.net/~emgent/+karma
[07:12] <Fujitsu> I think you should, but https://launchpad.net/~emgent/+karma says you don't.
[07:12] <emgent> uhm
[07:12] <emgent> impossible :°
[07:12] <Fujitsu> It's possible I've caught it in the middle of the recalculation, where rendered values seem to be completely arbitrary, but that's unlikely.
[07:13]  * Fujitsu thinks an LP dev might have a better idea.
[07:13] <emgent> uhm ok, i will wait launchpad dev :P
[07:14] <emgent> thanks Fujitsu
[08:07] <paulvg> hello ./ i uploaded a package to ppa but it doesn't show up even if i select "All states", how come?
[08:09] <Fujitsu> paulvg: Did you get an Accepted email?
[08:10] <paulvg> ooh, lemme check...
[08:11] <paulvg> oh ic, it landed in the wrong inbox
[08:12] <paulvg> "Rejected:
[08:12] <paulvg> Signer has no upload rights at all to this distribution.
[08:12] <paulvg> Not permitted to upload to the RELEASE pocket in a series in the 'CURRENT' state."
[08:12] <Fujitsu> Ah.
[08:12] <Fujitsu> You tried to upload to Ubuntu, not your PPA.
[08:12] <paulvg> i did?
[08:12] <paulvg> lmao
[08:28] <paulvg> oh noes
[08:28] <paulvg> it rejected again :'(
[08:28] <paulvg> "Rejected:
[08:28] <paulvg> MD5 sum of uploaded file does not match existing file in archive
[08:28] <paulvg> Files specified in DSC are broken or missing, skipping package unpack verification."
[08:28] <Fujitsu> Aha.
[08:28] <Fujitsu> What package?
[08:29] <Fujitsu> What version, also?
[08:29] <paulvg> i uploaded freeswitch from svn, after changing the changelog and control
[08:29] <paulvg> svn snapshot
[08:29] <paulvg> 7080
[08:29] <Fujitsu> Different snapshot to last time?
[08:29] <paulvg> yup
[08:29] <Fujitsu> What was the exact version number you used?
[08:30] <paulvg> freeswitch_1.0~beta3-1ubuntu2
[08:30] <Fujitsu> Right, that's wrong.
[08:30] <paulvg> why
[08:30] <Fujitsu> You changed the .orig.tar.gz, did you not?
[08:30] <paulvg> no, i let debuild make it
[08:30] <Fujitsu> How did you upgrade to the SVN snapshot?
[08:31] <paulvg> the .orig directory is the actual svn snapshot
[08:31] <paulvg> svn update
[08:31] <paulvg> the other directory has my changes
[08:31] <Fujitsu> So the previous one wasn't in fact 1.0b3, but a SVN snapshot?
[08:32] <paulvg> well ofcourse, beta3 doesn't mean much afaik
[08:32] <Fujitsu> Anyway, you've apparently modified the .orig.tar.gz.
[08:32] <Fujitsu> If you do that, you must change the version number before the -.
[08:32] <paulvg> debuild made the tar
[08:32] <Fujitsu> That is, you probably want 1.0~beta3+svn7080-1ubuntu2.
[08:33] <Fujitsu> Er, -0ubuntu1, sorry.
[08:33] <Fujitsu> debuild won't modify the .orig.tar.gz, to the best of my knowledge.
[08:33] <paulvg> ok, strange though, things did workTM last time
[08:33] <Fujitsu> It worked last time because there was nothing to conflict with.
[08:34] <Fujitsu> This time, it sees the old freeswitch_1.0~beta3.orig.tar.gz, and screams when the new one is different, but with the same name.
[08:34] <paulvg> oic
[09:29] <paulvg> yay, it worked!
[09:29] <paulvg> thanks for the help
[09:30] <Fujitsu> paulvg: No problem. :)
[09:31] <paulvg> the email said accepted, it still doesn't show up on lp though but i guess it's allright
[09:32] <Fujitsu> It is on LP.
[09:32] <paulvg> where
[09:32] <Fujitsu> I saw it several minutes before you mentioned it.
[09:32] <Fujitsu> Oh, you're looking at +builds?
[09:32] <paulvg> https://edge.launchpad.net/~paulvg/+archive/+builds?build_text=&build_state=all
[09:33] <Fujitsu> Right, the builds won't be created for probably about another 30 minutes.
[09:33] <Fujitsu> If you take out /+builds..., you'll see it.
[09:33] <paulvg> oic, status "Pending"
[09:34] <Fujitsu> Correct.
[09:34] <paulvg> could take a while on a caturday i guess :p
[09:34] <Fujitsu> It will be published in 6 minutes.
[09:34] <paulvg> ?
[09:34] <Fujitsu> It will move from Pending to Published at XX:40.
[09:35] <paulvg> ok, kewl
[09:35] <paulvg> actually building it usually takes much longer though
[09:36] <Fujitsu> The builds will take some time to appear (this should be fixed in Launchpad 1.2.1, I believe), but should start building fairly quickly.
[09:36] <paulvg> that's great :)
[09:36] <Fujitsu> Once they've finished building, they should be published at the next publisher run, which is (IIRC) every 20 minutes.
[09:38] <paulvg> does there happen to be a way to disable lpia? it'll probably fail each time
[09:39] <Fujitsu> I don't think that's possible in a PPA. Normally in Ubuntu we'd tell it not to build on lpia in a file called Packages-arch-specific, but not in PPA.
[09:39] <Fujitsu> Why does it fail on lpia?
[09:40] <Fujitsu> It shouldn't take much to make it work.
[09:41] <paulvg> yeah ok let's leave it then, last time it was a "file not found" error :p strange though
[09:42] <Fujitsu> lpia is almost identical to i386.
[09:42] <Fujitsu> The instruction set is the same.
[09:42] <paulvg> then it should compile with -D__VIA_HACK__ which is default iirc
[09:48] <paulvg> well actually it might compile without but it may crash when using mod_portaudio
[09:50] <Fujitsu> Why would it do that?
[09:50] <paulvg> ic it uses #if defined( __i386__ ), if lpia doesn't define that this should always be safe, but it's just a minor issue anyway :p
[09:52] <paulvg> because of 3 sse2 instructions... but anyway i hope the build works, i'll worry about lpia later if it does
[09:53] <Fujitsu> Ah.
[10:01] <emgent> some launchpad devel here?
[10:07] <Fujitsu> emgent: It's a weekend, so you might not be able to find anyone.
[10:07] <emgent> heheh :)
[10:18] <paulvg> lp seems unsure when the build started: https://edge.launchpad.net/~paulvg/+archive/+build/484012
[10:19] <paulvg> or what builder it's on
[10:21] <Fujitsu> paulvg: The fields are duplicated when it's building - I reported that bug a few weeks ago. You'll find the real fields at the bottom.
[10:21] <Fujitsu> Note that the build has just failed, so the duplicated fields are no longer present.
[10:22] <Fujitsu> Bug #177824
[10:22] <ubotu> Launchpad bug 177824 in soyuz "Build page for currently building builds has duplicate fields" [Medium,In progress] https://launchpad.net/bugs/177824 - Assigned to Celso Providelo (cprov)
[10:32] <paulvg> can i patch this without rebuilding the .orig?
[10:33] <Fujitsu> As long as you don't modify the .orig.tar.gz, yes.
[10:33] <paulvg> but need to +1 the version number, right?
[10:34] <paulvg> +i
[10:34] <Fujitsu> Just make it ubuntu2, right.
[10:38] <paulvg> hm, i think i'm doing it wrong... the directory is called freeswitch-1.0~beta3+svn7090 not freeswitch-1.0~beta3+svn7090-0ubuntu2
[10:38] <Fujitsu> paulvg: No, that's right.
[10:38] <Fujitsu> The dash seperates the upstream and Debian (or Ubuntu, in this case) versions.
[10:38] <paulvg> well ok then -_-'
[10:46] <paulvg> is this anything to worry about? "bad-distribution-in-changes-file gutsy"
[10:47] <Hobbsee> no
[10:47] <paulvg> and the tonnes of W: freeswitch source: source-contains-svn-control-dir
[10:48] <Kmos> paulvg: that yes.. remove all .svn
[10:49] <Hobbsee> paulvg: W means warning.  E means error.
[10:49] <Hobbsee> paulvg: still, some warnings are important
[10:49] <paulvg> i knew that -_-'
[11:05] <paulvg> kmos: i'll look into getting rid of .svn later, i hope the build works this time
[11:06] <paulvg> gotta run, thanks for all the help!
[11:07] <paulvg> nice day y'all
[11:07] <LucidFox> I have several .po files stuck in the translation import queue, the oldest one since October. Could someone look into this?
[11:08] <Hobbsee> LucidFox: it's a saturday
[11:10] <LucidFox> Heh. What would be a better day to ask?
[11:10] <Fujitsu> Not a weekend, where the Canonical employees won't be here.
[11:10] <Hobbsee> LucidFox: UK working week
[11:15] <ubotu> New bug: #180523 in launchpad "canceling duplicates is very unintuitive" [Undecided,New] https://launchpad.net/bugs/180523
[11:19] <Fujitsu> Dupe.
[11:19]  * Fujitsu finds it.
[11:56] <jel> Hi guys :)   Reading the PPA stuff, it seems to say that only x86/amd64 are supported.  Is there a way to make arch-independent stuff (packages for python code)?
[11:59] <Kmos> jel: lpia is also supported
[12:00] <Hobbsee> Fujitsu: is it arch:  all or arch: any? in debian/control for that?
[12:00]  * Hobbsee can never remember
[12:00] <Kmos> jel: just put "any" is Architecture: in debian/control.
[12:00] <Kmos> *as
[12:06] <Fujitsu> jel: Architecture independent stuff is architecture `all'
[12:06] <Fujitsu> Not `any'.
[12:06] <Fujitsu> jel: For an example, check pretty much any python-* package.
[12:16] <jel> OK, thanks :)
[12:23] <IntuitiveNipple> Could anyone solve some confusion I have over a PPA upload that shows as Published, but it is only there as source files (no binaries) and there's no build reports?
[12:24] <Hobbsee> IntuitiveNipple: the build queue is probably long
[12:24] <Hobbsee> or ppas are borken
[12:25] <IntuitiveNipple> Ahh... so, having got the Accepted email and showing as Published doesn't imply something was forgotten then?
[12:25] <Hobbsee> IntuitiveNipple: how long ago were they uploaded?
[12:25] <Hobbsee> IntuitiveNipple: what was it?
[12:25] <Hobbsee> and what's your LP id?
[12:26] <IntuitiveNipple> about an hour - I've done a new awstats package for 6.7 which doesn't 'have' binaries of course (perl scripts)
[12:26] <IntuitiveNipple> https://edge.launchpad.net/%7Eintuitivenipple/+archive
[12:26]  * Fujitsu looks too.
[12:26] <IntuitiveNipple> It builds fine in a pbuilder locally, which is why I've got confused :)
[12:27] <Fujitsu> Ah, it's very fresh.
[12:27] <Fujitsu> Give it half an hour to get builds, then they'll build.
[12:27] <IntuitiveNipple> btw... I've just uploaded a better version 0ubuntu2~ppa1 - forgot to set the proper version 1st time around :)
[12:27] <Fujitsu> Ah.
[12:27] <Fujitsu> So the previous version might have got somewhere.
[12:27] <Hobbsee> it's just built on i386, too
[12:27] <IntuitiveNipple> ok... what got me is there were no logs, and no status saying "waiting to be built" - that "Published" sounds kinda final :)
[12:28] <Fujitsu> Published refers to the sources.
[12:28] <Hobbsee> https://edge.launchpad.net/~intuitivenipple/+archive/+builds?build_text=&build_state=all
[12:28] <Hobbsee> ^ is the binaries
[12:28] <IntuitiveNipple> well darn me! It only did that build right now to embarrass me!
[12:29] <Fujitsu> IntuitiveNipple: The builds should be created within about 40 minutes of your upload. They should start building soon after that.
[12:29] <IntuitiveNipple> Ok... thanks... being the first one I've tried I was sure I'd got it wrong :)
[12:30] <IntuitiveNipple> There ought to be a "pending" state in the build records... save idiots like me getting confused
[12:31] <Fujitsu> IntuitiveNipple: There is a pending state.
[12:31] <Fujitsu> It is, in fact, called `Pending'.
[12:31] <Fujitsu> The problem is that the build-creating bit of Launchpad can't quite handle the load of all these hundreds of thousands of builds, so takes half an hour to run.
[12:33] <Fujitsu> So the builds don't appear in the first place until a second or two before they start building.
[12:33] <IntuitiveNipple> "pending" ? Hmm, up until that build just now, there was nothing show for 'build_state=all'
[12:33] <Fujitsu> This should be fixed in Launchpad 1.2.1, due in a couple of weeks.
[12:33] <IntuitiveNipple> ahhh ok... so there's sort of a 'hole' then between upload/publish and build
[12:33] <Fujitsu> Yes.
[12:34] <Fujitsu> A separate process looks for new uploads, and creates the build records.
[12:34] <IntuitiveNipple> It's pretty cool as it is; I think the problem is the guides don't show a step-by-step expectation of what to see, they leave a lot assumption in this regard. I was reading all the PPA guides and meeting logs for clues
[12:35] <Fujitsu> Well, it will hopefully make more sense in a couple of weeks. I've seen this question a lot lately.
[12:35] <IntuitiveNipple> I'm glad I'm not alone :)
[12:36] <IntuitiveNipple> I'd have been ok if the guide showed an actual session with what to expect for a successful process start to end
[12:36] <iKs> Hello.
[12:37] <Fujitsu> Hello iKs.
[12:37] <iKs> I'm trying to commit to my branch in Launchpad
[12:37] <iKs> and I basically get told that there is a lock, put by me, that prevents me from doing that
[12:37] <iKs> Unable to obtain lock lp--1220469780:///lock
[12:37] <iKs> locked 17 hours, 38 minutes ago
[12:37] <iKs> Will continue to try until 12:39:50
[12:38] <iKs> (and "held by [myemailadress] on [mycomputer]" also)
[12:38] <Fujitsu> Bleeergh.
[12:38] <Fujitsu> Oh.
[12:38] <iKs> How do I tell bazaar to take that lock out ? :D
[12:38] <Fujitsu> So it's not the LP-lock-holding bug.
[12:38] <Fujitsu> bzr break-lock
[12:38] <iKs> ok thanks
[12:38] <iKs> no I aborted a push I think
[12:38] <Fujitsu> OK. You probably want to bzr push --overwrite, then.
[12:39] <iKs> Why ?
[12:39] <Fujitsu> I'm not sure how well it will recover from a partial initial push.
[12:39] <Fujitsu> Or was it not an initial push?
[12:39] <iKs> it was an initial push :)
[12:40] <iKs> but since I'm in Iran right now, tunneling through a serv er in France :D
[12:40] <iKs> It's a bit slow ^^
[12:40] <iKs> i'll do
[12:40] <iKs> that*
[12:40] <Fujitsu> Ah yes, it can get slow.
[12:40] <iKs> Thanks a lot anyways
[12:40] <Fujitsu> No problem - I hope it ends up working for you.
[12:41] <IntuitiveNipple> Somethin else I've just noticed, whilst I'm at it! The package is an _all.deb but none of the report info makes that clear ( the full .deb isn't shown that I can find) and the build entry has specifically inserted 'i386' in places to make it confusing. In the build-log itself it does say " ../awstats_6.7+dfsg-0ubuntu1_all.deb" but thats all I can find.
[12:41] <iKs> Which protocol should I use on LP, bzr+ssh or sftp ? (in your opinion)
[12:42] <Fujitsu> bzr+ssh, if at all possible.
[12:42] <Hobbsee> IntuitiveNipple: i386 builds arch: all packages
[12:42] <Fujitsu> IntuitiveNipple: arch all builds are identical to i386 builds, except that the .deb is named differently and is published on all archs.
[12:42] <iKs> Fujitsu: why ? In which way is it better ?
[12:42] <Hobbsee> iKs: faster
[12:42] <iKs> Faster maybe ?
[12:42] <iKs> OK :)
[12:42] <iKs> Thanks a lot.
[12:42] <Fujitsu> iKs: It uses bzr on the other end too, and is much faster.
[12:43] <IntuitiveNipple> Is it? Ahhh thanks. Another little thing needs documenting then :)
[12:44] <Fujitsu> Bug #40096
[12:44] <ubotu> Launchpad bug 40096 in soyuz "do not show architecture 'all' builds as i386" [Medium,Confirmed] https://launchpad.net/bugs/40096 - Assigned to Diogo Matsubara (matsubara)
[12:45] <IntuitiveNipple> :)
[12:45] <Fujitsu> It was called `simple' more than 18 months ago, so don't count on it being fixed soon. Documentation is probably a good idea.
[12:46] <Fujitsu> Hobbsee: Do we know how the extended PPA FAQ is coming along?
[12:46] <IntuitiveNipple> yeah... just a note in the quickstart guide would help, especially as the people coming to PPA are more likely to be packaging novices
[12:46] <IntuitiveNipple> There's a few fixme's and blanks in the draft, when I looked earlier
[12:55] <Hobbsee> Fujitsu: no, but it's pending on people who are actually paid to do it
[12:55] <Hobbsee> and that it's certainly planned to be done at some point
[12:57] <Hobbsee> the sooner the better, obviously, but i don't overly want to write it myself, in current state
[13:10] <ubotu> New bug: #180538 in malone "Email interface doesn't allow escaping quotes in summary line" [Undecided,New] https://launchpad.net/bugs/180538
[13:50] <ubotu> New bug: #180554 in launchpad "karma dont work fine, answers karma dont work. Answers icon in "most active in" dont work too" [Undecided,New] https://launchpad.net/bugs/180554
[14:35] <emgent> heya fabbione :)
[14:35] <fabbione> hi
[14:59] <mpt> Gooooooooooooooooooooooooood afternoon Launchpadders!
[15:00] <geser> Hi mpt
[16:36] <ubotu> New bug: #180591 in launchpad "Can't edit/update the details that login.launchpad.net sends (dup-of: 177401)" [Undecided,New] https://launchpad.net/bugs/180591
[16:46] <ubotu> New bug: #180593 in launchpad "Add option to disable @ubuntu.com email forwarding" [Undecided,New] https://launchpad.net/bugs/180593
[17:25] <mpt> Egads
[18:58] <shiyee> when pushing to a LP bzr branch, i get the error "bzr: ERROR: Can't rename /srv/sm-ng/push-branches/00/00/14/e2/.bzr/repository/lock/auimcuu0ta.tmp to /srv/sm-ng/push-branches/00/00/14/e2/.bzr/repository/lock/held: /srv/sm-ng/push-branches/00/00/14/e2/.bzr/repository/lock/held already exists". I think a previous push was interrupted, will this fix itself, or can anyone help me?
[19:00] <jelmer> shiyee: you may be able to run "bzr break-lock"
[19:01] <shiyee> jelmer: nope, same error
[19:01] <shiyee> oh wait...
[19:02] <shiyee> jelmer: thx alot, that did the trick :-)
[20:06] <mtaylor> statik: someone should write a mylyn plugin for launchpad
[20:21] <_flx> hi
[20:21] <_flx> I would need help on the Bazaar system
[20:21] <_flx> I registered a main branch on Launchpad
[20:22] <_flx> aud made myself a dev branch
[20:22] <_flx> I made some changes in the dev branch
[20:22] <_flx> and clicked the "Propose for merging" in Launchpad so these changes could be merged into my trunk
[20:22] <_flx> but I don't quite understand how to merge those together
[20:23] <LarstiQ> _flx: heh, you're probably the one who would be doing the merging :)
[20:24] <LarstiQ> _flx: cd main.branch; bzr merge url-to-dev-branch; *review changes*; bzr commit
[20:25] <_flx> LarstiQ, Oh.. I see.. I don't have the "main branch" on my system
[20:25] <LarstiQ> _flx: you do have the dev branch though?
[20:25] <_flx> LarstiQ, Yes
[20:27] <_flx> I "kind of" transformed my trunk branch into a dev branch
[20:27] <_flx> but if I "bzr info"
[20:27] <LarstiQ> _flx: I guess this turns into a question of workflow. If your main branch does not have any new revisions you could just push your dev branch to it
[20:28] <LarstiQ> _flx: but if you want to more clearly mark that this work was done in a seperate branch, then merging would be the way to go
[20:29] <_flx> LarstiQ, Yes this is what I previously made (bzr push into the trunk), But since I'm trying to understand the Bazaar way of doing things and since I want to learn the "right way". If I understand, the trunk is not a dev branch itself. It is more a "merge location" for task-branches to be merged to
[20:30] <LarstiQ> _flx: that is indeed one way of working
[20:31] <_flx> LarstiQ, sounds good to me, altough I don't quite see the "P2P" aspect of it
[20:33] <LarstiQ> _flx: http://bazaar-vcs.org/Workflows may help
[20:34] <_flx> LarstiQ, What I evoked previously is, I think, the Decentralized with shared mainline
[20:35] <_flx> The thing I don't understand is why SVN couldn't do it. As far as I can see, it can also create branches and merge them together/into the mainline
[20:37] <LarstiQ> _flx: it can, but not decentralized, it needs to be done in the central repository, so you need connectivity to it at all times. That makes branching much more expensive so the incentive to do it isn't there as much.
[20:38] <LarstiQ> _flx: and the merging support is way more painful, although the svn people are working on that
[20:39] <_flx> LarstiQ, So basically what you are saying is that I can take a snapshot from lets say DevA, branch it, make some changes than publish this into the mainline when connectivity allows it ?
[20:39] <LarstiQ> _flx: yes
[20:40] <LarstiQ> _flx: or decide it's all wrong and never publish it, that's a great freedom of being decentralized
[20:40] <_flx> LarstiQ, Sounds interresting. Another question, what is the difference between the "bzr init-repo URL" and "bzr branch URL" ?
[20:41] <_flx> LarstiQ, I see. Launchpad is here to help publish/host branches.
[20:42] <LarstiQ> _flx: the first will create a repository at URL which can be used by multiple branches to store their revisions. The second will make a branch locally, and copying the information from the branch at URL
[20:42] <LarstiQ> _flx: exactly
[20:42] <LarstiQ> _flx: (well, and bugtracking/translations/blueprints etc)
[20:43] <_flx> LarstiQ, so the first command would make my "disk" to be avaiable to all for branching/commiting ?
[20:43] <LarstiQ> _flx: there is one notable workflow missing from that wiki page, and that's completely decentralized mesh merging. The drawback of that is that it's complete anarchy.
[20:43] <LarstiQ> _flx: not exactly
[20:44] <LarstiQ> _flx: you could just branch or bzr init to get a branch you can work and commit in
[20:45] <LarstiQ> _flx: but if you do that under an area you have created a repository, the branches will share it as a storage for revisions, which takes less diskspace and can often be faster
[20:46] <_flx> uhm ok
[20:46] <_flx> Sounds less "egoist"
[20:47] <LarstiQ> _flx: a typical way to use it would be: bzr init-repo $HOME/src/bzr; cd $HOME/src/bzr; bzr branch http://bazaar-vcs.org/bzr/bzr.dev (this will create a branch at $HOME/src/bzr/bzr.dev); bzr branch bzr.dev bzr.lq
[20:48] <LarstiQ> _flx: you then have two branches, a local mirror of bzr.dev, and a personal bzr.lq branch to work in. But the storage cost is only a few kilobytes more than if you had only the bzr.dev mirror
[20:49] <_flx> ok I just did that. Let me do some test, I might have some other questions
[20:50] <LarstiQ> sure.
[20:50] <LarstiQ> _flx: if they're all bzr related, we can also move it to #bzr
[20:50] <_flx> It will be Launchpad related in few minutes ;)
[20:52] <_flx> Ok I made a download of the trunk and a branch from it
[20:52] <_flx> I made a change into my branch (renamed a file)
[20:52] <_flx> if I "bzr commit", the change will be local only isn't it ?
[20:55] <LarstiQ> yes
[20:55] <ubotu> New bug: #180644 in launchpad-bazaar "Branch status menu has long clumsy caption" [Undecided,New] https://launchpad.net/bugs/180644
[20:56] <_flx> LarstiQ, I didn't made a "bzr push" and tried to merge the branch into the trunk but it says it have nothing to do
[20:57] <_flx> LarstiQ, What is the error I made ?
[20:58] <LarstiQ> _flx: if there is nothing to do, all the revisions in the branch you are trying to merge from are usually already contained in the branch you're merging into
[20:58] <LarstiQ> _flx: from the trunk, what does 'bzr missing url-to-dev' report?
[20:59] <_flx> LarstiQ, it reports that I am missing 1 revision
[21:00] <_flx> LarstiQ, now the merge works... I don't understand, I didn't do anything
[21:00] <LarstiQ> _flx: what exact command did you give before when it reported nothing to do?
[21:00] <_flx> LarstiQ, Oh, I forgot a dot... I wrote ./branches instead of ../branches
[21:02] <LarstiQ> _flx: ah :)
[21:02] <_flx> LarstiQ, when trying to push to Launchpad, it says that there is no new revision to push
[21:03] <LarstiQ> _flx: after merging, there is no new revision created. You will have to commit first before that happens.
[21:03] <LarstiQ> _flx: it's good practice to check the merge went ok before doing so, with the help of bzr status and bzr diff for example
[21:05] <_flx> LarstiQ, ok, it worked. Another thing is when trying to push my dev branch to Launchpad, it told me that my branches had diverged
[21:06] <_flx> LarstiQ, also, Launchpad is still showing the "Branches proposed to be merged into this one" line
[21:08] <LarstiQ> _flx: when branches each have new revisions that are not in the other branch, they have diverged, use bzr missing to find out what happened
[21:12] <_flx> LarstiQ, it complains that the branch has one missing rev and the trunk has one extra rev but its the same rev...
[21:12] <LarstiQ> _flx: absolutely the same?
[21:13] <_flx> LarstiQ, yes
[21:13] <LarstiQ> _flx: ie, same revision ids? (bzr missing --show-ids)
[21:14] <_flx> yes
[21:15] <LarstiQ> _flx: could you pastebin that output?
[21:15] <_flx> LarstiQ, yes, sec
[21:16] <_flx> LarstiQ, http://pastebin.com/d3c6f2c00
[21:19] <LarstiQ> _flx: ah, I didn't realise you were running it from both sides. You only have to run missing once and it will tell you if/what you have extra or are missing. From the other sides just swap the two categories.
[21:19] <LarstiQ> _flx: so this is entirely fine locally
[21:19] <_flx> LarstiQ, Okay so I guess it is normal
[21:20] <LarstiQ> _flx: if you would 'bzr push ../../trunk' locally from experimental-0.1, it would update the trunk with the new revision
[21:20] <LarstiQ> _flx: but which branch was it that complained about divergence?
[21:20] <LarstiQ> or, which url
[21:20] <LarstiQ> since branches are identified by url
[21:20] <_flx> experimental-1.0 locally vs experimental-1.0 Launchpad
[21:21] <LarstiQ> _flx: ok, so could you run missing between those two?
[21:23] <_flx> http://pastebin.com/d2938db90
[21:25] <LarstiQ> _flx: ok, so there it's genuinely diverged.
[21:25] <_flx> LarstiQ, What can I do to fix this ?
[21:26] <LarstiQ> _flx: if you want to have both revisions, merge the launchpad version into your local one, fix, commit, push.
[21:26] <LarstiQ> _flx: if you don't care about the launchpad one, bzr push --overwrite
[21:26] <_flx> good
[21:27] <_flx> LarstiQ, it worked
[21:27] <_flx> LarstiQ, Now in Launchpad, how can I get rid of the "This branch is proposed for merging into"
[21:28] <LarstiQ> _flx: now that is actually something I'm not familiar with, give me a minute to read up on it
[21:37] <_flx> LarstiQ, I found a way to just delete the proposal. Thx for all your advices, you were very helpful
[21:37] <LarstiQ> _flx: np, pleased to be of help


[00:23] <raevol> philipballew: sounds like a plan
[00:34] <philipballew> raevol, yeah dude!
[02:08] <rww> i think i spent an hour on Ingress today and will not go to Diablo Valley LUG today :P
[02:46] <nhaines> rww: I hope you joined the Resistance.  :P
[03:08] <rww> nhaines: yep!
[03:08] <rww> captured two portals :3
[03:13] <nhaines> rww: yay!  I need to capture one more unique portal and I get a new badge.  I'll Jarvis it if I have to.


[01:11] <kwwii> sleep now
[12:18] <nickm1> hello is there someone i could talk to? my name is Nick McMahon from the ubuntu marketing team
[12:21] <nickm1> i'm looking to find an ubuntu color chart
[12:37] <nickm1> well, colour chart :)
[04:20] <newz2000> I'd love to see ken's concepts, but bootsplash.org won't resolve for me. Not even if I use the coral cache. :-(
[04:23] <newz2000> oh, got it. Man that looks sharp.
[04:28] <newz2000> klepas: got a moment?
[04:29] <klepas> sure, what's up?
[04:29] <newz2000> I'm going to be restructing the server that hosts art.ubuntu.com
[04:30] <newz2000> Do you have any special config there that you want preserved?
[04:31] <klepas> sorry, i didn't not create or help set it up
[04:31] <klepas> henrik would be the person to consult in that regard
[04:43] <newz2000> sorry for the delay, got caught up in a big dns question
[04:44] <newz2000> klepas: Yeah, everyone says that server can be nuked, I just knew that you've put some effort into it and I wouldn't want you to loose anything
[04:45] <klepas> i haven't really done anything other than add submitted content
[04:45] <newz2000> ok. I'm not going to delete that content, just move it around
[04:45] <klepas> so basically i had admin rights and used them to approve submissions
[04:45] <klepas> good :)
[04:45] <klepas> what is your plan for the system?
[04:45] <newz2000> We're going to set it up for shared hosting so the loco teams can have free web space.
[04:46] <newz2000> ubuntu-au.org and etc.
[04:46] <newz2000> That server is way underutilized and there are a lot of people wanting hosting
[04:46] <klepas> :)
[04:46] <klepas> no i mean in regards to artwork...?
[04:47] <newz2000> Are you asking what artwork I'm going to make, or what I'm going to do with the existing artwork?
[04:48] <klepas> well the system supporting the existing artwork
[04:48] <newz2000> Hopefully I wont' change anything except the location of the files on the disk.
[04:48] <newz2000> If we want to open it back up, that's fine. If we want to kill it, that's fine too.
[04:49] <klepas> well make sure we have a backup of it all
[04:49] <newz2000> You bet.
[04:49] <newz2000> I ran webalizer on the log files for that site... it gets a remarkably number of hits
[04:50] <newz2000> In June it got over 5,000 page views and > 300,000 hits PER DAY
[04:51] <newz2000> Sorry, that's 30,000 hits, not 300,000.
[04:55] <klepas> that is a fairly large amount
[04:55] <klepas> indicates the site needs to be looking polished and has to be accessable to it's users
[04:55] <klepas> because that number of visitors would include a lot of disheartened people
[06:11] <newz2000> anyone feeling resourceful with icons?
[06:12] <newz2000> I'm doing the bzr website and wanted three icons. I've found two great ones in tango-scalable, a third is OK but not quite right
[06:13] <newz2000> I need a book, and stock_new-address-book.svg is close, but its the wrong perspective
[06:13] <newz2000> It's laying down and it would look better standing up
[06:13] <newz2000> My attempts look like a rectangle
[06:13] <newz2000> oh wait, I found the dictionary icon, it will work just fine
[06:33] <klepas> hehe :)
[06:37] <newz2000> know of a way to do something like "outer glow" in inkscape?
[06:39] <klepas_Zzz> select the largest background object, duplicate it, move it to the bottom, press ctrl + shift and use your mouse to pull the objects arrows to make it large
[06:39] <klepas_Zzz> and now change the fill to whatever you need to acheive the right colour for a glow :)
[06:39] <klepas_Zzz> play around with the transparency/opacity, gradients and so forth
[06:40] <klepas_Zzz> that's it for me, 'night
[06:40] <newz2000> thanks, I'll try it
[06:40] <newz2000> night
[07:40] <troy_s> hi sara_
[07:41] <sara_> hey troy
[07:42] <sara_> I am wondering how would a project go about getting help fromt he art team
[07:42] <troy_s> the mailing list is sort of our main avenue
[07:42] <troy_s> for discussion currently
[07:42] <troy_s> and we try to use the spec procedure at launchpad.
[07:42] <sara_> but Ineed to join that right
[07:43] <sara_> spc procedure?
[07:43] <troy_s> the mailing list is probably your best starting point...
[07:44] <troy_s> what in particular do you need?
[07:44] <troy_s> if you could wiki the needs, it is possible that you MIGHT get someone who can help.
[07:44] <troy_s> hi dinda.
[07:44] <dinda> hi Troy_s et al
[07:44] <sara_> We are working on an ubuntu magazine, and we are getting to the point where we might need some art work and maybe some help
[07:45] <sara_> Yeah we have a wiki and are restructuring so that we have a art work page and we are going to have a list of thing to do soon
[07:46] <troy_s> well it might be useful to get in touch with the mailing list.  unfortunately it still has some unfortunate bad habits on it, but it is evolving into a more professional direciton.
[07:47] <sara_> ok so as soona s we have something up I guess I'll make apost
[07:47] <troy_s> that would be great
[07:47] <troy_s> we have some sample specs there
[07:47] <troy_s> if you could at least wiki the needs, and be clear and specific, perhaps offering some samples
[07:47] <troy_s> or something
[07:47] <troy_s> it would greatly aid the folks who need to see that sort of thing :)
[07:48] <troy_s> photo based items i know i can knock off relatively quickly for you
[07:48] <troy_s> illustration will take longer.
[07:48] <troy_s> and i don't know how many on the team are adept illustrators.
[07:48] <sara_> ok, I'll work on it and hopefully have a nice list up
[07:48] <dinda> sara_, the marketing team still seems unclear on how to use the Spec/wiki/Launchpad for developing/tracking things
[07:49] <dinda> I keep meaning to try to post to the mailing list some of the process I observed but have been busy
[07:49] <troy_s> dinda:  how do you know that?
[07:49] <troy_s> ahh.
[07:49] <sara_> yeah, I am sorry to say I am in part at fault for that at least for my part
[07:49] <troy_s> yes the spec system is terrific
[07:49] <dinda> from the mailing list and from being in paris
[07:49] <troy_s> for quick and easy references
[07:49] <troy_s> dinda,  you were in paris?  *embarassed*
[07:50] <dinda> lol - yeah and you were extremely jetlagged  ;)
[07:50] <dinda> as I recall :)
[07:50] <troy_s> LOL
[07:50] <troy_s> indeed.
[07:50] <sara_> didnda you should probably post, since I know I am doing things wring, but really don't know how to do them right
[07:51] <troy_s> crappers... didn't realize that was you.
[07:51] <troy_s> sara_, the more folks who get up to speed on launchpad etc
[07:51] <troy_s> the more can spread the knowledge.
[07:51] <dinda> alot of good work happened there and I hope the marketing team can learn from the artwork group's development
[07:52] <sara_> I'll take a look at the marketing team work and see what we can learn from it
[07:52] <dinda> there are lots of very enthusiastic folks in the marketing group but I'd hate to see duplication of effort avoided if possible
[07:53] <sara_> yeah, I know what you mean I have 3 similar proposals on my mailbox that would of done with collaboartion
[07:54] <troy_s> that's why specs are wonderful
[07:54] <troy_s> you can easily cite a link
[07:54] <troy_s> with full design needs
[07:54] <troy_s> without typing 'we have been over this a 1000000 times, so here is a copy of the text...'
[07:54] <troy_s> laf.
[07:56] <sara_> I just took a look at you specs on launchpad and I am certain that our projects would greatly benefit from them
[07:56] <dinda> exactly, here's the project spec, everyone can throw darts at it, and it can move forward
[07:57] <troy_s> the idea behind the specs is to get them started in x cycle
[07:57] <troy_s> get them fleshed out while everyone does their official work for x cycle
[07:57] <troy_s> and have them ready for attacking in x+1
[07:59] <sara_> great, I'll keep on looking and maybe I'll pick some examples so that we can get started
[07:59] <troy_s> those specs
[08:00] <troy_s> are based on martin pitt's very good samples
[08:00] <troy_s> so they aren't out of tangent.
[08:00] <troy_s> martin works with the dev team and has a couple of exemplary specifications on launchpad.
[08:00] <sara_> uhh. I came here looking for art help and I am getting help on managing the project. Thanks
[08:00] <troy_s> so i borrowed his outline
[08:00] <troy_s> well you can't really build a house without a blueprint
[08:01] <sara_> exactly. I just realized that I am missing ameeting on the marketing channel, so I got to go
[08:01] <dinda> was that now?
[08:02] <sara_> no wrong time
[08:02] <sara_> ooops. I got the tabas messes up
[08:02] <sara_> the mmeting is the 13th
[08:03] <dinda> troy_s; development seems to be moving well for the artwork team this cycle
[08:03] <troy_s> dinda, plodding like a beast of burden
[08:03] <troy_s> hopefully people who can work within a professional structure will continue to appear as they have been.
[08:04] <dinda> it was great to see Ken W get picked up for the kubuntu stuff - his work is great
[08:04] <troy_s> eventually, when we hit critical mass and things start to run themselves, i will attempt to bring in some very gifted folks.
[08:04] <troy_s> yes... he needs to get some outlines and such in place...
[08:04] <troy_s> which is why i was all for getting some textural references in place for ubuntu.
[08:04] <troy_s> it is hard to hit a moving target.
[08:04] <troy_s> right now, kubuntu is too hodgey podgy too.
[08:05] <troy_s> but again, that will evolve hopefully.
[08:05] <dinda> definitely
[08:05] <dinda> it's all really a much larger project than most realize
[08:06] <troy_s> yes... i think the open source art community hasn't really hit the professional level that it needs to
[08:06] <troy_s> and it is largely because everyone fritters away doing their own thing...
[08:06] <troy_s> which doesn't see the 'forest through the trees'
[08:06] <troy_s> how's texas?  hot?
[08:06] <troy_s> you are in texas aren't you?
[08:06] <dinda> hotter than hades with mosquitoes to boot
[08:07] <dinda> yip, Galveston, near Houston
[08:07] <troy_s> mosquitoes are great if you are a bat
[08:07] <dinda> yeah we saw about two million of them last week in Austin - great - no bugs by them
[08:08] <dinda> I'm hoping that the artwork model will help with marketing and then eventually my area - training
[08:08] <troy_s> official ubuntu training?
[08:08] <dinda> yip
[08:09] <troy_s> wow
[08:09] <troy_s> are you a canonical employee as of now>
[08:09] <dinda> training is always the last thing
[08:09] <dinda> nope. . . someday I wish  ;)
[08:09] <troy_s> everything is the last thing until people see a 'critical mass' point... then everyone wants to help.
[08:10] <dinda> exactly, once the product is built and finally adopted then someone will realize we might need to actually offer training to larger installs - like the 40k install shown in paris
[08:12] <dinda> but I'm going to start the ball rolling and work on some specs and wiki pages - there's already alot in place that can hep
[08:12] <dinda> help
[08:23] <dinda> gotta run off for awhile - nice chatting with you all
[08:32] <newz2000> Fill in the blank:
[08:32] <newz2000> The Ubuntu Artwork team exist to _______.
[08:33] <troy_s> eek
[08:33] <troy_s> look to mark's quotations as a good starting point.
[08:33] <newz2000> good idea
[08:33] <troy_s> i believe the team exists to manage the aesthetic development of the entire Ubuntu project
[08:33] <troy_s> although those are grandiose words right now considering where we are at.
[08:33] <troy_s> :)
[08:34] <newz2000> Something like, "make the Ubuntu desktop ever more usable and attractive."
[08:35] <troy_s> it extends beyond that in scope
[08:35] <troy_s> it will eventually encompass the marketing aesthetic, etc.
[08:35] <troy_s> as well as other advertising related matters.
[08:36] <newz2000> Anything you can think of that needs to be included currently in that list?
[08:36] <newz2000> "Ubuntu desktop and its diriviatives..."
[08:37] <newz2000> :-( speling
[08:37] <newz2000> (sic)
[08:38] <troy_s> laf
[08:38] <troy_s> well ... again, i think that is the futures component.
[08:39] <troy_s> currently, we will be lucky if we can actually coordinate a usplash
[08:39] <troy_s> :)
[10:51] <kwwii> moin
[11:00] <kwwii> I just posted the svg sources to the pngs I sent to the list, in case someone is interested
[11:01] <kwwii> anyone seen frank lately?


[05:49] <hikiko> hi
[06:41] <pitti> Good morning
[06:55] <didrocks> good morning!
[06:57] <pitti> bonjour didrocks !
[06:58] <didrocks> hey pitti
[07:44] <larsu> good morning!
[07:46] <pitti> hey larsu!
[07:46] <larsu> morgen pitti!
[08:01] <didrocks> hey larsu!
[08:01] <larsu> bonjour didrocks!
[08:06] <desrt> happy 9am CEST, everyone!
[08:06]  * desrt parties
[08:06] <larsu> haha
[08:06] <larsu> morning desrt
[08:07] <desrt> hello larsu!
[08:07] <desrt> and everyone else at the party :)
[08:08]  * desrt would also like to give a special mention to the coffee machine, for being so lovely
[08:14] <didrocks> good morning desrt
[08:29] <seb128> good morning desktopers
[08:30] <seb128> hey larsu pitti didrocks desrt
[08:30] <pitti> bonjour seb128
[08:34] <zzarr> hello!
[08:34] <didrocks> salut seb128, ça va ?
[08:34] <seb128> didrocks, ouais, et toi ?
[08:34] <seb128> zzarr, hey
[08:35] <zzarr> I get an error trying to connect to WiFi networks from lightdm, "(32) Incufficient privileges"
[08:35] <zzarr> seb128, :-)
[08:36] <zzarr> I installed the system with the help of debootstrap so I suspect I'm missing some settings
[08:36] <seb128> zzarr, try #ubuntu for user questions
[08:36]  * duflu just learned what he should already know
[08:37] <seb128> hey duflu
[08:37] <duflu> seb128: Morning
[08:37] <zzarr> seb128, duflu sent me here ;-)
[08:37] <duflu> Yeah
[08:37] <seb128> zzarr, but that's normal afaik, the greeter has limited privileges to avoid having non auth users to be able to do too much on the system
[08:37] <zzarr> no problem, I'll ask in #ubuntu instead
[08:38] <duflu> Oh, so the system needs to learn about the network first inside a login
[08:38] <seb128> yes
[08:38] <didrocks> seb128: ça va :)
[08:38] <seb128> zzarr, duflu, http://bazaar.launchpad.net/~unity-greeter-team/unity-greeter/trunk/view/head:/debian/unity-greeter.pkla
[08:39] <duflu> Yep, as designed
[08:39] <zzarr> I'll have a look, thanks
[08:42] <zzarr> seb128, is that ini file found on the system anywhere?
[08:42] <seb128> zzarr, dpkg -S <filename>
[08:42] <seb128> usually replies to that question
[08:42] <seb128> unity-greeter: /var/lib/polkit-1/localauthority/10-vendor.d/unity-greeter.pkla
[08:42] <zzarr> seb128, okey, nice to know
[08:43] <zzarr> I'll have a look what it says on my system
[08:47] <zzarr> seb128, it looks the same to me
[08:48] <seb128> zzarr, why would it be different?
[08:48] <zzarr> seb128, I don't know, but I checked in case
[08:56] <zzarr> seb128, is there a command to connect to WiFi from console?
[08:57] <seb128> zzarr, nmcli
[08:57] <zzarr> thanks
[08:57] <seb128> zzarr, http://askubuntu.com/questions/377687/how-do-i-connect-to-a-wifi-network-using-nmcli
[08:58] <zzarr> thanks seb128
[08:58] <seb128> yw!
[09:01] <Laney> hey hey
[09:01] <willcooke> g'mornin'
[09:02] <willcooke> morning Laney
[09:02] <seb128> hey u.k people
[09:02] <seb128> how is your island today?
[09:02] <willcooke> what up seb128
[09:02] <Laney> hey willcooke seb128
[09:02] <willcooke> actually not too bad
[09:02] <Laney> it's sunny
[09:02] <seb128> we have sun here this morning!
[09:02] <Laney> looks good!
[09:02] <seb128> haha
[09:02]  * seb128 ^5 Laney
[09:02] <flocculant> Laney has now broken that and the rain will be back later
[09:03] <Laney> oh noes
[09:04] <zzarr> seb128, the step where it says "To list WiFi networks" don't work
[09:04] <zzarr> it complaints that there is no list option
[09:04] <seb128> I think nmcli changed syntax
[09:05] <zzarr> okey
[09:05] <seb128> zzarr, try nmcli d wifi
[09:05] <Laney> nmcli dev wifi list ifname wlan0
[09:05] <zzarr> seb128, okey, I'll do
[09:06] <seb128> or what Laney says
[09:06] <seb128> dunno the difference
[09:06] <Laney> don't you just love nmcli's interface?!?!?!
[09:06] <zzarr> thanks seb128 that worked
[09:06] <didrocks> good morning Laney, willcooke
[09:06] <Laney> hey didrocks!
[09:07] <willcooke> hey didrocks!  How's your market?
[09:07] <didrocks> willcooke: busy market place! but good, thanks! :)
[09:07] <willcooke> didrocks, I see that a community guy might pick up Fritzing \o/
[09:08] <didrocks> willcooke: it's the one with commit rights :)
[09:08] <willcooke> didrocks, that guy rocks!
[09:08] <willcooke> seb128, X tests:  http://paste.ubuntu.com/15002882/ <-- no failures on Xorg though. :/
[09:08] <didrocks> yeah, he really does :)
[09:08] <seb128> Laney, can you help me with that maybe? is there anything keeping appstream in main? http://people.canonical.com/~ubuntu-archive/component-mismatches.html lists it as "binary to demote", I'm wondering why it's not "source & binary"
[09:12] <willcooke> tjaalton, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813610  <--- fixed!  Thank you!
[09:12] <ubot5`> Debian bug 813610 in xf86-video-omap "Please update to 0.4.4" [Wishlist,Fixed]
[09:13] <Laney> seb128: the source is in universe already
[09:13] <Laney> don't ask me!
[09:13] <seb128> lol, ok
[09:13]  * seb128 demotes the binary
[09:13] <tjaalton> willcooke: yeah, seems it got synced too
[09:13]  * Laney has not the power
[09:13] <seb128> so gcab can build
[09:13] <seb128> can unblock gnome-software in universe
[09:13] <seb128> until we get the MIR resolved
[09:16] <willcooke> tjaalton, can I mark that bug as fixed release?>
[09:16] <willcooke> (the Ubuntu one)
[09:16] <seb128> urg, no, appstream-glib can't be demoted so it's not going to fix it
[09:16] <seb128> need the security team to do that review then
[09:17] <tjaalton> willcooke: I just did
[09:17] <willcooke> tjaalton, \m/
[09:17] <willcooke> thanks
[09:17] <seb128> tjaalton, did the drivers situation get resolved yesterday?
[09:17] <tjaalton> seb128: yes, -amdgpu is in main now
[09:17] <seb128> great
[09:17] <tjaalton> so the images should be fine?
[09:18] <seb128> indeed they are
[09:18] <seb128> well the manifest is at least
[09:18] <tjaalton> cool
[09:18] <seb128> I didn't try to boot one yet
[09:18] <tjaalton> so the xserver testing is going well, and a point-release happened yesterday. I'm thinking of moving them to main repo next monday before FF
[09:21] <seb128> great
[09:24] <seb128> TheMuso, hey, I guess you saw the pulseaudio build failure?
[09:33] <seb128> TheMuso, they renamed pa_strlist_tostring to pa_strlist_to_string and 0600-droid-sync-with-upstream-for-Android-5-support-and-b.patch needs to have those changed
[09:38] <seb128> Sweet5hark, hey
[09:39] <andyrock> morning
[09:39] <Sweet5hark> seb128: moin!
[09:39] <seb128> Sweet5hark, the libreoffice autopkgtests seem grumpy with the update
[09:39] <seb128> /tmp/adt-run.GLsJeZ/build.1te/libreoffice-5.1.0~rc3/solenv/gbuild/Package.mk:81: *** Something depends on package instsetoo_native_setup which does not exist..  Stop.
[09:39] <seb128> Sweet5hark, ^ does it speak to you?
[09:39] <seb128> andyrock, hey!
[09:41] <Sweet5hark> seb128: hmmm, it tells me something in the libreoffice build system is fubared (or rather, the abuse we do with it to run the tests standalone).
[09:42] <Sweet5hark> seb128: FWIW, it does not suggest that libreoffice itself is broken (yet).
[09:42] <seb128> right
[09:43] <seb128> still it makes britney frown at it
[09:43] <Sweet5hark> seb128: for more, I'd need to get a local autopkgtest setup to see what is odd there.
[09:43] <Sweet5hark> seb128: yeah, will look into it.
[09:43] <seb128> well, one way or another we need to unblock it
[09:43] <seb128> thanks!
[09:45]  * Sweet5hark mumbles something about  "tests are for quicheeaters" and real programmers use pascal (http://www.pbm.com/~lindahl/real.programmers.html)
[09:46] <seb128> :-)
[09:49] <desrt> "One can tell immediately by this comment that Nicklaus Wirth is a Quiche Eater."
[09:52] <seb128> shrug
[09:53]  * seb128 shakes fist at firefox, it crashed, used 100% cpu and now my awesome bar is less awesome/lost some history
[09:53] <seb128> I guess something in the profile got corrupted/deleted
[09:53] <seb128> it's annoying!
[09:53] <desrt> seb128: firefox has some very serious issues when the history db gets too big
[09:53] <seb128> :-(
[09:54] <desrt> i periodically sacrifice my history in order to avoid losing more important stuff like saved passwords :p
[09:56] <seb128> that is suboptimal :-/
[10:06] <Laney> oh em gee
[10:06] <Laney> we had a power cut
[10:06] <willcooke> nowai
[10:07] <Laney> I can now hear a symphony of burglar alarms
[10:07] <Laney> all across the land
[10:07] <willcooke> hah!
[10:07] <willcooke> I've never understood the logic in that
[10:08] <willcooke> presumably something like... now the burglars have reconnected the power I shall alert my owners to this probably break in
[10:08] <willcooke> or..  I was actually staring at some code before this rude interruption...
[10:11] <Laney> ...
[10:11]  * Laney looks for that video of Homer playing with the squirrels
[10:12] <willcooke> :)
[10:12] <seb128> need some UPS!
[10:12] <willcooke> Laney, https://frinkiac.com/ is your friend
[10:13] <Laney> this one will do
[10:13] <Laney> https://www.youtube.com/watch?v=zsKOYQ7z9CE
[10:14] <Laney> appstream segfaults... birds... appstream segfaults... cup of tea...
[10:14] <Laney> ok I'm back in the zone
[10:16] <Laney> WTF no I'm not
[10:16]  * Laney had never put pi's external hard drive in fstab
[10:20] <pitti> seb128: ftr, chromium-browser has failed on armhf for a long time, little sense in retrying
[10:21] <seb128> pitti, can we skip it?
[10:21] <pitti> seb128: we have a force-badtest for it
[10:21] <pitti> pitti:force-badtest chromium-browser/48.0.2564.82-0ubuntu1.1222
[10:21] <seb128> thanks
[10:21] <pitti> seb128: see excuses.html "Should wait for chromium-browser 48.0.2564.82-0ubuntu1.1222 test, but forced by pitti "
[10:22] <seb128> right, I overlooked that one
[10:22] <seb128> do you get notified of every retry? ;-)
[10:22] <pitti> one of these days I need to fix britney to show the overrides right after/on the affected result
[10:22] <pitti> seb128: no, I just look at http://autopkgtest.ubuntu.com/running.shtml#queue-xenial-armhf to see how far we are
[10:23] <seb128> I see
[10:23] <seb128> sorry for adding useless backlog
[10:23] <pitti> seb128: perl  and Qt in the silo combined have kept the armhf runners busy since Monday evening..
[10:23] <pitti> no worries
[10:23] <pitti> seb128: the armhf machines need quite a lot of handholding, so I'm looking at running regularly
[11:05] <doko> seb128, Laney: all sphinx* related packages updated, and fixed simon.
[11:05] <doko> except for unity-voice
[11:05] <doko> now, there is a problem: the vcs reads for 2014-06: Remove old energy-based VAD
[11:06] <doko> and unity-voice apparently relies on that :-/
[11:12] <Laney> doko: perhaps this is a thing that is not maintained
[11:12] <Laney> or needed
[11:12] <doko> how to find out?
[11:12] <Laney> it seems to not be on touch images
[11:12] <Laney> maybe ask sil2100
[11:12] <doko> sil2100, ^^^ you touched this last
[11:13] <sil2100> Hey, what's up?
[11:13] <doko> read backlog
[11:15] <sil2100> hm, ok, I suspect this package is no longer used, but let me double-confirm that
[11:16] <sil2100> s/used/maintained
[11:19] <doko> reverse-depends doesn't show anything for it
[11:22] <sil2100> doko: yeah, confirmed it's not used or really maintained
[11:22] <Laney> FLUSH IT
[11:23] <doko> sil2100, please could you address this at some meeting that those packages are removed? these issues cost people's time :-(
[11:23] <doko> sil2100, please file a bug report and assign it to ubuntu-archive
[11:23] <sil2100> doko: on it o/ I actually wonder why we didn't drop it when we dropped it from our touch images
[11:24] <sil2100> Thought they had some other uses for it
[12:06] <doko> sil2100, bug report?
[12:22] <sil2100> doko: https://bugs.launchpad.net/ubuntu/+source/unity-voice/+bug/1544025
[12:22] <ubot5`> Launchpad bug 1544025 in unity-voice (Ubuntu) "Please remove unity-voice from the archive" [Undecided,New]
[12:25] <doko> sil2100, removed
[12:25] <sil2100> doko: thanks o/
[12:34] <seb128> doko, Laney, check with ted or pete-woods maybe? I think unity-voice was going to be used for the hud (I think it's still on futur roadmaps, just not a priority atm)
[12:35] <Laney> yeah, when that time comes it can be fixed & reuploaded
[12:35] <Laney> already talked to pete on some other channel
[12:36] <seb128> k
[12:36] <seb128> I'm not going to complain about being agressive for removals
[12:37] <seb128> usually it's the other way around, I would delete half of the universe craps but people keep saying that those might have some users and we should better fix things than remove them :p
[12:43] <doko> seb128, Sweet5hark: are you going to work on the hsqldb dep-wait?
[12:44]  * doko ducks
[12:44] <seb128> doko, https://launchpad.net/ubuntu/+source/hsqldb/2.3.3+dfsg2-1 no dep-wait?
[12:44] <doko> https://launchpad.net/ubuntu/+source/hsqldb1.8.0
[12:45] <doko> yes, because it's still in universe
[12:45] <seb128> I can fix that
[12:45] <doko> sure, and please all resulting component mismatches
[12:45] <seb128> thanks for pointing it out
[12:46] <doko> I assume these are the same for the two versions
[12:52]  * Sweet5hark sticks pins in his libreoffice-base voodoo doll.
[12:53] <Sweet5hark> doko: thanks for the notification.
[13:05] <willcooke> grrrrr. the big orange thing in the sky is too bright and now I'm having to close the blinds
[13:05] <ogra_> send it over here, you can have our rain
[13:05]  * willcooke goes to look for an envelope
[13:06] <pitti> ogra_: dry and half-sunny here :)
[13:06] <ogra_> lucky you in the south
[14:43] <Sweet5hark> *grmbl*
[14:43] <Sweet5hark> toggling proposed in software updater toggles binaries, but not deb-src ...
[15:36] <seb128> Sweet5hark, did that use to work? unsure what's the logic but I would expect it to enable deb-src if you have those enabled for the main pocket
[16:09] <Sweet5hark> seb128: dunno, if it used to work. I just enabled proposed via GUI, then installed the libreoffice bins and was confused for a sec when I got libreoffice 5.0.x with apt-get source
[16:28] <dobey> Sweet5hark: pull-lp-source is your friend, btw
[16:30] <Sweet5hark> seb128: hacked the autopkgtest into submission, I think. needed some 3-line change in the bowels of the libreoffice build system
[16:32] <seb128> Sweet5hark, cool
[18:01] <davmor2> whose the best person to talk to about secureboot and it's behaviour in 16.04, more specifically how to re-enable it after the installer disabled it?
[18:02] <willcooke> davmor2, humm, I would guess foundations
[18:03] <davmor2> willcooke: thanks
[18:03] <willcooke> alrighty, g'night all
[18:15] <Sweet5hark> seb128: libreoffice_5.1.0~rc3-0ubuntu2 currently uploading to http://people.canonical.com/~bjoern/xenial/5.1.0/ and should fix the autopkgtests. no upload of libreoffice-l10n needed though. should be finished in a few minutes -- suggesting upload tomorrow though (as per "no late evening or friday uploads if possible" guideline for libreoffice)
[18:16]  * Sweet5hark is of for the day.
[18:16] <Sweet5hark> s/of/off/
[21:00] <TheMuso> seb128: Yeah, I'm on it.
[21:00] <TheMuso> Gah I always do that...
[22:00] <robert_ancell> attente, I pushed some coding style changes to the Ubuntu login dialog code
[22:22] <flocculant> robert_ancell: I've been playing with the gnome-software ppa in xubuntu - sort of, just got back to looking again - completely updated it, currently it want's (and obviously does) remove system-config-printer for me - should I report that? is that something you'd want to see reported
[22:23] <robert_ancell> flocculant, yeah, please report that
[22:23] <flocculant> ack
[22:26] <flocculant> robert_ancell: given it's a ppa and it won't let me ubuntu-bug - anything you want me to attach to the manual report?
[22:26] <robert_ancell> flocculant, just note in the report it's from the PPA
[22:27] <flocculant> ok
[22:30] <flocculant> bug 1544325
[22:30] <ubot5`> bug 1544325 in gnome-software (Ubuntu) "Installing gnome-software removes system-config-printer" [Undecided,New] https://launchpad.net/bugs/1544325
[22:30] <flocculant> I know someone else in our team was looking I'll try and get them to confirm that
[22:33] <flocculant> I know timezone issue here - so if I can do anything - leave a ping in here perhaps and I'll see it when I get back
[22:35] <robert_ancell> flocculant, thanks
[22:50] <flocculant> robert_ancell: might actually be an issue with an old vm install and the ppa and updating/grading - someone else looked and can't confirm it - redoing mine
[22:51] <attente> robert_ancell: can we squash those commits together to make a clean patch?
[22:51] <robert_ancell> attente, I have a local branch with everything squashed together
[22:52] <robert_ancell> attente, I've never worked out the appropriate way to do this with git - do we start a new branch with a clean commit?
[22:53] <attente> robert_ancell: i've only ever done it on private/in-progress branches too
[22:53] <attente> i guess it gets hard if we start to force-push to a common remote
[22:54] <attente> maybe it's best if you maintain the clean branch after all
[22:54] <robert_ancell> attente, yeah, the force push just doesn't seem to scale beyond one developer.
[22:55] <robert_ancell> attente, So I'm putting the patches from my rebased branch onto bugzilla - you can always pick up one of those and modify it if you need it
[22:55] <robert_ancell> attente, and of course it's not impossible to generate the rebased branch yourself, though there are likely many conflicts in the process
[22:57] <attente> yeah, you're right. probably best if you maintain the clean patchset
[22:58] <attente> but if you push it to the remote, i could work off of that instead
[22:59] <attente> because it must be confusing keeping track of changes between the wip branch and the bugzilla patches
[23:00] <robert_ancell> attente, it's not hard - I just do a git diff to see what needs pulling in and then git cherry-pick them followed by a rebase
[23:01] <robert_ancell> attente, the issue pushing to the remote is then we have to force push and it gets messy/dangerous
[23:01] <attente> robert_ancell: i think it's ok as long as you're the only one doing it. but yeah, if you're ok with cherry picking changes from the other branch, that's sounds ok too
[23:21] <flocculant> robert_ancell: I was trying to unconfirm that bug - now I've got add-apt-repository crashing on me - so I'll leave it for tomorrow - but it appears that a clean install today installs -gnome
[23:21] <flocculant> I'll look as soon as I can on that
[23:26] <flocculant> bug 1544346 just in case that's important
[23:26] <ubot5`> bug 1544346 in software-properties (Ubuntu) "add-apt-repository crashed with ssl.SSLError in create_default_context(): unknown error (_ssl.c:3046)" [Medium,New] https://launchpad.net/bugs/1544346