[Bug 145213] Please backport sysstat 7.1.4 or 8.0.0 from Gutsy to Feisty
Motin
motin at demomusic.nu
Wed Sep 26 14:12:11 BST 2007
Public bug reported:
1. Only packages currently in Ubuntu's development branches are eligible
for backporting. We do NOT take packages from Debian repositories,
unofficial repositories, or user-contributed source or binary packages.
> Version 7.1.4-1 is available in Gutsy: http://packages.ubuntu.com/gutsy/admin/sysstat
> Version 8.0.0 ought to be available in Gutsy in some time: https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/145209
2. Backports of large, interdepending application stacks are bad!
> 'tis a mere <200kb package. Shouldn't count as large. Interdepending I
don't know.
3. New versions can be backported, when they're already compatible with
OS and system-relevant libraries.
> It needs a 2.6.20+ kernel, which Feisty has. ./configure and make runs
fine on Feisty (both versions)
4. No new libraries which will "break" or affect other applications
(e.g. libvorbis, libz, etc.) unless the update fixes an exploit.
> Can't see this happening due to a system logger...
5. No changes to language interpreters (python, mono). These could
affect existing packages in unexpected ways.
> Check!
6. Applications to be backported must have meaningful benefits to the user not attainable via other processes. Specifically:
1. The sole purpose must not be to fix a bug or security vulnerability. There are more correct processes for these types of defects (specifically Security team and [WWW] https://wiki.ubuntu.com/StableReleaseUpdates). Exceptions may be granted ONLY in the case that the other processes have failed or refused to address the issue. Please, for bugfixes, try [WWW] https://wiki.ubuntu.com/StableReleaseUpdates first. We will reject any Backports requests for bugfixes if SRU has not been attempted.
> Check!
2. The application, therefore, should have some significant new
feature or benefits.
> The current Feisty version (7.0.0) does not include the program
pidstat (included in 7.1.4+), which is a significant new feature. After
some general discussion regarding a longstanding other (severe) Feisty
bug (regarding abnormal disk activity), it was concluded that pidstat
probably is the only program that will inform me of what process this
bug is caused by. As soon as pidstat is available I can then report the
bug as approriate.
PS Seems like http://sharkattack.media.mit.edu/request is down atm.
Can't submit request there atm
Edit: Grammatical error
** Affects: feisty-backports
Importance: Undecided
Status: New
** Description changed:
1. Only packages currently in Ubuntu's development branches are eligible
for backporting. We do NOT take packages from Debian repositories,
unofficial repositories, or user-contributed source or binary packages.
> Version 7.1.4-1 is available in Gutsy: http://packages.ubuntu.com/gutsy/admin/sysstat
> Version 8.0.0 ought to be available in Gutsy in some time: https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/145209
2. Backports of large, interdepending application stacks are bad!
> 'tis a mere <200kb package. Shouldn't count as large. Interdepending I
don't know.
3. New versions can be backported, when they're already compatible with
OS and system-relevant libraries.
> It needs a 2.6.20+ kernel, which Feisty has. ./configure and make runs
fine on Feisty (both versions)
4. No new libraries which will "break" or affect other applications
(e.g. libvorbis, libz, etc.) unless the update fixes an exploit.
- > Wouldn't can't see this happening.
+ > Can't see this happening due to a system logger...
5. No changes to language interpreters (python, mono). These could
affect existing packages in unexpected ways.
> Check!
6. Applications to be backported must have meaningful benefits to the user not attainable via other processes. Specifically:
1. The sole purpose must not be to fix a bug or security vulnerability. There are more correct processes for these types of defects (specifically Security team and [WWW] https://wiki.ubuntu.com/StableReleaseUpdates). Exceptions may be granted ONLY in the case that the other processes have failed or refused to address the issue. Please, for bugfixes, try [WWW] https://wiki.ubuntu.com/StableReleaseUpdates first. We will reject any Backports requests for bugfixes if SRU has not been attempted.
> Check!
2. The application, therefore, should have some significant new
feature or benefits.
> The current Feisty version (7.0.0) does not include the program
pidstat (included in 7.1.4+), which is a significant new feature. After
some general discussion regarding a longstanding other (severe) Feisty
bug (regarding abnormal disk activity), it was concluded that pidstat
probably is the only program that will inform me of what process this
bug is caused by. As soon as pidstat is available I can then report the
bug as approriate.
PS Seems like http://sharkattack.media.mit.edu/request is down atm.
Can't submit request there atm
+
+ Edit: Grammatical error
--
Please backport sysstat 7.1.4 or 8.0.0 from Gutsy to Feisty
https://bugs.launchpad.net/bugs/145213
You received this bug notification because you are a member of Ubuntu
Backporters, which is the registrant for Feisty Backports.
More information about the ubuntu-backports
mailing list