Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Buildout is pulling package twice #101

Open
tyctor opened this issue Mar 20, 2022 · 2 comments
Open

Buildout is pulling package twice #101

tyctor opened this issue Mar 20, 2022 · 2 comments

Comments

@tyctor
Copy link

tyctor commented Mar 20, 2022

Hi

i have weird issue, maybe somebody can help me explain it
in my buildout.cfg i have

...
parts =
    django

auto-checkout =
    django-suit

eggs =
    django-suit

[sources]
django-suit = git https://github.com/tyctor/django-suit.git

[django]
recipe = djangorecipe
project = django_project
eggs = ${buildout:eggs}
mediaroot = /media
...

when i run buildout, django-suit is pulled from git, but in next step when django is installed also another version of django-suit is is downloaded to eggs (0.2.28 version, which is very old)

can somebody explain why this happens?
here is buildout output

mr.developer: Queued 'django-suit' for checkout.
mr.developer: Cloned 'django-suit' with git from 'https://github.com/tyctor/django-suit.git'.
Develop: '/home/tyctor/projects/django-project/src/django-suit'
Updating _mr.developer.
Updating django.
Getting distribution for 'django-suit'.
Got django-suit 0.2.28.
Versions had to be automatically picked.
The following part definition lists the versions picked:
[versions]
django-suit = 0.2.28
@reinout
Copy link
Collaborator

reinout commented Mar 23, 2022

It is a couple of years since I used buildout, but.... shouldn't there be a develop = django-suit line in the buildout section to mark it as a development egg? I'm working from memory here, so I'm not sure.

@tyctor
Copy link
Author

tyctor commented Mar 23, 2022

what i found it starting happen after i synced my django-suit forked repo with parent repo
so i reverted this merge and issue disapears
i am not sure why is this, but when i will time i will try to investigate, because i am curious about it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants