what is dbus-glib-1? checking for LIBGNOMEVFS... configure: error: Package requirements (glib-2.0 >= 2.9.3 gmodule-no-export-2.0 >= 2.9.3 gthread-2.0 >= 2.9.3 gobject-2.0 >= 2.9.3 gconf-2.0 >= 1.1.1 libxml-2.0 >= 2.6.0 gnome-mime-data-2.0 dbus-glib-1 >= 0.60) were not met: No package 'dbus-glib-1' found <snip> Error: Unable to upgrade port: 1 white:~ root# port list | grep dbus dbus @0.61 devel/dbus -- Paul Beard contact info: www.paulbeard.org/paulbeard.vcf pictures: http://www.flickr.com/photos/pdb206/ Are you trying to win an argument or solve a problem?
dbus-glib-1 is the glib bindings for dbus. dbus 0.61 includes the bindings in that port. For a short period, dbus 0.92 was in ports, but I have since reverted the port tree to 0.61. If you have dbus 0.92 installed, forcibly uninstall it, clean the port, and reinstall it: sudo port -f uninstall dbus sudo port clean --all dbus sudo port install dbus On 2 Oct 2006, at 19:42, Paul Beard wrote:
what is dbus-glib-1?
checking for LIBGNOMEVFS... configure: error: Package requirements (glib-2.0 >= 2.9.3 gmodule-no-export-2.0 >= 2.9.3 gthread-2.0 >= 2.9.3 gobject-2.0 >= 2.9.3 gconf-2.0 >= 1.1.1 libxml-2.0 >= 2.6.0 gnome-mime-data-2.0 dbus-glib-1 >= 0.60) were not met:
No package 'dbus-glib-1' found
<snip>
Error: Unable to upgrade port: 1 white:~ root# port list | grep dbus dbus @0.61 devel/dbus
-- Paul Beard contact info: www.paulbeard.org/paulbeard.vcf pictures: http://www.flickr.com/photos/pdb206/ Are you trying to win an argument or solve a problem?
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Randall Wood rhwood@mac.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Oct 2, 2006, at 5:56 PM, Randall Wood wrote:
If you have dbus 0.92 installed, forcibly uninstall it, clean the port, and reinstall it:
I don't. It would be useful if MacPorts could recognize that and install it if it's required. - -- Paul Beard contact info: www.paulbeard.org/paulbeard.vcf pictures: http://www.flickr.com/photos/pdb206/ Are you trying to win an argument or solve a problem? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFIgQbfHLPwpj1/JQRAmY9AJkB9qylUJcPf69ycv8aA6FxXxM2JwCePHK1 JTBaU9roYichpsiM+Uv63WA= =qND5 -----END PGP SIGNATURE-----
dbus-glib-1 is the glib bindings for dbus. dbus 0.61 includes the bindings in that port.
Well, then you better fix that portfile really soon now. I don't want to flame, but... Do you guys actually test _anything_ before releasing it to the public? Do you actually want to be taken for serious? If so, you better start to use some methods of what is generally called "release management" really soon now. Until then, I'll personally consider Macports as inexistant, because unusable for actual use. As basically _most_ of the ports are broekk at any given moment and a quick "sudo port upgrade installed" can even break things that were previously working. Sincerely, Wolfgang Keller -- My email-address is correct. Do NOT remove ".nospam" to reply.
Hi Wolfgang, I never ever replied to a flame, but your mails are a constant annoyment, so let me explain some simple things to you. Wolfgang Keller wrote:
dbus-glib-1 is the glib bindings for dbus. dbus 0.61 includes the bindings in that port.
Well, then you better fix that portfile really soon now. "Well, then you better give us a patch really soon now". How would you feel if someone talked to you this way? As a side note, I could even say that if you lack the technical skills to fix it yourself, then you should probably not talk to Randall that way. Sorry if I'm being blunt.
I don't want to flame, but...
Do you guys actually test _anything_ before releasing it to the public?
Do you actually want to be taken for serious?
If so, you better start to use some methods of what is generally called "release management" really soon now. Just try to express your feelings with constructiveness.
Until then, I'll personally consider Macports as inexistant, because unusable for actual use. As basically _most_ of the ports are broekk at any given moment and a quick "sudo port upgrade installed" can even break things that were previously working. OK. I won't argue on the port brokeness because this won't get anywhere in terms of code and bugfixes. On the last argument you're having, you're telling me you can't reactivate older archives? Furthermore, on the "[port] can even break things that were previously working" part, guess what? All systems "can even break things that were previously working". We just dislike breaking stuff as much as you do.
Sincerely,
Wolfgang Keller
-- Pierre
It is often the case that others may suffer from build failures or crashes that a port maintainer is not capable of reproducing. That said, the port HAS been fixed. See the output below. Getafix:~ rhwood$ port info dbus dbus 0.61, Revision 2, devel/dbus (Variants: with_qt, with_mono) http://www.freedesktop.org/Software/dbus {A message bus system, a simple way for applications to talk to one another.} Library Dependencies: glib2, libxml2 Platforms: darwin Maintainers: macports-dev@lists.macosforge.org Getafix:~ rhwood$ port provides /opt/local/lib/pkgconfig/dbus-glib-1.pc /opt/local/lib/pkgconfig/dbus-glib-1.pc is provided by: dbus Getafix:~ rhwood$ port info gnome-vfs gnome-vfs 2.16.0, gnome/gnome-vfs (Variants: darwin_6, darwin_7, use_system_dependencies) http://www.gnome.org/ This is the GNOME Virtual File System. GNOME VFS is currently used as one of the foundations of the Nautilus file manager. Library Dependencies: gnome-mime-data, gconf, howl, neon, dbus, openssl, libidl Platforms: darwin Maintainers: macports-dev@lists.macosforge.org rhwood@macports.org On 4 Oct 2006, at 03:29, Wolfgang Keller wrote:
dbus-glib-1 is the glib bindings for dbus. dbus 0.61 includes the bindings in that port.
Well, then you better fix that portfile really soon now.
I don't want to flame, but...
Do you guys actually test _anything_ before releasing it to the public?
Do you actually want to be taken for serious?
If so, you better start to use some methods of what is generally called "release management" really soon now.
Until then, I'll personally consider Macports as inexistant, because unusable for actual use. As basically _most_ of the ports are broekk at any given moment and a quick "sudo port upgrade installed" can even break things that were previously working.
Sincerely,
Wolfgang Keller
-- My email-address is correct. Do NOT remove ".nospam" to reply.
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Randall Wood rhwood@mac.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."
participants (4)
-
Paul Beard
-
Pierre Queinnec
-
Randall Wood
-
Wolfgang Keller