Re: Stable/Testing branch in MacPorts
On 04-04-2010, Ryan Schmidt ryandes...@macports.org wrote: On Apr 4, 2010, at 08:01, Janosch Peters wrote: Has maintaing two branches been already discussed on the list? Several times. I don't see that we have anywhere close to the (personnel) resources necessary to support such a thing. Almost 2700 out of our almost 6800 ports are unmaintained; if we can't even maintain the ports we have in our single tree, how will we keep up with multiple trees? Good point. I wasnt aware that there are so many unmaintained ports. I also don't understand how you decide when to move something from unstable to stable. Logically, you do so when it's stable, meaning when it works all the time in every circumstance, but how do you know if it's working all the time in every circumstance if nobody has tested it because everybody's running the older version in the stable branch? Well, it obviously works, because thats what every major linux distribution does. If there are enough people using a distro, there are always some people who use packages from the testing branch, and some of them are reporting bugs. If a package hasnt received bug reports for some time, it can be moved to stable. But this works only if there are enough users. Are there any estimates about how many people are using macports? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Stable/Testing branch in MacPorts
Hi there, I use macports fot about 1.5 years now. Most things work great and MP has some lovely features like variants. However, it appears quite often that some ports are broken for various different reasons. E.g. the quartz variant of gtk2 lead to crashes in gimp2 and the bug was not fixed for several months. I know that maintaining two branches is probably more work, but in contrast to most linux distros, using macports I cannot be sure that a port works if I install/upgrade it. (Of course you cannot be 100% sure using e.g. ubuntu/debian either, but at least those package have been tested for some time). In terms of stability the single macports branch feels a bit like the unstable branch in debian. To make things even more annoying is the fact that there is no _straightforward_ way to downgrade to a previous version of the port. (I know that there is a way, but its not as easy as with apt-get for example). Has maintaing two branches been already discussed on the list? cheers, Janosch ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Gutenprint drivers
Hi, I wanted to install gutenprint in order to use several printers. I prefer using any software from macports (instaed of installers). However the gutenprint port does only contain the gimp plugin part, not any printer drivers. Is there another port which provides the drivers or are there any plans tin include the gutenprint drivers as a port or a variant of gutenprint? cheers, Janosch ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Unsubscribe from a bug report
Hi, I filed a bug some time ago. With help from other guys I submitted a fix myself some time later. The bug report is still open because the maintainer did not commit the patch yet. Is there any way that I unsubscribe from the bug reports I filed myself? I keep getting notifications from this ticket, which I find quite annoying cause the issue is allready solved. cheers, Janosch ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Gimp.app crashing
On 11-05-2009, Jeff Pitman jeff.pit...@gmail.com wrote: For some reason Gimp.app started crashing for me. I then did a full update of all outdated packages, but no effect. Anyone else having the same issue? Yes, I do. If we can verify that it is the same error, we could open a bug report. Are you running the no_x11/quartz variant? Could your run gimp from the command line and have a look if there occures a Bus error? It would be even better if you could install the debug version: gimp2 @2.6.7_0+darwin_9+debug+no_x11+quartz and run gimp --g-fatal-warnings --stack-trace-mode=always on the console. cheers, Janosch ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Gimp bus error
Hi, Since a few weeks, gimp crashes shortly after the UI comes up. If I drag the picture window over the desktop it crashes every time. This is the output: zaphod:skript jp$ gimp --g-fatal-warnings --stack-trace-mode=always gimp: fatal error: Bus error #0 0x9716b851 in __wait4 () #1 0x9716b847 in waitpid$UNIX2003 () #2 0x010422ec in g_on_error_stack_trace () #3 0x2be0 in gimp_eek () #4 0x2c64 in gimp_fatal_error () #5 0x36cc in gimp_sigfatal_handler () #6 signal handler called #7 0x in ?? () #8 0x00b654b9 in send_crossing_event () #9 0x00b6650e in _gdk_windowing_got_event () #10 0x00b7257c in _gdk_events_queue () #11 0x00b7117c in gdk_event_dispatch () #12 0x01068a0d in g_main_context_dispatch () #13 0x0106c48b in g_main_context_iterate () #14 0x0106c767 in g_main_loop_run () #15 0x2319 in app_run () #16 0x3493 in main () (script-fu:48431): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error But DBus IS running: zaphod:skript jp$ ps ax|grep dbus 48275 ?? Ss 0:00.00 /opt/local/bin/dbus-daemon --system --nofork 48373 s002 R+ 0:00.00 grep dbus Im really lost now. I rebuilt all dependencies of gimp to single out any errors which may be caused by linking to old libraries. BTW I use the quartz variant: The following ports are currently installed: gimp2 @2.6.7_0+darwin_9+debug+no_x11+quartz (active) gimp2 @2.6.7_0+darwin_9+no_x11+quartz Any help is appreciated. cheers, Janosch ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Building vte fails
Hi list, I'd like to install gtk-sharp which depends on vte. Unfortunately, vte fails to build. Because I found nothing on the net, I assume that it has sth to do with my configuration, but I dont know what it could be. Any ideas are highly appreciated. cheers, Janosch --- Building vte Error: Target org.macports.build returned: shell command cd /opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_ vte/work/vte-0.20.5 make all returned error 2 Command output: vtebg.c: At top level: vtebg.c:107: warning: declaration of 'atom' shadows a global declaration vtebg.c:83: warning: shadowed declaration is here vtebg.c:109: error: syntax error before 'XID' vtebg.c:110: warning: function declaration isn't a prototype vtebg.c: In function '_vte_property_get_pixmaps': vtebg.c:110: warning: old-style function definition vtebg.c:111: error: 'window' undeclared (first use in this function) vtebg.c:111: error: (Each undeclared identifier is reported only once vtebg.c:111: error: for each function it appears in.) vtebg.c:114: error: 'type' undeclared (first use in this function) vtebg.c:114: error: 'size' undeclared (first use in this function) vtebg.c:115: error: 'pixmaps' undeclared (first use in this function) vtebg.c: In function 'vte_bg_root_pixmap': vtebg.c:124: error: 'XID' undeclared (first use in this function) vtebg.c:124: error: 'pixmaps' undeclared (first use in this function) vtebg.c:129: error: dereferencing pointer to incomplete type vtebg.c:129: error: dereferencing pointer to incomplete type vtebg.c:135: error: dereferencing pointer to incomplete type vtebg.c: In function 'vte_bg_root_filter': vtebg.c:166: error: 'XEvent' undeclared (first use in this function) vtebg.c:166: error: 'xevent' undeclared (first use in this function) vtebg.c:166: error: syntax error before ')' token vtebg.c:171: error: 'PropertyNotify' undeclared (first use in this function) vtebg.c:173: error: dereferencing pointer to incomplete type vtebg.c:174: error: dereferencing pointer to incomplete type make[3]: *** [libvte_la-vtebg.lo] Error 1 make[2]: *** [all] Error 2 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Building vte fails
On 07-02-2009, David Evans dev...@macports.org wrote: and if it fails again open a ticket against vte on track (http://trac.macports.org) including the full debug output and specifying the following information about your system Done. Ticket is #20139. Its looking for a file called gdkx.h, which is not on my disk. Im pretty sure that it is the cause. cheers, Janosch ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
