/etc/cron.daily/sysstat: xargs: xz: No such file or directory

Bug #1578160 reported by Johan Wassberg
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
sysstat (Debian)
Fix Released
Unknown
sysstat (Ubuntu)
Fix Released
High
Unassigned
Xenial
Fix Released
High
Unassigned

Bug Description

Sysstat has changed the default compression from bzip2 to xz but the packages is lack of depend of the xz-utils.
This causes the daily cronjob to fail with:

/etc/cron.daily/sysstat:
xargs: xz: No such file or directory

This has been fixed in the Debian package by depending on the correct compression package.
https://anonscm.debian.org/cgit/users/robert/sysstat.git/commit/?id=a3cb350b63d3fd819d86e1f865589e5b2b73d393

Attaching a patch which will do the same for Ubuntu.

# lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04

# apt-cache policy sysstat
sysstat:
  Installed: 11.2.0-1
  Candidate: 11.2.0-1
  Version table:
 *** 11.2.0-1 500
        500 http://linux-sua.it.su.se/xenial/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status

[Test Case]
* Install the sysstat package
* Enable that sadc collect system activity informations.
* Wait until /etc/cron.daily/sysstat has run.
* Expect mail to you root account with "xargs: xz: No such file or directory"

[Regression Potential]
I don't think there is any risks with this fix.
Since bzip2 is more widely used then xz I think bzip2 still will installed on the machine. So if someone have changed the default compression from xz to bzip2 the daily job still should succeed.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in sysstat (Ubuntu):
status: New → Confirmed
Mathew Hodson (mhodson)
tags: added: xenial
Changed in sysstat (Ubuntu):
importance: Undecided → Low
tags: added: packaging
Changed in sysstat (Ubuntu):
status: Confirmed → Triaged
Changed in sysstat (Debian):
status: Unknown → Fix Released
Revision history for this message
Robie Basak (racb) wrote :

It sounds like this breaks the package in its default configuration, so I think High is more appropriate.

Changed in sysstat (Ubuntu):
importance: Low → High
Revision history for this message
Robie Basak (racb) wrote :

Since this was fixed in Debian in 11.3.2-1 and Yakkety has 11.3.3-1, marking Fix Released to reflect Yakkety and adding a task for Xenial.

TheSeal, thank you for providing this patch and subscribing ~ubuntu-sponsors. The patch itself looks good but we need a little more paperwork for updates to stable releases to reduce regression risk to users. Please see https://wiki.ubuntu.com/StableReleaseUpdates#Procedure. In particular, the patch should target xenial, should refer to this bug so that it auto-closes, and the SRU paperwork needs to be added to this bug.

Are you interested in fixing this up? If not, I'd like to pass this bug to someone else as it's a good candidate to help prospective developers become familiar with the SRU process.

Changed in sysstat (Ubuntu Xenial):
importance: Undecided → High
status: New → Triaged
Changed in sysstat (Ubuntu):
status: Triaged → Fix Released
tags: added: bitesize
Revision history for this message
Robie Basak (racb) wrote :

Note: I'd also prefer the version to follow the scheme at https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging as linked to from the SRU procedure.

Johan Wassberg (theseal)
description: updated
Revision history for this message
Johan Wassberg (theseal) wrote :
Revision history for this message
Johan Wassberg (theseal) wrote :

I think I have done what you asked for by updating the description(with SRU) and replacing the patch with a new one.

Anything else that needs to be done by me? :)

Revision history for this message
Robie Basak (racb) wrote :

You've updated everything correctly as far as I can see, thanks.

One final question. In the Regression Potential section, it looks like you have considered what might happen if a user relies on the fact that the package previously pulled in bzip2. In this case, would it be better to fix this just by adding the xz-utils dependency, instead of replacing the previous bzip2 one? For an SRU, we prefer a minimal fix to minimise regression potential over a "correct, refactored" type fix which we'd put in the development release.

What's your opinion on adding only the xz-utils dependency instead of replacing the previous bzip2 one?

Revision history for this message
Johan Wassberg (theseal) wrote :

I thought about just add the xz-utils as a dependency instead of replacing bzip2. But choose to do it the way the Debian maintainer did.
But yes, its possible to change the configuration for the compression method to something that isn't installed. Recommended and default from upstream is still xz.

Revision history for this message
Robie Basak (racb) wrote :

OK, I've uploaded this as-is and will leave it for the SRU team to decide. Now awaiting SRU team review. Thanks!

Changed in sysstat (Ubuntu Xenial):
status: Triaged → In Progress
Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Hello TheSeal, or anyone else affected,

Accepted sysstat into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sysstat/11.2.0-1ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in sysstat (Ubuntu Xenial):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

theseal, mind testing the update?

Revision history for this message
Johan Wassberg (theseal) wrote :

Sorry, I must have missed some notification about this issue.

I have tested and can confirm that the package in Proposed work as it
should and installs xz-utils when installing sysstat.

Noteworthy is that the package is "Helt back" since it has changes to
the dependencies if you try to upgrade your already installed version.

Revision history for this message
Robie Basak (racb) wrote :

Thank you for testing!

> Noteworthy is that the package is "Helt back" since it has changes to
the dependencies if you try to upgrade your already installed version.

Thank you for noting. As this is expected, I think we're OK. I'm not sure from your comment if you already know this, but for others, "sudo apt-get dist-upgrade" will tell apt to resolve the situation and pull in any new packages as required.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package sysstat - 11.2.0-1ubuntu0.1

---------------
sysstat (11.2.0-1ubuntu0.1) xenial; urgency=medium

  * Add missing depend, bzip2 is replaced by xz-utils. (LP: #1578160)

 -- Johan Carlquist <email address hidden> Wed, 04 May 2016 12:40:47 +0200

Changed in sysstat (Ubuntu Xenial):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of the Stable Release Update for sysstat has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.