Re: xcb-util
Kevin Oberman kob6...@gmail.com wrote: pkg_libchk -o | grep xcb- should just give the relevant information. Its a lot (all ports up to Date except x11-wm/xfce4-wm): # pkg_libchk -o | grep xcb- x11-fm/thunar: /usr/local/lib/thunarx-2/thunar-uca.so misses libxcb-aux.so.0 x11-fm/thunar: /usr/local/lib/thunarx-2/thunar-uca.so misses libxcb-event.so.1 x11-fm/thunar: /usr/local/lib/thunarx-2/thunar-uca.so misses libxcb-atom.so.1 x11-fm/thunar: /usr/local/lib/xfce4/panel/plugins/libthunar-tpa.so misses libxcb-aux.so.0 x11-fm/thunar: /usr/local/lib/xfce4/panel/plugins/libthunar-tpa.so misses libxcb-event.so.1 x11-fm/thunar: /usr/local/lib/xfce4/panel/plugins/libthunar-tpa.so misses libxcb-atom.so.1 x11-toolkits/libwnck: /usr/local/bin/wnck-urgency-monitor misses libxcb-aux.so.0 x11-toolkits/libwnck: /usr/local/bin/wnck-urgency-monitor misses libxcb-event.so.1 x11-toolkits/libwnck: /usr/local/bin/wnck-urgency-monitor misses libxcb-atom.so.1 x11-toolkits/libwnck: /usr/local/bin/wnckprop misses libxcb-aux.so.0 x11-toolkits/libwnck: /usr/local/bin/wnckprop misses libxcb-event.so.1 x11-toolkits/libwnck: /usr/local/bin/wnckprop misses libxcb-atom.so.1 x11-toolkits/libwnck: /usr/local/lib/libwnck-1.so.22 misses libxcb-aux.so.0 x11-toolkits/libwnck: /usr/local/lib/libwnck-1.so.22 misses libxcb-event.so.1 x11-toolkits/libwnck: /usr/local/lib/libwnck-1.so.22 misses libxcb-atom.so.1 x11-toolkits/libxfce4gui: /usr/local/lib/libxfcegui4.so.7 misses libxcb-aux.so.0 x11-toolkits/libxfce4gui: /usr/local/lib/libxfcegui4.so.7 misses libxcb-event.so.1 x11-toolkits/libxfce4gui: /usr/local/lib/libxfcegui4.so.7 misses libxcb-atom.so.1 x11-toolkits/libxfce4gui: /usr/local/lib/libglade/2.0/libxfce4.so misses libxcb-aux.so.0 x11-toolkits/libxfce4gui: /usr/local/lib/libglade/2.0/libxfce4.so misses libxcb-event.so.1 x11-toolkits/libxfce4gui: /usr/local/lib/libglade/2.0/libxfce4.so misses libxcb-atom.so.1 editors/mousepad: /usr/local/bin/mousepad misses libxcb-aux.so.0 editors/mousepad: /usr/local/bin/mousepad misses libxcb-event.so.1 editors/mousepad: /usr/local/bin/mousepad misses libxcb-atom.so.1 archivers/squeeze: /usr/local/bin/squeeze misses libxcb-aux.so.0 archivers/squeeze: /usr/local/bin/squeeze misses libxcb-event.so.1 archivers/squeeze: /usr/local/bin/squeeze misses libxcb-atom.so.1 x11-fm/thunar-vfs: /usr/local/lib/libthunar-vfs-1.so.5 misses libxcb-aux.so.0 x11-fm/thunar-vfs: /usr/local/lib/libthunar-vfs-1.so.5 misses libxcb-event.so.1 x11-fm/thunar-vfs: /usr/local/lib/libthunar-vfs-1.so.5 misses libxcb-atom.so.1 x11-wm/xfce4-desktop: /usr/local/bin/xfdesktop misses libxcb-aux.so.0 x11-wm/xfce4-desktop: /usr/local/bin/xfdesktop misses libxcb-event.so.1 x11-wm/xfce4-desktop: /usr/local/bin/xfdesktop misses libxcb-atom.so.1 x11-wm/xfce4-desktop: /usr/local/bin/xfdesktop-settings misses libxcb-aux.so.0 x11-wm/xfce4-desktop: /usr/local/bin/xfdesktop-settings misses libxcb-event.so.1 x11-wm/xfce4-desktop: /usr/local/bin/xfdesktop-settings misses libxcb-atom.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libactions.so misses libxcb-aux.so.0 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libactions.so misses libxcb-event.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libactions.so misses libxcb-atom.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libapplicationsmenu.so misses libxcb-aux.so.0 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libapplicationsmenu.so misses libxcb-event.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libapplicationsmenu.so misses libxcb-atom.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libclock.so misses libxcb-aux.so.0 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libclock.so misses libxcb-event.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libclock.so misses libxcb-atom.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libdirectorymenu.so misses libxcb-aux.so.0 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libdirectorymenu.so misses libxcb-event.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libdirectorymenu.so misses libxcb-atom.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/liblauncher.so misses libxcb-aux.so.0 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/liblauncher.so misses libxcb-event.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/liblauncher.so misses libxcb-atom.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libpager.so misses libxcb-aux.so.0 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libpager.so misses libxcb-event.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libpager.so misses libxcb-atom.so.1 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libseparator.so misses libxcb-aux.so.0 x11-wm/xfce4-panel: /usr/local/lib/xfce4/panel/plugins/libseparator.so misses libxcb-event.so.1 x11-wm/xfce4-panel:
Re: xcb-util
Heino Tiedemann wrote: Kevin Obermankob6...@gmail.com wrote: pkg_libchk -o | grep xcb- should just give the relevant information. Its a lot (all ports up to Date except x11-wm/xfce4-wm): It's not about been up to date, it's about been correctly linked. Go rebuild them. -- Sphinx of black quartz judge my vow. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: xcb-util
On Wednesday 18 January 2012 22:51:49 Kevin Oberman wrote: On Wed, Jan 18, 2012 at 6:08 PM, Jason Hellenthal jh...@dataix.net wrote: On Wed, Jan 18, 2012 at 05:46:07PM -0600, ajtiM wrote: On Wednesday 18 January 2012 08:28:38 Volodymyr Kostyrko wrote: Subbsd wrote: I found two broken rebuild after upgrade xcb: pkg_libchk from sysutils/bsdadminscripts would point you to all ports that should be rebuilt. I ran pkg_libchk and I got: diablo-jdk-16 misses libz.so.4 Unrelated to the issue... FYI the above package provides what the below package is utilized for. diablo-jre-16 misses libz.so.4 and both misses liodbcinst.so FYI The man page for pkg_libchk discusses this and explains that thy are false positives. pkg_libchk -o | grep xcb- should just give the relevant information. Thank you. I did and I didn't get anything. Mitja http://jpgmag.com/people/lumiwa ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: xcb-util
I found two broken rebuild after upgrade xcb: 1) vlc doesn't build ( http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/164268 ) 2) kalzium doesn't build ( It is corrected after force rebuild something from ocaml\* or facile\*) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: xcb-util
Subbsd sub...@gmail.com wrote: I found two broken rebuild after upgrade xcb: 1) vlc doesn't build ( http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/164268 ) 2) kalzium doesn't build ( It is corrected after force rebuild something from ocaml\* or facile\*) 3) xfce4-wm libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la' or unhandled argument `/usr/local/lib/libxcb-aux.la' g Heino ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: xcb-util
On Wednesday 18 January 2012 03:07:09 you wrote: I found two broken rebuild after upgrade xcb: 1) vlc doesn't build ( http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/164268 ) 2) kalzium doesn't build ( It is corrected after force rebuild something from ocaml\* or facile\*) I use mplayer and I don't have a problem. Is kalzium part of kdeedu? If it is than I didn't have a problem to rebuilt. Mitja http://jpgmag.com/people/lumiwa ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: xcb-util
Subbsd wrote: I found two broken rebuild after upgrade xcb: 1) vlc doesn't build ( http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/164268 ) 2) kalzium doesn't build ( It is corrected after force rebuild something from ocaml\* or facile\*) pkg_libchk from sysutils/bsdadminscripts would point you to all ports that should be rebuilt. -- Sphinx of black quartz judge my vow. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: xcb-util
On Wednesday 18 January 2012 08:28:38 Volodymyr Kostyrko wrote: Subbsd wrote: I found two broken rebuild after upgrade xcb: 1) vlc doesn't build ( http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/164268 ) 2) kalzium doesn't build ( It is corrected after force rebuild something from ocaml\* or facile\*) pkg_libchk from sysutils/bsdadminscripts would point you to all ports that should be rebuilt. I ran pkg_libchk and I got: diablo-jdk-16 misses libz.so.4 diablo-jre-16 misses libz.so.4 and both misses liodbcinst.so but I have: ocate libz.so.4 /usr/local/lib/compat/libz.so.4 but I don't have libodbcinst.so and I rebuilt diablo. libreoffice 3.4.5 misses libjawt.so I have: locate libjawt.so /usr/local/diablo-jdk1.6.0/jre/lib/i386/libjawt.so /usr/local/diablo-jre1.6.0/lib/i386/libjawt.so redland and rasqar misses libyajl.so.1 which I don't have and opera -11.60 misses libz.so.5 which I don't have. Which ports have libs which I need it, please? Mitja http://jpgmag.com/people/lumiwa ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: xcb-util
On Wed, Jan 18, 2012 at 05:46:07PM -0600, ajtiM wrote: On Wednesday 18 January 2012 08:28:38 Volodymyr Kostyrko wrote: Subbsd wrote: I found two broken rebuild after upgrade xcb: pkg_libchk from sysutils/bsdadminscripts would point you to all ports that should be rebuilt. I ran pkg_libchk and I got: diablo-jdk-16 misses libz.so.4 Unrelated to the issue... FYI the above package provides what the below package is utilized for. diablo-jre-16 misses libz.so.4 and both misses liodbcinst.so ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: xcb-util
On Wed, Jan 18, 2012 at 6:08 PM, Jason Hellenthal jh...@dataix.net wrote: On Wed, Jan 18, 2012 at 05:46:07PM -0600, ajtiM wrote: On Wednesday 18 January 2012 08:28:38 Volodymyr Kostyrko wrote: Subbsd wrote: I found two broken rebuild after upgrade xcb: pkg_libchk from sysutils/bsdadminscripts would point you to all ports that should be rebuilt. I ran pkg_libchk and I got: diablo-jdk-16 misses libz.so.4 Unrelated to the issue... FYI the above package provides what the below package is utilized for. diablo-jre-16 misses libz.so.4 and both misses liodbcinst.so FYI The man page for pkg_libchk discusses this and explains that thy are false positives. pkg_libchk -o | grep xcb- should just give the relevant information. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: xcb-util
I had fresh installed FreeBSD 9.0-RC3 ad than I updated to 9.0-Release. I ran portsnap fetch update and portmaster -a and xcb was updated. It happened day before when was /usr/ports/UPDATING update wtih portmaster -R -r xcb-util.0 which I ran yesterday and it happened what I wrote before. On Mon, Jan 16, 2012 at 5:17 PM, Freddie Cash fjwc...@gmail.com wrote: On Mon, Jan 16, 2012 at 3:11 PM, Chuck Swiger cswi...@mac.com wrote: On Jan 16, 2012, at 2:51 PM, ajtiM wrote: FreeBSD 9.0 is out, many people updated, new installation...KDE 4.7.4 is coming in the ports (I hope no) and now all this reinstallation for xcb-util. Is it not possible to synchronized a little with the other ports? You're the one managing your machine(s). If you want a package systems which releases less frequently than FreeBSD ports are updated, then either do not update your ports as rapidly, or consider switching to something like pkgsrc from NetBSD. Alternatively, switch to using pre-built, binary packages via the -P and -PP switches to portmaster/portupgrade, or even pkg_upgrade (from the sysutils/bsdadminscripts port). I need to reinstall about 300 ports (KDE, Firefox, libxul, GIMP...). It is to much... Why do you need to reinstall? Perhaps because he just completed an upgrade from 8.x to 9.0? While there are ways to mitigate the need for awhile (misc/compat8x, leaving old libraries around, various switches to portmaster/portupgrade to keep old versions of libs in /usr/local/compat, etc), eventually, one should reinstall all ports when upgrading between major versions of FreeBSD. However, one has the option of scheduling when that rebuilt/reinstall occurs. If you know a new version of X, KDE, Firefox are coming down the pipe soon, then why not wait until those major updates hit the ports tree? And then do everything all at once? Rather than reinstalling everything after the 8-9 upgrade, and then again for libxcb, then again for KDE, then again for Port X, Port Y, etc, etc, etc. Just because a new version hits the ports tree, doesn't mean you have to rush right out, this second, and upgrade to it. :) -- Freddie Cash fjwc...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: xcb-util
On Jan 16, 2012, at 2:51 PM, ajtiM wrote: FreeBSD 9.0 is out, many people updated, new installation...KDE 4.7.4 is coming in the ports (I hope no) and now all this reinstallation for xcb-util. Is it not possible to synchronized a little with the other ports? You're the one managing your machine(s). If you want a package systems which releases less frequently than FreeBSD ports are updated, then either do not update your ports as rapidly, or consider switching to something like pkgsrc from NetBSD. I need to reinstall about 300 ports (KDE, Firefox, libxul, GIMP...). It is to much... Why do you need to reinstall? Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: xcb-util
2012/1/16 ajtiM lum...@gmail.com: FreeBSD 9.0 is out, many people updated, new installation...KDE 4.7.4 is coming in the ports (I hope no) and now all this reinstallation for xcb-util. Is it not possible to synchronized a little with the other ports? I need to reinstall about 300 ports (KDE, Firefox, libxul, GIMP...). It is to much... Du you use portmaster, or portupgrade ? For me, also KDE and firefox user (~400 ports installed), portmaster only wants to upgrade few ports... Before the xcb-util update, during the ports tree freeze, my installed ports were nearly up-to-date. # portsnap fetch update # portmaster -R -r xcb-util-0 === The following actions will be taken if you choose to proceed: Upgrade xcb-util-0.3.6,1 to xcb-util-0.3.8,1 Install devel/gmake Install devel/gperf Install devel/libtool Upgrade cairo-1.10.2_2,1 to cairo-1.10.2_3,1 Upgrade glib-2.28.8_2 to glib-2.28.8_3 Upgrade pcre-8.21 to pcre-8.21_1 Install x11/xcb-util-renderutil The only direct dependency on xcb-util is set by cairo. Please note I use EXPLICIT_PACKAGE_DEPENDS=yes in my /etc/make.conf, that could explain the difference ? After the upgrade, KDE and firefox still work fine. -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org - against HTML email vCards X www: http://www.gid0.org - against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: xcb-util
On Mon, Jan 16, 2012 at 3:11 PM, Chuck Swiger cswi...@mac.com wrote: On Jan 16, 2012, at 2:51 PM, ajtiM wrote: FreeBSD 9.0 is out, many people updated, new installation...KDE 4.7.4 is coming in the ports (I hope no) and now all this reinstallation for xcb-util. Is it not possible to synchronized a little with the other ports? You're the one managing your machine(s). If you want a package systems which releases less frequently than FreeBSD ports are updated, then either do not update your ports as rapidly, or consider switching to something like pkgsrc from NetBSD. Alternatively, switch to using pre-built, binary packages via the -P and -PP switches to portmaster/portupgrade, or even pkg_upgrade (from the sysutils/bsdadminscripts port). I need to reinstall about 300 ports (KDE, Firefox, libxul, GIMP...). It is to much... Why do you need to reinstall? Perhaps because he just completed an upgrade from 8.x to 9.0? While there are ways to mitigate the need for awhile (misc/compat8x, leaving old libraries around, various switches to portmaster/portupgrade to keep old versions of libs in /usr/local/compat, etc), eventually, one should reinstall all ports when upgrading between major versions of FreeBSD. However, one has the option of scheduling when that rebuilt/reinstall occurs. If you know a new version of X, KDE, Firefox are coming down the pipe soon, then why not wait until those major updates hit the ports tree? And then do everything all at once? Rather than reinstalling everything after the 8-9 upgrade, and then again for libxcb, then again for KDE, then again for Port X, Port Y, etc, etc, etc. Just because a new version hits the ports tree, doesn't mean you have to rush right out, this second, and upgrade to it. :) -- Freddie Cash fjwc...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: xcb-util
On Mon, Jan 16, 2012 at 3:16 PM, Olivier Smedts oliv...@gid0.org wrote: The only direct dependency on xcb-util is set by cairo. Please note I use EXPLICIT_PACKAGE_DEPENDS=yes in my /etc/make.conf, that could explain the difference ? What is EXPLICIT_PACKAGE_DEPENDS, and where is it documented? I think I understand what it's supposed to do (only list direct dependencies between packages during install, not not everything all the way up the dependency chain in every package). But there's no mention of it in make.conf(5). And the only result of a grep for it in /usr/ports/Mk is a conditional that compares it's value. -- Freddie Cash fjwc...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: xcb-util 0.3.4 breaks awesome
* Josh Rickmar (joshua_rick...@eumx.net) wrote: starup-notification was updated, and I've just committed update of awesome to 3.3-rc2. This should have no problems with new xcb-util. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: xcb-util 0.3.4 breaks awesome
On Fri, 8 May 2009, Dmitry Marakasov wrote: * Josh Rickmar (joshua_rick...@eumx.net) wrote: starup-notification was updated, and I've just committed update of awesome to 3.3-rc2. This should have no problems with new xcb-util. Thanks! Yeah, I saw the update to 3.3-rc2 and the new startup-notification version. Upgrading right now. I'll notify you again if I see any more problems (not necessarily with xcb-util). -- IRC nick: jrick Jabber: jr...@jabber.org http://identi.ca/jrick ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: xcb-util 0.3.4 breaks awesome
* Josh Rickmar (joshua_rick...@eumx.net) wrote: That's quite complicated problem actually - xcb-util update has broken awesome; we could update awesome to 3.3-rc1, but it requires startup-notification 0.10 (which likely requires new xcb-util as well). Thus we'll likely have to wait for s-n 0.10 and consider awesome broken for now. Meanwhile, awesome users are recommended to not upgrade from/downgrade to xcb-util 0.3.3. This is really our fault as there should've been more testing and coordination with this update. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: xcb-util 0.3.4 breaks awesome
On Fri, 8 May 2009, Dmitry Marakasov wrote: * Josh Rickmar (joshua_rick...@eumx.net) wrote: That's quite complicated problem actually - xcb-util update has broken awesome; we could update awesome to 3.3-rc1, but it requires startup-notification 0.10 (which likely requires new xcb-util as well). Thus we'll likely have to wait for s-n 0.10 and consider awesome broken for now. Meanwhile, awesome users are recommended to not upgrade from/downgrade to xcb-util 0.3.3. This is really our fault as there should've been more testing and coordination with this update. OK. I've known about this break for quite some time now as there have been many Linux users who had this same problem. In case of something like this in the future, should I send a message to the maintainer telling him/her about the potential break? Also, to anyone who hasn't updated their xcb-util port yet, here's what I did to prevent tools like portmaster from installing the newer version: # touch /var/db/pkg/xcb-util-0.3.3/+IGNOREME Now in portmaster, I get the following message when using -a to update all my ports: === Launching child to update xcb-util-0.3.3 to xcb-util-0.3.4 === xcb-util-0.3.3 has an +IGNOREME file === Update anyway? [n] -- IRC nick: jrick Jabber: jr...@jabber.org http://identi.ca/jrick ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: xcb-util 0.3.4 breaks awesome
On Thu, 2009-05-07 at 18:39 -0400, Josh Rickmar wrote: On Fri, 8 May 2009, Dmitry Marakasov wrote: * Josh Rickmar (joshua_rick...@eumx.net) wrote: That's quite complicated problem actually - xcb-util update has broken awesome; we could update awesome to 3.3-rc1, but it requires startup-notification 0.10 (which likely requires new xcb-util as well). Thus we'll likely have to wait for s-n 0.10 and consider awesome broken for now. Meanwhile, awesome users are recommended to not upgrade from/downgrade to xcb-util 0.3.3. This is really our fault as there should've been more testing and coordination with this update. OK. I've known about this break for quite some time now as there have been many Linux users who had this same problem. In case of something like this in the future, should I send a message to the maintainer telling him/her about the potential break? Sending a HEADS UP message to the maintainer if you are aware of an issue would be a good courtesy and hopefully minimize any breakage. A short delay for a maintainer to address the issue is reasonable, but that is a slippery slope. I say give a reasonable amount of time for the breakage to be addressed (where the definition of reasonable is open to interpretation). If it isn't addressed, please move forward and commit. robert. Also, to anyone who hasn't updated their xcb-util port yet, here's what I did to prevent tools like portmaster from installing the newer version: # touch /var/db/pkg/xcb-util-0.3.3/+IGNOREME Now in portmaster, I get the following message when using -a to update all my ports: === Launching child to update xcb-util-0.3.3 to xcb-util-0.3.4 === xcb-util-0.3.3 has an +IGNOREME file === Update anyway? [n] -- Robert Noland rnol...@freebsd.org FreeBSD signature.asc Description: This is a digitally signed message part
Re: xcb-util 0.3.4 breaks awesome
* Robert Noland (rnol...@freebsd.org) wrote: That's quite complicated problem actually - xcb-util update has broken awesome; we could update awesome to 3.3-rc1, but it requires startup-notification 0.10 (which likely requires new xcb-util as well). Thus we'll likely have to wait for s-n 0.10 and consider awesome broken for now. Meanwhile, awesome users are recommended to not upgrade from/downgrade to xcb-util 0.3.3. This is really our fault as there should've been more testing and coordination with this update. Holding back X or it's sub-components is really not an option. The applications have to keep up. xcb-util doesn't fall under my umbrella, exactly, but I do update it in Xorg sweeps on occasion. Unless the damage is widespread progress must continue. Awesome needs to be patched, updated or marked BROKEN temporarily. Sure, I've just did exactly that - marked awesome BROKEN in presence of newer xcb-util. The note above was for awesome users who, regardless of ports progression and updates, will need a way to use them :) -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
