[07:09] <didrocks> good morning
[07:28] <Wimpress> Morning didrocks
[07:29] <didrocks> Guten Morgen Wimpress
[08:07] <hellsworth> good morning desktopers!
[08:08] <oSoMoN> good morning
[08:14] <didrocks> hey hellsworth, salut oSoMoN
[08:14] <didrocks> quel temps à Francfort ?
[08:14] <oSoMoN> salut didrocks, ça va?
[08:14] <oSoMoN> not raining :)
[08:15] <didrocks> oSoMoN: ça va :) raining here :p
[08:31] <robert_ancell> https://lists.x.org/archives/xorg-devel/2020-February/058417.html
[08:31] <robert_ancell> seb128, Wimpress Laney ^^
[08:36] <Laney> woah!
[08:39] <marcustomlinson> morning desktoppers
[08:40] <oSoMoN> good morning marcustomlinson
[08:42] <ricotz> good morning
[08:43] <seb128> gooood morning desktopers
[08:43] <ricotz> robert_ancell, imho this kind of impact of CI is expected
[08:43] <seb128> hey marcustomlinson popey ricotz , how are you?
[08:43] <marcustomlinson> seb128: doing ok thanks, you?
[08:43] <seb128> I'm good, thanks!
[08:46] <Laney> hey marcustomlinson ricotz didrocks
[08:47] <RikMills> morning
[08:47] <RikMills> seb128: I note autohinter seems to have just migrated the poppler transition :)
[08:49] <RikMills> oh, and there is an email as proof.....
[08:49] <seb128> hey RikMills, ah, good, I though gnome-desktop would have been needed to go together though, weird
[08:50] <Laney> didrocks: can you please promote me on https://salsa.debian.org/groups/ubuntu-dev-team/-/group_members ?
[08:51] <Laney> need some admin stuff
[09:15] <didrocks> Laney: will do once I find my creds :p
[09:16] <Laney> merci!
[09:17] <robert_ancell> ricotz, right, but we want it to keep working, as it's much better than the old system!
[09:22] <ricotz> robert_ancell, this is true -- I am seeing gitlab CI (on GNOME) running multiple times on the same commit (on any branch) which is overkill
[09:24] <ricotz> so there is room for improvements by restricting it to certains branches and making people aware when CI gets triggered
[09:24] <ricotz> hey seb128 Laney marcustomlinson didrocks
[09:25] <robert_ancell> ricotz, yeah
[10:17] <GunnarHj> Good morning seb128!
[10:17] <GunnarHj> I decided to prepare the update of ibus after all:
[10:17] <GunnarHj> https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus
[10:17] <GunnarHj> Does the GNOME specific FF exception apply?
[10:18] <seb128> hey GunnarHj , no it doesn't
[10:18] <seb128> is there features in the new version?
[10:19] <GunnarHj> seb128: Don't know. Guess I'd better look a bit closer to the changelog, then.
[10:21] <Laney> there is no GNOME specific FF exception
[10:21] <Laney> it's that GNOME's release schedule aligns with ours
[10:21] <Laney> (ish)
[10:23] <GunnarHj> Laney: Then I got it wrong, apparently.
[10:25] <Laney> That's OK, just wanted to clarify
[10:25] <GunnarHj> seb128: My impression is that there are only bug fixes and translations. The two first items are already in the archive via patches. https://github.com/ibus/ibus/releases/tag/1.5.22
[10:28]  * Laney salsa pokes didrocks
[10:28] <Laney> sorry, but trying to help Trevinho with pushing something
[10:39] <amurray> hey desktoppers - on an up-to-date focal install I am seeing weird font issues - seems like gnome-shell is perhaps using Cantarell instead of Ubuntu - and so things like shell dialogs look off - https://imgur.com/a/w6yEiB5
[10:40] <amurray> I tried searching for LP bugs but couldn't find any against gnome-shell or yaru-theme - should I file one and if so against which source package?
[10:40] <Laney> maybe wait a bit, we're trying to get gnome-shell 3.35 migrated so you can give that a go
[10:41] <amurray> Laney: sure, no worries - thanks!
[10:47] <didrocks> Laney: got it, you should be fine
[10:47] <Laney> thanks!
[10:47] <didrocks> Laney: what was the missing perm as maintainer?
[10:47]  * Laney feels the power
[10:47] <Laney> adding new people and creating new projects
[10:48] <didrocks> I can understand adding new people. Restriction creating projects is weird though
[10:48] <amurray> Laney: oh I just found https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1865373 which sounds like the same thing but filed against xorg
[10:49] <Laney> ah interesting
[11:13] <seb128> amurray, could be because yaru-theme migrated before gnome-shell, you could try downgrading that or upgrade the shell (hopefully it migrates in the next publisher run)
[11:26] <seb128> didrocks, the archive admin tools mostly work (at least change-override/remove-package/demote-to-proposed) with python3, easier than vm booting :) I just switched them in the vcs now
[11:28] <seb128> amurray, gnome-shell and co are just migrating, should make easier to test if the update fixes things
[12:22] <tseliot> Laney, hi did you build u-d-c in a PPA? (that triggers the test suite, and any syntax checks that we have in place)
[12:41] <Laney> tseliot: hmm, not sure about a PPA but I did use sbuild if that's enough?
[12:48] <tseliot> Laney, yes, that works too, thanks
[12:52] <seb128> tjaalton, the x11-utils update or maybe the xkeyboard-config made http://autopkgtest.ubuntu.com/packages/a/awesome/focal/amd64 unhappy
[12:52] <seb128> GunnarHj, ^
[12:53] <seb128> xkbcomp failing with errors lik Could not resolve keysym XF86RotationLockToggle
[13:07] <seb128> kenvandine, you had a snap-store-packagekit build failure due to
[13:07] <seb128> 'error: requested a non-existing branch on latest/edge for snap "snapcraft":
[13:07] <seb128>        pr-2794'
[13:07] <seb128> (armhf)
[13:08] <kenvandine> yeah, ignore that
[13:08] <kenvandine> amd64 built :)
[13:11] <Laney> tseliot: https://people.canonical.com/~laney/weird-things/udc.log.gz
[13:16] <tseliot> Laney, I don't see the test suite in that log. See this, for example: https://launchpadlibrarian.net/466697798/buildlog_ubuntu-bionic-amd64.ubuntu-drivers-common_1%3A<IP_ADDRESS>~<IP_ADDRESS>_BUILDING.txt.gz
[13:16] <Laney> I didn't disable it!
[13:16] <Laney> but ok, give me a second
[13:22] <GunnarHj> tjaalton: In xkeyboard-config 2.26 there were a few Debian patches which reverted certain upstream commits, for instance:
[13:22] <GunnarHj> https://salsa.debian.org/xorg-team/data/xkb-data/-/blob/aaf547756a393f0a9ef74b4136ca4a2050e8c478/debian/patches/revert-Map-evdev-keycode-KEY_BRIGHTNESS_CYCLE.diff
[13:22] <GunnarHj> Those patches were dropped in 2.29. Can that possibly have something to do with it?
[14:13] <GunnarHj> seb128: https://irclogs.ubuntu.com/2020/03/02/%23ubuntu-desktop.html#t13:22
[14:24] <Laney> tseliot: ah there is a test failure!!!
[14:25] <seb128> GunnarHj, thx for the hint, looks similar indeed
[14:26] <tseliot> Laney, good, have fun :P
[14:27] <GunnarHj> seb128: Guess it's best if tjaalton takes a look. He did the whole update - I was merely cheer leader. :)
[14:34] <marcustomlinson> hellsworth: https://launchpad.net/ubuntu/+source/libreoffice/1:6.3.5-0ubuntu<IP_ADDRESS>
[14:34] <marcustomlinson> Accepted :)
[14:35] <marcustomlinson> To proposed that is. Now once that builds you can test and update the SRU bug etc
[14:36] <Laney> tseliot: you know this fails on master too :P
[14:42] <tseliot> Laney, master (1:<IP_ADDRESS>) is in focal, so it definitely built https://launchpad.net/ubuntu/+source/ubuntu-drivers-common
[14:42] <Laney> jus' sayin!
[14:43] <Laney> I'll look into it
[14:43] <Laney> (after break)
[14:50] <GunnarHj> seb128: Are we agreed that the IBus update can be considered free of new features?
[15:09] <seb128> GunnarHj, let me have a look to the NEWS
[15:26] <GunnarHj> seb128: NEWS is not so useful, but this may help: https://github.com/ibus/ibus/releases/tag/1.5.22
[15:39] <seb128> GunnarHj, right, agreed it's not a ff item
[15:51] <GunnarHj> seb128: Good. It needs sponsoring, though... Can you put it into your 'queue'?
[15:53] <Laney> tseliot: ok I was wrong, it does build: https://launchpad.net/~laney/+archive/ubuntu/ppa/+sourcepub/11035868/+listing-archive-extra
[15:54] <Laney> I dunno why the gpu-manager tests were failing for me when I manualyran them
[15:57] <tseliot> Laney, maybe it was because gpu-manager hadn't been compiled yet, so the binary wasn't there
[16:01] <tseliot> Laney, either way, any specific reason why the feature needs to be on by default, and we allow users to disable it, whereas it would probably be used only in limited cases (so maybe keeping it disabled, unless "--with-oem" is used, would be better than it being enabled and passing "--no-oem")?
[16:02] <seb128_> GunnarHj, I can do the sponsoring yes, where are the files to upload?
[16:03] <GunnarHj> seb128: https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus
[16:11] <seb128_> GunnarHj, uploaded
[16:12] <GunnarHj> seb128: Thanks!
[16:13] <GunnarHj> seb128: Hmm... You didn't remove '~ppa' from the version number...
[16:22] <RikMills> oops
[16:26] <seb128> GunnarHj, sorry about that, reuploaded with the ppa
[16:27] <seb128> GunnarHj, the build failing weirdly on s390x, I hope it was only a random error
[16:32] <GunnarHj> seb128: Saw that. And the amd64 build failed! Crossing my fingers.
[16:37] <Laney> tseliot: there is - we're going to want to be doing in-session prompting for this next
[16:37] <Laney> i.e. "your hardware just got enabled, want to install the extra stuff?"
[16:39] <seb128> GunnarHj, new builds worked
[16:41] <GunnarHj> seb128: Great!
[18:30] <tjaalton> yes, it needed the new xkbcomp
[18:31] <tjaalton> x11-utils i mean
[23:41] <kenvandine_> popey: ping from srain
[23:41] <popey> haha
[23:41] <popey> that works then
[23:41] <kenvandine_> it does :)


