[04:09] <utkarsh2102> vorlon: hey, are you still around?
[04:21] <utkarsh2102> phpseclib/armhf has already been fixed by the new upload of phpseclib, all that's needed is re-triggers. Will do that now!
[04:35] -queuebot:#ubuntu-release- Unapproved: libreoffice (hirsute-proposed/main) [1:7.1.3-0ubuntu<IP_ADDRESS> => 1:7.1.4-0ubuntu<IP_ADDRESS>] (ubuntu-desktop)
[07:30] -queuebot:#ubuntu-release- Unapproved: virtualbox-ext-pack (focal-proposed/multiverse) [6.1.16-1~ubuntu<IP_ADDRESS> => 6.1.22-1~ubuntu<IP_ADDRESS>] (no packageset)
[07:30] -queuebot:#ubuntu-release- Unapproved: virtualbox-ext-pack (hirsute-proposed/multiverse) [6.1.18-1 => 6.1.22-1~ubuntu<IP_ADDRESS>] (no packageset)
[07:30] -queuebot:#ubuntu-release- Unapproved: virtualbox-ext-pack (groovy-proposed/multiverse) [6.1.16-1~ubuntu<IP_ADDRESS> => 6.1.22-1~ubuntu<IP_ADDRESS>] (no packageset)
[07:33] -queuebot:#ubuntu-release- Unapproved: virtualbox-guest-additions-iso (focal-proposed/multiverse) [6.1.16-1~ubuntu<IP_ADDRESS> => 6.1.22-1~ubuntu<IP_ADDRESS>] (no packageset)
[07:34] -queuebot:#ubuntu-release- Unapproved: virtualbox-hwe (focal-proposed/multiverse) [6.1.16-dfsg-6ubuntu<IP_ADDRESS> => 6.1.22-dfsg-1~ubuntu<IP_ADDRESS>] (kernel-dkms)
[07:35] -queuebot:#ubuntu-release- Unapproved: virtualbox-guest-additions-iso (groovy-proposed/multiverse) [6.1.16-1 => 6.1.22-1~ubuntu<IP_ADDRESS>] (no packageset)
[07:38] -queuebot:#ubuntu-release- Unapproved: virtualbox-hwe (groovy-proposed/multiverse) [6.1.16-dfsg-6ubuntu<IP_ADDRESS> => 6.1.22-dfsg-1~ubuntu<IP_ADDRESS>] (kernel-dkms)
[07:39] -queuebot:#ubuntu-release- Unapproved: virtualbox-guest-additions-iso (hirsute-proposed/multiverse) [6.1.20-1 => 6.1.22-1~ubuntu<IP_ADDRESS>] (no packageset)
[07:41] -queuebot:#ubuntu-release- Unapproved: virtualbox-hwe (hirsute-proposed/multiverse) [6.1.18-dfsg-5ubuntu<IP_ADDRESS> => 6.1.22-dfsg-1~ubuntu<IP_ADDRESS>] (kernel-dkms)
[07:42] -queuebot:#ubuntu-release- Unapproved: virtualbox (focal-proposed/multiverse) [6.1.16-dfsg-6~ubuntu<IP_ADDRESS> => 6.1.22-dfsg-1~ubuntu<IP_ADDRESS>] (kernel-dkms, ubuntu-cloud)
[07:45] -queuebot:#ubuntu-release- Unapproved: virtualbox (hirsute-proposed/multiverse) [6.1.18-dfsg-5 => 6.1.22-dfsg-1~ubuntu<IP_ADDRESS>] (kernel-dkms, ubuntu-cloud)
[07:46] -queuebot:#ubuntu-release- Unapproved: virtualbox (groovy-proposed/multiverse) [6.1.16-dfsg-6~ubuntu<IP_ADDRESS> => 6.1.22-dfsg-1~ubuntu<IP_ADDRESS>] (kernel-dkms, ubuntu-cloud)
[08:24] <ricotz> sil2100, hello :), I am hoping you will have some time for libreoffice/hirsute which is in the queue now -- https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1931272
[08:29] <sil2100> ricotz: hey! I might have but in approx 1-2 hours :)
[08:31] <ricotz> sil2100, sounds great :)
[08:32] <sil2100> ricotz: could you re-ping me once I get back online again in that time?
[08:35] <seb128> sil2100, hey, what's the status of fixing impish daily builds due to the zstd thing? are we waiting on that SRU to be installed on the machine, does it need to be moving to updates first?
[08:38] -queuebot:#ubuntu-release- Unapproved: mesa (hirsute-proposed/main) [21.0.1-2 => 21.0.3-0ubuntu0.1] (core, i386-whitelist, xorg)
[08:38] -queuebot:#ubuntu-release- Unapproved: rejected mesa [source] (hirsute-proposed) [21.0.3-0ubuntu0.1]
[08:41] -queuebot:#ubuntu-release- Unapproved: mesa (hirsute-proposed/main) [21.0.1-2 => 21.0.3-0ubuntu0.1] (core, i386-whitelist, xorg)
[08:45] -queuebot:#ubuntu-release- Unapproved: ubiquity (focal-proposed/main) [<IP_ADDRESS> => <IP_ADDRESS>] (core)
[08:51] <ginggs> laney: thanks for the easy hint for cuda yesterday
[08:52] <juliank> cjwatson: I screwed up a bit and did ./copy-package --from ppa:ubuntu-uefi-team/ubuntu/ppa -s hirsute --to-suite impish-proposed shim --to ubuntu *without* the -b; I do need the binaries from there copied though - I cancelled the builds in the archive
[08:52] <juliank> cjwatson: I can't rebuild it because that would change the hash, is there something that can be hacked around on the LP side?
[08:52] <juliank> or in ubuntu-archive
[08:52] <juliank> So did source-only copy by accident, cancelled builds, now need builds copied
[08:53] <juliank> or the whole thing purged from proposed so I can build again
[08:54] <juliank> Because otherwise, we'll have to resubmit the shim again and get it reviewed and signed again, and that's super silly
[08:54] <juliank> Or not update impish I guess
[08:55] <juliank> and yes, I should have talked to archive first
[08:56] <juliank> Oh after cancelling the build I could copy-package -b it now
[08:56] <juliank> So I guess sorry for the noise, I just got super scared :D
[08:56] <juliank> phew
[08:57] <juliank> (it rejected it first time I tried as it was scheduling builds alreaday)
[08:57] <juliank> gotta be more frakking careful
[08:58] <laney> it's a good idea to get copy-package commands reviewed
[09:00] <juliank> laney: -b is easy to miss :D
[09:00] <juliank> laney: Maybe copies should go into unapproved queue by default unless an extra flag is passed
[09:01] <juliank> Then you can go look at it and see it did the right thing
[09:09] <juliank> waiting for the binaries to pop up on rmadison
[09:46] <laney> ginggs: sorry missed that - np
[09:46] <apw> cancelling the builds and recopying with binaries ought to work out ok, pretty sure i've done that with the odd kernel in the past
[09:47] <apw> juliank, we have copy-proposed-kernel for this reason; which knows about which packages must have -b and which not to not make a horrible unfixable mess.
[09:48] <juliank> ack
[10:06] <utkarsh> cjwatson: hey, https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#php-defaults -> no more blockers now! \o/
[10:06] <cjwatson> utkarsh: Aside from the php7.4 stuff?  But indeed, progress
[10:07] <utkarsh> cjwatson: can you, with AA hat on, force migrate php-defaults & remove php7.4 from the archive?
[10:07] <utkarsh> php8.0 is already in the -release pocket.
[10:07] <cjwatson> utkarsh: This isn't something I've been involved with for years, so I'm reluctant to touch it
[10:07] <cjwatson> utkarsh: And migration is more an ~ubuntu-release thing
[10:08] <utkarsh> cjwatson: ah, no problem then! probably vorlon would know?
[10:08] <cjwatson> Yep
[10:08] <cjwatson> Or might well be somebody else in a more EUish timezone
[10:09] <utkarsh> in all, I'd like to know if there's anything that's left on my part to do? I've cleared up all the blockers + re-triggers and now only thing that's left is force-migrating & removing php7.4, I believe.
[10:09] <utkarsh> yep, thanks! I'll hang around here to see if there's anyone who can help :)
[10:09] <utkarsh> vorlon & I have polar opposite timezones :D
[10:10] <laney> utkarsh: can you file a hint to force-skiptest that, and a removal bug for php7.4?
[10:11] <laney> I guess once it migrates the rdepends list will become empty?
[10:12] <utkarsh> laney: perfect, I'll do that now. A removal bug already exists, though. As soon as it migrates, I'll let you know here, thank you!
[10:13] <laney> okey
[10:23] <ricotz> sil2100, here is the reminder ;P
[10:27] <utkarsh> laney: https://code.launchpad.net/~utkarsh/britney/+git/britney/+merge/404519 -> hints MP for your review.
[10:30] <juliank> Hmm
[10:30] <juliank> shim-signed FTBFS now because no sighed shim binaries for 15.4-0ubuntu5 in  http://ftpmaster.internal/ubuntu/dists/impish-proposed/main/signed/shim-amd64/ yet
[10:31] <sil2100> ricotz: thanks! On it in a minute ;)
[10:32] <laney> utkarsh: I think we'll need a force too, for the uninstallability noted there
[10:33] <laney> should I remove that php7.4 rebuild in proposed?
[10:33] <utkarsh> laney: yes, please. It's unneeded anyway.
[10:36] <utkarsh> as for force, Steve hinted to use hints instead, here: https://bugs.launchpad.net/ubuntu/+source/php-defaults/+bug/1927264/comments/2
[10:36] <utkarsh> let me know what you think I/we should do! :)
[10:37] <laney> yeah, I mean a force hint
[10:37] <laney> LP git is being interminably slow 'git pull'ing the hints, stand by
[10:38] <utkarsh> sure, no rush! \o/
[10:38] <mdeslaur> jamespage: ceph is pretty much built in the security team PPA here: https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+packages
[10:38] <mdeslaur> jamespage: we're just waiting on riscv64
[10:39] <mdeslaur> jamespage: do you want to run those against your usual testing procedure and let me know when I can release them?
[10:39] <jamespage> mdeslaur: as we always do
[10:39] <jamespage> yep - can get to that
[10:39] <mdeslaur> jamespage: awesome, thanks!
[10:44] <laney> utkarsh: ok pushed, removing 7.4 now
[10:44] <laney> (from -proposed)
[10:45] <sil2100> ricotz: oh, this noopt workaround for armhf feels much better than the other propositions!
[10:45] <laney> done
[10:46] <sil2100> ricotz: one thing that I'd like to request is - could you add info about this workaround in the SRU bug description?
[10:46] <laney> noopt> not sure about that, in terms of making nicely usable binaries ...
[10:48] <sil2100> Depends on how many libreoffice users we have on armhf, I still consider this nicer than building with gcc-8, quite the old compiler
[10:51] <sil2100> ricotz: re: that ^, did anyone test the armhf libreoffice armhf binaries when built with noopt?
[10:51] <utkarsh> laney: awesome, thank you!
[10:52] <laney> utkarsh: I can't actually push, it seems :/
[10:52] <ricotz> sil2100, added a note to the sru bug, there was no testing besides running the testsuite which didn't show the crash anymore
[10:53] <utkarsh> laney: to my branch? can you send a diff, I'll push from here?
[10:53] <ricotz> laney, sil2100, regarding the real world usage, I would expect people to use the arm64 build in recent hardware
[10:53] <seb128> sil2100, from an user perspective it might be nicer having an optimized binary build with an older gcc than a slower build from a new compiler
[10:53] <seb128> just saying :)
[10:53] <laney> utkarsh: no, to merge your branch to the real hints one
[10:54] <utkarsh> aah!
[10:54] <laney> I don't think I could push to yours - LP doesn't have that feature AFAIK
[10:54] <utkarsh> yep
[10:54] <laney> ('maintainers can push')
[10:55] <laney> anyway I pinged in #launchpad, hopefully git can be woken up
[10:55] <utkarsh> great, thank you!
[10:59] <laney> bah
[11:08] <sil2100> seb128, ricotz: hm hm, yeah, so maybe to get a better understanding, before we proceed I'd like to know if there is a huge performance regression when built with noopt for armhf or not
[11:09] <sil2100> Since yeah, it felt 'cleaner' to me before, but indeed if the performance drop is noticable, I guess I'd prefer another approach
[11:09] <seb128> sil2100, did we ever decide on the 'build in bileto without the buggy gcc-9 SRU'?
[11:09] <sil2100> So I both agree with laney and seb128 here - if, of course, it's noticable to armhf users
[11:10] <seb128> sil2100, that would give us a working binary with optimization on the same compiler serie the release has
[11:10] <sil2100> seb128: yeah, I mentioned at one moment that we could give it a try
[11:10] <sil2100> (on #ubuntu-desktop some days ago)
[11:10] <seb128> wdym give it a try?
[11:10] <laney> are you considering not blocking the SRU on this?
[11:10] <seb128> either it's ok by the SRU team or not
[11:10] <laney> the gcc-9 SRU on this regression, I m ean
[11:11] <laney> because if it is blocked, we might as well delete it ...
[11:11] <sil2100> laney: gcc-9 will not go out of -proposed
[11:11] <seb128> that's the other option
[11:11] <seb128> if it's proved to be buggy maybe delete and just rebuild libreoffice without bileto then
[11:11] <seb128> I would +1 that one :)
[11:12] <sil2100> I thought we wanted to have it there for debugging purposes, also, it's not entirely clear (at least from what I heard) if this needs changes on the gcc side or libreoffice side
[11:12] <sil2100> This is why I was leaving it blocked there
[11:12] <sil2100> I do not actively track the gcc regression discussion so I just know what I heard here and there
[11:12] <seb128> so we picked a binary that started segfaulting after rebuild with that gcc on armhf
[11:13] <seb128> how do we get confidence there are no other sources that will be impacted the same way?
[11:14] <laney> utkarsh: finally pushed
[11:14] <laney> the next complete proposed-migration run should see the new hints
[11:14] <utkarsh> laney: awesome! what's left now? we wait for hints to do its magic?
[11:14] <laney> probably be a couple of hours at least
[11:14] <utkarsh> right & php-defaults should auto-migrate then?
[11:15] <laney> well, we'll see ;-) that's always the game
[11:15] <utkarsh> heh, of course
[11:15] <laney> but hopefully
[11:15] <utkarsh> awesome, thank you! I'll keep an eye on this
[11:15] <utkarsh> btw, is php7.4 removed from -proposed?
[11:15] <laney> yeah
[11:16] <sil2100> hm, actually, the gcc-9 uploads were bincopies from the toolchain PPA, so that could be used for testing
[11:16] <laney> you can see on https://launchpad.net/ubuntu/+source/php7.4/+publishinghistory
[11:16] <utkarsh> right, thank you, again!
[11:17] <ricotz> sil2100, the gcc-9 build in impish shows the same issue, so hirsute is not strictly required to debug it
[11:17] <seb128> sil2100, launchpad also keep the debs anyway so it's always possible to download them and install
[11:17] <sil2100> Let me poke around on that in a minute, since my head is still a bit dizzy
[11:18] <ricotz> fun with libreoffice :(
[11:18]  * laney hugs ricotz :(
[11:18] <sil2100> Per SRU policy it indeed should be considered for removal
[11:19] <sil2100> Too bad it's been in -proposed for so long, since many other packages already used it to build
[11:20] <ricotz> sil2100, but gcc-10 is the default in hiruste?
[11:20] <seb128> it's only since the 8th and in hirsute
[11:20] <ricotz> so it should not have that much impact
[11:20] <laney> I guess one thing is that, if it's the same gcc-10 bug, it's been used to build most of hirsute and impish and the world didn't end
[11:22] <ricotz> laney, the impact of gcc-10 on libreoffice build is different though, but likely the same root cause
[11:22] <sil2100> Fun
[11:22] <laney> nod
[11:23] <ricotz> seeing "The bug is not reproducible, so it is likely a hardware or OS problem." while building libreoffice with different gcc-9 revision is weird too
[11:23] <laney> anyway, I still would remove it if it were up to me, then it can be debugged but the heat is off a bit :-)
[11:23] <ricotz> (and it is reproducible on the armhf builders)
[11:23] <seb128> also I don't want to derail and start another discussion, but does a gcc-9.3 to gcc-9.4 does really qualify for a SRU? it's neither a micro release nor something on the exceptions list
[11:24] <seb128> I would also vote +1 for deleting it
[11:31] <utkarsh> laney: hey, I've marked LP: #1927264 as "fix committed"; let me know if that doesn't represent the current situation appropriately!
[11:35] <sil2100> laney: btw.! Just out of curiosity - if I delete a package from, say, -proposed and then after a while restore (undelete it), will britney still consider the previous test results for that package? Or will it re-trigger tests again? I guess it should just take those existing, as the version didn't change?
[11:39] <laney> sil2100: that's right. It'll go look in its cache or swift first, before requesting a new test run, so the old results should get found
[11:40] <sil2100> Okay, then I guess I'm leaning towards removing it as per your proposition
[11:41]  * ricotz prepares a libreoffice source without touching the gcc deps
[11:47] <juliank> sil2100: could you approve the shim signing tarballs in hirsute for me?
[11:47] <sil2100> juliank: sure
[11:47] <ricotz> sil2100, if we want to the route then please reject libreoffice from the queue, so I will upload a version without the noopt tweak
[11:48] <sil2100> juliank: hm, don't see any
[11:48] <juliank> sil2100: sorry, impish
[11:48] <juliank> typo day
[11:48] <sil2100> ricotz: please upload away, there can be multiple packages with the same version number in the queue
[11:48] <sil2100> I'll pick the right one then
[11:48] <sil2100> juliank: ah!
[11:48] <ricotz> sil2100, alright, will do
[11:49]  * juliank also looked at the wrong queue and was totally confused
[11:49] <juliank> :D
[11:49] <juliank> (earlier today)
[11:49] <laney> I think juliank might need some close reviewing today 🙃
[11:49] <juliank> laney: Oh yeah
[11:50] <juliank> Or caffeine, but it's afternoon now so that ship has sailed I think
[11:52] <sil2100> Well, tell me about it, I was confused multiple times today as well, but thankfully there's laney
[11:52] <laney> I'm just confused as a baseline
[11:53] <juliank> it's hard it's only 17°C outside
[11:53] -queuebot:#ubuntu-release- Unapproved: libreoffice (hirsute-proposed/main) [1:7.1.3-0ubuntu<IP_ADDRESS> => 1:7.1.4-0ubuntu<IP_ADDRESS>] (ubuntu-desktop)
[11:54] <juliank> 10°C dfrop over night
[11:54] <juliank> messes with you
[11:54] <juliank> inside temperature dropped about 5°C
[11:55] -queuebot:#ubuntu-release- Unapproved: rejected libreoffice [source] (hirsute-proposed) [1:7.1.4-0ubuntu<IP_ADDRESS>]
[11:56] <RikMills> do we know when ISO builds will be fixed?
[11:57] <sil2100> Soon!
[11:57] <RikMills> :)
[11:57] <sil2100> initramfs-tools is publishing as we speak, my RT is ready to press ze button
[11:57] <RikMills> nice. thanks!
[12:10] <RikMills> sil2100: impish? I don't see a new initramfs-tools there
[12:10] <laney> focal
[12:11] <RikMills> k
[12:11] <RikMills> so no fix is queued for impish yet?
[12:12] <sil2100> It's not needed in impish, this is actually fixed in impish
[12:12] <sil2100> It's failing as the builder is on focal
[12:12] <laney> impish has the bits already. what's needed is a fix on the host which builds the isos
[12:12] <RikMills> laney: aha. that makes sense. cheers :)
[12:13] <laney> assuming we don't find another thing after fixing this one hyuk hyuk hyuk
[12:13] <sil2100> Don't jinx it!
[12:14]  * RikMills crosses everything
[12:41] <laney> cjwatson: could you update the locked mode in here to not have 't' so that the topic can be changed please? or give me permission to do so
[12:54] <cjwatson> laney: You should be able to op yourself and change it
[12:55] <cjwatson> laney: Or you have permission to use the chanserv topic command
[13:28] <jibel> SRU team / bdmurray : Hi could someone review/approve ubiquity <IP_ADDRESS> and sssd 2.2.3-3ubuntu0.6 in focal unapproved queue?
[13:30] <sil2100> I can take a look in a minute
[13:33] <apw> laney, chanserve topic seems to be the approved way
[13:39] -queuebot:#ubuntu-release- Unapproved: bluez (hirsute-proposed/main) [5.56-0ubuntu4.1 => 5.56-0ubuntu4.2] (i386-whitelist, ubuntu-desktop)
[13:39] -queuebot:#ubuntu-release- Unapproved: shim (hirsute-proposed/main) [15.4-0ubuntu2 => 15.4-0ubuntu5] (core) (sync)
[13:40] -queuebot:#ubuntu-release- Unapproved: shim-signed (hirsute-proposed/main) [1.47 => 1.48] (core) (sync)
[13:40] -queuebot:#ubuntu-release- Unapproved: shim-signed (xenial-proposed/main) [1.33.1~16.04.7 => 1.47] (core) (sync)
[13:40] <juliank> ubuntu-sru please reject shim-signed/xenial sync
[13:40] <juliank> (^ sil2100
[13:41] -queuebot:#ubuntu-release- Unapproved: shim (xenial-proposed/main) [15.4-0ubuntu2 => 15.4-0ubuntu5] (core) (sync)
[13:49] <apw> juliank, v
[13:49] <sil2100> !
[13:49] -queuebot:#ubuntu-release- Unapproved: rejected shim-signed [sync] (xenial-proposed) [1.47]
[13:49] <sil2100> apw is faster than me!
[13:49] <juliank> oh thanks apw
[13:49] <juliank> sil2100: everything is a race these days
[14:21] -queuebot:#ubuntu-release- Unapproved: bluez (focal-proposed/main) [5.53-0ubuntu3.2 => 5.53-0ubuntu3.3] (i386-whitelist, ubuntu-desktop)
[14:21] -queuebot:#ubuntu-release- Unapproved: bluez (hirsute-proposed/main) [5.56-0ubuntu4.1 => 5.56-0ubuntu4.2] (i386-whitelist, ubuntu-desktop)
[14:22] -queuebot:#ubuntu-release- Unapproved: rejected bluez [source] (hirsute-proposed) [5.56-0ubuntu4.2]
[14:25] -queuebot:#ubuntu-release- Unapproved: accepted libreoffice [source] (hirsute-proposed) [1:7.1.4-0ubuntu<IP_ADDRESS>]
[14:26] <laney> cjwatson: ok, should I read that as you being opposed to removing it?
[14:27] <laney> the mode is locked, so I can't remove it if that's what you meant
[14:27] <laney> it seemed fine to me having been open over the years
[14:35] <sil2100> jibel: hey! Re: the ubiquity SRUs - they're set to Fix Released for devel, so I assume these are fixed in the current version in impish, right? Also, this is not important that much but out of curiosity, are those fixed in hirsute?
[14:36] <sil2100> (since we don't intend to respin hirsute images)
[14:36] <sil2100> (but still interested)
[14:38] <cjwatson> laney: Sort of -0.1.  IME -t is OK a lot of the time and then spammers randomly turn up and make life miserable sometimes
[14:38] <LocutusOfBorg> so can we sync php8.0 from sid next britney run?
[14:39] <cjwatson> laney: I'd slightly prefer keeping topic changes just for ops (i.e. you can do it because chanserv thinks you have operator privileges here, you just need to op yourself)
[14:41] <cjwatson> But I'll remove +t if I seem to be outvoted :)
[14:45] <apw> given one can just ask chanserv, it seems strange to open it up to abuse (to me)
[14:45] <jibel> sil2100, yeah it's fixed in https://launchpad.net/ubuntu/+source/ubiquity/21.10.2 but we won't fix hirsute
[14:45] <jibel> since as you said there won't be new images
[14:47] <jibel> and *if* there is one, then we can SRU the fixes there too.
[14:47] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (focal-proposed) [<IP_ADDRESS>]
[14:57] <jibel> sil2100, and for sssd the code we backported to focal is already in hirsute
[14:58] <sil2100> jibel: thanks! One thing regarding that: since sssd I think is basically maintained by the server team, did you talk to them about what they think of adding this patch?
[14:59] <sil2100> Asking since it's quite a big patch so basically the server team will ahve to keep mainteining it
[15:00] <sil2100> Anyway, accepting that, left my concerns on the bug but otherwise accepting
[15:00] <jibel> sil2100, thanks, I'll request a review from them too.
[15:00] -queuebot:#ubuntu-release- Unapproved: accepted sssd [source] (focal-proposed) [2.2.3-3ubuntu0.6]
[15:03] <laney> apw: just makes life easier, lets people contribute, has been basically fine for years
[15:03] <laney> but doesn't matter, not a big deal
[15:05] <utkarsh2102> laney: I hope things are set to migrate, at least "Will attempt migration due to a hint (Any information below is purely informational)" has made me very hopeful :)
[15:05] <utkarsh2102> cf: https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#php-defaults
[15:06] <laney> utkarsh2102: https://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt nope
[15:06] <laney> maybe I need a stronger hint
[15:07] <laney> I think I need force-hint too
[15:08] <utkarsh2102> bah!
[15:08] <utkarsh2102> of course update_excuses :)
[15:08] <laney> ok added that
[15:08] <utkarsh2102> perfect, thank you!
[15:31] -queuebot:#ubuntu-release- Unapproved: evolution-data-server (hirsute-proposed/main) [3.40.0-1ubuntu1 => 3.40.0-1ubuntu1.1] (i386-whitelist, ubuntu-desktop)
[15:42] <vorlon> laney: yep, force-hint is the trick :)
[15:43]  * laney nods
[15:43] <laney> there's also 'allow-uninst' I see, wonder if that would have worked
[15:43] <vorlon> huh
[16:13] <vorlon> coreycb: hey, python-pbr shows up on https://people.canonical.com/~ubuntu-archive/nbs.html with a goodly number of reverse-build-dependencies that need updating.  Is the openstack team aware of this?
[16:16] <vorlon> ogra: what is the xlnx-firmware package in hirsute-proposed NEW queue?  If it's needed, it'll need some kind of reupload because I can't even download it from the queue for review
[16:17] <ogra> vorlon, sil2100 should be able to he was involved with the customer stuff ...
[16:18] <ogra> i was only the upload minion
[16:18] <vorlon> hmm :)
[16:18] <ogra> well ... pocket copy minion 🙂
[16:18] <vorlon> where was it copied from? because it's listed as "from private ppa" and it's not downloadable at all from the queue
[16:18] <ogra> yeah, it came from a private PPA
[16:19] <vorlon> well, it's unreviewable
[16:19] <vorlon> so I'm going to reject it
[16:19] <ogra> and people that should be able to review have been added to the PPA team
[16:19] <vorlon> have I?
[16:19] <ogra> heh, well, it was supposed that ubuntu-release as a whole should be added
[16:20] <coreycb> vorlon: thanks, we'll take care of that - I think we can just remove the python-pbr (build-)depends from those packages. icey can you take this?
[16:20] <vorlon> ... which is the wrong team for a NEW review in a stable release, but I'm in it, so it doesn't seem to have worked :)
[16:22] <vorlon> ogra: so do you want to have a second look at the ppa setup?
[16:23] <bdmurray> laney: how often is autopkgtest-package-configs updated on the server?
[16:24] <ogra> vorlon,oops, sorry, my bad, it was ubuntu-archive that was added, not -release (i have zero to do with that stuff, and was only asked by john agosta if i could copy it over as core-dev)
[16:24] <laney> bdmurray: https://git.launchpad.net/autopkgtest-cloud/tree/charms/focal/autopkgtest-cloud-worker/units/pull-package-configs.timer
[16:24] <vorlon> ogra: well, I'm in that team too but it still doesn't let me download! :)
[16:24] <ogra> weird
[16:25] <ogra> vorlon, i know xnox and sil2100 were able to download ... (at least they said so here) ... lets perhaps take it to mattermost
[16:27] <bdmurray> laney: thanks!
[16:29] <laney> the xlnx thing is another instance of bug #1923177 btw ;-)
[16:37] -queuebot:#ubuntu-release- New: rejected xlnx-firmware [sync] (hirsute-proposed) [0.1ubuntu14]
[16:45] <ogra> vorlon, better now ?
[16:45] -queuebot:#ubuntu-release- New source: xlnx-firmware (hirsute-proposed/primary) [0.1ubuntu15]
[17:21] -queuebot:#ubuntu-release- Unapproved: accepted evolution-data-server [source] (hirsute-proposed) [3.40.0-1ubuntu1.1]
[17:31] <laney> utkarsh2102: looks like it went in, let's do the removal tomorrow
[17:32] <laney> unless vorlon wants to get there first
[17:33] <utkarsh2102> laney: woot, woot! I am happy that it worked! thanks a bunch! \o/
[17:54] -queuebot:#ubuntu-release- Unapproved: rejected ceph [source] (groovy-proposed) [15.2.12-0ubuntu<IP_ADDRESS>]
[17:59] <utkarsh2102> laney: hey, I still see php-defaults in the excuses page, though. And rmadison still mentions -proposed :(
[18:01] <RikMills> https://kde.org/announcements/plasma/5/5.22.2/
[18:10] <laney> utkarsh2102: give it time, check the publishing history - it's moved
[18:11] <utkarsh2102> laney: aha, gotcha, thank you!
[18:11] <RikMills> whoops. that link was not meant for here. sorry
[18:13] <LocutusOfBorg> and php8.0 is syncd :D
[18:20] -queuebot:#ubuntu-release- Unapproved: accepted lighttpd [source] (focal-proposed) [1.4.55-1ubuntu<IP_ADDRESS>]
[18:22] -queuebot:#ubuntu-release- Unapproved: accepted lighttpd [source] (bionic-proposed) [1.4.45-1ubuntu<IP_ADDRESS>]
[18:42] -queuebot:#ubuntu-release- Unapproved: accepted simplestreams [source] (focal-proposed) [0.1.0-30-g3cc8988a-0ubuntu<IP_ADDRESS>]
[19:09] -queuebot:#ubuntu-release- Unapproved: mysql-5.7 (bionic-proposed/main) [5.7.34-0ubuntu<IP_ADDRESS> => 5.7.34-0ubuntu<IP_ADDRESS>] (core)
[19:10] -queuebot:#ubuntu-release- Unapproved: rejected mysql-5.7 [source] (bionic-proposed) [5.7.33-0ubuntu<IP_ADDRESS>]
[19:17] -queuebot:#ubuntu-release- New binary: gnome-desktop3 [amd64] (impish-proposed/main) [40.2-1ubuntu1] (ubuntu-desktop)
[19:17] -queuebot:#ubuntu-release- New binary: gnome-desktop3 [s390x] (impish-proposed/main) [40.2-1ubuntu1] (ubuntu-desktop)
[19:17] -queuebot:#ubuntu-release- New binary: gnome-desktop3 [ppc64el] (impish-proposed/main) [40.2-1ubuntu1] (ubuntu-desktop)
[19:18] -queuebot:#ubuntu-release- New binary: gnome-desktop3 [arm64] (impish-proposed/main) [40.2-1ubuntu1] (ubuntu-desktop)
[19:23] -queuebot:#ubuntu-release- New binary: gnome-desktop3 [armhf] (impish-proposed/main) [40.2-1ubuntu1] (ubuntu-desktop)
[19:30] -queuebot:#ubuntu-release- Unapproved: linux-firmware (hirsute-proposed/main) [1.197.1 => 1.197.2] (core, kernel)
[19:34] -queuebot:#ubuntu-release- Unapproved: shim-signed (xenial-proposed/main) [1.33.1~16.04.7 => 1.33.1~16.04.8] (core)
[19:49] -queuebot:#ubuntu-release- Unapproved: accepted strongswan [source] (bionic-proposed) [5.6.2-1ubuntu2.6]
[19:54] -queuebot:#ubuntu-release- New binary: gnome-desktop3 [riscv64] (impish-proposed/main) [40.2-1ubuntu1] (ubuntu-desktop)
[20:17] -queuebot:#ubuntu-release- Unapproved: accepted mysql-5.7 [source] (bionic-proposed) [5.7.34-0ubuntu<IP_ADDRESS>]
[20:21] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (hirsute-proposed) [1.197.2]
[21:25] -queuebot:#ubuntu-release- Unapproved: accepted shim [sync] (hirsute-proposed) [15.4-0ubuntu5]
[21:25] <utkarsh2102> vorlon: thanks a bunch! :D
[21:25] <vorlon> utkarsh2102: my pleasure
[21:25] <utkarsh2102> with this, php8.0 transition is formally over, yay! \o/
[21:29] -queuebot:#ubuntu-release- Unapproved: accepted shim-signed [sync] (hirsute-proposed) [1.48]
[21:33] -queuebot:#ubuntu-release- Unapproved: rejected shim-signed [sync] (groovy-proposed) [1.47]
[21:33] -queuebot:#ubuntu-release- Unapproved: rejected shim [sync] (groovy-proposed) [15.4-0ubuntu2]
[21:45] -queuebot:#ubuntu-release- Unapproved: accepted shim [sync] (xenial-proposed) [15.4-0ubuntu5]
[21:50] -queuebot:#ubuntu-release- Unapproved: accepted shim-signed [source] (xenial-proposed) [1.33.1~16.04.8]
[23:18] <Trevinho> anyone can ack those NEW's for gnome-desktop3 https://launchpad.net/ubuntu/impish/+queue?queue_state=0&queue_text=gnome-desktop3 ?


[10:42] <ari-tczew> kklimonda: can we sync python-django?
[12:19] <bdrung> tumbleweed: now we need a wrap-and-sort tool for command line parameters ;)
[12:27] <tumbleweed> bdrung: huh
[12:27] <tumbleweed> s/u/e/
[12:28] <bdrung> tumbleweed: look at the manpage for wrap-and-sort. the parameters are totally unsorted
[12:36] <aboudreault> hi
[12:36] <aboudreault> In my debian/rules file, after I the make install of the software. I'm trying to add a quick hack,
[12:37] <aboudreault> I mv a file from debian/tmp/.../lib/test.so.1.1.2 to [...]test.so.2.3.1. Then try to make symbolic links...
[12:37] <aboudreault> it seems that the command dh_install removes thoses symlinks, I'm not sure why
[12:38] <aboudreault> if I add a ls in my debian/rules, I can see that my symlink have been properly created... but the dh_install fails because it doesn't find them.
[12:38] <aboudreault> any idea?
[12:38] <tumbleweed> bdrung: I went for a logical order :)
[12:40] <aboudreault> (and after the dpkg-buildpackage, the symlinks disapeared
[12:57] <aboudreault> ha. got it. The command cd in a debian/rules files do not change directory
[12:59] <geser> aboudreault: every command in a Makefile gets run in it's own sub-shell
[12:59] <aboudreault> geser, good to know. thanks
[13:00] <geser> if you want to "cd" and then e.g. do a "ls" you need to use "cd foobar && ls" (or similar constructs)
[13:00] <aboudreault> all right
[14:00] <bdrung> tumbleweed: do we really set DEB_VENDOR=Ubuntu for all tools? grab-merge and syncpackage targets only ubuntu. there it is ok, but dgetlp and pull-lp-source? maybe a DD want to use pull-lp-source to pull a ubuntu package and maintain it in debian and upload to debian
[14:10] <bdrung> tumbleweed: what's the progress of pbuilder-dist-refactor? we have so many changes. i want to release them.
[16:17] <mirak> hello
[16:33] <tumbleweed> bdrung: fair questions. I assume the dgetlp case you mentoin is pretty rare, but then debian/patches/$distro.series is pretty rare too
[16:34] <tumbleweed> bdrung: the progress on pbuilder-dist is that it's completely untested and I'm only getting back home late on monday. It'll remain untested until then
[16:36] <bdrung> tumbleweed: i think dgetlp and pull-lp-source shouldn't set DEB_VENDOR
[16:37] <bdrung> tumbleweed: let me know once your pbuilder-dist changes are tested (and merged). then i will release the next version
[16:37] <tumbleweed> bdrung: I understand your concerns there, happy to revert that
[18:44] <crimsun> bah, I'll just file the bug myself and attach the patch thanks to the netsplit.
[19:39] <ebroder> ari-tczew: It looks like we need a plan for keeping the package up to date in stable releases to make upstream happy
[19:41] <bdrung> ari-tczew: ^ we need an ubuntu maintainer for it.
[19:44] <ebroder> Although it does seem like happyaron volunteered to do that
[19:49] <ari-tczew> ebroder, bdrung: that's right. I'm pretty sure that he want to be an ubuntu maintainer for tor. Looking on his related packages page, he has got a bit expierence in packaging.
[19:50] <ebroder> ari-tczew: I'd kind of like to see some sort of plan in case happyaron vanishes for whatever reason
[19:51] <geser> it's more about doing SRUs than packaging
[19:57] <ari-tczew> ebroder: I hate plans. Plans usually to end only on plans, without activities. The most important thing to achieve success are operational activities. But this is humble opinion, offtopic.


[06:17] <RikMills> looks like the archive publisher is not working for non x86 ports
[06:19] <RikMills> for example, 10 hrs later this is not published: https://launchpad.net/ubuntu/+source/kio/5.93.0-0ubuntu1/+build/23580447
[09:37] <cjwatson> RikMills: fix in progress
[09:37] <RikMills> cjwatson: thanks, espcially on a sunday on a bank holiday weekend!
[09:38] <cjwatson> I'm travelling so the bank holiday is postponed for me ...
[09:39] <RikMills> dman. hope you get to make up for it
[09:39] <RikMills> *damn
[09:39] <cjwatson> oh yeah of course
[09:40] <cjwatson> but it causes very loud alerts to go off when the archive publisher stops working so the on-call IS person had been poking at the publisher for some hours and eventually managed to get through to me on the train
[19:12] <Chalky> Every time I open a window it goes to the top left of the screen.  Why doesn't it go top centre?  If you own a big screen then I suggest it's fustrating to have to keep moving the window centrally to study the contents easily.


[00:46] <Unit193> https://lists.ubuntu.com/archives/ubuntu-devel/2016-July/039465.html in case you didn't see.
[00:49] <bluesabre> Unit193: thanks for the link
[06:43] <flocculant> Unit193: perhaps that's why the dropbox one is failing then *shrug*
[06:48] <Unit193> nm-applet too?
[06:49] <flocculant> Unit193: that appears to be there
[06:49] <Unit193> Hmm.  Didn't in VM, not updating yet on real. :P
[06:49] <flocculant> I don't actually have a use for it so don't fiddle with it ever
[07:14] <flocculant> gtk320 looks ok on install now - still fubar locally for some reason ?
[07:14] <flocculant> guessing difference between real and ppa there :)
[09:05] <astraljava> Wonder if a version update made it better.
[09:06] <astraljava> Oops, sorry wrong channel.
[11:05] <flocculant> akxwi-dave: didn't get time to check much but gtk320 looks ok on installs now - at least catfish and menulibre do
[11:12] <flocculant> akxwi-dave: might be in a rush tomorrow to get some trusty smoketests done as well - respin for xorg/nvidia implosions apparently
[11:57] <akxwi-dave> flocc
[11:58] <akxwi-dave> flocculant, no probs
[12:26] <akxwi-dave> flocculant, I am assuming that they will show ok in tomorrows ISO's?  In todays they still look bad..
[12:55] <flocculant> akxwi-dave: not sure wth is going on then - because today's iso looks ok here - perhaps ok on kvm *shrug*
[12:57] <akxwi-dave> i've done one on Vbox and the other on Vmware...  will do it tonight on Real.. also will try to get the .5 respin on real as well.. thats due tomorrow aint it.. if so I can rush a real thru at around 7pm on thurs if needed#
[15:00] <flocculant> akxwi-dave: late thurs will be too late
[15:00] <flocculant> I'm not that panicked by trusty anyway tbh
[15:01] <akxwi-dave> :-)
[15:01] <flocculant> any bugs that there are won't be ours
[15:02] <flocculant> also looking at -release respins should start soonish - hopefully there'll be one this evening - I can beat a hardware install out tonight with luck
[15:03] <flocculant> akxwi-dave: also ... /join #ubuntu-release ;)
[15:04] <akxwi-dave> already there.. :-)
[15:06] <flocculant> didn't see you - sorry :)
[15:07] <flocculant> akxwi-dave: so are you saying you still see oddities on yak from gtk3.20?
[15:07] <akxwi-dave> yep, can grab a screenie if you need..
[15:08] <flocculant> no need - I'll boot on hardware then :)
[15:09] <akxwi-dave> kk.. i'll also do a boot tonight on a lappie, one has Nvidia other AMD
[15:11] <flocculant> ok - well I'm always nvidia
[15:11] <flocculant> or intel if I'm brave
[15:12] <akxwi-dave> i used to be AMD desktop and Nvidia Laptop.. But bought a GTX960 for the desktop.. and that lappy I repaired has AMD in now
[15:12] <flocculant> :)
[15:14] <akxwi-dave> flocculant, started on the idiots guide for testing.. http://imgur.com/S8yfqX5
[15:15] <flocculant> nice one akxwi-dave :)
[15:15] <flocculant> that's the sort of thing I wanted to do - but got put off because hardly anyone reporting ;)
[15:16] <akxwi-dave> if we can make it easier for people to do then all we can do is try
[15:16] <flocculant> we can have a chat with knome - but might be useful to have that wikified - we can do that at 'our' wiki rather than ubuntu one too if we think that's best
[15:17] <flocculant> chat with knome would be about our wiki or ubuntu one ofc
[15:48] <flocculant> akxwi-dave: so if you boot the xenial iso instead of a yak one - everything looks fine ...
[15:49] <akxwi-dave> yep still have a xenial VM installed at the moment.. I'll get you a side by side
[15:50] <flocculant> akxwi-dave: no need :)
[15:50] <flocculant> the yak iso is still yuk not yak \o/
[15:50] <akxwi-dave> lol
[15:56] <akxwi-dave> also just noticed that on Yak it dont let me resize em
[16:02] <akxwi-dave> http://imgur.com/S8yfqX5
[16:02] <akxwi-dave> http://imgur.com/tDIINPu
[16:03] <akxwi-dave> ignore first one
[16:03] <akxwi-dave> http://imgur.com/OCpb3jN
[16:03] <akxwi-dave> http://imgur.com/xxnbbwd
[19:10] <knome> flocculant, (too bad dave left, but) my gut feeling is "contributor docs", but sure, i guess the wiki is fine too
[19:11] <knome> that said, i should make sure the media upload stuff doesn't look like crap (as it does now)
[19:12] <flocculant> knome: not sure about loads of images in cont docs tbh
[19:13] <knome> if the idiots (not my choice of word) will not understand it without, then i think we should have images...
[19:13] <knome> there are two things to that:
[19:13] <knome> 1) i think everybody should understand most things without images, as long as they are instructed well (and the UI lets them find stuff)
[19:14] <knome> 2) the UI should be easy enough that those idiots (again not my word) can find the information in it without too much holding hands (and/or images)
[19:14] <knome> but if we feel like images are needed, then sure, they can be in the contributor docs as well
[19:14] <flocculant> trouble with docs is if we need a quick change to image - not happening there is it
[19:14] <knome> the contributor docs are only online, so it's pretty swift.
[19:15] <flocculant> no it's not ;)
[19:15] <knome> ATM we have at least me an pleia2 who have access to the server, and Unit193 too
[19:15] <knome> (i think...)
[19:15] <flocculant> and on wiki - it can be changed without worrying about finding someone
[19:16] <knome> sure...
[19:17] <knome> though ultimately, i prefer how well the docs are (always) formatted, how easy it is to make a PDF version of them, how easy it is to translate them, etc. over the wiki
[19:17] <knome> and i think we should bang the contributor docs much more in our marketing that we are doing now (and prefer it over the wiki)
[19:17] <knome> yes, it's more maintenance (but tbh, at this point, not too much)
[19:18] <flocculant> well - in a couple of months all pretty moot
[19:18] <knome> why so?
[19:18] <flocculant> akwxi willl be qa lead :p
[19:18] <knome> so why is content created at that point moot?
[19:18] <flocculant> where
[19:19] <knome> anywhere?
[19:19] <knome> my main idea with everything we set up is that it can be passed on to new leaders and contributors without having to explain too much stuff
[19:19] <knome> so why would something be useless if a leader changes?
[19:20] <knome> (and isn't dave the one who's working on the guide anyway)
[19:20] <flocculant> because you might be able to browbeat dave into putting that on docs - woun't work with me :)
[19:20] <knome> i'm not going to say what you can or can't do
[19:20] <knome> so please don't take this as such
[19:21] <flocculant> I'm not
[19:21] <knome> i'm just giving my opinion as you were from my POV asking it
[19:21] <flocculant> actually if you read what I said - the choice was our wiki or the ubuntu one :)
[19:21] <knome> aha.
[19:22] <knome> well... i guess i don't mind choices too much, just think what's the best :P
[19:23] <knome> being limited to those choices, then i'd say the question is if it's generic enough to be appropriate for all flavors (ubuntu wiki) or specific enough to be useful only for xubuntu people (our wiki)
[19:23] <knome> and if the former, then i'd recommend being in touch with other flavor people *once you have the content ready on the wiki* to see if they want to add something, and to let them let their people know about the page(s)
[19:24] <flocculant> obviously I don't have a problem with the qa docs pages - I wrote what we have, and that is probably qty wise the same as the rest put together :)
[19:24] <knome> indeed
[19:24] <flocculant> anyway - bit midweekish now - might bbl
[19:25] <knome> there's a few things that should be put on the docs for website for example, but that's not high priority (as it's pretty clear on LP already)
[19:25] <knome> yeah, good night if not :)
[19:29] <flocculant> :)
[19:31] <flocculant> bluesabre: 32 bit trusty done again
[19:37] <knome> tv time
[20:56] <Unit193> knome: Yep, though I'm just a backup.
[21:05] <knome> Unit193, sure, i was mostly pointing out that we DO HAVE the backups in case either me or pleia2 isn't around.
[21:35] <bluesabre> evening all
[21:35] <Unit193> Howdy, bluesabre.
[21:35] <bluesabre> hey Unit193
[21:36] <knome> oi.
[21:37] <flocculant> evening bluesabre
[21:40] <bluesabre> hey knome
[21:40] <bluesabre> key flocculant
[21:40] <bluesabre> How's it going?
[21:40] <flocculant> a bit keyed up
[21:41] <flocculant> :p
[21:41] <bluesabre> :D
[21:42] <flocculant> bluesabre: set meeting for week friday at 2000 utc - just waiting on one response to the council mail - almost a full house :)
[21:43] <bluesabre> woo!
[21:43] <knome> so almost three of a kind and a pair?
[21:43] <bluesabre> probably can't make that, but let's see what happens then
[21:44] <knome> i probably can
[21:44] <knome> (and who cares of bluesabre anyway)
[21:44] <bluesabre> precisely
[21:44] <knome> bluesabre, i'm just kidding, i love you
[21:44] <knome> (not in the wrong way)
[21:45]  * bluesabre knows its all about the code
[21:45] <knome> ;)


