On Thu, 05 Jan 2012 14:38:57 -0600
Rex Dieter rdie...@math.unl.edu wrote:
Stijn Hoop wrote:
Well it also took them two years to consider 'NFS mounted home' a
valid use case, during which the whole 'you really need MySQL!!!'
was broken for our site.
It's easy to switch (maybe I should
2012-01-05 20:20 keltezéssel, Kevin Kofler írta:
Rex Dieter wrote:
I'm of a mind to revisit this (again).
NO, not again!!!
Can we please stop this nonsense?
Upstream defaults to MySQL for a reason, and strongly recommends NOT using
the SQLite backend by default. SQLite doesn't support
Zoltan Boszormenyi wrote:
Then switch to using PostgreSQL as the database backend.
It's secure by default (e.g. only allows localhost connections) and
has better concurrency than MySQL. It's also Tom Lane's territory
and I like it better too. :-)
PostgreSQL requires manual intervention at
Kevin Kofler wrote:
PostgreSQL requires manual intervention at each upgrade (dump BEFORE you
upgrade, restore afterwards)
As of PostgreSQL 9.0, there is an upgrade utility[1] that doesn't
require a dump/restore. I have used it to go from 8.4 to 9.0 and now 9.0
to 9.1 without an issue.
[1]
Michael Cronenworth m...@cchtml.com writes:
Kevin Kofler wrote:
PostgreSQL requires manual intervention at each upgrade (dump BEFORE you
upgrade, restore afterwards)
As of PostgreSQL 9.0, there is an upgrade utility[1] that doesn't
require a dump/restore.
But it does still require manual
On Thu, 2012-01-05 at 13:13 -0500, Bill Nottingham wrote:
Tom Lane (t...@redhat.com) said:
So I submitted a routine bodhi request for updating mysql, and was
astonished to find that it's marked as critpath. It was never that
before. Who decided this,
The dependency solver. It's not a
On Thu, 2012-01-05 at 20:25 +0100, Kevin Kofler wrote:
Bill Nottingham wrote:
kdepim is in critical path as part of 'critical-path-apps', which is
essentially mail web. The change that caused this to get added is that
the script prior to early December wasn't actually iterating over the
Adam Williamson (awill...@redhat.com) said:
On Thu, 2012-01-05 at 13:13 -0500, Bill Nottingham wrote:
Tom Lane (t...@redhat.com) said:
So I submitted a routine bodhi request for updating mysql, and was
astonished to find that it's marked as critpath. It was never that
before. Who
So I submitted a routine bodhi request for updating mysql, and was
astonished to find that it's marked as critpath. It was never that
before. Who decided this, and would it not have been polite to involve
or at least notify the package maintainer?
regards, tom lane
--
El Thu, 05 Jan 2012 12:16:34 -0500
Tom Lane t...@redhat.com escribió:
So I submitted a routine bodhi request for updating mysql, and was
astonished to find that it's marked as critpath. It was never that
before. Who decided this, and would it not have been polite to
involve or at least
Dennis Gilmore den...@ausil.us writes:
El Thu, 05 Jan 2012 12:16:34 -0500
Tom Lane t...@redhat.com escribió:
So I submitted a routine bodhi request for updating mysql, and was
astonished to find that it's marked as critpath. It was never that
before. Who decided this, and would it not have
On Thu, Jan 5, 2012 at 5:36 PM, Tom Lane t...@redhat.com wrote:
Dennis Gilmore den...@ausil.us writes:
El Thu, 05 Jan 2012 12:16:34 -0500
Tom Lane t...@redhat.com escribió:
So I submitted a routine bodhi request for updating mysql, and was
astonished to find that it's marked as critpath. It
El Thu, 05 Jan 2012 12:36:25 -0500
Tom Lane t...@redhat.com escribió:
Dennis Gilmore den...@ausil.us writes:
El Thu, 05 Jan 2012 12:16:34 -0500
Tom Lane t...@redhat.com escribió:
So I submitted a routine bodhi request for updating mysql, and was
astonished to find that it's marked as
Peter Robinson pbrobin...@gmail.com writes:
On Thu, Jan 5, 2012 at 5:36 PM, Tom Lane t...@redhat.com wrote:
That answer doesn't make me any happier. I've got a problem with being
saddled with an extra layer of bureaucracy without any say-so on my
part, and I'm also quite nervous about the
Tom Lane (t...@redhat.com) said:
So I submitted a routine bodhi request for updating mysql, and was
astonished to find that it's marked as critpath. It was never that
before. Who decided this,
The dependency solver. It's not a manual process.
and would it not have been polite to involve
Bill Nottingham wrote:
Tom Lane (t...@redhat.com) said:
So I submitted a routine bodhi request for updating mysql, and was
astonished to find that it's marked as critpath. It was never that
before. Who decided this,
The dependency solver. It's not a manual process.
and would it not
On 01/05/2012 07:32 PM, Rex Dieter wrote:
Sorry Tom, didn't foresee all the implications when we flipped f16's default
akonadi backend sqlite - mysql late(ish) in the cycle.
I'm of a mind to revisit this (again).
-- rex
Just my 2c, I'm also of the opinion something lighter than mysql is
Bill Nottingham nott...@redhat.com writes:
http://lists.fedoraproject.org/pipermail/devel-announce/2011-December/000868.html
... The change that caused this to get added is that the
script prior to early December wasn't actually iterating over the proper
critpath groups, including
Brendan Jones wrote:
On 01/05/2012 07:32 PM, Rex Dieter wrote:
Sorry Tom, didn't foresee all the implications when we flipped f16's
default
akonadi backend sqlite - mysql late(ish) in the cycle.
I'm of a mind to revisit this (again).
-- rex
Just my 2c, I'm also of the opinion something
Rex Dieter rdie...@math.unl.edu writes:
Bill Nottingham wrote:
As to where it came from, the dep chain is:
kdepim
- akonadi
- qt-mysql, mysql-server
kdepim is in critical path as part of 'critical-path-apps', which is
essentially mail web.
Sorry Tom, didn't foresee all the
On Thu, Jan 05, 2012 at 01:13:47PM -0500, Bill Nottingham wrote:
Tom Lane (t...@redhat.com) said:
So I submitted a routine bodhi request for updating mysql, and was
astonished to find that it's marked as critpath. It was never that
before. Who decided this,
The dependency solver. It's
Toshio Kuratomi a.bad...@gmail.com writes:
On Thu, Jan 05, 2012 at 01:13:47PM -0500, Bill Nottingham wrote:
We could consider having pkgdb e-mail the owner when the critpath bit for
the package gets flipped. Toshio, is that possible?
It is if we decide we want to do that.
Just let me know
On Thu, 2012-01-05 at 14:08 -0500, Tom Lane wrote:
Toshio Kuratomi a.bad...@gmail.com writes:
On Thu, Jan 05, 2012 at 01:13:47PM -0500, Bill Nottingham wrote:
We could consider having pkgdb e-mail the owner when the critpath bit for
the package gets flipped. Toshio, is that possible?
It
Rex Dieter wrote:
I'm of a mind to revisit this (again).
NO, not again!!!
Can we please stop this nonsense?
Upstream defaults to MySQL for a reason, and strongly recommends NOT using
the SQLite backend by default. SQLite doesn't support concurrency (i.e. any
Akonadi operation blocks all
Tom Lane wrote:
I'd recommend it. mysql is kind of a heavyweight requirement to have
underneath a desktop component: it raises the ante in terms of what has
to be installed and running, and in terms of required sysadmin-ish
know-how. (Does the average user have a clue how to configure mysql
Bill Nottingham wrote:
kdepim is in critical path as part of 'critical-path-apps', which is
essentially mail web. The change that caused this to get added is that
the script prior to early December wasn't actually iterating over the
proper critpath groups, including critical-path-apps.
I
Am 05.01.2012 20:22, schrieb Kevin Kofler:
Akonadi ships its own default MySQL configuration, which is per user. It
does not use or require the systemwide instance (by default; it can be
configured to connect to a systemwide or even remote MySQL server, but the
default is a local per-user
Kevin Kofler (kevin.kof...@chello.at) said:
Bill Nottingham wrote:
kdepim is in critical path as part of 'critical-path-apps', which is
essentially mail web. The change that caused this to get added is that
the script prior to early December wasn't actually iterating over the
proper
On 01/05/2012 08:20 PM, Kevin Kofler wrote:
Rex Dieter wrote:
I'm of a mind to revisit this (again).
NO, not again!!!
Can we please stop this nonsense?
Upstream defaults to MySQL for a reason, and strongly recommends NOT using
the SQLite backend by default. SQLite doesn't support
On Thu, Jan 05, 2012 at 02:08:02PM -0500, Tom Lane wrote:
Toshio Kuratomi a.bad...@gmail.com writes:
On Thu, Jan 05, 2012 at 01:13:47PM -0500, Bill Nottingham wrote:
We could consider having pkgdb e-mail the owner when the critpath bit for
the package gets flipped. Toshio, is that possible?
El Thu, 05 Jan 2012 20:20:55 +0100
Kevin Kofler kevin.kof...@chello.at escribió:
Rex Dieter wrote:
I'm of a mind to revisit this (again).
NO, not again!!!
Can we please stop this nonsense?
Upstream defaults to MySQL for a reason, and strongly recommends NOT
using the SQLite backend by
Reindl Harald wrote:
does it also run mysql_upgrade automatically or is it
supposed to be the road of dead two mysql-major-releases
later?
AFAIK, it does run mysql_upgrade when needed.
somehow strange that amarok was crippled down from optional
mysqld-usage to sqlite and now KDE introduces
Reindl Harald wrote:
Am 05.01.2012 20:22, schrieb Kevin Kofler:
Akonadi ships its own default MySQL configuration, which is per user. It
does not use or require the systemwide instance (by default; it can be
configured to connect to a systemwide or even remote MySQL server, but
the
Brendan Jones wrote:
Can understand that this is a hot topic but ... Surely for a single user
desktop you don't need a concurrent DB backend.
Try reading your existing mail while fetching new one. (Just one example.)
(And that hasn't worked with KMail 1 ever, AFAIK KMail 2 finally fixes this,
Dennis Gilmore wrote:
considering that mysql couldnt cope with my email and i had to stop
using kmail all together going to sqlite im sure would be worse. but
thats my 2c
Flipping defaults doesn't mean other backends cannot be used. We've helped
make sure that switching backends (to/from
On Thu, 05 Jan 2012 20:20:55 +0100
Kevin Kofler kevin.kof...@chello.at wrote:
Rex Dieter wrote:
I'm of a mind to revisit this (again).
NO, not again!!!
Can we please stop this nonsense?
Upstream defaults to MySQL for a reason, and strongly recommends NOT
using the SQLite backend by
Stijn Hoop wrote:
Well it also took them two years to consider 'NFS mounted home' a valid
use case, during which the whole 'you really need MySQL!!!' was broken
for our site.
It's easy to switch (maybe I should blog about it... )
per user: kcmshell4 akonadi
per machine/site: create/edit
On Thu, Jan 5, 2012 at 5:51 PM, Tom Lane t...@redhat.com wrote:
Peter Robinson pbrobin...@gmail.com writes:
On Thu, Jan 5, 2012 at 5:36 PM, Tom Lane t...@redhat.com wrote:
That answer doesn't make me any happier. I've got a problem with being
saddled with an extra layer of bureaucracy without
On 01/05/2012 09:03 PM, Kevin Kofler wrote:
Brendan Jones wrote:
Can understand that this is a hot topic but ... Surely for a single user
desktop you don't need a concurrent DB backend.
Try reading your existing mail while fetching new one. (Just one example.)
(And that hasn't worked with
Tom Lane wrote:
I've got other critpath packages, so I know exactly what kind of
additional bureaucracy I'm getting into, thank you. But I'm not
following how something that's not even installed by default can
reasonably become marked critpath.
mysql-server is actually installed by default
40 matches
Mail list logo
