[Group.of.nepali.translators] [Bug 1734983] Re: Request to backport sosreport v3.5

2021-03-15 Thread Bug Watch Updater 
** Changed in: sosreport (Debian)
   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/1734983

Title:
  Request to backport sosreport v3.5

Status in sosreport:
  Fix Released
Status in sosreport package in Ubuntu:
  Fix Released
Status in sosreport source package in Trusty:
  Fix Released
Status in sosreport source package in Xenial:
  Fix Released
Status in sosreport source package in Zesty:
  Won't Fix
Status in sosreport source package in Artful:
  Fix Released
Status in sosreport source package in Bionic:
  Fix Released
Status in sosreport package in Debian:
  Fix Released

Bug description:
  [Impact]

  Canonical support team (AKA STS) largely depend on sosreport package
  to troubleshoot system.

  sosreport is always in constant development including new bugfixes,
  new features such as new plugins[1],  that can be interesting to
  have in a support context.

  v3.5 is already found in devel release (bionic). We create this LP in
  the attempt to justify the SRU of v3.5 backport into current supported
  stable releases.

  [1] - New plugins for :
  * perl
  * boom
  * vdo
  * os_net_config
  * conntrackd
  * ovirt_imageio
  * nss
  * sas3ircu
  * openstack_aodh
  * docker_distribution
  * gluster_block
  * snappy

  Plugin API enhancements
  * Plugin triggers by executable name
  * Improved log size limit handling
  * Better handling of compressed log files
  * Per-plugin package verification lists

  Updates to 227 plugins

  This will also allow us to close some sosreport LP bugs:
  *Docker plugin uses the wrong command for Ubuntu (LP: #1693574)

  [Test Case]

   * Install sosreport
     $ apt-get install sosreport

   * Run sosreport
     $ sosreport -a
     $ sosreport -o 
     $ ...

   * Make sure it generate a tar.xz file in /tmp in the form of
     "/tmp/sosreport--.tar.xz"

   * Extract files from archive
     $ tar Jxvf /tmp/sosreport--.tar.xz

   * Look the content of sosreport, make sure the information is
  accurate and valid, 

   * Make sure all files that should to be collected by sosreport aren't 0 
size. (Files that should be collected may varies from one system to another, it 
depends on what packages are installed, ...)
     $ find /tmp/sosreport-- -size 0

  # Note :
  It is normal to see some 0 size files here and there, again it depend on how 
the plugin is run (package detection or not inside the plugins, ...) and if the 
package is installed or not on the system where you run sosreport. But in most 
cases, if the package is installed and if sosreport has a plugin for it then it 
should gather information, if not then it might be a problem with the plugins 
itself that need adjustments.

  [Regression Potential]

   * autopkgtest[2] didn't reveal any
  [2] - See Comment #1

   * We,STS, have intensively tested the package.

  During our testing, we found a severe regression that we already took
  action to fix it via :

  - Upstream issue - https://github.com/sosreport/sos/issues/1155
  - Debian bug - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883537
  - Fix Released in Ubuntu Devel release (bionic) via debdiff : 
lp1734983_bionic.debdiff

  [Other Info]

   * Sosreport upstream :
     https://github.com/sosreport/sos

   * rmadison -u debian,ubuntu sosreport
  debian:
  sosreport  | 3.2-2| oldstable  | source, amd64, 
arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x
  sosreport  | 3.2-2| oldstable-kfreebsd | source, 
kfreebsd-amd64, kfreebsd-i386
  sosreport  | 3.3+git50-g3c0349b-2 | stable | source, amd64, 
arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
  sosreport  | 3.5-1| testing| source, amd64, 
arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
  sosreport  | 3.5-1| unstable   | source, amd64, 
arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
  ubuntu:
   sosreport | 3.0-1~ubuntu12.04.1  | precise-backports/universe | 
source, amd64, armel, armhf, i386, powerpc
   sosreport | 3.1-1ubuntu2 | trusty | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.1-1ubuntu2.2   | trusty-security| 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.2-2~ubuntu14.04.1  | trusty-backports   | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.2+git276-g7da50d6-3ubuntu1 | xenial | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
   sosreport | 3.3+git50-g3c0349b-2

[Group.of.nepali.translators] [Bug 1734983] Re: Request to backport sosreport v3.5

2019-05-16 Thread Bug Watch Updater 
** Changed in: sosreport
   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/1734983

Title:
  Request to backport sosreport v3.5

Status in sosreport:
  Fix Released
Status in sosreport package in Ubuntu:
  Fix Released
Status in sosreport source package in Trusty:
  Fix Released
Status in sosreport source package in Xenial:
  Fix Released
Status in sosreport source package in Zesty:
  Won't Fix
Status in sosreport source package in Artful:
  Fix Released
Status in sosreport source package in Bionic:
  Fix Released
Status in sosreport package in Debian:
  New

Bug description:
  [Impact]

  Canonical support team (AKA STS) largely depend on sosreport package
  to troubleshoot system.

  sosreport is always in constant development including new bugfixes,
  new features such as new plugins[1],  that can be interesting to
  have in a support context.

  v3.5 is already found in devel release (bionic). We create this LP in
  the attempt to justify the SRU of v3.5 backport into current supported
  stable releases.

  [1] - New plugins for :
  * perl
  * boom
  * vdo
  * os_net_config
  * conntrackd
  * ovirt_imageio
  * nss
  * sas3ircu
  * openstack_aodh
  * docker_distribution
  * gluster_block
  * snappy

  Plugin API enhancements
  * Plugin triggers by executable name
  * Improved log size limit handling
  * Better handling of compressed log files
  * Per-plugin package verification lists

  Updates to 227 plugins

  This will also allow us to close some sosreport LP bugs:
  *Docker plugin uses the wrong command for Ubuntu (LP: #1693574)

  [Test Case]

   * Install sosreport
     $ apt-get install sosreport

   * Run sosreport
     $ sosreport -a
     $ sosreport -o 
     $ ...

   * Make sure it generate a tar.xz file in /tmp in the form of
     "/tmp/sosreport--.tar.xz"

   * Extract files from archive
     $ tar Jxvf /tmp/sosreport--.tar.xz

   * Look the content of sosreport, make sure the information is
  accurate and valid, 

   * Make sure all files that should to be collected by sosreport aren't 0 
size. (Files that should be collected may varies from one system to another, it 
depends on what packages are installed, ...)
     $ find /tmp/sosreport-- -size 0

  # Note :
  It is normal to see some 0 size files here and there, again it depend on how 
the plugin is run (package detection or not inside the plugins, ...) and if the 
package is installed or not on the system where you run sosreport. But in most 
cases, if the package is installed and if sosreport has a plugin for it then it 
should gather information, if not then it might be a problem with the plugins 
itself that need adjustments.

  [Regression Potential]

   * autopkgtest[2] didn't reveal any
  [2] - See Comment #1

   * We,STS, have intensively tested the package.

  During our testing, we found a severe regression that we already took
  action to fix it via :

  - Upstream issue - https://github.com/sosreport/sos/issues/1155
  - Debian bug - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883537
  - Fix Released in Ubuntu Devel release (bionic) via debdiff : 
lp1734983_bionic.debdiff

  [Other Info]

   * Sosreport upstream :
     https://github.com/sosreport/sos

   * rmadison -u debian,ubuntu sosreport
  debian:
  sosreport  | 3.2-2| oldstable  | source, amd64, 
arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x
  sosreport  | 3.2-2| oldstable-kfreebsd | source, 
kfreebsd-amd64, kfreebsd-i386
  sosreport  | 3.3+git50-g3c0349b-2 | stable | source, amd64, 
arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
  sosreport  | 3.5-1| testing| source, amd64, 
arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
  sosreport  | 3.5-1| unstable   | source, amd64, 
arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
  ubuntu:
   sosreport | 3.0-1~ubuntu12.04.1  | precise-backports/universe | 
source, amd64, armel, armhf, i386, powerpc
   sosreport | 3.1-1ubuntu2 | trusty | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.1-1ubuntu2.2   | trusty-security| 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.2-2~ubuntu14.04.1  | trusty-backports   | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.2+git276-g7da50d6-3ubuntu1 | xenial | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
   sosreport | 3.3+git50-g3c0349b-2 | zesty

[Group.of.nepali.translators] [Bug 1734983] Re: Request to backport sosreport v3.5

2018-02-08 Thread Launchpad Bug Tracker 
This bug was fixed in the package sosreport - 3.5-1~ubuntu14.04.2

---
sosreport (3.5-1~ubuntu14.04.2) trusty; urgency=medium

  * d/p/0003-fix-name-containers-is-not-defined.patch:
"containers" is an unknown variable, "insp" is the correct one.
(LP: #1734983)

sosreport (3.5-1~ubuntu14.04.1) trusty; urgency=medium

  * New upstream release v3.5 (LP: #1734983)
New features include :
New plugins for :
* perl
* boom
* vdo
* os_net_config
* conntrackd
* ovirt_imageio
* nss
* sas3ircu
* openstack_aodh
* docker_distribution
* gluster_block
* snappy

  * Plugin API enhancements
* Plugin triggers by executable name
* Improved log size limit handling
* Better handling of compressed log files
* Per-plugin package verification lists

  * Updates to 227 plugins

  * Debian modifications:
- Addition of DEP8 tests
- Do not run Python2 only tests

  * d/p/0002-reset-to-expected-variable-order-for-packagemanager.patch:
Fixing severe regression where many "packages = " lines are no
longer working in Debian/Ubuntu. Preventing automatic package detection.

 -- Eric Desrochers   Thu, 25 Jan 2018
16:01:03 -0500

** Changed in: sosreport (Ubuntu Trusty)
   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/1734983

Title:
  Request to backport sosreport v3.5

Status in sosreport:
  New
Status in sosreport package in Ubuntu:
  Fix Released
Status in sosreport source package in Trusty:
  Fix Released
Status in sosreport source package in Xenial:
  Fix Released
Status in sosreport source package in Zesty:
  Won't Fix
Status in sosreport source package in Artful:
  Fix Released
Status in sosreport source package in Bionic:
  Fix Released
Status in sosreport package in Debian:
  New

Bug description:
  [Impact]

  Canonical support team (AKA STS) largely depend on sosreport package
  to troubleshoot system.

  sosreport is always in constant development including new bugfixes,
  new features such as new plugins[1],  that can be interesting to
  have in a support context.

  v3.5 is already found in devel release (bionic). We create this LP in
  the attempt to justify the SRU of v3.5 backport into current supported
  stable releases.

  [1] - New plugins for :
  * perl
  * boom
  * vdo
  * os_net_config
  * conntrackd
  * ovirt_imageio
  * nss
  * sas3ircu
  * openstack_aodh
  * docker_distribution
  * gluster_block
  * snappy

  Plugin API enhancements
  * Plugin triggers by executable name
  * Improved log size limit handling
  * Better handling of compressed log files
  * Per-plugin package verification lists

  Updates to 227 plugins

  This will also allow us to close some sosreport LP bugs:
  *Docker plugin uses the wrong command for Ubuntu (LP: #1693574)

  [Test Case]

   * Install sosreport
     $ apt-get install sosreport

   * Run sosreport
     $ sosreport -a
     $ sosreport -o 
     $ ...

   * Make sure it generate a tar.xz file in /tmp in the form of
     "/tmp/sosreport--.tar.xz"

   * Extract files from archive
     $ tar Jxvf /tmp/sosreport--.tar.xz

   * Look the content of sosreport, make sure the information is
  accurate and valid, 

   * Make sure all files that should to be collected by sosreport aren't 0 
size. (Files that should be collected may varies from one system to another, it 
depends on what packages are installed, ...)
     $ find /tmp/sosreport-- -size 0

  # Note :
  It is normal to see some 0 size files here and there, again it depend on how 
the plugin is run (package detection or not inside the plugins, ...) and if the 
package is installed or not on the system where you run sosreport. But in most 
cases, if the package is installed and if sosreport has a plugin for it then it 
should gather information, if not then it might be a problem with the plugins 
itself that need adjustments.

  [Regression Potential]

   * autopkgtest[2] didn't reveal any
  [2] - See Comment #1

   * We,STS, have intensively tested the package.

  During our testing, we found a severe regression that we already took
  action to fix it via :

  - Upstream issue - https://github.com/sosreport/sos/issues/1155
  - Debian bug - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883537
  - Fix Released in Ubuntu Devel release (bionic) via debdiff : 
lp1734983_bionic.debdiff

  [Other Info]

   * Sosreport upstream :
     https://github.com/sosreport/sos

   * rmadison -u debian,ubuntu sosreport
  debian:
  sosreport  | 3.2-2| oldstable  | source, amd64, 
arm64,

[Group.of.nepali.translators] [Bug 1734983] Re: Request to backport sosreport v3.5

2018-02-08 Thread Launchpad Bug Tracker 
This bug was fixed in the package sosreport - 3.5-1~ubuntu16.04.2

---
sosreport (3.5-1~ubuntu16.04.2) xenial; urgency=medium

  * d/p/0003-fix-name-containers-is-not-defined.patch:
"containers" is an unknown variable, "insp" is the correct one.
(LP: #1734983)

sosreport (3.5-1~ubuntu16.04.1) xenial; urgency=medium

  * New upstream release v3.5 (LP: #1734983)
New features include :
New plugins for :
* perl
* boom
* vdo
* os_net_config
* conntrackd
* ovirt_imageio
* nss
* sas3ircu
* openstack_aodh
* docker_distribution
* gluster_block
* snappy

  * Plugin API enhancements
* Plugin triggers by executable name
* Improved log size limit handling
* Better handling of compressed log files
* Per-plugin package verification lists

  * Updates to 227 plugins

  * Debian modifications:
- Addition of DEP8 tests
- Do not run Python2 only tests

  * d/p/0002-reset-to-expected-variable-order-for-packagemanager.patch:
Fixing severe regression where many "packages = " lines are no
longer working in Debian/Ubuntu. Preventing automatic package detection.

 -- Eric Desrochers   Thu, 25 Jan 2018
15:55:05 -0500

** Changed in: sosreport (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/1734983

Title:
  Request to backport sosreport v3.5

Status in sosreport:
  New
Status in sosreport package in Ubuntu:
  Fix Released
Status in sosreport source package in Trusty:
  Fix Released
Status in sosreport source package in Xenial:
  Fix Released
Status in sosreport source package in Zesty:
  Won't Fix
Status in sosreport source package in Artful:
  Fix Released
Status in sosreport source package in Bionic:
  Fix Released
Status in sosreport package in Debian:
  New

Bug description:
  [Impact]

  Canonical support team (AKA STS) largely depend on sosreport package
  to troubleshoot system.

  sosreport is always in constant development including new bugfixes,
  new features such as new plugins[1],  that can be interesting to
  have in a support context.

  v3.5 is already found in devel release (bionic). We create this LP in
  the attempt to justify the SRU of v3.5 backport into current supported
  stable releases.

  [1] - New plugins for :
  * perl
  * boom
  * vdo
  * os_net_config
  * conntrackd
  * ovirt_imageio
  * nss
  * sas3ircu
  * openstack_aodh
  * docker_distribution
  * gluster_block
  * snappy

  Plugin API enhancements
  * Plugin triggers by executable name
  * Improved log size limit handling
  * Better handling of compressed log files
  * Per-plugin package verification lists

  Updates to 227 plugins

  This will also allow us to close some sosreport LP bugs:
  *Docker plugin uses the wrong command for Ubuntu (LP: #1693574)

  [Test Case]

   * Install sosreport
     $ apt-get install sosreport

   * Run sosreport
     $ sosreport -a
     $ sosreport -o 
     $ ...

   * Make sure it generate a tar.xz file in /tmp in the form of
     "/tmp/sosreport--.tar.xz"

   * Extract files from archive
     $ tar Jxvf /tmp/sosreport--.tar.xz

   * Look the content of sosreport, make sure the information is
  accurate and valid, 

   * Make sure all files that should to be collected by sosreport aren't 0 
size. (Files that should be collected may varies from one system to another, it 
depends on what packages are installed, ...)
     $ find /tmp/sosreport-- -size 0

  # Note :
  It is normal to see some 0 size files here and there, again it depend on how 
the plugin is run (package detection or not inside the plugins, ...) and if the 
package is installed or not on the system where you run sosreport. But in most 
cases, if the package is installed and if sosreport has a plugin for it then it 
should gather information, if not then it might be a problem with the plugins 
itself that need adjustments.

  [Regression Potential]

   * autopkgtest[2] didn't reveal any
  [2] - See Comment #1

   * We,STS, have intensively tested the package.

  During our testing, we found a severe regression that we already took
  action to fix it via :

  - Upstream issue - https://github.com/sosreport/sos/issues/1155
  - Debian bug - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883537
  - Fix Released in Ubuntu Devel release (bionic) via debdiff : 
lp1734983_bionic.debdiff

  [Other Info]

   * Sosreport upstream :
     https://github.com/sosreport/sos

   * rmadison -u debian,ubuntu sosreport
  debian:
  sosreport  | 3.2-2| oldstable  | source, amd64, 
arm64,

[Group.of.nepali.translators] [Bug 1734983] Re: Request to backport sosreport v3.5

2018-02-08 Thread Launchpad Bug Tracker 
This bug was fixed in the package sosreport - 3.5-1~ubuntu17.10.2

---
sosreport (3.5-1~ubuntu17.10.2) artful; urgency=medium

  * d/p/0003-fix-name-containers-is-not-defined.patch:
"containers" is an unknown variable, "insp" is the correct one.
(LP: #1734983)

sosreport (3.5-1~ubuntu17.10.1) artful; urgency=medium

  * New upstream release v3.5 (LP: #1734983)
New features include :
New plugins for :
* perl
* boom
* vdo
* os_net_config
* conntrackd
* ovirt_imageio
* nss
* sas3ircu
* openstack_aodh
* docker_distribution
* gluster_block
* snappy

  * Plugin API enhancements
* Plugin triggers by executable name
* Improved log size limit handling
* Better handling of compressed log files
* Per-plugin package verification lists

  * Updates to 227 plugins

  * Debian modifications:
- Addition of DEP8 tests
- Do not run Python2 only tests

  * d/p/0002-reset-to-expected-variable-order-for-packagemanager.patch:
Fixing severe regression where many "packages = " lines are no
longer working in Debian/Ubuntu. Preventing automatic package detection.

 -- Eric Desrochers   Thu, 25 Jan 2018
16:10:26 -0500

** Changed in: sosreport (Ubuntu Artful)
   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/1734983

Title:
  Request to backport sosreport v3.5

Status in sosreport:
  New
Status in sosreport package in Ubuntu:
  Fix Released
Status in sosreport source package in Trusty:
  Fix Committed
Status in sosreport source package in Xenial:
  Fix Released
Status in sosreport source package in Zesty:
  Won't Fix
Status in sosreport source package in Artful:
  Fix Released
Status in sosreport source package in Bionic:
  Fix Released
Status in sosreport package in Debian:
  New

Bug description:
  [Impact]

  Canonical support team (AKA STS) largely depend on sosreport package
  to troubleshoot system.

  sosreport is always in constant development including new bugfixes,
  new features such as new plugins[1],  that can be interesting to
  have in a support context.

  v3.5 is already found in devel release (bionic). We create this LP in
  the attempt to justify the SRU of v3.5 backport into current supported
  stable releases.

  [1] - New plugins for :
  * perl
  * boom
  * vdo
  * os_net_config
  * conntrackd
  * ovirt_imageio
  * nss
  * sas3ircu
  * openstack_aodh
  * docker_distribution
  * gluster_block
  * snappy

  Plugin API enhancements
  * Plugin triggers by executable name
  * Improved log size limit handling
  * Better handling of compressed log files
  * Per-plugin package verification lists

  Updates to 227 plugins

  This will also allow us to close some sosreport LP bugs:
  *Docker plugin uses the wrong command for Ubuntu (LP: #1693574)

  [Test Case]

   * Install sosreport
     $ apt-get install sosreport

   * Run sosreport
     $ sosreport -a
     $ sosreport -o 
     $ ...

   * Make sure it generate a tar.xz file in /tmp in the form of
     "/tmp/sosreport--.tar.xz"

   * Extract files from archive
     $ tar Jxvf /tmp/sosreport--.tar.xz

   * Look the content of sosreport, make sure the information is
  accurate and valid, 

   * Make sure all files that should to be collected by sosreport aren't 0 
size. (Files that should be collected may varies from one system to another, it 
depends on what packages are installed, ...)
     $ find /tmp/sosreport-- -size 0

  # Note :
  It is normal to see some 0 size files here and there, again it depend on how 
the plugin is run (package detection or not inside the plugins, ...) and if the 
package is installed or not on the system where you run sosreport. But in most 
cases, if the package is installed and if sosreport has a plugin for it then it 
should gather information, if not then it might be a problem with the plugins 
itself that need adjustments.

  [Regression Potential]

   * autopkgtest[2] didn't reveal any
  [2] - See Comment #1

   * We,STS, have intensively tested the package.

  During our testing, we found a severe regression that we already took
  action to fix it via :

  - Upstream issue - https://github.com/sosreport/sos/issues/1155
  - Debian bug - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883537
  - Fix Released in Ubuntu Devel release (bionic) via debdiff : 
lp1734983_bionic.debdiff

  [Other Info]

   * Sosreport upstream :
     https://github.com/sosreport/sos

   * rmadison -u debian,ubuntu sosreport
  debian:
  sosreport  | 3.2-2| oldstable  | source, amd64, 
arm64,

[Group.of.nepali.translators] [Bug 1734983] Re: Request to backport sosreport v3.5

2018-01-16 Thread Alex Moldovan 
Marked Zesty as invalid as it reached end of like on Jan 13 2018.

** Changed in: sosreport (Ubuntu Zesty)
   Status: Fix Committed => 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/1734983

Title:
  Request to backport sosreport v3.5

Status in sosreport:
  New
Status in sosreport package in Ubuntu:
  Fix Released
Status in sosreport source package in Trusty:
  Fix Committed
Status in sosreport source package in Xenial:
  Fix Committed
Status in sosreport source package in Zesty:
  Invalid
Status in sosreport source package in Artful:
  Fix Committed
Status in sosreport source package in Bionic:
  Fix Released
Status in sosreport package in Debian:
  New

Bug description:
  [Impact]

  Canonical support team (AKA STS) largely depend on sosreport package
  to troubleshoot system.

  sosreport is always in constant development including new bugfixes,
  new features such as new plugins[1],  that can be interesting to
  have in a support context.

  v3.5 is already found in devel release (bionic). We create this LP in
  the attempt to justify the SRU of v3.5 backport into current supported
  stable releases.

  [1] - New plugins for :
  * perl
  * boom
  * vdo
  * os_net_config
  * conntrackd
  * ovirt_imageio
  * nss
  * sas3ircu
  * openstack_aodh
  * docker_distribution
  * gluster_block
  * snappy

  Plugin API enhancements
  * Plugin triggers by executable name
  * Improved log size limit handling
  * Better handling of compressed log files
  * Per-plugin package verification lists

  Updates to 227 plugins

  This will also allow us to close some sosreport LP bugs:
  *Docker plugin uses the wrong command for Ubuntu (LP: #1693574)

  [Test Case]

   * Install sosreport
     $ apt-get install sosreport

   * Run sosreport
     $ sosreport -a
     $ sosreport -o 
     $ ...

   * Make sure it generate a tar.xz file in /tmp in the form of
     "/tmp/sosreport--.tar.xz"

   * Extract files from archive
     $ tar Jxvf /tmp/sosreport--.tar.xz

   * Look the content of sosreport, make sure the information is
  accurate and valid, 

   * Make sure all files that should to be collected by sosreport aren't 0 
size. (Files that should be collected may varies from one system to another, it 
depends on what packages are installed, ...)
     $ find /tmp/sosreport-- -size 0

  # Note :
  It is normal to see some 0 size files here and there, again it depend on how 
the plugin is run (package detection or not inside the plugins, ...) and if the 
package is installed or not on the system where you run sosreport. But in most 
cases, if the package is installed and if sosreport has a plugin for it then it 
should gather information, if not then it might be a problem with the plugins 
itself that need adjustments.

  [Regression Potential]

   * autopkgtest[2] didn't reveal any
  [2] - See Comment #1

   * We,STS, have intensively tested the package.

  During our testing, we found a severe regression that we already took
  action to fix it via :

  - Upstream issue - https://github.com/sosreport/sos/issues/1155
  - Debian bug - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883537
  - Fix Released in Ubuntu Devel release (bionic) via debdiff : 
lp1734983_bionic.debdiff

  [Other Info]

   * Sosreport upstream :
     https://github.com/sosreport/sos

   * rmadison -u debian,ubuntu sosreport
  debian:
  sosreport  | 3.2-2| oldstable  | source, amd64, 
arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x
  sosreport  | 3.2-2| oldstable-kfreebsd | source, 
kfreebsd-amd64, kfreebsd-i386
  sosreport  | 3.3+git50-g3c0349b-2 | stable | source, amd64, 
arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
  sosreport  | 3.5-1| testing| source, amd64, 
arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
  sosreport  | 3.5-1| unstable   | source, amd64, 
arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
  ubuntu:
   sosreport | 3.0-1~ubuntu12.04.1  | precise-backports/universe | 
source, amd64, armel, armhf, i386, powerpc
   sosreport | 3.1-1ubuntu2 | trusty | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.1-1ubuntu2.2   | trusty-security| 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.2-2~ubuntu14.04.1  | trusty-backports   | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.2+git276-g7da50d6-3ubuntu1 | xenial | 
source, amd64, arm64, armhf, i386,

[Group.of.nepali.translators] [Bug 1734983] Re: Request to backport sosreport v3.5

2017-12-07 Thread Eric Desrochers 
** Changed in: sosreport (Ubuntu Bionic)
   Status: Fix Released => In Progress

** Changed in: sosreport (Ubuntu Bionic)
 Assignee: (unassigned) => Eric Desrochers (slashd)

** Changed in: sosreport (Ubuntu Bionic)
   Importance: Undecided => Medium

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

Title:
  Request to backport sosreport v3.5

Status in sosreport:
  New
Status in sosreport package in Ubuntu:
  In Progress
Status in sosreport source package in Trusty:
  New
Status in sosreport source package in Xenial:
  New
Status in sosreport source package in Zesty:
  New
Status in sosreport source package in Artful:
  New
Status in sosreport source package in Bionic:
  In Progress
Status in sosreport package in Debian:
  New

Bug description:
  [Impact]

  Canonical support team (AKA STS) largely depend on sosreport package
  to troubleshoot system.

  sosreport is always in constant development including new bugfixes,
  new features such as new plugins[1],  that can be interesting to
  have in a support context.

  v3.5 is already found in devel release (bionic). We create this LP in
  the attempt to justify the SRU of v3.5 backport into current supported
  stable releases.

  [1] - New plugins for :
  * perl
  * boom
  * vdo
  * os_net_config
  * conntrackd
  * ovirt_imageio
  * nss
  * sas3ircu
  * openstack_aodh
  * docker_distribution
  * gluster_block
  * snappy

  Plugin API enhancements
  * Plugin triggers by executable name
  * Improved log size limit handling
  * Better handling of compressed log files
  * Per-plugin package verification lists

  Updates to 227 plugins

  This will also allow us to close some sosreport LP bugs:
  *Docker plugin uses the wrong command for Ubuntu (LP: #1693574)

  [Test Case]

   * Install sosreport
     $ apt-get install sosreport

   * Run sosreport
     $ sosreport -a
     $ sosreport -o 
     $ ...

   * Make sure it generate a tar.xz file in /tmp in the form of
     "/tmp/sosreport--.tar.xz"

   * Extract files from archive
     tar Jxvf /tmp/sosreport--.tar.xz

   * Look the content of sosreport, make sure the information is
  accurate and valid, 

  [Regression Potential]

   * autopkgtest[2] didn't reveal any
  [2] - See Comment #1

   * We have tested the package and found a severe regression that we already 
took action to fix it via :
  Upstream issue - https://github.com/sosreport/sos/issues/1155

  and submitted to Ubuntu Devel release via debdiff : 
  lp1734983_bionic.debdiff

  [Other Info]

   * Sosreport upstream :
     https://github.com/sosreport/sos

   * rmadison -u debian,ubuntu sosreport
  debian:
  sosreport  | 3.2-2| oldstable  | source, amd64, 
arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x
  sosreport  | 3.2-2| oldstable-kfreebsd | source, 
kfreebsd-amd64, kfreebsd-i386
  sosreport  | 3.3+git50-g3c0349b-2 | stable | source, amd64, 
arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
  sosreport  | 3.5-1| testing| source, amd64, 
arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
  sosreport  | 3.5-1| unstable   | source, amd64, 
arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
  ubuntu:
   sosreport | 3.0-1~ubuntu12.04.1  | precise-backports/universe | 
source, amd64, armel, armhf, i386, powerpc
   sosreport | 3.1-1ubuntu2 | trusty | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.1-1ubuntu2.2   | trusty-security| 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.2-2~ubuntu14.04.1  | trusty-backports   | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.2+git276-g7da50d6-3ubuntu1 | xenial | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
   sosreport | 3.3+git50-g3c0349b-2 | zesty  | 
source, amd64, arm64, armhf, i386, ppc64el, s390x
   sosreport | 3.4-1~ubuntu14.04.1  | trusty-updates | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.4-1~ubuntu16.04.1  | xenial-updates | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
   sosreport | 3.4-1~ubuntu17.04.1  | zesty-updates  | 
source, amd64, arm64, armhf, i386, ppc64el, s390x
   sosreport | 3.4-1| artful | 
source, amd64, arm64, armhf, i386, ppc64el, s390x
   sosreport | 3.5-1| bionic

[Group.of.nepali.translators] [Bug 1734983] Re: Request to backport sosreport v3.5

2017-12-04 Thread Eric Desrochers 
** Bug watch added: Debian Bug tracker #883537
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883537

** Also affects: sosreport (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883537
   Importance: Unknown
   Status: Unknown

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

Title:
  Request to backport sosreport v3.5

Status in sosreport:
  New
Status in sosreport package in Ubuntu:
  Fix Released
Status in sosreport source package in Trusty:
  New
Status in sosreport source package in Xenial:
  New
Status in sosreport source package in Zesty:
  New
Status in sosreport source package in Artful:
  New
Status in sosreport source package in Bionic:
  Fix Released
Status in sosreport package in Debian:
  Unknown

Bug description:
  *** DRAFT in progress ***
  [Impact]

  Canonical support team (AKA STS) largely depend on sosreport package
  to troubleshoot system.

  sosreport is always in constant development including new bugfixes,
  new features such as new plugins[1],  that can be interesting to
  have in a support context.

  v3.5 is already found in devel release (bionic). We create this LP in
  the attempt to justify the SRU of v3.5 backport into current supported
  stable releases.

  [1] - New plugins for :
  * perl
  * boom
  * vdo
  * os_net_config
  * conntrackd
  * ovirt_imageio
  * nss
  * sas3ircu
  * openstack_aodh
  * docker_distribution
  * gluster_block
  * snappy

  Plugin API enhancements
  * Plugin triggers by executable name
  * Improved log size limit handling
  * Better handling of compressed log files
  * Per-plugin package verification lists

  Updates to 227 plugins

  [Test Case]

   * Install sosreport
     $ apt-get install sosreport

   * Run sosreport
     $ sosreport -a
     $ sosreport -o 
     $ ...

   * Make sure it generate a tar.xz file in /tmp in the form of
     "/tmp/sosreport--.tar.xz"

   * Extract files from archive
     tar Jxvf /tmp/sosreport--.tar.xz

   * Look the content of sosreport, make sure the information is
  accurate and valid, 

  [Regression Potential]

   * autopkgtest[2] didn't reveal any
  [2] - See Comment #1

   * More to come..

  [Other Info]

   * Sosreport upstream :
     https://github.com/sosreport/sos

   * rmadison -u debian,ubuntu sosreport
  debian:
  sosreport  | 3.2-2| oldstable  | source, amd64, 
arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x
  sosreport  | 3.2-2| oldstable-kfreebsd | source, 
kfreebsd-amd64, kfreebsd-i386
  sosreport  | 3.3+git50-g3c0349b-2 | stable | source, amd64, 
arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
  sosreport  | 3.5-1| testing| source, amd64, 
arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
  sosreport  | 3.5-1| unstable   | source, amd64, 
arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
  ubuntu:
   sosreport | 3.0-1~ubuntu12.04.1  | precise-backports/universe | 
source, amd64, armel, armhf, i386, powerpc
   sosreport | 3.1-1ubuntu2 | trusty | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.1-1ubuntu2.2   | trusty-security| 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.2-2~ubuntu14.04.1  | trusty-backports   | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.2+git276-g7da50d6-3ubuntu1 | xenial | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
   sosreport | 3.3+git50-g3c0349b-2 | zesty  | 
source, amd64, arm64, armhf, i386, ppc64el, s390x
   sosreport | 3.4-1~ubuntu14.04.1  | trusty-updates | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.4-1~ubuntu16.04.1  | xenial-updates | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
   sosreport | 3.4-1~ubuntu17.04.1  | zesty-updates  | 
source, amd64, arm64, armhf, i386, ppc64el, s390x
   sosreport | 3.4-1| artful | 
source, amd64, arm64, armhf, i386, ppc64el, s390x
   sosreport | 3.5-1| bionic | 
source, amd64, arm64, armhf, i386, ppc64el, s390x

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to :

[Group.of.nepali.translators] [Bug 1734983] Re: Request to backport sosreport v3.5

2017-11-28 Thread Eric Desrochers 
** Also affects: sosreport via
   https://github.com/sosreport/sos/issues/1155
   Importance: Unknown
   Status: Unknown

** Description changed:

  *** DRAFT in progress ***
  [Impact]
  
  Canonical support team (AKA STS) largely depend on sosreport package to
  troubleshoot system.
  
  sosreport is always in constant development including new bugfixes, new
  features such as new plugins[1],  that can be interesting to have in
  a support context.
  
  v3.5 is already found in devel release (bionic). We create this LP in
  the attempt to justify the SRU of v3.5 backport into current supported
  stable releases.
  
  [1] - New plugins for :
  * perl
  * boom
  * vdo
  * os_net_config
  * conntrackd
  * ovirt_imageio
  * nss
  * sas3ircu
  * openstack_aodh
  * docker_distribution
  * gluster_block
  * snappy
  
  Plugin API enhancements
  * Plugin triggers by executable name
  * Improved log size limit handling
  * Better handling of compressed log files
  * Per-plugin package verification lists
  
  Updates to 227 plugins
  
  [Test Case]
  
   * Install sosreport
     $ apt-get install sosreport
  
   * Run sosreport
     $ sosreport -a
     $ sosreport -o 
     $ ...
  
   * Make sure it generate a tar.xz file in /tmp in the form of
     "/tmp/sosreport--.tar.xz"
  
   * Extract files from archive
     tar Jxvf /tmp/sosreport--.tar.xz
  
-  * Look the content of sosreport, make sure the information is accurate
+  * Look the content of sosreport, make sure the information is accurate
  and valid, 
  
  [Regression Potential]
  
-  * We don't expect regression, autopkgtest[2] didn't reveal any nor our
- testing.
+  * autopkgtest[2] didn't reveal any
+ [2] - See Comment #1
  
- [2] - See Comment #1
+  * More to come..
  
  [Other Info]
  
   * Sosreport upstream :
     https://github.com/sosreport/sos
  
   * rmadison -u debian,ubuntu sosreport
  debian:
  sosreport  | 3.2-2| oldstable  | source, amd64, 
arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x
  sosreport  | 3.2-2| oldstable-kfreebsd | source, 
kfreebsd-amd64, kfreebsd-i386
  sosreport  | 3.3+git50-g3c0349b-2 | stable | source, amd64, 
arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
  sosreport  | 3.5-1| testing| source, amd64, 
arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
  sosreport  | 3.5-1| unstable   | source, amd64, 
arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
  ubuntu:
   sosreport | 3.0-1~ubuntu12.04.1  | precise-backports/universe | 
source, amd64, armel, armhf, i386, powerpc
   sosreport | 3.1-1ubuntu2 | trusty | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.1-1ubuntu2.2   | trusty-security| 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.2-2~ubuntu14.04.1  | trusty-backports   | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.2+git276-g7da50d6-3ubuntu1 | xenial | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
   sosreport | 3.3+git50-g3c0349b-2 | zesty  | 
source, amd64, arm64, armhf, i386, ppc64el, s390x
   sosreport | 3.4-1~ubuntu14.04.1  | trusty-updates | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.4-1~ubuntu16.04.1  | xenial-updates | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
   sosreport | 3.4-1~ubuntu17.04.1  | zesty-updates  | 
source, amd64, arm64, armhf, i386, ppc64el, s390x
   sosreport | 3.4-1| artful | 
source, amd64, arm64, armhf, i386, ppc64el, s390x
   sosreport | 3.5-1| bionic | 
source, amd64, arm64, armhf, i386, ppc64el, s390x

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

Title:
  Request to backport sosreport v3.5

Status in sosreport:
  Unknown
Status in sosreport package in Ubuntu:
  Fix Released
Status in sosreport source package in Trusty:
  New
Status in sosreport source package in Xenial:
  New
Status in sosreport source package in Zesty:
  New
Status in sosreport source package in Artful:
  New
Status in sosreport source package in Bionic:
  Fix Released

Bug description:
  *** DRAFT in progress ***
  [Impact]

  Canonical support team (AKA STS) largely depend on sosreport package
  to troubleshoot system.

  sosreport is always in constant development including new