[13:23] <bdmurray> cjwatson: it looks like bug 907524 now has what you were looking for.
[13:23] <ubot2`> Launchpad bug 907524 in wubi "No Lubuntu option" [Undecided,Confirmed] https://launchpad.net/bugs/907524
[13:37] <cjwatson> bdmurray: ah, thanks
[13:37] <bdmurray> cjwatson: I also noticed that I can't set wubi bugs to Triaged and their importance.  Perhaps the bug supervisor could be changed to ubuntu-bugcontrol?
[15:24] <cjwatson> bdmurray: Hm, yes.  The previous bug supervisor (ago) is in the project maintainer team so he shouldn't lose out by being taken off bug supervisor.  However, I can't do it because I'm not an admin of ubuntu-bugcontrol.  I've temporarily made you an admin of ubuntu-installer - can you make that change?  https://launchpad.net/wubi/+configure-bugtracker
[15:25] <cjwatson> bdmurray: (ubuntu-installer gets a fair bit of mail; I can either set you back to an ordinary member or remove you from the team altogether after you've done that, up to you ...)
[15:27] <CIA-11> debian-installer: cjwatson * r1326 lucid-proposed/ (29 files in 7 dirs):
[15:27] <CIA-11> debian-installer: Add natty and oneiric images for amd64 and i386, built with the
[15:27] <CIA-11> debian-installer: respective backported kernels (LP: #881529).
[15:29] <CIA-11> debian-installer: cjwatson * r1327 lucid-proposed/ (8 files in 2 dirs): Move to 2.6.32-38 kernels.
[15:30] <CIA-11> debian-installer: cjwatson * r1328 lucid-proposed/ (9 files in 3 dirs): Move maverick-* images to 2.6.35-32 kernels.
[15:32] <CIA-11> debian-installer: cjwatson * r1329 lucid-proposed/build/config/ (8 files in 2 dirs): Move oneiric-* images to 3.0.0-15 kernels.
[15:33] <CIA-11> debian-installer: cjwatson * r1330 lucid-proposed/debian/changelog: releasing version 20081029ubuntu102.13
[15:47] <cjwatson> ev: could you do a fresh wubi build/upload, please?
[15:48] <cjwatson> r255
[15:48] <ev> sure thing
[15:48] <ev> on it now
[15:50] <cjwatson> ta
[15:50] <cjwatson> bdmurray: ^- that should sort out the Lubuntu people
[15:54] <ev> cjwatson: done
[15:55] <ev> how's your one man sprint going? :)
[15:55] <cjwatson> ev: heh.  trying to tick off work items with the rest of you
[15:55] <cjwatson> weird being at home with all you lot in .hu
[15:55] <ev> (I'm not there either, in case that bit of information hasn't made its way to you)
[15:56] <cjwatson> oh!  didn't know that
[15:56] <cjwatson> what happened?
[15:56] <ev> visa renewal
[15:56] <cjwatson> ah
[15:56] <ev> I'm trapped and passportless
[15:56] <cjwatson> you need a spare passport :-)
[15:56] <ev> haha, apparently I'm not allowed to leave the country even if I have a passport from another nation
[15:56] <ev> they've thought of every angle :)
[15:56] <cjwatson> oh, that sucks
[15:57] <ev> yeah, though I'll just be happy once I have everything back and another two years of approval
[15:57] <ev> very pleased to have the mountain of paperwork behind me
[15:58] <cjwatson> I can imagine
[15:59] <cjwatson> so it's heads-down crashdb week then?  you probably get more done without being in Budapest then :)
[16:00] <cjwatson> http://status.ubuntu.com/ubuntu-precise/canonical-foundations.html is scaring me :-/
[16:02] <ev> it is indeed
[16:02] <ev> and yeah, sorry about that. I assigned to the DX team for a week or two before the holiday to help with test infrastructure, then I had that month off.
[16:03] <ev> Caning it through January :)
[16:04] <ev> The reporting daemon is in the archive and has a MIR, and I've been trying to get ahold of James today to see where we stand on the hardware
[16:09] <bdmurray> cjwatson: that page says 'Mail about all bug activity will be sent to the supervisor by default. The bug supervisor can change the bug mail rules to limit the volume of email.'  Do you know if muting the teams subscription will stop email?
[16:11] <cjwatson> bdmurray: not for certain, although I guess it should
[16:17] <bdmurray> cjwatson: okay, I've made bugcontrol the bug supervisor but would like to stay in ubuntu-installer until I know bug mail isn't going to bugcontrol
[16:18] <cjwatson> OK
[16:18] <cjwatson> feel free to follow up with test mail to that wubi/lubuntu bug
[16:30] <bdmurray> cjwatson: was 241 or 245 the final wubi for oneiric? bug 891577
[16:30] <ubot2`> Launchpad bug 891577 in wubi "cannot install ubuntu 11.10" [Undecided,New] https://launchpad.net/bugs/891577
[16:32] <cjwatson> bdmurray: 245, but there was some last-minute stuff going on and I don't think we respun all the images with it
[16:32] <cjwatson> bdmurray: ev might remember better whether that matches what he fixed
[16:33]  * ev tries to recall
[16:45] <ev> confused as to how we're seeing EINVAL on a read call there
[16:47] <ev> bdmurray: outdated version as that may be, I believe there's a real bug there
[16:53] <ev> hm, posix_read only sets EINVAL if the size is less than zero, or if read itself returns EINVAL


