group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #04584
[Bug 1575628] Re: Snapcraft doesn't ignore already-built snaps when `source` is the folder containing the `snapcraft.yaml`
** Changed in: snapcraft
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1575628
Title:
Snapcraft doesn't ignore already-built snaps when `source` is the
folder containing the `snapcraft.yaml`
Status in Snapcraft:
Fix Released
Status in snapcraft package in Ubuntu:
Fix Released
Status in snapcraft source package in Xenial:
Fix Committed
Status in snapcraft source package in Yakkety:
Fix Released
Bug description:
[Impact]
* Many plugins support sources. When the `source` keyword points to
the directory containing the `snapcraft.yaml`, Snapcraft creates a
copy of that entire directory, including any snaps that have already
been built (which can be very large).
[Test Case]
1. Download and run `snapcraft` on http://people.canonical.com/~kyrofa/test-cases/1575628.tar . The result should be a .snap.
2. Run `snapcraft clean`. This shouldn't remove the .snap.
3. Run `snapcraft` again.
4. Notice that the .snap that was already built was copied into `parts/foo/build/`.
5. Apply the fix for this bug.
6. Run steps 2 and 3 again.
7. Notice that the .snap that was already built was NOT copied into `parts/foo/build/`.
[Regression Potential]
* When copying the source folder, Snapcraft-specific data is excluded
(e.g. parts/ stage/ snap/ snapcraft.yaml, etc.). That data may no
longer be excluded correctly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1575628/+subscriptions