[16:00]  * slangasek waves
[16:02] <slangasek> #startmeeting
[16:02] <meetingology> Meeting started Tue Sep 13 16:02:02 2016 UTC.  The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:02] <meetingology> Available commands: action commands idea info link nick
[16:02] <mdeslaur> \o
[16:02] <slangasek> welcome to the 189th fortnightly meeting of the Ubuntu Technical Board
[16:02]  * slangasek waits while people count to see if that's a real number
[16:03] <slangasek> [TOPIC] Apologies
[16:03] <mdeslaur> hehe
[16:03] <slangasek> none sent for this week
[16:03] <slangasek> [TOPIC] Action review
[16:03] <slangasek> a number of actions for infinity, who is not present
[16:03]  * stgraber waves
[16:03] <slangasek> so we'll carry those over
[16:04] <slangasek> for the record, they are:
[16:04] <slangasek> ACTION: infinity to follow up with maas SRU exception
[16:04] <slangasek> ACTION: infinity to document the new Docker SRU process
[16:04] <slangasek> ACTION: infinity to play with seed/maint-check changes on dogfood to build a new xenial release pocket for support length auditing
[16:04] <slangasek> one action for mdeslaur
[16:04] <slangasek> ACTION: mdeslaur to look into flavour CVE tracking
[16:04] <mdeslaur> please defer *sigh*
[16:04] <slangasek> carried over
[16:05] <slangasek> no new agenda items on https://wiki.ubuntu.com/TechnicalBoardAgenda
[16:05] <slangasek> [TOPIC] Mailing list archive
[16:05] <slangasek> only activity is that ci-train-bot is now a member of launchpad-buildd-admins, which probably doesn't require a response ;)
[16:06] <slangasek> (fwiw I have the context for why that was done, if anyone does feel that needs reviewed - I moderated that particular message through to the list in the interest of transparency)
[16:07] <slangasek> [TOPIC] Community bugs
[16:07] <slangasek> [LINK] https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard
[16:07] <slangasek> no bugs currently open
[16:07] <slangasek> [TOPIC] Select a chair for the next meeting
[16:07] <slangasek> next up should be stgraber, with infinity as backup, yes?
[16:08]  * mdeslaur looks at stgraber
[16:09] <slangasek> [AGREED] next chair is stgraber, with infinity as backup
[16:09] <slangasek> settled ;)
[16:09] <slangasek> [TOPIC] AOB
[16:10] <slangasek> anything else for this week that didn't make the agenda?
[16:10] <rbasak> o/
[16:10] <rbasak> infinity has a few DMB->TB tasks but hasn't been able to get to them for a while. I see the same applies to his TB actions. Any chance somebody else here could take them please? Details at: https://lists.ubuntu.com/archives/devel-permissions/2016-August/000951.html
[16:11] <slangasek> hmm, I'm not sure the mechanics of this
[16:11] <mdeslaur> yeah, I don't either
[16:12] <rbasak> I think edit-acl from ubuntu-archive-tools can do it all, though I'm not sure (I don't have the right permissions)
[16:12] <rbasak> stgraber is another TB person who would know, though I don't see him here.
[16:13] <slangasek> rbasak: ok, I can follow up on this, and if edit-acl doesn't get me there I'll come back to you
[16:13] <rbasak> Great. Thank you!
[16:13] <slangasek> [ACTION] slangasek to address outstanding DMB tasks from https://lists.ubuntu.com/archives/devel-permissions/2016-August/000951.html
[16:13] <meetingology> ACTION: slangasek to address outstanding DMB tasks from https://lists.ubuntu.com/archives/devel-permissions/2016-August/000951.html
[16:13] <slangasek> anything else?
[16:15] <mdeslaur> nothing from me
[16:15] <slangasek> #endmeeting
[16:15] <meetingology> Meeting ended Tue Sep 13 16:15:18 2016 UTC.
[16:15] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting-2/2016/ubuntu-meeting-2.2016-09-13-16.02.moin.txt
[16:15] <slangasek> mdeslaur, stgraber, rbasak: thanks
[16:16] <mdeslaur> thanks slangasek


