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

dbus-1.10.12 daemon #426

Open
jb329 opened this issue Nov 1, 2016 · 6 comments
Open

dbus-1.10.12 daemon #426

jb329 opened this issue Nov 1, 2016 · 6 comments
Assignees

Comments

@jb329
Copy link

jb329 commented Nov 1, 2016

Hello,

I'm not sure if this is where Mac OS X specific pkg-src issues go. Please redirect by responding if not.

I tried to install dbus-1.10.12 (was a dependency of another package I wanted to install, Dia-0) and got the attached dbus.txt.

I also get errors in the Dia application saying the dbus daemon is not running.

I don't think OS X fits any of the three start-up scripts suggested? The contents of /opt/pkg/share/examples/rc.d/dbus starts with . /etc/rc.subr which doesn't exist.

After a little reading, I think I need to:
sudo launchctl load -w /Library/LaunchDaemons/org.freedesktop.dbus-system.plist

But, there is no such plist file (in MacOS Sierra). I also found:
https://mail-index.netbsd.org/pkgsrc-users/2015/12/29/msg022776.html - unanswered.
https://cgit.freedesktop.org/dbus/dbus/tree/bus/org.freedesktop.dbus-session.plist.in

@jperkin jperkin self-assigned this Nov 1, 2016
@jperkin
Copy link
Collaborator

jperkin commented Nov 1, 2016

Yeh, we currently don't have support for launchd, and some of the MESSAGE files assume that the user is using the rc.d init system.

I'll take a look at fixing up the MESSAGE so at least we aren't advertising the wrong instructions, but launchd support is a bigger project.

@jb329
Copy link
Author

jb329 commented Nov 2, 2016

OK, thanks for the reply. Are you aware of any work around instructions that would get the dbus daemon running on MacOS/darwin so that I can use the application?

@jb329
Copy link
Author

jb329 commented Nov 3, 2016

Here's the feedback I got from the dbus mailing list to a similar query to above:

You probably need more than just a running DBus, you'll need the development headers too. It surprises me that pkgsrc doesn't provide a DBus package to satisfy dependencies.

MacPorts has an up-to-date DBus port which works just about perfectly. You can use that either to get the daemon up and running and point your package to the install location, or you can roll your own install using the installation "script" (Portfile) as a guideline.

https://trac.macports.org/browser/trunk/dports/devel/dbus/Portfile

I'd like to try to "roll my own" but I've never done that before. I'll do some reading and if I get anywhere I'll report back.

@jperkin
Copy link
Collaborator

jperkin commented Nov 3, 2016

That advice is incorrect, pkgsrc packages always include development headers, but in any case that wouldn't be the cause of the issue here.

I tried to reproduce this in my test VM, and dia appears to start dbus itself. I can't reproduce a failure due to dbus not running.

To compare, here's what I did:

sudo pkgin install dia modular-xorg-xquartz
cat >~/.xinitrc <<EOF
/opt/pkg/bin/quartz-wm &
/opt/pkg/bin/xterm
EOF
startx -- /opt/pkg/bin/Xquartz

Then in the screenshot attached you can see I ran pgrep to confirm that no dbus processes were running before launching dia, then after it had opened (took a while, not sure what is causing that) I opened a new xterm and showed that dbus had auto-launched.

dia

Let me know if that helps, or if there is a way I can reproduce your environment.

@jperkin
Copy link
Collaborator

jperkin commented Nov 3, 2016

Ok, I see the problem, I was too hasty in closing the warning dialog that popped up - clicking on details shows the dbus errors. I'll see if I can find a workaround for that in the meantime.

@jb329
Copy link
Author

jb329 commented Nov 7, 2016

Hello, thanks again. I'm using xquartz installed from the .dmg file here: https://www.xquartz.org/, not via pkgsrc, so my quartz-wm and xterm binaries are at /opt/X11/bin. I do not have any file ~/.xinitrc.d, so I'm just starting xquartz with the default settings.

Otherwise I have the same as you see. Full text of the dia error window is attached too.
error
diadbuserror.txt