[13:53] <cpaelzer> doko: I can confirm (from PPA) that the postgresql bugs related to perl will vanish with the stable update that I'm preparing
[13:53] <cpaelzer> so that should be good over the weekend or on monday
[13:53] <doko> nice
[13:54] <cpaelzer> and libvirt >6.8 I already mentioned that I have that ready and will work on it next week (after +1)
[13:54] <doko> cpaelzer: what about libvirt?
[13:54] <cpaelzer> that will unblock the two others
[13:54] <doko> ahh, ok. alternative would be remove that version from -proposed, and build with the old one
[13:55] <cpaelzer> no I'm rather close
[13:55] <cpaelzer> give me that few days to finalize it
[13:55] <doko> ok
[13:55] <cpaelzer> if - when looking into the test results - it looks horrible, then I'll let you know that we should revert and build the odl version
[13:55] <cpaelzer> as an interim solution
[16:08] <zyga> mwhudson: hey, is there a chance to backport a fix in go's IO loop: https://go-review.googlesource.com/c/go/+/232862/
[16:09] <zyga> mwhudson: this bug incorrectly surfaces EINTR in valid go programs
[16:17] <cristiangsp> Hello everybody,
[16:17] <cristiangsp> We want to make you aware that on Friday November 20th and Saturday November 21st there will be a scheduled downtime in our Boston data center to move several compute nodes that form part of the Launchpad build farm.
[16:17] <cristiangsp> During this maintenance window, the Launchpad build farm will not be able to perform builds on the following platforms: arm64, armhf, ppc64el, s390x, powerpc and armel.
[16:17] <cristiangsp> We appreciate your patience and understanding.If you have questions or issues, please submit them at: https://help.launchpad.net/Feedback.
[16:41] <Laney> That affects autopkgtest too FWIW.
[16:41] <juliank> :(
[16:42] <Laney> I know, earlier today I was like "hmm, ok, they should be done by the end of the weekend"
[16:46] <Laney> I wonder if it'll fix the bos01 ppc64el compute instance though, if the cloud gets turned off and on again
[16:46] <Laney> silver lining?
[16:48] <Laney> ah actually, maybe no worries, that's a week tomorrow not tomorrow!
[18:08] <mwhudson> zyga: probably! does it backport cleanly?
[19:09] <seb128> rcj, Odd_Bloke, so I finally got to try the old fashioned script and I think I got it working, thanks again for that! now how do I turn the .ext4 & co into an iso? using ubuntu-cdimage?
[19:15] <rcj> That's a great question seb128 but I don't know for sure.  We trade in qcows and the like.  But someone like xnox or Laney might be able to tell you how they make the ISOs for server or desktop from your output.
[19:19] <seb128> rcj, alright, thanks
[19:19] <seb128> mwhudson, or maybe you know about ^ ?
[19:19] <rcj> is he awake yet?
[19:21] <seb128> he wrote on this channel an hour ago
[19:22] <seb128> and even if he's not, he might read the backlog later :)
[19:33] <xnox> seb128:  i simply checkout ubuntu-cdimage; and checkout debian-cd branch and drive it normally as ubuntu-cdimage does.
[19:34] <seb128> xnox, how does ubuntu-cdimage knows where to find debian-cd ?
[19:34] <xnox> seb128:  and i tweak config to use my own +livefs in launchpad, instead of the production ones.
[19:34] <xnox> seb128:  it finds it in the cwd
[19:34] <xnox> seb128:  readme says, to checkout the debian-cd ubuntu' fork.
[19:34] <seb128> xnox, is that https://code.launchpad.net/~ubuntu-cdimage/debian-cd/ubuntu ?
[19:34] <xnox> i have no idea why they are separate repos, but they are.
[19:35] <xnox> seb128:  sounds right.
[19:36] <seb128> xnox, I'm getting confused
[19:36] <seb128> $ DIST=bionic for-project ubuntu cron.daily-live --live
[19:36] <seb128> is what I try in a debian-cd checkout
[19:36] <seb128> (with the ubuntu-cdimage/bin in the path)
[19:36] <seb128> but it errors with
[19:36] <seb128> cdimage.livefs.LiveBuildsFailed: No live filesystem builds succeeded.
[19:39] <seb128> after export CDIMAGE_ROOT to the ubuntu-cdimage checkout I get
[19:39] <seb128> cdimage.livefs.UnknownArchitecture: No live filesystem builder known for amd64
[19:39] <seb128> I wonder how many people had to figure out again those details over the years
[19:42] <seb128> xnox, and re livefs, there is no way to do that locally, you need to hit launchpad?
[19:47] <xnox> seb128:  not in debian-cd checkout
[19:48] <xnox> seb128:  one dir above it.
[19:48] <xnox> ubuntu-cdimage/debian-cd/
[19:48] <xnox> you want to be in the ubuntu-cdimage
[19:48] <xnox> with debian-cd available, as ./debian-cd
[19:48] <xnox> normally
[19:48] <seb128> k, well I get
[19:48] <seb128> cdimage.livefs.UnknownArchitecture: No live filesystem builder known for amd64
[19:48] <xnox> that sounds like lack of permissions
[19:49] <xnox> are you in ~ubuntu-cdimage?
[19:49] <seb128> yes
[19:49] <xnox> cause in etc/livefs-launchpad, i normally do twek to use my own xnox/any name of livefs
[19:49] <xnox> ok
[19:50] <xnox> path = os.path.join(config.root, "production", "livefs-builders")
[19:50] <xnox> i never have CDIMAGE_ROOT exported.....
[19:50] <seb128> do you add ubuntu-cdimage/bin to PATH?
[19:50] <xnox> just the bin added to path, and then i'm just in ubuntu-cdimage/ folder
[19:51] <xnox> yes, add ubuntu-cdimage/bin to PATH, and be in ubuntu-cdimage
[19:51] <seb128> I should maybe edit etc/livefs-launchpad ?
[19:52] <xnox> one sec, yeah, you ended up in the "ssh into builder" codepath (back in the day when we did not use launchpad as livefs builders)
[19:52] <xnox>         if lp_livefs is not None:
[19:52] <xnox> if lp_livefs is not None
[19:52] <seb128> also how does it know where to find the artifact if those are local?
[19:52] <xnox> yeap, your livefs got empty
[19:53] <seb128> $ ls ~/build.output/
[19:53] <seb128> binary.log  livecd.ubuntu.ext4            livecd.ubuntu.kernel-generic  livecd.ubuntu.manifest-minimal-remove  log
[19:53] <seb128> etc         livecd.ubuntu.initrd-generic  livecd.ubuntu.manifest        livecd.ubuntu.manifest-remove
[19:53] <seb128> it should use those right?
[19:53] <xnox> seb128: no.
[19:53] <xnox> seb128:  ubuntu-cdimage by default looks up livefs (the build it triggered, or the last one) and download things, and puts it into scratch dir, to invoke debian-cd against.
[19:54] <xnox> you can patch the download code, to just copy things from stuff you built locally.
[19:54] <xnox> or sometimes i just comment out downloading, after one download and hack things myself byhand.
[19:54] <seb128> sounds like that should be an option rather than individuals redoing that patching :)
[19:54] <xnox> seb128:  also i don't use old-fashioned, i simply use livefs builder in launchapd
[19:54] <seb128> doing local sounds better rather than wasting infra resources
[19:55] <xnox> seb128:  well, if my teams upload would not be reverted we might have more time to work on cdimage ;-)
[19:55] <seb128> do you remember offhand where the download code you patch is?
[19:55] <seb128> xnox, punt :p
[19:55] <xnox> seb128:  yeah, i should have it as the bzr shelve, one sec.
[19:55] <xnox> and then i run the build without  the '--live' option
[19:56] <xnox> download_live_filesystems and download_live_items
[19:56] <xnox> are the ones i stub out.
[19:56] <xnox> seb128:  but it would be nice, to fix ubuntu-cdimage local instance not able to talk to launchpad.
[19:57] <xnox> seb128:  cause i guess you might want to have one end-to-end run, with everything stock.
[19:57] <xnox> cause then there are logs & scratch dir with all the state, which then one can inspect and just run parts of it.
[19:59] <xnox> seb128:  path = os.path.join(config.root, "etc", "livefs-launchpad") -> this must exists and does exists, if one is in the ubuntu-cdimage checkout.
[19:59] <xnox> seb128:  and if your config.root is off, then lots of stuff will not work.
[20:00] <xnox> seb128:  if you cd into your checkout of "ubuntu-cdimage" (i.e. ~/canonical/ubuntu-cdimage) and then run  DIST=bionic for-project ubuntu cron.daily-live
[20:01] <xnox> does it work?
[20:01] <xnox> it should download all the things, and just work.
[20:01] <seb128> Exception: RSYNC_SRC not configured!  Edit /home/ubuntu/ubuntu-cdimage/production/anonftpsync or /home/ubuntu/ubuntu-cdimage/etc/anonftpsync and try again.
[20:09] <xnox> seb128:  horay, that's good!
[20:09] <xnox> seb128:  adjust etc/anonftpsync to taste, or make change to skip mirroring stuff.
[20:10] <seb128> xnox, can you maybe share you download functions diff?
[20:10] <xnox> seb128:  i have CDIMAGE_NOSYNC=1 =>
[20:10] <seb128> easier than redo that part
[20:10] <seb128> FileNotFoundError: [Errno 2] No such file or directory: '/home/ubuntu/ubuntu-cdimage/ftp/dists/bionic/main/debian-installer/binary-amd64/Packages.gz'
[20:10] <xnox> seb128:  i've looked for it, and i don't have it.
[20:11] <xnox> seb128:  without a mirror, locally, one cannot make an iso. because it needs to download things. and there is no way to rsync unsplit mirror locally.
[20:11] <xnox> seb128:  so i rsync the dists/ on people.canonical.com
[20:11] <xnox> seb128:  and then rsync it locally; and update whenever i want newer bootloaders.
[20:11] <xnox> seb128:  lately i had to build new images, with changes in livecd-rootfs => meaning full rebuilds.
[20:12] <xnox> seb128:  but yeah ftp/disksts/$suites for the suites you want to build for are needed
[20:12] <xnox> seb128:  and partial pools.
[20:12] <seb128> bah
[20:12] <xnox> seb128:  i dream to rework cdimage to work off networked mirror with apt-get download
[20:12] <xnox> seb128:  because one can totally add all the repos for all the arches locally. without this mirror bullshit.
[20:12] <seb128> I don't undestand why I need all this
[20:12] <seb128> old fashioned gave me the ext4 manifest etc
[20:13] <seb128> it sounds like building an ISO from those artifacts shouldn't that much overhead :/
[20:13] <xnox> seb128:  to assemble the iso these things are ndeed https://paste.ubuntu.com/p/CpGHgDgTMV/
[20:13] <xnox> seb128:  the iso consists of: squashfs, bios/uefi bootloader, pakcages pool of files with offline optional debs needed for install.
[20:14] <xnox> seb128:  that's for recent series
[20:14] <xnox> seb128:  for bionic it needs access to the bionic's isolinux ubuntu theme grub etc. to unpack them, put them in the scratch dir and pass them to the xorriso command when assembling the iso
[20:14] <xnox> seb128:  and the pool on the production iso must be signed with the cdimage key....
[20:15] <seb128> I'm not interested in bionic, I just though it would give me a stable basis
[20:15] <xnox> seb128:  hence launchpad/livecd-rootfs cannot spit out ready made iso, because it will not sign things on it.
[20:15] <xnox> seb128:  which series you care aobut then?
[20:15] <seb128> xnox, so basically going down the path we were discussing, I need to  create a mirror in ftp/dists?
[20:15] <xnox> seb128:  because every series supports different targets and behaves differently and is assembled differently, and needs differt amount of partial pool.
[20:15] <xnox> seb128:  yes, you need ftp/dists for the suites you  want to build for.
[20:16] <seb128> xnox, hirsute, my goal is to fix the canary build to use it as a basis for the subiquity desktop project
[20:16] <xnox> for the arches you want to build ofr.
[20:16] <seb128> you don't have a command to rsync or create that pool? ;)
[20:16] <seb128> I'm still amazed that no-one properly documented those
[20:17] <xnox> most cdimage people.... simply ssh into old minster, and run builds from there.
[20:17] <seb128> there is probably a bunch of us that went through the exercice to get this somehow working
[20:17] <seb128> each having their own tricks
[20:17] <xnox> i am one of the few who don't have that ssh access, hence have lcoal deployemnt; and i bootstrap julinak to it too
[20:17] <xnox> seb128:  sync
[20:17] <xnox> $ cat bin/sync
[20:17] <xnox> #!/bin/sh
[20:17] <xnox> set -x
[20:17] <xnox> MIRROR=/home/xnox/mirror/ubuntu
[20:17] <xnox> DEVEL=groovy
[20:17] <xnox> rsync -av --exclude dapper\* --exclude edgy\* --exclude feisty\* --exclude gutsy\* --exclude hardy\* --exclude intrepid\* --exclude jaunty\* --exclude karmic\* --exclude lucid\* --exclude maverick\* --exclude natty\* --exclude oneiric\* --exclude quantal\* --exclude raring\* --exclude saucy\* --exclude utopic\* --exclude wily\* --exclude yakkety\* --exclude zesty\* --exclude artful\* --exclude bionic\*
[20:17] <xnox> --exclude disco\* --exclude cosmic\* --exclude eoan\* --exclude precise\* --exclude xenial\* --exclude trusty\* --exclude vivid\* --include Packages\* --include Sources\* --include Release\* --include InRelease\* --include udeb.list --include \*\*/installer-\*/current --include "**/$DEVEL/Contents-*" --include "**/focal*/Contents-*" --include \*/ --include i18n/\* --exclude \* --delete --delete-excluded
[20:17] <xnox> --prune-empty-dirs ftpmaster.internal::ubuntu-dists/ "$MIRROR/dists/"
[20:17] <xnox> GERMINATE="/home/xnox/mirror/ubuntu-germinate"
[20:18] <xnox> rsync -avz --include germinate.output --exclude _\* --exclude \*.new --include "*_groovy_*" --include "*_focal_*" --exclude \* --delete --delete-excluded ftpmaster.internal::ubuntu-germinate/ "$GERMINATE/"
[20:18] <xnox> that will give you dists..... bah
[20:18] <xnox> https://paste.ubuntu.com/p/MWNb6zrYD3/
[20:18] <seb128> thanks
[20:18] <xnox> seb128:  and then for the pool, i just run the build, see where it fails to fetch, mkdir  -p that dir, and then run like $ pull-lp-debs --arch $arch $pkg => for the right version, or series.
[20:18] <xnox> i guess you will want the latest cd-boot-images-amd64
[20:19] <xnox> it's 9 at the moment.
[20:19] <xnox> and you will need the keyring too
[20:19] <xnox> so pull-lp-debs ubuntu-keyring
[20:20] <seb128> xnox, alright, I'm doing a rsync and will probably come back to that in a while or tomorrow, thanks for the guidance
[20:21] <seb128> xnox, the other option would be to just restore the canary build and try to fix it by upload and watch the result on the official infra :p
[20:21] <xnox> seb128:  yes that would be the quickest way, to just readd it in the etc/crontab
[20:22] <xnox> seb128:  because then for example, i will see the logs too, as they would be publically mirrored.
[20:22] <xnox> and anyone else.
[20:22] <seb128> xnox, well I expect the first thing is going to fix the kernel problem that was discussed back then when didrocks and ji_bel were working on it, I don't think that anyone handled it
[20:22] <xnox> seb128:  especially if the canary image is to become the new subiquity-desktop playground.
[20:23] <seb128> that's the plan
[20:23] <seb128> but I wanted to iterate locally rather than waste infra resources to test things, I though it would also be quicker to iterate
[20:23] <seb128> I didn't expect it to be so complex to set up
[20:23] <xnox> seb128:  what was the kernel problem? when we redid the bootloader, it didn't work for the canary build? a debian-cd / ubuntu-cdimage build log would be helpful for that.
[20:24] <xnox> seb128:  this one is _easy_ =))))))) wait till you see the CPC or the OEM-images setup =)))))))))))))))))))
[20:24] <xnox> (the publishers there, were forked ubuntu-cdimage when it was shell with added ceph buckets and jenkins)
[20:25] <seb128> lol
[20:25] <seb128> xnox, what you wrote back then was 'We should make kernel/linux install be done in the is_live_layer only. Including regenerating the initrd as done in hacks, and rip it out.'
[20:30] <xnox> seb128:  oooooh.
[20:31] <xnox> seb128:  but that's in livecd-rootfs and live-build, not in ubuntu-cdimage/debian-cd levels.
[20:33] <seb128> xnox, right, well I'm trying to build up my way from bottom to top
[20:34] <seb128> I though old fashioned would drive livecd-rootfs for me
[20:34] <seb128> which is where I started
[20:34] <seb128> well; I think that's still true
[20:34] <seb128> if I replace the download code and use those artifacts
[20:35] <xnox> yes that would drive livecd-rootfs & live-build, but not ubuntu-cdimage/debian-cd.
[20:35] <seb128> I can use old fashioned to build with the livecd-rootfs changes
[20:35] <seb128> and then I need the up stack to end up to the ISO
[20:35] <xnox> imho having a personal xnox/ubuntu +livefs build, in etc/launchpad-livefs is easier than old-fashioned.
[20:35] <xnox> with upload of livecd-rootfs / live-build to a ppa
[20:35] <xnox> and launchpad the builds in that ppa
[20:35] <xnox> thus iterating out of archive.
[20:35] <seb128> I don't know how to do that either
[20:35] <seb128> so much knowledge missing there :)
[20:36] <xnox> seb128:  yes, we have teams that only do that. i.e. cpc & oem.
[20:36] <seb128> they should fix the canary image for us :p
[20:36] <xnox> seb128:  which salesforce contract is it for? they have minimum revenue before they can be invoked =)
[20:37] <xnox> seb128:  do you have pull-lp-source of live-build?
[20:37] <xnox> seb128:  i don't know how layers work, but i think the ./scripts/build/lb_chroot_linux-image needs to be come layer aware
[20:38] <xnox> and do nothing if the layered build is run and the layer is not the live-layer;
[20:39] <seb128> xnox, I will check later or tomorrow but I need to go for now, thanks again for the help and have a nice evening!
[20:39] <xnox> seb128:  and separately we need to get UPDATE_INITRAMFS_OPTIONS="CASPER_GENERATE_UUID=1" into there too.
[20:39] <xnox> i.e. if live-layer also rerun CASPER_GENERATE_UUID=1 update-initramfs -u
[20:39] <seb128> k
[20:40] <xnox> because ./scripts/build/lb_chroot_hacks is not run at all, i think, or something like that.
[20:40] <xnox> seb128:  so we had a headcount cancelled multiple times / postponed / fail to hire, to complete ubuntu-image => which is a snap, and just builds everything in one go.
[20:40] <xnox> seb128:  it was meant to be able to do all classic images, reproducibly. but alas, still not here.
[20:41] <xnox> aka replacement for debian-cd and the image building.
[20:41] <seb128> right
[20:41] <seb128> I with I had an IRC proxy but I don't, need to drop now sorry
[20:42] <seb128> xnox, thanks again for the help and the advices! enjoy your evening
[21:46] <cjwatson> 16:49 <sil2100> openssh has two regressions, libssh and sshuttle - is anyone looking at it?
[21:46] <cjwatson> bdmurray: ^ FWIW I just got libssh fixed in Debian today
[21:47] <cjwatson> will need a merge
[21:48] <cjwatson> sshuttle looks plausibly transient - retrying
[21:49] <bdmurray> cjwatson: I'd already retried sshuttle
[21:49] <bdmurray> cjwatson: I also found debian bug 974039
[21:52] <cjwatson> ah, I thought I'd checked sshuttle's history but maybe I failed
[21:52] <bdmurray> It's likely still in the queue
[21:52] <cjwatson> ack
[21:53] <bdmurray> Oh nope, its running right now
[22:18] <GunnarHj> bdmurray: Do you have an idea what's going on re bug #1903574? The Debian maintainer would appreciate a helping hand.
[22:18] <bdmurray> GunnarHj: I haven't looked at it other than trying to get it to retrace
[22:19] <bdmurray> GunnarHj: sorry for the noise!
[22:19] <GunnarHj> bdmurray: Ok, n.p.


