** Changed in: snapcraft (Ubuntu)
Assignee: Kyle Fazzari (kyrofa) => (unassigned)
** Changed in: snapcraft (Ubuntu)
Status: In Progress => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Phew, thanks Marc.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906277
Title:
PCL armhf FTBFS
To manage notifications about this bug go to:
Note that this failed to build on ppc64el:
powerpc64le-linux-gnu-g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
recognition/CMakeFiles/pcl_recognition.dir/build.make:281: recipe for target
Verified: I can actually install pcl-dev on armhf now. I tested it using
https://github.com/kyrofa/pcl-sru-test which is (mostly) taken from
https://pcl.readthedocs.io/en/latest/using_pcl_pcl_config.html#using-
pcl-pcl-config:
$ git clone https://github.com/kyrofa/pcl-sru-test.git
$ cd
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596296
Title:
CeresConfig.cmake is not installed
To manage notifications about
Thank you, Marc!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906277
Title:
PCL armhf FTBFS
To manage notifications about this bug go to:
Here is a patch for Xenial. It's mostly a backport of the upstream
Debian patch (https://salsa.debian.org/science-
team/pcl/-/commit/f559d014ee8960f84100d6b6cd8e7372de15fbb4), but opts
not to completely remove the dependency on Qt4 to ensure no changes on
other architectures.
** Patch added:
** Summary changed:
- PCL is not available on armhf
+ PCL armhf FTBFS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906277
Title:
PCL armhf FTBFS
To manage notifications about this bug go to:
is low unless a typo is made in the patch.
** Affects: pcl (Ubuntu)
Importance: Undecided
Status: New
** Affects: pcl (Ubuntu Xenial)
Importance: Undecided
Assignee: Kyle Fazzari (kyrofa)
Status: In Progress
** Affects: pcl (Ubuntu Bionic)
Importance: Undecided
Note that armhf is not building. It already wasn't in the Xenial archive
actually due to this bug, but now that this bug is fixed it still isn't
building due to this Debian bug: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=798408 . I'll SRU a fix for that separately.
** Bug watch added:
Tested this using both the basic test case above using
https://github.com/kyrofa/pcl-sru-test as well as the much-more-involved
https://github.com/ros-perception/perception_pcl .
Using version 6.2.0+dfsg1-10build1 of libvtk6-dev and version
1.7.2-14build1 of libpcl-dev, both the basic test case
** Description changed:
[Impact]
* Any code that links to libraries provided by libpcl1.7 (which depends
on vtk6) fails to link because it cannot find vtkproj4 (see
https://github.com/PointCloudLibrary/pcl/issues/1594 for example)
* This has been fixed in Debian, but in a way
** Description changed:
[Impact]
* Any code that links to libraries provided by libpcl1.7 (which depends
on vtk6) fails to link because it cannot find vtkproj4 (see
https://github.com/PointCloudLibrary/pcl/issues/1594 for example)
* This has been fixed in Debian, but in a way
Thank you, Marc!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573234
Title:
unable to link: cannot find libvtkproj4
To manage notifications about this bug go to:
** Description changed:
[Impact]
* Any code that links to libraries provided by libpcl1.7 (which depends
on vtk6) fails to link because it cannot find vtkproj4 (see
https://github.com/PointCloudLibrary/pcl/issues/1594 for example)
- * This has been fixed in Debian
+ * This has
Changed in: pcl (Ubuntu Xenial)
Assignee: (unassigned) => Kyle Fazzari (kyrofa)
** Changed in: pcl (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Here's the patch required for pcl (no-change rebuild). It must happen
only after vtk6 has been built with the above patch.
** Patch added: "pcl-rebuild.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pcl/+bug/1573234/+attachment/5435349/+files/pcl-rebuild.debdiff
--
You received this bug
** Also affects: ceres-solver (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596296
Title:
CeresConfig.cmake is not installed
To manage
Note that upgrades to a given release uses the upgrader from that
release. As a result, there's no need to SRU this to Xenial, since
Xenial-to-Bionic upgrades will use the one from Bionic.
** Changed in: ubuntu-release-upgrader (Ubuntu Xenial)
Status: Confirmed => Won't Fix
--
You
** Description changed:
[Impact]
* Any code that links to libraries provided by libpcl1.7 (which depends
on vtk6) fails to link because it cannot find vtkproj4 (see
https://github.com/PointCloudLibrary/pcl/issues/1594 for example)
* This has been fixed in Debian
* The
** Description changed:
[Impact]
- * Any code that links to libraries provided by libpcl1.7 (which depends
+ * Any code that links to libraries provided by libpcl1.7 (which depends
on vtk6) fails to link because it cannot find vtkproj4 (see
** Description changed:
- This issue has been reported and fixed in Debian:
+ [Impact]
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819741
+ * Any code that links to libraries provided by libpcl1.7 (which depends
+ on vtk6) fails to link because it cannot find vtkproj4 (see
+
Here's a patch that fixes this issue in Xenial
** Patch added: "libproj-fix.debdiff"
https://bugs.launchpad.net/ubuntu/+source/vtk6/+bug/1573234/+attachment/5432746/+files/libproj-fix.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: vtk6 (Ubuntu Xenial)
Assignee: (unassigned) => Kyle Fazzari (kyrofa)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573234
Title:
unable to link: cannot find libvtkpr
** Also affects: vtk6 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: vtk6 (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here's the patch for Bionic.
** Patch added: "debdiff containing bionic patch"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1611737/+attachment/5427593/+files/18.04.41.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
- This message was appear when upgrade
+ [Impact]
- ProblemType: Bug
- DistroRelease: Ubuntu 14.04
- Package: ubuntu-release-upgrader-core 1:0.220.8
- ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22
- Uname: Linux 3.19.0-66-generic x86_64
-
** Also affects: ubuntu-release-upgrader (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: ubuntu-release-upgrader (Ubuntu Groovy)
Importance: Undecided
Assignee: Kyle Fazzari (kyrofa)
Status: In Progress
** Also affects: ubuntu-release-upgrader (Ubuntu
Proposed a (hopefully) helpful warning here:
https://code.launchpad.net/~kyrofa/ubuntu-release-upgrader/+git/ubuntu-
release-upgrader/+merge/388145
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Kyle Fazzari (kyrofa)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611737
Title:
Can't upgrade from a release if
Tested using upstream ceres-solver's helloworld.cc example[1].
Unable to test for regressions on arm64 because the package wasn't
available there before -proposed:
$ sudo apt install libceres-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Thank you, Marc!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882626
Title:
libceres-dev Focal arm64 build failing with failed test
To manage notifications about this bug go to:
** Attachment removed: "New debdiff with proper patch tags"
https://bugs.launchpad.net/ubuntu/+source/ceres-solver/+bug/1882626/+attachment/5383012/+files/debdiff_with_tagged_patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, last debdiff got garbled.
** Attachment added: "Real patch"
https://bugs.launchpad.net/ubuntu/+source/ceres-solver/+bug/1882626/+attachment/5383038/+files/debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "New debdiff with proper patch tags"
https://bugs.launchpad.net/ubuntu/+source/ceres-solver/+bug/1882626/+attachment/5383012/+files/debdiff_with_tagged_patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached is the debdiff of the patch for this issue.
** Patch added: "debdiff of patch"
https://bugs.launchpad.net/ubuntu/+source/ceres-solver/+bug/1882626/+attachment/5382703/+files/reduce-minimizer-iterations.debdiff
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
+ [Impact]
+
+ * ceres-solver's binary packages are not available on arm64 in Ubuntu
+ Focal
+
+ * tests seem to be failing on arm64:
https://launchpad.net/ubuntu/+source/ceres-
solver/1.14.0-4ubuntu1/+build/19091179
- Trying to install libceres-dev after
** Changed in: ceres-solver (Ubuntu Focal)
Assignee: (unassigned) => Kyle Fazzari (kyrofa)
** Changed in: ceres-solver (Ubuntu Focal)
Importance: Undecided => High
** Also affects: ceres-solver (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: ceres-
Note that libceres1 is present on arm64 in Groovy
(https://packages.ubuntu.com/groovy/libceres1)-- this only effects
Focal.
** Also affects: ceres-solver (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: ceres-solver (Ubuntu Focal)
Status: New => Confirmed
--
You
*** This bug is a duplicate of bug 1611737 ***
https://bugs.launchpad.net/bugs/1611737
The problem here is that you have ROS Kinetic installed, which only
supports Ubuntu 16.04: it doesn't support the upgrade. We're working on
a nicer error for exactly this situation.
** This bug has been
*** This bug is a duplicate of bug 1611737 ***
https://bugs.launchpad.net/bugs/1611737
To clarify: if you want to upgrade to to 18.04, I'm afraid you'll need
to remove ROS Kinetic first.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
> This makes some upgrades technically not possible since there could
not be packages in the ROS repositories available for the new
distribution in an upgrade process. For example, there is no a single
ROS Release that support 14.04 and 16.04. I can not see a
safe/straightforward upgrade path.
Thanks for testing, Simon!
> I was not able to find any fields where I could set "verification-
done-bionic"
Right under the bug description you'll see a set of tags that you can
edit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This patch is complex enough to make folks a little uncomfortable with
the SRU. Beyond Julian's suggestions (thanks Julian), Jose, are you
willing to commit to thoroughly testing this and resolving any
autopkgtest regressions?
--
You received this bug notification because you are a member of
Just finished taking this for a spin, both on armhf (to ensure it now
works) and amd64 (to smoke test for no regressions).
Here is an up-to-date amd64 using 1.4~rc1-1build2:
$ cat << EOF >> test.py
> #!/usr/bin/env python3
>
> import pygraphviz
>
> graph = pygraphviz.AGraph()
>
I've confirmed that this issue is only present in Bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834379
Title:
armhf Bionic python3-pygraphviz package errors for simple use case
To manage
** Changed in: python-pygraphviz (Ubuntu Eoan)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834379
Title:
armhf Bionic python3-pygraphviz package errors for
** Changed in: python-pygraphviz (Ubuntu Disco)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834379
Title:
armhf Bionic python3-pygraphviz package errors for
** Changed in: python-pygraphviz (Ubuntu Cosmic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834379
Title:
armhf Bionic python3-pygraphviz package errors for
** Changed in: python-pygraphviz (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834379
Title:
armhf Bionic python3-pygraphviz package errors for
** Description changed:
[Impact]
python3-pygraphviz does not work for even simple use cases on armhf
Bionic. See error output in Test Case section from adding an edge to a
graph.
This package is currently being used as a dependency of ROS2, which is
now including armhf as a
Can you try getting a no-change rebuild in a PPA?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834379
Title:
armhf Bionic python3-pygraphviz package errors for simple use case
To manage
jdstrand, I've added those rules, and the denials go away, but I'm
afraid it still doesn't work. There doesn't seem to be any denials, but
it's like chrome just doesn't see it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm hitting this in 18.04 as well, trying to use ufraw-batch for my .CR2
thumbnails.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to lensfun in Ubuntu.
https://bugs.launchpad.net/bugs/1768855
Title:
ufraw-batch in bionic segfault
To
*** This bug is a duplicate of bug 1628098 ***
https://bugs.launchpad.net/bugs/1628098
** This bug has been marked a duplicate of bug 1628098
organize needs to run after build in stage
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Package changed: snapcraft (Ubuntu) => snapcraft
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759700
Title:
Add a which-part-provided command or output (behind a flag)
To manage notifications
Public bug reported:
If I dare to launch any electron-based app (chrome, spotify, atom,
vscode, etc.) there's roughly an 80% chance that it kills X (bringing me
back to the login screen). This doesn't _always_ happen. Note that I
have a 4k laptop, with a 4k external screen. Things seem to have a
With those last few PRs applied:
$ git-ubuntu.self-test
pylint passed!
= test session starts
=
platform linux -- Python 3.6.3, pytest-3.1.3, py-1.5.2, pluggy-0.4.0
rootdir:
Fix for that last bit about the cache:
https://github.com/snapcore/snapcraft/pull/1980
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752481
Title:
Regressions in 2.39.2 in xenial-updates in
We probably need the cache to be either per-part, or do the rpath
patching after all parts have been primed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752481
Title:
Regressions in 2.39.2 in
(note that we already reset the cache for each part, but only for libs
that weren't found)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752481
Title:
Regressions in 2.39.2 in xenial-updates in
Got it. Hello global state!
The problem is that dpkg is a prerequisite of xz-utils, but _also_
requires liblzma. As a result, when priming them one after the other, we
cache the lookup result for dpkg, and re-use it when priming xz-utils:
Or perhaps it's not properly setting rpaths for libraries coming from
the same part unless those directories already exist.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752481
Title:
Regressions
Okay check this out. I removes all parts from the project except dpkg
and xz-utils to speed things up.
If I have a clean tree and run `snapcraft prime` this is what I end up
with:
$ ldd prime/usr/bin/xz
prime/usr/bin/xz: /lib/x86_64-linux-gnu/liblzma.so.5: version `XZ_5.2' not
found (required
Try ppa:kyrofa/1752481. With that I get:
$ ldd /snap/git-ubuntu/x1/usr/bin/gpgv
linux-vdso.so.1 => (0x7ffd40d56000)
libz.so.1 => /snap/core/current/lib/x86_64-linux-gnu/libz.so.1
(0x7fcb20e93000)
libbz2.so.1.0 =>
Note that I've noticed the same issue with mksquashfs in snapcraft
itself, LP: #1752964.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752481
Title:
Regressions in 2.39.2 in xenial-updates in
Invalidating the Snapcraft task since it's fixed everywhere else.
** Changed in: snapcraft
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626121
Title:
strict mode
Would you mind trying the snapcraft from edge, please?
sudo snap install --classic --edge snapcraft
That has a fix that may help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727695
Title:
Indeed, specifying the aliases in the YAML no longer does anything, more
information on this is here:
https://forum.snapcraft.io/t/improving-the-aliases-implementation/18
However, specifying the aliases in the YAML never had anything to do
with automatically connected them, that always has
Fix here: https://github.com/snapcore/snapcraft/pull/1618
** Changed in: snapcraft
Status: Triaged => In Progress
** Changed in: snapcraft
Assignee: (unassigned) => Kyle Fazzari (kyrofa)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks for the update, Tyler. I know this has been a long road, but the
cumulative effect of everyone's hard work on this particular front will
be huge. I'm very much looking forward to this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Sergio, what is the snapcraft solution to this? I'm still under the
impression the title (and license) need to go into the snap.yaml, but
you seemed to think it was only out-of-band to the store. Did we get
that resolved?
--
You received this bug notification because you are a member of Ubuntu
** Changed in: snapcraft
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694945
Title:
setuptools v36.0.0 breaks the python plugin
To manage
** Description changed:
The ubuntu-xenial kernel doesn't compile if you use -Werror
=incompatible-pointer-types. This seems to be due to ubuntu/i915, though
it's possible there are others. For example, in
ubuntu/i915/i915_gem_dmabuf.c, the signatures of the functions handed
off to
Public bug reported:
The ubuntu-xenial kernel doesn't compile if you use -Werror
=incompatible-pointer-types. This seems to be due to ubuntu/i915, though
it's possible there are others. For example, in
ubuntu/i915/i915_gem_dmabuf.c, the signatures of the functions handed
off to dma_buf_ops's
This is better: http://pastebin.ubuntu.com/24402954/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1617765
Title:
Connections reset when downloading snaps from CDN
To manage notifications about
Oh my. That looks dreadful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1617765
Title:
Connections reset when downloading snaps from CDN
To manage notifications about this bug go to:
Just got this twice from an lxc container here. It succeeded the third
time. The mtr report to one of the failed IP addresses looks like this:
$ mtr --report 64.94.115.6
Start: Mon Apr 17 20:10:51 2017
HOST: growing-urchin Loss% Snt Last Avg Best Wrst StDev
1.|--
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674484
Title:
snap install core failure: permission denied (apparmor)
To manage
** Changed in: nextcloud-snap
Importance: Unknown => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647031
Title:
systemd-resolved’s 127.0.0.53 server does not follow CNAME records
To
I assume this was actually released into xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621127
Title:
snap-confine doesn't work with new snap-run/snap-exec flow
To manage notifications
I've not tested anywhere else, but this bug is _not_ fixed on arm64,
running core from edge:
$ snap --version
snap2.23~201702241616.git.9d8157d~ubuntu16.04.1
snapd 2.23~201702241616.git.9d8157d~ubuntu16.04.1
series 16
kernel 4.4.0-1032-snapdragon
$ snap list
NameVersion
I think this really comes down to: when you run the snapped application
via .desktop file, you get an icon (since the icon is specified in the
.desktop file). When you run the application directly in the terminal,
there's no icon as the icon is only specified in the .desktop file.
--
You
** Description changed:
1- I uploaded a snap on myapps.developer.ubuntu.com
2- I choose Category: Games (note that I cannot choose a sub-category (Kids))
3- Default type: ? (I choose application, but not sure what it does exactly)
4- Opening Ubuntu Software on Ubuntu 16.04 I can find and
Good point, thanks ogra. Sorry for the noise!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560942
Title:
Support swap
To manage notifications about this bug go to:
Note that this was assigned to snapd as the mailing list discussion led
me to believe this would be implemented via the gadget snap, which is
something snapd would need to support no?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576411
Title:
UTF-8 is not very well supported inside snaps
To manage
** Package changed: snapd (Ubuntu) => snapd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636934
Title:
snapctl seem to cache values even if snap is removed and then
installed again
To manage
** Package changed: snapd (Ubuntu) => snapd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661126
Title:
Add One-shot Install/Uninstall Hook
To manage notifications about this bug go to:
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1586400
Title:
Snap type: change from "os" to "core"
To manage notifications about
** Package changed: snapd (Ubuntu) => snapd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1599620
Title:
SNAP_REEXEC doesn't cover snap-exec
To manage notifications about this bug go to:
** Package changed: snapd (Ubuntu) => snapd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636633
Title:
Content interface supports multiple sources, but only one destination
To manage
** Changed in: snapcraft
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590811
Title:
"clean that part" advice doesn't tell you the command to use
To
@Matt, I'd like to hear about your use-case for an uninstall hook. I
typically think of this as a "clean up behind yourself" hook, but since
when removing a snap the snap itself and all its writable areas are
blown away, I don't have a clear picture for how an uninstall hook would
be useful.
--
I'd like this as well. The only way to do things like this today is to
wrap the services that require configs (or databases, whatever) in a
script and make that script the daemon. It'd be great if that was an
optional step (e.g. if I wanted to verify a config before launching it,
as Mark
Fix here: https://github.com/snapcore/snapcraft/pull/1096
** Changed in: snapcraft
Status: Confirmed => In Progress
** Changed in: snapcraft (Ubuntu)
Status: Confirmed => In Progress
** Changed in: snapcraft
Assignee: (unassigned) => Kyle Fazzari (kyrofa)
*
Public bug reported:
Running Ubuntu Xenial 64-bit on a Dell M3800, which is one of those dual
video card things (built-in Intel as well as an nvidia). I'm currently
getting the following message spamming my syslog so much I'm starting to
get warnings about my disk getting full:
Jan 27 13:12:09
Note that there is also https://github.com/snapcore/snapd/wiki/hooks .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587447
Title:
Config interface needs to be better documented
To manage
Note that snapcraft doesn't exclude libraries correctly when that file
is different than xenial's either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650207
Title:
original lsb-release file
Yeah, hit this today:
$ python3
Python 3.5.2 (default, Nov 17 2016, 17:05:23)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import lsb_release
>>> lsb_release.get_distro_information()
Traceback (most recent call last):
File "", line 1,
1 - 100 of 316 matches
Mail list logo
