byobu 2.4 "2.4"
Milestone information
- Project:
- byobu
- Series:
- trunk
- Version:
- 2.4
- Code name:
- 2.4
- Released:
- Registrant:
- Dustin Kirkland
- Release registered:
- Active:
- No. Drivers cannot target bugs and blueprints to this milestone.
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
Release notes
[ Dustin Kirkland ]
* byobu: support Debian/Ubuntu's diversion of screen to screen.real,
as well as RH, which does not divert the real screen binary
* debian/release.sh: handle version incrementing in the rpm specfile
* bin/disk-used: fix situations where df output wraps to the next
line
* bin/logo: check that lsb_release is available before using it
* bin/release: try to grab both distro and version from /etc/issue
if that's what we're forced to use
* bin/updates-
* bin/ip-
colors look bad on the light* profiles
* bin/ip-address: hostname -i doesn't always work, use ifconfig
instead, LP: #376080
* bin/network-
for status cache files, to keep from waking up the disk
* bin/battery: color the entire battery the same way, only use 3 tones,
Green/
capital G/Y/R background
* byobu-export: tar files with owner/group as root/root, LP: #371025
* byobu, debian/install, motd+shell, profiles/byoburc: launch screen
with a simple config file that includes the chosen profile plus
the chosen windows; but on refresh, only reload the chosen profile;
revert previous hack that did this by creating a temporary config
file and broke on hardy, LP: #375309
* screen-launcher: don't use the -x argument if launching a new screen,
as this fails to launch default windows, LP: #375768
* debian/control: suggest vim, for better handling of status details
[ David Duffey ]
* rpm/byobu.spec: initial specfile for RH packaging
Changelog
This release does not have a changelog.
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.