[Group.of.nepali.translators] [Bug 1582367] Re: confusing error when the binary is not found and it has the same name of the app

[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/1582367

Title:
  confusing error when the binary is not found and it has the same name
  of the app

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:
  I've made a mistake when trying to snap a CLI app. In the command
  section I entered the name of a bin that doesn't exist. I got this
  error back:

  The specified command 'hollywood' defined in 'hollywood' does not
  exist or is not executable

  The error is ok, but we could improve it with something like:

  The specified command 'hollywood' defined in *the 'hollywood' app*
  does not exist or is not executable.

  Here's the relevant part of my snapcraft.yaml:

  apps:
hollywood:
  command: hollywood

  [Impact]

   * New users are likely to make this error, and the error might
  confuse them more.

  [Test Case]

   * Define a snapcraft.yaml with a wrong command path
   * Run snapcraft

  [Regression Potential]

   * Extremely low. The fix is to change a string, that won't affect the
  error handling of existing code paths.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1582367/+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 1582955] Re: snap step prints too much information about mksquashfs

[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/1582955

Title:
  snap step prints too much information about mksquashfs

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:
  The snapcraft build finishes with something like this:

  Snapping kpcli-elopio_3.0_amd64.snap
  Parallel mksquashfs: Using 10 processors
  Creating 4.0 filesystem on kpcli-elopio_3.0_amd64.snap, block size 131072.
  
[===-]
 2983/2983 100%

  Exportable Squashfs 4.0 filesystem, xz compressed, data block size 131072
  compressed data, compressed metadata, compressed fragments, no xattrs
  duplicates are removed
  Filesystem size 12193.21 Kbytes (11.91 Mbytes)
  23.13% of uncompressed filesystem size (52710.07 Kbytes)
  Inode table size 25248 bytes (24.66 Kbytes)
  23.25% of uncompressed inode table size (108609 bytes)
  Directory table size 28830 bytes (28.15 Kbytes)
  42.88% of uncompressed directory table size (67241 bytes)
  Number of duplicate files found 481
  Number of inodes 3347
  Number of files 2752
  Number of fragments 168
  Number of symbolic links  40
  Number of device nodes 0
  Number of fifo nodes 0
  Number of socket nodes 0
  Number of directories 555
  Number of ids (unique uids + gids) 1
  Number of uids 1
  root (0)
  Number of gids 1
  root (0)
  Snapped kpcli-elopio_3.0_amd64.snap

  Everything between the progress bar and the Snapped message seems
  irrelevant to me.

  [Impact]

   * The output of every snapcraft build is too noise and not really 
understandable.
   
   * A cleaner output makes the experience better, and helps to find real 
errors.

  [Test Case]

   * Run snapcraft with and without debug to generate a snap.
   * Check that a progress animations is shown.
   * Check that the output is short and to the point without the flag, and that 
it's the same as before with the flag.

  [Regression Potential]

   * This touches the final step of the snap generation and could break
  it. We are safe against this regression because we have a suite that
  generates, installs and executes snaps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1582955/+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 1582515] Re: strip phase name is not great

[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/1582515

Title:
  strip phase name is not great

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:
  The "strip" phase name is not great. It's not actually stripping..
  it's the phase that copies the content into the snap directory, as I
  understand it. So it's the opposite of stripping (although I
  understand where the motivation comes from). See how this command
  makes little sense, for example:

  snapcraft clean --step=strip

  So it might be better named as something like "cast", or "shape", or
  "form". I'd check with Mark for the best word here.

  [Impact]

   * One of the snapcraft commands is confusing.

   * The change is backwards compatible, so anything that's relying on
  strip will still work.

  [Test Case]

   * Run snapcraft strip
   * Check that you get a deprecation message.
   * Clean
   * Run snapcraft prime
   * Check that the results are the same, without deprecation message.

  [Regression Potential]

   * This could affect the strip command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1582515/+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 1586137] Re: Snapcraft should provide an `tour` subcommand that sets up a basic tour