[11:23] <penguin42> hmm never seen that before on a Hermes tracking 'Problem resolved and parcel is in transit'
[11:23] <penguin42> curiously only on Amazon's view of Hermes tracking
[11:48] <zxmpi> have a package stuck in some depot since start of september
[12:01] <penguin42> haha
[12:15] <zxmpi> that's 3 euro i'll have to claim back :-)
[15:49] <Nokaji> I'm in the process of building a dual boot pc ... it used to be iirc that you had to install windows first, then ubuntu ... is it true you can now install ubuntu first and it will auto set up for dual boot when selected during install process?
[15:52] <daftykins> i'd probably choose to independantly install on separate physical drives, then use the firmware hotkey at boot to pick which i'm running at a given time


[07:44] <tristanbob> I thought I would join this team since I have some ideas related to marketing Ubuntu :)
[07:47] <jenda> tristanbob: welcome to the team, then :)
[07:47] <tristanbob> thanks jenda !
[08:59] <tristanbob> I just plugged this team on the planet :)
[09:04] <jenda> :)


[11:29] <BluesKaj> Howdy folks
[15:42] <magic_ninja_work> seems I found a bluetooth bug
 Please share the link to the bug report.  I will see if I can duplicate here.
 Beta Live Session and Install worked great on an old Dell laptop.  Other than the 3rd party driver checkbox, I did not see an option for installing graphics drivers during install-did I miss it or just not enabled?  Regardless manual install of NVidia driver worked well (sometimes it's a fight on this old hw).
 I tried to add comments to the Beta tracker, but comments are disabled-is this due to a beta respin?
 The Beta is out, so testing moves on
 Nvidia did not install with 3rd party?
 Correct, NVidia driver did not auto install.  It's legacy 8600M-get Nvidia HW so not sure if older hw is the issue.
 s/get/gt
 @DarinMiller, 340?
 yes, nvidia-340 driver
 That is not on the iso
 ah, makes sense!
 How did you determine what drivers were on the iso?
 we have 390, 430 and 435
 @DarinMiller, The same wildcard that Ubuntu used
 @DarinMiller https://bazaar.launchpad.net/~kubuntu-dev/ubuntu-seeds/kubuntu.eoan/view/head:/ship-live#L18
 I gues doesn't match 340, as they come from before Ubuntu changed how the driver meta package was named
 exactly
 In fact, I blindly attempted to install nvidia-driver-340 which obviously failed...then I had to to find the correct package name from the apt list.
 ISOs are already huge. I am scared to add another nvidia, as it adds about 100MB 😱
 I don't think adding to the iso is necessary.  However, we should advertise legacy driver are not included to properly set expectations.
 Yeah, we need to add info about the nvidia driver on release notes anyway, so we can explain there
[17:23] <santa_> good afternoon everyone
[17:23] <santa_> @RikMills, I have been thinking a bit about the branch checking in KA
 good afternoon santa :)
[17:24] <santa_> after some pondering my conclusions is that it may be a good idea to remove it completely
[17:24] <santa_> so what do you think?
[17:25] <santa_> my original idea was to just keep it for gbp-newrelease and gbp-archive, but even in those commands it could be annoying
[17:25] <santa_> for instance, wrt gbp-nr, see your plasma-5.17 branches
[17:26] <santa_> with branch checking that would fail, so I have the impression it would be better to just let the KA user do whatever
[17:28] <santa_> another alternative would be just printing a non-fatal, orange colored warning (instead of just removing the functionality)
[17:29] <santa_> but I think I'm more in favour of removing
 sounds reasonable
[17:38] <santa_> ok, I will work on the removal
[17:39] <santa_> I also plan to remove the "-u" option from uploadsource, which is annoying in a similar way than branch checking. also to see if they are uncommited changes in a git local clone we have now "check-changes"
[17:40] <santa_> so no point to check that in uploadsource
 Yeah that is annoying 😋
[17:41] <santa_> indeed it isn't as great as I pictured it in my mind some time ago XD


[11:53] <dupondje> My Xorg crashes regulary with the following message: "Xorg crashed with SIGABRT in __libc_message()"
[11:54] <dupondje> but can't seem to find an existing bugreport on it? While I did report it with apport
[11:54] <dupondje> but it seems like apport sends to whoopsie?
[12:06] <dupondje> seems to be in /usr/lib/xorg/modules/drivers/intel_drv.so
[12:06] <dupondje> but no debug symbols installed
[12:06] <dupondje> ahhh :(
[14:23] <tjaalton> oh
[14:23] <tjaalton> huh? wrong channel


[07:18] <DanChapman> elijh, are you running ubuntu-gnome?
[07:19]  * DanChapman should really look at the playback timestamps first
[08:43] <elijh> nope, running Unity
[09:29] <DanChapman> elijh, I have no idea then, sorry. When i tried using QtCreator on ubuntu gnome i had to remove appmenu-qt5 to make it visible. I run Unity normally and havn't seen that. Might be worth filing a bug for it
[09:39] <bzoltan> renato___: Here is an important MR for the address-book what we need for the new UITK -> https://code.launchpad.net/~elopio/address-book-app/autopilot-get_header_from_toolkit/+merge/225729
[09:40] <bzoltan> popey: Do you think it would be OK to include this MR to the UITK landing -> https://code.launchpad.net/~elopio/ubuntu-clock-app/prepare_for_page11/+merge/225728
[09:51] <elijh> DanChapman: removing appmenu-qt5 did the trick! Thanks. I have no idea why it was installed, nothing was depending on it.
[10:43] <popey> bzoltan: how is that related to uitk?
[10:43] <popey> bzoltan: nik90_ is probably a good person to ask anyway
[10:44] <bzoltan> popey: https://code.launchpad.net/~bzoltan/ubuntu-ui-toolkit/landing_0307/+merge/225476 Look for elopio's comment
[10:45] <bzoltan> popey:  long story short ... I do not want to release a UITK what makes the autopilot tests fail for any app.
[10:47] <popey> ok, sounds good
[10:47] <popey> when will this land in the image?
[10:52] <rpadovani> mzanetti, o/ I upgraded to Utopic, and it uses production server. So I deleted my accounts and create a new one on production server. Then I added it to online account, but reminders doesn't do the login
[10:52] <rpadovani> What's wrong?
[10:52] <rpadovani> EDAMSystemException Default TException.
[10:52] <rpadovani> Error fetching username: "Default TException."
[10:53] <mzanetti> rpadovani: hmm... not sure
[10:53] <mzanetti> is the app up to date?
[10:54] <mzanetti> ah, you're on the desktop...
[10:54] <mzanetti> hmm... let me have a look at the code
[10:55] <rpadovani> mhh, I'm behind of 6 version from the trunk, I try a merge
[10:55] <mzanetti> ah ok
[10:55] <mzanetti> that would explain things
[10:57] <rpadovani> mzanetti, yap, now works, sorry for the stupid ping :D
[10:57] <mzanetti> no problem :) glad it works
[11:03] <nik90_> bzoltan: so you need https://code.launchpad.net/~elopio/ubuntu-clock-app/prepare_for_page11/+merge/225728 to be merged first?
[11:06] <nik90_> elopio: ping
[12:55] <bzoltan> nik90_: yes
[13:44] <renato___> bzoltan, this function already exists on the current UITK or this will land with the new release?
[14:20] <qtros> Hi all
[14:21] <qtros> Is someone from SDK team here?
[16:37] <bzoltan> nik90_: so if you approve that MR I can include it to the UITK landing right away
[16:53] <nik90_> bzoltan: yeah I approved it
[17:07] <renato___> popey, are you around?
[17:13] <renato___> any calculator developer around?
[17:15] <daker> rpadovani: ^
[17:15] <rpadovani> renato___, o/
[17:15] <rpadovani> thanks daker :-)
[17:16] <renato___> rpadovani, hey, My calculator is doing wrong math for more than a week :D, Did you fix this bug already?
[17:16] <rpadovani> renato___, yes, let me check if the MR is landed
[17:17] <renato___> I am using the developer image
[17:17] <rpadovani> renato___, it only needs a top approve: https://code.launchpad.net/~rpadovani/ubuntu-calculator-app/1332567/+merge/225225
[17:17] <renato___> let me see if I can top approve it
[17:20] <renato___> rpadovani, yeah I can not top approval it. popey  could you do that
[17:21] <renato___> this is very critical :D
[17:21] <rpadovani> yap, and it's very weird
[18:13] <nik90_> popey, bzoltan: Do you happen to know the package required to get the ubuntu touch ringtones installed on the trusty desktop? I cannot remember the name of it since I added it a long time ago.
[18:57] <bzoltan> nik90_: I do not know
[20:20] <popey> nik90_: on the phone do "dpkg -S /path/to/audio/file"
[20:21] <popey> nik90_: it'll tell you the package name, or use packages.ubuntu.com
[21:43] <dibs> Hey all, just started looking at the SDK today and am building an html5 app. Can I call commands like in a bash script with this kind of app?
[21:45] <daker> dibs: no, this is not possible
[22:57] <nik90_> popey: sweet! That worked nicely


