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

Unable to run winrepo.update_git_repos #35993

Closed
jbouse opened this issue Sep 1, 2016 · 14 comments
Closed

Unable to run winrepo.update_git_repos #35993

jbouse opened this issue Sep 1, 2016 · 14 comments
Labels
info-needed waiting for more info
Milestone
Blocked

Comments

@jbouse
Copy link
Contributor

jbouse commented Sep 1, 2016

Description of Issue/Question

Running salt-run winrepo.update_git_repos is not working to populate the winrepo.

Setup

All default values using the pygit2 gitfs_provider

Steps to Reproduce Issue

Simply run salt-run winrepo.update_git_repos

~# salt-run winrepo.update_git_repos
[WARNING ] /usr/lib/python2.7/dist-packages/salt/grains/core.py:1493: DeprecationWarning: The "osmajorrelease" will be a type of an integer.

[ERROR   ] Error occured fetching winrepo remote 'https://github.com/saltstack/salt-winrepo.git': Failed to resolve address for https: Name or service not known
[ERROR   ] Failed to checkout master from winrepo remote 'https://github.com/saltstack/salt-winrepo.git': remote ref does not exist
[ERROR   ] Error occured fetching winrepo remote 'https://github.com/saltstack/salt-winrepo-ng.git': Failed to resolve address for https: Name or service not known
[ERROR   ] Failed to checkout master from winrepo remote 'https://github.com/saltstack/salt-winrepo-ng.git': remote ref does not exist

Actual DNS resolution doesn't appear to be an issue:

~# host github.com
github.com has address 192.30.253.112
github.com mail is handled by 5 ALT2.ASPMX.L.GOOGLE.COM.
github.com mail is handled by 10 ALT3.ASPMX.L.GOOGLE.COM.
github.com mail is handled by 10 ALT4.ASPMX.L.GOOGLE.COM.
github.com mail is handled by 5 ALT1.ASPMX.L.GOOGLE.COM.
github.com mail is handled by 1 ASPMX.L.GOOGLE.COM.

Performing a normal git clone WINREPO_URL works fine from the host

Output from running with -l trace option

[DEBUG   ] Reading configuration from /etc/salt/master
[DEBUG   ] Including configuration from '/etc/salt/master.d/engine.conf'
[DEBUG   ] Reading configuration from /etc/salt/master.d/engine.conf
[DEBUG   ] Including configuration from '/etc/salt/master.d/f_defaults.conf'
[DEBUG   ] Reading configuration from /etc/salt/master.d/f_defaults.conf
[DEBUG   ] Including configuration from '/etc/salt/master.d/lxc_profiles.conf'
[DEBUG   ] Reading configuration from /etc/salt/master.d/lxc_profiles.conf
[DEBUG   ] Including configuration from '/etc/salt/master.d/reactor.conf'
[DEBUG   ] Reading configuration from /etc/salt/master.d/reactor.conf
[DEBUG   ] Using cached minion ID from /etc/salt/minion_id: salt01.xxxx.xxxx
[TRACE   ] None of the required configuration sections, 'logstash_udp_handler' and 'logstash_zmq_handler', were found in the configuration. Not loading the Logstash logging handlers module.
[TRACE   ] The required configuration section, 'fluent_handler', was not found the in the configuration. Not loading the fluent logging handlers module.
[DEBUG   ] Configuration file path: /etc/salt/master
[WARNING ] Insecure logging configuration detected! Sensitive data may be logged.
[DEBUG   ] LazyLoaded winrepo.update_git_repos
[DEBUG   ] Reading configuration from /etc/salt/master
[DEBUG   ] Including configuration from '/etc/salt/minion.d/_schedule.conf'
[DEBUG   ] Reading configuration from /etc/salt/minion.d/_schedule.conf
[DEBUG   ] Including configuration from '/etc/salt/minion.d/f_defaults.conf'
[DEBUG   ] Reading configuration from /etc/salt/minion.d/f_defaults.conf
[DEBUG   ] Including configuration from '/etc/salt/minion.d/returners.conf'
[DEBUG   ] Reading configuration from /etc/salt/minion.d/returners.conf
[DEBUG   ] Using cached minion ID from /etc/salt/minion_id: salt01.xxxx.xxxx
[DEBUG   ] Reading configuration from /etc/salt/master
[DEBUG   ] Including configuration from '/etc/salt/master.d/engine.conf'
[DEBUG   ] Reading configuration from /etc/salt/master.d/engine.conf
[DEBUG   ] Including configuration from '/etc/salt/master.d/f_defaults.conf'
[DEBUG   ] Reading configuration from /etc/salt/master.d/f_defaults.conf
[DEBUG   ] Including configuration from '/etc/salt/master.d/lxc_profiles.conf'
[DEBUG   ] Reading configuration from /etc/salt/master.d/lxc_profiles.conf
[DEBUG   ] Including configuration from '/etc/salt/master.d/reactor.conf'
[DEBUG   ] Reading configuration from /etc/salt/master.d/reactor.conf
[TRACE   ] Loading core.hwaddr_interfaces grain
[TRACE   ] Loading core.hostname grain
[TRACE   ] Loading core.get_master grain
[TRACE   ] Loading core.pythonversion grain
[TRACE   ] Loading core.path grain
[TRACE   ] Loading core.get_server_id grain
[TRACE   ] Loading core.saltversion grain
[TRACE   ] Loading core.saltpath grain
[TRACE   ] Loading core.pythonexecutable grain
[TRACE   ] Loading core.ip_fqdn grain
[TRACE   ] Loading core.dns grain
[TRACE   ] Loading core.ip6_interfaces grain
[TRACE   ] Loading core.ip4_interfaces grain
[TRACE   ] Loading core.append_domain grain
[TRACE   ] Loading core.os_data grain
[WARNING ] /usr/lib/python2.7/dist-packages/salt/grains/core.py:1493: DeprecationWarning: The "osmajorrelease" will be a type of an integer.

