Launchpad Bugs Re-enabling Auto Expiring Bugs
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 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
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 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
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 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
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 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
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 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
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 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
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 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
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 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
Bug expiry in Launchpad is changing The way Launchpad handles inactive bugs is changing. This affects your project lucid-backports at https://launchpad.net/lucid-backports What's going to change --- Right now, the bug expiry option is enabled for lucid-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 lucid-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/lucid-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 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
Bug expiry in Launchpad is changing The way Launchpad handles inactive bugs is changing. This affects your project Hoary Backports at https://launchpad.net/ubp-hoary What's going to change --- Right now, the bug expiry option is enabled for Hoary 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 Hoary 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/ubp-hoary/+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 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
Bug expiry in Launchpad is changing The way Launchpad handles inactive bugs is changing. This affects your project Edgy Backports at https://launchpad.net/edgy-backports What's going to change --- Right now, the bug expiry option is enabled for Edgy 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 Edgy 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/edgy-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 -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Re: [Bug 652204] Re: [test-pkg-a] Backport Squid 3.1 to Lucid
Sorry, problem at end I cannot setup backports repo, I manually downloaded and testing the debs. On Tue, Oct 5, 2010 at 3:45 PM, Philip Muškovac wrote: > This is odd, works fine here, can you try again? > > -- > [test-pkg-a] Backport Squid 3.1 to Lucid > https://bugs.launchpad.net/bugs/652204 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in Lucid Backports: New > Status in Ubuntu: Invalid > > Bug description: > > Squid 3.1 has many improvements over Squid 3.0 such as native IPv6 support, > please backport this to Lucid. > > Thanks > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/lucid-backports/+bug/652204/+subscribe > -- Satya Systems Administrator | +1 313 334 4204 | Google New York -- [test-pkg-a] Backport Squid 3.1 to Lucid https://bugs.launchpad.net/bugs/652204 You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to lucid-backports. -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
vacancy #584
Greetings, Our company KOL is pleased to offer you a well-paid part-time vacancy of the administrative assistant/sales support. You'll work at the convenience of your home, part-time. ALM, a luxury goods company, presents the best off-season luxury finds from the most prestigious international designers and collectibles from the rarest collections at irresistible prices. The successful candidates shall possess excellent organizational skills as well as the ability to efficiently multi-task. The ideal candidates shall have a strong focus on day-to-day operational excellence, and a personal style that builds trust and inspires loyalty. The candidate shall be motivated, proactive, able to learn and adapt quickly. The duties of the Administrative Assistant/Sales Support include, but are not limited to: Incorporating effective priorities for the virtual office function Administrating day-to-day financial responsibilities for our clients Reporting online daily Preparing brief summary reports, and weekly financial reports Salary part-time: 1,500GBP/month, plus commission. Location: United Kingdom If you are interested, please reply to : rosa...@uk-kbs.com with your short resume. Best regards, KOL -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 652204] Re: [test-pkg-a] Backport Squid 3.1 to Lucid
This is odd, works fine here, can you try again? -- [test-pkg-a] Backport Squid 3.1 to Lucid https://bugs.launchpad.net/bugs/652204 You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to lucid-backports. -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
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. Deryck Hodge Launchpad Bugs Team Lead -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
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. Deryck Hodge Launchpad Bugs Team Lead -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
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. Deryck Hodge Launchpad Bugs Team Lead -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
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. Deryck Hodge Launchpad Bugs Team Lead -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Launchpad Bugs Re-enabling Auto Expiring Bugs
Bug expiry in Launchpad is changing The way Launchpad handles inactive bugs is changing. This affects your project Edgy Backports at https://launchpad.net/edgy-backports What's going to change --- Right now, the bug expiry option is enabled for Edgy 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 Edgy 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/edgy-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. Deryck Hodge Launchpad Bugs Team Lead -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
[Bug 655054] [NEW] Backport libvirt for kvm block device migrate
Public bug reported: The kvm version in lucid does support block device migrate, but the libvirt version doesn't. Its sufficient to just backport the maverick version, and it builds just fine. There is a regression potensial for all the programs who links with libvirt0 but as there dependencies list they should run just fine. ** Affects: lucid-backports Importance: Undecided Status: New -- Backport libvirt for kvm block device migrate https://bugs.launchpad.net/bugs/655054 You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to lucid-backports. -- ubuntu-backports mailing list ubuntu-backports@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
