/srv/irclogs.ubuntu.com/2021/08/17/#ubuntu-devel.txt

guivercbdmurray, lubuntu focal daily (2021-08-16) boots fine on sony_vaio_svp112a1cw; ubuntu zsync keeps falling over but i'll get there.. and I'll add entry on bug report in due course00:25
mwhudsonvorlon: omg is it possibly shim-signed works on arm64 on all releases now? or do we still need it to migrate on bionic?01:15
mardyis there a way for a privileged process (such as snapd) to find the ID of all wayland windows belonging to a certain PID?08:02
schopinRegarding the freeze, what are the rules regarding the packages that are in -proposed at freeze time? Do they need a freeze exception ?09:34
doko_no09:42
=== doko_ is now known as doko
slyonschopin: This would best be asked in #ubuntu-release but from my understanding packages in -proposed are fine and can be migrated after FF (do not need a FFe), they just won't accept anything new into -proposed.10:08
RikMillsmwhudson: qtwebengine fix looks good. it has been uploaded to unstable, and will get synced later12:30
RikMillssync will close the bug12:30
rafaeldtinocosorry.. maybe this was discussed already here but what happened to ddebs.ubuntu.com/dists ?13:08
rafaeldtinocoasking this because all linux-image-XXX-dbgsym files are 15Kb13:13
rafaeldtinocoand dists directory was renamed to dists.old13:14
xnoxddstreet:  laney: forwards the token to juliank.....13:15
ddstreetthanks, laney that's all you needed right?13:20
juliankWe do not have docs for which token is which or how to udpate them13:21
mclemenceau_o/ Hello, I'm looking for a sponsor for a simple merge for lshw (LP: #1939695) before feature freeze? anyone interested ? Thx :)13:22
ubottuLaunchpad bug 1939695 in lshw (Ubuntu) "Please merge lshw-02.18.85-0.7 (main) from Debian unstable (main)" [Wishlist, New] https://launchpad.net/bugs/193969513:22
julianknvm, I was on the wrong page13:23
juliankERROR cannot deploy bundle: processing option "swift-web-credentials" for application "autopkgtest-web": resolving include "/srv/mojo/mojo-prod-proposed-migration/focal/production/local/swift-web-credentials.conf": include file "/srv/mojo/mojo-prod-proposed-migration/focal/production13:23
juliank/local/swift-web-credentials.conf" not found13:23
juliankhorry13:23
ddstreethmm, well i've never had access to the internals of autopkgtest-cloud deployment, i'm unlikely to be able to help with that13:24
julianksil2100: ^ you added include-file for swift-web-credentials.conf to autopkgtest-cloud, but no such secret is provided on prod-proposed-migration13:27
juliankAlso how did Laney deploy this if it's not deployable13:28
sil2100juliank: we never deployed it in production so I guess! I know it has to be available on the staging instance, but I have no knowledge of how that ties to the creds for production13:34
julianksil2100: in any case, it's broken right now, so no github systemd status thingy update13:39
julianksil2100: I'll try to reconstruct it and hope everything works :D13:41
slyonmclemenceau_: o/ I can do that sponsoring.13:44
sil2100Ah! So I see my private-testing branch got merged! Ok, so uh, I can try reading up on how the mojo creds are being stored, possibly moving those over from the staging instance could work13:44
julianksil2100: Copying over doens't work, no, they're separate users13:45
sil2100juliank: ah, you mean the swift user? Yeah, I wonder if we have a user for that for production, hmmm13:52
juliankI don't know what you did and how it related, certainly the password is different than what is stored in swift_password13:53
sil2100Ok, so I see Laney only requested a new swift user for staging, let me request a new user from IS for production13:55
mclemenceau_o/ slyon sure that would be great thank you!14:01
=== genii-core is now known as genii
Guest11I created a simple .deb package as per https://ubuntuforums.org/showthread.php?t=910717 .. I need to print some text as a banner while installing or removing the newly created .deb package, does DEBIAN/control supports this?14:09
Guest11Is it possible to run a set of commands after post-installation or removal of the .deb package?14:10
rbasakGuest11: try #ubuntu-packaging. This channel is for the development of Ubuntu itself.14:15
laneysil2100: ohhhh I forgot that14:28
laneyI thought I saw that mojo succeeded, what did I do14:28
laneynothing good, that's for sure14:29
laneysil2100: also this is the kind of thing that would be documented ;-)14:29
sil2100laney: hah, no worries, I also forgot that we had the user only for staging, not production as well! Somehow in my mind I thought it's one for both14:30
laneyjuliank: just revert the charm to the previous version in the stable channel thing14:30
laneyjuliank: did you revise your opinion of not having docs?14:31
juliankdocs are there14:31
juliankjust in manage/admin thingy, not deploy, but that makes sense I guess14:31
laneynod14:32
laneyinteresting that xnox sent it to you and not me who replied to the thread and was CCed14:32
laneyrecipe for confusion there14:32
sil2100laney: filled in RT: #132557, can you check if what I copy-pasted and edited there makes sense?14:35
laneysil2100: looks good, get it prioritised14:36
cjwatsonrafaeldtinoco: Both dists and (to be ignored) dists.old are present.  linux-image-*-dbgsym are probably not very interesting due to the signed/unsigned split; it looks like you typically want linux-image-unsigned-*-dbgsym14:37
cjwatsonrafaeldtinoco: If that doesn't solve your problem, please be more specific14:37
julianklaney: I've blacked out on the whole charm revert thingy14:38
rafaeldtinococjwatson: it does indeed and thank you cjwatson. I thought signed and unsigned had diff debug packages. thx14:48
laneyjuliank: charm release takes a revision on the end14:52
laneyjuliank: the latest version is 109 so charm release cs:~ubuntu-release/autopkgtest-cloud-worker-10814:53
laneymight be an idea to document that one14:54
julianklaney: gotta look at -web15:00
julianklaney: tags for 55,56,57 are missing15:01
laneyI just pushed 5715:01
laneyam I responsible for those others? :p15:02
julianklaney: I don't know15:02
julianklaney: neither revert helps anyway15:02
laneywhy, hook errors?15:03
laneylet me look a second15:03
julianklaney: i'll try 5415:03
laneyhang on15:04
laneylook in `juju debug-log`, the blooming disk is full15:04
julianklaney: still failing at processing that option / unlucde file15:05
laneywhere are you seeing this?15:05
laneywhen running mojo?15:07
laneyjuliank: ok resolved with a hack, removing the unused lxd snap to free up space15:13
laneymojo was unhappy because the reverted charm doesn't have that config item15:13
julianklaney: as usual, (mojo-prod-proposed-migration)prod-proposed-migration@wendigo:~$15:13
laneyprobably want to reset the checkout there to correspond to 108/56 I guess15:14
laneywe should add constraints to get bigger web machines, 10G is not good15:14
laneylet me do that15:14
laneydone15:15
laneynow we need to ask IS to resize the existing instances to match that, let me do that too15:15
schopindoko: do you have any problem with me fixing the c++17-related errors in log4shib, including its public headers? You added a -std=g++14 flag but the headers cause failures in other packages :-(15:15
julianklaney: if we resize, we should also add a 2nd cpu15:17
juliankthis should get rid of all spikes we have now15:17
dokoschopin, well, I uploaded these other packages as well, so these should be fine now ...15:18
laneyjuliank: good idea, do you want to fix the constraints for that?15:18
laneysee the commit I just made and the constraint syntax of juju15:18
juliankok15:18
* juliank in mth15:18
juliank* meeting15:18
laneyack15:19
dokoschopin, I didn't get to libcifpp and libpdb-redo yet, so that's c++17 stuff as well15:19
dokoschopin, so maybe let the current uploads migrate first before touching them again15:20
schopindoko: you did xmltooling as well?15:21
laneyjuliank: what I don't know is if we `mojo run` now that we changed the constraints, will it notice and decide to add new machines ...15:21
laneywell I guess that's not a bad way to do it really15:21
laneycould hack in there, stop download-all-results, and copy the DB over15:22
laneysecond option if the resize route takes a long time15:22
juliankhmm15:22
dokoschopin, are you subscribed to the impish-changes ML?15:24
schopinup until now I didn't see the point of it except drowning me in mail. I guess I'll start setup some filters then ;)15:25
dokohttps://lists.ubuntu.com/mailman/listinfo/impish-changes15:25
vorlonmwhudson: looks like shim-signed still needs to migrate on bionic...15:31
xnoxlaney:  i lost track of things, sorry.15:44
laneyah well16:07
=== alan_g__ is now known as alan_g
laneyjuliank: ah yay, IS did the migration quickly ♥19:16
laneyonly one core still, sad19:17
mwhudsondbungert, vorlon: thanks for the livecd-rootfs review21:02
dbungertyou bet21:03
mwhudsonschopin, doko: all the autopkgtests still fail though because they are not using -std=c++1421:41
mwhudsoni think patching the source would be a more useful fix21:42
bdmurraymwhudson: The apport autopkgtests are failing with the new glibc fwict due to the gdb fields changing. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/a/apport/20210815_215748_e3421@/log.gz I've a fix for it https://paste.ubuntu.com/p/d6wPQSrdK4/ but wonder if that's best.21:50
jawn-smithIs any core dev available to retry https://autopkgtest.ubuntu.com/request.cgi?release=impish&arch=amd64&package=syncthing&trigger=glibc/2.34-0ubuntu122:01
jawn-smithIt's one of the packages blocking glibc, but it appears to just be a flakey test based on some older test results22:02
bdmurrayjawn-smith: I can do that22:04
jawn-smiththanks bdmurray!22:07
mwhudsonbdmurray: yeah, i mean that patch looks like it would help but as usual i have to ask "what is this test testing"?22:14
bdmurraymwhudson: I'm not entirely sure but _validate_gdb_fields is used in almost every test22:15
mwhudsonbdmurray: yeah so i've looked at the code and i'm still not really sure what it's trying to do22:54
mwhudsonbdmurray: does anything else read the Stacktrace field or is it mostly for humans to read?22:55
bdmurraymwhudson: ah, that's a good question so apport generates a StacktraceTop and StacktraceAddressSignature from the Stacktrace23:00
mwhudsonbdmurray: so viewing this as an integration test, it is kinda important that we find out if gdb changes output in a way that breaks crash_signature_addresses23:02
mwhudsonbdmurray: but i'm not sure anything is really testing that?23:04
mwhudsonall the tests of crash_signature_addresses i'm seeing use canned input23:04
mwhudson(which makes sense for a unit test, of course)23:04
bdmurrayokay, I'll keep digging23:07
mwhudsonthanks23:07
mwhudsoni think if we can convince ourselves the signatures are still ok in the current state of impish-proposed, your patch is fine23:07

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!