<?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.devel">
    <title>gmane.linux.ubuntu.devel</title>
    <link>http://blog.gmane.org/gmane.linux.ubuntu.devel</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.devel/35324"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.devel/35323"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.devel/35322"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.devel/35313"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.devel/35300"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.devel/35296"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.devel/35294"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.devel/35291"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.devel/35288"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.devel/35285"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.devel/35276"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.devel/35275"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.devel/35262"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.devel/35261"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.devel/35258"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.devel/35255"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.devel/35253"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.devel/35248"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.devel/35240"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.ubuntu.devel/35226"/>
      </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.devel/35324">
    <title>Ubuntu Server Team Meeting Minute 20120522</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.devel/35324</link>
    <description>&lt;pre&gt;Meeting started by s3h at 16:01:01 UTC.  The full logs are available at
http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-22-16.01.log.html
.

== Meeting summary ==

 *Review ACTION points from previous
''LINK:'' https://blueprints.launchpad.net/~ubuntu-server/+specs?role=drafter   (Daviey, 16:04:06)
''LINK:'' https://blueprints.launchpad.net/~james-page/+specs?searchtext=servercloud-q&amp;amp;role=assignee   (Daviey, 16:04:12)
''LINK:'' https://blueprints.launchpad.net/~james-page/+specs?searchtext=servercloud-q&amp;amp;role=assignee   (s3h, 16:04:57)
''LINK:'' http://people.canonical.com/~davewalker/delta.html   (Daviey, 16:06:53)
''ACTION:'' zul talk to arosales and jamespage offline about SRU tracker  (s3h, 16:07:05)

 *Quantal Development

Specs currently under consideration are at https://blueprints.launchpad.net/~ubuntu-server/+specs?role=drafter.  If a spec is missing, let Daviey know.

Blueprints which $user is responsible for driving to Approved state can be found at https://blueprints&lt;/pre&gt;</description>
    <dc:creator>Serge Hallyn</dc:creator>
    <dc:date>2012-05-23T21:23:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.devel/35323">
    <title>Next Ubuntu Algorithm Classess</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.devel/35323</link>
    <description>&lt;pre&gt;Hello,

We have a monthly delay, because ACM ICPC (International Algorithm
Competition) was held in Poland and everyone were busy at that time.

Next classess will be held on 25.05 at 17:00 UTC (Time in your city
http://bit.ly/KLG8Lh), freenode IRC chat &amp;lt;http://webchat.freenode.net/&amp;gt; (
webchat.freenode.net), channel *#ubuntu-classroom*
Here is the link to notes:
https://docs.google.com/document/d/1Okbul4AIzQTR4CVGLcx-dmIXkdToNvLiJkIZurxNB8Q/edit



Marek Bardoński
&lt;/pre&gt;</description>
    <dc:creator>bdfhjk</dc:creator>
    <dc:date>2012-05-23T17:39:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.devel/35322">
    <title>Patch pilot report, 22/05/2012.</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.devel/35322</link>
    <description>&lt;pre&gt;Bug #1002909  sync mpqc - Synced.

Bug #1002885 merge lastfm - Wasn't really a merge, more a sync and fix FTBFs due to our glib.h change, so uploaded.

Bug 1002875 sync istanbul - Synced.

Bug 1002869 sync inspircd - Already synced.

lp:~logatron/ubuntu/quantal/netatalk/fix-for-992849 - The patch to fix a typo wasn't present in bzr, marked needs fixing.

lp:~n-muench/ubuntu/quantal/open-vm-tools/open-vm-tools.march-merge2b - Needs fixing, using deprecated glib functions.

lp:~logatron/ubuntu/quantal/ac100-tarball-installer/fix-for-848188 - Uploaded

&lt;/pre&gt;</description>
    <dc:creator>Luke Yelavich</dc:creator>
    <dc:date>2012-05-23T06:44:45</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.devel/35313">
    <title>Patch pilot report 2012-05-22</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.devel/35313</link>
    <description>&lt;pre&gt;Patch pilot report 2012-05-22

