Re: [gentoo-portage-dev] [PATCH] repos.conf: support strict-misc-digests attribute (bug 600128)

On 11/24/2016 02:24 PM, Robin H. Johnson wrote: > > On Wed, Nov 23, 2016 at 11:04:54PM -0800, Zac Medico wrote: >> The current GLEP 60 draft specifies that non-strict handling of MISC >> digests should be supported. > In my followup post about how it should work, I noted that

Re: [gentoo-portage-dev] [PATCH] unpack: fix txz unpack support (bug 600660)

On 11/24/2016 11:07 AM, Brian Dolbec wrote: > On Thu, 24 Nov 2016 10:46:21 -0800 > Zac Medico <zmed...@gentoo.org> wrote: > >> Since txz unpack support was added in commit >> daa65a336102050396482f08c77524fe99e48c9f, it has been non-functional, >> as follows:

[gentoo-portage-dev] [PATCH] unpack: fix txz unpack support (bug 600660)

Since txz unpack support was added in commit daa65a336102050396482f08c77524fe99e48c9f, it has been non-functional, as follows: phase-helpers.sh: line 521: ___eapi_supports_txz: command not found unpack portage-2.3.2.txz: file format not recognized. Ignoring. Fixes: daa65a336102 ("Add tentative

Re: [gentoo-portage-dev] [PATCH] repos.conf: support strict-misc-digests attribute (bug 600128)

On 11/24/2016 12:14 AM, Brian Dolbec wrote: > On Wed, 23 Nov 2016 23:04:54 -0800 > Zac Medico <zmed...@gentoo.org> wrote: > >> This setting determines whether digests are checked for files declared >> in the Manifest with MISC type (includes ChangeLog and metadata.xml

[gentoo-portage-dev] [PATCH] repos.conf: support strict-misc-digests attribute (bug 600128)

This setting determines whether digests are checked for files declared in the Manifest with MISC type (includes ChangeLog and metadata.xml files). Defaults to true. The current GLEP 60 draft specifies that non-strict handling of MISC digests should be supported. X-Gentoo-Bug: 600128

Re: [gentoo-portage-dev] [PATCH v2] dep_zapdeps: make package selections internally consistent (bug 600346)

On 11/22/2016 08:21 AM, Brian Dolbec wrote: > On Sun, 20 Nov 2016 15:56:54 -0800 > Zac Medico <zmed...@gentoo.org> wrote: > >> When selecting packages to determine which choices have upgrades >> or downgrades relative to other choices, make the package selectio

[gentoo-portage-dev] [PATCH v2] dep_zapdeps: make package selections internally consistent (bug 600346)

When selecting packages to determine which choices have upgrades or downgrades relative to other choices, make the package selections internally consistent by choosing a package that satisfies all atoms in the choice which match a package in the same slot. Also, fix the Atom.match() method to

[gentoo-portage-dev] [PATCH] dep_zapdeps: make package selections internally consistent (bug 600346)

When selecting packages to determine which choices have upgrades or downgrades relative to other choices, make the package selections internally consistent by choosing a package that satisfies all atoms in the choice which match a package in the same slot. Also, fix the Atom.match() method to

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

On 11/10/2016 02:57 AM, Alexander Berntsen wrote: > It's OK by me then. Thanks, pushed: https://gitweb.gentoo.org/proj/portage.git/commit/?id=fb25c5d908c22bdd6868c7db44c56ef5cd459fe4 -- Thanks, Zac

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

Before a package is merged, prune any libraries from the registry that no longer exist on disk, in case they have been manually removed. This has to be done prior to merge, since after merge it is non-trivial to distinguish these files from files that have just been merged. The performance impact

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

On 11/09/2016 03:49 AM, Alexander Berntsen wrote: > On 09/11/16 10:05, Zac Medico wrote: >> Before a package is merge > +d Thanks, fixed. > Looks okay. What's the performance impact, if non-negligible? It's negligible. The relevant code already executes a couple of other time

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

Before a package is merge, prune any libraries from the registry that no longer exist on disk, in case they have been manually removed. This has to be done prior to merge, since after merge it is non-trivial to distinguish these files from files that have just been merged. X-Gentoo-Bug: 599240

Re: [gentoo-portage-dev] Vote to revert all changes related to shallow git fetch from bug 552814

On 11/07/2016 12:28 PM, Brian Dolbec wrote: > On Sun, 6 Nov 2016 11:26:06 -0800 > Zac Medico <zmed...@gentoo.org> wrote: > >> Given the performance issues introduced by `git update-index` and `git >> prune`, shallow fetch doesn't seem to be a practical default at t

Re: [gentoo-portage-dev] [PATCH v3] parse_metadata_use: apply English language preference (bug 599060)

On 11/07/2016 12:32 PM, Brian Dolbec wrote: > On Sun, 6 Nov 2016 14:18:12 -0800 > Zac Medico <zmed...@gentoo.org> wrote: > >> Descriptions may exist for multiple languages, so prefer English >> language descriptions for use.local.desc content. >> >> X

[gentoo-portage-dev] [PATCH v3] parse_metadata_use: apply English language preference (bug 599060)

Descriptions may exist for multiple languages, so prefer English language descriptions for use.local.desc content. X-Gentoo-Bug: 599060 X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=599060 --- pym/portage/xml/metadata.py | 28 +++- 1 file changed, 27

Re: [gentoo-portage-dev] [PATCH v2] parse_metadata_use: prefer first language found (bug 599060)

On 11/06/2016 12:52 PM, Michał Górny wrote: > On Sun, 6 Nov 2016 12:37:22 -0800 > Zac Medico <zmed...@gentoo.org> wrote: > >> Descriptions may exist for multiple languages, so ignore all except >> the first description found for a particular value of restrict, so >

[gentoo-portage-dev] [PATCH v2] parse_metadata_use: prefer first language found (bug 599060)

Descriptions may exist for multiple languages, so ignore all except the first description found for a particular value of restrict, so that use.local.desc content is consistent. X-Gentoo-Bug: 599060 X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=599060 --- pym/portage/xml/metadata.py

[gentoo-portage-dev] [PATCH] parse_metadata_use: prefer first language found (bug 599060)

Descriptions may exist for multiple languages, so ignore all except the first description found, so that use.local.desc content is consistent. X-Gentoo-Bug: 599060 X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=599060 --- pym/portage/xml/metadata.py | 4 +++- 1 file changed, 3

Re: [gentoo-portage-dev] [PATCH] sync: call git prune before shallow fetch (bug 599008)

On 11/06/2016 10:46 AM, Zac Medico wrote: > On 11/06/2016 01:59 AM, Michał Górny wrote: >> On Sat, 5 Nov 2016 15:56:20 -0700 >> Zac Medico <zmed...@gentoo.org> wrote: >> >>> On 11/05/2016 03:22 PM, Michał Górny wrote: >>>> On Sat, 5 Nov 2016 15

[gentoo-portage-dev] Vote to revert all changes related to shallow git fetch from bug 552814

Given the performance issues introduced by `git update-index` and `git prune`, shallow fetch doesn't seem to be a practical default at this time. In order to prepare a release that will be eligible for stabilization, I propose that we revert all of the changes related to bug 552814:

Re: [gentoo-portage-dev] [PATCH] sync: call git prune before shallow fetch (bug 599008)

On 11/06/2016 01:59 AM, Michał Górny wrote: > On Sat, 5 Nov 2016 15:56:20 -0700 > Zac Medico <zmed...@gentoo.org> wrote: > >> On 11/05/2016 03:22 PM, Michał Górny wrote: >>> On Sat, 5 Nov 2016 15:11:10 -0700 >>> Zac Medico <zmed...@gentoo.org> wrot

Re: [gentoo-portage-dev] [PATCH] sync: call git prune before shallow fetch (bug 599008)

On 11/05/2016 03:22 PM, Michał Górny wrote: > On Sat, 5 Nov 2016 15:11:10 -0700 > Zac Medico <zmed...@gentoo.org> wrote: > >> On 11/05/2016 02:50 PM, Michał Górny wrote: >>> On Sat, 5 Nov 2016 13:43:15 -0700 >>> Zac Medico <zmed...@gentoo.org>

Re: [gentoo-portage-dev] [PATCH] sync: call git prune before shallow fetch (bug 599008)

On 11/05/2016 02:50 PM, Michał Górny wrote: > On Sat, 5 Nov 2016 13:43:15 -0700 > Zac Medico <zmed...@gentoo.org> wrote: > >> This is necessary in order to avoid "There are too many unreachable >> loose objects" warnings from automatic git gc calls. >>

[gentoo-portage-dev] [PATCH] sync: call git prune before shallow fetch (bug 599008)

This is necessary in order to avoid "There are too many unreachable loose objects" warnings from automatic git gc calls. X-Gentoo-Bug: 599008 X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=599008 --- pym/portage/sync/modules/git/git.py | 6 ++ 1 file changed, 6 insertions(+) diff

Re: [gentoo-portage-dev] portage-2.3.2 stable request?

On 11/04/2016 03:55 PM, Zac Medico wrote: > On 11/04/2016 03:47 PM, Brian Dolbec wrote: >> On Fri, 4 Nov 2016 13:53:02 -0700 >> Zac Medico <zmed...@gentoo.org> wrote: >> >>> On 11/04/2016 01:43 PM, Michał Górny wrote: >>>> On Fri, 4 Nov 2016 13

Re: [gentoo-portage-dev] portage-2.3.2 stable request?

On 11/04/2016 03:47 PM, Brian Dolbec wrote: > On Fri, 4 Nov 2016 13:53:02 -0700 > Zac Medico <zmed...@gentoo.org> wrote: > >> On 11/04/2016 01:43 PM, Michał Górny wrote: >>> On Fri, 4 Nov 2016 13:19:39 -0700 >>> Zac Medico <zmed...@gentoo.org> wro

Re: [gentoo-portage-dev] portage-2.3.2 stable request?

On 11/04/2016 01:43 PM, Michał Górny wrote: > On Fri, 4 Nov 2016 13:19:39 -0700 > Zac Medico <zmed...@gentoo.org> wrote: > >> On 11/04/2016 01:14 PM, Brian Dolbec wrote: >>> On Thu, 3 Nov 2016 15:55:23 -0700 >>> Zac Medico <zmed...@gentoo.org> wrot

Re: [gentoo-portage-dev] portage-2.3.2 stable request?

On 11/04/2016 01:14 PM, Brian Dolbec wrote: > On Thu, 3 Nov 2016 15:55:23 -0700 > Zac Medico <zmed...@gentoo.org> wrote: > >> In about a week, portage-2.3.2 will be eligible for a stable request. >> >> The only potential problem that I've noticed is the complaint

Re: [gentoo-portage-dev] Re: [PATCH] _expand_new_virtuals: constrain output for dep_zapdeps (bug 597752)

On 11/03/2016 03:46 PM, Brian Dolbec wrote: > On Thu, 3 Nov 2016 13:34:22 -0700 > Zac Medico <zmed...@gentoo.org> wrote: > >> On 10/30/2016 11:15 PM, Zac Medico wrote: >>> Constrain _expand_new_virtuals output in order to avoid incorrect >>> re-ordering

[gentoo-portage-dev] portage-2.3.2 stable request?

In about a week, portage-2.3.2 will be eligible for a stable request. The only potential problem that I've noticed is the complaint about changes from bug 552814 causing issues for people using git sync with overlay filesystems, but setting sync-depth = 0 gives those users a workaround. There's

[gentoo-portage-dev] Re: [PATCH] _expand_new_virtuals: constrain output for dep_zapdeps (bug 597752)

On 10/30/2016 11:15 PM, Zac Medico wrote: > Constrain _expand_new_virtuals output in order to avoid incorrect > re-ordering of || deps in the dep_zapdeps function, as reported in > bug 597752. > > The incorrect dep_zapdeps behavior involved a problem in the

Re: [gentoo-portage-dev] [PATCH] sync: always pass -q --unmerged to git-update-index

On 11/03/2016 12:59 PM, Brian Dolbec wrote: > On Thu, 3 Nov 2016 12:29:12 -0700 > Zac Medico <zmed...@gentoo.org> wrote: > >> On 11/03/2016 12:22 PM, Mike Gilbert wrote: >>> Passing -q --unmerged prevents update-index from erroring out when >>> local fil

Re: [gentoo-portage-dev] [PATCH] sync: always pass -q --unmerged to git-update-index

On 11/03/2016 12:22 PM, Mike Gilbert wrote: > Passing -q --unmerged prevents update-index from erroring out when local > file changes are present. > > From git-update-index(1): > >-q >Quiet. If --refresh finds that the index needs an update, the >default behavior

Re: [gentoo-portage-dev] [PATCH] sync: always pass -q to git-update-index

On 11/03/2016 10:03 AM, Brian Dolbec wrote: > On Thu, 3 Nov 2016 09:10:14 -0700 > Zac Medico <zmed...@gentoo.org> wrote: > >> On 11/02/2016 11:17 PM, Brian Dolbec wrote: >>> On Wed, 2 Nov 2016 21:57:09 -0700 >>> Zac Medico <zmed...@gentoo.org> wrote: &

Re: [gentoo-portage-dev] [PATCH] sync: always pass -q to git-update-index

On 11/02/2016 11:17 PM, Brian Dolbec wrote: > On Wed, 2 Nov 2016 21:57:09 -0700 > Zac Medico <zmed...@gentoo.org> wrote: > >> On 11/02/2016 05:17 PM, Zac Medico wrote: >>> On 11/02/2016 02:09 PM, Mike Gilbert wrote: >>>> The -q opti

Re: [gentoo-portage-dev] [PATCH] sync: always pass -q to git-update-index

On 11/02/2016 05:17 PM, Zac Medico wrote: > On 11/02/2016 02:09 PM, Mike Gilbert wrote: >> The -q option allows git-update-index to succeed even if there are >> locally modified files present. >> >> X-Gentoo-Bug-URL: https://bugs.gentoo.org/552814#c58 >> --- >&g

Re: [gentoo-portage-dev] [PATCH] sync: always pass -q to git-update-index

On 11/02/2016 02:09 PM, Mike Gilbert wrote: > The -q option allows git-update-index to succeed even if there are > locally modified files present. > > X-Gentoo-Bug-URL: https://bugs.gentoo.org/552814#c58 > --- > pym/portage/sync/modules/git/git.py | 5 + > 1 file changed, 1 insertion(+), 4

[gentoo-portage-dev] [PATCH] _expand_new_virtuals: constrain output for dep_zapdeps (bug 597752)

Constrain _expand_new_virtuals output in order to avoid incorrect re-ordering of || deps in the dep_zapdeps function, as reported in bug 597752. The incorrect dep_zapdeps behavior involved a problem in the construction of the _dep_choice.cp_map dictionary inside the dep_zapdeps function, with

Re: [gentoo-portage-dev] [PATCH] [sync] Increase the default git sync-depth to 10

On 10/30/2016 03:03 PM, Michał Górny wrote: > On Sun, 30 Oct 2016 14:44:26 -0700 > Zac Medico <zmed...@gentoo.org> wrote: > >> On 10/30/2016 02:34 PM, Michał Górny wrote: >>> +The default depth of 10 was chosen as a compromise between space >>> +and bandw

Re: [gentoo-portage-dev] [PATCH] [sync] Increase the default git sync-depth to 10

On 10/30/2016 02:34 PM, Michał Górny wrote: > Increate the default git sync-depth from 1 to 10, to ensure that s/Increate/Increase/ > gentoo-mirror git clones retain at least a single original signed > commit. > --- > man/portage.5| 10 -- >

Re: [gentoo-portage-dev] [PATCH] [sync] Increase the default git sync-depth to 10

On 10/30/2016 01:42 PM, Michał Górny wrote: > On Sun, 30 Oct 2016 13:22:51 -0700 > Zac Medico <zmed...@gentoo.org> wrote: > >> On Sun, Oct 30, 2016 at 1:19 PM, Zac Medico <zmed...@gentoo.org> wrote: >>> On 10/30/2016 12:08 PM, Michał Górny wrote: >>>

Re: [gentoo-portage-dev] [PATCH] [sync] Run `git update-index --refresh` when doing shallow pulls

On 10/30/2016 12:23 PM, Michał Górny wrote: > Run `git update-index --refresh` to force proper index recheck before > running `git reset --merge` on a shallow pull. This fixes syncing on > some filesystem configurations including overlayfs on squashfs. Maybe we should use --really-refresh in case

Re: [gentoo-portage-dev] [PATCH] [sync] Increase the default git sync-depth to 10

On 10/30/2016 01:22 PM, Zac Medico wrote: > On Sun, Oct 30, 2016 at 1:19 PM, Zac Medico <zmed...@gentoo.org> wrote: >> On 10/30/2016 12:08 PM, Michał Górny wrote: >>> Increate the default git sync-depth from 1 to 10, to ensure that >>> gentoo-mirror git clones

Re: [gentoo-portage-dev] [PATCH] [sync] Increase the default git sync-depth to 10

On Sun, Oct 30, 2016 at 1:19 PM, Zac Medico <zmed...@gentoo.org> wrote: > On 10/30/2016 12:08 PM, Michał Górny wrote: >> Increate the default git sync-depth from 1 to 10, to ensure that >> gentoo-mirror git clones retain at least a single original signed >> commit. >

Re: [gentoo-portage-dev] [PATCH] [sync] Increase the default git sync-depth to 10

On 10/30/2016 12:08 PM, Michał Górny wrote: > Increate the default git sync-depth from 1 to 10, to ensure that > gentoo-mirror git clones retain at least a single original signed > commit. Why wouldn't the last commit always be signed? We'd also need to update man/portage.5 here, and it should

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

On 10/27/2016 10:38 AM, Brian Dolbec wrote: > On Thu, 27 Oct 2016 10:16:42 -0700 > Zac Medico <zmed...@gentoo.org> wrote: > >> Use gkeys to verify gpg signatures by default. Refresh the gentoo >> snapshot signing key before signature verification, in order to ensure &g

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

On 10/27/2016 11:09 AM, Alexander Berntsen wrote: > 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 d

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

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. Warn about man-in-the-middle attacks when the

Re: [gentoo-portage-dev] Leadership election

On 10/11/2016 12:06 AM, Alexander Berntsen wrote: > Right, voting. I vote for... Brian? Yeah. Brian! > I vote for Brian too. Brian! :) -- Thanks, Zac signature.asc Description: OpenPGP digital signature

Re: [gentoo-portage-dev] Leadership election

On 10/07/2016 08:09 AM, Alexander Berntsen wrote: > 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

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

The libc bindings are optional, since ctypes is used as a fallback when they are not available. The libc bindings do not support cross- compilation, therefore it is useful to be able to build them conditionally. This patch adds an option to enable them conditionally, which the ebuild can use by

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

On 10/05/2016 06:11 AM, Alexander Berntsen wrote: > 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? The new --portage-ext-modules option shows up int the output of `./setup.py

Re: [gentoo-portage-dev] Re: [PATCH] locks: use fcntl.flock if fcntl.lockf is broken (bug 595146)

On 10/01/2016 09:30 PM, Brian Dolbec wrote: > On Sat, 1 Oct 2016 17:08:46 -0700 > Zac Medico <zmed...@gentoo.org> wrote: > >> On 09/25/2016 11:44 PM, Zac Medico wrote: >>> This is needed for Windows Subsystem for Linux (WSL), as well as >>> older version

[gentoo-portage-dev] Re: [PATCH] locks: use fcntl.flock if fcntl.lockf is broken (bug 595146)

On 09/25/2016 11:44 PM, Zac Medico wrote: > This is needed for Windows Subsystem for Linux (WSL), as well as > older versions of PyPy. > > X-Gentoo-bug: 595146 > X-Gentoo-bug-url: https://bugs.gentoo.org/show_bug.cgi?id=595146 > --- > pym/

Re: [gentoo-portage-dev] [PATCH v2] AbstractEbuildProcess: disable ipc_daemon under Windows Subsystem for Linux

On Mon, Sep 26, 2016 at 3:58 PM, Kerin Millar <k...@plushkava.net> wrote: > On Sun, 25 Sep 2016 22:49:59 -0700 > Zac Medico <zmed...@gentoo.org> wrote: > >> On Thu, Sep 22, 2016 at 8:48 PM, Zac Medico <zmed...@gentoo.org> wrote: >> > On Thu

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

On Mon, Sep 26, 2016 at 8:49 AM, Alexander Berntsen wrote: > 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 > Pushed:

Re: [gentoo-portage-dev] [PATCH v2] AbstractEbuildProcess: disable ipc_daemon under Windows Subsystem for Linux

On Thu, Sep 22, 2016 at 8:48 PM, Zac Medico <zmed...@gentoo.org> wrote: > On Thu, Sep 22, 2016 at 8:23 PM, Kerin Millar <k...@plushkava.net> wrote: >> Duly updated to use any instead of ==, as recommended by Brian Dolbec. >> >> -- >> Kerin Millar <k..

Re: [gentoo-portage-dev] [PATCH v2] AbstractEbuildProcess: disable ipc_daemon under Windows Subsystem for Linux

On Thu, Sep 22, 2016 at 8:23 PM, Kerin Millar wrote: > Duly updated to use any instead of ==, as recommended by Brian Dolbec. > > -- > Kerin Millar My first choice would be to use a small test case to detect when ipc is broken, and disable it dynamically.

Re: [gentoo-portage-dev] [Patch] 1/1 New commitmsgfile "cat/pkg: " auto-substitution

On 09/15/2016 03:27 PM, Brian Dolbec wrote: > On Thu, 15 Sep 2016 14:47:31 -0700 > Zac Medico <zmed...@gentoo.org> wrote: > >> On 09/15/2016 12:50 PM, Brian Dolbec wrote: >>> >>> From 08f6d22b366c8dc2968573ebc4fd4f0401ea67b7 Mon Sep 17 00:00:00 >>

Re: [gentoo-portage-dev] [Patch] 1/1 New commitmsgfile "cat/pkg: " auto-substitution

On 09/15/2016 12:50 PM, Brian Dolbec wrote: > > From 08f6d22b366c8dc2968573ebc4fd4f0401ea67b7 Mon Sep 17 00:00:00 2001 > From: Brian Dolbec > Date: Thu, 15 Sep 2016 12:45:10 -0700 > Subject: [PATCH] repoman: Update man page and commitmsgfile option > > Use .lower() on the

Re: [gentoo-portage-dev] [PATCH 3/3] news: skip parsing if News-Item-Format is unspecified

Merged: https://gitweb.gentoo.org/proj/portage.git/commit/?id=0cb7426796b2fb082f9176b7b08d08b21b5c86bb https://gitweb.gentoo.org/proj/portage.git/commit/?id=67fcbccd1b60b599e4e5dcc97f2959164ba6a7eb https://gitweb.gentoo.org/proj/portage.git/commit/?id=216297a9a7e91e48b74ef796b6642fd8c15085fc --

Re: [gentoo-portage-dev] [PATCH v5] news: Support News-Item-Format 2.0

On 09/07/2016 10:31 PM, Mike Gilbert wrote: > Validate Display-If-Installed with EAPI 0 or 5. > Add support for trailing wildcard matching for Display-If-Profile. > > Bug: https://bugs.gentoo.org/577372 > --- > pym/portage/news.py | 50 ++ > 1 file

Re: [gentoo-portage-dev] [PATCH v4] news: Support News-Item-Format 2.0

On 09/07/2016 02:03 PM, Mike Gilbert wrote: > Validate Display-If-Installed with EAPI 0 or 5. > Add support for trailing wildcard matching for Display-If-Profile. > > Bug: https://bugs.gentoo.org/577372 > --- > pym/portage/news.py | 50 ++ > 1 file

Re: [gentoo-portage-dev] [PATCH v3] news: Support News-Item-Format 2.0

On 09/04/2016 10:04 AM, Mike Gilbert wrote: > Validate Display-If-Installed with EAPI 0 or 5. > Add support for trailing wildcard matching for Display-If-Profile. > > Bug: https://bugs.gentoo.org/577372 > --- > pym/portage/news.py | 42 ++ > 1 file

Re: [gentoo-portage-dev] [PATCH] news: Support News-Item-Format 2.0

On 09/02/2016 01:49 PM, Mike Gilbert wrote: > Display-If-Installed already supported EAPI 5 atoms. > Use fnmatch for wildcard support on Display-If-Profile. > --- > pym/portage/news.py | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/pym/portage/news.py

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

On 08/23/2016 08:40 AM, Alexander Berntsen wrote: > OK, LGTM. > Pushed: https://gitweb.gentoo.org/proj/portage.git/commit/?id=995f0f983386e2a82dbce65d4366ee7f58f59138 -- Thanks, Zac

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

On 08/22/2016 03:14 AM, Alexander Berntsen wrote: > Woah. I remember this bug. Nice. LGTM. > Pushed: https://gitweb.gentoo.org/proj/portage.git/commit/?id=d54a795615ccb769a25a0f8d6cc15ba930ec428f -- Thanks, Zac

Re: [gentoo-portage-dev] [PATCH] repoman: fix erroneous LICENSE.syntax (bug 591184)

On 08/14/2016 08:18 AM, Brian Dolbec wrote: > On Sat, 13 Aug 2016 16:00:59 -0700 > Zac Medico <zmed...@gentoo.org> wrote: > >> X-Gentoo-bug: 591184 >> X-Gentoo-bug-url: https://bugs.gentoo.org/show_bug.cgi?id=591184 >> --- >> .../pym/repoman/module

[gentoo-portage-dev] [PATCH] repoman: fix erroneous LICENSE.syntax (bug 591184)

X-Gentoo-bug: 591184 X-Gentoo-bug-url: https://bugs.gentoo.org/show_bug.cgi?id=591184 --- .../pym/repoman/modules/scan/depend/_depend_checks.py| 16 +++- 1 file changed, 7 insertions(+), 9 deletions(-) diff --git a/repoman/pym/repoman/modules/scan/depend/_depend_checks.py

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

On 08/08/2016 02:22 AM, Alexander Berntsen wrote: > LGTM. Thanks for addressing my previous concerns. Thanks, pushed: https://gitweb.gentoo.org/proj/portage.git/commit/?id=b7f0937a811ef4859333ccc45f8076dca109dc2f -- Thanks, Zac

Re: [gentoo-portage-dev] [PATCH] depgraph._serialize_tasks: improve runtime cycle handling (bug 590514)

On 08/07/2016 08:14 AM, Brian Dolbec wrote: > As usual, we are not resolver guru's, but the code changes look decent > enough :) > > LGTM > Thanks, pushed: https://gitweb.gentoo.org/proj/portage.git/commit/?id=6412205462671735f6e8b3196a780bc4b0d6a077 -- Thanks, Zac

[gentoo-portage-dev] [PATCH] depgraph._serialize_tasks: improve runtime cycle handling (bug 590514)

Previously, it was possible for _serialize_tasks to count some dependencies of a runtime cycle as part of that cycle, leading to sub-optimal merge order for these dependencies because they got grouped together with the cycle in the overall merge order. Fix it to separate these dependencies from

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

On 04/08/2016 04:33 AM, Alexander Berntsen wrote: > 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 t

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

Add --fuzzy-search option, and --search-similarity option to adjust the minimum similarity for search results (defaults to 80%). X-Gentoo-bug: 65566 X-Gentoo-bug-url: https://bugs.gentoo.org/show_bug.cgi?id=65566 --- man/emerge.1 | 14 ++ pym/_emerge/actions.py | 7 +--

Re: [gentoo-portage-dev] [PATCH v2] GitSync.update: respect sync-depth (bug 552814)

On 07/14/2016 11:43 AM, Zac Medico wrote: > On 07/14/2016 10:08 AM, Brian Dolbec wrote: >> looks fine > > Pushed: > > https://gitweb.gentoo.org/proj/portage.git/commit/?id=84413bb1dd9df322568ce25efc5b7854a43d03c7 > Now optimized to use `git reset --merge`: https:

Re: [gentoo-portage-dev] [PATCH v2] GitSync.update: respect sync-depth (bug 552814)

On 07/14/2016 10:08 AM, Brian Dolbec wrote: > looks fine Pushed: https://gitweb.gentoo.org/proj/portage.git/commit/?id=84413bb1dd9df322568ce25efc5b7854a43d03c7 -- Thanks, Zac

[gentoo-portage-dev] [PATCH v2] GitSync.update: respect sync-depth (bug 552814)

Fix updates to respect sync-depth (previously it was only respected for clone operations). Since the default merge strategy typically fails when the the depth is not unlimited, use `git fetch` followed by `git reset --hard`. X-Gentoo-Bug: 552814 X-Gentoo-Bug-url:

[gentoo-portage-dev] [PATCH] GitSync.update: respect sync-depth (bug 552814)

Fix updates to respect sync-depth (previously it was only respected for clone operations). Since the default merge strategy typically fails when the the depth is not unlimited, use `git fetch` followed by `git reset --hard`. X-Gentoo-Bug: 552814 X-Gentoo-Bug-url:

Re: [gentoo-portage-dev] [PATCH v4] portage.cache: write md5 instead of mtime (bug 568934)

On 07/13/2016 04:16 AM, Alexander Berntsen wrote: > LGTM. > > Pushed: https://gitweb.gentoo.org/proj/portage.git/commit/?id=9abbda7d054761ae6c333d3e6d420632b9658b6d -- Thanks, Zac

[gentoo-portage-dev] [PATCH v4] portage.cache: write md5 instead of mtime (bug 568934)

Change cache modules to write md5 in cache entries, instead of mtime. Since portage-2.2.27, the relevant cache modules have had the ability to read cache entries containing either md5 or mtime, therefore this change is backward-compatible with portage-2.2.27 and later. Also fix the

Re: [gentoo-portage-dev] [PATCH v3] portage.cache: write md5 instead of mtime (bug 568934)

On 07/12/2016 06:59 AM, Alexander Berntsen wrote: > The _chf_deserializers and _md5_deserializer stuff looks rather > overengineered. That stuff is not strictly required after the addition of the intelligent reconstruct_eclasses skipping in __getitem__. However, it's still good to have because

[gentoo-portage-dev] [PATCH v3] portage.cache: write md5 instead of mtime (bug 568934)

Change cache modules to write md5 in cache entries, instead of mtime. Since portage-2.2.27, the relevant cache modules have had the ability to read cache entries containing either md5 or mtime, therefore this change is backward-compatible with portage-2.2.27 and later. Also fix the

[gentoo-portage-dev] [PATCH] portage.cache: write md5 instead of mtime (bug 568934)

Change cache modules to write md5 in cache entries, instead of mtime. Since portage-2.2.27, the relevant cache modules have had the ability to read cache entries containing either md5 or mtime, therefore this change is backward-compatible with portage-2.2.27 and later. Also, fix the

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

On 07/04/2016 05:17 AM, Alexander Berntsen wrote: > 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. I wasn't aware that there was an argument about that. I'll be happy to send pushed emails. -- Thanks, Zac

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

On 07/04/2016 05:16 AM, Alexander Berntsen wrote: > Looks OK. But you've found a few bugs already. Maybe you'll find more. > I'd appreciate if you hold off until the end of the week before > pushing it confidently. I'm extremely confident in v2 of the patch. I don't expect that we'll find any

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

On 07/01/2016 03:46 PM, Zac Medico wrote: > On 07/01/2016 12:37 AM, Zac Medico wrote: >> @@ -327,6 +341,11 @@ def action_build(settings, trees, mtimedb, >> display_missing_pkg_set(root_config, e.value) >> return 1 >>

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

This option will cause emerge to automatically apply autounmask changes to configuration files, and continue to execute the specified command. If the dependency calculation is not entirely successful, then emerge will simply abort without modifying any configuration files. This sort of behavior

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

On 07/01/2016 12:37 AM, Zac Medico wrote: > @@ -327,6 +341,11 @@ def action_build(settings, trees, mtimedb, > display_missing_pkg_set(root_config, e.value) > return 1 > > + if success and mydepgraph.nee

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

On 07/01/2016 09:42 AM, Duncan wrote: > Zac Medico posted on Fri, 01 Jul 2016 08:35:26 -0700 as excerpted: > >>> But if you genuinely think this is a good idea, and someone else on the >>> team does too, I won't oppose it. We should make sure that we strongly >>>

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

On 07/01/2016 03:29 AM, Alexander Berntsen wrote: > The patch itself looks OK, but I think that this option is a bad idea > and design, and that the extra complexity isn't warranted. I know > users have asked for something similar several times, but thankfully > the users aren't the developers.

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

This option will cause emerge to automatically apply autounmask changes to configuration files, and continue to execute the specified command. If the dependency calculation is not entirely successful, then emerge will simply abort without modifying any configuration files. This sort of behavior

Re: [gentoo-portage-dev] [PATCH] repoman: Make LIVEVCS.* checks fatal

On 06/28/2016 11:30 AM, Michał Górny wrote: > Make LIVEVCS.* checks fatal to prevent people from committing ebuilds > using live eclasses instead of package.masking them afterwards by QA. > --- > repoman/pym/repoman/qa_data.py | 2 -- > 1 file changed, 2 deletions(-) > > diff --git

[gentoo-portage-dev] Re: [PATCH 2/2] depgraph: fix missed llvm update (bug 584626)

On 06/23/2016 12:38 AM, Zac Medico wrote: > @@ -2113,6 +2129,19 @@ class depgraph(object): > > self._dynamic_config._need_restart = True > > + def _upgrade_available(self, pkg): > + """ > + Detect cases w

[gentoo-portage-dev] [PATCH 1/2] Add a unit test which reproduces bug 584626

X-Gentoo-Bug: 584626 X-Gentoo-Bug-url: https://bugs.gentoo.org/show_bug.cgi?id=584626 --- .../resolver/test_slot_operator_reverse_deps.py| 109 + 1 file changed, 109 insertions(+) create mode 100644 pym/portage/tests/resolver/test_slot_operator_reverse_deps.py diff

[gentoo-portage-dev] [PATCH 2/2] depgraph: fix missed llvm update (bug 584626)

Fix check_reverse_dependencies to ignore dependencies of parent packages for which updates are desirable, and add required _want_update_pkg support for DependencyArg parents. This solves a missed llvm update by ignoring a reverse dependency from the installed instance of clang, since an update to

[gentoo-portage-dev] [PATCH] repoman: fix KeyError during manifest generation (bug 585388)

Fix Scanner not to override portdbapi._aux_cache_keys when generating manifests, since spawn_nofetch requires additional keys. Fixes: 87e32d4863f3 ("repoman: fix KeyError...during manifest generation (bug 569942)") X-Gentoo-Bug: 585388 X-Gentoo-Bug-url:

[gentoo-portage-dev] [PATCH] unmerge-backup: check BUILD_TIME of existing binary package (bug 586410)

Fix the dblink._quickpkg_dblink method to search for a binary package having identical BUILD_TIME to the installed instance. X-Gentoo-Bug: 586410 X-Gentoo-Bug-url: https://bugs.gentoo.org/show_bug.cgi?id=586410 --- pym/portage/dbapi/vartree.py | 15 +++ 1 file changed, 11

Re: [gentoo-portage-dev] [PATCH] repoman: new QA error: slot operator under '||' alternative

On 06/18/2016 01:38 PM, Brian Dolbec wrote: > Zac, what do you think? I don't see any problems except for the need to do atom.slot_operator == '=', as mentioned in my previous reply. -- Thanks, Zac

[gentoo-portage-dev] Re: [PATCH v2] repoman: new QA error: slot operator under '||' alternative

On 06/18/2016 12:27 PM, Sergei Trofimovich wrote: > + if in_any_of and atom.slot_operator: > + qatracker.add_error("dependency.badslotop", > relative_path + > + ": %s: '%s' uses ':=' slot operator under '||' > dep clause." % > +

[gentoo-portage-dev] Re: [PATCH v2] repoman/modules/.../profile.py: typo in docstring s/dependancy/dependency/

On 06/18/2016 12:27 PM, Sergei Trofimovich wrote: > From: Sergei Trofimovich > > Signed-off-by: Sergei Trofimovich > --- > V2: updated subject > repoman/pym/repoman/modules/scan/depend/profile.py | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-)

<    6   7   8   9   10   11   12   13   14   15   >