[Group.of.nepali.translators] [Bug 1564192] Re: Lifecycle needs to track cross compilation

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.9

---
snapcraft (2.9) xenial; urgency=medium

  [ Leo Arias ]
  * autopkgtests: run the install examples tests in classic. (#481)
(LP: #1572764)

  [ Matteo Bertini ]
  * Fix typo in description of the python3 example. (#504)

  [ Jamie Bennett ]
  * Documentation: Use plugs instead of caps. (#507)

  [ Chris Wayne ]
  * Add in bash completion. (#453) (LP: #1570506)

  [ Sergio Schvezov ]
  * Fail validation if plugs or slots are declared at the part level (#514)
(LP: #1581166)

  [ Kyle Fazzari ]
  * Make pull and build steps dirty if target arch changes. (#450)
(LP: #1564192)
  * Add support for the confinement property. (#501) (LP: #1580819)
  * Add support for the epoch property. (#502) (LP: #1581113)

 -- Sergio Schvezov   Tue, 24 May 2016
23:32:11 -0300

** Changed in: snapcraft (Ubuntu Xenial)
   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/1564192

Title:
  Lifecycle needs to track cross compilation

Status in Snapcraft:
  Fix Released
Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  Fix Released
Status in snapcraft source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

   * If a snap is built using a specific target architecture, and one
  tries to build it again for a different architecture, Snapcraft says
  the snap is already built.

  [Test Case]

   1. Build the 96boards-kernel example with `snapcraft --target-arch arm64`.
   2. Build the 96boards-kernel example with `snapcraft --target-arch armhf`.
   3. Note that Snapcraft doesn't try to rebuild the kernel for the new 
architecture, it says it's already done.
   4. Apply the fix for this bug.
   5. Build the 96boards-kernel example with `snapcraft --target-arch armhf`.
   6. Note that Snapcraft now tries to rebuild the kernel using the new target 
architecture (which should fail-- all we care about is that it tries).

  [Regression Potential]

   * Dirty state tracking (rerunning steps if YAML sections change, bug
  #1477904) may not work correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1564192/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1564192] Re: Lifecycle needs to track cross compilation

[Sergio Schvezov]

** 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/1564192

Title:
  Lifecycle needs to track cross compilation

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]

   * If a snap is built using a specific target architecture, and one
  tries to build it again for a different architecture, Snapcraft says
  the snap is already built.

  [Test Case]

   1. Build the 96boards-kernel example with `snapcraft --target-arch arm64`.
   2. Build the 96boards-kernel example with `snapcraft --target-arch armhf`.
   3. Note that Snapcraft doesn't try to rebuild the kernel for the new 
architecture, it says it's already done.
   4. Apply the fix for this bug.
   5. Build the 96boards-kernel example with `snapcraft --target-arch armhf`.
   6. Note that Snapcraft now tries to rebuild the kernel using the new target 
architecture (which should fail-- all we care about is that it tries).

  [Regression Potential]

   * Dirty state tracking (rerunning steps if YAML sections change, bug
  #1477904) may not work correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1564192/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1564192] Re: Lifecycle needs to track cross compilation

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.9+16.10

---
snapcraft (2.9+16.10) yakkety; urgency=medium

  [ Leo Arias ]
  * autopkgtests: run the install examples tests in classic. (#481)
(LP: #1572764)

  [ Matteo Bertini ]
  * Fix typo in description of the python3 example. (#504)

  [ Jamie Bennett ]
  * Documentation: Use plugs instead of caps. (#507)

  [ Chris Wayne ]
  * Add in bash completion. (#453) (LP: #1570506)

  [ Sergio Schvezov ]
  * Fail validation if plugs or slots are declared at the part level (#514)
(LP: #1581166)

  [ Kyle Fazzari ]
  * Make pull and build steps dirty if target arch changes. (#450)
(LP: #1564192)
  * Add support for the confinement property. (#501) (LP: #1580819)
  * Add support for the epoch property. (#502) (LP: #1581113)

 -- Sergio Schvezov   Tue, 24 May 2016
23:32:11 -0300

** Changed in: snapcraft (Ubuntu Yakkety)
   Status: New => 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/1564192

Title:
  Lifecycle needs to track cross compilation

Status in Snapcraft:
  Fix Committed
Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  New
Status in snapcraft source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

   * If a snap is built using a specific target architecture, and one
  tries to build it again for a different architecture, Snapcraft says
  the snap is already built.

  [Test Case]

   1. Build the 96boards-kernel example with `snapcraft --target-arch arm64`.
   2. Build the 96boards-kernel example with `snapcraft --target-arch armhf`.
   3. Note that Snapcraft doesn't try to rebuild the kernel for the new 
architecture, it says it's already done.
   4. Apply the fix for this bug.
   5. Build the 96boards-kernel example with `snapcraft --target-arch armhf`.
   6. Note that Snapcraft now tries to rebuild the kernel using the new target 
architecture (which should fail-- all we care about is that it tries).

  [Regression Potential]

   * Dirty state tracking (rerunning steps if YAML sections change, bug
  #1477904) may not work correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1564192/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp