/srv/irclogs.ubuntu.com/2021/05/07/#snappy.txt

mborzeckimorning06:07
zygagoood morning06:25
* zyga is back after the long weekend06:25
mardyhi all :-)06:57
mardymborzecki: do you think I can merge https://github.com/snapcore/snapd/pull/10245? I cannot understand if the spread failures are related to my changes or not06:58
mupPR #10245: cmd/snap: exit normally if "snap changes" has no changes <Created by mardy> <https://github.com/snapcore/snapd/pull/10245>06:58
mborzeckimardy: hey, let me look at the spread logs07:00
mborzeckimardy: looks like it was store issues, so i've restarted the tests workflow07:01
pstolowskimorning07:02
mborzeckimardy: oh, and it's only possible to merge if the required workflows are successful07:02
mborzeckipstolowski: hey07:02
mupPR snapd#10250 opened: interfaces/camera: allow devices in /sys/devices/platform/**/usb* <Created by tsunghanliu> <https://github.com/snapcore/snapd/pull/10250>07:24
zygahey pstolowski, mborzecki07:36
mborzeckizyga: hey, back from vacation?07:36
zygayep07:36
pstolowskihey zyga07:36
zygaperfect for the one day of work left :D07:36
mborzeckihaha, yeah friday is a good choice of a day to start your work week with07:41
mardydegville: hi, I'm not sure you are the right person for this topic, but after reading https://snapcraft.io/docs/base-snaps it's still not clear to me what core and core16 are (and how they differ)07:41
zygamardy core and core16 are the same07:46
zygacore is the initial base snap07:46
zyga(nee ubuntu-core)07:46
zygacore16 never happened, it was supposed to be core without snapd07:46
zygalike core18 was07:46
mardyzyga: mmm... thanks. https://snapcraft.io/docs/glossary explains them a bit better, but says that core16 is still in development (which somehow sounds to me it's something new)07:48
zygait's not really07:49
zyganot a priority07:49
zygacore is good enough07:49
zygacore16 may never happen07:49
mardyand core18, does it ship snapd?07:50
zyganope07:50
zygathat's the entire point07:50
zygasnapd is a separate snap07:50
zygaso many possible bases can use it07:50
mardymmm... so, the reason why "core" ships snapd, is that because "core" is more than a base snap, but rather a complete OS?07:51
mardyI hope I'm not shaming myself with silly questions :-D07:51
zygacore is the initial base snap07:52
zygaso it was easier to start with one image that has everything except for the kernel and bootloader07:52
zygaover time, it was clear this is not maintainable07:52
zygaso core18 was different07:52
zygaat the time we hoped to make core16 but we never managed to07:52
zyga(no time)07:52
zygahaving core16 might have allowed us to transition everyone to base+snapd model and simplify some code07:53
mardyI see. So "core" is kind of not recommended anymore?07:53
zygabut this never happened and it would also require epochs to really work07:53
zygaand those were not implemented at the time07:53
zygaso no code/complexity saving was possible07:53
zygacore is just old, most people are much better off with core18 or core2007:53
zygacore is derived from ubuntu 16.0407:53
mardygot it, now it's more clear, thanks :-)07:54
zyga(epochs would allow us to remove support code from snapd and force everyone through a version of snapd that still supports both core and the new core16 and upgrade before going to a revision that would no longer understand core as a snap)07:55
zygacheers :)07:55
zygait's possible now but I don't think it's realistically going to happen07:55
degvillemardy: I'm definitely the right person, and it's great you're bringing these things up - it's really valuable. I'll try and clear up the core core16 confusion. It's actually something I'm touching on with the end of standard support for 16.04, but it's never been clear.08:13
zygahey degville :-)08:13
degvillehello zyga!! lovely to see you! :)08:13
zygait's been a while :)08:15
mardymborzecki: after re-running the CI, more tests are passing, but threre's still some required test failing. Should I just keep retrying?08:19
mardyhttps://pipelines.actions.githubusercontent.com/xS8oSnypZkPEQZqiZgDaRp2kdvQJKbOY08TesHp7E8vn7g4hYR/_apis/pipelines/1/runs/25434/signedlogcontent/7008:21
mborzeckimardy: nah, it looks ok, that failure in snap-advise is related to snap store returning 403 unexpectedly08:22
mborzeckimardy: i've pinged mvo and pedronis to land the PR, they are the only ones with github permissions who can land prs into master when required systems failed the test workflow08:23
mardymborzecki: thanks08:31
mardyone more question: is "privileged interface" a synonym for "interface with auto-connect=no"?08:33
pedronismborzecki: hi, should https://github.com/snapcore/snapd/pull/9005 be closed?08:36
mupPR #9005: boot: support setting extra command line argument, bootloader interface tweaks <UC20> <⛔ Blocked> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/9005>08:36
mborzeckipedronis: ah, thanks, i've closed it now08:37
mardydegville: when I'm in https://snapcraft.io/docs/process-for-aliases-auto-connections-and-tracks and click on the "@reviewers" link, I get to a 404. Is there a way to report such issues, or is it fine if I just ping you?08:37
mupPR snapd#9005 closed: boot: support setting extra command line argument, bootloader interface tweaks <UC20> <⛔ Blocked> <Created by bboozzoo> <Closed by bboozzoo> <https://github.com/snapcore/snapd/pull/9005>08:39
degvillemardy: it's absolutely fine to ping me. But (for reference), as everything's published on the forum, you can edit and write things directly my following the link to the forum post at the bottom. We don't typically have a formal process as I try to track edits.08:40
degvilles/my/by08:40
mardydegville: ok, then I can try to fix this myself. Just I'm not sure what is the correct link for the reviewers group :-)08:42
degvillemardy: I've fixed it. That's a weird one as it's forum-specific.08:43
degvillemardy: updates can take a few minutes to propagate to the docs site, but it's done automatically.08:44
mupPR snapd#10245 closed: cmd/snap: exit normally if "snap changes" has no changes <Created by mardy> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/10245>08:44
zygagood morning mvo08:56
mvogood morning zyga !08:57
mardypstolowski: Hi! Can you please re-review https://github.com/snapcore/snapd/pull/10242?09:43
mupPR #10242: overlord: fix errors reported by linter <Created by mardy> <https://github.com/snapcore/snapd/pull/10242>09:43
pstolowskimardy: sure09:43
pstolowski+1, thank you09:46
mupPR snapd#10226 closed: interfaces/udisks2: Allow access to the login manager via dbus <Created by alexmurray> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/10226>11:20
mardythis is up for early feedback: https://github.com/snapcore/snapd/pull/1025111:23
mupPR #10251: interfaces/builtin: introduce raw-input interface <Created by mardy> <https://github.com/snapcore/snapd/pull/10251>11:23
mardyand to see if someone has any suggestion on which snap I could use as a starting point to test this interface11:24
mupPR snapd#10251 opened: interfaces/builtin: introduce raw-input interface <Created by mardy> <https://github.com/snapcore/snapd/pull/10251>11:25
mupPR snapd#10252 opened: boot: reseal given keys when the respective boot chain has changed <Needs Samuele review> <Run nested> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/10252>12:10
mupPR snapd#10253 opened: boot: helpers for manipulating current and good recovery systems list <Run nested> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/10253>12:10
pstolowskire12:29
mupPR snapd#10254 opened: [RFC] overlord/devicestate: tasks for creating recovery systems at runtime <Skip spread> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/10254>12:30
=== dob1_ is now known as dob1
mardyit's me again :-) I've made a snap of libinput's debug-events tool, I installed it in --devmode, and I see these messages in the log: https://paste.ubuntu.com/p/QTTDvMrxmB/13:47
mardyI understand the last two, but why all the network ones?13:47
mardyare they really required, in order to talk to udevd?13:47
mupPR snapd#10250 closed: interfaces/camera: allow devices in /sys/devices/platform/**/usb* <Created by tsunghanliu> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/10250>14:00
mupPR snapd#10255 opened: tests/nested/core/core20-create-recovery: verify that recovery system can be created at runtime <Run nested> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/10255>14:15
* cachio lunch15:05
ijohnsoncachio: can you take a look at #10099 again when you have a chance?16:42
mupBug #10099: paul: new changes from Debian require merging <Ubuntu:Fix Released by cjwatson> <https://launchpad.net/bugs/10099>16:42
mupPR #10099: tests/main/snapd-snap: build the snapd snap on all platforms with lxd <Test Robustness> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/10099>16:42
mupPR snapd#9477 closed: tests/lib/fakestore: some improvements for testing console-conf things <Created by anonymouse64> <Closed by anonymouse64> <https://github.com/snapcore/snapd/pull/9477>16:46
mupPR snapd#9396 closed: snapstate/check_snap: add snap_docker to shared system-usernames <Needs security review> <⛔ Blocked> <Created by anonymouse64> <Closed by anonymouse64> <https://github.com/snapcore/snapd/pull/9396>17:06
mupPR snapd#9701 closed: snapcraft.yaml: allow configuring the snapd snap build via dev options files <Needs Samuele review> <Skip spread> <⛔ Blocked> <Created by anonymouse64> <Closed by anonymouse64> <https://github.com/snapcore/snapd/pull/9701>17:06
mupPR snapcraft#3519 opened: requirements: correct setup.py install_requires and add tooling to freeze reqs <Created by cjp256> <https://github.com/snapcore/snapcraft/pull/3519>17:14
cachioijohnson, left few questions there17:17
ijohnsoncachio: thanks let me take a look17:17
cachioijohnson, do we need also to run snapcraft clean?17:18
cachiofrom the project path17:18
ijohnsonhmm, yeah probably not a bad idea to run snapcraft clean too17:18
cachioI mean, which is hte pwd when we run a command through defer17:19
ijohnsonyeah let me think about this, I think the main reason I used $PROJECT_PATH as the pwd for tests.cleanup was because it's awkward to change dir in the command we use with `tests.cleanup`17:19
cachiolet me make a quick test17:22
cachioto check that17:22
cachioI supose that just on restore is needed17:22
cachioI think the CD PROJ... needed is in restore17:23
cachioit is where we call tests.cleanup restore17:24
cachiothere the deferred commands are executed17:24
cachioijohnson, looking the code, I think we could avoid prepare and restore17:25
cachioit could be an improvement for tests cleanup17:25
mupPR snapd#10247 closed: tests: update spread url <Run nested> <Simple 😃> <Created by sergiocazzolato> <Merged by sergiocazzolato> <https://github.com/snapcore/snapd/pull/10247>19:06
mupPR snapd#10256 opened: snapstate: do not allow installing the same snap revision via IntallPath <Created by mvo5> <https://github.com/snapcore/snapd/pull/10256>20:31
mupPR snapd#10257 opened: tests: remove old fedora systems from tests <Simple 😃> <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/10257>21:01

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