[02:57] <stgraber> doko: I still use it on my servers, so just did a quick and dirty port to python3, uploaded now
[02:57] <stgraber> (seemed lesswork than figuring out a replacement for it)
[07:15] <CarlFK> focal - wifi weirdness http://paste.ubuntu.com/p/g5xD775kfN/  zgrep wlo1 syslog.2.gz | grep -A 500 1585626648
[07:15] <CarlFK> if I should bug this, what package?
[07:17] <CarlFK> shucks - my grep didn't catch gnome-shell[1232]: An active wireless connection, in infrastructure mode, involves no access point?
[07:22] <cpaelzer> rbasak: I saw no update on https://bugs.launchpad.net/ubuntu/+source/openjade/+bug/1869734 did this review get stuck on your side and can I do anything to help?
[07:22] <cpaelzer> I could share a login to a test system if something like that is what you are looking for
[09:03] <jamespage> cpaelzer: spend an hour with spice-html5 + websockify and libvirt - all hangs together fine with the new revisions and does what is required so I've updated the MIR and uploaded the 0.2.2 release referencing the MIR to focal
[09:03] <jamespage> the delta was not very big tbh
[09:33] <rbasak> cpaelzer: sorry. I had given you a +1 on IRC
[09:36] <cpaelzer> rbasak: now I understand
[09:36] <cpaelzer> rbasak: for the auth trail coudl you do on the bug as well?
[09:36] <cpaelzer> juts one line is enough
[09:36] <rbasak> Sure
[09:37] <cpaelzer> thanks, it also helps me to do it when I get back to the case
[09:39] <cpaelzer> jamespage: thanks, re-checked and Ack'ed
[09:39] <cpaelzer> on the bug
[10:00] <jamespage> cpaelzer: thanks
[11:59] <arunpyasi> Hi everyone, which script is responsible for creating user for live cd?
[11:59] <arunpyasi> *script/package
[12:50] <RikMills> juliank: libqapt is about to get a new upstream release. would you be able to confirm that all apt porting required for focal is in that?
[12:50] <RikMills> https://cgit.kde.org/libqapt.git/log/
[12:51] <juliank> RikMills: you'll see if it compiles?
[12:51] <RikMills> juliank: lol. ok
[13:06] <juliank> Anyone has more insight into DST and bug 1824088?
[13:07] <juliank> I have a simple workaround for daily intervals: Instead of comparing time at midnight for 24 hour difference, compare the dates
[13:07] <juliank> https://salsa.debian.org/apt-team/apt/-/merge_requests/115/diffs
[13:07] <juliank> But that does not really help anyone else
[13:07] <juliank> I'm unsure if there's a more sensible solution
[13:08] <juliank> OTOH, people can (and should) override the systemd timer executions
[13:15] <juliank> Figuring out how many days have passed-ish is hard
[14:19] <Saviq> doko: hey, https://github.com/capnproto/capnproto/issues/962 fixes https://bugs.launchpad.net/ubuntu/+source/capnproto/+bug/1870055 - how would you suggest I proceed?
[14:19] <Saviq> we're now out of sync with Debian due to the no-change rebuild, but would we even accept a sync from Debian at this stage?
[14:23] <seb128> Saviq, depend of the content of the change, a sync is not different from an upload, it's a diff to review
[14:23] <seb128> there is no rule against syncing :)
[14:34] <doko> Saviq: please forward to debian, and upload to ubuntu. we can re-sync it later
[14:44] <seb128> doko, thanks for filing those ftbfs bugs but no need to both for desktop ones, we do look at results and handle problems in our set so you can spare some work if you prefer...
[15:16] <Saviq> doko: I don't have the rights to upload to archive, shall I upload to a PPA?
[15:32] <doko> Saviq: or paste a debdiff
[15:40] <Saviq> doko: https://paste.ubuntu.com/p/f8YRsNC8sk/
[15:45] <doko> Saviq: uploaded
[16:06] <AsciiWolf> kenvandine, hi, I have noticed small typo: https://gitlab.gnome.org/Community/Ubuntu/gnome-software/-/commit/4cde4f1cbcc7c0a17ec1442314ee97885416b1df#d490cae4d945759dee37cd8a461857f050b1ec11_13_12
[18:52] <jwallden> Hello. I'm a bit confused around Ubiquity installer. I'm trying to fully automate the install and thought I would give kickstart a go. But does Ubiquity support kickstart installation?
[18:55] <sarnold> jwallden: take a look at this, see if it helps https://discourse.ubuntu.com/t/cloud-init-and-the-live-server-installer/14597
[18:59] <CarlFK> jwallden: this might help - 20 min, minimal effort on your part https://debconf-video-team.pages.debian.net/ansible/usb_install/usb_quick_start.html
[19:00] <juliank> CarlFK: please don't
[19:00] <CarlFK> juliank: why not?
[19:01] <juliank> CarlFK: It boots into legacy installer
[19:01] <juliank> CarlFK: jwallden is interested in ubiquity, not the legacy server installer
[19:01] <juliank> sarnold: that's for subiquity, not ubiquity
[19:02] <juliank> jwallden: you're interested in the desktop, right?
[19:02] <jwallden> Im sorry. Maybe I should mention that i I'm trying to automate install for Ubuntu Desktop
[19:02] <sarnold> juliank: apparently I'm confused about our installers too :)
[19:02] <CarlFK> juliank: might be interested in fully automate the install and doesn't care which path
[19:02] <juliank> jwallden: Well, ubiquity is desktop, but it's only a typo away from subiquity :)
[19:02] <jwallden> What is subiquity then?
[19:03] <juliank> CarlFK: I don't think setting up an automated install that will stop working after 20.04.0 is a reasonable suggestion
[19:03] <juliank> jwallden: subiquity is the server installer, like server ubiquity :)
[19:03] <CarlFK> juliank: I bet it will keep working
[19:03] <jwallden> Aha! Ok ok
[19:04] <jwallden> Im trying to remaster a Desktop image (19.10 atm) and would very much like to automate the install
[19:05] <jwallden> Tried preeseeding but didn't get it to work so thought I should try kickstart, as it seems simpler
[19:05] <juliank> I think both should work
[19:05] <juliank> but I'm not sure
[19:05] <CarlFK> jwallden: I did some remaster things. found it much easier to start with a minimal installer and apt install / ansible  the additional packages way easier to work with
[19:07] <CarlFK> jwallden: again, 20 minutes, mostly watching bytes move to and from a usb stick.  and yes, it may break in the future, and then I'll fix it.
[19:07] <juliank> You won't be able to fix it once we stopped building d-i
[19:08] <CarlFK> juliank: yes I will.
[19:09] <juliank> sigh
[19:09] <jwallden> When was Ubiquity introduced?
[19:09] <juliank> In 2006
[19:09] <juliank> in 6.06
[19:10] <jwallden> Aha.
[19:11] <juliank> ubiquity embeds a lot of d-i, the debian-installer, so shares most of the preseeding config
[19:12] <jwallden> CarlFK: Thanks for the tip. But I think I'll need something more "basic" and, that is working in the future as well :)
[19:12] <CarlFK> jwallden: it is pretty basic, and it will keep working.  it isn't that hard to switch
[19:13] <CarlFK> jwallden: and I assure you , it it way easier to work with a rw filesystem than building an image, and then later updating that image when it stops working
[19:13] <jwallden> Mmm, I'll think about it
[19:14] <CarlFK> jwallden: easier to run the script
[19:14] <CarlFK> less debating, more trying stuff
[19:15] <juliank> We told people 2 (?) years ago the d-i images are going away, and we're stopping building udebs
[19:15] <juliank> It did not really make it this cycle, but this is no reason to tell people to continue to use it
[19:16] <CarlFK> juliank: di is only a part of it.  the yml version is like 1 line.
[19:16] <CarlFK> juliank: you should try it ;)
[19:17] <juliank> I'm not sure what you're talking about
[19:17] <CarlFK> https://debconf-video-team.pages.debian.net/ansible/usb_install/usb_quick_start.html
[19:17] <jwallden> But CarlFK, what system does that create? Debian?
[19:18] <CarlFK> jwallden: default is debain, ubuntu if you set a setting
[19:18] <juliank> What you should do is preseed ubiquity, and then maybe if you want to, you might as well run ansible in the target
[19:19] <juliank> Modifying the live image is another approach, but not recommended or supported
[19:20] <juliank> (for desktop)
[19:20] <jwallden> Yep, Ansible is definitly in the stew :D
[19:21] <jwallden> I guess I have to try some more with preseed
[19:21] <juliank> Now, I guess the documentation for preseeding ubiquity is a bit suboptimal
[19:21] <jwallden> Yeah, could be improved
[19:22] <juliank> Another alternative, for multiple systems, is to install one of them (in OEM mode, possibly), and then create an image and copy that to the other machines, I guess
[19:23] <CarlFK> gross
[19:23] <jwallden> Haha
[19:23] <jwallden> Well, a bit hacky at least :)
[19:23] <jwallden> I'll rather do the preeseed thing.
[19:24] <CarlFK> jwallden: don't say preeseed, that gets people riled up
[19:24] <juliank> preesed
[19:24] <juliank> :D
[19:24] <CarlFK> juliank: what is the new thing called, that uses yaml ?
[19:24] <juliank> CarlFK: subiquity I guess uses yaml, via curtin and cloud-init
[19:25] <juliank> subiquity is the "live" server installer
[19:25] <cjwatson>  and we're stopping building udebs
[19:25] <rafaeldtinoco> bdmurray: ping. could u review 2 srus for me today ?
[19:25] <cjwatson> oops
[19:25] <cjwatson> sorry, mispaste
[19:25] <juliank> curtin is the backend of the installer
[19:25] <rafaeldtinoco> bdmurray: the merge requests have a good review from cpaelzer already to help
[19:25] <juliank> and cloud-init configures the server on first boot
[19:25] <juliank> I think
[19:26] <CarlFK> d-i consumes a pressed file.  subiquity consumes a .. what do you call this file?
[19:26] <juliank> CarlFK: I think it's an autoinstall file?
[19:27] <bdmurray> rafaeldtinoco: which SRUs?
[19:27] <juliank> e.g. https://github.com/CanonicalLtd/subiquity/blob/master/examples/autoinstall.yaml
[19:27] <rafaeldtinoco> bdmurray: 1) https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1866119
[19:27] <rafaeldtinoco> bdmurray: 2) https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1865523
[19:28] <rafaeldtinoco> this will enable Bionic to be an option for Azure new shared-disk feature.
[19:28] <rafaeldtinoco> (allowing fence-scsi to work there, as it was completely broken)
[19:28] <juliank> CarlFK: More info here: https://wiki.ubuntu.com/FoundationsTeam/AutomatedServerInstalls
[19:32] <kenvandine> AsciiWolf: thanks, i commented there.  Basically it's correct.
[19:32] <kenvandine> AsciiWolf: thx for checking though
[19:36] <CarlFK> this might matter:  "when the answer to a question is not present in a preseed, d-i stops..."   that isn't exactly true - d-i has lots of defaults baked in.
[19:36] <CarlFK> ^^ https://wiki.ubuntu.com/FoundationsTeam/AutomatedServerInstalls
[19:41] <CarlFK> d-i will still be in 20.04 ?
[19:50] <bdmurray> rafaeldtinoco: so we can use the block-proposed-bionic tag to keep fence-agents in -proposed longer
[19:51] <rafaeldtinoco> great! I'd say 15 days at least!
[19:55] <bdmurray> rafaeldtinoco: what is the relationship between these packages should the dependency be versioned?
[19:58] <rafaeldtinoco> bdmurray: i didnt want to enforce the dependency
[19:58] <rafaeldtinoco> but we thought about it during the review
[19:59] <rafaeldtinoco> pacemaker fix is independent of the fence-agents either way but we didnt want to add delta for the dependency
[19:59] <rafaeldtinoco> iirc
[20:26] <rafaeldtinoco> bdmurray: thanks a lot for the review
[20:26] <rafaeldtinoco> i know these were big :\
[20:42] <juliank> CarlFK: it likely will be mostly available on 20.04.0, but won't receive updates for point releases
[20:42] <juliank> I'm not sure if and which images we stop producing before 20.04.0
[20:43] <juliank> but they'll change URL locations for 20.04.0 and that will be the last round of d-i built
[21:11] <CarlFK> on a stock usb desktop interactive installer install, I am having odd wifi issues.  is this the place or #ubuntu+1?  or log a bug against nm because that is my best guess