[06:58] <dholbach> hiya kirkland :)
[06:58] <kirkland> dholbach: howdy
[06:58]  * kirkland wonders how many people are up at this crazy hour :-)
[06:59] <Rail> +1 :)
[06:59]  * FuturePilot is
[06:59] <kirkland> very good :-)
[06:59] <RoAkSoAx> +1
[06:59] <kirkland> i'm just getting my demo env setup
[06:59]  * dholbach just told a few folks
[06:59] <Jordan_U> I'm not
[07:00] <ienorand> I've sleep during the day...
[07:00] <kirkland> howdy all!
[07:01] <kirkland> alrighty ...
[07:01] <kirkland> my name is Dustin Kirkland
[07:02] <kirkland> I'm a MOTU and Core Developer in Ubuntu, and I work for Canonical on the Ubuntu Server
[07:02] <kirkland> i'm here to talk about PPA's
[07:02] <kirkland> what they are
[07:02] <kirkland> how to use them
[07:03] <kirkland> and how wonderfully useful they are!
[07:03] <kirkland> so a PPA is a Personal Package Archive
[07:03] <kirkland> and it's a tremendously interesting concept
[07:04] <kirkland> i have been in and around Linux development for almost 10 years now, and I never heard of this "PPA" concept until I began working on ubuntu and with launchpad
[07:04] <kirkland> so let's start by explaining what an archive is
[07:05] <kirkland> i assume most people here have used something like apt-get, aptitude, smart, update-manager, synaptic
[07:05] <kirkland> these are client-side utilities that talk to a server providing an archive
[07:06] <kirkland> now the archive itself
[07:06] <kirkland> is really just an http server
[07:06] <kirkland> with files and directories that can be browsed
[07:06] <kirkland> i suppose it could probably be an ftp server too
[07:07] <kirkland> in any case, you're probably familiar with http://archive.ubuntu.com
[07:07] <kirkland> if not, browse around it some time, by hand, by pointing a web browser at that address
[07:07] <kirkland> you should see a fairly regular hierarchy
[07:07] <kirkland> most of the interesting stuff happens in the pool/ directory
[07:08] <kirkland> that's where binary and source packages land
[07:09] <kirkland> now, archive.ubuntu.com is the "official" archive
[07:09] <kirkland> which means that these are the packages, as "officially" prepared by the developers of the Ubuntu project
[07:10] <kirkland> ie, MOTU for Universe/Multiverse, and Core Dev for Main
[07:10] <kirkland> users should be able to maintain some fair amount of confidence in the quality and security of packages available in the general ubuntu archive
[07:10] <kirkland> .....
[07:10] <kirkland> now, that's all fine and dandy
[07:11] <kirkland> but where does the really fun crack live?
[07:11] <kirkland> in PPA's of course :-)
[07:11] <kirkland> so a PPA is really just a mini little archive
[07:11] <kirkland> the structure is basically identical to the archive.ubuntu.com
[07:12] <kirkland> but the packages provided there are not part of the official distribution
[07:12] <kirkland> there are several reasons for this
[07:12] <kirkland> and different people use PPA's for different ones
[07:12] <kirkland> usually, it's intended for testing
[07:13] <kirkland> providing a binary, built package to some person or people for them to test
[07:13] <kirkland> let's take a look at a couple of examples ...
[07:14] <kirkland> as part of my responsibilities on the Ubuntu Server Team, I'm the package maintainer of KVM
[07:14] <kirkland> it's a virtualization hypervisor, similar, perhaps, to vmware or virtualbox
[07:14] <kirkland> 8.04 (hardy) shipped with kvm-62, 8.10 (intrepid) shipped with kvm-72
[07:14] <kirkland> whereas 9.04 (jaunty) shipped with kvm-84
[07:15] <kirkland> now, in the last ~1 year, this particular package has come *a long* way
[07:15] <kirkland> and there are people using hardy and intrepid want to use kvm-84, for various bugs that have been fixed, or new features added
[07:16] <kirkland> of course, we have processes for rolling out small fixes via updates to Hardy/Intrepid etc.
[07:16] <kirkland> and we have a backports mechanism for backporting packages too
[07:16] <kirkland> but this is a bit of a special case, and I wanted some really thorough testing
[07:16] <kirkland> i could ask people to just "go build it yourself"
[07:16] <kirkland> but really, how many people would do that? :-)
[07:17] <kirkland> and, furthermore, how would I be sure that they built the right thing, or in the right way?
[07:17] <kirkland> so i've been using a PPA to provide packages to this group of people
[07:17] <kirkland> https://edge.launchpad.net/~ubuntu-virt/+archive/ppa
[07:17] <kirkland> specifically, that PPA ^
[07:18] <kirkland> if you go to that webpage, you should see 3 version of kvm published in that ppa, one each for Hardy, Intrepid, and Jaunty
[07:18] <kirkland> you can also see that I uploaded the latest version merely 7 hours ago :-)
[07:18] <kirkland> that brings us to another nice benefit of PPA's ...
[07:19] <kirkland> you can upload to them basically whenever you want!
[07:19] <kirkland> for the official archives, we have a number of deadlines and freezes that must be adhered to
[07:19] <kirkland> currently, Karmic is open for development, and developers can upload to it
[07:19] <kirkland> but Hardy/Intrepid/Jaunty are not open for development
[07:20] <kirkland> and thus, it requires special permission to upload to those official archives
[07:20] <kirkland> but PPA's can be uploaded to at any time, really
[07:20] <kirkland> I should also note that this particular PPA is a "team" PPA
[07:20] <kirkland> this is a relatively recent feature to Launchpad
[07:21] <kirkland> so I have my own PPA ...
[07:21] <kirkland> https://edge.launchpad.net/~kirkland/+archive/ppa
[07:21] <kirkland> but i also have access to a number of team ppa's
[07:21] <kirkland> so these KVM packages are sort of maintained by the ~ubuntu-virt team
[07:22] <kirkland> in my PPA, you'll see a different set of packages
[07:22] <kirkland> for one thing, you might notice XMMS :-)
[07:22] <kirkland> i still prefer xmms over all of the other mp3 players out there, but it was pulled from the official Ubuntu archives (for some very good reasons)
[07:23] <kirkland> no matter ... I just keep a copy in my PPA, that I can use on any Ubuntu machine I have :-)
[07:23] <kirkland> so using a ppa
[07:23] <kirkland> i should probably explain how to do this ...
[07:24] <kirkland> to do so, i have created a shared screen instance
[07:24] <kirkland> you can join me at:
[07:25] <kirkland> ssh -C<EMAIL_ADDRESS>[07:25] <kirkland> the password is "guest"
[07:26] <kirkland> okay
[07:26] <kirkland> please try to watch IRC, where I'll explain what I'm doing
[07:26] <kirkland> and the terminal, where I'm going to do it
[07:26] <kirkland> first, I'm going to add my PPA to my list of archives
[07:26] <kirkland> sudo vi /etc/apt/sources.list
[07:27] <kirkland> now, see the webpage https://edge.launchpad.net/~kirkland/+archive/ppa
[07:27] <kirkland> deb http://ppa.launchpad.net/kirkland/ppa/ubuntu jaunty main
[07:27] <kirkland> deb-src http://ppa.launchpad.net/kirkland/ppa/ubuntu jaunty mai
[07:27] <kirkland> i'm going to add that to my sources.list
[07:27] <kirkland> i'm going to save that file
[07:27] <kirkland> and sudo apt-get update
[07:28] <kirkland> as you can see, i get an error about a missing gpg key
[07:28] <kirkland> we can solve that by retrieving the proper key
[07:28] <kirkland> This repository is signed with 1024R/34BEEE14 OpenPGP key. Follow these instructions for installing packages from this PPA.
[07:28] <kirkland> ^ the webpage tells us this
[07:28] <kirkland> http://keyserver.ubuntu.com:11371/pks/lookup?search=0x657A928364338B14A900B68D7781BA0134BEEE14&op=index
[07:29] <kirkland> https://help.launchpad.net/Packaging/PPA#Adding a PPA to your Ubuntu repositories
[07:30] <kirkland> sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 657a928364338b14a900b68d7781ba0134beee14
[07:30] <kirkland> now, let's rerun the update
[07:30] <kirkland> \o/
[07:30] <kirkland> no errors
[07:31] <kirkland> so i want to install the last screen-profiles package from my PPA
[07:31] <kirkland> note that version on this Hardy server is 1.44
[07:31] <kirkland> https://edge.launchpad.net/~kirkland/+archive/ppa
[07:31] <kirkland> and note that 1.54 is available here
[07:32] <kirkland> now, notice that version 1.54-0ubuntu1~ppa3 is installed
[07:33] <kirkland> thanks micahg
[07:33] <kirkland> so apt-cache policy screen-profiles will show the different versions available
[07:33] <kirkland> and specifically where they came from
[07:33] <kirkland> now, let's grab a source package
[07:35] <kirkland> whoops, bad example
[07:35] <kirkland> um, let's grab a different package (something that's not already in my ppa)
[07:36] <kirkland> gotta chase down some dependencies
[07:36] <rolando-ve> Try a usplash-theme
[07:36] <santiago-ve> fish
[07:37] <kirkland> so i'm going to grab the source of a package called bip
[07:37] <kirkland> it's an irc proxy
[07:37] <kirkland> apt-get source bip
[07:37] <kirkland> let's imagine that i've made some edition to the source code
[07:38] <kirkland> now, i need to increment the version, and add a changelog message
[07:38] <kirkland> dch -i
[07:38] <kirkland> (more dependencies)
[07:40] <kirkland> okay, now here's an important point
[07:40] <kirkland> when preparing a package for upload to a ppa
[07:40] <kirkland> we need to version it in such a way that it's a "successor" to previous versions
[07:40] <kirkland> but we want to make sure that future, official versions supercede this package
[07:41] <kirkland> in this case, jaunty's bip is version 0.7.4-2ubuntu1
[07:41] <kirkland> by doing a dch -i, i have "incremented" the ubuntu1 to an ubuntu2
[07:41] <kirkland> that will ensure that this is considered an "upgrade" from the previous ubuntu1 version
[07:42] <kirkland> however, we want to make sure that a future, *real* ubuntu2 version will supercede this one
[07:42] <kirkland> and thus, there's a special character that allows us to do this ...
[07:42] <kirkland> the ~ tilda
[07:42] <kirkland> bip (0.7.4-2ubuntu2~ppa1) jaunty; urgency=low
[07:42] <kirkland> package is bip
[07:42] <kirkland> the version is 0.7.4-2ubuntu2~ppa1
[07:43] <kirkland> if i want to make multiple uploads of this package over and over to my ppa, i can iterate ~ppa2, ~ppa3, etc.
[07:43] <kirkland> now, i add a change log entry
[07:43] <kirkland> specificying the file i changed
[07:43] <kirkland> and why
[07:43] <kirkland> and i reference the bug number fixed
[07:44] <kirkland> next I should build the package locally
[07:44] <kirkland> to make sure that I haven't broken the build somehow
[07:44] <kirkland> before wasting the time of the build machines in soyuz
[07:44] <kirkland> (note that you should really use pbuild or sbuild, eventually, but that's an hour long class in itself)
[07:44] <kirkland> so first, i need to get the build-dependencies
[07:45] <kirkland> sudo apt-get build-dep bip
[07:45] <kirkland> and then I'll do the build
[07:45] <kirkland> using "debuild"
[07:46]  * kirkland now wishes he had shelled out $0.80/hour for the quad-core ec2 instance :-)
[07:47] <kirkland> so dch is the changelog editor
[07:47] <kirkland> you can use dch -e to edit the existing entry
[07:47] <kirkland> (ie, don't increment)
[07:47] <kirkland> the -i does the increment
[07:47] <kirkland> i also should have noted that you really want to double check the release
[07:47] <kirkland> in this case, it's "jaunty"
[07:48] <kirkland> but you might have, perhaps, wanted to specify that this package is for hardy or karmic, for instance
[07:48] <kirkland> okay, the build is done
[07:48] <kirkland> you see there's an error
[07:48] <kirkland> it's missing the gpg to sign this package
[07:48] <kirkland> of course, I have not copied my gpg key to ec2 :-)
[07:48] <kirkland> so I'm not going to be able to sign this package
[07:49] <kirkland> (nor actually upload it)
[07:49] <kirkland> but let's get to that point ....
[07:49] <kirkland> looking in the director above this one, we can now see that we have binary *.deb files
[07:49] <kirkland> so we have build the binary package locally
[07:49] <kirkland> now, let's build the source package
[07:49] <kirkland> debuild -S
[07:50] <kirkland> again, i'm going to get the same GPG errors
[07:50] <kirkland> under normal circumstances, you will be prompted for your GPG password
[07:50] <kirkland> and GPG will be used to "sign" your package
[07:50] <kirkland> this is how Launchpad (and users of your PPA) can have confidence that you're the person who created that pacakge
[07:51] <kirkland> okay, so the *source.changes file is the file that contains the magic needed to upload to a ppa
[07:51] <kirkland> we should see some important information in this file
[07:52] <kirkland> most importantly, checksums of the files, and a manifest of the files that need to be uploaded
[07:52] <kirkland> once you have a changes file, you are clear to upload
[07:52] <kirkland> now, uploading to a PPA requires one configuration change
[07:52] <kirkland> you need a file in your home directory called ~/.dput.cf
[07:53] <kirkland> my ppa entry looks like this:
[07:53] <kirkland> [kirkland-ppa]
[07:53] <kirkland> fqdn = ppa.launchpad.net
[07:53] <kirkland> method = ftp
[07:53] <kirkland> incoming = ~kirkland/ubuntu/
[07:53] <kirkland> login = anonymous
[07:53] <kirkland> allow_unsigned_uploads = 0
[07:53] <kirkland> now that i have that file, i could attempt the upload
[07:54] <kirkland> (note that this is going to fail, because of the lack of a gpg signature)
[07:54] <kirkland> but i want to demonstrate the command
[07:54] <kirkland>  dput kirkland-ppa *sources.changes
[07:54] <kirkland>  dput kirkland-ppa *source.changes
[07:55] <kirkland> now under normal circumstances, you'd see a few messages scroll by, and see your upload take place
[07:55] <kirkland> about a minute later, you should get an email from Launchpad either accepting, or rejecting your upload (in case something was malformed)
[07:55] <kirkland> if it's accepted, your package will go into the build queue
[07:55] <kirkland> and eventually, Soyuz will build your code, and publish it to your PPA
[07:56] <kirkland> alrighty ... let's take a few questions ...
[07:56] <djails> how do you specify what ubuntu version your package is for ?
[07:56] <rolando-ve> Kirk, If I use intrepid, and need to do that for Hardy, I must to do in a chroot + debootstrap?
[07:56] <blacknred0> so if i am building my first package should i start importing my keys first from launchpad?
[07:56] <kirkland> it's pretty quiet, so i suppose you can just paste your question here
[07:57] <kirkland> djails: in the first line of the changelog, edited with dch
[07:57] <kirkland> djails: bip (0.7.4-2ubuntu2~ppa1) jaunty; urgency=low
[07:57] <kirkland> djails: note the "jaunty" in that line
[07:58] <kirkland> rolando-ve: hmm, to do your test binary build properly -- yes
[07:58] <kirkland> rolando-ve: however, you should be able to build your source package safely
[07:58] <kirkland> rolando-ve: so in that case you could grab the source, edit your changelog (and whatever files) and debuild -S
[07:58] <kirkland> rolando-ve: again, it's always proper form to test your build locally first
[07:58] <iKOSHrf> can i make it a version that never gets replaced by the official branch? or just start my own ?
[07:59] <kirkland> rolando-ve: it's quite rude to cause build failures on launchpad (costing other people time) if your build won't even work locally
[07:59] <micahg> ls
[07:59] <micahg> oops
[07:59] <kirkland> blacknred0: if you're building your first package, you should make sure that launchpad has your GPG and SSH public keys
[08:00] <kirkland> blacknred0: also, i think you have to sign the Ubuntero agreement to use PPAs
[08:00] <kirkland> iKOSHrf: i don't think i understand that question?
[08:00] <blacknred0> kirkland, yeap, i have all of them.  i am getting problems in the building :S
[08:00] <Ludo> kirkland, i see the package you build was for the i386 architectures.  How will you change the package to be build for the amd64 architectures?
[08:00] <kirkland> iKOSHrf: if you don't ever want it to get replaced, change the version to 99999.99999.9999 :-)
[08:00] <iKOSHrf> kirkland, if i just want to "fork" the version to make it my own "version" for some odd reason
[08:01] <iKOSHrf> hehehe ok.
[08:01] <kirkland> blacknred0: make sure you have all of the build dependencies, sudo apt-get build-dep $PKG
[08:01] <blacknred0> kirkland, i mean is just a single script but it the make doesn't want to make the file properly
[08:01] <blacknred0> kirkland, ok, thnx for the info.
[08:02] <kirkland> iKOSHrf: well i think that's exactly what I did in my bip example -- i have forked the ubuntu2 version;  but you're saying that you don't want it to ever be replaced
[08:02] <kirkland> iKOSHrf: in that case, you could add a really big number at the beginning of the package (which I don't really recommend), or "pin" the package
[08:02] <kirkland> iKOSHrf: see the manpages for apt-get for pinning instructions
[08:02] <iKOSHrf> ok, thanks.
[08:02] <djails> kirkland: thanks. Now if you want to create a package for different versions of ubuntu, how do you go about that ?
[08:03] <kirkland> Ludo: well, ideally you'd test your build on both architectures;  i usually do that with KVM virtual machines;  however, I understand that this isn't always possible
[08:03] <kirkland> Ludo: launchpad will build PPA packages for several archectures for you
[08:04] <kirkland> Ludo: basically, once I've confirmed that it builds on one arch, and if I have reasonable certainty that it'll build elsewhere, I go ahead and push it to launchpad
[08:04] <Ludo> kirkland,  thanks.
[08:04] <kirkland> djails: what do you mean?  you just change "jaunty" to say "karmic" or "hardy" in that first line
[08:05] <djails> kirkland: so do you maintain a debian/ dir per version ? I have this upstream source tree and I want to createpackages for serveral ubuntus
[08:05] <micahg> do you need ot backport -dev packages?
[08:05] <kirkland> djails: ah ...
[08:06] <kirkland> djails: gotcha
[08:06] <Ludo> kirkland, how would one add a extra dependency to a package? For example I need a extra library or newer library for my modification to work?
[08:06] <kirkland> djails: so I usually just dch -e, add a ~ppa1 ... hardy, then debuild -S
[08:06] <kirkland> djails: then, in that same dir
[08:07] <kirkland> djails: dch -e again, change to ~ppa2 ... intrepid, debuild -S again
[08:07] <kirkland> djails: dch -e again, change to ~ppa3 ... jaunty; debuild -S
[08:07] <kirkland> djails: then cd ..
[08:07] <kirkland> djails: and dput kirkland-ppa *source.changes
[08:07] <kirkland> djails: HOWEVER ....
[08:07] <kirkland> djails: this won't necessarily work for just any package
[08:08] <kirkland> djails: it'll work fine for simple packages with minimal build dependencies
[08:08] <kirkland> djails: but if a package depends on a newer version of some library, it's quite a bit more difficult :-)
[08:08] <djails> kirkland: ok got it ! i ll try that
[08:08] <kirkland> Ludo: that information is in debian/control
[08:08] <kirkland> Ludo: so over in our shared screen session ...
[08:09] <kirkland> Build-Depends: cdbs (>= 0.4.49), debhelper (>= <IP_ADDRESS>), bison, flex, libssl-dev, quilt
[08:09] <kirkland> Ludo: those are the build-deps for bip
[08:09] <kirkland> okay guys ... i'm about to call it a night here
[08:09] <kirkland> as it's past 2am :-)
[08:09] <micahg> 1 last Q?
[08:09] <kirkland> one thing that i'll mention
[08:09] <kirkland> micahg: shoot!
[08:09] <micahg> do you have to backport -dev packages?
[08:10] <micahg> I want to build FF3.5b4 for Jaunty
[08:10] <micahg> or are -dev only used when compiling?
[08:10] <ienorand> ps
[08:10] <ienorand> sorry
[08:11] <kirkland> micahg: i'm not sure i understand your question
[08:11] <kirkland> micahg: but your build dependencies should be available
[08:11] <kirkland> micahg: so if you want to build something in your PPA, you need to ensure that the build deps are available
[08:11] <kirkland> micahg: that brings up an important point ....
[08:12] <kirkland> micahg: in your PPA configuration page, you can specify a few different restrictions, or options for your dependencies
[08:12] <kirkland> on your own PPA page, you should see a link for "Edit dependencies"
[08:13] <kirkland>  Basic (only released packages).
[08:13] <kirkland>  Security (basic dependencies and important security updates).
[08:13] <kirkland>  Default (security dependencies and recommended updates).
[08:13] <kirkland>  Proposed (default dependencies and proposed updates).
[08:13] <kirkland>  Backports (default dependencies and unsupported updates).
[08:13] <kirkland> micahg: that might help
[08:13] <micahg> ok
[08:13] <micahg> thanks
[08:13] <rolando-ve> Thanks
[08:14] <djails> kirkland: thanks !
[08:14] <FuturePilot> kirkland: thanks for the tutorial :)
[08:14] <kirkland> you guys are most welcome
[08:14] <Ludo> kirkland, thanks.
[08:14] <rolando-ve> Nice job kirkland
[08:14] <kirkland> so one last thing in closing
[08:14] <kirkland> some people have asked how to setup a shared screen session like i used
[08:14] <kirkland> did you guys find that useful?
[08:14] <micahg> yes
[08:14] <djails> definitely
[08:14] <FuturePilot> very
[08:15] <rolando-ve> Yeap
[08:15] <Ludo> ^^
[08:15] <kirkland> okay, so i have a blog post about this
[08:15] <kirkland> http://blog.dustinkirkland.com/2009/04/teaching-class-with-gnu-screen.html
[08:15] <kirkland> that explains in detail what needs to be done
[08:15] <rolando-ve> Thanks again, :D
[08:15] <ienorand> Thankyou for the session :)
[08:15] <kirkland> more simply, if you have an EC2 account, you can use a script I wrote, called "screenbin"
[08:16] <kirkland> i just uploaded a new version to my PPA, so look for it there shortly :-)
[08:16] <kirkland> that's all from me
[08:16] <kirkland> good night :-)
[08:16] <kirkland> or morning
[08:16] <micahg> good night
[08:17] <rolando-ve> kirkland: If you let me, I would like to translate it to Spanish
[08:17] <kirkland> rolando-ve: please, go for it :-)
[08:17] <rolando-ve> and post it in my blog, (as yours)
[08:17] <rolando-ve> Thanks!
[08:17] <rolando-ve> see all!
[08:35] <neoXsys> Where can i find the log of last session by kirkland?
[08:37] <neoXsys> http://irclogs.ubuntu.com/2009/05/07/%23ubuntu-classroom.html
[09:40] <Walter_Eco> Is the a session about Personal Package Archives (PPAs) still on or did I miss it?
[09:45] <maxb> Walter_Eco: It was a few hours ago: http://irclogs.ubuntu.com/2009/05/07/%23ubuntu-classroom.html
[09:56] <Walter_Eco> thanks
[14:51] <blue> Shouldn't the motd be updated to show that the PPA class has already taken place?
[14:52] <blue> and the wiki.ubuntu.com/Classroom specifies two classes as upcoming even though they have already taken place
[14:53] <blue> not to mention today's class is not even listed on the wiki
[16:53] <TurtlePie> ikes
[17:58] <tamizh-geek> date -u
[17:59] <tamizh-geek> not upcomin. its finished!
[18:01] <pleia2> looks like it might have been canceled actually
[18:01] <jarlen> which?
[18:02] <pleia2> the class in the topic
[18:02] <pleia2> it's not up on the packaging team's wiki anymore
[18:02] <jarlen> hm, somethings bugged at my place
[18:03] <jarlen> why is UTC 2 hours and 17 minutes behind my time?
[18:03] <jarlen> it can't be like 2 1/4 timezone :P
[18:09] <rfkrocktk> hello!
[18:12] <pleia2> hm
[18:12] <pleia2> no, you guys confused me :) the session happened!
[18:14] <rfkrocktk> when will the session on ubuntu packaging start? is that in an hour?
[18:15] <pleia2> rfkrocktk: there was a session this morning
[18:15] <rfkrocktk> oh, did I miss it?
[18:16] <pleia2> https://wiki.ubuntu.com/Packaging/Training/Logs/2009-05-07
[18:16] <pleia2> on PPAs? yes, looks like
[18:16] <rfkrocktk> right: 6:00 UTC AM
[18:17]  * rfkrocktk failed.
[18:23] <pleia2> there, should be all accurate now
[20:51] <xmetalcorex> i have a problem with   < apt -get  > apt: command not found
[20:51] <pleia2> it's apt-get
[20:51] <pleia2> no space :)
[20:52] <xmetalcorex> no space will try
[20:53] <xmetalcorex> i want to install dhcp
[20:53] <xmetalcorex> can you tell me the syntaxe
[20:53] <pleia2> xmetalcorex: this channel is for hosting classes, you want #ubuntu for support
[20:54] <jimcooncat> xmetalcorex: meet me in #ubuntu, I'll give you a hand with that
[20:55] <xmetalcorex> thanxxxxx alot


