byobu

byobu 5.112

  1. Series trunk
  2. 5.112

Milestone information

Project:
byobu
Series:
trunk
Version:
5.112
Released:
 
Registrant:
Dustin Kirkland 
Release registered:
Active:
Yes. Drivers can target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon byobu_5.112.orig.tar.gz (md5, sig) release tarball 1,213
last downloaded 4 days ago
Total downloads: 1,213

Release notes 

This release does not have release notes.

Changelog 

View the full changelog

byobu (5.112-0ubuntu1) yakkety; urgency=medium

  [ Mohamed Elawadi ]
  * usr/bin/byobu.in, usr/bin/byobu-janitor.in, usr/bin/byobu-launch.in,
    usr/bin/byobu-select-profile.in, usr/bin/byobu-status.in,
    usr/lib/byobu/battery, usr/lib/byobu/disk_io,
    usr/lib/byobu/include/common, usr/lib/byobu/include/constants,
    usr/lib/byobu/include/shutil, usr/lib/byobu/ip_address,
    usr/lib/byobu/memory, usr/lib/byobu/release,
    usr/lib/byobu/updates_available:
    - https://github.com/dustinkirkland/byobu/pull/15
    - Fixing BYOBU_TEST issues
    - The first issue was that command -v, which and type were always
      returning an error code when executed without an extra argument.
      so BYOBU_TEST was always falling to which because it was the last one.
    - The second issue was, command -v didn't work because of a different
      reason. When executed in a shell (at least my shell) using variable
      substitution, the shell was trying to find a binary called
      "command -v" so it was failing.

 -- Dustin Kirkland <email address hidden> Fri, 16 Sep 2016 10:13:05 -0500

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.