[01:57] <mup> PR snapcraft#3887 opened: store: support status for an onprem store <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/3887>
[06:53] <mup> PR snapd#12059 closed: packaging/*/tests/integrationtests: reload ssh.service, not sshd.service <Created by vorlonofportland> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/12059>
[06:58] <mup> PR snapd#12058 closed: overlord: allow seeding in the case of classic with modes system <Created by alfonsosanchezbeato> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/12058>
[07:43] <mup> PR snapd#12079 opened: multiple: move arguments for auth.NewUser into a struct (auto-removal 1/n) <Created by Meulengracht> <https://github.com/snapcore/snapd/pull/12079>
[07:44] <eoli3n> Hi
[07:44] <eoli3n> mardy, testing is snapd.socket is ready is not enough
[07:44] <eoli3n> https://0x0.st/o90z.txt
[07:45] <eoli3n> https://0x0.st/o90i.txt
[07:53] <eoli3n> I can install a snap package in a chroot during os deployment
[07:53] <eoli3n> so i differ it at startup
[07:53] <eoli3n> and now i can't even install a pacakge at startup
[07:53] <eoli3n> guys
[07:53] <eoli3n> seriously ??
[07:53] <eoli3n> s/can/can't
[07:54] <eoli3n> my playbook is 500 tasks
[07:54] <eoli3n> it plays with a lot of packages, configurations, daemons
[07:54] <eoli3n> no other tools is problematic
[07:55] <eoli3n> the only problem is snap
[07:55] <eoli3n> snap and snap again
[08:13] <mup> PR snapd#12080 opened: overlord: track security profiles for non-active snaps <Bug> <Created by pedronis> <https://github.com/snapcore/snapd/pull/12080>
[08:18] <eoli3n> if i test on snapd.service instead of socket, it seems to wait without end
[08:19] <eoli3n> ok, does snapd depend on graphical.target ?
[08:19] <eoli3n> it would be very funny
[08:24] <eoli3n> mardy i run ansible-pull before lightdm service
[08:25] <eoli3n> it seems that snapd service is never ready before lightdm
[08:25] <eoli3n> i can't identify the constraint
[08:25] <eoli3n> but if i pkill ansible-pull then lightdm shows up and snapd becomes instantly ready
[08:25] <eoli3n> probleme is that ansible-pull needs snapd to be ready to be able to install packages
[08:30] <eoli3n> lets move firefox install to flatpak too. Then i remove snapd, that shit is simply not working
[08:33] <lissyx> eoli3n, you might hit more problem with flatpak
[08:33] <eoli3n> i don't have any problem with any flatpak
[08:33] <eoli3n> i install many
[08:34] <lissyx> I mean the firefox one
[08:34] <eoli3n> maybe, but at least i can install it
[08:34] <eoli3n> automate the deployment*
[08:34] <lissyx> I have not followed what issues you have with it
[08:35] <lissyx> just warning you that you might end up with bugs that are fixed on snap
[08:35] <eoli3n> huhu
[08:35] <eoli3n> i hear it as a troll
[08:36] <lissyx> ?
[08:36] <eoli3n> what kind of problem do you talk about for exemple ?
[08:36] <lissyx> I have no example
[08:36] <eoli3n> that's what i talk about
[08:37] <eoli3n> "bugs that are fixed on snap" : no exemple then ?
[08:37] <eoli3n> because i can tell you much bugs that snap introduce that flatpak doesn't have
[08:38] <eoli3n> choose your hand
[08:38] <lissyx> eoli3n, this is not constructive
[08:38] <eoli3n> what is not constructive ? 
[08:38] <eoli3n> i explained ealier what are my problem
[08:38] <eoli3n> s
[08:38] <lissyx> I'm actively working on fixing firefox/snap 
[08:38] <lissyx> I dont have time to also focus on flatpak
[08:39] <lissyx> so I am saying it is possible some issues due to running into those environemnt might have been fixed on Snap and not on Flatpak
[08:39] <eoli3n> saying that much work has been done on firefox snap package without beeing able to give at least one example is not constructive too
[08:39] <eoli3n> possible yes
[08:40] <lissyx>  eoli3n https://bugzilla.mozilla.org/showdependencytree.cgi?id=1665641&hide_resolved=0
[08:40] <eoli3n> but i can't even deploy firefox package with ansible-pull on my 800 hosts
[08:40] <lissyx> I'll let you go through it?
[08:40] <lissyx> there are still way too many issues, but so much we can't reproduce and investigate ...
[08:40] <eoli3n> huhu, my guess is that most of those bugs are introduced by the snapd architecture
[08:40] <eoli3n> that flatpak doesnt even hit
[08:41] <lissyx> maybe
[08:41] <lissyx> maybe not
[08:41] <eoli3n> maybe is the word yes
[08:41] <lissyx> there are quite some that are reported on both sides.
[08:41] <lissyx> and how many for which we dont know because there's so much less users of flatpak
[08:41] <eoli3n> i'm not into downing snaps for pleasure
[08:41] <eoli3n> i would use firefox snap package
[08:42] <eoli3n> but i'm migrating my infrastructure to ubuntu 22.04, and i need it to be done in next 5h
[08:42] <eoli3n> then i hit the ultime snapd problem
[08:42] <eoli3n> i can't install them with ansible-pull 
[08:42] <lissyx> I was just mentionning that if your problem is deployment, you might want to verify first the level of stability of the flatpak
[08:42] <lissyx> maybe you will discover it is more broken than then snap for your usage
[08:43] <eoli3n> i had the same problem 2 years ago with chromium
[08:43] <eoli3n> apt install chromium resulted in snap install chromium
[08:43] <eoli3n> and the same story 
[08:43] <eoli3n> impossible to run chromium with nfs mounted home
[08:43] <lissyx> is this unfixable by design ?
[08:44] <eoli3n> lot of time and work both side with snapcraft and finally moved to flatpak
[08:44] <eoli3n> never had a problem with it
[08:44] <lissyx> but maybe there are more people fixing chromium's flatpak
[08:44] <eoli3n> the problem is not chromium, it is snap
[08:45] <lissyx> https://bugzilla.mozilla.org/showdependencytree.cgi?id=1278719&hide_resolved=1
[08:45] <lissyx> flatpak meta bug
[08:45] <eoli3n> 224 versus 54
[08:46] <lissyx> notice the hide_resolved=
[08:46] <lissyx> https://bugzilla.mozilla.org/showdependencytree.cgi?id=1665641&hide_resolved=1
[08:46] <lissyx> current state is 68 to 54
[08:46] <eoli3n> it looks like systemd versus runit for exemple
[08:46] <eoli3n> snapd is overcomplex, that is the failure
[08:47] <eoli3n> more complexity had more bugs
[08:47] <eoli3n> that's subjective
[08:48] <eoli3n> anyway, if someone shows up here to help me to solve that ansible deployment problem, i would stick with firefox on snap
[08:48] <eoli3n> as is, i just can't deploy it so...
[08:49] <lissyx> eoli3n, two minutes on the list, already three bugs that are just dupes from the snap work as well
[08:50] <lissyx> https://bugzilla.mozilla.org/show_bug.cgi?id=1764700
[08:50] <lissyx> reported against flatpak, same root cause as of the snap report, it's not because of snapd
[08:50] <lissyx> eoli3n, if you are really in a deadend, why not switching to our binaries?
[08:50] <lissyx> either tarball or ppa?
[08:51] <eoli3n> i didn't know there was a ppa
[08:51] <eoli3n> that's a better option
[08:51] <eoli3n> lets check
[08:51] <eoli3n> thanks
[08:52] <eoli3n> which one should i use to have the current stable version ?
[08:53] <lissyx> ppa ,
[08:53] <lissyx> ?
[08:53] <eoli3n> ppa:mozillateam/ppa ?
[08:53] <eoli3n> yes
[08:53] <lissyx> yes I think so
[08:54] <eoli3n> lets test
[09:00] <mardy> Support for NFS and other remote FS is in the works. The reason why it doesn't work now is that snaps are run by executing a setuid binary, snap-confine, which tries to read the current directory, and that fails on most remote FS (for security reason they don't allow root access)
[09:00] <mardy> we are migrating away from setuid, and use Linux capabilities instead
[09:00] <mardy> but it's not a trivial task
[09:02] <mardy> bug 1973321
[09:02] <mup> Bug #1973321: snaps don't start when current working directory is on sshfs <snapd:Triaged> <https://launchpad.net/bugs/1973321>
[09:02] <eoli3n> mardy its working now, i don't know how
[09:02] <eoli3n> but that's ok
[09:02] <eoli3n> lissyx the funny thing is, i added the ppa, but as ubuntu wrap firefox package with apt to install with snap, i don't know how to force install from ppa
[09:03] <eoli3n> mardy, could you help about the snapd at startup problem ?
[09:04] <eoli3n> not sure i exposed it in the clearest way
[09:04] <eoli3n> lissyx found a doc about not using the snap package : https://doc.ubuntu-fr.org/firefox#installer_firefox_en_deb_classique_au_lieu_de_snap
[09:04] <eoli3n> in french, perfect
[09:06] <lissyx> eoli3n, is this some enterprise deployment?
[09:06] <eoli3n> french university
[09:06] <lissyx> if so, you might want to make sure you block auto-updates, and this might be complicated with the ppa
[09:06] <lissyx> which one?
[09:06] <eoli3n> Montpellier
[09:07] <lissyx> ok it's far enough you wont come to complain :D
[09:07] <eoli3n> huhu
[09:07] <eoli3n> you saw that complaining on IRC is in my skills
[09:07] <eoli3n> ;)
[09:08] <eoli3n> lissyx how to block auto-updates ? 
[09:08] <lissyx> pretty sure we have some doc on that but I dont know where
[09:08] <eoli3n> lissyx even funnier, firefox snap package is defaulty install, so i need to be able to remove it with ansible
[09:08] <eoli3n> then i hit my snapd not ready problem
[09:09] <lissyx> https://support.mozilla.org/en-US/products/firefox-enterprise/deploy-firefox-for-enterprise
[09:09] <eoli3n> thanks !
[09:09] <lissyx> how do you provision your ubuntu base system?
[09:14] <lissyx> mardy, so for speech-dispatcher socket, where should I add it?
[09:14] <eoli3n> boot pxe on a nfsroot with the iso installer extracted, preseed install, chroot -> ansible-pull, then reboot, ansible-pull again with apps installation enables
[09:14] <eoli3n> enabled
[09:14] <lissyx> desktop.go ?
[09:14] <lissyx> well during the preseed you can probably uninstall firefox snap?
[09:14] <eoli3n> i don't think so, that's my i split my ansible-pull runs : snapd is not running in chroot, because systemd is not running in chroot
[09:16] <eoli3n> s/my/why
[09:17] <lissyx> mardy, ok seb128 reminded me about at-spi one, I'm going to do it next to it
[09:21] <eoli3n> ah !!! 
[09:21] <eoli3n> https://0x0.st/o90v.txt
[09:21] <eoli3n> why waiting for multi-user.target !!
[09:22] <eoli3n> lets disable this
[09:23] <eoli3n> and then i found this !! in my playbook 
[09:23] <eoli3n> https://0x0.st/o90w.txt
[09:23] <eoli3n> facepalm
[09:23] <mup> PR snapd#12081 opened: Bug 1787245 - Grant access to speech-dispatcher socket <Created by lissyx> <https://github.com/snapcore/snapd/pull/12081>
[09:23] <eoli3n> that's something we put with mardy to solve my firefox issue
[09:25] <eoli3n> lets remove this
[09:26] <eoli3n> ok, that fixed the nfs home autodetection, if i remove it snapd will not detect that autofs use nfs for home
[09:33] <mup> PR snapd#12065 closed: store/tooling: support using snapcraft v7+ base64-encoded auth data <Squash-merge> <snap-revision-delegation> <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/12065>
[12:39] <mup> PR snapd#12082 opened: tests: remove NESTED_IMAGE_ID from nested manual tests <Run nested> <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/12082>
[12:43] <mup> PR snapcraft#3887 closed: store: support status for an onprem store <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/3887>
[13:12] <eoli3n> lissyx this problem will never end
[13:12] <eoli3n> the ppa kicked us
[13:12] <lissyx> kicked us ?
[13:13] <eoli3n> as i automate many host that add it in the same time
[13:13] <eoli3n> it timeouts now
[13:13] <eoli3n> so i think my public subnet was banned or something
[13:13] <lissyx> just use the tarball and  follow the doc to disable autoupdate ?
[13:13] <lissyx> or it's just infra failure, it happens
[13:14] <eoli3n> i don't need to disable autoupdate
[13:14] <eoli3n> i use unnatended upgrade so
[13:14] <lissyx> I'm referring to firefox'
[13:16] <eoli3n> yes, but as said, i use unattended upgrade for firefox package on the ppa
[13:16] <eoli3n> i want it to be as up to date as possible
[13:16] <lissyx> you just said PPA is blocked now
[13:17] <eoli3n> it timed out during the install process, replaying it on only one host worked
[13:17] <eoli3n> maybe that's a ddos protection or something
[13:17] <lissyx> so I'm just suggesting to move to the tarball we distribute instead of usign the ppa
[13:18] <lissyx> and doing so, you might want to disable autoupdate in the firefox install
[13:18] <eoli3n> i don't want static installations
[13:23] <lissyx> eoli3n, static?
[13:28] <mup> PR snapcraft#3884 closed: cli: parse http-proxy and https-proxy <Created by mr-cal> <Merged by mr-cal> <https://github.com/snapcore/snapcraft/pull/3884>
[13:55] <eoli3n> lissyx extracting a tarball is a static install, you can't upgrade it without manual intervention
[14:01] <ogra> doesnt the FF tarball install update itself ? 
[14:01] <ogra> (via a built in mechanism in FF)
[14:03] <ahasenack> FF tarball does update itself
[14:04] <ogra> yeah, thought so ... 
[14:06] <ahasenack> I have one place where it's extracted to ~/firefox, and I start it manually from there, and every now and then the shell CURDIR that is in that directory gets confused, because it was deleted an recreated
[14:06] <ahasenack> I have to cd -; cd -
[14:06] <ahasenack> then I know ff updated itself
[14:08] <ogra> well, i think it shows a popup too that you should restart (after it did the update)
[14:09]  * ogra is just gussing ... i do indeed use the snap 
[14:09] <ogra> *guessing
[14:09] <ogra> but i used to use the tarball some years ago and that was what it did 
[14:40] <mup> PR snapd#12077 closed: tests: add extra space to ubuntu bionic <Simple 😃> <Created by sergiocazzolato> <Merged by sergiocazzolato> <https://github.com/snapcore/snapd/pull/12077>
[17:23] <mup> PR snapcraft#3875 closed: providers: delete instances via Executor object <Created by mr-cal> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/3875>
[17:38] <mup> PR snapcraft#3888 opened: Hotfix/7.1.2 merge <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/3888>
[17:56] <mup> PR snapd#12082 closed: tests: remove NESTED_IMAGE_ID from nested manual tests <Run nested> <Created by sergiocazzolato> <Merged by sergiocazzolato> <https://github.com/snapcore/snapd/pull/12082>
[18:48] <mup> PR snapcraft#3873 closed: cli: add backwards compatible log enablement for LP <Created by sergiusens> <Closed by sergiusens> <https://github.com/snapcore/snapcraft/pull/3873>
[18:53] <mup> PR snapcraft#3889 opened: cli: add legacy envvar for login and check stdin <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/3889>
[20:23] <mup> PR snapcraft#3882 closed: Write passthrough to meta data and add some missing fields <Created by valentindavid> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/3882>
[20:23] <mup> PR snapcraft#3888 closed: Hotfix/7.1.2 merge <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/3888>
[20:48] <mup> PR snapcraft#3867 closed: DT-500 Fix Cups for Gtk support in Gnome-42 <Created by sergio-costas> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/3867>
[21:03] <mup> PR snapcraft#3886 closed: ua: specify and enable ua services <Created by cmatsuoka> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/3886>
[21:16] <mup> PR pc-amd64-gadget#68 closed: Increase boot partition size for classic gadget <Created by jawn-smith> <Closed by jawn-smith> <https://github.com/snapcore/pc-amd64-gadget/pull/68>
[22:23] <mup> PR snapcraft#3889 closed: cli: add legacy envvar for login and check stdin <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/3889>
[22:33] <mup> PR snapcraft#3890 opened: ua: enable ua services in legacy <Created by cmatsuoka> <https://github.com/snapcore/snapcraft/pull/3890>