Re: Re : Re: [gentoo-portage-dev] Constraint-Based Dependency Solver for Portage: a prototype

On 08/01/18 03:06, Michael Lienhardt wrote: > Many thanks for the advices. I started few discussions on the forum > and will go to FOSDEM. I'll see where it will go. Consider mentioning this in #gentoo-fosdem on irc.freenode.net, which is where the Gentoo devs & users who are going to FOSDEM

Re: [gentoo-portage-dev] [PATCH] Disable dynamic-deps by default

ACK. Finally. -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander signature.asc Description: OpenPGP digital signature

Re: [gentoo-portage-dev] Constraint-Based Dependency Solver for Portage: a prototype

Unfortunately I am way too busy to even entertain looking into this in any detail. A few years ago I was hoping to work on something like this, though in Agda (or possibly in Haskell or Coq), and do work on making Portage much more modular so that you could actually pick whatever dependency

[gentoo-portage-dev] Re: [gentoo-dev] taking a break from arches stabilization

On 10/07/17 20:11, Jonas Stein wrote: > It would be so motivating to see that many user are glad about a > special package. One gets rarely feedback. Interesting idea. We could have some (separate) portage-y helper tool send a standardised email that could easily be filtered based on sender

Re: [gentoo-portage-dev] Leader election

On 06/07/17 19:25, Brian Dolbec wrote: > You can't, I declined this time around You didn't reply here. So technically you just didn't accept. ;) I vote for Zac then. -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander signature.asc Description: OpenPGP digital signature

Re: [gentoo-portage-dev] Leader election

I vote for Brian. -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander signature.asc Description: OpenPGP digital signature

Re: [gentoo-portage-dev] Leader election

On 04/07/17 22:02, Zac Medico wrote: > Thank you, I accept. > > I also nominate Brian Dolbec and Alexander Berntsen. Thank you, I accept. Do we vote here in the same thread? -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander signature.asc Description: OpenPG

[gentoo-portage-dev] Leader election & general development meeting

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Friends, It's that time of year. We're having a leader election again, as well as a general development meeting. The agenda will be updated in more detail at: https://wiki.gentoo.org/wiki/Project:Portage/Meetings Please schedule a time at:

Re: [gentoo-portage-dev] [PATCH v2] preserve-libs: handle manually removed libraries better (bug 599240)

It's OK by me then. -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander signature.asc Description: OpenPGP digital signature

Re: [gentoo-portage-dev] [PATCH] preserve-libs: handle manually removed libraries better (bug 599240)

On 09/11/16 10:05, Zac Medico wrote: > Before a package is merge +d Looks okay. What's the performance impact, if non-negligible? -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander signature.asc Description: OpenPGP digital signature

Re: [gentoo-portage-dev] [PATCH] emerge-webrsync: use gkeys to verify gpg signatures (bug 597918)

On 27/10/16 19:16, Zac Medico wrote: > Use gkeys to verify gpg signatures by default. Refresh the gentoo > snapshot signing key before signature verification, in order to > ensure that the latest revocation data is available. Add an > --insecure option which disables gpg signature verification.

Re: [gentoo-portage-dev] Leadership election

On 11/10/16 18:28, Brian Dolbec wrote: > hmm, seems I've been drafted :) OK, so Brian's the new lead. Gz. -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander signature.asc Description: OpenPGP digital signature

Re: [gentoo-portage-dev] [PATCH] repoman: add gentoo to remote-id type.

Is there an associated bug for this? The patch itself looks reasonable enough, but I prefer knowing the background for patches being deemed necessary. Also, get rid of the period in the commit message. And we seem to... mostly... agree that it should be 'component: Capitalised description', not

[gentoo-portage-dev] Leadership election

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Friends, It's that time of year. I have been lead developer for a year, so we need to have another election. I've not been very good, nor attentive enough. So if you want to elect someone else than me, I can understand that. If nobody else wants

Re: [gentoo-portage-dev] [PATCH v2] setup.py: enable libc bindings optionally (bug 594744)

LGTM. -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander signature.asc Description: OpenPGP digital signature

Re: [gentoo-portage-dev] [PATCH] setup.py: enable libc bindings optionally (bug 594744)

