Re: [gentoo-dev] New portage git sync behavior

2016-10-12 Thread konsolebox 
On Thu, Oct 13, 2016 at 2:51 AM, Mike Gilbert  wrote:
> You may direct any complaints to the Portage dev team.

I only intended to notify.

-- 
konsolebox

Re: [gentoo-dev] New portage git sync behavior

2016-10-12 Thread konsolebox 
On Thu, Oct 13, 2016 at 9:36 AM, Daniel Campbell  wrote:
> On 10/12/2016 11:45 AM, konsolebox wrote:
>> On Wed, Sep 21, 2016 at 11:02 AM, Mike Gilbert  wrote:
>>> Portage 2.3.1 changes the default behavior for git repositories to
>>> sync with a depth of 1. If you are using a development tree with
>>> emerge --sync, you may want to override this in repos.conf by setting
>>> sync-depth = 0.
>>>
>>> If you have accidentally converted your development tree into a
>>> shallow repository, you can undo the damage by running git fetch
>>> --unshallow.
>>>
>>
>> I can't find this in the release notes.
>>
> Wasn't it in a news message? I recall seeing it somewhere, and made the
> appropriate changes before upgrading.
>

I think you saw it here, and so did I but surprised to see that it's
not in the /usr/share/doc/portage-2.3.1 nor in 'eselect news'.

-- 
konsolebox

Re: [gentoo-dev] New portage git sync behavior

2016-10-12 Thread Daniel Campbell 
On 10/12/2016 11:45 AM, konsolebox wrote:
> On Wed, Sep 21, 2016 at 11:02 AM, Mike Gilbert  wrote:
>> Portage 2.3.1 changes the default behavior for git repositories to
>> sync with a depth of 1. If you are using a development tree with
>> emerge --sync, you may want to override this in repos.conf by setting
>> sync-depth = 0.
>>
>> If you have accidentally converted your development tree into a
>> shallow repository, you can undo the damage by running git fetch
>> --unshallow.
>>
> 
> I can't find this in the release notes.
> 
Wasn't it in a news message? I recall seeing it somewhere, and made the
appropriate changes before upgrading.

-- 
Daniel Campbell - Gentoo Developer
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
fpr: AE03 9064 AE00 053C 270C  1DE4 6F7A 9091 1EA0 55D6



signature.asc
Description: OpenPGP digital signature

Re: [gentoo-dev] New single dev-python/twisted package releases in the tree

2016-10-12 Thread Brian Dolbec 
On Wed, 12 Oct 2016 16:35:25 -0700
Brian Dolbec  wrote:

> Since the mid 15.x.x releases of twisted, upstream changed from the
> split releases twisted-{core,names,web,...} to a single twisted
> package release. Our gentoo tree has been behind with upstream
> releases since then partially due to this change and the work
> involved in the conversion.
> 
> I am pleased to inform you that I have now completed the new twisted
> package ebuilds and updated/additional/new dependencies.  There are
> now dev-python/twisted-16.2.0 and 16.3.2 releases in the gentoo tree
> and I am working on 16.4.1 to get the tests working before adding it
> to the tree.  I have been doing testing of the 16.2 and 16.3 releases
> in my buildbot-0.9.0 (day job) work without any issues.
> 
> Currently I have added dev-util/buildbot, dev-util/buildbot-worker,
> www-servers/tornado, dev-python/autobahn, dev-python/txrequests
> ebuilds which have ||() dependencies on either the old split twisted
> or new twisted single pkg dependencies.
> 
> Since there are no longer any split twisted-* pkg releases, any new
> pkgs/ebuilds should be made with either the new dev-python/twisted
> only or ||() twisted pkgs dependencies as the maintainer sees fit. You
> should also list the new dev-python/twisted pkg first in any ||() deps
> you add.  I have come across a portage bug where the resolver was not
> able to solve a conflict between the old split pkgs and the new single
> pkg where it should have been able to.  This was partially due to
> having the old split twisted pkgs listed as the first (left) entry in
> the ||().
> 
> You should not introduce new pkgs and hopefully new ebuild versions of
> existing pkgs that list only the old split twisted pkgs as
> dependencies. I am sure that eventually the old split releases will
> be tree-cleaned at some future point.
> 
> Thank you

I forgot...

The new twisted package is also mostly python3 compatible. There is
code in twisted's setup.py that will not install modules to a py3 that
are not yet ported to python3.  So, there should be no issue turn up
during the twisted install.

I have not checked as to which modules have not been ported yet, but
those modules will still install to python2.7.  If you have any issues
with your pkg using twisted under python3, then you may have to
restrict py3 from your pkg's PYTHON_COMPAT.  As I get caught up, I'll
check in more detail which modules are not yet ported.  If you come
across any, feel free to send me a note or even add an ewarn to the
affected twisted ebuild about that sub-modules py3 availability. 

-- 
Brian Dolbec 



pgp48SDhsw0vP.pgp
Description: OpenPGP digital signature

[gentoo-dev] New single dev-python/twisted package releases in the tree

2016-10-12 Thread Brian Dolbec 

Since the mid 15.x.x releases of twisted, upstream changed from the
split releases twisted-{core,names,web,...} to a single twisted package
release. Our gentoo tree has been behind with upstream releases since
then partially due to this change and the work involved in the
conversion.

I am pleased to inform you that I have now completed the new twisted
package ebuilds and updated/additional/new dependencies.  There are now
dev-python/twisted-16.2.0 and 16.3.2 releases in the gentoo tree and I
am working on 16.4.1 to get the tests working before adding it to the
tree.  I have been doing testing of the 16.2 and 16.3 releases in my
buildbot-0.9.0 (day job) work without any issues.

Currently I have added dev-util/buildbot, dev-util/buildbot-worker,
www-servers/tornado, dev-python/autobahn, dev-python/txrequests
ebuilds which have ||() dependencies on either the old split twisted
or new twisted single pkg dependencies.

Since there are no longer any split twisted-* pkg releases, any new
pkgs/ebuilds should be made with either the new dev-python/twisted only
or ||() twisted pkgs dependencies as the maintainer sees fit. You
should also list the new dev-python/twisted pkg first in any ||() deps
you add.  I have come across a portage bug where the resolver was not
able to solve a conflict between the old split pkgs and the new single
pkg where it should have been able to.  This was partially due to having
the old split twisted pkgs listed as the first (left) entry in the ||().

You should not introduce new pkgs and hopefully new ebuild versions of
existing pkgs that list only the old split twisted pkgs as dependencies.
I am sure that eventually the old split releases will be tree-cleaned
at some future point.

Thank you
-- 
Brian Dolbec 



pgpxfrk_UJPrK.pgp
Description: OpenPGP digital signature

[gentoo-dev] [warning] the bug queue has 82 bugs

2016-10-12 Thread Alex Alexander 
Our bug queue has 82 bugs!

If you have some spare time, please help assign/sort a few bugs.

To view the bug queue, click here: http://bit.ly/m8PQS5

Thanks!

[gentoo-dev] Last rites: www-client/rekonq

2016-10-12 Thread Michael Palimaka 
# Michael Palimamka  12 Oct 2016)
# Dead upstream. Requires dead and vulnerable qtwebkit4.
# Consider www-client/qupzilla or www-client/otter instead.
# Masked for removal in 30 days.
www-client/rekonq

Re: [gentoo-dev] New portage git sync behavior

2016-10-12 Thread Mike Gilbert 
On Wed, Oct 12, 2016 at 2:45 PM, konsolebox  wrote:
> On Wed, Sep 21, 2016 at 11:02 AM, Mike Gilbert  wrote:
>> Portage 2.3.1 changes the default behavior for git repositories to
>> sync with a depth of 1. If you are using a development tree with
>> emerge --sync, you may want to override this in repos.conf by setting
>> sync-depth = 0.
>>
>> If you have accidentally converted your development tree into a
>> shallow repository, you can undo the damage by running git fetch
>> --unshallow.
>>
>
> I can't find this in the release notes.

Because it isn't there. You may direct any complaints to the Portage dev team.

Re: [gentoo-dev] New portage git sync behavior

