Re: Ubuntu bug reporting for snaps (was: Should we remove chromium-browser from the archive?)
On Tue, Feb 15, 2022 at 11:21 PM Brian Murray wrote: > > On Tue, Feb 08, 2022 at 09:18:41PM +0100, Olivier Tilloy wrote: > > On Tue, Feb 8, 2022 at 8:57 PM Sebastien Bacher wrote: > > > > > > Hey Olivier, thanks for raising the topic! > > > > > > Le 08/02/2022 à 19:33, Olivier Tilloy a écrit : > > > > - a custom apport hook that collects additional information about the > > > > snap and its dependencies > > > > > > I'm going to sidetrack slightly the discussion in a new topic to address > > > that point. I think that's a problem we need to resolve for snaps. We > > > added some hooks to apport directly for subiquity or > > > ubuntu-desktop-installer but it would be better if ubuntu-bug was able > > > to find hooks provided by the snaps (either by having snapd exporting > > > them to a system location or by teaching ubuntu-bug to look into > > > /snap/<...>/current/. > > > > A good first step, not going as far as enabling snaps to expose custom > > hooks, would be for apport to attach standard additional information > > when reporting a bug for a snap (in the add_snap_info function?): > > > > - snap changes --abs-time $SNAPNAME > > - snap connections $SNAPNAME > > - snap info --abs-time $SNAPNAME > > - for PROVIDER in $(grep default-provider > > /snap/$SNAPNAME/current/meta/snap.yaml | uniq | cut -d: -f2); do snap > > info --abs-time $PROVIDER; done > > - snap info --abs-time $(grep base: > > /snap/$SNAPNAME/current/meta/snap.yaml | cut -d: -f2) > > I've gone ahead and created http://launchpad.net/bugs/1960964 to track > this, please update the bug if I missed anything. I'll try and get this > done before the release of Jammy. Excellent, thanks Brian! -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Ubuntu bug reporting for snaps (was: Should we remove chromium-browser from the archive?)
On Tue, Feb 08, 2022 at 09:18:41PM +0100, Olivier Tilloy wrote: > On Tue, Feb 8, 2022 at 8:57 PM Sebastien Bacher wrote: > > > > Hey Olivier, thanks for raising the topic! > > > > Le 08/02/2022 à 19:33, Olivier Tilloy a écrit : > > > - a custom apport hook that collects additional information about the > > > snap and its dependencies > > > > I'm going to sidetrack slightly the discussion in a new topic to address > > that point. I think that's a problem we need to resolve for snaps. We > > added some hooks to apport directly for subiquity or > > ubuntu-desktop-installer but it would be better if ubuntu-bug was able > > to find hooks provided by the snaps (either by having snapd exporting > > them to a system location or by teaching ubuntu-bug to look into > > /snap/<...>/current/. > > A good first step, not going as far as enabling snaps to expose custom > hooks, would be for apport to attach standard additional information > when reporting a bug for a snap (in the add_snap_info function?): > > - snap changes --abs-time $SNAPNAME > - snap connections $SNAPNAME > - snap info --abs-time $SNAPNAME > - for PROVIDER in $(grep default-provider > /snap/$SNAPNAME/current/meta/snap.yaml | uniq | cut -d: -f2); do snap > info --abs-time $PROVIDER; done > - snap info --abs-time $(grep base: > /snap/$SNAPNAME/current/meta/snap.yaml | cut -d: -f2) I've gone ahead and created http://launchpad.net/bugs/1960964 to track this, please update the bug if I missed anything. I'll try and get this done before the release of Jammy. Cheers, -- Brian Murray -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Ubuntu bug reporting for snaps (was: Should we remove chromium-browser from the archive?)
On Tue, Feb 08, 2022 at 08:57:16PM +0100, Sebastien Bacher wrote: > Hey Olivier, thanks for raising the topic! > > Le 08/02/2022 à 19:33, Olivier Tilloy a écrit : > > - a custom apport hook that collects additional information about the > > snap and its dependencies > > I'm going to sidetrack slightly the discussion in a new topic to address > that point. I think that's a problem we need to resolve for snaps. We added > some hooks to apport directly for subiquity or ubuntu-desktop-installer but > it would be better if ubuntu-bug was able to find hooks provided by the > snaps (either by having snapd exporting them to a system location or by > teaching ubuntu-bug to look into /snap/<...>/current/. The hooks for subiquity and ubuntu-desktop-installer are shipped with apport, and should continue to be shipped with apport, because those snaps are only installed in the live environment. > Brian, any chance we could get that on the foundation backlog? I've added the general idea of apport looking for snap hooks to the Foundations team backlog. Thanks! -- Brian Murray -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Ubuntu bug reporting for snaps (was: Should we remove chromium-browser from the archive?)
On Tue, Feb 8, 2022 at 8:57 PM Sebastien Bacher wrote: > > Hey Olivier, thanks for raising the topic! > > Le 08/02/2022 à 19:33, Olivier Tilloy a écrit : > > - a custom apport hook that collects additional information about the > > snap and its dependencies > > I'm going to sidetrack slightly the discussion in a new topic to address > that point. I think that's a problem we need to resolve for snaps. We > added some hooks to apport directly for subiquity or > ubuntu-desktop-installer but it would be better if ubuntu-bug was able > to find hooks provided by the snaps (either by having snapd exporting > them to a system location or by teaching ubuntu-bug to look into > /snap/<...>/current/. A good first step, not going as far as enabling snaps to expose custom hooks, would be for apport to attach standard additional information when reporting a bug for a snap (in the add_snap_info function?): - snap changes --abs-time $SNAPNAME - snap connections $SNAPNAME - snap info --abs-time $SNAPNAME - for PROVIDER in $(grep default-provider /snap/$SNAPNAME/current/meta/snap.yaml | uniq | cut -d: -f2); do snap info --abs-time $PROVIDER; done - snap info --abs-time $(grep base: /snap/$SNAPNAME/current/meta/snap.yaml | cut -d: -f2) Of course, custom hooks would be a nice addition. -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Ubuntu bug reporting for snaps (was: Should we remove chromium-browser from the archive?)
Hey Olivier, thanks for raising the topic! Le 08/02/2022 à 19:33, Olivier Tilloy a écrit : - a custom apport hook that collects additional information about the snap and its dependencies I'm going to sidetrack slightly the discussion in a new topic to address that point. I think that's a problem we need to resolve for snaps. We added some hooks to apport directly for subiquity or ubuntu-desktop-installer but it would be better if ubuntu-bug was able to find hooks provided by the snaps (either by having snapd exporting them to a system location or by teaching ubuntu-bug to look into /snap/<...>/current/. Brian, any chance we could get that on the foundation backlog? Cheers, Sebastien -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
