| 2014-01-28 22:11:05 |
Gary Poster |
bug |
|
|
added bug |
| 2014-01-29 00:21:59 |
Ubuntu Foundations Team Bug Bot |
tags |
|
needs-packaging |
|
| 2014-01-29 23:55:04 |
Brian Murray |
ubuntu: importance |
Undecided |
Wishlist |
|
| 2014-02-14 17:44:40 |
James Page |
summary |
[needs-packaging] juju-quickstart |
[MIR] juju-quickstart |
|
| 2014-02-14 17:44:50 |
James Page |
affects |
ubuntu |
juju-quickstart (Ubuntu) |
|
| 2014-02-14 17:44:58 |
James Page |
juju-quickstart (Ubuntu): milestone |
|
ubuntu-14.04-beta-1 |
|
| 2014-02-14 17:47:24 |
James Page |
description |
URL: https://launchpad.net/juju-quickstart
License: GNU Affero GPL v3
Description: Help both new and experienced users quickly start Juju from Ubuntu. Juju Quickstart is an opinionated command-line tool that quickly starts Juju and the GUI, whether you've never installed Juju or you have an existing Juju environment running.
The following is a draft for the MIP that I started. It might have useful information for this process as well.
= Availability =
Violation: "The package must already be in the Ubuntu universe." It is in PPA only at this time (but in the official Juju stable PPA). See https://launchpad.net/~juju/+archive/stable . The recipe is https://code.launchpad.net/~juju-gui-charmers/+recipe/juju-quickstart-daily and the associated packaging is found in https://code.launchpad.net/~juju-gui/juju-quickstart/packaging .
= Rationale =
It makes installing a key part of Ubuntu's cloud tools, Juju, much easier. It also is useful to anyone who uses Juju with its GUI regularly.
The following features, as described in https://launchpad.net/juju-quickstart, support the above two assertions.
* New users are guided, as needed, to install Juju, set up SSH keys, and configure it for first use.
* Juju environments can be created and managed from a command line interactive session.
* The Juju GUI is automatically installed, adding no additional machines (installing on an existing state server when possible).
* Bundles can be deployed, from local files, HTTP(S) URLs or the charm store, so that a complete topology of services can be set up in one simple command.
* Quickstart ends by opening the browser and automatically logging the user into the GUI, to observe and manage the environment visually.
* Users with a running Juju environment can run the quickstart command again to simply re-open the GUI without having to find the proper URL and password.
= Security =
Since we are not in Universe, our history is weak at best. However, I do not believe we fail any of the security checks, though we do ask for sudo in some cases (specifically to install juju's stable PPA and juju itself).
= Quality Assurance =
We have a very thorough test suite with 100% coverage by line measurements.
Bugs are tracked in https://bugs.launchpad.net/juju-quickstart .
Violation: "If the package ships a test suite, and there is no obvious reason why it cannot work during build (e. g. it needs root privileges or network access), it should be run during package build, and a failing test suite should fail the build." We can work to incorporate it into the build process.
Violation: "The package uses a debian/watch file whenever possible. In cases where this is not possible (e. g. native packages), the package should either provide a debian/README.source file or a debian/watch file (with comments only) providing clear instructions on how to generate the source tar file." We don't know what this means yet, but we do not have a debian/watch file in our PPA packaging.
= UI standards =
"End-user applications must be internationalized (translatable), using the standard intltool/gettext build and runtime system and produce a proper PO template during build." Not yet done.
= Dependencies =
The following need to be in main. They are currently included in our own build.
http://packages.ubuntu.com/trusty/python-jujuclient
http://packages.ubuntu.com/trusty/python-urwid
This dependency, and Python itself, is in main.
http://packages.ubuntu.com/trusty/python-yaml
= Standards compliance =
Our current packaging is certainly simple. I hope that it complies to standards but am not familiar with them beyond the most cursory read.
= Maintenance =
The Juju GUI team are the current maintainers (https://launchpad.net/~juju-gui). |
URL: https://launchpad.net/juju-quickstart
License: GNU Affero GPL v3
Description: Help both new and experienced users quickly start Juju from Ubuntu. Juju Quickstart is an opinionated command-line tool that quickly starts Juju and the GUI, whether you've never installed Juju or you have an existing Juju environment running.
= Availability =
In universe
= Rationale =
It makes installing a key part of Ubuntu's cloud tools, Juju, much easier. It also is useful to anyone who uses Juju with its GUI regularly.
The following features, as described in https://launchpad.net/juju-quickstart, support the above two assertions.
* New users are guided, as needed, to install Juju, set up SSH keys, and configure it for first use.
* Juju environments can be created and managed from a command line interactive session.
* The Juju GUI is automatically installed, adding no additional machines (installing on an existing state server when possible).
* Bundles can be deployed, from local files, HTTP(S) URLs or the charm store, so that a complete topology of services can be set up in one simple command.
* Quickstart ends by opening the browser and automatically logging the user into the GUI, to observe and manage the environment visually.
* Users with a running Juju environment can run the quickstart command again to simply re-open the GUI without having to find the proper URL and password.
= Security =
Since we are not in Universe, our history is weak at best. However, I do not believe we fail any of the security checks, though we do ask for sudo in some cases (specifically to install juju's stable PPA and juju itself).
= Quality Assurance =
We have a very thorough test suite with 100% coverage by line measurements.
Bugs are tracked in https://bugs.launchpad.net/juju-quickstart .
Violation: "If the package ships a test suite, and there is no obvious reason why it cannot work during build (e. g. it needs root privileges or network access), it should be run during package build, and a failing test suite should fail the build." We can work to incorporate it into the build process.
= UI standards =
"End-user applications must be internationalized (translatable), using the standard intltool/gettext build and runtime system and produce a proper PO template during build." Not yet done.
= Dependencies =
python-jujuclient, python-urwid
= Standards compliance =
Our current packaging is certainly simple. I hope that it complies to standards but am not familiar with them beyond the most cursory read.
= Maintenance =
The Juju GUI team are the current maintainers (https://launchpad.net/~juju-gui).
Ubuntu server team will pick bug triage alongside juju-core in distro. |
|
| 2014-02-14 17:47:49 |
James Page |
bug task added |
|
python-jujuclient (Ubuntu) |
|
| 2014-02-14 17:48:04 |
James Page |
bug task added |
|
urwid (Ubuntu) |
|
| 2014-02-14 17:48:13 |
James Page |
python-jujuclient (Ubuntu): status |
New |
Incomplete |
|
| 2014-02-14 17:48:15 |
James Page |
urwid (Ubuntu): status |
New |
Incomplete |
|
| 2014-02-14 23:55:03 |
Brian Murray |
summary |
[MIR] juju-quickstart |
[needs-packaging] [MIR] juju-quickstart |
|
| 2014-02-14 23:55:06 |
Brian Murray |
urwid (Ubuntu): importance |
Undecided |
Wishlist |
|
| 2014-02-14 23:55:09 |
Brian Murray |
python-jujuclient (Ubuntu): importance |
Undecided |
Wishlist |
|
| 2014-02-20 15:57:50 |
Robie Basak |
tags |
needs-packaging |
|
|
| 2014-02-20 15:58:00 |
Robie Basak |
summary |
[needs-packaging] [MIR] juju-quickstart |
[MIR] juju-quickstart |
|
| 2014-02-20 15:58:05 |
Robie Basak |
bug |
|
|
added subscriber Robie Basak |
| 2014-03-11 16:43:03 |
James Page |
juju-quickstart (Ubuntu): importance |
Wishlist |
High |
|
| 2014-03-11 16:43:06 |
James Page |
python-jujuclient (Ubuntu): importance |
Wishlist |
High |
|
| 2014-03-11 16:43:08 |
James Page |
urwid (Ubuntu): importance |
Wishlist |
High |
|
| 2014-03-13 10:47:49 |
Robie Basak |
bug task added |
|
python-websocket-client (Ubuntu) |
|
| 2014-03-13 10:48:02 |
Robie Basak |
python-websocket-client (Ubuntu): status |
New |
Incomplete |
|
| 2014-03-13 10:48:05 |
Robie Basak |
python-websocket-client (Ubuntu): importance |
Undecided |
High |
|
| 2014-03-13 12:33:22 |
Robie Basak |
juju-quickstart (Ubuntu): status |
New |
In Progress |
|
| 2014-03-13 12:33:26 |
Robie Basak |
juju-quickstart (Ubuntu): assignee |
|
Robie Basak (racb) |
|
| 2014-03-13 13:14:40 |
Robie Basak |
attachment added |
|
add-build-tests.debdiff https://bugs.launchpad.net/ubuntu/+source/juju-quickstart/+bug/1273865/+attachment/4022141/+files/add-build-tests.debdiff |
|
| 2014-03-13 15:20:55 |
James Page |
nominated for series |
|
Ubuntu Trusty |
|
| 2014-03-13 15:20:55 |
James Page |
bug task added |
|
urwid (Ubuntu Trusty) |
|
| 2014-03-13 15:20:55 |
James Page |
bug task added |
|
python-jujuclient (Ubuntu Trusty) |
|
| 2014-03-13 15:20:55 |
James Page |
bug task added |
|
python-websocket-client (Ubuntu Trusty) |
|
| 2014-03-13 15:20:55 |
James Page |
bug task added |
|
juju-quickstart (Ubuntu Trusty) |
|
| 2014-03-13 16:23:46 |
Ubuntu Foundations Team Bug Bot |
tags |
|
patch |
|
| 2014-03-14 14:28:47 |
Robie Basak |
bug task added |
|
websocket-client (Ubuntu) |
|
| 2014-03-14 14:29:30 |
Robie Basak |
python-websocket-client (Ubuntu Trusty): status |
Incomplete |
Invalid |
|
| 2014-03-14 14:29:47 |
Robie Basak |
websocket-client (Ubuntu Trusty): importance |
Undecided |
High |
|
| 2014-03-14 14:29:47 |
Robie Basak |
websocket-client (Ubuntu Trusty): status |
New |
Incomplete |
|
| 2014-03-14 14:41:46 |
Robie Basak |
attachment added |
|
websocket-client.debdiff https://bugs.launchpad.net/ubuntu/trusty/+source/websocket-client/+bug/1273865/+attachment/4024035/+files/websocket-client.debdiff |
|
| 2014-03-17 12:32:05 |
Robie Basak |
attachment added |
|
python-jujuclient.debdiff https://bugs.launchpad.net/ubuntu/trusty/+source/websocket-client/+bug/1273865/+attachment/4028332/+files/python-jujuclient.debdiff |
|
| 2014-03-17 14:31:12 |
Patricia Gaughen |
bug |
|
|
added subscriber Patricia Gaughen |
| 2014-03-17 17:21:15 |
Robie Basak |
description |
URL: https://launchpad.net/juju-quickstart
License: GNU Affero GPL v3
Description: Help both new and experienced users quickly start Juju from Ubuntu. Juju Quickstart is an opinionated command-line tool that quickly starts Juju and the GUI, whether you've never installed Juju or you have an existing Juju environment running.
= Availability =
In universe
= Rationale =
It makes installing a key part of Ubuntu's cloud tools, Juju, much easier. It also is useful to anyone who uses Juju with its GUI regularly.
The following features, as described in https://launchpad.net/juju-quickstart, support the above two assertions.
* New users are guided, as needed, to install Juju, set up SSH keys, and configure it for first use.
* Juju environments can be created and managed from a command line interactive session.
* The Juju GUI is automatically installed, adding no additional machines (installing on an existing state server when possible).
* Bundles can be deployed, from local files, HTTP(S) URLs or the charm store, so that a complete topology of services can be set up in one simple command.
* Quickstart ends by opening the browser and automatically logging the user into the GUI, to observe and manage the environment visually.
* Users with a running Juju environment can run the quickstart command again to simply re-open the GUI without having to find the proper URL and password.
= Security =
Since we are not in Universe, our history is weak at best. However, I do not believe we fail any of the security checks, though we do ask for sudo in some cases (specifically to install juju's stable PPA and juju itself).
= Quality Assurance =
We have a very thorough test suite with 100% coverage by line measurements.
Bugs are tracked in https://bugs.launchpad.net/juju-quickstart .
Violation: "If the package ships a test suite, and there is no obvious reason why it cannot work during build (e. g. it needs root privileges or network access), it should be run during package build, and a failing test suite should fail the build." We can work to incorporate it into the build process.
= UI standards =
"End-user applications must be internationalized (translatable), using the standard intltool/gettext build and runtime system and produce a proper PO template during build." Not yet done.
= Dependencies =
python-jujuclient, python-urwid
= Standards compliance =
Our current packaging is certainly simple. I hope that it complies to standards but am not familiar with them beyond the most cursory read.
= Maintenance =
The Juju GUI team are the current maintainers (https://launchpad.net/~juju-gui).
Ubuntu server team will pick bug triage alongside juju-core in distro. |
[juju-quickstart]
Availability: in universe, arch: all.
Rationale: key component for the Juju ecosystem.
Security: no security history. No CVEs found. No suid or sgid
executables. No executables in /sbin or /usr/sbin. No daemons. No
privileged ports (although the Juju GUI does open a privileged port,
which this package deploys). One might consider Juju to be
security-sensitive, as it controls production deployments, and this
package bootstraps Juju. This package uses sudo, although this use is
scheduled to be removed. See bug 1282630.
Quality assurance:
Upstream ships a thorough test suite which includes 100% SLOC coverage.
By design, this tool makes it possible to use juju with as minimal
configuration as possible and with no documentation reading, by
deploying the GUI for the user and presenting its interface.
No debconf questions. No long-term outstanding bugs.
No relevant packaging bugs. There are a number of active bugs open
upstream; these are being actively worked on by upstream. This package
does not deal with exotic hardware. The upstream test suite is run as
part of the package build, and a failing test suite fails the package
build. A debian/watch file exists and is functional.
UI standards:
This is an end-user console application and is not internationalized
(not translatable). This is tracked in bug 1292026.
The package does not ship a desktop file. As a console application
designed for developer use, a desktop file has minimal relevance for
developers.
Dependencies:
urwid, python-jujuclient and websocket-client are dependencies in
universe. MIR reports follow in this bug.
Standards compliance: standard and minimal dh sequencer based packaging.
FHS compliant and the packaging is up to current Debian policy.
Maintenance:
Actively maintained upstream, by the Juju GUI team. ~ubuntu-server
commits to maintaining this package in Ubuntu and is subscribed to
package bugs.
[urwid]
Availability: in universe and built on all architecture.
Rationale: dependency of juju-quickstart.
Security: no security history. No CVEs found. No suid or sgid
executables. No executables in /sbin or /usr/sbin. No daemons. No
privileged port use is apparent. urwid is a UI library, so may be used
as a UI in security sensitive software, although this isn't the case
with juju-quickstart.
Quality assurance:
As a library, this package is functional on installation. No debconf
questions. No major long-term outstanding bugs. Upstream is active. No
use of exotic hardware.
Test-related packaging bugs in Debian are all fixed in Debian svn. The
only other bug in Debian is believed fixed already. Upstream has more
bugs, but none of them appear to be major issues for general urwid use.
No use of exotic hardware. Test suite is run as part of the package
build, and fails the build if tests fail. debian/watch file is out of
date, but fixed in current Debian svn.
UI standards: N/A
Dependencies: all in main.
Standards compliance: minimal cdbs+debhelper based packaging. Ideally
this would use the dh sequencer now, and I get the impression that DPMT
would be happy to switch it. But urwid is a relatively slow moving
project, and the rules file is simple and minimal enough that it doesn't
seem worth switching just for the sake of it. If there is a problem that
requires a change, then it could be switched to dh at that time easily
enough. FHS compliant and the packaging is up to current Debian policy.
urwid is a long-lived relatively stable package, with minimal
maintenance requirements. Upstream is active though, and all bugs in
Debian BTS are fixed in Debian svn. ~ubuntu-server commits to
maintaining this package in Ubuntu and is subscribed to package bugs.
[python-jujuclient]
Availability: in universe, arch: all.
Rationale: dependency of juju-quickstart.
Security: no security history. No CVEs found. No suid or sgid
executables. No executables in /sbin or /usr/sbin. No daemons. No
privileged ports. python-jujuclient is used by juju-quickstart to manage
deployments; the deployments themselves are security-sensitive.
Quality assurance:
As a library, this package is functional on installation. No debconf
questions. No long-term outstanding bugs. Upstream is active. No use of
exotic hardware.
No relevant upstream test suite.
debian/watch file is present and working.
UI standards: N/A
Dependencies: websocket-client is in universe (also see bug 1292502
regarding the package naming of this dependency). MIR report follows.
Standards compliance: standard and minimal dh sequencer based packaging.
FHS compliant and the packaging is up to current Debian policy.
Maintenance: actively maintained upstream, by Kapil Thangavelu.
~ubuntu-server commits to maintaining this package in Ubuntu and is
subscribed to package bugs. The upstream code says: "Seriously Alpha.
Works now, but API *will* change". Upstream responds: "yeah.. i should
take that out, it was commentary from the first release against the api,
but in truth it has been pretty stable to date".
[websocket-client]
Availability: in universe, arch: all.
Rationale: dependency of python-jujuclient.
Security: no security history. No CVEs found. No suid or sgid
executables. No executables in /sbin or /usr/sbin. No daemons. This
library is a client for the WebSocket protocol, and as such will
generally handle untrusted input, although this isn't the case with
juju-quickstart.
Quality assurance:
As a library, this package is functional on installation. No debconf
questions. No major long-term outstanding bugs. Upstream is active. No
use of exotic hardware. Test suite is run as part of the package build,
and fails the build if tests fail. debian/watch file is present and
working.
There was an issue with a conflict between Debian and Ubuntu packaging
and tracked in bug 1292502, but this is now resolved. The upstream test
suite had to be imported using a distribution patch in order to run it
as part of the package build (bug 1292511); this was reported to
upstream, so hopefully will be fixed upstream soon so that the
distribution patch can be removed.
UI standards: N/A
Dependencies: all in main.
Standards compliance: standard and minimal dh sequencer based packaging.
FHS compliant and the packaging is up to current Debian policy.
Maintenance: upstream is active. ~ubuntu-server commits to maintaining
this package in Ubuntu and is subscribed to package bugs. |
|
| 2014-03-17 17:22:16 |
Robie Basak |
juju-quickstart (Ubuntu Trusty): status |
In Progress |
New |
|
| 2014-03-17 17:22:38 |
Robie Basak |
juju-quickstart (Ubuntu Trusty): assignee |
Robie Basak (racb) |
|
|
| 2014-03-17 17:22:49 |
Robie Basak |
python-jujuclient (Ubuntu Trusty): status |
Incomplete |
New |
|
| 2014-03-17 17:22:59 |
Robie Basak |
urwid (Ubuntu Trusty): status |
Incomplete |
New |
|
| 2014-03-17 17:23:09 |
Robie Basak |
websocket-client (Ubuntu Trusty): status |
Incomplete |
New |
|
| 2014-03-17 17:23:19 |
Robie Basak |
bug |
|
|
added subscriber MIR approval team |
| 2014-03-18 11:42:53 |
Robie Basak |
summary |
[MIR] juju-quickstart |
[MIR] juju-quickstart, python-jujuclient, urwid, websocket-client |
|
| 2014-03-18 11:49:24 |
Robie Basak |
description |
[juju-quickstart]
Availability: in universe, arch: all.
Rationale: key component for the Juju ecosystem.
Security: no security history. No CVEs found. No suid or sgid
executables. No executables in /sbin or /usr/sbin. No daemons. No
privileged ports (although the Juju GUI does open a privileged port,
which this package deploys). One might consider Juju to be
security-sensitive, as it controls production deployments, and this
package bootstraps Juju. This package uses sudo, although this use is
scheduled to be removed. See bug 1282630.
Quality assurance:
Upstream ships a thorough test suite which includes 100% SLOC coverage.
By design, this tool makes it possible to use juju with as minimal
configuration as possible and with no documentation reading, by
deploying the GUI for the user and presenting its interface.
No debconf questions. No long-term outstanding bugs.
No relevant packaging bugs. There are a number of active bugs open
upstream; these are being actively worked on by upstream. This package
does not deal with exotic hardware. The upstream test suite is run as
part of the package build, and a failing test suite fails the package
build. A debian/watch file exists and is functional.
UI standards:
This is an end-user console application and is not internationalized
(not translatable). This is tracked in bug 1292026.
The package does not ship a desktop file. As a console application
designed for developer use, a desktop file has minimal relevance for
developers.
Dependencies:
urwid, python-jujuclient and websocket-client are dependencies in
universe. MIR reports follow in this bug.
Standards compliance: standard and minimal dh sequencer based packaging.
FHS compliant and the packaging is up to current Debian policy.
Maintenance:
Actively maintained upstream, by the Juju GUI team. ~ubuntu-server
commits to maintaining this package in Ubuntu and is subscribed to
package bugs.
[urwid]
Availability: in universe and built on all architecture.
Rationale: dependency of juju-quickstart.
Security: no security history. No CVEs found. No suid or sgid
executables. No executables in /sbin or /usr/sbin. No daemons. No
privileged port use is apparent. urwid is a UI library, so may be used
as a UI in security sensitive software, although this isn't the case
with juju-quickstart.
Quality assurance:
As a library, this package is functional on installation. No debconf
questions. No major long-term outstanding bugs. Upstream is active. No
use of exotic hardware.
Test-related packaging bugs in Debian are all fixed in Debian svn. The
only other bug in Debian is believed fixed already. Upstream has more
bugs, but none of them appear to be major issues for general urwid use.
No use of exotic hardware. Test suite is run as part of the package
build, and fails the build if tests fail. debian/watch file is out of
date, but fixed in current Debian svn.
UI standards: N/A
Dependencies: all in main.
Standards compliance: minimal cdbs+debhelper based packaging. Ideally
this would use the dh sequencer now, and I get the impression that DPMT
would be happy to switch it. But urwid is a relatively slow moving
project, and the rules file is simple and minimal enough that it doesn't
seem worth switching just for the sake of it. If there is a problem that
requires a change, then it could be switched to dh at that time easily
enough. FHS compliant and the packaging is up to current Debian policy.
urwid is a long-lived relatively stable package, with minimal
maintenance requirements. Upstream is active though, and all bugs in
Debian BTS are fixed in Debian svn. ~ubuntu-server commits to
maintaining this package in Ubuntu and is subscribed to package bugs.
[python-jujuclient]
Availability: in universe, arch: all.
Rationale: dependency of juju-quickstart.
Security: no security history. No CVEs found. No suid or sgid
executables. No executables in /sbin or /usr/sbin. No daemons. No
privileged ports. python-jujuclient is used by juju-quickstart to manage
deployments; the deployments themselves are security-sensitive.
Quality assurance:
As a library, this package is functional on installation. No debconf
questions. No long-term outstanding bugs. Upstream is active. No use of
exotic hardware.
No relevant upstream test suite.
debian/watch file is present and working.
UI standards: N/A
Dependencies: websocket-client is in universe (also see bug 1292502
regarding the package naming of this dependency). MIR report follows.
Standards compliance: standard and minimal dh sequencer based packaging.
FHS compliant and the packaging is up to current Debian policy.
Maintenance: actively maintained upstream, by Kapil Thangavelu.
~ubuntu-server commits to maintaining this package in Ubuntu and is
subscribed to package bugs. The upstream code says: "Seriously Alpha.
Works now, but API *will* change". Upstream responds: "yeah.. i should
take that out, it was commentary from the first release against the api,
but in truth it has been pretty stable to date".
[websocket-client]
Availability: in universe, arch: all.
Rationale: dependency of python-jujuclient.
Security: no security history. No CVEs found. No suid or sgid
executables. No executables in /sbin or /usr/sbin. No daemons. This
library is a client for the WebSocket protocol, and as such will
generally handle untrusted input, although this isn't the case with
juju-quickstart.
Quality assurance:
As a library, this package is functional on installation. No debconf
questions. No major long-term outstanding bugs. Upstream is active. No
use of exotic hardware. Test suite is run as part of the package build,
and fails the build if tests fail. debian/watch file is present and
working.
There was an issue with a conflict between Debian and Ubuntu packaging
and tracked in bug 1292502, but this is now resolved. The upstream test
suite had to be imported using a distribution patch in order to run it
as part of the package build (bug 1292511); this was reported to
upstream, so hopefully will be fixed upstream soon so that the
distribution patch can be removed.
UI standards: N/A
Dependencies: all in main.
Standards compliance: standard and minimal dh sequencer based packaging.
FHS compliant and the packaging is up to current Debian policy.
Maintenance: upstream is active. ~ubuntu-server commits to maintaining
this package in Ubuntu and is subscribed to package bugs. |
[juju-quickstart]
Availability: in universe, arch: all.
Rationale: key component for the Juju ecosystem.
Security: no security history. No CVEs found. No suid or sgid
executables. No executables in /sbin or /usr/sbin. No daemons. No
privileged ports (although the Juju GUI does open a privileged port,
which this package deploys). One might consider Juju to be
security-sensitive, as it controls production deployments, and this
package bootstraps Juju. This package uses sudo, although this use is
scheduled to be removed. See bug 1282630.
Quality assurance:
Upstream ships a thorough test suite which includes 100% SLOC coverage.
By design, this tool makes it possible to use juju with as minimal
configuration as possible and with no documentation reading, by
deploying the GUI for the user and presenting its interface.
No debconf questions. No long-term outstanding bugs.
No relevant packaging bugs. There are a number of active bugs open
upstream; these are being actively worked on by upstream. This package
does not deal with exotic hardware. The upstream test suite is run as
part of the package build, and a failing test suite fails the package
build. A debian/watch file exists and is functional.
UI standards:
This is an end-user console application and is not internationalized
(not translatable). This is tracked in bug 1292026.
The package does not ship a desktop file. As a console application
designed for developer use, a desktop file has minimal relevance for
developers.
Dependencies:
urwid, python-jujuclient and websocket-client are dependencies in
universe. MIR reports follow in this bug.
Standards compliance: standard and minimal dh sequencer based packaging.
FHS compliant and the packaging is up to current Debian policy.
Maintenance:
Actively maintained upstream, by the Juju GUI team. ~ubuntu-server
commits to maintaining this package in Ubuntu and is subscribed to
package bugs.
[urwid]
Availability: in universe and built on all architecture.
Rationale: dependency of juju-quickstart.
Security: no security history. No CVEs found. No suid or sgid
executables. No executables in /sbin or /usr/sbin. No daemons. No
privileged port use is apparent. urwid is a UI library, so may be used
as a UI in security sensitive software, although this isn't the case
with juju-quickstart.
Quality assurance:
As a library, this package is functional on installation. No debconf
questions. No major long-term outstanding bugs. Upstream is active. No
use of exotic hardware.
Test-related packaging bugs in Debian are all fixed in Debian svn. The
only other bug in Debian is believed fixed already. Upstream has more
bugs, but none of them appear to be major issues for general urwid use.
No use of exotic hardware. Test suite is run as part of the package
build, and fails the build if tests fail. debian/watch file is out of
date, but fixed in current Debian svn.
UI standards: N/A
Dependencies: all in main.
Standards compliance: minimal cdbs+debhelper based packaging. Ideally
this would use the dh sequencer now, and I get the impression that DPMT
would be happy to switch it. But urwid is a relatively slow moving
project, and the rules file is simple and minimal enough that it doesn't
seem worth switching just for the sake of it. If there is a problem that
requires a change, then it could be switched to dh at that time easily
enough. FHS compliant and the packaging is up to current Debian policy.
urwid is a long-lived relatively stable package, with minimal
maintenance requirements. Upstream is active though, and all bugs in
Debian BTS are fixed in Debian svn. ~ubuntu-server commits to
maintaining this package in Ubuntu and is subscribed to package bugs.
[python-jujuclient]
Availability: in universe, arch: all.
Rationale: dependency of juju-quickstart.
Security: no security history. No CVEs found. No suid or sgid
executables. No executables in /sbin or /usr/sbin. No daemons. No
privileged ports. python-jujuclient is used by juju-quickstart to manage
deployments; the deployments themselves are security-sensitive.
Quality assurance:
As a library, this package is functional on installation. No debconf
questions. No long-term outstanding bugs. Upstream is active. No use of
exotic hardware.
No relevant upstream test suite; tracked in bug 1293467.
debian/watch file is present and working.
UI standards: N/A
Dependencies: websocket-client is in universe (also see bug 1292502
regarding the package naming of this dependency). MIR report follows.
Standards compliance: standard and minimal dh sequencer based packaging.
FHS compliant and the packaging is up to current Debian policy.
Maintenance: actively maintained upstream, by Kapil Thangavelu.
~ubuntu-server commits to maintaining this package in Ubuntu and is
subscribed to package bugs. The upstream code says: "Seriously Alpha.
Works now, but API *will* change". Upstream responds: "yeah.. i should
take that out, it was commentary from the first release against the api,
but in truth it has been pretty stable to date".
[websocket-client]
Availability: in universe, arch: all.
Rationale: dependency of python-jujuclient.
Security: no security history. No CVEs found. No suid or sgid
executables. No executables in /sbin or /usr/sbin. No daemons. This
library is a client for the WebSocket protocol, and as such will
generally handle untrusted input, although this isn't the case with
juju-quickstart.
Quality assurance:
As a library, this package is functional on installation. No debconf
questions. No major long-term outstanding bugs. Upstream is active. No
use of exotic hardware. Test suite is run as part of the package build,
and fails the build if tests fail. debian/watch file is present and
working.
There was an issue with a conflict between Debian and Ubuntu packaging
and tracked in bug 1292502, but this is now resolved. The upstream test
suite had to be imported using a distribution patch in order to run it
as part of the package build (bug 1292511); this was reported to
upstream, so hopefully will be fixed upstream soon so that the
distribution patch can be removed.
UI standards: N/A
Dependencies: all in main.
Standards compliance: standard and minimal dh sequencer based packaging.
FHS compliant and the packaging is up to current Debian policy.
Maintenance: upstream is active. ~ubuntu-server commits to maintaining
this package in Ubuntu and is subscribed to package bugs. |
|
| 2014-03-25 21:16:00 |
Michael Terry |
juju-quickstart (Ubuntu Trusty): status |
New |
Incomplete |
|
| 2014-03-26 16:52:45 |
Francesco Banconi |
bug |
|
|
added subscriber Francesco Banconi |
| 2014-03-27 15:37:12 |
Robie Basak |
juju-quickstart (Ubuntu Trusty): status |
Incomplete |
New |
|
| 2014-03-31 13:11:05 |
Robie Basak |
python-jujuclient (Ubuntu Trusty): status |
New |
Incomplete |
|
| 2014-03-31 13:11:39 |
Robie Basak |
urwid (Ubuntu Trusty): status |
New |
Incomplete |
|
| 2014-03-31 13:11:44 |
Robie Basak |
websocket-client (Ubuntu Trusty): status |
New |
Incomplete |
|
| 2014-03-31 13:11:49 |
Robie Basak |
juju-quickstart (Ubuntu Trusty): status |
New |
Incomplete |
|
| 2014-04-09 11:02:49 |
James Page |
nominated for series |
|
Ubuntu U-series |
|
| 2014-04-09 11:02:49 |
James Page |
bug task added |
|
urwid (Ubuntu U-series) |
|
| 2014-04-09 11:02:49 |
James Page |
bug task added |
|
websocket-client (Ubuntu U-series) |
|
| 2014-04-09 11:02:49 |
James Page |
bug task added |
|
python-jujuclient (Ubuntu U-series) |
|
| 2014-04-09 11:02:49 |
James Page |
bug task added |
|
python-websocket-client (Ubuntu U-series) |
|
| 2014-04-09 11:02:49 |
James Page |
bug task added |
|
juju-quickstart (Ubuntu U-series) |
|
| 2014-04-09 11:03:05 |
James Page |
bug task deleted |
juju-quickstart (Ubuntu Trusty) |
|
|
| 2014-04-09 11:03:13 |
James Page |
bug task deleted |
python-jujuclient (Ubuntu Trusty) |
|
|
| 2014-04-09 11:03:22 |
James Page |
bug task deleted |
python-websocket-client (Ubuntu Trusty) |
|
|
| 2014-04-09 11:03:30 |
James Page |
bug task deleted |
urwid (Ubuntu Trusty) |
|
|
| 2014-04-09 11:03:38 |
James Page |
bug task deleted |
websocket-client (Ubuntu Trusty) |
|
|
| 2016-04-24 10:47:31 |
Rolf Leggewie |
juju-quickstart (Ubuntu Utopic): status |
New |
Won't Fix |
|
| 2016-04-24 10:47:34 |
Rolf Leggewie |
python-jujuclient (Ubuntu Utopic): status |
New |
Won't Fix |
|
| 2016-04-24 10:47:37 |
Rolf Leggewie |
python-websocket-client (Ubuntu Utopic): status |
New |
Won't Fix |
|
| 2016-04-24 10:47:42 |
Rolf Leggewie |
urwid (Ubuntu Utopic): status |
New |
Won't Fix |
|
| 2016-04-24 10:47:44 |
Rolf Leggewie |
websocket-client (Ubuntu Utopic): status |
New |
Won't Fix |
|
| 2016-06-24 04:17:28 |
Launchpad Janitor |
websocket-client (Ubuntu): status |
Incomplete |
Expired |
|
| 2016-06-24 04:17:30 |
Launchpad Janitor |
python-jujuclient (Ubuntu): status |
Incomplete |
Expired |
|
| 2016-06-24 04:17:32 |
Launchpad Janitor |
urwid (Ubuntu): status |
Incomplete |
Expired |
|