* Reviewed python3 branch for software-properties
  https://code.launchpad.net/~glatzor/software-properties/python3/+merge/105755
  Needs Fixing

* Reviewed python-couchdb merge from Debian merge proposal:
  https://code.launchpad.net/~dmitrij.ledkov/ubuntu/quantal/python-couchdb/merge/+merge/104527
  Needs Fixing

* Reviewed, approved, and uploaded python-tz packaging merge that adds Python
  3 support:
  https://code.launchpad.net/~takluyver/ubuntu/quantal/python-tz/merge-py3/+merge/105551

* Reviewed landscape-client merge proposal:
  https://code.launchpad.net/~bkerensa/ubuntu/quantal/landscape-client/fix-for-962974/+merge/103843
  Suggested that the change be pushed to lp:landscape-client

* Sync'd canto 0.7.10-3 with Ubuntu delta for dh_python2.
  LP: #1002861

Cheers,
-Barry
&lt;/pre&gt;</description>
    <dc:creator>Barry Warsaw</dc:creator>
    <dc:date>2012-05-22T23:24:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.devel/35300">
    <title>dh_python2 and /usr/share/pyshared in quantal</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.devel/35300</link>
    <description>&lt;pre&gt;In https://launchpad.net/ubuntu/+source/python-defaults/2.7.3-0ubuntu3 Ubuntu 
modified dh_python2 to drop creation of /usr/share/pyshared and creation of 
python version specific symlinks to /usr/lib/python2.7/dist-packages/.

I believe this change should be reverted, but rather than just upload, wanted 
to discuss it first.  See https://bugs.launchpad.net/ubuntu/+source/python-
defaults/+bug/1001912 for additional discussion.

I've checked with Piotr Ożarowski (POX), the upstream developer for dh_python2 
and he does not support removing this feature of dh_python2 until after 
pysupport and pycentral are removed.  Even with a single supported python 
version (as Ubuntu has now) it's still useful because pysupport installs files 
in the same location.  It avoids some namespace issues.

This change breaks dozens of packages and has negligible (if any) advantages.

Additionally, the Python policy lists /usr/share/pyshared as the correct 
location to install version independent python files, so removing it mo&lt;/pre&gt;</description>
    <dc:creator>Scott Kitterman</dc:creator>
    <dc:date>2012-05-22T14:49:15</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.devel/35296">
    <title>Patch Pilot Report 20120521</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.devel/35296</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

https://bugs.launchpad.net/ubuntu/+source/munin/+bug/598385
  - Review revised patch for quantal and uploaded alongside bug
https://pad.lv/1000678
  - Nominated for 12.04 - SRU information needs more work.
  - Worked with vibhav to prepare SRU information + uploaded to
precise-proposed.

https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/985981
  - Re-based to version in quantal and uploaded.

https://bugs.launchpad.net/ubuntu/+source/cfitsio3/+bug/1001572
  - Uploaded

https://code.launchpad.net/~kroq-gar78/ubuntu/precise/activemq/sid-merge/+merge/106539
  - Merge from Debian testing for SRU - not appropriate and not
correct either so pointed the proposer at the SRU process with some
general guidance - also commented in bug.

https://code.launchpad.net/~kroq-gar78/ubuntu/quantal/activemq/sid-merge/+merge/106540
  - Disapprove - package can now be synced from Debian testing -
however it FTBFS due to the switch to openjdk-7 as default Java in
Ubuntu only.
  - &lt;/pre&gt;</description>
    <dc:creator>James Page</dc:creator>
    <dc:date>2012-05-21T17:10:21</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.devel/35294">
    <title>Improving the release notes for 12.10</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.devel/35294</link>
    <description>&lt;pre&gt;Hi,
   With UDS just last week, why am I starting a note off about the
release notes for 12.10 you ask?  ;)    Because this is the time we're
all putting together our blueprints, and the best opportunity to get
some standardized formats in place,  so we can get a bit smarter about
generating our release notes for this upcoming cycle.  :D

   Historically the release notes are pulled together manually as we 