On 02/10/16 05:03, Zac Medico wrote: > The ebuild can use this Shouldn't "this" be documented somewhere more useful than in the commit msg? Also, the msg should mention that the libc bindings are optional in the first place. -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander

Re: [gentoo-portage-dev] [PATCH] ebuild.sh: start phases in temporary HOME if available (bug 595028)

No real opinion -- not familiar enough with this to suggest alternative solutions. Patch itself looks OK. -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander signature.asc Description: OpenPGP digital signature

Re: [gentoo-portage-dev] [PATCH] EventLoop: add run_until_complete method (bug 591760)

On 21/08/16 00:18, Zac Medico wrote: > This emulates the > asyncio.AbstractEventLoop.run_until_complete(future) interface What's that, and why are we emulating it instead of just using it? > which will make it possible to reduce latency in situations where it > is desirable for a loop to exit at

Re: [gentoo-portage-dev] [PATCH] Scheduler._terminate_tasks: purge _running_tasks (bug 425554)

Woah. I remember this bug. Nice. LGTM. -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander signature.asc Description: OpenPGP digital signature

Re: [gentoo-portage-dev] [PATCH] emerge: add --fuzzy-search and --search-similarity (bug 65566)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 LGTM. Thanks for addressing my previous concerns. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJXqE9jAAoJENQqWdRUGk8B4m8QAJyQ7AicdYPGvF8pnIsGafKf

Re: [gentoo-portage-dev] Re: [PATCH] Add emerge --autounmask-continue option (bug 582624)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 04/07/16 20:00, Zac Medico wrote: > I wasn't aware that there was an argument about that. I didn't argue it very heavily, but I do find it useful. > I'll be happy to send pushed emails. Thanks! - -- Alexander berna...@gentoo.org

Re: [gentoo-portage-dev] Re: [PATCH] Add emerge --autounmask-continue option (bug 582624)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Never mind. I see that it's already pushed. I guess this is where I continue to argue my case for "Pushed as [commit hash]" emails. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG

Re: [gentoo-portage-dev] Re: [PATCH] Add emerge --autounmask-continue option (bug 582624)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 01/07/16 18:42, Duncan wrote: > Perhaps rename the option so it makes perfectly clear the possible > consequences? Something like --autounmask-breakme, or > --auto-breakme ? No. - -- Alexander berna...@gentoo.org

Re: [gentoo-portage-dev] Enforced OpenPGP signatures

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 14/06/16 20:48, Robin H. Johnson wrote: > Please file a bug to have infra turn it on for the repos you want > (specify them in the bug). Thank you, Robin. Will do once I have some sort of ACK, or at least a long enough period without NACKs. -

[gentoo-portage-dev] Enforced OpenPGP signatures

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Friends, I saw Brian asking Michał to OpenPGP-sign his commits in IRC, to which Michał quipped that we would have if it were enforced. So perhaps we should just enforce it. Most of us do it -- but I see Zac not doing it sometimes, seemingly at

Re: [gentoo-portage-dev] [PATCH] repoman: flag URIs using http:// when https:// is available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Looks OK to me, but I'll let Brian have primary ACK on repoman for some time forward. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2

Re: [gentoo-portage-dev] New meeting

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Friends, Thank you for a nice meeting. A summary has been made available along with the full log[0]. Brian, could you upload the log to your devspace and link that instead of the bpaste? It would be nice to have them all in the same place. If you

Re: [gentoo-portage-dev] New meeting

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 07/06/16 09:48, Michał Górny wrote: >> Could you add the topic of PMS compliance patches for me? Done. >> In case the latter happens, [here's a] short note I will paste this when we begin the discussion. - -- Alexander berna...@gentoo.org

Re: [gentoo-portage-dev] New meeting

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 It seems the three of us who've replied are all available 2016-06-07 at 2pm UTC. That's 4pm for me. Check when it is in your timezone[0], and I'll see you then! And remember to update the agenda[1] with your items. [0]

Re: [gentoo-portage-dev] [PATCH 3/3] pym/portage/util/locale.py: add a C module to help check locale

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 27/05/16 16:26, Anthony G. Basile wrote: > However, this gets bogged down in implementation details and fails > with musl. Is it possible to elucidate this a bit more in a paragraph? Right now it reads a bit like "but this fails because reasons

[gentoo-portage-dev] New meeting

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Brian approached me a while back saying we need a new meeting. So let's do that. Sorry for taking so long. So set your availability[0], and add your items to the agenda[1]. [0] [1]

Re: [gentoo-portage-dev] [PATCH v2 2/2] Colorize packages in world_sets (bug 583164)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 26/05/16 17:29, Zac Medico wrote: > Looks good to me. ACK. Thank you. Pushed as 40cdc1c3f467ac94d3a966777eb6a0907c269550. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2

Re: [gentoo-portage-dev] [PATCH v2 2/2] Colorize packages in world_sets (bug 583164)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Looks OK to me, but I'll set Zac ACK it too, since he was the one commenting on the bug. For future reference, please use --in-reply-to when sending v2 patches, so that they're in the same email thread. It is also customary to write what has

Re: [gentoo-portage-dev] [PATCH 2/2] Colorize packages in world_sets (bug 583164)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 You give no justification for the first commit. This commit message has some grammar issues, so I don't know what you are trying to say in it. The bug has same relevant discussion. If you could give some reason for reverting in patch 1, and clean

Re: [gentoo-portage-dev] [PATCH] Remove unneeded native_kwargs wrapper

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Welp that took forever to read through... I didn't see anything wrong with it. So if tests pass and everything looks OK to you, go ahead and push it. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP

Re: [gentoo-portage-dev] Re: [PATCH v2] repoman: declare '-x', '--xmlparse' command line options obsolete

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 24/05/16 02:31, Duncan wrote: > No argument with obsolete here, but as long as the option is still > allowed (even if ignored) for backward compatibility, isn't > "deprecated" the usual term? I meant to ask if there is any existing precedent in

Re: [gentoo-portage-dev] [PATCH v2] repoman: declare '-x', '--xmlparse' command line options obsolete

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 When submitting v2-patches, please submit them in-reply-to=the message ID of the original thread. The patch looks OK, but I don't recall us using the "OBSOLETE" phrase in any documentation. Does anybody know any phrase we should be using instead,

[gentoo-portage-dev] [PATCH v2] news.py: Check only for major version when parsing

. Suggested-by: Ulrich Müller <u...@gentoo.org> Signed-off-by: Alexander Berntsen <berna...@gentoo.org> --- pym/portage/news.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/pym/portage/news.py b/pym/portage/news.py index 784ba70..ea1b947 100644 --- a/pym/por

Re: [gentoo-portage-dev] [PATCH] news.py: Check only for major version when parsing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 18/05/16 17:46, Zac Medico wrote: > not fnmatch.fnmatch(format_match.group(1), '1.*')): Wait, why "not"? - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2

Re: [gentoo-portage-dev] [PATCH] news.py: Check only for major version when parsing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 18/05/16 17:46, Zac Medico wrote: > if (format_match is not None and not > fnmatch.fnmatch(format_match.group(1), '1.*')): Yes! Sorry! I had made that change, but then forgotten to stage it. So sorry. It's been hell of a day, so it just slipped

[gentoo-portage-dev] [PATCH] news.py: Check only for major version when parsing

. Suggested-by: Ulrich Müller <u...@gentoo.org> Signed-off-by: Alexander Berntsen <berna...@gentoo.org> --- pym/portage/news.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pym/portage/news.py b/pym/portage/news.py index 784ba70..f52d96e 100644 --- a/pym/por

Re: [gentoo-portage-dev] [PATCH] pym/portage/util/locale.py: add a C module to check locale

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 17/05/16 14:47, Anthony G. Basile wrote: > Since this is the first python module written in C included in > portage, as a side effect, we introduce the machinary for future > modules in setup.py. Split it into two commits. - -- Alexander

Re: [gentoo-portage-dev] [PATCH] dblink: add locks for parallel-install with blockers (bug 576888)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 17/05/16 15:48, Brian Dolbec wrote: > Alexander, with 2.3.0_rc1-r1 released, I think we can re-open > portage code for more patches before the official 2.3.0 release. > We now know the split install is working, it only had the one > portage bug

Re: [gentoo-portage-dev] [PATCH] dblink: add locks for parallel-install with blockers (bug 576888)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 16/05/16 21:20, Zac Medico wrote: > Can we merge this now? Yes! - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2

