On 13 Aug 2015 09:00, Kristian Fiskerstrand wrote:
On 08/13/2015 05:17 AM, Mike Frysinger wrote:
+Your best option is to generate new keys using newer types such as
rsa +or ecdsa or ed25519. RSA keys will give you the greatest
portability +with other clients/servers while ed25519 will get
11.08.2015 17:56, Ian Stakenvicius пишет:
On 11/08/15 08:58 AM, Sergey Popov wrote:
11.08.2015 15:30, Michael Palimaka пишет:
On 11/08/15 20:10, Sergey Popov wrote:
Err, i have read the whole thread and still does not get a
point, why i am wrong.
You clearly have not. The reasoning behind
On 02 Mar 2015 16:57, viv...@gmail.com wrote:
good memory,
maybe someone could write a frontend in eselect to gcc-config, to have a
proved manager _and_ everything in one place.
done for the next release
https://bugs.gentoo.org/507870
-mike
signature.asc
Description: Digital signature
12.08.2015 22:14, Peter Stuge пишет:
May I suggest instead:
qt? (
qt5? ( dev-lang/qt$something:5 )
qt4? ( dev-lang/qt$something:4 )
)
And what would be if USE=qt -qt4 -qt5? Should we introduce a
REQUIRED_USE for that? Well, congrats then, USE qt becomes useless,
cause it does
11.08.2015 16:49, Michael Palimaka пишет:
You think that REQUIRED_USE is abusive to users: fine. Point accepted.
I think that provided DEPEND strings if they will be typed at every
single qt-related ebuild that needs them are abusive to developers.
So, maybe we should wrap them into eclass
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
might be nitpick, but..
On 08/13/2015 05:17 AM, Mike Frysinger wrote:
+Your best option is to generate new keys using newer types such as
rsa +or ecdsa or ed25519. RSA keys will give you the greatest
portability +with other
Hi,
Now that we have the official git repository, I've switched user-facing
git mirrors from rsync-git to the real git. As a result, users are now
complaining that some random Gentoo metadata has disappeared.
As you may have noticed already, I am *really* unhappy about adding
special
---
profiles/default/linux/make.defaults | 3 +++
1 file changed, 3 insertions(+)
diff --git a/profiles/default/linux/make.defaults
b/profiles/default/linux/make.defaults
index 7ad3bdb..be2f6a1 100644
--- a/profiles/default/linux/make.defaults
+++ b/profiles/default/linux/make.defaults
@@ -17,6
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/11/2015 07:32 AM, Michał Górny wrote:
Hello, everyone.
Now that we're officially on git and can officially use pull
requests to provide rapid community interaction, it'd be convenient
to have a little better framework for pinging package
Dnia 2015-08-13, o godz. 00:35:39
Daniel Campbell (zlg) z...@gentoo.org napisał(a):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/11/2015 07:32 AM, Michał Górny wrote:
Hello, everyone.
Now that we're officially on git and can officially use pull
requests to provide rapid
11.08.2015 18:02, Ian Stakenvicius пишет:
On 11/08/15 09:04 AM, Sergey Popov wrote:
11.08.2015 15:32, Michael Palimaka пишет:
On 11/08/15 20:17, Sergey Popov wrote:
09.08.2015 23:28, Ulrich Mueller пишет:
I disagree with this. Really, REQUIRED_USE should be used
sparingly, and IMHO the above
On Thu, Aug 13, 2015 at 5:26 AM, Andrew Savchenko birc...@gentoo.org wrote:
On Thu, 13 Aug 2015 09:12:30 +0200 Michał Górny wrote:
Hi,
Now that we have the official git repository, I've switched user-facing
git mirrors from rsync-git to the real git. As a result, users are now
complaining
On Thu, 13 Aug 2015 09:12:30 +0200 Michał Górny wrote:
Hi,
Now that we have the official git repository, I've switched user-facing
git mirrors from rsync-git to the real git. As a result, users are now
complaining that some random Gentoo metadata has disappeared.
As you may have noticed
I vote for a simple
Bug: 333531
If it is going to be any longer than that, then you need to make sure
it is part of the commit message template magic. Because I'm surely
not the only one who is lazy and thus averse to typing anything longer
for the most common use case: Gentoo bugs.
--
Cheers,
Dnia 2015-08-12, o godz. 22:43:24
Dean Stephens desult...@gentoo.org napisał(a):
On 08/11/15 10:32, Michał Górny wrote:
Hello, everyone.
Now that we're officially on git and can officially use pull
requests to provide rapid community interaction, it'd be convenient
to have a little
On Thu, Aug 13, 2015 at 7:19 AM, Ben de Groot yng...@gentoo.org wrote:
I vote for a simple
Bug: 333531
If it is going to be any longer than that, then you need to make sure
it is part of the commit message template magic. Because I'm surely
not the only one who is lazy and thus averse to
On 08/12/2015 09:52 PM, Mike Frysinger wrote:
On 12 Aug 2015 18:27, Brian Dolbec wrote:
2) There is another alternate location that you can define files to
ignore locally without having to commit them to .gitignore.
Consider .gitignore a global setting. There is another setting
inside
On 13/08/15 18:17, Sergey Popov wrote:
11.08.2015 16:49, Michael Palimaka пишет:
You think that REQUIRED_USE is abusive to users: fine. Point accepted.
I think that provided DEPEND strings if they will be typed at every
single qt-related ebuild that needs them are abusive to developers.
So,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/08/15 04:24 AM, Sergey Popov wrote:
11.08.2015 17:56, Ian Stakenvicius пишет:
BUT I would advise against this. If a user has specified both
qt4 and qt5 in USE, then I see no problem with the VDB having
both qt4 and qt5 atoms listed as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/08/15 09:27 PM, Brian Dolbec wrote:
2) There is another alternate location that you can define files
to ignore locally without having to commit them to .gitignore.
Consider .gitignore a global setting. There is another setting
inside
On Thu, 13 Aug 2015 01:34:36 -0700
Zac Medico zmed...@gentoo.org wrote:
Repos are synced in parallel (includes their post-sync hooks). Output
of concurrent processes is currently mixed (irrelevant with --quiet).
Support for FEATURES=metadata-transfer is handled in the main process,
which may
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, 13 Aug 2015 10:16:19 -0400
Ian Stakenvicius a...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/08/15 09:27 PM, Brian Dolbec wrote:
2) There is another alternate location that you can define files
to
On Thu, 13 Aug 2015, Michał Górny wrote:
Dnia 2015-08-13, o godz. 19:13:06
Ulrich Mueller u...@gentoo.org napisał(a):
If this is a highly-requested feature then some discussion or
other reference to it should exist in mailing lists. I can neither
remember nor can I find such a discussion.
On Thu, Aug 13, 2015 at 12:12 PM, Mike Frysinger vap...@gentoo.org wrote:
On 13 Aug 2015 10:36, William Hubbs wrote:
I understood the usefulness of this line to some when we were using CVS
since it expanded into the ebuild revision, date, etc.
This expansion doesn't take place under git, so
On Thu, 13 Aug 2015, Rich Freeman wrote:
On Thu, Aug 13, 2015 at 12:12 PM, Mike Frysinger vap...@gentoo.org wrote:
delete it and be done
+1
When I asked a few days ago the arugment was made that it will be
expanded when the ebuilds hit rsync, and then users can reference
these when
On Thu, 13 Aug 2015 19:13:06 +0200 Ulrich Mueller wrote:
On Thu, 13 Aug 2015, Rich Freeman wrote:
On Thu, Aug 13, 2015 at 12:12 PM, Mike Frysinger vap...@gentoo.org wrote:
delete it and be done
+1
+1 to remove this CVS remnant. It was needed before, it is not
really needed now.
Best
On Thu, Aug 13, 2015 at 9:18 AM, Tyler Pohl tylerap...@gmail.com wrote:
Can someone please tell me how to get off this mailing list? Please please
please
Well first you don't reply to an unrelated topic...
But the instructions are here:
On Thu, 13 Aug 2015 08:44:58 +0800
Patrick Lauer patr...@gentoo.org wrote:
On 08/12/15 22:38, William Hubbs wrote:
I always wondered why pkg_pretend never caught on.
Because, in a way, it triggers at the wrong point of the merge.
emerge -pv fnurk = dependencies look ok
emerge fnurk =
Hello, everyone.
The official git migration inspired some real changes in the semi-
related Git mirror [1] and Repo mirror CI [2] projects. In this mail,
I'd like to shortly summarize what changed and how to proceed forward.
TL;DR, short summary:
1. rsync-git mirror has been disabled and the
Dnia 2015-08-13, o godz. 19:13:06
Ulrich Mueller u...@gentoo.org napisał(a):
On Thu, 13 Aug 2015, Rich Freeman wrote:
On Thu, Aug 13, 2015 at 12:12 PM, Mike Frysinger vap...@gentoo.org wrote:
delete it and be done
+1
When I asked a few days ago the arugment was made that it will be
On Thu, Aug 13, 2015 at 1:13 PM, Ulrich Mueller u...@gentoo.org wrote:
On Thu, 13 Aug 2015, Rich Freeman wrote:
On Thu, Aug 13, 2015 at 12:12 PM, Mike Frysinger vap...@gentoo.org wrote:
delete it and be done
+1
When I asked a few days ago the arugment was made that it will be
expanded
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Eclass:
virtuoso.eclass is only used by dev-db/virtuoso-odbc and
dev-db/virtuoso-server. Will be removed in 30 days as well.
Packages:
# Johannes Huber johu@@gentoo.org (13 Aug 2015)
# Nepomuk removal. Announced via portage news item on 2015/08/11.
On 08/13/2015 07:29 AM, Brian Dolbec wrote:
On Thu, 13 Aug 2015 01:34:36 -0700
Zac Medico zmed...@gentoo.org wrote:
+def _task_exit(self, task):
+'''
+Remove the task from the graph, in order to expose
+more leaf nodes.
+'''
+
wireless posted on Thu, 13 Aug 2015 08:33:13 -0500 as excerpted:
On 08/12/2015 09:52 PM, Mike Frysinger wrote:
On 12 Aug 2015 18:27, Brian Dolbec wrote:
2) There is another alternate location that you can define files to
ignore locally without having to commit them to .gitignore.
Consider
On Thu, Aug 13, 2015 at 03:59:37PM -0400, Rich Freeman wrote:
On Thu, Aug 13, 2015 at 3:43 PM, Robin H. Johnson robb...@gentoo.org wrote:
The intent is that the ONLY place the keywords are expanded, will be in
the rsync export. FUTURE tense, it's not ready yet.
Will that include any case
On 13 Aug 2015 17:29, Rich Freeman wrote:
On Thu, Aug 13, 2015 at 3:55 PM, Paweł Hajdan, Jr. wrote:
I'd like to start with: kudos for the very skilfully performed migration
from CVS to git! I just committed a simple changed and it worked great.
I was curious and started exploring the repo
On Thu, Aug 13, 2015 at 7:28 PM, Robin H. Johnson robb...@gentoo.org wrote:
On Thu, Aug 13, 2015 at 03:59:37PM -0400, Rich Freeman wrote:
On Thu, Aug 13, 2015 at 3:43 PM, Robin H. Johnson robb...@gentoo.org wrote:
The intent is that the ONLY place the keywords are expanded, will be in
the
On Thu, Aug 13, 2015 at 1:42 PM, Michał Górny mgo...@gentoo.org wrote:
Please also remember to ping package maintainers. We usually do that
through @-highlights in comments. The developers who are direct package
maintainers can be referenced directly (@mgorny), while teams and
projects can be
On 13 Aug 2015 17:18, Mike Gilbert wrote:
On Wed, Aug 12, 2015 at 11:17 PM, Mike Frysinger vap...@gentoo.org wrote:
+If you are stuck with DSA keys, you can re-enable support locally by
+updating your sshd_config file with a line like so:
+ PubkeyAcceptedKeyTypes=+ssh-dss
I think
On 08/13/2015 05:28 PM, Duncan wrote:
wireless posted on Thu, 13 Aug 2015 08:33:13 -0500 as excerpted:
On 08/12/2015 09:52 PM, Mike Frysinger wrote:
On 12 Aug 2015 18:27, Brian Dolbec wrote:
2) There is another alternate location that you can define files to
ignore locally without having to
On Thu, Aug 13, 2015 at 9:55 PM, Paweł Hajdan, Jr.
phajdan...@gentoo.org wrote:
Is the historical data available now? Is it still work in progress?
Good question!
I'd all be interested in some ballpark figures about the size of such a thing.
Cheers,
Dirkjan
Dnia 2015-08-13, o godz. 22:53:11
Maxim Koltsov maksbo...@gentoo.org napisał(a):
11 авг. 2015 г. 17:33 пользователь Michał Górny mgo...@gentoo.org
написал:
Hello, everyone.
Now that we're officially on git and can officially use pull requests
to provide rapid community interaction,
On Thu, 13 Aug 2015 11:36:58 -0700
Zac Medico zmed...@gentoo.org wrote:
On 08/13/2015 02:06 AM, Alexander Berntsen wrote:
Superficially it looks OK, except a few minor details.
On 13/08/15 10:34, Zac Medico wrote:
Repos are synced in parallel (includes their post-sync hooks).
Output
11 авг. 2015 г. 17:33 пользователь Michał Górny mgo...@gentoo.org
написал:
Hello, everyone.
Now that we're officially on git and can officially use pull requests
to provide rapid community interaction, it'd be convenient to have
a little better framework for pinging package maintainers.
I'd like to start with: kudos for the very skilfully performed migration
from CVS to git! I just committed a simple changed and it worked great.
I was curious and started exploring the repo a little bit, and the
initial commit says:
This commit is the start of the NEW history.
Any historical
On Thu, Aug 13, 2015 at 3:55 PM, Paweł Hajdan, Jr.
phajdan...@gentoo.org wrote:
I'd like to start with: kudos for the very skilfully performed migration
from CVS to git! I just committed a simple changed and it worked great.
I was curious and started exploring the repo a little bit, and the
Hell with it, top posting this one ;)
Thanks, questions answered :)
On Thu, 13 Aug 2015 12:00:46 -0700
Zac Medico zmed...@gentoo.org wrote:
On 08/13/2015 07:29 AM, Brian Dolbec wrote:
On Thu, 13 Aug 2015 01:34:36 -0700
Zac Medico zmed...@gentoo.org wrote:
+ def _task_exit(self, task):
On Thu, Aug 13, 2015 at 10:36:16AM -0500, William Hubbs wrote:
I understood the usefulness of this line to some when we were using CVS
since it expanded into the ebuild revision, date, etc.
This expansion doesn't take place under git, so now I don't understand
the usefulness of this line. If
On Thu, Aug 13, 2015 at 3:43 PM, Robin H. Johnson robb...@gentoo.org wrote:
The intent is that the ONLY place the keywords are expanded, will be in
the rsync export. FUTURE tense, it's not ready yet.
Will that include any case where the string $Id$ appears in a patch file?
That is the main
On Wed, Aug 12, 2015 at 11:17 PM, Mike Frysinger vap...@gentoo.org wrote:
---
.../2015-08-13-openssh-weak-keys.en.txt| 26
++
1 file changed, 26 insertions(+)
create mode 100644
2015/2015-08-13-openssh-weak-keys/2015-08-13-openssh-weak-keys.en.txt
diff
On Thu, 13 Aug 2015 07:43:24 -0700
Brian Dolbec dol...@gentoo.org wrote:
No, there clearly should be some things that are commonly present
that should never be committed. Those common things should be in a
global .gitignore. I did not read the entire thread(s) but it seemed
there was more
On 08/13/15 02:15, Michał Górny wrote:
Dnia 2015-08-12, o godz. 22:43:24 Dean Stephens
desult...@gentoo.org napisał(a):
On 08/11/15 10:32, Michał Górny wrote:
Hello, everyone.
Now that we're officially on git and can officially use pull
requests to provide rapid community interaction,
On Thu, Aug 13, 2015 at 8:38 PM, Mike Frysinger vap...@gentoo.org wrote:
On 13 Aug 2015 17:29, Rich Freeman wrote:
On Thu, Aug 13, 2015 at 3:55 PM, Paweł Hajdan, Jr. wrote:
I'd like to start with: kudos for the very skilfully performed migration
from CVS to git! I just committed a simple
On 14 August 2015 at 07:59, Rich Freeman ri...@gentoo.org wrote:
Will that include any case where the string $Id$ appears in a patch file?
Surely that can be avoided by using a git attributes specification
that only applies to */*/*.ebuild ?
--
Kent
KENTNL -
On 13 Aug 2015 10:36, William Hubbs wrote:
I understood the usefulness of this line to some when we were using CVS
since it expanded into the ebuild revision, date, etc.
This expansion doesn't take place under git, so now I don't understand
the usefulness of this line. If I have missed
Can someone please tell me how to get off this mailing list? Please please
please
On Aug 13, 2015 8:37 AM, William Hubbs willi...@gentoo.org wrote:
All,
I understood the usefulness of this line to some when we were using CVS
since it expanded into the ebuild revision, date, etc.
This
Dnia 2015-08-13, o godz. 20:28:11
Joseph Booker j...@neoturbine.net napisał(a):
On Thu, Aug 13, 2015 at 1:42 PM, Michał Górny mgo...@gentoo.org wrote:
Please also remember to ping package maintainers. We usually do that
through @-highlights in comments. The developers who are direct
Dnia 2015-08-14, o godz. 13:55:47
Kent Fredric kentfred...@gmail.com napisał(a):
On 14 August 2015 at 07:59, Rich Freeman ri...@gentoo.org wrote:
Will that include any case where the string $Id$ appears in a patch file?
Surely that can be avoided by using a git attributes specification
All,
I understood the usefulness of this line to some when we were using CVS
since it expanded into the ebuild revision, date, etc.
This expansion doesn't take place under git, so now I don't understand
the usefulness of this line. If I have missed something, can someone
fill me in, or if it
13.08.2015 18:36, William Hubbs пишет:
All,
I understood the usefulness of this line to some when we were using CVS
since it expanded into the ebuild revision, date, etc.
This expansion doesn't take place under git, so now I don't understand
the usefulness of this line. If I have missed
This expansion doesn't take place under git, so now I don't understand
the usefulness of this line. If I have missed something, can someone
fill me in, or if it isn't useful any more can we consider removing it?
It is possible to define custom keyword expansions for $Id$ with
.gitattributes
61 matches
Mail list logo