[03:40] <fling> xnox: thanks
[03:40]  * fling just lost the url
[06:48] <fling> ok so how to filter shiftfs related commits?
[06:48] <fling> the ones touching shiftfs.c are not enough
[06:48] <fling> there is something elso
[06:48] <fling> eg for shiftfs_setattr to work
[08:42] <fling> Is not there newer 5.14 than 5.14.3?
[11:32] <xnox> fling:  there might be in -next and -prep we were frozen a bit for the release. We are now actively working on v5.15 in linux-unstable
[11:32] <xnox> fling:  the 5.14 development continues in focal as oem-5.14 only
[11:32] <xnox> (no idea how long lived it will be)
[11:33] <xnox> i think we are actively skipping 5.14 and going from v5.13 to v5.15


[22:40] <thumper> mwhudson: could I get you to put an official reviewer stamp on https://code.edge.launchpad.net/~thumper/launchpad/claim-review-into-model/+merge/15524?
[22:40] <thumper> mwhudson: last revision has just been pushed, diff should be updated shortly
[22:40] <mwhudson> thumper: looking
[22:41] <thumper> mwhudson: diff is updated
[22:45] <mwhudson> man, a slider to increase context on the diff would sure be nice...
[22:45] <thumper> mwhudson: heh
[22:46] <thumper> that would be awesome wouldn't it
[22:46] <thumper> the guts of it is to use .first() instead of .one()
[22:46] <thumper> we still try to control that there should only be one
[22:46] <thumper> but don't die horribly if there isn't
[22:55] <mwhudson> thumper: done
[22:57] <thumper> mwhudson: ta
[23:03] <mwhudson> thumper: can you approve https://code.edge.launchpad.net/~mwhudson/launchpad/code-import-paranoia/+merge/15467 ?
[23:05] <thumper> mwhudson: done
[23:09] <mwhudson> thumper: ta
[23:40] <thumper> https://code.edge.launchpad.net/~thumper/launchpad/claim-review-into-model-attempt2/+merge/15718
[23:43] <thumper> and
[23:43] <thumper> https://code.edge.launchpad.net/~thumper/launchpad/claim-review-into-model-browser-integration/+merge/15719


