On 22/03/18 07:31, Benda Xu wrote:
> We might be able to require GPG signed email to make a post.
Almost definitely.
But before bikeshedding that, it would be advisable to find out whether
it would be a good idea in the first place. Unless you want only
prospective developers to be able to contrib
On 20/03/18 13:17, Michael Palimaka wrote:
> Could someone please explain how this doesn't directly contradict the
> core tenets of an open and inclusive community?
It's fairly simple to produce a justification of the decision. I can
think of several ways of doing so. One is through an appeal to so
On 10/01/18 08:55, Lars Wendler wrote:
> Seems we're turning into an elitist club or something...
Gentoo has already had the reputation of being an elitist club for
years. As such I'd like to see steps to remedy this status, rather than
taking steps like this, which just exacerbates the unfortunat
On 17/12/17 20:35, Lars Wendler wrote:
>> On Sun, Dec 17, 2017 at 1:39 PM, Mike Gilbert
>> wrote:
>>> I just want to voice my opinion on this: as a developer, this
>>> policy is a royal pain in the ass.
>>>
>>> I would ask the council to please increase this limit to at
>>> least 100 KiB, prefer
On 14/12/17 17:09, David Seifert wrote:
>> So I can add tons of broken packages, sprinkled over different
>> days, hidden between other valid bumps, and can then tell people
>> they need to lastrite this stuff first and do the 30-day rain
>> dance? Come on, even for Gentoo standards, that's absolut
On 08/12/17 21:22, Andreas K. Huettel wrote:
>
> Independent of whether William now unsubscribed or not, he's now enjoying a
> lengthy (1 year until review) vacation from all Gentoo communication channels.
>
This seems like a meaningless thing to post at this point. And you might
want to conside
On 31/08/17 09:49, Vladimir Romanov wrote:
> I've attached "old" rar_v3.rar and "new" rar_v4.rar.
Works fine. :)
--
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
signature.asc
Description: OpenPGP digital signature
On 31/08/17 09:37, Vladimir Romanov wrote:
> But does it work for RAR5?
Give me a RAR5, and I can test it for you.
--
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
signature.asc
Description: OpenPGP digital signature
Just a note in case anyone is relying on this package for RAR files;
check out unar. It's LGPL, and works for e.g. RARv3.
--
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
signature.asc
Description: OpenPGP digital signature
While the PMS perhaps hasn't been an unequivocal success, it's still a
good effort with some success. I would be disappointed to see the
proposed change, and view it as a bad sign for Gentoo.
--
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
signature.asc
Description: OpenPG
On 27/05/17 18:17, Patrick Lauer wrote:
> But you do gentoo wrong, so as a user I'd like you to reconsider what
> you wrote there and maybe take a long vacation.
I too do not hate our users (in which I include myself).
Treating users as a worthless nuisance, unless they're writing ebuilds
or mana
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 17/06/16 15:58, Rich Freeman wrote:
> That could actually be generalized. I could see many types of
> bugs where the issue is with upstream, and we might want to track
> the progress as upstream implements a fix, releases it, and then it
> is sta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I *seriously* object to a RFC that affects so many people lasting
*less than 24h*.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCgAGBQJXY77iAAoJENQqWdRUGk8BCKIP/3ZG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 17/06/16 09:50, Michał Górny wrote:
> However, isn't the URL field sufficient for this?
This is useful in many cases for describing the bug and similar things
when the bug is being reported. Is it possible to have multiple URLs
sensibly in this fi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I would like to keep CONFIRMED as I use it and find it useful.
I also think that renaming UNCONFIRMED to OPEN is silly and
misleading, since any non-RESOLVED bug is indeed an open bug. I don't
have anything against renaming it to NEW, although I thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
What we have been doing in Portage so far is that when we fix it in
git, we put IN_PROGRESS + InVCS, and write a comment that links to the
commit on gitweb. Then when we actually release Portage, we consider
it to be fixed, and make it RESOLVED.
I w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 16/06/16 09:39, Daniel Campbell wrote:
> I guess what I mean is these outside developers could continue
> hacking and/or breaking things, or whatever else, without worrying
> about their "official" branch. We could have a standard that
> assumes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 16/06/16 09:34, Daniel Campbell wrote:
> There is overhead in choosing which repositories you want to
> include in your 'upstream'. Even with an automated tool like
> layman, there's maintenance overhead. We'd need another tool to
> assist in disc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 16/06/16 09:24, Daniel Campbell wrote:
> To touch on the user repo part.. can't it be as simple as adding
> one requirement to user repos that wish to be considered as
> curated?
>
> Create a "gentoo-ci" branch or something else, and the maintain
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
You've got most things right, Rich. But a couple of comments follow.
On 15/06/16 02:25, Rich Freeman wrote:
> 1. Developers wouldn't have access to all the ebuilds in the
> curated repositories. They would only have access to the ones they
> con
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 14/06/16 08:48, Daniel Campbell wrote:
> What sort of modularization are you talking about?
The cheap answer is "as much as possible.
> Would we suggest something like GNOME, KDE, XFCE, Mate, Cinnamon,
> et al getting their own overlays? dev-lang
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
In addition to what Peter Stuge (correctly) identifies as needing to
change, there also needs to be a modularisation of Gentoo-curated
package repositories.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 13/06/16 10:09, M. J. Everitt wrote:
> Excuse me .. and this thread emerged from deprecating the EXACT
> thing you are suggesting!?
I don't know what you are talking about.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 13/06/16 09:54, M. J. Everitt wrote:
> I really think someone needs to do a bit of portageq and see what
> the Tree *actually* contains
>
> Likewise .. a trek through bugzilla would also be enlightening for
> those not familiar ...
>
> On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/06/16 09:00, Michał Górny wrote:
> If you are not going to maintain your contribution, we can't
> guarantee it will be accepted. I'm certainly not interested in
> having to worry about 20 more maintainer-needed packages next month
> because som
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/06/16 18:18, Rich Freeman wrote:
> And my understanding again for Exherbo
And it is wrong again, according to an Exherbo user I talked to.
Please get your Exherbo developer to participate directly, because I
think you are having some trouble co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/06/16 17:32, Ian Stakenvicius wrote:
> On 10/06/16 03:53 AM, Alexander Berntsen wrote:
>> ... Their repositories would likely be amalgamations of our
>> curated and reviewed repositories ...
> Could you elaborate on wha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/06/16 12:38, Rich Freeman wrote:
> So, I was chatting with an Exherbo dev. Their model isn't quite
> what your earlier emails seemed to suggest (at least as I read
> it).
You should get them to reply to this thread, because...
> As I underst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/06/16 11:33, Consus wrote:
> That's great, but how are you gonna prevent nodejs-like
> clusterfuck[?]
By not being nodejs. The core repos are curated and reviewed.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/06/16 22:37, Pacho Ramos wrote:
> sys-apps/razercfg
I'm not an ebuild person, but if someone could maintain this I would
be grateful.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNATURE-
Version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/06/16 09:39, M. J. Everitt wrote:
> So forgive me for being blind .. but we were talking about going
> -away- from central, curated repositories, and now we've come full
> circle to the situation we have now with overlays, mostly
> controlled
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/06/16 22:15, Michał Górny wrote:
> Didn't you just contradict yourself? First you tell that everyone
> should have their own public repo... then you tell that we should
> merge stuff from those repos. So are you targeting split-repo
> model,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/06/16 12:28, Igor Savlook wrote:
> Ok how coordinate? Example: I install packageA in exherbo from
> repository1 and packageA denend on packageB on repository2. Now
> packageB removed from repository2 and exherbo crash on install
> package or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/06/16 12:20, Rich Freeman wrote:
> Perhaps you could explain how they actually prevent the issues I
> brought up?
You should probably ask the Exherbo developers, not me.
>
> Suppose you have 10 packages, and they each depend on zlib from a
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/06/16 12:14, Johannes Huber wrote:
> This statement is not feeded with numbers. Distrowatch tells
> something else.
I don't know what "feeded" means. Distrowatch is useless for anything
but figuring out what distros are popular among people wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/06/16 11:55, Daniel Campbell wrote:
> According to Enigmail, it expired April 19th.
I suggest you refresh your keys. My signing subkey was signed April
20th and expires in 2017.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~al
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/06/16 11:45, M. J. Everitt wrote:
> Btw, your key is showing up as expired, Alex.
It doesn't expire until next year.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/06/16 01:08, Andreas K. Huettel wrote:
> Sigh. Every 2 years somebody else comes up with the same silly
> idea.
I stopped reading your email after this sentence.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/06/16 18:15, Peter Stuge wrote:
> Do NOT - I repeat NOT - tie "user repos" to GitHub Inc.
If I were in charge or to be involved, I would not even dream about
tying users to a proprietary SaaS. That would be highly unethical in
my view.
- --
A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/06/16 17:53, james wrote:
>> DEAL?
No thanks.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCgAGBQJXWTpTAAoJENQqWdRUGk8BPAsQAM1vjeh7AzBx8yVGHcZ0U+vJ
RNoIDrF05PL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/06/16 16:53, Rich Freeman wrote:
> Do you propose that you can have cross-repo dependencies?
Sure. This works well in Exherbo using Paludis. We could do it right now
if we wanted to.
> If so that creates a lot of potential issues, even if you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/06/16 16:53, Consus wrote:
> How all those people are expected to coordinate their work?
I don't want to control this. That's up to them. It works well in
Exherbo and NixOS. But I agree that tooling to support it would be
useful.
- --
Alexand
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/06/16 16:39, Zac Medico wrote:
> The first obstacle that comes to my mind is how to discover the
> packages. There needs to be a central index of repositories which
> includes searchable metadata for all of the packages provided by
> those re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Friends,
It would be wise of us to create a novel way of involving users from
the ashes of Sunrise.
Here is my suggestion: It would be fruitful to encourage every single
Gentoo user to have their own repository. And this repository should
be public
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/06/16 13:27, James Le Cuirot wrote:
> What does that mean?
It means that it is made explicit in some way clearly visible to the
end-user.
> Take www-client/otter, for example. It's a qt5-based browser. It
> doesn't have the qt5 flag. How can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/06/16 11:27, James Le Cuirot wrote:
> I don't think that's unreasonable given that it only does that
> when qt4 and gtk3 are disabled.
It is horribly counter-intuitive. -qt5 should never result in qt5.
> Some packages require qt5 unconditional
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
There's only superficial changes required to the commit message
required -- capitalise the message, s/This changes/change/ in the
description -- it looks good otherwise.
However, I don't know whether this patch is *desired*.
Doug, do you have a bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
FWIW, I tried contacting the games team members via IRC and email a
few times over a few years, but never got even a simple "hello" out of
them. So I gave up. And I've heard several similar tales confirmed by
established developers. So maybe they're
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 16/12/15 13:39, Rich Freeman wrote:
> I don't see how this is dishonest.
You answered this yourself,
> They'll just be credited side-by-side with everybody else in once
> place.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~ale
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I agree with Mike that this isn't kosher. It just isn't honest.
On 15/12/15 20:37, William Hubbs wrote:
> Multiple entries are what I want to get away from; it is a
> nightmare to maintain, and the vcs shows far better than you or I
> ever could whi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 18/11/15 13:01, Rich Freeman wrote:
> People who run ~arch are not really end-users - they're
> contributors who have volunteered to test packages.
We are talking about people who run Gentoo stable who need to
keyword several specific packages be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 18/11/15 12:59, Rich Freeman wrote:
> Actually, what is less clear to me is how portage versioning
> actually works, or if we attach any meaning to the version numbers
> at all.
The higher number is the newer version.
- --
Alexander
berna...@gen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 18/11/15 12:23, Ulrich Mueller wrote:
> That sort of QA should take place before making a new Portage
> relaese. I was talking about marking it stable, though.
The problem we are talking about isn't making sure Portage's EAPI 6
support is bug fre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 18/11/15 12:05, Ulrich Mueller wrote:
> Only that there is no real difference to the existing situation
> when mixing stable and unstable. It is not guaranteed that all
> dependencies of an unstable package are stable, so already now
> users may h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 18/11/15 08:25, Ulrich Mueller wrote:
> - If you mix stable and unstable then you are by definition an
> advanced user, who will be able to cope with the situation. :)
This attitude is shitty, and I am willing to wager a really big bunch
of users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/11/15 14:24, Michael Palimaka wrote:
> Which workflow do you mean? Most features seem optional, allowing
> people to work as they wish.
It's been a while since I looked at it outside of GHC, so please bear
in mind these things might have chang
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
phabricator is very problematic in that it is a huge piece of PHP
software that is very difficult to change, and it's virtually
impossible to upstream your changes, unless they are simple bug fixes.
It is tailored to Facebook's workflow. Their workf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 22/09/15 15:56, Ian Stakenvicius wrote:
> This is the Portage team i assume? It seems implied but i see
> nothing explicit so i just wanted to confirm.
Yes. I merely CC-ed dev FYI.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Friends,
please set your availability[0] for our next meeting, where we will
elect team leader(s). We should probably also clear up the memberships
as most of the members haven't been active in months (some have
actually never been active at all).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 20/09/15 11:26, Jeroen Roovers wrote:
> My personal policy is to completely ignore anything Gentoo related
> that gets posted on Github.
+1.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNATURE-
V
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/09/15 15:14, Rich Freeman wrote:
> If you ask and there is no answer I wouldn't hold things up.
Michał was working on implementing EAPI6 in Portage, perhaps you
should ping him somewhere.
- --
Alexander
berna...@gentoo.org
https://secure.plai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/09/15 14:53, Rich Freeman wrote:
> I was suggesting that somebody talk to the portage developers about
> how they intend to implement EAPI6
We don't know. But our tardiness should not retard the development of
other package managers.
- --
Ale
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 21/08/15 12:58, Rich Freeman wrote:
> Somebody made the argument that sometimes having consistency
> within domains matters more than global consistency. I can buy
> that argument, but I don't think this is one of those cases.
As an old-school ga
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
- -1. The way "dedicated" is used in games ebuilds is a very established
term that all gamers know and expect to behave in a specific way. This
will mess with our users.
\
Also, this is retarded micro-management bullshit. QA doesn't need to
police e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/08/15 22:59, Aaron W. Swenson wrote:
> Users can fetch/pull from Github.
Users should not have to interface with or rely on proprietary
software to use Gentoo.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/08/15 21:38, Sergey Popov wrote:
>
>
> In short - apropriate REQUIRED_USE with setting recommended
> USE-flag(e.g. USE="+qt4 qt5" or USE="qt4 +qt5")
>
>
Strong -1.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 17/04/15 16:33, Andrew Savchenko wrote:
> The problem is double effort: previously one developer effort was
> needed, now effort is doubled at least
You have correctly identified the problem; in order to do things
properly one must do things prop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15/04/15 15:02, Peter Stuge wrote:
> the threshold to become a developer with write access to the
> gentoo repo is very high
LOL. No. It's way too low, given our review-less workflow in which any
dev can do essentially whatever they want.
- --
Al
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15/04/15 11:56, Andrew Savchenko wrote:
> frankly it looks like to me that we are just selling our freedom,
> slowly, bit by bit.
Sadly, I think most Gentoo devs are way past the point of caring.
But, for what it's worth, I agree with you comple
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
+1 for everything.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iF4EAREIAAYFAlUWwDgACgkQRtClrXBQc7XyRQEAh2fJrr9aW9kLLa+a4hmwOT80
2ucx01RUq2IGmm9P7kMA/2o/rh46QX8xrAn5lbHtjqc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 16/03/15 11:09, Nikos Chantziaras wrote:
>> On 16/03/15 11:58, Alexander Berntsen wrote:
>>> Does smplayer work with mpv?
> Version 14.9.0.6690 and up supports mpv.
Then I would encourage that we stabilise this before re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15/03/15 10:15, Ben de Groot wrote:
> # These projects have been abandoned upstream. Most mplayer2 devs have moved
> # on to media-video/mpv, and users are suggested to do the same. We have
> # media-video/baka-mplayer and media-video/smplayer ava
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 16/02/15 14:02, Alexander Berntsen wrote:
> FWIW: I'm in the "warnings are pointless, either we care about
> something (so make it an error), or we don't (so get rid of it)".
s/\./ camp./
(I accidentally a word
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
FWIW: I'm in the "warnings are pointless, either we care about
something (so make it an error), or we don't (so get rid of it)".
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/02/15 19:01, hasufell wrote:
> Jan Matejka:
>> On Fri, 16 Jan 2015 21:00:24 +0100 Luca Barbato
>> wrote:
>>> Anything written in haskell tend to be impractical to deploy.
>>
>> http://code.haskell.org/~dons/talks/dons-google-2015-01-27.pdf
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'd just like to take a few seconds to say "thank you, Brian"!
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 27/11/14 10:51, Daniel Campbell wrote:
> I have a lot of IRL things going on
Gentoo is a strange place. But let me assure you, this is real life too.
Happy hacking.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 24/11/14 02:50, Andrew Savchenko wrote:
> On Thu, 20 Nov 2014 20:16:09 -0800 Zac Medico wrote:
>>> I forgot, we have a --verbose-conflicts option already.
> Yeah, that's exactly what I need. Somehow I missed this option,
> sorry.
That's OK. I for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20/10/14 08:36, Luca Barbato wrote:
> Since gcc-4.7 there is a -std=c++11 option, do not use it since it
> breaks the ABI, resulting in a non-functional system.
Since gcc-4.7 there is a -std=c++11 option, do not use it {+yet+}
since it breaks the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Check out Linphone. Works well to Mac OS X and Microsoft Windows in my
experience. The interface is not great, but several non-technical
users have been able to use it to talk to me, so it can't be that bad
while we're waiting for Tox to mature.
Usi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Friends,
the repoman patch is reverted. And that is the end of this.
I do not have gx86 access, so if someone wants me to revert 3K commits
there, I'll need a proxy...
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 25/07/14 17:01, Ciaran McCreesh wrote:
> The reason everything is such a mess at the moment is precisely
> because we've accumulated so much "good enough" and "not thinking
> your cunning plan all the way through" that nothing is actually
> corre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 22/07/14 20:44, Kent Fredric wrote:
> So we'll probably need a repoman check that is smart enough to know
> "X is modified" and compare the DEPEND fields with the previous
> incarnation prior to commit, and then at very least, warn people
> doi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 22/07/14 20:40, Martin Vaeth wrote:
> If there is interest, I can post my patches so far. Where?
If you think these patches are useful for Portage, please send them to
dev-port...@gentoo.org.
- --
Alexander
berna...@gentoo.org
https://secure.plai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 22/07/14 09:39, Martin Vaeth wrote:
> Pacho Ramos wrote:
>>
>> Maybe this could be solved by having two kinds of revisions: -
>> One would rebuild all as usually (for example, -r1...) - The
>> other one would only regenerate VDB and wouldn't cha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 22/07/14 02:36, hasufell wrote:
> William Hubbs:
>> My concern about doing a revbump just because the deps change is
>> that the new revision has to be committed in ~arch, so we then
>> have to hit the arch teams, which we know are overworked anyw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
+1. Nice idea Manuel!
On 21/07/14 19:41, Ciaran McCreesh wrote:
> What's wrong with HOMEPAGE="()" ?
It is not very informative.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Friends,
Michał has documented the shortcomings of dynamic deps in our wiki[0].
(Thank you!) This documentation also includes two of our possible
solutions.
1. Improve dynamic-deps. This is, as Michał pointed out earlier in
this thread a pipe dream
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Please stop spamming this thread now.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iF4EAREIAAYFAlPHiMcACgkQ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 16/07/14 21:19, Denis Dupeyron wrote:
> I agree with you and Ulrich. That was a very poor choice of word
> from my part and not what I wanted to say. I didn't mean we should
> distribute distfiles without consent, but back them up to a hidden
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ulrich is right. Abandonware just means orphaned works -- i.e. the
copyright holder hasn't sued anyone yet. Gentoo should not have
anything to do with this.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15/07/14 13:36, Pacho Ramos wrote:
> It's: https://bugs.gentoo.org/show_bug.cgi?id=462118
Thank you for the info.
> The problem is that it's not clear to us how to make it
> automatically without needing to call it manually from every
> ebuild i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
# emerge postgresql-server
...
# emerge --config dev-db/postgresql-server:9.3
...
# systemctl start postgresql-server-9.3
Job for postgresql-9.3.service failed. See 'systemctl status
postgresql-9.3.service' and 'journalctl -xn' for details.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/06/14 18:45, Andrew Savchenko wrote:
> Why are you saying that git is inefficient with large projects?
Because it is.
> It was developed with efficiency in mind in the first place.
Not for big projects.
> And kernel guys will likely disagree
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/06/14 17:45, Andrew Savchenko wrote:
> I don't know why CVS is still used for Gentoo main repository,
> probably some infrastructure elements depends deeply on its
> internals, because I see of no other reason why Git is still not
> used des
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
For what it's worth, I strongly oppose using GitHub or any other SaaSS
that is not licensed using AGPL or under similar terms.
My suggestion is Phabricator, which additionally beats GitHub on
functionality by having proper code review support. I wil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/06/14 18:38, Alexey Shvetsov wrote:
>> Perhaps we could consider GitLab?
>
> Yep. Its better to have gitlab || gerrit || ReviewBoard Personaly
> i have only expirience with gerrit
>
> However this will depend on migration of gentoo-x86 to git
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/06/14 23:08, Jeroen Roovers wrote:
> You can start fixing bugs immediately. You can check out the
> sources, write patches and attach the patches to the bug reports.
> Then all it takes is someone else to review/commit the patches.
Hacking an i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 30/05/14 19:18, Tom Wijsman wrote:
> Well, this thread's problem is not severe at all; thus, no need to
> mask.
I disagree. I'm with ssuominen. Do with that information what you will...
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.ne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 30/05/14 19:11, Tom Wijsman wrote:
> Well, let's just mask the whole tree; there are wrong lines
> everywhere.
It is not a matter of quantity but severity.
$ echo "Dnoe"
$ rm -rf / --no-preserve-root
Same quantity, somewhat different severity.
1 - 100 of 155 matches
Mail list logo
