[Bug 966511] [NEW] Please backport mosh 1.1-1 (universe) from precise

Launchpad Bug Tracker 966511 at bugs.launchpad.net
Tue Mar 27 19:34:04 UTC 2012


You have been subscribed to a public bug by Evan Broder (broder):

Please backport mosh 1.1-1 (universe) from precise to lucid, maverick,
natty, oneiric.

Reason for the backport:
========================
mosh is a new remote shell application that uses automatic
reconnection and predictive echo to deliver a better experience to
mobile clients on potentially laggy connections.

It's a new package and has no reverse-dependencies.

Lucid needs dh-autoreconf from backports (not a problem since it's
pre-NotAutomatic)

Testing:
========
Mark off items in the checklist [X] as you test them, but please leave the checklist so that backporters can quickly evaluate the state of testing.

You can test-build the backport in your PPA with backportpackage:
$ backportpackage -u ppa:<lp username>/<ppa name> -s precise -d lucid mosh
$ backportpackage -u ppa:<lp username>/<ppa name> -s precise -d maverick mosh
$ backportpackage -u ppa:<lp username>/<ppa name> -s precise -d natty mosh
$ backportpackage -u ppa:<lp username>/<ppa name> -s precise -d oneiric mosh

* lucid:
[X] Package builds without modification
[X] mosh installs cleanly and runs
* maverick:
[X] Package builds without modification
[X] mosh installs cleanly and runs
* natty:
[X] Package builds without modification
[X] mosh installs cleanly and runs
* oneiric:
[X] Package builds without modification
[X] mosh installs cleanly and runs

No reverse dependencies

** Affects: lucid-backports
     Importance: Wishlist
         Status: In Progress

** Affects: maverick-backports
     Importance: Wishlist
         Status: In Progress

** Affects: natty-backports
     Importance: Wishlist
         Status: In Progress

** Affects: oneiric-backports
     Importance: Wishlist
         Status: In Progress

-- 
Please backport mosh 1.1-1 (universe) from precise
https://bugs.launchpad.net/bugs/966511
You received this bug notification because you are a member of Ubuntu Package Archive Administrators, which is subscribed to the bug report.



More information about the ubuntu-archive mailing list