2016-10-12 Thread konsolebox 
On Wed, Sep 21, 2016 at 11:02 AM, Mike Gilbert  wrote:
> Portage 2.3.1 changes the default behavior for git repositories to
> sync with a depth of 1. If you are using a development tree with
> emerge --sync, you may want to override this in repos.conf by setting
> sync-depth = 0.
>
> If you have accidentally converted your development tree into a
> shallow repository, you can undo the damage by running git fetch
> --unshallow.
>

I can't find this in the release notes.

-- 
konsolebox

Re: [gentoo-dev] RFC: VCS element in metadata.xml

2016-10-12 Thread Michał Górny 
On Wed, 12 Oct 2016 09:44:39 -0700
"Robin H. Johnson"  wrote:

> For projects where no consistent remote-id is available yet, make it possible
> to track where the source is available. The element may appear multiple times,
> but values must be unique.
> 
> git://git.gentoo.org/proj/genkernel.git
> https://gitweb.gentoo.org/proj/genkernel.git/

The second form is ambiguous, as it doesn't declare the VCS
in question. To follow a precedence, I suggest using the format from
repositories.xml.

Furthermore, you are missing the most important part -- patch for
GLEP 68.

-- 
Best regards,
Michał Górny



pgp56R6nnZCTL.pgp
Description: OpenPGP digital signature

Re: [gentoo-dev] [PATCH] metadata: add vcs tag

2016-10-12 Thread Michał Górny 
On Wed, 12 Oct 2016 09:44:41 -0700
"Robin H. Johnson"  wrote:

> Signed-off-by: Robin H. Johnson 
> ---
>  metadata.xsd | 4 
>  1 file changed, 4 insertions(+)
> 
> diff --git a/metadata.xsd b/metadata.xsd
> index cad8304..20423f8 100644
> --- a/metadata.xsd
> +++ b/metadata.xsd
> @@ -83,6 +83,10 @@
>   
>   
>   
> + 
> + 
> + 
> + 

Is there a reason to disallow more than one occurrence of ?

>   
>   
>   

You are missing actually adding the element... You just added
a constraint on a non-existing element.

-- 
Best regards,
Michał Górny



pgpB6qP6RPBH9.pgp
Description: OpenPGP digital signature

[gentoo-dev] RFC: VCS element in metadata.xml

2016-10-12 Thread Robin H. Johnson 
For projects where no consistent remote-id is available yet, make it possible
to track where the source is available. The element may appear multiple times,
but values must be unique.

git://git.gentoo.org/proj/genkernel.git
https://gitweb.gentoo.org/proj/genkernel.git/

[gentoo-dev] [PATCH] metadata: add vcs tag

2016-10-12 Thread Robin H. Johnson 
Signed-off-by: Robin H. Johnson 
---
 metadata.dtd | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/metadata.dtd b/metadata.dtd
index d7ef81c..380fdbd 100644
--- a/metadata.dtd
+++ b/metadata.dtd
@@ -35,7 +35,7 @@
   
 
   
-  
+  
 
 
   
+
+
 
   
-- 
2.9.0

[gentoo-dev] [PATCH] metadata: add vcs tag

2016-10-12 Thread Robin H. Johnson 
Signed-off-by: Robin H. Johnson 
---
 metadata.xsd | 4 
 1 file changed, 4 insertions(+)

diff --git a/metadata.xsd b/metadata.xsd
index cad8304..20423f8 100644
--- a/metadata.xsd
+++ b/metadata.xsd
@@ -83,6 +83,10 @@



+   
+   
+   
+   



-- 
2.9.0

Re: [gentoo-dev] grub-2 configuration

2016-10-12 Thread William Hubbs 
On Tue, Oct 11, 2016 at 10:42:43AM -0400, Tom H wrote:
> I was sharing what I do because I've overwritten a manually-edited
> grub.cfg by running grub-mkconfig/grub2-mkconfig/update-grub (re
> grub2-mkconfig, I use grub-mkconfig on Gentoo because I set
> "-multislot") more than once - and I know other sysadmins who've made
> the same mistake.

Multislot is a downstream feature that renames parts of grub-2.x to
grub2-* instead of grub-* so that grub-0.x and grub-2.x can be on the
system at the same time. My understanding is that it is there to make
switching back and forth between grub-0 and grub-2 easier . In my
opinion, the better choice is to turn it off.

William


signature.asc
Description: Digital signature