[TRACE   ] Loading core.zmqversion grain
[TRACE   ] Loading core.saltversioninfo grain
[TRACE   ] Loading core.pythonpath grain
[TRACE   ] Loading core.id_ grain
[TRACE   ] Loading core.locale_info grain
[TRACE   ] Loading core.get_machine_id grain
[TRACE   ] Loading core.ip_interfaces grain
[TRACE   ] Device fd0 reports itself as an HDD
[TRACE   ] Device sda reports itself as an HDD
[TRACE   ] Device sr0 reports itself as an HDD
[TRACE   ] Device dm-0 reports itself as an HDD
[TRACE   ] Device dm-1 reports itself as an HDD
[TRACE   ] Device dm-2 reports itself as an HDD
[TRACE   ] Device loop0 reports itself as an HDD
[TRACE   ] Device loop1 reports itself as an HDD
[TRACE   ] Device loop2 reports itself as an HDD
[TRACE   ] Device loop3 reports itself as an HDD
[TRACE   ] Device loop4 reports itself as an HDD
[TRACE   ] Device loop5 reports itself as an HDD
[TRACE   ] Device loop6 reports itself as an HDD
[TRACE   ] Device loop7 reports itself as an HDD
[DEBUG   ] MasterEvent PUB socket URI: /var/run/salt/master/master_event_pub.ipc
[DEBUG   ] MasterEvent PULL socket URI: /var/run/salt/master/master_event_pull.ipc
[DEBUG   ] Initializing new IPCClient for path: /var/run/salt/master/master_event_pull.ipc
[TRACE   ] IPCClient: Connecting to socket: /var/run/salt/master/master_event_pull.ipc
[DEBUG   ] Sending event - data = {'fun': 'runner.winrepo.update_git_repos', 'fun_args': [], 'jid': '20160901150311705527', 'user': 'sudo_jbouse', '_stamp': '2016-09-01T15:03:12.629467'}
[TRACE   ] Error loading runners.nacl: libnacl import error, perhaps missing python libnacl package
[DEBUG   ] pygit2 winrepo_provider enabled
[DEBUG   ] Set update lock for winrepo remote 'https://github.com/saltstack/salt-winrepo.git'
[DEBUG   ] Fetching winrepo remote 'https://github.com/saltstack/salt-winrepo.git'
[ERROR   ] Error occured fetching winrepo remote 'https://github.com/saltstack/salt-winrepo.git': Failed to resolve address for https: Name or service not known
[DEBUG   ] Removed update lock for winrepo remote 'https://github.com/saltstack/salt-winrepo.git'
[ERROR   ] Failed to checkout master from winrepo remote 'https://github.com/saltstack/salt-winrepo.git': remote ref does not exist
[DEBUG   ] Set update lock for winrepo remote 'https://github.com/saltstack/salt-winrepo-ng.git'
[DEBUG   ] Fetching winrepo remote 'https://github.com/saltstack/salt-winrepo-ng.git'
[ERROR   ] Error occured fetching winrepo remote 'https://github.com/saltstack/salt-winrepo-ng.git': Failed to resolve address for https: Name or service not known
[DEBUG   ] Removed update lock for winrepo remote 'https://github.com/saltstack/salt-winrepo-ng.git'
[ERROR   ] Failed to checkout master from winrepo remote 'https://github.com/saltstack/salt-winrepo-ng.git': remote ref does not exist
[DEBUG   ] LazyLoaded nested.output
[TRACE   ] data = {}
[DEBUG   ] Sending event - data = {'fun_args': [], 'jid': '20160901150311705527', 'return': {}, 'success': True, '_stamp': '2016-09-01T15:03:12.664199', 'user': 'sudo_jbouse', 'fun': 'runner.winrepo.update_git_repos'}
[DEBUG   ] LazyLoaded local_cache.prep_jid
[INFO    ] Runner completed: 20160901150311705527
[DEBUG   ] Runner return: {}

