I have been running the tests to verify this SRU. I found no blockers,
so I'm marking this as verified. Please, continue with the release
process.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug
Oh, yes, very bad design :) Thanks for the info and the link Jeremy!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751954
Title:
disabling wi-fi in power management options disables the wi-fi
To
Same bug reported for redhat:
https://bugzilla.redhat.com/show_bug.cgi?id=1495433
** Bug watch added: Red Hat Bugzilla #1495433
https://bugzilla.redhat.com/show_bug.cgi?id=1495433
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
In the gnome-control-center, in the power section, there is a checkbox
that says:
Wi-Fi
Turn off Wi-Fi to save power
I have it checked, so after a few minutes without using my computer, the
wi-fi is disabled. I want to keep my wi-fi working, so I unchecked this
box, but it
The latest snapcraft released to the stable distros was 2.35. So, in
order to accept this update, the following tests need to be executed:
For 2.36:
snapcraft.yaml:
Build a snap with $SNAPCRAFT_ARCH_TRIPLET in the snapcraft.yaml.
Store:
Run snapcraft push-metadata.
Exploratory:
Alright! I installed v4.14.3, and it seems to work now :)
Fwiw, I tried going crazy with multiple fingers in the touchpad, and it still
works.
Thank you! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On cold boot, the touchpad dies too. I'm on bionic, is the fix going to
be released here too?
About the mainline kernel, do you mean this one?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc2/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hey, so I upgrade the machine by mistake, and now the touchpad dies
again after a few seconds/minutes. I tried reinstalling the debs you
linked, but this time it doesn't seem to fix it :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I ran the tests in xenial, zesty and artful, and have been doing exploratory
testing on the release.
I didn't find any blocker bugs, so this has the QA green light.
We have a call for testing in progress, and I'll be on holidays next
week, so I'll leave sergiusens to mark this a verified when he
To land this in the -updates pocket, the following tests must pass:
Sources:
* Build a snap with a deb as the source.
Scripts:
* Try to run snapcraft with a script (prepare, build or install) that exits
non-zero.
* Run snapcraft with a script (prepare, build or install), edit the script
Thanks kaihengfeng, the mouse is already working after a couple of minutes. I
haven't been this far :)
I'll let you know if it stops working later.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I have installed ubuntu bionic on a Lenovo ideapad 320. The touchpad
stops working a few seconds after I log in.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname:
I've successfully run the tests in xenial, zesty and artful LXD
containers, testing the upgrade and then making various snaps to
exercise the new features in this release, plus exploratory.
I couldn't find any blockers, so I'm marking this as verified.
Thanks Łukasz!
** Tags removed:
Before this update lands in the -update pockets, the following tests
need to pass:
Container builds:
* Clean the project without arguments:
`SNAPCRAFT_CONTAINER_BUILDS=1 snapcraft clean`
Plugins:
* Build a snap with the catkin plugin.
* Build a snap with the jhbuild plugin.
Errors:
Thanks seb. I'm marking this as Triaged.
We improved a little the stuff we print to the terminal. Now we need to
improve logging and also the way we call subprocess when we capture the
output.
This will require touching pieces of code everywhere, but now that we
are using a nicer cli library it
Hey Sebastian,
We are working on recording a manifest of what happened during the
build, like the packages that were installed, and info about the
machine. Is that what you want, or do you want the full output printed
to stdout?
** Changed in: snapcraft
Status: Triaged => Incomplete
--
I have run those tests in xenial and zesty, and I've been running
exploratory tests on this version since Friday. I haven't found any
issue, so I'm going to mark it as verified.
Thanks Andy!
** Tags removed: verification-needed verification-needed-xenial
verification-needed-zesty
** Tags added:
These are the tests that must pass before landing this new release in
the -updates pockets of xenial and zesty:
Plugins:
* Cross-compile and run an autotools snap.
* Cross-compile and run an waf snap.
Cleanbuild:
* Test a build failure in cleanbuild with --debug.
Snapd:
* Test a
Thanks Lukasz.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696402
Title:
chroot configuration strictly depends on overlayfs
To manage notifications about this bug go to:
We tested this in xenial, yakkety and zesty proposed, together with snapcraft
for bug #1692102.
No issues found with the rename of the package, and now snapcraft can be
updated without problems.
I've just marked this as verified.
** Tags removed: verification-needed
** Tags added:
I've just marked this bug as verified. Please, accept it in -updates.
Thank you!
** 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.
I ran extensive tests using snapcraft 2.31 after an upgrade from 2.29 in
xenial, yakkety and zesty.
Some more details here:
https://forum.snapcraft.io/t/in-progress-snapcraft-2-31/682/8
I've also made a call for testing in case more people want to give it a
try during the weekend. Early on
In order to accept this release in the -updates pockets of xenial,
yakkety and zesty, the following tests must be executed:
Plugins:
* Build a Qt snap using the default version.
* Build go snaps for different architectures using --target-arch.
Exploratory:
* Build snaps with build-packages.
I ran the test cases documented in this bug using a xenial container and
the bileto PPA: https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/2812
Everything works as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
The kernel changed the module name from overlayfs to overlay, this needs
to be taken into consideration when creating the chroot.
+
+ [Impact]
+
+ When trying to create the chroot, it fails like this:
+ Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
+ E:
I ran the test cases documented in this bug using an artful lxc
container.
Everything works as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693226
Title:
Break the conflicts with click
** Tags added: isv
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607067
Title:
Add a dotfiles / hidden files interface
To manage notifications about this bug go to:
In order to accept this release in the -updates pockets of xenial,
yakkety and zesty, the following tests must be executed:
Plugins:
* Run the kernel manual tests documented in `manual-tests.md`.
* Build a snap with that uses meson.
Sources:
* Build a snap with a 7zip source.
Store:
* Run
I ran the tests in comment #1 in zesty, yakkety and xenial. I didn't
find any blockers, so I'm marking this bug as verified.
Thanks Andy!
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
These are the tests that must pass before accepting this version in the
-updates pockets of xenial, yakkety and zesty:
Plugins:
* Build nodejs snaps.
* Check that by default they use the newer nodejs LTS version.
* Build a nodejs snap using yarn.
* Build a classic rust snap.
* Build the
** 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/1676750
Title:
error: cannot perform the following tasks: - Download snap
I've tested the updates from 2.27.1 in xenial and yakkety lxc and kvm,
and ran the tests mentioned in the comment #1. Also a call for testing
was active during the weekend with the qa community [1]
We didn't find any regressions or blocker bugs, so I'm going to mark
this as verified. Thanks Andy!
The following tests have to be run before this update is accepted into
xenial and yakkety updates:
plugins:
* Build a snap using a python staged on the same snap.
* Build the pc kernel snap.
https://github.com/snapcore/snapcraft/blob/master/manual-tests.md#test-the-pc-kernel
* Check that
I tested this in a clean xenial vm up-to-date and could install and play
ohmygiraffe. There was an apport crash which I submitted, but it didn't
seem to affect the installation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Project changed: snappy => snapd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668891
Title:
Can install non classic snap with --classic, but classic flag isn't
set
To manage notifications
** Tags added: bitesize snap-docs ui
** Changed in: snapcraft
Status: New => Confirmed
** Changed in: snapcraft
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: snapcraft
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590807
Title:
Snapcraft doesn't store build logs
To manage notifications about this bug
** Project changed: snappy => snapd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670397
Title:
On Debian Stretch (9) /snap/bin is not added to path
To manage notifications about this bug go to:
Raising the priority, because the help is pretty bad now with the big
list of snapcraft commands that we have.
** Tags added: snap-docs
** Changed in: snapcraft
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: new-plugin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1525487
Title:
Support swift programming language
To manage notifications about this bug go to:
We don't have docs for remote parts, we need to add that, and also we
need to improve some important parts of sharing parts. For now, you can
look at the existing parts: https://wiki.ubuntu.com/snapcraft/parts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** 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/1667216
Title:
build-attributes not documented
To manage notifications about this bug go to:
I installed snapd 2.22.2 in my trusty, xenial and yakkety kvms.
Then I enabled -proposed, updated snapd to 2.22.3 and did a little exploratory
on the machines:
install, run, refresh various snaps.
I didn't find any problem, so I'm going to mark this bug as verified.
Thanks Andy.
** Tags
I've been running tests since yesterday for this SRU. No blocker bugs
found, so I'm going to mark this as verified. Thanks Steve!
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1664651 ***
https://bugs.launchpad.net/bugs/1664651
** Package changed: snapcraft (Ubuntu) => snapcraft
** This bug has been marked a duplicate of bug 1664651
pre-flight checks not catching missing name registration
--
You received this bug
Before this new revision is accepted in xenial and yakkety updates, the
following test must be executed:
plugins:
* Build and run the checkbox snap.
classic:
* Build a classic snap without core installed.
* Snap asciinema in xenial and run it in trusty.
cleanbuild:
* Cleanbuild a snap
I've run the tests mentioned in the comment #1 in xenial and yakkety,
after upgrading the snapcraft packages from 2.25 to 2.26.
I found no blocker bugs, so I'm going to mark this bug as verified.
Thanks Steve!
** Tags removed: verification-needed
** Tags added: verification-done
--
You
https://github.com/snapcore/snapcraft/pull/1097
** Changed in: snapcraft
Status: Triaged => In Progress
** Changed in: snapcraft
Assignee: (unassigned) => Leo Arias (elopio)
** Changed in: snapcraft
Milestone: None => 2.27
--
You received this bug notification be
** Changed in: snapd-glib
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/167
Title:
[snaps] License information from the store not available
To manage
Pat, can you please attach the yaml please? I think I've hit this
problem when the right side value had a ":", and then yaml goes crazy.
** Changed in: snapcraft (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631270
Title:
running a command for a snap in try mode fails on trusty
To manage notifications about this bug go to:
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1660573
Title:
"system is booting up" while trying to log in after installing snapd
on ubuntu 14.04
To manage notifications
Hey Robert, any progress here?
Harald's post became popular today:
https://apachelog.wordpress.com/2017/01/30/kde-applications-in-ubuntu-
snap-store/
Sadly, it has a prominent picture of this bug too :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Before this can be released to the updates pocket of the archive, the
following tests need to pass:
plugins:
* Make a godeps snap with the go-packages keyword.
* Make a gradle snap without gradlew.
* Check that the gradle binary is called instead.
* Make a catkin snap.
* Check that
https://bitbucket.org/flexiondotorg/podpublish/src/4fce812d64149151d97d2bba6bc46bc6595f682f/snapcraft.yaml?at=master
=file-view-default#snapcraft.yaml-15
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
A few more sightings, that require the workaround:
https://github.com/21dotco/two1-python/pull/16/files#diff-
184032a532406b07009403e26f4fc62fR13
https://github.com/warner/magic-wormhole/blob/master/snapcraft.yaml#L21
--
You received this bug notification because you are a member of Ubuntu
I have run the tests specified above in xenial and yakkety. I've also
done extensive exploratory testing on the areas related to the changes
made by this release, and we have a call for community testing since
Friday. So, I'm going to mark this bug as verified.
Thanks Steve.
** Tags removed:
Before the package can be promoted to xenial-updates and yakkety-updats,
it must pass the following tests:
snapcraft-parser:
* Run snapcraft-parser -h
* Try to parse an origin without snapcraft.yaml
* Run with the debug flag.
plugins:
* Make snaps with ant, autotools, godeps, catkin,
*** This bug is a duplicate of bug 1644673 ***
https://bugs.launchpad.net/bugs/1644673
** Package changed: snapcraft (Ubuntu) => snapcraft
** This bug has been marked a duplicate of bug 1644673
Trying to register a snap name with reserved characters fails opaquely
--
You received this
The help command expects the plugin name with _ instead of -.
$ snapcraft help plainbox_provider
It should replace the - it gets from the command line to a _.
I'm setting priority to medium, because we only have two plugins with -.
** Package changed: snapcraft (Ubuntu) => snapcraft
**
It affects people trying to do an earlang snap with snapcraft. But you
are right, this probably should be a won't fix in snapcraft.
** Changed in: snapcraft
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I installed snapcraft, snapcraft-examples and snapcraft-parser in clean
xenial and yakkety vms. Then enabled -proposed and upgraded the three
packages to 2.24.
Then I ran the tests mentions in the comment #1 above, and extensive
exploratory building and running a variety of snaps. I could found
** Tags added: bitesize ui
** Changed in: snapcraft
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1610847
Title:
Failed authentication looks like it succeeded
These are the tests that have to pass before the update can land into
xenial and yakkety:
help:
Run snapcraft plugins.
plugins:
Pull and build using a rust part.
Check that the download happens only during pull.
Build a python snap that has a read-only file.
Build
Wow, this is old. It's surprising that it hasn't been released:
$ apt search python3-junitxml
Sorting... Done
Full Text Search... Done
python3-junitxml/zesty,zesty 0.6-1.1ubuntu1 all
PyUnit extension for reporting in JUnit compatible XML
I'm no longer using jenkins, and I hope I won't have to
If launchpad used snapcraft cleanbuild it would be easier to get the
same environment locally. I wonder if Sergio and Colin will like this
idea.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649620
** 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/1646993
Title:
[SRU] New stable micro release 2.23
To manage notifications about
I installed snapcraft, snapcraft-parser and snapcraft-examples in clean xenial
and yakkety virtual machines.
Then I enabled -proposed and upgraded the three packages to 2.23.
I ran the tests mentioned in the comment #2 above, and extensive
exploratory in both machines.
I couldn't find any
Before this can land into xenial and yakkety, the following tests need
to be executed:
sources:
- build a snap with the shutter tar.gz as a source, from bug #1611776.
- try to build snaps without the source commands: bzr, git, hg.
- build a snap with an ftp source.
- build the snap from
I tested this in xenial and yakkety:
Install snapcraft, snapcraft-examples and snapcraft parser. Enable -proposed.
Upgrade the packages to 2.22.1.
Then I checked that the reverted commit from 2.22 was actually removed
and it wasn't causing weird problems. I also did a quick exploratory to
check
Marking verification failed because one change of syntax in 2.22 would
prevent a new feature that we want to implement for multiarch. 2.22.1 is
coming with that change reverted, and a following version will get it
back with support for more things.
** Tags removed: verification-done
** Tags
I tested this in xenial and yakkety:
Install snapcraft, snapcraft-examples and snapcraft parser. Enable -proposed.
Upgrade the packages to 2.22.
Then I ran the following tests:
Build a gadget snap.
Run snapcraft --version.
Exploratory on store commands.
Build snaps and check that the cache is
I tried using a link: setup/gui/keepassxc.desktop ->
share/linux/keepassxc.desktop
That didn't work:
[('setup/gui/icon.png',
'/home/elopio/workspace/keepassxreboot/keepassxc/prime/meta/gui/icon.png',
"[Errno 2] No such file or directory: 'setup/gui/icon.png'"),
('setup/gui/keepassxc.desktop',
I tested this in xenial and yakkety:
Install snapcraft, snapcraft-examples and snapcraft-parser. Enabled
-proposed. Upgrade the three packages to 2.21.
Then I did a few tests:
- Exploratory on the new bash completion features.
- Exploratory building snaps with the python plugin.
- Build
I tested this release, both in xenial and yakkety.
I installed snapcraft, snapcraft-examples and snapcraft-parser. Then enabled
-proposed and upgraded the snaps to 2.20.
Then I ran the following tests:
Plugins:
Try to build a snap using an invalid ros distro.
Build a snap that uses
Public bug reported:
I restarted my zesty machine, and this report popped up.
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: liblirc-client0 0.9.4c-1
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon
Same problem in errbot, and same workaround to force LC_ALL=C.UTF-8:
https://github.com/elopio/errbot/blob/snapcraft/snapcraft.yaml#L14
--
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:
It works today. ¯\_(ツ)_/¯
** Changed in: qemu (Ubuntu)
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/1636658
Title:
copy no longer works from the host to a kvm
** Changed in: snapd (Ubuntu)
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/1634392
Title:
have a snap command to wait for a change
To manage notifications about
Public bug reported:
I used to be working on yakkety, with many kvm guest machines using
spice. Those machines have spice-vdagent installed so I can copy and
paste from the host to the guest.
That worked fine until I upgraded to zesty. Now I can no longer use the
clipboard to share text with the
I tested this in a trusty lxc. Updated sudo to 1.8.9p5-1ubuntu1.3 and:
# mkdir -p /snap/bin
# cp $(which echo) /snap/bin/echo-test
# su ubuntu
$ sudo echo-test test
test
I'm marking it as verified. Thanks Brian.
** Tags removed: verification-needed
** Tags added: verification-done
--
You
I tested the launch of snaps in a xenial kvm up-to-date after updating
snap-confine from -proposed to 0.43.
I'm marking this as verified.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
For all the bugs of the linked milestones that didn't have the
verification-done tag I ran the specified tests in a xenial clean kvm
after the upgrade to snap-confine 1.0.43. I couldn't run the test for
snaps on lxc nor the one for nvidia. I left comments on those, but they
shouldn't block this
I ran the snap-confine test in an up-to-date xenial classic kvm, after
enabling proposed and upgrading to snap-confine to 0.43.
I got no errors, looks good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I ran the snap-confine test in an up-to-date xenial classic kvm, after
enabling proposed and upgrading to snap-confine to 0.43.
I got no errors, looks good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have no machine available with an nvidia card, so I can't verify this
one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615248
Title:
ubuntu-core-launcher nvidia driver detection is bogus
To
I ran the snap-confine test in an up-to-date xenial classic kvm, after
enabling proposed and upgrading to snap-confine to 0.43.
I got no errors, looks good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This can't really be tested yet for snap-confine in xenial proposed
because the required packages are not yet in xenial. I tried bringing
packages from yakkety and yakkety-proposed, but that didn't work, it was
just a long shot. It even seems there is still a PR in flight for snapd.
I checked the
There is nothing to manually verify here other than the test passes and the
package builds.
As 1.0.43 is already in proposed, I'm going to mark this as verified.
Thanks Andy.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because
This bug and fix don't affect snap-confine in a classic system, and zyga
already verified it in an all-snaps system.
So I'm going to mark it as verified. Thanks Andy.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a
I verified that the snap-confine version in xenial-proposed fixes this
bug:
I tested this in a clean xenial kvm, with snap-confine 1.0.38:
elopio@ubuntu-xenial:/$ snapd-hacker-toolbelt.busybox cat /var/lib/lxd/canary
cat: can't open '/var/lib/lxd/canary': No such file or directory
snap-confine doesn't fail to build anymore, 1.0.43 landed successfully
in -proposed. I also tested the related bug: https://bugs.launchpad.net
/snap-confine/+bug/1613845/comments/10
I'm going to mark this as verified. Thanks Andy.
** Tags removed: verification-needed
** Tags added:
@balloons, this hasn't been yet released to xenial. On xenial the latest
snap-confine is 1.0.38-0ubuntu0.16.04.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613845
Title:
Juju snap can no
Thanks Andy. I'm going to mark the bug as verified.
** 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/1629472
Title:
[SRU] New
I tested the SRU in a clean and up-to-date kvm xenial machine. I
installed snapcraft, snapcraft-examples and snapcraft-parser, enabled
-proposed and upgraded them to 2.19.
I ran the following tests:
Snaps:
✓ Build the plainbox provider snap.
✓ Build a snap that requires npm commands.
✓ Build a
I have tested this release in a clean and up-to-date xenial vm:
Installed snapcraft, snapcraft-examples and snapcraft-parser, enabled
-proposed, and upgraded them to 2.18.1.
I then ran the following tests:
Plugins:
✓ Build a snap with a python constraints file from a URL.
✓ Build a snap with a
This has just happened to me. For some reason, all my machines had
machine='pc-i440fx-wily'.
After an update in yakkety, they stopped working.
$ qemu-system-x86_64 -enable-kvm -machine help | grep wily
So I updated the machine xml to a supported machine as Charles
suggested, and they work
It's happening for me today. I'm changing it back to confirmed.
** Changed in: phablet-tools (Ubuntu)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1610650
Added snapcraft as affected because this makes the autopkgtests fail, so
it blocks the release to yakkety.
** Also affects: snapcraft
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
strace: http://paste.ubuntu.com/23212239/
/etc/apparmor.d/usr.lib.snapd.snap-confine: http://paste.ubuntu.com/23212242/
--
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:
snap-confine
1 - 100 of 2142 matches
Mail list logo