[08:25] <dpm> morning
[08:28] <Geochr> good morning
[08:39] <happyaron> morning
[08:40] <happyaron> dpm: any thoughs on opening translation?
[08:45] <dpm> morning happyaron, I just came back from holiday and I'm still catching up. But in summary, yes, it should be time to open them
[08:46] <happyaron> dpm: take you time, I'll wait your email on the topic, and I can do the work if there is a procedure to follow.
[08:46] <dpm> cool


[03:35] <reya276> anyone in?
[03:35] <reya276> I forgot the password for my Daughters PC is there anyway that I can reset it
[03:36] <reya276> I need to ship it to her but I have to update it first and I can't do that without her password
[03:39] <mhall119> !seen tiemonster
[03:39] <ubuntu-fl> mhall119: tiemonster was last seen in #ubuntu-us-fl 8 hours, 24 minutes, and 10 seconds ago: <tiemonster> festival
[03:40] <mhall119> reya276: it's Ubuntu?
[03:40] <reya276> yes
[03:41] <mhall119> boot from a LiveCD, chroot to your HDD, then run passwd
[03:41] <reya276> I  even got a log from an IM conversation to see if it is that but that password is for her Ubuntu one acct not her desktop login
[03:42] <reya276> chroot?
[03:42] <reya276> how do you do that
[03:42] <mhall119> from the command line
[03:42] <mhall119> say you mount your HDD as /media/Disk
[03:42] <mhall119> in your LiveCD session
[03:43] <mhall119> you just open the terminal, type "sudo chroot /media/Disk" and it'll give you a command prompt that acts like you booted from the HDD
[03:43] <mhall119> running "passwd $daughtersusername" from there will let you reset her password
[03:44] <reya276> ok let me try it
[03:45] <reya276> ok how do I mount the CD?
[03:48] <reya276> thanks lets see if I can get this to work
[03:50] <mhall119> boot from the CD
[03:50] <mhall119> then mount your harddrive
[03:51] <reya276> mount the HD then mount the CD
[03:51] <mhall119> no, just boot from the CD to the live session, then mount the HD
[03:51] <mhall119> there's nothing you need to do with teh CD other than boot from it
[03:54] <reya276> oh when I tried doing sudo chroot /media/Disk from the CLI it said "chroot: cannot change root directory to /media/Disk: no such file or directory
[03:56] <mhall119> right, that was an example path
[03:57] <mhall119> you'll need to mount the HDD (double-click it in nautilus), then use whatever path it has
[03:57] <mhall119> it'll probably be /media/something
[03:57] <reya276> ok I did it, thanks
[03:57] <reya276> lets see if I can log in as her
[03:58] <reya276> cool it worked, thanks
[03:59] <reya276> damn this thing does work miracles
[04:27] <mhall119> :)
[04:28] <mhall119> good night
[04:35] <reya276> wait
[04:36] <reya276> how can I find a way to run this package/app called kde-config-tablet?
[07:38] <floridagurl941> hello
[12:57] <mhall119> morning
[15:39] <dantalizing> morning
[15:39] <itnet7> Morning
[15:40] <dantalizing> itnet7:  pm?
[15:40] <itnet7> sure
[16:01] <reya276> morning everyone
[16:03] <dantalizing> morning
[16:05] <dantalizing> so reya276 were you referring to the data-foo tags?
[16:06] <reya276> yes, trying to see if it is an option for us to move to HTML5
[16:07] <dantalizing> like
soemthing

