** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705538
Title:
Update Package request for libservicelog
To manage
This bug was fixed in the package libservicelog - 1.1.16-0ubuntu1.1
---
libservicelog (1.1.16-0ubuntu1.1) xenial; urgency=medium
* debian/patches: Cherry-pick and rebase upstream fixes for additional NULL
checking, string length calculation and validation. (LP: #1705538)
-
--- Comment From hegdevas...@in.ibm.com 2018-06-15 10:50 EDT---
(In reply to comment #42)
> (In reply to comment #41)
> > Thank you!
> >
> > Vasant, new version of libservicelog is now available in xenial-proposed -
> > could you proceed with testing and forward us the results? Testing +
Thank you!
Vasant, new version of libservicelog is now available in xenial-proposed
- could you proceed with testing and forward us the results? Testing +
running the test-suite manually.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: ubuntu-power-systems
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705538
Title:
Update Package request for libservicelog
To manage
Hello bugproxy, or anyone else affected,
Accepted libservicelog into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/libservicelog/1.1.16-0ubuntu1.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new
Running the test suite manually seems to me that it should be sufficient
here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705538
Title:
Update Package request for libservicelog
To manage
I have updated the description to include some of the information that
has been shared through the comments. One thing I wanted to know: is
running the test-suite manually work correctly right now? Is it possible
to do that and get valid test results?
Also Vasant, you mentioned that you have a
** Description changed:
[Impact]
Update Package request for libservicelog. Some upstream patches have
- been requested to be included in both bionic and xenial.
+ been requested to be included in both bionic and xenial. The addressed
+ issues can potentially affect customer environments,
> Patches mentioned in this bugzilla can potentially impact customer
environment.
How? Ubuntu's SRU procedure requires this to be documented to make sure
that the SRU is justified.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: ubuntu-power-systems
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705538
Title:
Update Package request for libservicelog
To manage
** Changed in: libservicelog (Ubuntu Xenial)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705538
Title:
Update Package request for libservicelog
To manage
We're waiting on a response to Steve's question in comment #20.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705538
Title:
Update Package request for libservicelog
To manage notifications about
> [Impact]
> Update Package request for libservicelog. Some upstream patches have
been requested to be included in both bionic and xenial.
This is not a user impact explanation as described at
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure and I can't find
any other justification or need
** Tags removed: triage-a
** Tags added: triage-g
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705538
Title:
Update Package request for libservicelog
To manage notifications about this bug go
> Also we have unit test cases in libservicelog package .. which is enough to
> cover basic
> validation.
If I'm not mistaken, we still have this testsuite disabled in the
package because while I sent some fixes, servicelog_open() still fails
if /var/lib/servicelog does not exist. Does this
This work is currently blocked waiting on a test case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705538
Title:
Update Package request for libservicelog
To manage notifications about this bug
** Changed in: ubuntu-power-systems
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705538
Title:
Update Package request for libservicelog
To manage
Uploaded to the xenial UNAPPROVED queue, waiting for SRU team review.
** Description changed:
+ [Impact]
+
+ Update Package request for libservicelog. Some upstream patches have
+ been requested to be included in both bionic and xenial.
+
+ [Test Case]
+
+ The packages will be validated by
As per Steve's comment - could someone provide a more detailed test case
for the uploaded changes? e.g. how to reproduce the original issues in
steps that could be executed by a potential tester.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This SRU says that the updated package will be "validated by the
requesting party". How will IBM validate it? If IBM have a test plan
for how we will make sure this update is correct, we should be able to
run that test plan ourselves. If IBM do not have such a test plan, I am
concerned that
** Changed in: libservicelog (Ubuntu Xenial)
Assignee: Canonical Foundations Team (canonical-foundations) => Łukasz
Zemczak (sil2100)
** Changed in: libservicelog (Ubuntu Xenial)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
** Tags removed: triage-g
** Tags added: triage-a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705538
Title:
Update Package request for libservicelog
To manage notifications about this bug go
** Tags removed: triage-r
** Tags added: triage-g
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705538
Title:
Update Package request for libservicelog
To manage notifications about this bug go
** Changed in: libservicelog (Ubuntu Xenial)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705538
Title:
Update Package request for libservicelog
To manage
** Changed in: libservicelog (Ubuntu Xenial)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705538
Title:
Update Package request for libservicelog
To manage
** Tags removed: triage-a
** Tags added: triage-r
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705538
Title:
Update Package request for libservicelog
To manage notifications about this bug go
** Tags removed: triage-g
** Tags added: triage-a
** Changed in: ubuntu-power-systems
Status: New => Incomplete
** Changed in: ubuntu-power-systems
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This package is out of date in debian w.r.t. upstream. Is Frederic
Bonnard going to upgrade the package to 1.1.18?
Do you still require NULL check / NULL dereference patches SRUed into
xenial?
** Changed in: libservicelog (Ubuntu Xenial)
Status: New => Incomplete
--
You received this
** Tags removed: triage-a
** Tags added: triage-g
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705538
Title:
Update Package request for libservicelog
To manage notifications about this bug go
** Tags added: id-59a4c1e54b49b47985c45376
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705538
Title:
Update Package request for libservicelog
To manage notifications about this bug go to:
No. The SRU guidelines are not different for universe packages vs. main.
For xenial, the plan here would still be to cherry-pick the patches.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705538
Steve, Since this package is in universe for Xenial, would it be
possible to sync this packages with debian for 16.04.4 once the patches
have been picked up in Debian?
** Tags removed: triage-r
** Tags added: triage-a
--
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package libservicelog - 1.1.18-0ubuntu2
---
libservicelog (1.1.18-0ubuntu2) artful; urgency=medium
* Disable the test suite, which doesn't actually test the built library
but a previously-installed library (which we don't have on the buildds).
--
** Patch added: "Fix segfault on servicelog_open() failure"
https://bugs.launchpad.net/ubuntu/+source/libservicelog/+bug/1705538/+attachment/4940509/+files/0002-Fix-segfault-on-servicelog_open-failure.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
For 17.10, I've attempted to upload the 1.1.18 upstream version rather
than cherry-picking individual fixes. However, the package fails to
build on the Ubuntu builders due to a series of bugs.
- when the test binary is built, it is linked against libservicelog.so, not
libservicelog.la. This
** Also affects: libservicelog (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: libservicelog (Ubuntu)
Assignee: Canonical Foundations Team (canonical-foundations) => Steve
Langasek (vorlon)
** Changed in: libservicelog (Ubuntu)
Status: New => Fix Committed
** Changed in: libservicelog (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Canonical Foundations Team (canonical-foundations)
** Changed in: libservicelog (Ubuntu)
Importance: Undecided => High
** Tags removed: triage-g
** Tags added: triage-r
--
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
** Tags added: triage-g
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705538
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705538
Title:
Update Package request for libservicelog
To manage notifications about this bug go to:
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
41 matches
Mail list logo