Re: [gentoo-portage-dev] [PATCH v5] Colorize packages in user sets (bug 577720)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 OK then. Pushed as 739845a6eab95fbc44eab1b7b938c860563631d7. Thank you, Adam! - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2

Re: [gentoo-portage-dev] [PATCH] __eapi6_src_prepare: handle empty PATCHES array (bug 579626)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 OK. LGTM. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJXGd+fAAoJENQqWdRUGk8BRR8QAMAwVCpFeoXIfDQ3KIhecKrV

[gentoo-portage-dev] Re: [PATCH] bin/portageq: perform case-insensitive matching for maintainer email addresses

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Pushed as 94e9bbb342ec6f2eec746f7500e9b0ae86722df7, with a slightly wibbled commit message (primarily to make it shorter). Please use the ML in the future, not the alias. Thanks for the patch! - -- Alexander berna...@gentoo.org

Re: [gentoo-portage-dev] [PATCH v5] Colorize packages in user sets (bug 577720)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Definitely a huge improvement over v1. Thanks a lot for taking the time and making the effort. You've been a great contributor! I'll leave the final word to Zac, but the patch looks OK to me now. If it's OK by Zac, I'll merge it quick as. - --

Re: [gentoo-portage-dev] [PATCH] Colorize packages in user sets (bug 577720)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 20/03/16 15:33, Adam Mills wrote: > + def isUserSet(self): + return False + Furthermore, this makes no sense and needs to go. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE-

Re: [gentoo-portage-dev] [PATCH] emerge: add --search-fuzzy and --search-fuzzy-cutoff options (bug 65566)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 08/04/16 08:21, Zac Medico wrote: > Reverse? You want it to measure dissimilarity? Not sure what you > mean. Sorry, I meant reverse the *docs* to mean "find things that are at least 50% similar" rather than "cut off things that aren't above the

Re: [gentoo-portage-dev] [PATCH] emerge: add --search-fuzzy and --search-fuzzy-cutoff options (bug 65566)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This is a great idea! On 04/04/16 07:03, Zac Medico wrote: > +.BR "\-\-search\-fuzzy [ y | n ]" > +Enable or disable fuzzy search for search actions. This is likely a good place to briefly explain what a "fuzzy search" is. Also, I'm not sold on

Re: [gentoo-portage-dev] [PATCH v2] Colorize packages in user sets (bug 577720)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I'm not too sure about the isUserSets, but unless anyone else has any feedback, I'll test and merge this during the week. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2

Re: [gentoo-portage-dev] [PATCH v3] EbuildBuild: call _record_binpkg_info earlier (bug 578204)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Thanks. LGTM. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJW+3OvAAoJENQqWdRUGk8BM+wQAK1YIiKaS4itrZnJHAapQiCU

Re: [gentoo-portage-dev] [PATCH 2/2] runtests: fix output for skipped pythons

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Pushed as aa7558a93d42d73ad916eecd2c3e8c6c294fe735. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJW+lUCAAoJENQqWdRUGk8BiekQAMy3U5kBVEJozLInUenb9Saz

Re: [gentoo-portage-dev] [PATCH 1/2] cleanup: fix spaces to tabs in depgraph.py

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Pushed as 12c91bce20eeb7d6746b148b1056084a18bd8c53 Sorry for the delay. Easter break caught me by surprise. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2

Re: [gentoo-portage-dev] [PATCH] Colorize packages in user sets (bug 577720)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 20/03/16 15:33, Adam Mills wrote: > + for set_name in root_config.sets: > + if set_name == "system": > + system = >

Re: [gentoo-portage-dev] [PATCH 2/2] runtests: fix output for skipped pythons

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Replying to this email segfaulted my Thunderbird... I'll try this again: Nice! This LGMT too, and I'll commit and push it Monday with the other one unless there are any objections. However, Sergei, when you're sending related patches, please send

Re: [gentoo-portage-dev] [PATCH] dispatch-conf: fix popen UnicodeDecode error (bug 576788)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 LGTM, but remember the plan about merging repoman first. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJW5pJWAAoJENQqWdRUGk8Bk6EP/2LYCPnx+CsDAAe5I59MsVPf