go through the cycle.  This tends to involve a lot of last minute
reminders and a bit of a scramble to get the editing and summarizing
done.   This cycle,  based on the discussions at UDS[1],  we'd like to
try something different:  basically using a standard section in the
blueprint to capture the release notes, and then automating them being
copied to the right products WIKI pages when the blueprint is marked
done.

   Some teams will also be experimenting this cycle with using even more
standardized format for the whiteboards in the blueprints[2],  of which
the "Release Notes:", section will be part of.&lt;/pre&gt;</description>
    <dc:creator>Kate Stewart</dc:creator>
    <dc:date>2012-05-18T19:05:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.devel/35291">
    <title>Apport API users: Watch your data types / Python 3 porting</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.devel/35291</link>
    <description>&lt;pre&gt;Hello Ubuntu developers,

I just uploaded Apport 2.1 to Quantal. A big change in that version is
that the whole code now works with both Python 2 and 3, except for the
launchpadlib crash database backend (as we do not yet have a
python3-launchpadlib package).

I took some care that apport report objects get along with both
strings ("unicode" type in Python 2) and byte arrays ("str" type in
Python 2) in values, so most package hooks should still work. However,
now is the time to check whether they also work with Python 3, to make
the impending transition to Python 3 easier.

However, you need to watch out if you use projects or scripts which
directly use python-apport to process reports: The open(), write(),
and write_mime() methods now require the passed file descriptors to be
open in binary mode. You will get an exception otherwise.

A common pattern so far has been code like

  report = apport.Report()
  report.load(open('myfile.crash'))

This needs to be changed to

  report = apport.Report()
  with open(&lt;/pre&gt;</description>
    <dc:creator>Martin Pitt</dc:creator>
    <dc:date>2012-05-18T14:41:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.devel/35288">
    <title>Pilot Report 2012-05-17</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.devel/35288</link>
    <description>&lt;pre&gt;80 items at start, 70 (actually, 63) by end.

221112 keyboard-config: [SRU] Fix problem with space bar for fr(oss) keymap
  + Uploaded to quantal in 2.5-1ubuntu2
  + Filed SRU

825624 xkeyboard-config: [SRU] Add dead_hook and dead_horn to latin keymap
  + Uploaded to quantal in 2.5-1ubuntu2
  + Filed SRU

1000355 drbd8 - lucid sru
  + Already sponsored by timg-tpi; unsub sponsors

829819 balazarbrothers - spelling fix
  + Already accepted by Debian.  Too minor to diverge; disapproved branch

1000541 ia32-libs - Drop fluendo depends
  + Fix was uploaded for precise but not quantal
  + sponsored quantal upload 

994752 lxc
  + Already sponsored; unsub sponsors

quantal/emacs23/merge-23.4
  + Reviewed two branches from Laney, uploaded the second

1000557, 1000558, 1000560, 1000561 - texlive-* sync requests
  + sync'd

Branches needing set to Work In Progress:
 (I'm unable to set this for some reason; perhaps someone else could?)
 https://code.launchpad.net/~logatron/ubuntu/precise/xchat/fix-for-584207/+merge/10&lt;/pre&gt;</description>
    <dc:creator>Bryce Harrington</dc:creator>
    <dc:date>2012-05-18T00:12:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.devel/35285">
    <title>Python 3 port of ubiquity</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.devel/35285</link>
    <description>&lt;pre&gt;I uploaded a Python 3 port of ubiquity today, which I've been dealing
with on and off for a while.  It was surprisingly easier than I
expected, although there were a few interesting roadblocks.  I mostly
embarked on this to get some practice in writing Python 3 code, with a
side order of thinking that it would be a good idea to attack the stack
of things to port from the top down rather than the bottom up, in case
any of the work became unnecessary as a result.

I'd done a Python 3 port before, namely germinate (assisted at the time
by http://python3porting.com/), so I had a rough idea of the sort of way
I find it useful to attack these problems.  In particular, my preference
is definitely to avoid using 2to3 except as a sort of first cut at a
to-do list.  A great deal of the problem can be demolished simply by
porting to a sufficiently modern Python 2 style first.

Thus, I started with a few old standbys: print function, 'except
Exception as value', module renamings, and so on.  To start with, I
found I cou&lt;/pre&gt;</description>
    <dc:creator>Colin Watson</dc:creator>
    <dc:date>2012-05-17T17:51:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.devel/35276">
    <title>qmake configured correctly for multiarch library directories?</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.devel/35276</link>
    <description>&lt;pre&gt;I recently upgraded to 12.04 and now see two library directories on my
system, /usr/lib/ and /usr/lib/i386-linux-gnu.  The former is about
30% bigger than the latter.  When I switched to this new Ubuntu
version, my build started to break as qmake now links against
/usr/lib/i386-linux-gnu, so any libraries I were referencing residing
in /usr/lib are now missing.  For example, I can include -lGL and
-lpython as they are both in /usr/lib/i386-linux-gnu, but when I
include -lassimp it fails as the build only includes this new
multiarch dir -L/usr/lib/i386-linux-gnu.

$ qmake-qt4 --version
QMake version 2.01a
Using Qt version 4.8.1 in /usr/lib/i386-linux-gnu

$ qmake -query
QT_INSTALL_PREFIX:/usr
QT_INSTALL_DATA:/usr/share/qt4
QT_INSTALL_DOCS:/usr/share/qt4/doc
QT_INSTALL_HEADERS:/usr/include/qt4
QT_INSTALL_LIBS:/usr/lib/i386-linux-gnu
QT_INSTALL_BINS:/usr/bin
QT_INSTALL_PLUGINS:/usr/lib/i386-linux-gnu/qt4/plugins
QT_INSTALL_IMPORTS:/usr/lib/qt4/imports
QT_INSTALL_TRANSLATIONS:/usr/share/qt4/translations
QT_INSTA&lt;/pre&gt;</description>
    <dc:creator>Josh Stratton</dc:creator>
    <dc:date>2012-05-16T06:33:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.devel/35275">
    <title>PulseAudio 2.0 now available for testing for quantal.</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.devel/35275</link>
    <description>&lt;pre&gt;Hey folks,
PulseAudio 2.0 was recently released, and the audio team would like to get this into quantal at some point, but before we do, some testing is required to make sure things don't massively break. We don't believe they will, but its better to be sure.

PulseAudio 2.0 packages are available in the Ubuntu Audio dev PPA, https://launchpad.net/~ubuntu-audio-dev/+archive for quantal and precise. Precise packages are also available to help get increased testing coverage, as I am sure many of you are not yet running quantal.

If you find any regressions with PulseAudio 2.0, please file a bug against pulseaudio in launchpad, and clearly state in the bug subject that you are testing PulseAudio 2.0. Please also state whether you are running quantal or precise, just in case the bug is reproduceable on one, but not the other.

All being well, PulseAudio 2.0 will be uploaded to Quantal at the end of May, in time for alpha 1.

Thanks in advance.

Luke

&lt;/pre&gt;</description>
    <dc:creator>Luke Yelavich</dc:creator>
    <dc:date>2012-05-16T00:36:51</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.devel/35262">
    <title>event based initramfs</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.devel/35262</link>
    <description>&lt;pre&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I was a bit confused when I saw this uds event.  It is unclear to me why we would want to add upstart to the initramfs.  I think it is important to remember that the the whole purpose of the initramfs is to help the kernel find the root fs, so things that aren't needed to access the root fs really shouldn't be there, lest it add bloat and slow down booting.  After listening to the audio of the session, it seems like there are a few issues people are trying to address with upstart in the initramfs:

1)  Want to fix bugs with mdadm/luks

I don't see what this has to do with upstart at all.  If your root is encrypted, then you must prompt for the password before you can continue, so there is no reason to do this event driven rather than procedural.  Luks volumes not mounted at boot should be handled by udisks or something that can interact with the desktop.  mdadm, dmraid, and lvm have already been converted to event driven and handled via udev and are done the sam&lt;/pre&gt;</description>
    <dc:creator>Phillip Susi</dc:creator>
    <dc:date>2012-05-11T03:54:36</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.devel/35261">
    <title>Minutes from the Developer Membership Board meeting - 2012-05-09</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.devel/35261</link>
    <description>&lt;pre&gt;== Developer Membership Board meeting, 2012-05-09 ==

Chair: laney

Present: barry stgraber tumbleweed micahg bdrung

=== MOTU application Ante Karamatić ===

Application: https://wiki.ubuntu.com/AnteKaramatic/DeveloperApplicationMOTU

Voting: +1 barry tumbleweed micahg stgraber laney bdrung

The application is accepted.

Action: micahg to add permissions.

=== Per-Package uploader Ike Panhc ===

Application: https://wiki.ubuntu.com/IkePanhc/DeveloperApplication-PPU

Voting for linux-armadaxp, linux-meta-armadaxp, linux-highbank and
linux-meta-highbank (the latter two for discussion and approval on the mailing
list after the enter the archive)

Voting: +1 barry laney tumbleweed stgraber
        +0 micahg bdrung

The application is accepted.

ACTION: stgraber to add permissions

=== Per-Package uploader James Hunt ===

Application: https://wiki.ubuntu.com/JamesHunt/PPUApplication

Voting for friendly-recovery, libnih, mountall, upstart

Voting: +1 barry laney tumbleweed stgraber micahg bdrung

The applicatio&lt;/pre&gt;</description>
    <dc:creator>Iain Lane</dc:creator>
    <dc:date>2012-05-09T23:46:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.devel/35258">
    <title>New mailing list for discussion of Arsenal</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.devel/35258</link>
    <description>&lt;pre&gt;(No, not the football team...)

Arsenal is our tool for creating listings of bug reports.  As per
yesterday's session at UDS, we've set up an open membership team and
mailing list for further discussion about development, installation, and
usage.

Join the team, and the mailing list here:

  https://launchpad.net/~arsenal-user

Arsenal is currently used by a bunch of teams across Ubuntu to help
do queries against Launchpad to track bugs and generate statistics.

Bryce


&lt;/pre&gt;</description>
    <dc:creator>Bryce Harrington</dc:creator>
    <dc:date>2012-05-08T16:50:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.devel/35255">
    <title>UDS-Q Architecture Preview</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.devel/35255</link>
    <description>&lt;pre&gt;Here's a little help putting the sea of UDS sessions into context (the
web version also has clickable links from topics to sessions
http://allisonrandal.com/2012/05/07/uds-q-architecture-preview/):

I’ve shuffled and reshuffled the sessions several times, looking for the
"governing dynamic", the thematic structure that holds the Quetzal
together. I’ve settled, appropriately, on "quantization". In general
terms, quantization is a process of separating a continuous stream into
significant values or "quanta", such as image pixels from the continuous
colors of real life, or discrete atomic energy levels. The theme applies
on multiple levels. First, there's the process attendees are going
through right now (in person or remote), surfing the sea of sessions,
determining how to divide their time for maximum value.

From a historical perspective, there was another UDS here in California
not too long ago, where I recall the schedule was dominated by the
desktop. We’re in a different world today, and what struck&lt;/pre&gt;</description>
    <dc:creator>Allison Randal</dc:creator>
    <dc:date>2012-05-08T00:49:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.devel/35253">
    <title>Quantal: End of the line for i386 non-PAE</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.devel/35253</link>
    <description>&lt;pre&gt;As decided by the Tech Board, 12.04 is the last release to have the i386
non-PAE kernel flavour. So, how do we upgrade folks ? IIRC a non-PAE
kernel was installed because 1) there was less then 4GB RAM, or 2) their
CPU did not have PAE support.

The folks in case 2 are simply out of luck (and no longer supported).

I have removed the non-PAE kernel meta package from Quantal that would
allow a non-PAE upgrade. Its likely that folks attempting an upgrade to
Quantal will be left with a Precise kernel.

Any ideas on how we might allow PAE capable CPUs to upgrade? Is this the
job of update-manager ? It seems likely that Debian must have
encountered this issue before.

rtg
&lt;/pre&gt;</description>
    <dc:creator>Tim Gardner</dc:creator>
    <dc:date>2012-05-02T14:57:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.devel/35248">
    <title>Creating isos from PPAs</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.devel/35248</link>
    <description>&lt;pre&gt;Hi all,

I would like to have a developer tool that allows for someone to spin an
ubuntu iso with a set of ppas enabled. Then someone else, say someone
from the design team, could run the iso under test drive or even on
metal to see the changes. I imagine this is possible, but I don't know
where to look. Any pointers would be appreciated.

Thanks!

&lt;/pre&gt;</description>
    <dc:creator>Chase Douglas</dc:creator>
    <dc:date>2012-05-01T16:53:03</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.devel/35240">
    <title>Patch pilot report 2012-04-30</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.devel/35240</link>
    <description>&lt;pre&gt;I didn't get very much done this shift because I was mainly focusing on
