diff options
author | Repository mirror & CI <repomirrorci@gentoo.org> | 2021-03-09 07:50:42 +0000 |
---|---|---|
committer | Repository mirror & CI <repomirrorci@gentoo.org> | 2021-03-09 07:50:42 +0000 |
commit | 2c0e1d1ec9a227834c21adeac5d60b3b66e3f230 (patch) | |
tree | e2ca214154e1f4b2ddde578ce98293f481bc710f /earshark.txt | |
parent | 2021-03-09T07:30:01Z (diff) | |
download | repos-2c0e1d1ec9a227834c21adeac5d60b3b66e3f230.tar.gz repos-2c0e1d1ec9a227834c21adeac5d60b3b66e3f230.tar.bz2 repos-2c0e1d1ec9a227834c21adeac5d60b3b66e3f230.zip |
2021-03-09T07:45:01Z
Diffstat (limited to 'earshark.txt')
-rw-r--r-- | earshark.txt | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/earshark.txt b/earshark.txt index 6f5b90f53e11..b0c1423c5eaf 100644 --- a/earshark.txt +++ b/earshark.txt @@ -10,11 +10,6 @@ {'type': 'git', 'uri': 'git://github.com/Chemrat/overlay.git'}], 'status': 'unofficial'} $ pmaint sync earshark -WARNING:pkgcore:0bs1d1an repo at '/var/lib/repo-mirror-ci/sync/0bs1d1an', doesn't specify masters in metadata/layout.conf. Please explicitly set masters (use "masters =" if the repo is standalone). -WARNING:pkgcore:ag-ops repo at '/var/lib/repo-mirror-ci/sync/ag-ops', doesn't specify masters in metadata/layout.conf. Please explicitly set masters (use "masters =" if the repo is standalone). -WARNING:pkgcore:bitcoin repo at '/var/lib/repo-mirror-ci/sync/bitcoin', doesn't specify masters in metadata/layout.conf. Please explicitly set masters (use "masters =" if the repo is standalone). -WARNING:pkgcore:brave-overlay repo at '/var/lib/repo-mirror-ci/sync/brave-overlay', doesn't specify masters in metadata/layout.conf. Please explicitly set masters (use "masters =" if the repo is standalone). -WARNING:pkgcore:concaveoverlay repo at '/var/lib/repo-mirror-ci/sync/concaveoverlay', doesn't specify masters in metadata/layout.conf. Please explicitly set masters (use "masters =" if the repo is standalone). warning: Pulling without specifying how to reconcile divergent branches is discouraged. You can squelch this message by running one of the following commands sometime before your next pull: |