Re: [gentoo-portage-dev] [PATCH] dblink: add locks for parallel-install with blockers (bug 576888)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I can't say much more than "ACK, probably makes sense" really. But please test this *a lot* before merging it. Regarding the merging of this patch, and th egencache patch that has already been released: I thought we agreed that .29 should be *only*

Re: [gentoo-portage-dev] [PATCH] bin/portageq: add a matcher to match the orphaned (maintainer-needed) packages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Thanks, Zac. I was going to push it, but it seems Brian already pushed this too. Let's try to communicate these things on the list. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version:

Re: [gentoo-portage-dev] [PATCH] bin/portageq: add a matcher to match the orphaned (maintainer-needed) packages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 06/03/16 16:12, Brian Dolbec wrote: > reviewed and dealt with this on IRC. > > final v2 patch merged... Oh OK... Göktürk, please try to avoid using multiple threads for patches. Brian, thanks for dealing with it! - -- Alexander

Re: [gentoo-portage-dev] [PATCH] getgccversion: check for clang if gcc is not found

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Shouldn't this also do a sort of "clang not found either!" type of output? - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2

Re: [gentoo-portage-dev] Wiki updates

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I wibbled the ongoing-todo-list[0] slightly. We should add any long-standing bugs to the "specific bugs" list, and we should try to come up with some low-hanging fruit to attract newcomers. [0]

Re: [gentoo-portage-dev] Wiki updates

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I have wibbled the Membership article[0]. In the process I have also slightly wibbled some of your roles on the main article[1]. If everyone could please ensure that they have the correct roles, and that my description of them are good, that would

[gentoo-portage-dev] 2.2.28

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Friends, I have added a tracker for 2.2.28[0] (and also cleaned up the 2.2.27 tracker). I've added all the bugs we've already fixed in git as blockers, and also some bugs I think we should be looking to fix for 2.2.8; some of which I'll be looking

[gentoo-portage-dev] Wiki updates

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Friends, Both for our sake and in order to attract new developers, I think we need to make sure our Wiki stuff is nice. I have updated our main Wiki substantially: https://wiki.gentoo.org/index.php?title=Project:Portage Please make sure the

Re: [gentoo-portage-dev] [PATCH] Make config update tools stand out (bug 543706)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Pushed as 3ff375e832d469f03dc922f7a30651726f86d3e0. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJWsICZAAoJENQqWdRUGk8BCV0P/iFNv3D6mla1LfycaLoraBNf

[gentoo-portage-dev] [PATCH] Be extra clear on INSTALL_MASK & dirs (bug 527004)

Signed-off-by: Alexander Berntsen <berna...@gentoo.org> X-Gentoo-Bug: 527004 X-Gentoo-Bug-url: https://bugs.gentoo.org/show_bug.cgi?id=527004 --- man/make.conf.5 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/man/make.conf.5 b/man/make.conf.5 index 1d1cfeb..4

Re: [gentoo-portage-dev] [PATCH] isolated-functions.sh: Output error message for nofatal die.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 27/01/16 23:19, Brian Dolbec wrote: > looks good, you can push it I think can't you? I added acked-by and the bug URL to the commit message and pushed it as f0ce7366b137119f087974d52ae807940e74ed56. Thanks for the patch, Ulrich! - -- Alexander

Re: [gentoo-portage-dev] [PATCH] Clarify no binary packages error (bug 573070)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Pushed as 9c9165fb9420a285e8e2c62cb9ba8eb91120cb66. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJWqgK+AAoJENQqWdRUGk8BDjcQAMIoIo80WQrqTlTN7/caw3Bn

Re: [gentoo-portage-dev] [PATCH] repoman: fix _here_doc_re to handle file redirection

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Uhm. Looks. Uhm. Brian, is this OK? - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJWnfn9AAoJENQqWdRUGk8B9GkP/RMSjepdRA84K6IG7nhCLLWC

Re: [gentoo-portage-dev] [PATCH] Print WORKDIR & D sizes in build logs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 testDoebuild (portage.tests.ebuild.test_doebuild_fd_pipes.DoebuildFdPipesTestCase)... FAIL Travelling and stuff, but I'll try to look at it later; if you haven't got to it by then. - -- Alexander berna...@gentoo.org

