Alan McKinnon posted on Fri, 17 Jul 2015 23:38:44 +0200 as excerpted:
>> First off, a new virtual is being introduced, virtual/libmysqlclient.
>> virtual/mysql will represent the server (mysqld) and tools (mysqldump,
>> mysql, mysqladmin, etc) while virtual/libmysqlclient will represent the
>> mys
> On Fri, 17 Jul 2015, Ciaran McCreesh wrote:
>> Title is too long (51 chars). Maximum is 44 chars by GLEP 42.
> Every other news item seems to hit this. Maybe eselect news needs to
> be made to render news item titles over two lines if necessary.
It already does this for the "read" action.
On 17/07/2015 22:17, Brian Evans wrote:
> Here is a second Draft based on comments
>
>
> Title: MySQL client libraries and server packaging changes
> Author: Brian Evans
> Content-Type: text/plain
> Posted: 2015-07-17
> Revision: 1
> News-Item-Format: 1.0
> Display-If-Installed: virtual/mysql
>
On Fri, 17 Jul 2015 23:32:10 +0200
Ulrich Mueller wrote:
> > On Fri, 17 Jul 2015, Brian Evans wrote:
>
> > Here is a second Draft based on comments
>
> > Title: MySQL client libraries and server packaging changes
>
> Title is too long (51 chars). Maximum is 44 chars by GLEP 42.
Every other
> On Fri, 17 Jul 2015, Brian Evans wrote:
> Here is a second Draft based on comments
> Title: MySQL client libraries and server packaging changes
Title is too long (51 chars). Maximum is 44 chars by GLEP 42.
Ulrich
pgptu4Duj5yI5.pgp
Description: PGP signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here is a second Draft based on comments
Title: MySQL client libraries and server packaging changes
Author: Brian Evans
Content-Type: text/plain
Posted: 2015-07-17
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: virtual/mysql
First off, a n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 17.07.2015 19:56, Brian Evans wrote:
> Title: MySQL client libraries and server packaging changes
Be more specific, call it "split" instead of changing.
> Author: Brian Evans Content-Type: text/plain
> Posted: 2015-07-17 Revision: 1 News-Item-Fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/17/2015 2:04 PM, NP-Hardass wrote:
> On 07/17/2015 01:56 PM, Brian Evans wrote:
>> Title: MySQL client libraries and server packaging changes
>> Author: Brian Evans Content-Type:
>> text/plain Posted: 2015-07-17 Revision: 1 News-Item-Format: 1.0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/17/2015 2:19 PM, Rich Freeman wrote:
> On Fri, Jul 17, 2015 at 1:56 PM, Brian Evans wrote:
>>
>> Developers and ebuild writers should reference
>> virtual/libmysqlclient when linking against the libraries as the
>> package will keep the subslot
On Fri, Jul 17, 2015 at 1:56 PM, Brian Evans wrote:
>
> Developers and ebuild writers should reference virtual/libmysqlclient
> when linking against the libraries as the package will keep the
> subslot the same as the soversion for easy rebuilds.
This isn't super-relevant to the news item itself,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/17/2015 01:56 PM, Brian Evans wrote:
> Title: MySQL client libraries and server packaging changes Author:
> Brian Evans Content-Type: text/plain Posted:
> 2015-07-17 Revision: 1 News-Item-Format: 1.0 Display-If-Installed:
> virtual/mysql
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Title: MySQL client libraries and server packaging changes
Author: Brian Evans
Content-Type: text/plain
Posted: 2015-07-17
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: virtual/mysql
The future of the mysql packages is changing.
First off,
On Fri, 17 Jul 2015 08:50:43 -0400
Rich Freeman wrote:
> On Fri, Jul 17, 2015 at 8:36 AM, Rich Freeman
> wrote:
> > On Fri, Jul 17, 2015 at 12:42 AM, Brian Dolbec
> > wrote:
> >>
> >> I don't know tbh, most are already signed, with the git migration,
> >> the strongly recommended commit signing
On Fri, 17 Jul 2015 08:36:25 -0400
Rich Freeman wrote:
> On Fri, Jul 17, 2015 at 12:42 AM, Brian Dolbec
> wrote:
> >
> > I don't know tbh, most are already signed, with the git migration,
> > the strongly recommended commit signing will become MANDATORY.
> >
> > So, we are at 50 devs with valid
On Fri, Jul 17, 2015 at 8:36 AM, Rich Freeman wrote:
> On Fri, Jul 17, 2015 at 12:42 AM, Brian Dolbec wrote:
>>
>> I don't know tbh, most are already signed, with the git migration, the
>> strongly recommended commit signing will become MANDATORY.
>>
>> So, we are at 50 devs with valid gpg keys n
On 17 July 2015 at 15:36, Rich Freeman wrote:
> On Fri, Jul 17, 2015 at 12:42 AM, Brian Dolbec wrote:
>>
>> I don't know tbh, most are already signed, with the git migration, the
>> strongly recommended commit signing will become MANDATORY.
>>
>> So, we are at 50 devs with valid gpg keys now, wit
On Fri, Jul 17, 2015 at 12:42 AM, Brian Dolbec wrote:
>
> I don't know tbh, most are already signed, with the git migration, the
> strongly recommended commit signing will become MANDATORY.
>
> So, we are at 50 devs with valid gpg keys now, with 200 more gpg keys
> listed in LDAP that fail to meet
Hi,
On Fri, 17 Jul 2015 14:22:23 +0400 Jason Zaman wrote:
> On Fri, Jul 17, 2015 at 01:15:53PM +0300, Andrew Savchenko wrote:
> > Hello,
> >
> > TL;DR Is there any tool to build dependency tree for all packages
> > needed to be stabilized (or keyworded) in order stabilize (keyword)
> > foo/bar?
>
On 17 July 2015 at 22:34, Andrew Savchenko wrote:
> 2. Add an optional feature to emerge (or even to PMS?) allowing user
> to provide a usable GPG key for signing packages CONTENTS files
> after its generation. In order for such key to be usable during
> emerge run, gpg-agent should be used; alter
Hi,
On Fri, 17 Jul 2015 10:18:14 +0200 Kristian Fiskerstrand wrote:
> > Additionally, I feel that a signature is a means of acknowledging
> > that a package has been looked over, and that developer has stated
> > that they approve of the existing state. I'm not sure if others
> > agree with that
On Fri, Jul 17, 2015 at 01:15:53PM +0300, Andrew Savchenko wrote:
> Hello,
>
> TL;DR Is there any tool to build dependency tree for all packages
> needed to be stabilized (or keyworded) in order stabilize (keyword)
> foo/bar?
gnome team has this, its pretty good and has a --check-dependencies too
Hello,
TL;DR Is there any tool to build dependency tree for all packages
needed to be stabilized (or keyworded) in order stabilize (keyword)
foo/bar?
Sometimes in order to stabilize a single version bump a whole lot
of packages needs to be stabilized as dependencies. A good example
is [1]. What I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/17/2015 11:48 AM, hasufell wrote:
> On 07/17/2015 10:18 AM, Kristian Fiskerstrand wrote:
>> On 07/17/2015 03:13 AM, NP-Hardass wrote:
>>
>>> Additionally, I feel that a signature is a means of
>>> acknowledging that a package has been looked o
On 07/17/2015 10:18 AM, Kristian Fiskerstrand wrote:
> On 07/17/2015 03:13 AM, NP-Hardass wrote:
>
>> Additionally, I feel that a signature is a means of acknowledging
>> that a package has been looked over, and that developer has stated
>> that they approve of the existing state. I'm not sure if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/17/2015 03:13 AM, NP-Hardass wrote:
> Additionally, I feel that a signature is a means of acknowledging
> that a package has been looked over, and that developer has stated
> that they approve of the existing state. I'm not sure if others
> a
25 matches
Mail list logo
