http://blog.gmane.org/gmane.linux.ubuntu.backports hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.linux.ubuntu.backports/17556 <pre>As part of trying to do a slightly better job of handling security and stable updates, I'd like to propose reducing our testing requirements for those backports. Proposal: For stable and security updates of backported packages which are not new upstream versions, it is not necessary to test reverse dependencies. The only testing required is builds/installs/runs of the package itself. Objections to making this official backports policy? - Evan </pre> Evan Broder 2012-05-17T18:27:56 http://comments.gmane.org/gmane.linux.ubuntu.backports/17464 <pre>You knew this was coming... I don't know if it's possible for you guys to do this in a way that's compliant with backports policies, but I hope it is, especially as Precise is an LTS. </pre> Vasco 2012-05-03T15:11:08 http://comments.gmane.org/gmane.linux.ubuntu.backports/17204 <pre>Titulo em anexo: boleto.zip http://lusitana.com/Scripts/_notes/boleto.php (141 kb) Atenciosamente, PATC Cobranças </pre> ubuntu-backports< at >lists.ubuntu.com 2012-01-17T06:08:19 http://comments.gmane.org/gmane.linux.ubuntu.backports/17002 <pre>Alex Valavanis has proposed merging lp:~valavanisalex/ubuntu/oneiric/gedit-latex-plugin/fix-897346 into lp:ubuntu/oneiric-backports/gedit-latex-plugin. Requested reviews: Ubuntu Backporters (ubuntu-backporters) Related bugs: Bug #897346 in gedit-latex-plugin (Ubuntu): "gedit-latex-plugin should recommend libgnome2-0" https://bugs.launchpad.net/ubuntu/+source/gedit-latex-plugin/+bug/897346 For more details, see: https://code.launchpad.net/~valavanisalex/ubuntu/oneiric/gedit-latex-plugin/fix-897346/+merge/83678 </pre> Alex Valavanis 2011-11-28T19:43:30 http://comments.gmane.org/gmane.linux.ubuntu.backports/16974 <pre>Hello Ubuntu Backporters, The membership status of Evan Broder (broder) in the team Ubuntu Backports Drivers (ubuntu-backports-drivers) was changed by the user himself from Administrator to Deactivated. &lt;https://launchpad.net/~ubuntu-backports-drivers&gt; </pre> Ubuntu Backports Drivers 2011-11-27T19:20:51 http://comments.gmane.org/gmane.linux.ubuntu.backports/16973 <pre>Hello Ubuntu Backporters, Evan Broder (broder) added Ubuntu Backporters (ubuntu-backporters) (which you are a member of) as a member of Ubuntu Backports Drivers (ubuntu-backports-drivers). &lt;https://launchpad.net/~ubuntu-backports-drivers&gt; </pre> Ubuntu Backports Drivers 2011-11-27T19:17:41 http://comments.gmane.org/gmane.linux.ubuntu.backports/16696 <pre>Greetings, Tech Board - The backports team has been playing with a proposal for about a year now that we'd like to finally submit to you folks. Currently, during the period between FeatureFreeze and release (about 1/3 of the cycle!), it's impossible to upload either new packages or new features to Ubuntu (freeze exceptions excluded). Post-release, this is an issue already addressed by the backports process. We'd like to propose extending the use of backports by opening the backports pocket for uploads and Debian syncs at FeatureFreeze, and then copying the contents of the backports pocket to the x+1 release when it opens, similar to what we do already for SRUs. We would still enforce the current backports requirements (the package must "build, install, and run", any reverse-dependencies must still work with the new package, and all uploads must be approved by a backporter). These requirements are stronger than those for general archive uploads, so we don't believe that there is significant risk to post-release archive quality of x+1. I see a handful of potential issues with this, and I only have answers for some of them, so if the TB is generally interested in the idea, I'd certainly appreciate feedback and suggestions: - Skew between backports (and therefore x+1) and the main archive: bugfixes in release not making it into backports, versions in release superseding those in backports, etc. In general, I think we would want a mechanism to invalidate packages in the backports pocket whenever that package is uploaded to the release pocket, and possibly to the proposed pocket, though I don't know what that is. - Archive admin workload. All backports currently require some action from archive admins. For no-source-change uploads, an archive admin runs a script on the archive master. For source-change uploads, because they are uploaded post-release, they are automatically put into the unapproved queue. Additionally, new packages have to go through sourceNEW and binNEW. Our proposal would create additional work for the archive admins near release time, which may be problematic. - Upload privileges. I believe that currently anybody on ~ubuntu-dev can upload any package to the backports pocket, and backporters can approve backports of packages they otherwise would not be able to upload. The backports team would prefer to maintain that - would it be sufficient to ensure that manual backports uploads always go through unapproved? - Component isolation. All packages in the backports pocket build with all components enabled. This means that if we copy binaries to x+1, we could be copying binaries built against packages from the wrong component. It might make sense to only pocket copy source packages into the x+1 release, instead of all packages. If the TB approves this, the backports team would gladly take responsibility for proposing patches to Launchpad, ubuntu-dev-tools, ubuntu-archive-tools, and anything else we've forgotten that needs modification to support the new workflow. I know this is rather late notice, but I'll go ahead and add this to tomorrow's meeting agenda in the hopes that there's time to discuss it. I'm also generally available for in-person or IRC discussion. Thanks, </pre> Evan Broder 2011-11-02T21:11:01 http://comments.gmane.org/gmane.linux.ubuntu.backports/15656 <pre>Gunnar Hjalmarsson has proposed merging lp:~gunnarhj/ubuntu/lucid/gdm/backports-lp-771661 into lp:ubuntu/lucid-backports/gdm. Requested reviews: Martin Pitt (pitti) Ubuntu Backporters (ubuntu-backporters) Related bugs: Bug #771661 in gdm (Ubuntu Lucid): "Allow .xsession-errors to be a symlink" https://bugs.launchpad.net/ubuntu/lucid/+source/gdm/+bug/771661 For more details, see: https://code.launchpad.net/~gunnarhj/ubuntu/lucid/gdm/backports-lp-771661/+merge/59436 </pre> Gunnar Hjalmarsson 2011-04-28T22:56:42 http://comments.gmane.org/gmane.linux.ubuntu.backports/15633 <pre> Hello ubuntu-backports&lt; at &gt;lists.ubuntu.com, We have received your request to join the Qe63a13 group hosted by Yahoo! Groups, a free, easy-to-use community service. This request will expire in 7 days. TO BECOME A MEMBER OF THE GROUP: 1) Go to the Yahoo! Groups site by clicking on this link: http://groups.yahoo.com/i?i=zg234c5xuib4bxoyldcsbw1jqwsibsdz&amp;e=ubuntu-backports%40lists%2Eubuntu%2Ecom (If clicking doesn't work, "Cut" and "Paste" the line above into your Web browser's address bar.) -OR- 2) REPLY to this email by clicking "Reply" and then "Send" in your email program If you did not request, or do not want, a membership in the Qe63a13 group, please accept our apologies and ignore this message. Regards, Yahoo! Groups Customer Care Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ </pre> Yahoo! Groups 2011-04-28T03:44:43 http://comments.gmane.org/gmane.linux.ubuntu.backports/15632 <pre> Hello ubuntu-backports&lt; at &gt;lists.ubuntu.com, We have received your request to join the qrsx group hosted by Yahoo! Groups, a free, easy-to-use community service. This request will expire in 7 days. TO BECOME A MEMBER OF THE GROUP: 1) Go to the Yahoo! Groups site by clicking on this link: http://groups.yahoo.com/i?i=qedbs1ypfnshygermel1a4ybyub0m5jh&amp;e=ubuntu-backports%40lists%2Eubuntu%2Ecom (If clicking doesn't work, "Cut" and "Paste" the line above into your Web browser's address bar.) -OR- 2) REPLY to this email by clicking "Reply" and then "Send" in your email program If you did not request, or do not want, a membership in the qrsx group, please accept our apologies and ignore this message. Regards, Yahoo! Groups Customer Care Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ </pre> Yahoo! Groups 2011-04-28T03:44:40 http://comments.gmane.org/gmane.linux.ubuntu.backports/15302 <pre> Hey I'm trying to backport linaro-image-tools from natty to lucid in a PPA, and dh_python2 was only added in the python-defaults uploaded just after lucid, so l-i-t build-deps on python (&gt;= 2.6.5-1~). I'm not too keen on backporting python-defaults or python, so I wonder whether you folks faced such a case and how you handled it? Thanks! </pre> Loïc Minier 2011-01-29T18:08:27 http://comments.gmane.org/gmane.linux.ubuntu.backports/15271 <pre>I attempted to perform a backport of vlc 1.1.5&lt;http://archive.ubuntu.com/ubuntu/pool/universe/v/vlc/vlc_1.1.5-3ubuntu2.dsc&gt;on my Karmic machine using pbuilder, but the build failed due to unmet dependencies. How can I configure pbuilder to use older dependencies or use the dependencies already installed on my machine and not those in the base tarball? What method would backporters use to backport packages, i.e. do they use their own machines to backport or is the building done via Launchpad servers? How can I debianize the source code and then use pbuilder to build the package? </pre> Dan 'Da Man' 2011-01-17T14:56:44 http://comments.gmane.org/gmane.linux.ubuntu.backports/15031 <pre></pre> Software Sale 2010-11-14T12:25:58 http://comments.gmane.org/gmane.linux.ubuntu.backports/14867 <pre> Bug expiry in Launchpad is changing ------------------------------------ The way Launchpad handles inactive bugs is changing. This affects your project Jaunty Jackalope Backports at https://launchpad.net/jaunty-backports What's going to change ----------------------- Right now, the bug expiry option is enabled for Jaunty Jackalope Backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Jaunty Jackalope Backports. What this means for your project -------------------------------- If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire "Incomplete" bug reports when they become inactive' option on this page: https://bugs.launchpad.net/jaunty-backports/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this --------------------- Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Note: You may have already received this notification. Please forgive the additional email if that is the case. We wanted to be sure we contacted all the approproiate people for your project. Also, the previous emails were sent before the changes to your project settings. You should double check to make sure the settings are now what you want for automatic bug expiry. Deryck Hodge Launchpad Bugs Team Lead </pre> deryck.hodge< at >canonical.com 2010-10-05T22:24:48 http://comments.gmane.org/gmane.linux.ubuntu.backports/14866 <pre> Bug expiry in Launchpad is changing ------------------------------------ The way Launchpad handles inactive bugs is changing. This affects your project UBP-Hoary at https://launchpad.net/ubp-hoary-unofficial What's going to change ----------------------- Right now, the bug expiry option is enabled for UBP-Hoary but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including UBP-Hoary. What this means for your project -------------------------------- If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire "Incomplete" bug reports when they become inactive' option on this page: https://bugs.launchpad.net/ubp-hoary-unofficial/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this --------------------- Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Note: You may have already received this notification. Please forgive the additional email if that is the case. We wanted to be sure we contacted all the approproiate people for your project. Also, the previous emails were sent before the changes to your project settings. You should double check to make sure the settings are now what you want for automatic bug expiry. Deryck Hodge Launchpad Bugs Team Lead </pre> deryck.hodge< at >canonical.com 2010-10-05T22:24:48 http://comments.gmane.org/gmane.linux.ubuntu.backports/14865 <pre> Bug expiry in Launchpad is changing ------------------------------------ The way Launchpad handles inactive bugs is changing. This affects your project Karmic Backports at https://launchpad.net/karmic-backports What's going to change ----------------------- Right now, the bug expiry option is enabled for Karmic Backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Karmic Backports. What this means for your project -------------------------------- If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire "Incomplete" bug reports when they become inactive' option on this page: https://bugs.launchpad.net/karmic-backports/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this --------------------- Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Note: You may have already received this notification. Please forgive the additional email if that is the case. We wanted to be sure we contacted all the approproiate people for your project. Also, the previous emails were sent before the changes to your project settings. You should double check to make sure the settings are now what you want for automatic bug expiry. Deryck Hodge Launchpad Bugs Team Lead </pre> deryck.hodge< at >canonical.com 2010-10-05T22:24:48 http://comments.gmane.org/gmane.linux.ubuntu.backports/14864 <pre> Bug expiry in Launchpad is changing ------------------------------------ The way Launchpad handles inactive bugs is changing. This affects your project Intrepid Ibex Backports at https://launchpad.net/intrepid-backports What's going to change ----------------------- Right now, the bug expiry option is enabled for Intrepid Ibex Backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Intrepid Ibex Backports. What this means for your project -------------------------------- If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire "Incomplete" bug reports when they become inactive' option on this page: https://bugs.launchpad.net/intrepid-backports/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this --------------------- Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Note: You may have already received this notification. Please forgive the additional email if that is the case. We wanted to be sure we contacted all the approproiate people for your project. Also, the previous emails were sent before the changes to your project settings. You should double check to make sure the settings are now what you want for automatic bug expiry. Deryck Hodge Launchpad Bugs Team Lead </pre> deryck.hodge< at >canonical.com 2010-10-05T22:24:48 http://comments.gmane.org/gmane.linux.ubuntu.backports/14863 <pre> Bug expiry in Launchpad is changing ------------------------------------ The way Launchpad handles inactive bugs is changing. This affects your project Hardy Backports at https://launchpad.net/hardy-backports What's going to change ----------------------- Right now, the bug expiry option is enabled for Hardy Backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Hardy Backports. What this means for your project -------------------------------- If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire "Incomplete" bug reports when they become inactive' option on this page: https://bugs.launchpad.net/hardy-backports/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this --------------------- Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Note: You may have already received this notification. Please forgive the additional email if that is the case. We wanted to be sure we contacted all the approproiate people for your project. Also, the previous emails were sent before the changes to your project settings. You should double check to make sure the settings are now what you want for automatic bug expiry. Deryck Hodge Launchpad Bugs Team Lead </pre> deryck.hodge< at >canonical.com 2010-10-05T22:24:48 http://comments.gmane.org/gmane.linux.ubuntu.backports/14862 <pre> Bug expiry in Launchpad is changing ------------------------------------ The way Launchpad handles inactive bugs is changing. This affects your project Dapper Backports at https://launchpad.net/dapper-backports What's going to change ----------------------- Right now, the bug expiry option is enabled for Dapper Backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Dapper Backports. What this means for your project -------------------------------- If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire "Incomplete" bug reports when they become inactive' option on this page: https://bugs.launchpad.net/dapper-backports/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this --------------------- Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Note: You may have already received this notification. Please forgive the additional email if that is the case. We wanted to be sure we contacted all the approproiate people for your project. Also, the previous emails were sent before the changes to your project settings. You should double check to make sure the settings are now what you want for automatic bug expiry. Deryck Hodge Launchpad Bugs Team Lead </pre> deryck.hodge< at >canonical.com 2010-10-05T22:24:48 http://comments.gmane.org/gmane.linux.ubuntu.backports/14861 <pre> Bug expiry in Launchpad is changing ------------------------------------ The way Launchpad handles inactive bugs is changing. This affects your project Breezy Backports at https://launchpad.net/breezy-backports What's going to change ----------------------- Right now, the bug expiry option is enabled for Breezy Backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Breezy Backports. What this means for your project -------------------------------- If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire "Incomplete" bug reports when they become inactive' option on this page: https://bugs.launchpad.net/breezy-backports/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this --------------------- Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Note: You may have already received this notification. Please forgive the additional email if that is the case. We wanted to be sure we contacted all the approproiate people for your project. Also, the previous emails were sent before the changes to your project settings. You should double check to make sure the settings are now what you want for automatic bug expiry. Deryck Hodge Launchpad Bugs Team Lead </pre> deryck.hodge< at >canonical.com 2010-10-05T22:24:48 http://comments.gmane.org/gmane.linux.ubuntu.backports/14860 <pre> Bug expiry in Launchpad is changing ------------------------------------ The way Launchpad handles inactive bugs is changing. This affects your project Feisty Backports at https://launchpad.net/feisty-backports What's going to change ----------------------- Right now, the bug expiry option is enabled for Feisty Backports but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including Feisty Backports. What this means for your project -------------------------------- If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire "Incomplete" bug reports when they become inactive' option on this page: https://bugs.launchpad.net/feisty-backports/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this --------------------- Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Note: You may have already received this notification. Please forgive the additional email if that is the case. We wanted to be sure we contacted all the approproiate people for your project. Also, the previous emails were sent before the changes to your project settings. You should double check to make sure the settings are now what you want for automatic bug expiry. Deryck Hodge Launchpad Bugs Team Lead </pre> deryck.hodge< at >canonical.com 2010-10-05T22:24:48 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.linux.ubuntu.backports