Il 15/04/2013 08:19, "Jóhann B. Guðmundsson" ha scritto:
On 04/14/2013 07:10 PM, Matthias Runge wrote:
On 04/14/2013 06:54 PM, "Jóhann B. Guðmundsson" wrote:
Convincing this is about doing the right thing!
I your intention was to ban mysql in the distribution then it should
have been banned an
On 04/14/2013 07:10 PM, Matthias Runge wrote:
On 04/14/2013 06:54 PM, "Jóhann B. Guðmundsson" wrote:
Convincing this is about doing the right thing!
I your intention was to ban mysql in the distribution then it should
have been banned and dropped instead of this mess that you guys have
created.
Hi
On Sun, Apr 14, 2013 at 7:31 PM, Kevin Kofler wrote:
> Matthias Runge wrote:
> > IMHO you cannot ban/deprecate a package from the distro, if there's
> > still a packager/contributor to the package. Also you can not force
> > somebody to drop a package.
>
> FESCo has done that even to a whole
Matthias Runge wrote:
> IMHO you cannot ban/deprecate a package from the distro, if there's
> still a packager/contributor to the package. Also you can not force
> somebody to drop a package.
FESCo has done that even to a whole group of packages: (separately-packaged)
kernel modules! It would mak
On 04/14/2013 06:54 PM, "Jóhann B. Guðmundsson" wrote:
>
> Convincing this is about doing the right thing!
>
> I your intention was to ban mysql in the distribution then it should
> have been banned and dropped instead of this mess that you guys have
> created.
IMHO you cannot ban/deprecate a p
On 04/14/2013 03:11 PM, Tom Lane wrote:
Kevin Kofler writes:
Jóhann B. Guðmundsson wrote:
If I installed mysql and have been running mysql then upgrade I expect
the upgrade process to pick up the latest mysql we ship upgraded to that
and I will be continuing to run mysql not be magically mov
Kevin Kofler writes:
> Jóhann B. Guðmundsson wrote:
>> If I installed mysql and have been running mysql then upgrade I expect
>> the upgrade process to pick up the latest mysql we ship upgraded to that
>> and I will be continuing to run mysql not be magically moved to fork of
>> it mariadb.
> S
Jóhann B. Guðmundsson wrote:
> It goes without saying that users should never be automatically moved
> from component A to component B if component A is still being provided,
> maintained and shipped in the distribution.
Which is why IMHO MySQL should not be provided anymore at all.
> If I instal
On 04/13/2013 09:42 PM, Kevin Kofler wrote:
Jóhann B. Guðmundsson wrote:
Users should not be switched automatically to Mariadb on upgrades
Of course they should! That's the point of switching!
It goes without saying that users should never be automatically moved
from component A to component
Jóhann B. Guðmundsson wrote:
> Users should not be switched automatically to Mariadb on upgrades
Of course they should! That's the point of switching!
Kevin Kofler
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
08:36 PM, Norvald Ryeng wrote:
> >>>>> What is the deadline for fixing the remaining issues with MySQL and
> >>>>> MariaDB in Fedora? We would like to find a solution and get 5.6 in
> >>>>> soon.
> >>>>
> >>>> Hi Norva
On 05/04 23.18, Matthias Runge wrote:
> On 04/05/2013 08:06 PM, Norvald Ryeng wrote:
> >
> > How do we get push access to the git repo? It would be great to get
> > 5.6 in before the test day on April 30.
> >
>
> About updating:
> https://fedoraproject.org/wiki/Updates_Policy
>
> and how to joi
On 04/10/2013 02:34 PM, Norvald Ryeng wrote:
- hho...@redhat.com wrote:
On 04/05/2013 08:06 PM, Norvald Ryeng wrote:
- hho...@redhat.com wrote:
On 03/21/2013 08:36 PM, Norvald Ryeng wrote:
What is the deadline for fixing the remaining issues with MySQL and
MariaDB in Fedora? We
- hho...@redhat.com wrote:
> On 04/05/2013 08:06 PM, Norvald Ryeng wrote:
> > - hho...@redhat.com wrote:
> >
> >> On 03/21/2013 08:36 PM, Norvald Ryeng wrote:
> >>> What is the deadline for fixing the remaining issues with MySQL and
> >>
On Mon, 08 Apr 2013 09:38:53 +0200
Honza Horak wrote:
...snip...
> > How do we get push access to the git repo? It would be great to get
> > 5.6 in before the test day on April 30.
>
> To get involved, just follow standard process as described on Fedora
> wiki:
> https://fedoraproject.org/wiki/
On 04/08/2013 07:38 AM, Honza Horak wrote:
However, I'd rather wait with 5.6 until F20 because of the following
reasons:
* we are almost a month after feature freeze
Yes thanks to how you have handled this
* I believe users will have enough concerns with switching to MariaDB
and MySQL-5.6
On 04/05/2013 08:06 PM, Norvald Ryeng wrote:
- hho...@redhat.com wrote:
On 03/21/2013 08:36 PM, Norvald Ryeng wrote:
What is the deadline for fixing the remaining issues with MySQL and
MariaDB in Fedora? We would like to find a solution and get 5.6 in
soon.
Hi Norvald,
I've just
On 04/05/2013 08:06 PM, Norvald Ryeng wrote:
>
> Could you rename the MySQL packages to mysql-community-* instead of
> community-mysql-*? That way the prefix aligns with the product name
> and OpenSuSE's prefix.
https://fedoraproject.org/wiki/Package_Renaming_Process
also naming rules apply
ht
- hho...@redhat.com wrote:
> On 03/21/2013 08:36 PM, Norvald Ryeng wrote:
> > What is the deadline for fixing the remaining issues with MySQL and
> > MariaDB in Fedora? We would like to find a solution and get 5.6 in
> > soon.
>
> Hi Norvald,
>
> I
On 03/21/2013 08:36 PM, Norvald Ryeng wrote:
What is the deadline for fixing the remaining issues with MySQL and
MariaDB in Fedora? We would like to find a solution and get 5.6 in
soon.
Hi Norvald,
I've just asked for creating component community-mysql, as discussed on
fedora-devel
20 matches
Mail list logo
