Hello. With portage-9999/repoman-9999 @ 246373bbe repoman shows a warning on each invocation: $ repoman -x /usr/lib64/python3.4/site-packages/portage/repository/config.py:176: UserWarning: repos.conf: sync-depth is deprecated, use clone-depth instead warnings.warn(_("repos.conf: sync-depth is deprecated," RepoMan scours the neighborhood... Note: use --include-dev (-d) to check dependencies for 'dev' profiles RepoMan sez: "If everyone were like you, I'd be out of business!" Portage doesn't produce this warning when I use it normally (emerge --sync, emerge -av foo, etc.). The most interesting thing is that I don't have 'sync-depth' setting anywhere: $ grep -q depth /etc/portage/repos.conf/* || echo 'Nope' Nope Please fix.
I can't reproduce it. What repository are you running repoman in? Do you have PORTDIR_OVERLAY set in make.conf, maybe by sourcing a layman config?
(In reply to Zac Medico from comment #1) > I can't reproduce it. What repository are you running repoman in? Do you > have PORTDIR_OVERLAY set in make.conf, maybe by sourcing a layman config? I run it in a local testing overlay. This overlay doesn't have a corresponding entry in repos.conf. I have it for years and never did any layman/repoman configuration to use it.
PORTDIR_OVERLAY is not set in any place I am aware of.
Steps to reproduce from scratch here: coacher@Photon ~ $ mkdir testrepo coacher@Photon ~ $ mkdir -p testrepo/profiles coacher@Photon ~ $ mkdir -p testrepo/metadata coacher@Photon ~ $ echo 'testrepo' > testrepo/profiles/repo_name coacher@Photon ~ $ echo 'repo-name = testrepo' >> testrepo/metadata/layout.conf coacher@Photon ~ $ echo 'masters = gentoo' >> testrepo/metadata/layout.conf coacher@Photon ~ $ echo 'thin-manifests = true' >> testrepo/metadata/layout.conf coacher@Photon ~ $ cd testrepo/ coacher@Photon ~/testrepo $ repoman -x /usr/lib64/python3.4/site-packages/portage/repository/config.py:176: UserWarning: repos.conf: sync-depth is deprecated, use clone-depth instead warnings.warn(_("repos.conf: sync-depth is deprecated," RepoMan scours the neighborhood... RepoMan sez: "If everyone were like you, I'd be out of business!" coacher@Photon ~/testrepo $
it looks like repos.conf is getting a default setting for sync-depth when there is not a repos.conf file defined? Just to confirm, that repo is not defined in repos.conf or make.conf PORTDIR_OVERLAY???
(In reply to Brian Dolbec from comment #5) > it looks like repos.conf is getting a default setting for sync-depth when > there is not a repos.conf file defined? > > Just to confirm, that repo is not defined in repos.conf or make.conf > PORTDIR_OVERLAY??? No, it's not defined. The steps above are the only steps required. No extra configuration was made.
It looks like this is caused by the following code in pym/portage/sync/modules/git/__init__.py. def check_depth(self): for attr in ('clone_depth', 'sync_depth'): self._check_depth(attr) def _check_depth(self, attr): d = getattr(self.repo, attr) # default setattr(self.repo, attr, 1) If sync_depth is unset, the setattr call defaults it to 1. If I comment out that setattr() call, the problem goes away.
Patch posted for review: https://archives.gentoo.org/gentoo-portage-dev/message/32293eca7b84e73dfdba20d21fe46e5e https://github.com/gentoo/portage/pull/126
Fixed in the master branch now: https://gitweb.gentoo.org/proj/portage.git/commit/?id=58e8b280794af7396115ea76747f0cc5fc5ab013
