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

Feature request: add --force key to "repo add" function #83

Closed
netflash opened this Issue Jul 16, 2014 · 6 comments

Comments

Projects
None yet
3 participants
@netflash

netflash commented Jul 16, 2014

Hi, Andrey.

Is it possible to add some "-force" key to "re-add" package to repository.

Now, when the package is the same - it works fine, but when everything (name, version, etc.) except contents of the package is the same - aptly generate error 'conflict package'

@smira

This comment has been minimized.

Show comment
Hide comment
@smira

smira Jul 16, 2014

Member

@netflash, you can't add packages with same name, version, arch and different content to one repo (because you can't publish such repo). Are you actually trying to replace package?

Member

smira commented Jul 16, 2014

@netflash, you can't add packages with same name, version, arch and different content to one repo (because you can't publish such repo). Are you actually trying to replace package?

@netflash

This comment has been minimized.

Show comment
Hide comment
@netflash

netflash Jul 16, 2014

@smira Yes, I try to replace package.
I know, that I can do "repo remove", but for my issue it's not the best option.

netflash commented Jul 16, 2014

@smira Yes, I try to replace package.
I know, that I can do "repo remove", but for my issue it's not the best option.

@smira

This comment has been minimized.

Show comment
Hide comment
@smira

smira Jul 16, 2014

Member

I think this would be good feature, something like aptly repo add --replace file.deb

Member

smira commented Jul 16, 2014

I think this would be good feature, something like aptly repo add --replace file.deb

@divanikus

This comment has been minimized.

Show comment
Hide comment
@divanikus

divanikus Jul 31, 2014

Currently, I'm doing so by deleting and re-adding package. But then I try to publish repo, aptly fails complaining about conflict.

divanikus commented Jul 31, 2014

Currently, I'm doing so by deleting and re-adding package. But then I try to publish repo, aptly fails complaining about conflict.

@smira smira modified the milestones: v0.7, v0.8 Aug 4, 2014

@smira smira added the enhancement label Aug 4, 2014

@smira

This comment has been minimized.

Show comment
Hide comment
@smira

smira Aug 4, 2014

Member

@divanikus, publishing conflict is related to #65.

Member

smira commented Aug 4, 2014

@divanikus, publishing conflict is related to #65.

smira added a commit to aptly-dev/aptly-bash-completion that referenced this issue Sep 1, 2014

smira added a commit to aptly-dev/aptly-dev.github.io that referenced this issue Sep 1, 2014

@smira

This comment has been minimized.

Show comment
Hide comment
@smira

smira Sep 1, 2014

Member

New flag -force-replace has been added in master.

Member

smira commented Sep 1, 2014

New flag -force-replace has been added in master.

@smira smira closed this Sep 1, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment