For full changelog reference:
This bug was fixed in the package sosreport - 4.3-1ubuntu2
---
sosreport (4.3-1ubuntu2) jammy; urgency=medium
* d/p/0003-mention-sos-help-in-sos-manpage.patch:
Fix sos-help manpage.
-- Eric Desrochers Wed, 16 Feb 2022 13:05:13 -0500
** Description changed:
[IMPACT]
The sos team is pleased to announce the release of sos-4.3. This release
includes a number of quality-of-life changes to both end user experience
and for contributors dealing with the plugin API.
[TEST PLAN]
Documentation for Special Cases:
https://launchpad.net/ubuntu/+source/sosreport/4.3-1ubuntu2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960996
Title:
[sru] sos upstream 4.3
To manage notifications about this bug go to:
Just notice man page doesn't include sos help.
I'll push another update (4.3-1ubuntu2) in Jammy.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960996
Title:
[sru] sos upstream 4.3
To
** Changed in: sosreport (Ubuntu Impish)
Assignee: (unassigned) => nikhil kshirsagar (nkshirsagar)
** Changed in: sosreport (Ubuntu Focal)
Assignee: (unassigned) => nikhil kshirsagar (nkshirsagar)
** Changed in: sosreport (Ubuntu Bionic)
Assignee: (unassigned) => nikhil kshirsagar
Uploaded in Jammy with a quilt patch to fix setup.py (see comment #1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960996
Title:
[sru] sos upstream 4.3
To manage notifications about this bug go
Found one bug that I have reported upstream with regard to sos.help module
https://github.com/sosreport/sos/issues/2860
** Bug watch added: github.com/sosreport/sos/issues #2860
https://github.com/sosreport/sos/issues/2860
--
You received this bug notification because you are a member of
** Changed in: sosreport (Ubuntu Jammy)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: sosreport (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: sosreport (Ubuntu Jammy)
Status: New => In Progress
** Tags added: seg sts
--
You received
[sts-sponsor]
After a discussion with ddstreet about nobody being able (as it requires
specific HW) nor reply to our request to test the proposed packages for
this particular bug.
Since the packages of freeipmi are languishing in proposed for about 176
days (as of today) with no
[sts-sponsor]
After a discussion with ddstreet about nobody being able (as it requires
specific HW) nor reply to our request to test the proposed packages for
this particular bug.
Since the packages of freeipmi are languishing in proposed for about 176
(as of today) with no
Is there any reproducer that could exercise the code path you have
modified ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900617
Title:
gateway error detail is not passed along in raised
Is there any reproducer that could exercise the code you have modified ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900617
Title:
gateway error detail is not passed along in raised exception
Not having a good test for the binary package would be a blocker here
for the release of the package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900617
Title:
gateway error detail is not passed
Can you build a reproducer out of the unit tests for this bug while
using the binary package ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900617
Title:
gateway error detail is not passed along
> I will attempt to upstream this fix to klibc, but I believe the change
to Bionic should happen in parallel/independently since the upstream
patch will not make its way back to Bionic (which is stuck at 2.0.4, as
mentioned above).
Yes that is the plan to SRU the fix on top of what is currently
And let them judge if it's worth an upstream adoption or not as a first
exercise. Then we can take a decision for Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does
And let them judge if it's worth the adoption or not as a first
exercise. Then we can take a decision for Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does not
I still believe, it would be a good practice to submit the patch to
upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does not honour user-requested timeouts in some
Khaled El Mously (kmously),
Thanks for the update. I'll review this and talk with sil2100, an SRU
verification member.
Could you please help to fill the SRU template in the description above.
Extra documentations can be found here:
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
Thanks, Heather.
Don't forget to do the verification for the other bug as well (LP:
#1900617)
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820083
Title:
TLS params not set for session
Is there a way you can verify the actual binary package ? Instead of
testing it by pulling the source code ?
Verification need to be done on the binary package, this is what we will
promote in -updates.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
[IMPACT]
The sos team is pleased to announce the release of sos-4.2. This release
contains numerous improvements and bug fixes to several components
within sos, including an overhaul to the project's test suite and
infrastructure.
[TEST PLAN]
Let's focus our time testing Focal/20.04LTS, which can cover various areas:
Openstack, Ceph, k8s, MAAS, juju, Landscape, ... (to only name those)
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[VERIFICATION HIRSUTE/IMPISH]
Since theses 2 releases are non-LTS. They are less exposed to various
context & environment types such as: Openstack, Ceph, k8s, JuJu, MAAS,
Landscape, ...
It's safe to say that non-LTS should be limited to general sosreport
run, most likely in the Desktop area.
[sts-sponsors]
The upload mentioned in comment #38 has been rejected as per my request.
Re-uploaded in Focal and Bionic upload queues, including both (LP:
#1820083) & (LP: #1900617)
It is now waiting for the SRU verification team to approve the src
package to start building and become available
** Description changed:
[impact]
when the gateway reports an error, it is not passed along in the
exception raised by python-etcd3gw
[test case]
Upstream added unit tests for this bug, which are included in the
backport, so a successful package build (which runs the unit
[sts-sponsors]
Uploaded in Focal and Bionic upload queues.
It is now waiting for the SRU verification team to approve the src
package to start building and become available in the -proposed pockets
for the testing/verification phase.
Thanks for your contribution, Heather.
- Eric & Dariusz
--
In theory, python3-mock should be installed by the fact that
python3-oslotest as a runtime dependency for it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900617
Title:
gateway error detail is
After more analysis it should be fine:
18 Build-Depends-Indep:
19 python-coverage,
20 python-futurist,
21 python-hacking,
22 python-nose,
23 python-oslosphinx,
24 python-oslotest,
25 python-pytest,
26 python-requests,
27 python-six,
[sts-sponsors]
* The patch '0002-lp1900617-When-gateway-sends-failure-response-include-
text-in-.patch'[0] introduce a 'import mock', but python-mock nor
python3-mock is part of the build-Depends: in d/control.
Which make me doubt that this part of the code wasn't probably tested ?
Or is it
** Changed in: sosreport (Ubuntu Focal)
Status: Confirmed => Triaged
** Changed in: sosreport (Ubuntu Focal)
Status: Triaged => In Progress
** Changed in: sosreport (Ubuntu Focal)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: sosreport (Ubu
** Changed in: sosreport (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: sosreport (Ubuntu)
Status: Won't Fix => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901786
This has been tested on Cisco Hardware by Field Engineering and the bug
is no longer reproducible.
- Eric
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
+ ** SRU TEMPLATE DRAFT **
+
+ [Impact]
+
+
+ [Test Plan]
+
+
+ [Where problems could occur]
+
+
+ [Other Info]
+
+
+ [Original Description]
+
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c,
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does not honour user-requested timeouts in some cases
To manage notifications about this bug go to:
@Khaled El Mously (kmously)
I don't see this piece of code in the klibc upstream project[0]
Is this something you only reproduce in Bionic/18.04LTS ?
Since your fix is not found anywhere else, I would be tempted to assume that it
could be affecting other releases of Ubuntu and possibly more.
[VERIFICATION]
The ansible (and the fixed packages listed in the bugs) installation has
been tested by impacted users and the outcomes were as expected.
- Eric
** Tags removed: verification-needed-bionic verification-needed-focal
** Tags added: verification-done-bionic verification-done-focal
[sts-sponsors]
Uploaded in Focal and Bionic upload queues.
It is now waiting for the SRU verification team to approve the src package to
start building and become available in the -proposed pockets for the
testing/verification phase.
Thanks for your contribution Heather.
- Eric
--
You
I see that dims is the maintainer[0], so the github repo should be fine
and be considered as a trusted source.
We can leave it as is.
[0] - https://pypi.org/project/etcd3gw/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I see that dims is the maintainer[0], so the github repo should be fine.
We can leave it as is.
[0] - https://pypi.org/project/etcd3gw/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820083
Title:
Because:
1) We want to make sure we give credit to the author by making sure his/her
name is readable.
2) The Bug-Ubuntu URL you originally added redirected to a 404 ERROR.
3) The dims' github repo last update was back in 2020, so it seems like a
mirror or no-longer maintained source location.
5) The patch rename is to continue the logic in the patch convention
name already existing in the src code.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820083
Title:
TLS params not set for
[sts-sponsors]
It is looking definitely better.
Here's some nitpicking:
# For both Focal and Bionic:
- From: =?UTF-8?q?Tade=C3=A1=C5=A1=20Urs=C3=ADny?=
+ from: Tadeas Ursíny
- Origin: upstream,
https://github.com/dims/etcd3-gateway/commit/90b7a19cdc4daa1230d7f15c10b113abdefdc8c0
+ Origin:
@ioanna,
Does it maintain compatibility for release that could have both <= and
>= 5.10 available ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921403
Title:
makedumpfile does not create dmesg
The regressions observed in azure-cli for Focal/20.04LTS have nothing to
do with this particular SRU change.
I have reported a separate bug for this:
https://bugs.launchpad.net/ubuntu/+source/azure-cli/+bug/1948595
One unit test is failing as it misses an argument (--subscription) in "az cloud
** Summary changed:
- buildlog failure
+ buildlog failure "az: error: unrecognized arguments: --subscription"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948595
Title:
buildlog failure "az:
Public bug reported:
#Version:
2.0.81+ds-4ubuntu0.2
#Buildlog:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/a/azure-cli/20211020_155434_06453@/log.gz
#Failure:
tests_core/test_cloud.py::SubscriptionSuppressionTest::test_subscription_suppression
FAILED [ 30%]
.
** Changed in: sosreport (Ubuntu Focal)
Status: New => Confirmed
** Changed in: sosreport (Ubuntu Bionic)
Status: New => Incomplete
** Changed in: sosreport (Ubuntu Bionic)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of
irsute)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Description changed:
[IMPACT]
The sos team is pleased to announce the release of sos-4.2. This release
contains numerous improvements and bug fixes to several components
within sos, including an overhaul to the project's t
** Changed in: sosreport (Ubuntu Impish)
Status: New => In Progress
** Changed in: sosreport (Ubuntu Impish)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: sosreport (Ubuntu Impish)
Importance: Undecided => Medium
--
You received this bug notificatio
** Changed in: python-netaddr (Ubuntu Bionic)
Assignee: Eric Desrochers (slashd) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877792
Title:
jmespath/netaddr SyntaxWarn
To answer #10 from Lukasz.
python-netaddr so as python-jmespath (both ansible runtime dependencies)
spew syntaxwarning at ansible installation time (or their respective
package).
It is purely cosmetic, but we hope fixing these bug will make user gain
confidence in the Ansible package found in
To answer #10 from Lukasz.
python-netaddr so as python-jmespath (both ansible runtime dependencies)
spew syntaxwarning at ansible installation time (or their respective
package).
It is purely cosmetic, but we hope fixing these bug will make user gain
confidence in the ansible package found in
** Description changed:
[IMPACT]
* Allow broader Ops/Eng team to consume Ansible from our packages
instead of the upstream PyPi repositories in order to fix this warning.
* Sanitize package installation:
Setting up python3-jmespath (0.9.4-2) ...
*** This bug is a duplicate of bug 1877792 ***
https://bugs.launchpad.net/bugs/1877792
** This bug is no longer a duplicate of bug 1917318
code confuses identity and equality (fixed upstream)
** This bug has been marked a duplicate of bug 1877792
jmespath/netaddr SyntaxWarning: "is"
*** This bug is a duplicate of bug 1877792 ***
https://bugs.launchpad.net/bugs/1877792
** This bug is no longer a duplicate of bug 1917318
code confuses identity and equality (fixed upstream)
** This bug has been marked a duplicate of bug 1877792
jmespath/netaddr SyntaxWarning: "is"
*** This bug is a duplicate of bug 1877792 ***
https://bugs.launchpad.net/bugs/1877792
** This bug is no longer a duplicate of bug 1917318
code confuses identity and equality (fixed upstream)
** This bug has been marked a duplicate of bug 1877792
jmespath/netaddr SyntaxWarning: "is"
*** This bug is a duplicate of bug 1877792 ***
https://bugs.launchpad.net/bugs/1877792
** This bug is no longer a duplicate of bug 1917318
code confuses identity and equality (fixed upstream)
** This bug has been marked a duplicate of bug 1877792
jmespath/netaddr SyntaxWarning: "is"
*** This bug is a duplicate of bug 1877792 ***
https://bugs.launchpad.net/bugs/1877792
** This bug has been marked a duplicate of bug 1877792
jmespath/netaddr SyntaxWarning: "is" with a literal when installing ansible.
--
You received this bug notification because you are a member of
** Also affects: python-netaddr (Ubuntu)
Importance: Undecided
Status: New
** Changed in: python-netaddr (Ubuntu Focal)
Status: New => In Progress
** Changed in: python-netaddr (Ubuntu Focal)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: python-n
I have just re-test in a focal lxd container, the installation worked.
ii python3-jmespath 0.9.4-2
all JSON Matching Expressions (Python 3)
but could mislead the user that it wasn't successfully installed:
Setting up python3-jmespath (0.9.4-2) ...
One of the impact is:
https://github.com/jmespath/jmespath.py/issues/201
** Bug watch added: github.com/jmespath/jmespath.py/issues #201
https://github.com/jmespath/jmespath.py/issues/201
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Summary changed:
- [FFe][sync][sru] sos upstream 4.2
+ [sru] sos upstream 4.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941745
Title:
[sru] sos upstream 4.2
To manage notifications about
** Also affects: sosreport (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: sosreport (Ubuntu Jammy)
Status: New => In Progress
** Changed in: sosreport (Ubuntu Jammy)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: sosreport (Ubuntu
[sts-sponsor]
The debdiff add a new build-depends for python-openssl[0].
It seems like you made a patch of yours[1] (UBUNTU SAUCE ?? I can't find in the
upstream project[2]) since your patch requires crypto in OpenSSL module[3].
Could you elaborate and provide rationale for this patch ? And
[sts-sponsor]
The debdiff add a new build-depends for 'python-openssl'
It seems like you made a patch of yours[0] that I can't find in the
upstream project[1], since you patch requires crypto in OpenSSL module.
Could you elaborate and provide rationale for this patc ? and why this is
needed
Focal debdiff
** Patch added: "Focal debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-jmespath/+bug/1877792/+attachment/5531626/+files/f.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Bionic debdiff
** Patch added: "Bionic debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-jmespath/+bug/1877792/+attachment/5531623/+files/b.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: python-jmespath (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: python-jmespath (Ubuntu Focal)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: python-jmespath (Ubuntu Bionic)
Status: Confirmed => In Progress
*
** Description changed:
[IMPACT]
* Allow broader Ops/Eng team to consume Ansible from our packages
instead of the upstream PyPi repositories in order to fix this warning.
* Sanitize package installation:
Setting up python3-jmespath (0.9.4-2) ...
** Description changed:
[IMPACT]
* Allow broader Ops/Eng team to consume Ansible from our packages
instead of the upstream PyPi repositories in order to fix this warning.
* Sanitize package installation:
Setting up python3-jmespath (0.9.4-2) ...
** Description changed:
[IMPACT]
* Allow broader Ops/Eng team to consume Ansible from our packages
instead of the upstream PyPi repositories in order to fix this warning.
* Sanitize package installation:
Setting up python3-jmespath (0.9.4-2) ...
** Description changed:
[IMPACT]
* Allow broader Ops/Eng team to consume Ansible from our packages
instead of the upstream PyPi repositories in order to fix this warning.
* Sanitize package installation:
Setting up python3-jmespath (0.9.4-2) ...
** Description changed:
+ [IMPACT]
+
+ [TEST CASE]
+
+ ** Scenario #1 **
+ This could be reproduced outside python-jmespath as follows (a little script
I have written to compare result between py2 and py3 :
+
+ # reproducer_test.py
+
+ def reproducer(x,y):
+ if x is 0 or x is 1:
+
** Also affects: ansible (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: python-jmespath (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: ansible (Ubuntu Impish)
Importance: Undecided
Status: Invalid
** Also affects:
** Description changed:
[IMPACT]
The sos team is pleased to announce the release of sos-4.2. This release
contains numerous improvements and bug fixes to several components
within sos, including an overhaul to the project's test suite and
infrastructure.
[TEST PLAN]
x (Ubuntu)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: linux (Ubuntu Focal)
Importance: Undecided =>
** Summary changed:
- kernel bug found when disconnecting one fiber channel interface on Cisco
Chassis with fnic DRV_VERSION " 1.6.0.47"
+ kernel bug found when disconnecting one fiber channel interface on Cisco
Chassis with fnic DRV_VERSION "1.6.0.47"
--
You received this bug notification
Public bug reported:
[Impact]
It has been brought to my attention the following:
"
We have been experiencing node lockups and degradation when testing fiber
channel fail over for multi-path PURESTORAGE drives.
Testing usually consists of either failing over the fabric or the local
I/O module
[Potential fix candidate]
commit 712582e60f288e7cede8d6fc8769529317e0f3e0
Author: Hannes Reinecke
Date: Fri May 15 13:26:47 2020 +0200
scsi: fnic: Do not call 'scsi_done()' for unhandled commands
The fnic drivers assigns an ioreq structure to each command and severs this
assignment once
** Bug watch added: Debian Bug tracker #994564
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994564
** Also affects: sosreport (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994564
Importance: Unknown
Status: Unknown
** Description changed:
[IMPACT]
[Verification Focal]
This has been brought to my attention by an impacted user:
"
I was able to apply the fixed procps package from the focal-proposed repo on
servers in a test cluster. The fix resolved the issue with free -V and the
related DataStax OpsCenter error.
Thanks
"
- Eric
** Tags
[autopkg regression]
All tests are now fine. They needed a second retry.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917148
Title:
ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
To
I'll probably drop 'avocado-framework' testing for now and keep the
nosetest.
override_dh_auto_test:
nosetests3 -v --with-cover --cover-package=sos tests/unittests
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(Ubuntu Impish)
Assignee: Eric Desrochers (slashd) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941745
Title:
[FFe][sync][sru] sos upstream 4.2
To manage notifications ab
I totally get your concern. In the same time, other procps pkkg in
Ubuntu groovy, ... uses the same approach.
But I leave you to decide what is best for this particular bug.
Let us know.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Tags removed: sts-sponsors-slashd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917148
Title:
ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
To manage notifications about this bug go to:
[sts-sponsors]
Sponsored in Focal upload queue, now waiting for SRU verification team
approval.
Thanks for your contribution, Kellen.
Test case validation (before upload):
root@procpsf:/tmp# pgrep --version
pgrep from procps-ng 3.3.16
root@procpsf:/tmp# ps --version
ps from procps-ng
** Description changed:
[Impact]
* Breakage of tools expecting the version number or the number to
substantially match the Debian package version.
* May confuse users expecting the version to substantially match the Debian
package version.
* Restores behavior to that provided in
[sts-sponsors]
Debian uses autopkgtest for 'version' w/ restriction superficial as
follows:
Tests: version
Restrictions: superficial
https://people.debian.org/~eriberto/README.package-tests.html
superficial
The test does not provide significant test coverage, so if it passes, that does
not
** Tags added: sts-sponsors-slashd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917148
Title:
ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
To manage notifications about this bug go to:
** Tags added: seg sts
** Also affects: procps (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: procps (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: procps (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects:
I'll be reviewing the change with my colleague Kellen.
In the meanwhile ...
What is the concern/impact behind not having the version available in ps ?
(Outside it should output/report it) ?
The version can be found in the package version (dpkg -l procps)
Is it for integrity purposes in order
t be
able to introduce a new package in stable release like I can do in devel.
Stay tuned !!
** Changed in: sosreport (Ubuntu Impish)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Other possible option is to revert the avocado change that has been made
between 4.1 and 4.2 and continue the former way by reverting the
necessary commits
Example:
e325f38e [tests] use Avocado "recursive" behavior by default
f568fb21 [tests] Start using avocado for test suite
--
You
Other option is to revert the avocado change that has been made between
4.1 and 4.2 and continue the former way by reverting the following
"UBUNTU SAUCE:" style.
e325f38e [tests] use Avocado "recursive" behavior by default
05787e50 [cirrus] Update avocado commands with new test directories
While I figure out the 'avocado' portion on the test build.
I have a package ready, produces by skipping the tests at build time
that can be found here:
sudo add-apt-repository ppa:slashd/sos42test
sudo apt-get update
--
You received this bug notification because you are a member of Ubuntu
# Note
Currently facing a problem with dh_auto_test: while running test w/
avocado-framework.
Avocado is not packaged in Ubuntu/Debian, and requires to be installed
via 'pip3 install avocado-framework' which doesn't seem to be accepted
by the builder.
Tried severals scenarios such as:
#
Public bug reported:
[IMPACT]
The sos team is pleased to announce the release of sos-4.2. This release
contains numerous improvements and bug fixes to several components
within sos, including an overhaul to the project's test suite and
infrastructure.
[TEST PLAN]
Documentation for Special
systemd reaches day 7 wo/ autopkgtest failure nor negative
outcome/feedbacks.
I have asked 'sil2100' to promote the package into bionic-updates.
Stay tuned ...
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 3441 matches
Mail list logo
