Weekly suggestions of bugs for Stable Release Updates.
Hi
We'd like to get your suggestions on the bugs listed below that may be
considered for backports to the stable releases. The bugs must meet
meet the SRU criteria.
= SRU criteria =
As outlined in the Stable Release Updates Policy [1], Stable Release
Updates will only be issued in order to fix *high-impact*
bugs.
A. Bugs which may, under realistic circumstances, directly cause a security
vulnerability. These are done by the Ubuntu Security Team.
B. Bugs which represent severe regressions from the previous release of
Ubuntu. This includes packages which are totally unusable, like being
uninstallable or crashing on startup.
C. Bugs which may, under realistic circumstances, directly cause a loss of
user data.
D. Bugs which do not fit under above categories, but (1) have an obviously
safe patch and (2) affect an application rather than critical
infrastructure packages (like X.org or the kernel).
E. For Long Term Support releases we regularly want to enable new hardware.
Such changes are appropriate provided that we can ensure to not affect
upgrades on existing hardware. For example, modaliases of newly introduced
drivers must not overlap with previously shipped drivers.
F. FTBFS (Fails To Build From Source) can also be considered. Please note
that in main the release process ensures that there are no binaries which
are not built from a current source. Usually those bugs should only be
SRUed in conjunction with another bug fix.
For new upstream versions of packages which provide new features, but don't fix
critical bugs, a backport [2] should be requested instead.
If you find a bug below that would qualify as a Stable Release Update according
to any of the criteria outlined above, you can suggest it by replying to this
email mentioning the bug number and the criteria letter (as defined above):
* bug 12345 - ...
[....]
+1: A
* bug 67890 - ...
[....]
+1: D
Bugs listed below that will not be suggested in one week on Mon July 12
will be automatically declined.
=== List of bugs nominated last week: ===
* bug 591100 - autofs5 (Ubuntu) - Undecided
autofs5 eats the cpu if you have large groups
http://bugs.launchpad.net/bugs/591100
* bug 520601 - autofs5 (Ubuntu) - Medium
package autofs5 5.0.4-3.1ubuntu4 failed to install/upgrade: trying to overwrite '/usr/sbin/automount', which is also in package autofs 0:4.1.4+debian-3ubuntu1
http://bugs.launchpad.net/bugs/520601
* bug 575945 - chkrootkit (Ubuntu) - Low
[SRU] chkrootkit falsely flags files owned by Firefox 3 and Sun Java 6 valid packages
http://bugs.launchpad.net/bugs/575945
* bug 588410 - eucalyptus (Ubuntu) - High
dynamic block storage should use virtio
http://bugs.launchpad.net/bugs/588410
* bug 595421 - eucalyptus (Ubuntu) - High
Eucalyptus doesn't start with latest stable version of "Groovy"
http://bugs.launchpad.net/bugs/595421
* bug 599910 - libvirt (Ubuntu) - Undecided
Libvirt/kvm permissions/ownership issue on upgrade from Karmic to Lucid
http://bugs.launchpad.net/bugs/599910
* bug 579584 - libvirt (Ubuntu) - Medium
setgid, setuid needed by /etc/apparmor.d/abstractions/libvirt-qemu
http://bugs.launchpad.net/bugs/579584
* bug 288358 - nmap (Ubuntu) - Medium
Nmap package missing lua libraries, also doesn't look in debian locations
http://bugs.launchpad.net/bugs/288358
* bug 579737 - openvpn (Ubuntu) - Medium
OpenVPN client connect hangs on PUSH_REQUEST
http://bugs.launchpad.net/bugs/579737
* bug 598649 - qemu-kvm (Ubuntu) - Medium
cannot boot grub multiboot image with kvm -kernel
http://bugs.launchpad.net/bugs/598649
* bug 601004 - setserial (Ubuntu) - High
setserial fails to build from source in maverick
http://bugs.launchpad.net/bugs/601004
* bug 227881 - tftp-hpa (Ubuntu) - Undecided
tftpd-hpa does not use /etc/default/tftp-hpa options
http://bugs.launchpad.net/bugs/227881
* bug 589142 - tickcount (Ubuntu) - Medium
[FTBFS] Error in PYTHONPATH
http://bugs.launchpad.net/bugs/589142
* bug 590111 - whois (Ubuntu) - Wishlist
Please merge whois (5.0.5) main from debian unstable
http://bugs.launchpad.net/bugs/590111
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
07-12-2010, 11:58 AM
Weekly suggestions of bugs for Stable Release Updates.
Hi
We'd like to get your suggestions on the bugs listed below that may be
considered for backports to the stable releases. The bugs must meet
meet the SRU criteria.
= SRU criteria =
As outlined in the Stable Release Updates Policy [1], Stable Release
Updates will only be issued in order to fix *high-impact*
bugs.
A. Bugs which may, under realistic circumstances, directly cause a security
vulnerability. These are done by the Ubuntu Security Team.
B. Bugs which represent severe regressions from the previous release of
Ubuntu. This includes packages which are totally unusable, like being
uninstallable or crashing on startup.
C. Bugs which may, under realistic circumstances, directly cause a loss of
user data.
D. Bugs which do not fit under above categories, but (1) have an obviously
safe patch and (2) affect an application rather than critical
infrastructure packages (like X.org or the kernel).
E. For Long Term Support releases we regularly want to enable new hardware.
Such changes are appropriate provided that we can ensure to not affect
upgrades on existing hardware. For example, modaliases of newly introduced
drivers must not overlap with previously shipped drivers.
F. FTBFS (Fails To Build From Source) can also be considered. Please note
that in main the release process ensures that there are no binaries which
are not built from a current source. Usually those bugs should only be
SRUed in conjunction with another bug fix.
For new upstream versions of packages which provide new features, but don't fix
critical bugs, a backport [2] should be requested instead.
If you find a bug below that would qualify as a Stable Release Update according
to any of the criteria outlined above, you can suggest it by replying to this
email mentioning the bug number and the criteria letter (as defined above):
* bug 12345 - ...
[....]
+1: A
* bug 67890 - ...
[....]
+1: D
Bugs listed below that will not be suggested in one week on Mon July 19
will be automatically declined.
=== List of bugs nominated last week: ===
* bug 550689 - vm-builder (Ubuntu) - Medium
vmbuilder: error: no such option: --firstlogin
http://bugs.launchpad.net/bugs/550689
* bug 536942 - vm-builder (Ubuntu) - High
--firstboot option broken in 0.12.2-0ubuntu3
http://bugs.launchpad.net/bugs/536942
* bug 590111 - whois (Ubuntu) - Wishlist
Please merge whois (5.0.5) main from debian unstable
http://bugs.launchpad.net/bugs/590111
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
07-12-2010, 01:36 PM
"Serge E. Hallyn"
Weekly suggestions of bugs for Stable Release Updates.
Quoting zulcss@gmail.com (zulcss@gmail.com):
> * bug 603363 - openssh (Ubuntu) - Medium
> sshd never stops, prevents umount of /usr partition
> http://bugs.launchpad.net/bugs/603363
+1: A
Not cleanly umounting is a huge deal.
-serge
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
07-12-2010, 03:18 PM
Jamie Strandboge
Weekly suggestions of bugs for Stable Release Updates.
On Mon, 2010-07-12 at 04:58 -0700, zulcss@gmail.com wrote:
> * bug 579584 - libvirt (Ubuntu) - Medium
> setgid, setuid needed by /etc/apparmor.d/abstractions/libvirt-qemu
> http://bugs.launchpad.net/bugs/579584
>
+1 D
--
Jamie Strandboge | http://www.canonical.com
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
07-19-2010, 09:27 AM
Weekly suggestions of bugs for Stable Release Updates.
Hi
We'd like to get your suggestions on the bugs listed below that may be
considered for backports to the stable releases. The bugs must meet
meet the SRU criteria.
= SRU criteria =
As outlined in the Stable Release Updates Policy [1], Stable Release
Updates will only be issued in order to fix *high-impact*
bugs.
A. Bugs which may, under realistic circumstances, directly cause a security
vulnerability. These are done by the Ubuntu Security Team.
B. Bugs which represent severe regressions from the previous release of
Ubuntu. This includes packages which are totally unusable, like being
uninstallable or crashing on startup.
C. Bugs which may, under realistic circumstances, directly cause a loss of
user data.
D. Bugs which do not fit under above categories, but (1) have an obviously
safe patch and (2) affect an application rather than critical
infrastructure packages (like X.org or the kernel).
E. For Long Term Support releases we regularly want to enable new hardware.
Such changes are appropriate provided that we can ensure to not affect
upgrades on existing hardware. For example, modaliases of newly introduced
drivers must not overlap with previously shipped drivers.
F. FTBFS (Fails To Build From Source) can also be considered. Please note
that in main the release process ensures that there are no binaries which
are not built from a current source. Usually those bugs should only be
SRUed in conjunction with another bug fix.
For new upstream versions of packages which provide new features, but don't fix
critical bugs, a backport [2] should be requested instead.
If you find a bug below that would qualify as a Stable Release Update according
to any of the criteria outlined above, you can suggest it by replying to this
email mentioning the bug number and the criteria letter (as defined above):
* bug 12345 - ...
[....]
+1: A
* bug 67890 - ...
[....]
+1: D
Bugs listed below that will not be suggested in one week on Mon July 26
will be automatically declined.
=== List of bugs nominated last week: ===
* bug 579909 - mysql-5.1 (Ubuntu) - High
mysql fails to build form source with Linaro and CodeSourcery toolchains
http://bugs.launchpad.net/bugs/579909
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
07-26-2010, 01:59 PM
Weekly suggestions of bugs for Stable Release Updates.
Hi
We'd like to get your suggestions on the bugs listed below that may be
considered for backports to the stable releases. The bugs must meet
meet the SRU criteria.
= SRU criteria =
As outlined in the Stable Release Updates Policy [1], Stable Release
Updates will only be issued in order to fix *high-impact*
bugs.
A. Bugs which may, under realistic circumstances, directly cause a security
vulnerability. These are done by the Ubuntu Security Team.
B. Bugs which represent severe regressions from the previous release of
Ubuntu. This includes packages which are totally unusable, like being
uninstallable or crashing on startup.
C. Bugs which may, under realistic circumstances, directly cause a loss of
user data.
D. Bugs which do not fit under above categories, but (1) have an obviously
safe patch and (2) affect an application rather than critical
infrastructure packages (like X.org or the kernel).
E. For Long Term Support releases we regularly want to enable new hardware.
Such changes are appropriate provided that we can ensure to not affect
upgrades on existing hardware. For example, modaliases of newly introduced
drivers must not overlap with previously shipped drivers.
F. FTBFS (Fails To Build From Source) can also be considered. Please note
that in main the release process ensures that there are no binaries which
are not built from a current source. Usually those bugs should only be
SRUed in conjunction with another bug fix.
For new upstream versions of packages which provide new features, but don't fix
critical bugs, a backport [2] should be requested instead.
If you find a bug below that would qualify as a Stable Release Update according
to any of the criteria outlined above, you can suggest it by replying to this
email mentioning the bug number and the criteria letter (as defined above):
* bug 12345 - ...
[....]
+1: A
* bug 67890 - ...
[....]
+1: D
Bugs listed below that will not be suggested in one week on Mon August 02
will be automatically declined.
=== List of bugs nominated last week: ===
== lucid ==
* bug 609290 - apache2 - High
overlapping memcpy in ssl_io_input_read
https://bugs.launchpad.net/bugs/609290
* bug 605721 - tgt (Ubuntu) - Medium
tgtd target will not start unless it's configured with "allow-in-use yes"
http://bugs.launchpad.net/bugs/605721
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
08-16-2010, 02:53 PM
Weekly suggestions of bugs for Stable Release Updates.
Hi
We'd like to get your suggestions on the bugs listed below that may be
considered for backports to the stable releases. The bugs must meet
meet the SRU criteria.
= SRU criteria =
As outlined in the Stable Release Updates Policy [1], Stable Release
Updates will only be issued in order to fix *high-impact*
bugs.
A. Bugs which may, under realistic circumstances, directly cause a security
vulnerability. These are done by the Ubuntu Security Team.
B. Bugs which represent severe regressions from the previous release of
Ubuntu. This includes packages which are totally unusable, like being
uninstallable or crashing on startup.
C. Bugs which may, under realistic circumstances, directly cause a loss of
user data.
D. Bugs which do not fit under above categories, but (1) have an obviously
safe patch and (2) affect an application rather than critical
infrastructure packages (like X.org or the kernel).
E. For Long Term Support releases we regularly want to enable new hardware.
Such changes are appropriate provided that we can ensure to not affect
upgrades on existing hardware. For example, modaliases of newly introduced
drivers must not overlap with previously shipped drivers.
F. FTBFS (Fails To Build From Source) can also be considered. Please note
that in main the release process ensures that there are no binaries which
are not built from a current source. Usually those bugs should only be
SRUed in conjunction with another bug fix.
For new upstream versions of packages which provide new features, but don't fix
critical bugs, a backport [2] should be requested instead.
If you find a bug below that would qualify as a Stable Release Update according
to any of the criteria outlined above, you can suggest it by replying to this
email mentioning the bug number and the criteria letter (as defined above):
* bug 12345 - ...
[....]
+1: A
* bug 67890 - ...
[....]
+1: D
Bugs listed below that will not be suggested in one week on Mon August 23
will be automatically declined.
=== List of bugs nominated last week: ===
* bug 611769 - eucalyptus (Ubuntu) - Undecided
Can't create volume from snapshot with different size
http://bugs.launchpad.net/bugs/611769
* bug 617032 - eucalyptus (Ubuntu) - Undecided
euca-describe-volumes does not show volume size when vol is created from snap
http://bugs.launchpad.net/bugs/617032
* bug 617127 - eucalyptus (Ubuntu) - Undecided
CacheConcurrencyStrategy should be READ_WRITE and not TRANSACTIONAL
http://bugs.launchpad.net/bugs/617127
* bug 584497 - eucalyptus (Ubuntu) - Medium
The EC2 endpoint should be HTTPS by default
http://bugs.launchpad.net/bugs/584497
* bug 610259 - eucalyptus (Ubuntu) - Medium
inconsistent output euca_conf and euca-describe-availability-zones
http://bugs.launchpad.net/bugs/610259
* bug 613832 - eucalyptus (Ubuntu) - Medium
Cannot mark address as allocating[unallocated.false->allocated.true] when it is assigned.true:
http://bugs.launchpad.net/bugs/613832
* bug 615529 - eucalyptus (Ubuntu) - Medium
eucalyptus instance reboot fails: Guest moved used index from 0 to 2639
http://bugs.launchpad.net/bugs/615529
* bug 566792 - eucalyptus (Ubuntu) - High
metadata service returns empty data with 200 OK
http://bugs.launchpad.net/bugs/566792
* bug 600687 - eucalyptus (Ubuntu) - High
[maverick] Regression: nodes.list is ignored by CC
http://bugs.launchpad.net/bugs/600687
* bug 613549 - libvirt (Ubuntu) - Low
does not support cloning vm storage on lvm backend
http://bugs.launchpad.net/bugs/613549
* bug 591943 - libvirt (Ubuntu) - Medium
improperly mapped source privileged ports may allow for obtaining privileged resources on the host
http://bugs.launchpad.net/bugs/591943
* bug 610103 - migrationtools (Ubuntu) - Medium
package suggests editing an installed non-conffile for normal operation
http://bugs.launchpad.net/bugs/610103
* bug 574704 - munin (Ubuntu) - Medium
munin-node after update to Lucid still in /etc/rc*.d, invoked twice
http://bugs.launchpad.net/bugs/574704
* bug 616404 - munin (Ubuntu) - Medium
package munin-node 1.4.4-1ubuntu1 failed to install/upgrade: subproces installed post-installation script gaf een foutwaarde 1 terug
http://bugs.launchpad.net/bugs/616404
* bug 617461 - mysql-5.1 (Ubuntu) - Undecided
mysql-testsuite: testsuite fails due to unexpected installation layout
http://bugs.launchpad.net/bugs/617461
* bug 617463 - mysql-5.1 (Ubuntu) - Undecided
mysql fails to load innodb plugin due to apparmor rejection.
http://bugs.launchpad.net/bugs/617463
* bug 598476 - mysql-5.1 (Ubuntu) - Low
MySQL server fails to load on boot
http://bugs.launchpad.net/bugs/598476
* bug 564920 - php5 (Ubuntu) - Low
PHP5 under Apache2 on 64 bit system is not completely 64 bit
http://bugs.launchpad.net/bugs/564920
* bug 610371 - qemu-kvm (Ubuntu) - Low
qemu-kvm is hard to debug (ddebs are stripped)
http://bugs.launchpad.net/bugs/610371
* bug 595438 - qemu-kvm (Ubuntu) - Medium
KVM segmentation fault, using SCSI+writeback and linux 2.4 guest
http://bugs.launchpad.net/bugs/595438
* bug 574554 - tgt (Ubuntu) - Medium
tgtd needs init script or upstart job
http://bugs.launchpad.net/bugs/574554
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
08-23-2010, 06:07 PM
Weekly suggestions of bugs for Stable Release Updates.
Hi
We'd like to get your suggestions on the bugs listed below that may be
considered for backports to the stable releases. The bugs must meet
meet the SRU criteria.
= SRU criteria =
As outlined in the Stable Release Updates Policy [1], Stable Release
Updates will only be issued in order to fix *high-impact*
bugs.
A. Bugs which may, under realistic circumstances, directly cause a security
vulnerability. These are done by the Ubuntu Security Team.
B. Bugs which represent severe regressions from the previous release of
Ubuntu. This includes packages which are totally unusable, like being
uninstallable or crashing on startup.
C. Bugs which may, under realistic circumstances, directly cause a loss of
user data.
D. Bugs which do not fit under above categories, but (1) have an obviously
safe patch and (2) affect an application rather than critical
infrastructure packages (like X.org or the kernel).
E. For Long Term Support releases we regularly want to enable new hardware.
Such changes are appropriate provided that we can ensure to not affect
upgrades on existing hardware. For example, modaliases of newly introduced
drivers must not overlap with previously shipped drivers.
F. FTBFS (Fails To Build From Source) can also be considered. Please note
that in main the release process ensures that there are no binaries which
are not built from a current source. Usually those bugs should only be
SRUed in conjunction with another bug fix.
For new upstream versions of packages which provide new features, but don't fix
critical bugs, a backport [2] should be requested instead.
If you find a bug below that would qualify as a Stable Release Update according
to any of the criteria outlined above, you can suggest it by replying to this
email mentioning the bug number and the criteria letter (as defined above):
* bug 12345 - ...
[....]
+1: A
* bug 67890 - ...
[....]
+1: D
Bugs listed below that will not be suggested in one week on Mon August 30
will be automatically declined.
=== List of bugs nominated last week: ===
* bug 591100 - autofs5 - Undecided
autofs5 eats the cpu if you have large groups
https://bugs.launchpad.net/bugs/591100
* bug 576949 - mysql-dfsg-5.1 - Undecided
[lucid] LOAD DATA INFILE fails in replication, simple patch available in 5.1.43
https://bugs.launchpad.net/bugs/576949
* bug 564920 - php5 - Undecided
PHP5 under Apache2 on 64 bit system is not completely 64 bit
https://bugs.launchpad.net/bugs/564920
* bug 602539 - qemu-kvm - Undecided
qemu-system-x86_64 segfaults if using -no-kvm with -m 4096 or greater
https://bugs.launchpad.net/bugs/602539
* bug 563175 - eucalyptus (Ubuntu) - Medium
eucalyptus should hold on to console logs as after instance terminated
http://bugs.launchpad.net/bugs/563175
* bug 610479 - eucalyptus (Ubuntu) - High
Instance fails to start
http://bugs.launchpad.net/bugs/610479
* bug 619970 - eucalyptus (Ubuntu) - High
suddenly no instance starts anymore - bad date formatting?
http://bugs.launchpad.net/bugs/619970
* bug 622010 - mysql-5.1 (Ubuntu) - High
Error in AppArmor rule for mysqld
http://bugs.launchpad.net/bugs/622010
* bug 269298 - mysql-dfsg-5.1 (Ubuntu) - Low
/etc/init.d/mysql run without privileges reports wrong status.
http://bugs.launchpad.net/bugs/269298
* bug 599790 - mysql-dfsg-5.1 (Ubuntu) - Low
Error message flood when enabling events in Ubuntu
http://bugs.launchpad.net/bugs/599790
* bug 576949 - mysql-dfsg-5.1 (Ubuntu) - Medium
[lucid] LOAD DATA INFILE fails in replication, simple patch available in 5.1.43
http://bugs.launchpad.net/bugs/576949
* bug 471468 - nagios3 (Ubuntu) - Wishlist
should recognize that exit code 126 means plugin is not executable
http://bugs.launchpad.net/bugs/471468
* bug 615810 - nagios3 (Ubuntu) - Low
nagios3-common and nagios3-core : grep: /etc/nagios3/cgi.cfg: No such file or directory
http://bugs.launchpad.net/bugs/615810
* bug 591286 - php5 (Ubuntu) - Low
PHP Deprecated: Comments starting with '#' are deprecated in[...] on line 1 in Unknown on line 0
http://bugs.launchpad.net/bugs/591286
* bug 607646 - php5 (Ubuntu) - Medium
Segmentation fault in PHP5 with pgsql module
http://bugs.launchpad.net/bugs/607646
* bug 534155 - qemu-kvm (Ubuntu) - Wishlist
qemu-debootstrap uses qemu for lpia hosts and targets when not required
http://bugs.launchpad.net/bugs/534155
* bug 414010 - rrdtool (Ubuntu) - Low
rrdtool .pot template is missing, existing .po files not imported
http://bugs.launchpad.net/bugs/414010
* bug 276472 - samba (Ubuntu) - Medium
cp -p on CIFS mount does not preserve permissions and returns a permission denied error
http://bugs.launchpad.net/bugs/276472
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
08-30-2010, 02:12 PM
Nigel Jones
Weekly suggestions of bugs for Stable Release Updates.
Per our discussion I'd like to suggest
lucid - seabios
Bug 589063
Under D, fixed upstream and in maverick already.
(It could potentially be B, as I had a friend test with older QEMU/KVM
versions that shipped prior to seabios (not under Ubuntu though) who
told me that the bug didn't exist then).
-- Nigel Jones
On Tue, Aug 24, 2010 at 6:07 AM, <zulcss@gmail.com> wrote:
> Hi
>
> We'd like to get your suggestions on the bugs listed below that may be
> considered for backports to the stable releases. The bugs must meet
> meet the SRU criteria.
>
> = SRU criteria =
>
> As outlined in the Stable Release Updates Policy [1], Stable Release
> Updates will only be issued in order to fix *high-impact*
> bugs.
>
> [1]: https://wiki.ubuntu.com/StableReleaseUpdates#When
>
> Examples of such bugs include:
>
> A. Bugs which may, under realistic circumstances, directly cause a security
> * vulnerability. These are done by the Ubuntu Security Team.
> B. Bugs which represent severe regressions from the previous release of
> * Ubuntu. This includes packages which are totally unusable, like being
> * uninstallable or crashing on startup.
> C. Bugs which may, under realistic circumstances, directly cause a loss of
> * user data.
> D. Bugs which do not fit under above categories, but (1) have an obviously
> * safe patch and (2) affect an application rather than critical
> * infrastructure packages (like X.org or the kernel).
> E. For Long Term Support releases we regularly want to enable new hardware.
> * Such changes are appropriate provided that we can ensure to not affect
> * upgrades on existing hardware. For example, modaliases of newly introduced
> * drivers must not overlap with previously shipped drivers.
> F. FTBFS (Fails To Build From Source) can also be considered. Please note
> * that in main the release process ensures that there are no binaries which
> * are not built from a current source. Usually those bugs should only be
> * SRUed in conjunction with another bug fix.
>
> For new upstream versions of packages which provide new features, but don't fix
> critical bugs, a backport [2] should be requested instead.
>
> [2]: https://help.ubuntu.com/community/UbuntuBackports
>
> = How-to suggest a bug for a SRU =
>
> If you find a bug below that would qualify as a Stable Release Update according
> to any of the criteria outlined above, you can suggest it by replying to this
> email mentioning the bug number and the criteria letter (as defined above):
>
> ** bug 12345 - ...
> *[....]
> *+1: A
>
> ** bug 67890 - ...
> *[....]
> *+1: D
>
> Bugs listed below that will not be suggested in one week on Mon August 30
> will be automatically declined.
> === List of bugs nominated last week: ===
>
> == lucid ==
> * bug 595116 - apache2 - Undecided
> ssl "error reading the headers"
> https://bugs.launchpad.net/bugs/595116
>
> * bug 591100 - autofs5 - Undecided
> autofs5 eats the cpu if you have large groups
> https://bugs.launchpad.net/bugs/591100
>
> * bug 576949 - mysql-dfsg-5.1 - Undecided
> [lucid] LOAD DATA INFILE fails in replication, simple patch available in 5.1.43
> https://bugs.launchpad.net/bugs/576949
>
> * bug 564920 - php5 - Undecided
> PHP5 under Apache2 on 64 bit system is not completely 64 bit
> https://bugs.launchpad.net/bugs/564920
>
> * bug 602539 - qemu-kvm - Undecided
> qemu-system-x86_64 segfaults if using -no-kvm with -m 4096 or greater
> https://bugs.launchpad.net/bugs/602539
>
> == karmic ==
> == jaunty ==
> == hardy ==
> == dapper ==
>
> === List of bugs fixed in maverick: ===
>
> * bug 583698 - apache2 (Ubuntu) - Low
> [SRU] If /usr/sbin/apache2 is set -x, upgrades fail
> http://bugs.launchpad.net/bugs/583698
>
> * bug 603285 - dovecot (Ubuntu) - Wishlist
> Please convert init script to upstart.
> http://bugs.launchpad.net/bugs/603285
>
> * bug 571926 - dovecot (Ubuntu) - Medium
> dovecot-postfix initial setting in postfix-main.cf wrong
> http://bugs.launchpad.net/bugs/571926
>
> * bug 606243 - eucalyptus (Ubuntu) - Low
> euca-describe-availability-zones verbose corrupted (ENT config only)
> http://bugs.launchpad.net/bugs/606243
>
> * bug 615468 - eucalyptus (Ubuntu) - Low
> Invalid quantifier javascript error when creating account
> http://bugs.launchpad.net/bugs/615468
>
> * bug 563175 - eucalyptus (Ubuntu) - Medium
> eucalyptus should hold on to console logs as after instance terminated
> http://bugs.launchpad.net/bugs/563175
>
> * bug 610479 - eucalyptus (Ubuntu) - High
> Instance fails to start
> http://bugs.launchpad.net/bugs/610479
>
> * bug 619970 - eucalyptus (Ubuntu) - High
> suddenly no instance starts anymore - bad date formatting?
> http://bugs.launchpad.net/bugs/619970
>
> * bug 622682 - libvirt (Ubuntu) - Wishlist
> [FFe] Cherry-pick UML enhancements from upstream
> http://bugs.launchpad.net/bugs/622682
>
> * bug 545795 - libvirt (Ubuntu) - Medium
> apparmor driver blocks access to some hostdev and pcidev devices
> http://bugs.launchpad.net/bugs/545795
>
> * bug 605021 - mysql-5.1 (Ubuntu) - Low
> mismatch in mysql_config output and libmysqld cflags
> http://bugs.launchpad.net/bugs/605021
>
> * bug 619172 - mysql-5.1 (Ubuntu) - Low
> AppArmor Denied
> http://bugs.launchpad.net/bugs/619172
>
> * bug 622010 - mysql-5.1 (Ubuntu) - High
> Error in AppArmor rule for mysqld
> http://bugs.launchpad.net/bugs/622010
>
> * bug 269298 - mysql-dfsg-5.1 (Ubuntu) - Low
> /etc/init.d/mysql run without privileges reports wrong status.
> http://bugs.launchpad.net/bugs/269298
>
> * bug 599790 - mysql-dfsg-5.1 (Ubuntu) - Low
> Error message flood when enabling events in Ubuntu
> http://bugs.launchpad.net/bugs/599790
>
> * bug 576949 - mysql-dfsg-5.1 (Ubuntu) - Medium
> [lucid] LOAD DATA INFILE fails in replication, simple patch available in 5.1.43
> http://bugs.launchpad.net/bugs/576949
>
> * bug 471468 - nagios3 (Ubuntu) - Wishlist
> should recognize that exit code 126 means plugin is not executable
> http://bugs.launchpad.net/bugs/471468
>
> * bug 615810 - nagios3 (Ubuntu) - Low
> nagios3-common and nagios3-core : *grep: /etc/nagios3/cgi.cfg: No such file or directory
> http://bugs.launchpad.net/bugs/615810
>
> * bug 518653 - opie (Ubuntu) - Wishlist
> libopie exports conflicting symbols
> http://bugs.launchpad.net/bugs/518653
>
> * bug 397721 - php5 (Ubuntu) - Wishlist
> [needs-packaging] php-fpm
> http://bugs.launchpad.net/bugs/397721
>
> * bug 610630 - php5 (Ubuntu) - Wishlist
> Please add Kolab php patches to Ubuntu php5
> http://bugs.launchpad.net/bugs/610630
>
> * bug 591286 - php5 (Ubuntu) - Low
> PHP Deprecated: *Comments starting with '#' are deprecated in[...] on line 1 in Unknown on line 0
> http://bugs.launchpad.net/bugs/591286
>
> * bug 607646 - php5 (Ubuntu) - Medium
> Segmentation fault in PHP5 with pgsql module
> http://bugs.launchpad.net/bugs/607646
>
> * bug 534155 - qemu-kvm (Ubuntu) - Wishlist
> qemu-debootstrap uses qemu for lpia hosts and targets when not required
> http://bugs.launchpad.net/bugs/534155
>
> * bug 414010 - rrdtool (Ubuntu) - Low
> rrdtool .pot template is missing, existing .po files not imported
> http://bugs.launchpad.net/bugs/414010
>
> * bug 276472 - samba (Ubuntu) - Medium
> cp -p on CIFS mount does not preserve permissions and returns a permission denied error
> http://bugs.launchpad.net/bugs/276472
>
> * bug 620428 - unixodbc (Ubuntu) - Undecided
> unixodbc-dev: 64bit typedefs don't work
> http://bugs.launchpad.net/bugs/620428
>
>
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam
>
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
Weekly suggestions of bugs for Stable Release Updates.
