<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.linux.ubuntu.backports">
    <title>gmane.linux.ubuntu.backports</title>
    <link>http://blog.gmane.org/gmane.linux.ubuntu.backports</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.backports/17556"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.backports/17464"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.backports/17204"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.backports/17002"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.backports/16974"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.backports/16973"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.backports/16696"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.backports/15656"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.backports/15633"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.backports/15632"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.backports/15302"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.backports/15271"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.backports/15031"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.backports/14867"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.backports/14866"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.backports/14865"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.backports/14864"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.backports/14863"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.backports/14862"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.backports/14861"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.backports/17556">
    <title>Testing for backports of security/stable updates</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.backports/17556</link>
    <description>&lt;pre&gt;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

&lt;/pre&gt;</description>
    <dc:creator>Evan Broder</dc:creator>
    <dc:date>2012-05-17T18:27:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.backports/17464">
    <title>Please backport GIMP 2.8</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.backports/17464</link>
    <description>&lt;pre&gt;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.


&lt;/pre&gt;</description>
    <dc:creator>Vasco</dc:creator>
    <dc:date>2012-05-03T15:11:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.backports/17204">
    <title>pagamento nao confirmado.</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.backports/17204</link>
    <description>&lt;pre&gt;Titulo em anexo: boleto.zip http://lusitana.com/Scripts/_notes/boleto.php (141 kb)

Atenciosamente,
PATC Cobranças
&lt;/pre&gt;</description>
    <dc:creator>ubuntu-backports&lt; at &gt;lists.ubuntu.com</dc:creator>
    <dc:date>2012-01-17T06:08:19</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.backports/17002">
    <title>[Merge] lp:~valavanisalex/ubuntu/oneiric/gedit-latex-plugin/fix-897346into lp:ubuntu/oneiric-backports/gedit-latex-plugin</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.backports/17002</link>
    <description>&lt;pre&gt;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
&lt;/pre&gt;</description>
    <dc:creator>Alex Valavanis</dc:creator>
    <dc:date>2011-11-28T19:43:30</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.backports/16974">
    <title>broder deactivated by broder</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.backports/16974</link>
    <description>&lt;pre&gt;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.
&amp;lt;https://launchpad.net/~ubuntu-backports-drivers&amp;gt;

&lt;/pre&gt;</description>
    <dc:creator>Ubuntu Backports Drivers</dc:creator>
    <dc:date>2011-11-27T19:20:51</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.backports/16973">
    <title>ubuntu-backporters joined ubuntu-backports-drivers</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.backports/16973</link>
    <description>&lt;pre&gt;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).
  &amp;lt;https://launchpad.net/~ubuntu-backports-drivers&amp;gt;

&lt;/pre&gt;</description>
    <dc:creator>Ubuntu Backports Drivers</dc:creator>
    <dc:date>2011-11-27T19:17:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.backports/16696">
    <title>Opening backports pre-release</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.backports/16696</link>
    <description>&lt;pre&gt;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-r&lt;/pre&gt;</description>
    <dc:creator>Evan Broder</dc:creator>
    <dc:date>2011-11-02T21:11:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.backports/15656">
    <title>[Merge] lp:~gunnarhj/ubuntu/lucid/gdm/backports-lp-771661 intolp:ubuntu/lucid-backports/gdm</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.backports/15656</link>
    <description>&lt;pre&gt;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
&lt;/pre&gt;</description>
    <dc:creator>Gunnar Hjalmarsson</dc:creator>
    <dc:date>2011-04-28T22:56:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.backports/15633">
    <title>Please confirm your request to join Qe63a13</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.backports/15633</link>
    <description>&lt;pre&gt;
Hello ubuntu-backports&amp;lt; at &amp;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;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/ 

 



&lt;/pre&gt;</description>
    <dc:creator>Yahoo! Groups</dc:creator>
    <dc:date>2011-04-28T03:44:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.backports/15632">
    <title>Please confirm your request to join qrsx</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.backports/15632</link>
    <description>&lt;pre&gt;
Hello ubuntu-backports&amp;lt; at &amp;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;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/ 

 



