UbuntuIRC / 2020 /05 /11 /#ubuntu-devel.txt
niansa
Initial commit
4aa5fce
=== Guest806 is now known as Woodpecker
=== Woodpecker is now known as Guest84182
=== helio|afk is now known as heliocastro
=== juergh_ is now known as juergh
=== ebarretto_ is now known as ebarretto
[08:52] <ackk> xnox, hi question about maas transitional deb. we're considering dropping it entirely in groovy, given that users will be migrated to the snap. is that acceptable, or does it have to be demoted to universe first?
[09:02] <xnox> ackk: open an RM bug report in launchpad, subscribe ubuntu-archive and let it be gone.
[09:03] <ackk> xnox, cool, thanks
[09:15] <ackk> xnox https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1877973 FTR
[09:15] <ubottu> Launchpad bug 1877973 in maas (Ubuntu) "RM request - removal from archive" [Undecided,New]
=== cpaelzer__ is now known as cpaelzer
[12:52] <cpaelzer> paride: you wrote on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1877575 that this happens with focal live-server as well
[12:52] <ubottu> Launchpad bug 1877575 in qemu (Ubuntu) "kernel crash with 0010:ovl_open_realfile+0x4a/0x150 [overlay] in Qemu with focal daily" [Critical,Confirmed]
[12:52] <cpaelzer> paride: does it crash the guest or the host?
[12:55] <paride> cpaelzer, it's the guest that crashes
[12:56] <cpaelzer> paride: while looking at that - is it concerning that on http://cdimage.ubuntu.com/ubuntu-server/daily-live/current/ the most recent arm64 image is of 2019-11-04 07:40 ?
[12:59] <paride> cpaelzer, the pending->current promotion script did certainly run on much newer images
[12:59] * paride checks
[13:03] <paride> cpaelzer, well I think we shouldn't have focal images at all in that location
[13:03] <paride> sil2100, what do you think? ^^
[14:42] <rbasak> paride: around? May I have some help/advice with a git-ubuntu release task please?
[14:43] <paride> rbasak, yes, 1 minute as I finish replying to a bug
[14:48] <paride> rbasak, available when you want
[14:49] <rbasak> paride: I just realised that it might take far too long to type and explain. To save time, do you have time now to join a hangout? Maybe my squad's daily standup?
[14:49] <paride> rbasak, joining
=== snowwy is now known as Snow-Man
[15:45] <paride> rbasak, standups done, looking into the job
[15:49] <rbasak> Thanks! Let me know if you need anything
[16:14] <paride> rbasak, the git-ubuntu-ci-nightly job now has a parameter to specify which branch/tag to checkout
[16:14] <paride> I'm testing it with the default settings (master)
[16:14] <rbasak> Thank you!
[16:14] <paride> rbasak, once it's done you can try with the tag you want to release
[16:15] <rbasak> Will do
[16:15] <paride> https://github.com/canonical/server-jenkins-jobs/pull/119 <- to be merged if everything works
[16:19] <rbasak> bryce: ^ just FYI - that's for a 0.10.1 release as it's the first time we're releasing from not-master.
[16:19] <bryce> rbasak, ok
[16:19] <rbasak> I'll update the doc
[16:20] <bryce> rbasak, is this new policy or just for the 1.0?
[16:21] <rbasak> bryce: it's just the means to get a build if master isn't on the release tag. I suppose we could change the procedure to always do that in order to make the process simpler.
[16:46] <rbasak> paride: your build succeeded, so I'll start one now against the release tag.
[16:46] <rbasak> Oh. The "Build Now" button didn't ask me for parameters.
[16:52] <smoser> whats the correct way to ask for a git-ubuntu import ?
[16:52] <ahasenack> smoser: here is fine
[16:52] <smoser> i'm interested in sbuild-launchpad-chroot
[16:54] <ahasenack> let me run that
[16:56] <ahasenack> rbasak: is it ok to import that now, given your g-u work, with what is running on the importer nodE?
[16:59] <ahasenack> rbasak: I'll run it
[17:03] <ahasenack> smoser: it's imported now
[17:03] <ahasenack> smoser: I also committed a change so it's whitelisted from now on, but to have that effective requires a new deployment of the importer, which doesn't happen all the time
[17:03] <ahasenack> in other words, ping me if it's out of date
[17:04] <smoser> ahasenack: k. thank you
[17:05] <rbasak> ahasenack: yes, that was fine
[17:05] <ahasenack> ok
[17:06] <rbasak> ahasenack: in general, if the service is running, then it's safe to do a manual import also. If it is not, then I'm messing with it and it's not.
[17:17] <rbasak> paride: git-ubuntu-ci-nightly seems to still have a "Build Now" button but I'm expecting a "Build with Parameters" button. Any ideas?
[17:17] <rbasak> The git-ubuntu-ci job is an example of one that has "Build with Parameters"
[17:19] <paride> rbasak, yes, the new job definition got overwritten by the auto-deploy job
[17:20] <rbasak> Ah. That would explain it!
[17:20] <paride> rbasak, now it has "build with parameters" again
[17:20] <rbasak> It was very puzzling :)
[17:20] <rbasak> Thank you!
[17:20] <rbasak> I've started a job for 1.10.1. Let's see.
[17:21] <rbasak> I hope aborting the previous job didn't break anything.
[17:21] <paride> it shouldn't
[17:44] <paride> rbasak, wrong tag?
[18:35] <rbasak> paride: :(
[18:35] <rbasak> paride: I've retried with the right one (I hope!)
=== ben_r_ is now known as ben_r