opening quantal, but I didn't want to do no sponsoring at all this
month, so:

#990378: grub-ipxe: update-grub fragment inconsistent with other GRUB scripts' format
  Uploaded.

#990983: This wil enable the use memcache support what was not working and this wil close ubuntu bug 987404  Summary (one line): Sync mod-gnutls 0.5.10-1.1 (universe) from Debian sid (main)
  Offered SRU advice.

#978228: Multiarch support for libpaper
  Suggested NMUing to Debian and we can sync, since the maintainer said
  that would be OK.

#988984: [SRU] Clustered VGs require monitoring to be turned on
  Uploaded to quantal and precise-proposed; but the latter clashed with
  an existing SRU, so asked for tidy-ups.

#927828: sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void *)0)' failed.
  Uploaded to quantal and precise-proposed.

lp:~yofel/software-properties/lp-944876
  Already uploaded to precise-proposed; marked as merged.

&lt;/pre&gt;</description>
    <dc:creator>Colin Watson</dc:creator>
    <dc:date>2012-04-30T22:48:36</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.devel/35226">
    <title>THANKS</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.devel/35226</link>
    <description>&lt;pre&gt;Hello everybody,

I've been completely overwhelmed by the general reactions to the Ubuntu
12.04 release. It's clear that this was the best Ubuntu release ever.

To get a feel for how people love the work you've all been doing, check out

https://twitter.com/#!/ubuntudev

where I just retweeted a few of the incoming messages of praise and thanks.

Keep up the good work everyone!

Have a great day,
 Daniel

&lt;/pre&gt;</description>
    <dc:creator>Daniel Holbach</dc:creator>
    <dc:date>2012-04-30T10:28:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.ubuntu.devel/35225">
    <title>Considering removing flags export from dpkg-buildpackage for quantal</title>
    <link>http://comments.gmane.org/gmane.linux.ubuntu.devel/35225</link>
    <description>&lt;pre&gt;On #ubuntu-release today we've been discussing the possibility of
removing our hack from dpkg-buildpackage that exports the default output
of dpkg-buildflags in the environment.  This was an ugly hack to start
with, and some months ago we had to make it even more ugly temporarily
(https://lists.ubuntu.com/archives/ubuntu-devel/2011-November/034351.html),
but on the general understanding that we would revert the whole lot
after 12.04 and start relying on dpkg-buildflags.

The effects of this change require some analysis; they were certainly
not obvious to me.  Many of the default flags set by dpkg-buildflags are
in fact already the defaults in Ubuntu's compiler:

  -fstack-protector --param=ssp-buffer-size=4
  -D_FORTIFY_SOURCE=2
  -Wformat -Wformat-security
  -Wl,-z,relro

-Werror=format-security is output by dpkg-buildflags, but we filter that
out in the dpkg-buildpackage export hack at the moment to avoid causing
lots of build failures in unsuspecting packages.

The last remaining issue for default builds &lt;/pre&gt;</description>
    <dc:creator>Colin Watson</dc:creator>
    <dc:date>2012-04-28T00:39:54</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.linux.ubuntu.devel">
    <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.devel</link>
  </textinput>
</rdf:RDF>