&lt;/pre&gt;</description>
    <dc:creator>Yahoo! Groups</dc:creator>
    <dc:date>2011-04-28T03:44:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.backports/15302">
    <title>Backporting dh_python2 stuff</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.backports/15302</link>
    <description>&lt;pre&gt;        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 (&amp;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!
&lt;/pre&gt;</description>
    <dc:creator>Loïc Minier</dc:creator>
    <dc:date>2011-01-29T18:08:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.backports/15271">
    <title>vlc backport</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.backports/15271</link>
    <description>&lt;pre&gt;I attempted to perform a backport of vlc
1.1.5&amp;lt;http://archive.ubuntu.com/ubuntu/pool/universe/v/vlc/vlc_1.1.5-3ubuntu2.dsc&amp;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?
&lt;/pre&gt;</description>
    <dc:creator>Dan 'Da Man'</dc:creator>
    <dc:date>2011-01-17T14:56:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.backports/15031">
    <title>Hi ubuntu-backports, sale 90% discount. living</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.backports/15031</link>
    <description>&lt;pre&gt;&lt;/pre&gt;</description>
    <dc:creator>Software Sale</dc:creator>
    <dc:date>2010-11-14T12:25:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.backports/14867">
    <title>Launchpad Bugs Re-enabling Auto Expiring Bugs</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.backports/14867</link>
    <description>&lt;pre&gt;
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 de&lt;/pre&gt;</description>
    <dc:creator>deryck.hodge&lt; at &gt;canonical.com</dc:creator>
    <dc:date>2010-10-05T22:24:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.backports/14866">
    <title>Launchpad Bugs Re-enabling Auto Expiring Bugs</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.backports/14866</link>
    <description>&lt;pre&gt;
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 i&lt;/pre&gt;</description>
    <dc:creator>deryck.hodge&lt; at &gt;canonical.com</dc:creator>
    <dc:date>2010-10-05T22:24:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.backports/14865">
    <title>Launchpad Bugs Re-enabling Auto Expiring Bugs</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.backports/14865</link>
    <description>&lt;pre&gt;
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 determin&lt;/pre&gt;</description>
    <dc:creator>deryck.hodge&lt; at &gt;canonical.com</dc:creator>
    <dc:date>2010-10-05T22:24:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.backports/14864">
    <title>Launchpad Bugs Re-enabling Auto Expiring Bugs</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.backports/14864</link>
    <description>&lt;pre&gt;
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 &lt;/pre&gt;</description>
    <dc:creator>deryck.hodge&lt; at &gt;canonical.com</dc:creator>
    <dc:date>2010-10-05T22:24:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.backports/14863">
    <title>Launchpad Bugs Re-enabling Auto Expiring Bugs</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.backports/14863</link>
    <description>&lt;pre&gt;
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&lt;/pre&gt;</description>
    <dc:creator>deryck.hodge&lt; at &gt;canonical.com</dc:creator>
    <dc:date>2010-10-05T22:24:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.backports/14862">
    <title>Launchpad Bugs Re-enabling Auto Expiring Bugs</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.backports/14862</link>
    <description>&lt;pre&gt;
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 determin&lt;/pre&gt;</description>
    <dc:creator>deryck.hodge&lt; at &gt;canonical.com</dc:creator>
    <dc:date>2010-10-05T22:24:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.backports/14861">
    <title>Launchpad Bugs Re-enabling Auto Expiring Bugs</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.backports/14861</link>
    <description>&lt;pre&gt;
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 determin&lt;/pre&gt;</description>
    <dc:creator>deryck.hodge&lt; at &gt;canonical.com</dc:creator>
    <dc:date>2010-10-05T22:24:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.backports/14860">
    <title>Launchpad Bugs Re-enabling Auto Expiring Bugs</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.backports/14860</link>
    <description>&lt;pre&gt;
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 determin&lt;/pre&gt;</description>
    <dc:creator>deryck.hodge&lt; at &gt;canonical.com</dc:creator>
    <dc:date>2010-10-05T22:24:48</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.linux.ubuntu.backports">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.linux.ubuntu.backports</link>
  </textinput>
</rdf:RDF>

