2008-09-09 19:17:20 |
Chuck Short |
bug |
|
|
added bug |
2008-09-09 19:17:30 |
Chuck Short |
bug |
|
|
added subscriber MIR approval team |
2008-09-11 19:19:39 |
Christopher Armstrong |
description |
I would like to ask for a Main Inclusion exception for smart. It is needed by launchpad.
https://wiki.ubuntu.com/SmartMIR
If you have any questions please feel free to ask me.
Thanks
chuck |
I would like to ask for a Main Inclusion for python-smartpm. It is needed by landscape-client.
https://wiki.ubuntu.com/MainInclusionReportPythonSmartpm
|
|
2008-09-11 19:19:39 |
Christopher Armstrong |
title |
MIR for smart |
MIR for python-smartpm |
|
2008-09-11 19:20:49 |
Dustin Kirkland |
smart: status |
New |
Confirmed |
|
2008-09-11 19:20:49 |
Dustin Kirkland |
smart: importance |
Undecided |
Medium |
|
2008-09-11 19:20:49 |
Dustin Kirkland |
smart: statusexplanation |
|
|
|
2008-09-11 19:20:49 |
Dustin Kirkland |
smart: milestone |
|
intrepid-alpha-6 |
|
2008-09-12 16:07:24 |
Martin Pitt |
smart: status |
Confirmed |
In Progress |
|
2008-09-12 16:07:24 |
Martin Pitt |
smart: statusexplanation |
|
As discussed in today's phone call:
* Approved the library for main, since we have the main developer on board, and will fix problems anyway for Landscape. This is similar to RPM which has been in main from day 1 for LSB compatibility.
* Having the smart executable in main is possible as well if it significantly eases packaging. In this case we need to make sure that it at least does not get installed by default on fresh installs or upgrades, so that people won't start using it for dist-upgrades and the like. However, since it seems to be possible to keep the binary in universe, that's the better solution, of course. |
|
2008-09-12 16:10:28 |
Martin Pitt |
smart: status |
In Progress |
Fix Released |
|
2008-09-12 16:10:28 |
Martin Pitt |
smart: statusexplanation |
As discussed in today's phone call:
* Approved the library for main, since we have the main developer on board, and will fix problems anyway for Landscape. This is similar to RPM which has been in main from day 1 for LSB compatibility.
* Having the smart executable in main is possible as well if it significantly eases packaging. In this case we need to make sure that it at least does not get installed by default on fresh installs or upgrades, so that people won't start using it for dist-upgrades and the like. However, since it seems to be possible to keep the binary in universe, that's the better solution, of course. |
python-smartpm and smart source promoted to main. |
|