Re: [gentoo-portage-dev] [PATCH] Print WORKDIR & D sizes in build logs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 15/01/16 15:21, Michał Górny wrote: > You make it look like you noticed it before I pinged you about it! > :-P It was just a note for myself to fix it later or at least see to that someone else fixes it. > Looks like the test relies on the

Re: [gentoo-portage-dev] [PATCH] portage.xml.metadata: Include maintainer type per GLEP 67

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 LGTM. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJWlP7QAAoJENQqWdRUGk8BbDcP/R/nMpd6kvrRuggoaqFLB50R

Re: [gentoo-portage-dev] [PATCH] Print WORKDIR & D sizes in build logs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 LGTM. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJWlP8MAAoJENQqWdRUGk8B2lMP/0PEe5zwEQzesacPogONqsB5

Re: [gentoo-portage-dev] [Patch] Repoman rewrite stage2 modularization conversion complete

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I read through these ages ago, and I think you've incorporated my feedback from back then. But like back then, I don't have too much feedback to offer as this is certainly not an area of Portage I'm nearly as familiar with as you are. It mostly just

[gentoo-portage-dev] Re: [PATCH v3] emerge: Add --autounmask-only parameter (bug 570672)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Ta! After testing it a bit, I pushed it as 51f100e42753d6ffd3a24dfcb2ff8af0aa34966e. I hope to see more patches from you! :-] - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2

Re: [gentoo-portage-dev] [PATCH v2] emerge: Add --autounmask-only parameter

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 LGTM. Thanks for this! - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJWgmQ1AAoJENQqWdRUGk8B3qwP/itaogbVFoyxXqBHQT1aA0/X

Re: [gentoo-portage-dev] [PATCH] fs_template.gen_label: handle hash randomization

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 ACK. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJWgl+aAAoJENQqWdRUGk8BhiEP/0DYEQbbG7SmnDony8bPJ33c

Re: [gentoo-portage-dev] [PATCH v2] emerge: Add --autounmask-only parameter

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I just remembered -- did I not ask you to add a bug for this? Did you? If so, please add it to the commit message -- see the other messages for how. Just add (bug ) to the header, and X-Gentoo-Bug and X-Gentoo-Bug-url to the message. If you did

Re: [gentoo-portage-dev] [PATCH 2/2] sqlite: enable md5 validation (bug 568934)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 These two are eh probably fine. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJWgl55AAoJENQqWdRUGk8Bdk0P/1eXVvw6qq2Baz9pOBN39sQ0

Re: [gentoo-portage-dev] [PATCH v4] egencache: add --stable-mtime option

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 21/12/15 20:57, Zac Medico wrote: > Since the Manifest "stable mtime" behavior could have undiscovered > bugs This isn't exactly very motivating. "Since Foo could have bugs" applies to pretty much any Python code >10 lines. The patch itself

