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.

Sign up for GitHub

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

Jump to bottom

Passing options to pkgng #55169

Open
darkpixel opened this issue Oct 30, 2019 · 4 comments
Open

Passing options to pkgng #55169

darkpixel opened this issue Oct 30, 2019 · 4 comments
Labels
Feature new functionality including changes to functionality and code refactors, etc. Pending-Discussion The issue or pull request needs more discussion before it can be closed or merged
Milestone
Blocked

Comments

@darkpixel
Copy link
Contributor

Description of Issue

On some of my FreeBSD hosts that have IPv6 enabled, pkgng is extremely slow. For example running pkg install py36-salt takes over 15 minutes. But if I force pkg to use IPv4 (pkg -4 install py36-salt it takes a few seconds.

There doesn't appear to be a way in salt to tell pkg.installed to pass the -4 option to pkgng.
@network-shark
Copy link
Contributor

I know this problem , but it is related to the freebsd infrastructure or anycast dns.

As a workaround can you try to set your Freebsd.conf mirror from quarterly to latest ?

For me this works well... .

Nevertheless a feature request with -4 would be cool . I'm pretty sure that not everyone want /latest
@frogunder frogunder added this to the Blocked milestone Oct 31, 2019
@frogunder frogunder added the Pending-Discussion The issue or pull request needs more discussion before it can be closed or merged label Oct 31, 2019
@cmcmarrow cmcmarrow added the Feature new functionality including changes to functionality and code refactors, etc. label Oct 31, 2019
@stale
Copy link

stale bot commented Jan 7, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.
@stale stale bot added the stale label Jan 7, 2020
@darkpixel
Copy link
Contributor Author

I really hate stalebot...
@stale
Copy link

stale bot commented Jan 7, 2020

Thank you for updating this issue. It is no longer marked as stale.
@stale stale bot removed the stale label Jan 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature new functionality including changes to functionality and code refactors, etc. Pending-Discussion The issue or pull request needs more discussion before it can be closed or merged
4 participants
@darkpixel @network-shark @frogunder @cmcmarrow