Re: vim - GTK2 or GTK3?
On Thu, Jan 03, 2019 at 06:08:43PM +0100, Miroslav Lachman wrote: > Adriaan de Groot wrote on 2019/01/03 14:28: > > Niclas wrote: > > > > On Thursday, 3 January 2019 13:00:02 CET freebsd-ports-requ...@freebsd.org > > wrote: > > > > Firefox and Chromium both depend on GTK3, so it's highly likely that a > > > > typical desktop user has GTK3 installed. > > > > > > +1, GTK3 is probably the best choice. > > > > > > As a side note, it looks like libreoffice defaults to GTK2 as well, > > > perhaps it should be switched to GTK3 also? > > > > As a not-really-GTK-using person, I still have both GTK2 and GTK3 installed > > on > > my system running KDE Plasma. Not for vim though: > > > > Installed packages to be REMOVED: > > gtk2-2.24.32 > > fontforge-20170731 > > mftrace-1.2.18_1 > > > > Installed packages to be REMOVED: > > gtk3-3.22.30_4 > > gpsd-3.17 > > > > I'm a fan of pushing for toolkit migration, so reducing the number of things > > that pull in GTK2 is a good thing. > > > > > > So if we're expressing hopes that ports might be made GTK2-free (by porting > > to > > GTK3 for instance) then I'd hope that fontforge gets that treatment, too. > > From > > looking at the source repo, I don't think the GTK2 option actually works > > (and > > the comments suggest it's not all that good anyway). In the configure.ac it > > looks like there are spelling-inconsistencies between > > fontforge_can_use_gtk=yes > > and, e.g,, > > FONTFORGE_ARG_ENABLE_GDK > > > > (mtrace depends on fontforge, so fixing fontforge would clean GTK2 off my > > system) > > It is not so simple. What works for you doesn't work for somebody else. I am > running KDE4 with QT4 but some applications use GTK2 as the only option or I > set them to use GTK2 because GTK2 has better theme integration to KDE4 / QT > style than GTK3 (in my personal case). > And, for example, Total Commander has two choices - QT or GTK2. I tried it > to build with QT but it failed so I switched to GTK2 and it builds fine. > So in my current situation I am glad we have GTK2 and GTK3 and all my > applications are working (better with GTK2 than GTK3). And having both GTK > versions installed is not a big problem. Their size is relatively small > compared to apps like browsers, libreoffice etc. KDE4 is not in the ports tree anymore (since January 01), and Qt4 is marked to go at 2019-03-15. > Miroslav Lachman > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Best Regards, Alexandre C. Guimarães. https://bitbucket.org/rigoletto-freebsd/ signature.asc Description: PGP signature
Re: A potential new porter seeking some clarifications
On Thu, Dec 13, 2018 at 10:41:01PM +0800, Arthur Pirika wrote: > Hi all! I’m hoping to get into porting for FreeBSD, right now just focusing > on one package, a plugin for bitlbee, however I’d like to extend my hand to > maintain other ports in the future once I have more knowledge and practice > with the system. Hello! > Before I start, though, I just need some clarifications of things from the > porter’s handbook. > > 1. If I understand correctly, the version of the ports tree as fetched by > portsnap isn’t the best for working on the tree. I should instead make > another copy of the tree as an svn checkout? Distfiles, however, still go to > /usr/ports/distfiles You don't necessary need use a separated copy of the ports tree, you can use a svn copy in the default location; however it can become a bit problematic sometimes, like when you are working on ports that you use but you won't/can't use the updated version yet. Portsnap is intended for end users only, so it is not really practical to use while working with ports, and you can get all your work deleted with a random tree update. ;-) > 2. Is it absolutely necessary to use poudriere before submitting a port? >I’m still getting to grips with how it works, and if I need to get >comfortable with it first, I’ll do so. Poudriere is the default tool to test ports. The `poudriere testport` facility does several extra checks during the building-packaging process. So, it is very desirable to have its logs when you fill a bug report, since it can speed up the review process. Some help with poudriere: https://github.com/freebsd/poudriere/wiki This is a bit old but still helpful: https://www.digitalocean.com/community/tutorials/how-to-set-up-a-poudriere-build-system-to-create-packages-for-your-freebsd-servers > Thanks! > Arthur You're welcome. > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Best Regards, Alexandre C. Guimarães. https://bitbucket.org/rigoletto-freebsd/ signature.asc Description: PGP signature
Re: Poudriere building far more ports than it should
On Wed, Nov 14, 2018 at 08:57:59PM +0200, Reko Turja via freebsd-ports wrote: > Hello! > > -Original Message- From: Dmytro Bilokha > > On Wed, Nov 14, 2018 at 03:33:38AM +0200, reko.turja--- via freebsd-ports > wrote: > > > > I finally took the hurdle and made a poudriere VM for building my ports > > > instead of building them on target system. At first I did however build > > > every single port I will need on the VM resulting on 240 or so ports. > > > > > > Then I copied over my options, and the list of installed ports etc. and > > > started the build. For some reason poudriere wants to build a ton of > > > extra > > > baggage (360+ ports instead of 240.) > > > > Hello, Reko! > > > Poudriere builds different kinds of ports: > > > 1. Ports from your list. > > 2. Run-time dependencies of ports from your list. 3. Build-time > > dependecies of ports from your list. > < 4. Run-time and build-time dependencies of your ports dependencies, as > well > > That all I know - Ive been using ports and only ports since early 2000's. So > the problem is that I made a dry run from ports, linking only to stuff that > I wanted on the final package receiver. Then I copied the list of ports over > to poudriere using portversion -oQ. When I started the run, there was > suddenly every single dependency I previously dropped brought in. (I know > about automake, autoconf and similar build dependencies.) > > I guess one option would be blacklisting in poudriere those unneeded > dependencies which shouldn't be linked with my packages, if my options are > honoured by poudriere. Do you mean the OPTIONS you previously set were not honoured by poudriere? Just in case, poudriere does not `read` OPTIONS and/or other things like make.conf from the default location but from /usr/local/etc/poudriere.d/* Cheers! > > -Reko > > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Best Regards, Alexandre C. Guimarães. https://bitbucket.org/rigoletto-freebsd/ signature.asc Description: PGP signature
devel/sope2 with MySQL can't be installed
Hi, I tried ton install sope2 with the MySQL connector. At first I tried to install it with the package but by default this connector seems to be disable. So next I tried to install it from the port tree. The compilation is done without any problem, but when I do "make install" I get : pkg-static: Unable to access file /usr/ports/devel/sope2/work/stage/usr/local/GNUstep/Local/Library/GDLAdaptors-4.9/MySQL.gdladaptor/MySQL: No such file or directory pkg-static: Unable to access file /usr/ports/devel/sope2/work/stage/usr/local/GNUstep/Local/Library/GDLAdaptors-4.9/MySQL.gdladaptor/Resources/Info-gnustep.plist: No such file or directory pkg-static: Unable to access file /usr/ports/devel/sope2/work/stage/usr/local/GNUstep/Local/Library/GDLAdaptors-4.9/MySQL.gdladaptor/Resources/Version: No such file or directory pkg-static: Unable to access file /usr/ports/devel/sope2/work/stage/usr/local/GNUstep/Local/Library/GDLAdaptors-4.9/MySQL.gdladaptor/stamp.make: No such file or directory *** Error code 74 And so, it can't be installed. So how can I install sope2 with this connector ? Is it planned to build the binary package with this connector someday soon ? I have also seen some files which seem to be related to a SQLite connector ; does anyone know if it can be used with SOGo ? Best regards, Alexandre <alexan...@lotharedon.org> ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
/net-p2p/qbittorrent-nox11 PORT segmentation fault qbittorrent-nox
Hi, I filled a bug here https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203081 because net-p2p/qbittorrent-nox11 does not works after upgrade to v3.2.3. I upgraded net-p2p/libtorrent-rasterbar to v1.0.6 too. I encounter an issue when starting qbittorrent-nox: --- Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org and provide the following backtrace: qBittorrent version: v3.2.3 stack trace: segmentation fault qbittorrent-nox --- # uname -a FreeBSD sd-44877.local 10.2-RELEASE FreeBSD 10.2-RELEASE #0 r28: Wed Aug 12 15:26:37 UTC 2015 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 -- Thank you for your support. Kind regards. Alexandre ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
p5-Elasticsearch port renamed
Hi list, r349932 has renamed textproc/p5-Elasticsearch to textproc/p5-Search-Elasticsearch. Shouldn't deserve a entry in UPDATING and/or a mention anywhere ? ___ 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 port: zabbix2-server-2.0.10
Hi, i have just a little question : actually i am using zabbix 2.0.10 port and i wanted to upgrade to 2.2.1. As zabbix2 is different from zabbix22 port it's actually not possible. Are there plan to merge the two ports and allow upgrade from 2.0 to 2.2? If not, the migration process should be handled manually? Thanks Best regards, smime.p7s Description: S/MIME cryptographic signature
ASSP current stable
Hi, as mentioned in ASSP 1.9x latest changelog, ASSP 1.98 any build are no longer maintained and the only stable version is build 1.99 (13098) : ASSP changelog assp.pl 1.99 (13106) -There is no developer version 1.98 any longer. -There is only a stable version starting with build 1.99 (13098). Are there any plans to upgrade FreeBSD ASSP port? Thanks Regards, MAIRIE DE SALLANCHES Direction des Systèmes d'Information Alexandre RAYNAUD email: alexandre.rayn...@sallanches.fr ___ 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 Port: fping-3.4
Hi, i just wanted to inform you that i have filled an issue on fping github. Fping is not fully compatible with freebsd os. https://github.com/schweikert/fping/issues/39 also tested with FreeBSD 8 always same result. Have a nice day. Cheers, MAIRIE DE SALLANCHES Direction des Systèmes d'Information Alexandre RAYNAUD email: alexandre.rayn...@sallanches.fr ___ 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: Portmaster 3.1 upgrade
On Sun, Oct 31, 2010 at 6:22 PM, David Wolfskill da...@catwhisker.orgwrote: On Sun, Oct 31, 2010 at 05:57:52PM +0100, Alexandre wrote: Hi, I read in /usr/ports/UPGRADING the instructions to properly upgrade PORTMASTER 3.1. It is written to do : # pkg_delete -f portmaster* # cd /usr/ports/ports-mgmt/portmaster make clean make install clean But when I type the first one, I got the message : pkg_delete: No match. Portmaster is installed : #pkg_info | grep portmaster portmaster-3.0 Manage your ports without external databases or languages I know that I can uninstall and reinstall portmaster using # pkg_delete portmaster-3.0 and the second command mentionned #make install clean I just write this message because this instruction is written in /usr/ports/UPDATING Change the pkg_delete invocation from: # pkg_delete -f portmaster* to: # pkg_delete -f 'portmaster*' so the shell will leave the wildcard alone. Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpghttp://www.catwhisker.org/%7Edavid/publickey.gpgfor my public key. Thanks to all ! # pkg_delete -f 'portmaster*' works for me. I have also use this command to upgrade to portmaster v3.2 as suggested by Doug Barton. ___ 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
Portmaster 3.1 upgrade
Hi, I read in /usr/ports/UPGRADING the instructions to properly upgrade PORTMASTER 3.1. It is written to do : # pkg_delete -f portmaster* # cd /usr/ports/ports-mgmt/portmaster make clean make install clean But when I type the first one, I got the message : pkg_delete: No match. Portmaster is installed : #pkg_info | grep portmaster portmaster-3.0 Manage your ports without external databases or languages I know that I can uninstall and reinstall portmaster using # pkg_delete portmaster-3.0 and the second command mentionned #make install clean I just write this message because this instruction is written in /usr/ports/UPDATING ___ 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: some problem with portsnap servers?
Portsnap builds were temporarily offiline pending a move to new hardware, but portsnap builds are back online. Thanks Colin for these informations. On Thu, Sep 30, 2010 at 9:23 PM, Ruslan Mahmatkhanov cvs-...@yandex.ruwrote: Hi! I have not have any updates from aprox 2010/09/30 14:00 +0400. portsnap says that ports tree is up to date all the time. It's just me or anybody have this problem right now? -- Regards, Ruslan ___ 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: Web feed for /usr/ports/UPDATING
Really nice. I like the Atom feed. Thanks. On Fri, Sep 24, 2010 at 5:39 AM, Alexander Kojevnikov alexan...@kojevnikov.com wrote: Hi list, Since the only SUBJ I could find [0] is long since dead I created my own: http://updating.versia.com/ Any feedback is welcome. Cheers, Alex [0] http://lists.freebsd.org/mailman/htdig/freebsd-ports/2005-June/024285.html ___ 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
Install Fuse-SSHFS from ports or from Fuse Website Project ?
Hi, I want to use Fuse-SSHFS http://www.freshports.org/sysutils/fusefs-sshfs/but the port is old (and it got a Sanity Test Failure). When I go to the website of the project Fuse http://sourceforge.net/projects/fuse/ , there is a more recent version fuse-2.8.4.tar.gz and available (?) for FreeBSD. Is anyone is using Fuse-SSHFS and which version : the one from ports or from the project website ? I haven't found anything on Google. Best Regards, Alexandre. ___ 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 Port: openx-2.8.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I think the FreeBSD port is currently having securities issues. We are using OpenX from the ports, and since September, 18th, it's been everyday that some script-kiddie-like injects stuff in our database which needs to be cleaned following http://blog.openx.org/09/security-update-how-to-secure-your-openx-installation/ I'm still checking for suspect installed but I think you may have to upgrade the ports. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyYT5wACgkQfP+GwT1GJ3HpfgCfTxuPk5LuF6FrqUf/Gz4LB/nS v9wAn2pSCJKPiCK3Pz1YwJ/x4pAac6mr =+61S -END PGP SIGNATURE- ___ 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: FreeBSD Port: openx-2.8.2
Hello, Thanks, I didn't saw this one, sorry for the noise. And thanks for your work. Le 21/09/2010 09:56, cvs-...@yandex.ru a écrit : 21.09.10, 11:54, Alexandre LISSY : -BEGIN PGP SIGNED MESSAGE-Hash: SHA1Hello,I think the FreeBSD port is currently having securities issues. We areusing OpenX from the ports, and since September, 18th, it's beeneveryday that some script-kiddie-like injects stuff in our databasewhich needs to be cleaned followinghttp://blog.openx.org/09/security-update-how-to-secure-your-openx-installation/I'm still checking for suspect installed but I think you may have toupgrade the ports.-BEGIN PGP SIGNATURE-Version: GnuPG v1.4.10 (GNU/Linux)Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/iEYEARECAAYFAkyYT5wACgkQfP+GwT1GJ3HpfgCfTxuPk5LuF6FrqUf/Gz4LB/nSv9wAn2pSCJKPiCK3Pz1YwJ/x4pAac6mr=+61S-END PGP signature-___freebsd-po...@freebsd.org mailing listhttp://lists.freebsd.org/mailman/listinfo/freebsd-portsTo unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org There is PR about this: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/150610 Maintainer approved it. Just wait while it will be commited to the ports tree or apply patch from PR manually if you need it right now. ___ 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 : polkit-0.95_3: update fails
You could read /usr/ports/UPDATING because there is section for policikit and polkit. --- En date de : Ven 22.1.10, O. Hartmann ohart...@zedat..fu-berlin.de a écrit : De: O. Hartmann ohart...@zedat.fu-berlin.de Objet: polkit-0.95_3: update fails À: freebsd-questi...@freebsd.org, freebsd-ports@freebsd.org Date: Vendredi 22 Janvier 2010, 15h45 I try to update ports via 'portmaster -av' on a regular basis and ran into a sticky problem with poolkit and docbook I'm incapable to solve. Error message follows. Does anybody has any hint or tip? Please email me in CC. Regards, Oliver === Starting build for for ports that need updating === === Launching child to update polkit-0.95_3 === Port directory: /usr/ports/sysutils/polkit === Starting check for build dependencies === Gathering dependency list for sysutils/polkit from ports === Starting dependency check === Checking dependency: devel/eggdbus === Checking dependency: devel/gettext === Checking dependency: devel/glib20 === Checking dependency: devel/gmake === Checking dependency: devel/gobject-introspection === Checking dependency: devel/pkg-config === Checking dependency: textproc/docbook-410 === Launching child to update textproc/docbook-410 polkit-0.95_3 textproc/docbook-410 === Port directory: /usr/ports/textproc/docbook-410 === Starting check for build dependencies === Gathering dependency list for textproc/docbook-410 from ports === Starting dependency check === Checking dependency: archivers/unzip === Dependency check complete for textproc/docbook-410 polkit-0.95_3 textproc/docbook-410 === Cleaning for docbook-4.1_3 === Vulnerability check disabled, database not found === Extracting for docbook-4.1_3 = MD5 Checksum OK for docbk41.zip. = SHA256 Checksum OK for docbk41.zip. === docbook-4.1_3 depends on file: /usr/local/bin/unzip - found === Patching for docbook-4.1_3 === Configuring for docbook-4.1_3 === Starting check for runtime dependencies === Gathering dependency list for textproc/docbook-410 from ports === Starting dependency check === Checking dependency: textproc/iso8879 === Launching child to update textproc/iso8879 polkit-0.95_3 textproc/docbook-410 textproc/iso8879 === Port directory: /usr/ports/textproc/iso8879 === Starting check for build dependencies === Gathering dependency list for textproc/iso8879 from ports === Starting dependency check === Checking dependency: archivers/unzip === Dependency check complete for textproc/iso8879 polkit-0.95_3 textproc/docbook-410 textproc/iso8879 === Cleaning for iso8879-1986_2 === Vulnerability check disabled, database not found === Extracting for iso8879-1986_2 = MD5 Checksum OK for isoENTS.zip. = SHA256 Checksum OK for isoENTS.zip. === Patching for iso8879-1986_2 === iso8879-1986_2 depends on executable: unzip - found === Configuring for iso8879-1986_2 === Starting check for runtime dependencies === Gathering dependency list for textproc/iso8879 from ports === Starting dependency check === Checking dependency: textproc/xmlcatmgr === Dependency check complete for textproc/iso8879 polkit-0.95_3 textproc/docbook-410 textproc/iso8879 === Installing for iso8879-1986_2 === Generating temporary packing list xmlcatmgr: entry already exists for `iso8879/catalog' of type `CATALOG' *** Error code 1 Stop in /usr/ports/textproc/iso8879. === Installation of iso8879-1986_2 (textproc/iso8879) failed === Aborting update === Update for textproc/iso8879 failed === Aborting update === Update for textproc/docbook-410 failed === Aborting update === Update for polkit-0.95_3 failed === Aborting update ___ freebsd-questi...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-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
FreeBSD Port: ocsinventory-ng-1.02.1
Hi, Actually i would like to use the port you maintain on a freebsd box (8.0) already installed with apache22 and mysql55-server. I have tried to install ocsinventory-bg-1.02.1 but that's is not possible because of dependencies (http://pastebin.com/m6bb44729) Have you planned to update the ocsinventory-bg-1.02.1 for using mysql 5.0 and apache22? If not, is there a way for me to install ocsinventory-bg-1.02.1port considering my system already run apache22 and mysql55-server? Some contributor to ocsinventory told me about changing the makefile ocsinventory freebsd port.. Sorry to disturb you, just answer if you can. Have a nice day!!! MAIRIE DE SALLANCHES Service Informatique et Télécommunication Alexandre RAYNAUD email: service.i...@ville-sallanches.fr ___ 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: Call for tester: VirtualBox 3.1.2 for FreeBSD (take 2)
On Mon, 2010-01-04 at 18:31 +0100, Beat Gaetzi wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, First of all thanks a lot for all the valuable feedback. We have updated the ports Works without a problem here on FreeBSD 8.0-STABLE #0 r201431 i386 with Windows XP and Debian Lenny guests. Thank you very much for this work. -- Alexandre Kovalenko (Олександр Коваленко) ___ 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: Unhappy Xorg upgrade
On Sat, 2009-01-31 at 16:25 -0500, Alex Goncharov wrote: ,--- You/vehemens (Sat, 31 Jan 2009 11:53:58 -0800) * | In general when upgrading, you take your chances. If a port upgrade | fails, you should fall back to what worked. So, a *fundamental* (practically an OS component) port is brought in -- and it disables my system. What is my way of action? Right -- install the old packages, taken from an FTP site (is there a way to get the previous source, that is all the ports/*/*/Makefile files? Csup can only go forward -- or can it go back?) When I install the old packages, I can no longer rebuild and install new (say `csup'ed on 2009-03-01) port components, as one whole -- I can only do it selectively, excluding from the upgrade most X-dependent things. That sucks and will lead to a problem earlier or later. Will combination of sysutils/portdowngrade and HOLD_PKGS variable in /usr/local/etc/pkgtools.conf accomplish what you are trying to accomplish? -- Alexandre Sunny Kovalenko ___ 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: 7-STABLE regression that breaks lang/drscheme is src/contrib/gcc/gthr-posix.h 1.1.1.8.2.1
On Tue, 2008-01-22 at 21:10 +1100, Andrew Reilly wrote: Hi Marius, On Tue, 22 Jan 2008 10:33:27 +0100 Marius Strobl [EMAIL PROTECTED] wrote: The __gthread_active_p(), which returns false positives prior to the current version of gthr-posix.h, isn't only used in libstdc++ but also in headers that are installed beneath /usr/include/c++. So the code in those headers compiled into an existing binary which was built prior to the gthr-posix.h fix still might erroneously determine that it's running in a threaded environment while f.e. libstdc++ does not, causing the problems you see. Did you try a mred built on a stock 7-STABLE? When it first stopped working (around the 11th, from memory), my first approach was to rebuild it (over and over, and attempt to debug it...) No joy that way. It's only since I reverted to the earlier version of FreeBSD that it's started working again. As part of the attempt to make mred work again, I re-built *all* of the ports that I have installed (some 900-odd), so all of the libraries in /usr/local/lib are post-15 Jan., and have whatever effect the change introduces. Perhaps that is why epiphany has gone unstable on me (seems to be complaining about failing to connect to gnomevfs). I suspect that mred wasn't minding false-positives before, because it's been configured/compiled with pthreads enabled (for the benefit of Mesa/OpenGL, apparently). If you think that it might help to track things down, I can jump forward to -STABLE again and rebuild at least all of mred's dependencies, but that's going to be a slow process... Reckon I'll give that a go. No point staying in the past, now that we know where abouts the breakage occurred. Am I right to assume that this is *not* i386? I have 7-PRERELEASE (i386) cvsup'ed on January 22, early morning EST, and mred built from vanilla 372 sources (per your earlier recommendation) on January 8th. They seem to be pretty happy with each other. If there is any information I can provide that will help you with your quest, please, let me know. Cheers, -- Alexandre Sunny Kovalenko ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
[patch] glib20, UTF-8 and string collation
I have seen recent commit WRT string collation in devel/glib20 by
marcus, so I have decided to check if there is an interest to fix SEGV
in g_utf8_collate when it is given 8-bit non-UTF-8 string(s) to collate.
Good (but by no means only) example of this would be using Evolution to
open mailbox with the mix of KOI-8, CP1251 and UTF-8 message subjects
and order them by the subject. Admittedly, I do not know whether there
are special symbols that trigger the situation or any mix would do. vova
at fbsd ru posted test case mailbox under the link below.
Full discussion including my first approach to fix this problem could be
found here
http://bugzilla.gnome.org/show_bug.cgi?id=492389
Slightly different approach is attached to this E-mail.
Without either patch, my Evolution will core dump on start-up.
First patch was rejected by gnome folks with the recommendation Don't
do that, which, unfortunately, is not that easy to follow ;)
Any comments from people with the knowledge of gnome, UTF-8 and string
collation will be greatly appreciated.
I am not subscribed to ports@, please, make sure to keep me on CC list
when replying.
--
Alexandre Sunny Kovalenko
--- glib/gunidecomp.c.BAK 2008-01-09 09:07:46.0 -0500
+++ glib/gunidecomp.c 2008-01-09 09:17:04.0 -0500
@@ -22,6 +22,7 @@
#include config.h
#include stdlib.h
+#include string.h
#include glib.h
#include gunidecomp.h
@@ -528,6 +529,14 @@
result = g_ucs4_to_utf8 (result_wc, -1, NULL, NULL, NULL);
g_free (result_wc);
+ // Upstream callers rely on the returned pointer to be valid
+ // and produce core if it does not (witness collation routine).
+#define NOT_VALID_UTF8_STRING *** This was not a valid UTF-8 string ***
+ if(!result)
+ {
+result = g_malloc(strlen(NOT_VALID_UTF8_STRING) + 1);
+strcpy(result, NOT_VALID_UTF8_STRING);
+ }
return result;
}
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [patch] glib20, UTF-8 and string collation
On Wed, 2008-01-09 at 12:35 -0500, Joe Marcus Clarke wrote:
On Wed, 2008-01-09 at 10:53 -0500, Alexandre Sunny Kovalenko wrote:
I have seen recent commit WRT string collation in devel/glib20 by
marcus, so I have decided to check if there is an interest to fix SEGV
in g_utf8_collate when it is given 8-bit non-UTF-8 string(s) to collate.
Any commits I have made in the area of UTF-8 are completely accidental.
I am not the UTF-8 guy. Both bland and jylefort have expressed interest
in this. Perhaps one of them will comment.
I hope so. Just in case, they would decide to, I have reduced the
situation to the small program below. I get
GLib-CRITICAL **: g_convert: assertion `str != NULL' failed
and no core dump from this simple program, whereas Evolution manages to
pass NULL to strcoll further down in g_utf8_collate and get SEGV for its
pains.
Conversely, if the answer still is Evolution should not have done
that, I will happily crawl back under my rock and keep my patch
locally.
#include stdio.h
#include glib.h
int main(int argc, char *argv[])
{
GString *str1 = g_string_new(\xf3\xcf\xd2\xcf\xcb\x20\xd7\xcf\xd3\xc5
\xcd\xd8\x20\xcf\xc2\xc5\xda\xd8\xd1\xce\x2e\x2e\x2e);
GString *str2 = g_string_new(Goodbye, cruel world!);
printf(%s\n, str1-str);
if(g_utf8_collate(str1-str, str2-str) == 0)
g_print(%s and %s are equal\n, str1-str, str2-str);
else
g_print(%s and %s are NOT equal\n, str1-str, str2-str);
}
built with
gcc `pkg-config --cflags glib-2.0` -g -o testCollate testCollate.c
`pkg-config --libs glib-2.0`
on
7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #0: Sat Jan 5 22:37:29 EST 2008
using
glib-2.14.5 and libiconv-1.11_1
option fix string collation was set during the build of glib.
I'm not sure why the malloc and copy. Why not just use g_strdup()?
Because I don't know much of anything about glib programming, and I was
suspecting that someone will use g_free() on the result, so g_malloc()
sounded like the plausible candidate. I really hope someone with
the necessary knowledge will come up with the right solution, but, for
now, I do what I can.
--
Alexandre Sunny Kovalenko
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [patch] glib20, UTF-8 and string collation
On Wed, 2008-01-09 at 20:16 -0500, Joe Marcus Clarke wrote:
On Wed, 2008-01-09 at 19:40 -0500, Alexandre Sunny Kovalenko wrote:
On Wed, 2008-01-09 at 12:35 -0500, Joe Marcus Clarke wrote:
On Wed, 2008-01-09 at 10:53 -0500, Alexandre Sunny Kovalenko wrote:
I have seen recent commit WRT string collation in devel/glib20 by
marcus, so I have decided to check if there is an interest to fix SEGV
in g_utf8_collate when it is given 8-bit non-UTF-8 string(s) to collate.
Any commits I have made in the area of UTF-8 are completely accidental.
I am not the UTF-8 guy. Both bland and jylefort have expressed interest
in this. Perhaps one of them will comment.
I hope so. Just in case, they would decide to, I have reduced the
situation to the small program below. I get
GLib-CRITICAL **: g_convert: assertion `str != NULL' failed
and no core dump from this simple program, whereas Evolution manages to
pass NULL to strcoll further down in g_utf8_collate and get SEGV for its
pains.
That sounds like a no-no for Evolution to be dereferencing a NULL
pointer. Hopefully they'd fix this to prevent the problem.
It's not Evolution, it is glib, specifically g_utf8_collate, which would
call strcoll(3) blindly on the return of g_utf8_normalize inside
gunicollate.c. And now, I can get core dumped out of this simple program
as well, merely by setting CHARSET=en_US.UTF-8 (I had it is ASCII in the
terminal window, which would trigger different path within
g_utf8_collate).
Conversely, if the answer still is Evolution should not have done
that, I will happily crawl back under my rock and keep my patch
locally.
I can't imagine you're alone in this. But then again, any Cyrillic mail
that comes my way is always spam, so what do I know.
More importantly, it is UTF-8 spam -- in order to trigger this, you need
KOI8-R or CP1251, and in the sorted column to boot. I suspect that
Latin1 or ShiftJIS would do the trick too.
Now, how about this: would you be amenable to this Really Harmless(tm)
patch, which merely adds error checking along the lines used in the same
function, about dozen lines up ;)
--- glib/gunicollate.c.B 2008-01-09 20:48:25.0 -0500
+++ glib/gunicollate.c 2008-01-09 20:49:35.0 -0500
@@ -166,6 +166,9 @@
str1_norm = g_utf8_normalize (str1, -1, G_NORMALIZE_ALL_COMPOSE);
str2_norm = g_utf8_normalize (str2, -1, G_NORMALIZE_ALL_COMPOSE);
+ g_return_val_if_fail (str1_norm != NULL, 0);
+ g_return_val_if_fail (str2_norm != NULL, 0);
+
if (g_get_charset (charset))
{
result = strcoll (str1_norm, str2_norm);
I can add it to your files/extra-patch-glib_gunicollate.c, or package
it separately -- I really hate it when I start Evolution after portupgrade
to write some E-mails real quick, only to find out that I have forgotten
to patch glib... again.
--
Alexandre Sunny Kovalenko
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [patch] glib20, UTF-8 and string collation
On Thu, 2008-01-10 at 13:18 +0900, Alexander Nedotsukov wrote:
Alexandre,
The problem you exposed have its roots in Evo code. g_utf8_* stuff
defined to work on *utf-8* strings only and have undefined behaviour on
MBCS strings. It may sound stupid but crashes are allowed in this case
:-) Even we apply your latest patch the true problem solution will be
only postponed. We have to continue with Evo source. Find subject parser
part and ensure that it will be utf-8 encoded string at the end.
rant
While I see this as the noble goal, I fail to understand why asserts are
OK 10 lines above my latest patch, but not in this specific place. Nor
does this latest patch mask any issues in Evo -- you still get
Glib-CRITICAL assert. Hell, you even get assert without the patch if
your CHARSET is ASCII, but core dump if your CHARSET is xx_YY.UTF-8. If
we are talking noble goals here, how about some consistency in the error
handling?
/rant
On the more productive note: I have picked up more glib programming
today than I had before (or cared to) -- it's easy to improve when you
started from the veritable zero ;) However, it might not be sufficient
to do what needs to be done to Evolution. One thing you can help me
with, is to suggest glib function, I can feed arbitrary string of bytes
(either counted or zero-terminated) and it will tell me whether this is
valid UTF-8. g_print() apparently does this somehow, so there must be a
way.
As promised, I'll crawl back under my rock and wait for rainy weekend to
read some Evolution code.
All the best,
Alexander.
BTW: What happened to no top posting rule?
Alexandre Sunny Kovalenko wrote:
On Wed, 2008-01-09 at 20:16 -0500, Joe Marcus Clarke wrote:
On Wed, 2008-01-09 at 19:40 -0500, Alexandre Sunny Kovalenko wrote:
On Wed, 2008-01-09 at 12:35 -0500, Joe Marcus Clarke wrote:
On Wed, 2008-01-09 at 10:53 -0500, Alexandre Sunny Kovalenko wrote:
I have seen recent commit WRT string collation in devel/glib20 by
marcus, so I have decided to check if there is an interest to fix SEGV
in g_utf8_collate when it is given 8-bit non-UTF-8 string(s) to collate.
Any commits I have made in the area of UTF-8 are completely accidental.
I am not the UTF-8 guy. Both bland and jylefort have expressed interest
in this. Perhaps one of them will comment.
I hope so. Just in case, they would decide to, I have reduced the
situation to the small program below. I get
GLib-CRITICAL **: g_convert: assertion `str != NULL' failed
and no core dump from this simple program, whereas Evolution manages to
pass NULL to strcoll further down in g_utf8_collate and get SEGV for its
pains.
That sounds like a no-no for Evolution to be dereferencing a NULL
pointer. Hopefully they'd fix this to prevent the problem.
It's not Evolution, it is glib, specifically g_utf8_collate, which would
call strcoll(3) blindly on the return of g_utf8_normalize inside
gunicollate.c. And now, I can get core dumped out of this simple program
as well, merely by setting CHARSET=en_US.UTF-8 (I had it is ASCII in the
terminal window, which would trigger different path within
g_utf8_collate).
Conversely, if the answer still is Evolution should not have done
that, I will happily crawl back under my rock and keep my patch
locally.
I can't imagine you're alone in this. But then again, any Cyrillic mail
that comes my way is always spam, so what do I know.
More importantly, it is UTF-8 spam -- in order to trigger this, you need
KOI8-R or CP1251, and in the sorted column to boot. I suspect that
Latin1 or ShiftJIS would do the trick too.
Now, how about this: would you be amenable to this Really Harmless(tm)
patch, which merely adds error checking along the lines used in the same
function, about dozen lines up ;)
--- glib/gunicollate.c.B 2008-01-09 20:48:25.0 -0500
+++ glib/gunicollate.c 2008-01-09 20:49:35.0 -0500
@@ -166,6 +166,9 @@
str1_norm = g_utf8_normalize (str1, -1, G_NORMALIZE_ALL_COMPOSE);
str2_norm = g_utf8_normalize (str2, -1, G_NORMALIZE_ALL_COMPOSE);
+ g_return_val_if_fail (str1_norm != NULL, 0);
+ g_return_val_if_fail (str2_norm != NULL, 0);
+
if (g_get_charset (charset))
{
result = strcoll (str1_norm, str2_norm);
I can add it to your files/extra-patch-glib_gunicollate.c, or package
it separately -- I really hate it when I start Evolution after portupgrade
to write some E-mails real quick, only to find out that I have forgotten
to patch glib... again.
--
Alexandre Sunny Kovalenko (Олександр Коваленко)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
[www/p5-libapreq2] Broken ?
Hi, I'm currently trying to install www/rt36 port, with apache22 and mod_perl2, but this requires me to build the perl5 interface to libapreq2 (www/p5-libapreq2). Only problem, it is broken. Any idea as to when it will be back, or if it has been totally abandonned ? Thanks. -- Alexandre Brooks ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