Versions Report

Salt Version:
           Salt: 2016.3.3

Dependency Versions:
           cffi: 1.7.0
       cherrypy: Not Installed
       dateutil: 2.4.2
          gitdb: 0.6.4
      gitpython: 2.0.5
          ioflo: Not Installed
         Jinja2: 2.8
        libgit2: 0.24.0
        libnacl: Not Installed
       M2Crypto: Not Installed
           Mako: Not Installed
   msgpack-pure: Not Installed
 msgpack-python: 0.4.8
   mysql-python: 1.3.7
      pycparser: 2.14
       pycrypto: 2.6.1
         pygit2: 0.24.1
         Python: 2.7.12+ (default, Aug  4 2016, 20:04:34)
   python-gnupg: Not Installed
         PyYAML: 3.11
          PyZMQ: 15.2.0
           RAET: Not Installed
          smmap: 0.9.0
        timelib: Not Installed
        Tornado: 4.4.1
            ZMQ: 4.1.5

System Versions:
           dist: debian stretch/sid
        machine: x86_64
        release: 4.6.0-1-amd64
         system: Linux
        version: debian stretch/sid

Also same behavior:

Salt Version:
           Salt: 2016.3.3

Dependency Versions:
           cffi: 1.5.2
       cherrypy: Not Installed
       dateutil: 2.4.2
          gitdb: 0.6.4
      gitpython: 1.0.1
          ioflo: Not Installed
         Jinja2: 2.8
        libgit2: 0.24.0
        libnacl: Not Installed
       M2Crypto: 0.21.1
           Mako: 1.0.3
   msgpack-pure: Not Installed
 msgpack-python: 0.4.6
   mysql-python: Not Installed
      pycparser: 2.14
       pycrypto: 2.6.1
         pygit2: 0.24.0
         Python: 2.7.12 (default, Jul  1 2016, 15:12:24)
   python-gnupg: Not Installed
         PyYAML: 3.11
          PyZMQ: 15.2.0
           RAET: Not Installed
          smmap: 0.9.0
        timelib: Not Installed
        Tornado: 4.2.1
            ZMQ: 4.1.4

System Versions:
           dist: Ubuntu 16.04 xenial
        machine: x86_64
        release: 4.6.5-x86_64-linode71
         system: Linux
        version: Ubuntu 16.04 xenial
@Ch3LL
Copy link
Contributor

Ch3LL commented Sep 1, 2016

@jbouse I'm having a hard time replicating this .Did you just see htis after upgrading to 2016.3.3. Di you just recently upgrade pygit2?

@Ch3LL Ch3LL added the info-needed waiting for more info label Sep 1, 2016
@Ch3LL Ch3LL added this to the Blocked milestone Sep 1, 2016
@lubyou
Copy link
Contributor

lubyou commented Sep 2, 2016 •
edited
Loading

I am having a similar problem.

I did not use the feature before, I only tried it after upgrading ubuntu to 16.04 and salt to 2016.3.3.
This is also the first time I installed python-pygit2.