[01:40] <em> AlanBell: We should now also add #ubuntu-women to the list of places I would like explanations for :)
[01:40] <em> You know when Ubuntu claims to be an open community that embraces diversity and freedom of information is there any actual truth to that?
[01:41] <IdleOne> Don't bother, #ubuntu-women doesn't have the same rules as the core ubuntu channels.
[01:41] <em> Or is a person only safe so long as they, for example, agree with IdleOne?
[01:41] <IdleOne> You were making the channel an unsafe and unwelcome environment. I banned you.
[01:41] <em> Im sure we do have different philosophical views but do you actually claim to be more civilised, rational or worthy than me?
[01:42] <IdleOne> I'm done explaining.
[01:42] <em> That's pretty rich, "Unsafe"
[01:42] <em> That is a remarkable comment to make about a person who was typing fully articulated and defensible sentences into a channel that claims to be interested in making sure everyone is included.
[01:43] <em> It is a regrettable thing that free-thinking makes #ubuntu-women unsafe, and yet here it is immortalised in the #ubuntu-ops log for all to see.
[01:43] <em> Let's for the time being forget about #ubuntu-women. That will be easy.
[01:44] <em> AlanBell: Is there any chance that the bans in either of the other two could be lifted since there is no apparent reason for them and they are ancient?
[01:44] <IdleOne> Not today.
[01:44] <em> IdleOne: And what is the reson for that?
[01:45] <IdleOne> Your past history.
[01:45] <em> IdleOne: Past history of what?
[01:45] <IdleOne> You know where the logs are located.
[01:45] <em> IdleOne: Bring it forth. Past history of what?
[01:46] <em> IdleOne: Are my relevant questions making you feel "unsafe"?
[01:46] <IdleOne> I think it is best if you email the IRCC (/msg ubottu !appeals) and let them answer any questions you may have.
[01:47] <em> Someone should perhaps message them and encourage them to look at this entire operation. What are you doing here?
[01:47] <em> That is not just a philosophical question.
[01:47] <em> You are a volunteer, and good for you, thanks for that. What did you volunteer to do?
[01:48] <em> Did you volunteer only to ban people? Does this channel we are in right now exist for any reason?
[01:48] <IdleOne> I volunteered to help maintain a safe and welcoming irc experience for all users. Sometimes those users don't understand the ubuntu community guidelines and we are forced to ban them.
[01:48] <em> I suppose these questions are becoming too rhetorical. I'll tone it down.
[01:49] <em> Then articulate how I have violated the "Ubuntu community values" in #ubuntu
[01:49] <em> Anything you have to contribute to that would be a wonderful surprise.
[01:50] <Flannel> em: I don't think any operator, given the history and discussions today and on the day AlanBell linked to a few hours ago, is going to unban you today, or probably any day.  I think your best recourse is to have a conversation with the IRCC.  They'll be able to look at all of the aspects involved and get an answer to you.
[01:51] <Flannel> Not to say that you're not unbannable, merely that it would require a good deal of homework, and discussions with various parties, and these things don't happen over the course of an hour.
[01:51] <em> Flannel: Could you invite them to come on to IRC, that would be a lot easier.
[01:52] <Flannel> em: I think some of them are here, but your best bet is to follow the official channels and not try to invent your own process.  I believe that is still an email to their mailing list as an initiation, and I believe they can/may invite you to discuss things on IRC if anything needs to be worked out interactively.
[01:53] <em> Flannel: I claim there is absolutely no reason for me to be banned in #ubuntu [full stop]. The non-reasons I was banned in #ubuntu-offtopic are ancient and irrelevant. So irrelevant that I was not even banned and no one seemed to mind I was there until two days ago when it was placed again in closed-source fashion.
[01:53] <Flannel> I just checked, and yes, it does appear that an email to their mailing list (let me know if you need the address) is the first step.
[01:53] <em> Flannel: Finally I claim that the single reason I was banned in #ubuntu-women is because I have an independent mind and IdleOne finds that dangerous.
[01:54] <IdleOne> even if that were true, team channels are free to govern their channel as they see fit.
[01:54] <Flannel> First, the easy stuff: #ubuntu-women isn't covered by this channel, if you have an issue there, take it up with #ubuntu-irc.
[01:55] <em> Flannel: Then what you are saying is that any person who was mistakenly given the privilege of being an op can ban me in #ubuntu for no reason and the only way that can be resolved is to force me to go through time consuming lengths and a lengthy process to have it possibly resolved.
[01:55] <em> Flannel: Then I think it is clear for all to see that your processes are broken.
[01:55] <Flannel> Now, if you feel you're not happy with the resolution there, I believe you should still appeal to the IRCC.  Because they still have purview.
[01:55] <Flannel> em: Slow down there slugger.  I haven't even responded regarding #ubuntu.
[01:56] <em> Flannel: I will only contact the IRCC if there is the possibility that not only will I have the ban lifted but I will also receive a direct apology from the Ubuntu Community for insulting me and wasting my time.o
[01:56] <em> Flannel: When is the next meeting of the IRCC here on IRC. I will attend it if possible.
[01:56] <Flannel> Alright, do you want me to respond to everything you say? or just the most recent thing? since you're typing so much that I find it difficult to think you're interested in having a conversation.
[01:56] <em> Flannel: Sorry for that, go ahead. I'm listening.
[01:57] <Flannel> I think I'm like eight statements back/
[01:58] <Flannel> Alright, about you being banned in #ubuntu, I acknowledge that you believe you shouldn't be banned there.  I'm not sure that simply stating that is going to further your cause for becoming unbanned, however.
[01:59] <em> Correct.
[02:00] <Flannel> em: I'm saying that any person who was given the responsibility of being an operator has the power to behave like an operator in any channel they are an operator of (that's only a shred above a tautology).  When people become operators, they are observed closely for a period of time, and beyond that there's still course corrections that take place.  The person banning you need not be the one who unbans you either.
[02:00] <Flannel> This, along with other things, prevents a single person's opinion from blacklisting someone.
[02:01] <em> Sounds good. For some reason it is failing in practice.
[02:01] <Flannel> In your particular case, there are a number of people who have been involved, so I don't think focusing on a single person "mistakenly" being made an operator is relevant, nor constructive.
[02:02] <Flannel> em: Well, that's the operator level, your next step is to appeal to the IRCC when you feel the operators are in error, which is entirely possible, as we're all human.
[02:02] <Flannel> From what I understand, you haven't yet attempted to do so, so I can only conjecture wildly at this point.
[02:03] <Flannel> em: I think the IRCC has the ability, if they see fit, of issuing you an apology.  It won't be from the "Ubuntu community", as the IRCC is not the entire community.
[02:03] <em> Flannel: Well I give you credit for being lucid and rational. If you could be cloned to replace a few of the trolls who are allowed to idle here in #ubuntu-ops everything would be right with the world.
[02:04] <Flannel> But again, I am not the IRCC, so I can't speak for them.
[02:05] <em> IRCC stands for the IRC Community Council? Or something else?
[02:05] <Flannel> IRC Council. https://wiki.ubuntu.com/IRC/IrcCouncil
[02:05] <em> Okay thanks.
[02:06] <em> This is a pretty slick system you guys have. It is a lot like Best Buy giving me a rebate that they know I'm unlikely to bother with.
[02:07] <Flannel> em: It's not quite a system.  It's "discuss it with operators in -ops" then "email the IRCC".
[02:07] <em> Alright.
[02:07] <Flannel> em: I do see that apparently you can go talk to them in #ubuntu-irc-council instead of emailing.
[02:08] <em> Ahh. That would be a lot better.
[02:08] <Flannel> I'm not sure which would be more expedient.
[02:08] <em> Okay thanks.
[02:09] <Flannel> em: Even with IRC, I imagine they will have to discuss it with the entire body (as that's the point of a council).  So either way, don't expect a turnaround of a couple of hours.  This is things-via-the-internet, people don't always check email, etc.  You know the drill.
[02:09] <em> I'll be parting as soon as you indicate that you had a chance to say everything you wanted to tell me.
[02:09] <Flannel> I'm good.
[02:09] <Flannel> If there's nothing else on your end, I bid you good day and wish you a speedy resolution.
[02:10] <em> Sure, thanks for your feedback and information. Take care.
[02:17] <IdleOne> That is not spam is it?
[02:18] <IdleOne> because it sure looks like a troll spamming
[02:24] <Flannel> where?
[02:32] <IdleOne> I guess you don't see part messages
[02:34] <IdleOne> I should probably look before jumping in the pool
[02:34] <Flannel> I did.  I have no idea how that would be spam.  That's her standard part message, at that.
[02:38] <IdleOne> I wasn't aware she had been interviewed. I honestly thought it was just some fake ubuntu interview.
[03:33] <elky> it's been in her part message since it happened i think
[03:35] <IdleOne> I never noticed it before
[03:36] <elky> i especially like q3
[03:40] <elky> anyway, considering the whole interview was a contrived publicity stunt to advertise a channel which shuns the primary tenet of the community... it is somewhat spammerific.
[07:15] <Tm_T> how amusing
[07:17]  * gnomefreak wants to laugh :) its beocme a crappy month already
[07:18] <gnomefreak> its :18 and im decindin gif i want coffee. (2:18am
[07:18] <gnomefreak> )
[07:19] <gnomefreak> ok that copmment sucks
[07:19] <Flannel> gnomefreak: Irish Coffee?
[07:19] <gnomefreak> Flannel: nope
[07:20] <gnomefreak> didnt even knew there was an irish coffee
[07:20] <gnomefreak> yu would think i would have learned that in the 36 years ive been here
[07:21] <Tm_T> hmmm, so em was or was not going to contact IRCC?
[07:21] <Tm_T> I didn't really get what was the outcome
[07:21] <elky> gnomefreak, try having coffee before trying to work the keyboard again :P
[07:21] <Flannel> Tm_T: I'm not sure.  She knows that's the next step.
[07:24] <gnomefreak> :) should really do that
[07:24] <Tm_T> Flannel: I know she knows
[07:26] <IdleOne> There's no audience on the mailing list
[08:43] <usr13> elfer
[08:46] <Myrtti> oh man
[08:46] <Myrtti> I was trying to press backspace
[08:46] <Myrtti> not enter
[08:47] <elky> ?
[08:47] <elky> i looked at the logs, i still don't know
[10:51] <AlanBell> oh dear that didn't go so well with em did it
[10:55] <Tm_T> good rule would be with her "direct to ircc and be done with it" at this point?


[00:02] <mannyv> strycore, it looks like it has been fixed upstream but has not been packaged in debian yet
[00:04] <mannyv> that is a new version upstream so the fix won't make it into karmic. Your best bet, given it is a regression with a simple fix, would be trying to request a SRU i think
[00:04] <mannyv> https://wiki.ubuntu.com/StableReleaseUpdates
[00:04] <mannyv> im kind of new to this though so I might be wrong
[00:04] <strycore> yes this bug is fixed in convertall 0.4.3, I took just one line from it. But I know that were not going to have it before Lucid so it might be nice to patch convertall 0.4.2 so it actually works
[00:05] <strycore> and it's the smallest patch ever !
[00:07] <mannyv> so then get the fix in karmic: https://wiki.ubuntu.com/StableReleaseUpdates =)
[00:15] <strycore> ok i've subscribed the ubuntu-sru team and nominated the fix for karmic, but I'm not a motu, there are things I can't do
[03:57] <pmatulis> what is the equivalent pbuilder/pdebuild command for 'dpkg-buildpackage -sa -S' ?
[04:13] <jmarsden> pmatulis: pdebuild -S -sa  # should work fine, as should    pbuilder --build --debuildopts "-S -sa" foo.dsc
[11:14] <cemc> havp
[14:06] <bddebian> dtchen: Can you hit me up if you come around?
[14:41] <pmatulis> what is the equivalent pbuilder/pdebuild command for 'dpkg-buildpackage -sa -S' ?
[14:43] <bddebian> --debbuildopts -sa
[14:43] <geser> pmatulis: why would you need that? for pbuilder you need to have a .dsc file already
[14:44] <bddebian> I have to use -sa occasionally to ensure the .orig.tar.gz gets included in the .changes file
[14:45] <geser> yes, but you don't use pbuilder to build your source package, do you?
[14:46] <pmatulis> geser: my goal is to have PPA's for any release i choose
[14:47] <pmatulis> geser: and pbuilder provides that in general.  needless to say i'm quite new at this
[14:48] <geser> pbuilder takes your source package and builds the binary debs from it
[14:48] <bddebian> geser: No not usually, good point :)
[14:49] <geser> you don't need a lucid pbuilder to build a source package for lucid (in most cases)
[14:51] <pmatulis> geser: so if my host is jaunty how do i get LP to build karmic PPA's?
[14:51] <geser> you target karmic in your changelog entry
[14:52] <geser> that lets LP know that it should build it for karmic
[14:53] <pmatulis> geser: alright, easier than i thought then
[15:23] <bddebian> dtchen: OK, I just uploaded libsdl 1.2.14 to experimental if you get bored and want to test :)
[15:26] <sebner> heya bddebian  :)
[15:27] <bddebian> Hi sebner
[16:17] <hedkandi> fyi uploads to revu isn't working
[16:18] <hedkandi> it says "wrong password"!
[16:20] <Laney> revu is down
[16:38] <jjlee> i'd like to package this: http://www.pre-emptive.net/doco/w3cvalidator-command-line-html-validator
[16:38] <geser> ScottK: do you know if your changes to some r-cran-* packages are still needed? (Don't build with xvfb on Sparc to work around LP 410711)
[16:38] <ScottK> geser: That should be fixed now.
[16:38] <geser> so sync those packages again?
[16:38] <jjlee> at work we tend to produce native packages, but I know that's frowned upon
[16:38] <ScottK> geser: I have three R packages that should be able to sync now that the new r-base is in.
[16:39] <ScottK> geser: Yes.  If you want to file the syncs, I'm fine with that.
[16:39] <ScottK> (just let me know)
[16:39] <jjlee> I'd like to keep the original source code under version control
[16:39] <geser> I guess the ones I looked at to get some FTBFS of the list
[16:39] <jjlee> what's the best way to do that and comply with debian / ubuntu guidelines?
[16:41] <jjlee> seems like keeping original source under version control might make it awkward to comply with requirement to work from "original tarball"
[16:41] <geser> ScottK: I'll testbuild them and file sync request then
[16:41] <ScottK> geser: Thanks.
[16:41] <ScottK> jjlee: Keep it all in your VCS, but exclude the debian dir when you make the tarball for release.
[16:41] <jjlee> are there tools to generate patches (and even generate "original tarball") from a version control repository?
[16:41] <ScottK> Yes, there are, but it depends a lot on what you use for a VCS.
[16:42] <jjlee> git by preference, but bzr if it integrates better with LP (which I assume it does?)
[16:43] <ScottK> It does, but it really only matters if the project is hosted on LP.
[16:43] <jjlee> ScottK: how do I generate "original tarball" from repo?  does it have to be bit-for-bit the same as the real original tarball?  Does tar include timestamps in archives?
[16:43] <jjlee> I do want to use LP's PPAs
[16:43] <jjlee> don't care especially about the rest of LP's features
[16:44] <ScottK> jjlee: You want to look at pristine-tar as the tarball has to have a consistent md5sum.
[16:44] <jjlee> though I guess it's nice for issue tracking to be in the official place
[16:45] <jjlee> ScottK: thanks -- this binary delta that pristine-tar talks about contains the timestamp (&c.?) stuff extracted from original tarball, presumably?
[16:46] <ScottK> Something like that.  I don't know the details.
[16:46] <jjlee> ScottK: thanks anyway, looks promising!
[16:50] <jjlee> is there other LP stuff I should do other than just uploading my source package to PPA (other than getting it into {multi,uni}verse)?
[16:50] <jjlee> stuff that makes other maintainers / regular users lives easier?
[16:50] <jjlee> like using standard issue tracker?
[17:26] <geser> ScottK: sync requested for r-cran-time{date,series}: bug #489632 and bug #489636
[17:27] <ScottK> Good.  Thanks.
[17:35] <mannyv> i have been working my way down the universe list on M-o-M looking for and filing sync requests. I have not been asking or notifying the previous uploader as I just noticed geser doing. Should I not just go down the list filing syncs (when appropriate)?
[17:39] <geser> mannyv: it's good to at least let the previous uploader know it to avoid double work
[17:42] <mannyv> geser, ok will do. That'll be a chore, iv'e filed about 20 sync requests
[17:43] <ScottK> mannyv: If you look at the top of that page, it's the first thing that's suggested.
[17:47] <mannyv> ScottK, technically it says it before doing a merge. I am not trying to be pedantic but syncs (at least the ones i have been touching) are not much work and so not likely to be sitting in someone work log half done. But I take your point and will ask first
[17:48] <ScottK> mannyv: The other thing is that it isn't rare for the previous uploader to know something relevant about the package and if it can be synced, for example, I knew it was now OK to sync the packages that geser asked about due to following the bug I uploaded a workaround for and knowing that r-base had recently been synced.  It'd have been a lot tougher for someone who hadn't been following the packages to know.
[17:52] <mannyv> ScottK, ive been skipping over the packages with more complicated. I have focused on obvious easy changes like changing a Depends or renaming getline to get_line
[17:52] <ScottK> That's good, but still please ask.
[17:54] <mannyv> i will
[18:27] <jjlee> anybody know how to explicitly specify gpg key to use when signing a file?
[18:27] <hyperair> jjlee: -k
[18:28] <jjlee> hyperair: man gpg says that's the same as --list-public-keys
[18:29] <ScottK> jjlee: hyperair is correct.
[18:29] <hyperair> jjlee: sorry, i was talking about debsign. were you talking about something else?
[18:29]  * ScottK was too
[18:30] <jjlee> hyperair: sorry, I was referring to gpg itself
[18:31] <hyperair> jjlee: look for default-key in the manpage
[18:31] <pochu> jjlee: see --sign in the manpage
[18:31] <jjlee> hyperair: thanks, that led me to --local-user
[18:32] <hyperair> ah
[19:10] <Laney> yay
[19:48] <jjlee> is this a suitable name & version for my ppa package (from release 1.0.1 of http://www.pre-emptive.net/doco/w3cvalidator-command-line-html-validator)? w3c-markup-validator-commandline_1.0.1ubuntu1~ppa1
[19:48] <directhex> jjlee, that's still a native package version
[19:50] <jjlee> ah, thanks.  So 1.0.1-1ubuntu1~ppa1?  Do I need the ubuntu1?
[19:51] <directhex> 1.0.1-1ubuntu1~ppa1 means:
[19:51] <directhex> upstream version 1.0.1
[19:51] <directhex> debian version 1
[19:51] <directhex> ubuntu modification 1 of debian version
[19:51] <jjlee> So 1.0.1-1~ppa1 I guess
[19:52] <directhex> ppa package 1 based upon the above, but versioned to be "lower" than the non-ppa version
[19:52] <directhex> (should one exist)
[19:52] <jjlee> right, I want it to be lower
[19:52] <jjlee> (though none exists yet)
[19:52] <directhex> 1.0.1-0ubuntu1~ppa1
[19:52] <jjlee> it's not a modification of a big-D Debian package
[19:52] <directhex> unless you plan on targeting debian rather than ubuntu with a "real" package
[19:53] <directhex> use 0ubuntu1 for packages not based on debian versions
[19:53] <jjlee> this is a new package
[19:53] <jjlee> So 1.0.1-0ubuntu1~ppa1 ?
[19:53] <lfaraone> jjlee: you're still using 0ubuntu1 if you're going to upload to Ubuntu not Debian.
[19:54] <jjlee> I'm going to upload to ubuntu, not Debian, yes
[19:54] <jjlee> thanks
[20:19] <jjlee> This package has a perl module in it.  Not sure I want to take the obvious debian package name for that w3c-markup-validator-perl.
[20:19] <jjlee> Seems reasonable just to keep it all in a single "binary" package?
[20:19] <jjlee> it's not in CPAN
[20:24] <jjlee> Can anybody suggest an example perl debian package that's midway in the level of debian/rules auto-magic-ness between libwww-perl (only a couple of lines in debian/rules) and libuuid-perl (big ugly makefile)?
[20:30] <RainCT> DktrKranz: thanks for getting ubuntu-dev-tools into Debian :)
[20:31] <nhandler> DktrKranz: So are we going to continue to maintain u-d-t the same way and you will just "sync" it in Debian ?
[20:35] <DktrKranz> RainCT: hehe, np :)
[20:36] <DktrKranz> nhandler: I think it's safe, I only diverge in a dep (which it will be applied in Lucid too, as soon as dependency stack will be synced), and Maintainer (to avoid ML bouncing)
[20:37] <DktrKranz> now that we sync from testing, it's not worthy to wait 10 days
[20:38] <DktrKranz> the only issue I've encountered is some unicode issues in buildd script
[20:39] <RainCT> DktrKranz: btw, have you seen http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543315?
[20:40] <RainCT> looks like they want mk-sbuild-lv in the sbuild package
[20:40] <RainCT> kees: ^
[20:41] <ScottK> Even better.
[20:41] <ScottK> The less we have to maintain, it's good.
[20:43] <DktrKranz> RainCT: I agree some tools should be included in other packages (i.e. devscripts), and leave here only Ubuntu-specific ones
[21:56] <geser> DktrKranz: what unicode issues exist in the buildd script?
[22:13] <mihailikos> hi
[22:13] <mihailikos> im just strart
[22:14] <mihailikos> and i like so much that version of ubuntu
[22:14] <mihailikos> can some one hellp me
[22:15] <mihailikos> i want install ubuntu on my usb
[22:15] <mihailikos> is that keep me eny change i have made on setings
[22:15] <RainCT> mihailikos: #ubuntu is the place for support
[22:15] <RAOF> mihailikos: This is a development channel; your question would be better asked in #ubuntu.
[22:15] <mihailikos> aha
[22:15] <mihailikos> ok
[22:15] <mihailikos> sorry
[22:49] <jjlee> should the .changes file I upload to launchpad end in _source.changes, as this page suggests? https://help.launchpad.net/Packaging/PPA/Uploading
[22:49] <jjlee> mine doesn't
[22:50] <jjlee> though the .changes file does point to an .orig.tar.gz
[22:50] <jjlee> (it also points to a .dsc, and a .diff.gz, and a .deb)
[22:58] <wgrant> jjlee: Launchpad only accepts source uploads. You need to pass '-S' to debuild or dpkg-buildpackage.
[23:00] <jjlee> I'm using git-buildpackage, didn't see any similar-looking options
[23:01] <jjlee> oh, it passes options along
[23:01] <jjlee> thanks


[00:26] <johnc4510> anyone notice that the rss feed for the planet isn't working?
[00:28] <kennymc0> i noticed that
[00:29] <cody-somerville> Known issues
[00:29] <johnc4510> k, i wasn't sure
[00:29] <johnc4510> :)
[00:29] <johnc4510> cody-somerville: how goes it?
[00:29] <cody-somerville> Not too shabby. Yourself?
[00:29] <johnc4510> good good thx