[16:07] <reya276> could we use say a dynamic language such as PHP or Coldfusion8, JSP
[16:08] <reya276> along with this tag
[16:08] <dantalizing> sure ... but they are not inherently associated with any database context.
[16:08] <dantalizing> you can stick whatever you want in those
[16:09] <dantalizing> there is no such thing as a data tag "insert" or "update"
[16:09] <dantalizing> in the database sense of those words
[16:09] <dantalizing> they're literally just tags
[16:09] <dantalizing> but you can definitely use php or whatever to populate them and use then use those tags for your app data
[17:07] <crashsystems> hello world
[17:10] <mhall119> hello crashsystems
[17:13]  * crashsystems <3 Firefox Sync :D
[18:58] <dantalizing> crashsystems: you're not using a manual sync process with my app?? :(
[19:03] <crashsystems> dantalizing: No, I'm using Firefox 4 sync between my personal laptop, work computer and Fennec on my phone.
[19:06] <dantalizing> boo
[19:06] <dantalizing> install it anyway and give it 5 stars
[19:09] <crashsystems> your app is for syncing with the default browser's bookmarks isn't it?
[19:10] <dantalizing> crashsystems: yes
[19:22] <tiemonster> !ping
[19:22] <ubuntu-fl> pong
[19:37] <crashsystems> dantalizing: have you tried Fennec recently?
[19:38] <dantalizing> crashsystems: i tried beta9 iirc and it blew up on me ... i'm assuming i had some cruft from the previous releases, but didnt really follow up
[19:39] <dantalizing> sry beta4
[19:41] <crashsystems> beta5 is the current version. its good enough now to be my main browser on my phone
[19:41] <dantalizing> ah maybe beta5 then
[19:41] <dantalizing> whatever came out a few weeks back
[19:42] <dantalizing> ow 14MB
[19:54] <crashsystems> its performance is actually pretty good considering it's size. Also, flash alone is 10mb, so 14MB for a browser is not bad.
[19:55] <dantalizing> beta4 is in the market and its crashing on me again
[19:55] <dantalizing> :(
[19:56] <crashsystems> hah, don't bother with beta4
[19:56] <dantalizing> well where's beta5
[19:56] <dantalizing> ?
[19:56] <crashsystems> https://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-central-android-r7/en-US/
[19:56] <dantalizing> ah
[19:57] <dantalizing> isnt there an irssi script to save links
[19:57] <crashsystems> ?
[19:58] <crashsystems> I don't use irssi
[19:58] <crashsystems> I would if it had decent spellcheck
[20:02] <dantalizing> you should write a nice little perl irssi spell check script
[20:20] <dantalizing> we should do a florida ubuntu hour in CA in may
[20:20] <dantalizing> zbrown: crashsystems jamalta ^^^^
[22:47] <mhall119> lol


[01:01] !alindeman:*! Happy new year freenodia (Just past midnight freenode standard time)!  We're celebrating in #newyear if you're interested :-)
[08:48] <BradB> elmo: Are you running hoary COTD by any chance? I'd be curious to know if you see the same problem on your Powerbook as I see on mine, after upgrading to the COTD. http://nopaste.snit.ch:8001/1505.
[08:49] <BradB> Caps Lock refuses to behave like Control, even though X is telling me it is.