[DEBUG   ] Reading configuration from /etc/salt/master
[DEBUG   ] Using cached minion ID from /etc/salt/minion_id: salt.xxxxxx.xxx
[TRACE   ] None of the required configuration sections, 'logstash_udp_handler' and 'logstash_zmq_handler', were found in the configuration. Not loading the Logstash logging handlers module.
[TRACE   ] The required configuration section, 'fluent_handler', was not found the in the configuration. Not loading the fluent logging handlers module.
[DEBUG   ] Configuration file path: /etc/salt/master
[WARNING ] Insecure logging configuration detected! Sensitive data may be logged.
[DEBUG   ] LazyLoaded winrepo.update_git_repos
[DEBUG   ] Reading configuration from /etc/salt/master
[DEBUG   ] Using cached minion ID from /etc/salt/minion_id: salt.xxxxxx.xxx
[DEBUG   ] Reading configuration from /etc/salt/master
[TRACE   ] Loading core.hwaddr_interfaces grain
[TRACE   ] Loading core.hostname grain
[TRACE   ] Loading core.get_master grain
[TRACE   ] Loading core.pythonversion grain
[TRACE   ] Loading core.path grain
[TRACE   ] Loading core.get_server_id grain
[TRACE   ] Loading core.saltversion grain
[TRACE   ] Loading core.saltpath grain
[TRACE   ] Loading core.pythonexecutable grain
[TRACE   ] Loading core.ip_fqdn grain
[TRACE   ] Loading core.dns grain
[TRACE   ] Loading core.ip6_interfaces grain
[TRACE   ] Loading core.ip4_interfaces grain
[TRACE   ] Loading core.append_domain grain
[TRACE   ] Loading core.os_data grain
[TRACE   ] 'virt-what' could not be found in the following search path: '['/usr/local/sbin', '/usr/local/bin', '/usr/sbin', '/usr/bin', '/sbin', '/bin
```', '/usr/games', '/usr/local/games']'
[DEBUG   ] Please install 'virt-what' to improve results of the 'virtual' grain.
[WARNING ] /usr/lib/python2.7/dist-packages/salt/grains/core.py:1493: DeprecationWarning: The "osmajorrelease" will be a type of an integer.

[TRACE   ] Loading core.zmqversion grain
[TRACE   ] Loading core.saltversioninfo grain
[TRACE   ] Loading core.pythonpath grain
[TRACE   ] Loading core.id_ grain
[TRACE   ] Loading core.locale_info grain
[TRACE   ] Loading core.get_machine_id grain
[TRACE   ] Loading core.ip_interfaces grain
[TRACE   ] Device fd0 reports itself as an HDD
[TRACE   ] Device sda reports itself as an HDD
[TRACE   ] Device sr0 reports itself as an HDD
[TRACE   ] Device ram0 reports itself as an HDD
[TRACE   ] Device ram1 reports itself as an HDD
[TRACE   ] Device ram2 reports itself as an HDD
[TRACE   ] Device ram3 reports itself as an HDD
[TRACE   ] Device ram4 reports itself as an HDD
[TRACE   ] Device ram5 reports itself as an HDD
[TRACE   ] Device ram6 reports itself as an HDD
[TRACE   ] Device ram7 reports itself as an HDD
[TRACE   ] Device ram8 reports itself as an HDD
[TRACE   ] Device ram9 reports itself as an HDD
[TRACE   ] Device loop0 reports itself as an HDD
[TRACE   ] Device loop1 reports itself as an HDD
[TRACE   ] Device loop2 reports itself as an HDD
[TRACE   ] Device loop3 reports itself as an HDD
[TRACE   ] Device loop4 reports itself as an HDD
[TRACE   ] Device loop5 reports itself as an HDD
[TRACE   ] Device loop6 reports itself as an HDD
[TRACE   ] Device loop7 reports itself as an HDD
[TRACE   ] Device ram10 reports itself as an HDD
[TRACE   ] Device ram11 reports itself as an HDD
[TRACE   ] Device ram12 reports itself as an HDD
[TRACE   ] Device ram13 reports itself as an HDD
[TRACE   ] Device ram14 reports itself as an HDD
[TRACE   ] Device ram15 reports itself as an HDD
[DEBUG   ] MasterEvent PUB socket URI: /var/run/salt/master/master_event_pub.ipc
[DEBUG   ] MasterEvent PULL socket URI: /var/run/salt/master/master_event_pull.ipc
[DEBUG   ] Initializing new IPCClient for path: /var/run/salt/master/master_event_pull.ipc
[TRACE   ] IPCClient: Connecting to socket: /var/run/salt/master/master_event_pull.ipc
[DEBUG   ] Sending event - data = {'fun': 'runner.winrepo.update_git_repos', 'fun_args': [], 'jid': '20160902020528270239', 'user': 'sudo_xxx', '_stamp': '2016-09-02T00:05:28.518602'}
[TRACE   ] Error loading runners.nacl: libnacl import error, perhaps missing python libnacl package
[DEBUG   ] pygit2 winrepo_provider enabled
[DEBUG   ] Set update lock for winrepo remote 'https://github.com/saltstack/salt-winrepo.git'
[DEBUG   ] Fetching winrepo remote 'https://github.com/saltstack/salt-winrepo.git'
[ERROR   ] Error occured fetching winrepo remote 'https://github.com/saltstack/salt-winrepo.git': Failed to resolve address for https: Name or service not known
[DEBUG   ] Removed update lock for winrepo remote 'https://github.com/saltstack/salt-winrepo.git'
[ERROR   ] Failed to checkout master from winrepo remote 'https://github.com/saltstack/salt-winrepo.git': remote ref does not exist
[DEBUG   ] Set update lock for winrepo remote 'https://github.com/saltstack/salt-winrepo-ng.git'
[DEBUG   ] Fetching winrepo remote 'https://github.com/saltstack/salt-winrepo-ng.git'
[ERROR   ] Error occured fetching winrepo remote 'https://github.com/saltstack/salt-winrepo-ng.git': Failed to resolve address for https: Name or service not known
[DEBUG   ] Removed update lock for winrepo remote 'https://github.com/saltstack/salt-winrepo-ng.git'
[DEBUG   ] Set update lock for winrepo remote 'git@git.xxxxxx.xxx:salt/salt-winrepo.git'
[DEBUG   ] Fetching winrepo remote 'git@git.xxxxxx.xxx:salt/salt-winrepo.git'
[DEBUG   ] winrepo remote 'git@git.xxxxxx.xxx:salt/salt-winrepo.git' is up-to-date
[DEBUG   ] pygit2 does not support detecting stale refs for authenticated remotes, saltenvs will not reflect branches/tags removed from remote 'git@git.xxxxxx.xxx:salt/salt-winrepo.git'
[DEBUG   ] Removed update lock for winrepo remote 'git@git.xxxxxx.xxx:salt/salt-winrepo.git'
[ERROR   ] Failed to checkout master from winrepo remote 'https://github.com/saltstack/salt-winrepo-ng.git': remote ref does not exist
[ERROR   ] Failed to checkout master from winrepo remote 'git@git.xxxxxx.xxx:salt/salt-winrepo.git': remote ref does not exist
[DEBUG   ] LazyLoaded nested.output
[TRACE   ] data = {}
[DEBUG   ] Sending event - data = {'fun_args': [], 'jid': '20160902020528270239', 'return': {}, 'success': True, '_stamp': '2016-09-02T00:05:29.164050', 'user': 'sudo_xxx', 'fun': 'runner.winrepo.update_git_repos'}
[DEBUG   ] LazyLoaded local_cache.prep_jid
[INFO    ] Runner completed: 20160902020528270239
[DEBUG   ] Runner return: {}

Salt Version:
           Salt: 2016.3.3

Dependency Versions:
           cffi: 1.5.2
       cherrypy: Not Installed
       dateutil: 2.4.2
          gitdb: 0.6.4
      gitpython: 1.0.1
          ioflo: Not Installed
         Jinja2: 2.8
        libgit2: 0.24.0
        libnacl: Not Installed
       M2Crypto: Not Installed
           Mako: 1.0.3
   msgpack-pure: Not Installed
 msgpack-python: 0.4.6
   mysql-python: Not Installed
      pycparser: 2.14
       pycrypto: 2.6.1
         pygit2: 0.24.0
         Python: 2.7.12 (default, Jul  1 2016, 15:12:24)
   python-gnupg: Not Installed
         PyYAML: 3.11
          PyZMQ: 15.2.0
           RAET: Not Installed
          smmap: 0.9.0
        timelib: Not Installed
        Tornado: 4.2.1
            ZMQ: 4.1.4

System Versions:
           dist: Ubuntu 16.04 xenial
        machine: x86_64
        release: 4.4.0-36-generic
         system: Linux
        version: Ubuntu 16.04 xenial

@jbouse
Copy link
Contributor Author

jbouse commented Sep 2, 2016

@Ch3LL It worked with 2016.3.2 using GitPython on Debian 8 (Jessie) and Ubuntu 14.04 LTS. I just upgraded to Debian testing (Stretch) and Ubuntu 16.04 LTS in order to enable pygit2 for GitFS support since you can't use the privkey/pubkey options without pygit2.

When I tried to run the winrepo.update_git_repos this afternoon it failed as I documented so I went ahead and upgraded to 2016.3.3 to see if that would fix it but there was no change in outcome.

@jbouse
Copy link
Contributor Author

jbouse commented Sep 2, 2016

@Ch3LL My Salt Master configuration is managed using a fork of the salt-formula and being fed my pillar data. I don't change any of the winrepo related configuration settings and even though I specify the gitfs_provider to pygit2 I believe if I'm not mistaken that's the default provided it's available.

@Ch3LL
Copy link
Contributor

Ch3LL commented Sep 2, 2016

@jbouse and @lubyou I think this might be related to libgit2. I found this issue: libgit2/libgit2#3786 How did you install libgit2? If you try the rebuild suggestions in that post does it work?

Also @jbouse can you try installing pkg-config. Our documentation says the following:

If pygit2 is not packaged for the platform on which the Master is running, the pygit2 website has installation instructions here. Keep in mind however that following these instructions will install libgit2 and pygit2 without system packages. Additionally, keep in mind that SSH authentication in pygit2 requires libssh2 (not libssh) development libraries to be present before libgit2 is built. On some Debian-based distros pkg-config is also required to link libgit2 with libssh2.

@Ch3LL
Copy link
Contributor

Ch3LL commented Sep 2, 2016

I also found this issue libgit2/pygit2#573 which might be useful for your situation to make sure libgit2 is functioning properly.

@lubyou
Copy link
Contributor

lubyou commented Sep 2, 2016

@Ch3LL it seems that libgit2 is indeed built without openssl on Ubuntu 16.04.
Rebuilding it with openssl support did the trick.

Thank you for your help!

@Ch3LL
Copy link
Contributor

Ch3LL commented Sep 2, 2016

@lubyou awesome thanks for the feedback! Glad you got it working.

@lubyou
Copy link
Contributor

lubyou commented Sep 2, 2016

https://bugs.launchpad.net/ubuntu/+source/libgit2/+bug/1595565 upstream bug

@jbouse
Copy link
Contributor Author

jbouse commented Sep 3, 2016

I'm away for the holiday weekend and won't be back at a terminal I could do any testing from until Thursday; however, if the solution is in fact to recompile libpygit2 then it seems like upon my return my options are to either hope the upstream build bug is fixed in both Debian and Ubuntu and be able to upgrade the python-pygit2 package or I'll be rebuilding my salt master servers back on Ubuntu 14.04 and Debian 8 and then reverting back to using GitPython until pygit2 is more stable and readily available to use. Having to custom compile distribution packages to get it to work is an unacceptable solution for me.

@jbouse
Copy link
Contributor Author

jbouse commented Sep 4, 2016

Found a better work around solution than recompiling the package... I just set winrepo_provider: gitpython in my salt master config since GitPython works fine with HTTPS URLs and in the case of winrepo_remotes_ng and winrepo_remotes I don't need to use authentiction which was the reason for moving to pygit2 for my pillar and state repositories.

@jbouse jbouse mentioned this issue Sep 6, 2016
Merged
@Ch3LL
Copy link
Contributor

Ch3LL commented Sep 6, 2016

@jbouse glad you found a workaround. Are you okay to close this issue as it seems this is an upstream issue?

@jbouse
Copy link
Contributor Author

jbouse commented Sep 8, 2016

@Ch3LL yeah we can close this... As well as it being an upstream build issue I've gotten a PR fix into the salt-formula that helps work around it.

@jbouse jbouse closed this as completed Sep 8, 2016
@infinity0 infinity0 mentioned this issue Aug 1, 2017
Closed
@infinity0
Copy link

I have a patch to fix the issue in Debian and Ubuntu which would allow you to avoid these rebuilds. Please review!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
info-needed waiting for more info
Projects
None yet
Milestone
Blocked
Development

No branches or pull requests
4 participants
@jbouse @infinity0 @lubyou @Ch3LL