[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/1586137

Title:
  Snapcraft should provide an `tour` subcommand that sets up a basic
  tour

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:
  The snapcraft codebase currently includes a number of examples that
  are more suited to be demos. Snapcraft should include a number of very
  simple examples that can be created on the fly in order to walk though
  introductory documentation. These examples should be created in the
  current working directory via `snapcraft examples`.

  [Impact]

   * A tour will help users getting started with snapcraft.

  [Test Case]

   * Follow the tour docs and instructions.

  [Regression Potential]

   * New tests were added for the tour snaps, and the old examples tests
  were renamed. If they fail, they will block the package getting to
  proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1586137/+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 1568131] Re: Terse error message when package cannot be found

[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/1568131

Title:
  Terse error message when package cannot be found

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:
  I typo'ed the nonexistent libcap instead of libcap2 in stage-packages.
  The resulting error message (snapcraft 2.7) wasn't helpful:

  ev@elsa:~/branches/whoopsie/snappy$ snapcraft
  Preparing to pull whoopsie
  Hit http://security.ubuntu.com/ubuntu xenial-security InRelease
  Hit http://us.archive.ubuntu.com/ubuntu xenial InRelease
  Hit http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease
  Fetched 0 B in 0s (0 B/s)
  libcap

  [Impact]

   * There is no error when the package doesn't exist.

   * What snapcraft does is confusing and leads to wasted time trying to
  understand what was wrong.

  [Test Case]

   * Create an snapcraft.yaml with an unexisting stage-package.
   * Run snapcraft.
   * Verify that the error is clear.

  [Regression Potential]

   * Existing stage packages could be affected. Run snapcraft with an
  existing package to confirm it still works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1568131/+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 1583426] Re: can't load package when building a go project

[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/1583426

Title:
  can't load package when building a go project

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:
  I'm trying to make a snap for hashicorp's vault.

  This is the error I'm getting:

  env GOPATH=/home/elopio/workspace/canonical/snaps/vault/parts/vault/go go get 
-t -d ./vault.git/...
  can't load package: package vault.git: code in directory 
/home/elopio/workspace/canonical/snaps/vault/parts/vault/go/src/vault.git 
expects import "github.com/hashicorp/vault"
  Command '['/bin/sh', '/tmp/tmpwyqwm_y3', 'env',
  'GOPATH=/home/elopio/workspace/canonical/snaps/vault/parts/vault/go',
  'go', 'get', '-t', '-d', './vault.git/...']' returned non-zero exit
  status 1

  This is the snapcraft.yaml I'm using:

  name: vault-elopio
  version: snap0.1
  summary: Vault is a tool for securely accessing secrets.
  description: bla

  apps:
    vault:
  command: bin/vault
  plugs: [network, network-bind]

  parts:
    vault:
  plugin: go
  source: https://github.com/hashicorp/vault.git

  [Impact]

   * Some go projects can't be easily build.

   * The workaround is hard to find, it should be clearer what to do for
  these projects.

  [Test Case]

   * Create a snapcraft with the vault yaml from this bug.
   * Add the new go-importpath field.
   * Run snapcraft.
   * Verify that you get a usable snap.

  [Regression Potential]

   * This could affect other go projects.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1583426/+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 1586832] Re: log in with one-time password no longer works on master

[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/1586832

Title:
  log in with one-time password no longer works on master

Status in Snapcraft:
  Fix Released
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:
  I made a mistake in the refactoring of the login method, passing the
  one-time password as token.

  This is a regression on master, but it's a branch that landed last
  week, so it hasn't been released to ubuntu.

  [Impact]

   * Existing users of the ubuntu package are not affected because the
  bug has not been released.

   * The bug affects all users with two-factor autentication enabled
  that want to login with snapcraft.

  [Test Case]

   * set up an account with 2fa.
   * run snapcraft login

  [Regression Potential]

   * Various log in scenarios could be affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1586832/+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 1570944] Re: ppc64le uses the wrong cross build package

