Alexander, That could potentially create some issues for some users in that 2.7.9 breaks some other non-fink things that won't be fixed until 2.7.10. Forcing an upgrade to 2.7.9 will create a quandary since some can't go to 2.7.9 which might force those users into a very laborious fink update process since update-all would no longer be an option. So, there's a bit more than normal to consider in this situation.
Merle > On Jun 6, 2016, at 11:17 AM, Alexander Hansen <alexanderk.han...@gmail.com> > wrote: > >> >> On Jun 2, 2016, at 10:30, Alexander Hansen <alexanderk.han...@gmail.com> >> wrote: >> >>> >>> On Jun 2, 2016, at 09:57, Jack Howarth <howarth.at.f...@gmail.com> wrote: >>> >>> >>> >>> On Thu, Jun 2, 2016 at 10:57 AM, Stefan Bruda <ste...@bruda.ca> wrote: >>> At 10:02 -0400 on 2016-6-2 Jack Howarth wrote: >>>> >>>> So I assume you are talking about using extensions to emacs like >>>> https://github.com/Malabarba/spinner.el/blob/master/README.org >>>> rather than just the stock configuration? >>> >>> Strangely enough this is (was, see below) all standard configuration. >>> After some thought I realized that it is quite possible that any >>> Athena item could cause the crash. Sure enough, attempting to open a >>> file using the menu (which opens a dialogue) rather than the shortcut >>> (which uses the minibuffer) would cause the same kind of crash. In >>> the end I concluded that the Athena library is the culprit. I thus >>> rebuilt libxaw3dxft and libxaw3dxft-shlibs, then rebuilt xemacs, and >>> sure enough everything appears to be back in working order. >>> >>> The only change that I can imagine happening on the rebuild of libxaw3dxft >>> is that the linkage on libXt is switched from the flat-namespace copy, >>> /opt/X11/lib/libXt.6.dylib, to the newer two-level namespace one, >>> /opt/X11/lib/libXt.7.dylib. If this fixes xemacs, it is the total opposite >>> situation from motif (where the flat-namespace copy of libXt is required), >>> >> >> (moving discussion just to -devel for packaging-specific issue) >> >> Our system-pkgconfig-xt version changes from 1.1.4-1 for Xquartz 2.7.7 >> (libXt.6.dylib) to 1.1.5-1 for Xquartz 2.7.8 (libXt.6.dylib). No clue why >> 2.7.9 didn’t provoke an update there. >> >> However, system-pkgconfig-xorg-server does update (as we might expect) >> >> Fionna-3:tmp hansen$ diff -Nurd system-pkgconfig-2.7.8.txt >> system-pkgconfig-2.7.9.txt | grep server >> - i system-pkgconfig-xorg-server 1.16.4-1 [virtual pkgconfig >> package representing xorg-server] >> + i system-pkgconfig-xorg-server 1.17.4-1 [virtual pkgconfig >> package representing xorg-server] >> >> So that’s probably the most reasonable method currently to grab the Xquartz >> version without creating new virtual packages. >> >> I’m not sure how best to handle this automatically for libxaw3dxft2 and >> packages that use it. >> >> —akh > > Since system-pkgconfig-xorg-server isn’t BuildDependsOnly, unless somebody > objects I’m going to add a Depends: system-pkgconfig-xorg-server ( >= > 1.17.4-1 ) to libxaw3dxft-shlibs to force an update to the new Xquartz and a > rebuild. It would have been more informative to use system-pkgconfig-xt, but > that doesn’t indicate a difference between Xquartz-2.7.8 and 2.7.9 > > —akh > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic > patterns at an interface-level. Reveals which users, apps, and protocols are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning reports. > https://ad.doubleclick.net/ddm/clk/305295220;132659582;e_______________________________________________ > Fink-devel mailing list > Fink-devel@lists.sourceforge.net > List archive: > http://news.gmane.org/gmane.os.apple.fink.devel > Subscription management: > https://lists.sourceforge.net/lists/listinfo/fink-devel ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