wiedi pushed a commit to wiedi/pkgsrc-legacy that referenced this issue Nov 17, 2016
version 1.11.1: 2016-06-14

    * new guesser infrastructure, support for emacs and vim modelines (TritonDataCenter#489)
    * javascript bugfix for nested objects with quoted keys (TritonDataCenter#496)
    * new theme: Gruvbox (thanks @jamietanna!)
    * praat: lots of improvements (thanks @jjatria)
    * fix for rougify error when highlighting from stdin (TritonDataCenter#493)
    * new lexer: kotlin (thanks @meleyal!)
    * new lexer: cfscript (thanks @mjclemente!)

version 1.11.0: 2016-06-06

    * groovy:
	o remove pathological regexes and add basic support for
	  triple-quoted strings (TritonDataCenter#485)
	o add the "trait" keyword and fix project url (thanks @glaforge! TritonDataCenter#378)
    * new lexer: coq (thanks @gmalecha! TritonDataCenter#389)
    * gemspec license now more accurate (thanks @connorshea! TritonDataCenter#484)
    * swift:
	o properly support nested comments (thanks @dblessing! TritonDataCenter#479)
	o support swift 2.2 features (thanks @radex TritonDataCenter#376 and @wokalski TritonDataCenter#442)
	o add indirect declaration (thanks @nRewik! TritonDataCenter#326)
    * new lexer: verilog (thanks @Razer6! TritonDataCenter#317)
    * new lexer: typescript (thanks @Seikho! TritonDataCenter#400)
    * new lexers: jinja and twig (thanks @robin850! TritonDataCenter#402)
    * new lexer: pascal (thanks @alexcu!)
    * css: support attribute selectors (thanks @skoji! TritonDataCenter#426)
    * new lexer: shell session (thanks @sio4! TritonDataCenter#481)
    * ruby: add support for <<~ heredocs (thanks @tinci! TritonDataCenter#362)
    * recognize comments at EOF in SQL, Apache, and CMake (thanks @julp! TritonDataCenter#360)
    * new lexer: phtml (thanks @Igloczek TritonDataCenter#366)
    * recognize comments at EOF in CoffeeScript (thanks @rdavila! TritonDataCenter#370)
    * c/c++:
	o support c11/c++11 features (thanks @Tosainu! TritonDataCenter#371)
	o Allow underscores in identifiers (thanks @coverify! TritonDataCenter#333)
    * rust: add more builtin types (thanks @RalfJung! TritonDataCenter#372)
    * ini: allow hyphen keys (thanks @KrzysiekJ! TritonDataCenter#380)
    * r: massively improve lexing quality (thanks @klmr! TritonDataCenter#383)
    * c#:
	o add missing keywords (thanks @BenVlodgi TritonDataCenter#384 and @SLaks TritonDataCenter#447)
    * diff: do not require newlines at the ends (thanks @AaronLasseigne! TritonDataCenter#387)
    * new lexer: ceylon (thanks @bjansen! TritonDataCenter#414)
    * new lexer: biml (thanks @japj! TritonDataCenter#415)
    * new lexer: TAP - the test anything protocol (thanks @mblayman! TritonDataCenter#409)
    * rougify bugfix: treat input as utf8 (thanks @japj! TritonDataCenter#417)
    * new lexer: jsonnet (thanks @davidzchen! TritonDataCenter#420)
    * clojure: associate *.cljc for cross-platform clojure (thanks @alesguzik! TritonDataCenter#423)
    * new lexer: D (thanks @nikibobi! TritonDataCenter#435)
    * new lexer: smarty (thanks @tringenbach! TritonDataCenter#427)
    * apache:
	o add directives for v2.4 (thanks @stanhu!)
	o various improvements (thanks @julp! TritonDataCenter#301)
	    - faster keyword lookups
	    - fix nil error on unknown directive (cf TritonDataCenter#246, TritonDataCenter#300)
	    - properly manage case-insensitive names (cf TritonDataCenter#246)
	    - properly handle windows CRLF
    * objective-c:
	o support literal dictionaries and block arguments (thanks @BenV!
	  TritonDataCenter#443 and TritonDataCenter#444)
	o Fix error tokens when defining interfaces (thanks @meleyal! TritonDataCenter#477)
    * new lexer: NASM (thanks @sraboy! TritonDataCenter#457)
    * new lexer: gradle (thanks @nerro! TritonDataCenter#468)
    * new lexer: API Blueprint (thanks @kylef! TritonDataCenter#261)
    * new lexer: ActionScript (thanks @honzabrecka! TritonDataCenter#241)
    * terminal256 formatter: stop confusing token names (thanks @julp! TritonDataCenter#367)
    * new lexer: julia (thanks @mpeteuil! TritonDataCenter#331)
    * new lexer: cmake (thanks @julp! TritonDataCenter#302)
    * new lexer: eiffel (thanks @Conaclos! TritonDataCenter#323)
    * new lexer: protobuf (thanks @fqqb! TritonDataCenter#327)
    * new lexer: fortran (thanks @CruzR! TritonDataCenter#328)
    * php: associate *.phpt files (thanks @Razer6!)
    * python: support raise from and yield from (thanks @mordervomubel! TritonDataCenter#324)
    * new VimL example (thanks @tpope! TritonDataCenter#315)
wiedi pushed a commit to wiedi/pkgsrc-legacy that referenced this issue Nov 17, 2016
## v4.0.0

New features:
* New Django samples. (#636)
* Add support for RFC7636 PKCE. (#588)
* Release as a universal wheel. (#665)

Bug fixes:
* Fix django authorization redirect by correctly checking validity of credentials. (#651)
* Correct query loss when using parse_qsl to dict. (#622)
* Switch django models from pickle to jsonpickle. (#614)
* Support new MIDDLEWARE Django 1.10 aetting. (#623)
* Remove usage of os.environ.setdefault. (#621)
* Handle missing storage files correctly. (#576)
* Try to revoke token with POST when getting a 405. (#662)

Internal changes:
* Use transport module for GCE environment check. (#612)
* Remove __author__ lines and add contributors.md. (#627)
* Clean up imports. (#625)
* Use transport.request in tests. (#607)
* Drop unittest2 dependency (#610)
* Remove backslash line continuations. (#608)
* Use transport helpers in system tests. (#606)
* Clean up usage of HTTP mocks in tests. (#605)
* Remove all uses of MagicMock. (#598)
* Migrate test runner to pytest. (TritonDataCenter#569)
* Merge util.py and _helpers.py. (#579)
* Remove httplib2 imports from non-transport modules. (#577)

Breaking changes:
* Drop Python 3.3 support. (#603)
* Drop Python 2.6 support. (#590)
* Remove multistore_file. (#589)

## v3.0.0

* Populate `token_expiry` for GCE credentials. (#473)
* Move GCE metadata interface to a separate module. (TritonDataCenter#520)
* Populate `scopes` for GCE credentials. (TritonDataCenter#524)
* Fix Python 3.5 compatibility. (TritonDataCenter#531)
* Add `oauth2client.contrib.sqlalchemy`, a SQLAlchemy-based credential store. (TritonDataCenter#527)
* Improve error when an invalid client secret is provided. (TritonDataCenter#530)
* Add `oauth2client.contrib.multiprocess_storage`. This supersedes the functionality in `oauth2client.contrib.multistore_file`. (TritonDataCenter#504)
* Pull httplib2 usage into a separate transport module. (TritonDataCenter#559, TritonDataCenter#561)
* Refactor all django-related code into `oauth2client.contrib.django_util`. Add `DjangoORMStorage`, remove `FlowField`. (TritonDataCenter#546)
* Fix application default credentials resolution order. (#570)
* Add configurable timeout for GCE metadata server check. (#571)
* Add warnings when using deprecated `approval_prompt='force'`. (#572)
* Add deprecation warning to `oauth2client.contrib.multistore_file`. (#574)
* (Hygiene) PEP8 compliance and various style fixes (TritonDataCenter#537, TritonDataCenter#540, TritonDataCenter#552, TritonDataCenter#562)
* (Hygiene) Remove duplicated exception classes in `oauth2client.contrib.appengine`. (TritonDataCenter#533)

NOTE: The next major release of oauth2client (v4.0.0) will remove the `oauth2client.contrib.multistore_file` module.

## v2.2.0

* Added support to override `token_uri` and `revoke_uri` in `oauth2client.service_account.ServiceAccountCredentials`. (TritonDataCenter#510)
* `oauth2client.contrib.multistore_file` now handles `OSError` in addition to `IOError` because Windows may raise `OSError` where other platforms will raise `IOError`.
* `oauth2client.contrib.django_util` and `oauth2client.contrib.django_orm` have been updated to support Django 1.8 - 1.10. Versions of Django below 1.8 will not work with these modules.

## v2.1.0

* Add basic support for JWT access credentials. (TritonDataCenter#503)
* Fix `oauth2client.client.DeviceFlowInfo` to use UTC instead of the system timezone when calculating code expiration.

## v2.0.2

* Fix issue where `flask_util.UserOAuth2.required` would accept expired credentials (TritonDataCenter#452).
* Fix issue where `flask_util` would fill the session with `Flow` objects (TritonDataCenter#498).
* Fix issue with Python 3 binary strings in `Flow.step2_exchange` (TritonDataCenter#446).
* Improve test coverage to 100%.

## v2.0.1

* Making scopes optional on Google Compute Engine `AppAssertionCredentials`
  and adding a warning that GCE won't honor scopes (TritonDataCenter#419)
* Adding common `sign_blob()` to service account types and a
  `service_account_email` property. (TritonDataCenter#421)
* Improving error message in P12 factory
  `ServiceAccountCredentials.from_p12_keyfile` when pyOpenSSL is
  missing. (TritonDataCenter#424)
* Allowing default flags in `oauth2client.tools.run_flow()`
  rather than forcing users to create a dummy argparser (TritonDataCenter#426)
* Removing `oauth2client.util.dict_to_tuple_key()` from public
  interface (TritonDataCenter#429)
* Adding `oauth2client.contrib._appengine_ndb` helper module
  for `oauth2client.contrib.appengine` and moving most code that
  uses the `ndb` library into the helper (TritonDataCenter#434)
* Fix error in `django_util` sample code (TritonDataCenter#438)

## v2.0.0-post1

* Fix Google Compute Engine breakage (TritonDataCenter#411, breakage introduced in TritonDataCenter#387) that
  made it impossible to obtain access tokens
* Implement `ServiceAccountCredentials.from_p12_keyfile_buffer()`
  to allow passing a file-like object in addition to the factory
  constructor that uses a filename directly (TritonDataCenter#413)
* Implement `ServiceAccountCredentials.create_delegated()`
  to allow upgrading a credential to one that acts on behalf
  of a given subject (TritonDataCenter#420)
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