[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/1570944

Title:
  ppc64le uses the wrong cross build package

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:
  If cross-compiling for ppc64le, Snapcraft uses gcc-powerpc64-linux-
  gnu. It should probably be using gcc-powerpc64le-linux-gnu. It also
  tries to use "gcc-powerpc64-linux-gnu-" as the prefix (note the "gcc"
  at the beginning).

  [Impact]

   * If cross-compiling for ppc64le, snapcraft tries to use gcc-
  powerpc64-linux-gnu. It should instead be using gcc-powerpc64le-linux-
  gnu.

   * It also tries to use "gcc-powerpc64-linux-gnu-" as the prefix (note
  the "gcc" at the beginning).

  [Test Case]

   1. Only the kbuild and kernel plugins make use of this feature, so first 
find a kernel that can be built for ppc64le.
   2. Build it with `snapcraft --target-arch ppc64le`
   3. Make sure it runs on ppc64le hardware.

  [Regression Potential]

   * None, this wouldn't have ever worked anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1570944/+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 1586504] Re: The interaction with servers is implemented as functions in a module

[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/1586504

Title:
  The interaction with servers is implemented as functions in a module

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:
  We can group all the interactions with each server in a client object.
  That will simplify testing, is cleaner and could make it easier to
  later split the clients to a separate project.

  [Impact]

   * No visual impact for users, the commands are untouched.
   * This change improves the existing code, but also allows us to make an 
easier landing of the macaroons feature.

  [Test Case]

   * snapcraft login.
   * build a snap.
   * snapcraft upload the snap build.
   * check that the snap is in the store.

  [Regression Potential]

   * The existing features that interact with the servers might fail:
  login, upload.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1586504/+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 1575628] Re: Snapcraft doesn't ignore already-built snaps when `source` is the folder containing the `snapcraft.yaml`

[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/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

___
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 1585023] Re: integration tests are skipped when the test user password is not in the env

[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/1585023

Title:
  integration tests are skipped when the test user password is not in
  the env

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:
  We run the integration tests against staging passing the password of
  an existing user in an environment variable.

  When that variable is not present, the tests are skipped.

  We can run the tests against a fake local implementation of the
  servers. Then CI will execute the tests against the staging servers.
  If both tests pass we are ok. If one of them fail, then either the
  fake server is out of sync or there is a real error.

  [Impact]

   * No visible impact for users.

   * This change will prevent regressions on the functions that touch
  the store.

  [Test Case]

   * N/A

  [Regression Potential]

   * The tests could fail, which would block the proposed-migration. If
  the package got to proposed, this didn't happen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1585023/+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 1586511] Re: the config is handled as function in a module

[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/1586511

Title:
  the config is handled as function in a module

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:
  We can improve the config handling by including the save, load and get 
methods in an object.
  This will simplify testing and is cleaner.

  [Impact]

   * No visual impact for users, the config file will have the same format and 
same path.
   * This change improves the existing code, but also allows us to make an 
easier landing of the macaroons feature.

  [Test Case]

   * snapcraft login.
   * build a snap.
   * snapcraft upload the snap build.
   * check that the snap is in the store.
   * snapcraft logout.
   * try snapcraft upload again.
   * check that you get an error.

  [Regression Potential]

   * The existing features that use the config might fail: login,
  upload, logout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1586511/+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 1575581] Re: "snapcraft init" doesn't generate a valid template

[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/1575581

Title:
  "snapcraft init" doesn't generate a valid template

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:
  Using snapcraft 2.8.4 in xenial

  Getting a source and doing "snapcraft init", editing the
  snapcraft.yaml to file the info required and doig "snapcraft build"
  leads to an error "'parts' is a required property" ... if that's
  required the default template should include it or at least a comment
  saying "you need to add a parts section, see documentation on ..."

  [Impact]

   * It's hard for a user to get started.

   * The init template will contain more info, and will be snapcraft-
  able.

  [Test Case]

   * Run snapcraft init
   * Run snapcraft
   * Verify that you get a valid snap.

  [Regression Potential]

   * The only risk would be that the error message is worse than before.
  We added a test to check that there is no error message anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1575581/+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 1588098] Re: The autopkgtests are skiping the ros demo test

[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/1588098

Title:
  The autopkgtests are skiping the ros demo test

Status in Snapcraft:
  Fix Released
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:
  For some reason I never understood, the ros demo was failing in
  autopkgtests. This was not reproducible in my test systems so we
  skipped this test.

  Now it should be reenabled.

  [Impact]

   * No impact for users.

   * This will prevent regressions in the ros demo on future releases.

  [Test Case]

   * N/A. The test will run when the package goes to proposed. If it
  fails, the package won't get there.

  [Regression Potential]

   * autopkgtests could fail. This will block the release to propose so
  we will have a prominent indicator if it happened.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapcraft/+bug/1588098/+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 1590062] Re: [meta] documentation update for xenial

[dann frazier]

** Changed in: installation-guide (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: installation-guide (Ubuntu Xenial)
   Status: Confirmed => In Progress

-- 
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/1590062

Title:
  [meta] documentation update for xenial

Status in installation-guide package in Ubuntu:
  Fix Released
Status in installation-guide source package in Xenial:
  In Progress

Bug description:
  [Impact]
  There are a number of updates needed for the installation guide for >= xenial
   - Ubuntu is described as a desktop operating system - but that's odd text 
for architectures
     where desktop is not appropriate (e.g. s390x)
   - There is no ISO for arm64 (yet) - but the installation guide strongly 
recommends it (xenial-specific)
   - The only ARM firmware described is U-Boot - but we also support UEFI there.
   - Cavium ThunderX is a newly supported arm64 platform - let's mention it.
   - Various software versions are out of date (Linux, GNOME, brltty).

  [Test Case]
  Text changes get rendered :)

  [Regression Risk]
  Minor; it is documentation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/installation-guide/+bug/1590062/+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 1588977] Re: [2.0.6] snapd.refresh.timer fails

[Brian Murray]

** Also affects: snapd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
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/1588977

Title:
  [2.0.6] snapd.refresh.timer fails

Status in snapd package in Ubuntu:
  Fix Committed
Status in snapd source package in Xenial:
  New

Bug description:
  The 2.0.6 update warns with the following message:
  $ sudo apt install snapd/xenial-proposed
  Preparing to unpack .../archives/snapd_2.0.6_amd64.deb ...^M
  Unpacking snapd (2.0.6) over (2.0.5) ...^M
  Processing triggers for man-db (2.7.5-1) ...^M
  Setting up snapd (2.0.6) ...^M
  Job for snapd.refresh.timer failed. See "systemctl status 
snapd.refresh.timer" and "journalctl -xe" for details.^M
  snapd.refresh.timer couldn't start.^M

  And indeed:

  $ sudo systemctl status snapd.refresh.timer|more
  ● snapd.refresh.timer - Timer to automatically refresh installed snaps
     Loaded: loaded (/lib/systemd/system/snapd.refresh.timer; enabled; vendor 
pres
  et: enabled)
     Active: inactive (dead)

  Jun 03 23:21:32 bod systemd[1]: snapd.refresh.timer: Refusing to start, unit 
to
  trigger not loaded.
  Jun 03 23:21:32 bod systemd[1]: Failed to start Timer to automatically 
refresh i
  nstalled snaps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1588977/+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 1584040] Re: Horizon wsgi can run in the wrong WSGIProcessGroup

[Launchpad Bug Tracker]

This bug was fixed in the package horizon - 2:10.0.0~b1-0ubuntu2

---
horizon (2:10.0.0~b1-0ubuntu2) yakkety; urgency=medium

  * Fold Ubuntu theme into themes installed as part of the core
openstack-dashboard package:
- d/openstack-dashboard-ubuntu-theme.*,control:
  Make openstack-dashboard-ubuntu-theme transitional.
- d/openstack-dashboard.install: Install Ubuntu theme.
- d/theme/ubuntu_theme.py: Drop, no longer needed.
- d/p/ubuntu_settings.patch: Add Ubuntu theme to list of available
  themes for users.
  * d/p/*: Refresh.
  * d/openstack-dashboard.conf: Ensure wsgi process-group is set for
horizon application (LP: #1584040), set process display-name to
wsgi application group for ease of debugging.

 -- James Page   Tue, 07 Jun 2016 11:00:15 +0100

** Changed in: horizon (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/1584040

Title:
  Horizon wsgi can run in the wrong WSGIProcessGroup

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive icehouse series:
  New
Status in Ubuntu Cloud Archive kilo series:
  New
Status in Ubuntu Cloud Archive liberty series:
  New
Status in Ubuntu Cloud Archive mitaka series:
  New
Status in Ubuntu Cloud Archive newton series:
  New
Status in horizon package in Ubuntu:
  Fix Released
Status in horizon source package in Trusty:
  New
Status in horizon source package in Wily:
  New
Status in horizon source package in Xenial:
  New
Status in horizon source package in Yakkety:
  Fix Released

Bug description:
  Horizon wsgi can run in the wrong WSGIProcessGroup when multiple
  WSGIProcessGroup are defined. Typically with the 2 following
  configurations enabled on apache2:

  # /etc/apache2/conf-enabled/openstack-dashboard.conf
 WSGIScriptAlias /horizon 
/usr/share/openstack-dashboard/openstack_dashboard/wsgi/django.wsgi
 WSGIDaemonProcess horizon user=horizon group=horizon processes=3 threads=10
 WSGIProcessGroup horizon
 Alias /static /usr/share/openstack-dashboard/openstack_dashboard/static/
 Alias /horizon/static 
/usr/share/openstack-dashboard/openstack_dashboard/static/
 
   Order allow,deny
   Allow from all
 

  # /etc/apache2/conf-enabled/wsgi.conf
 WSGIScriptAlias /mywsgi /usr/share/mywsgi/.. process-group=mywsgi
 WSGIDaemonProcess mywsgi user=mywsgi group=mywsgi processes=5 threads=10
 WSGIProcessGroup mywsgi
 
   Order allow,deny
   Allow from all
 

  Nothing ensures that Horizon wsgi will run in "horizon"
  WSGIProcessGroup.

  
  To ensure it we should use:
 WSGIScriptAlias /horizon 
/usr/share/openstack-dashboard/openstack_dashboard/wsgi/django.wsgi 
processes-group=horizon
  instead of:
 WSGIScriptAlias /horizon 
/usr/share/openstack-dashboard/openstack_dashboard/wsgi/django.wsgi

  
  It affects my Kilo openstack-dashboard on Trusty BUT should affect every 
openstack-dashboard on every ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1584040/+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 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working

[Launchpad Bug Tracker]

This bug was fixed in the package isc-dhcp - 4.3.3-5ubuntu13

---
isc-dhcp (4.3.3-5ubuntu13) yakkety; urgency=medium

  * Fixed missing broadcast flag for Infiniband interfaces (LP: #1529815)
  - added:
+ d/p/dhcp-4.2.4-dhclient-options-changed.patch

 -- Rafael David Tinoco (Inaddy)   Tue, 07
Jun 2016 15:52:40 +0200

** Changed in: isc-dhcp (Ubuntu)
   Status: In Progress => 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/1529815

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Wily:
  In Progress
Status in isc-dhcp source package in Xenial:
  In Progress

Bug description:
  [Impact]

   * Infiniband users relying on DHCP can't use DHCP relay.

  [Test Case]

   * Comment #13
   * Mellanox has tested themselves. 
   * Clear way of knowing if fix worked (tcpdump).

  [Regression Potential]

   * Only related to Infiniband.
   * Infiniband support could stop working (unlikely, already tested).

  [Other Info]

  None

  [ Original Description ]
   
   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance

  DHCP client is sending discover with Unicast type request for the
  offer, in this configuration of IB to ETH through a relay we need the
  type to be broadcast.

  The issue is that when using dhclient from the client on Ubuntu (and only on 
Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in 
unicast instead of broadcast. It seems there is no way to correct this from the 
client side using dhclient configuration file.
  this issue exist even when we use always-broadcast statement in configuration 
file.

  in other vendors we see that discover request type is broadcast.
  attached pcap files from working (other vendor) and not working (Ubuntu) 
clients.

  DHCP CLIENT (IPoIB)
  Ubuntu 14.04  kernel 3.13.0-74
  Mellanox OFED 3.1-1.0.3 or inbox driver
  isc-dhcp-client  4.2.4-7ubuntu12.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+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 1582320] Re: libdebian-installer uses a different detection method for EFI than efivar

[Mathieu Trudel-Lapierre]

** Summary changed:

- Problem detected upon boot/login
+ libdebian-installer uses a different detection method for EFI than efivar

** Also affects: libdebian-installer (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libdebian-installer (Ubuntu Xenial)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: libdebian-installer (Ubuntu Yakkety)
   Importance: Undecided => Critical

** Changed in: libdebian-installer (Ubuntu Yakkety)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: libdebian-installer (Ubuntu Xenial)
   Importance: Undecided => Critical

** Changed in: libdebian-installer (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: libdebian-installer (Ubuntu Yakkety)
   Status: New => In Progress

** Changed in: ubiquity (Ubuntu Xenial)
   Status: Incomplete => Invalid

** Changed in: ubiquity (Ubuntu Yakkety)
   Status: Incomplete => Invalid

-- 
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/1582320

Title:
  libdebian-installer uses a different detection method for EFI than
  efivar

Status in libdebian-installer package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  Invalid
Status in libdebian-installer source package in Xenial:
  In Progress
Status in ubiquity source package in Xenial:
  Invalid
Status in libdebian-installer source package in Yakkety:
  In Progress
Status in ubiquity source package in Yakkety:
  Invalid

Bug description:
  [Impact]
  Some systems which do not correctly support EFI variables or have an 
incomplete implementation of the EFI spec may fail to install due to efibootmgr 
being unable to set BootEntry although archdetect reports the system being 
booted in EFI mode.

  [Test case]
  1) boot in EFI mode
  TEST) Unmount /sys/firmware/efi/efivars and/or remove efivars module.
  2) Run archdetect.

  [Regression potential]
  If efivars or vars don't get mounted (use of another init system than 
systemd, or lack of the efivars kernel module); the detection code will fail to 
see that the system is in EFI mode and installation will proceed in legacy mode.

  --

  After installing 16.04 (upgrade or re-install), I get this exception
  on login.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shim-signed 1.12+0.8-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootEFIContents:
   fw
   fwupx64.efi
  Date: Mon May 16 09:28:29 2016
  Df:
   Filesystem 1K-blocks Used Available Use% Mounted on
   /dev/sdb2  208735776 11061044 187048532   6% /
   /dev/sr0 1451056  1451056 0 100% /cdrom
   udev 78945400   7894540   0% /dev
   tmpfs1581840 9536   1572304   1% /run
  EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2: 
efibootmgr: EFI variables are not supported on this system.
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: shim-signed
  Title: package shim-signed 1.12+0.8-0ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdebian-installer/+bug/1582320/+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 1587475] Re: Kernel panic on btrfs mount and ls

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7-rc1 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc1-yakkety/

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Tags removed: trusty
** Tags added: kernel-da-key xenial

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Xenial)
   Status: New => Incomplete

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

-- 
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/1587475

Title:
  Kernel panic on btrfs mount and ls

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  Kernel panic happens after mount and ls specific btrfs image

  Way to reproduce:
  1. download and unpack btrfs image from tar(sparse file)(tar -Sxf img.tar)
  2. mount btrfs (sudo mount -t btrfs -o rw,noatime,compress=no,commit=5 
71bb49cf-26f1-484a-832c-e966f43adca9.img broken)
  3. list files in mount point (ls -al broken)

  the system down to kernel panic with log above

  (looks like 3.19.x and 4.2.x not affected, only 4.4.x)

  dmesg log:
  May 31 13:02:21 fs-new kernel: [  694.744630] BTRFS error (device loop0): 
parent transid verify failed on 30425088 wanted 120 found 119
  May 31 13:02:21 fs-new kernel: [  694.747077] BTRFS error (device loop0): 
parent transid verify failed on 30425088 wanted 120 found 119
  May 31 13:02:21 fs-new kernel: [  694.747128] [ cut here 
]
  May 31 13:02:21 fs-new kernel: [  694.747135] WARNING: CPU: 0 PID: 13795 at 
/build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/lib/idr.c:1051 
ida_remove+0xfa/0x130()
  May 31 13:02:21 fs-new kernel: [  694.747136] ida_remove called for id=47 
which is not allocated.
  May 31 13:02:21 fs-new kernel: [  694.747137] Modules linked in: ufs qnx4 
hfsplus hfs minix ntfs msdos jfs xfs libcrc32c nfsv3 vboxsf xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack zram 
lz4_compress xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables autofs4 
ppdev vboxvideo ttm crct10dif_pclmul crc32_pclmul drm_kms_helper drm 
aesni_intel aes_x86_64 lrw input_leds gf128mul nfsd glue_helper ablk_helper 
cryptd auth_rpcgss serio_raw nfs_acl nfs fb_sys_fops syscopyarea lockd 
sysfillrect grace 8250_fintek parport_pc sysimgblt vboxguest i2c_piix4 sunrpc 
video mac_hid fscache lp parport zfs(POE) zunicode(POE) zcommon(POE) 
znvpair(POE) spl(OE) zavl(POE) btrfs xor raid6_pq psmouse e1000 fjes pata_acpi
  May 31 13:02:21 fs-new kernel: [  694.747182] CPU: 0 PID: 13795 Comm: ls 
Tainted: P   OE   4.4.0-22-generic #40~14.04.1-Ubuntu
  May 31 13:02:21 fs-new kernel: [  694.747183] Hardware name: innotek GmbH 
VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
  May 31 13:02:21 fs-new kernel: [  694.747185]   
8800024e7a88 813cde6c 8800024e7ad0
  May 31 13:02:21 fs-new kernel: [  694.747187]  81af5298 
8800024e7ac0 8107d856 
  May 31 13:02:21 fs-new kernel: [  694.747189]  81fce200 
88003c827a00 88003616e068 0001
  May 31 13:02:21 fs-new kernel: [  694.747191] Call Trace:
  May 31 13:02:21 fs-new kernel: [  694.747195]  [] 
dump_stack+0x63/0x87
  May 31 13:02:21 fs-new kernel: [  694.747199]  [] 
warn_slowpath_common+0x86/0xc0
  May 31 13:02:21 fs-new kernel: [  694.747201]  [] 
warn_slowpath_fmt+0x4c/0x50
  May 31 13:02:21 fs-new kernel: [  694.747214]  [] ? 
free_percpu+0xba/0x180
  May 31 13:02:21 fs-new kernel: [  694.747217]  [] 
ida_remove+0xfa/0x130
  May 31 13:02:21 fs-new kernel: [  694.747220]  [] 
free_anon_bdev+0x2c/0x50
  May 31 13:02:21 fs-new kernel: [  694.747239]  [] 
free_fs_root+0xbe/0xe0 [btrfs]
  May 31 13:02:21 fs-new kernel: [  694.747251]  [] 
btrfs_get_fs_root+0x216/0x250 [btrfs]
  May 31 13:02:21 fs-new kernel: [  694.747264]  [] ? 
memcmp_extent_buffer+0xbd/0x120 [btrfs]
  May 31 13:02:21 fs-new kernel: [  694.747277]  [] 
btrfs_lookup_dentry+0x28c/0x4c0 [btrfs]
  May 31 13:02:21 fs-new kernel: [  694.747288]  [] 
btrfs_lookup+0x12/0x40 [btrfs]
  May 31 13:02:21 fs-new kernel: [  694.747291]  [] 
lookup_real+0x1d/0x50
  May 31 13:02:21 fs-new kernel: [  694.747293]  [] 
__lookup_hash+0x33/0x40
  May 

[Group.of.nepali.translators] [Bug 1587510] Re: Thinkpad keyboard backlight is not properly restored on resume from suspend

[Joseph Salisbury]

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
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/1587510

Title:
  Thinkpad keyboard backlight is not properly restored on resume from
  suspend

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  New

Bug description:
  This is fixed in: https://github.com/torvalds/linux/commit/afcedeb

  Please backport this to Yakkety and to Xenial (once lp:1574498 fix is 
released)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marco  2143 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=e95ce812-4be1-4186-9f30-e10d6d6430f5
  InstallationDate: Installed on 2016-05-02 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160415)
  MachineType: LENOVO 20F9CTO1WW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=328bf97f-143a-483c-8ca9-282e1bfbdf79 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 04/14/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET43W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET43W(1.11):bd04/14/2016:svnLENOVO:pn20F9CTO1WW:pvrThinkPadT460s:rvnLENOVO:rn20F9CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20F9CTO1WW
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1587510/+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 1576726] Re: [SRU] network-manager 1.2.0

[Amr Ibrahim]

** Also affects: network-manager-pptp (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1576726

Title:
  [SRU] network-manager 1.2.0

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-openconnect package in Ubuntu:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Confirmed
Status in network-manager-pptp package in Ubuntu:
  New
Status in network-manager-ssh package in Ubuntu:
  Fix Released
Status in network-manager-vpnc package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Released
Status in network-manager-openconnect source package in Xenial:
  Confirmed
Status in network-manager-openvpn source package in Xenial:
  Confirmed
Status in network-manager-ssh source package in Xenial:
  Confirmed
Status in network-manager-vpnc source package in Xenial:
  Confirmed
Status in network-manager-openconnect package in Debian:
  Fix Released

Bug description:
  [Impact]
  Xenial was released with upstream beta2 version of network-manager to keep in 
time for the release schedule, and upstream stable release has been made so 
it's time to update to it.

  [Testcase]
  After upgrading the package, user should still be able to connect to networks 
like Ethernet, Wi-Fi and VPNs.

  [Regression Potential]
  Potential of causing regression is relatively small because there is not big 
changes made during beta2 -> stable process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576726/+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 1585948] Re: Mitaka Ubuntu theme has a number of bugs

[James Page]

This bug was fixed in the package horizon - 2:9.0.0-0ubuntu2.16.04.1~cloud0
---

 horizon (2:9.0.0-0ubuntu2.16.04.1~cloud0) trusty-mitaka; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 horizon (2:9.0.0-0ubuntu2.16.04.1) xenial; urgency=medium
 .
   * d/theme/ubuntu/*: Refresh with misc fixes from the Canonical design
 team (LP: #1585948).


** Changed in: cloud-archive/mitaka
   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/1585948

Title:
  Mitaka Ubuntu theme has a number of bugs

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  Fix Released
Status in Ubuntu Cloud Archive newton series:
  Fix Released
Status in horizon package in Ubuntu:
  Fix Released
Status in horizon source package in Xenial:
  Fix Released
Status in horizon source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Misc niggles that make the Ubuntu theme for the dashboard look a bit 
inconsistent with previous versions.

  [Test Case]
  sudo apt-get install openstack-dashboard
  
  Go to login screen (two logos displayed)

  [Regression Potential]
  Minimal - just theme updates

  [Original Bug Report]
  Specifically:

  The login screen displays both the default OpenStack Logo and the
  Ubuntu branded one.

  Some spacing is not consistent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1585948/+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