Re: [gentoo-portage-dev] [PATCH] flat_hash: enable md5 validation for /var/cache/edb/dep (bug 568934)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 22/12/15 08:02, Zac Medico wrote: > For forward-compatibility, add a flat_hash.mtime_md5_database > cache module which is capable of validating cache entries > containing either mtimes or md5 digests (only mtime validation was > previously

Re: [gentoo-portage-dev] [PATCH v2] flat_hash: enable md5 validation for /var/cache/edb/dep (bug 568934)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Great! Thanks. Go ahead & push. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJWeYZDAAoJENQqWdRUGk8BWy4P/jM8su6UwETWM3WeYYLQ6SwW

Re: [gentoo-portage-dev] [PATCH v2] egencache: add --stable-mtime option

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The patch looks OK. On 20/12/15 23:32, Zac Medico wrote: > Since the Manifest "stable mtime" behavior could be have > undiscovered bugs, disable it by default, and add a corresponding > egencache option. You have an English børk here -- "could be

Re: [gentoo-portage-dev] Re: [PATCH] depgraph._resolve: consider unresolved @system atoms fatal (bug 568354)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 16/12/15 04:31, Zac Medico wrote: > On 12/15/2015 12:46 PM, Zac Medico wrote: >> Since @system atoms are presumably chosen by someone who knows what >> they are doing (usually a gentoo developer), it makes sense to consider >> resolution failures

Re: [gentoo-portage-dev] [PATCH] repoman: use metadata.dtd from rsync tree if available (bug 567746)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 LGTM. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJWcWrfAAoJENQqWdRUGk8BmAsQALl6yvoA9QJBn9TcmxENI8L4

Re: [gentoo-portage-dev] [PATCH] egencache: add --stable-mtime option

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 16/12/15 06:33, Zac Medico wrote: > Disable Manifest "stable mtime" behavior by default, and add a > corresponding egencache option. This message tells me nothing about why we need to do this. - -- Alexander berna...@gentoo.org

Re: [gentoo-portage-dev] How do we want to deal with Arfrever's bunch of patches?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Thanks for cleaning up guys. It won't happen again. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJWbr83AAoJENQqWdRUGk8BksEP/3PIkgDX0EM14qwhXeSnanLt

Re: [gentoo-portage-dev] [PATCH] Add .git dir to excluded dirs in default PORTAGE_RSYNC_OPTS

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 14/12/15 04:08, NP-Hardass wrote: > like those that we recently experienced. I don't know what this is in reference too, so it should be explained better. I have no real objects on the patch, but defer the ACK to Brian. Could you have a look,

[gentoo-portage-dev] How do we want to deal with Arfrever's bunch of patches?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Resending this from an address that will actually reach the list... Friends, As I'm sure you've noticed, Arfrever pushed a bunch of unreviewed stuff. Michał reverted some of them as they were breaking changes in addition to being unreviewed (oh,

Re: [gentoo-portage-dev] [PATCH] depgraph._too_deep: fix logic when deep is True (bug 566024)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 09/12/15 07:52, Zac Medico wrote: > When deep is True and depth is an int, the method is intended to > return False What a time to be alive, people. I almost can't believe languages can be this bad. ACK; go ahead & push. - -- Alexander

Re: [gentoo-portage-dev] [PATCH] SyncManager: redirect command stderr to stdout (bug 566132)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 23/11/15 17:46, Zac Medico wrote: > Since the sync modules can call a variety of different commands, > it's hard to predict which ones will unnecessarily write to stderr. > So, the assumption here is that the process exit status is a more >

Re: [gentoo-portage-dev] [PATCH] depgraph: autounmask for conditional USE deps (bug 566704)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Woah -- nice! What's up with the pargs/kwargs stuff? I don't remember that stuff. Specifically, what does On 24/11/15 10:30, Zac Medico wrote: > + pargs, kwargs = item > + kwargs =

Re: [gentoo-portage-dev] [PATCH] SyncManager: redirect command stderr to stdout (bug 566132)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Sorry for not being up to date what this does, but the bug complains specifically about GitHub mirrors, while the patch itself seems far more invasive. Is it the case that they should *never* go to STDERR? - -- Alexander berna...@gentoo.org

[gentoo-portage-dev] Feature freeze/bugfix frenzy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Friends, Regarding EAPI 6: Let's not commit anything but bugfixes until 23rd. Then we do a .6 release, aiming at getting it stabilised. So unless there are any objections, please don't merge any non-bugfix patches until post release. Optimally,

[gentoo-portage-dev] Infra branch

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Friends, Robin (robbat2) have joined the Portage team. Welcome, Robin! He is going to launch an infra branch in order to commit necessary hotfixes or infra-specific short-term patches, etc. If possible and convenient he will hopefully get reviews

Re: [gentoo-portage-dev] [PATCH] egencache: fix results when GIT_DIR is used in the environment.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 13/11/15 18:27, Robin H. Johnson wrote: > Infra can pretty much commit to anywhere; but refrain from doing > so without somebody else reviewing our changes and stating that > they are good. zmedico did review it, and since it wasn't committed >

Re: [gentoo-portage-dev] Re: [PATCH] egencache: Delay updating Manifests until all other tasks complete

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I'm not American -- and I would say/write penultimate. I don't very much care though. Just pick one and fix the commit msg børk. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2

Re: [gentoo-portage-dev] [PATCH v4] LinkageMapELF: account for {PROVIDES,REQUIRES}_EXCLUDE (bug 565792)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Uh this probably makes sense. Anyone else know anything about this stuff? - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2

  1   2   3   >