[00:56] <skaet> infinity,  once the d-i stuff is published could you nick highlight NCommander?
[00:59] <infinity> skaet: Yeah.  I jumped the gun on the upload by a few minutes, but it'll build in a while. :P
[01:00] <skaet> k
[01:08] <skaet> infinity,  can you check the pad, and make sure I've not missed anything with the latest updates?
[01:09] <skaet> http://pad.ubuntu.com/ubuntu-release
[01:11] <infinity> skaet: I think kernel+d-i is a catch-all for everything.
[01:11] <infinity> skaet: So, I'd just "rebuild everything that's in A1" once d-i publishes, and not worry so much about the specifics, personally. ;)
[01:12]  * skaet nods
[01:13] <infinity> I suppose you can skip core if you want, but I haven't been watching -changes like a hawk to make sure nothing's changed in that set since the last build.
[01:13] <infinity> And it's not like it takes long.
[01:14] <stgraber> infinity: no need to rebuild core, but besides that, yeah, looks like everything
[01:14] <stgraber> I rebuilt core just a few hours ago (because I thought we had isc-dhcp in there, which we apparently don't :))
[01:14] <infinity> Yeah, we really don't. ;)
[01:45] <infinity> Alright, d-i is building everywhere.  When it's done, it'll need to be published.
[01:46] <infinity> stgraber: You keeping an eye on things right now?  I need some food.
[01:48]  * ScottK has leftover spaghetti.  Want some?
[01:57] <stgraber> infinity: yep, I'm still kind of around
[02:09]  * infinity wonders why three of his d-i builds appear to be "stuck"...
[02:10] <infinity> stgraber: And where does the ISO tracker get its "Netboot" info from?
[02:11] <infinity> stgraber: Cause it's obviously lying. ;)
[02:11] <stgraber> infinity: looks at LP for published state IIRC but not using rmadison or anything like that to check it's actually published
[02:12] <infinity> stgraber: Erm, just looks for published state of the source, I guess?
[02:13] <infinity> stgraber: Cause none of the binaries it just mentioned were published.
[02:13] <infinity> (Some are still building)
[02:14] <stgraber> infinity: that sounds likely, yes, IIRC it's based on part of queuebot's code, so probably only looking at sources
[02:15] <stgraber> I guess I could make that use rmadison instead, would be more accurate and as it's just running once an hour, won't cause any extra load on the already slow rmadison server
[02:16] <infinity> Or the API...
[02:17] <infinity> Anyhow.  d-i all built now, should hit the :33 run, and be published before the hour.
[02:17] <stgraber> yeah but the LP's definition of "published" is usually off by whatever time the publisher needs to run
[02:18] <infinity> Oh, true.
[02:19] <ScottK> Which is a really odd definition.
[02:19] <infinity> It's true, from the publisher's POV.
[02:19] <infinity> It's published when it hits disk.
[02:19] <infinity> The fact that it hasn't run apt-ftparchive yet, or triggered mirrors.  Meh. :P
[02:20] <infinity> (I suppose one could queue up all the "we published in this run" toggles and hit them at the end, but it makes the whole thing be one scary long transaction)
[02:22] <infinity> Anyhow.  Food.  I was going to do that.
[03:07] <stgraber> oh, d-i published, let's kick some rebuilds
[03:09] <skaet> thanks stgraber
[03:09] <stgraber> desktop and alternates are building
[04:03] <stgraber> skaet, NCommander, infinity: Going to call it a day now. I have ARM desktop building and the desktop pipeline running on nusakan, assuming it works properly, that should cover everything but ARM server that'll still need to be started manually whenever ARM desktop finishes
[04:03] <skaet> Thanks stgraber
[04:03] <skaet> sleep well!
[04:04]  * skaet looks like she'll be up with the grub/AMI issue for a bit.  :P
[05:35] <NCommander> stgraber: skaet taking over now for the night
[06:17] <knome> somebody familiar with gtk3? :]
[06:22] <NCommander> knome: not really but I might be able to take a look
[06:22] <NCommander> whats up ?
[06:23] <knome> bug #1008682
[06:23] <ubot2`> Launchpad bug 1008682 in gtk+3.0 "Resize handle can lead to unintended window movement and jumps (dup-of: 1001936)" [Undecided,Confirmed] https://launchpad.net/bugs/1008682
[06:23] <ubot2`> Launchpad bug 1001936 in gtk+3.0 "GTK3 Grab/Move Triggered on Mouse Click" [Undecided,Confirmed] https://launchpad.net/bugs/1001936
[06:24] <micahg> knome: #ubuntu-desktop
[06:24] <knome> the dup has better description
[07:28] <jibel> what is the status of desktop rebuilds ? stgraber says at 3:09UTC "<stgraber> desktop and alternates are building" but I don't see them on the tracker and cdimages.u.c
[08:20] <cjwatson> ogra_: I wasn't going to do autosyncs before reading IRC anyway. :-)
[08:20] <micahg> cjwatson: are you up for some security copies?
[08:26] <cjwatson> slangasek: I'm OK with that - I've gone ahead and added bdmurray now
[08:26] <cjwatson> micahg: sure, what do I need to do?
[08:26] <micahg> cjwatson: please copy firefox from ubuntu-mozilla-security for lucid, natty, oneiric, and precise to their respective security pockets (updates as well if you like)
[08:27] <cjwatson> grr, why are these docs still all about copy-package.py
[08:28] <cjwatson> do you mind if I take a few minutes to modernise the process while I'm here?
[08:29] <micahg> cjwatson: sure, I'm working on the USN, so I've got a little time (would like it published sometimes in the next hour :))
[08:30] <micahg> cjwatson: as long as I have you here, I tried to use lp-shell to do the copy, but ended up with a silent failure
[08:30]  * micahg wonders which piece he's missing to make this work
[08:32] <cjwatson> not sure
[08:33] <cjwatson> you're in core-dev, that should normally be enough to at least get it to land in the queue
[08:33] <cjwatson> hah, it was
[08:33] <cjwatson> https://launchpad.net/ubuntu/lucid/+queue?queue_state=1
[08:33] <cjwatson> micahg: please just do whatever you did for the other series as well :)
[08:34] <micahg> ooh, but I should have permissions for the other series as well
[08:34] <micahg> oops, I mean that pocket
[08:34] <cjwatson> it was a silent *success*, not a silent *failure* - but you missed the fact that it'll land in the queue (a common gotcha, this confused me as well)
[08:34] <micahg> why is it in unapproved
[08:34] <cjwatson> because
[08:34] <micahg> ah, queuebot :)
[08:34] <cjwatson> happens when archive admins use the API to copy stuff too
[08:34] <micahg> \o/
[08:34] <cjwatson> I have a bug open about it
[08:34]  * micahg didn't notice queuebot spitting that out above
[08:36] <Riddell> do the current candidate images have known re-spin issues or are they good to test?
[08:36] <micahg> cjwatson: I'll try to update our scripts to use copyPackage which should fix my timeout issues as well (but how do we approve)
[08:36] <cjwatson> micahg: you'll have to ask one of us to
[08:37] <cjwatson> until such time as I can arrange for LP to allow per-pocket queue admin privileges
[08:37] <Laney> get bug #648611 fixed :-)
[08:37] <ubot2`> Launchpad bug 648611 in launchpad "ubuntu-sru either have too much or too little permission as queue admins" [High,Triaged] https://launchpad.net/bugs/648611
[08:37] <micahg> ah, so maybe I'll just make a copy for me ATM (almost everyone else can just do their copies)
[08:37] <cjwatson> indeed
[08:37] <micahg> cjwatson: should I do the manual copy to -updates or wait for the copy job?
[08:37] <cjwatson> I'm fine with letting the cron job do it
[08:38] <cjwatson> I have kind of started on 648611, I got the DB column added
[08:38]  * micahg hugs stgraber for showing me lp-shell over the weekend
[08:39] <micahg> cjwatson: so, they're all there
[08:39] <cjwatson> I've started on a generic API copy-package tool, but since you've already copied these I won't rush it
[08:39] <micahg> yeah, i've got the 3 lines I need
[08:41] <micahg> \o/ and solved the issue of my stuff not hitting the changes list :)
[08:43] <cjwatson> is there anything useful I can do for a1?  I'm thoroughly out of date :)
[08:44] <Daviey> cjwatson: Ah, i was writing one over the weekend aswell.. but lost my opportunity to try it.. I'm happy to drop mine.
[08:47] <Riddell> stgraber is eu based driver for alpha 1 and last seen at 5 in the morning, I guess he won't we awake for a bit!
[08:48] <cjwatson> Daviey: whichever of us wins :)
[08:49] <micahg> cjwatson: if you're taking feature requests for the tool, please include the option to sponsor as well
[08:58] <Daviey> I don't know that copyPackage supports that.
[08:58] <Daviey> cjwatson: Well, i would have won.. but my chance to use it was hijacked :)
[08:59] <Laney> copyPackage does support sponsoring. It's how we sponsor syncs
[09:01] <micahg> hooray for reuseability
[09:03] <Daviey> Hmm, Laney - do you have a package you know that was used on?
[09:03] <Laney> gosh
[09:03] <Daviey> The one over the weekend seems to have a bad 'details' page https://launchpad.net/ubuntu/+source/imagemagick
[09:03] <Laney> yes, that's another bug
[09:03] <Daviey> click Quantal publication
[09:04] <Laney> look at the SPPH in the API, or the changes mail
[09:05] <Daviey> ah yes, you are quite right, it does support sponsoring :)
[09:05] <Laney> bug 861488
[09:05] <ubot2`> Launchpad bug 861488 in launchpad "Mention sync requester on package version page" [High,In progress] https://launchpad.net/bugs/861488
[09:06] <Daviey> hmm, all details pacges seem broken on that package.
[09:06] <Laney> I'll need someone to help me finish that though, because Launchpad
[09:06]  * Laney gets on a train to Cambridge
[09:14] <jibel> can you respin desktop images or look what happened to the last respin, we need kernel 3.4.0-5.11 for Mac
[09:14] <Riddell> ooh quantal works!
[09:15] <Laney> a quantal of solace
[09:23] <xnox> Laney: tooodotoooo toooodotooo tah dah
[09:25] <Laney> xnox: this release is forever associated in my mind with http://youtu.be/vjcic99S
[09:26] <xnox> Laney: with 'An error occurred during validation?!'?
[09:26] <Laney> hopefully not
[09:27] <xnox> Laney: the link is broken =( me don't see anything
[09:28] <Laney> http://youtu.be/vjcic99SNog
[09:28] <Laney> weird, what happened there?
[10:14] <ogra_> hmm, is the omap3 kernel still not in the archive ?
[10:14]  * ogra_ doesnt see any arm image rebuilds
[10:25] <ogra_> infinity, hmm, looking at the ac100 build failure i guess we need to teach live-build to divert flash-kernel during build, it tries to find the boot partition otherwise during update-initramfs
[10:45]  * ogra_ would be really happy if someone could trigger another armhf rebuild, seems there was a stale archive lock during the last try
[10:49] <ogra_> oh, looking at the failure mails that seems to apply to all images, apparetnly something is wrong with the archive mirror
[10:50] <ogra_> lockfile: Sorry, giving up on "/srv/cdimage.ubuntu.com/etc/.lock-archive-sync"
[10:50] <ogra_> Timed out waiting for archive sync lock!
[10:52] <ogra_> hmm, and indeed there are two lockfile processes in the processlist on nusakan
[10:53] <ogra_> cjwatson, ^^^ any idea ?
[10:53]  * ogra_ doesnt just want to kill them, i'm not sure what exactly triggers them, though having two for the same lockfile seems pretty wrong
[10:56] <cjwatson> looking
[10:58] <cjwatson> it's apparently stale; log/ubuntu/quantal/daily-live-20120606.log got killed for some reason I think.  I've broken the lock
[10:59] <ogra_> thanks, seems there were rebuilds for almost everything that failed due to it
[11:00] <ogra_> ubuntu-server/precise/daily, ubuntu/precise/daily and ubuntu/quantal/daily-preinstalled is what i got mails for
[11:02] <cjwatson> somebody who's more familiar with what the RM actually wants rebuilt today should do that (i.e. not me)
[11:02] <cjwatson> kind of surprised the cron jobs are still on
[11:02] <ogra_> precise ...
[11:02] <cjwatson> oh, they aren't, yeah, ok
[11:02] <cjwatson> I'll just leave those, they'll wait 'til tomorrow
[11:05] <ogra_> though we need armhf rebuilds (new omap3 kernel) ... i guess i'll trigger these ... if we wait for someone from release team i wont have enough time to test anymore i guess
[11:06] <ogra_> heh, looks like you moved something by removing the lock :)
[11:06]  * ogra_ fires off a preinstalled desktop build
[13:18]  * stgraber waves
[13:18] <stgraber> Riddell: not quite EU based at the moment ;) back in Canada
[13:19] <stgraber> ok, so looking at what happened there, we seem to have everything but Ubuntu Desktop...
[13:19] <ogra_> just wait until we swallow you too !
[13:19] <ogra_> stgraber, there was a stale lockfile
[13:19] <ogra_> colin fixed it, i didnt know what was missing apart from preinstalled (which i triggered a still running build for)
[13:21] <Riddell> oh new images
[13:21] <stgraber> ok, thanks. Did anyone actually retrigger Ubuntu Desktop after that?
[13:22] <ogra_> nope, as i said, i wasnt sure what else had failed
[13:22] <ogra_> go ahead :)
[13:22] <Riddell> stgraber: what's the issue needed these respins?
[13:23] <stgraber> ok, having a look at the pad then. We also have a precise cron running at the moment that I'll wait for before starting another build
[13:23] <stgraber> Riddell: kernel
[13:23] <stgraber> Riddell: exploding on mac hardware
[13:23] <ogra_> why isnt the pad in the topic anymore though ?
[13:23]  * ogra_ didnt think about looking there
[13:23] <Riddell> ogra_ just what I was wondering
[13:24] <ogra_> :)
[13:24] <Riddell> people have been saying the pad has issues
[13:24] <jibel> Riddell, and new ubiquity
[13:24] <stgraber>           things during freezes where you shouldn't, or be prepared to apologise to the release team | we accept payment in cash, check or birdseed | melior malum quod cognoscis
[13:24] <jibel> to fix wireless setup page
[13:25] <stgraber> gah
[13:25] <ogra_> stgraber, try again :)
[13:25] <stgraber> ogra_: 13:25 -!- #ubuntu-release You're not a channel operator
[13:25] <ogra_> ah, bah
[13:25] <Riddell> stgraber: if it is in use, what's the URL?
[13:26] <jibel> stgraber, I updated the pad. Ubuntu Desktop and Wubi have not been rebuilt
[13:26] <stgraber> http://pad.ubuntu.com/ubuntu-release
[13:26] <stgraber> jibel: thanks
[13:27] <jibel> stgraber, but other images are appearing (k|l|edubuntu) so maybe there's a build in progress
[13:28] <stgraber> jibel: yeah, updating the pad for these. They were in the pipeline, not sure whether they just worked or whether cjwatson triggered them after fixing the lock
[13:29]  * stgraber waits for things to settle down on nusakan to look at exactly what we're missing and build that
[13:30] <stgraber> so far it looks like ARM images (both desktop and server), ubuntu desktop and wubi
[13:30] <stgraber> ogra_: what ARM images are you building? server or desktop?
[13:39] <stgraber> jibel: wubi is almost built, then I'll look at ubuntu desktop
[13:40]  * stgraber tries to understand why the previous ARM desktop builds never published to the tracker, nothing seems to have gone wrong there (besides ac100 failing)
[13:42] <stgraber> oh, ok, got hit by the same lock issue as ubuntu...
[13:45]  * skaet waves good morning and goes to check the pad
[13:46] <stgraber> skaet: lock file prevented most of the overnight builds from happening, cjwatson fixed it earlier today, so we're still missing ARM and Ubuntu Desktop
[13:46] <skaet> thanks stgraber
[13:46] <stgraber> skaet: Wubi should appear on the tracker anytime now
[13:47]  * stgraber starts Ubuntu Desktop now
[13:48] <stgraber> jibel: ETA 1h30-2h for desktop images
[13:51] <jibel> stgraber, and wubi is broken
[13:51] <jibel> the exe downloads precise instead of quantal
[13:52] <stgraber> ev: ^
[13:52] <cjwatson> stgraber: I didn't retrigger anything
[13:52] <ev> arghhh
[13:52] <ev> my mistake
[13:52] <ev> fixing
[13:53] <stgraber> cjwatson: right, noticed after checking exactly what was still running. It just unlocked the existing pipeline but by that time, ubuntu desktop and ARM had already timed out. Anyway, should have everything fixed in a couple of hours (maybe I'm a bit optimistic on ARM build time though ;))
[13:54] <ogra_> ARM should be done soon
[13:54] <ogra_> its only ac100 left, all others have finished
[13:54] <ogra_> though we need preinstalled-server too
[13:55] <ogra_> skaet, ^^^
[13:56] <stgraber> ogra_: ok, I'll start preinstalled server as soon as your desktop builds are done
[13:56] <skaet> ogra_, noted. :)
[13:56] <stgraber> ogra_: does it look like we'll actually have a working ac100 build this time?
[13:56] <stgraber> well, s/working//
[13:57] <ogra_> stgraber, no, that will need live-build changes (flash-kernel needs to be diverted, it tries to write to SD card on the builder)
[13:57] <ogra_> so no ac100 for A1
[14:20] <ev> right, despite a curiously slow link to the DC, http://people.canonical.com/~wubi/quantal/stable is in place with the fixes for 12.04 references in quantal
[14:21] <stgraber> http://people.canonical.com/~evand/wubi/quantal/stable
[14:22] <jibel> ev, I confirm the fix works
[14:23] <ev> err yes, that url
[14:23] <ev> thanks stgraber, jibel :)
[14:26] <jibel> then second stage of the installation crashes :)
[14:27] <bdmurray> cjwatson: so to be clear on the +queue page I check the checkbox and click accept?  the overrides are unnecessary most of the time correct?
[14:31] <cjwatson> For SRUs?
[14:31] <cjwatson> You generally shouldn't need to override SRUs, no.
[14:32] <bdmurray> cjwatson: yes, thanks
[14:47] <jibel> ev, the problem with wubi during the second stage is a kernel crash
[14:48] <jibel> not wubi's fault
[14:50] <ev> music to my ears ;)
[14:52] <jibel> collecting logs will be fun, hard lock, black screen
[14:58]  * skaet suspects no WUBI for A1
[15:04] <stgraber> ok, starting arm server now
[15:07] <ogra_> thanks :)
[15:19] <jibel> skaet, I confirm no Wubi. kernel crash + segfaults in sysctl, python, stty
[15:19] <jibel> I'll file a bug with the logs
[15:19] <skaet> Thanks jibel,   is there a bug number now?
[15:19] <skaet> heh
[15:20] <jibel> skaet, apart from Wubi there is bug 1009052 on Ubuntu Desktop with Asian languages
[15:20] <ubot2`> Launchpad bug 1009052 in language-selector "CJK Installation fails with error: poppler-data : Breaks: cmap-adobe-gb1 (<= 0+20090930-2)" [High,Confirmed] https://launchpad.net/bugs/1009052
[15:21] <skaet> thanks jibel.
[15:21] <xnox> ev ^^^^
[15:22] <xnox> i guess it's not wubi specific is it?
[15:22]  * ev hides
[15:22] <skaet> xnox,  nope.
[15:22] <skaet> :)
[15:22] <xnox> ev: you can come out now.
[15:22] <ev> phew
[15:22] <ev> that was a close one
[15:23]  * xnox realises that I should get wubi buildable before next milestone as per spec
[15:23] <jibel> xnox, it is not, now I wish it is not the new kernel.
[15:29] <seb128> jibel, bug #1009052 is a ghostscript issue, somebody needs to merge it with Debian
[15:29] <ubot2`> Launchpad bug 1009052 in ghostscript "CJK Installation fails with error: poppler-data : Breaks: cmap-adobe-gb1 (<= 0+20090930-2)" [High,Confirmed] https://launchpad.net/bugs/1009052
[15:29] <seb128> we need that change
[15:30] <seb128> ghostscript (9.05~dfsg-6) unstable; urgency=low
[15:30] <seb128>    * Have libgs9 depend on recent poppler-data favored over
[15:30] <seb128>      gs-cjk-resource.
[15:37] <seb128> cyphermox_, ^ do you think you could look at that?
[15:38] <seb128> cyphermox_, maybe no need to merge it but I think the depends need to be changed for zh to be installable
[15:39] <cyphermox_> seb128: sure, it was my next firefox tab too ;)
[15:39] <seb128> cyphermox_, thanks, bug reassigned to you ;-)
[15:46] <jibel> skaet, bug 1009564
[15:46] <ubot2`> Launchpad bug 1009564 in linux "Quantal Ubuntu Wubi failed to install" [Undecided,New] https://launchpad.net/bugs/1009564
[15:53] <skaet> thanks jibel
[16:16] <stgraber> and that's all the rebuilds finally done!
[16:19] <stgraber> time for food now, will test Edubuntu when I get back
[16:35] <balloons> jibel, did you see the wubi upgrade failure from last night? https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1009226
[16:35] <ubot2`> Launchpad bug 1009226 in update-manager "can't load DistUpgradeViewGtk (No module named vte)" [Undecided,Confirmed]
[16:35] <balloons> or did that cause the re-spin? ;-)
[16:36] <balloons> also, will the fix for 1009052 also fix jp language?
[16:38] <ogra_> infinity, will you test mx5 ?
[16:45] <infinity> ogra_: Can't right now, my mx5 is in the middle of some builds. :/
[16:45] <jibel> balloons, I saw the upgrade bug.
[16:46] <jibel> it can be fixed after post-a1
[16:50] <ogra_> infinity, ah, sad, i should really get one some day
[16:51] <ogra_> (not that i'm eager to do more image testing though)
[16:53] <jibel> desktop on mac and x86 are good. I'll do more tests after dinner.
[16:53] <jibel> import open issues for a1 bug 1009052 and bug 1009564
[16:53] <ubot2`> Launchpad bug 1009052 in ghostscript "CJK Installation fails with error: poppler-data : Breaks: cmap-adobe-gb1 (<= 0+20090930-2)" [High,Confirmed] https://launchpad.net/bugs/1009052
[16:53] <ubot2`> Launchpad bug 1009564 in wubi "Quantal Ubuntu Wubi failed to install" [Critical,Confirmed] https://launchpad.net/bugs/1009564
[16:56] <seb128> jibel, is the cjk one something you want to see in for a respin?
[16:56] <seb128> skaet, ^
[16:56] <seb128> the fix is depends change for ghostscript
[16:58] <skaet> seb128,  given we're at A1,  I'm fine release noting it.   But if a fix is available,  and we need to respin for other reasons, it would be good to include it, certainly.
[16:59] <seb128> skaet, ok, fix will be uploaded a bit later by cyphermox_
[17:00] <skaet> thanks seb128 :)
[17:00] <jibel> seb128, agreed with skaet
[17:00] <seb128> skaet, jibel: thanks
[17:40]  * skaet --> lunch,  biab
[18:25] <stgraber> highvoltage: did you have a chance to test ltsp-live yet? it looks a bit broken here. I'll test some more and see if I can easily fix it
[18:26] <highvoltage> stgraber: I did, it failed, I didn't have enough time to confirm the failures so I left it out of the test
[18:27] <dobey> can someone please accept the ubuntuone-client i just uploaded to precise-proposed, as it is the same set of in-progress SRUs, merged with the security fix that was released today
[18:27] <stgraber> highvoltage: ok, was it stuck configuring openssh?
[18:28] <highvoltage> stgraber: it got to "ltsp live should be ready to use", I got dhcp on the clients and it seemed to load the kernel but didn't continue from there
[18:29] <stgraber> ok, so I had a different problem here ... triple checking the md5 as I saw some squashfs errors at one point, might just be corrupted iso
[18:47] <stgraber> highvoltage: second try booted and worked fine, so just going to blame it on kernel/squashfs/kvm and consider it a pass (good enough for a1) :)
[18:48] <highvoltage> stgraber: sounds reasonable.
[19:24] <balloons> skaet, thoughts on when we expect to announce tomorrow? any more respins in the works? I know there's pending fixes
[19:25] <skaet> balloons,  depends on whether we decide to respin or not, and how the testing is going.
[19:26] <skaet> most of the bugs we know about, while not good, we can live with for an A1, and they'll get fixed on the next daily.
[19:37] <skaet> Daviey,  is server going with the 800MB USB form factor this release as well,  or sticking with CD sized images?
[19:38]  * skaet trying to figure out if Bug 1009553 is invalid (working by designed or there's something that needs documenting)
[19:38] <ubot2`> Launchpad bug 1009553 in debian-installer "jeos install oversized" [Undecided,New] https://launchpad.net/bugs/1009553
[19:44] <cyphermox_> skaet: ghostscript uploaded; if you're looking to respin the zh image.
[19:45] <slangasek> skaet: does that bug follow from some documented minimum requirements for jeos?
[19:46] <skaet> cyphermox_, thanks. :)
[19:47] <skaet> slangasek,  could be,  not familiar with jeos.
[19:48] <slangasek> I guess that's a question the server team should answer
[19:48] <skaet> yup,  but if others know,  feel free to chime in.  ;)
[20:04] <dobey> slangasek: hi. can you please accept the new ubuntuone-client upload to precise-proposed? it's the same SRU set, but includes the security fix patch that was released today as well
[20:18] <Daviey> skaet: I'd rather we strive for the smaller image, but not be hold to it
[20:18] <stgraber> dobey: the diff looks a bit confusing (the changelog entry), did you properly use -v3.0.0-0ubuntu1.1 when building the .changes?
[20:19] <Daviey> skaet: although.. *A2* currently looks around 875M :o
[20:20] <skaet> Daviey,   could you put a statement out as to what target you're aiming at?
[20:34] <slangasek> Daviey: do you know if there's documentation somewhere for what the jeos footprint is supposed to be?
[20:35] <slangasek> dobey: accepted
[20:38] <Daviey> slangasek: yes, there is.. and we test for it.. i need to double check the figure
[20:40] <Daviey> skaet: "Unlike the Desktop flavour, we are currently targeting the image to fit onto a standard cd image (703MB).  However, some structural changes are expected for Alpha 2, which will allow us to re-review this sizing requirement"
[20:40] <Daviey> slangasek: we are still 703MB for max CD, or was that now reduced ?
[20:40] <skaet> Daviey,  sounds good.  :)
[20:40] <slangasek> Daviey: are we talking download size, or image size?
[20:41] <slangasek> Daviey: bug #1009553 that skaet pointed to is about the install footprint, claiming that it's bigger than it should be
[20:41] <ubot2> Launchpad bug 1009553 in debian-installer "jeos install oversized" [Undecided,New] https://launchpad.net/bugs/1009553
[20:43] <Daviey> slangasek: image size for minimal install
[20:43] <Daviey> (formally known as jeos)
[20:43] <slangasek> sorry, I meant "download size or install size"
[20:43] <Daviey> slangasek: That bug ius valid, see https://jenkins.qa.ubuntu.com/view/Quantal/view/ISO%20Testing%20Dashboard/job/quantal-server-amd64_minimal-virtual/14/testReport/
[20:44] <slangasek> ok
[20:44] <Daviey> It's not an A1 blocker in my book.
[20:44] <slangasek> it's also probably not a debian-installer bug... is there a better place to track it?
[20:44] <Daviey> The 500MB is arbitrary that we selected, and it should be reduced to fit that.. but for A1 - i'd be happier release noting it
[20:44] <Daviey> slangasek: no better place i can think of
[20:45] <Daviey> cd image project?
[20:51] <slangasek> Daviey: I was thinking ubuntu-meta, since that actually controls the selection of packages included, I think
[21:13] <skaet> Daveiy,  I put some placeholders into the TechnicalOverview,  massage to something better as time permits on the image size
[21:17] <Daviey> ta
[21:37] <balloons> skaet, stgraber I think we've got a whoops on the tracker.. the upgrades have the upgrade test from lucid.. that shouldn't be a supported upgrade
[21:37] <balloons> i can disable if you agree
[21:38] <Daviey> That is most certainly a bug.  Nice catch balloons
[21:38] <balloons> btw Daviey are you and team doing all the testing for the server images?
[21:40] <Daviey> balloons: yes, both Jenkins and Human
[21:41] <Daviey> balloons: https://lists.ubuntu.com/archives/ubuntu-server/2012-June/006328.html
[21:41] <balloons> k, we had some testing during the precise final iso, but I've not focused on getting community testing for the server images
[21:41] <balloons> for this alpha I mean to say
[21:41] <stgraber> balloons: actually it's a bug we shouldn't try to fix until we have the new website
[21:41] <stgraber> balloons: currently we have both precise and quantal on the tracker
[21:41] <stgraber> balloons: quantal should only have precise => quantal upgrades
[21:41] <stgraber> balloons: but precise definitely needs lucid => precise
[21:41] <Daviey> balloons: yeah, we expected that :P
[21:42] <balloons> stgraber, yes.. so I should re-enable it then?
[21:42] <stgraber> balloons: yeah
[21:42] <balloons> :-)
[21:42] <stgraber> balloons: it's easier to remember to consider 1/2 as a pass than to go look at oneiric => precise upgrade results to check if they aren't actually lucid => precise :)
[21:42] <stgraber> and we'll have that fixed for alpha2 with the tracker update
[21:43] <balloons> k
[22:12] <balloons> can we get http://www.ubuntu.com/testing updated? who can help with this?


 "I've been looking at `boost::..." <- This may be a good time for you to look at adding the API alan_g referenced: [issue 2543](https://github.com/MirServer/mir/issues/2543)?
[00:01] <RAOF> Hm. Except you'd *actually* be wanting to add a timer, which would be exposing an `Alarm`-type API.
[00:01] <RAOF> But it's the same sort of thing.
[06:12] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2601](https://github.com/MirServer/mir/pull/2601): Ensure test_wayland_generator runs (and fix test)
[06:12] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] closed [issue #2597](https://github.com/MirServer/mir/issues/2597): test_wayland_generator fails (but not run by ptest target)
[07:57] <RAOF> Hey hey Saviq. WRT the fact that [we don't test the *tarballs* we release](https://github.com/MirServer/mir/issues/2596), could we in fact have a github action that runs on final release, runs `tools/make_release_tarball`, and reports any failures?
[07:58] <RAOF> (We would also want to add a "run the tests" check to `make_release_tarball`, but that's easy)
[07:58] <Saviq> We really should have a pre- job that builds the tarball and source packages, where applicable, and goes from there
[07:59] <Saviq> Rather than every job checking out on its own
[07:59] <RAOF> Aaah, yes. That would be neatm.
[07:59] <RAOF> s/neatm/neat/
[08:00] <Saviq> I'll put that as part of my release process rework
[08:15] <Saviq> We broked something:
[08:15] <Saviq> https://launchpad.net/~mir-team/+archive/ubuntu/dev/+packages?field.name_filter=mir&field.status_filter=&field.series_filter=
[08:18] <Saviq> It's the release merge that triggered it
[08:31] <alan_g[m]> Just seen the email storm. Are you looking into it?
[08:32] <Saviq> Nothing obvious so far
[08:33] <Saviq> The version bump?
[08:33] <alan_g[m]> unable to open lockfile /run/user/2001/wayland-0.lock check permissions... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/b782fab1ffacb67ca4786e13633333b3b72fb395)
[08:34] <alan_g[m]> That's how the tests are breaking. Now for why...
[08:37] <alan_g[m]> Saviq: Has the Launchpad infrastructure changed?
[08:40] <Saviq> Doubt that
[08:41] <Saviq> I will push the last working one with a version bump to confirm
[08:42] <alan_g[m]> Ack. My first suspicion is that a useless XDG_RUNTIME_DIR has been added to the environment
[08:43] <alan_g[m]> Because we have a hack along the lines of "if XDG_RUNTIME_DIR is missing, set it (to /tmp)"
[08:51] <alan_g[m]> Yup, we've now got the following user environment:
[08:51] <alan_g[m]> XDG_RUNTIME_DIR=/run/user/2001
[08:51] <alan_g[m]> XDG_SESSION_CLASS=background
[08:51] <alan_g[m]> XDG_SESSION_ID=c80
[08:51] <alan_g[m]> XDG_SESSION_TYPE=unspecified
[08:51] <alan_g[m]> Which is new with the failing builds
[08:53] <alan_g[m]> So the question is "what is wrong with `/run/user/2001` - does it exist? Etc?"
[08:55] <Saviq> I feel like we've been through this before...
[08:55] <alan_g[m]> Can you get access to an instance to poke around?
[08:56] <alan_g[m]> We have
[09:05] <Saviq> For reference, reported the issue to Launchpad:
[09:05] <Saviq> https://answers.launchpad.net/launchpad/+question/702995
[09:07] <alan_g[m]> OK, I'll leave you with this one
[09:17] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq requested a review from AlanGriffiths for [pull request #2603](https://github.com/MirServer/mir/pull/2603): tests: fix XDG_RUNTIME_DIR handling
[09:17] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq opened [pull request #2603](https://github.com/MirServer/mir/pull/2603): tests: fix XDG_RUNTIME_DIR handling... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/62bc3aaa1d4cd920f95e15dd759d7c8c1ee506b5)
[10:19] <alan_g[m]> Saviq is there any pattern to your "transparent windows" issue? I've been working on my oldest laptop without seeing it yet. Is there a particular app it happens to?
[10:20] <Saviq> If I had to guess, it'd be Firefox affected most often, but that's mostly because that's what I'm looking at the most
[10:20] <Saviq> s/mostly/likely/
[10:21] <alan_g[m]> OK, so I've got glmark running behind clion and firefox and seeing nothing. (yet)
[10:22] <Saviq> It does only happen occasionally, a few flashes in quick succession, then it's back in order again
[10:22] <Saviq> Between 1-3 times a day
[10:23] <alan_g[m]> OK, so may not show in an hour or two
[11:07] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2603](https://github.com/MirServer/mir/pull/2603): tests: fix XDG_RUNTIME_DIR handling
[12:18] <Saviq> alan_g ah, got an idea about my copy/paste issues. There's two c/p modes are there not? "online", where clients negotiate the data, and "cached", where it's a one way thing. So the latter is what's not working I think. If I quit the "source", I never get to paste anything
[12:19] <Saviq> Maybe Firefox / Thunderbird behave similarly to that with some copies (from the address bar, or through "copy link")?
[13:11] <alan_g[m]> There's only the one way we support, and that requires both source and destination to be alive
[13:14] <alan_g[m]> primary-select (which we don't support) could allow stuff to be cached by a third party
[13:17] <Saviq> Sure, but I don't mean primary-select. I mean Ctrl+C, close the source, Ctrl+V
[13:17] <Saviq> That, for at least some cases, should work
[13:17] <alan_g[m]> The source needs to hang around (possibly without a window) to negotiate mime type and data
[13:22] <alan_g[m]> The Mir code is pretty simple (just relaying between source and sink) if you want to poke around:src/server/frontend_wayland/wl_data_device.cpp
[13:31] <Saviq> Sure, I just mean we may need to complicate it to support this (valid, IMO) use case - regardless of whether this is actually what Firefox / Thunderbird is actually impacted by
[13:31] <alan_g[m]> You mean adding a new protocol and hoping clients implement it?
[13:33] <Saviq> I don't think there's now protocols needed. I mean, other compositors do it already
[13:34] <alan_g[m]> Other compositors implement primary selection
[13:34] <Saviq> Conceptually, Mir could take over the mime type negotation in the case when source went away, with the information it has
[13:34] <Saviq> But Ctrl+V doesn't paste primary selecton
[13:34] <Saviq> +i
[13:35] <Saviq> I'll have to log out into GNOME to confirm, but I believe the compositor takes over the mime type negotation if the source went away, with the information it does have
[13:35] <Saviq> It may not work always, but for simple cases like text the compositor can certainly do it
[13:43] <Saviq> Looks like the my fix didn't work...
[13:43] <alan_g[m]> Agreed
[13:44] <Saviq> In other news, https://bugs.launchpad.net/ubuntu/+source/gcc-12/+bug/1983852 spread to other architectures, and the breaking gcc-12 now migrated to the release pocket.
[13:47] <alan_g[m]> Feels like "Whac-A-Mole"
[14:08] <alan_g[m]> I should think before approving! You need something like `XDG_RUNTIME_DIR=/tmp GTEST_OUTPUT=xml:./ dh_auto_build -- ARGS="-V" ptest`
[14:08] <alan_g[m]> This is running in make, not bash
[14:09] <alan_g[m]> Shall I just push to main?
[14:11] <Saviq> Hmm but export should work in make? But maybe I indented and that was wrong?
[14:12] <Saviq> Right, it'd have to be `XDG_RUNTIME_DIR := /tmp\nexport XDG_RUNTIME_DIR`
[14:12] <alan_g[m]> No make basically runs the export command on a shell of its own
[14:12] <Saviq> That's with the indent, without the indent, that's a make command, not a shell one?
[14:13] <Saviq> I. Hate. Make.
[14:13] <alan_g[m]> Resistance is futile
[14:14] <alan_g[m]> Anyway, shall I push the fix?
[14:20] <alan_g[m]> nm done it. What can go wrong?
[16:55] <alan_g[m]> Saviq I've not seen your "transparent windows" issue despite looking for it all day.
[16:56] <alan_g[m]> Nor have I come up with a plausible theory to investigage (yet).
[16:56] <Saviq> Sorry :/
[16:58] <alan_g[m]> I have, however noticed that with a nested session I can get garbled window content with windows spanning displays. (But you have see-through, not just garbage, so I think unrelated)
[16:59] <alan_g[m]> So, I think there's something wrong in the buffer management. And that might be a cause for both symptoms
[17:01] <alan_g[m]> Anyway, signing off in the hope of progress tomorrow
[17:01] <alan_g[m]> 👋
[17:01] <Saviq> My issues are likely to be gone tomorrow
[17:01] <Saviq> Just got the new laptop, so if it's load related…
[17:03] <alan_g[m]> You'll have the one where it manifests though.
[17:06] <Saviq> So I should not burn it on the stake?
[17:06] <Saviq> Good night o/
[18:28] -GitHub[m]:#mir-server- **[MirServer/mir]** wmww opened [issue #2604](https://github.com/MirServer/mir/issues/2604): Popups dismissed by Mir when parent clicked... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/dc6cabf51301d1dbea557642bceed1d7ec0edaea)
[22:26] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths opened [issue #2605](https://github.com/MirServer/mir/issues/2605): Nesting Wayland compositors should use pointer confinement... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/49ef59251f63d6ca3414f21a0b163bf264890be7)


[19:43] <sa7noun_> hi, I need help to fix my network wireless card, I installed ubuntu gnome 16.04 and the wifi won't turn on , can some one give some help ? thanks
[20:25] <sa7noun>  hi , can some one help me to resolve wireless network issue ? the wifi won't turn ON ! here is the pastebin of lspci | grep Wireless : https://pastebin.com/Nvua1nfE , thanks for your help